U.S. patent application number 13/223876 was filed with the patent office on 2011-12-22 for system for application server autonomous access across different types of access technology networks.
This patent application is currently assigned to INTERDIGITAL TECHNOLOGY CORPORATION. Invention is credited to Alan Gerald Carlton, Narayan Parappil Menon, Debashish Purkayastha.
Application Number | 20110310876 13/223876 |
Document ID | / |
Family ID | 34594962 |
Filed Date | 2011-12-22 |
United States Patent
Application |
20110310876 |
Kind Code |
A1 |
Carlton; Alan Gerald ; et
al. |
December 22, 2011 |
SYSTEM FOR APPLICATION SERVER AUTONOMOUS ACCESS ACROSS DIFFERENT
TYPES OF ACCESS TECHNOLOGY NETWORKS
Abstract
An Application Server Autonomous Access (ASAA) system for
providing autonomous access to a wireless infrastructure by devices
employing different types of access technology. The system includes
a server, having an associated data storage device, for storing at
least one policy, and a plurality of subnetworks, coupled to
server, for providing access to the server. The plurality of
subnetworks employ at least two different types of access
technology. A plurality of wireless transmit/receive units (WTRUs)
are wirelessly coupled to at least one of the subnetworks. The
server monitors the wireless coupling and, depending upon the at
least one policy, switches the WTRUs between different ones of the
subnetworks.
Inventors: |
Carlton; Alan Gerald;
(Mineola, NY) ; Menon; Narayan Parappil; (Syosset,
NY) ; Purkayastha; Debashish; (Pottstown,
PA) |
Assignee: |
INTERDIGITAL TECHNOLOGY
CORPORATION
Wilmington
DE
|
Family ID: |
34594962 |
Appl. No.: |
13/223876 |
Filed: |
September 1, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10987773 |
Nov 12, 2004 |
8014367 |
|
|
13223876 |
|
|
|
|
60519440 |
Nov 12, 2003 |
|
|
|
60623091 |
Oct 28, 2004 |
|
|
|
Current U.S.
Class: |
370/338 |
Current CPC
Class: |
H04W 88/06 20130101;
H04W 4/02 20130101; H04W 84/12 20130101; H04W 84/10 20130101; H04W
40/00 20130101; H04L 67/16 20130101; H04W 24/00 20130101; H04W
36/14 20130101; H04L 67/18 20130101 |
Class at
Publication: |
370/338 |
International
Class: |
H04W 84/02 20090101
H04W084/02 |
Claims
1. A method implemented in a mobility information server, the
method comprising: communicating with a wireless transmit/receive
unit (WTRU) using Internet Protocol (IP) via a first access network
of a first access technology type; transmitting mobility-related
information to the WTRU; and communicating with the WTRU using IP
via a second access network of a second access technology type on a
condition that the WTRU transitions from the first access network
of the first access technology type to the second access network of
the second access technology type, wherein the second access
technology type is different from the first access technology
type.
2. The method of claim 1 wherein the mobility information server is
an Application Server Autonomous Access (ASAA) server.
3. The method of claim 1 further comprising obtaining a permanent
identity of the WTRU.
4. The method of claim 3 further comprising sending
mobility-related information regarding the first and the second
access network to the WTRU based on a mobility policy and the
permanent identity of the WTRU.
5. The method of claim 1 further comprising receiving location
information regarding the WTRU via a registration procedure.
6. The method of claim 1 wherein the mobility-related information
includes location information.
7. The method of claim 1 wherein the mobility-related information
includes access network profile information or network capability
information.
8. The method of claim 1, further comprising: maintaining a list of
a plurality of access networks which are available for the WTRU to
connect to.
9. The method of claim 1 wherein the first access network is one of
a wireless local area network (WLAN), a wireless private area
network (WPAN), a universal mobile telecommunications system (UMTS)
of a terrestrial radio access network (UTRAN), a code division
multiple access (CDMA) 2000 network, a small office/home office
(SOHO) network, a Bluetooth network, an IEEE 802.11 network, an
IEEE 802.15 network or a ZigBee network.
10. The method of claim 1 wherein the second access network is one
of a wireless local area network (WLAN), a wireless private area
network (WPAN), a universal mobile telecommunications system (UMTS)
of a terrestrial radio access network (UTRAN), a code division
multiple access (CDMA) 2000 network, a small office/home office
(SOHO) network, a Bluetooth network, an IEEE 802.11 network, an
IEEE 802.15 network or a ZigBee network.
11. A method implemented in a wireless transmit/receive unit
(WTRU), the method comprising: the WTRU communicating with a
mobility information server using Internet Protocol (IP) via a
first access network of a first access technology type; the WTRU
receiving mobility-related information from the mobility
information server; the WTRU transitioning from the first access
network of the first access technology type to a second access
network of a second access technology type based on the
mobility-related information, wherein the second access technology
type is different from the first access technology type; and the
WTRU communicating with the mobility information server using IP
via the second access network of the second access technology
type.
12. The method of claim 11 wherein the mobility information server
is an Application Server Autonomous Access (ASAA) server.
13. The method of claim 11 further comprising transmitting a
permanent identity of the WTRU to the mobility information
server.
14. The method of claim 13 wherein the mobility-related information
is based on a mobility policy and the permanent identity of the
WTRU.
15. The method of claim 13 wherein the mobility-related information
further includes policy information in accordance with the
permanent identity of the WTRU.
16. The method of claim 11 further comprising transmitting location
information to the mobility information server via a registration
procedure.
17. The method of claim 11 wherein the mobility-related information
includes location information, access network profile information,
or network capability information.
18. The method of claim 11 further comprising receiving the
mobility-related information via a push service.
19. The method of claim 11 wherein the first access network is one
of a wireless local area network (WLAN), a wireless private area
network (WPAN), a universal mobile telecommunications system (UMTS)
of a terrestrial radio access network (UTRAN), a code division
multiple access (CDMA) 2000 network, a small office/home office
(SOHO) network, a Bluetooth network, an IEEE 802.11 network, an
IEEE 802.15 network or a ZigBee network.
20. The method of claim 11 wherein the second access network is one
of a wireless local area network (WLAN), a wireless private area
network (WPAN), a universal mobile telecommunications system (UMTS)
of a terrestrial radio access network (UTRAN), a code division
multiple access (CDMA) 2000 network, a small office/home office
(SOHO) network, a Bluetooth network, an IEEE 802.11 network, an
IEEE 802.15 network or a ZigBee network.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 10/987,773 which claims the benefit of U.S.
Provisional Application No. 60/519,440 filed on Nov. 12, 2003, and
U.S. Provisional Application No. 60/623,091 filed on Oct. 28, 2004,
which are incorporated by reference as if fully set forth.
FIELD OF INVENTION
[0002] The present invention is related to wireless communication
systems. More particularly, the present invention is related to a
system which permits access to an infrastructure by devices
employing different types of access technology.
BACKGROUND
[0003] Current technology allows different types of wireless and
wireline access networks to offer service to subscribers. Support
of mobility inter-working between different access technologies,
for example, second and third generation (2G/3G) wireless networks,
code division multiple access 2000 (CDMA 2000) networks, wireless
local area network (WLAN)/Bluetooth.RTM. networks, exists to a very
limited degree at the radio access network (RAN) level.
Standardization work, in the area of WLAN and Global Standard for
Mobile Units (GSM)/Universal Mobile Telecommunication System (UMTS)
inter-working is in progress. However, the mechanisms being defined
address mobility between these networks within the radio access
domain. As such, these efforts factor in only wireless, (i.e.,
RAN), criteria into their schemes. A mechanism is needed whereby
"application level" integration is possible across heterogeneous
access networks, allowing seamless mobility and inter-working to
occur between these systems.
SUMMARY
[0004] The present invention solves the problems associated with
prior art interoperability problems. The present invention is an
Application Server Autonomous Access (ASAA) system that brings
together different types of wireless and wireline access networks.
It allows a potentially non-Public LAN Mobile Network, 3rd-party
service provider to provide services to subscribers, based on user
location, behavioral preferences, tariffing criteria, etc. The ASAA
network consolidates location, service and routing information for
users as they roam between different types of access networks. The
ASAA network provides flexible routing of calls and push services
to users via the appropriate technology network, based upon
criteria such as user location, behavioral preferences and
tariffing preferences. The architecture of the ASAA network allows
different types of services to be offered to the user based upon
the same criteria. In essence, this architecture allows a 3rd-party
service provider to draw significant revenues from, (and away
from), wide-area PLMN networks, (such as GSM/UMTS and CDMA 2000
networks).
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] FIG. 1 is a diagram showing an ASAA network implemented in
accordance with the present invention.
[0006] FIG. 2 is a diagram showing the relationship between a WTRU,
an ASAA server and access networks.
[0007] FIG. 3 is a diagram showing an ASAA network implementation
of a remote video media function in accordance with one aspect of
the present invention.
[0008] FIG. 4 is a schematic diagram showing a remote control
connection of a camera device implemented in accordance with one
embodiment of the present invention.
[0009] FIG. 5 is a schematic diagram showing a remote control
operation of a camera device implemented in accordance with one
embodiment of the present invention.
[0010] FIG. 6 is a diagram showing a user interface of a personal
lock and key device which provides secure communication over an
ASAA network in accordance with a particular aspect of the present
invention.
[0011] FIG. 7 is a block schematic diagram showing the operational
functions of the personal lock and key device of FIG. 6.
[0012] FIG. 8 is a diagram showing the interoperability of the
personal lock and key device of FIG. 6 with a terminal or WTRU
application.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] As used herein, the terminology "wireless transmit/receive
unit" (WTRU) includes but is not limited to a user equipment,
mobile station, fixed or mobile subscriber unit, pager, or any
other type of device capable of operating in a wireless
environment. The terminology "base station" includes but is not
limited to a Node B, site controller, access point or any other
type of interfacing device in a wireless environment. An "access
point" (AP) is a station or device which provides a wireless access
for devices to establish a wireless connection with a LAN, and
establishes a part of a wireless LAN (WLAN). If the AP is a fixed
device on a WLAN, the AP is a station which transmits and receives
data. The AP permits connection of a WTRU to a network, provided
that the WLAN itself has a connection to the network.
[0014] According to the present invention, wireless
telecommunication services are provided to at least one WTRU by
identifying at least a plurality of wireless access networks
capable of providing wireless links to the WTRU. A server is
capable of communicating with a plurality of the wireless access
networks and determines a status of the WTRU in the sense of an
ability to establish a radio link with one or more of the wireless
access networks. The server establishes a server communication link
a wireless access networks with which the WTRU has an ability to
establish a radio link and uses the communication link to establish
communication between the WTRU. The server communication link is
then used to establish communication between the WTRU and a further
destination through one of the access networks.
[0015] The ASAA server consolidates location, service and routing
information for subscribed users. The ASAA server also routes calls
and push-services to a user's appropriate serving network, based on
policy profiles. These profiles include, for example, location,
technology network capabilities, behavioral factors and tariffing
criteria. The ASAA network uses IP-based technologies (e.g. SIP) to
support inter-technology convergence.
[0016] FIG. 1 is a schematic diagram of an ASAA network 11, showing
an exemplary relationship between an ASAA server 12, network
service entities 21-26, and a WTRU 13 according to the present
invention. The ASAA network 11 implemented in accordance with the
present invention brings together different technology networks,
such as: 3G wide-area PLMN (e.g., UMTS and CDMA 2000); private area
networks (WPANs), for example office and campus networks (e.g.,
WLAN, Bluetooth, IEEE 802.11, IEEE 802.15 and ZigBee); and private
SOHO networks (e.g., WLAN, Bluetooth, IEEE 802.15 and ZigBee). As
shown in FIG. 1, in addition to the ASAA network 11 and the ASAA
server 12, is a public switched telephone network or public data
network (PSTN/PDN) 14 and a public land mobile network (PLMN)
15.
[0017] While certain protocols, such as IEEE 802.15, are described,
a number of suitable protocols can be used for communications
within the scope of the present invention. These are described by
way of example and it is contemplated that other communication
techniques and protocols, such as ZigBee, UWB and IrDA, will be
used to implement the inventive concepts.
[0018] The PLMN 15 includes a plurality of LANs 21-25, depicted as
an entertainment store 21 at an airport location, an airport lounge
22, an office network 23, a coffee shop 24 offering WLAN services,
and a home network 25. The PLMN 15 also includes a network 26
offering large area mobile services, which in the example includes
a 3G device 27 and a SIP device 28. The large area mobile services
network 26 provides communication via WLAN, BT and UMTS. The LANs
21-25 and large area mobile services network 26 form access
networks. Typical communications through the LANs 21-25 are
according to the IP protocol, SIP protocol or other packet-switched
protocols. Typically, such communications use a common channel and
are assigned bandwidths according to demand.
[0019] A plurality of ASAA application servers 41, 42 and 43 are
provided at various locations including at the office network 23,
the home network 25 and the large area mobile services network 26.
The ASAA application servers 41, 42 and 43 provide application
services through their respective access networks 23, 25 and 26,
but are also accessible through other access networks.
[0020] The WTRU 13 is depicted and is able to communicate with
various ones of the access networks 21-26. The ASAA server 12 is
able to establish a communication link with the WTRU 13 by
connecting directly or indirectly to individual ones of the
networks 21-26 to which the WTRU 13 has established a communication
link. The services come from the ASAA server in this architecture.
The access networks provide access to the user and hence, calls and
other interactions between the user and the ASAA server are routed
through the access network to which the user is connected. This
enables the ASAA server 12 to function as a service platform in
order to deliver services to the user through the various ones of
the access networks 21-26.
[0021] The WTRU 13 is able to communicate through various services
as provided via the WLAN 23, but once connected, the ASAA server 12
can provide administrative functions to either provide services
directly through the ASAA server 12, or request that services be
routed between the various access networks 21-26 to an access
network connected to the WTRU 13. The services are provided by the
ASAA server 12 in this architecture. The access networks provide
access to the WTRU 13, and hence calls and other interactions
between the WTRU 13 and the ASAA server 12 are routed through the
access network 21-26 to which the WTRU 13 is connected.
[0022] The ASAA server 12 also includes server function modules 61,
62. The server function modules 61, 62 provide administrative
functions for operating the ASAA server 12, and maintaining a
database of locations of the WTRU 13 and availability of
connections to the access networks 21-26. The server function
modules 61, 62 also provide application functions which can be
executed by the WTRU through connections to the access networks
21-26.
[0023] The ASAA server 12 provides an anchored interface to the
PSTN/PDN 14 for receipt/transmission of call attempts, and routes
incoming calls to the WTRU's serving access network based on the
WTRU's location. In routing incoming calls, the ASAA server 12
pages all underlying possible serving access networks configured
for the WTRU 13. The WTRU 13 responds with a paging response,
routed through currently connected serving network. The ASAA server
12 then delivers incoming calls, via a serving access network to
which the WTRU 13 is currently connected.
[0024] The WTRU 13 can also "force-route" incoming call through a
specified serving access network by configuring the ASAA server 12
appropriately, with the identity of serving access network to route
the call through to its destination. By specifying the access
network, the WTRU 13 can control which services are used.
[0025] This architecture broadens the traditional cellular paging
and call routing mechanisms to work across a range of access
networks. In one embodiment, an IP based application-level paging
mechanism, which operates across a variety of access networks to
help locate the WTRU 13 issued.
[0026] One embodiment includes a provision of a consolidated
interface, via the ASAA server 12, to allow PSTN/PDN 14 receipt of
calls. The ASAA server 12 allows PSTN/PDN 14 receipt of calls to be
effected through a single anchor point. The effect is that, from
the user's standpoint, radio link services are provided by the
particular radio links, which are the individual ones of the access
networks 21-26. The service management, which is the user's
interface, can be either one of the local network 21-26 or the ASAA
server 12. Thus as indicated by dashed line 69, the system shifts
the network administration for the user's services and the service
management for the user "upward" from the individual access
networks 21-26 to the ASAA server 12. The ASAA server 12 then
becomes a virtual server from the user's perspective. Network
services are provided by the individual access networks 21-26 for
the radio link, and by the ASAA server 12 for services provided to
the user other than the radio link. If the operator of the ASAA
server 12 is able to obtain wireless services as provided by the
individual access networks 21-26, then the user is able to make
service subscription arrangements with the operator of the ASAA
server 12.
[0027] This architecture supports mobility of the WTRU 13 across
multiple access networks, and helps locate the WTRU 13 seamlessly.
The use of the ASAA server 12 allows for user-configured routing of
calls through a given access network. This also provides a uniform
set of supplementary services and features across multiple access
networks, resulting in a continuity of user's experience despite
network changes. The architecture also may provide a configuration
for a uniform mechanism for provision of push services to the WTRU
13 across multiple underlying access networks.
[0028] The role of the ASAA server 12 providing an administrative
function concerning routing of services to various access networks
12-26 makes the ASAA server 12 able to maintain a common location
for user profiles. The user can determine what services to use, and
under which physical circumstances. Examples of parameters include
call handling, selection of services by type, selection of services
by cost and cost structure, selection of services by network
ownership, notification of availability of connections to services,
user determined minimum quality of service (QOS), required
bandwidth of services for a particular function. Call handling
profile selection functions can include voicemail, selective
admission of calls and "challenge" responses. In a similar manner,
the ASAA server 12 can also provide the voicemail and other data
management services.
[0029] FIG. 2 is a diagram showing the relationship between a WTRU
81, an ASAA server 83 and access networks 91-95. The WTRU 81
includes a first circuit 87 for establishing an RF link and a
second circuit 88 for processing data, although some of these
functions are integrated circuit functions. The WTRU 81 establishes
a communications link with the ASAA server 83, but in general the
service connection is between the WTRU 81 and one of the service
networks 91-95. Services may be communicated either through the
ASAA server 83 through the service network in radio communication
with the WTRU 81. Alternatively, services may be communicated from
one service network to a service network which establishes a radio
link with the WTRU 81 without passing through the ASAA server 83.
In the case of ASAA server supervised communications,
communications which do not pass through the ASAA server 83 or
originate with the ASAA server 83 may still be supervised by the
ASAA server 83. Since the processing circuitry 88 handles the data
regardless of its source, the actual connection to a particular
service network 91-95 can be transparent to the user.
[0030] In operation, upon energization of the media device, the
ASAA application attempts to access the ASAA server 83 via the 3G
PLMN infrastructure. This registration action will result in the
regular transmission of location information between the PLMN and
the ASAA application server.
[0031] The ASAA server 83 will maintain a catalog of subnetworks
available to the media device and, during the life of the session,
may push the media device onto these subnetworks automatically, or
upon some user command following an ASAA system prompt. This push
action is policy-based. By way of example, server policies may
include user location, behavioral profiling, and optimal
tariffing.
[0032] During the lifetime of the session, the ASAA network
provides the connectivity between the media device and the
PSTN/PDN. Depending on ASAA and PLMN subscription, (such as the
quality of service profile), different levels and types of services
may be offered to the media device. This may also dependent upon
location.
[0033] By way of example, a general PLMN voice service may not be
necessary to a user having a behavioral profile that places the
user at home or in the office for a large percentage of normal
time. For such a user, a simple ASAA (SIP-based) paging scheme may
be applied during times of subnetwork unavailability.
[0034] The ASAA system in accordance with the present invention
results in several advantages over current systems. The ASAA system
consolidates location, service and routing information for
subscribed users at the ASAA Server 83. This permits seamless
communication provision of seamless mobility between different
technology networks, using a common IP-based scheme. The system
routes calls and push services to the appropriate technology
network based on policy profiles. The system also supports a
flexible tariffing scheme based on a user's location and choice of
technology network. Finally, the system enables 3rd-party
application providers to extract services revenue from wireless
networks.
[0035] A further advantage of the ASAA system is that the ASAA
server 83 can assign a virtual identity to the WTRU 81, which for
example can be a user identity. In this way, the user identity can
be made portable across different WTRUs. Thus, if each WTRU has a
unique identity, the ASAA server 83 can communicate with the
various WTRUs according to their identities such as ESN numbers.
The communication of the ASAA server 83 can be in response to
different identity as selected by the user. This permits a user to
"clone" a WTRU such as a cellular telephone by using the ASAA
server 83. The ASAA server 83 can then communicate with a different
WTRU in order to provide information corresponding to the identity.
Therefore, a user can use a different physical device, with its own
identity in place of a particular WTRU. Conversely, multiple
different user IDs may be mapped onto a single device by the ASAA
server 83. In either case, the ASAA server 83 provides an identity
proxy service for the WTRU.
[0036] By way of example, the user may wish to have a personal
cellphone and a work cellphone on a trip, but only carry a single
physical device. Instead of using call forwarding services, the
user may communicate under the supervision of the ASAA network
which is able to communicate with the physical device which the
user is carrying. Since this is under the supervision of the ASAA
network, the ASAA server 83 can convert device information such as
telephone number or other identifying data in accordance with
information registered on the database of the ASAA server 83.
[0037] Remote Camera Device
[0038] FIG. 3 is a diagram showing an ASAA network implementation
of a remote video media function in accordance with one aspect of
the present invention. As can be seen, camera devices 121 and 122
are connected through network connections which provide virtual
connections to an ASAA server 128. The actual connections of the
camera devices 121 and 122 may be either through a LAN, such as
WLAN 131, or through a WTRU 135 capable of effecting a cellular
connection. WTRU 135 may be a separate device connected through a
local connection such as an IEEE 802.15 connection or may be
self-contained in or hardwired to the camera device 122. In each
case, communication is effected which can be controlled by the ASAA
server 128.
[0039] Also shown in FIG. 3 is a PC 142 which is able to
communicate with the ASAA server 128 through either through WLAN
131 or through another connection such as a direct internet
connection. A local WTRU 146 communicates with the ASAA server 128
either directly or through the WLAN 131. Likewise a WTRU 149 may be
located at a separate location and communicate with the ASAA server
128. The ASAA server 128 may provide a virtual identity to the WTRU
149 or the camera device 122 as described supra.
[0040] FIG. 4 is a schematic diagram showing a remote control
connection of a camera device 171 implemented in accordance with
one embodiment of the present invention. This remote control is
performed either through the ASAA network of FIGS. 1-3 or through
network services. FIG. 4 shows a one-way transmission of images
through a two-way link. The camera device 171 includes a camera
with associated image processor 172, an image storage device 173
and a transceiver 174. The camera device 171 communicates through
an access point (AP) 177, which, in turn, communicates with an ASAA
network 181 under the control of an ASAA server 183.
[0041] The ASAA network 181 connects with a user's WTRU 188, which
provides an image through display 189. The user's WTRU 188 is able
to control the camera device 171 through the communications link
established by the camera device 171, AP 177, ASAA network 181 and
WTRU 188. Control can be open or restricted by controlled access.
In the case of restricted control of the camera device 171, this
may be either in accordance with the particular terminal providing
control instructions or requesting outputs, in accordance with
establishment of a secure connection, or by means of authentication
by password or other user information.
[0042] In order to communicate with the camera device 171, the ASAA
network 181 provides a registration of the camera device 171.
Communications with the camera device are effected through the ASAA
network 181 under the supervision of the ASAA server 183. It is
also possible to effect other network connections (not shown).
Therefore, control and access to the output of the camera device
171 is achieved in a controlled manner. This means that in order to
access the camera device 171 through the ASAA server 183, one must
either be registered through the ASAA server 183 or have been
granted access. One advantage of using the ASAA server 183 is that
any user with access to the ASAA network can be provided with
access to the camera device 171 in accordance with the
registration.
[0043] In use, if the camera device 171 is to have restricted use
for privacy or utility reasons, then the control of the camera
device 171 is established by an authorized user. The authorized
user can be given control of the camera device 171 by the ASAA
server 183 and can proceed to control the camera device either
through the ASAA server or through a connection authorized by the
ASAA server 183. Thus, the camera can be reserved for use by
particular individuals such as family members, or lesser
restrictions may be permitted. Therefore, while the network link
used by the camera device may inherently be open to outside control
of viewing, the ASAA server permits owner control while permitting
wide access by the owner and those authorized by the owner.
[0044] FIG. 5 is a schematic diagram showing a remote control
operation of the camera device 171 implemented in accordance with
one embodiment of the present invention. The camera device 171 is
controlled remotely by a remote terminal such as terminal 192 or by
WTRU 188. Control operations are executed under the supervision of
the ASAA server 128 which provides control between the WTRU 188 or
terminal 192 and the camera device 171. In addition, a media path
195 may be established through the ASAA server 128, under the
supervision of the ASAA server 128 or independently. While the
execution of commands is depicted as directly between the camera
device 171, WTRU 188, terminal 192 and the ASAA server 128, it is
anticipated that the ASAA server will use intermediary network
connections for providing these signals.
[0045] Registration with the ASAA server 128 is established by the
WTRU 188 or the terminal 192 registering 201, 202 separately as
devices accessible by the ASAA server 128. A control request 203 is
made by the terminal and is granted 204. The terminal then opens
the application 205, 206 which in this case is the camera control.
This is followed by commands such as turning commands 207-210. In
addition, the terminal can access the camera output as indicated by
media path 195 may be restricted by the ASAA server 128.
[0046] Personal Communication Lock and Key
[0047] Communication across a network incorporates a variety of
wired and wireless devices. In instances where security is required
a personal lock and key device provides controlled secure access to
communication, service and data. According to the present
invention, a separate personal lock and key device is used in order
to implement the security by effecting a wired dongle or local
wireless connection with a local device operated by the user. The
local device can be a WTRU, a terminal under the control of the
user or a public terminal being used by the user. The personal lock
and key device is able to provide multiple functions, which may
include: 1) communication with a security server which provides
security data to servers offering services to the user; 2) dongle
security by encryption and decryption of signals processed by a
local terminal or WTRU; 3) storage of password information which
can be decrypted through the security server; 4) communication with
multiple security servers; and 5) providing password access and
security data to servers according to the server's protocol
independently of the security server.
[0048] FIG. 6 depicts the user end of a network environment 300
with a personal lock and key device 301 used to provide secure
access through a computer terminal 311, WTRUs 312, 313, and a
portable computer 314 connected through a WTRU, (not separately
depicted). The personal lock and key device 301 is convenient in
that a single device is able to be used in connection with the
various user devices without a requirement to provide separate
equipment for each terminal device 311-314. In instances where the
personal lock and key device 301 is not necessary for operation of
the terminal device 311-314, the personal lock and key device 301
can be conveniently stowed because it has a limited profile for
physical connection, and has either no user interface or a limited
user interface.
[0049] The personal lock and key device 301 can use data stored
internally. In addition, the personal lock and key device 301 is
able to read further security data, such as that provided by an
external card device 321. This enables separate secure devices to
operate in conjunction with the personal lock and key device 301
without a direct association between the protocol used by the
external card device 321 and the personal lock and key device 301.
The personal lock and key device 301 would be expected to
communicate with the separate, external card device 321 and with
external services, but would not otherwise be required to share a
protocol with the external card device 321.
[0050] FIG. 7 is a block schematic diagram showing the operational
functions of the personal lock and key device 301 of FIG. 6. A
wireless communication circuit 361 such as an IEEE 802.15 or
BlueTooth.TM., and an infrared port 364 provides communication to a
connection bus 371, which also has an external port connection 376.
The connection bus 371 communicates with a logic circuit 381, which
receives signals transferred to the connection bus 371 from the
wireless communication circuit 361, infrared port 364 or external
port connection 376. The logic circuit 381 provides signals to the
connection bus 371 for transmission through the wireless
communication circuit 361, infrared port 364 or external port
connection 376. The logic circuit 381 uses encryption/decryption
data stored in a memory store 385 for decryption or encryption of
data transferred through the connection bus 371.
[0051] A card reader circuit 389 receives data from an external
card (321, FIG. 6) for communication through the connection bus 371
which communicates with the wireless communication circuit 361,
infrared port 364 or external port connection 376 as described
above. The external card reader 389 may obtain complete data
conversions or may provide data for use by the logic circuit 381
for conversion. In the case of the complete data conversion
obtained by the external card reader 389, the logic circuit 381
transfers the data as received to or from the connection bus 371 to
or from the external card reader 389. In the case of data provided
for use by the logic circuit 381 by the external card reader 389,
the data is used by the logic circuit 381 to convert data
transferred through the connection bus 371. It is also understood
that the logic circuit 381 may use a combination of data converted
externally and transferred by the external card reader 389 along
with data converted by the logic circuit 381.
[0052] FIG. 8 is a diagram showing the interoperability of the
personal lock and key device 301 and secure services. A local
application device 401, which is a local terminal, includes an
application 405 and a dongle port 404. The dongle port 404 may be a
physical dongle such as a USB port, a wireless communication port
or other communication port. The purpose is to permit the personal
lock and key device 301 to receive data from the local application
device 401 and transmit data back to the local application device
401. The use of an external dongle decryption device is known to
those skilled in the art.
[0053] The local application device 401 communicates through
network connections 420 and 421 to a security server 428, which
provides encryption data that cooperates with the personal lock and
key device 301. The security server 428 communicates with the
personal lock and key device 301 to provide and receive encrypted
data across the network connections 420 and 421.
[0054] The security server 428 may retain data and provide program
services. Additionally, services may be provided externally of the
security server 428, as represented by application service server
431. The security server 428 may communicate with the application
service server 431 with secure protocols which may be the same or
different protocols used for the security server 428 to communicate
through the local application device 401 and the personal lock and
key device 301. As depicted, secure communication between the
application service server 431 and the security server 428 may be
through network connection 421, but the communication link is
effectively secured between the application service server 431 and
the security server 428 so as to be inaccessible from the outside
as represented by dashed line 439. In that respect, the security
server 428 may store user keys and passwords and respond to
communication requests by communicating with personal lock and key
device 301. When personal lock and key device 301 is identified,
the security server 428 communicates the necessary access
information.
[0055] By way of example, the user may with to access a private
directory (such as a private list of names, customer list or other
confidential data). The directory is resident on a server which
offers access to the directory only in a secure manner, so that
there is no public access to the directory. The user may connect at
the local application device 401, which may be a public terminal,
and request access to the security server 428. The security server
428 provides data which is accessible only through the personal
lock and key device 301, and further uses the personal lock and key
device 301 to authenticate the user. Thus data is provided to the
user only in the form requested by the user, and with essential
elements in a format which is only readable through the personal
lock and key device 301. Therefore only displayed data selected by
the user would be accessible at the public terminal 401 and would
only be retrieved when the personal lock and key device 301 is
connected to the dongle port 404. Thus, the data transferred cannot
be "sniffed" in unencrypted form from the network connections 420
and 421. Only the data provided back to the public terminal 401 for
local display or manipulation can be detected through access to the
public terminal 401.
[0056] The data can be stored at the security server 428 in the
manner of passwords, or can be stored elsewhere, as at application
service server 431. In the example, if the data is stored at the
application service server 431, then data is transferred between
the application service server 431 and the security server 428, and
then transferred to the public terminal 401, where it is decrypted
by the personal lock and key device 301. The processing of the data
can occur at any convenient location, including the public
terminal, application service server 431 or the security server
428.
[0057] In another example, secured data is stored at an application
service server 431. The user wishes to download a data output to
the local application device 401, which may be a laptop computer.
The data output is to be manipulated or displayed at the laptop
computer 401. The user requests the service by providing
authentication between the personal lock and key device 301 and the
security server 428. The security server responds by providing
authentication between itself. The application service server 431
provides the service as requested and returns a data output. The
data output is then provided either directly to the user or to the
user through the security server 428. The data output may be
provided in encrypted form, to be decrypted by the personal lock
and key device 301, or in unencrypted form, as appropriate for the
particular type of data. For example if the data output is a name
and telephone number derived from a confidential list, it is
possible that the user doesn't consider a single name and number to
be confidential and would rather have it freely accessible
locally.
[0058] The security server 428 may be a separate device accessible
through communication links or may be provided as a function of the
ASAA server 12. In the case of the ASAA server 12, the secure
functions can be implemented across divers networks while
maintaining secure connections according to the protocols supported
by the personal lock and key device 301.
[0059] As depicted in FIG. 6, the personal lock and key device 301
may use self-contained data, or may use data provided the external
card device 321. This permits the personal lock and key device 301
to be used as an interface between the external card device 321 and
the local application device 401, as depicted in FIG. 8. It is
further contemplated that the lock and key device 301 will be
conveniently mountable to at least one further device such as a
WTRU. This enables the lock and key device 301 to communicate
through the WTRU in order to execute its function.
[0060] The ability to connect through a further device is also
useful in circumstances in which a particular device cannot connect
to the personal lock and key device 301. For example if a device
may be unable to connect to the personal lock and key device 301
but is connected to a WTRU for wireless connectivity. In such a
case the WTRU is connected to both the lock and key device 301
enabling security, and to the device, thus providing secured
wireless connection.
[0061] It is possible to include biometric identification functions
in the lock and key device 301. This would require a biometric
identification and authentication procedure, so as to restrict use
of the lock and key device 301 to the owner. Examples of biometric
functions would include a physical feature reader, voice matching
circuitry or other function which uniquely identifies the user. The
biometric data may also be provided for purposes of use of a
diverse device such as a camera to match a biometric attribute
based on biometric data stored in the personal lock and key device
301.
[0062] The personal lock and key device 301 may be assigned an
identity by the security server 428. Alternatively, the security
server 428 may assign a virtual identity to a device, such as the
local application device 401, through which the personal lock and
key device 301 communicates.
* * * * *