CN101064884A - Method for processing message based on terminal R3 mobile mode - Google Patents
Method for processing message based on terminal R3 mobile mode Download PDFInfo
- Publication number
- CN101064884A CN101064884A CNA2006100795076A CN200610079507A CN101064884A CN 101064884 A CN101064884 A CN 101064884A CN A2006100795076 A CNA2006100795076 A CN A2006100795076A CN 200610079507 A CN200610079507 A CN 200610079507A CN 101064884 A CN101064884 A CN 101064884A
- Authority
- CN
- China
- Prior art keywords
- message
- mobile
- terminal
- mode
- move mode
- 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.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a method of processing information according to the terminal R3 moving mode, which includes following steps: it sends information to the network entity, said information carries indication information which is used to recognize terminal R3 moving mode; the network entity recognizes the terminal R3 moving mode according to the indication information which is used to recognize the terminal R3 moving mode in the received information, and processes the information. The invention solves the problems that the present technique can not distinguish the information to be processed by the FA or the PMIP client correctly according to the original information.
Description
Technical field
The present invention relates to the wireless metropolitan area network technology, relate to a kind of method concretely according to the terminal R 3 mobile mode processing messages.
Background technology
In present WiMAX WAN (wireless wide area network) technology, WiMAX (microwave interoperability, Worldwide Interoperability for Microwave Access are inserted in the whole world) is the technology that attracts people's attention most.WiMAX is a kind of wireless metropolitan area network technology of IEEE 802.16 standards based on maturation, this standard criterion wireless WAN wireless technology and put the wireless network of multiple spot.IEEE 802.16 is divided into the sublayer with the MAC layer and is used to support different transmission technologys, comprises IPv4, IPv6, Ethernet, ATM(Asynchronous Transfer Mode), thereby makes the WiMAX technology can support multiple different transmission technology.
The WiMAX network mainly is made up of three parts, promptly client (MSS/SS), comprise the accessing business network (ASN) of base station (BS) and accessing business network gate (ASN GW) and comprise prepaid server (PPS), AAA server logic entities such as (AAA Server) be connected service network (CSN).WiMAX network wireless side is based on the wireless MAN access technology of IEEE 802.16d/e standard.What now mainly follow is IEEE 802.16d standard.IEEE 802.16d standard is used for the non line of sight point-to-multipoint technology of metropolitan area network, it mainly is the form of fixing and nomadic network, although the IEEE802.16d of earlier version is mobility between support region not, yet present IEEE 802.16e can support simple mobile communication, under leg speed, support this mobility, and WiMax has begun at present to increase ambulant support at the IP layer.Fig. 1 is the logical architecture figure of WiMAX network.As shown in Figure 1, the WiMAX network mainly comprises 3 parts:
1. client (SS/MS): the user uses this devices accessing WiMAX network.
2. accessing business network (ASN): ASN is defined as the network function set that the WiMAX terminal provides the wireless access service.ASN has comprised BS and ASN-GW network element.Wherein the major function of BS network element is: provide the L2 of BS and MS to be connected, RRM or the like; The major function of ASN-GW network element is: for MS authentication function provides client functionality, provide for MS and switch in the relay function (as IP address assignment), ASN of L3 information etc.
3. connect service network (CSN): CSN is defined as the WiMAX terminal IP is provided Connection Service.The major function that CSN provided is: the IP address assignment of MS, the Internet insert, AAA agency or server, based on user's authorization control etc.
Communicate by the interface from R1 to R6 between the logic entity of three parts, each network element and interface relationship are seen Fig. 1.
Along with the continuous development of technology, mobile IP terminal is more and more higher in the popularity rate of society.Mobile IP terminal may move on network in communication period, and perhaps its IP address can often change.
Because the terminal of Traditional IP technology uses fixed IP addresses and tcp port number to communicate.In communication process, its IP address and tcp port number must remain unchanged, otherwise the IP communication between terminals can't go on.And for mobile IP terminal, if adopt traditional approach, the variation of IP address will cause communication disruption.And mobile IP technology has solved the problem that exists in the Traditional IP, it has been quoted and has handled the principle that cellular mobile telephone is called out, make mobile node adopt changeless IP address, once login can be implemented in and keep on the optional position being connected with the single link layer of IP main frame, makes communication continue to carry out.
The operation principle of mobile IP technology is as shown in Figure 2:
1) multicast that home agent on the network (HA, Home Agent) and Foreign Agent (FA, Foreign Agent) can the cycles or broadcast and act on behalf of broadcast is declared the annexation of itself and link.(act on behalf of and comprise a territory in the broadcast, show that this this Agent Type is home agent or Foreign Agent, comprise Care-of Address (CoA, Care-of-Address) information in the foreign link if Foreign Agent also can comprise a territory.)
2) mobile node receives that these act on behalf of after the broadcast, checks to lay oneself open on the home link still to be on the foreign link.As 1) described in, show that this agency is a home agent if act on behalf of the information that comprises in the broadcast, illustrate that the network that mobile node connects is a home network, need not to adopt the mechanism of mobile IP, all communication process are with normal process is consistent at ordinary times.Show that this agency is a Foreign Agent if act on behalf of the information that comprises in the broadcast, illustrate that so mobile node has moved to field network, will preserve the address information of acting on behalf of in the broadcast.The configuration rules that dispose mobile IP of the Care-of Address of mobile node can be used the IP control protocol (IPCP) or the manual configuration of DHCP (DHCP), peer-peer protocol (PPP).
3) next mobile node can carry out mobile IP registration registration to home agent, informs its Care-of Address of obtaining of home agent.If run into Foreign Agent proxy requests service outwards in the way.
4) home agent is accepted the register requirement of mobile node, obtain after the Care-of Address, some other router on home agent and the home link will declaration itself attract to mail to the packet of moving nodes local address to the accessibility of the network prefix of moving nodes local address on network.Home agent intercepts these packets, and the Care-of Address according to the mobile node registration sends to mobile node by the tunnel with these packets.
5) may be a port (not having Foreign Agent in the middle of when mobile node moves on the foreign link in such cases) of Foreign Agent or mobile node at Care-of Address place-Care-of Address, packet is extracted from the tunnel gives mobile node.
6) simultaneously, the packet that is sent by mobile node directly is routed to destination node, need not tunneling technique.Concerning the bag that all visiting mobile nodes send, Foreign Agent is finished the function of router.
The R3 Move Mode of the mobile IPv 4 terminal in the present stage WiMAX network has 2 kinds: proxy-mobile IP v4 (PMIPv4) Move Mode and client ip v4 (CMIPv4) Move Mode.
Proxy-mobile IP v4 Move Mode: user terminal is not supported the mobile IPv 4 protocol stack, but exists a mobile IP agent client to support the mobile IPv 4 protocol stack in the network.This agent client can replace user terminal to finish the mobile IPv 4 registration.
Client mobile IP v4 Move Mode: user terminal is supported the mobile IPv 4 protocol stack, can receive the broadcasting of Foreign Agent, can carry out the mobile IPv 4 registration to home agent.
R3 is the home agent and the Foreign Agent of connecting terminal and the passage that transmits data for this terminal.R3 switch (R3_relocate.request) be meant the home agent of terminal and new Foreign Agent set up data channel and remove and old Foreign Agent between data channel.And R3 release (R3_session_release.request) is meant the home agent of terminal and the release of the data channel between its Foreign Agent.
Two kinds of R3 Move Modes of PMIPv4 above-mentioned and CMIPv4 can be got different values by attribute-terminal Move Mode (MS Mobility Mode) that message is carried and represent (as table 1).
Table 1. terminal Move Mode
| Type | |
| Eight | 2 bits |
| Value | Indicates the R3 mobility the MS is using: the R3 Move Mode 00:PMIPv4 that the expression terminal is used represents that the R3 Move Mode of terminal represents that as proxy-mobile IP v4 Move Mode 01:CMIPv4 the R3 Move Mode of terminal represents that as client mobile IP v4 Move Mode 10:CMIPv6 the R3 Move Mode of terminal is |
In addition, two kinds of R3 Move Modes above-mentioned, also the sub-attribute R3 Move Mode (R3 Mobility Mode) of the attribute R3 MM Context (R3 MM context:R3 Mobility Management context) that can be carried by message is got different values and is represented:
00:PMIPv4 represents that the R3 Move Mode of terminal is a proxy-mobile IP v4 Move Mode;
01:CMIPv4 represents that the R3 Move Mode of terminal is a client mobile IP v4 Move Mode;
10:CMIPv6 represents that the R3 Move Mode of terminal is the mobile IP v 6 Move Mode;
11: keep (reserve).
Fig. 3 is in the prior art, the R3 switching flow in up-to-date WiMAX scene 2 documents under the proxy-mobile IP v4 Move Mode:
(1) for network take place R3 switch (R3_Relocate.Request) before terminal home agent and existing mobile IP contextual information between the Foreign Agent of service just is provided for terminal.
(2) for network R3 switching (R3_Relocate.Request) the existing before datapath function body of service and data channel between the target side datapath function body of just providing taking place.
(3) in that taking place, R3 switches the data channel that (R3_Relocate.Request) set up between base station and the target data channel function body before for network.
(4a) accessing business network functional entity (ASN functional entity) R3 that is triggered moves switching.
(4b) the ASN functional entity sends R3_Relocate.Request (R3 handoff request) message to PMIP client (acting on behalf of mobile client).
(4c) the PMIP client is responded switch acknowledgment message R3_Relocate.Confirm and is given the ASN functional entity, agrees to switch.
(5) the PMIP client begins to send mobile IP login request (MIP Registration Request) message through target foreign agent to home agent.
(6) target side FA forwards this mobile IP login request message to the home agent place and carries out mobile IP registration registration.
(7) home agent is verified mobile IP login request, agrees that a back mobile IP registration response message (MIP Registration Reply) is to target side FA.
(8) target side FA receives that mobile IP registration replys (MIP Registration Reply) message and be transmitted to mobile client PMIP client, and the mobile IP registration process is finished.
(9) the PMIP client is responded R3 handoff response (R3_Relocate.Response) message and is given the ASN functional entity, and the expression switching is finished.
(10) refresh data channel between base station and the target data channel function body, and set up the mobile IP contextual information between new home agent and the target foreign agent.
Fig. 4 is in the prior art, the R3 switching flow in up-to-date WiMAX scene 2 documents under the client mobile IP v4 Move Mode:
(1) in that taking place, R3 switches the data channel of having set up between the datapath function body that service just is provided that (R3_Relocate.Request) set up before and the data channel between the target data channel function body and base station and the target data channel function body for network.
(2) network take place R3 switch (R3_Relocate.Request) before terminal home agent and existing mobile IP contextual information between the Foreign Agent of service just is being provided.
(3a) the ASN functional entity sends R3 handoff request (R3_Relocate.Request) message to target foreign agent.
(3b) target foreign agent is responded switch acknowledgment message R3_Relocate.Confirm and is given the ASN functional entity, agrees to switch.
(4) the target side Foreign Agent sends mobile IP broadcast (Mobility Advertisement).
(5) MS obtains Care-of Address from the mobile IP broadcast that target foreign agent is sent, and beginning is sent out mobile IP login request (MIP Registration Request) message through target FA to home agent.Target side FA forwards this mobile IP login request message to the home agent place and carries out the mobile IP registration registration.
(6) home agent is verified mobile IP login request, agrees that back answer IP registration reply message (MIP Registration Reply) is to target FA.Target FA receives message MIP RegistrationReply and is transmitted to mobile client MS that the mobile IP registration process is finished.
(7) target FA responds and switches corresponding message (R3_Relocate.Response) to the ASN functional entity, and the expression switching is finished.
(8) set up new mobile IP contextual information between home agent and the target foreign agent.
(9) refresh existing data channel between base station and the target data channel function body.
(10) the deletion network switches datapath function body that service just is provided that (R3_Relocate.Request) set up before and the data channel between the target side datapath function body in that R3 takes place.
Fig. 5 is in the prior art, and the R3 in up-to-date WiMAX scene 2 documents under the proxy-mobile IP v4 Move Mode discharges flow process.
(1) the ASN functional entity is triggered the back and is sent R3 release request message (R3_Session_Release.Request) to the PMIP client.
(2) after the PMIP client is received message R3_Session_Release.Request, send mobile IP login information (MIP Registration Request) to FA, by the life time (lifetime) in the message (MIP Registration Request) is made as 0, realize the registration that deletion is original.
(3) FA transmits message MIP Registration Request to HA.
(4) HA agrees the registration that deletion is original, replys mobile IP registration response message (MIPRegistration Reply) and gives FA.
(5) FA transmits message MIP Registration Reply and gives the PMIP client, after the PMIP client is received message MIP Registration Reply, respond R3 and discharge corresponding message (R3_Session_Release.Response) to the ASN functional entity, expression R3 discharges and finishes.
Fig. 6 is in the prior art, and the R3 in up-to-date WiMAX scene 2 documents under the client mobile IP v4 Move Mode discharges flow process.
(1) the ASN functional entity is received the triggering (Session release trigger) that session discharges.
(1a) the ASN functional entity is initiated R3 release request by message R3_Session_Release.Request to FA.
(1b) FA receives R3_Session_Release.Request, agrees to discharge R3, responds acknowledge message R3_Session_Release.Confirm and gives the ASN functional entity.
(2) FA sends out and is broadcast to terminal, and the life time that carries (lifetime) is 0.
(3) terminal is sent the original registration of deletion to FA after receiving broadcasting, by the life time (lifetime) in the message mobile IP login request (MIP Registration Request) is made as 0.
(4) FA transmits message MIP Registration Request (lifetime=0) to HA.
(5) HA agrees the registration that deletion is original, responds mobile IP login information (MIP Registration Reply) and gives FA.
(6) FA transmits message MIP Registration Reply and gives terminal.
(7) FA is receiveed the response R3_Session_Release.Response to the ASN functional entity, and expression R3 discharges and finishes.
In existing WiMAX network, when external agent (FA) and the common entity of PMIP client, take place that R3 switches or R3 when discharging, the ASN functional entity is subjected to can sending after the corresponding triggering message R3_Relocate.Request or R3_Session_Release.Request to the FA/PMIP client.Yet, the FA of entity has identical address with the PMIP client altogether, according to message R3_Relocate.Request and the existing form of R3_Session_Release.Request (as Fig. 7), message receiver can't be distinguished by FA according to the attribute that the destination address or the message of message are carried and still bring in these two message of reception by PMIP client.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of method according to the terminal R 3 mobile mode processing messages, by waiting altogether in the message of network entity and carry the indication that is used to discern middle-end R3 Move Mode being sent to external agent/PMIP client, the FA/PMIP client is handled corresponding message according to described indication.Thereby can't correctly distinguish by FA according to original message in the solution prior art still is the problem of PMIP message that client process is received.
In order to realize described purpose, technical scheme of the present invention is:
A kind of method according to the terminal R 3 mobile mode processing messages comprises the steps:
A. send a message to network entity, carry the indication information that is used for identification terminal R3 Move Mode in the described message;
B. network entity comes identification terminal R3 Move Mode according to the indication that is used for identification terminal R3 Move Mode in the message that receives, and described message is handled accordingly.
When described indication information indicating terminal R3 Move Mode was proxy-mobile IP v4, this entity was according to the described message of proxy-mobile IP v4 mode treatment;
When described indication information indicating terminal R3 Move Mode was client mobile IP v4, entity was according to the described message of client mobile IP v4 mode treatment.
Described entity is external agent/proxy mobile IP customer terminal entity altogether.
Step b comprises:
When described indication information indicating terminal R3 Move Mode when acting on behalf of mobile terminal IP v4, this message is handled by proxy mobile IP customer terminal;
When described indication information indicating terminal R3 Move Mode was client mobile IP v4, this message was handled by the external agent.
Described message is that R3 handoff request R3_Relocate.Request message or R3 discharge request R3_Session_Release.Request message.
Described indication information is the attribute MS Move Mode of described message.
Described indication information is the sub-attribute R3 Move Mode of the attribute R3 MM Context of described message.
Beneficial effect of the present invention is, the concrete processing entities and the tupe of network entity message as described in entity (as FA/PMIPv4) is judged by the indication information of discerning the R3 Move Mode according to being used to of carrying in the message that receives especially altogether can't still be that PMIP client brings in the problem of handling described message according to correct the differentiation by FA of original message thereby solved prior art.
Description of drawings
Fig. 1 is the logical architecture figure of WiMAX network;
Fig. 2 is the operation principle schematic diagram of mobile IP;
Fig. 3 is the R3 switching flow figure under the proxy-mobile IP v4 Move Mode in up-to-date WiMAX scene 2 documents;
Fig. 4 is the R3 switching flow figure under the client mobile IP v4 Move Mode in up-to-date WiMAX scene 2 documents;
Fig. 5 is that the R3 under the proxy-mobile IP v4 Move Mode discharges flow chart in up-to-date WiMAX scene 2 documents;
Fig. 6 is that the R3 under the client mobile IP v4 Move Mode discharges flow chart in up-to-date WiMAX scene 2 documents;
Fig. 7 is the form of message R3_Relocate.Request and R3_Session_Release.Request in the prior art;
Fig. 8 is the form of message R3_Relocate.Request of the present invention and R3_Session_Release.Request;
Fig. 9 is the form for message R3_Relocate.Request of the present invention and R3_Session_Release.Request.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, specific embodiments of the invention are elaborated below in conjunction with accompanying drawing.
Core concept of the present invention is by carrying the indication that is used for identification terminal R3 Move Mode in the message that sends to entity at transmit leg, carry out corresponding processing method, as message as described in determining according to indication information to handle by which recipient and/or determine with as described in the tupe etc. of message.Describe below by specific embodiment.
In order to realize the present invention, in the WiMAX network, when FA and PMIP client are total to entity, carry the indication that is used for identification terminal R3 Move Mode when sending out message can the regulation message sender for the FA/PMIP clients entities, the FA/PMIP clients entities is judged according to the indication that is used for identification terminal R3 Move Mode of receiving and corresponding the processing.
(1) at first the present invention can come indicating terminal R3 Move Mode by carry attribute user Move Mode (MS Mobility Mode) in message R3_Relocate.Request or R3_Session_Release.Requet:
When the R3 Move Mode of the attribute MS Mobility Mode indicating terminal that carries in message R3_Relocate.Request or the R3_Session_Release.Requet is PMIPv4, this message is transferred to the PMIP client process, and the PMIP client is initiated to the registration of HA subsequently; When the R3 Move Mode of the attribute MS Mobility Mode indicating terminal that carries when message was CMIPv4, this message was transferred to FA and is handled, and FA can send mobile IP broadcast.
Equally, can also determine the processing mode of entity by described indication information to described message.As: attribute user Move Mode (the MS Mobility Mode) indication of carrying in the message of receiving according to entity, when indicating terminal R3 Move Mode was PMIPv4, entity was according to proxy-mobile IP v4 mode treatment; When indicating terminal R3 Move Mode was CMIPv4, entity was according to client mobile IP v4 mode treatment.
Here the form of message R3_Relocate.Request and R3_Session_Release.Requet as shown in Figure 8.
(2) in addition, the present invention can also be by carrying attribute R3 MM Context (R3MM context) in message R3_Relocate.Request or R3_Session_Release.Requet, and come indicating terminal R3 Move Mode by the sub-attribute R3 Move Mode (R3 Mobility Mode) of R3 MM context:
When the R3 Move Mode of the sub-attribute R3 Mobility Mode indicating terminal of the attribute R3 MM context that carries in message R3_Relocate.Request or the R3_Session_Release.Requet is PMIPv4, this message is transferred to the PMIP client process, and the PMIP client is initiated to the registration of HA subsequently; When the R3 Move Mode of the sub-attribute R3 Mobility Mode indicating terminal of the attribute R3 MM context that carries when message was CMIPv4, this message was transferred to FA and is handled, and FA can send mobile IP broadcast.
Equally, can also determine the processing mode of entity by described indication information to described message.As: the contextual sub-attribute R3 Move Mode terminal indication of the attribute R3 MM that has in the message of receiving according to entity, when indicating terminal R3 Move Mode was PMIPv4, entity was according to proxy-mobile IP v4 mode treatment; When indicating terminal R3 Move Mode was CMIPv4, entity was according to client mobile IP v4 mode treatment.
Here the form of message R3_Relocate.Request and R3_Session_Release.Requet as shown in Figure 9.
Above embodiment indicates the R3 Move Mode by message attributes MS Mobility Mode or the sub-attribute R3 of message Mobility Mode, but the present invention is not limited to this, so long as can indicate the parameter or the attribute of other setting of R3 Move Mode to be equally applicable to the present invention.In addition, network entity is indicated other similar judgement and processing of making according to receiving the terminal R 3 mobile mode that carries in the message, comprises within the scope of the invention too.
Below only be the present invention to be described by message R3_Relocate.Request and R3_Session_Release.Requet, but the present invention is not limited to this two message, but is used in the message that other carries the indication that is used for identification terminal R3 Move Mode equally.
In sum, in the WiMAX network, FA and PMIP client be entity altogether, still bring in the message that processing is received by PMIP client by the FA/PMIP clients entities is judged by FA according to the indication that is used for the identification terminal Move Mode of carrying in the message of being received, solved prior art and can't still bring in the problem of handling the message of receiving according to correct differentiation of original message by FA by PMIP client.
Above embodiment only is used to illustrate the present invention, but not is used to limit the present invention.Within the spirit and principles in the present invention all, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (7)
1. the method according to the terminal R 3 mobile mode processing messages is characterized in that comprising the steps:
A. send a message to network entity, carry the indication information that is used for identification terminal R3 Move Mode in the described message;
B. network entity comes identification terminal R3 Move Mode according to the indication that is used for identification terminal R3 Move Mode in the message that receives, and described message is handled accordingly.
2. method according to claim 1 is characterized in that:
When described indication information indicating terminal R3 Move Mode was proxy-mobile IP v4, this entity was according to the described message of proxy-mobile IP v4 mode treatment;
When described indication information indicating terminal R3 Move Mode was client mobile IP v4, entity was according to the described message of client mobile IP v4 mode treatment.
3. method according to claim 1 is characterized in that:
Described network entity is external agent/proxy mobile IP customer terminal entity altogether.
4. method according to claim 3 is characterized in that step b comprises:
When described indication information indicating terminal R3 Move Mode when acting on behalf of mobile terminal IP v4, this message is handled by proxy mobile IP customer terminal;
When described indication information indicating terminal R3 Move Mode was client mobile IP v4, this message was handled by the external agent.
5. method according to claim 1 is characterized in that:
Described message is that R3 handoff request message or R3 discharge request message.
6. according to any described method among the claim 1-5, it is characterized in that:
Described indication information is the attribute terminal Move Mode MS Mobility Mode of described message.
7. according to any described method among the claim 1-5, it is characterized in that:
Described indication information is the sub-attribute terminal R 3 mobile mode of the attribute R3 MM Context of described message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100795076A CN101064884A (en) | 2006-04-25 | 2006-04-25 | Method for processing message based on terminal R3 mobile mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100795076A CN101064884A (en) | 2006-04-25 | 2006-04-25 | Method for processing message based on terminal R3 mobile mode |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101064884A true CN101064884A (en) | 2007-10-31 |
Family
ID=38965537
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006100795076A Pending CN101064884A (en) | 2006-04-25 | 2006-04-25 | Method for processing message based on terminal R3 mobile mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101064884A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101860849A (en) * | 2009-12-29 | 2010-10-13 | 中国科学院声学研究所 | Method for judging and informing terminal R3 mobile mode in WiMAX network |
-
2006
- 2006-04-25 CN CNA2006100795076A patent/CN101064884A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101860849A (en) * | 2009-12-29 | 2010-10-13 | 中国科学院声学研究所 | Method for judging and informing terminal R3 mobile mode in WiMAX network |
| CN101860849B (en) * | 2009-12-29 | 2012-08-15 | 中国科学院声学研究所 | Method for judging and informing terminal R3 mobile mode in WiMAX network |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101119101B1 (en) | Method for Allocating IP Address in Broadband Wireless Access System | |
| JP4903855B2 (en) | Method and apparatus for wireless packet data service connection handoff | |
| CN1245844C (en) | Router for mobile communication network and mobile communication terminal | |
| CN1898933A (en) | Methods and apparatus for network initiated data services | |
| KR101439270B1 (en) | Support for continuity of tunnel communications for mobile nodes having multiple care of addressing | |
| US10484903B2 (en) | Bearer service in communications | |
| CN101043737A (en) | Terminal and terminal switching method and system | |
| EP1782605A1 (en) | A method, network elements, a terminal, a network infrastructure, and a communication system for triggering events | |
| WO2000054475A1 (en) | Multicast handover for mobile internet protocol | |
| CN1802024A (en) | Method for carrying out management on information of terminal quitting idle mode | |
| CN1992606A (en) | NGN network system and method for implementing mobility management | |
| CN101047673A (en) | Method and system for acquiring terminal address correlation information | |
| US8767622B2 (en) | Method and system for managing address prefix information associated with handover in networks | |
| CN1112014C (en) | Wireless network roaming method of cross IP domain | |
| CN101060692A (en) | A switching method and system for wireless evolution network | |
| CN1181655C (en) | Data packet transmission method in mobile IP | |
| CN1960569A (en) | Method for quickening switch of terminal | |
| CN101035359A (en) | Method for apprizing the binding result of the target network address and mobile user terminal | |
| KR101373354B1 (en) | Mobility management method and system using proxy mobile ip and mobile ip context transfer in a mobile telecommunication system | |
| CN101047710A (en) | Method for implementing terminal denetwork at agent mobile network protocol | |
| CN1870819A (en) | Method of route optimization for implementing IPv6 communication buddy supporting mobile IPv6 | |
| CN1306775C (en) | Mobile node, mobile communication system, communication control method and access router | |
| CN1324924C (en) | Method for realizing mobile node switching in mobile IP | |
| CN101043717A (en) | Method for notifying terminal R3 mobile mode to WiMAX network | |
| CN101064884A (en) | Method for processing message based on terminal R3 mobile mode |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |