CN109150727B - Software definition-based next generation network implementation method - Google Patents
Software definition-based next generation network implementation method Download PDFInfo
- Publication number
- CN109150727B CN109150727B CN201810916549.3A CN201810916549A CN109150727B CN 109150727 B CN109150727 B CN 109150727B CN 201810916549 A CN201810916549 A CN 201810916549A CN 109150727 B CN109150727 B CN 109150727B
- Authority
- CN
- China
- Prior art keywords
- message
- address
- access node
- controller
- coordinate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
Abstract
The invention provides a next generation network implementation method based on software definition, wherein the next generation network comprises a controller, more than two access nodes and more than two mobile devices; a mobile device is connected with an access node link, the access node is called an associated access node of the mobile device, and the mobile device communicates with other mobile devices through the associated access node; the location of the controller and the access node are fixed. The network can rapidly acquire network data through the implementation method provided by the invention, shorten the routing delay, reduce the data packet loss rate and improve the service quality.
Description
Technical Field
The invention relates to an implementation method, in particular to a next generation network implementation method based on software definition.
Background
The next generation network, as a new communication network, can implement multi-hop wireless communication between nodes. With the continuous development of network technology and the continuous emergence of various new applications, there is an urgent need to improve network performance.
At present, researchers have proposed a mode for acquiring network services through a next generation network and defined a corresponding protocol stack, but the existing network service acquisition method has some limitations because the architecture of the next generation network is different from that of the conventional network. Therefore, a method for implementing a next generation network is needed to improve the quality of service.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the technical problem of providing a next generation network implementation method based on software definition aiming at the defects of the prior art.
The technical scheme is as follows: the invention discloses a next generation network implementation method based on software definition, wherein the next generation network comprises a controller, more than two access nodes and more than two mobile devices; a mobile device is connected with an access node link, the access node is called an associated access node of the mobile device, and the mobile device communicates with other mobile devices through the associated access node; the positions of the controller and the access node are fixed;
the controller, the access node or the mobile device are respectively uniquely identified by an address, one address is composed of a geographical coordinate and a hardware ID, and the hardware ID is an MAC address for example;
a message comprises a message type, a sending source address, a forwarding source address, a destination address and a load;
the message types are as follows:
after the controller C1 starts, the following issuing operations are performed:
step 101: starting;
step 102: the controller C1 sends a release message, the message type of the release message is 1, the sending source address is the address of the controller C1, the forwarding source address is the address of the controller C1, the destination address is a broadcast address, each bit of the broadcast address is 1, and the load is null;
step 103: judging whether the mobile node or the access node receives the publishing message, if the mobile node is the mobile node, executing step 104, otherwise, executing step 105;
step 104: the mobile node that received the distribution message saves the transmission source address of the distribution message, and executes step 107;
step 105: the access node receiving the distribution message saves the sending source address of the distribution message, if the distance between the coordinate of the access node and the sending source address coordinate of the distribution message is larger than the distance between the sending source address coordinate of the distribution message and the forwarding source address coordinate of the distribution message, step 106 is executed, otherwise step 107 is executed;
step 106: the access node receiving the release message updates the forwarding source address of the release message to its own address, forwards the release message, and executes step 103;
step 107: and (6) ending.
The controller publishes the existence of the controller through the process, so that each mobile node and each access node can acquire the source address of the controller so as to establish communication with the controller; in the process, the access node determines whether to forward the release message by judging the distance between the access node and the controller, so that the cost of the controller for releasing the address is reduced, and the efficiency of controlling the release address is improved.
In the method of the invention, a controller stores an access node table and an equipment table; the access node table entry consists of an address domain and a life cycle domain; the equipment table entry comprises an address domain, a path set domain and a life cycle domain; the element of the path set is the address of the access node;
after the access node AP1 is started, it periodically performs registration operation with the controller C1 of the network:
step 201: starting;
step 202: the access node AP1 sends an access node registration message, the message type of the access node registration message is 2, the sending source address is the address of the access node AP1, the sending source address is the address of the access node AP1, the destination address is the address of the controller C1, and the load is empty;
step 203: judging whether the mobile node receives the access node registration message, executing step 210, otherwise executing step 204;
step 204: judging whether the controller C1 receives the access node registration message, if yes, executing step 207, otherwise, executing step 205;
step 205: the access node receiving the access node registration message judges whether the distance between the coordinate of the access node and the destination address coordinate of the access node registration message is smaller than the distance between the forwarding source address coordinate of the access node registration message and the destination address coordinate of the access node registration message, if so, the step 206 is executed, otherwise, the step 210 is executed;
step 206: the access node receiving the access node registration message updates the forwarding source address of the access node registration message to its own address, forwards the access node registration message, and executes step 203;
step 207: the controller C1 that has received the access node registration message checks the access node table, and determines whether there is an access node table entry whose hardware ID of the address field is equal to the hardware ID of the transmission source address of the access node registration message, if so, executes step 208, otherwise, executes step 209;
step 208: the controller C1 that receives the access node registration message selects an access node entry whose address field has a hardware ID equal to the hardware ID of the source address of the access node registration message, updates the address field of the access node entry to the source address of the access node registration message, sets the life cycle field value to the maximum value, e.g., 1s, and performs step 210;
step 209: the controller C1 that receives the access node registration message creates an access node entry whose address field is equal to the source address of the access node registration message and whose life cycle field value is set to the maximum value;
step 210: and (6) ending.
The access node establishes the access node list item of the access node in the controller through the process, so that the routing path from the controller to the access node can be established, the access node updates the access node list item of the access node in the controller in real time, so that the controller can acquire the real-time information of the access node, and meanwhile, in the process, the access node determines whether to forward the access node registration message or not by judging the distance between the access node and the controller, so that the cost of access node registration is reduced, and the performance of access node registration is also improved.
In the method of the invention, after the mobile node MD1 is started, its own path set PS1 is constructed, the path set PS1 is formed by addresses of access nodes included in the path traversed by the mobile node MD1, for example, the address set of access nodes traversed from home to office, the currently associated access node is the first element of the path set PS1, the next associated access node is the second element of the path set PS1, and the sequentially associated nth access node is the nth element of the path set PS 1;
the mobile node MD1 periodically performs the following registration operations:
step 301: starting;
step 302: the mobile node MD1 sends a device registration message, the message type of the device registration message is 3, the sending source address is the address of the mobile node MD1, the sending source address is the address of the mobile node MD1, and the load is a path set PS 1; if the mobile node MD1 knows the address of controller C1, then the destination address of the device registration message is the address of controller C1, otherwise the destination address of the device registration message is null;
step 303: determining whether the mobile node receives a device registration message, if yes, performing step 312, otherwise, performing step 304;
step 304: judging whether the controller C1 receives the device registration message, if yes, executing step 309, otherwise, executing step 305;
step 305: the access node receiving the device registration message judges whether the destination address of the device registration message is empty, if yes, step 306 is executed, otherwise step 307 is executed;
step 306: the access node receiving the device registration message updates the destination address of the device registration message to the address of the controller C1, forwards the source address to the own address, forwards the device registration message, and executes step 303;
step 307: the access node receiving the device registration message judges whether the distance between the coordinate of the access node and the destination address coordinate of the device registration message is smaller than the distance between the forwarding source address coordinate of the device registration message and the destination address coordinate of the device registration message, if so, the step 308 is executed, otherwise, the step 312 is executed;
step 308: the access node receiving the device registration message updates the forwarding source address of the device registration message to its own address, forwards the device registration message, and executes step 303;
step 309: the controller C1 that has received the device registration message checks the device table, and determines whether there is a device table entry whose hardware ID of the address field is equal to the hardware ID of the source address of the device registration message, if so, performs step 310, otherwise, performs step 311;
step 310: the controller C1 that received the device registration message selects a device table entry whose hardware ID of the address field is equal to the hardware ID of the transmission source address of the device registration message, updates the address field of the device table entry to the transmission source address of the device registration message, sets the path set field value to the path set in the device registration message load, sets the lifetime field value to the maximum value, e.g., 1s, and executes step 312;
step 311: the controller C1 that received the device registration message creates a device table entry whose address field is equal to the sending source address of the device registration message, sets the path set field value to the path set in the device registration message load, and sets the life cycle field value to the maximum value;
step 312: finishing;
if the coordinates of the mobile device change, the registration process of step 301 and step 312 is performed so that the controller can update the address of the mobile device in time;
if the mobile device passes through an access node, the path set is reconstructed and then the registration process of step 301 and 312 is performed so that the controller can update the path set of the mobile device in time.
The mobile device establishes the device list item of the mobile device in the controller through the process, so that the routing path from the controller to the mobile device can be established, the mobile device updates the device list item of the mobile device in the controller in real time, the controller is ensured to be capable of acquiring the real-time coordinate and the path set of the mobile device, and the controller can realize pre-switching operation for the mobile device, so that the communication continuity and the communication correctness of the mobile device are ensured.
In the method of the invention, the mobile equipment sends beacon messages to the associated access nodes periodically, and the access nodes send the beacon messages periodically;
the controller C1 periodically checks the device table, and if it detects that the device table entry E1 satisfies the condition 1, the first element of the path set domain value of the device table entry E1 is the address of the access node AP2, the second element of the path set domain value of the device table entry E1 is the address of the access node AP3, and the access nodes AP2 and AP3 are neighbor nodes, the controller C1 performs the following operations:
condition 1: the distance between the coordinates of the address domain value a1 of the device table entry E1 and the coordinates of the address of the access node AP2 is D1, the distance between the coordinates of the address domain value a1 of the device table entry E1 and the coordinates of the address of the access node AP3 is D2, the distance D1 is less than the distance D2, the absolute value of the difference between the distance D1 and the distance D2 is less than a threshold TH1, the threshold TH1 is preset, the threshold TH1 is generally greater than 10% of the communication radius and less than 50% of the communication radius, and the greater the threshold TH1 is, which indicates that the closer the distance between the mobile node and the access node AP3 is, the higher the probability of performing pre-handover is;
step 401: starting;
step 402: the controller C1 sends a pre-switching message, the message type of the pre-switching message is 4, the destination address is the address of the access node AP2, the sending source address and the forwarding source address are both the addresses of the controller C1, and the load is the address of the access node AP3 and the address A1; the controller C1 sends a waiting message, the message type of the waiting message is 5, the destination address is the address of the access node AP3, the sending source address and the forwarding source address are both the addresses of the controller C1, and the load is the address A1; the controller C1 sends a switching message, the message type of the switching message is 6, the destination address is an address A1, the sending source address and the forwarding source address are both addresses of the controller C1, and the load is the address of the access node AP 3;
step 403: judging whether the access node AP2 receives the pre-switching message, if yes, executing step 414, otherwise executing step 404;
step 404: determining whether the AP3 receives the wait message, if yes, performing step 415, otherwise performing step 405;
step 405: judging whether the hardware ID of the address of the mobile equipment receiving the switching message is equal to the hardware ID of the destination address of the switching message, if so, executing the step 416, otherwise, executing the step 406;
step 406: judging whether the access node receives the pre-switching message, if so, executing a step 407, otherwise, executing a step 409;
step 407: the access node receiving the pre-switching message judges whether the distance between the coordinate of the address of the access node and the coordinate of the destination address of the pre-switching message is smaller than the distance between the coordinate of the forwarding source address of the pre-switching message and the coordinate of the destination address of the pre-switching message, if so, the step 408 is executed, otherwise, the step 409 is executed;
step 408: the access node receiving the pre-switching message updates the forwarding source address of the pre-switching message to its own address, forwards the pre-switching message, and executes step 403;
step 409: judging whether the access node receives the waiting message, if so, executing step 410, otherwise, executing step 412;
step 410: the access node receiving the waiting message judges whether the distance between the coordinate of its address and the coordinate of the destination address of the waiting message is smaller than the distance between the coordinate of the forwarding source address of the waiting message and the coordinate of the destination address of the waiting message, if so, step 411 is executed, otherwise, step 412 is executed;
step 411: the access node receiving the waiting message updates the forwarding source address of the waiting message to its own address, forwards the waiting message, and executes step 403;
step 412: the access node receiving the switching message judges whether the distance between the coordinate of its address and the coordinate of the destination address of the switching message is smaller than the distance between the coordinate of the forwarding source address of the switching message and the coordinate of the destination address of the switching message, if so, step 413 is executed, otherwise, step 414 is executed;
step 413: the access node receiving the switching message updates the forwarding source address of the switching message to its own address, forwards the switching message, and performs step 403;
step 414: after the access node AP2 receives the pre-switch message, if a message that the hardware ID of the destination address is equal to the hardware ID of address a1 in the pre-switch message payload is received, the message is forwarded to the access node AP3, the access node AP2 saves the message, and step 417 is executed;
step 415: after the access node AP3 receives the wait message, if the message that the hardware ID of the destination address is equal to the hardware ID of address a1 in the wait message payload is received, then the message is saved and step 417 is executed;
step 416: after receiving the switching message, the mobile device with the hardware ID equal to the hardware ID of the destination address of the switching message switches to the access node AP3, and takes the access node AP3 as the currently associated access node;
step 417: if the access node AP3 receives a beacon message with a hardware ID equal to the hardware ID of address a1, the access node AP3 forwards all saved messages with a hardware ID of the destination address equal to the hardware ID of address a 1; the mobile device whose hardware ID is equal to that of address a1 receives and saves these messages;
step 418: and (6) ending.
The controller realizes pre-switching operation on the mobile equipment through the process, and informs a new access node of the mobile equipment of pre-storing the message with the destination address as the mobile equipment through the pre-switching operation, and forwards the message to the mobile equipment after the mobile equipment is linked to the new access node, so that the packet loss rate caused by mobile switching is effectively reduced, the success rate of data communication is improved, and the data communication delay is reduced.
In the method, the hardware ID of the mobile equipment MD1 is HID1, the controller of the next generation network where the mobile equipment MD1 is located is controller C1, and the hardware ID of the mobile equipment MD2 is HID 2; mobile device MD1 enables communication with mobile device MD2 by:
step 501: starting;
step 502: the mobile node MD1 sends a request message, the message type of the request message is 7, the sending source address is the address of the mobile equipment MD1, the forwarding source address is the address of the mobile equipment MD1, and the load is the hardware ID HID 2; if the mobile device MD1 knows the address of controller C1, then the destination address of the request message is the address of controller C1, otherwise the destination address of the request message is null;
step 503: judging whether the controller C1 or the access node receives the request message, if the request message is the controller C1, executing the step 508, otherwise, executing the step 504;
step 504: the access node receives the request message, judges whether the destination address of the request message is empty, if yes, step 505 is executed, otherwise step 506 is executed;
step 505: the access node receiving the request message updates the destination address of the request message to the address of the controller C1, updates the forwarding source address to its own address, forwards the request message, and executes step 503;
step 506: the access node receiving the request message judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the request message is smaller than the distance between the coordinate of the forwarding source address of the request message and the coordinate of the destination address, if so, the step 507 is executed, otherwise, the step 508 is executed;
step 507: the access node receiving the request message updates the forwarding source address of the request message to its own address, forwards the request message, and executes step 503;
step 508: after receiving the request message, the controller C1 selects an equipment table entry, the hardware ID of the address field of the equipment table entry is equal to the hardware ID in the load of the request message, updates the destination address of the request message to the address field value of the equipment table entry, updates the forwarding source address to the address of the controller C1, and forwards the request message;
step 509: determining whether the mobile device MD2 or the access node received the request message, if yes, go to step 512, otherwise go to step 510;
step 510: after receiving the request message, the access node judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the request message is smaller than the distance between the coordinate of the forwarding source address of the request message and the coordinate of the destination address, if so, executing step 511, otherwise, executing step 512;
step 511: the access node receiving the request message updates the forwarding source address of the request message to its own address, forwards the request message, and performs step 509;
step 512: after receiving the request message, the mobile device MD2 sends a response message, where the message type of the response message is 8, the sending source address and the forwarding source address are both addresses of the mobile device MD2, and the load is response data and the hardware ID HID1 of the mobile device MD 1; if the mobile device MD2 knows the address of controller C1, the destination address of the response message is the address of controller C1, otherwise, the destination address of the response message is null;
step 513: determining whether the controller C1 or the access node receives the response message, if yes, performing step 518, otherwise, performing step 514;
step 514: the access node receives the response message, judges whether the destination address of the response message is empty, if yes, step 515 is executed, otherwise step 516 is executed;
step 515: the access node that received the response message updates the destination address of the response message to the address of the controller C1, updates the forwarding source address to its own address, forwards the response message, and performs step 513;
step 516: the access node receiving the response message judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the response message is smaller than the distance between the coordinate of the forwarding source address of the response message and the coordinate of the destination address, if so, the step 517 is executed, otherwise, the step 518 is executed;
517: the access node receiving the response message updates the forwarding source address of the response message to its own address, forwards the response message, and performs step 513;
step 518: after receiving the response message, the controller C1 selects an equipment table entry, the hardware ID of the address field of the equipment table entry is equal to the hardware ID in the response message load, updates the destination address of the response message to the address field value of the equipment table entry, updates the forwarding source address to the address of the controller C1, and forwards the response message;
step 519: judging whether the mobile device MD1 or the access node receives the response message, executing step 522, otherwise executing step 520;
step 520: after receiving the response message, the access node judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the response message is smaller than the distance between the coordinate of the forwarding source address of the response message and the coordinate of the destination address, if so, the step 521 is executed, otherwise, the step 522 is executed;
step 521: the access node that receives the response message updates the forwarding source address of the response message to its own address, forwards the response message, and performs step 519;
step 522: after receiving the response message, the mobile device MD1 saves the response data in the response message load;
step 523: and (6) ending.
The mobile equipment realizes data communication through the process, and the controller stores the real-time coordinates of the source mobile equipment and the target mobile equipment, so that the source mobile equipment can realize communication with the target mobile equipment through the real-time coordinates of the target mobile equipment, the success rate of data communication is improved, and the delay of data communication is reduced. In addition, in the above process, the access node determines whether to forward the request message or the response message by judging the distance between the access node and the controller, thereby further reducing the cost and delay of data communication.
Has the advantages that: the invention provides a next generation network implementation method based on software definition, and the network can rapidly acquire network data, shorten routing delay, reduce data packet loss rate and improve service quality by the implementation method provided by the invention.
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 diagram of a controller issuing process according to the present invention.
Fig. 2 is a schematic diagram illustrating a controller registration process according to the present invention.
Fig. 3 is a schematic diagram illustrating a mobile node registration process according to the present invention.
Fig. 4 is a schematic diagram of a pre-switching process according to the present invention.
Fig. 5 is a schematic diagram of a communication flow according to the present invention.
The specific implementation mode is as follows:
the invention provides a next generation network implementation method based on software definition, and the network can rapidly acquire network data, shorten routing delay, reduce data packet loss rate and improve service quality by the implementation method provided by the invention.
Fig. 1 is a schematic diagram of a controller issuing process according to the present invention. The next generation network comprises a controller, more than two access nodes and more than two mobile devices; a mobile device is connected with an access node link, the access node is called an associated access node of the mobile device, and the mobile device communicates with other mobile devices through the associated access node; the positions of the controller and the access node are fixed;
the controller, the access node or the mobile device are respectively uniquely identified by an address, one address is composed of a geographical coordinate and a hardware ID, and the hardware ID is an MAC address for example;
a message comprises a message type, a sending source address, a forwarding source address, a destination address and a load;
the message types are as follows:
after the controller C1 starts, the following issuing operations are performed:
step 101: starting;
step 102: the controller C1 sends a release message, the message type of the release message is 1, the sending source address is the address of the controller C1, the forwarding source address is the address of the controller C1, the destination address is a broadcast address, each bit of the broadcast address is 1, and the load is null;
step 103: judging whether the mobile node or the access node receives the publishing message, if the mobile node is the mobile node, executing step 104, otherwise, executing step 105;
step 104: the mobile node that received the distribution message saves the transmission source address of the distribution message, and executes step 107;
step 105: the access node receiving the distribution message saves the sending source address of the distribution message, if the distance between the coordinate of the access node and the sending source address coordinate of the distribution message is larger than the distance between the sending source address coordinate of the distribution message and the forwarding source address coordinate of the distribution message, step 106 is executed, otherwise step 107 is executed;
step 106: the access node receiving the release message updates the forwarding source address of the release message to its own address, forwards the release message, and executes step 103;
step 107: and (6) ending.
Fig. 2 is a schematic diagram illustrating a controller registration process according to the present invention. A controller stores an access node table and a device table; the access node table entry consists of an address domain and a life cycle domain; the equipment table entry comprises an address domain, a path set domain and a life cycle domain; the element of the path set is the address of the access node;
after the access node AP1 is started, it periodically performs registration operation with the controller C1 of the network:
step 201: starting;
step 202: the access node AP1 sends an access node registration message, the message type of the access node registration message is 2, the sending source address is the address of the access node AP1, the sending source address is the address of the access node AP1, the destination address is the address of the controller C1, and the load is empty;
step 203: judging whether the mobile node receives the access node registration message, executing step 210, otherwise executing step 204;
step 204: judging whether the controller C1 receives the access node registration message, if yes, executing step 207, otherwise, executing step 205;
step 205: the access node receiving the access node registration message judges whether the distance between the coordinate of the access node and the destination address coordinate of the access node registration message is smaller than the distance between the forwarding source address coordinate of the access node registration message and the destination address coordinate of the access node registration message, if so, the step 206 is executed, otherwise, the step 210 is executed;
step 206: the access node receiving the access node registration message updates the forwarding source address of the access node registration message to its own address, forwards the access node registration message, and executes step 203;
step 207: the controller C1 that has received the access node registration message checks the access node table, and determines whether there is an access node table entry whose hardware ID of the address field is equal to the hardware ID of the transmission source address of the access node registration message, if so, executes step 208, otherwise, executes step 209;
step 208: the controller C1 that receives the access node registration message selects an access node entry whose address field has a hardware ID equal to the hardware ID of the source address of the access node registration message, updates the address field of the access node entry to the source address of the access node registration message, sets the life cycle field value to the maximum value, e.g., 1s, and performs step 210;
step 209: the controller C1 that receives the access node registration message creates an access node entry whose address field is equal to the source address of the access node registration message and whose life cycle field value is set to the maximum value;
step 210: and (6) ending.
Fig. 3 is a schematic diagram illustrating a mobile node registration process according to the present invention. After the mobile node MD1 is started, its own path set PS1 is constructed, where the path set PS1 is composed of addresses of access nodes included in a path traversed by the mobile node MD1, for example, an address set of access nodes traversed from home to office, a currently associated access node is a first element of the path set PS1, a next associated access node is a second element of the path set PS1, and an nth access node sequentially associated is an nth element of the path set PS 1;
the mobile node MD1 periodically performs the following registration operations:
step 301: starting;
step 302: the mobile node MD1 sends a device registration message, the message type of the device registration message is 3, the sending source address is the address of the mobile node MD1, the sending source address is the address of the mobile node MD1, and the load is a path set PS 1; if the mobile node MD1 knows the address of controller C1, then the destination address of the device registration message is the address of controller C1, otherwise the destination address of the device registration message is null;
step 303: determining whether the mobile node receives a device registration message, if yes, performing step 312, otherwise, performing step 304;
step 304: judging whether the controller C1 receives the device registration message, if yes, executing step 309, otherwise, executing step 305;
step 305: the access node receiving the device registration message judges whether the destination address of the device registration message is empty, if yes, step 306 is executed, otherwise step 307 is executed;
step 306: the access node receiving the device registration message updates the destination address of the device registration message to the address of the controller C1, forwards the source address to the own address, forwards the device registration message, and executes step 303;
step 307: the access node receiving the device registration message judges whether the distance between the coordinate of the access node and the destination address coordinate of the device registration message is smaller than the distance between the forwarding source address coordinate of the device registration message and the destination address coordinate of the device registration message, if so, the step 308 is executed, otherwise, the step 312 is executed;
step 308: the access node receiving the device registration message updates the forwarding source address of the device registration message to its own address, forwards the device registration message, and executes step 303;
step 309: the controller C1 that has received the device registration message checks the device table, and determines whether there is a device table entry whose hardware ID of the address field is equal to the hardware ID of the source address of the device registration message, if so, performs step 310, otherwise, performs step 311;
step 310: the controller C1 that received the device registration message selects a device table entry whose hardware ID of the address field is equal to the hardware ID of the transmission source address of the device registration message, updates the address field of the device table entry to the transmission source address of the device registration message, sets the path set field value to the path set in the device registration message load, sets the lifetime field value to the maximum value, e.g., 1s, and executes step 312;
step 311: the controller C1 that received the device registration message creates a device table entry whose address field is equal to the sending source address of the device registration message, sets the path set field value to the path set in the device registration message load, and sets the life cycle field value to the maximum value;
step 312: finishing;
if the coordinates of the mobile device change, the registration process of step 301 and step 312 is performed so that the controller can update the address of the mobile device in time;
if the mobile device passes through an access node, the path set is reconstructed and then the registration process of step 301 and 312 is performed so that the controller can update the path set of the mobile device in time.
Fig. 4 is a schematic diagram of a pre-switching process according to the present invention. The mobile equipment sends a beacon message to an associated access node regularly, and the access node sends the beacon message regularly;
the controller C1 periodically checks the device table, and if it detects that the device table entry E1 satisfies the condition 1, the first element of the path set domain value of the device table entry E1 is the address of the access node AP2, the second element of the path set domain value of the device table entry E1 is the address of the access node AP3, and the access nodes AP2 and AP3 are neighbor nodes, the controller C1 performs the following operations:
condition 1: the distance between the coordinates of the address domain value a1 of the device table entry E1 and the coordinates of the address of the access node AP2 is D1, the distance between the coordinates of the address domain value a1 of the device table entry E1 and the coordinates of the address of the access node AP3 is D2, the distance D1 is less than the distance D2, the absolute value of the difference between the distance D1 and the distance D2 is less than a threshold TH1, the threshold TH1 is preset, the threshold TH1 is generally greater than 10% of the communication radius and less than 50% of the communication radius, and the greater the threshold TH1 is, which indicates that the closer the distance between the mobile node and the access node AP3 is, the higher the probability of performing pre-handover is;
step 401: starting;
step 402: the controller C1 sends a pre-switching message, the message type of the pre-switching message is 4, the destination address is the address of the access node AP2, the sending source address and the forwarding source address are both the addresses of the controller C1, and the load is the address of the access node AP3 and the address A1; the controller C1 sends a waiting message, the message type of the waiting message is 5, the destination address is the address of the access node AP3, the sending source address and the forwarding source address are both the addresses of the controller C1, and the load is the address A1; the controller C1 sends a switching message, the message type of the switching message is 6, the destination address is an address A1, the sending source address and the forwarding source address are both addresses of the controller C1, and the load is the address of the access node AP 3;
step 403: judging whether the access node AP2 receives the pre-switching message, if yes, executing step 414, otherwise executing step 404;
step 404: determining whether the AP3 receives the wait message, if yes, performing step 415, otherwise performing step 405;
step 405: judging whether the hardware ID of the address of the mobile equipment receiving the switching message is equal to the hardware ID of the destination address of the switching message, if so, executing the step 416, otherwise, executing the step 406;
step 406: judging whether the access node receives the pre-switching message, if so, executing a step 407, otherwise, executing a step 409;
step 407: the access node receiving the pre-switching message judges whether the distance between the coordinate of the address of the access node and the coordinate of the destination address of the pre-switching message is smaller than the distance between the coordinate of the forwarding source address of the pre-switching message and the coordinate of the destination address of the pre-switching message, if so, the step 408 is executed, otherwise, the step 409 is executed;
step 408: the access node receiving the pre-switching message updates the forwarding source address of the pre-switching message to its own address, forwards the pre-switching message, and executes step 403;
step 409: judging whether the access node receives the waiting message, if so, executing step 410, otherwise, executing step 412;
step 410: the access node receiving the waiting message judges whether the distance between the coordinate of its address and the coordinate of the destination address of the waiting message is smaller than the distance between the coordinate of the forwarding source address of the waiting message and the coordinate of the destination address of the waiting message, if so, step 411 is executed, otherwise, step 412 is executed;
step 411: the access node receiving the waiting message updates the forwarding source address of the waiting message to its own address, forwards the waiting message, and executes step 403;
step 412: the access node receiving the switching message judges whether the distance between the coordinate of its address and the coordinate of the destination address of the switching message is smaller than the distance between the coordinate of the forwarding source address of the switching message and the coordinate of the destination address of the switching message, if so, step 413 is executed, otherwise, step 414 is executed;
step 413: the access node receiving the switching message updates the forwarding source address of the switching message to its own address, forwards the switching message, and performs step 403;
step 414: after the access node AP2 receives the pre-switch message, if a message that the hardware ID of the destination address is equal to the hardware ID of address a1 in the pre-switch message payload is received, the message is forwarded to the access node AP3, the access node AP2 saves the message, and step 417 is executed;
step 415: after the access node AP3 receives the wait message, if the message that the hardware ID of the destination address is equal to the hardware ID of address a1 in the wait message payload is received, then the message is saved and step 417 is executed;
step 416: after receiving the switching message, the mobile device with the hardware ID equal to the hardware ID of the destination address of the switching message switches to the access node AP3, and takes the access node AP3 as the currently associated access node;
step 417: if the access node AP3 receives a beacon message with a hardware ID equal to the hardware ID of address a1, the access node AP3 forwards all saved messages with a hardware ID of the destination address equal to the hardware ID of address a 1; the mobile device whose hardware ID is equal to that of address a1 receives and saves these messages;
step 418: and (6) ending.
Fig. 5 is a schematic diagram of a communication flow according to the present invention. The hardware ID of the mobile device MD1 is HID1, the controller of the next generation network is controller C1, and the hardware ID of the mobile device MD2 is HID 2; mobile device MD1 enables communication with mobile device MD2 by:
step 501: starting;
step 502: the mobile node MD1 sends a request message, the message type of the request message is 7, the sending source address is the address of the mobile equipment MD1, the forwarding source address is the address of the mobile equipment MD1, and the load is the hardware ID HID 2; if the mobile device MD1 knows the address of controller C1, then the destination address of the request message is the address of controller C1, otherwise the destination address of the request message is null;
step 503: judging whether the controller C1 or the access node receives the request message, if the request message is the controller C1, executing the step 508, otherwise, executing the step 504;
step 504: the access node receives the request message, judges whether the destination address of the request message is empty, if yes, step 505 is executed, otherwise step 506 is executed;
step 505: the access node receiving the request message updates the destination address of the request message to the address of the controller C1, updates the forwarding source address to its own address, forwards the request message, and executes step 503;
step 506: the access node receiving the request message judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the request message is smaller than the distance between the coordinate of the forwarding source address of the request message and the coordinate of the destination address, if so, the step 507 is executed, otherwise, the step 508 is executed;
step 507: the access node receiving the request message updates the forwarding source address of the request message to its own address, forwards the request message, and executes step 503;
step 508: after receiving the request message, the controller C1 selects an equipment table entry, the hardware ID of the address field of the equipment table entry is equal to the hardware ID in the load of the request message, updates the destination address of the request message to the address field value of the equipment table entry, updates the forwarding source address to the address of the controller C1, and forwards the request message;
step 509: determining whether the mobile device MD2 or the access node received the request message, if yes, go to step 512, otherwise go to step 510;
step 510: after receiving the request message, the access node judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the request message is smaller than the distance between the coordinate of the forwarding source address of the request message and the coordinate of the destination address, if so, executing step 511, otherwise, executing step 512;
step 511: the access node receiving the request message updates the forwarding source address of the request message to its own address, forwards the request message, and performs step 509;
step 512: after receiving the request message, the mobile device MD2 sends a response message, where the message type of the response message is 8, the sending source address and the forwarding source address are both addresses of the mobile device MD2, and the load is response data and the hardware ID HID1 of the mobile device MD 1; if the mobile device MD2 knows the address of controller C1, the destination address of the response message is the address of controller C1, otherwise, the destination address of the response message is null;
step 513: determining whether the controller C1 or the access node receives the response message, if yes, performing step 518, otherwise, performing step 514;
step 514: the access node receives the response message, judges whether the destination address of the response message is empty, if yes, step 515 is executed, otherwise step 516 is executed;
step 515: the access node that received the response message updates the destination address of the response message to the address of the controller C1, updates the forwarding source address to its own address, forwards the response message, and performs step 513;
step 516: the access node receiving the response message judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the response message is smaller than the distance between the coordinate of the forwarding source address of the response message and the coordinate of the destination address, if so, the step 517 is executed, otherwise, the step 518 is executed;
517: the access node receiving the response message updates the forwarding source address of the response message to its own address, forwards the response message, and performs step 513;
step 518: after receiving the response message, the controller C1 selects an equipment table entry, the hardware ID of the address field of the equipment table entry is equal to the hardware ID in the response message load, updates the destination address of the response message to the address field value of the equipment table entry, updates the forwarding source address to the address of the controller C1, and forwards the response message;
step 519: judging whether the mobile device MD1 or the access node receives the response message, executing step 522, otherwise executing step 520;
step 520: after receiving the response message, the access node judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the response message is smaller than the distance between the coordinate of the forwarding source address of the response message and the coordinate of the destination address, if so, the step 521 is executed, otherwise, the step 522 is executed;
step 521: the access node that receives the response message updates the forwarding source address of the response message to its own address, forwards the response message, and performs step 519;
step 522: after receiving the response message, the mobile device MD1 saves the response data in the response message load;
step 523: and (6) ending.
Example 1
Based on the simulation parameters in table 1, the present embodiment simulates a next generation network implementation method based on software definition in the present invention, and the performance analysis is as follows: when the mobile node moves faster, the controller executes pre-switching operation more frequently, and when the mobile node moves slower, the controller executes pre-switching operation less frequently; the average delay for the controller to perform the pre-switching is 95 ms.
TABLE 1 simulation parameters
The present invention provides a concept of a next generation network implementation method based on software definition, and a plurality of methods and approaches for implementing the technical solution, and the above description is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, a plurality of improvements and modifications may be made without departing from the principle of the present invention, 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 (1)
1. A next generation network implementation method based on software definition is characterized in that the next generation network comprises a controller, more than two access nodes and more than two mobile devices; a mobile device is connected with an access node link, the access node is called an associated access node of the mobile device, and the mobile device communicates with other mobile devices through the associated access node; the positions of the controller and the access node are fixed;
the controller, the access node or the mobile equipment are respectively and uniquely identified by one address, and one address is composed of a geographical coordinate and a hardware ID;
a message comprises a message type, a sending source address, a forwarding source address, a destination address and a load;
the message types are as follows:
After the controller C1 starts, the following issuing operations are performed:
step 101: starting;
step 102: the controller C1 sends a release message, the message type of the release message is 1, the sending source address is the address of the controller C1, the forwarding source address is the address of the controller C1, the destination address is a broadcast address, each bit of the broadcast address is 1, and the load is null;
step 103: judging whether the mobile equipment or the access node receives the publishing message, if so, executing step 104, otherwise, executing step 105;
step 104: the mobile device that received the distribution message saves the transmission source address of the distribution message, and executes step 107;
step 105: the access node receiving the distribution message saves the sending source address of the distribution message, if the distance between the coordinate of the access node and the sending source address coordinate of the distribution message is larger than the distance between the sending source address coordinate of the distribution message and the forwarding source address coordinate of the distribution message, step 106 is executed, otherwise step 107 is executed;
step 106: the access node receiving the release message updates the forwarding source address of the release message to its own address, forwards the release message, and executes step 103;
step 107: finishing;
a controller stores an access node table and a device table; the access node table entry consists of an address domain and a life cycle domain; the equipment table entry comprises an address domain, a path set domain and a life cycle domain; the element of the path set is the address of the access node;
after the access node AP1 is started, it periodically performs registration operation with the controller C1 of the network:
step 201: starting;
step 202: the access node AP1 sends an access node registration message, the message type of the access node registration message is 2, the sending source address is the address of the access node AP1, the sending source address is the address of the access node AP1, the destination address is the address of the controller C1, and the load is empty;
step 203: judging whether the mobile equipment receives an access node registration message, executing step 210, otherwise executing step 204;
step 204: judging whether the controller C1 receives the access node registration message, if yes, executing step 207, otherwise, executing step 205;
step 205: the access node receiving the access node registration message judges whether the distance between the coordinate of the access node and the destination address coordinate of the access node registration message is smaller than the distance between the forwarding source address coordinate of the access node registration message and the destination address coordinate of the access node registration message, if so, the step 206 is executed, otherwise, the step 210 is executed;
step 206: the access node receiving the access node registration message updates the forwarding source address of the access node registration message to its own address, forwards the access node registration message, and executes step 203;
step 207: the controller C1 that has received the access node registration message checks the access node table, and determines whether there is an access node table entry whose hardware ID of the address field is equal to the hardware ID of the transmission source address of the access node registration message, if so, executes step 208, otherwise, executes step 209;
step 208: the controller C1 that receives the access node registration message selects an access node entry whose address field has a hardware ID equal to the hardware ID of the source address of the access node registration message, updates the address field of the access node entry to the source address of the access node registration message, sets the life cycle field value to the maximum value, and performs step 210;
step 209: the controller C1 that receives the access node registration message creates an access node entry whose address field is equal to the source address of the access node registration message and whose life cycle field value is set to the maximum value;
step 210: finishing;
after the mobile device MD1 is started, its own path set PS1 is constructed, where the path set PS1 is formed by addresses of access nodes included in a path traversed by the mobile device MD1, the currently associated access node is a first element of the path set PS1, the next associated access node is a second element of the path set PS1, and the sequentially associated nth access node is an nth element of the path set PS 1;
the mobile device MD1 periodically performs the following registration operations:
step 301: starting;
step 302: the mobile equipment MD1 sends an equipment registration message, the message type of the equipment registration message is 3, the sending source address is the address of the mobile equipment MD1, the sending source address is the address of the mobile equipment MD1, and the load is a path set PS 1; if the mobile device MD1 knows the address of controller C1, then the destination address of the device registration message is the address of controller C1, otherwise the destination address of the device registration message is null;
step 303: determining whether the mobile device receives a device registration message, if yes, performing step 312, otherwise, performing step 304;
step 304: judging whether the controller C1 receives the device registration message, if yes, executing step 309, otherwise, executing step 305;
step 305: the access node receiving the device registration message judges whether the destination address of the device registration message is empty, if yes, step 306 is executed, otherwise step 307 is executed;
step 306: the access node receiving the device registration message updates the destination address of the device registration message to the address of the controller C1, forwards the source address to the own address, forwards the device registration message, and executes step 303;
step 307: the access node receiving the device registration message judges whether the distance between the coordinate of the access node and the destination address coordinate of the device registration message is smaller than the distance between the forwarding source address coordinate of the device registration message and the destination address coordinate of the device registration message, if so, the step 308 is executed, otherwise, the step 312 is executed;
step 308: the access node receiving the device registration message updates the forwarding source address of the device registration message to its own address, forwards the device registration message, and executes step 303;
step 309: the controller C1 that has received the device registration message checks the device table, and determines whether there is a device table entry whose hardware ID of the address field is equal to the hardware ID of the source address of the device registration message, if so, performs step 310, otherwise, performs step 311;
step 310: the controller C1 that received the device registration message selects a device table entry whose hardware ID of the address field is equal to the hardware ID of the transmission source address of the device registration message, updates the address field of the device table entry to the transmission source address of the device registration message, sets the path set field value as the path set in the device registration message load, sets the lifetime field value as the maximum value, and executes step 312;
step 311: the controller C1 that received the device registration message creates a device table entry whose address field is equal to the sending source address of the device registration message, sets the path set field value to the path set in the device registration message load, and sets the life cycle field value to the maximum value;
step 312: finishing;
if the coordinates of the mobile device change, the registration process of step 301 and step 312 is performed so that the controller can update the address of the mobile device in time;
if the mobile device passes through an access node, reconstructing the path set, and then performing the registration process of step 301 and step 312 so that the controller can update the path set of the mobile device in time;
the mobile equipment sends a beacon message to an associated access node regularly, and the access node sends the beacon message regularly;
the controller C1 periodically checks the device table, and if it detects that the device table entry E1 satisfies the condition 1, the first element of the path set domain value of the device table entry E1 is the address of the access node AP2, the second element of the path set domain value of the device table entry E1 is the address of the access node AP3, and the access nodes AP2 and AP3 are neighbor nodes, the controller C1 performs the following operations:
condition 1: the distance between the coordinates of the address domain value A1 of the device table entry E1 and the coordinates of the address of the access node AP2 is D1, the distance between the coordinates of the address domain value A1 of the device table entry E1 and the coordinates of the address of the access node AP3 is D2, the distance D1 is smaller than the distance D2, the absolute value of the difference between the distance D1 and the distance D2 is smaller than a threshold TH1, and the threshold TH1 is preset;
step 401: starting;
step 402: the controller C1 sends a pre-switching message, the message type of the pre-switching message is 4, the destination address is the address of the access node AP2, the sending source address and the forwarding source address are both the addresses of the controller C1, and the load is the address of the access node AP3 and the address A1; the controller C1 sends a waiting message, the message type of the waiting message is 5, the destination address is the address of the access node AP3, the sending source address and the forwarding source address are both the addresses of the controller C1, and the load is the address A1; the controller C1 sends a switching message, the message type of the switching message is 6, the destination address is an address A1, the sending source address and the forwarding source address are both addresses of the controller C1, and the load is the address of the access node AP 3;
step 403: judging whether the access node AP2 receives the pre-switching message, if yes, executing step 414, otherwise executing step 404;
step 404: determining whether the AP3 receives the wait message, if yes, performing step 415, otherwise performing step 405;
step 405: judging whether the hardware ID of the address of the mobile equipment receiving the switching message is equal to the hardware ID of the destination address of the switching message, if so, executing the step 416, otherwise, executing the step 406;
step 406: judging whether the access node receives the pre-switching message, if so, executing a step 407, otherwise, executing a step 409;
step 407: the access node receiving the pre-switching message judges whether the distance between the coordinate of the address of the access node and the coordinate of the destination address of the pre-switching message is smaller than the distance between the coordinate of the forwarding source address of the pre-switching message and the coordinate of the destination address of the pre-switching message, if so, the step 408 is executed, otherwise, the step 409 is executed;
step 408: the access node receiving the pre-switching message updates the forwarding source address of the pre-switching message to its own address, forwards the pre-switching message, and executes step 403;
step 409: judging whether the access node receives the waiting message, if so, executing step 410, otherwise, executing step 412;
step 410: the access node receiving the waiting message judges whether the distance between the coordinate of its address and the coordinate of the destination address of the waiting message is smaller than the distance between the coordinate of the forwarding source address of the waiting message and the coordinate of the destination address of the waiting message, if so, step 411 is executed, otherwise, step 412 is executed;
step 411: the access node receiving the waiting message updates the forwarding source address of the waiting message to its own address, forwards the waiting message, and executes step 403;
step 412: the access node receiving the switching message judges whether the distance between the coordinate of its address and the coordinate of the destination address of the switching message is smaller than the distance between the coordinate of the forwarding source address of the switching message and the coordinate of the destination address of the switching message, if so, step 413 is executed, otherwise, step 414 is executed;
step 413: the access node receiving the switching message updates the forwarding source address of the switching message to its own address, forwards the switching message, and performs step 403;
step 414: after the access node AP2 receives the pre-switch message, if a message that the hardware ID of the destination address is equal to the hardware ID of address a1 in the pre-switch message payload is received, the message is forwarded to the access node AP3, the access node AP2 saves the message, and step 417 is executed;
step 415: after the access node AP3 receives the wait message, if the message that the hardware ID of the destination address is equal to the hardware ID of address a1 in the wait message payload is received, then the message is saved and step 417 is executed;
step 416: after receiving the switching message, the mobile device with the hardware ID equal to the hardware ID of the destination address of the switching message switches to the access node AP3, and takes the access node AP3 as the currently associated access node;
step 417: if the access node AP3 receives a beacon message with a hardware ID equal to the hardware ID of address a1, the access node AP3 forwards all saved messages with a hardware ID of the destination address equal to the hardware ID of address a 1; the mobile device whose hardware ID is equal to that of address a1 receives and saves these messages;
step 418: finishing;
the hardware ID of the mobile device MD1 is HID1, the controller of the next generation network is controller C1, and the hardware ID of the mobile device MD2 is HID 2; mobile device MD1 enables communication with mobile device MD2 by:
step 501: starting;
step 502: the mobile equipment MD1 sends a request message, the message type of the request message is 7, the sending source address is the address of the mobile equipment MD1, the forwarding source address is the address of the mobile equipment MD1, and the load is the hardware ID HID 2; if the mobile device MD1 knows the address of controller C1, then the destination address of the request message is the address of controller C1, otherwise the destination address of the request message is null;
step 503: judging whether the controller C1 or the access node receives the request message, if the request message is the controller C1, executing the step 508, otherwise, executing the step 504;
step 504: the access node receives the request message, judges whether the destination address of the request message is empty, if yes, step 505 is executed, otherwise step 506 is executed;
step 505: the access node receiving the request message updates the destination address of the request message to the address of the controller C1, updates the forwarding source address to its own address, forwards the request message, and executes step 503;
step 506: the access node receiving the request message judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the request message is smaller than the distance between the coordinate of the forwarding source address of the request message and the coordinate of the destination address, if so, the step 507 is executed, otherwise, the step 508 is executed;
step 507: the access node receiving the request message updates the forwarding source address of the request message to its own address, forwards the request message, and executes step 503;
step 508: after receiving the request message, the controller C1 selects an equipment table entry, the hardware ID of the address field of the equipment table entry is equal to the hardware ID in the load of the request message, updates the destination address of the request message to the address field value of the equipment table entry, updates the forwarding source address to the address of the controller C1, and forwards the request message;
step 509: determining whether the mobile device MD2 or the access node received the request message, if yes, go to step 512, otherwise go to step 510;
step 510: after receiving the request message, the access node judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the request message is smaller than the distance between the coordinate of the forwarding source address of the request message and the coordinate of the destination address, if so, executing step 511, otherwise, executing step 512;
step 511: the access node receiving the request message updates the forwarding source address of the request message to its own address, forwards the request message, and performs step 509;
step 512: after receiving the request message, the mobile device MD2 sends a response message, where the message type of the response message is 8, the sending source address and the forwarding source address are both addresses of the mobile device MD2, and the load is response data and the hardware ID HID1 of the mobile device MD 1; if the mobile device MD2 knows the address of controller C1, the destination address of the response message is the address of controller C1, otherwise, the destination address of the response message is null;
step 513: it is determined whether controller C1 or the access node received the response message, if so, step 518 is performed,
otherwise, go to step 514;
step 514: the access node receives the response message, judges whether the destination address of the response message is empty, if yes, step 515 is executed, otherwise step 516 is executed;
step 515: the access node that received the response message updates the destination address of the response message to the address of the controller C1, updates the forwarding source address to its own address, forwards the response message, and performs step 513;
step 516: the access node receiving the response message judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the response message is smaller than the distance between the coordinate of the forwarding source address of the response message and the coordinate of the destination address, if so, the step 517 is executed, otherwise, the step 518 is executed;
517: the access node receiving the response message updates the forwarding source address of the response message to its own address, forwards the response message, and performs step 513;
step 518: after receiving the response message, the controller C1 selects an equipment table entry, the hardware ID of the address field of the equipment table entry is equal to the hardware ID in the response message load, updates the destination address of the response message to the address field value of the equipment table entry, updates the forwarding source address to the address of the controller C1, and forwards the response message;
step 519: judging whether the mobile device MD1 or the access node receives the response message, executing step 522, otherwise executing step 520;
step 520: after receiving the response message, the access node judges whether the distance between the coordinate of the access node and the coordinate of the destination address of the response message is smaller than the distance between the coordinate of the forwarding source address of the response message and the coordinate of the destination address, if so, the step 521 is executed, otherwise, the step 522 is executed;
step 521: the access node that receives the response message updates the forwarding source address of the response message to its own address, forwards the response message, and performs step 519;
step 522: after receiving the response message, the mobile device MD1 saves the response data in the response message load;
step 523: and (6) ending.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810916549.3A CN109150727B (en) | 2018-08-13 | 2018-08-13 | Software definition-based next generation network implementation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810916549.3A CN109150727B (en) | 2018-08-13 | 2018-08-13 | Software definition-based next generation network implementation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109150727A CN109150727A (en) | 2019-01-04 |
| CN109150727B true CN109150727B (en) | 2020-10-30 |
Family
ID=64792772
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810916549.3A Active CN109150727B (en) | 2018-08-13 | 2018-08-13 | Software definition-based next generation network implementation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109150727B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105915419A (en) * | 2015-11-25 | 2016-08-31 | 北京邮电大学 | Wireless access controller deployment method based on SDN (Software Defined Network) |
| CN107360613A (en) * | 2017-08-28 | 2017-11-17 | 常熟理工学院 | A kind of reliable wireless network route Realization Method of Communication |
| CN107949074A (en) * | 2017-12-06 | 2018-04-20 | 常熟理工学院 | A kind of reliable next generation network implementation method |
| CN108289062A (en) * | 2017-12-21 | 2018-07-17 | 北京邮电大学 | A kind of information centre's network structure based on software definition |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10863558B2 (en) * | 2016-03-30 | 2020-12-08 | Schweitzer Engineering Laboratories, Inc. | Communication device for implementing trusted relationships in a software defined network |
-
2018
- 2018-08-13 CN CN201810916549.3A patent/CN109150727B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105915419A (en) * | 2015-11-25 | 2016-08-31 | 北京邮电大学 | Wireless access controller deployment method based on SDN (Software Defined Network) |
| CN107360613A (en) * | 2017-08-28 | 2017-11-17 | 常熟理工学院 | A kind of reliable wireless network route Realization Method of Communication |
| CN107949074A (en) * | 2017-12-06 | 2018-04-20 | 常熟理工学院 | A kind of reliable next generation network implementation method |
| CN108289062A (en) * | 2017-12-21 | 2018-07-17 | 北京邮电大学 | A kind of information centre's network structure based on software definition |
Non-Patent Citations (3)
| Title |
|---|
| Neda Cvijetic;Ting Wang.Software-defined throughput optimization for next-generation optical mobile backhaul.《2013 18th OptoElectronics and Communications Conference held jointly with 2013 International Conference on Photonics in Switching (OECC/PS)》.2013, * |
| Software Defined Networking for Next Generation Converged Metro-Access Networks;M. Ruffini; F. Slyne; C. Bluemm;《Optical Fiber Technology》;20151215;全文 * |
| 无线传感器网络构建与实现;孙琪；王晓喃;《常熟理工学院学报》;20170320;第31卷(第2期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109150727A (en) | 2019-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4981125B2 (en) | Handover of a plurality of mobile stations from a first base station to a second base station | |
| CN106954236B (en) | method for controlling wireless terminal to roam seamlessly and wireless access point | |
| JP5374929B2 (en) | Mobile communication system, mobile communication method, and communication apparatus | |
| JP6000746B2 (en) | Data connection point selection | |
| CN106130905B (en) | The link restoring method of HWMP priori tree route pattern | |
| CN106954243B (en) | Route realizing method based on wireless chain network | |
| CN108848528B (en) | SDN and NFV converged network mobility management method | |
| CN105722170A (en) | Industrial mobile network AP (Access Point) switching method based on double wireless network cards | |
| ATE546024T1 (en) | A METHOD FOR A ßDUAL TRANSFER MODE FORWARDING | |
| CN104254110A (en) | Wireless Mesh network inter-domain switching method | |
| CN101208908A (en) | Access point and method for delivering information on media independent handover protocol | |
| CN105188103A (en) | Rapid roaming optimization method for use in MESH network routing protocol | |
| CN100558185C (en) | Mobile communication system and paging method thereof | |
| CN109150727B (en) | Software definition-based next generation network implementation method | |
| JP2013115466A (en) | Radio communication device, radio communication device control method, radio communication device control program, radio communication system, radio communication system control method, control device, control device control method, and control device control program | |
| CN109462875A (en) | Wireless roaming method, access point apparatus and mobile station | |
| US9247483B2 (en) | Method and system for data traffic offload | |
| CN109194526B (en) | Fault take-over method for realizing cluster group calling by group multi-homing | |
| CN108777702B (en) | Network data communication method based on vehicle-mounted cloud | |
| Tsubouchi et al. | Anchorless routing for URLLC services in 5G network | |
| CN109039912B (en) | Software defined network implementation method based on multipath | |
| JP2005086560A (en) | Mobile communication terminal, mobile communication system, and method for registering location of mobile communication terminal | |
| Kim et al. | SWITCH: SDN-WLAN Integrated Handover Scheme for QoS-Guaranteed Mobile Service. | |
| CN108777871B (en) | Method for realizing next generation sensor network communication system | |
| CN102821375A (en) | Signaling processing method and system used for switching relay node |
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: 20230420 Address after: 230000 floor 1, building 2, phase I, e-commerce Park, Jinggang Road, Shushan Economic Development Zone, Hefei City, Anhui Province Patentee after: Dragon totem Technology (Hefei) Co.,Ltd. Address before: 215500 Changshu Institute of Technology (southeast campus), Changshu City, Suzhou City, Jiangsu Province Patentee before: CHANGSHU INSTITUTE OF TECHNOLOGY |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230515 Address after: 202, Block B, No. 10 Xiqin Street, Wuchang Street, Yuhang District, Hangzhou City, Zhejiang Province, 310000 Patentee after: Zhejiang Weite Electronic Information Co.,Ltd. Address before: 230000 floor 1, building 2, phase I, e-commerce Park, Jinggang Road, Shushan Economic Development Zone, Hefei City, Anhui Province Patentee before: Dragon totem Technology (Hefei) Co.,Ltd. |