CN102170389B - data message transmission method and access device - Google Patents
data message transmission method and access device Download PDFInfo
- Publication number
- CN102170389B CN102170389B CN201010122079.7A CN201010122079A CN102170389B CN 102170389 B CN102170389 B CN 102170389B CN 201010122079 A CN201010122079 A CN 201010122079A CN 102170389 B CN102170389 B CN 102170389B
- Authority
- CN
- China
- Prior art keywords
- data message
- message
- destination
- rid
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/106—Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
Abstract
The present invention relates to a kind of data message transmission method and access device, the method comprises: source access device (ASN) receives AID data message, and the source wherein in heading, destination address are source, destination access mark (AID); Source ASN is converted to RID data message by needing the AID data message being sent to terminal, comprise replacement source, object access mark (AID) be source, object (RID) increase message extension header, wherein, message extension header comprises described source, destination AID; Destination ASN receives RID data message, forwarding, directly processing not carrying the prolate-headed RID data message of message carrying the prolate-headed RID data message of message.Data message transmission method of the present invention and access device, can to realize in identify label and locator separation network access device to the correct process of data message.
Description
Technical field
The present invention relates to field of mobile communication, particularly relate to a kind of data message transmission method and access device.
Background technology
Existing internet widely used transmission control protocol/Internet Protocol (TransmissionControlProtocol/InternetProtocol, TCP/IP) in, IP address has dual-use function, both as the station location marker of network interface in network topology of network layer host, again as the identify label of the host network interface of transport layer.The situation of host mobility is not considered at the beginning of ICP/IP protocol design.But when host mobility is more and more general, the semanteme overload defect of this IP address is day by day obvious.As: when the IP address of main frame changes, not only route will change, and the identify label of communication terminal main frame also changes, and routing overhead can be caused so more and more heavier, and the change of host identification can cause application and the interruption be connected.
The object that identify label and position separation problem propose is that the semanteme in order to solve IP address transships and routing overhead is serious and security problems, the dual-use function of IP address is separated, realizes mobility, many locals property, the dynamic code reassignment in IP address, alleviate the support of the problems such as exchanging visit in routing overhead and Next Generation Internet between heterogeneous networks region.
In order to solve the problem, propose the framework of the network that multiple identify label is separated with position at present.
Wherein, a kind of identify label and locator separation network framework are as shown in Figure 1, this identify label and locator separation network framework comprise access service node (AccessServiceNode, ASN), user terminal (UserEquipment, UE), identity position register (Identification & LocationRegister, ILR) etc.Wherein, access service node is responsible for the access realizing user terminal, and bears the function such as charging and switching; ILR bears the position registration of user and the function of identification, and the identification identifier of each user terminal existence anduniquess, namely accesses mark (AccessIdentification, AID).
In Fig. 1, access service node ASN1 and ASN2 is used for access user terminal UE1 and UE2, ASN1 and ASN2 respectively and has Route Distinguisher RID1 and RID2 respectively, access mark AID1 and AID2 of UE1 and UE2 existence anduniquess respectively.
For convenience of description, hereafter by this identify label and locator separation network referred to as SILSN (SubscriberIdentifier & LocatorSeparationNetwork).
In SILSN network, during with existing network mixed networking, ASN also bears common ISILSN network node functions, needs to process some traditional IP messages simultaneously; When ASN process Traditional IP message (as shown in table 1 below), do not have distinctive mark to distinguish which message by ASN and issue the node of ASN own, which message is the mobile subscriber's issued under ASN, causes ASN confusion reigned (message format that terminal, user receive also is the form in table 4) when deal with data message.
Table 1 is sent to the message content of ASN self process
Most typical example is: when network manager needs to manage the core net node such as ASN, router, sending destination is the Traditional IP data message of ASN by keeper, that is, ASN will receive two kinds of messages: one will be transmitted to terminal use, a kind of wanting processes oneself, and these two kinds of messages all cannot clearly be distinguished and process to existing processing mode, to the message processing method made new advances, the message of ASN energy differentiating and processing two type must be made for this reason.
Summary of the invention
The technical problem to be solved in the present invention is to provide a kind of data message transmission method and access device, to realize in identify label and locator separation network access device to the correct process of data message.
For solving above technical problem, the invention provides a kind of data message transmission method, the method identity-based mark and locator separation network realize, and comprising:
A, the first access device receive and resolve the first data message, and the source wherein in heading, destination address are source, destination access mark (AID);
Source in heading, destination address are replaced with source, destination Route Distinguisher (RID) by B, described first access device, and increase message extension header and generate the second data message, wherein message extension header comprises described source, destination AID, and the second access device pointed to destination RID forwards described second data message;
C, described second access device receive described second data message, judge whether described second data message carries message extension header, if carry, perform step D, otherwise perform step e;
Source in the heading of described second data message, destination address are replaced with source in message extension header, destination AID by D, described second access device, and delete message extension header and be reduced to the first data message, the terminal that this first data message points to destination AID is forwarded;
E, described second access device process this second data message.
Further, in step C, after described second access device receives described second data message, before judging whether to carry message extension header, judge that destination RID points to described second access device.
Further, in step C, after described second access device receives described second data message, first judge whether destination RID points to described second access device; If judge, destination RID points to described second access device, then judges whether to carry message extension header, otherwise directly forwards described second data message to the access device that destination RID points to.
Further, described message extension header is IPV6 message extension header.
Further, ground option head for the purpose of described message extension header, the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
For solving above technical problem, present invention also offers a kind of access device, described access device is positioned at identify label and locator separation network, comprising:
Data message receiver module, for receiving AID data message and RID data message, source in the heading of wherein AID data message, destination address are source, destination access mark (AID), and the source in the heading of RID data message, destination address are source, destination RID;
Data message parsing module, for the data message that resolution data message receiver module receives, if data message is AID data message, then notification data message modular converter is changed; If data message is RID data message, and destination RID points to current access device, and this data message does not carry message extension header, then notification data message processing module (MPM) processes;
Data message modular converter, for the source in heading, destination address are replaced with source, destination Route Distinguisher (RID), and increase message extension header generation RID data message, wherein message extension header comprises described source, destination AID, also for notifying that described data message sending module forwards described RID data message to the access device that destination RID points to;
Data message recovers module, for the source in heading, destination address being replaced with source in message extension header, destination AID, and delete message extension header and be reduced to AID data message, also for notifying the terminal forwarding that the AID data message after reduction points to destination AID by described data message sending module;
Data message processing module, for pointing to current access device to destination RID, and does not carry the prolate-headed RID data message of message and processes.
Data message sending module, for routing forwarding AID data message and RID data message.
Further, if hold RID to point to the RID data message of other access devices for the purpose of the data message that resolution data message receiver module receives, described data message parsing module also forwards described RID data message for notification data message sending module to other access devices that destination RID points to.
Further, described message extension header is IPV6 message extension header.
Further, ground option head for the purpose of described message extension header, the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
For solving above technical problem, present invention also offers another kind of data message transmission method, the method identity-based mark and locator separation network realize, and comprising:
Source access device (ASN) receives AID data message, and the source wherein in heading, destination address are source, destination access mark (AID);
Source ASN is converted to RID data message by needing the AID data message being sent to terminal, comprise replacement source, object access mark (AID) be source, object (RID) increase message extension header, wherein, message extension header comprises described source, destination AID;
Destination ASN receives RID data message, forwarding, directly processing not carrying the prolate-headed RID data message of message carrying the prolate-headed RID data message of message.
Further, RID data message is first converted to AID data message before forwarding RID data message by described destination ASN, comprises and source, object RID are replaced with source, object AID, delete message extension header, then forward described AID data message to object AID sensing terminal.
Further, described message extension header is IPV6 message extension header.
Further, ground option head for the purpose of described message extension header, the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
For solving above technical problem, present invention also offers another kind of access device, described access device (ASN) is positioned at identify label and locator separation network, comprising:
Data message receiver module, during as source ASN, for receiving AID data message; During as destination ASN, for receiving RID data message, source in the heading of wherein AID data message, destination address are source, destination access mark (AID), and the source in the heading of RID data message, destination address are source, destination RID;
Data message parsing module, for resolution data message receiver module receive data message, if data message is AID data message, or data message is RID data message, and carry message extension header then notification data packet forwarding module forward; If data message is RID data message, and Wen Wei carries message extension header, then notification data message processing module (MPM) processes;
Data message forwarding module, during as source ASN, for the source in the heading of ADI data message, destination address are replaced with source, destination Route Distinguisher (RID), and increase message extension header generation RID data message, wherein, comprise source, object AID in described message extension header, the destination ASN also for pointing to destination RID forwards described RID data message; During as destination ASN, for RID data message is forwarded to its lower terminal;
Data message processing module, for pointing to current access device to destination RID, and does not carry the prolate-headed RID data message of message and processes.
Further, described data message forwarding module, before forwarding to its lower terminal, first RID data message is converted to AID data message, comprise and source, object RID are replaced with source, object AID, delete message extension header, then forward described AID data message to object AID sensing terminal.
Further, described message extension header is IPV6 message extension header.
Further, ground option head for the purpose of described message extension header, the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
In data message transmission method of the present invention and access device, changed needing the AID data message being sent to terminal by source access device (ASN), comprise replacement source, object access mark (AID) be source, object Route Distinguisher (RID) increase message extension header, destination ASN forwards or directly process according to whether comprising message extension header the data message received, to realize the correct process of ASN to data message.
Accompanying drawing explanation
Fig. 1 is the system architecture diagram of SILSN network;
Fig. 2 is the schematic diagram that SILSN network carries out data message process;
Fig. 3 is the schematic flow sheet of data message transmission method of the present invention;
Fig. 4 is the idiographic flow schematic diagram of data message transmission method of the present invention;
Fig. 5 is the modular structure schematic diagram of access device of the present invention;
Fig. 6 is another modular structure schematic diagram of access device of the present invention.
Embodiment
How data message transmits from source ASN to destination ASN, is the problem that the present invention mainly solves.The main thought of data message transmission method of the present invention and access device is, changed needing the AID data message being sent to terminal by source access device (ASN), comprise replacement source, object access mark (AID) be source, object Route Distinguisher (RID) increase message extension header, destination ASN forwards or directly process according to whether comprising message extension header the data message received, to realize the correct process of ASN to data message.As shown in Figure 3, data message transmission method of the present invention comprises the following steps:
Step 301: source access device (ASN) receives AID data message, the source wherein in heading, destination address are source, destination access mark (AID);
Step 302: source ASN is converted to RID data message by needing the AID data message being sent to terminal, comprise replacement source, object access mark (AID) be source, object RID) and increase message extension header;
Step 303: destination ASN receives RID data message, forwarding, directly processing not carrying the prolate-headed RID data message of message carrying the prolate-headed RID data message of message.
Destination ASN refers to the ASN that the destination RID of data message points to.Source, destination address are that the data message of AID is called AID data message or the first data message by the present invention, are that the data message of RID is called RID data message or the second data message by source, destination address.
Source, object terminal identification information is comprised in message extension header, preferably, for source, object AID, before described destination ASN forwards RID data message, first RID data message is converted to AID data message, comprise and source, object RID are replaced with source, object AID, delete message extension header, then forward described AID data message to object AID sensing terminal.
In the present invention, when the message of ASN1 to ASN2 adopts IPV6 to transmit time, for the packet mailing to terminal use, ASN1 does not adopt the method for an encapsulation IP head in addition, and by destination address and source address in IP head respectively by object AID and source AID, replace with object RID and source RID, then an extension header is increased to IP head, object AID and source AID is attached in the extension header of IPV6 message, as in destination-address scaling option, like this, the message of the terminal use under what ASN1 sent issue ASN2 carries amplifying message head, as shown in table 2 below:
Table 2 data transmission method schematic diagram of the present invention
And ASN1 sends, issue the message of ASN2 self, then can use conventional IPV6 message, namely do not carry amplifying message head.
After taking IPV6 extension header method, as long as destination ASN checks whether this packet has corresponding amplifying message head, if there is amplifying message head, issue its lower terminal, otherwise issue the core net nodes such as destination ASN, make core net node can correctly distinguish and process the message being sent to core net node self and the message being sent to terminal use.
Below the extension header of existing IPV6 data message is described:
The IPV6 heading shown in table 3 is defined, for carrying additional Internet information in IPV6 agreement (RFC2460):
Table 3
RFC2460 proposes to add IPV6 amplifying message head between the heading of IPV6 and upper-layer protocol head.6 kinds of amplifying message heads are defined in RFC2460, hop-by-hop options header (Hop-by-HopOptionsheader) respectively, route head (Routingheader), fragment header (Fragmentheader), authentication header (Authenticationheader), ESP encapsulation header (EncapsulatingSecurityPayloadheader), destination option head (DestinationOptionsheader).
RFC2460 defines protocol number to often kind of extension header, and if hop-by-hop options header is 0, destination option head is 60.When Internet application needs to use IPV6 message extension header to carry out transmission of information, only need the next heading (NextHeader) in table 5 to be set to corresponding protocol number.Such as, if when needing to adopt destination option head to transmit data in message, only need the next heading (NextHeader) in table 5 to be set to 60.
Various IPV6 extension header can in certain sequence and deposit, and as shown in table 4, being and then route head after IPV6 head, is subsequently destination option head, is finally TCP message head.
Table 4
| IPv6 head (IPv6 header) next heading (Next Header)=route (Routing) | Route head (Routing header) next heading (Next Header)=destination option (Destination Options) | Destination option head (Destination Options header) next heading (Next Header)=TCP | TCP message head (TCP header)+data (data) |
In 6 kinds of extension header of IPV6 definition, the information that destination option head checks for destination node for carrying those.The message format of destination option head is as shown in table 5 below:
Table 5
Wherein, NextHeader represents Next protocol header type, and HdrExtLen represents the length of this destination option extension head, in units of 8 bytes, does not comprise first character joint.
In RFC2460, option is made up of option type (OptionType), option (OptDataLen) and option data further.And first 3 of option type are all specified, wherein first, second defines the node of this IPV6 data message of process, the action taked when not being familiar with this this label:
00-skips this option and continues process heading
01-abandons this message.
10-abandons this message, sends ICMP
11-abandons this message, when not being multicast address, sends ICMP
In addition, RFC2460 has following regulation to the 3rd of option type (OptionType) the, if option data can affect route, is then set to 1, otherwise is set to 0.
For the OptionType of 8, except above front three, only have 5 optional, namely actual only have 32 numbering spaces, current RFC has defined a kind of destination option for mobile IP protocol, is called home address option (TheHomeAddressoption), its numerical value definition 0xC9, its low 5 is 00111, occupies sequence number 9.
Option is in units of byte, and describe the physical length of option data, the embodiment of described method is generally set to 12.
Due to the information that destination option head checks for destination node for carrying those, and the indication information in extension header involved in the present invention is only for destination ASN, therefore the present invention preferably adopts destination option head to expand.
Below the concrete grammar that the present invention utilizes the destination option head of IPV6 to carry user source address information is described, as shown in table 6:
Table 6
In table, the implication of next heading (NextHeader) and heading extension length (HdrExtLen) is same as above, is not repeating at this, and the destination extension header option increasing newly the present invention below or newly define is described:
1, option type (OptionType):
Option type OptionType in the option head of destination has 8:
For high 2, the present invention does not do particular provisions, according to circumstances can be arranged by node processing equipment, such as, when requiring higher occasion, as police network to safe class, this option can be set to 01, that is, if the node processing this data message is not familiar with this data format, by whole packet loss.For the node of general type, can 00 be set to, even if node is not familiar with this option like this, still can the whole data message of normal process, thus improve the compatibility of system, at utmost utilize existing equipment;
For the 3rd, because of in the present invention, intermediate node can process this option, and option data can affect route, is therefore set to 1;
For low 5, any one can choosing in other 31 sequence numbers except the sequence number 00111 of home address option is expanded, as low 5 are selected 11000 to expand.
The present invention 01111000, namely 0X98, represents when destination node is not familiar with this option, the still remainder of normal process data message.
2, source address mark
Source address mark herein refers to the source address mark of the terminal use sending this packet, also with regard to the user ID AID1 of UE1.When adopting IPV6 transmission, source address mark also adopts 128.
3, destination address mark
Destination address mark herein refers to the source address mark of the terminal use receiving this packet, the namely user ID AID2 of UE2.When adopting IPV6 transmission, destination address mark also adopts 128.
Be below the best implementation of data message transmission method of the present invention, wherein message extension header comprises the preferred forms of source, object AID, and the method comprises:
A, the first access device receive and resolve the first data message, and the source wherein in heading, destination address are source, destination access mark (AID);
Source in heading, destination address are replaced with source, destination Route Distinguisher (RID) by B, described first access device, and increase message extension header and generate the second data message, wherein message extension header comprises described source, destination AID, and the second access device pointed to destination RID forwards described second data message;
C, described second access device receive described second data message, judge whether described second data message carries message extension header, if carry, perform step D, otherwise perform step e;
In step C, after described second access device receives described second data message, before judging whether to carry message extension header, judge that destination RID points to described second access device.
In step C, after described second access device receives described second data message, first judge whether destination RID points to described second access device; If judge, destination RID points to described second access device, then judges whether to carry message extension header, otherwise directly forwards described second data message to the access device that destination RID points to.
Source in the heading of described second data message, destination address are replaced with source in message extension header, destination AID by D, described second access device, and delete message extension header and be reduced to the first data message, the terminal that this first data message points to destination AID is forwarded;
E, described second access device process this second data message.
Fig. 4 is the concrete schematic diagram adopting this method to carry out data transmission, and the data message that user sends, after ASN1 and ASN2 twice conversion, finally sends to UE2, and no matter where UE2 roams into, and data message correctly can both give UE2.As shown in Figure 3, comprise the following steps:
Step 401, user terminal UE1 sends to ASN1 the end-to-end data message that data format is IPV6, and its destination address is the user ID AID2 of UE2, and source address is the station address AID1 of UE1;
The example of the data message that table 7UE1 sends
In upper table, the data message that user UE1 sends is TCP message, and wherein source address is AID1, and destination address is AID2.
Step 402, whether ASN1 inquiry stores the position of AID2, if do not stored, then asks for the position of AID to ILR;
Step 403, ILR returns the positional information RID2 of the access server at the place of this user to ASN1;
Step 404, the source address in IPV6 data message and destination address AID1 and AID2 are replaced with RID1 and RID2 by ASN1 respectively, and increase destination scaling option corresponding to IPV6 extension header;
Step 405, the data message after conversion is sent to ASN2 by ASN1;
The example of the data message that table 8ASN1 sends
ASN1 is through inquiring about the position of AID2 to ILR, change destination address into RID2, source address changes RID1. into simultaneously, conveniently message is issued AID2 by ASN2, also source user mark and object user ID AID1 and AID2 are also placed in data message to carry, carrying mode is increase IPV6 message extension header option, ground option for the purpose of option type.AID1 and AID2 is carried in option.
Step 406, ASN2 judges that RID2 is sensing self and data message carries extension header, the source address in data message and destination address RID1 and RID2 is replaced with AID1 and AID2 respectively, and deletes destination scaling option corresponding to IPV6 extension header;
Step 407, the data message after conversion is sent to UE2 by ASN2.
The example of the data message that table 9ASN2 sends
When data message is sent to ASN2, ASN2 checks whether this data message carries corresponding destination option, if carried, then extract source address AID1 wherein and destination address AID2, then the source address RID1 of IPV6 message and destination address RID2 is changed respectively into address AID1 and AID2 of terminal, then delete the destination option that ASN1 increases, the data message through conversion is sent to UE2.
Adopt IPV6 message extension header to carry the method for source user mark and object mark, well distinguished the message being sent to terminal use and the message being sent to core net node, made SILSN network have practicality.
For realizing above method, the present invention also provides a kind of access device, and described access device is positioned at identify label and locator separation network, as shown in Figure 5, comprising:
Data message receiver module, for receiving AID data message and RID data message, source in the heading of wherein AID data message, destination address are source, destination access mark (AID), and the source in the heading of RID data message, destination address are source, destination RID;
Data message parsing module, for the data message that resolution data message receiver module receives, if data message is AID data message, then notification data message modular converter is changed; If data message is RID data message, and destination RID points to current access device, and this data message carries message extension header, then notification data message recovery module is recovered; If data message is RID data message, and destination RID points to current access device, and this data message does not carry message extension header, then notification data message processing module (MPM) processes;
Data message modular converter, for the source in heading, destination address are replaced with source, destination Route Distinguisher (RID), and increase message extension header generation RID data message, wherein message extension header comprises described source, destination AID, also for notifying that described data message sending module forwards described RID data message to the access device that destination RID points to;
Data message recovers module, for the source in heading, destination address being replaced with source in message extension header, destination AID, and delete message extension header and be reduced to AID data message, also for notifying the terminal forwarding that the AID data message after reduction points to destination AID by described data message sending module;
Data message processing module, for pointing to current access device to destination RID, and does not carry the prolate-headed RID data message of message and processes.
Data message sending module, for routing forwarding AID data message and RID data message.
Further, if hold RID to point to the RID data message of other access devices for the purpose of the data message that resolution data message receiver module receives, described data message parsing module also forwards described RID data message for notification data message sending module to other access devices that destination RID points to.
Further, described message extension header is IPV6 message extension header.
Ground option head for the purpose of described message extension header, the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
Present invention also offers another kind of access device, this access device (ASN) is positioned at identify label and locator separation network, and as shown in Figure 6, this access device comprises:
Data message receiver module, during as source ASN, for receiving AID data message; During as destination ASN, for receiving RID data message, source in the heading of wherein AID data message, destination address are source, destination access mark (AID), and the source in the heading of RID data message, destination address are source, destination RID;
Data message parsing module, for resolution data message receiver module receive data message, if data message is AID data message, or data message is RID data message, and carry message extension header then notification data packet forwarding module forward; If data message is RID data message, and Wen Wei carries message extension header, then notification data message processing module (MPM) processes;
Data message forwarding module, during as source ASN, for the source in the heading of ADI data message, destination address are replaced with source, destination Route Distinguisher (RID), and increase message extension header generation RID data message, wherein, comprise source, object AID in described message extension header, the destination ASN also for pointing to destination RID forwards described RID data message; During as destination ASN, for RID data message is forwarded to its lower terminal;
Data message processing module, for pointing to current access device to destination RID, and does not carry the prolate-headed RID data message of message and processes.
Further, described data message forwarding module, before forwarding to its lower terminal, first RID data message is converted to AID data message, comprise and source, object RID are replaced with source, object AID, delete message extension header, then forward described AID data message to object AID sensing terminal.
Further, described message extension header is IPV6 message extension header.
Further, ground option head for the purpose of described message extension header, the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
Claims (17)
1. a data message transmission method, is characterized in that, the method identity-based mark and locator separation network realize, and comprising:
A, the first access device receive and resolve the first data message, and the source wherein in heading, destination address are source, destination access mark (AID);
Source in heading, destination address are replaced with source, destination Route Distinguisher (RID) by B, described first access device, and increase message extension header and generate the second data message, wherein message extension header comprises described source, destination AID, and the second access device pointed to destination RID forwards described second data message;
C, described second access device receive described second data message, judge whether described second data message carries message extension header, if carry, perform step D, otherwise perform step e;
Source in the heading of described second data message, destination address are replaced with source in message extension header, destination AID by D, described second access device, and delete message extension header and be reduced to the first data message, the terminal that this first data message points to destination AID is forwarded;
E, described second access device process this second data message;
Wherein, ground option head for the purpose of described message extension header.
2. the method for claim 1, is characterized in that: in step C, after described second access device receives described second data message, before judging whether to carry message extension header, has judged that destination RID points to described second access device.
3. the method for claim 1, is characterized in that: in step C, after described second access device receives described second data message, first judges whether destination RID points to described second access device; If judge, destination RID points to described second access device, then judges whether to carry message extension header, otherwise directly forwards described second data message to the access device that destination RID points to.
4. the method for claim 1, is characterized in that: described message extension header is IPV6 message extension header.
5. the method for claim 1, it is characterized in that: the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
6. an access device, is characterized in that, described access device is positioned at identify label and locator separation network, comprising:
Data message receiver module, for receiving AID data message and RID data message, source in the heading of wherein AID data message, destination address are source, destination access mark (AID), and the source in the heading of RID data message, destination address are source, destination RID;
Data message parsing module, for the data message that resolution data message receiver module receives, if data message is AID data message, then notification data message modular converter is changed; If data message is RID data message, and destination RID points to current access device, and this data message does not carry message extension header, then notification data message processing module (MPM) processes;
Data message modular converter, for the source in heading, destination address are replaced with source, destination Route Distinguisher (RID), and increase message extension header generation RID data message, wherein message extension header comprises described source, destination AID, also for notifying that described data message sending module forwards described RID data message to the access device that destination RID points to;
Data message recovers module, for the source in heading, destination address being replaced with source in message extension header, destination AID, and delete message extension header and be reduced to AID data message, also for notifying the terminal forwarding that the AID data message after reduction points to destination AID by described data message sending module;
Data message processing module, for pointing to current access device to destination RID, and does not carry the prolate-headed RID data message of message and processes;
Data message sending module, for routing forwarding AID data message and RID data message;
Wherein, ground option head for the purpose of described message extension header.
7. access device as claimed in claim 6, it is characterized in that: if hold RID to point to the RID data message of other access devices for the purpose of the data message of resolution data message receiver module reception, described data message parsing module also forwards described RID data message for notification data message sending module to other access devices that destination RID points to.
8. access device as claimed in claim 6, is characterized in that: described message extension header is IPV6 message extension header.
9. access device as claimed in claim 6, it is characterized in that: the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
10. a data message transmission method, is characterized in that, the method identity-based mark and locator separation network realize, and comprising:
Source access device (ASN) receives AID data message, and the source wherein in heading, destination address are source, destination access mark (AID);
Source ASN is converted to RID data message by needing the AID data message being sent to terminal, comprise replacement source, object access mark (AID) be source, object (RID) increase message extension header, wherein, message extension header comprises described source, destination AID;
Destination ASN receives RID data message, forwarding, directly processing not carrying the prolate-headed RID data message of message carrying the prolate-headed RID data message of message;
Wherein, ground option head for the purpose of described message extension header.
11. methods as claimed in claim 10, it is characterized in that: before described destination ASN forwards RID data message, first RID data message is converted to AID data message, comprise and source, object RID are replaced with source, object AID, delete message extension header, then forward described AID data message to object AID sensing terminal.
12. methods as claimed in claim 10, is characterized in that: described message extension header is IPV6 message extension header.
13. methods as claimed in claim 10, it is characterized in that: the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
14. 1 kinds of access devices, is characterized in that, described access device (ASN) is positioned at identify label and locator separation network, comprising:
Data message receiver module, during as source ASN, for receiving AID data message; During as destination ASN, for receiving RID data message, source in the heading of wherein AID data message, destination address are source, destination access mark (AID), and the source in the heading of RID data message, destination address are source, destination RID;
Data message parsing module, for resolution data message receiver module receive data message, if data message is AID data message, or data message is RID data message, and carry message extension header then notification data packet forwarding module forward; If data message is RID data message, and Wen Wei carries message extension header, then notification data message processing module (MPM) processes;
Data message forwarding module, during as source ASN, for the source in the heading of AID data message, destination address are replaced with source, destination Route Distinguisher (RID), and increase message extension header generation RID data message, wherein, comprise source, object AID in described message extension header, the destination ASN also for pointing to destination RID forwards described RID data message; During as destination ASN, for RID data message is forwarded to its lower terminal;
Data message processing module, for pointing to current access device to destination RID, and does not carry the prolate-headed RID data message of message and processes;
Wherein, ground option head for the purpose of described message extension header.
15. access devices as claimed in claim 14, it is characterized in that: described data message forwarding module, before forwarding to its lower terminal, first RID data message is converted to AID data message, comprise and source, object RID are replaced with source, object AID, delete message extension header, then forward described AID data message to object AID sensing terminal.
16. access devices as claimed in claim 14, is characterized in that: described message extension header is IPV6 message extension header.
17. access devices as claimed in claim 14, it is characterized in that: the front two of the option type (OptionType) of described destination option head (DestinationOptionsheader) is 00 or 01, when representing that destination node is not familiar with this option normal process data message remainder or abandon this data message.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010122079.7A CN102170389B (en) | 2010-02-26 | 2010-02-26 | data message transmission method and access device |
| PCT/CN2010/080057 WO2011103761A1 (en) | 2010-02-26 | 2010-12-21 | Data packet transmission method and access device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010122079.7A CN102170389B (en) | 2010-02-26 | 2010-02-26 | data message transmission method and access device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102170389A CN102170389A (en) | 2011-08-31 |
| CN102170389B true CN102170389B (en) | 2016-01-20 |
Family
ID=44491373
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010122079.7A Expired - Fee Related CN102170389B (en) | 2010-02-26 | 2010-02-26 | data message transmission method and access device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102170389B (en) |
| WO (1) | WO2011103761A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103095581B (en) * | 2011-10-31 | 2017-03-22 | 中兴通讯股份有限公司 | System and method for separated terminal identification location marking and service router |
| CN103108056B (en) * | 2011-11-15 | 2017-05-24 | 中兴通讯股份有限公司 | Device and method capable of achieving subscriber identifier and locator separation network |
| CN103166825B (en) * | 2011-12-16 | 2018-07-31 | 中兴通讯股份有限公司 | The method and system of network interworking is realized by expanding universal routed encapsulation technology |
| CN109194579B (en) * | 2018-11-19 | 2020-09-04 | 盛科网络（苏州）有限公司 | Method and device for realizing segmented routing by IPv6 |
| CN110611625B (en) | 2018-11-27 | 2020-11-06 | 新华三技术有限公司 | Network equipment and logic device applied to same |
| CN112532563B (en) * | 2019-09-17 | 2022-04-05 | 华为技术有限公司 | Message sending method and device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247299A (en) * | 2007-02-14 | 2008-08-20 | 华为技术有限公司 | Multi-homing network system and method for implementing multi-homing network access |
-
2010
- 2010-02-26 CN CN201010122079.7A patent/CN102170389B/en not_active Expired - Fee Related
- 2010-12-21 WO PCT/CN2010/080057 patent/WO2011103761A1/en active Application Filing
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247299A (en) * | 2007-02-14 | 2008-08-20 | 华为技术有限公司 | Multi-homing network system and method for implementing multi-homing network access |
Non-Patent Citations (2)
| Title |
|---|
| 《下一代互联网的移动性管理技术研究》;乐德广;《中国优秀硕博士学位论文全文数据库（博士） 信息科技辑》;20070615(第06期);正文第21页第3.1节、第25-26页第3.3.4节 * |
| 董平.《基于身份与位置分离映射的可扩展路由体系研究》.《中国博士学位论文全文数据库 信息科技辑》.2009,(第10期),正文第11页第2.2.1节，第32页第3.2.3节，第35页第1段，第34页图3.4. * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2011103761A1 (en) | 2011-09-01 |
| CN102170389A (en) | 2011-08-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102170389B (en) | data message transmission method and access device | |
| US8169984B2 (en) | Communication system, radio lan base station control device, and radio lan base station device | |
| CN104253759B (en) | Message forwarding method, apparatus and system | |
| CN102724118B (en) | Label distribution method and device | |
| US20080107060A1 (en) | Relay device, wireless communication system and multicast relay method | |
| EP2608581B1 (en) | Method, system and apparatus for indicating type of messages | |
| CN107852773B (en) | Data transmission method, related equipment and system | |
| CN102917333B (en) | The satellite communication system of extensive ICBM SHF satellite terminal and the cut-in method of ICBM SHF satellite terminal | |
| CN104040987A (en) | User plane data transmission method, mobility management network element, evolved node b and system | |
| CN102025600B (en) | Method, system and router for transmitting and receiving data | |
| CN102025601B (en) | Data encapsulation method and system | |
| EP2332319B1 (en) | Systems and methods for bulk release of resources associated with node failure | |
| CN103067278B (en) | A kind of method for transmission processing of Frame, equipment and system | |
| CN106888450A (en) | Information processing method and device | |
| CN102202389A (en) | Method and system for realizing gateway management | |
| CN102123072B (en) | The implementation method of Packet Classification process, network and terminal | |
| CN104995882A (en) | Packet processing method and device | |
| CN102065469A (en) | Method and mobile network system for reducing IP address requirement | |
| CN101442478B (en) | Method, system and equipment for establishing data channel of wireless network | |
| CN103685007A (en) | Method for MAC address learning during packet forwarding of edge devices and edge device | |
| CN100442769C (en) | Method and system for processing data based on between GGSN and external data network | |
| CN102957755B (en) | A kind of address resolution method, device and information transferring method | |
| US20110222541A1 (en) | Network System, Edge Node, and Relay Node | |
| CN101448298B (en) | Method for processing downlink data message of packet radio gateway equipment and device thereof | |
| KR20120011803A (en) | Method and apparatus for providing multicast service for mobile node in mobile communication system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160120 Termination date: 20180226 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |