Location based enhanced routing

• US 20030217150A1
• Filed: 02/28/2003
• Published: 11/20/2003
• Est. Priority Date: 03/01/2002
• Status: Abandoned Application

• Current Assignee: Enterasys Networks Incorporated (Extreme Networks, Inc.)
• Original Assignee: Enterasys Networks Incorporated (Extreme Networks, Inc.)
• Inventors: Roese, John J., Graham, Richard W., Frattura, David
• Application Number:
  US10/377,163
• Publication Number:
  US 20030217150A1
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: G01S 5/02 using radio waves using satellite radio beacon systems for determining position G01S19/00
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 64/00 : Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: Y10S 707/99932 : Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99939 : Privileged access

Abstract

Data is generated to include restrictive routing information based on physical location. The data can then be transmitted and routed according to the restrictive routing information. The approach can include prohibiting the data from being transmitted to a network device located at a restricted physical location in accordance with the restricted routing information. Optionally the data can be destroyed if a network device receiving the data is located at a restricted physical location in accordance with the restricted routing information.

Claims

1. A method comprising,

generating data including restrictive routing information based on physical location.

2. The method of claim 1 further comprising transmitting the data in accordance with the restrictive routing information.

3. The method of claim 1 further comprising destroying the data if a network device receiving the data is located at a restricted physical location in accordance with the restricted routing information.

4. The method of claim 1 further comprising prohibiting the data from being transmitted to a network device located at a restricted physical location in accordance with the restricted routing information.

5. The method of claim 1 further comprising prohibiting the data from being accessed by a client device located at a restricted physical location in accordance with the restricted routing information.

6. The method of claim 1 wherein the restricted routing information comprises a prohibited physical location.

7. The method of claim 1 wherein the restricted routing information comprises a permitted physical location.

8. The method of claim 1 wherein the data comprises a data packet.

9. The method of claim 1 wherein the data comprises a file.

10. The method of claim 1 wherein the data comprises a document.

11. A method comprising:

receiving data at a first network device; and

routing the data to a second network device based on a policy determined using location information.

12. A system comprising:

network devices with associated physical locations; and

data with restrictive routing information based on physical location.

13. The system of claim 12 further comprising a physical location server including a storage module configured to store the associations of network devices with their respective physical locations.

14. The system of claim 12 wherein each network device includes a storage module configured to store the association of that particular network device with its respective physical location.

15. The system of claim 12 wherein each network device includes a location module configured to transmit the data in accordance with the restrictive routing information.

16. The system of claim 12 wherein each network device includes a location module configured to destroy the data if the respective network device receiving the data is located at a restricted physical location in accordance with the restricted routing information.

17. The system of claim 12 wherein each network device includes a location module configured to prohibit the data from being transmitted to another network device located at a restricted physical location in accordance with the restricted routing information.

18. The system of claim 12 wherein each network device includes a location module configured to prohibit the data from being accessed by a client device located at a restricted physical location in accordance with the restricted routing information.

19. The system of claim 12 wherein the restricted routing information comprises a prohibited physical location.

20. The system of claim 12 wherein the restricted routing information comprises a permitted physical location.

21. The system of claim 12 wherein the data comprises a data packet.

22. The system of claim 12 wherein the data comprises a file.

23. The system of claim 12 wherein the data comprises a document.

24. Data comprising restrictive routing information based on physical location.

25. The data of claim 24 further comprising a header that includes the restricted routing information.

26. The data of claim 24 wherein the restricted routing information comprises network layer information.

27. The data of claim 24 wherein the restricted routing information comprises transport layer information.

28. The data of claim 24 wherein the restricted routing information identifies prohibited physical locations.

29. The data of claim 24 wherein the restricted routing information identifies permitted physical locations.

30. The data of claim 24 further comprising a data packet.

31. The data of claim 24 further comprising a file.

32. The data of claim 24 further comprising a document.