CN108429673B - A kind of quick Future Data network implementation approach - Google Patents
A kind of quick Future Data network implementation approach Download PDFInfo
- Publication number
- CN108429673B CN108429673B CN201810236551.6A CN201810236551A CN108429673B CN 108429673 B CN108429673 B CN 108429673B CN 201810236551 A CN201810236551 A CN 201810236551A CN 108429673 B CN108429673 B CN 108429673B
- Authority
- CN
- China
- Prior art keywords
- forwarding
- router
- name
- prefix
- message
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
- H04L45/121—Shortest path evaluation by minimising delays
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention provides a kind of quick Future Data network implementation approach, the network includes backbone network and subnet, backbone network includes more than two core routers, and a core router includes more than two wireline interfaces, and each wireline interface is by an interface ID unique identification;Provided data communications method can obtain service data to mobile node through the invention, shorten the delay and cost for obtaining service data, improve service quality, and present invention can apply to the fields such as big data acquisition, are with a wide range of applications.
Description
Technical field
The present invention relates to a kind of implementation method more particularly to a kind of quick Future Data network implementation approach.
Background technique
Network has become indispensable a part in human lives, it provides a variety of data services, therefore reduces number
It is particularly important according to communication delay.In recent years, many research work are dedicated to the data communication of mobile network, to make people
It being capable of quick obtaining network service.With the development of network technology, the data communication technology of network can further increase Service Quality
Amount.
Currently, the data communication delays and cost of network are all bigger, network service performance is reduced.Therefore, how to drop
The delay of the data communication of low mobile network and cost become the hot issue of Recent study.
Summary of the invention
Goal of the invention: a kind of quick the technical problem to be solved by the present invention is in view of the deficiencies of the prior art, provide
Future Data network implementation approach.
Technical solution: the invention discloses a kind of quick Future Data network implementation approach, and the network includes backbone
Network and subnet, backbone network include more than two core routers, and a core router includes more than two wired
Interface, each wireline interface is by an interface ID unique identification;One subnet is by a couple in router and more than two shiftings
Dynamic node is constituted;One mobile node has a wireless interface;Couple in router has a wireless interface and two or more
Wireline interface;Each wireline interface of couple in router is connected with the wireline interface link of a core router, accesses road
It is linked by the wireless interface of device and the wireless interface of mobile node;
A kind of data are by a name unique identification, and a name is by name prefix and name ID unique identification;Movable joint
Point is obtained or is provided data by address and message;Address is made of forwarding prefix and name;One subnet and the subnet
Couple in router by a name prefix unique identification, which presets, such as china/js/sz/;
Message is made of source address field, destination address domain, message type field and load domain;Message type field such as following table institute
Show:
Each core router and couple in router safeguard a forwarding table, and a forwarding-table item includes forwarding prefix, connects
Mouth ID and life cycle thresholding;After couple in router starting in one subnet, before regularly publishing the name for identifying the subnet
Sew to establish or update forwarding table, process is as follows:
Step 101: starting;
Step 102: couple in router creates an address, and the forwarding prefix of the address is equal to where mark couple in router
The name prefix of subnet, name are sky;Couple in router sends one by each wireline interface and gives out information, which disappears
In breath, source address is the address of building, and destination address is sky, and type of message thresholding is 1, is loaded as sky;
Step 103: core router or couple in router to after giving out information, check forwarding from oneself interface
The interface ID of the interface is defined as f by table, and if there is a forwarding-table item, the forwarding prefix of the forwarding-table item, which is equal to, to be received
To the source address that gives out information forwarding prefix and interface ID thresholding be equal to f, then follow the steps 104, it is no to then follow the steps 105;
Step 104: receiving the core router to give out information from interface f or couple in router selects a forwarding table
, the forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the source address that gives out information received and interface ID thresholding is equal to f,
Maximum value is set by the life cycle of the forwarding-table item, executes step 106;
Step 105: receiving the core router to give out information from interface f or couple in router creates a forwarding table
, the forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the source address that gives out information received, and interface ID thresholding is equal to f,
Life cycle is set as maximum value;
Step 106: giving out information if couple in router is received from interface f, then follow the steps 108, otherwise execute step
Rapid 107;
Step 107: receiving the core router to give out information from interface f and turn from the total interface other than interface f
What hair received gives out information, and executes step 103;
Step 108: terminating;
If the life cycle of a forwarding-table item decays to 0, the forwarding-table item is deleted from forwarding table.
The above process can establish forwarding table so that it is guaranteed that routing correctness.
In the method for the invention, in data C1 by name NA1 unique identification, name NA1 is by name prefix NP1 and name
ID NID1 is constituted, and couple in router AR1 is located in subnet S1, and subnet S1 is known as by name prefix NP1 unique identification, subnet S1
The home sub-net of data C1, couple in router AR1 are known as under conditions of the home agent of data C1, and couple in router safeguards one
Binding table, each binding list item are made of forwarding prefix domain, name field and life cycle domain;
Mobile node N1 can provide data in X, and X is positive integer, every kind of data CyBy name NAyUnique identification, y value model
Enclose 1~X, name NAyBy name prefix NPyWith name ID NIDyIt constitutes, data CyHome sub-net be subnet Sy, data Cy's
Home agent is couple in router ARy;
After mobile node N1 starting, it is periodically executed following handover operations:
Step 201: starting;
Step 202: parameter z is arranged in mobile node N1, and the initial value of parameter z is 0;
Step 203: parameter z is incremented by 1 by mobile node N1, if parameter z is greater than X, is thened follow the steps 205, is otherwise executed
Step 204;
Step 204: mobile node N1 sends handover request, and in the destination address of the handover request, forwarding prefix is name
Prefix NPz, name NAz;In the source address of the handover request, forwarding prefix is the name of subnet S where identifying mobile node N1
Word prefix NP, name are sky, are loaded as sky, type of message 2, execution step 203;
Step 205: after the couple in router in subnet S receives handover request, checking forwarding table, select a forwarding table
, the forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the handover request destination address, from the interface domain of the forwarding-table item
Send the handover request;
Step 206: judgement is that core router or couple in router receive handover request, if couple in router connects
The handover request is received, thens follow the steps 208, it is no to then follow the steps 207;
Step 207: after core router receives the handover request, checking forwarding table, select a forwarding-table item, this turn
The forwarding prefix of forwarding list item is equal to the forwarding prefix of the handover request destination address, sends this from the interface domain of the forwarding-table item and cuts
Message is changed, step 206 is executed;
Step 208: after couple in router receives handover request, check binding table, it, should if there is a binding list item
The forwarding prefix of binding list item is equal to the forwarding prefix of the handover request source address, and name thresholding is equal to the handover request purpose
The name of address, thens follow the steps 209, no to then follow the steps 210;
Step 209: the couple in router for receiving handover request selects a binding list item, before the forwarding of the binding list item
Sew the forwarding prefix equal to the handover request source address, and name thresholding is equal to the name of the handover request destination address, by this
The life span of binding list item is set as maximum value, executes step 211;
Step 210: the couple in router for receiving handover request creates a binding list item, before the forwarding of the binding list item
Sew the forwarding prefix equal to the handover request source address, name thresholding is equal to the name of the handover request destination address, when existence
Between be set as maximum value;
Step 211: terminating;
If the life cycle of a binding list item decays to 0, the binding list item is deleted from binding table.
The above process can ensure to route correctness.
In the method for the invention, couple in router safeguards that a waiting table, each waiting list item include message field and life
Order period region;
In data C1 by name NA1 unique identification, name NA1 is made of name prefix NP1 and name ID NID1, data
The home sub-net of C1 is subnet S1, under conditions of the home agent of data C1 is couple in router AR1, if mobile node N1
In subnet S1, it then obtains data C1 by following processes:
Step 301: starting;
Step 302: mobile node N1 sends request message, and in the source address of the request message, forwarding prefix is NP1, name
Word is NA1, and in the destination address of the request message, forwarding prefix is NP1, name NA1, and type of message 3 loads as sky;
Step 303: after the couple in router in subnet S1 receives request message, binding table is checked, if at least existed
One binding list item, the forwarding prefix of the binding list item are equal to the forwarding prefix of request message destination address, and name thresholding etc.
In the name of request message destination address, 307 are thened follow the steps, it is no to then follow the steps 304;
Step 304: after the couple in router in subnet S1 receives request message, selecting a binding list item, the binding
The name thresholding of list item is equal to the name of request message destination address, by the forwarding prefix updates of the destination address of the request message
For the forwarding prefix of the binding list item, forwarding table being checked, selecting a forwarding-table item, the forwarding prefix of the forwarding-table item is equal to more
The forwarding prefix of request message destination address after new sends updated request message from the interface domain of the forwarding-table item;
Step 305: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 307, it is no to then follow the steps 306;
Step 306: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 305;
Step 307: after couple in router receives request message, sending the request message from wireless interface and create one etc.
To list item, waiting the message thresholding of list item is the request message received, and life cycle is maximum value, such as 1s;Mobile node
Judge whether oneself can provide the data that the name field of the request message destination address is identified after receiving request message, if energy
Data are enough provided, then follow the steps 309, it is no to then follow the steps 308;
Step 308: the mobile node for receiving request message abandons the request message, executes step 316;
Step 309: the mobile node for receiving request message sends a response message, and the destination address of the response message is
The source address of the request message received, the source address of the response message are the destination address of the request message received, message
Type is 4, and loading the data identified for the name of the request message destination address received and the mobile node can mention
The name set of all data supplied;The couple in router being connected with the mobile node link checks waiting after receiving response message
Table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the destination address of the response message
And the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 311, it is no to then follow the steps 310;
Step 310: the couple in router for receiving response message abandons the response message, executes step 316;
Step 311: the couple in router for receiving response message selects a waiting list item, the message field of the waiting list item
The source address of value is equal to the destination address of the response message, and the destination address of message thresholding is with being equal to the source of the response message
Location, the couple in router delete the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark
The name prefix for knowing subnet where the couple in router, thens follow the steps 315, no to then follow the steps 312;
Step 312: the couple in router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, sends the response message from the interface domain of the forwarding-table item;
Step 313: if couple in router receives response message, then follow the steps 315, it is no to then follow the steps 314;
Step 314: the core router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, send the response message from the interface domain of the forwarding-table item,
Execute step 313;
Step 315: the couple in router for receiving response message sends the response message from wireless interface;
Step 316: after mobile node N1 receives response message, for each name in name set in response message load
Word establishes a binary group, and first element of binary group is the name, and second element of binary group is the response message source
The forwarding prefix of address;Mobile node N1 saves the data in response message load;
Step 317: terminating.
Node by the above process being capable of quick obtaining data.
In the method for the invention, in data C2 by name NA2 unique identification, name NA2 is by name prefix NP2 and name
ID NID2 is constituted, and the home sub-net of data C2 is subnet S2, and the home agent of data C2 is couple in router AR2, mobile node
N1 is located in subnet S1, under conditions of subnet S1 is identified by name prefix NP1, if mobile node N1 saves a binary group,
First element of the binary group is NA2, then mobile node N1 selects the binary group and obtains data C2 by following processes:
Step 401: starting;
Step 402: mobile node N1 sends request message, and in the source address of the request message, forwarding prefix is NP1, name
Word is NA2, and in the destination address of the request message, forwarding prefix is second element in the binary group chosen, and name is
NA2, type of message 3 load as sky;
Step 403: after the couple in router in subnet S1 receives request message, if request message destination address turns
It sends out prefix and is equal to NP1, then follow the steps 407, it is no to then follow the steps 404;
Step 404: after the couple in router in subnet S1 receives request message, selecting a forwarding-table item, the forwarding
The forwarding prefix of list item is equal to the forwarding prefix of the request message destination address, sends the request from the interface domain of the forwarding-table item
Message;
Step 405: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 407, it is no to then follow the steps 406;
Step 406: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 405;
Step 407: after couple in router receives request message, sending the request message from wireless interface and create one etc.
To list item, waiting the message thresholding of list item is the request message received, and life cycle is maximum value, such as 1s;Mobile node
Judge whether oneself can provide the data that the name field of the request message destination address is identified after receiving request message, if energy
Data are enough provided, then follow the steps 409, it is no to then follow the steps 408;
Step 408: the mobile node for receiving request message abandons the request message, executes step 416;
Step 409: the mobile node for receiving request message sends a response message, and the destination address of the response message is
The source address of the request message received, the source address of the response message are the destination address of the request message received, message
Type is 4, and loading the data identified for the name of the request message destination address received and the mobile node can mention
The name set of all data supplied;The couple in router being connected with the mobile node link checks waiting after receiving response message
Table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the destination address of the response message
And the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 411, it is no to then follow the steps 410;
Step 410: the couple in router for receiving response message abandons the response message, executes step 416;
Step 411: the couple in router for receiving response message selects a waiting list item, the message field of the waiting list item
The source address of value is equal to the destination address of the response message, and the destination address of message thresholding is with being equal to the source of the response message
Location, the couple in router delete the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark
The name prefix for knowing subnet where the couple in router, thens follow the steps 415, no to then follow the steps 412;
Step 412: the couple in router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, sends the response message from the interface domain of the forwarding-table item;
Step 413: judgement is that core router or couple in router receive response message, if couple in router connects
Response message is received, thens follow the steps 415, it is no to then follow the steps 414;
Step 414: the core router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, send the response message from the interface domain of the forwarding-table item,
Execute step 413;
Step 415: the couple in router for receiving response message sends the response message from wireless interface;
Step 416: after mobile node N1 receives response message, for each name in name set in response message load
Word establishes a binary group, and first element of binary group is the name, and second element of binary group is the response message source
The forwarding prefix of address;Mobile node N1 saves the data in response message load;
Step 417: terminating.
Node by the above process being capable of quick obtaining data.
In the method for the invention, in data C1 by name NA1 unique identification, name NA1 is by name prefix NP1 and name
ID NID1 is constituted, and the home sub-net of data C1 is subnet S1, and the home agent of data C1 is couple in router AR1, mobile node
N2 is located in subnet S2, subnet S2 by name prefix NP2 identify under conditions of, if mobile node N2 save any one two
First element of tuple is all not equal to NA1, then mobile node N2 selects the binary group and obtains data C1 by following processes:
Step 501: starting;
Step 502: mobile node N2 sends request message, and in the source address of the request message, forwarding prefix is NP2, name
Word is NA1, and in the destination address of the request message, forwarding prefix is NP1, name NA1, and type of message 3 loads as sky;
Step 503: after the couple in router in subnet S2 receives request message, selecting a forwarding-table item, the forwarding
The forwarding prefix of list item is equal to the forwarding prefix of the request message destination address, sends the request from the interface domain of the forwarding-table item
Message;
Step 504: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 506, it is no to then follow the steps 505;
Step 505: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 504;
Step 506: after couple in router receives request message, binding table is checked, if at least there is a binding table
, the forwarding prefix of the binding list item is equal to the forwarding prefix of the request message destination address, and name thresholding is equal to request and disappears
The name for ceasing destination address, thens follow the steps 510, no to then follow the steps 507;
Step 507: after couple in router receives request message, selecting a binding list item, the name of the binding list item
Thresholding is equal to the name of the request message destination address, is the binding by the forwarding prefix updates of the destination address of the request message
The forwarding prefix of list item, checks forwarding table, selects a forwarding-table item, and the forwarding prefix of the forwarding-table item is equal to updated ask
The forwarding prefix for seeking message destination address sends updated request message from the interface domain of the forwarding-table item;
Step 508: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 510, it is no to then follow the steps 509;
Step 509: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 508;
Step 510: after couple in router receives request message, sending the request message from wireless interface and create one etc.
To list item, the message thresholding of the waiting list item is the request message received, and life cycle is maximum value, such as 1s;Movable joint
Point judges the data that the name field of the request message destination address is identified oneself whether can be provided after receiving request message, if
Data are capable of providing, then follow the steps 512, it is no to then follow the steps 511;
Step 511: the mobile node for receiving request message abandons the request message, executes step 519;
Step 512: the mobile node for receiving request message sends a response message, and the destination address of the response message is
The source address of the request message received, the source address of the response message are the destination address of the request message received, message
Type is 4, and loading the data identified for the name of the request message destination address received and the mobile node can mention
The name set of all data supplied;The couple in router being connected with the mobile node link checks waiting after receiving response message
Table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the destination address of the response message,
And the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 514, it is no to then follow the steps 513;
Step 513: the couple in router for receiving response message abandons the response message, executes step 519;
Step 514: the couple in router for receiving response message selects a waiting list item, the message field of the waiting list item
The source address of value is equal to the destination address of the response message, and the destination address of message thresholding is with being equal to the source of the response message
Location, the couple in router delete the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark
The name prefix for knowing subnet where the couple in router, thens follow the steps 518, no to then follow the steps 515;
Step 515: the couple in router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, sends the response message from the interface domain of the forwarding-table item;
Step 516: if couple in router receives response message, then follow the steps 518, it is no to then follow the steps 517;
Step 517: the core router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, send the response message from the interface domain of the forwarding-table item,
Execute step 516;
Step 518: the couple in router for receiving response message sends the response message from wireless interface;
Step 519: after mobile node N1 receives response message, for each name in name set in response message load
Word establishes a binary group, and first element of binary group is the name, and second element of binary group is the response message source
The forwarding prefix of address;Mobile node N1 saves the data in response message load;
Step 520: terminating.
The above process can ensure mobile node quick obtaining data.
The utility model has the advantages that the present invention provides a kind of quick Future Data network implementation approach, mobile node passes through this hair
Data communications method provided by bright can obtain service data, shorten the delay and cost for obtaining service data, improve
Service quality, present invention can apply to the fields such as big data acquisition, are with a wide range of applications.
Detailed description of the invention
The present invention is done with reference to the accompanying drawings and detailed description and is further illustrated, of the invention is above-mentioned
And/or otherwise advantage will become apparent.
Fig. 1 establishes forwarding table flow diagram to be of the present invention.
Fig. 2 is switching flow schematic diagram of the present invention.
Fig. 3 is data communication process schematic diagram of the present invention.
Fig. 4 is acquisition data flow diagram of the present invention.
Fig. 5 is acquisition teledata flow diagram of the present invention.
Specific embodiment:
The present invention provides a kind of quick Future Data network implementation approach, mobile node is provided through the invention
Data communications method can obtain service data, shorten the delay and cost for obtaining service data, improve service quality, this
Invention can be applied to the fields such as big data acquisition, be with a wide range of applications.
Fig. 1 establishes forwarding table flow diagram to be of the present invention.The network includes backbone network and subnet, backbone
Network includes more than two core routers, and a core router includes more than two wireline interfaces, each wired to connect
Mouth is by an interface ID unique identification;One subnet is made of a couple in router and more than two mobile nodes;One
Mobile node has a wireless interface;Couple in router has a wireless interface and more than two wireline interfaces;Access
Each wireline interface of router is connected with the wireline interface link of a core router, the wireless interface of couple in router with
The wireless interface of mobile node links;
A kind of data are by a name unique identification, and a name is by name prefix and name ID unique identification;Movable joint
Point is obtained or is provided data by address and message;Address is made of forwarding prefix and name;One subnet and the subnet
Couple in router by a name prefix unique identification, which presets;
Message is made of source address field, destination address domain, message type field and load domain;Message type field such as following table institute
Show:
Type of message | Value |
It gives out information | 1 |
Handover request | 2 |
Request message | 3 |
Response message | 4 |
Each core router and couple in router safeguard a forwarding table, and a forwarding-table item includes forwarding prefix, connects
Mouth ID and life cycle thresholding;After couple in router starting in one subnet, before regularly publishing the name for identifying the subnet
Sew to establish or update forwarding table, process is as follows:
Step 101: starting;
Step 102: couple in router creates an address, and the forwarding prefix of the address is equal to where mark couple in router
The name prefix of subnet, name are sky;Couple in router sends one by each wireline interface and gives out information, which disappears
In breath, source address is the address of building, and destination address is sky, and type of message thresholding is 1, is loaded as sky;
Step 103: core router or couple in router to after giving out information, check forwarding from oneself interface
The interface ID of the interface is defined as f by table, and if there is a forwarding-table item, the forwarding prefix of the forwarding-table item, which is equal to, to be received
To the source address that gives out information forwarding prefix and interface ID thresholding be equal to f, then follow the steps 104, it is no to then follow the steps 105;
Step 104: receiving the core router to give out information from interface f or couple in router selects a forwarding table
, the forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the source address that gives out information received and interface ID thresholding is equal to f,
Maximum value is set by the life cycle of the forwarding-table item, executes step 106;
Step 105: receiving the core router to give out information from interface f or couple in router creates a forwarding table
, the forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the source address that gives out information received, and interface ID thresholding is equal to f,
Life cycle is set as maximum value;
Step 106: giving out information if couple in router is received from interface f, then follow the steps 108, otherwise execute step
Rapid 107;
Step 107: receiving the core router to give out information from interface f and turn from the total interface other than interface f
What hair received gives out information, and executes step 103;
Step 108: terminating;
If the life cycle of a forwarding-table item decays to 0, the forwarding-table item is deleted from forwarding table.
Fig. 2 is switching flow schematic diagram of the present invention.In data C1 by name NA1 unique identification, name NA1 is by name
Word prefix NP1 and name ID NID1 is constituted, and couple in router AR1 is located in subnet S1, and subnet S1 is unique by name prefix NP1
Mark, subnet S1 are known as the home sub-net of data C1, and couple in router AR1 is known as under conditions of the home agent of data C1, connects
Enter router and safeguards that a binding table, each binding list item are made of forwarding prefix domain, name field and life cycle domain;
Mobile node N1 can provide data in X, and X is positive integer, every kind of data CyBy name NAyUnique identification, y value model
Enclose 1~X, name NAyBy name prefix NPyWith name ID NIDyIt constitutes, data CyHome sub-net be subnet Sy, data Cy's
Home agent is couple in router ARy;
After mobile node N1 starting, it is periodically executed following handover operations:
Step 201: starting;
Step 202: parameter z is arranged in mobile node N1, and the initial value of parameter z is 0;
Step 203: parameter z is incremented by 1 by mobile node N1, if parameter z is greater than X, is thened follow the steps 205, is otherwise executed
Step 204;
Step 204: mobile node N1 sends handover request, and in the destination address of the handover request, forwarding prefix is name
Prefix NPz, name NAz;In the source address of the handover request, forwarding prefix is the name of subnet S where identifying mobile node N1
Word prefix NP, name are sky, are loaded as sky, type of message 2, execution step 203;
Step 205: after the couple in router in subnet S receives handover request, checking forwarding table, select a forwarding table
, the forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the handover request destination address, from the interface domain of the forwarding-table item
Send the handover request;
Step 206: judgement is that core router or couple in router receive handover request, if couple in router connects
The handover request is received, thens follow the steps 208, it is no to then follow the steps 207;
Step 207: after core router receives the handover request, checking forwarding table, select a forwarding-table item, this turn
The forwarding prefix of forwarding list item is equal to the forwarding prefix of the handover request destination address, sends this from the interface domain of the forwarding-table item and cuts
Message is changed, step 206 is executed;
Step 208: after couple in router receives handover request, check binding table, it, should if there is a binding list item
The forwarding prefix of binding list item is equal to the forwarding prefix of the handover request source address, and name thresholding is equal to the handover request purpose
The name of address, thens follow the steps 209, no to then follow the steps 210;
Step 209: the couple in router for receiving handover request selects a binding list item, before the forwarding of the binding list item
Sew the forwarding prefix equal to the handover request source address, and name thresholding is equal to the name of the handover request destination address, by this
The life span of binding list item is set as maximum value, executes step 211;
Step 210: the couple in router for receiving handover request creates a binding list item, before the forwarding of the binding list item
Sew the forwarding prefix equal to the handover request source address, name thresholding is equal to the name of the handover request destination address, when existence
Between be set as maximum value;
Step 211: terminating;
If the life cycle of a binding list item decays to 0, the binding list item is deleted from binding table.
Fig. 3 is data communication process schematic diagram of the present invention.Couple in router safeguards a waiting table, each waiting
List item includes message field and life cycle domain;
In data C1 by name NA1 unique identification, name NA1 is made of name prefix NP1 and name ID NID1, data
The home sub-net of C1 is subnet S1, under conditions of the home agent of data C1 is couple in router AR1, if mobile node N1
In subnet S1, it then obtains data C1 by following processes:
Step 301: starting;
Step 302: mobile node N1 sends request message, and in the source address of the request message, forwarding prefix is NP1, name
Word is NA1, and in the destination address of the request message, forwarding prefix is NP1, name NA1, and type of message 3 loads as sky;
Step 303: after the couple in router in subnet S1 receives request message, binding table is checked, if at least existed
One binding list item, the forwarding prefix of the binding list item are equal to the forwarding prefix of request message destination address, and name thresholding etc.
In the name of request message destination address, 307 are thened follow the steps, it is no to then follow the steps 304;
Step 304: after the couple in router in subnet S1 receives request message, selecting a binding list item, the binding
The name thresholding of list item is equal to the name of request message destination address, by the forwarding prefix updates of the destination address of the request message
For the forwarding prefix of the binding list item, forwarding table being checked, selecting a forwarding-table item, the forwarding prefix of the forwarding-table item is equal to more
The forwarding prefix of request message destination address after new sends updated request message from the interface domain of the forwarding-table item;
Step 305: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 307, it is no to then follow the steps 306;
Step 306: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 305;
Step 307: after couple in router receives request message, sending the request message from wireless interface and create one etc.
To list item, waiting the message thresholding of list item is the request message received, and life cycle is maximum value;Mobile node receives request
Judge whether oneself can provide the data that the name field of the request message destination address is identified after message, if it is possible to provide number
According to, then follow the steps 309, it is no to then follow the steps 308;
Step 308: the mobile node for receiving request message abandons the request message, executes step 316;
Step 309: the mobile node for receiving request message sends a response message, and the destination address of the response message is
The source address of the request message received, the source address of the response message are the destination address of the request message received, message
Type is 4, and loading the data identified for the name of the request message destination address received and the mobile node can mention
The name set of all data supplied;The couple in router being connected with the mobile node link checks waiting after receiving response message
Table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the destination address of the response message
And the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 311, it is no to then follow the steps 310;
Step 310: the couple in router for receiving response message abandons the response message, executes step 316;
Step 311: the couple in router for receiving response message selects a waiting list item, the message field of the waiting list item
The source address of value is equal to the destination address of the response message, and the destination address of message thresholding is with being equal to the source of the response message
Location, the couple in router delete the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark
The name prefix for knowing subnet where the couple in router, thens follow the steps 315, no to then follow the steps 312;
Step 312: the couple in router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, sends the response message from the interface domain of the forwarding-table item;
Step 313: if couple in router receives response message, then follow the steps 315, it is no to then follow the steps 314;
Step 314: the core router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, send the response message from the interface domain of the forwarding-table item,
Execute step 313;
Step 315: the couple in router for receiving response message sends the response message from wireless interface;
Step 316: after mobile node N1 receives response message, for each name in name set in response message load
Word establishes a binary group, and first element of binary group is the name, and second element of binary group is the response message source
The forwarding prefix of address;Mobile node N1 saves the data in response message load;
Step 317: terminating.
Fig. 4 is acquisition data flow diagram of the present invention.In data C2 by name NA2 unique identification, movable joint
Point N1 is located in subnet S1, under conditions of subnet S1 is identified by name prefix NP1, if mobile node N1 saves a binary
Group, first element of the binary group are NA2, then mobile node N1 selects the binary group and obtains data by following processes
C2:
Step 401: starting;
Step 402: mobile node N1 sends request message, and in the source address of the request message, forwarding prefix is NP1, name
Word is NA2, and in the destination address of the request message, forwarding prefix is second element in the binary group chosen, and name is
NA2, type of message 3 load as sky;
Step 403: after the couple in router in subnet S1 receives request message, if request message destination address turns
It sends out prefix and is equal to NP1, then follow the steps 407, it is no to then follow the steps 404;
Step 404: after the couple in router in subnet S1 receives request message, selecting a forwarding-table item, the forwarding
The forwarding prefix of list item is equal to the forwarding prefix of the request message destination address, sends the request from the interface domain of the forwarding-table item
Message;
Step 405: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 407, it is no to then follow the steps 406;
Step 406: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 405;
Step 407: after couple in router receives request message, sending the request message from wireless interface and create one etc.
To list item, waiting the message thresholding of list item is the request message received, and life cycle is maximum value;Mobile node receives request
Judge whether oneself can provide the data that the name field of the request message destination address is identified after message, if it is possible to provide number
According to, then follow the steps 409, it is no to then follow the steps 408;
Step 408: the mobile node for receiving request message abandons the request message, executes step 416;
Step 409: the mobile node for receiving request message sends a response message, and the destination address of the response message is
The source address of the request message received, the source address of the response message are the destination address of the request message received, message
Type is 4, and loading the data identified for the name of the request message destination address received and the mobile node can mention
The name set of all data supplied;The couple in router being connected with the mobile node link checks waiting after receiving response message
Table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the destination address of the response message
And the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 411, it is no to then follow the steps 410;
Step 410: the couple in router for receiving response message abandons the response message, executes step 416;
Step 411: the couple in router for receiving response message selects a waiting list item, the message field of the waiting list item
The source address of value is equal to the destination address of the response message, and the destination address of message thresholding is with being equal to the source of the response message
Location, the couple in router delete the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark
The name prefix for knowing subnet where the couple in router, thens follow the steps 415, no to then follow the steps 412;
Step 412: the couple in router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, sends the response message from the interface domain of the forwarding-table item;
Step 413: judgement is that core router or couple in router receive response message, if couple in router connects
Response message is received, thens follow the steps 415, it is no to then follow the steps 414;
Step 414: the core router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, send the response message from the interface domain of the forwarding-table item,
Execute step 413;
Step 415: the couple in router for receiving response message sends the response message from wireless interface;
Step 416: after mobile node N1 receives response message, for each name in name set in response message load
Word establishes a binary group, and first element of binary group is the name, and second element of binary group is the response message source
The forwarding prefix of address;Mobile node N1 saves the data in response message load;
Step 417: terminating.
Fig. 5 is acquisition teledata flow diagram of the present invention.In data C1 by name NA1 unique identification, name
Word NA1 is made of name prefix NP1 and name ID NID1, and the home sub-net of data C1 is subnet S1, and mobile node N2 is located at son
It nets in S2, under conditions of subnet S2 is identified by name prefix NP2, if the of any one binary group that mobile node N2 is saved
One element is all not equal to NA1, then mobile node N2 selects the binary group and obtains data C1 by following processes:
Step 501: starting;
Step 502: mobile node N2 sends request message, and in the source address of the request message, forwarding prefix is NP2, name
Word is NA1, and in the destination address of the request message, forwarding prefix is NP1, name NA1, and type of message 3 loads as sky;
Step 503: after the couple in router in subnet S2 receives request message, selecting a forwarding-table item, the forwarding
The forwarding prefix of list item is equal to the forwarding prefix of the request message destination address, sends the request from the interface domain of the forwarding-table item
Message;
Step 504: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 506, it is no to then follow the steps 505;
Step 505: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 504;
Step 506: after couple in router receives request message, binding table is checked, if at least there is a binding table
, the forwarding prefix of the binding list item is equal to the forwarding prefix of the request message destination address, and name thresholding is equal to request and disappears
The name for ceasing destination address, thens follow the steps 510, no to then follow the steps 507;
Step 507: after couple in router receives request message, selecting a binding list item, the name of the binding list item
Thresholding is equal to the name of the request message destination address, is the binding by the forwarding prefix updates of the destination address of the request message
The forwarding prefix of list item, checks forwarding table, selects a forwarding-table item, and the forwarding prefix of the forwarding-table item is equal to updated ask
The forwarding prefix for seeking message destination address sends updated request message from the interface domain of the forwarding-table item;
Step 508: judgement is that core router or couple in router receive request message, if couple in router connects
Request message is received, thens follow the steps 510, it is no to then follow the steps 509;
Step 509: after core router receives request message, selecting a forwarding-table item, the forwarding of the forwarding-table item
Prefix is equal to the forwarding prefix of the request message destination address received, sends the request from the interface domain of the forwarding-table item and disappears
Breath executes step 508;
Step 510: after couple in router receives request message, sending the request message from wireless interface and create one etc.
To list item, the message thresholding of the waiting list item is the request message received, and life cycle is maximum value;Mobile node, which receives, asks
Judge whether oneself can provide the data that the name field of the request message destination address is identified after seeking message, if it is possible to provide
Data, then follow the steps 512, no to then follow the steps 511;
Step 511: the mobile node for receiving request message abandons the request message, executes step 519;
Step 512: the mobile node for receiving request message sends a response message, and the destination address of the response message is
The source address of the request message received, the source address of the response message are the destination address of the request message received, message
Type is 4, and loading the data identified for the name of the request message destination address received and the mobile node can mention
The name set of all data supplied;The couple in router being connected with the mobile node link checks waiting after receiving response message
Table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the destination address of the response message,
And the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 514, it is no to then follow the steps 513;
Step 513: the couple in router for receiving response message abandons the response message, executes step 519;
Step 514: the couple in router for receiving response message selects a waiting list item, the message field of the waiting list item
The source address of value is equal to the destination address of the response message, and the destination address of message thresholding is with being equal to the source of the response message
Location, the couple in router delete the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark
The name prefix for knowing subnet where the couple in router, thens follow the steps 518, no to then follow the steps 515;
Step 515: the couple in router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, sends the response message from the interface domain of the forwarding-table item;
Step 516: if couple in router receives response message, then follow the steps 518, it is no to then follow the steps 517;
Step 517: the core router for receiving response message selects a forwarding-table item, before the forwarding of the forwarding-table item
Sew the forwarding prefix for being equal to the response message destination address received, send the response message from the interface domain of the forwarding-table item,
Execute step 516;
Step 518: the couple in router for receiving response message sends the response message from wireless interface;
Step 519: after mobile node N1 receives response message, for each name in name set in response message load
Word establishes a binary group, and first element of binary group is the name, and second element of binary group is the response message source
The forwarding prefix of address;Mobile node N1 saves the data in response message load;
Step 520: terminating.
Embodiment 1
Based on the simulation parameter of table 1, the present embodiment simulates one of present invention quickly Future Data network implementations
Method, performance evaluation are as follows: when mobile node quantity increases, volume of transmitted data increases, network performance decline, therefore data pass
Defeated delay increases, and the average retardation that mobile node obtains service data is 1.5s.
1 simulation parameter of table
The present invention provides a kind of thinkings of quick Future Data network implementation approach, implement the technical solution
There are many method and approach, the above is only a preferred embodiment of the present invention, it is noted that for the common of the art
For technical staff, various improvements and modifications may be made without departing from the principle of the present invention, these are improved and profit
Decorations also should be regarded as protection scope of the present invention.The available prior art of each component part being not known in the present embodiment is subject to reality
It is existing.
Claims (5)
1. a kind of quick Future Data network implementation approach, which is characterized in that the network includes backbone network and subnet, bone
Dry network includes more than two core routers, and a core router includes more than two wireline interfaces, each wired
Interface is by an interface ID unique identification;One subnet is made of a couple in router and more than two mobile nodes;One
A mobile node has a wireless interface;Couple in router has a wireless interface and more than two wireline interfaces;It connects
The each wireline interface for entering router is connected with the wireline interface link of a core router, the wireless interface of couple in router
It is linked with the wireless interface of mobile node;
A kind of data are by a name unique identification, and a name is by name prefix and name ID unique identification;Mobile node is logical
It crosses address and message obtains or provide data;Address is made of forwarding prefix and name;One subnet and the subnet connect
Enter router by a name prefix unique identification, which presets;
Message is made of source address field, destination address domain, message type field and load domain;Message type field is as follows:
Type of message respectively gives out information, handover request, request message and response message, corresponding value are respectively 1,2,3
With 4;Each core router and couple in router safeguard a forwarding table, and a forwarding-table item includes forwarding prefix, interface ID
And life cycle thresholding;In one subnet couple in router starting after, regularly publish identify the subnet name prefix with
It establishes or updates forwarding table, process is as follows:
Step 101: starting;
Step 102: couple in router creates an address, and the forwarding prefix of the address is equal to subnet where mark couple in router
Name prefix, name be sky;Couple in router sends one by each wireline interface and gives out information, this gives out information
In, source address is the address of creation, and destination address is sky, and type of message thresholding is 1, is loaded as sky;
Step 103: core router or couple in router to after giving out information, check forwarding table from oneself interface,
The interface ID of the interface is defined as f, if there is a forwarding-table item, the forwarding prefix of the forwarding-table item, which is equal to, to be received
The forwarding prefix and interface ID thresholding for the source address that gives out information are equal to f, then follow the steps 104, no to then follow the steps 105;
Step 104: the core router to give out information is received from interface f or couple in router selects a forwarding-table item,
The forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the source address that gives out information received and interface ID thresholding is equal to f, will
The life cycle of the forwarding-table item is set as maximum value, executes step 106;
Step 105: the core router to give out information is received from interface f or couple in router creates a forwarding-table item,
The forwarding prefix of the forwarding-table item is equal to the forwarding prefix of the source address that gives out information received, and interface ID thresholding is equal to f, life
Period is set as maximum value;
Step 106: it gives out information if couple in router is received from interface f, thens follow the steps 108, it is no to then follow the steps
107;
Step 107: receiving the core router to give out information from interface f and connect from the total interface forwarding other than interface f
What is received gives out information, and executes step 103;
Step 108: terminating;
If the life cycle of a forwarding-table item decays to 0, the forwarding-table item is deleted from forwarding table.
2. a kind of quick Future Data network implementation approach according to claim 1, which is characterized in that data C1 by
Name NA1 unique identification, name NA1 are made of name prefix NP1 and name ID NID1, and couple in router AR1 is located at subnet S1
Interior, for subnet S1 by name prefix NP1 unique identification, subnet S1 is known as the home sub-net of data C1, and couple in router AR1 is known as counting
Under conditions of the home agent of C1, couple in router AR1 safeguard a binding table, each binding list item by forwarding prefix domain,
Name field and life cycle domain are constituted;
Mobile node N1 can provide X kind data, and X is positive integer, every kind of data CyBy name NAyUnique identification, y value range 1~
X, name NAyBy name prefix NPyWith name ID NIDyIt constitutes, data CyHome sub-net be subnet Sy, data CyLocal generation
Reason is couple in router ARy;
After mobile node N1 starting, it is periodically executed following handover operations:
Step 201: starting;
Step 202: parameter z is arranged in mobile node N1, and the initial value of parameter z is 0;
Step 203: parameter z is incremented by 1 by mobile node N1, if parameter z is greater than X, thens follow the steps 205, no to then follow the steps
204;
Step 204: mobile node N1 sends handover request, and in the destination address of the handover request, forwarding prefix is name prefix
NPz, name NAz;In the source address of the handover request, before forwarding the name that prefix is subnet S where identifying mobile node N1
Sew NP, name is sky, is loaded as sky, type of message 2, execution step 203;
Step 205: the couple in router for receiving handover request in subnet S checks forwarding table, selects a forwarding-table item, should
The forwarding prefix of forwarding-table item is equal to the forwarding prefix of the handover request destination address, and sending from the interface domain of the forwarding-table item should
Handover request;
Step 206: judgement is that core router or the couple in router being connected with the interface link for sending the handover request connect
Handover request is received, if couple in router receives the handover request, thens follow the steps 208, it is no to then follow the steps 207;
Step 207: after core router receives the handover request, checking forwarding table, select a forwarding-table item, the forwarding table
The forwarding prefix of item is equal to the forwarding prefix of the handover request destination address, sends the switching from the interface domain of the forwarding-table item and disappears
Breath executes step 206;
Step 208: after the couple in router in step 206 receives handover request, checking binding table, bound if there is one
List item, the forwarding prefix of the binding list item is equal to the forwarding prefix of the handover request source address, and name thresholding is equal to the switching
The name of message destination address, thens follow the steps 209, no to then follow the steps 210;
Step 209: the couple in router for receiving handover request selects a binding list item, forwarding prefix of the binding list item etc.
In the forwarding prefix of the handover request source address, and name thresholding is equal to the name of the handover request destination address, by the binding
The life cycle of list item is set as maximum value, executes step 211;
Step 210: the couple in router for receiving handover request creates a binding list item, forwarding prefix of the binding list item etc.
In the forwarding prefix of the handover request source address, name thresholding is equal to the name of the handover request destination address, and life cycle is set
It is set to maximum value;
Step 211: terminating;
If the life cycle of a binding list item decays to 0, the binding list item is deleted from binding table.
3. a kind of quick Future Data network implementation approach according to claim 2, which is characterized in that couple in router
Safeguard that a waiting table, each waiting list item include message field and life cycle domain;
In data C1 by name NA1 unique identification, name NA1 is made of name prefix NP1 and name ID NID1, data C1's
Home sub-net is subnet S1, under conditions of the home agent of data C1 is couple in router AR1, if mobile node N1 is located at son
It nets in S1, it then obtains data C1 by following processes:
Step 301: starting;
Step 302: mobile node N1 sends request message, and in the source address of the request message, forwarding prefix is NP1, and name is
NA1, in the destination address of the request message, forwarding prefix is NP1, name NA1, and type of message 3 loads as sky;
Step 303: the couple in router for receiving request message in subnet S1 checks binding table, ties up if at least having one
Determine list item, the forwarding prefix of the binding list item is equal to the forwarding prefix of request message destination address, and name thresholding is equal to request
The name of message destination address, thens follow the steps 307, no to then follow the steps 304;
Step 304: after the couple in router in subnet S1 in step 303 receives request message, a binding list item is selected,
The name thresholding of the binding list item is equal to the name of request message destination address, before the forwarding of the destination address of the request message
Sew the forwarding prefix for being updated to the binding list item, check forwarding table, selects a forwarding-table item, the forwarding prefix of the forwarding-table item
Equal to the forwarding prefix of updated request message destination address, updated request is sent from the interface domain of the forwarding-table item and is disappeared
Breath;
Step 305: judgement is that core router or the couple in router being connected with the interface link for sending the request message connect
Request message is received, if couple in router receives request message, thens follow the steps 307, it is no to then follow the steps 306;
Step 306: after core router receives request message, selecting a forwarding-table item, the forwarding prefix of the forwarding-table item
Equal to the forwarding prefix of the request message destination address received, the request message is sent from the interface domain of the forwarding-table item, is held
Row step 305;
Step 307: after the couple in router in step 305 receives request message, sending the request message from wireless interface and create
A waiting list item is built, waiting the message thresholding of list item is the request message received, and life cycle is maximum value;Receive request
The mobile node of message judges whether oneself can provide the data that the name field of the request message destination address is identified, if energy
Data are enough provided, then follow the steps 309, it is no to then follow the steps 308;
Step 308: the mobile node for receiving request message in step 307 abandons the request message, executes step 316;
Step 309: the mobile node for receiving request message in step 307 sends a response message, the mesh of the response message
Address be the request message received source address, the source address of the response message is the destination of the request message received
Location, type of message 4 load the data identified for the name of the request message destination address received and the mobile node
The name set for all data that can be provided;The couple in router being connected with the mobile node link is looked into after receiving response message
See waiting table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the mesh of the response message
Address and the destination address of message thresholding be equal to the source address of the response message, then follow the steps 311, it is no to then follow the steps
310;
Step 310: the couple in router for receiving response message abandons the response message, executes step 316;
Step 311: the couple in router for receiving response message selects a waiting list item, the message thresholding of the waiting list item
Source address is equal to the destination address of the response message, and the destination address of message thresholding is equal to the source address of the response message, should
Couple in router deletes the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark, this is connect
The name prefix for entering subnet where router, thens follow the steps 315, no to then follow the steps 312;
Step 312: the couple in router for receiving response message selects a forwarding-table item, forwarding prefix of the forwarding-table item etc.
In the forwarding prefix of the response message destination address received, the response message is sent from the interface domain of the forwarding-table item;
Step 313: if the couple in router being connected with the interface link for sending response message receives response message, executing
Step 315, no to then follow the steps 314;
Step 314: the core router for receiving response message selects a forwarding-table item, forwarding prefix of the forwarding-table item etc.
In the forwarding prefix of the response message destination address received, the response message is sent from the interface domain of the forwarding-table item, is executed
Step 313;
Step 315: the couple in router for receiving response message sends the response message from wireless interface;
Step 316: after mobile node N1 receives response message, each name in name set in response message load being built
A binary group is found, first element of binary group is the name, and second element of binary group is the response message source address
Forwarding prefix;Mobile node N1 saves the data in response message load;
Step 317: terminating.
4. a kind of quick Future Data network implementation approach according to claim 3, which is characterized in that data C2 by
Name NA2 unique identification, mobile node N1 are located in subnet S1, under conditions of subnet S1 is identified by name prefix NP1, if moved
Dynamic node N1 saves a binary group, and first element of the binary group is NA2, then mobile node N1 selects the binary group and leads to
It crosses following processes and obtains data C2:
Step 401: starting;
Step 402: mobile node N1 sends request message, and in the source address of the request message, forwarding prefix is NP1, and name is
NA2, in the destination address of the request message, forwarding prefix is second element in the binary group chosen, and name NA2 disappears
Ceasing type is 3, is loaded as sky;
Step 403: after the couple in router in subnet S1 receives request message, if before the forwarding of request message destination address
Sew and be equal to NP1, thens follow the steps 407, it is no to then follow the steps 404;
Step 404: after the couple in router in subnet S1 receives request message, selecting a forwarding-table item, the forwarding-table item
Forwarding prefix be equal to the request message destination address forwarding prefix, send the request from the interface domain of the forwarding-table item and disappear
Breath;
Step 405: judgement is that core router or couple in router receive request message, if couple in router receives
Request message, thens follow the steps 407, no to then follow the steps 406;
Step 406: after core router receives request message, selecting a forwarding-table item, the forwarding prefix of the forwarding-table item
Equal to the forwarding prefix of the request message destination address received, the request message is sent from the interface domain of the forwarding-table item, is held
Row step 405;
Step 407: after couple in router receives request message, sending the request message from wireless interface and create a waiting table
, waiting the message thresholding of list item is the request message received, and life cycle is maximum value;Receive the movable joint of request message
Point judges the data that the name field of the request message destination address is identified oneself whether can be provided, if it is possible to data are provided,
Then follow the steps 409, it is no to then follow the steps 408;
Step 408: the mobile node for receiving request message in step 407 abandons the request message, executes step 416;
Step 409: the mobile node for receiving request message in step 407 sends a response message, the mesh of the response message
Address be the request message received source address, the source address of the response message is the destination of the request message received
Location, type of message 4 load the data identified for the name of the request message destination address received and the mobile node
The name set for all data that can be provided;The couple in router being connected with the mobile node link is looked into after receiving response message
See waiting table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the mesh of the response message
Address and the destination address of message thresholding be equal to the source address of the response message, then follow the steps 411, it is no to then follow the steps
410;
Step 410: the couple in router for receiving response message abandons the response message, executes step 416;
Step 411: the couple in router for receiving response message selects a waiting list item, the message thresholding of the waiting list item
Source address is equal to the destination address of the response message, and the destination address of message thresholding is equal to the source address of the response message, should
Couple in router deletes the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark, this is connect
The name prefix for entering subnet where router, thens follow the steps 415, no to then follow the steps 412;
Step 412: the couple in router for receiving response message selects a forwarding-table item, forwarding prefix of the forwarding-table item etc.
In the forwarding prefix of the response message destination address received, the response message is sent from the interface domain of the forwarding-table item;
Step 413: judgement is that core router or couple in router receive response message, if couple in router receives
Response message, thens follow the steps 415, no to then follow the steps 414;
Step 414: the core router for receiving response message selects a forwarding-table item, forwarding prefix of the forwarding-table item etc.
In the forwarding prefix of the response message destination address received, the response message is sent from the interface domain of the forwarding-table item, is executed
Step 413;
Step 415: the couple in router for receiving response message sends the response message from wireless interface;
Step 416: after mobile node N1 receives response message, each name in name set in response message load being built
A binary group is found, first element of binary group is the name, and second element of binary group is the response message source address
Forwarding prefix;Mobile node N1 saves the data in response message load;
Step 417: terminating.
5. a kind of quick Future Data network implementation approach according to claim 3, which is characterized in that data C1 by
Name NA1 unique identification, name NA1 are made of name prefix NP1 and name ID NID1, and the home sub-net of data C1 is subnet
S1, mobile node N2 are located in subnet S2, under conditions of subnet S2 is identified by name prefix NP2, if mobile node N2 is saved
First element of any one binary group be all not equal to NA1, then mobile node N2 selects the binary group and by following mistake
Journey obtains data C1:
Step 501: starting;
Step 502: mobile node N2 sends request message, and in the source address of the request message, forwarding prefix is NP2, and name is
NA1, in the destination address of the request message, forwarding prefix is NP1, name NA1, and type of message 3 loads as sky;
Step 503: after the couple in router in subnet S2 receives request message, selecting a forwarding-table item, the forwarding-table item
Forwarding prefix be equal to the request message destination address forwarding prefix, send the request from the interface domain of the forwarding-table item and disappear
Breath;
Step 504: judgement is that core router or couple in router receive request message, if couple in router receives
Request message, thens follow the steps 506, no to then follow the steps 505;
Step 505: after core router receives request message, selecting a forwarding-table item, the forwarding prefix of the forwarding-table item
Equal to the forwarding prefix of the request message destination address received, the request message is sent from the interface domain of the forwarding-table item, is held
Row step 504;
Step 506: after couple in router receives request message, check binding table, it, should if at least there is a binding list item
The forwarding prefix of binding list item is equal to the forwarding prefix of the request message destination address, and name thresholding is equal to request message purpose
The name of address, thens follow the steps 510, no to then follow the steps 507;
Step 507: after couple in router receives request message, selecting a binding list item, the name thresholding of the binding list item
It is the binding list item by the forwarding prefix updates of the destination address of the request message equal to the name of the request message destination address
Forwarding prefix, check forwarding table, select a forwarding-table item, the forwarding prefix of the forwarding-table item is equal to updated request and disappears
The forwarding prefix for ceasing destination address sends updated request message from the interface domain of the forwarding-table item;
Step 508: judgement is that core router or couple in router receive request message, if couple in router receives
Request message, thens follow the steps 510, no to then follow the steps 509;
Step 509: after core router receives request message, selecting a forwarding-table item, the forwarding prefix of the forwarding-table item
Equal to the forwarding prefix of the request message destination address received, the request message is sent from the interface domain of the forwarding-table item, is held
Row step 508;
Step 510: after couple in router receives request message, sending the request message from wireless interface and create a waiting table
, the message thresholding of the waiting list item is the request message received, and life cycle is maximum value;Receive the movement of request message
Node judges whether oneself can provide the data that the name field of the request message destination address is identified, if it is possible to provide number
According to, then follow the steps 512, it is no to then follow the steps 511;
Step 511: the mobile node for receiving request message in step 510 abandons the request message, executes step 519;
Step 512: the mobile node for receiving request message in step 510 sends a response message, the mesh of the response message
Address be the request message received source address, the source address of the response message is the destination of the request message received
Location, type of message 4 load the data identified for the name of the request message destination address received and the mobile node
The name set for all data that can be provided;The couple in router being connected with the mobile node link is looked into after receiving response message
See waiting table, if there is a waiting list item, the source address of the message thresholding of the waiting list item is equal to the mesh of the response message
Address, and the destination address of message thresholding is equal to the source address of the response message, thens follow the steps 514, no to then follow the steps
513;
Step 513: the couple in router for receiving response message abandons the response message, executes step 519;
Step 514: the couple in router for receiving response message selects a waiting list item, the message thresholding of the waiting list item
Source address is equal to the destination address of the response message, and the destination address of message thresholding is equal to the source address of the response message, should
Couple in router deletes the waiting list item, if the forwarding prefix of the destination address of the response message received is equal to mark, this is connect
The name prefix for entering subnet where router, thens follow the steps 518, no to then follow the steps 515;
Step 515: the couple in router for receiving response message selects a forwarding-table item, forwarding prefix of the forwarding-table item etc.
In the forwarding prefix of the response message destination address received, the response message is sent from the interface domain of the forwarding-table item;
Step 516: if couple in router receives response message, then follow the steps 518, it is no to then follow the steps 517;
Step 517: the core router for receiving response message selects a forwarding-table item, forwarding prefix of the forwarding-table item etc.
In the forwarding prefix of the response message destination address received, the response message is sent from the interface domain of the forwarding-table item, is executed
Step 516;
Step 518: the couple in router for receiving response message sends the response message from wireless interface;
Step 519: after mobile node N1 receives response message, each name in name set in response message load being built
A binary group is found, first element of binary group is the name, and second element of binary group is the response message source address
Forwarding prefix;Mobile node N1 saves the data in response message load;
Step 520: terminating.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810236551.6A CN108429673B (en) | 2018-03-21 | 2018-03-21 | A kind of quick Future Data network implementation approach |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810236551.6A CN108429673B (en) | 2018-03-21 | 2018-03-21 | A kind of quick Future Data network implementation approach |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108429673A CN108429673A (en) | 2018-08-21 |
CN108429673B true CN108429673B (en) | 2019-11-05 |
Family
ID=63159201
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810236551.6A Active CN108429673B (en) | 2018-03-21 | 2018-03-21 | A kind of quick Future Data network implementation approach |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108429673B (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109089293B (en) * | 2018-10-24 | 2020-09-04 | 常熟理工学院 | Route communication realization method for future mobile network |
CN109309589B (en) * | 2018-10-24 | 2021-07-16 | 常熟理工学院 | Method for realizing smart city network |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102130834A (en) * | 2011-03-15 | 2011-07-20 | 杭州华三通信技术有限公司 | Internet protocol (IP) routing method and router |
CN106453090A (en) * | 2016-10-19 | 2017-02-22 | 常熟理工学院 | Communication method taking data as center |
CN106507428A (en) * | 2016-10-19 | 2017-03-15 | 常熟理工学院 | A kind of data communications method of following mobile network |
CN106713515A (en) * | 2017-03-29 | 2017-05-24 | 常熟理工学院 | Data transmission method of Internet of Things |
CN107666436A (en) * | 2016-07-27 | 2018-02-06 | 中兴通讯股份有限公司 | Message forwarding method and device |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9491085B2 (en) * | 2010-05-24 | 2016-11-08 | At&T Intellectual Property I, L.P. | Methods and apparatus to route control packets based on address partitioning |
-
2018
- 2018-03-21 CN CN201810236551.6A patent/CN108429673B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102130834A (en) * | 2011-03-15 | 2011-07-20 | 杭州华三通信技术有限公司 | Internet protocol (IP) routing method and router |
CN107666436A (en) * | 2016-07-27 | 2018-02-06 | 中兴通讯股份有限公司 | Message forwarding method and device |
CN106453090A (en) * | 2016-10-19 | 2017-02-22 | 常熟理工学院 | Communication method taking data as center |
CN106507428A (en) * | 2016-10-19 | 2017-03-15 | 常熟理工学院 | A kind of data communications method of following mobile network |
CN106713515A (en) * | 2017-03-29 | 2017-05-24 | 常熟理工学院 | Data transmission method of Internet of Things |
Also Published As
Publication number | Publication date |
---|---|
CN108429673A (en) | 2018-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106453090B (en) | A kind of data-centered communication means | |
CN108271227B (en) | A kind of SOT state of termination across RAT determines method and terminal | |
CN101616466B (en) | Ad hoc network zone routing method | |
CN106713515B (en) | A kind of internet of things data transmission method | |
CN106911570B (en) | A kind of reliable network data communication method | |
CN109246785B (en) | Method for realizing future mobile network | |
CN103517300B (en) | The self-discovery method, apparatus and system of distributed base station | |
CN102111912B (en) | Centralized construction method for Zigbee homogeneous tree-type wireless sensor network | |
CN106973017B (en) | A kind of quick network data communication method | |
CN108429673B (en) | A kind of quick Future Data network implementation approach | |
CN106941449B (en) | A kind of network data communication method based on on-demand mechanism | |
CN107071010B (en) | A kind of network data communication method based on vehicle-mounted cloud | |
CN108347381B (en) | A kind of a new generation's data network communications method | |
CN106506368B (en) | A kind of data communication implementation method Internet-based | |
CN110446233A (en) | Switching method, equipment and system | |
CN110138663A (en) | A kind of data-centered new generation network implementation method | |
CN108494688B (en) | A kind of Future Data network implementation approach of low-cost | |
CN105188104B (en) | A kind of implementation method of wireless communication | |
CN108449274B (en) | A kind of data-centered future network implementation method | |
KR100942156B1 (en) | Self-making and Self-healing method of Mesh Network for communication node | |
CN107612738B (en) | The uplink traffic fast switching system and method for VPLS dual-homed service model | |
CN109089293A (en) | A kind of routing Realization Method of Communication of future mobile network | |
CN102769829B (en) | The method and system that information is issued and obtained | |
CN108449443A (en) | A kind of All-IP wireless network address configuration implementation method | |
CN109041164A (en) | A kind of road safety information real-time communication method based on car networking |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |