CA2567596A1 - System and method for location based policy management - Google PatentsSystem and method for location based policy management
- Publication number
- CA2567596A1 CA2567596A1 CA 2567596 CA2567596A CA2567596A1 CA 2567596 A1 CA2567596 A1 CA 2567596A1 CA 2567596 CA2567596 CA 2567596 CA 2567596 A CA2567596 A CA 2567596A CA 2567596 A1 CA2567596 A1 CA 2567596A1
- Grant status
- Patent type
- Prior art keywords
- 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.)
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATIONS NETWORKS
- H04W4/00—Mobile application services or facilities specially adapted for wireless communication networks
- H04W4/02—Mobile application Services making use of the location of users or terminals, e.g. OMA SUPL, OMA MLP or 3GPP LCS
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network-specific arrangements or communication protocols supporting networked applications
- H04L67/18—Network-specific arrangements or communication protocols supporting networked applications in which the network application is adapted for the location of the user terminal
SYSTEM AND METHOD FOR LOCATION BASED POLICY MANAGEMENT
FIELD THE DISCLOSURE
This disclosure, in general, relates to systems and methods for location based policy management.
Short-range wireless data networks have become commonplace, being found in homes, coffee shops, and places of business. Short-range wireless standards, such as 802. I lx, and to some extent Bluetooth, provide network users with mobility and easy network access. However, this ease of wireless network access poses problems to network administrators including securing network traffic and preventing unauthorized network access.
Manufacturers of short-range wireless equipment have attempted to address the security issues posed by intrusive and unauthorized traffic through protocols, such as wireless application protocol (WAP), and encryption mechanisms such as wired equivalent privacy (WEP) and Wi-Fi protected access (WPA). The WAP protocol, for example, provides services for wireless devices that include security layers, such as wireless transport layer security (WTLS), that are designed to provide privacy, data integrity and authentication between communicating applications. WEP is an algorithm used to protect wireless communications from eavesdropping through data encryption. WEP relies upon a key that is shared between a mobile station and an access point. The key is used to encrypt packets before they are transmitted, and an integrity check is used to verify that the packets are not modified in transit.
WPA is a security enhancement for Wi-Fi networks that defines the use of the advance encryption standard (AES) as an additional replacement for WEP encryption.
However, even with these security methods and mechanisms, wireless networks tend to extend beyond traditional physical boundaries, allowing users outside the boundaries to gain unauthorized access to networks. As such, improved systems and methods for managing access to short-range wireless networks would be desirable.
BRIEF DESCRIPTION OF THE DRAWINGS
FIGS. 1, 2, 3 and 4 are general diagrams that depict an exemplary short-range wireless network.
FIG. 5 is a flow diagram that illustrates an exemplary method for defining a wireless boundary region.
FIGS. 6 and 7 are general diagrams that depict exemplary computer systems for providing a short-range wireless network.
FIG. 8 is a block diagram depicting an exemplary policy server.
FIG. 9 is a block diagram depicting an exemplary wireless device.
FIGS. 10 and 11 are flow diagrams illustrating exemplary methods for controlling network traffic.
FIGS. 12 and 13 are flow diagrams illustrating exemplary methods for providing a feature policy.
DESCRIPTION OF THE DRAWINGS) In a particular embodiment, the disclosure is directed to a method of controlling network traffic including providing boundary data defining a boundary zone within a short-range wireless network coverage area, determining whether a wireless enabled device is located within the boundary zone, and controlling network traffic received from the wireless enabled device when the wireless enabled device is located outside the boundary zone.
In another embodiment, the disclosure is directed to a policy server including a processor, communication circuitry, and memory. The communication circuitry is accessible to the processor and is configured to connect to a set of wireless network access points. The set of wireless access points provide a short-range wireless network coverage area. The memory is accessible to the processor and includes boundary data and computer-implemented instructions operable by the processor to determine whether a wireless enabled device is located within a boundary zone within the coverage area based on data received from the set of wireless network access points. The boundary zone is defined by the boundary data.
In a further embodiment, the disclosure is directed to a communications device including long-range wireless communication circuitry configured to access a long-range wireless network, short-range wireless communication circuitry configured to access a short-range wireless network, configurable feature circuitry, and a feature policy driver. The feature policy driver is programmed to receive a feature policy via the short-range wireless communication circuitry and is programmed to configure the feature circuitry based on the feature policy.
In another embodiment, the disclosure is directed to a method for managing feature functionality of a wireless enabled device. The method includes providing boundary data defining a boundary zone within a short-range wireless network coverage area, determining whether a wireless enabled device is located within the boundary zone, and determining a feature policy to be applied to the wireless enabled device based on determining whether the wireless enabled device is located within the boundary zone.
In a particular embodiment, the disclosure is directed to a system including a set of access points and a policy server. The set of access points establish a coverage area for a short-range wireless network and provide data to the policy server regarding wireless devices within the coverage area. The policy server determines the location of the wireless devices and whether the wireless devices are located within a boundary zone. Based on the location of the wireless device or its location within or outside of the boundary zone, a policy, such as a network fraffic policy or a feature policy, may be applied to the wireless devices or network traffic transmitted by the network device. For example, network traffic policies may define network access and network access parameters based on wireless enabled device location. Feature policies may manipulate device features and feature availability based on wireless enabled device location.
FIG. 1 illustrates an exemplary short-range wireless network. The exemplary short-range wireless network 100 includes a set of access points 102 that each provide portions 104 of a coverage area.
Typically, the coverage area portions 104 may extend beyond traditional physical boundaries or desired access areas. In this exemplary embodiment, the coverage area portions 104 extend beyond a physical boundary 106, such as a building, a room, an office space, a residence, or a shop location. In other examples, the boundaries or desired access areas 106 may include conceptual regions such as patios, balconies, reception areas, gardens, and parks.
The nature of the short-range wireless network is such that individuals having wireless enabled devices located within the portions 104 of the short-range wireless network coverage area may receive signals from one or more of the access points 102. An individual within a preferred access area, such as a user 108, may receive data emitted by the access points 102. In addition, a user located outside the preferred access area, such as user 110, may also receive data transmitted from the access points 102.
In exemplary embodiments, the access points 102 may provide a short-range wireless network using standards and protocols, such as Wi-Fi, Wi-Max, Institute of Electrical and Electronics Engineers (IEEE) 802.11x, IEEE 802.15, IEEE 802.16, and Bluetooth. A short-range wireless network may, for example, have an effective coverage area portion provided by an access point, wherein the effective coverage area does not exceed 1000 feet in radius, such as not greater than 200 feet, or not greater than about 50 feet in radius. The short-range wireless network may, for example, provide wireless data network access in proximity to the access points, such as in and around a building, room, residence, office space, shop, or preferred access area. Wireless devices accessing the short-range wireless network may include wireless enabled computational devices, such as portable commuters, printers, handheld computational devices, portable digital assistants (PDAs), wireless data network enabled cellular telephones, and other networkable devices. In general, a short-range wireless network is not a cellular or pager based network and is an Internet protocol (IP) based wireless data network. In contrast, long-range wireless networks generally provide wireless networks having a radius greater than about 1000 feet. For example, long-range wireless networks include pager networks and cellular telephone networks, such as time division multiple access (TDMA), code division multiple access (CDMA), and global system for mobile communication (GSM) networks.
FIG. 2 depicts an exemplary short-range wireless network 200 that includes a set of wireless network access points 202 that each provide portions 204 of a wireless network coverage area. Users having wireless enabled devices such as users 208 and 210 may be located within the coverage area portions 204 and, as such, may receive network transmissions transmitted from access points 202. A boundary 212 that defines a boundary zone 214 may be established for policy management, such as network traffic policies and feature policies. For example, a server or other network equipment may include boundary data that defines the boundary zone 214 and the boundaries 212. In this exemplary embodiment the boundary zone 214 corresponds closely with a preferred access area such as a room or building 206.
The location of a wireless enabled device may be determined using data from the access points. In one exemplary embodiment, a triangulation method uses at least three access points. For example, location may be determined by evaluating timing data associated with a signal reaching several access points.
Network equipment such as a server or router device may include instructions for determining location based on timing data provided by the access points. In another exemplary embodiment, the triangulation method may use relative power levels of wireless communications received either at the wireless device or at the access points. The network equipment may determine the location relative to the access points based on these power measurements. In alternative embodiments, methods may be employed such as power measurement methods to determine location using one or two access points.
The network equipment may use data from the access points 202 to determine whether wireless devices, such as those co-located with users 208 and 210 are located within the boundary zone 214. In one exemplary embodiment, the network equipment utilizes triangulation methods based on at least three access points 202 to determine the location of a user and whether the user is located within the boundary 212 or the boundary zone 214. Using this determination, the network equipment may determine and implement policies associated with the location of the mobile device, the device's traffic, and/or device features. For example, a user having a wireless device, such as user 208, located within the boundary zone 214 may be provided with or associated with a policy different than a user located outside the boundary zone 214, such as user 210. For example, user 208 located within the boundary zone 214 may be provided with differing security and network traffic controls than user 210 located outside the boundary zone. In another exemplary embodiment the user 208 located within the boundary zone 214 may be provided with one feature policy while a user device 210 located outside of the boundary zone 214 may be provided with a second feature policy.
While FIG. 2 depicts a single boundary zone 214, alternative systems may include multiple boundary zones. Boundary data may be used to establish more than one boundary zone. In addition, systems having multiple boundary zones may apply different policies to wireless devices located within different boundary zones or different policies to the same wireless enabled device as it traverses the multiple boundary zones. In this manner, the system may implement multiple policy areas or a policy ' mapping.
In one exemplary embodiment; users located outside of the preferred access zone as defined by the boundary zone may be denied network access. FIG. 3 illustrates an exemplary short-range wireless network 300 that implements location based network management. The short-range wireless network 300 may include wireless access points 302 that each provide a portion 304 of a coverage area. Within the coverage area, a boundary 312 may define a boundary zone 314 that represents a preferred access area. In this exemplary embodiment, the preferred access area and boundary zone 314 are located within a physical structure 306. For example, a preferred access region may be located within a building, a room, a residence, an office space, a shop or a patio region. In this exemplary embodiment, wireless enabled devices located within the boundary zone 314, such as devices co-located with user 308 may be provided with network access. For example, the set of access points 302 may provide data to network equipment, such as a server or router that determines the location of the user and determines whether the user is within the boundary zone 314. Network packets provided to and received from the wireless device associated with the user 308 may be transmitted across the wireless network and may be given access to external wired networks. In contrast, wireless enabled devices located outside of the boundary zone 314, such as devices co-located with user 310, may be denied access to the network.
For example, network equipment may determine the location of the user 310 based on data from a set of access points 302. Using this location determination, data packets 316 transmitted from the wireless device 310 located outside of the boundary zone 314 may be dropped, discarded, sent to a holding place or trash 318, or treated with policies and algorithms differing from those applied to a wireless device located within the boundary zone 314.
FIG. 4 illustrates another exemplary short-range wireless network 400 that includes a set of wireless access points 402 that each provide portions 404 of a wireless network coverage area. In one exemplary embodiment, a boundary and a boundary zone may be established using a set of locations within a coverage area. These locations may be used to establish the boundary and boundary zones, such that they conform closely to a preferred access area or region. In one exemplary embodiment, the user 406, having a wireless enabled calibration device, may provide boundary data to network equipment by calibrating at various points along a boundary path 408. In the exemplary embodiment depicted, the boundary path 408 closely conforms to the physical boundary of a room or building. In alternative examples, the calibration device may provide a set of points from which a boundary may be extrapolated. For example, two boundary points may be used to create a boundary line or a set of boundary measurements, such as power measurements may be used to create a statistical boundary zone or area.
In one exemplary embodiment, boundary data and locations may be determined by triangulation between at least three access points. A set of triangulated boundary points may be compared to locations of devices in the coverage area to determine whether the devices are located within a boundary zone. Using this determination, differing network access policies and feature policies may be applied to mobile wireless enabled device.
FIG. 5 depicts an exemplary method for providing a boundary zone. As shown at step 502, a set of boundary locations is established. For example, a wireless calibration device may communicate with network equipment to establish a set of locations along a boundary. This set of locations may be converted to boundary data that defines a boundary zone. In this manner, the boundary zone is determined, as shown at step 504.
FIG. 6 depicts an exemplary system 600 for establishing a short-range wireless network. A device 604, such as a wireless hand-held electronic device, a wireless enabled laptop or a short-range wireless enabled cell phone, may interact with access points 604 when located within the coverage area of the short-range wireless network. The access points 604 collect data associated with the location of the wireless device 602 and transfer that data via a routes or other network equipment 606 to a policy server 608. For example, the access points 604 may record a time that a signal was received. This signal arrival time may be transferred to the policy server 608 and the policy server 608 may determine the location of the wireless device within a coverage area based on the reported signal arrival times from each access point 604. The policy server 608 compares the location with boundary zone data to determine whether the wireless device 602 is located within a boundary zone.
The policy server 608 implements and associates policies with the wireless, device 602 based on its location relative to a boundary zone. For example, the policy server may implement network traffic controls based on the location of the wireless device 602. In one exemplary embodiment, the policy server 608 manipulates network equipment, such as network equipment 606, to control network traffic received from the wireless device 602. In one example, network traffic received from the wireless device 602 when the wireless device 602 is located within a boundary zone is permitted to pass to external networks. In another example, network packets transmitted from the wireless device 602 when the wireless is outside of a boundary zone are dropped or discarded. In another exemplary embodiment, the policy server 608 may implement additional security protocols for devices accessing the network based on their location relative to the boundary zone. For example, a policy server may implement a network that uses different encryption protocols or different security keys based on the location of the wireless device.
In another embodiment, the policy server 608 may interact with the wireless device 602 and control its features and feature activation based on the location within the coverage area. For example, if wireless device 602 is a short-range wireless enabled cellular telephone, the policy server 608 may interact with the cellular telephone to manipulate features located on the cellular telephone based on the phone's location. For example, the policy server may manipulate ring tones, ring volume and vibration modes on a cellular telephone based on the cellular telephone's location. In another exemplary embodiment, the policy server manipulates or deactivates camera features on a camera enabled cellular telephone based on its location within the coverage area. Additional exemplary features and feature policies are described below.
FIG. 7 depicts an alternate embodiment of a system where a policy server is implemented within network equipment. The system 700 includes a set of access points 704 connected to network equipment 706. The access points 704 interact with the wireless device 702 to gather data that may be used in determining the wireless device location. The network equipment 706 uses this data to determine the location of the wireless device. Using the location, the network equipment may compare the location of the wireless device to boundary zone data to determine the location of the device relative to the boundary zone. In response, the network equipment may implement policies, such as _7_ network traffic controls and feature policies, based on the relative location of the device 702 to a boundary zone.
FIG. 8 depicts an exemplary policy server 800. The policy server 800 may be a separate computational system or may be implemented within other data network equipment. The policy server includes processors 802, network and device interfaces 804, and storage 806, such as memory. The storage or memory 806 includes boundary data 808 and programs and instructions 812, and may include policy data and/or algorithms 810.
The network and device interfaces 804 interact with access points and network equipment. For example, the network and device interfaces 804 include interfaces to a wired network and interfaces to access points that implement a wireless short-range wireless network. Through this interaction with the access points, data associated with the location of a wireless device are transferred to the policy server 800.
Programs and instructions 812 are operable by the processors 802 to determine the location of the wireless device within the short-range wireless network coverage area based on the data received from the access points. For example, the programs and instructions 812 may include location determination logic. In addition, the program and instructions 812 may also include software instructions for comparing the location of the wireless device to boundary data 808. From this comparison, the system determines whether particular wireless devices are located within or outside of the boundary zone. The programs and instructions 812 may further include software instructions for implementing policies, such as network traffic controls and feature policies, based on the location of the wireless device. For example, software instructions 812, operable by the processors 802, may be configured to access policy data and algorithms 810 to determine selected policies to implement based on the relative location of the wireless device to a boundary zone. For example, the system 800 may implement network traffic controls based on the location of the wireless device. In another exemplary embodiment the system 800 may implement feature policy controls based on the location of the wireless device.
In one particular embodiment, the wireless device may be implemented as a cellular telephone or portable hand-held device with cellular telephone functionality. In another exemplary embodiment, the wireless device may be configured to access both a long-range network, such as a pager or cellular network, and a short-range network. FIG. 9 depicts an exemplary device that includes both long distance communication circuitry 902 and short-range wireless communication circuitry 904. For example, the long-range communication circuitry 902 may be implemented as a cellular telephone transceiver. The short-range wireless communication circuitry 904 may, for example, interact with a short-range wireless network. In exemplary embodiments, the short-range wireless network includes networks utilizing protocols and standards, such as IEEE 802.11x, IEEE 802.15, IEEE 802.16, Bluetooth, Wi-Fi, and Wi-Max. In addition, to the communications circuitry 902 and 904, the device 900 includes feature devices and circuitry 906 and a feature policy driver 908. The feature devices and circuitry 906 may include circuitry that enables inbound calling, outbound calling, ringer volume _g_ levels, text messaging, voice alert messaging, camera features, web access features, application features, such as JAVA based application, games, voice-over-IP (VoIP). The feature policy driver 908 interacts with the feature devices and circuitry 906 to activate, enable, disable, deactivate or manipulate the parameters or policies associated with those devices and circuitry 906.
For example, the feature policy driver 908 may deactivate a camera capability or web feature when a device is located within a boundary zone. In another example, the features policy driver 908 may activate or deactivate application environments such as JAVA application environments based on a location of the device relative to boundary zones. In a further example, the feature policy driver 908 may initiate downloading of applications.
In one exemplary embodiment, when the device 900 enters a coverage area of a short-range wireless network, short-range wireless communications circuitry 904 interacts with access points to establish a location of the wireless device 900. A policy server associated with the short-range wireless network determines a feature policy based upon the location of the wireless device within the coverage area relative to boundary zones or a policy mapping. T'he policy server transmits a feature policy to the device via the short-range wireless network. The feature policy driver 908 implements feature policies that manipulate the feature devices and circuitry 906. For example, the features policy server may transmit a feature policy that disables or deactivates camera features within camera enabled cell phones. ., .
In one exemplary embodiment, a school may implement a policy that disables game features and JAVA-based applications within classrooms. In this example, the school may establish a short-range wireless network with boundary zones associated with classroom locations. When wireless enabled devices including a feature policy driver are located within the classroom boundary zones, features such as games, JAVA applications, cameras, and ringer volume may be manipulated, disabled or shut off. Similarly, an establishment may establish a boundary zone closely associated with restrooms and locker rooms. In such boundary zones, features such as cameras may be disabled. In a further exemplary embodiment, movie theaters may activate vibration or silent modes within theaters by applying feature policies to features policy enabled devices.
In another exemplary embodiment, a policy server may communicate with feature policy enabled devices utilizing voice alert messages and text alert messages. For example, the policy server may provide a text alert message indicating that the device is entering a restricted zone or that a certain feature policy will be enacted. A similar message may be provided by a voice alert. In a further example, features, such as voice over IP capabilities, may be enabled or disabled based on locations within the coverage area relative to the boundary zone.
FIG. 10 depicts an exemplary method for controlling network traffic. The method includes providing boundary data, as shown at step 1002. The boundary data may include a set of boundary locations that are used to establish a boundary zone or region. When a wireless device enters the short-range wireless network coverage area, the system determines the location of the wireless device, as shown at step 1004. For example, the system may use a time-based triangulation technique utilizing at least three wireless access points. In another exemplary embodiment, the system may use a power-based technique for determining wireless device location. Determining the location of the wireless device may further include comparing a location to the boundary data to determine whether the location is within a boundary zone. Based on the location relative to the boundary zone, the system may control network trafFc, as shown at step 1006. For example, the system may discard packets received from devices located outside of the boundary zone.
FIG. 11 depicts a method for controlling the network traffic. The method 1100 includes receiving a packet from a wireless device, as shown at step 1102. A determination is made as to whether the device is within the boundary zone or region, as shown at step 1104. For example, the system may periodically determine the location of the wireless device relative to the boundary zone. The system may, for example, set a flag that indicates whether the device is in or out of the boundary zone. This flag may be checked to determine whether a packet received from the device should be forwarded or discarded.
If the device is determined to be in the boundary zone, the packet is forwarded, as shown at step 1108.
If the device is not within the boundary zone, the packet is dropped or discarded, as shown at step 1106.
Policies may also be implemented as feature policies that manipulate and control features of a device enabled to receive the feature policies. FIG. 12 depicts an exemplary method for controlling features policies. Boundary data is provided, as shown at step 1202. When a wireless device enters a coverage area of a short-range wireless network, the location of the wireless device is determined, as shown at step 1204. For example, the system may utilize a triangulation technique or a power-based technique to determine the location of the device. Determining the location of the device may further include comparing the location to the boundary data to determine the location of the device relative to a boundary zone. Based on the location of the device relative to the boundary zone, the system determines a feature policy, as shown at step 1206. For example, one feature policy may apply to a device when it is located within a boundary zone and a second feature policy may apply to the device when it is located outside of the boundary zone. The system provides the location based feature policy to the wireless device, as shown at step 1208.
A device enabled to communicate via the short-range wireless network and including a feature policy driver, may receive the feature policy, as shown at step 1302 in FIG. 13. The feature policy may, for example, deactivate features, such as cameras. The feature policy driver on the device may enact the feature policy, as shown at step 1304. For example, the feature policy driver may deactivate camera capabilities within the cellular telephone.
While the examples depict utilize a boundary that is determined based on data associated with a short range network, a boundary zone may be determined using long-range networks and policies and features applied based on location within the long-range network. For example, location may be determined by GPS or cellular triangulation and policies applied to devices based on a policy mapping within the cellular network. Policies, such as the feature policy or network policy, may be implemented on a long-range network. In addition, IP-based communications protocols may be implemented that extend beyond the typical range of short-range wireless networks. In one exemplary embodiment, a Wi-Max or IEEE 802.16 network that has a long-range coverage area may be used to implement boundary zones.
The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
a set of short-range wireless access points configured to provide a short-range wireless network having a coverage area and configured to communicate with a wireless enabled device within the coverage area; and a policy server communicatively coupled with the set of short-range wireless access points and configured to determine whether the wireless enabled device is located within a designated region within the coverage area based on data received from the set of short-range wireless access points.
providing boundary data defining a boundary zone within a short-range wireless network coverage area;
determining whether a wireless enabled device is located within the boundary zone; and controlling network traffic received from the wireless enabled device when the wireless enabled device is located outside the boundary zone.
communication circuitry accessible to the processor and configured to connect to a set of wireless network access points, the set of wireless access points providing a short-range wireless network coverage area; and memory accessible to the processor, the memory including:
boundary data; and computer-implemented instructions operable by the processor to determine whether a wireless enabled device is located within a boundary zone within the coverage area based on data received from the set of wireless network access points, the boundary zone defined by the boundary data.
long-range wireless communication circuitry configured to access a long-range wireless network;
short-range wireless communication circuitry configured to access a short-range wireless network;
configurable feature circuitry; and a feature policy driver programmed to receive a feature policy via the short-range wireless communication circuitry and to configure the feature circuitry based on the feature policy.
providing boundary data defining a boundary zone within a short-range wireless network coverage area;
determining whether a wireless enabled device is located within the boundary zone; and determining a feature policy to be applied to the wireless enabled device based on determining whether the wireless enabled device is located within the boundary zone.
Priority Applications (3)
|Application Number||Priority Date||Filing Date||Title|
|US10890397 US7286834B2 (en)||2004-07-13||2004-07-13||System and method for location based policy management|
|PCT/US2005/023788 WO2006017071A3 (en)||2004-07-13||2005-07-06||System and method for location based policy management|
|Publication Number||Publication Date|
|CA2567596A1 true true CA2567596A1 (en)||2006-02-16|
Family Applications (1)
|Application Number||Title||Priority Date||Filing Date|
|CA 2567596 Abandoned CA2567596A1 (en)||2004-07-13||2005-07-06||System and method for location based policy management|
Country Status (5)
|US (2)||US7286834B2 (en)|
|EP (1)||EP1766803A4 (en)|
|KR (1)||KR20070032673A (en)|
|CA (1)||CA2567596A1 (en)|
|WO (1)||WO2006017071A3 (en)|
Families Citing this family (110)
|Publication number||Priority date||Publication date||Assignee||Title|
|FR2812509B1 (en) *||2000-07-26||2002-12-27||Gemplus Card Int||Process for securisee recognition between two units of a radio frequency network|
|US7231219B2 (en) *||2002-12-17||2007-06-12||International Business Machines Corporation||Method, apparatus, and program for automated property adjustment in a cellular network|
|US8561175B2 (en) *||2003-02-14||2013-10-15||Preventsys, Inc.||System and method for automated policy audit and remediation management|
|US7725098B1 (en) *||2003-09-04||2010-05-25||Emc Corporation||Data message processing|
|US20050266857A1 (en) *||2004-05-27||2005-12-01||Nokia Corporation||Location based execution rights|
|US8924469B2 (en)||2008-06-05||2014-12-30||Headwater Partners I Llc||Enterprise access control and accounting allocation for access networks|
|US8725123B2 (en)||2008-06-05||2014-05-13||Headwater Partners I Llc||Communications device with secure data path processing agents|
|US8571541B2 (en) *||2004-07-15||2013-10-29||Avaya Inc.||Proximity-based authorization|
|WO2006017699A3 (en) *||2004-08-05||2006-07-06||Meshnetworks Inc||Bandwidth efficient system and method for ranging nodes in a wireless communication network|
|US7409220B2 (en) *||2004-08-05||2008-08-05||Meshnetworks, Inc.||Autonomous reference system and method for monitoring the location and movement of objects|
|US7730485B2 (en)||2004-08-10||2010-06-01||At&T Intellectual Property I, L.P.||System and method for advertising to a Wi-Fi device|
|US7869790B2 (en)||2004-09-24||2011-01-11||Scenera Technologies, Llc||Policy-based controls for wireless cameras|
|US7400891B2 (en) *||2004-11-10||2008-07-15||At&T Delaware Intellectual Property, Inc.||Methods, systems and computer program products for remotely controlling wireless terminals|
|US7826835B2 (en) *||2004-12-16||2010-11-02||Intel Corporation||Mobile phone policy management|
|US8594704B2 (en) *||2004-12-16||2013-11-26||Atc Technologies, Llc||Location-based broadcast messaging for radioterminal users|
|US8145241B2 (en) *||2005-06-30||2012-03-27||Armstrong, Quinton Co. LLC||Methods, systems, and computer program products for role- and locale-based mobile user device feature control|
|US8831194B2 (en)||2005-06-30||2014-09-09||Emc Corporation||Telephonic communication redirection and compliance processing|
|US8059805B2 (en) *||2005-06-30||2011-11-15||Emc Corporation||Enhanced services provided using communication redirection and processing|
|US8605878B2 (en) *||2005-06-30||2013-12-10||Emc Corporation||Redirecting and mirroring of telephonic communications|
|US9226259B2 (en)||2005-07-14||2015-12-29||Binj Laboratories, Inc.||Systems and methods for detecting and controlling transmission devices|
|US9066194B2 (en)||2005-07-14||2015-06-23||Binj Laboratories, Inc.||System and method for detecting and controlling transmission devices|
|KR100719118B1 (en) *||2005-10-27||2007-05-17||삼성전자주식회사||Method and system for limitting a function of device in specific perimeters|
|US8177632B2 (en) *||2005-11-09||2012-05-15||Wms Gaming Inc.||Information flow control for gaming machines requiring server support|
|EP1969883B1 (en) *||2005-12-12||2009-07-01||Telenor ASA||Method, subscriber identity module and system for providing mobile communication terminal location data|
|US20070167175A1 (en) *||2006-01-17||2007-07-19||Tony Wong||Wireless virtual-network systems and methods to operate the same|
|US20070185980A1 (en) *||2006-02-03||2007-08-09||International Business Machines Corporation||Environmentally aware computing devices with automatic policy adjustment features|
|US20070206546A1 (en) *||2006-03-02||2007-09-06||Alberth William P Jr||Method and apparatus for preventing denial of service attacks on cellular infrastructure access channels|
|CN101496387B (en)||2006-03-06||2012-09-05||思科技术公司||System and method for access authentication in a mobile wireless network|
|US7715562B2 (en) *||2006-03-06||2010-05-11||Cisco Technology, Inc.||System and method for access authentication in a mobile wireless network|
|US9060071B1 (en) *||2006-08-01||2015-06-16||Oracle America, Inc.||Bluetooth location identifier and general information broadcaster|
|US7414529B2 (en) *||2006-08-04||2008-08-19||International Business Machines Corporation||Disablement of camera functionality for a portable device|
|US7769394B1 (en) *||2006-10-06||2010-08-03||Sprint Communications Company L.P.||System and method for location-based device control|
|US7853691B2 (en) *||2006-11-29||2010-12-14||Broadcom Corporation||Method and system for securing a network utilizing IPsec and MACsec protocols|
|US8102825B2 (en) *||2006-11-30||2012-01-24||Kyocera Corporation||Detection of a multi-mode portable communication device at a mesh network|
|US7969930B2 (en) *||2006-11-30||2011-06-28||Kyocera Corporation||Apparatus, system and method for managing wireless local area network service based on a location of a multi-mode portable communication device|
|US9532399B2 (en) *||2006-11-30||2016-12-27||Kyocera Corporation||Apparatus, system and method for managing wireless local area network service to a multi-mode portable communication device|
|US7978667B2 (en) *||2006-11-30||2011-07-12||Kyocera Corporation||Management of WLAN and WWAN communication services to a multi-mode wireless communication device|
|US8103285B2 (en) *||2007-04-19||2012-01-24||Kyocera Corporation||Apparatus, system and method for determining a geographical location of a portable communication device|
|US20080279290A1 (en) *||2007-05-09||2008-11-13||At&T Knowledge Ventures, Lp||Technique for Operating a Communication System at a Higher Spectral Utilization for Wireless Broadband Applications|
|US20090017839A1 (en) *||2007-07-11||2009-01-15||Broadcom Corporation||Wireless network with enhanced security by real-time identification of a location of a received packet source|
|KR101236910B1 (en)||2007-10-09||2013-02-25||삼성전자주식회사||Method for performing operation related with other device through Near Field Communication and apparatus therfor|
|US8112785B1 (en)||2007-12-31||2012-02-07||Symantec Corporation||Systems and methods for administering policies for physical locations|
|US8595336B1 (en) *||2008-02-01||2013-11-26||Wimm Labs, Inc.||Portable universal personal storage, entertainment, and communication device|
|US20090215400A1 (en) *||2008-02-26||2009-08-27||Henry Chang||Pilot signal transmission management|
|US8233433B2 (en) *||2008-02-26||2012-07-31||Kyocera Corporation||Apparatus, system and method for initiating WLAN service using beacon signals|
|CN101572854A (en) *||2008-04-28||2009-11-04||华为技术有限公司||Method, system and equipment for strategy authorization|
|US9565707B2 (en)||2009-01-28||2017-02-07||Headwater Partners I Llc||Wireless end-user device with wireless data attribution to multiple personas|
|US8745191B2 (en)||2009-01-28||2014-06-03||Headwater Partners I Llc||System and method for providing user notifications|
|US8924543B2 (en)||2009-01-28||2014-12-30||Headwater Partners I Llc||Service design center for device assisted services|
|US9557889B2 (en)||2009-01-28||2017-01-31||Headwater Partners I Llc||Service plan design, user interfaces, application programming interfaces, and device management|
|US9647918B2 (en)||2009-01-28||2017-05-09||Headwater Research Llc||Mobile device and method attributing media services network usage to requesting application|
|US9270559B2 (en)||2009-01-28||2016-02-23||Headwater Partners I Llc||Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow|
|US9578182B2 (en)||2009-01-28||2017-02-21||Headwater Partners I Llc||Mobile device and service management|
|US8893009B2 (en)||2009-01-28||2014-11-18||Headwater Partners I Llc||End user device that secures an association of application to service policy with an application certificate check|
|US9571559B2 (en)||2009-01-28||2017-02-14||Headwater Partners I Llc||Enhanced curfew and protection associated with a device group|
|US9858559B2 (en)||2009-01-28||2018-01-02||Headwater Research Llc||Network service plan design|
|US8793758B2 (en)||2009-01-28||2014-07-29||Headwater Partners I Llc||Security, fraud detection, and fraud mitigation in device-assisted services systems|
|US9351193B2 (en)||2009-01-28||2016-05-24||Headwater Partners I Llc||Intermediate networking devices|
|US9755842B2 (en)||2009-01-28||2017-09-05||Headwater Research Llc||Managing service user discovery and service launch object placement on a device|
|FI20085604A0 (en) *||2008-06-18||2008-06-18||Elektrobit Wireless Comm Oy||Manage connections|
|US8693987B2 (en) *||2008-12-31||2014-04-08||Airvana Lp||Femto personal policy server|
|US9210569B2 (en) *||2008-12-31||2015-12-08||Commscope Technologies Llc||Femto personal proxy application client|
|JP4743305B2 (en) *||2009-01-06||2011-08-10||ソニー株式会社||Function control method according to boundary definition, the function control system according to boundary definition, function control server and a program according to boundary definition|
|US8402111B2 (en)||2009-01-28||2013-03-19||Headwater Partners I, Llc||Device assisted services install|
|US8635335B2 (en)||2009-01-28||2014-01-21||Headwater Partners I Llc||System and method for wireless network offloading|
|US8275830B2 (en)||2009-01-28||2012-09-25||Headwater Partners I Llc||Device assisted CDR creation, aggregation, mediation and billing|
|US8626115B2 (en)||2009-01-28||2014-01-07||Headwater Partners I Llc||Wireless network service interfaces|
|US9572019B2 (en)||2009-01-28||2017-02-14||Headwater Partners LLC||Service selection set published to device agent with on-device service selection|
|US8321526B2 (en)||2009-01-28||2012-11-27||Headwater Partners I, Llc||Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account|
|US9706061B2 (en)||2009-01-28||2017-07-11||Headwater Partners I Llc||Service design center for device assisted services|
|US8340634B2 (en)||2009-01-28||2012-12-25||Headwater Partners I, Llc||Enhanced roaming services and converged carrier networks with device assisted services and a proxy|
|US9392462B2 (en)||2009-01-28||2016-07-12||Headwater Partners I Llc||Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy|
|US9253663B2 (en)||2009-01-28||2016-02-02||Headwater Partners I Llc||Controlling mobile device communications on a roaming network based on device state|
|US8832777B2 (en)||2009-03-02||2014-09-09||Headwater Partners I Llc||Adapting network policies based on device service processor configuration|
|US8898293B2 (en)||2009-01-28||2014-11-25||Headwater Partners I Llc||Service offer set publishing to device agent with on-device service selection|
|US8346225B2 (en)||2009-01-28||2013-01-01||Headwater Partners I, Llc||Quality of service for device assisted services|
|US8391834B2 (en)||2009-01-28||2013-03-05||Headwater Partners I Llc||Security techniques for device assisted services|
|US8589541B2 (en)||2009-01-28||2013-11-19||Headwater Partners I Llc||Device-assisted services for protecting network capacity|
|US8548428B2 (en)||2009-01-28||2013-10-01||Headwater Partners I Llc||Device group partitions and settlement platform|
|US8406748B2 (en)||2009-01-28||2013-03-26||Headwater Partners I Llc||Adaptive ambient services|
|JP2010178867A (en) *||2009-02-05||2010-08-19||Fujifilm Corp||Radiography network system and radiographic image capturing system control method|
|US8165577B2 (en) *||2009-03-19||2012-04-24||Kyocera Corporation||Pilot signal transmission management|
|US8131846B1 (en) *||2009-07-06||2012-03-06||Symantec Corporation||Global, location-aware computer security|
|US8787174B2 (en) *||2009-12-31||2014-07-22||Tekelec, Inc.||Methods, systems, and computer readable media for condition-triggered policies|
|US9185510B2 (en) *||2010-03-03||2015-11-10||Tekelec, Inc.||Methods, systems, and computer readable media for managing the roaming preferences of mobile subscribers|
|US9917700B2 (en)||2010-03-15||2018-03-13||Tekelec, Inc.||Systems, methods, and computer readable media for policy enforcement correlation|
|US8812020B2 (en) *||2010-10-15||2014-08-19||Tekelec, Inc.||Methods, systems, and computer readable media for location-based policy enhancement|
|US8626156B2 (en)||2010-10-20||2014-01-07||Tekelec, Inc.||Methods, systems, and computer readable media for selective policy enhancement (PE) for high-usage roamers|
|US9026813B2 (en)||2010-11-22||2015-05-05||Qualcomm Incorporated||Establishing a power charging association on a powerline network|
|US8681622B2 (en)||2010-12-17||2014-03-25||Tekelec, Inc.||Policy and charging rules function (PCRF) and performance intelligence center (PIC) based congestion control|
|US9154826B2 (en)||2011-04-06||2015-10-06||Headwater Partners Ii Llc||Distributing content and service launch objects to mobile devices|
|US9003492B2 (en)||2011-06-21||2015-04-07||Qualcomm Incorporated||Secure client authentication and service authorization in a shared communication network|
|US9021278B2 (en)||2011-08-10||2015-04-28||Qualcomm Incorporated||Network association of communication devices based on attenuation information|
|US9106769B2 (en)||2011-08-10||2015-08-11||Tekelec, Inc.||Methods, systems, and computer readable media for congestion management in a diameter signaling network|
|US20130078963A1 (en) *||2011-09-23||2013-03-28||Ford Global Technologies, Llc||Method and Apparatus for Incoming Call Filtration and Message Delivery|
|US8429103B1 (en)||2012-06-22||2013-04-23||Google Inc.||Native machine learning service for user adaptation on a mobile platform|
|US8510238B1 (en)||2012-06-22||2013-08-13||Google, Inc.||Method to predict session duration on mobile devices using native machine learning|
|US8886576B1 (en)||2012-06-22||2014-11-11||Google Inc.||Automatic label suggestions for albums based on machine learning|
|US8897811B2 (en) *||2012-06-29||2014-11-25||Google Inc.||Systems and methods for aggregating missed call data and adjusting telephone settings|
|US9473928B2 (en)||2012-07-14||2016-10-18||Tekelec, Inc.||Methods, systems, and computer readable media for policy-based local breakout (LBO)|
|WO2014014829A1 (en)||2012-07-14||2014-01-23||Tekelec, Inc.||Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network|
|US9843603B2 (en) *||2012-10-16||2017-12-12||Dell Products, L.P.||Techniques for dynamic access control of input/output devices|
|JP6080183B2 (en)||2012-10-19||2017-02-15||マカフィー， インコーポレイテッド||Program for the store authentication security, methods, systems|
|WO2014159862A1 (en)||2013-03-14||2014-10-02||Headwater Partners I Llc||Automated credential porting for mobile devices|
|US9414348B2 (en)||2013-04-22||2016-08-09||Nokia Technologies Oy||Method and apparatus for determining dynamic access tokens for location-based services|
|US20160088608A1 (en) *||2013-04-30||2016-03-24||Telefonaktiebolaget L M Ericsson (Publ)||Radio communication policy allocation in a network node|
|US20150326617A1 (en) *||2014-05-06||2015-11-12||DoNotGeoTrack, Inc.||Privacy Control Processes for Mobile Devices, Wearable Devices, other Networked Devices, and the Internet of Things|
|CN105227524A (en)||2014-06-12||2016-01-06||阿里巴巴集团控股有限公司||Information security method and related devices|
|US20160078350A1 (en) *||2014-09-17||2016-03-17||Mark D. Yarvis||Contextual platform feature recommendations|
|CN105989280A (en) *||2015-02-10||2016-10-05||富泰华工业（深圳）有限公司||Application program authority management system, device and method|
Family Cites Families (30)
|Publication number||Priority date||Publication date||Assignee||Title|
|JP3052405B2 (en) *||1991-03-19||2000-06-12||株式会社日立製作所||Mobile communication system|
|US6758755B2 (en) *||1996-11-14||2004-07-06||Arcade Planet, Inc.||Prize redemption system for games executed over a wide area network|
|US5850444A (en)||1996-09-09||1998-12-15||Telefonaktienbolaget L/M Ericsson (Publ)||Method and apparatus for encrypting radio traffic in a telecommunications network|
|US6271757B1 (en) *||1997-12-19||2001-08-07||Invisible Fence, Inc.||Satellite animal containment system with programmable Boundaries|
|US6178506B1 (en)||1998-10-23||2001-01-23||Qualcomm Inc.||Wireless subscription portability|
|US6236852B1 (en)||1998-12-11||2001-05-22||Nortel Networks Limited||Authentication failure trigger method and apparatus|
|FI112433B (en) *||2000-02-29||2003-11-28||Nokia Corp||Location-bound services|
|DE60121924T2 (en) *||2000-03-13||2007-02-15||Nokia Corp.||Dienstanbietung in a communication system|
|EP1329127B1 (en) *||2000-10-27||2008-04-02||Nokia Corporation||Method and apparatus for securing a mobile electronic device based on location|
|US20030119480A1 (en) *||2001-02-26||2003-06-26||Jahangir Mohammed||Apparatus and method for provisioning an unlicensed wireless communications base station for operation within a licensed wireless communications system|
|US6907254B1 (en)||2001-03-08||2005-06-14||Cisco Technology, Inc.||Method and apparatus for controlling a quiet zone for wireless units|
|US20030017826A1 (en) *||2001-07-17||2003-01-23||Dan Fishman||Short-range wireless architecture|
|US20030118015A1 (en) *||2001-12-20||2003-06-26||Magnus Gunnarsson||Location based notification of wlan availability via wireless communication network|
|US7591020B2 (en) *||2002-01-18||2009-09-15||Palm, Inc.||Location based security modification system and method|
|US20030220116A1 (en) *||2002-04-23||2003-11-27||Axis Ab||Method and apparatus for determining the position of a portable device|
|US7551930B2 (en) *||2002-05-06||2009-06-23||Nokia Corporation||Location-based services for mobile stations using short range wireless technology|
|US7676232B2 (en) *||2002-05-16||2010-03-09||Telefonaktiebolaget Lm Ericsson (Publ)||Altitude determination and distribution in cellular communication systems|
|US20040014422A1 (en) *||2002-07-19||2004-01-22||Nokia Corporation||Method and system for handovers using service description data|
|US20040203602A1 (en) *||2002-09-12||2004-10-14||Broadcom Corporation||Enabling and controlling access to wireless hot spots|
|US7398090B2 (en) *||2002-09-13||2008-07-08||Hewlett-Packard Development Company, L.P.||Defining a smart area|
|WO2004028070A1 (en)||2002-09-23||2004-04-01||Credant Technologies, Inc.||Server, computer memory, and method to support security policy maintenance and distribution|
|US7715850B2 (en) *||2002-10-22||2010-05-11||Qualcomm Incorporated||Method and apparatus for identifying transmitters in a wireless communication system using power predictions|
|US7130646B2 (en) *||2003-02-14||2006-10-31||Atheros Communications, Inc.||Positioning with wireless local area networks and WLAN-aided global positioning systems|
|JP3999683B2 (en) *||2003-02-17||2007-10-31||株式会社エヌ・ティ・ティ・ドコモ||Wireless communication method and a base station|
|WO2004086667A3 (en) *||2003-03-24||2005-01-27||Strix Systems Inc||Self-configuring, self-optimizing wireless local area network system|
|US7085571B2 (en) *||2003-08-26||2006-08-01||Kyocera Wireless Corp.||System and method for using geographical location to determine when to exit an existing wireless communications coverage network|
|US20050239479A1 (en) *||2004-04-22||2005-10-27||Bednasz Kenneth M||Hands-free reminder for a wireless communications terminal|
|US20050277428A1 (en) *||2004-05-13||2005-12-15||International Business Machines Corporation||Location-based control of wireless communications device features|
|US7486956B2 (en) *||2004-05-19||2009-02-03||Qualcomm, Incorporated||Channel estimation and channel quality indicator (CQI) measurements for a high-speed downlink GPRS|
|US7469139B2 (en) *||2004-05-24||2008-12-23||Computer Associates Think, Inc.||Wireless manager and method for configuring and securing wireless access to a network|
Also Published As
|Publication number||Publication date||Type|
|Gruteser et al.||Privacy-Aware Location Sensor Networks.|
|US8401521B2 (en)||Enabling remote and anonymous control of mobile and portable multimedia devices for security, tracking and recovery|
|Gruteser et al.||Enhancing location privacy in wireless LAN through disposable interface identifiers: a quantitative analysis|
|Karygiannis et al.||Wireless network security|
|US7937067B2 (en)||System and method for an emergency location information service (E-LIS)|
|US20020055361A1 (en)||Location-based equipment control|
|US20040059914A1 (en)||Using signal-generated location information to identify and authenticate available devices|
|US20060246920A1 (en)||Method for providing a location information service in mobile communications system|
|US20130007848A1 (en)||Monitoring of smart mobile devices in the wireless access networks|
|US20080096529A1 (en)||Location-Based Security Rules|
|US7565529B2 (en)||Secure authentication and network management system for wireless LAN applications|
|US20100317317A1 (en)||EMERGENCY LOCATION INFORMATION GATEWAY FOR PUBLIC SAFETY ANSWERING POINTS (PSAPs) AND METHOD OF USE|
|Kindberg et al.||Context authentication using constrained channels|
|Buttyan et al.||Security and cooperation in wireless networks: thwarting malicious and selfish behavior in the age of ubiquitous computing|
|US20020169958A1 (en)||Authentication in data communication|
|US20060126645A1 (en)||Methods and systems for connecting mobile nodes to private networks|
|Brown et al.||Potential cognitive radio denial-of-service vulnerabilities and protection countermeasures: a multi-dimensional analysis and assessment|
|US20060161628A1 (en)||System and method of remotely locating a lost mobile communication device|
|US20080318592A1 (en)||Delivering telephony communications to devices proximate to a recipient after automatically determining the recipient's location|
|US20090170496A1 (en)||Device and method of managing data communications of a device in a network via a split tunnel mode connection|
|US6990587B2 (en)||Cryptographic architecture for secure, private biometric identification|
|US20070109983A1 (en)||Method and System for Managing Access to a Wireless Network|
|US6799032B2 (en)||Providing location data about a mobile entity|
|US9219816B2 (en)||System and method for automated whitelist management in an enterprise small cell network environment|
|US20060141981A1 (en)||Universal temporary communication ID with service integration|
Effective date: 20121206