Claims:
We claim:
1. A wireless MANET routing system, comprising an application plane, a control plane and a data plane, wherein the application plane comprises routing, data application, strategy, load balancing, security, and QoS; the control plane comprises a control plane of a mobile SDN controller and a control plane of a mobile node, the control plane of the mobile SDN controller comprises a connection management unit, a topology learning unit, a forwarding management unit and an OpenFlow message compression and decompression unit, and the control plane of the mobile node MN comprises an OpenFlow message compression and decompression local adaptation controller LAC and a flow table FT; the data plane has the functions of forwarding an incoming media streams and one of compressing and decompressing packet headers based on the flow table FT rules.

2. The system as claimed in claim 1, wherein the mobile SDN controller performs at least one of hosting data applications and relay data packets, selecting network routes as a routing function of an application inside the mobile SDN, and sending a route update RU to all other mobile nodes in the network.

3. The system as claimed in claim 1, wherein the connection management unit is configured to maintain a route associated with a mobile, the mobile node maintains a route from itself to the mobile SDN controller so as to send a corresponding control message.

4. The system as claimed in claim 1, wherein the topology learning unit is configured to provide the mobile SDN controller with the functionality to perform one of learn and collect, or maintain information about the number of mobile nodes in the MANET network and connectivity between the nodes.

5. The system as claimed in claim 1, wherein the forwarding management unit is used by the mobile SDN controller to send routes, prepare a flow table FT using the selected route and send it to the node as a route update RU message.

6. The system as claimed in claim 1, wherein the system comprises an application connected to the mobile SDN controller through a northbound interface to provide policies to the mobile SDN controller to determine network routes and make decisions regarding at least one of load balancing, QoS, and firewalls.

7. The system as claimed in claim 1, wherein the mobile SDN controller compresses and decompresses the headers of the media data packets of an application and media data packets of applications from the mobile node MN before transmitting.

8. The system as claimed in claim 1, wherein a mobile node includes a flow table, enabled forwarding device FD, wherein the flow table comprises at least one of rules for forwarding flows received from an application or from another mobile node MN. , Description:FORM 2
THE PATENTS ACT 1970
[39 OF 1970]
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
[See section 10 and rule 13]

TITLE: “A WIRELESS MANET ROUTING SYSTEM”
Name and Address of the Applicants:
1. S. R. M. KRISHNA; Professor, Department of CSE, Lords Institute of Engineering and Technology, Survey No. 32, Near Police Academy, Appa Junction, Himayathsagar, Hyderabad, Telangana 500091; Nationality: Indian;
2. S. POTHALAIAH; Professor, Department of ECE, Vignana Bharathi Institute of Technology, Aushapur, Ghatkesar, near HPCL, Hyderabad, Telangana 501301; Nationality: Indian;
3. M. AMRU; Professor, Department of ECE, CMR Engineering College, Kandlakoya(v), Medchal Road, Hyderabad, Telangana, INDIA-501401; Nationality: Indian;
4. S. RAMA KISHORE REDDY; Associate Professor, Department of ECE, CMR Engineering College, Kandlakoya(v), Medchal Road, Hyderabad, Telangana, INDIA-501401; Nationality: Indian; and
5. G. CHANDRAIAH; Professor, Department of ECE, Sri Venkateswara Engineering College, Karakambadi Rd, Mangalam, Tirupati, Andhra Pradesh 517502; Nationality: Indian.

The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
The present invention is generally related to Mobile Ad-hoc NETworks (MANET) routing protocol optimization and more specifically, to a system to route adaptively for reducing the load of the node in the MANET.

BACKGROUND
Currently, MANET wireless ad hoc networks are used in many areas of communications. As the nodes in a network move around from time to time, the topology of the MANET network has the characteristic of changing dynamically. Although the computing speed of processors, the bandwidth of wireless nodes and storage has advanced significantly with the evolution of technology, the data traffic carried by the entire network has also increased explosively. There are always some central nodes in the network topology change process, and these central nodes will usually process more task requests than general nodes as relay nodes. If a rational planning method is not adopted, the central node needs to process a longer transmission queue such as to increase the delay and packet loss of the whole network, the central node may stop working because energy is exhausted in advance, and the existence of the central node is likely to be the target of malicious attack. Due to the condition limitations of the volume, the battery capacity, the cost and the like of the wireless node, the design of the method for reducing the load of the central node has important significance.

Conventional MANET routing protocols consists of table driven and on demand protocols that are triggered when a source node and a destination node need to communicate, and which require periodic exchanges of routing information.

A node in the table driven routing protocol maintains a topology table generated based on the position of the node, and the table contains routing information from the node to other nodes in the network. When the topological structure changes, the routing information is updated among the nodes, so that the routing table is kept in the latest state. Common table-driven protocols are the DSDV, OLSR, GSR protocols and protocols derived based on these protocols. Designers often keep some redundant routes in place to deal with an emergency when designing a protocol. The traditional MANET table driven routing protocol is based on the routing with the minimum hop count, and although redundant routing exists, the problem of overlarge load of some nodes is avoided.

There are techniques or methods for reducing the load of nodes. For example, a load balancing method for routers, which is to form a virtual router group by a plurality of entity routers, determine one entity router as a master router, and the rest entity routers as backup routers, where the master router is used to respond and forward data packets, and the backup routers are in a standby state; setting a flow threshold value and monitoring the load flow of the master control router; the invention segments the whole topological structure, and the main router distributes flow when reaching the threshold, thus limiting the selection of the node for searching the optimal route, increasing the total cost of the whole network and having weak universality.

Another method provides a routing method based on load sensing of distributed networks. This method calculates the path normalization network load of the alternative path, and selects the path with low network load to forward the data packet. The method cannot avoid the phenomenon that the load of the cross nodes in a plurality of routes is too high under a larger topological model and is easy to fall into local optimum, and the method needs to calculate all possible paths and has larger calculation amount.

Although the methods can reduce the overhead, the resource wastage is huge and serious, the calculation amount is large, and the universality is not high.

SUMMARY
The shortcomings of the prior art are overcome and additional advantages are provided through the provision of method of the present disclosure.

Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.

In an aspect of the present disclosure, a wireless MANET routing system is provided. The system comprises an application plane, a control plane, and a data plane. The application plane includes routing, data application, security, load balancing, policy, QoS; the control plane includes the control plane of the mobile SDN controller MSC and the control plane of the mobile node MN, and the control plane of the mobile SDN controller MSC includes Connection management unit, topology learning unit, forwarding management unit, and OpenFlow message compression and decompression. The control plane of the mobile node includes OpenFlow message compression and decompression LAC and flow table; The media stream is forwarded and the packet header is compressed/decompressed packet headers according to the flow table rules.

The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, compendia, and features described above, further aspects, compendia, and features will become apparent by reference to the drawings and the following detailed description.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of device or system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
Figure 1 is a block diagram of a routing architecture, in accordance with an embodiment of the present disclosure.

The figures depict embodiments of the disclosure for purpose of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.

DETAILED DESCRIPTION
In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a device or system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the device or system or apparatus.

The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise. The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise.

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The present disclosure provides a wireless Mobile Ad-hoc NETworks (MANET) system or wireless MANET routing architecture. The wireless system comprising three basic layers: the system comprises an application plane, a control plane and a data plane, wherein the application plane comprises routing, data application, security, load balancing, strategy and QoS; the control plane comprises a control plane of a mobile SDN controller MSC and a control plane of a mobile node MN, the control plane of the mobile SDN controller MSC comprises a connection management unit, a topology learning unit, a forwarding management unit and OpenFlow message compression and decompression, and the control plane of the mobile node MN comprises an OpenFlow message compression and decompression LAC and a flow table FT; the data plane has the functions of forwarding incoming media streams and compressing/decompressing packet headers according to the flow table FT rules.

In another embodiment of the present disclosure, the mobile SDN controller MSC in the mobile node MN is responsible for hosting data applications and relaying data packets, the routing function implemented as an application inside the mobile SDN controller MSC is responsible for selecting network routes and sending route update RUs to all other mobile nodes MN in the network, the mobile SDN controller MSC continuously collects connectivity information of all mobile nodes MN and learns network topology, and each mobile node MN maintains a route to the mobile SDN controller MSC to receive the connectivity information.

In another embodiment of the present disclosure, the connection management unit is responsible for assisting each mobile node MN to maintain a route to itself, so that in case of frequent change of MANET topology, the mobile node MN can still maintain a route to the mobile SDN controller MSC for sending corresponding control messages.

In an embodiment of the present disclosure, said topology learning unit provides the mobile SDN controller MSC with the function of learning/collecting and maintaining a global view of the MANET network it manages, this view being information about the number of mobile nodes MN in the MANET network and the connectivity between the nodes.

In an embodiment of the present disclosure, the forwarding management unit is for use by the mobile SDN controller MSC in sending routes, preparing a flow table FT using the selected route and sending it to the node as a route update RU message, flow table FT information contained in the route update RU message being usable by the local adaptation controller LAC of the mobile node MN for installing in its flow table FT media flow routes FR that follow the OpenFlow message format for flow-based forwarding, routes currently installed in the node flow table FT being maintained in a centralized repository of the mobile SDN controller MSC, which information is part of the network state information maintained at the mobile SDN controller MSC.

It is further included that the application connected to the mobile SDN controller MSC through the northbound interface provides policies so that the mobile SDN controller MSC can determine network routes and make decisions regarding load balancing, QoS, firewalls.

The mobile SDN controller MSC compresses and decompresses the headers of the media data packets of its own application and the media data packets of the application from the mobile node MN/other mobile SDN controller MSC node, and then forwards them.

It is further included that each mobile node MN has a flow table FT, similar to the OpenFlow-enabled forwarding device FD, which contains rules for forwarding flows received from an application or from another mobile node MN, the mobile node MN routing application communicates with routing applications in other mobile nodes MN using the UDP protocol, and updates the flow table FT routing entries.
As a further preferable mode of the present disclosure, in a standard SDN architecture, each forwarding device has an agent for communicating with an SDN controller using an OpenFlow protocol and installing flow table FT routing, and in the routing architecture, each forwarding device node has a local adaptation controller LAC having a similar function, and communication between the mobile SDN controller MSC and the local adaptation controller LAC uses a custom local protocol instead of the OpenFlow protocol, and the local adaptation controller LAC converts routing information sent by the mobile SDN controller MSC into OpenFlow messages used by the flow table FT.

In an embodiment of the present disclosure, compared with the prior art, the disclosure has the benefits such as, but not limited to the MANET routing system structure provided by the disclosure does not need the position service support for tracking the position of the node, reduces the size of Openflow information by a compression and decompression method, and saves the empty resource of the node.

Referring to Figure 1, the present disclosure provides a technical solution that a wireless MANET routing system or architecture, said wireless MANET routing system comprising three basic layers: the system comprises an application plane, a control plane and a data plane, wherein the application plane comprises routing, data application, safety, load balance, strategy, QoS and the like; the control plane comprises a control plane of a mobile SDN controller MSC and a control plane of a mobile node MN, the control plane of the mobile SDN controller MSC comprises a connection management unit, a topology learning unit, a forwarding management unit and OpenFlow message compression and decompression, and the control plane of the mobile node MN comprises an OpenFlow message compression and decompression LAC and a flow table FT; the data plane has the functions of forwarding incoming media streams and compressing/decompressing packet headers according to the flow table FT rules.

A mobile SDN controller MSC in the mobile node MN is responsible for hosting data applications and relay data packets, and is responsible for selecting network routes as a routing function implemented by an application inside the mobile SDN controller MSC, and sending a route update RU to all other mobile nodes MN in the network, the mobile SDN controller MSC continuously collects connectivity information of all mobile nodes MN and learns network topology, and each mobile node MN maintains a route to the mobile SDN controller MSC to receive the connectivity information.

The connection management unit is responsible for helping each mobile node MN maintain a route to itself, so that under the condition of frequent change of MANET topology, the mobile node MN can still maintain a route from itself to the mobile SDN controller MSC so as to send a corresponding control message.

The topology learning unit provides the mobile SDN controller MSC with the functionality to learn/collect and maintain a global view of the MANET network it manages, which is information about the number of mobile nodes MN in the MANET network and connectivity between the nodes.

The forwarding management unit is used by the mobile SDN controller MSC to send routes, prepare a flow table FT using the selected route and send it to the node as a route update RU message, flow table FT information contained in the route update RU message may be used by the local adaptation controller LAC of the mobile node MN to install in its flow table FT a media flow route FR that is flow-based forwarded following an OpenFlow message format, routes currently installed in the node flow table FT being maintained in a centralized repository of the mobile SDN controller MSC, which is part of network state information maintained at the mobile SDN controller MSC.

It is also included that an application connected to the mobile SDN controller MSC through a northbound interface provides policies so that the mobile SDN controller MSC can determine network routes and make decisions regarding load balancing, QoS, firewalls, etc.

The method also comprises that the mobile SDN controller MSC compresses and decompresses the headers of the media data packets of its own application and the media data packets of applications from the mobile node MN/other mobile SDN controller MSC nodes before forwarding them.

It is further included that each mobile node MN has a flow table FT, similar to the OpenFlow enabled forwarding device FD, which flow table FT contains rules for forwarding flows received from an application or from another mobile node MN, which mobile node MN routing application communicates with routing applications in other mobile nodes MN using UDP protocol and updates the flow table FT routing entries.

The method also comprises the steps that in a standard SDN system structure, each forwarding device is provided with an agent used for communicating with the SDN controller by using an OpenFlow protocol and installing flow table FT routing, in the routing system structure, each forwarding device node is provided with a local adaptive controller LAC with similar functions, communication between the mobile SDN controller MSC and the local adaptive controller LAC uses a self-defined local protocol instead of the OpenFlow protocol, and the local adaptive controller LAC converts routing information sent by the mobile SDN controller MSC into OpenFlow messages used by the flow table FT.

In summary, the MANET routing architecture provided by the present disclosure does not need location service support for tracking node location, reduces the size of Openflow messages by compression and decompression methods, and saves the empty resources of nodes.

While there have been shown and described what are at present considered the fundamental principles and essential features of the disclosure and its advantages, it will be apparent to those skilled in the art that the disclosure is not limited to the details of the foregoing exemplary embodiments, but is capable of other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the disclosure being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.

Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.