CN104717142B - Method for carrying out mobility management based on OpenFlow protocol - Google Patents
Method for carrying out mobility management based on OpenFlow protocol Download PDFInfo
- Publication number
- CN104717142B CN104717142B CN201510069728.4A CN201510069728A CN104717142B CN 104717142 B CN104717142 B CN 104717142B CN 201510069728 A CN201510069728 A CN 201510069728A CN 104717142 B CN104717142 B CN 104717142B
- Authority
- CN
- China
- Prior art keywords
- mobile node
- openflow switch
- address
- controller
- openflow
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000006870 function Effects 0.000 claims abstract description 80
- 230000006399 behavior Effects 0.000 claims abstract description 4
- 238000004891 communication Methods 0.000 claims description 23
- 239000003795 chemical substances by application Substances 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for carrying out mobility management based on an OpenFlow protocol, which comprises the following steps: step 1), a Controller maintains a corresponding relation table recorded with a plurality of OpenFlow switches with AP functions and port numbers connected to each gateway; step 2) receiving identification information containing a mobile node MN and reported information of a first OpenFlow switch attached to the mobile node MN, wherein the identification information of the mobile node MN is an MAC address and/or an IP address of the mobile node, and the identification information is transmitted by the first OpenFlow switch with the AP function; and 3) checking the corresponding relation table according to the report information, and executing different routing behaviors based on the identification information of the mobile node MN and the query result of the report information of the first OpenFlow switch attached to the mobile node MN.
Description
Technical Field
The invention discloses a method and a device for carrying out mobility management based on an OpenFlow protocol, and belongs to the technical field of mobile communication.
Background
Mobile IP is designed to satisfy the requirement that Mobile Nodes (MN) maintain their connectivity on the move. There are now two versions of Mobile IP, Mobile IPv4 and Mobile IPv 6.
Software-defined networking (SDN) is a network virtualization (network virtualization) technology. The control plane (control plane) of the router is separated from the data plane (data plane) by utilizing an OpenFlow protocol, and the control plane (control plane) is realized in a software mode. The architecture can enable a network administrator to plan the network again by programs in a central control mode on the premise of not changing hardware equipment, provides a new method for controlling network flow, and also provides a good platform for core network and application innovation.
The OpenFlow technology was originally proposed by Stanford university and aims to solve various bottlenecks generated by the current network facing new services by creating a new network interconnection concept based on the existing TCP/IP technical conditions.
The core idea of the method is to convert the packet forwarding process which is originally completely controlled by a Switch/router into independent processes which are respectively completed by an OpenFlow Switch (OpenFlow Switch) and a Controller (Controller).
What is actually done behind the transition is an alternation of the control authority: the flow direction of a data packet in a traditional network is manually specified, although a switch and a router have control rights, the concept of the data packet does not exist, and only the data packet level switching is carried out; in the OpenFlow network, a unified control server replaces routing, and determines transmission paths of all data packets in the network.
The OpenFlow switch maintains a Flow Table (Flow Table) different from the forwarding Table locally, and if the data packet to be forwarded has a corresponding item in the Flow Table, the data packet is directly and rapidly forwarded; if the flow table does not have the item, the data packet is sent to the control server to confirm the transmission path, and then is forwarded according to the issuing result.
Each flow entry of the OpenFlow switch has a priority field, which indicates the matching order of the flow entries. The value range of the priority is 0-65535. When the data packet is matched with the flow table, the flow table item with high priority is preferentially matched. The flow entry for which all fields are wildcarded (all field omitted) and for which the priority is equal to 0 is called a table-miss flow entry.
In IPv4, the IP address of a node uniquely identifies the node's access point in the network. Therefore, a node must be in the network represented by its IP address to accept messages sent to it; otherwise, the data packet sent to the node is not reachable. In order to keep the nodes continuously communicating during the movement, there are two methods: changing the access point while changing its IP address; host-based routing is used. Both of these approaches are generally undesirable. Mechanisms for mobile IP have therefore been proposed to address this problem.
Each node is uniquely identified by its home address, regardless of its access point in the network. When leaving the home network, the mobile node is assigned a care-of address (care-of address) indicating the mobile node's current location in the network. The mobile node registers a care-of address with a home agent (home agent) informing it of the location where it is now located. The home agent sends the data packet sent to the mobile node to the care-of address of the mobile node in a tunnel mode, and after the data packet reaches the other end of the tunnel, the data packet is forwarded to the mobile node.
Proxy Mobile IPv6 (PMIP) is a network-based regional mobility management scheme that does not require a Mobile node to participate in any IP mobility-related signaling flow. A mobile entity in the network tracks the movement of the mobile node and initiates the mobility signaling process and sets the necessary routing states. The core entities in PMIPv6 are LMA (LocalMobilty Anchor) and MAG (Mobile Access gateway).
The LMA is used for maintaining the access state of the MN and the home network prefix of the MN and is used for maintaining the connection of the home address of the MN with the network. The MAG is located on the access link as an access router. The MN is directly accessed to the MAG in the moving process, the MAG executes mobility management on behalf of the MN after detecting the access or moving information of the MN, and a binding registration message is sent to the LMA. MAG detects the state of MN, and represents MN to send and receive the binding message and the process of binding state establishment, thus reducing the signaling interaction of MN participating in switching, saving the bandwidth of wireless link and reducing the processing delay of signaling message.
Traditional mobility management schemes are mostly based on tunnel management mechanisms. In the mobile IP, the continuity of the service of the terminal in the moving process is realized by establishing a tunnel between a home agent and a foreign agent; and in the proxy mobile IPv6, the LMA and the MAG communicate by establishing a bidirectional tunnel. Therefore, the problems of triangular routing, tunnel state maintenance and the like are brought.
The triangular routing problem refers to that data packets sent to a mobile node MN are forwarded through a home agent or MAG, so that the workload of a router where the home agent or MAG of the mobile node MN is located is increased, and meanwhile, the routing of the data packets from a source address to a destination address is not an optimal path; tunnels between communicating entities require periodic maintenance of state information and, if necessary, removal.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a method for carrying out mobility management by utilizing an OpenFlow protocol, which distributes a flow table to enable MN to communicate with an opposite terminal through the perception of a Controller to the topology condition of the whole network; when the MN moves, the traditional tunnel management mechanism is abandoned, and the continuity of the communication between the MN and the opposite terminal is maintained by deleting the existing flow table and issuing the flow table again.
The technical scheme adopted by the invention for solving the technical problems is as follows:
a method for carrying out mobility management based on an OpenFlow protocol comprises the following steps:
step 1), a Controller maintains a corresponding relation table recorded with a plurality of OpenFlow switches with AP functions and port numbers connected to each gateway;
step 2) receiving identification information containing a mobile node MN and reported information of a first OpenFlow switch attached to the mobile node MN, wherein the identification information of the mobile node MN is an MAC address and/or an IP address of the mobile node, and the identification information is transmitted by the first OpenFlow switch with the AP function;
and 3) checking the corresponding relation table according to the report information, and executing different routing behaviors based on the identification information of the mobile node MN and the query result of the report information of the first OpenFlow switch attached to the mobile node MN.
Preferably, the method further comprises the following steps:
defining a field in the Vendor message to store the identification information of the mobile node MN; the Vendor message is sent to a Controller by an OpenFlow switch with an AP function; or,
defining a field in the Experimenter message to store the identification information of the mobile node MN; the identifier message is sent to the Controller by the OpenFlow switch having the AP function.
Preferably, the step 3) specifically includes: checking the corresponding relation table according to the reported information, wherein if the corresponding relation table has no information of the mobile MN;
the flow table corresponding to the mobile node is issued by the controller for other OpenFlow switches of the gateway of the network where the mobile node is located, so that the mobile node establishes communication with the mobile node of the opposite end.
Preferably, in step 3), the method further comprises:
if the reported information does not contain the IP address of the mobile node, the IP address is distributed to the mobile node MN according to the self DHCP function of the controller, and a flow table reaching the mobile node MN is added in a gateway corresponding to the IP address of the mobile node MN according to the corresponding relation among the IP address of the mobile node MN, the OpenFlow switch with the AP function and the port number of each gateway connected with the OpenFlow switch with the AP function.
Preferably, the Controller records a network address field corresponding to each gateway and an IP address and the number of IP addresses assignable to the mobile node MN in each network address field;
when the mobile node MN is judged to have no IP address, the Controller selects a network address segment with the maximum number of assignable IP addresses, selects an IP address from the IP addresses assignable to the mobile node MN in the network address segment, assigns the IP address to the MN and writes a DHCP OFFER data packet, and modifies the IP address and the number of the IP addresses assignable to the mobile node MN in the network address segment;
the method comprises the steps that a DHCP OFFER data Packet is packaged in a Packet _ out data Packet and sent to an OpenFlow switch with an AP function, and the OpenFlow switch with the AP function sends the DHCP OFFER data Packet to a mobile node MN;
the mobile node MN sends a DHCP REQUEST data Packet to the OpenFlow switch with the AP function, the OpenFlow switch with the AP function packages the DHCP REQUEST data Packet in a Packet _ in data Packet and sends the Packet _ in data Packet to a Controller, the Controller packages a DHCP ACK data Packet in a Packet _ out data Packet and sends the Packet _ out data Packet to the OpenFlow switch with the AP function, and the OpenFlow switch with the AP function sends the DHCP ACK data Packet to the mobile node MN; at this time, the mobile node MN acquires the IP address.
Preferably, step 3) specifically includes: checking the corresponding relation table according to the reported information, wherein if the corresponding relation table has the information of the mobile node;
and the attached OpenFlow switch is different from the newly reported OpenFlow switch, the record is deleted, and the information of the mobile node and the newly reported OpenFlow switch is used as a new record to be added into the corresponding relation table.
Preferably, the method further comprises the following steps:
the Controller and controllers of other domains maintain a corresponding relation table of the identification information of the mobile node MN and the attached OpenFlow switch with the AP function together, and the network address sections managed by the Controller and the controllers of other domains are different;
and the Controller judges whether the mobile node moves in a cross-domain or a region according to the IP address of the mobile node.
Preferably, the method further comprises the following steps:
if the mobile node MN is detected to move in the same area;
the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located, and simultaneously issues a new flow table corresponding to the mobile node for other OpenFlow switches of the gateway of the network where the mobile node is located, so that the communication between the mobile node and the opposite terminal is not interrupted.
Preferably, in step 3), the method further comprises:
if the mobile node MN is detected to move in a cross-domain mode, the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located;
and selecting a proper communication path according to the weighted value of the newly added network, and providing a flow table for all OpenFlow switches on the path next to the mobile node MN, so that the communication between the mobile node and the opposite terminal is not interrupted.
Preferably, the weighting factor of the newly added network selects a link state of each link and a load of each OpenFlow switch.
After the scheme is adopted, the traditional tunnel management mechanism is abandoned, the problem of triangular routing is well solved, and the extra overhead caused by tunnel state maintenance is avoided; the SDN technology is used, so that the management of the network is more convenient and flexible, and the mobility management can be effectively carried out by sensing the current position of the mobile node MN and flexibly controlling the flow table in each OpenFlow switch in the network controlled by the controller.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The present invention will be described in detail below with reference to the accompanying drawings so that the above advantages of the present invention will be more apparent. Wherein,
FIG. 1 is a network topology diagram of one embodiment of the present invention;
fig. 2 is a network topology diagram of another embodiment of the present invention.
Detailed Description
The following detailed description of the embodiments of the present invention will be provided with reference to the drawings and examples, so that how to apply the technical means to solve the technical problems and achieve the technical effects can be fully understood and implemented. It should be noted that, as long as there is no conflict, the embodiments and the features of the embodiments of the present invention may be combined with each other, and the technical solutions formed are within the scope of the present invention.
Additionally, the steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions and, although a logical order is illustrated in the flow charts, in some cases, the steps illustrated or described may be performed in an order different than here.
Specifically, in one embodiment of the present invention, based on OpenFlow implementation, the Controller senses the topology of the whole network and issues a flow table to enable the MN to communicate with an opposite terminal; when the MN moves, the traditional tunnel management mechanism is abandoned, and the continuity of the communication between the MN and the opposite terminal is maintained by deleting the existing flow table and issuing the flow table again.
Specifically, the detailed scheme of the invention is as follows:
the first embodiment is as follows:
a method for carrying out mobility management based on an OpenFlow protocol comprises the following steps:
step 1), a Controller maintains a corresponding relation table recorded with a plurality of OpenFlow switches with AP functions and port numbers connected to each gateway;
step 2) receiving identification information containing a mobile node MN and reported information of a first OpenFlow switch attached to the mobile node MN, wherein the identification information of the mobile node MN is an MAC address and/or an IP address of the mobile node, and the identification information is transmitted by the first OpenFlow switch with the AP function;
and 3) checking the corresponding relation table according to the report information, and executing different routing behaviors based on the identification information of the mobile node MN and the query result of the report information of the first OpenFlow switch attached to the mobile node MN.
Preferably, the method further comprises the following steps:
defining a field in the Vendor message to store the identification information of the mobile node MN; the Vendor message is sent to a Controller by an OpenFlow switch with an AP function; or,
defining a field in the Experimenter message to store the identification information of the mobile node MN; the identifier message is sent to the Controller by the OpenFlow switch having the AP function.
Preferably, the step 3) specifically includes: checking the corresponding relation table according to the reported information, wherein if the corresponding relation table has no information of the mobile MN;
the flow table corresponding to the mobile node is issued by the controller for other OpenFlow switches of the gateway of the network where the mobile node is located, so that the mobile node establishes communication with the mobile node of the opposite end.
Preferably, in step 3), the method further comprises:
if the reported information does not contain the IP address of the mobile node, the IP address is distributed to the mobile node MN according to the self DHCP function of the controller, and a flow table reaching the mobile node MN is added in a gateway corresponding to the IP address of the mobile node MN according to the corresponding relation among the IP address of the mobile node MN, the OpenFlow switch with the AP function and the port number of each gateway connected with the OpenFlow switch with the AP function.
Preferably, the Controller records a network address field corresponding to each gateway and an IP address and the number of IP addresses assignable to the mobile node MN in each network address field;
when the mobile node MN is judged to have no IP address, the Controller selects a network address segment with the maximum number of assignable IP addresses, selects an IP address from the IP addresses assignable to the mobile node MN in the network address segment, assigns the IP address to the MN and writes a DHCP OFFER data packet, and modifies the IP address and the number of the IP addresses assignable to the mobile node MN in the network address segment;
the method comprises the steps that a DHCP OFFER data Packet is packaged in a Packet _ out data Packet and sent to an OpenFlow switch with an AP function, and the OpenFlow switch with the AP function sends the DHCP OFFER data Packet to a mobile node MN;
the mobile node MN sends a DHCP REQUEST data Packet to the OpenFlow switch with the AP function, the OpenFlow switch with the AP function packages the DHCP REQUEST data Packet in a Packet _ in data Packet and sends the Packet _ in data Packet to a Controller, the Controller packages a DHCP ACK data Packet in a Packet _ out data Packet and sends the Packet _ out data Packet to the OpenFlow switch with the AP function, and the OpenFlow switch with the AP function sends the DHCP ACK data Packet to the mobile node MN; at this time, the mobile node MN acquires the IP address.
Preferably, step 3) specifically includes: checking the corresponding relation table according to the reported information, wherein if the corresponding relation table has the information of the mobile node;
and the attached OpenFlow switch is different from the newly reported OpenFlow switch, the record is deleted, and the information of the mobile node and the newly reported OpenFlow switch is used as a new record to be added into the corresponding relation table.
Preferably, the method further comprises the following steps:
the Controller and controllers of other domains maintain a corresponding relation table of the identification information of the mobile node MN and the attached OpenFlow switch with the AP function together, and the network address sections managed by the Controller and the controllers of other domains are different;
and the Controller judges whether the mobile node moves in a cross-domain or a region according to the IP address of the mobile node.
Preferably, the method further comprises the following steps:
if the mobile node MN is detected to move in the same area;
the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located, and simultaneously issues a new flow table corresponding to the mobile node for other OpenFlow switches of the gateway of the network where the mobile node is located, so that the communication between the mobile node and the opposite terminal is not interrupted.
Preferably, in step 3), the method further comprises:
if the mobile node MN is detected to move in a cross-domain mode, the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located;
and selecting a proper communication path according to the weighted value of the newly added network, and providing a flow table for all OpenFlow switches on the path next to the mobile node MN, so that the communication between the mobile node and the opposite terminal is not interrupted.
Preferably, the weighting factor of the newly added network selects a link state of each link and a load of each OpenFlow switch.
After the scheme is adopted, the traditional tunnel management mechanism is abandoned, the problem of triangular routing is well solved, and the extra overhead caused by tunnel state maintenance is avoided; the SDN technology is used, so that the management of the network is more convenient and flexible, and the mobility management can be effectively carried out by sensing the current position of the mobile node MN and flexibly controlling the flow table in each OpenFlow switch in the network controlled by the controller.
Example two:
the OpenFlow protocol is one of the basic protocols of Software Defined Networking (SDN). The communication between the controller and the OpenFlow switch should follow the OpenFlow protocol.
In addition, in order to enable an OpenFlow switch with an AP function to report information of a mobile node MN to a controller, in the embodiment of the present invention, a new message field is defined on the basis of an existing OpenFlow protocol message format:
specifically, under the version 1.0 of the OpenFlow protocol, a new field MN's MAC of 6 bytes 6 is defined in the vector message to store the identification information of the mobile node MN; the vector message is sent to the Controller by the OpenFlow switch with the AP function, and has the following structure:
| header | vendor | MN’s MAC |
specifically, under the version 1.3 of the OpenFlow protocol, a new field MN's MAC of 6 bytes is defined in the Experimenter message to store the identification information of the mobile node MN; the identifier message is sent to the Controller by the OpenFlow switch with AP function, and the identifier message has the following structure:
| header | experimenter | exp_type | MN’s MAC |
in this embodiment, a network managed by one controller is referred to as a domain, and fig. 1 and fig. 2 correspond to topologies of intra-domain mobility management and cross-domain mobility management, respectively, that is, in the embodiment of the present invention, research is mainly performed on the topologies shown in fig. 1 and fig. 2.
When the mobile node MN moves within a domain, as shown in fig. 1, s1 is a non-OpenFlow switch and does not need to be connected to the Controller; s2, s3, s4 are conventional OpenFlow switches, act as gateways, need to be connected to a Controller, but do not need to support a new OpenFlow protocol field mentioned in the patent, and the network address fields of s2, s3, s4 are A, B, C respectively;
s5, s6, s7 are OpenFlow switches with AP functionality, and need to connect with Controller, and support the new OpenFlow protocol fields mentioned in the patent.
When the mobile node MN moves across domains, as shown in fig. 2, s1, s2, s3, s4, s1 ', s 2', s3 ', and s 4' are all conventional OpenFlow switches, and need to be connected to the Controller; s2, s3, s4, s2 ', s3 ', s4 ' act as a gateway, and do not need to support new OpenFlow protocol fields mentioned in the patent, and the network address segments of s2, s3, s4, s2 ', s3 ', s4 ' are A, B, C, A ', B ', and C ', respectively; s5, s6, s7, s5 ', s6 ' and s7 ' are OpenFlow switches with AP functions, and need to be connected with a Controller, and need to support new OpenFlow protocol fields mentioned in the patent.
The Controller has a function of a DHCP server, and can allocate an IP address to the accessed mobile node MN, and the process is described as follows:
the Controller records the network address segment corresponding to each gateway and the IP address and the number of the IP addresses which can be allocated to the mobile node MN in each network address segment;
when receiving the address request of the mobile node MN, the Controller selects the network address field with the maximum number of assignable IP addresses, selects an IP address from the IP address which can be assigned to the mobile node MN in the network address field and assigns the IP address to the MN, and modifies the IP address and the number of the IP addresses which can be assigned to the mobile node MN in the network address field;
the mobile node MN sends a DHCP DISCOVER data Packet to an OpenFlow switch with an AP function to request an IP address, the OpenFlow switch with the AP function packages the DHCP DISCOVER data Packet in a Packet _ in data Packet and sends the Packet to a Controller, the Controller selects an IP address, writes the IP address into a DHCP OFFER data Packet, packages the DHCP OFFER data Packet in a Packet _ out data Packet and sends the Packet to the OpenFlow switch with the AP function, and the OpenFlow switch with the AP function sends the DHCP OFFER data Packet to the mobile node MN;
the mobile node MN sends a DHCP REQUEST data Packet to the OpenFlow switch with the AP function, the OpenFlow switch with the AP function packages the DHCP REQUEST data Packet in a Packet _ in data Packet and sends the Packet _ in data Packet to a Controller, the Controller packages a DHCP ACK data Packet in a Packet _ out data Packet and sends the Packet _ out data Packet to the OpenFlow switch with the AP function, and the OpenFlow switch with the AP function sends the DHCP ACK data Packet to the mobile node MN; at this time, the mobile node MN acquires the IP address.
Before mobility management is performed, some necessary initialization configuration needs to be performed on the network.
In fig. 1, 4 pieces of routing information are configured in the non-OpenFlow switch s1, so that a packet addressed to s2, s3, s4, CN can be sent out from a corresponding interface;
a traditional OpenFlow switch in the network is connected with a Controller, the Controller issues two flow tables for the traditional OpenFlow switch, one flow table sends a data packet sent to a gateway address of the traditional OpenFlow switch to a LOCAL interface, and the other flow table sends the data packet in the network, the destination address of which is not the gateway address of the traditional OpenFlow switch, to s 1;
the OpenFlow switch with the AP function in the network is connected with a Controller, the Controller issues three flow tables for the OpenFlow switch with the AP function, the three flow tables respectively judge the source address of the received data packet, check which network the source address belongs to in s2, s3 and s4, and then send the source address from the corresponding port.
In fig. 2, 7 initialization flow tables are configured in the conventional OpenFlow switches s1 and s1 ', respectively, so that data packets addressed to s2, s3, s4, s 2', s3 ', s 4', and CN can be sent out from the corresponding interfaces.
s2, s3, s4, s2 ', s3 ', s4 ' are connected with a Controller, the Controller1 and the Controller2 respectively issue two flow tables for s2, s3, s4, s2 ', s3 ' and s4 ', one flow table sends a data packet addressed to the gateway address of the traditional OpenFlow switch to the LOCAL interface, and the other flow table sends a data packet in the network corresponding to the gateway address of the traditional OpenFlow switch, wherein the destination address of the data packet is not the gateway address of the traditional OpenFlow switch, to s1 and s1 '. The OpenFlow switch with the AP function in the network is connected with a Controller, the Controller issues three flow tables for the OpenFlow switch with the AP function, the three flow tables respectively judge the source addresses of received data packets, the source addresses of the received data packets belong to the networks of s2, s3 and s4 in a first area, the source addresses of the data packets belong to the networks of s2 ', s3 ' and s4 ' in a second area, and the data packets are sent out from corresponding ports.
The priority of the flow table entry at the time of initial configuration is set to 1 to avoid conflict with the flow table added in the mobility management. s2, s3, s4, s2 ', s3 ' and s4 ' each have a buffer area, which can buffer the communication data in the process of moving and modifying the flow table by the mobile node MN and send the data after the movement is completed, so as to maintain the continuity of the communication.
Example three:
the intra-domain mobility management workflow is as follows:
when sensing the attachment of the MN, the OpenFlow switch having the AP function actively reports the identification information (MAC address, IP address, etc.) of the MN and the AP to which the MN is attached to the controller. If the mobile node is detected to have no IP address, the IP address needs to be acquired through the DHCP function of the controller.
The Controller records a corresponding relationship between an OpenFlow switch with an AP function and a port number of each gateway to which the OpenFlow switch with the AP function is connected, and adds a flow table to the gateway corresponding to the IP address of the mobile node MN according to the corresponding relationship between the IP address of the mobile node MN, the port number of each gateway to which the OpenFlow switch with the AP function and the OpenFlow switch with the AP function are connected, after the Controller assigns an IP address to the mobile node MN.
The controller records a corresponding relation table of an MN in a network controlled by the controller and an OpenFlow switch with an AP function attached to the MN, and after the controller receives reported information of the OpenFlow switch with the AP function, the controller checks the corresponding relation table;
if the information of the MN is not included in the correspondence table, which indicates that the MN is a host newly added to the network, the MN and the corresponding OpenFlow switch having the AP function are recorded. Meanwhile, the controller issues a flow table corresponding to the mobile node for an OpenFlow switch of a gateway of a network where the mobile node is located, so that the mobile node MN establishes communication with a mobile node CN of an opposite terminal.
If the corresponding relation table already contains the information of the mobile node, the attached OpenFlow switch is different from the newly reported one, the record is deleted, and the information of the mobile node and the newly reported OpenFlow switch is taken as a new record to be added into the corresponding relation table; meanwhile, the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located, and simultaneously issues a new flow table corresponding to the mobile node for the OpenFlow switch of the gateway of the network where the mobile node is located, so that the communication between the mobile node and the opposite terminal is not interrupted.
Example four:
the cross-domain mobility management workflow is as follows:
when sensing the attachment of the MN, the OpenFlow switch having the AP function actively reports the identification information (MAC address, IP address, etc.) of the MN and the AP to which the MN is attached to the controller. If the mobile node is detected to have no IP address, the IP address needs to be acquired through the DHCP function of the controller.
The Controller records a corresponding relationship between an OpenFlow switch with an AP function and a port number of each gateway to which the OpenFlow switch with the AP function is connected, and adds a flow table to the gateway corresponding to the IP address of the mobile node MN according to the corresponding relationship between the IP address of the mobile node MN, the port number of each gateway to which the OpenFlow switch with the AP function and the OpenFlow switch with the AP function are connected, after the Controller assigns an IP address to the mobile node MN.
The controllers in the two domains maintain identification information of a mobile node MN and a corresponding relation table of an attached OpenFlow switch with an AP function together, and after the reported information of the OpenFlow switch with the AP function is received, the controllers check the corresponding relation table;
if the information of the MN is not included in the correspondence table, which indicates that the MN is a host newly added to the network, the MN and the corresponding OpenFlow switch having the AP function are recorded. Meanwhile, the controller issues a flow table corresponding to the mobile node for an OpenFlow switch of a gateway of a network where the mobile node is located, so that the mobile node establishes communication with the mobile node at the opposite end.
And if the corresponding relation table already contains the information of the mobile node, the attached OpenFlow switch is different from the newly reported one, deleting the record, and adding the information of the mobile node and the newly reported OpenFlow switch as a new record into the corresponding relation table.
The network address segments managed by controllers 1 and 2 are A, B, C and a ', B ' and C ', respectively. If the mobile node MN is detected to move in the same area, the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located, and simultaneously issues a new flow table corresponding to the mobile node for the OpenFlow switch of the gateway of the network where the mobile node is located, so that the communication between the mobile node and the opposite terminal is not interrupted; if the mobile node MN is detected to move across domains, the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located, selects a proper communication path with the CN according to the weighted value of the newly added network (such as the link state of each link, the load of each OpenFlow switch and the like), and enables the communication between the mobile node and the opposite terminal not to be interrupted for the next flow table aiming at the mobile node MN of the OpenFlow switch on the path.
That is, the present invention records, in the controller, the correspondence table between the mobile node MN and the OpenFlow switch OVS AP having an AP function, and the OpenFlow switch in which the flow table of the mobile node MN exists in the network, and implements mobility management by the OpenFlow protocol.
The traditional tunnel management mechanism is abandoned, the problem of triangular routing is well solved, and the extra overhead caused by tunnel state maintenance is avoided; and the SDN technology is used, so that the management of the network is more convenient and flexible.
It should be noted that for simplicity of description, the above method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects.
Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Finally, it should be noted that: although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that changes may be made in the embodiments and/or equivalents thereof without departing from the spirit and scope of the invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (4)
1. A method for carrying out mobility management based on an OpenFlow protocol comprises the following steps:
step 1), a Controller maintains a corresponding relation table recorded with a plurality of OpenFlow switches with AP functions and port numbers connected to each gateway;
step 2) receiving identification information containing a mobile node MN and reported information of a first OpenFlow switch attached to the mobile node MN, wherein the identification information of the mobile node MN is an MAC address and/or an IP address of the mobile node, and the identification information is transmitted by the first OpenFlow switch with the AP function;
step 3) checking the corresponding relation table according to the report information, and executing different routing behaviors based on the identification information of the mobile node MN and the query result of the report information of the first OpenFlow switch attached to the mobile node MN;
the step 3) specifically comprises the following steps: checking the corresponding relation table according to the reported information, wherein if the corresponding relation table has no information of the mobile MN;
recording the mobile node and the attached first OpenFlow switch, and simultaneously issuing a flow table corresponding to the mobile node for other OpenFlow switches of a gateway of a network where the mobile node is located by the controller to enable the mobile node to establish communication with the mobile node of the opposite end;
in step 3), further comprising:
if the reported information does not contain the IP address of the mobile node, the IP address is distributed to the mobile node MN according to the self DHCP function of the controller, and a flow table reaching the mobile node MN is added in a gateway corresponding to the IP address of the mobile node MN according to the corresponding relation of the IP address of the mobile node MN, an OpenFlow switch with an AP function and the port number of each gateway connected with the OpenFlow switch with the AP function;
the Controller records the network address field corresponding to each gateway and the IP address and the number of the IP addresses which can be allocated to the mobile node MN in each network address field;
when the mobile node MN is judged to have no IP address, the Controller selects a network address segment with the maximum number of assignable IP addresses, selects an IP address from the IP addresses assignable to the mobile node MN in the network address segment, assigns the IP address to the MN and writes a DHCP OFFER data packet, and modifies the IP address and the number of the IP addresses assignable to the mobile node MN in the network address segment;
the method comprises the steps that a DHCP OFFER data Packet is packaged in a Packet _ out data Packet and sent to an OpenFlow switch with an AP function, and the OpenFlow switch with the AP function sends the DHCP OFFER data Packet to a mobile node MN;
the mobile node MN sends a DHCP REQUEST data Packet to the OpenFlow switch with the AP function, the OpenFlow switch with the AP function packages the DHCP REQUEST data Packet in a Packet _ in data Packet and sends the Packet _ in data Packet to a Controller, the Controller packages a DHCP ACK data Packet in a Packet _ out data Packet and sends the Packet _ out data Packet to the OpenFlow switch with the AP function, and the OpenFlow switch with the AP function sends the DHCP ACK data Packet to the mobile node MN; at this time, the mobile node MN acquires an IP address; further comprising:
defining a field in the Vendor message to store the identification information of the mobile node MN; the Vendormessage is sent to a Controller by an OpenFlow switch with an AP function; or,
defining a field in the Experimenter message to store the identification information of the mobile node MN; the Experimenter message is sent to a Controller by an OpenFlow switch with an AP function; in the step 3), the method specifically comprises the following steps: checking the corresponding relation table according to the reported information, wherein if the corresponding relation table has the information of the mobile node;
and the attached OpenFlow switch is different from the newly reported OpenFlow switch, the record is deleted, and the information of the mobile node and the newly reported OpenFlow switch is taken as a new record to be added into the corresponding relation table; in step 3), further comprising:
if the mobile node MN is detected to move in a cross-domain mode, the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located;
and selecting a proper communication path according to the weighted value of the newly added network, and providing a flow table for all OpenFlow switches on the path next to the mobile node MN, so that the communication between the mobile node and the opposite terminal is not interrupted.
2. The method for mobility management based on the OpenFlow protocol of claim 1, further comprising:
the Controller and controllers of other domains maintain a corresponding relation table of the identification information of the mobile node MN and the attached OpenFlow switch with the AP function together, and the network address sections managed by the Controller and the controllers of other domains are different;
and the Controller judges whether the mobile node moves in a cross-domain or a region according to the IP address of the mobile node.
3. The method for mobility management based on the OpenFlow protocol of claim 1, further comprising:
if the mobile node MN is detected to move in the same area;
the controller deletes the flow table corresponding to the mobile node in the OpenFlow switch of the gateway of the network where the mobile node is located, and simultaneously issues a new flow table corresponding to the mobile node for other OpenFlow switches of the gateway of the network where the mobile node is located, so that the communication between the mobile node and the opposite terminal is not interrupted.
4. The method for mobility management based on the OpenFlow protocol of claim 1, wherein the weighting factor of the newly added network selects a link state of each link and a load of each OpenFlow switch.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510069728.4A CN104717142B (en) | 2015-02-10 | 2015-02-10 | Method for carrying out mobility management based on OpenFlow protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510069728.4A CN104717142B (en) | 2015-02-10 | 2015-02-10 | Method for carrying out mobility management based on OpenFlow protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104717142A CN104717142A (en) | 2015-06-17 |
| CN104717142B true CN104717142B (en) | 2020-01-10 |
Family
ID=53416121
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510069728.4A Expired - Fee Related CN104717142B (en) | 2015-02-10 | 2015-02-10 | Method for carrying out mobility management based on OpenFlow protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104717142B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106411972A (en) * | 2015-07-29 | 2017-02-15 | 中国科学院沈阳自动化研究所 | Real-time data distribution system and method based on Openflow protocol |
| CN106790734B (en) * | 2016-01-29 | 2021-04-30 | 新华三技术有限公司 | Network address allocation method and device |
| CN106027527B (en) * | 2016-05-23 | 2019-04-12 | 华中科技大学 | A kind of anonymous communication method based on SDN environment |
| CN106506371A (en) * | 2016-11-11 | 2017-03-15 | 清华大学 | The detached IP mobility treating methods of ID/Locator and device based on OpenFlow agreements |
| CN107135282A (en) * | 2017-04-12 | 2017-09-05 | 清华大学 | A kind of internet mobility method based on SDN |
| CN113055968A (en) * | 2019-12-26 | 2021-06-29 | 国网山西省电力公司信息通信分公司 | SDN-based IPV6 network layer mobility management method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101330460A (en) * | 2008-05-13 | 2008-12-24 | 武汉理工大学 | New construction model and routing method for mobile IP |
| CN103369613A (en) * | 2013-07-05 | 2013-10-23 | 中国科学院计算机网络信息中心 | System and method for realizing mobile switching based on Open Flow |
| CN104065764A (en) * | 2014-07-05 | 2014-09-24 | 中国科学技术大学 | Mobility management system based on address substitution in software-defined network |
| CN104104744A (en) * | 2014-07-09 | 2014-10-15 | 杭州华三通信技术有限公司 | IP address assignment method and device |
-
2015
- 2015-02-10 CN CN201510069728.4A patent/CN104717142B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101330460A (en) * | 2008-05-13 | 2008-12-24 | 武汉理工大学 | New construction model and routing method for mobile IP |
| CN103369613A (en) * | 2013-07-05 | 2013-10-23 | 中国科学院计算机网络信息中心 | System and method for realizing mobile switching based on Open Flow |
| CN104065764A (en) * | 2014-07-05 | 2014-09-24 | 中国科学技术大学 | Mobility management system based on address substitution in software-defined network |
| CN104104744A (en) * | 2014-07-09 | 2014-10-15 | 杭州华三通信技术有限公司 | IP address assignment method and device |
Non-Patent Citations (1)
| Title |
|---|
| "基于OpenFlow技术实现移动通信的方法";崔大凯，葛敬国等;《计算机应用》;20131231;第14-15页以及图4，表1-2 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104717142A (en) | 2015-06-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104717142B (en) | Method for carrying out mobility management based on OpenFlow protocol | |
| US7706301B2 (en) | Routing in a data communication network | |
| EP3949270B1 (en) | Local user plane function control | |
| KR101364402B1 (en) | Network based on identity identifier and location separation architecture, backbone network, and network element thereof | |
| US7447800B2 (en) | Mobile router device, mobile network system, and mobility management method of mobile router device | |
| EP1206098B1 (en) | Home agent and IP packet transferring method | |
| CN103152726B (en) | Multi-protocol association and topology detection in eHRPD network | |
| CN102256236B (en) | System and method for mobility management under separate mapping mechanism | |
| US20050232146A1 (en) | System and method for recovering a damaged routing path in a mobile network | |
| Cominardi et al. | Distributed mobility management solutions for next mobile network architectures | |
| CN104065764A (en) | Mobility management system based on address substitution in software-defined network | |
| CN104301445A (en) | Mobile Internet data transmission method and system | |
| CN101111067A (en) | Mobile terminal and communication method for gateway access | |
| US9253623B2 (en) | Method, system, mapping forward server and access router for mobile communication controlling | |
| CN116368860A (en) | Network layer support for 5G edge computing sticky traffic | |
| JP5655018B2 (en) | Handover processing system and gateway router | |
| CN109743726B (en) | Method for sharing static terminal in LTE system roaming scene | |
| US9629059B2 (en) | Mobile node registration method, intercommunication method, switching method and network element | |
| KR101680137B1 (en) | Sdn-based terminal mobility management framework and management methof thereof | |
| WO2021179935A1 (en) | Route determination method, apparatus and network device | |
| CN114157724B (en) | Identity/position identification hybrid forwarding method based on source route | |
| US20090147759A1 (en) | Method and apparatus for supporting mobility of node using layer 2/layer 3 addresses | |
| Yaseen et al. | Smart virtualization packets forwarding during handover for beyond 5G networks | |
| KR20120104331A (en) | Method and system for routing data to a mobile node in a foreign network | |
| Chen et al. | SDN-enabled session continuity for wireless networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | 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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200110 Termination date: 20210210 |