WO2013003751A1

WO2013003751A1 - Methods for using embedded client location information for network management and devices thereof

Info

Publication number: WO2013003751A1
Application number: PCT/US2012/044995
Authority: WO
Inventors: Daniel J. MATTE
Original assignee: F5 Networks, Inc.
Priority date: 2011-06-30
Filing date: 2012-06-29
Publication date: 2013-01-03
Also published as: TW201306521A; TWI591979B

Abstract

A method, non-transitory computer readable medium, and device for using embedded client location information for network management includes obtaining at a network management computing device traffic comprising at least one network packet which includes a header and a payload. Client location information embedded in the header of the at least one network packet is extracted with the network management computing device. At least one network management action is executed with the network management computing device based on the extracted client location information from the at least one packet.

Description

METHODS FOR USING EMBEDDED CLIENT LOCATION INFORMATION FOR NETWORK MANAGEMENT AND

DEVICES THEREOF

[0001] This application claims the benefit of U.S. Provisional Patent

Application Serial No. 61/503,484 filed June 30, 2011, which is hereby incorporated by reference in its entirety.

FIELD

[0002] This technology generally relates to methods and devices for network management and, more particularly, to methods, non-transitory computer readable medium and devices that use embedded client location information for network management.

BACKGROUND

[0003] Internet network management, also known as application network management, refers to tools that monitor the flow of Web application traffic over a network. These tools route traffic among multiple devices within a network, limiting delays and freeing bandwidth. Unfortunately, currently there is no mechanism for quickly and easily extracting location as well as date and time of creation from a network packet to take one or more actions for network management.

SUMMARY

[0004] A method for using embedded client location information for network management includes obtaining at a network management computing device traffic comprising at least one network packet which includes a header and a payload.

Client location information embedded in the header of the at least one network packet is extracted with the network management computing device. At least one network management action is executed with the network management computing device based on the extracted client location information from the at least one packet. [0005] A non-transitory computer readable medium having stored thereon instructions for using embedded client location information for network management comprising machine executable code which when executed by at least one processor, causes the processor to perform steps including obtaining traffic comprising at least one network packet which includes a header and a payload. Client location information embedded in the header of the at least one network packet is extracted and at least one network management action is executed based on the extracted client location information from the at least one packet.

[0006] A network management device includes at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory including obtaining traffic comprising at least one network packet which includes a header and a payload. Client location information embedded in the header of the at least one network packet is extracted and at least one network management action is executed based on the extracted client location information from the at least one packet.

[0007] A method for embedding client location information for network management includes obtaining at a network management computing device traffic comprising at least one network packet comprising a header and a payload. Client location information in payload of the at least one network packet is extracted with the network management computing device. Client location information in a header of the at least one network packet is embedded with the network management computing device.

[0008] A non-transitory computer readable medium having stored thereon instructions for embedding client location information for network management comprising machine executable code which when executed by at least one processor, causes the processor to perform steps including obtaining at traffic comprising at least one network packet comprising a header and a payload. Client location information

10039413-1 in payload of the at least one network packet is extracted. Client location information in a header of the at least one network packet is embedded.

[0009] A network management device includes at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory including obtaining at traffic comprising at least one network packet comprising a header and a payload. Client location information in payload of the at least one network packet is extracted. Client location information in a header of the at least one network packet is embedded [0010] This technology provides more effective methods, non-transitory computer readable medium and devices for network management by using embedded client location information in network packets. With this technology, client location information is placed in a header of a TCP/IP packet where it is easily accessible by a network management device without the need for decryption. As a result, this technology enables the network management device to quickly and easily take one or more value added actions based on this easily extracted client location information.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 is a block diagram of an environment with exemplary network management devices which utilize embedded client location information to take one or more value added actions;

[0012] FIG. 2 is a block diagram of the exemplary network management devices shown in FIG. 1 ;

[0013] FIG. 3 is a flowchart of an exemplary method for using embedded client location information for network management to take one or more value added actions; and

10039413-1 [0014] FIG. 4 is a flowchart of an exemplary method for extracting client location information from a payload and inserting into a packet header.

DETAILED DESCRIPTION

[0015] An environment 10 with exemplary network management devices 14(1)- 14(2) which utilize embedded client location information for network management is illustrated in FIGS 1-2. This network environment 10 includes client computing devices 12, the network management devices 14(1) and 14(2) in a symmetric deployment, and servers 16 which are coupled together by local area networks (LAN) 28 and wide area network (WAN) 30, although other types and numbers of devices and components in other topologies could be used. This technology provides a number of advantages including more effective methods, non- transitory computer readable medium and devices for network management by using embedded client location information in network traffic packets as illustrated and described herein. [0016] Referring more specifically to FIGS. 1-2, the network management device 14(1) is coupled to client computing devices 12 through one of the LANs 28, although the client computing devices 12 or other devices and network management device 14(1) may be coupled together via other topologies. Additionally, the network management device 14(2) is coupled to the servers 16 through another one of the LANs 28, although the servers 16 or other devices and network management device 14(2) may be coupled together via other topologies. LANs 28 each may employ any suitable interface mechanisms and communications technologies including, for example, telecommunications in any suitable form (e.g., voice, modem, and the like), Public Switched Telephone Network (PSTNs), Ethernet- based Packet Data Networks (PDNs), combinations thereof, and the like. The network management device 14(1) is coupled to the network management device 14(2) through the WAN 30, which may comprise any wide area network (e.g., Internet), although any other type of communication network topology may be used. Various network processing applications, such as CIFS applications, NFS applications, HTTP Web Server

10039413-1 applications, FTP applications, may be operating on servers 16 and transmitting data (e.g., files, Web pages) through the network management devices 14(1) and 14(2) in response to requests from client computing devices 12.

[0017] In this example, the network management devices 14(1) and 14(2) run one or more network management applications on one or more processors 18 to manage network traffic by optimizing, securing and accelerating the traffic between client computing devices 12 and servers 16 including implementing adaptive forward error correction, although network management devices 14(1) and 14(2) may perform other network related functions. Moreover, the network traffic may be received and transmitted by network management devices 14(1) and 14(2) from and to the LANs 28 and WAN 30 in the form of network data packets in the TCP/IP protocol, although the network data packets could be in other network protocols. Further, the network management devices 14(1) and 14(2) execute and provide one or more value added actions based on the extracted embedded client location information as illustrated and described herein.

[0018] Network management devices 14(1) and 14(2) each include processor(s) 18, memory 20, interface(s) 22, and network interface controller (NIC) 24, which are coupled together by bus 26, although each may comprise other types and numbers of elements in other configurations. Although the network management devices 14(1) and 14(2) are shown in FIGS. 1-2 in this example as being standalone devices, such as a BIG-IP® network management device offered by F5 Networks, Inc., of Seattle, WA, it should be appreciated that the network management devices 14(1) and 14(2) could also be one of several blades servers coupled to a chassis device, such as a VIPRION® network management device, also offered by F5 Networks, Inc., of Seattle, WA.

[0019] Processor(s) 18 execute the network management applications that handle the network traffic between applications on the client computing devices 12 and servers 16 and the one or more value added actions as well as one or more computer-executable instructions stored in the memory 20 and other operations

10039413-1 illustrated and described herein. The processor(s) 18 may comprise one or more central processing units ("CPUs") or general purpose processors with one or more processing cores, such as AMD® processor(s), although other types of processor(s) could be used (e.g., Intel®). [0020] Memory 20 may comprise one or more tangible storage media such as, for example, RAM, ROM, flash memory, CD-ROM, floppy disk, hard disk drive(s), solid state memory, DVD, or any other memory storage type or devices, including combinations thereof, which are known to those of ordinary skill in the art. Memory 20 may store one or more computer-readable instructions that may be executed by the one or more processor(s) 18 and/or the NIC 24. When these stored instructions are executed, they may implement processes that are illustrated, for exemplary purposes only, by the flow chart diagram shown in FIG. 3. It should be appreciated the flow chart diagram shown in FIG. 3 is representative of example steps or actions that may be embodied or expressed as one or more computer or machine readable instructions or logic that may be executed by the processor(s) 18 and/or NICs 24 in network management devices 14(1) and 14(2) shown in FIGS. 1-2. In this example, the machine readable instructions may embody an algorithm or computer program for execution by at least one of: (a) one or more processors each having one or more processor cores, (b) hardware specifically configured to perform the instructions (e.g., ASICs, FPGAs) and (c) one or more other suitable processing device(s). The algorithm or computer program may be embodied in software stored on memory 20 by way of example only.

[0021] NIC 24 may comprise specialized hardware to achieve maximum execution speeds, such a field programmable gate arrays ("FPGAs") and execute functions of this technology as illustrated and described with the examples herein, although other types and amounts of hardware and/or software may be used, such as ASICs, field programmable logic devices ("FPLDs"), programmable logic units ("PLUs"), software executed by the processor 18, and combinations thereof. The use of the specialized hardware in this example, however allows the NIC 24 and/or the

10039413-1 processor 18 executing programmed instructions stored in memory 20 to efficiently assist with the transmission and receipt of packets via WAN 30 and the LANs 28. It is to be understood that NIC 24 may take the form of a network peripheral card or other logic that is installed inside a bus interface within network management devices 1 (1) and 14(2) or may be an embedded component as part of a computer processor motherboard, a router or printer interface, or a USB device that may be internal or external to the network management devices 14(1) and 14(2).

[0022] Input/output interfaces 22 include one or more keyboard/mouse interfaces, display devices interfaces, and other physical and/or logical mechanisms for enabling network management devices 14(1) and 14(2) to communicate with the outside environment, which includes WAN 30, LANs 28 and users (e.g.,

administrators) desiring to interact with network management devices 14(1) and 14(2), such as to configure, program or operate it. The bus 26 is a hyper-transport bus in this example, although other bus types may be used, such as PCI. [0023] Each of the client computing devices 12 and servers 16 include a central processing unit (CPU) or processor, a memory, a global positioning device, and an interface or I/O system, which are coupled together by a bus or other link, although other numbers and types of elements could be used. Additionally, the global positioning device in one or more of the client computing devices 12 and servers 16 is optional and also the global positioning device could be in other devices, such as on the network management device 14(1) managing the network traffic from the client computing devices 12 or the network management device 14(2) managing the network traffic from the servers 16 by way of example only. The client computing devices 12, in this example, may run interface applications, such as Web browsers, that may provide an interface to make requests for and send data to different server based applications via the LANs 28 and WAN 30. Generally, servers 16 process requests received from requesting client computing devices 12 via LANs 28 and WAN 30 according to the HTTP -based application RFC protocol or the CIFS or NFS protocol in this example, but the principles discussed herein are not limited to this

10039413-1 example and can include other application protocols. A series of applications may run on the servers 16 that allow the transmission of data, such as a data file or metadata, requested by the client computing devices 12. The servers 16 may provide data or receive data in response to requests directed toward the respective applications on the servers 16 from the client computing devices 12. As per TCP, packets may be sent to the servers 16 from the requesting client computing devices 12 to send data. It is to be understood that the servers 16 may be hardware or software or may represent a system with multiple servers 16, which may include internal or external networks. In this example the servers 16 may be any version of Microsoft^® IIS servers or Apache^® servers, although other types of servers may be used. Further, additional servers may be coupled to the LAN 28 and many different types of applications may be available on servers coupled to the LAN 28.

[0024] Although an exemplary network environment 10 with client computing devices 12, network management devices 14(1) and 14(2), servers 16, LANs 28 and WAN 30 are described and illustrated herein, other types and numbers of systems, devices, blades, components, and elements in other topologies can be used. It is to be understood that the systems of the examples described herein are for exemplary purposes, as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those skilled in the relevant art(s).

[0025] Furthermore, each of the systems of the examples may be

conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, and micro-controllers, programmed according to the teachings of the examples, as described and illustrated herein, and as will be appreciated by those ordinary skill in the art.

[0026] In addition, two or more computing systems or devices can be substituted for any one of the systems in any example. Accordingly, principles and advantages of distributed processing, such as redundancy and replication also can be implemented, as desired, to increase the robustness and performance of the devices

10039413-1 and systems of the examples. The examples may also be implemented on computer system or systems that extend across any suitable network using any suitable interface mechanisms and communications technologies, including by way of example only telecommunications in any suitable form (e.g., voice and modem), wireless communications media, wireless communications networks, cellular communications networks, 3G/4G/LTE communications networks, Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, and combinations thereof.

[0027] The examples may also be embodied as a non-transitory computer readable medium having instructions stored thereon for one or more aspects of the technology as described and illustrated by way of the examples herein, which when executed by a processor (or configurable hardware), cause the processor to carry out the steps necessary to implement the methods of the examples, as described and illustrated herein. [0028] An exemplary method for using embedded client location information for network management will now be described with reference to FIGS. 1-3. In step 100, the network management device 14(1) receives at least one more network packets from one or more of the client computing devices 12, although the network management device 14(1) could obtain other numbers of network packets from other types and numbers of devices. In this particular example, the received network packet is a TCP/IP packet comprising a header and a payload for transmission, although other types and numbers of packets. With this technology, the client location information is embedded in the header as opposed to the payload so that it is more easily accessible by the network management device 14(1) or 14(2). [0029] In step 102, in this example the network management device 14(1) determines whether the header in the received network packet includes embedded client location information. If in step 102, the network management device 14(1) determines the header in the received network packet does not contain embedded client location information, then the No branch is taken to step 104. In step 104, the

10039413-1 network management device 14(1) processes the received network packet in accordance with the standard network management protocols based on stored programmed instructions in the network management device 14(1).

[0030] If in step 102, the network management device 14(1) determines the header in the received network packets does contain embedded client location information, then the Yes branch is taken to step 106. In step 106, the network management device 14(1) extracts the embedded client location information from the header of the received network packet, although other manners for obtaining the embedded client location information could be used. The embedded client location information is located in the header so and is not encrypted so it can be quickly extracted and utilized by the network management 14(1), although other types of devices could extract and utilize this information to take one or more value added actions. In this particular example, the embedded client location information includes geographic location information comprising a latitude, longitude, and altitude of the one of the client computing devices 12 that generated the network packet as well as date and time information when the received network packet was created, although other types and amounts of information could be obtained and embedded. In this particular example, the header comprises TCP or a cookie in HTTP, although the client location information could be embedded in other locations that enable easy access based on the particular protocol.

[0031] In step 108, the network management device 14(1) determines whether to take one or more actions based on the extracted embedded client location information from the header of the received network packet. If in step 108, the network management device 14(1) does not identify any action to be taken based on the extracted embedded client location information, then the No branch is taken back to step 104 as described earlier.

[0032] If in step 108, the network management device 14(1) identifies one or more actions to be taken based on the extracted embedded client location information, then the Yes branch is taken back to step 110. In step 110, the network management

10039413-1 device 14(1) identifies and takes the one or more identified actions based on the extracted embedded client location information.

[0033] By way of example only, the one or more identified actions executed by the network management device 14(1) could comprise: (1) Implementing network traffic management, such as routing, switching or blocking the transmission of the received network packet based on the extracted embedded client location information; (2) Implementing vector based routing by using the extracted time and location information from subsequent network packets with embedded client location information to determine a direction and rate of travel and then routing the source of the network packet to a next cell along a highway or ground station when traveling by air, car or train based on the determined direction and rate of travel; (3) Limiting certain types of traffic access based on the extracted embedded client location information, such as blocking streaming live video from a stadium, but allowing texting or blocking cell calls in a theater or while a plane is on the runway; (4) Blocking all access to and from the source of the network packet which is identified as being at a secure location based on the extracted embedded client location information; (5) Directing content to the source of the network packet based on the determined location, such as directions, local event information, local places to eat, local and current entertainment options, other points of interest, and emergency warnings, e.g. a severe storm warming; (6) Contacting one or more other computing devices who are identified in a table or other database as friends and are within a first distance of the source of the network packet; (7) Tracking a location of the source of the network packet in an event, such as a bike race by way of example; (8)

Facilitating a link directly from the source of the network packet to another device via a local communication protocol (e.g. Bluetooth, wireless, peer to peer networks) instead of connecting over a traditional network medium (e.g. cellular, wireless then onto a gateway to the internet); and (9) Tagging geographic location information in content, such as pictures or text, associated with the at least one network packet based on the extracted embedded client location information.

10039413-1 [0034] An exemplary method for extracting client location information from a payload and inserting into a packet header will now be described with reference to FIGS. 1, 2 and 4. In step 200, the network management device 14(1) receives at least one more network packets from one or more of the client computing devices 12, although the network management device 14(1) could obtain other numbers of network packets from other types and numbers of devices. In this particular example, the received network packet is a TCP/IP packet comprising a header and a payload for transmission, although other types and numbers of packets.

[0035] In step 202, in this example the network management device 14(1) determines whether to try and obtain client location information based on the payload of the obtained packet for insertion in the header of the obtained packet. If in step 202, the network management device 14(1) determines not to try and obtain client location based on the payload of the obtained packet, then the No branch is taken to step 208. In step 208, the network management device 14(1) processes the obtained network packet in accordance with the standard network management protocols based on stored programmed instructions in the network management device 14(1).

[0036] If in step 202, the network management device 14(1) determines to try and obtain client location information based on the payload of the obtained packet, then the Yes branch is taken to step 204. In step 204, the network management device 14(1) extracts the client location information from the payload of the obtained network packet, although other manners for obtaining the client location information could be used. For example, the network management device 14(1) could extract and use information in the obtained network packet to obtain the client location information based on a correlation of the obtained information against matching identifiers in a stored database or table in the network management device to obtain client location information

[0037] In step 206, the network management device 14(1) embeds the extracted client location information from the payload of the obtained network packet and embeds the client location information in the header of the obtained network

10039413-1 packet and then proceeds to step 208 as described earlier, although other manners for inserting the client location information into the header could be used.

[0038] Accordingly, as illustrated and described above, this technology provides more effective methods, non-transitory computer readable medium, and devices for network management by using unencrypted client location information embedded in the header of a standard TCP/IP packet. Placing the embedded client location information in the header and in an unencrypted format enables the network management device to quickly and easily extract and utilize this information to take one or more value added actions. [0039] Having thus described the basic concept of the invention, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations,

improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the invention. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the invention is limited only by the following claims and equivalents thereto.

10039413-1

Claims

CLAIMS What is claimed is:

1. A method for using embedded client location information for network management, the method comprising:

obtaining at a network management computing device traffic comprising at least one network packet, the at least one network packet comprising a header and a payload;

extracting by the network management computing device client location information embedded in the header of the at least one network packet; and executing by the network management computing device at least one network management action based on the extracted client location information from the at least one network packet.

2. The method as set forth in claim 1 wherein the extracting by the network management computing device the client location information occurs without needing to decrypt the extracted client location information.

3. The method as set forth in claim 1 further comprising determining by the network management computing device whether to take the at least one network management action based on the extracted embedded client location information from the header of the obtained network packet, wherein the executing is based on the network management computing device determining at least one network management action should be taken.

4. The method as set forth in claim 1 wherein the client location information further comprises geographic information of the source of the at least one network packet and a date and time of creation of the at least one network packet.

5. The method as set forth in claim 4 wherein the executing by the network management computing device the at least one action is further based on the

10039413-1 geographic information of the source of the at least one network packet and the date and time of creation of the at least one network packet.

6. The method as set forth in claim 5 wherein the executing by the network management computing device the at least one action is further based on the geographic information of the source of the at least one network packet and the date and time of creation of the at least one network packet and of at least one

subsequently obtained network packet.

7. The method as set forth in claim 1 wherein the executing by the network management computing device the at least one action further comprises at least one of: implementing network traffic management; implementing vector based routing; limiting at least one type of traffic access; blocking all access to and from the source of the at least one network packet which is identified as being at a secure location; directing content to the source of the at least one network packet; contacting one or more other computing devices associated with the source of the at least one network packet and within a first distance of the source of the at least one network packet; tracking a location of the source of the at least on network packet in an event; and facilitating a link directly from the source of the at least one network packet to another device via a local communication protocol; and tagging geographic location information in content associated with the at least one network packet.

8. A non-transitory computer readable medium having stored thereon instructions for using embedded client location information for network management comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

obtaining traffic comprising at least one network packet, the at least one network packet comprising a header and a payload;

extracting client location information embedded in the header of the at least one network packet; and

10039413-1 executing at least one network management action based on the extracted client location information from the at least one network packet.

9. The medium as set forth in claim 8 wherein the extracting the client location information occurs without needing to decrypt the extracted client location information.

10. The medium as set forth in claim 8 further comprising determining whether to take the at least one network management action based on the extracted embedded client location information from the header of the obtained network packet, wherein the executing is based on the determining at least one network management action should be taken.

11. The medium as set forth in claim 8 wherein the client location information further comprises geographic information of the source of the at least one network packet and a date and time of creation of the at least one network packet.

12. The medium as set forth in claim 11 wherein the executing the at least one action is further based on the geographic information of the source of the at least one network packet and the date and time of creation of the at least one network packet.

13. The medium as set forth in claim 12 wherein the executing the at least one action is further based on the geographic information of the source of the at least one network packet and the date and time of creation of the at least one network packet and of at least one subsequently obtained network packet.

14. The medium as set forth in claim 8 wherein the executing the at least one action further comprises at least one of: implementing network traffic management; implementing vector based routing; limiting at least one type of traffic

10039413-1 access; blocking all access to and from the source of the at least one network packet which is identified as being at a secure location; directing content to the source of the at least one network packet; contacting one or more other computing devices associated with the source of the at least one network packet and within a first distance of the source of the at least one network packet; tracking a location of the source of the at least on network packet in an event; and facilitating a link directly from the source of the at least one network packet to another device via a local communication protocol; and tagging geographic location information in content associated with the at least one network packet.

15. A network management device comprising:

at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory comprising:

executing at least one network management action based on the extracted client location information from the at least one network packet.

16. The device as set forth in claim 15 wherein at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory for the extracting further comprising extracting the client location information occurs without needing to decrypt the extracted client location information.

10039413-1

17. The device as set forth in claim 15 wherein at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory further comprising determining whether to take the at least one network management action based on the extracted embedded client location information from the header of the obtained network packet, wherein the executing is based on the determining at least one network management action should be taken.

18. The device as set forth in claim 15 wherein the client location information further comprises geographic information of the source of the at least one network packet and a date and time of creation of the at least one network packet.

19. The device as set forth in claim 18 wherein at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory further comprising executing the at least one action based on the geographic information of the source of the at least one network packet and the date and time of creation of the at least one network packet.

20. The device as set forth in claim 19 wherein at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory for the executing further comprising executing the at least one action based on the geographic information of the source of the at least one network packet and the date and time of creation of the at least one network packet and of at least one subsequently obtained network packet.

21. The device as set forth in claim 15 wherein at least one of the configurable logic unit is further configured to implement and the one or more processors is further configured to execute programmed instructions stored in the

10039413-1 memory for the executing further comprising executing the at least one action comprising at least one of: implementing network traffic management; implementing vector based routing; limiting at least one type of traffic access; blocking all access to and from the source of the at least one network packet which is identified as being at a secure location; directing content to the source of the at least one network packet; contacting one or more other computing devices associated with the source of the at least one network packet and within a first distance of the source of the at least one network packet; tracking a location of the source of the at least on network packet in an event; and facilitating a link directly from the source of the at least one network packet to another device via a local communication protocol; and tagging geographic location information in content associated with the at least one network packet.

22. A method for embedding client location information for network management, the method comprising:

obtaining with the network management computing device client location information based on the payload of the at least one network packet; and

embedding with the network management computing device the obtained client location information in the header of the at least one network packet.

23. The method as set forth in claim 22 wherein the obtaining the client location information further comprises extracting with the network

management computing device the client location information from the payload.

24. The method as set forth in claim 22 wherein the obtaining the client location information further comprises obtaining with the network management

10039413-1 computing device the client location information from a stored database based on a correlation with information in the obtained network packet.

25. A non-transitory computer readable medium having stored thereon instructions for embedding client location information for network management comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

obtaining traffic comprising at least one network packet comprising a header and a payload;

obtaining client location information based on the payload of the at least one network packet; and

embedding client location information in the header of the at least one network packet.

26. The medium as set forth in claim 25 wherein the obtaining the client location information further comprises extracting the client location information from the payload.

27. The medium as set forth in claim 25 wherein the obtaining the client location information further comprises obtaining the client location information from a stored database based on a correlation with information in the obtained network packet.

28. A network management device comprising:

10039413-1 obtaining client location information based on the payload of least one network packet; and

29. The device as set forth in claim 28 wherein at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory for the obtaining the client location information further comprising extracting the client location information from the payload.

30. The device as set forth in claim 27 wherein at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory for the obtaining the client location information further comprising obtaining the client location information from a stored database based on a correlation with information in the obtained network packet.

10039413-1