CN1816036A - Method for realizing protocol edition compatible between apparatuses in mobile IP network - Google Patents
Method for realizing protocol edition compatible between apparatuses in mobile IP network Download PDFInfo
- Publication number
- CN1816036A CN1816036A CN 200510004834 CN200510004834A CN1816036A CN 1816036 A CN1816036 A CN 1816036A CN 200510004834 CN200510004834 CN 200510004834 CN 200510004834 A CN200510004834 A CN 200510004834A CN 1816036 A CN1816036 A CN 1816036A
- Authority
- CN
- China
- Prior art keywords
- mobile
- protocol version
- message
- protocol
- network
- 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
Abstract
Adding extension field of protocol version number to registered information message of mobile IP, the method makes party of sending message possible to inform party of receiving message that protocol version number is adopted in the party of sending message. According to version number, the party of receiving message determines relevant protocol process mode so as to guarantee compatibility between devices of implementing new/old version according to mobile IP protocol. The invention guarantees that mobile nodes can obtain mobile IP protocol service reliably, and ensures interoperability between devices from different manufacturers. The method does not need to add new entitative device in mobile IP network, and will not increase additional cost of building network for multiple versions in protocol.
Description
Technical field
The present invention relates to network communications technology field, relate in particular to the method for equipment room realization protocol edition compatible in a kind of mobile IP network.
Background technology
Mobile IPv 4 is a kind ofly to provide mobile support function communication protocol at the last layer Network Based of Internet (internet), it makes mobile node between heterogeneous networks in the moving process, needn't change IP addresses of nodes, still can keep with other mobile nodes or do not have the continuity of the inter-node communication of mobile IP function.
Can in roam procedure, freely realize the problem of network insertion because the mobile IPv 4 technology has solved the user, so stipulate clearly among the 3G standard IMT2000 that 3-G (Generation Three mobile communication system) must be supported mobile IP Packet Service.
Along with the continuous evolution of IETF (Internet engineering duty group) to the standardization effort of mobile IP, IETF has released two cover mobile IP protocol standards: RFC 2002 and RFC 3344, wherein, RFC3344 is a latest edition, is used for substituting original RFC 2002.With respect to RFC2002, RFC3344 has clarified the part of bluring in the original version, and the support of mobile network's application scenarios is provided, and has revised the identifying algorithm of original version agreement.
Yet, because mobile IP protocol lacks the consideration of edition compatibility in the design of redaction, and do not provide cell that the protocol version that message sender adopts is described in the protocol message body again, therefore message receiver can not be resolved the message that receives according to the protocol version of message sender, can cause the problem that the equipment room realized according to different editions can't interoperability.
Identifying algorithm when registering on home agent with mobile node below illustrates the problem that protocol version may be drawn under can't compatible context.
When mobile node roamed on the field network, the access address (being Care-of Address) that mobile node need be new with it was registered to home agent (HA, Home Agent).For solving potential safety problem in the login mechanism, mobile IP protocol has been introduced authentication mechanism, promptly in registration message (register requirement and registration reply message), increase authentication extension (Authentication Extension), the legitimacy that message receiver comes the authentication message transmit leg according to authentication extension, authentication extension is filled in by transmit leg.
The form of described authentication extension is generally form as shown in Figure 1, specifically comprises field:
Type (type) field: the type field is an eight bit byte, is used for the type of distinguishing authentication expansion;
Length (length) field: length field is occupied a byte, and expression comprises the length of SPI (Security Parameter Index) and Authenticator (authentication value);
The SPI field: this field has been selected algorithm, the pattern of authentication and has been used for the key that the authenticator calculates, and is used to calculate authentication value and recipient's verification authentication value;
The Authenticator field: the algorithm, pattern and the key that adopt the SPI appointment are to protected message field result calculated.
In RFC2002, the protection registration message of the Authenticator field carrying that authentication extension comprises specifically comprises following field:
1, UDP (User Datagram Protoco (UDP)) load, i.e. register requirement or registration reply data;
2, all expansions before this authentication extension;
3, the type of this authentication extension, length.
In RFC 3344, the computational methods of the Authenticator field of described authentication extension are then different with RFC 2002, specifically are that in the information that comprises of the Authenticator field with RFC 2002 regulation the 3rd expands to and comprise: the type of this authentication extension, length and SPI.
This shows that if mobile node is followed different RFC standards with home agent, home agent can't successfully authenticate the authentication extension that mobile node is sent.
Because historical reasons, the formulation of WCDMA (Wideband Code Division Multiple Access (WCDMA)) standard 3GPP and CDMA2000 standard 3GPP2 is early than RFC 3344 standard issuing time, so mobile IP standard is only supported RFC 2002, and the formulation of follow-up 3G standard is not included RFC 3344 in consideration yet.Cause the incompatible problem of protocol version in the 3G moving communicating field, to come out day by day significantly.
In the application scenarios of 3G wireless network, the 3GPP2 P.S0001B agreement that 3GPP TS23.060 agreement that the WCDMA network is followed and CDMA2000 network are followed is regulation HA (home agent clearly, Home Agent) and FA (Foreign Agent, Foreign Agent) follows the RFC2002 standard, home agent and Foreign Agent can be simultaneously for mobile phone and fixed terminal (as notebook, PC) provide service, and terminal nodes such as mobile phone or fixed terminal are often supported RFC 3344 agreements upgraded.
Because mobile node is not known the mobile IP protocol version that home agent or Foreign Agent are followed, and there is not the field mobile IP protocol version of identification message sender employing clearly in the registration message yet, therefore, lack effective mechanism and determine the authentication value account form.At this moment, home agent can only carry out the calculating of authentication value according to the agreement that oneself realizes, this will inevitably refuse the register requirement of the inconsistent mobile node of part agreement because of authentification failure, the mobile node that causes following a certain RFC standard can't obtain mobile IP service, although the agreement of mobile node own realizes not problem.
Therefore, because in the existence of a plurality of standards of mobile IP, and mobile IP design do not consider compatibling problem between version, makes that the equipment between the distinct device merchant is difficult to guarantee interoperability.And then make the modification of the authentication calculations method of 3344 pairs of registration messages of RFC, cause in wireless network mobile node can't normally obtain mobile IP service probably because of the difference of protocol version.
Certainly, provide support if Virtual network operator, also can increase a plurality of entity devices in order to solve equipment room edition compatibility problem, but will increase the network construction cost of Virtual network operator greatly like this mobile IP protocol different editions.
Summary of the invention
In view of above-mentioned existing in prior technology problem, the purpose of this invention is to provide equipment room in a kind of mobile IP network and realize the method for protocol edition compatible, make that need not to increase in mobile IP network new equipment just can realize compatibility between mobile IP different editions.
The objective of the invention is to be achieved through the following technical solutions:
The invention provides the method for equipment room realization protocol edition compatible in a kind of mobile IP network, comprising:
In mobile IP network, the protocol version information-bearing that mobile IP control messages transmit leg equipment is used local terminal equipment sends to opposite equip. in described mobile IP control messages;
Opposite equip. obtains described protocol version information after receiving described mobile IP control messages, and handles according to the mobile IP control messages that described protocol version information butt joint is received.
The present invention also provides the method for equipment room realization protocol edition compatible in a kind of mobile IP network, comprising:
Mobile node sends login request message to network equipment in A, the mobile IP network, is carrying the protocol version information that mobile node is used in the described login request message;
After B, network equipment are received described login request message, login request message is handled according to the protocol version information of carrying in the described message.
Equipment room realizes that the method for protocol edition compatible also comprises in the mobile IP network of the present invention:
C, network equipment return registration reply message to mobile node, are carrying the protocol version information that mobile node is used in the message;
After D, mobile node are received described registration reply message, this message is handled according to the protocol version information of wherein carrying.
Among the present invention, when described network equipment was Foreign Agent equipment, described step B also comprised:
Foreign Agent equipment is carrying the protocol version information that mobile node is used to the login request message of the home agent equipment transmission mobile node of mobile node in the message;
After home agent equipment is received described login request message, described message is handled according to the protocol version information of carrying in the message.
The protocol version extended field of described protocol version information-bearing in login request message and registration reply message.
But described protocol version extended field is arranged at the first place of the fixed length part expansion afterwards in login request message and the registration reply message.
Described protocol version extended field comprises:
Expansion type field: the type that is used to represent this expansion;
Length field: be used to represent extension length;
Version number field: the protocol version information that is used to carry application.
Described protocol version information is:
The protocol version corresponding codes information that equipment in the mobile IP network is used.
The form that described protocol version extended field specifically can adopt comprises:
The short extended format of RFC 3344 definition, the privately owned extended format of common vendor/organisation that defines among the type lengths values form of RFC 2002 definition or the RFC3115.
Protocol version information of the present invention can be arranged in the reservation position of attribute field of login request message.
Equipment room realizes that the method for protocol edition compatible also comprises in the described mobile IP network:
The protocol version assembling registration reply message that home agent is determined according to the protocol version information of attribute field carrying, and send to mobile node;
Mobile node receives described registration reply message, and handles.
Equipment room realizes that the method for protocol edition compatible also comprises in the described mobile IP network:
Foreign Agent receives the login request message that mobile node is sent, and preserves flag bit described in the message;
After the registration reply message that Foreign Agent reception home agent returns, determine the corresponding protocol version according to the flag bit of preserving, and handle response message according to described protocol version.
As seen from the above technical solution provided by the invention, the present invention has realized the compatibility between different mobile IP protocol versions, thereby can guarantee that mobile node can obtain mobile IP service reliably, and can guarantee the interoperability of the equipment between the distinct device merchant.And realization of the present invention need not in mobile IP network to increase new entity device, guarantees that fully Virtual network operator need not to realizing that the new battle array between the multi-protocols version increases the cost of networking.
Description of drawings
Fig. 1 is the schematic diagram of authentication extension form in the prior art;
Fig. 2 is the flow chart of method of the present invention.
Fig. 3 is the form schematic diagram 1 of the protocol version extended field described in the present invention;
Fig. 4 is the form schematic diagram 2 of the protocol version extended field described in the present invention;
Fig. 5 is the form schematic diagram 3 of the protocol version extended field described in the present invention;
Fig. 6 is the form schematic diagram 4 of the protocol version extended field described in the present invention.
Embodiment
Core concept of the present invention is a bearing protocol version number information in the mobile IP control messages of the transmission in mobile IP network, so that the recipient of mobile IP control messages can handle the mobile IP control messages of receiving accordingly according to protocol version information wherein, to realize the control corresponding process.
Increase the protocol version expansion in login request message that specifically can be in mobile IP network among the present invention and the registration reply message, compatibling problem with the equipment room of the mobile IP protocol that solve to adopt different editions guarantees that mobile IP network can provide more reliable mobile IP service.
The present invention is by increasing protocol version expansion (VersionExtension) field in the registration message message of mobile IP, the protocol version that makes message sender it can be adopted is notified to message receiver, thereby message sink can be determined the corresponding protocol processing mode according to version number, has guaranteed the compatibility according to the equipment room of mobile IP protocol new and old edition realization.
Because RFC 3344 is different with the authentication value information of the regulation of RFC 2002, think that equipment that assurance realizes based on the different editions agreement can finish the access authentication of the mobile node of realizing based on the different editions agreement, increase the protocol version extended field in login request message that the present invention just sends and the registration reply message in mobile IP network.
That is to say, among the present invention, when mobile node when the home agent router sends login request message, need to carry the protocol version information that mobile node is used in the message, equally, when the local agent router when mobile node returns registration reply message, also need to carry described protocol version information.
Specific implementation of the present invention mainly comprises following process as shown in Figure 2:
Step 21: the network equipment (as home agent router) of mobile node in mobile IP network sends and carries protocol version information login request message;
Described protocol version information is specially to be carried on to be increased in the protocol version extended field that is provided with in the login request message;
Step 22: after network equipment is received described login request message, obtain the described protocol version information of carrying in the message;
Step 23: the access to mobile node authenticates based on described protocol version information, is specially to utilize described protocol version information corresponding protocols processing section that the authentication extension information of carrying in the login request message is carried out authentication processing;
Step 24: network equipment sends to mobile node with authentication result by registration reply message, carrying the protocol version information that mobile node is used in the described registration reply message equally, described protocol version information is carried in the protocol version extended field that increases equipment in registration reply message equally;
That is to say, can correctly handle registration reply message in order to guarantee mobile node, home agent must copy protocol version extended field loaded information in the login request message that mobile node sends in registration reply message, according to the assembling of the protocol version information in protocol version extended field registration reply message;
Step 25: after mobile node is received described registration reply message, obtain the described protocol version information of carrying in the message;
Step 26: described registration reply message is handled based on described protocol version information.
Protocol version information in login request message or the registration reply protocol of messages version number extended field is determined by the equipment of initial this message of transmission, does not allow to revise before arriving final treatment facility.
When mobile node sends login request message, fill in the protocol version expansion according to the protocol type that adopts, promptly described protocol version information is determined by mobile node; Forwarding unit was not revised in the middle of described login request message did not allow before arriving home agent;
Equally, the protocol version information in the described registration reply message is to be determined by home agent, and does not also allow to be revised by middle forwarding unit before arriving mobile node;
Described intermediate equipment may be a Foreign Agent, also may be other network equipments.
If login request message is transmitted to home agent through Foreign Agent, Foreign Agent needs protocol version extended field loaded information is copied in the login request message that sends to home agent, so that after home agent receives described message, can authenticate location registration process to login request message by the protocol version information in the protocol version extended field.
As can be seen, the core in above-mentioned processing procedure is to have increased the protocol version extended field in login request message and registration reply message.For this reason, where described protocol version extended field is carried on respectively in the message, and adopts which type of form, and being equally needs a technical problem underlying solving among the present invention, will do detailed explanation to this below.
For effectively utilizing the limited expansion type resource of mobile IP, the form of described protocol version extended field can adopt the short extended format (Short Extension Format) of RFC3344 definition, the space has been reserved in the definition that short extended format is new expansion type, and the expansion of short extended format for crossing, if promptly equipment can't be discerned this expansion, then can directly ignore this expansion, and can not abandon this message, simultaneously, short extended format and expansion type standard are easy to be adopted use by each equipment vendors.
Among the present invention, the protocol version extended field that adopts described short extended format specifically comprises following field as shown in Figure 3:
The type of Type (type) field: Type definition expansion, greater than 127, less than 256, occurrence should be distributed by IANA (interconnected network No. distributor gear); This value has guaranteed can ignore this expansion when equipment can't be discerned this expansion, and needn't abandon the registration message that carries this expansion greater than 127.
Length (length) field: take a byte, the extended field length of expression except that the type field and Length field.
Sub-Type (subtype) field: equal 1, be first subtype of this expansion.
Version (version number) field: version number is specifically as follows: 0 corresponding to RFC 2002,1 corresponding to RFC 3344, this value can also be adjusted or increases progressively according to the issue of mobile IP new standard.
Because the protocol version extended field all works to mobile node, Foreign Agent and home agent, so the protocol version extended field preferably is positioned in login request message and registration reply message after the fixed length part, and before all the other extended fields, promptly be arranged at the first place of all expansions of mobile IP control messages, for example, must expand at MN-FA.Enable before authentication extension (authorization-enablingextension) (as the MN-HA authentication extension), the HA-FA expansion.
Among the present invention, the form of described protocol version expansion also can adopt Type-length-Value (type lengths values) extended format of definition among the RFC 2002, and at this moment, described protocol version extended field specifically comprises following field as shown in Figure 4:
The type of Type (type) field: Type definition expansion is greater than 127, less than 256, occurrence should be distributed by IANA, this value can guarantee that the equipment that can't discern this expansion can ignore this expansion, and needn't abandon the registration message that carries this expansion greater than 127.
Length (length) field: take a byte, the length of expression Version field.
Version (version number) field: version number is specifically as follows: 0 corresponding to RFC 2002,1 corresponding to RFC 3344, this value can also be adjusted or increases progressively according to the issue of mobile IP new standard.
Among the present invention, the form of described protocol version expansion can also adopt Normal Vendor (common the manufacturer)/Organization Specific Extensions (the privately owned expansion of tissue) of definition among the RFC 3115, it is the NVSE form, the form of described protocol version expansion this moment specifically comprises following field as shown in Figure 5:
Type (type) field: be 134, because the Type of NVSE expansion is 134, greater than 127, message receiver can be ignored this expansion as discerning this expansion, continues the remainder of processing messages.
Length (length) field: take a byte, this expansion does not comprise the byte number of other fields of Type and Length.
Reserved (reservation) field: reserve.
Vendor/Org-ID (vendor/organisation ID) field: the identification number of manufacturer or tissue.
Vendor-NVSE-Type (NVSE of manufacturer type) field: be 1, define the expansion type of this protocol version expansion.
Version (version number) field: version number is specifically as follows: 0 corresponding to RFC 2002,1 corresponding to RFC 3344, this value can be adjusted or increases progressively according to the issue of mobile IP new standard.
The present invention is except that increasing the protocol version extended field bearing protocol version number information as previously described in login request message and registration reply message, can also adopt the 1st bit in login request message fixed length part Flags (sign) field as described protocol version extended field bearing protocol version number information, promptly utilize this bit for keeping the characteristics of position, with this bit as version number's flag bit.When adopting flag bit bearing protocol version number information, it is different that process is described in the processing procedure of corresponding home agent and Foreign Agent and front, and the back will be described in detail.
Preceding four byte formats of described message specifically comprise following field as shown in Figure 6 behind the increase protocol version flag bit:
Type (type) field: 1, represent that this message is login request message, original field.
| S|B|D|M|G|r|T|E|: being the flag bit of login request message, is an octet.Wherein S, B, D, M, G definition can be with reference to RFC 2002 or RFC 3344, but all kept the 1st bit, i.e. E bit shown in the figure.
Wherein the E bit is version number's flag bit that the present invention increases newly, can work as " E " set, represents this message support RFC 3344, when " E " not set, represents this login request message support RFC2002, and vice versa.
The same as described previously, when mobile node sends login request message, whether determine to the set of " E " bit according to the protocol type that adopts.
Describe with the front and different to be, if login request message is transmitted to home agent through Foreign Agent, Foreign Agent needs Flag flag bit (comprising flag bit " E ") is saved in the user visiting tabulation, copy all flag bits simultaneously in the login request message that sends to home agent, so that home agent is handled registration message according to the protocol version of " E " flag bit appointment.
Another point and front are described and different are, when Foreign Agent is received the registration reply message of home agent response, need visit " E " flag bit of preserving in the tabulation according to the local user and determine to handle this registration reply protocol of messages version, and handle accordingly.
Can correctly handle registration reply for guaranteeing mobile node, home agent also must handle and assemble registration reply message according to the protocol version of " E " flag bit appointment to login request message, like this, mobile node just can correctly have been handled after receiving corresponding registration reply message.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (12)
1, the method for equipment room realization protocol edition compatible in a kind of mobile IP network is characterized in that, comprising:
In mobile IP network, the protocol version information-bearing that mobile IP control messages transmit leg equipment is used local terminal equipment sends to opposite equip. in described mobile IP control messages;
Opposite equip. obtains described protocol version information after receiving described mobile IP control messages, and handles according to the mobile IP control messages that described protocol version information butt joint is received.
2, the method for equipment room realization protocol edition compatible in a kind of mobile IP network is characterized in that, comprising:
Mobile node sends login request message to network equipment in A, the mobile IP network, is carrying the protocol version information that mobile node is used in the described login request message;
After B, network equipment are received described login request message, login request message is handled according to the protocol version information of carrying in the described message.
3, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 2 is characterized in that this method also comprises:
C, network equipment return registration reply message to mobile node, are carrying the protocol version information that mobile node is used in the message;
After D, mobile node are received described registration reply message, this message is handled according to the protocol version information of wherein carrying.
4, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 2 is characterized in that when described network equipment was Foreign Agent equipment, described step B also comprised:
Foreign Agent equipment is carrying the protocol version information that mobile node is used to the login request message of the home agent equipment transmission mobile node of mobile node in the message;
After home agent equipment is received described login request message, described message is handled according to the protocol version information of carrying in the message.
5, realize the method for protocol edition compatible according to equipment room in claim 2, the 3 or 4 described mobile IP networks, it is characterized in that the protocol version extended field of described protocol version information-bearing in login request message and registration reply message.
6, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 5, it is characterized in that, but described protocol version extended field is arranged at the first place of the fixed length part expansion afterwards in login request message and the registration reply message.
7, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 5 is characterized in that described protocol version extended field comprises:
Expansion type field: the type that is used to represent this expansion;
Length field: be used to represent extension length;
Version number field: the protocol version information that is used to carry application.
8, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 7 is characterized in that described protocol version information is:
The protocol version corresponding codes information that equipment in the mobile IP network is used.
9, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 7 is characterized in that the form that described protocol version extended field specifically can adopt comprises:
The short extended format of RFC 3344 definition, the privately owned extended format of common vendor/organisation that defines among the type lengths values form of RFC 2002 definition or the RFC3115.
10, realize the method for protocol edition compatible according to equipment room in claim 2, the 3 or 4 described mobile IP networks, it is characterized in that described protocol version information can be arranged in the reservation position of attribute field of login request message.
11, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 10 is characterized in that this method also comprises:
The protocol version assembling registration reply message that home agent is determined according to the protocol version information of attribute field carrying, and send to mobile node;
Mobile node receives described registration reply message, and handles.
12, the method for equipment room realization protocol edition compatible in the mobile IP network according to claim 10 is characterized in that this method also comprises:
Foreign Agent receives the login request message that mobile node is sent, and preserves flag bit described in the message;
After the registration reply message that Foreign Agent reception home agent returns, determine the corresponding protocol version according to the flag bit of preserving, and handle response message according to described protocol version.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510004834 CN1816036A (en) | 2005-02-02 | 2005-02-02 | Method for realizing protocol edition compatible between apparatuses in mobile IP network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510004834 CN1816036A (en) | 2005-02-02 | 2005-02-02 | Method for realizing protocol edition compatible between apparatuses in mobile IP network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1816036A true CN1816036A (en) | 2006-08-09 |
Family
ID=36907992
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200510004834 Pending CN1816036A (en) | 2005-02-02 | 2005-02-02 | Method for realizing protocol edition compatible between apparatuses in mobile IP network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1816036A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007101405A1 (en) * | 2006-03-07 | 2007-09-13 | Huawei Technologies Co., Ltd. | A transmission method, a reception method and device, and a user equipment for high speed downlinkpacket access data |
| WO2009097730A1 (en) * | 2008-02-04 | 2009-08-13 | Huawei Technologies Co., Ltd. | A method for deleting mobility management entity's information and device thereof |
| CN101834746A (en) * | 2010-05-24 | 2010-09-15 | 中兴通讯股份有限公司 | Method, device and system for implementing compatibility of network management device and equipment veneer |
| CN101483855B (en) * | 2008-01-09 | 2011-04-13 | 华为技术有限公司 | Network switching method, mobile network system and mobility management equipment |
| CN101141783B (en) * | 2006-09-06 | 2012-07-04 | 华为技术有限公司 | Method of negotiating mobile IP characteristics |
| CN104899017A (en) * | 2014-03-07 | 2015-09-09 | 施耐德电器工业公司 | Electronic system, circuit breaker and method for generating a deviation indicator |
| CN109327428A (en) * | 2018-06-05 | 2019-02-12 | 中国移动通信有限公司研究院 | A kind of message transmitting method, device, network side equipment and storage medium |
| WO2020093377A1 (en) * | 2018-11-09 | 2020-05-14 | 华为技术有限公司 | Method and device for determining internet protocol version |
| CN113364683A (en) * | 2020-03-05 | 2021-09-07 | 华为技术有限公司 | Route sending method and equipment |
-
2005
- 2005-02-02 CN CN 200510004834 patent/CN1816036A/en active Pending
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007101405A1 (en) * | 2006-03-07 | 2007-09-13 | Huawei Technologies Co., Ltd. | A transmission method, a reception method and device, and a user equipment for high speed downlinkpacket access data |
| CN101141783B (en) * | 2006-09-06 | 2012-07-04 | 华为技术有限公司 | Method of negotiating mobile IP characteristics |
| CN101483855B (en) * | 2008-01-09 | 2011-04-13 | 华为技术有限公司 | Network switching method, mobile network system and mobility management equipment |
| US8369851B2 (en) | 2008-02-04 | 2013-02-05 | Huawei Technologies Co., Ltd. | Mobility management entity information deleting method and device |
| US8359027B2 (en) | 2008-02-04 | 2013-01-22 | Huawei Technologies Co., Ltd. | Mobility management entity information deleting method and device |
| WO2009097730A1 (en) * | 2008-02-04 | 2009-08-13 | Huawei Technologies Co., Ltd. | A method for deleting mobility management entity's information and device thereof |
| CN101834746A (en) * | 2010-05-24 | 2010-09-15 | 中兴通讯股份有限公司 | Method, device and system for implementing compatibility of network management device and equipment veneer |
| CN101834746B (en) * | 2010-05-24 | 2014-09-10 | 中兴通讯股份有限公司 | Method, device and system for implementing compatibility of network management device and equipment veneer |
| CN104899017A (en) * | 2014-03-07 | 2015-09-09 | 施耐德电器工业公司 | Electronic system, circuit breaker and method for generating a deviation indicator |
| CN109327428A (en) * | 2018-06-05 | 2019-02-12 | 中国移动通信有限公司研究院 | A kind of message transmitting method, device, network side equipment and storage medium |
| US11924314B2 (en) | 2018-06-05 | 2024-03-05 | China Mobile Communication Co., Ltd Research Institute | Message transmission method, message transmission device, network side device and storage medium |
| WO2020093377A1 (en) * | 2018-11-09 | 2020-05-14 | 华为技术有限公司 | Method and device for determining internet protocol version |
| CN112534866A (en) * | 2018-11-09 | 2021-03-19 | 华为技术有限公司 | Method and device for determining Internet protocol version |
| CN113364683A (en) * | 2020-03-05 | 2021-09-07 | 华为技术有限公司 | Route sending method and equipment |
| WO2021175309A1 (en) * | 2020-03-05 | 2021-09-10 | 华为技术有限公司 | Method and device for routing transmission |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1816036A (en) | Method for realizing protocol edition compatible between apparatuses in mobile IP network | |
| EP2263396B1 (en) | Access through non-3gpp access networks | |
| JP5559182B2 (en) | System and method for dynamic creation and release of proxy mobile IP connections | |
| CN1643947A (en) | Method to provide dynamic internet protocol security policy service | |
| CN1961538A (en) | Dynamic network management apparatus and dynamic network management method | |
| CN1716879A (en) | The method and apparatus that is used for waking remote terminal | |
| CN1677976A (en) | Viirtual private network structure reuse for mobile computing devices | |
| CN101036174A (en) | Enhanced techniques for using core based nodes for state transfer | |
| CN1969568A (en) | Mobility architecture using pre-authentication, pre-configuration and/or virtual soft-handoff | |
| CN1623309A (en) | Method and system for connecting mobile client devices to the internet | |
| CN1636378A (en) | Addressing mechanisms in mobile ip | |
| US20080080427A1 (en) | Method and system for handoff of mobile node in mobile communication system supporting proxy mobile internet protocol | |
| KR20060117798A (en) | Method for preventting replay attack in mobile ipv6 | |
| CN1736081A (en) | Early determination of network support for mobile IP | |
| WO2008091906A3 (en) | Message ordering for network based mobility management systems | |
| CN101079704A (en) | System and method for implementing mobile IP access | |
| CN1838632A (en) | Method for realizing mobile IPv6 message crossing firewall | |
| CN1653775A (en) | Method and apparatus for providing compatibility between elements of a wireless communication system | |
| CN101075964A (en) | Method and system for realizing port re-direction by router interface address | |
| CN100352211C (en) | Policy information renewing method and system in WLAN | |
| CN1794678A (en) | Register/deregister method of mobile inter net protocol | |
| JP2009517986A (en) | Method, system and apparatus for forming a reverse tunnel | |
| CN101030936A (en) | Telecommunication for switching node from IPv4 network to IPv6 network | |
| CN1691668A (en) | A system and method for providing IPv6 service | |
| CN101052034A (en) | Method and system for transmitting network event journal protocol message |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20060809 |