CN108494595B - High-efficiency new-generation big data network implementation method - Google Patents

High-efficiency new-generation big data network implementation method Download PDF

Info

Publication number
CN108494595B
CN108494595B CN201810235148.1A CN201810235148A CN108494595B CN 108494595 B CN108494595 B CN 108494595B CN 201810235148 A CN201810235148 A CN 201810235148A CN 108494595 B CN108494595 B CN 108494595B
Authority
CN
China
Prior art keywords
data
message
router
interface address
name
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
Application number
CN201810235148.1A
Other languages
Chinese (zh)
Other versions
CN108494595A (en
Inventor
王晓喃
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Daoji Intelligence Anhui Information Technology Co ltd
Original Assignee
Changshu Institute of Technology
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Changshu Institute of Technology filed Critical Changshu Institute of Technology
Priority to CN201810235148.1A priority Critical patent/CN108494595B/en
Publication of CN108494595A publication Critical patent/CN108494595A/en
Application granted granted Critical
Publication of CN108494595B publication Critical patent/CN108494595B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/54Organization of routing tables
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/745Address table lookup; Address filtering

Abstract

The invention provides a high-efficiency new generation big data network implementation method, wherein the network comprises a backbone network, a data network and a mobile network; the backbone network comprises more than two core routers, the data network comprises a proxy router, a data router and an access node, and the mobile network comprises one mobile router and more than two mobile devices; each node in the big data network can quickly acquire data through the network implementation method provided by the invention, thereby greatly improving the service performance. The invention can be applied to various fields such as traffic road condition detection and control, agricultural engineering and the like, and has wide application prospect.

Description

High-efficiency new-generation big data network implementation method
Technical Field
The invention relates to an implementation method, in particular to an efficient new generation big data network implementation method.
Background
The communication between nodes in the big data network is realized by forwarding and routing of intermediate nodes, so one of the key technologies to be solved for realizing the big data network is to reduce data transmission delay so as to enable users to quickly acquire network services. With the development of network technology, big data networks will become a mode for providing services in the future.
At present, the implementation mode of the big data network is realized through broadcasting, so that both delay and cost are large, and the network service performance is reduced. Therefore, how to reduce the delay and cost of providing services by a big data network becomes a hot issue of research in recent years.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the technical problem of providing an efficient new generation big data network implementation method aiming at the defects of the prior art.
The technical scheme is as follows: the invention discloses a method for realizing a new generation of high-efficiency big data network, wherein the network comprises a backbone network, a data network and a mobile network; the backbone network comprises more than two core routers, the data network comprises a proxy router, a data router and an access node, and the mobile network comprises one mobile router and more than two mobile devices.
A core router contains X1 wired interfaces, X1 is a positive integer greater than 1; a proxy router comprises an upstream wired interface and X2 downstream wired interfaces, a data router comprises an upstream wired interface and X2 downstream wired interfaces, and X2 is a positive integer greater than 1; an access node comprising an upstream wired interface and a downstream wireless interface, a mobile router comprising an upstream wireless interface and a downstream wireless interface; a mobile device includes a wireless interface.
The upstream interface of the proxy router is connected with one interface of the core router, and each downstream interface of the proxy router is connected with the upstream interface of one data router; the upstream interface of a data router is connected with the downstream interface of a proxy router or a data router, and each downstream interface of the data router is connected with the upstream interfaces of other data routers or access nodes; the upstream interface of the access node is connected with the downstream interface of the data router, and the downstream interface of the access node is connected with the upstream interface link of the mobile router; the upstream interface of the mobile router is connected to a downstream interface link of an access node, and the downstream interface of the mobile router is connected to an interface link of the mobile device.
Each of the core routers, data routers, proxy routers, and access nodes have unique geographic coordinates.
Each interface of a core router is uniquely identified by an interface address, which is equal to j, and j takes values from 1 to X1.
The upstream interface and each downstream interface of a proxy router are uniquely identified by an interface address, and the interface address comprises a geographic abscissa and a geographic ordinate; a data network is uniquely identified by the interface address of the upstream interface of the proxy router of the network in which it resides.
The upstream interface and each downstream interface of a data router are respectively and uniquely identified by an interface address, the interface address is formed by geographical coordinates, and the geographical coordinates comprise a geographical abscissa and a geographical ordinate; the upstream interface and the downstream interface of one access node are both uniquely identified by an interface address, and the interface address is formed by geographic coordinates; the upstream interface and the downstream interface of a mobile router are both uniquely identified by an interface address, which is composed of geographical coordinates.
One kind of data is uniquely identified by a name, and one name is composed of geographical coordinates and a name ID; the mobile equipment realizes data communication through messages; a message is composed of a name field, a message type field, a source interface address set field, a destination interface address set field, an identification field and a load.
If one type of data has a length of m bits, a maximum length of a message payload is n bits, n and m are positive integers, m is greater than w1 xn, and w1 is a positive integer greater than 10, the data is divided into u data blocks and transmitted through u messages, as shown in equation (1); the length of the first u-1 data blocks is n, and the length of the last data block is m- (u-1) x n;
Figure GDA0002881747940000021
the message types are shown in the following table:
message type value Message name
1 Address configuration messages
2 Creating forwarding table messages
3 Data request message
4 Data acquisition messages
5 Data response message
The identification field of a message is only valid when the message type is 5, and the value of the identification field is 0 or 1; if the identification domain value is 0, the message load is the last data block of the type of data; if the identification field value is 1, the message load is indicated as other data blocks except the last data block in the type of data.
If the coordinates of the access node are (x1, y1), after the access node is started, the access node sets the interface address of the upstream interface of the access node to (x1, y1), the interface address of the downstream interface to (x1+ b1, y1+ b1), b1 is a non-zero integer, and the access node periodically performs the following interface address configuration operations:
step 101: start of
Step 102: the access node sends an address configuration message from the upstream interface, the geographic coordinate of the name domain value of the address configuration message is (x1, y1), the name ID is 0, the identifier is 0, the message type is 1, the source interface address set and the destination interface address set are both empty, and the load is empty.
Step 103: and judging whether the proxy router or the data router receives the address configuration message, if the proxy router receives the address configuration message, executing the step 105, and if not, executing the step 104.
Step 104: after receiving the address configuration message from the downstream interface, the data router sets the interface address of the downstream interface as the geographic coordinate in the name domain of the received address configuration message, and sets the interface address of the upstream interface as the geographic coordinate of the upstream interface. The data router sends an address configuration message from the upstream interface, the geographical coordinate of the name field value of the address configuration message is the geographical coordinate of the address configuration message, the name ID is 0, the identifier is 0, the message type is 1, the source interface address set and the destination interface address set are both empty, the load is empty, and step 103 is executed.
Step 105: after receiving the address configuration message from the downstream interface, the proxy router sets the interface address of the downstream interface as the geographic coordinate in the name domain of the received address configuration message, and sets the interface address of the upstream interface as the geographic coordinate of the proxy router.
Step 106: and (6) ending.
The proxy router and the data router can rapidly configure the address through the above process so as to ensure the correctness of data communication.
In the method of the invention, a mobile router sets the interface address of the upstream interface as the geographical coordinate (x2, y2) of the mobile router, sets the interface address of the downstream interface as (x2+ b2, y2+ b2), and b2 is a non-zero integer. A mobile device sets the interface address of its interface to its geographical coordinates. Each core router maintains a forwarding table, each forwarding table entry including geographic coordinates, an interface address and a lifecycle. After the agent router configures the interface address, the following operations are executed to create a forwarding table:
step 201: start of
Step 202: the proxy router sends a message for creating a forwarding table from an upstream interface, the geographical coordinates of the name domain value of the message for creating the forwarding table are the geographical coordinates of the proxy router, the name ID is 0, the identifier is 0, the message type is 2, the source interface address set and the destination interface address set are both empty, and the load is empty.
Step 203: and judging whether the proxy router or the core router receives the message for creating the forwarding table, if the proxy router receives the message for creating the forwarding table, executing the step 208, and if not, executing the step 204.
Step 204: after the core router receives the message for creating the forwarding table from an interface, if the interface address of the interface is k, the core router checks the forwarding table, and if a forwarding table entry exists, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table and the interface address is equal to k, step 205 is executed, otherwise step 206 is executed.
Step 205: the core router receiving the message for creating the forwarding table selects a forwarding table entry, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table, and the interface address is equal to k, sets the life cycle of the forwarding table entry to the maximum value, and executes step 207.
Step 206: and the core router receiving the message for creating the forwarding table creates a forwarding table entry, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table, the interface address is equal to k, and the life cycle is set to be the maximum value.
Step 207: the core router having received the message of creating the forwarding table forwards the received message of creating the forwarding table from all interfaces except interface k, and performs step 203.
Step 208: the proxy router that received the create forwarding table message discards the create forwarding table message.
Step 209: and (6) ending.
The above process can correctly establish the forwarding table to ensure that the mobile device can correctly acquire the data.
In the method of the invention, each agent router, data router or access node respectively maintains a data table, and each data table item is composed of a data domain, a name domain and a life cycle domain. Each agent router, data router or access node maintains an index table, and each index table item is composed of an interface address set domain, a name domain and a life cycle domain.
If the data C3 consists of the name NA3, a proxy router saves the data C3 by creating a data table entry in which the data value is data C3, the name field value is name NA3, and the lifetime is maximum. Meanwhile, the proxy router creates an index table entry, the interface address set of the index table entry is null, the name domain value is NA3, and the life cycle is maximum. The data router or access node then saves the data C3 by performing the following process:
step 301: and starting.
Step 302: the data router or access node creates a data table entry in which the data value is data C3, the name field value is name NA3, and the lifetime is maximum. Meanwhile, the data router or the access node creates an index table entry, the interface address set of the index table entry is null, the name domain value is NA3, and the life cycle is the maximum value. The data router or the access node sends a data request message through an upstream interface, in the data request message, the geographic coordinate of the name domain value is the geographic coordinate of the data router or the access node, the name ID is 0, the message type is 3, the identifier is 0, and the source interface address set is formed by the geographic coordinate of the data router or the access node. The destination interface address set is empty and the load is empty.
Step 303: it is determined whether the data request message is received by the router or the data router, and if the data request message is received by the proxy router, step 308 is performed, otherwise step 304 is performed.
Step 304: after receiving the data request message, the data router checks the index table, if there is an index table entry, the interface address set field value of the index table entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, then step 305 is executed, otherwise step 306 is executed.
Step 305: the data router receiving the data request message selects an index entry, the interface address set field value of the index entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, the life cycle of the forwarding entry is set to the maximum value, and step 307 is executed.
Step 306: and the data router receiving the data request message creates an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, the name domain value is equal to the name of the received data request message, and the life cycle of the forwarding table entry is set to be the maximum value.
Step 307: the data router receiving the data request message adds its own geographical coordinates to the source interface address set of the received data request message, and the geographical coordinates are used as the first element of the source interface address set, forwards the received data request message from the upstream interface, and executes step 303.
Step 308: after receiving the data request message, the proxy router checks the index table, if an index table entry exists, the interface address set field value of the index table entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, then step 309 is executed, otherwise step 310 is executed.
Step 309: the proxy router receiving the data request message selects an index entry, the interface address set field value of the index entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, the life cycle of the forwarding entry is set to the maximum value, and step 311 is executed.
Step 310: the proxy router receiving the data request message creates an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, the name domain value is equal to the name of the received data request message, and the life cycle of the forwarding table entry is set to be the maximum value.
Step 311: and (6) ending.
The above process can correctly save the data to ensure that the mobile device can correctly acquire the data.
In the method of the invention, if data C3 is uniquely identified by name NA3, name NA3 is composed of geographical coordinates (x3, y3) and name ID NID3, the length of data C3 is m3 bits, the maximum length of a message load is n bits, n and m3 are positive integers, m3 is greater than w1 x n, the data is divided into u3 data blocks and transmitted by u3 messages, as shown in formula (2), the length of the first u3-1 data blocks is n, and the length of the last data block is m3- (u3-1) x n.
Figure GDA0002881747940000061
Each data router, proxy router or access node maintains a request table, each request table including a name field and an interface address set field.
Under the condition that the mobile device MD3 is connected with the mobile router MR3, the mobile router MR3 is connected with the access node AP3, the access node AP3 is located in the data network DN1, and the proxy router of the data network DN1 is PR1, if at least one index entry exists in the proxy router PR1, the name field value of the index entry is NA3, the mobile device MD3 obtains the data C3 through the following processes:
step 401: and starting.
Step 402: the mobile device MD3 sends a data acquisition message, where the name of the data acquisition message is NA3, the message type is 4, the identifier is 0, the source interface address set and the destination interface address set are null, and the load is null. After receiving the data acquisition message from the downstream interface, the mobile router MR3 forwards the data acquisition message from the upstream interface.
Step 403: after the access node AP3 receives the data get message, it looks at the request table, if there is a request table entry whose name field value is equal to the name of the received data get message, then step 427 is performed, otherwise step 404 is performed.
Step 404: the access node AP3 creates a request entry with a name field value equal to the name of the received data fetch message and a set of interface addresses equal to the set of source interface addresses of the received data fetch message. The access node AP3 looks at the data table and if there is a data table entry with a name field value equal to the name of the received data acquisition message, then step 405 is performed, otherwise step 409 is performed.
Step 405: the access node AP3 divides the data C3 into u3 data blocks, sets a variable u1, and sets an initial value of the variable u1 to 0.
Step 406: the access node AP3 increments the variable u1 by 1 and performs step 407 if u1 is less than u3, otherwise performs step 408.
Step 407: the access node AP3 creates a data response message with a name field equal to the name of the received data response message, a message type of 5, an identification field of 1, a source interface address set and a destination interface address set of null, and a load of u1 data blocks, and performs step 406.
Step 408: the access node AP3 creates a data response message with a name field equal to the name of the received data response message, a message type of 5, an identification field of 0, a source interface address set and a destination interface address set of null, and a payload of u1 data block, and performs step 427.
Step 409: the access node AP3 adds its geographical coordinates to the source interface address set of the received data response message, and the geographical coordinates are the first element of the source interface address set, and forwards the received data response message from the upstream interface.
Step 410: if the proxy router receives the data response message, step 420 is performed, and if the data router or the access node receives the data response message, step 411 is performed.
Step 411: the data router or the access node checks the request table after receiving the data response message, if there is a request table entry whose name field value is equal to the name of the received data response message, step 427 is executed, otherwise, step 412 is executed.
Step 412: the data router or the access node receiving the data response message creates a request table entry, the name field value of the request table entry is equal to the name of the received data response message, and the interface address set is equal to the source interface address set of the received data response message. The data router or access node looks at the data table and if there is a data entry with a name field value equal to the name of the received data response message, step 416 is performed, otherwise step 413 is performed.
Step 413: the data router or access node that received the data response message looks at the index table, and if there is one, the name field value of the index table is equal to the name of the received data response message, then step 414 is executed, otherwise step 415 is executed.
Step 414: the data router or access node receiving the data response message selects an index table having a name field value equal to the name of the received data response message, updates the destination interface address set of the data response message to an interface address set field value of the index table, selects an interface having an interface address equal to the first element of the destination interface address set of the data response message, adds the first element of the destination interface address set of the data response message to the source interface address set of the data response message as the first element of the source interface address set, deletes the first element from the destination interface address set of the data response message, sends the data response message from the selected interface, and performs step 410.
Step 415: the data router or access node receiving the data response message adds its own geographical coordinates to the source interface address set of the data response message and serves as the first element of the source interface address set, and sends the data response message from the upstream interface, and step 410 is executed.
Step 416: the data router or the access node that receives the data response message divides the data C3 into u3 data blocks, sets a variable u1, and the initial value of the variable u1 is 0.
Step 417: the data router or access node receiving the data response message increments the variable u1 by 1 and performs step 418 if u1 is less than u3 and otherwise performs step 419.
Step 418: the data router or the access node that receives the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is null, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 417 is executed.
Step 419: the data router or the access node receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is null, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 427 is executed.
Step 420: after receiving the data response message, the proxy router checks the request table, if there is a request table entry whose name field value is equal to the name of the received data response message, then step 427 is executed, otherwise step 421 is executed.
Step 421: the proxy router receiving the data response message creates a request table entry, the name field value of the request table entry is equal to the name of the received data response message, and the interface address set is equal to the source interface address set of the received data response message. The proxy router looks at the data table and if there is a data entry with a name field value equal to the name of the received data response message, then step 423 is performed, otherwise step 422 is performed.
Step 422: the proxy router receiving the data response message selects an index table having a name field value equal to the name of the received data response message, updates the destination interface address set of the data response message to an interface address set field value of the index table, selects an interface having an interface address equal to the first element of the destination interface address set of the data response message, adds the first element of the destination interface address set of the data response message to the source interface address set of the data response message as the first element of the source interface address set, deletes the first element from the destination interface address set of the data response message, sends the data response message from the selected interface, and performs step 410.
Step 423: the proxy router having received the data response message divides the data C3 into u3 data blocks, sets a variable u1, and the initial value of the variable u1 is 0.
Step 424: the data router receiving the data response message increments the variable u1 by 1, executes step 425 if u1 is less than u3, otherwise executes step 426.
Step 425: the data router receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 424 is executed.
Step 426: the data router receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block.
Step 427: the access node, the data router or the proxy router looks at the request table, selects all request table entries with the name domain value equal to the name of the data response message, and performs the following operations for each request table entry: updating the destination interface address set of the data response message to the interface address set of the request table entry, if the destination interface address set is empty, forwarding the data response message from a downstream interface, if the destination interface address set is not empty, selecting an interface, wherein the interface address of the interface is equal to the first element of the destination interface address set, deleting the first element from the destination interface address set, forwarding the data response message from the interface, if the identification domain value of the data response message is 0, deleting the request table entry, otherwise, keeping the request table entry. If the data response message destination interface address set field value is null, then step 428 is performed, otherwise step 427 is re-performed.
Step 428: after receiving the data response message, the mobile router MR3 forwards the data response message from the downstream interface. After receiving the data response message, mobile device MD3 saves the data in the data response message.
Step 429: and (6) ending.
In the above process, after the access node, the data router or the proxy router receives the message with the message type of 5, if the data in the message type is stored, the steps 301 to 311 are executed to create the index table.
The above process can ensure that the mobile device acquires the data correctly.
In the method of the present invention, under the condition that data C3 is identified by name NA3, mobile device MD4 is connected to mobile router MR4 through a link, mobile router MR4 is connected to access node AP4 through a link, access node AP4 is located in data network DN2, and the proxy router of data network DN2 is PR2, if the name field value of any index entry of proxy router PR2 is not equal to NA3, mobile device MD4 obtains data C3 through the following process:
step 501: and starting.
Step 502: the mobile device MD4 sends a data acquisition message, where the name of the data acquisition message is NA3, the message type is 4, the identifier is 0, the source interface address set and the destination interface address set are null, and the load is null. After receiving the data acquisition message from the downstream interface, the mobile router MR4 forwards the data acquisition message from the upstream interface.
Step 503: after the access node AP4 receives the data get message, it looks at the request table, if there is a request table entry whose name field value is equal to the name of the received data get message, then step 520 is executed, otherwise step 504 is executed.
Step 504: the access node AP4 creates a request entry with a name field value equal to the name of the received data fetch message and a set of interface addresses equal to the set of source interface addresses of the received data fetch message. The access node AP4 adds its geographical coordinates to the source interface address set of the received data acquisition message and forwards the received data acquisition message from the upstream interface as the first element of the source interface address set.
Step 505: and judging whether the proxy router or the data router receives the data acquisition message, if the proxy router receives the data acquisition message, executing the step 508, and if not, executing the step 506.
Step 506: after receiving the data acquisition message, the data router checks the request table, if a request table entry exists, and the name field value of the request table entry is equal to the name of the received data acquisition message, then step 520 is executed, otherwise step 507 is executed.
Step 507: the data router receiving the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message. The data router adds its own geographical coordinates to the source interface address set of the received data acquisition message, and the geographical coordinates are used as the first element of the source interface address set, forwards the received data acquisition message from the upstream interface, and executes step 505.
Step 508: after receiving the data acquisition message, the proxy router checks the request table, if there is a request table entry whose name field value is equal to the name of the received data acquisition message, then step 520 is executed, otherwise step 509 is executed.
Step 509: the proxy router receiving the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message. The proxy router adds the geographical coordinates of the proxy router to a source interface address set of the received data acquisition message, and forwards the received data acquisition message from an upstream interface by taking the geographical coordinates as a first element of the source interface address set.
Step 510: if the core router receives the data acquisition message, step 511 is performed, and if the proxy router, the data router or the access node receives the data acquisition message, step 513 is performed.
Step 511: after the core router receives the data acquisition message from an interface, the interface address of the interface is z1, the core router checks the request table, if there is a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, step 520 is executed, otherwise step 512 is executed.
Step 512: the core router that received the data fetch message from interface z1 creates a request entry with a name field value equal to the name of the received data fetch message and a set of interface addresses equal to the source interface address set of the received data fetch message. The core router adds interface address z1 to the source interface address set of the received data acquisition message with the interface address as the first element of the source interface address set, selects a forwarding entry with a geographic coordinate field value equal to the geographic coordinate in the name of the received data acquisition message, forwards the data acquisition message from the interface identified by the interface address of the forwarding entry, and performs step 510.
Step 513: the proxy router, data router or access node looks at the request table and if there is a request table entry whose name field value is equal to the name of the received data acquisition message, step 520 is performed, otherwise step 514 is performed.
Step 514: the proxy router, the data router or the access node which receives the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message. The proxy router, data router or access node looks at the data table and if there is a data table entry with a name field value equal to the name of the received data acquisition message, step 516 is performed, otherwise step 515 is performed.
Step 515: the proxy router, the data router or the access node that receives the data acquisition message selects an index table, the name field value of the index table is equal to the name of the received data acquisition message, the destination interface address set of the data acquisition message is updated to the interface address set field value of the index table, an interface is selected, the interface address of the interface is equal to the first element of the destination interface address set of the data acquisition message, the first element of the destination interface address set of the data acquisition message is added to the source interface address set of the data acquisition message and is used as the first element of the source interface address set, the first element is deleted from the destination interface address set of the data acquisition message, the data acquisition message is sent from the selected interface, and step 513 is executed.
Step 516: the proxy router, the data router, or the access node that receives the data acquisition message divides the data C3 into u3 data blocks, sets a variable u1, and sets an initial value of the variable u1 to 0.
517: the proxy router, data router or access node receiving the data acquisition message increments the variable u1 by 1, if u1 is less than u3, step 518 is performed, otherwise step 519 is performed.
Step 518: the proxy router, the data router or the access node which receives the data acquisition message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data block, and step 517 is executed.
Step 519: the proxy router, the data router or the access node which receives the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data blocks.
Step 520: the access node, the data router, the proxy router or the core router looks up the request table, selects all request table entries with the name field value equal to the name of the data response message, and for each request table entry, the core router, the access node, the data router or the proxy router performs the following operations: updating the destination interface address set of the data response message to the interface address set of the request table entry, if the destination interface address set is empty, forwarding the data response message from a downstream interface, if the destination interface address set is not empty, selecting an interface, wherein the interface address of the interface is equal to the first element of the destination interface address set, deleting the first element from the destination interface address set, forwarding the data response message from the interface, if the identification domain value of the data response message is 0, deleting the request table entry, otherwise, keeping the request table entry. If the data response message destination interface address set field value is null, step 521 is executed, otherwise step 520 is executed again.
Step 521: after receiving the data response message, the mobile router MR4 forwards the data response message from the downstream interface. After receiving the data response message, mobile device MD4 saves the data in the data response message.
Step 522: and (6) ending.
In the above process, after the access node, the data router or the proxy router receives the message with the message type of 5, if the data in the message type is stored, the steps 301 to 311 are executed to create the index table.
The above process can ensure that the mobile device acquires the data correctly.
Has the advantages that: the invention provides an efficient new generation big data network implementation method, and each node in the big data network can rapidly acquire data through the network implementation method provided by the invention, thereby greatly improving the service performance. The invention can be applied to various fields such as traffic road condition detection and control, agricultural engineering and the like, and has wide application prospect.
Drawings
The foregoing and/or other advantages of the invention will become further apparent from the following detailed description of the invention when taken in conjunction with the accompanying drawings.
Fig. 1 is a schematic view of an address configuration process according to the present invention.
Fig. 2 is a schematic diagram of a process for establishing a forwarding table according to the present invention.
Fig. 3 is a schematic diagram of a data saving process according to the present invention.
Fig. 4 is a schematic diagram of a data communication process according to the present invention.
Fig. 5 is a schematic diagram of a data acquisition process according to the present invention.
The specific implementation mode is as follows:
the invention provides an efficient new generation big data network implementation method, and each node in the big data network can rapidly acquire data through the network implementation method provided by the invention, thereby greatly improving the service performance. The invention can be applied to various fields such as traffic road condition detection and control, agricultural engineering and the like, and has wide application prospect.
Fig. 1 is a schematic view of an address configuration process according to the present invention. The network includes a backbone network, a data network, and a mobile network. The backbone network comprises more than two core routers, the data network comprises a proxy router, a data router and an access node, and the mobile network comprises one mobile router and more than two mobile devices.
A core router contains X1 wired interfaces, X1 being a positive integer greater than 1. A proxy router comprises an upstream wired interface and X2 downstream wired interfaces, a data router comprises an upstream wired interface and X2 downstream wired interfaces, and X2 is a positive integer greater than 1. An access node includes an upstream wired interface and a downstream wireless interface, and a mobile router includes an upstream wireless interface and a downstream wireless interface. A mobile device includes a wireless interface.
The upstream interface of the proxy router is connected to an interface of the core router, and each downstream interface of the proxy router is connected to an upstream interface of a data router. The upstream interface of one data router is connected to the downstream interfaces of the proxy routers or data routers, and each downstream interface of a data router is connected to the upstream interfaces of other data routers or access nodes. The upstream interface of the access node is connected with the downstream interface of the data router, and the downstream interface of the access node is connected with the upstream interface link of the mobile router. The upstream interface of the mobile router is connected to a downstream interface link of an access node, and the downstream interface of the mobile router is connected to an interface link of the mobile device.
Each of the core routers, data routers, proxy routers, and access nodes have unique geographic coordinates.
Each interface of a core router is uniquely identified by an interface address, which is equal to j, and j takes values from 1 to X1.
The upstream interface and each downstream interface of a proxy router are uniquely identified by an interface address that includes a geographic abscissa and a geographic ordinate. A data network is uniquely identified by the interface address of the upstream interface of the proxy router of the network in which it resides.
The upstream interface and each downstream interface of a data router are uniquely identified by an interface address, the interface address is formed by geographic coordinates, and the geographic coordinates comprise a geographic horizontal coordinate and a geographic vertical coordinate. The upstream interface and the downstream interface of an access node are both uniquely identified by an interface address, which is formed by geographical coordinates. The upstream interface and the downstream interface of a mobile router are both uniquely identified by an interface address, which is composed of geographical coordinates.
One type of data is uniquely identified by a name, and one name is composed of geographical coordinates and a name ID. The mobile device communicates data through messages. A message is composed of a name field, a message type field, a source interface address set field, a destination interface address set field, an identification field and a load.
If one type of data has a length of m bits, a maximum length of a message payload is n bits, n and m are positive integers, m is greater than w1 × n, and w1 is a positive integer greater than 10, the data is divided into u data blocks and transmitted through u messages, as shown in equation (1). The first u-1 data blocks have a length of n, and the last data block has a length of m- (u-1) x n.
Figure GDA0002881747940000141
The message types are shown in the following table:
Figure GDA0002881747940000142
Figure GDA0002881747940000151
the identification field of a message is valid only if the message type is 5, which has a value of 0 or 1. If the identification field value is 0, it indicates that the message payload is the last data block of that type of data. If the identification field value is 1, the message load is indicated as other data blocks except the last data block in the type of data.
If the coordinates of the access node are (x1, y1), after the access node is started, the access node sets the interface address of the upstream interface of the access node to (x1, y1), the interface address of the downstream interface to (x1+ b1, y1+ b1), b1 is a non-zero integer, and the access node periodically performs the following interface address configuration operations:
step 101: start of
Step 102: the access node sends an address configuration message from the upstream interface, the geographic coordinate of the name domain value of the address configuration message is (x1, y1), the name ID is 0, the identifier is 0, the message type is 1, the source interface address set and the destination interface address set are both empty, and the load is empty.
Step 103: and judging whether the proxy router or the data router receives the address configuration message, if the proxy router receives the address configuration message, executing the step 105, and if not, executing the step 104.
Step 104: after receiving the address configuration message from the downstream interface, the data router sets the interface address of the downstream interface as the geographic coordinate in the name domain of the received address configuration message, and sets the interface address of the upstream interface as the geographic coordinate of the upstream interface. The data router sends an address configuration message from the upstream interface, the geographical coordinate of the name field value of the address configuration message is the geographical coordinate of the address configuration message, the name ID is 0, the identifier is 0, the message type is 1, the source interface address set and the destination interface address set are both empty, the load is empty, and step 103 is executed.
Step 105: after receiving the address configuration message from the downstream interface, the proxy router sets the interface address of the downstream interface as the geographic coordinate in the name domain of the received address configuration message, and sets the interface address of the upstream interface as the geographic coordinate of the proxy router.
Step 106: and (6) ending.
Fig. 2 is a schematic diagram of a process for establishing a forwarding table according to the present invention. A mobile router sets the interface address of its upstream interface to its own geographical coordinates (x2, y2), sets the interface address of its downstream interface to (x2+ b2, y2+ b2), and b2 is a non-zero integer. A mobile device sets the interface address of its interface to its geographical coordinates. Each core router maintains a forwarding table, each forwarding table entry including geographic coordinates, an interface address, and a lifetime. After the agent router configures the interface address, the following operations are executed to create a forwarding table:
step 201: start of
Step 202: the proxy router sends a message for creating a forwarding table from an upstream interface, the geographical coordinates of the name domain value of the message for creating the forwarding table are the geographical coordinates of the proxy router, the name ID is 0, the identifier is 0, the message type is 2, the source interface address set and the destination interface address set are both empty, and the load is empty.
Step 203: and judging whether the proxy router or the core router receives the message for creating the forwarding table, if the proxy router receives the message for creating the forwarding table, executing the step 208, and if not, executing the step 204.
Step 204: after the core router receives the message for creating the forwarding table from an interface, if the interface address of the interface is k, the core router checks the forwarding table, and if a forwarding table entry exists, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table and the interface address is equal to k, step 205 is executed, otherwise step 206 is executed.
Step 205: the core router receiving the message for creating the forwarding table selects a forwarding table entry, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table, and the interface address is equal to k, sets the life cycle of the forwarding table entry to the maximum value, and executes step 207.
Step 206: and the core router receiving the message for creating the forwarding table creates a forwarding table entry, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table, the interface address is equal to k, and the life cycle is set to be the maximum value.
Step 207: the core router having received the message of creating the forwarding table forwards the received message of creating the forwarding table from all interfaces except interface k, and performs step 203.
Step 208: the proxy router that received the create forwarding table message discards the create forwarding table message.
Step 209: and (6) ending.
Fig. 3 is a schematic diagram of a data saving process according to the present invention. Each agent router, data router or access node maintains a data table, and each data table is composed of a data field, a name field and a life cycle field. Each agent router, data router or access node maintains an index table, and each index table item is composed of an interface address set domain, a name domain and a life cycle domain.
If the data C3 consists of the name NA3, a proxy router saves the data C3 by creating a data table entry in which the data value is data C3, the name field value is name NA3, and the lifetime is maximum. Meanwhile, the proxy router creates an index table entry, the interface address set of the index table entry is null, the name domain value is NA3, and the life cycle is maximum. The data router or access node then saves the data C3 by performing the following process:
step 301: and starting.
Step 302: the data router or access node creates a data table entry in which the data value is data C3, the name field value is name NA3, and the lifetime is maximum. Meanwhile, the data router or the access node creates an index table entry, the interface address set of the index table entry is null, the name domain value is NA3, and the life cycle is the maximum value. The data router or the access node sends a data request message through an upstream interface, in the data request message, the geographic coordinate of the name domain value is the geographic coordinate of the data router or the access node, the name ID is 0, the message type is 3, the identifier is 0, and the source interface address set is formed by the geographic coordinate of the data router or the access node. The destination interface address set is empty and the load is empty.
Step 303: and judging whether the data request message is received by the proxy router or the data router, if the data request message is received by the proxy router, executing the step 308, otherwise, executing the step 304.
Step 304: after receiving the data request message, the data router checks the index table, if there is an index table entry, the interface address set field value of the index table entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, then step 305 is executed, otherwise step 306 is executed.
Step 305: the data router receiving the data request message selects an index entry, the interface address set field value of the index entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, the life cycle of the forwarding entry is set to the maximum value, and step 307 is executed.
Step 306: and the data router receiving the data request message creates an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, the name domain value is equal to the name of the received data request message, and the life cycle of the forwarding table entry is set to be the maximum value.
Step 307: the data router receiving the data request message adds its own geographical coordinates to the source interface address set of the received data request message, and the geographical coordinates are used as the first element of the source interface address set, forwards the received data request message from the upstream interface, and executes step 303.
Step 308: after receiving the data request message, the proxy router checks the index table, if an index table entry exists, the interface address set field value of the index table entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, then step 309 is executed, otherwise step 310 is executed.
Step 309: the proxy router receiving the data request message selects an index entry, the interface address set field value of the index entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, the life cycle of the forwarding entry is set to the maximum value, and step 311 is executed.
Step 310: the proxy router receiving the data request message creates an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, the name domain value is equal to the name of the received data request message, and the life cycle of the forwarding table entry is set to be the maximum value.
Step 311: and (6) ending.
Fig. 4 is a schematic diagram of a data communication process according to the present invention. If the data C3 is uniquely identified by a name NA3, the name NA3 is composed of geographical coordinates (x3, y3) and a name ID NID3, the length of the data C3 is m3 bits, the maximum length of one message payload is n bits, n and m3 are positive integers, and m3 is greater than w1 × n, the data is divided into u3 data blocks and transmitted through u3 messages, as shown in formula (2), the first u3-1 data blocks are n, and the last data block is m3- (u3-1) × n.
Figure GDA0002881747940000171
Each data router, proxy router or access node maintains a request table, each request table including a name field and an interface address set field.
Under the condition that the mobile device MD3 is connected with the mobile router MR3, the mobile router MR3 is connected with the access node AP3, the access node AP3 is located in the data network DN1, and the proxy router of the data network DN1 is PR1, if at least one index entry exists in the proxy router PR1, the name field value of the index entry is NA3, the mobile device MD3 obtains the data C3 through the following processes:
step 401: and starting.
Step 402: the mobile device MD3 sends a data acquisition message, where the name of the data acquisition message is NA3, the message type is 4, the identifier is 0, the source interface address set and the destination interface address set are null, and the load is null. After receiving the data acquisition message from the downstream interface, the mobile router MR3 forwards the data acquisition message from the upstream interface.
Step 403: after the access node AP3 receives the data get message, it looks at the request table, if there is a request table entry whose name field value is equal to the name of the received data get message, then step 427 is performed, otherwise step 404 is performed.
Step 404: the access node AP3 creates a request entry with a name field value equal to the name of the received data fetch message and a set of interface addresses equal to the set of source interface addresses of the received data fetch message. The access node AP3 looks at the data table and if there is a data table entry with a name field value equal to the name of the received data acquisition message, then step 405 is performed, otherwise step 409 is performed.
Step 405: the access node AP3 divides the data C3 into u3 data blocks, sets a variable u1, and sets an initial value of the variable u1 to 0.
Step 406: the access node AP3 increments the variable u1 by 1 and performs step 407 if u1 is less than u3, otherwise performs step 408.
Step 407: the access node AP3 creates a data response message with a name field equal to the name of the received data response message, a message type of 5, an identification field of 1, a source interface address set and a destination interface address set of null, and a load of u1 data blocks, and performs step 406.
Step 408: the access node AP3 creates a data response message with a name field equal to the name of the received data response message, a message type of 5, an identification field of 0, a source interface address set and a destination interface address set of null, and a payload of u1 data block, and performs step 427.
Step 409: the access node AP3 adds its geographical coordinates to the source interface address set of the received data response message, and the geographical coordinates are the first element of the source interface address set, and forwards the received data response message from the upstream interface.
Step 410: if the proxy router receives the data response message, step 420 is performed, and if the data router or the access node receives the data response message, step 411 is performed.
Step 411: the data router or the access node checks the request table after receiving the data response message, if there is a request table entry whose name field value is equal to the name of the received data response message, step 427 is executed, otherwise, step 412 is executed.
Step 412: the data router or the access node receiving the data response message creates a request table entry, the name field value of the request table entry is equal to the name of the received data response message, and the interface address set is equal to the source interface address set of the received data response message. The data router or access node looks at the data table and if there is a data entry with a name field value equal to the name of the received data response message, step 416 is performed, otherwise step 413 is performed.
Step 413: the data router or access node that received the data response message looks at the index table, and if there is one, the name field value of the index table is equal to the name of the received data response message, then step 414 is executed, otherwise step 415 is executed.
Step 414: the data router or access node receiving the data response message selects an index table having a name field value equal to the name of the received data response message, updates the destination interface address set of the data response message to an interface address set field value of the index table, selects an interface having an interface address equal to the first element of the destination interface address set of the data response message, adds the first element of the destination interface address set of the data response message to the source interface address set of the data response message as the first element of the source interface address set, deletes the first element from the destination interface address set of the data response message, sends the data response message from the selected interface, and performs step 410.
Step 415: the data router or access node receiving the data response message adds its own geographical coordinates to the source interface address set of the data response message and serves as the first element of the source interface address set, and sends the data response message from the upstream interface, and step 410 is executed.
Step 416: the data router or the access node that receives the data response message divides the data C3 into u3 data blocks, sets a variable u1, and the initial value of the variable u1 is 0.
Step 417: the data router or access node receiving the data response message increments the variable u1 by 1 and performs step 418 if u1 is less than u3 and otherwise performs step 419.
Step 418: the data router or the access node that receives the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is null, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 417 is executed.
Step 419: the data router or the access node receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is null, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 427 is executed.
Step 420: after receiving the data response message, the proxy router checks the request table, if there is a request table entry whose name field value is equal to the name of the received data response message, then step 427 is executed, otherwise step 421 is executed.
Step 421: the proxy router receiving the data response message creates a request table entry, the name field value of the request table entry is equal to the name of the received data response message, and the interface address set is equal to the source interface address set of the received data response message. The proxy router looks at the data table and if there is a data entry with a name field value equal to the name of the received data response message, then step 423 is performed, otherwise step 422 is performed.
Step 422: the proxy router receiving the data response message selects an index table having a name field value equal to the name of the received data response message, updates the destination interface address set of the data response message to an interface address set field value of the index table, selects an interface having an interface address equal to the first element of the destination interface address set of the data response message, adds the first element of the destination interface address set of the data response message to the source interface address set of the data response message as the first element of the source interface address set, deletes the first element from the destination interface address set of the data response message, sends the data response message from the selected interface, and performs step 410.
Step 423: the proxy router having received the data response message divides the data C3 into u3 data blocks, sets a variable u1, and the initial value of the variable u1 is 0.
Step 424: the data router receiving the data response message increments the variable u1 by 1, executes step 425 if u1 is less than u3, otherwise executes step 426.
Step 425: the data router receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 424 is executed.
Step 426: the data router receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block.
Step 427: the access node, the data router or the proxy router looks at the request table, selects all request table entries with the name domain value equal to the name of the data response message, and performs the following operations for each request table entry: updating the destination interface address set of the data response message to the interface address set of the request table entry, if the destination interface address set is empty, forwarding the data response message from a downstream interface, if the destination interface address set is not empty, selecting an interface, wherein the interface address of the interface is equal to the first element of the destination interface address set, deleting the first element from the destination interface address set, forwarding the data response message from the interface, if the identification domain value of the data response message is 0, deleting the request table entry, otherwise, keeping the request table entry. If the data response message destination interface address set field value is null, then step 428 is performed, otherwise step 427 is re-performed.
Step 428: after receiving the data response message, the mobile router MR3 forwards the data response message from the downstream interface. After receiving the data response message, mobile device MD3 saves the data in the data response message.
Step 429: and (6) ending.
In the above process, after the access node, the data router or the proxy router receives the message with the message type of 5, if the data in the message type is stored, the steps 301 to 311 are executed to create the index table.
Fig. 5 is a schematic diagram of a data acquisition process according to the present invention. Under the condition that the data C3 is identified by a name NA3, the mobile device MD4 is link-connected with the mobile router MR4, the mobile router MR4 is link-connected with the access node AP4, the access node AP4 is located in the data network DN2, and the proxy router of the data network DN2 is PR2, if the name domain value of any index entry of the proxy router PR2 is not equal to the name NA3, the mobile device MD4 obtains the data C3 by the following process:
step 501: and starting.
Step 502: the mobile device MD4 sends a data acquisition message, where the name of the data acquisition message is NA3, the message type is 4, the identifier is 0, the source interface address set and the destination interface address set are null, and the load is null. After receiving the data acquisition message from the downstream interface, the mobile router MR4 forwards the data acquisition message from the upstream interface.
Step 503: after the access node AP4 receives the data get message, it looks at the request table, if there is a request table entry whose name field value is equal to the name of the received data get message, then step 520 is executed, otherwise step 504 is executed.
Step 504: the access node AP4 creates a request entry with a name field value equal to the name of the received data fetch message and a set of interface addresses equal to the set of source interface addresses of the received data fetch message. The access node AP4 adds its geographical coordinates to the source interface address set of the received data acquisition message and forwards the received data acquisition message from the upstream interface as the first element of the source interface address set.
Step 505: and judging whether the proxy router or the data router receives the data acquisition message, if the proxy router receives the data acquisition message, executing the step 508, and if not, executing the step 506.
Step 506: after receiving the data acquisition message, the data router checks the request table, if a request table entry exists, and the name field value of the request table entry is equal to the name of the received data acquisition message, then step 520 is executed, otherwise step 507 is executed.
Step 507: the data router receiving the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message. The data router adds its own geographical coordinates to the source interface address set of the received data acquisition message, and the geographical coordinates are used as the first element of the source interface address set, forwards the received data acquisition message from the upstream interface, and executes step 505.
Step 508: after receiving the data acquisition message, the proxy router checks the request table, if there is a request table entry whose name field value is equal to the name of the received data acquisition message, then step 520 is executed, otherwise step 509 is executed.
Step 509: the proxy router receiving the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message. The proxy router adds the geographical coordinates of the proxy router to a source interface address set of the received data acquisition message, and forwards the received data acquisition message from an upstream interface by taking the geographical coordinates as a first element of the source interface address set.
Step 510: if the core router receives the data acquisition message, step 511 is performed, and if the proxy router, the data router or the access node receives the data acquisition message, step 513 is performed.
Step 511: after the core router receives the data acquisition message from an interface, the interface address of the interface is z1, the core router checks the request table, if there is a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, step 520 is executed, otherwise step 512 is executed.
Step 512: the core router that received the data fetch message from interface z1 creates a request entry with a name field value equal to the name of the received data fetch message and a set of interface addresses equal to the source interface address set of the received data fetch message. The core router adds interface address z1 to the source interface address set of the received data acquisition message with the interface address as the first element of the source interface address set, selects a forwarding entry with a geographic coordinate field value equal to the geographic coordinate in the name of the received data acquisition message, forwards the data acquisition message from the interface identified by the interface address of the forwarding entry, and performs step 510.
Step 513: the proxy router, data router or access node looks at the request table and if there is a request table entry whose name field value is equal to the name of the received data acquisition message, step 520 is performed, otherwise step 514 is performed.
Step 514: the proxy router, the data router or the access node which receives the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message. The proxy router, data router or access node looks at the data table and if there is a data table entry with a name field value equal to the name of the received data acquisition message, step 516 is performed, otherwise step 515 is performed.
Step 515: the proxy router, the data router or the access node that receives the data acquisition message selects an index table, the name field value of the index table is equal to the name of the received data acquisition message, the destination interface address set of the data acquisition message is updated to the interface address set field value of the index table, an interface is selected, the interface address of the interface is equal to the first element of the destination interface address set of the data acquisition message, the first element of the destination interface address set of the data acquisition message is added to the source interface address set of the data acquisition message and is used as the first element of the source interface address set, the first element is deleted from the destination interface address set of the data acquisition message, the data acquisition message is sent from the selected interface, and step 513 is executed.
Step 516: the proxy router, the data router, or the access node that receives the data acquisition message divides the data C3 into u3 data blocks, sets a variable u1, and sets an initial value of the variable u1 to 0.
517: the proxy router, data router or access node receiving the data acquisition message increments the variable u1 by 1, if u1 is less than u3, step 518 is performed, otherwise step 519 is performed.
Step 518: the proxy router, the data router or the access node which receives the data acquisition message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data block, and step 517 is executed.
Step 519: the proxy router, the data router or the access node which receives the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data blocks.
Step 520: the access node, the data router, the proxy router or the core router looks up the request table, selects all request table entries with the name field value equal to the name of the data response message, and for each request table entry, the core router, the access node, the data router or the proxy router performs the following operations: updating the destination interface address set of the data response message to the interface address set of the request table entry, if the destination interface address set is empty, forwarding the data response message from a downstream interface, if the destination interface address set is not empty, selecting an interface, wherein the interface address of the interface is equal to the first element of the destination interface address set, deleting the first element from the destination interface address set, forwarding the data response message from the interface, if the identification domain value of the data response message is 0, deleting the request table entry, otherwise, keeping the request table entry. If the data response message destination interface address set field value is null, step 521 is executed, otherwise step 520 is executed again.
Step 521: after receiving the data response message, the mobile router MR4 forwards the data response message from the downstream interface. After receiving the data response message, mobile device MD4 saves the data in the data response message.
Step 522: and (6) ending.
In the above process, after the access node, the data router or the proxy router receives the message with the message type of 5, if the data in the message type is stored, the steps 301 to 311 are executed to create the index table.
Example 1
Based on the simulation parameters in table 1, this embodiment simulates an efficient new-generation big data network implementation method in the present invention, and the performance analysis is as follows: when the amount of transmission data increases, the delay of data transmission increases, and when the amount of data transmission decreases, the delay of data transmission decreases, and the average delay of data acquisition is 2.5 s.
TABLE 1 simulation parameters
Figure GDA0002881747940000231
The present invention provides an efficient new generation big data network implementation method, and the method and the way for implementing the technical solution are many, the above description is only a preferred embodiment of the present invention, it should be noted that, for those skilled in the art, without departing from the principle of the present invention, several improvements and modifications may be made, and these improvements and modifications should also be regarded as the protection scope of the present invention. The components not specified in this embodiment can be implemented by the prior art.

Claims (5)

1. An efficient new generation big data network implementation method is characterized in that the network comprises a backbone network, a data network and a mobile network; the backbone network comprises more than two core routers, the data network comprises a proxy router, a data router and an access node, and the mobile network comprises one mobile router and more than two mobile devices;
a core router contains X1 wired interfaces, X1 is a positive integer greater than 1; a proxy router comprises an upstream wired interface and X2 downstream wired interfaces, a data router comprises an upstream wired interface and X2 downstream wired interfaces, and X2 is a positive integer greater than 1; an access node comprising an upstream wired interface and a downstream wireless interface, a mobile router comprising an upstream wireless interface and a downstream wireless interface; a mobile device comprising a wireless interface;
the upstream interface of the proxy router is connected with one interface of the core router, and each downstream interface of the proxy router is connected with the upstream interface of one data router; the upstream interface of a data router is connected with the downstream interface of a proxy router or a data router, and each downstream interface of the data router is connected with the upstream interfaces of other data routers or access nodes; the upstream interface of the access node is connected with the downstream interface of the data router, and the downstream interface of the access node is connected with the upstream interface link of the mobile router; the upstream interface of the mobile router is connected with a downstream interface link of an access node, and the downstream interface of the mobile router is connected with an interface link of the mobile equipment;
each core router, data router, proxy router and access node has unique geographic coordinates;
each interface of a core router is uniquely identified by an interface address, the interface address is equal to j, and j takes values from 1 to X1;
the upstream interface and each downstream interface of a proxy router are uniquely identified by an interface address, and the interface address comprises a geographic abscissa and a geographic ordinate; a data network is uniquely identified by an interface address of an upstream interface of a proxy router of the network;
the upstream interface and each downstream interface of a data router are respectively and uniquely identified by an interface address, the interface address is formed by geographical coordinates, and the geographical coordinates comprise a geographical abscissa and a geographical ordinate; the upstream interface and the downstream interface of one access node are both uniquely identified by an interface address, and the interface address is formed by geographic coordinates; the upstream interface and the downstream interface of a mobile router are both uniquely identified by an interface address, and the interface address is formed by geographical coordinates;
one kind of data is uniquely identified by a name, and one name is composed of geographical coordinates and a name ID; the mobile equipment realizes data communication through messages; one message consists of a name domain, a message type domain, a source interface address set domain, a destination interface address set domain, an identification domain and a load;
if one type of data has a length of m bits, a maximum length of a message payload is n bits, n and m are positive integers, m is greater than w1 xn, and w1 is a positive integer greater than 10, the data is divided into u data blocks and transmitted through u messages, as shown in equation (1); the length of the first u-1 data blocks is n, and the length of the last data block is m- (u-1) x n;
Figure FDA0002881747930000021
the message types are shown in the following table:
message type value Message name 1 Address configuration messages 2 Creating forwarding table messages 3 Data request message 4 Data acquisition messages 5 Data response message
The identification field of a message is only valid when the message type is 5, and the value of the identification field is 0 or 1; if the identification domain value is 0, the message load is the last data block of the type of data; if the identification domain value is 1, indicating that the message load is other data blocks except the last data block in the type of data;
if the coordinates of the access node are (x1, y1), after the access node is started, the access node sets the interface address of the upstream interface of the access node to (x1, y1), the interface address of the downstream interface to (x1+ b1, y1+ b1), b1 is a non-zero integer, and the access node periodically performs the following interface address configuration operations:
step 101: starting;
step 102: the access node sends an address configuration message from an upstream interface, the geographic coordinate of the name domain value of the address configuration message is (x1, y1), the name ID is 0, the identifier is 0, the message type is 1, the source interface address set and the destination interface address set are both empty, and the load is empty;
step 103: judging whether the proxy router or the data router receives the address configuration message, if the proxy router receives the address configuration message, executing step 105, otherwise executing step 104;
step 104: after receiving the address configuration message from the downstream interface, the data router sets the interface address of the downstream interface as the geographic coordinate in the name domain of the received address configuration message, and sets the interface address of the upstream interface as the geographic coordinate of the upstream interface; the data router sends an address configuration message from an upstream interface, the geographical coordinate of the name domain value of the address configuration message is the geographical coordinate of the address configuration message, the name ID is 0, the identifier is 0, the message type is 1, the source interface address set and the destination interface address set are both empty, the load is empty, and step 103 is executed;
step 105: after receiving the address configuration message from the downstream interface, the agent router sets the interface address of the downstream interface as the geographic coordinate in the name domain of the received address configuration message, and sets the interface address of the upstream interface as the geographic coordinate of the agent router;
step 106: and (6) ending.
2. An efficient new generation big data network implementation method as claimed in claim 1, wherein a mobile router sets the interface address of its upstream interface to its geographical coordinates (x2, y2), sets the interface address of its downstream interface to (x2+ b2, y2+ b2), and b2 is a non-zero integer; a mobile device sets the interface address of the interface of the mobile device as the geographical coordinate of the mobile device; each core router maintains a forwarding table, and each forwarding table item comprises a geographic coordinate, an interface address and a life cycle; after the agent router configures the interface address, the following operations are executed to create a forwarding table:
step 201: starting;
step 202: the proxy router sends a message for creating a forwarding table from an upstream interface, the geographical coordinate of the name domain value of the message for creating the forwarding table is the geographical coordinate of the proxy router, the name ID is 0, the identifier is 0, the message type is 2, the source interface address set and the destination interface address set are both empty, and the load is empty;
step 203: judging whether the proxy router or the core router receives the message for creating the forwarding table, if the proxy router receives the message for creating the forwarding table, executing the step 208, otherwise executing the step 204;
step 204: after the core router receives the message for creating the forwarding table from an interface, if the interface address of the interface is k, the core router checks the forwarding table, if a forwarding table entry exists, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table, and the interface address is equal to k, step 205 is executed, otherwise step 206 is executed;
step 205: the core router receiving the message for creating the forwarding table selects a forwarding table entry, the geographic coordinate of the forwarding table entry is equal to the geographic coordinate in the name of the received message for creating the forwarding table, the interface address is equal to k, the life cycle of the forwarding table entry is set to be the maximum value, and step 207 is executed;
step 206: the core router which receives the message for creating the forwarding table creates a forwarding table item, the geographic coordinate of the forwarding table item is equal to the geographic coordinate in the name of the received message for creating the forwarding table, the interface address is equal to k, and the life cycle is set to be the maximum value;
step 207: the core router receiving the message for creating the forwarding table forwards the received message for creating the forwarding table from all interfaces except the interface k, and executes step 203;
step 208: the proxy router which receives the message for creating the forwarding table discards the message for creating the forwarding table;
step 209: and (6) ending.
3. The method of claim 2, wherein each proxy router, data router or access node maintains a data table, and each data table is composed of a data field, a name field and a life cycle field; each agent router, data router or access node maintains an index table, each index table is composed of an interface address set domain, a name domain and a life cycle domain;
if the data C3 consists of the name NA3, a proxy router saves the data C3 by creating a data table entry in which the data value is data C3, the name field value is name NA3, and the lifetime is maximum; meanwhile, the proxy router creates an index table entry, the interface address set of the index table entry is null, the name domain value is NA3, and the life cycle is the maximum value; the data router or access node then saves the data C3 by performing the following process:
step 301: starting;
step 302: the data router or the access node creates a data table entry, wherein in the data table entry, the data value is data C3, the name domain value is name NA3, and the life cycle is the maximum value; meanwhile, the data router or the access node creates an index table entry, the interface address set of the index table entry is null, the name domain value is NA3, and the life cycle is the maximum value; the data router or the access node sends a data request message through an upstream interface, in the data request message, the geographic coordinate of the name domain value is the geographic coordinate of the data router or the access node, the name ID is 0, the message type is 3, the identifier is 0, and the source interface address set is formed by the geographic coordinate of the data router or the access node; the destination interface address set is empty and the load is empty;
step 303: judging whether the proxy router or the data router receives the data request message, if the proxy router receives the data request message, executing step 308, otherwise executing step 304;
step 304: after receiving the data request message, the data router checks an index table, if an index table entry exists, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, and the name domain value is equal to the name of the received data request message, then step 305 is executed, otherwise step 306 is executed;
step 305: the data router receiving the data request message selects an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, and the name domain value is equal to the name of the received data request message, the life cycle of the forwarding table entry is set to be the maximum value, and step 307 is executed;
step 306: the data router receiving the data request message creates an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, the name domain value is equal to the name of the received data request message, and the life cycle of the forwarding table entry is set to be the maximum value;
step 307: the data router receiving the data request message adds the geographical coordinates of itself to the source interface address set of the received data request message, the geographical coordinates serve as a first element of the source interface address set, the received data request message is forwarded from the upstream interface, and step 303 is executed;
step 308: after receiving the data request message, the proxy router checks an index table, if an index table entry exists, the interface address set field value of the index table entry is equal to the source interface address set field value of the received data request message, and the name field value is equal to the name of the received data request message, then step 309 is executed, otherwise step 310 is executed;
step 309: the proxy router receiving the data request message selects an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, and the name domain value is equal to the name of the received data request message, the life cycle of the forwarding table entry is set to be the maximum value, and step 311 is executed;
step 310: the agent router receiving the data request message creates an index table entry, the interface address set domain value of the index table entry is equal to the source interface address set domain value of the received data request message, the name domain value is equal to the name of the received data request message, and the life cycle of the forwarding table entry is set to be the maximum value;
step 311: and (6) ending.
4. An efficient new generation big data network implementation method as claimed in claim 3, wherein if the data C3 is uniquely identified by name NA3, the name NA3 is composed of geographical coordinates (x3, y3) and name ID NID3, the data C3 has a length of m3 bits, the maximum length of a message payload is n bits, n and m3 are positive integers, and m3 is greater than w1 xn, the data is divided into u3 data blocks and transmitted through u3 messages, as shown in formula (2), the first u3-1 data blocks have a length of n, and the last data block has a length of m3- (u3-1) xn;
Figure FDA0002881747930000051
each data router, agent router or access node respectively stores a request table, and each request table comprises a name domain and an interface address set domain;
under the condition that the mobile device MD3 is connected with the mobile router MR3, the mobile router MR3 is connected with the access node AP3, the access node AP3 is located in the data network DN1, and the proxy router of the data network DN1 is PR1, if at least one index entry exists in the proxy router PR1, the name field value of the index entry is NA3, the mobile device MD3 obtains the data C3 through the following processes:
step 401: starting;
step 402: the mobile device MD3 sends a data acquisition message, wherein the name of the data acquisition message is NA3, the type of the message is 4, the identifier is 0, the source interface address set and the destination interface address set are empty, and the load is empty; after receiving the data acquisition message from the downstream interface, the mobile router MR3 forwards the data acquisition message from the upstream interface;
step 403: after receiving the data acquisition message, the access node AP3 checks the request table, if there is a request table entry whose name field value is equal to the name of the received data acquisition message, then step 427 is executed, otherwise step 404 is executed;
step 404: the access node AP3 creates a request entry with a name field value equal to the name of the received data acquisition message and an interface address set equal to the source interface address set of the received data acquisition message; the access node AP3 looks up the data table, if there is a data table entry whose name field value is equal to the name of the received data acquisition message, then step 405 is executed, otherwise step 409 is executed;
step 405: the access node AP3 divides the data C3 into u3 data blocks, and sets a variable u1, wherein the initial value of the variable u1 is 0;
step 406: the access node AP3 increments the variable u1 by 1, if u1 is less than u3, then step 407 is performed, otherwise step 408 is performed;
step 407: the access node AP3 creates a data response message, the name field value of which is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set and the destination interface address set are empty, and the load is the u1 th data block, and performs step 406;
step 408: the access node AP3 creates a data response message, the name field value of which is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the source interface address set and the destination interface address set are empty, and the load is the u1 th data block, and performs step 427;
step 409: the access node AP3 adds its own geographical coordinates to the source interface address set of the received data response message, and the geographical coordinates are used as the first element of the source interface address set, and forwards the received data response message from the upstream interface;
step 410: if the proxy router receives the data response message, executing step 420, and if the data router or the access node receives the data response message, executing step 411;
step 411: the data router or the access node checks the request table after receiving the data response message, if a request table entry exists, the name field value of the request table entry is equal to the name of the received data response message, step 427 is executed, otherwise step 412 is executed;
step 412: the data router or the access node which receives the data response message creates a request table entry, the name field value of the request table entry is equal to the name of the received data response message, and the interface address set is equal to the source interface address set of the received data response message; the data router or the access node checks the data table, if there is a data table entry whose name field value is equal to the name of the received data response message, then go to step 416, otherwise go to step 413;
step 413: the data router or the access node receiving the data response message checks the index table, if an index table exists, the name field value of the index table is equal to the name of the received data response message, step 414 is executed, otherwise step 415 is executed;
step 414: selecting an index table by the data router or the access node which receives the data response message, wherein the name field value of the index table is equal to the name of the received data response message, updating the destination interface address set of the data response message into the interface address set field value of the index table, selecting an interface, wherein the interface address of the interface is equal to the first element of the destination interface address set of the data response message, adding the first element of the destination interface address set of the data response message into the source interface address set of the data response message to be used as the first element of the source interface address set, deleting the first element from the destination interface address set of the data response message, sending the data response message from the selected interface, and executing step 410;
step 415: the data router or the access node receiving the data response message adds the geographical coordinates of the data router or the access node to the source interface address set of the data response message and uses the geographical coordinates as a first element of the source interface address set, the data response message is sent from the upstream interface, and step 410 is executed;
step 416: the data router or the access node which receives the data response message divides the data C3 into u3 data blocks, and sets a variable u1, wherein the initial value of the variable u1 is 0;
step 417: the data router or access node receiving the data response message increments the variable u1 by 1, if u1 is less than u3, performs step 418, otherwise performs step 419;
step 418: the data router or the access node receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 417 is executed;
step 419: the data router or the access node receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is null, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 427 is executed;
step 420: after receiving the data response message, the proxy router checks the request table, if a request table entry exists, the name field value of the request table entry is equal to the name of the received data response message, then step 427 is executed, otherwise step 421 is executed;
step 421: the proxy router receiving the data response message creates a request table entry, the name field value of the request table entry is equal to the name of the received data response message, and the interface address set is equal to the source interface address set of the received data response message; the proxy router checks the data table, if a data table entry exists, the name field value of the data table entry is equal to the name of the received data response message, step 423 is executed, otherwise, step 422 is executed;
step 422: selecting an index table by the proxy router receiving the data response message, wherein the name field value of the index table is equal to the name of the received data response message, updating the destination interface address set of the data response message to the interface address set field value of the index table, selecting an interface, wherein the interface address of the interface is equal to the first element of the destination interface address set of the data response message, adding the first element of the destination interface address set of the data response message to the source interface address set of the data response message and using the first element as the first element of the source interface address set, deleting the first element from the destination interface address set of the data response message, sending the data response message from the selected interface, and executing step 410;
step 423: the proxy router receiving the data response message divides the data C3 into u3 data blocks, sets a variable u1, and sets an initial value of the variable u1 to 0;
step 424: the data router receiving the data response message increments the variable u1 by 1, if u1 is less than u3, performs step 425, otherwise performs step 426;
step 425: the data router receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 th data block, and step 424 is executed;
step 426: the data router receiving the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data blocks;
step 427: the access node, the data router or the proxy router looks at the request table, selects all request table entries with the name domain value equal to the name of the data response message, and performs the following operations for each request table entry: updating a destination interface address set of the data response message to an interface address set of the request table entry, if the destination interface address set is empty, forwarding the data response message from a downstream interface, if the destination interface address set is not empty, selecting an interface, wherein an interface address of the interface is equal to a first element of the destination interface address set, deleting the first element from the destination interface address set, forwarding the data response message from the interface, if an identification field value of the data response message is 0, deleting the request table entry, otherwise, keeping the request table entry; if the data response message destination interface address set field value is null, go to step 428, otherwise go to step 427 again;
step 428: after receiving the data response message, the mobile router MR3 forwards the data response message from the downstream interface; after receiving the data response message, the mobile device MD3 saves the data in the data response message;
step 429: finishing;
in the above process, after the access node, the data router or the proxy router receives the message with the message type of 5, if the data in the message type is stored, the steps 301 to 311 are executed to create the index table.
5. The method as claimed in claim 4, wherein, in the condition that the data C3 is identified by name NA3, the mobile device MD4 is connected to the mobile router MR4, the mobile router MR4 is connected to the access node AP4, the access node AP4 is located in the data network DN2, and the proxy router of the data network DN2 is PR2, if the name domain value of any index entry of the proxy router PR2 is not equal to NA3, the mobile device MD4 obtains the data C3 by:
step 501: starting;
step 502: the mobile device MD4 sends a data acquisition message, wherein the name of the data acquisition message is NA3, the type of the message is 4, the identifier is 0, the source interface address set and the destination interface address set are empty, and the load is empty; after receiving the data acquisition message from the downstream interface, the mobile router MR4 forwards the data acquisition message from the upstream interface;
step 503: after receiving the data acquisition message, the access node AP4 checks the request table, if there is a request table entry whose name field value is equal to the name of the received data acquisition message, then step 520 is executed, otherwise step 504 is executed;
step 504: the access node AP4 creates a request entry with a name field value equal to the name of the received data acquisition message and an interface address set equal to the source interface address set of the received data acquisition message; the access node AP4 adds its own geographical coordinates to the source interface address set of the received data acquisition message, and the geographical coordinates are used as the first element of the source interface address set, and forwards the received data acquisition message from the upstream interface;
step 505: judging whether the proxy router or the data router receives the data acquisition message, if the proxy router receives the data acquisition message, executing step 508, otherwise executing step 506;
step 506: after receiving the data acquisition message, the data router checks the request table, if a request table entry exists, the name field value of the request table entry is equal to the name of the received data acquisition message, step 520 is executed, otherwise step 507 is executed;
step 507: the data router receiving the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message; the data router adds its own geographical coordinates into the source interface address set of the received data acquisition message, and the geographical coordinates are used as the first element of the source interface address set, forwards the received data acquisition message from the upstream interface, and executes step 505;
step 508: after receiving the data acquisition message, the proxy router checks the request table, if a request table entry exists, and the name field value of the request table entry is equal to the name of the received data acquisition message, then step 520 is executed, otherwise step 509 is executed;
step 509: the proxy router receiving the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message; the proxy router adds the geographical coordinates of the proxy router into a source interface address set of the received data acquisition message, the geographical coordinates serve as a first element of the source interface address set, and the received data acquisition message is forwarded from an upstream interface;
step 510: if the core router receives the data acquisition message, executing step 511, if the proxy router, the data router or the access node receives the data acquisition message, executing step 513;
step 511: after the core router receives the data acquisition message from an interface, the interface address of the interface is z1, look up the request table, if there is a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, execute step 520, otherwise execute step 512;
step 512: the core router receiving the data acquisition message from interface z1 creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message; the core router adds an interface address z1 to the source interface address set of the received data acquisition message, and the interface address is used as the first element of the source interface address set, selects a forwarding table entry, the geographic coordinate domain value of the forwarding table entry is equal to the geographic coordinate in the name of the received data acquisition message, forwards the data acquisition message from the interface identified by the interface address of the forwarding table entry, and executes step 510;
step 513: the agent router, the data router or the access node checks the request table, if a request table entry exists, the name field value of the request table entry is equal to the name of the received data acquisition message, step 520 is executed, otherwise step 514 is executed;
step 514: the proxy router, the data router or the access node which receives the data acquisition message creates a request table entry, the name field value of the request table entry is equal to the name of the received data acquisition message, and the interface address set is equal to the source interface address set of the received data acquisition message; the proxy router, the data router or the access node checks a data table, if a data table entry exists, the name field value of the data table entry is equal to the name of the received data acquisition message, step 516 is executed, otherwise, step 515 is executed;
step 515: selecting an index table by the proxy router, the data router or the access node which receives the data acquisition message, wherein the name field value of the index table is equal to the name of the received data acquisition message, updating the destination interface address set of the data acquisition message into the interface address set field value of the index table, selecting an interface, the interface address of which is equal to the first element of the destination interface address set of the data acquisition message, adding the first element of the destination interface address set of the data acquisition message into the source interface address set of the data acquisition message to be used as the first element of the source interface address set, deleting the first element from the destination interface address set of the data acquisition message, sending the data acquisition message from the selected interface, and executing step 513;
step 516: the proxy router, the data router or the access node which receives the data acquisition message divides the data C3 into u3 data blocks, sets a variable u1, and sets an initial value of the variable u1 to 0;
517: the proxy router, data router or access node receiving the data acquisition message increments the variable u1 by 1, if u1 is less than u3, performs step 518, otherwise performs step 519;
step 518: the proxy router, the data router or the access node which receives the data acquisition message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 1, the source interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data blocks, and step 517 is executed;
step 519: the proxy router, the data router or the access node which receives the data response message creates a data response message, the name field value of the data response message is equal to the name of the received data response message, the message type is 5, the identification field value is 0, the interface address set is empty, the destination interface address set is the source interface address set of the received data response message, and the load is the u1 data blocks;
step 520: the access node, the data router, the proxy router or the core router looks up the request table, selects all request table entries with the name field value equal to the name of the data response message, and for each request table entry, the core router, the access node, the data router or the proxy router performs the following operations: updating a destination interface address set of the data response message to an interface address set of the request table entry, if the destination interface address set is empty, forwarding the data response message from a downstream interface, if the destination interface address set is not empty, selecting an interface, wherein an interface address of the interface is equal to a first element of the destination interface address set, deleting the first element from the destination interface address set, forwarding the data response message from the interface, if an identification field value of the data response message is 0, deleting the request table entry, otherwise, keeping the request table entry; if the data response message destination interface address set field value is null, executing step 521, otherwise, executing step 520 again;
step 521: after receiving the data response message, the mobile router MR4 forwards the data response message from the downstream interface; after receiving the data response message, the mobile device MD4 saves the data in the data response message;
step 522: finishing;
in the above process, after the access node, the data router or the proxy router receives the message with the message type of 5, if the data in the message type is stored, the steps 301 to 311 are executed to create the index table.
CN201810235148.1A 2018-03-21 2018-03-21 High-efficiency new-generation big data network implementation method Active CN108494595B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810235148.1A CN108494595B (en) 2018-03-21 2018-03-21 High-efficiency new-generation big data network implementation method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810235148.1A CN108494595B (en) 2018-03-21 2018-03-21 High-efficiency new-generation big data network implementation method

Publications (2)

Publication Number Publication Date
CN108494595A CN108494595A (en) 2018-09-04
CN108494595B true CN108494595B (en) 2021-03-26

Family

ID=63318932

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810235148.1A Active CN108494595B (en) 2018-03-21 2018-03-21 High-efficiency new-generation big data network implementation method

Country Status (1)

Country Link
CN (1) CN108494595B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109218021B (en) * 2018-10-24 2021-02-05 常熟理工学院 Safe new-generation Internet of things data communication method
CN109768893B (en) * 2019-03-04 2021-06-18 常熟理工学院 High-efficiency big data network data communication implementation method

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103108308A (en) * 2011-11-15 2013-05-15 中兴通讯股份有限公司 Method, network element and user end for achieving identity location separation and distribution interface identification

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8099104B2 (en) * 2004-02-26 2012-01-17 Telcordia Licensing Company Llc Location based services for integrated cellular and LAN networks
CN103096299B (en) * 2011-11-01 2017-09-15 中兴通讯股份有限公司 The method and LISP networks of a kind of mobile node dynamic access station location marker
CN106507428B (en) * 2016-10-19 2019-05-07 常熟理工学院 A kind of data communications method of future mobile network
CN106792978B (en) * 2017-03-29 2021-03-16 常熟理工学院 Cloud-based intelligent Internet of vehicles data communication method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103108308A (en) * 2011-11-15 2013-05-15 中兴通讯股份有限公司 Method, network element and user end for achieving identity location separation and distribution interface identification

Also Published As

Publication number Publication date
CN108494595A (en) 2018-09-04

Similar Documents

Publication Publication Date Title
CN110113264B (en) Method for realizing cache and route of named data network
CN109088778B (en) Data communication implementation method for future mobile network
CN109246785B (en) Method for realizing future mobile network
CN109150723B (en) Routing communication implementation method of Internet of things
CN104243630A (en) MAC (media access control) address learning method and MAC address learning device in VXLAN (virtual extensible local area network)
CN109462549B (en) Method for implementing new generation wireless mobile network
CN110138663B (en) Method for implementing new generation network using data as center
CN109005567B (en) Mobile network implementation method based on cluster
CN102014039B (en) Data transmission method and access point
CN108494595B (en) High-efficiency new-generation big data network implementation method
CN110233889B (en) Network data communication implementation method based on cache mechanism
CN111245725B (en) Future network implementation method based on distribution
CN109768893B (en) High-efficiency big data network data communication implementation method
CN104717640A (en) Realization method for wireless network communication based on positioning
CN109089293B (en) Route communication realization method for future mobile network
CN107949000B (en) Low-delay opportunistic network implementation method
CN108696838B (en) Vehicle-mounted data routing method based on position information
CN108055204B (en) Big data network communication implementation method
CN111277497A (en) Method for realizing network service deployment and discovery based on distribution
CN101022419A (en) Path maximum transmission unit item establishing method and message transmitting method and device
CN110380971B (en) Network data communication method based on buffer mechanism
CN107948342B (en) Big data network implementation method
CN108965138B (en) Method for implementing new generation multimedia sensor network
CN108770030B (en) Data communication method of next generation wireless network
CN109039901B (en) High-efficiency data network routing implementation method

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
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20220406

Address after: 230000 room 1414, building D, Yinhe happiness Plaza, intersection of Luzhou Avenue and Fuzhou Road, Baohe District, Hefei City, Anhui Province

Patentee after: Hefei keyiguo Information Technology Co.,Ltd.

Address before: 215500 School of computer science and engineering, Changshu Institute of Technology (southeast campus), Changshu City, Suzhou City, Jiangsu Province

Patentee before: CHANGSHU INSTITUTE OF TECHNOLOGY

Effective date of registration: 20220406

Address after: 222000 room 13016, No. 201, sunshine free trade building, Lianyungang District, Lianyungang Area, China (Jiangsu) pilot Free Trade Zone, Lianyungang City, Jiangsu Province

Patentee after: Lianyungang Yunqiao Information Technology Co.,Ltd.

Address before: 230000 room 1414, building D, Yinhe happiness Plaza, intersection of Luzhou Avenue and Fuzhou Road, Baohe District, Hefei City, Anhui Province

Patentee before: Hefei keyiguo Information Technology Co.,Ltd.

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20231222

Address after: 233600 Star Garden Incubator in the Optoelectronics Standardization Plant, Economic Development Zone, Guoyang County, Bozhou City, Anhui Province

Patentee after: Daoji Intelligence (Anhui) Information Technology Co.,Ltd.

Address before: 222000 room 13016, No. 201, sunshine free trade building, Lianyungang District, Lianyungang Area, China (Jiangsu) pilot Free Trade Zone, Lianyungang City, Jiangsu Province

Patentee before: Lianyungang Yunqiao Information Technology Co.,Ltd.