CN108462623B

CN108462623B - High-efficiency data center network implementation method

Info

Publication number: CN108462623B
Application number: CN201810235916.3A
Authority: CN
Inventors: 王晓喃
Original assignee: Changshu Institute of Technology
Current assignee: Changshu Institute of Technology
Priority date: 2018-03-21
Filing date: 2018-03-21
Publication date: 2020-07-07
Anticipated expiration: 2038-03-21
Also published as: CN108462623A

Abstract

The invention provides a high-efficiency data center network implementation method, wherein the network comprises a data backbone network, more than two data subnets and more than two access subnets; a data backbone network comprising controllers and core routers, each controller and core router having unique geographic coordinates; a core router has R1 interfaces, R1 is an integer greater than 1, a controller has an interface, the interface of the controller is connected with the interface of the core router; each node in the data center network can acquire data rapidly through the network implementation method provided by the invention, so that the service performance is greatly improved. 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 data center network implementation method

Technical Field

The invention relates to an implementation method, in particular to an efficient data center network implementation method.

Background

Communication between nodes in the data center network is realized through forwarding and routing of intermediate nodes, and therefore, one of key technologies to be solved for realizing the data center network is to reduce data transmission delay so as to enable users to quickly acquire network services. With the development of network technology, data center networks will become a mode for providing services in the future.

At present, the implementation mode of the data center 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 data center 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 data center network implementation method aiming at the defects of the prior art.

The technical scheme is as follows: the invention discloses a high-efficiency data center network implementation method, wherein the network comprises a data backbone network, more than two data subnets and more than two access subnets; a data backbone network comprising controllers and core routers, each controller and core router having unique geographic coordinates; a core router has R1 interfaces, R1 is an integer greater than 1, a controller has an interface, the interface of the controller is connected with the interface of the core router;

a data subnet comprises data routers and servers, wherein each data router comprises an upstream interface and R2 downstream interfaces, and R2 is an integer greater than 1; the server comprises an interface which is connected with a downstream interface of the data server; the upstream interface of only one data router in the data subnet is connected with one interface of the core router, and the data router is called as a main data router; each data router has unique geographic coordinates;

an access subnetwork comprises an access router, an access node and a mobile node, wherein the access router is provided with an upstream interface and R3 downstream interfaces, and R3 is an integer greater than 1; a mobile node having a wireless interface; an access node having an upstream interface coupled to a downstream interface of an access router and a downstream radio interface coupled to the radio interface link of the mobile node; the upstream interface of only one access router in the access sub-network is connected with one interface of the core router, and the access router is called as a main access router; each access router and access node has unique geographic coordinates;

the core router, the data router, the access router and the access node are collectively called communication equipment; each upstream interface or downstream interface of a communication device is uniquely identified by an interface ID; if a communication device has R4 downstream interfaces and an upstream interface, the interface ID of each downstream interface is j4, j4 takes values from 1 to R4, and the interface ID of each upstream interface is R4+ 1;

the interface IDs of the controller, the server and the mobile node are all 1;

a data is uniquely identified by a name; the mobile nodes communicate through messages, and one message comprises a name domain, a geographic coordinate domain, a message type domain, a source interface ID set, a destination interface ID set and a load;

message types are shown in the following table

Message type value	Message name
		1	Publishing messages
2	Data router issuing messages
		3	Server publishing messages
4	Information request message
		5	Information response message
6	Data request message
		7	Data response message

The core router, the main data router, the main access router and the controller jointly maintain a controller table, and one controller table is composed of a geographic coordinate, an interface ID set and a life cycle domain;

after a controller is started, the following operations are periodically executed to establish or update a controller table:

step 101: starting;

step 102: the controller sends a release message, wherein the name domain value in the release message is null, the geographic coordinate domain value is equal to the coordinate of the controller, the message type is 1, the source interface ID set and the destination interface ID set are both null, and the load is null;

step 103: judging whether the core router receives the release message, if so, executing step 104, otherwise, executing step 108;

step 104: after receiving a publish message from an interface f1 of a core router, adding an interface f1 into a source interface ID set of the publish message, and taking the interface f1 as a first element of the source interface ID set; the core router checks the controller table, if a controller table entry exists, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the release message, and the interface ID set is equal to the source interface ID set of the release message, step 105 is executed, otherwise step 106 is executed;

step 105: selecting a controller table entry from the core router receiving the publish message from the interface f1, where the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the publish message, and the interface ID set is equal to the source interface ID set of the publish message, setting the lifetime of the controller table entry to the maximum value, and executing step 107;

step 106: the core router receiving the release message from the interface f1 creates a controller table entry, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the release message, the interface ID set is equal to the source interface ID set of the release message, and the life cycle is set to the maximum value;

step 107: the core router that received the publish message from interface f1 forwards the publish message from each interface other than interface f1, performing step 103;

step 108: after the master data router, the master access router or the controller receives the publish message from the interface e1, adding the interface e1 into the source interface ID set of the publish message, and using the interface e1 as the first element of the source interface ID set; e1 is a variable in which the interface value is saved; the master data router, the master access router or the controller checks the controller table, if a controller table entry exists, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the release message, and the interface ID set is equal to the source interface ID set of the release message, the life cycle of the controller table entry is set to be the maximum value; otherwise, the master data router receiving the release message from the interface e1, the master access router or the controller creating a controller table entry, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the release message, the interface ID set is equal to the source interface ID set of the release message, and the life cycle is set to the maximum value;

step 109: and (6) ending.

The above process enables the controller table to be established or updated to achieve proper communication of data.

In the method, a core router, a main data router, a main access router and a controller jointly maintain a main data router table, and one main data router table item consists of a geographical coordinate, an interface ID set and a life cycle domain;

after a main data router is started, the following operations are periodically executed to establish or update a main data router table:

step 201: starting;

step 202: the main data router sends a data router release message, wherein in the data router release message, a name field value is null, a geographic coordinate field value is equal to the geographic coordinate of the main data router, the message type is 2, a source interface ID set and a destination interface ID set are both null, and the load is null;

step 203: judging whether the core router receives the data router publishing message, if so, executing the step 204, otherwise, executing the step 208;

step 204: after receiving a data router publishing message from an interface a1 of a core router, adding an interface a1 into a source interface ID set of the data router publishing message, and taking the interface a1 as a first element of the source interface ID set; the core router checks the main data router table, if a main data router table item exists, the geographic coordinate domain value of the table item is equal to the geographic coordinate in the message issued by the data router, and the interface ID set is equal to the source interface ID set of the message issued by the data router, step 205 is executed, otherwise step 206 is executed;

step 205: selecting a main data router table entry by a core router which receives a data router release message from an interface a1, setting the life cycle of the main data router table entry as the maximum value, wherein the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the data router release message, and the interface ID set is equal to the source interface ID set of the data router release message;

step 206: the core router receiving the data router release message from the interface a1 creates a main data router table entry, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the data router release message, the interface ID set is equal to the source interface ID set of the data router release message, and the life cycle is set to be the maximum value;

step 207: the core router, which receives the data router advertisement message from the interface a1, forwards the data router advertisement message from each interface except the interface a1, and performs step 203;

step 208: after receiving the data router publishing message from the interface a2, the master access router or the controller adds the interface a2 to the data router publishing message source interface ID set, and uses the interface a2 as the first element of the source interface ID set; a2 is a variable in which the interface value is saved; the main data router, the main access router or the controller checks the main data router table, if one main data router table item exists, the geographic coordinate domain value of the table item is equal to the geographic coordinate in the message issued by the data router, and the interface ID set is equal to the source interface ID set of the message issued by the data router, the life cycle of the main data router table item is set to be the maximum value; otherwise, the master data router receiving the data router publishing message from the interface a2, the master access router or the controller creating a master data router table entry, the geographic coordinate domain value of the table entry being equal to the geographic coordinate in the data router publishing message, the interface ID set being equal to the source interface ID set of the data router publishing message, the life cycle being set to the maximum value;

step 209: and (6) ending.

The above process enables the creation or updating of a master data router table to achieve proper communication of data.

In the method, each main data router and each controller jointly maintain a server table, and one server table item comprises a name domain, a geographic coordinate domain, an interface ID set and a life cycle domain; the data C1 is uniquely identified by a name NA1, and if the server holds the data C1, the following procedure is performed to build or update a server table:

step 301: starting;

step 302: a server sends a server release message, wherein in the server release message, a name domain value is name NA1, a geographic coordinate domain value is equal to a geographic coordinate of the server, the message type is 3, a source interface ID set and a destination interface ID set are both empty, and the load is empty;

step 303: judging whether the main data router or the data router receives the server publishing message, if the main data router receives the server publishing message, executing the step 305, otherwise executing the step 304;

step 304: after receiving a server publishing message from an interface f2 of a data router, adding an interface f2 into a source interface ID set of the server publishing message, and taking the interface f2 as a first element of the source interface ID set; the data router forwards the server publishing message from the upstream interface, and step 303 is executed;

step 305: after receiving a server publishing message from an interface f3 of a master data router, adding an interface f3 into a source interface ID set of the server publishing message, and taking the interface f3 as a first element of the source interface ID set; the main data server checks a server table, if a server table entry exists, the name domain value of the table entry is equal to the name of the message issued by the server, the geographic coordinate domain value is equal to the geographic coordinate in the message issued by the server, and the interface ID set is equal to the source interface ID set of the message issued by the server, the life cycle of the server table entry is set to be the maximum value; otherwise, the master data router receiving the server publishing message from the interface f3 creates a server table entry, the name domain value of the server table entry is equal to the name in the server publishing message, the geographic coordinate domain value is equal to the geographic coordinate in the server publishing message, the interface ID set is equal to the source interface ID set of the server publishing message, and the life cycle is set to the maximum value;

step 306: the master data router receiving the server publish message from interface f3 looks at the controller table and performs the following for each controller table entry in the controller table: the main data router updates the geographical coordinates of the received server release message into the geographical coordinates of the main data router, sets a source interface ID set to be null, sets a load to be null, sets a destination interface ID set to be an interface ID set of the controller list item, selects an interface, the interface ID of the interface is equal to the first element in the destination interface ID set, deletes the first element from the destination interface ID set, and sends the server release message from the selected interface;

step 307: judging whether the controller or the core router receives the server publishing message, if the core router receives the server publishing message, executing step 308, otherwise executing step 309;

step 308: after receiving a server publishing message from an interface f5 of a core router, adding an interface f5 into a source interface ID set of the server publishing message, and taking the interface f5 as a first element of the source interface ID set; selecting an interface by the core router, wherein the interface ID of the interface is equal to the first element in the destination interface ID set, deleting the first element from the destination interface ID set, sending the server issuing message from the selected interface, and executing step 307;

step 309: after the controller receives a server publishing message from an interface e2 of the controller, adding an interface e2 into a source interface ID set of the server publishing message, and taking the interface e2 as a first element of the source interface ID set; the controller checks the server table, if a server table entry exists, the name domain value of the table entry is equal to the name of the received server release message, the geographic coordinate domain value is equal to the geographic coordinate in the server release message, and the interface ID set is equal to the source interface ID set of the server release message, the life cycle of the server table entry is set to be the maximum value; otherwise, the controller creates a server table entry, the name domain value of the table entry is equal to the name in the received server release message, the geographic coordinate domain value is equal to the geographic coordinate in the server release message, the interface ID set is equal to the source interface ID set of the server release message, and the life cycle is set to be the maximum value;

step 310: and (6) ending.

The above process enables the establishment or updating of server tables to achieve proper communication of data.

In the method of the invention, if the data C1 is uniquely identified by the name NA1, the mobile node MN1 obtains the server information of the stored data C1 which is closest to the mobile node MN through the following processes:

step 401: starting;

step 402: the mobile node MN1 sends an information request message, the name domain value of the information request message is NA1, the message type is 4, and the geographic coordinates are that the current geographic coordinates, the source interface ID set and the destination interface ID set of the mobile node MN1 are all empty, and the load is empty;

step 403: judging whether the main access router or the access router receives the information request message, if the main access router receives the information request message, executing the step 405, otherwise executing the step 404;

step 404: after receiving the information request message from the interface b2 of the access router, adding the interface b2 into the source interface ID set of the information request message, and taking the interface b2 as the first element of the source interface ID set; the access router forwards the information request message from the upstream interface, and executes step 403;

step 405: after receiving the information request message from the interface b3 of the master access router, adding the interface b3 into the source interface ID set of the information request message, and taking the interface b3 as the first element of the source interface ID set; the main access router checks a controller table, selects a controller table entry, the geographical coordinate of the table entry is closest to the geographical coordinate in the received information request message, a destination interface ID set in the information request message is updated to an interface ID set of the controller table entry, the main access router selects an interface, the interface ID of the interface is equal to a first element in the destination interface ID set, the first element is deleted from the destination interface ID set, and the information request message is sent from the selected interface;

step 406: judging whether the core router or the controller receives the information request message, if the core router receives the information request message, executing step 407, otherwise executing step 408;

step 407: after receiving the information request message from the interface b4 of the core router, adding the interface b4 into the source interface ID set of the information request message, and taking the interface b4 as the first element of the source interface ID set; selecting an interface by the core router, wherein the interface ID of the interface is equal to the first element in the destination interface ID set, deleting the first element from the destination interface ID set, sending the information request message from the selected interface, and executing step 406;

step 408: after receiving the information request message from the own interface e3, the controller adds the interface e3 into the source interface ID set of the information request message, and takes the interface e3 as the first element of the source interface ID set; the controller checks the server table and selects a server table entry, the name of the table entry is equal to the name of the information request message, and the geographic coordinate is closest to the geographic coordinate in the information request message; the controller creates an information response message, the name of the information response message is equal to the name in the received information request message, the geographic coordinate is equal to the geographic coordinate in the received information request message, the message type is 5, the source interface ID set is empty, the destination interface ID set is equal to the source interface ID set in the received information request message, and the load is the selected server table item; the controller selects an interface having an interface ID equal to a first element in the destination interface ID set, deletes the first element from the destination interface ID set, and transmits the information response message from the selected interface;

step 409: judging whether the mobile node MN1 or the communication equipment receives the information response message, if the mobile node MN1 receives the information response message, executing the step 411, otherwise executing the step 410;

step 410: the communication device selects an interface whose interface ID is equal to the first element of the destination interface ID set in the received information response message, deletes the first element from the destination interface ID set, sends the information response message from the selected interface, and executes step 409;

step 411: mobile node MN1 saves the server table entry in the information response message load;

step 412: and (6) ending.

The mobile node can rapidly acquire data through the above process.

In the method of the invention, after the mobile node MN1 executes the steps 401-412 to obtain the server table entry SE1 which is nearest and can provide the data C1, the data C1 is obtained through the following processes:

step 501: starting;

step 502: the mobile node MN1 sends a data request message, the name domain value of the data request message is NA1, the message type is 6, the geographic coordinate is equal to the geographic coordinate in the server table entry SE1, the source interface ID set and the destination interface ID set are all empty, and the load is empty;

step 503: judging whether the main access router or the access router receives the data request message, if the main access router receives the data request message, executing step 505, otherwise executing step 504;

step 504: after receiving a data request message from an interface g2 of an access router, adding an interface g2 into a source interface ID set of the data request message, and taking the interface g2 as a first element of the source interface ID set; the access router forwards the data request message from the upstream interface, and executes step 503;

step 505: after receiving a data request message from an interface g3 of a master access router, adding an interface g3 into a source interface ID set of the data request message, wherein the interface g3 serves as a first element of the source interface ID set; the main access router checks a main data router table, selects a main data router table item, the geographical coordinates of the table item are the same as those of the received data request message, updates a destination interface ID set in the data request message into an interface ID set of the main data server table item, selects an interface by the main access router, the interface ID of the interface is equal to a first element in the destination interface ID set, deletes the first element from the destination interface ID set, and sends the data request message from the selected interface;

step 506: judging whether the main data router or the core router receives the data request message, if the core router receives the data request message, executing a step 507, otherwise executing a step 508;

step 507: after receiving the data request message from the interface g4, the core router adds the interface g4 to the source interface ID set of the data request message, and the interface g4 is used as the first element of the source interface ID set; selecting an interface by the core router, wherein the interface ID of the interface is equal to the first element in the destination interface ID set, deleting the first element from the destination interface ID set, sending the data request message from the selected interface, and executing step 506;

step 508: after receiving the data request message from the interface g5, the master data router adds the interface g5 to the source interface ID set of the data request message, and uses the interface g5 as the first element of the source interface ID set; the main data router checks a server table and selects a server table entry, wherein the name of the server table entry is equal to the name of the data request message, and the geographical coordinate is closest to the geographical coordinate of the main data router; the main data router updates a destination interface ID set of the received data request message into an interface ID set of the list item of the server, selects an interface, the interface ID of the interface is equal to a first element in the destination interface ID set, deletes the first element from the destination interface ID set, and sends the data request message from the selected interface;

step 509: judging whether the data router or the server receives the data request message, if the server receives the data request message, executing step 511, otherwise executing step 510;

step 510: after receiving a data request message from an interface g6 of a data router, adding an interface g6 into a source interface ID set of the data request message, wherein the interface g6 serves as a first element of the source interface ID set; selecting an interface with interface ID equal to the first element in the destination interface ID set, deleting the first element from the destination interface ID set, sending the data request message from the selected interface, and executing step 509;

step 511: after receiving a data request message from an interface g7 of a server, adding an interface g7 into a source interface ID set of the data request message, and taking the interface g7 as a first element of the source interface ID set; the server creates a data response message, the name of the data response message is equal to the name in the received data request message, the geographic coordinate is equal to the geographic coordinate in the received data request message, the message type is 7, the source interface ID set is empty, the destination interface ID set is equal to the source interface ID set in the received data request message, and the load is the data identified by the name of the received data request message; the server selects an interface, the interface ID of which is equal to the first element in the destination interface ID set in the constructed data response message, deletes the first element from the destination interface ID set, and sends the data response message from the selected interface;

step 512: judging whether the communication device or the mobile node MN1 receives the data response message, if the mobile node MN1 receives the data response message, executing the step 514, otherwise executing the step 513;

step 513: the communication device selects an interface with an interface ID equal to the first element of the destination interface ID set in the received data response message, deletes the first element from the destination interface ID set, sends the data response message from the selected interface, and executes step 512;

step 513: mobile node MN1 holding the data in the data response message payload;

step 514: and (6) ending.

The mobile node can rapidly acquire data through the above process.

Has the advantages that: the invention provides an efficient data center network implementation method, and each node in the data center network can quickly acquire data through the network implementation method provided by the invention, so that the service performance is greatly improved. 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 flow chart of the controller table establishment according to the present invention.

Fig. 2 is a schematic diagram of a process for establishing a master data server table according to the present invention.

Fig. 3 is a schematic diagram of a server table establishment 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 data center network implementation method, and each node in the data center network can quickly acquire data through the network implementation method provided by the invention, so that the service performance is greatly improved. 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 flow chart of the controller table establishment according to the present invention. The network comprises a data backbone network, more than two data subnets and more than two access subnets; a data backbone network comprising controllers and core routers, each controller and core router having unique geographic coordinates; a core router has R1 interfaces, R1 is an integer greater than 1, a controller has an interface, the interface of the controller is connected with the interface of the core router;

the interface IDs of the controller, the server and the mobile node are all 1;

message types are shown in the following table

step 101: starting;

step 108: after the master data router, the master access router or the controller receives the publish message from the interface e1, adding the interface e1 into the source interface ID set of the publish message, and using the interface e1 as the first element of the source interface ID set; the master data router, the master access router or the controller checks the controller table, if a controller table entry exists, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the release message, and the interface ID set is equal to the source interface ID set of the release message, the life cycle of the controller table entry is set to be the maximum value; otherwise, the master data router receiving the release message from the interface e1, the master access router or the controller creating a controller table entry, the geographic coordinate domain value of the table entry is equal to the geographic coordinate in the release message, the interface ID set is equal to the source interface ID set of the release message, and the life cycle is set to the maximum value;

step 109: and (6) ending.

Fig. 2 is a schematic diagram of a process for establishing a master data server table according to the present invention. The core router, the main data router, the main access router and the controller jointly maintain a main data router table, and one main data router table item is composed of a geographic coordinate, an interface ID set and a life cycle domain;

step 201: starting;

step 208: after receiving the data router publishing message from the interface a2, the master access router or the controller adds the interface a2 to the data router publishing message source interface ID set, and uses the interface a2 as the first element of the source interface ID set; the main data router, the main access router or the controller checks the main data router table, if one main data router table item exists, the geographic coordinate domain value of the table item is equal to the geographic coordinate in the message issued by the data router, and the interface ID set is equal to the source interface ID set of the message issued by the data router, the life cycle of the main data router table item is set to be the maximum value; otherwise, the master data router receiving the data router publishing message from the interface a2, the master access router or the controller creating a master data router table entry, the geographic coordinate domain value of the table entry being equal to the geographic coordinate in the data router publishing message, the interface ID set being equal to the source interface ID set of the data router publishing message, the life cycle being set to the maximum value;

step 209: and (6) ending.

Fig. 3 is a schematic diagram of a server table establishment process according to the present invention. Each main data router and the controller jointly maintain a server table, and one server table item comprises a name domain, a geographic coordinate domain, an interface ID set and a life cycle domain; the data C1 is uniquely identified by a name NA1, and if the server holds the data C1, the following procedure is performed to build or update a server table:

step 301: starting;

step 310: and (6) ending.

Fig. 4 is a schematic diagram of a data communication process according to the present invention. If the data C1 is uniquely identified by the name NA1, the mobile node MN1 acquires the server information of the stored data C1 that is closest to by the following procedure:

step 401: starting;

step 412: and (6) ending.

Fig. 5 is a schematic diagram of a data acquisition process according to the present invention. After the mobile node MN1 executes steps 401-412 to obtain the closest server entry SE1 capable of providing the data C1, the data C1 is obtained by the following procedures:

step 501: starting;

step 511: after receiving a data request message from an interface g6 of a server, adding an interface g6 into a source interface ID set of the data request message, and taking the interface g6 as a first element of the source interface ID set; the server creates a data response message, the name of the data response message is equal to the name in the received data request message, the geographic coordinate is equal to the geographic coordinate in the received data request message, the message type is 7, the source interface ID set is empty, the destination interface ID set is equal to the source interface ID set in the received data request message, and the load is the data identified by the name of the received data request message; the server selects an interface, the interface ID of which is equal to the first element in the destination interface ID set in the constructed data response message, deletes the first element from the destination interface ID set, and sends the data response message from the selected interface;

step 514: and (6) ending.

Example 1

Based on the simulation parameters in table 1, this embodiment simulates an efficient data center 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 transmission data decreases, the delay of data transmission decreases, and the data acquisition average delay is 1.4 s.

TABLE 1 simulation parameters

The present invention provides a high-efficiency data center network implementation method, and a number of methods and ways for implementing the technical solution are provided, the above description is only a preferred embodiment of the present invention, it should be noted that, for those skilled in the art, a number of modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations 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

1. A high-efficiency data center network implementation method is characterized in that the network comprises a data backbone network, more than two data subnetworks and more than two access subnetworks; a data backbone network comprising controllers and core routers, each controller and core router having unique geographic coordinates; a core router has R1 interfaces, R1 is an integer greater than 1, a controller has an interface, the interface of the controller is connected with the interface of the core router;

the interface IDs of the controller, the server and the mobile node are all 1;

the message types are as follows: the message names are respectively a publishing message, a data router publishing message, a server publishing message, an information request message, an information response message, a data request message and a data response message, and the corresponding message type values are 1, 2, 3, 4, 5, 6 and 7; the core router, the main data router, the main access router and the controller jointly maintain a controller table, and one controller table is composed of a geographic coordinate, an interface ID set and a life cycle domain;

step 101: starting;

step 109: and (6) ending.

2. The method of claim 1, wherein the core router, the master data router, the master access router, and the controller collectively maintain a master data router table, wherein a master data router table entry comprises geographic coordinates, an interface ID set, and a lifecycle domain;

step 201: starting;

step 209: and (6) ending.

3. The method of claim 2, wherein each of the master data routers and the controllers collectively maintain a server table, wherein a server table entry comprises a name field, a geographic coordinate field, an interface ID set, and a lifecycle field; the data C1 is uniquely identified by a name NA1, and if the server holds the data C1, the following procedure is performed to build or update a server table:

step 301: starting;

step 310: and (6) ending.

4. An efficient data center network implementation method as claimed in claim 3, wherein if the data C1 is uniquely identified by the name NA1, the mobile node MN1 obtains the server information of the closest stored data C1 by:

step 401: starting;

step 412: and (6) ending.

5. The method as claimed in claim 4, wherein after the mobile node MN1 performs steps 401-412 to obtain the closest server entry SE1 capable of providing the data C1, the data C1 is obtained by:

step 501: starting;

step 514: and (6) ending.