U.S. patent application number 17/455999 was filed with the patent office on 2022-03-17 for location based sharing of a network access credential.
The applicant listed for this patent is AT&T Intellectual Property I, L.P., AT&T Mobility II LLC. Invention is credited to Mark Austin, Mario Kosseifi, Rick Tipton, Mostafa Tofighbakhsh.
Application Number | 20220086191 17/455999 |
Document ID | / |
Family ID | 1000005988619 |
Filed Date | 2022-03-17 |
United States Patent
Application |
20220086191 |
Kind Code |
A1 |
Tipton; Rick ; et
al. |
March 17, 2022 |
LOCATION BASED SHARING OF A NETWORK ACCESS CREDENTIAL
Abstract
A network access credential can be shared among devices based on
location information for a device. Location information can include
timed fingerprint location information. In an aspect, location
information can be associated with a location of user equipment.
This location information can be correlated with network access
credentials. Location information can be used to access a relevant
network access credential. The relevant network access credential
can be shared with other devices. In an embodiment, sharing a
network access credential can be between mobile devices. In another
embodiment, sharing a network access credential can be between a
remote computing device and a mobile device. Sharing a credential
can allow for access to a network without having to generate or
input new credentials.
Inventors: |
Tipton; Rick; (Corryton,
TN) ; Austin; Mark; (Roswell, GA) ; Kosseifi;
Mario; (Roswell, GA) ; Tofighbakhsh; Mostafa;
(Cupertino, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
AT&T Intellectual Property I, L.P.
AT&T Mobility II LLC |
Atlanta
Atlanta |
GA
GA |
US
US |
|
|
Family ID: |
1000005988619 |
Appl. No.: |
17/455999 |
Filed: |
November 22, 2021 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16803344 |
Feb 27, 2020 |
11212320 |
|
|
17455999 |
|
|
|
|
16434164 |
Jun 6, 2019 |
10594739 |
|
|
16803344 |
|
|
|
|
16108060 |
Aug 21, 2018 |
10362066 |
|
|
16434164 |
|
|
|
|
15603416 |
May 23, 2017 |
10084824 |
|
|
16108060 |
|
|
|
|
14957525 |
Dec 2, 2015 |
9667660 |
|
|
15603416 |
|
|
|
|
14530605 |
Oct 31, 2014 |
9232399 |
|
|
14957525 |
|
|
|
|
13291917 |
Nov 8, 2011 |
8909247 |
|
|
14530605 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 24/00 20130101;
H04L 63/08 20130101; H04W 12/08 20130101; H04W 12/06 20130101; H04W
12/61 20210101; H04L 67/18 20130101; H04W 12/43 20210101; H04W
12/04 20130101; H04L 63/20 20130101; H04W 12/63 20210101; H04L
67/306 20130101 |
International
Class: |
H04L 29/06 20060101
H04L029/06; H04W 24/00 20060101 H04W024/00; H04W 12/04 20060101
H04W012/04; H04W 12/08 20060101 H04W012/08; H04L 29/08 20060101
H04L029/08; H04W 12/06 20060101 H04W012/06 |
Claims
1. A method, comprising: facilitating, by a first user equipment
comprising a processor, wirelessly sharing, with a second user
equipment via a short-range communications interface, a network
access credential for a wireless local area network, to allow the
second user equipment to access a network device that is part of
the wireless local area network, wherein facilitating the
wirelessly sharing comprises: facilitating, by the first user
equipment, receiving, via the short-range communications interface,
a network access credential request, selecting, by the first user
equipment, the network access credential based on a user equipment
location, and determining, by the first user equipment, whether the
second user equipment has permission to access the wireless local
area network, based on a user identity associated with the second
user equipment.
2. The method of claim 1, further comprising facilitating, by the
first user equipment, communicating, via the short-range
communications interface, the network access credential to the
second user equipment.
3. The method of claim 1, wherein the user equipment location
comprises a location of the second user equipment.
4. The method of claim 1, wherein determining whether the second
user equipment has the permission comprises determining whether the
second user equipment is a member of a group of devices indicated
have permission to access the network device of the wireless local
area network.
5. The method of claim 1, wherein determining whether the second
user equipment has the permission comprises determining whether the
second user equipment is a member of a group of devices indicated
to be prohibited to access the network device of the wireless local
area network.
6. The method of claim 1, wherein determining whether the second
user equipment has the permission comprises accessing historical
network access information related to a previous access to the
network device of the wireless local area network, wherein the
previous access is from prior to determining whether the second
user equipment has the permission.
7. The method of claim 1, wherein determining whether the second
user equipment has the permission comprises identifying the second
user equipment as a device associated with the user identity.
8. The method of claim 1, wherein the network access credential
request comprises subscriber identity module information, and
wherein determining whether the second user equipment has
permission to access the wireless local area network comprises
performing a comparison using the subscriber identity module
information.
9. The method of claim 1, wherein the short-range communications
interface communicates according to a Bluetooth wireless protocol
or a Wi-Fi protocol.
10. The method of claim 1, wherein the network access credential
comprises a Wi-Fi key, a wired equivalent privacy key, a Wi-Fi
protected access key, or a Wi-Fi protected access II key.
11. The method of claim 1, wherein the network access credential
comprises a service set identifier and a Wi-Fi protected access II
key that are able to be used by the second user equipment to
identify and access the network device of the wireless local area
network.
12. The method of claim 1, wherein facilitating the wirelessly
sharing further comprises determining that the second user
equipment is within a defined effective range to share the network
access credential.
13. A first user equipment, comprising: a processor; and a memory
that stores executable instructions that, when executed by the
processor, facilitate performance of operations, comprising:
determining whether a second user equipment has a permission to
access an access point device, which is part of a wireless local
area network, in a region associated with the first user equipment,
based on historical network access information related to a
previous access to the access point device of the wireless local
area network; and in response to the determining indicating that
the second user equipment has the permission to access the access
point device, selecting a network access credential and wirelessly
sharing, via a short-range communications interface, the network
access credential with the second user equipment.
14. The first user equipment of claim 13, wherein the determining
whether the second user equipment has the permission is further
based on a user identity associated with the second user
equipment.
15. The first user equipment of claim 13, wherein selecting the
network access credential is based on user equipment location
information.
16. The first user equipment of claim 15, wherein the user
equipment location information comprises location information
associated with a location of the second user equipment.
17. The first user equipment device of claim 13, wherein the
operations further comprise receiving a network access credential
request comprising second user equipment subscriber identity module
information.
18. The first user equipment of claim 13, wherein the short-range
communications interface implements a wireless protocol from a
group of wireless protocols, the group of wireless protocols
comprising a Bluetooth protocol and a Wi-Fi protocol.
19. A non-transitory machine-readable medium, comprising executable
instructions that, when executed by a processor of a first mobile
device, facilitate performance of operations, comprising:
receiving, via a short-range communications interface from a second
mobile device, request data representative of a network access
credential request applicable to network equipment of a wireless
local area network, to enable the second mobile device to access
the network equipment of the wireless local area network; selecting
a network access credential based on a mobile device location;
determining that the second mobile device is permitted to access
the network equipment, based on a user identity determined to be
associated with the second mobile device; and in response to the
determining, sending the network access credential to the second
mobile device via the short-range communications interface.
20. The non-transitory machine-readable medium of claim 19, wherein
the network access credential comprises a Wi-Fi key to enable the
second mobile device to access the network equipment.
Description
RELATED APPLICATIONS
[0001] This application is a continuation of, and claims priority
to each of, U.S. patent application Ser. No. 16/803,344, filed on
27 Feb. 2020, and entitled "LOCATION BASED SHARING OF A NETWORK
ACCESS CREDENTIAL," which is a continuation of U.S. patent
application Ser. No. 16/434,164, filed on 6 Jun. 2019, now issued
as U.S. Pat. No. 10,594,739, and entitled "LOCATION BASED SHARING
OF A NETWORK ACCESS CREDENTIAL," which is a continuation of U.S.
patent application Ser. No. 16/108,060, filed on 21 Aug. 2018, now
issued as U.S. Pat No. 10,362,066, and entitled "LOCATION BASED
SHARING OF A NETWORK ACCESS CREDENTIAL," which is a continuation of
U.S. patent application Ser. No. 15/603,416, filed on 23 May 2017,
now issued as U.S. Pat. No. 10,084,824, and entitled "LOCATION
BASED SHARING OF A NETWORK ACCESS CREDENTIAL," which is a
continuation of U.S. patent application Ser. No. 14/957,525, filed
on 2 Dec. 2015, now issued as U.S. Pat. No. 9,667,660, and entitled
"LOCATION BASED SHARING OF A NETWORK ACCESS CREDENTIAL," which is a
continuation of U.S. patent application Ser. No. 14/530,605, filed
on 31 Oct. 2014, now issued as U.S. Pat. No. 9,232,399, and
entitled "LOCATION BASED SHARING OF A NETWORK ACCESS CREDENTIAL,"
which is a continuation of U.S. patent application Ser. No.
13/291,917, filed on 8 Nov. 2011, now issued as U.S. Pat. No.
8,909,247, and entitled "LOCATION BASED SHARING OF A NETWORK ACCESS
CREDENTIAL." The entireties of the aforementioned applications are
hereby incorporated by reference herein.
TECHNICAL FIELD
[0002] The disclosed subject matter relates to network access
credentials and, more particularly, to sharing network access
credentials.
BACKGROUND
[0003] Conventional sources of location information for mobile
devices are based on a wide variety of location determination
technologies, such as global positioning system (GPS) technology,
triangulation, multilateration, etc. These sources of data have
provided the opportunity to capture location information for a
device and share it with another device, which can allow
non-location enabled devices to participate, at some level, in
location-centric services. In contrast to conventional systems that
rely on technologies such as GPS, triangulation, multilateration,
etc., the use of timed fingerprint location (TFL) technology can
provide advantages over the conventional technologies. For example,
GPS is well known to be energy intensive and to suffer from signal
confusion in areas with interference between the satellite
constellation and the GPS enabled device. Further, GPS is simply
not available on many mobile devices, especially where the devices
are cost sensitive. Multilateration and triangulation technologies
are computationally intensive, which can result in processing time
issues and a corresponding level of energy consumption.
[0004] The above-described deficiencies of conventional mobile
device location data sources for transportation analytics is merely
intended to provide an overview of some of problems of current
technology, and are not intended to be exhaustive. Other problems
with the state of the art, and corresponding benefits of some of
the various non-limiting embodiments described herein, may become
further apparent upon review of the following detailed
description.
BRIEF DESCRIPTION OF DRAWINGS
[0005] FIG. 1 is an illustration of a system that facilitates
sharing a network access credential based on location information
in accordance with aspects of the subject disclosure.
[0006] FIG. 2 is a depiction of a system that facilitates sharing a
network access credential based on timed fingerprint location
information in accordance with aspects of the subject
disclosure.
[0007] FIG. 3 illustrates a system that facilitates sharing a
network access credential based on timed fingerprint location
information in accordance with aspects of the subject
disclosure.
[0008] FIG. 4 illustrates an exemplary system including sharing a
network access credential based on location information in
accordance with aspects of the subject disclosure.
[0009] FIG. 5 illustrates an exemplary system including sharing a
network access credential based on location information in
accordance with aspects of the subject disclosure.
[0010] FIG. 6 illustrates a method facilitating sharing a network
access credential based on location information in accordance with
aspects of the subject disclosure.
[0011] FIG. 7 illustrates a method for sharing a network access
credential based on timed fingerprint location information in
accordance with aspects of the subject disclosure.
[0012] FIG. 8 illustrates a method facilitating sharing a network
access credential based on timed fingerprint location information
in accordance with aspects of the subject disclosure.
[0013] FIG. 9 is a block diagram of an exemplary embodiment of a
mobile network platform to implement and exploit various features
or aspects of the subject disclosure.
[0014] FIG. 10 illustrates a block diagram of a computing system
operable to execute the disclosed systems and methods in accordance
with an embodiment.
DETAILED DESCRIPTION
[0015] The presently disclosed subject matter illustrates sharing a
network access credential based on location information. Location
information can be determined from timed fingerprint location (TFL)
information. Similarly, location information can be determined from
GPS information, multilateration, triangulation, etc., though TFL
information can provide advantages over these more conventional
location determination technologies, as disclosed herein.
[0016] Sharing network access credentials can allow devices to
access a network based on the shared credential. This can be
advantageous over acquiring new credentials. As an example, where a
first user equipment (UE) has network access credentials for a
local area network (LAN), these network access credentials can be
shared with a second UE to allow the second UE to access the LAN.
This can eliminate, for example, the need to go through a
registration process for new credentials for the second UE. Given
that several network access credentials can be associated with the
first UE, these credentials can be related to the location of the
UE, such as a network access credential for a home LAN, a work LAN,
a school LAN, an access point at a local coffee shop, etc.
Selection of a network access credential to share can be based on a
location, for example, the UE can share the home LAN network access
credential when the UE is located in a region associated with the
home LAN. TFL information can be employed advantageously in
determining a location as a basis for receiving a network access
credential.
[0017] TFL information can include location information or timing
information as disclosed in more detail in U.S. Ser. No. 12/712,424
filed Feb. 25, 2010, which application is hereby incorporated by
reference in its entirety. Further, such information can be
accessed from active state or idle state user equipment as
disclosed in more detail in U.S. Ser. No. 12/836,471, filed Jul.
14, 2010, which application is also hereby incorporated by
reference in its entirety. As such, TFL information component can
facilitate access to location information or timing information for
a mobile device or user equipment (UE) in an active or idle state.
TFL information can be information from systems in a timed
fingerprint location wireless environment, such as a TFL component
of a wireless telecommunications carrier. As a non-limiting
example, UEs, including mobile devices not equipped with a GPS-type
system, can be associated with TFL information, which can
facilitate determining a location for a UE based on the timing
information associated with the UE.
[0018] In an aspect, TFL information can include information to
determine a differential value for a NodeB site pair and a bin grid
frame, as disclosed in more detail in incorporated U.S. Ser. No.
12/712,424. A centroid region (possible locations between any site
pair) for an observed time value associated with any NodeB site
pair (NBSP) can be calculated and is related to the determined
value (in units of chip) from any pair of NodeBs. When UE time data
is accessed, a value look-up can be initiated (e.g., a lookup for
"DV(?,X)" as disclosed in more detail in the application
incorporated herein by reference). Relevant NBSPs can be
prioritized as part of the look-up. Further, the relevant pairs can
be employed as an index to lookup a first primary set. As an
example, time data for a UE can be accessed in relation to a
locating event in a TFL wireless carrier environment. In this
example, it can be determined that a NBSP, with a first reference
frame, be used for primary set lookup with the computed DV(?,X)
value as the index. This can for example return a set of bin grid
frame locations forming a hyperbola between the NodeBs of the NBSP.
A second lookup can then be performed for an additional relevant
NBSP, with a second reference frame, using the same value DV(?,X),
as an index into the data set. Continuing the example, the returned
set for the look up with second NBSP can return a second set of bin
grid frames. Thus, the UE is likely located in both sets of bin
grid frames. Therefore, where the UE is likely in both sets, it is
probable that the location for the UE is at an intersection of the
two sets. Additional NBSPs can be included to further narrow the
possible locations of the UE by providing additional intersections
among relevant bin grid sets. As such, employing TFL information
for location determination is demonstrably different from
conventional location determination techniques or systems such as
GPS, eGPS, triangulation or multilateration in wireless carrier
environments, near field techniques, or proximity sensors.
[0019] Moreover, whereas TFL can be operable in a wide array of
current and legacy devices without any substantial dependence on
GPS technologies, a greater number of mobile devices can act as TFL
source devices than would be expected for GPS-enabled devices at
the current time. A greater number of data sources are generally
considered desirable in facilitating access to location
information. Further, where TFL information can be employed in a
lookup of location data sets, TFL can be much less computationally
intense than triangulation or multilateration technologies. Reduced
computational load is generally desirable in UE devices. TFL can
piggyback on timing signals employed in wireless
telecommunications, which systems are already deployed. A reduced
need to rollout additional hardware is generally considered
desirable. Additionally, by piggybacking on existing timing signals
and by reducing the computational load, TFL can be associated with
minimal additional energy expenditure in sharp contrast to GPS or
triangulation/multilateration technologies. Reduced energy
expenditure is generally related to a reduced battery drain in
mobile devices and is typically a highly desirable trait.
[0020] Various embodiments relate to sharing a network access
credential based on location. In one example embodiment, a system
comprises a location component that receives location information.
The exemplary system further comprises a credential component to
determine a network access credential based on the location
information. The network access credential can be distributed by
way of an interface component.
[0021] In a further embodiment, a method comprises receiving
location information. The location information can be for a user
equipment. The example method further comprises receiving a network
access credential based on the location information. The network
access credential can then be accessed in the exemplary method.
[0022] In another example embodiment, a computer-readable storage
medium comprises instructions for receiving location information
for a first user equipment and receiving a network access
credential based on the location information. The computer-readable
storage medium further comprises instructions for allowing access
to the network access credential. The access can be based on an
aspect of a request for access. The request for access can be
related to a second user equipment.
[0023] The subject disclosure is now described with reference to
the drawings, wherein like reference numerals are used to refer to
like elements throughout. In the following description, for
purposes of explanation, numerous specific details are set forth in
order to provide a thorough understanding of the subject
disclosure. It may be evident, however, that the subject disclosure
may be practiced without these specific details. In other
instances, well-known structures and devices are shown in block
diagram form in order to facilitate describing the subject
disclosure.
[0024] FIG. 1 is an illustration of a system 100, which facilitates
sharing a network access credential based on location information
in accordance with aspects of the subject disclosure. System 100
can include location component 110. Location component 110 can
facilitate access to location information. Location information can
be received from GPS components, multilateration components,
triangulation components, or any other location information
technology. In an embodiment, TFL information can be a source of
location information, e.g., location information derived from TFL
timing information, or can be a source of TFL timing information
that can facilitate determining a location. TFL timing information
can be for one or more NBSPs. TFL information can be derived from
timing associated with one or more NBSPs.
[0025] Location component 110 can be communicatively coupled with
credentials component 120. Credentials component 120 can select a
network access credential based on location information. Location
information can be correlated with one or more network access
credentials. Based on a location, one or more selected network
access credentials, e.g., network access credentials correlated
with location information, can be determined to be relevant. One or
more of these relevant network access credentials can be made
available to be shared with another device. The shared network
access credential can be employed to facilitate access to the
related network by the device with which the network access
credential was shared.
[0026] In an embodiment, credentials component 120 can determine a
permission related to access of the one or more relevant network
access credentials. The permission can be based on nearly any
metric. As an example, the permission can be based on information
related to a network related to the relevant network access
credential, for instance, the network can be designated as "do not
share" which can lead to a permission prohibiting sharing of the
relevant network access credential. As a second example, the
network can be designated as "share with predetermined list A"
which can lead to a permission allowing sharing of the network
access credential with any device indicated on "list A". As a third
example, the permission can be based on time of day, for instance,
a permission can allow sharing in "off-peak" times. As a fourth
example, the permission can be associated with particular user
inputs, for instance, a password, a user identity, a personal
identification number, a kinetic action, etc. The exemplary kinetic
action, for instance, can be the act of "bumping" a first UE with a
second UE, e.g., emulating a fist-bump action between the two
devices, to designate that there is an affirmative permission to
share the relevant network access credential between the first and
second UE. Numerous other examples are within the scope of the
present subject matter despite not being explicitly recited for the
sake of clarity and brevity.
[0027] In an embodiment, credentials component 120 can be local
with regard to location component 110 or interface component 130.
As an example, system 100 can be embodied in a cellular phone and
can include credentials component 120 as a component of the
cellular phone. In this example, a network access credential
correlated with location information can be selected by credentials
component 120 at the cellular phone. This credential can then be
shared, for instance, with another cellular phone, laptop computer,
tablet computer, smartphone, etc.
[0028] In another embodiment, credentials component 120 can be
remote with regard to location component 110 or interface component
130. As another example, credentials component 120 can be embodied
in a corporate server remote from location component 110 or
interface component 130 that, for instance, can be embodied in a
tablet computer. In this example, location information, such as TFL
location information, can be received at the tablet computer and
communicated to the corporate server such that credentials
component can determine a network access credential based on the
location information from tablet computer. This network access
credential can then be shared for instance, with another cellular
phone, laptop computer, tablet computer, smartphone, etc. As an
example, a smartphone can enter a corporate campus having a
credentials component 120 embodied in a corporate server. As the
smartphone enters the corporate campus, the location information
can be communicated to the corporate server. This location
information can indicate that the smartphone is in an area served
by a corporate local area network (LAN). Based on the location
information indicating that the smartphone is within the area
served by the LAN, a set of LAN access credentials can be selected
by credentials component 120. These credentials can be communicated
to the smartphone and can facilitate the smartphone accessing the
LAN. It will be noted that the selection of the credentials in this
example is by location and not by actually detecting the LAN
itself. As such, where the smartphone has a Wi-Fi radio for
accessing the LAN, this radio can be turned off while credentials
can still be accessed based on the location, for instance, a
location determined by TFL information.
[0029] Credentials component 120 can be communicatively coupled
with interface component 130. Interface component 130 can
facilitate interaction with credentials component 120 from other
devices, for instance, a UE, laptop computer, tablet computer,
access point, femto-cell, etc. In an embodiment, interface
component 130 can include a short-range communications interface to
facilitate communication of a network access credential or request
for sharing a network access credential with devices, e.g., UEs, in
a region associated with a first device, e.g., a first UE. As an
example, interface component 130 can include Bluetooth components
that can facilitate wirelessly sharing a network access credential
by way of Bluetooth between a smartphone and a tablet computer. As
a second example, interface component 130 can include 802.xx
components, e.g., 802.11b, 802.11g, 802.11n, ZigBee, etc., that can
facilitate wirelessly sharing a network access credential by way of
the 802.xx technology between two laptop computers. As a third
example, interface component 130 can include 802.xx components that
can facilitate wirelessly sharing a network access credential by
way of the 802.xx technology between a tablet computer and an
access point, e.g., a Wi-Fi hotspot, corporate wireless LAN access
point, etc. Short-range communications can include other
technologies with effective wireless ranges up to about 500 meters,
though more typically on the order of meters to tens of meters.
[0030] FIG. 2 is a depiction of a system 200, which can facilitate
sharing a network access credential based on timed fingerprint
location information in accordance with aspects of the subject
disclosure. System 200 can include timed fingerprint location
information component (TFLIC) 210. TFLIC 210 can facilitate access
to location information. In an embodiment, TFL information can be
location information, e.g., location information derived from TFL
timing information, or can be TFL timing information that can
facilitate determining a location. TFL timing information can be
for one or more NBSPs. TFL information can be derived from timing
associated with one or more NBSPs.
[0031] TFLIC 210 can be communicatively coupled with credentials
component 220. Credentials component 220 can select a network
access credential based on location information. Location
information can be correlated with one or more network access
credentials. Based on a location, one or more selected network
access credentials can be determined to be relevant. One or more of
these relevant network access credentials can be made available to
be shared with another device.
[0032] Credentials component 220 can include credentials
information data (CID) component 222. CID component 222 can
facilitate access to credentials information data. Credentials
information data can include a network access key, e.g., wired
equivalent privacy (WEP) key, Wi-Fi protected access (WPA) or Wi-Fi
protected access II (WPA2) key, counter mode with cipher block
chaining message authentication code protocol (CCMP) key, advanced
encryption standard (AES) key, etc.; service set identifier (SSID)
information; network name, network location information, e.g.,
lat/long, address, range information, etc.; or other information
associated with accessing a network. A network access credential
can include credentials information data to facilitate access to
the associated network. As an example, a network access credential
can include an SSID and WPA2 key that can be used by a UE to
identify and access the network associated with the SSID.
[0033] Credentials component 220 can include network history
component 224. Network history component 224 can facilitate access
to historical network access information. Historical network access
information can include data on nearly any aspect of accessing a
network. As examples, historical network access information can
include one or more of historical dates of network access, lengths
of access, data throughput for a network access connection, quality
of service or level of service for a network access connection,
count of instances a network access connection has been accessed
successfully/unsuccessfully/total, data on security protocols for a
network access connection, cost of use for network access, etc.
Numerous other examples of historical network access information
will fall within the scope of the subject disclosure despite not
being explicitly recited herein for clarity and brevity. Historical
network access information can be employed in selecting relevant
network access credentials. As an example, where two network access
credentials are selected based on location information, a history
of poor performance for one of the networks can reduce the
relevance of that network with regard to the other network.
Credentials for this less relevant network can be less likely to be
shared.
[0034] Credentials component 220 can include device selection
component 226. Device selection component 226 can facilitate
selection of appropriate devices with which network access
credentials can be shared. As an example, device selection
component 226 can indicate that only devices that can be identified
as belonging to a designated user can be given access to shared
network access credentials. As a second example, device selection
component 226 can designate that only devices with accounts at a
particular telecommunications carrier can receive permission to
access shared network access credentials. As a third example,
device selection component 226 can designate that access to shared
network access credentials should conform to a list of devices, for
instance a list of phone numbers, customer numbers, account
numbers, employee identifiers, device identifiers, account user
names, etc.
[0035] Credentials component 220 can include permission component
228. Permission component 228 can be communicatively coupled to CID
component 222, network history component 224, or device selection
component 226. Permission component 228 can designate a permission
related to accessing a network access credential. As an example,
permission component 228 can designate that access to a network
access credential is permitted based on a requesting device being
identified and affirmatively designated by device selection
component 226 and a network access credential being associated with
a current location of a source device. As a second example,
permission component 228 can designate that access to a network
access credential is permitted based on a network access credential
being designated as highly relevant and being associated with a
current location of a source device. As a third example permission
component 228 can designate that access to a network access
credential is denied based on a requesting device not being
identified by device selection component 226 even where a network
access credential is associated with a current location of a source
device. In an embodiment, permission can be designated based on
application of a set of permission rules or algorithms to data
related to a network access credential, a requesting device, a
receiving device, network history, etc.
[0036] Credentials component 220 can be communicatively coupled to
interface component 230 that can include a transmitter component
232 and a receiver component 234. Transmitter component 232 and
receiver component 234 can facilitate sharing a network access
credential. In an embodiment transmitter component 232 and receiver
component 234 can facilitate sharing a network access credential
over a wireless interface and, as such, can include an antenna and
associated electronics for wireless communications. In another
embodiment, transmitter component 232 and receiver component 234
can facilitate determining aspects of an employed wireless
communications technology, such as determining a typical effective
range for sharing a network access credential over a Bluetooth
link. The determined effective range can then, for example, be
employed in determining a permission related to sharing the network
access credential.
[0037] FIG. 3 illustrates a system 300, which facilitates sharing a
network access credential based on timed fingerprint location
information in accordance with aspects of the subject disclosure.
System 300 can include timed fingerprint location information
component (TFLIC) 310. TFLIC 310 can facilitate access to location
information. In an embodiment, TFL information can be location
information, e.g., location information derived from TFL timing
information, or can be TFL timing information that can facilitate
determining a location. TFL timing information can be for one or
more NBSPs. TFL information can be derived from timing associated
with one or more NBSPs.
[0038] TFLIC 310 can be communicatively coupled with credentials
component 320. Credentials component 320 can select a network
access credential based on location information. Location
information can be correlated with one or more network access
credentials. Based on a location, one or more selected network
access credentials can be determined to be relevant. One or more of
these relevant network access credentials can be made available to
be shared with another device. In an embodiment, credentials
component 320 can be local with regard to location component 310 or
interface component 330. In another embodiment, credentials
component 320 can be remote with regard to location component 310
or interface component 330.
[0039] Credentials component 320 can be communicatively coupled
with remote credential provisioning (RCP) component 340. In an
embodiment, RCP component 340 can facilitate access to credential
information data. Credential information data can include
information relating to accessing a network. Credential information
data can therefore include passcodes, passwords, SSIDs, keys,
device identifiers, user identifiers, service provider identifiers,
network identifiers, etc. As an example, RCP component 340 can be a
cloud based data store including SSIDs, locations, and WEP keys.
Exemplary RCP component 340 can provide access to this information
from credentials component 320, which can be local to a device
including TFLIC 310, such as a smartphone, or remote from a device
including TFLIC 310, such as a laptop computer accessing a
credentials component 320 on a corporate computer system.
[0040] In an embodiment, RCP component 340 can designate a
permission related to accessing a network access credential. A
permission can be designated based on application of a set of
permission rules or algorithms to data related to a network access
credential, a requesting device, a receiving device, network
history, etc. As an example, RCP component 340 can receive an
identifier and can designate a permission relating to access of a
network access credential based on the identifier. In this example,
for instance, a smartphone requesting sharing of a network access
credential can be identified by telephone number that can be
compared to a list of phone numbers allowed access to a network
access credential. Where the exemplary telephone number is on the
list of allowed identifiers, a permission can be set allowing the
smartphone to access a shared network access credential. Where the
exemplary telephone number is not on the list of allow identifiers,
a permission can be set requiring additional verification before
allowing access, denying access entirely, allowing access to an
alternate network access credential, etc. It will be noted that
numerous other examples of a permission and logic associated with
determining the permission are considered within the scope of the
disclosed subject matter despite not being explicitly recited for
the sake of clarity and brevity.
[0041] Credentials component 320 can be communicatively coupled to
interface component 330 that can include a transmitter component
332 and a receiver component 334. Transmitter component 332 and
receiver component 334 can facilitate sharing a network access
credential. In an embodiment, transmitter component 332 and
receiver component 334 can be electronics or software for wireless
communications, such as those enumerated elsewhere herein.
[0042] Interface component 330 can be communicatively coupled to
antenna component 336. Antenna component 336 can facilitate
communicating between UEs by way of a radio access network. As an
example, UEs can communicate over a cellular telecommunications
network. Antenna component 336 can include medium-range antenna
components, long-range antenna components, etc. In an embodiment,
antenna component 336 does not include short-range antenna
components that are included in short-range antenna component 338.
In some embodiments, antenna component 336 can be employed to
facilitate communication between credentials component 320 and RCP
component 340.
[0043] Interface component 330 can be communicatively coupled to
short-range antenna component 338. Short-range antenna component
338 can facilitate communicating between UEs to facilitate sharing
TFL information by way of a short-range communication technology.
The short-range communication technology, for example, can be
infrared, optical, Bluetooth, ZigBee, 802.xx, etc. In some
embodiments, short-range antenna component 338 can be associated
with predetermined transmission ranges. These transmission ranges
can be, for example, associated with a personal area network that
can include devices within about 1-3 meters of the short-range
antenna; a home area network that can include devices within about
150 meters of the short-range antenna; a work area network that can
extend out to about 500 meters of the short-range antenna, etc.
Short-range communications can include technologies with effective
wireless ranges up to about 500 meters, though they can more
typically be on the order of meters to tens of meters. As an
example, a personal area network can be limited to devices on or
near a user and can, for example, be associated with a range of
about 1-3 meters. The exemplary short-range antenna component 338
covering about 1-3 meters would facilitate sharing network access
credentials from a source device to other devices within about 1-3
meters of the source device. This, for example, can be an efficient
way of sharing network access credentials among devices of a single
person, such as sharing a network access credential from a cell
phone to a laptop, watch, PDA, running shoe fob, etc., of a user to
enable those devices to access the network for which the user
already has credentials without needing to manually enter them on
each device. Other ranges can be employed and are within the scope
of the present disclosure despite not being explicitly recited.
[0044] FIG. 4 is illustrates an exemplary system 400 including
sharing a network access credential based on location information
in accordance with aspects of the subject disclosure. System 400
can include NodeBs 498A-D. Combinations of NodeBs 498A-D can act as
NBSPs for determining TFL information. UE 480 can be a TFL-enabled
UE. UE 480 can acquire TFL timing or location information relative
to NodeBs 498A-D. UE 480 can be associated with a short-range
communication region 483. UE 480 can be a source device for sharing
network access credentials. As an example, UE 480 can have network
access credentials for accessing a network associated with wireless
access point 484.
[0045] System 400 can further include UE 482. UE 482 can be a
requesting device. As an example, UE 482 can be without access
credentials for accessing wireless access point 484. UE 482 can
generate a request for shared network access credentials. This
request can be received by UE 480. UE 480 can determine its
location, e.g., based on TFL information. The location can be
correlated with a set of relevant network access credentials for a
network associated with access point 484. UE 480 can then determine
that the requesting device, UE 482, has permission to access the
set of relevant access credentials. This permission can be based,
for instance, on the wireless service provider being the same for
both UE 480 and UE 482, the network associated with access point
484 being open to all users, the users of UE 480 and UE 482 doing a
fist-bump kinetic action that indicates that a credentials transfer
between the two "bumped" device is approved by the users, etc. The
exemplary set of relevant network access credentials can then be
made accessible form UE 480, for instance, by transmitting the
credentials within the short-range communication region 483 with a
short-range antenna component (not illustrated). UE 482 can receive
the shared network access credentials. UE 482 can then employ the
credentials in accessing the network associated with access point
484.
[0046] In an aspect, UE 486 can be outside the short-range
communication region 483 and can thus be unable to receive the
shared network access credentials. In another aspect, UE 486 can be
determined not to have permission to access the shared network
access credentials. Where UE 486 does not have permission, but is
within range (not illustrated) transmitting the credentials in an
encoded manner can facilitate preventing UE 486 from accessing the
shared network access credentials. Other selective transmission
techniques can also be employed, for example, emailing the
credentials to an address designated by UE 482, texting the
credentials to UE 482, transmitting over a more limited range that
includes UE 482 but exclude UE 486, etc. These, and other
techniques not explicitly recited herein for clarity and brevity,
are to be considered within the scope of the presently disclosed
subject matter.
[0047] FIG. 5 illustrates an exemplary system 500 including sharing
a network access credential based on location information in
accordance with aspects of the subject disclosure. System 500 can
include NodeBs 598A-D. Combinations of NodeBs 598A-D can act as
NBSPs for determining TFL information. UE 580 can be a TFL-enabled
UE. UE 580 can acquire TFL timing or location information relative
to NodeBs 598A-D. UE 580 can be associated with a short-range
communication region 581. UE 580 can be a TFL source device.
[0048] UE 580 can be within region 583 associated, for example,
with a corporate campus for a corporation in building 582. Access
point 584 can service region 583 with access to a wireless network.
UE 580 can be communicatively connected to RCP component 540.
Further, UE 580 can request network access data from RCP component
540 based on the location of UE 580 within region 583. The location
of UE 580 within region 583 can be determined from location data,
e.g., TFL information.
[0049] In an embodiment, RCP component 540 can be embodied in a
computing system remote from UE 580. UE 580 can be associated with
a permission for access to a network access credential. As an
example, UE 580 can be a corporate issued smartphone that can have
a subscriber identity module (SIM). The SIM information can be
received by RCP component 540. The SIM information can be compared
to a list of corporate devices with permission to access the
network associate with access point 584. Where the SIM information
matches an identified and approved device, a network access
credential can be shared with UE 580. Sharing the network access
credential can be by any appropriate communications protocol, for
instance, texting, encrypted transmission, email, etc.
[0050] In some embodiments, RCP component 540 can be remote from
both UE 580 and building 582. RCP component 540 can be administered
by a third party. As examples, RCP component 540 can be a cloud
based component; RCP component 540 can be a corporate computing
element located in a foreign country; RCP component 540 can be a
corporate computing element administered by a vendor company;
etc.
[0051] FIGS. 4 and 5 are presented only to better illustrate some
of the benefits of the presently disclosed subject matter and are
explicitly not intended to limit the scope of the disclosure to the
various aspects particular to the presently illustrated
non-limiting example. In some embodiments, the use of GPS or other
location technology can be included instead of, or as complimentary
to, TFL information without departing from the scope of the present
disclosure. It is noteworthy that GPS or other location information
from a UE is not required to determine TFL information as disclosed
in the related application. Thus, even where legacy UEs, e.g., UEs
without GPS or eGPS capabilities, are represented in systems 400
and 500, the timing information from those legacy devices can be
employed in TFL information determinations. This can be
particularly useful in regions that have limited distribution of
GPS enabled UEs or where GPS functions poorly due to environmental
factors such as urban cores, mountainous regions, etc.
[0052] In view of the example system(s) described above, example
method(s) that can be implemented in accordance with the disclosed
subject matter can be better appreciated with reference to
flowcharts in FIG. 6-FIG. 8. For purposes of simplicity of
explanation, example methods disclosed herein are presented and
described as a series of acts; however, it is to be understood and
appreciated that the claimed subject matter is not limited by the
order of acts, as some acts may occur in different orders and/or
concurrently with other acts from that shown and described herein.
For example, one or more example methods disclosed herein could
alternatively be represented as a series of interrelated states or
events, such as in a state diagram. Moreover, interaction
diagram(s) may represent methods in accordance with the disclosed
subject matter when disparate entities enact disparate portions of
the methodologies. Furthermore, not all illustrated acts may be
required to implement a described example method in accordance with
the subject specification. Further yet, two or more of the
disclosed example methods can be implemented in combination with
each other, to accomplish one or more aspects herein described. It
should be further appreciated that the example methods disclosed
throughout the subject specification are capable of being stored on
an article of manufacture (e.g., a computer-readable medium) to
allow transporting and transferring such methods to computers for
execution, and thus implementation, by a processor or for storage
in a memory.
[0053] FIG. 6 illustrates aspects of a method 600 facilitating
sharing a network access credential based on location information
in accordance with aspects of the subject disclosure. At 610, TFL
information can be received. TFL information can be location
information derived from TFL timing information or TFL timing
information that can facilitate determining a location. TFL
information can include information to determine a differential
value for a NodeB site pair and a bin grid frame, as disclosed in
more detail in incorporated U.S. Ser. No. 12/712,424.
[0054] TFL information can include location information or timing
information as disclosed in more detail in U.S. Ser. No. 12/712,424
filed Feb. 25, 2010, which application is hereby incorporated by
reference in its entirety. Further, such information can be
received from active state or idle state user equipment as
disclosed in more detail in U.S. Ser. No. 12/836,471, filed Jul.
14, 2010, which application is also hereby incorporated by
reference in its entirety. As such, TFL information can include
location information for a UE, in an active or idle state, based on
timing information. As a non-limiting example, a mobile device,
including mobile devices not equipped with a GPS-type system, can
be located by looking up timing information associated with the
mobile device from a TFL information reference. As such, the
exemplary mobile device can be located using TFL information
without employing GPS-type techniques. In an aspect, TFL
information can include information to determine a DV(?,X). The
centroid region (possible locations between any site pair) for an
observed time value associated with any NodeB site pair (NBSP) can
be calculated and is related to the determined value (in units of
chip) from any pair of NodeBs. When UE time data is accessed, a
DV(?,X) look-up can be initiated. Relevant NBSPs can be prioritized
as part of the look-up. Further, the relevant pairs can be employed
as an index to lookup a first primary set. As an example, time data
for a UE can be accessed in relation to a locating event in a TFL
wireless carrier environment. In this example, it can be determined
that a NBSP, with a first reference frame, be used for primary set
lookup with the computed DV(?,X) value as the index. This can for
example return a set of bin grid frames locations forming a
hyperbola between the NodeBs of the NBSP. A second lookup can then
be performed for an additional relevant NBSP, with a second
reference frame, using the same value DV(?,X), as an index into the
data set. Continuing the example, the returned set for the look up
with second NBSP can return a second set of bin grid frames. Thus,
the UE is likely located in both sets of bin grid frames.
Therefore, where the UE is most likely in both sets, it is probable
that the location for the UE is at the intersection of the two
sets. Additional NBSPs can be included to further narrow the
possible locations of the UE. Employing TFL information for
location determination is demonstrably different from conventional
location determination techniques or systems such as GPS, eGPS,
triangulation or multilateration in wireless carrier environments,
near field techniques, or proximity sensors.
[0055] At 620, a network access credential can be received. The
network access credential can be correlated with location
information. As such, TFL information can be employed to select a
relevant network access credential. The network access credential
can include credentials information data to facilitate access to an
associated network. As an example, a network access credential can
include a network identifier and password that can be used by a UE
to identify and access the network associated with the network
identifier. Credentials information data can include a network
access key, e.g., WEP key, WPA or WPA2 key, CCMP key, AES key,
etc.; SSID information; network name, network location information,
e.g., lat/long, address, range information, etc.; or other
information associated with accessing a network.
[0056] At 630, a permission related to accessing the network access
credential can be determined. Access to a network can be related to
a permission. A permission can include open access, limited access,
or no access. Determining a permission can be associated with a
allowing a requesting entity access to a network having a
predetermined access policy. A predetermined access policy can be
embodied in a set of rules or a logic applied to determining a
permission based on the entity requesting access and the network to
be accessed. As an example, where a network is open to any user, a
permission can simply be determined to allow any user access to the
network. As a second example, where a network access policy limits
access to subscribers to a service, a permission can limit access
to a shared network access credential to subscribers to the
service, for instance by verifying a customer number, subscriber
identity, credit card number, device identifier, etc.
[0057] At 640, access to the network access credential can be
allowed based on the related permission. At this point, method 600
can end. A permission that limits access to the network access
credential can be applied at 640 to limit access to the network
access credential. As an example, where a first UE requests access
to a shared network access credential, a permission can be
determined denying access where the UE has not paid a monthly fee.
As such, at 640, the first UE would not be allowed to access the
network access credential by method 600. As a second example, where
a first UE requests access to a shared network access credential, a
permission can be determined granting access because the UE is
owned by Company X and the UE is located at Company X headquarters.
As such, at 640, the first UE would be allowed to access the
network access credential by method 600.
[0058] FIG. 7 illustrates aspects of a method 700 for sharing a
network access credential based on timed fingerprint location
information in accordance with aspects of the subject disclosure.
At 710, TFL information can be received from a first mobile device.
TFL information can be location information derived from TFL timing
information or TFL timing information that can facilitate
determining a location. At 720, a network access credential can be
accessed. The network access credential can be correlated with
location information, such as TFL information from the first mobile
device. This location information, e.g., TFL information, can be
employed to select a relevant network access credential. The
network access credential can include credentials information data
to facilitate access to an associated network.
[0059] At 730, a request for access to the network access
credential can be received. The request can be from a second mobile
device. At 740, in response to receiving the request for access to
the network access credential, a permission can be determined. The
permission can be related to allowing access to the relevant
network access credential. In an aspect, the permission can be
based on the request from the second mobile device. Allowing access
can be premised on satisfaction of an access policy. Wherein
allowing the second mobile device to access the relevant network
access credential would satisfy the access policy, a permission can
be determined that can facilitate access to the credential.
[0060] At 750, access to the network access credential can be
allowed for the second mobile device. Allowing access can be based
on the determined permission from 740. At this point, method 700
can end. As such, access can be granted where a permission has been
received indicating that access should be granted. This permission
can be based on the request from the second mobile device
satisfying a policy on access to the network access credential. As
an example, wherein the request is for access and the access policy
for the relevant network is that the network is open to any device,
a permission can be determined to allow access to the network
access credential. As a second example, where the request is for
access from a second device belonging to a user and the access
policy for the relevant network is to allow access to the devices
of the user, a permission can be determined to allow access to the
network access credential. As a third example, where the requesting
device is serviced by wireless carrier A and the access policy if
to allow access to devices serviced by wireless carrier B only, a
permission can be determined to deny access to the network access
credential.
[0061] FIG. 8 illustrates a method 800 facilitating sharing a
network access credential based on timed fingerprint location
information in accordance with aspects of the subject disclosure.
At 810, location information for a mobile device can be received.
The location information can be received at a remote credential
provisioning component. A remote credential provisioning component
can facilitate access to credential information data. Credential
information data can include information relating to accessing a
network. At 820, aspect information for the mobile device can be
received at the remote credential provisioning component. Aspect
information for the mobile device can include identification of a
user, a type of mobile device, a feature of the mobile device, a
service provider of the mobile device, a specification of the
mobile device, or any other information relating to an aspect of
the mobile device. This aspect information can be employed in
determining a permission when applying an access policy with regard
to the mobile device and a relevant network.
[0062] At 830, a network access credential can be access based on
the location information. Location information can be correlated
with networks and access credentials for those networks. As an
example, a vehicle network can be correlated with the position of
the vehicle of the vehicle network. Where a UE is collocated with
the vehicle, access to the vehicle network can be desirable. As
such, where an access credential to the vehicle network is
available, it can be correlated with the location of the vehicle as
well. Thus, where a first user wants to share the vehicle network
access credential with other devices in the location of the
vehicle, this can be facilitated by selecting relevant network
access credentials to share, e.g., selecting the vehicle network
credentials because they are collocated with the device seeking to
share those same credentials.
[0063] At 840, a permission can be determined. The permission can
be related to access of the network access credentials. The
permission can be based on the aspect information received at 820.
Allowing access can be premised on satisfaction of an access
policy. Wherein allowing the mobile device to access the relevant
network access credential would satisfy the access policy, a
permission can be determined that can facilitate access to the
credential. Satisfaction of the access policy can be based on the
aspect information. As an example, the aspect information can
include information of the owner of the mobile device. Where the
exemplary mobile device is owned by a corporation and used by a
corporation employee, this can satisfy an access policy to allow
network access to corporation owned devices. As such, a permission
allowing access to the network access credential can be determined
that will facilitate access to the credential based on satisfaction
of the exemplary access policy based on the aspect information of
the mobile device. Wherein aspect information can be related to
almost any aspect of the mobile device, a wide variety of access
policies can be employed in determining a permission. All such
aspect information permutations are within the present scope
despite not being explicitly recited for clarity and brevity.
[0064] At 850, access to the network access credential can be
allowed for the mobile device. Allowing access can be based on the
determined permission from 840. At this point, method 800 can end.
As an example, where a student registered at a university comes on
campus, the student's location can be associated with the student
being within an area serviced by the university wireless network.
The student's laptop can provide location information, for
instance, TFL information. This information can be received by
remote credential provisioning component of the university. The
student's laptop can also be identified by hardware address
information that can also be received at the remote credential
provisioning component of the university. A network access
credential can be accessed based on the location of the student's
laptop, for instance, a network access credential for a North
campus access point where the student laptop is located in the
North part of the university campus. A permission can be determined
to allow access to the North campus credential based on a
determination that being a student laptop satisfies an access
policy giving students access to university network resources. This
permission can allow the laptop to access the network access
credential for the North campus access point to facilitate the
laptop gaining access to the university network.
[0065] FIG. 9 presents an example embodiment 900 of a mobile
network platform 910 that can implement and exploit one or more
aspects of the subject matter described herein. Generally, wireless
network platform 910 can include components, e.g., nodes, gateways,
interfaces, servers, or disparate platforms, that facilitate both
packet-switched (PS) (e.g., internet protocol (IP), frame relay,
asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic
(e.g., voice and data), as well as control generation for networked
wireless telecommunication. As a non-limiting example, wireless
network platform 910 can be included as part of a
telecommunications carrier network. Mobile network platform 910
includes CS gateway node(s) 912 which can interface CS traffic
received from legacy networks like telephony network(s) 940 (e.g.,
public switched telephone network (PSTN), or public land mobile
network (PLMN)) or a signaling system #7 (SS7) network 970. Circuit
switched gateway node(s) 912 can authorize and authenticate traffic
(e.g., voice) arising from such networks. Additionally, CS gateway
node(s) 912 can access mobility, or roaming, data generated through
SS7 network 970; for instance, mobility data stored in a visited
location register (VLR), which can reside in memory 930. Further,
network access credentials can be stored in memory 930. Similarly,
location information, such as TFL information, can be stored in
memory 930. In an aspect, the TFL information can be based on
timing signals associated with communication between mobile network
platform 910 and mobile device 975 by way of RAN 970. Moreover, CS
gateway node(s) 912 interfaces CS-based traffic and signaling and
PS gateway node(s) 918. As an example, in a 3GPP UMTS network, CS
gateway node(s) 912 can be realized at least in part in gateway
GPRS support node(s) (GGSN). It should be appreciated that
functionality and specific operation of CS gateway node(s) 912, PS
gateway node(s) 918, and serving node(s) 916, can be provided and
dictated by radio technology(ies) utilized by mobile network
platform 910 for telecommunication.
[0066] In addition to receiving and processing CS-switched traffic
and signaling, PS gateway node(s) 918 can authorize and
authenticate PS-based data sessions with served mobile devices.
Data sessions can include traffic, or content(s), exchanged with
networks external to the wireless network platform 910, like wide
area network(s) (WANs) 950, enterprise network(s) 970, and service
network(s) 980, which can be embodied in local area network(s)
(LANs), can also be interfaced with mobile network platform 910
through PS gateway node(s) 918. It is to be noted that WANs 950 and
enterprise network(s) 960 can embody, at least in part, a service
network(s) like IP multimedia subsystem (IMS). Based on radio
technology layer(s) available in technology resource(s) 917,
packet-switched gateway node(s) 918 can generate packet data
protocol contexts when a data session is established; other data
structures that facilitate routing of packetized data also can be
generated. To that end, in an aspect, PS gateway node(s) 918 can
include a tunnel interface (e.g., tunnel termination gateway (TTG)
in 3GPP UMTS network(s) (not shown)) which can facilitate
packetized communication with disparate wireless network(s), such
as Wi-Fi networks.
[0067] In embodiment 900, wireless network platform 910 also
includes serving node(s) 916 that, based upon available radio
technology layer(s) within technology resource(s) 917, convey the
various packetized flows of data streams received through PS
gateway node(s) 918. It is to be noted that for technology
resource(s) 917 that rely primarily on CS communication, server
node(s) can deliver traffic without reliance on PS gateway node(s)
918; for example, server node(s) can embody at least in part a
mobile switching center. As an example, in a 3GPP UMTS network,
serving node(s) 916 can be embodied in serving GPRS support node(s)
(SGSN).
[0068] For radio technologies that exploit packetized
communication, server(s) 914 in wireless network platform 910 can
execute numerous applications that can generate multiple disparate
packetized data streams or flows, and manage (e.g., schedule,
queue, format . . . ) such flows. Such application(s) can include
add-on features to standard services (for example, provisioning,
billing, customer support . . . ) provided by wireless network
platform 910. Data streams (e.g., content(s) that are part of a
voice call or data session) can be conveyed to PS gateway node(s)
918 for authorization/authentication and initiation of a data
session, and to serving node(s) 916 for communication thereafter.
In addition to application server, server(s) 914 can include
utility server(s), a utility server can include a provisioning
server, an operations and maintenance server, a security server
that can implement at least in part a certificate authority and
firewalls as well as other security mechanisms, and the like. In an
aspect, security server(s) secure communication served through
wireless network platform 910 to ensure network's operation and
data integrity in addition to authorization and authentication
procedures that CS gateway node(s) 912 and PS gateway node(s) 918
can enact. Moreover, provisioning server(s) can provision services
from external network(s) like networks operated by a disparate
service provider; for instance, WAN 950 or Global Positioning
System (GPS) network(s) (not shown). Provisioning server(s) can
also provision coverage through networks associated to wireless
network platform 910 (e.g., deployed and operated by the same
service provider), such as femto-cell network(s) (not shown) that
enhance wireless service coverage within indoor confined spaces and
offload RAN resources in order to enhance subscriber service
experience within a home or business environment.
[0069] It is to be noted that server(s) 914 can include one or more
processors configured to confer at least in part the functionality
of macro network platform 910. To that end, the one or more
processor can execute code instructions stored in memory 930, for
example. It should be appreciated that server(s) 914 can include a
content manager 915, which operates in substantially the same
manner as described hereinbefore.
[0070] In example embodiment 900, memory 930 can store information
related to operation of wireless network platform 910. Other
operational information can include provisioning information of
mobile devices served through wireless platform network 910,
subscriber databases; application intelligence, pricing schemes,
e.g., promotional rates, flat-rate programs, couponing campaigns;
technical specification(s) consistent with telecommunication
protocols for operation of disparate radio, or wireless, technology
layers; and so forth. Memory 930 can also store information from at
least one of telephony network(s) 940, WAN 950, enterprise
network(s) 960, or SS7 network 970. In an aspect, memory 930 can
be, for example, accessed as part of a data store component or as a
remotely connected memory store.
[0071] In order to provide a context for the various aspects of the
disclosed subject matter, FIG. 10, and the following discussion,
are intended to provide a brief, general description of a suitable
environment in which the various aspects of the disclosed subject
matter can be implemented. While the subject matter has been
described above in the general context of computer-executable
instructions of a computer program that runs on a computer and/or
computers, those skilled in the art will recognize that the
disclosed subject matter also can be implemented in combination
with other program modules. Generally, program modules include
routines, programs, components, data structures, etc. that perform
particular tasks and/or implement particular abstract data
types.
[0072] In the subject specification, terms such as "store,"
"storage," "data store," data storage," "database," and
substantially any other information storage component relevant to
operation and functionality of a component, refer to "memory
components," or entities embodied in a "memory" or components
comprising the memory. It will be appreciated that the memory
components described herein can be either volatile memory or
nonvolatile memory, or can include both volatile and nonvolatile
memory.
[0073] By way of illustration, and not limitation, nonvolatile
memory, for example, can be included in volatile memory 1020,
non-volatile memory 1022 (see below), disk storage 1024 (see
below), and memory storage 1046 (see below). Further, nonvolatile
memory can be included in read only memory (ROM), programmable ROM
(PROM), electrically programmable ROM (EPROM), electrically
erasable ROM (EEPROM), or flash memory. Volatile memory can include
random access memory (RAM), which acts as external cache memory. By
way of illustration and not limitation, RAM is available in many
forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),
synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),
enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus
RAM (DRRAM). Additionally, the disclosed memory components of
systems or methods herein are intended to comprise, without being
limited to comprising, these and any other suitable types of
memory.
[0074] Moreover, it will be noted that the disclosed subject matter
can be practiced with other computer system configurations,
including single-processor or multiprocessor computer systems,
mini-computing devices, mainframe computers, as well as personal
computers, hand-held computing devices (e.g., PDA, phone, watch,
tablet computers, . . . ), microprocessor-based or programmable
consumer or industrial electronics, and the like. The illustrated
aspects can also be practiced in distributed computing environments
where tasks are performed by remote processing devices that are
linked through a communications network; however, some if not all
aspects of the subject disclosure can be practiced on stand-alone
computers. In a distributed computing environment, program modules
can be located in both local and remote memory storage devices.
[0075] FIG. 10 illustrates a block diagram of a computing system
1000 operable to execute the disclosed systems and methods in
accordance with an embodiment. Computer 1012 includes a processing
unit 1014, a system memory 1016, and a system bus 1018. In an
embodiment, computer 1012 can be part of the hardware of a timed
fingerprint location component. In a further embodiment, computer
1012 can be part of a remote credential provisioning component to
facilitate access to credentials. System bus 1018 couples system
components including, but not limited to, system memory 1016 to
processing unit 1014. Processing unit 1014 can be any of various
available processors. Dual microprocessors and other multiprocessor
architectures also can be employed as processing unit 1014.
[0076] System bus 1018 can be any of several types of bus
structure(s) including a memory bus or a memory controller, a
peripheral bus or an external bus, and/or a local bus using any
variety of available bus architectures including, but not limited
to, Industrial Standard Architecture (ISA), Micro-Channel
Architecture (MSA), Extended ISA (EISA), Intelligent Drive
Electronics , VESA Local Bus (VLB), Peripheral Component
Interconnect (PCI), Card Bus, Universal Serial Bus (USB), Advanced
Graphics Port (AGP), Personal Computer Memory Card International
Association bus (PCMCIA), Firewire (IEEE 1194), and Small Computer
Systems Interface (SCSI).
[0077] System memory 1016 includes volatile memory 1020 and
nonvolatile memory 1022. A basic input/output system (BIOS),
containing routines to transfer information between elements within
computer 1012, such as during start-up, can be stored in
nonvolatile memory 1022. By way of illustration, and not
limitation, nonvolatile memory 1022 can include ROM, PROM, EPROM,
EEPROM, or flash memory. Volatile memory 1020 includes RAM, which
acts as external cache memory. By way of illustration and not
limitation, RAM is available in many forms such as SRAM, dynamic
RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR
SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus
direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus
dynamic RAM (RDRAM).
[0078] Computer 1012 also includes removable/non-removable,
volatile/non-volatile computer storage media. FIG. 10 illustrates,
for example, disk storage 1024. Disk storage 1024 includes, but is
not limited to, devices like a magnetic disk drive, floppy disk
drive, tape drive, flash memory card, or memory stick. In addition,
disk storage 1024 can include storage media separately or in
combination with other storage media including, but not limited to,
an optical disk drive such as a compact disk ROM device (CD-ROM),
CD recordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive)
or a digital versatile disk ROM drive (DVD-ROM). To facilitate
connection of the disk storage devices 1024 to system bus 1018, a
removable or non-removable interface can be used, such as interface
1026. In an embodiment, disk storage 1024 can store TFL lookup
tables to facilitate lookup of location information based on NodeB
site pairs and time values. In another embodiment, disk storage
1024 can store TFL location information. In a further embodiment,
network access credentials can be stored on disk storage 1024.
Similarly, network history can be stored on disk storage 1024.
[0079] Computing devices can include a variety of media, which can
include computer-readable storage media or communications media,
which two terms are used herein differently from one another as
follows.
[0080] Computer-readable storage media can be any available storage
media that can be accessed by the computer and includes both
volatile and nonvolatile media, removable and non-removable media.
By way of example, and not limitation, computer-readable storage
media can be implemented in connection with any method or
technology for storage of information such as computer-readable
instructions, program modules, structured data, or unstructured
data. Computer-readable storage media can include, but are not
limited to, RAM, ROM, EEPROM, flash memory or other memory
technology, CD-ROM, digital versatile disk (DVD) or other optical
disk storage, magnetic cassettes, magnetic tape, magnetic disk
storage or other magnetic storage devices, or other tangible and/or
non-transitory media which can be used to store desired
information. Computer-readable storage media can be accessed by one
or more local or remote computing devices, e.g., via access
requests, queries or other data retrieval protocols, for a variety
of operations with respect to the information stored by the
medium.
[0081] Communications media can embody computer-readable
instructions, data structures, program modules, or other structured
or unstructured data in a data signal such as a modulated data
signal, e.g., a carrier wave or other transport mechanism, and
includes any information delivery or transport media. The term
"modulated data signal" or signals refers to a signal that has one
or more of its characteristics set or changed in such a manner as
to encode information in one or more signals. By way of example,
and not limitation, communication media include wired media, such
as a wired network or direct-wired connection, and wireless media
such as acoustic, RF, infrared and other wireless media.
[0082] It can be noted that FIG. 10 describes software that acts as
an intermediary between users and computer resources described in
suitable operating environment 1000. Such software includes an
operating system 1028. Operating system 1028, which can be stored
on disk storage 1024, acts to control and allocate resources of
computer system 1012. System applications 1030 take advantage of
the management of resources by operating system 1028 through
program modules 1032 and program data 1034 stored either in system
memory 1016 or on disk storage 1024. It is to be noted that the
disclosed subject matter can be implemented with various operating
systems or combinations of operating systems.
[0083] A user can enter commands or information into computer 1012
through input device(s) 1036. Input devices 1036 include, but are
not limited to, a pointing device such as a mouse, trackball,
stylus, touch pad, keyboard, microphone, joystick, game pad,
satellite dish, scanner, TV tuner card, digital camera, digital
video camera, web camera, cell phone, smartphone, tablet computer,
etc. These and other input devices connect to processing unit 1014
through system bus 1018 by way of interface port(s) 1038. Interface
port(s) 1038 include, for example, a serial port, a parallel port,
a game port, a universal serial bus (USB), an infrared port, a
Bluetooth port, an IP port, or a logical port associated with a
wireless service, etc. Output device(s) 1040 use some of the same
type of ports as input device(s) 1036.
[0084] Thus, for example, a USB port can be used to provide input
to computer 1012 and to output information from computer 1012 to an
output device 1040. Output adapter 1042 is provided to illustrate
that there are some output devices 1040 like monitors, speakers,
and printers, among other output devices 1040, which use special
adapters. Output adapters 1042 include, by way of illustration and
not limitation, video and sound cards that provide means of
connection between output device 1040 and system bus 1018. It
should be noted that other devices and/or systems of devices
provide both input and output capabilities such as remote
computer(s) 1044.
[0085] Computer 1012 can operate in a networked environment using
logical connections to one or more remote computers, such as remote
computer(s) 1044. Remote computer(s) 1044 can be a personal
computer, a server, a router, a network PC, a workstation, a
microprocessor based appliance, a peer device, or other common
network node and the like, and can include many or all of the
elements described relative to computer 1012.
[0086] For purposes of brevity, only a memory storage device 1046
is illustrated with remote computer(s) 1044. Remote computer(s)
1044 can be logically connected to computer 1012 through a network
interface 1048 and then physically connected by way of
communication connection 1050. Network interface 1048 encompasses
wire and/or wireless communication networks such as local-area
networks (LAN) and wide-area networks (WAN). LAN technologies
include Fiber Distributed Data Interface (FDDI), Copper Distributed
Data Interface (CDDI), Ethernet, Token Ring and the like. WAN
technologies include, but are not limited to, point-to-point links,
circuit switching networks like Integrated Services Digital
Networks (ISDN) and variations thereon, packet switching networks,
and Digital Subscriber Lines (DSL). As noted below, wireless
technologies may be used in addition to or in place of the
foregoing.
[0087] Communication connection(s) 1050 refer(s) to
hardware/software employed to connect network interface 1048 to bus
1018. While communication connection 1050 is shown for illustrative
clarity inside computer 1012, it can also be external to computer
1012. The hardware/software for connection to network interface
1048 can include, for example, internal and external technologies
such as modems, including regular telephone grade modems, cable
modems and DSL modems, ISDN adapters, and Ethernet cards.
[0088] The above description of illustrated embodiments of the
subject disclosure, including what is described in the Abstract, is
not intended to be exhaustive or to limit the disclosed embodiments
to the precise forms disclosed. While specific embodiments and
examples are described herein for illustrative purposes, various
modifications are possible that are considered within the scope of
such embodiments and examples, as those skilled in the relevant art
can recognize.
[0089] In this regard, while the disclosed subject matter has been
described in connection with various embodiments and corresponding
figures, where applicable, it is to be understood that other
similar embodiments can be used or modifications and additions can
be made to the described embodiments for performing the same,
similar, alternative, or substitute function of the disclosed
subject matter without deviating therefrom. Therefore, the
disclosed subject matter should not be limited to any single
embodiment described herein, but rather should be construed in
breadth and scope in accordance with the appended claims below.
[0090] As it employed in the subject specification, the term
"processor" can refer to substantially any computing processing
unit or device comprising, but not limited to comprising,
single-core processors; single-processors with software multithread
execution capability; multi-core processors; multi-core processors
with software multithread execution capability; multi-core
processors with hardware multithread technology; parallel
platforms; and parallel platforms with distributed shared memory.
Additionally, a processor can refer to an integrated circuit, an
application specific integrated circuit (ASIC), a digital signal
processor (DSP), a field programmable gate array (FPGA), a
programmable logic controller (PLC), a complex programmable logic
device (CPLD), a discrete gate or transistor logic, discrete
hardware components, or any combination thereof designed to perform
the functions described herein. Processors can exploit nano-scale
architectures such as, but not limited to, molecular and
quantum-dot based transistors, switches, and gates, in order to
optimize space usage or enhance performance of user equipment. A
processor may also be implemented as a combination of computing
processing units.
[0091] As used in this application, the terms "component,"
"system," "platform," "layer," "selector," "interface," and the
like are intended to refer to a computer-related entity or an
entity related to an operational apparatus with one or more
specific functionalities, wherein the entity can be either
hardware, a combination of hardware and software, software, or
software in execution. As an example, a component may be, but is
not limited to being, a process running on a processor, a
processor, an object, an executable, a thread of execution, a
program, and/or a computer. By way of illustration and not
limitation, both an application running on a server and the server
can be a component. One or more components may reside within a
process and/or thread of execution and a component may be localized
on one computer and/or distributed between two or more computers.
In addition, these components can execute from various computer
readable media having various data structures stored thereon. The
components may communicate via local and/or remote processes such
as in accordance with a signal having one or more data packets
(e.g., data from one component interacting with another component
in a local system, distributed system, and/or across a network such
as the Internet with other systems via the signal). As another
example, a component can be an apparatus with specific
functionality provided by mechanical parts operated by electric or
electronic circuitry, which can be operated by a software or
firmware application executed by a processor, wherein the processor
can be internal or external to the apparatus and executes at least
a part of the software or firmware application. As yet another
example, a component can be an apparatus that provides specific
functionality through electronic components without mechanical
parts, the electronic components can include a processor therein to
execute software or firmware that confers at least in part the
functionality of the electronic components.
[0092] In addition, the term "or" is intended to mean an inclusive
"or" rather than an exclusive "or." That is, unless specified
otherwise, or clear from context, "X employs A or B" is intended to
mean any of the natural inclusive permutations. That is, if X
employs A; X employs B; or X employs both A and B, then "X employs
A or B" is satisfied under any of the foregoing instances.
Moreover, articles "a" and "an" as used in the subject
specification and annexed drawings should generally be construed to
mean "one or more" unless specified otherwise or clear from context
to be directed to a singular form.
[0093] Moreover, terms like "user equipment (UE)," "mobile
station," "mobile," subscriber station," "subscriber equipment,"
"access terminal," "terminal," "handset," and similar terminology,
refer to a wireless device utilized by a subscriber or user of a
wireless communication service to receive or convey data, control,
voice, video, sound, gaming, or substantially any data-stream or
signaling-stream. The foregoing terms are utilized interchangeably
in the subject specification and related drawings. Likewise, the
terms "access point (AP)," "base station," "Node B," "evolved Node
B (eNode B)," "home Node B (HNB)," "home access point (HAP)," and
the like, are utilized interchangeably in the subject application,
and refer to a wireless network component or appliance that serves
and receives data, control, voice, video, sound, gaming, or
substantially any data-stream or signaling-stream to and from a set
of subscriber stations or provider enabled devices. Data and
signaling streams can include packetized or frame-based flows.
[0094] Additionally, the term "core-network", "core", "core carrier
network", or similar terms can refer to components of a
telecommunications network that provide some or all of aggregation,
authentication, call control and switching, charging, service
invocation, or gateways. Aggregation can refer to the highest level
of aggregation in a service provider network wherein the next level
in the hierarchy under the core nodes can be the distribution
networks and then the edge networks. UEs do not normally connect
directly to the core networks of a large service provider but can
be routed to the core by way of a switch or radio area network.
Authentication can refer to determinations regarding whether the
user requesting a service from the telecom network is authorized to
do so within this network or not. Call control and switching can
refer determinations related to the future course of a call stream
across carrier equipment based on the call signal processing.
Charging can be related to the collation and processing of charging
data generated by various network nodes. Two common types of
charging mechanisms found in present day networks can be prepaid
charging and postpaid charging. Service invocation can occur based
on some explicit action (e.g. call transfer) or implicitly (e.g.,
call waiting). It is to be noted that service "execution" may or
may not be a core network functionality as third party
network/nodes may take part in actual service execution. A gateway
can be present in the core network to access other networks.
Gateway functionality can be dependent on the type of the interface
with another network.
[0095] Furthermore, the terms "user," "subscriber," "customer,"
"consumer," "prosumer," "agent," and the like are employed
interchangeably throughout the subject specification, unless
context warrants particular distinction(s) among the terms. It
should be appreciated that such terms can refer to human entities
or automated components (e.g., supported through artificial
intelligence, as through a capacity to make inferences based on
complex mathematical formalisms), that can provide simulated
vision, sound recognition and so forth.
[0096] Aspects, features, or advantages of the subject matter can
be exploited in substantially any, or any, wired, broadcast,
wireless telecommunication, radio technology or network, or
combinations thereof. Non-limiting examples of such technologies or
networks include Geocast technology; broadcast technologies (e.g.,
sub-Hz, ELF, VLF, LF, MF, HF, VHF, UHF, SHF, THz broadcasts, etc.);
Ethernet; X.25; powerline-type networking (e.g., PowerLine AV
Ethernet, etc.); femto-cell technology; Wi-Fi; Zigbee, other 802.XX
wireless technologies, Worldwide Interoperability for Microwave
Access (WiMAX); Enhanced General Packet Radio Service (Enhanced
GPRS); Third Generation Partnership Project (3GPP or 3G) Long Term
Evolution (LTE); 3GPP Universal Mobile Telecommunications System
(UMTS) or 3GPP UMTS; Third Generation Partnership Project 2 (3GPP2)
Ultra Mobile Broadband (UMB); High Speed Packet Access (HSPA); High
Speed Downlink Packet Access (HSDPA); High Speed Uplink Packet
Access (HSUPA); GSM Enhanced Data Rates for GSM Evolution (EDGE)
Radio Access Network (RAN) or GERAN; UMTS Terrestrial Radio Access
Network (UTRAN); or LTE Advanced.
[0097] What has been described above includes examples of systems
and methods illustrative of the disclosed subject matter. It is, of
course, not possible to describe every combination of components or
methodologies here. One of ordinary skill in the art may recognize
that many further combinations and permutations of the claimed
subject matter are possible. Furthermore, to the extent that the
terms "includes," "has," "possesses," and the like are used in the
detailed description, claims, appendices and drawings such terms
are intended to be inclusive in a manner similar to the term
"comprising" as "comprising" is interpreted when employed as a
transitional word in a claim.
* * * * *