United States Patent Application |
20080125102
|
Kind Code
|
A1
|
Abel; Miller Thomas
;   et al.
|
May 29, 2008
|
MOBILE DEVICE MANNERS PROPAGATION AND COMPLIANCE
Abstract
The present invention includes methods and technologies for defining and
administering device manners policy ("DMP"), propagating DMP, reception
and recognition of, and compliance with DMP. Such policy may be used to
communicate to various mobile and other devices the "manners" with which
compliance is expected or required. Similar to some of the social manners
honored among people, such as with "no smoking" or "employees only"
zones, "no swimming" or "no flash photography" areas, and scenarios for
"please wash your hands" or "no talking out loud", devices may recognize
and comply with analogous "device manners" policy.
Inventors: |
Abel; Miller Thomas; (Mercer Island, WA)
; Guday; Shai; (Redmond, WA)
; Sinclair; Michael; (Kirkland, WA)
|
Correspondence Name and Address:
|
MICROSOFT CORPORATION
ONE MICROSOFT WAY
REDMOND
WA
98052-6399
US
|
Assignee Name and Adress: |
Microsoft Corporation
Redmond
WA
|
Serial No.:
|
533140 |
Series Code:
|
11
|
Filed:
|
September 19, 2006 |
U.S. Current Class: |
455/418 |
U.S. Class at Publication: |
455/418 |
Intern'l Class: |
H04M 3/00 20060101 H04M003/00 |
Claims
1. A method for recognizing a device manners policy ("DMP") and
configuring a device for compliance with the DMP, the method
comprising:recognizing the DMP; anddetermining an applicability of the
DMP to the device and, if applicable:identifying any relevant device
manners specified in the DMP, andconfiguring the device for compliance
with the any relevant device manners.
2. The method of claim 1 further comprising, if the DMP is applicable to
the device, periodically testing to determine if the DMP is still
applicable.
3. The method of claim 2 further comprising, when the DMP is no longer
applicable to the device, restoring a previous configuration to the
device.
4. The method of claim 1 wherein the recognizing includes the device
receiving the DMP via a network.
5. The method of claim 1 wherein the recognizing includes the device
detecting the DMP via an optical means.
6. The method of claim 1 wherein the recognizing includes the device
detecting the DMP via an acoustic means.
7. The method of claim 1 embodied as device-executable instructions on a
device-readable medium.
8. A method for controlling a device based on a device manners policy
("DMP"), the method comprising:accessing the DMP from a DMP data store
associated with a DMP server;receiving the DMP from the DMP server at the
device; andconfiguring the device based on one or more device manners
specified by the DMP.
9. The method of claim 8 further comprising:forwarding an indication of
DMP compliance from the device to a service provider; andaccessing a
service provided by the service provider to the device based on the
indication.
10. The method of claim 8 embodied as device-executable instructions on a
device-readable medium.
11. A system for device manners propagation and compliance, the system
comprising:a device manners policy ("DMP") including an expression of a
device manner;a DMP server operable to provide the DMP to a device; anda
DMP data store associated with the DMP server and operable to store the
DMP.
12. The system of claim 11 wherein the device manner is expressed in an
extensible markup language format.
13. The system of claim 11 wherein the device manner is expressed as an
image.
14. The system of claim 11 wherein the device manner is expressed in an
audio format.
15. The system of claim 11 wherein the DMP server provides the DMP to the
device via a network.
16. The system of claim 11 wherein the device is configured to comply with
the DMP when the DMP is applicable to the device.
17. The system of claim 16 wherein the device is restored to a previous
configuration when the DMP is no longer applicable to the device.
18. The system of claim 11 wherein an indication of DMP compliance is
provided to a service provider.
19. The system of claim 18 wherein access by the device to a service
provided by the service provider is conditioned upon the indication of
DMP compliance.
20. The system of claim 11 wherein the device is a mobile device and the
DMP is stored on the mobile device.
Description
BACKGROUND
[0001]As various types of mobile devices proliferate, a number of social
issues develop. For example, a movie-goer who forgets to silence his cell
phone may interrupt an entire audience with a ring. Or a locker room
patron may feel justifiably ill-at-ease upon seeing other locker room
patrons making use of camera phones or digital cameras. Or a corporation
may wish to prevent near-by unauthorized devices from discovering its
wireless networks. These and other examples illustrate some of the
security and privacy concerns resulting from mobile devices, such
concerns ranging from unintentional rudeness to critical security and
privacy matters. Such mobile device intrusions may be summarized as
socially undesirable audible or visual disturbance or unauthorized
information or data capture.
SUMMARY
[0002]The following presents a simplified summary of the disclosure in
order to provide a basic understanding to the reader. This summary is not
an extensive overview of the disclosure and it does not identify
key/critical elements of the invention or delineate the scope of the
invention. Its sole purpose is to present some concepts disclosed herein
in a simplified form as a prelude to the more detailed description that
is presented later.
[0003]The present examples provide methods and technologies for defining
and administering device manners policy ("DMP"), propagating DMP,
reception and recognition of, and compliance with DMP. Such policy may be
used to communicate to various mobile and other devices the "manners"
with which compliance is expected or required. Similar to some of the
social manners honored among people, such as with "no smoking" or
"employees only" zones, "no swimming" or "no flash photography" areas,
and scenarios for "please wash your hands" or "no talking out loud",
devices may recognize and comply with analogous "device manners" policy.
[0004]Many of the attendant features will be more readily appreciated as
the same becomes better understood by reference to the following detailed
description considered in connection with the accompanying drawings.
DESCRIPTION OF THE DRAWINGS
[0005]The present description will be better understood from the following
detailed description read in light of the accompanying drawings, wherein:
[0006]FIG. 1 is a block diagram showing example mobile devices coupled to
together via a network and to a device manners policy ("DMP") server and
database.
[0007]FIG. 2 is a block diagram showing example mobile devices coupled to
together via an ad-hoc network.
[0008]FIG. 3 is a block diagram showing an example device manners policy
("DMP") applied to an example mobile device.
[0009]FIG. 4 is a block diagram showing an example process for recognizing
a DMP and configuring a device to comply with the DMP.
[0010]FIG. 5 is a block diagram showing an example computing environment
in which the technologies and processes described above may be
implemented.
[0011]Like reference numerals are used to designate like parts in the
accompanying drawings.
DETAILED DESCRIPTION
[0012]The detailed description provided herein below in connection with
the appended drawings is intended as a description of the present
examples and is not intended to represent the only forms in which the
present example may be constructed or utilized. The description sets
forth the functions of the examples and/or the sequence of steps for
constructing and operating the examples. However, the same or equivalent
functions and sequences may be accomplished by different examples.
[0013]Although the present examples are described and illustrated herein
as being implemented in a computing and networking environment, the
environment described is provided as an example and not a limitation. As
those skilled in the art will appreciate, the present examples are
suitable for application in a variety of different types of computing and
networking environments.
[0014]FIG. 1 is a block diagram showing example mobile devices coupled to
together via a network 110 and to a device manners policy ("DMP") server
120 and database 122. Example devices may include personal data assistant
("PDA") 130, tablet personal computer ("PC") 140, digital camera 150,
laptop PC 160, digital video recorder ("DVR") 170, and cell phone 180.
Such devices should be operable to at least receive, recognize and/or
support device manner policies. Some such devices may include computing
environments such as that described in connection with FIG. 5. Many other
devices may also be coupled via network 110 or other means, including a
watch with an alarm, shoes with lights (such as some children's shoes),
game devices, audio recorders, or any other device for which device
manners recognition and compliance may be of value. Such devices may
include mobile devices or other devices such as desktop PCs, servers, set
top boxes, appliances, or any other type of non-mobile device that may
benefit from device manners recognition and compliance, Further examples
of such devices include vehicles or any other device, system, construct,
composition, or the like operable to at least receive, recognize and/or
support device manner policies.
[0015]Devices may be coupled to network 110 via any operable link, such as
example link 190. Such links may include a network interface card
("NIC"), a serial or parallel port, a data bus, an analog interface, or
the like, may be wired or wireless, may make use of infrared ("IR"),
acoustics, optics, radios frequency ("RF"), or the like. Network 110 may
be an ad-hoc network with mobile devices coupling transiently. Server
devices, such as server 120, and other less mobile devices, may be
coupled to network 110 more persistently than mobile devices. In one
example, network 110 may be a wireless fidelity ("Wi-Fi") network at a
coffee shop, city library, courtroom, or airport lounge. Mobile and other
devices may typically link to such a Wi-Fi network via wireless adapters.
Such devices may also be operable to link to other types of networks. In
another example, cell phones may link to a cellular network via
appropriate RF adapters and protocols. Such cell phones may also be
operable to link to other types of networks, such as Wi-Fi networks or
the like.
[0016]In one example, DMP server 120 and database 122 may be a DMP
appliance-a special-purpose device or system or the like primarily
intended to provide DMP server and/or database functionality. Such a DMP
appliance may be coupled to network 110 via any operable link, such as
example link 190. Alternatively, a DMP appliance may provide a subset of
DMP server and database functionality and/or may not be coupled to a
network. Such an appliance may simply emit policy via RF means or
acoustic means or the like.
[0017]FIG. 2 is a block diagram showing example mobile devices coupled to
together via an ad-hoc network 210. Such an ad-hoc network may not
include any persistent devices such as DMP servers or related data
stores. Ad-hoc networks for DMP purposes may be formed as various mobile
devices form and join such networks. For example, an ad-hoc network may
be formed comprising devices of people on a particular bus. Example
devices shown in FIG. 2 include those described in connection with FIG.
1.
[0018]FIG. 3 is a block diagram showing an example device manners policy
("DMP") 310 applied to an example mobile device 180 as indicated by arrow
330. Such a DMP may originate from a DMP server, such as server 120 and
related data store 122, and may be transferred or downloaded 320 to a
device such as mobile device 180. Alternatively, DMP 310 may be created
on device 180 or transferred to device 180 via other means.
[0019]Upon receipt of DMP 310 by device 180, DMP 310 may be evaluate to
determine what, if any, compliance may be suggested or required. In one
example, a DMP may be received by cell phone 180 upon entering a
hospital, the DMP requiring no cell phone usage. Cell phone 180 may be
operable to comply with such a DMP by shutting down, entering a sleep
mode, or the like. Upon leaving the hospital cell phone 180 typically
returns to its previous mode of operation as the hospital DMP is no
longer applicable.
[0020]In another example, service provider 350 may require that a device
provide an indication of DMP compliance capability prior to or for
continuation of services, such as over link 352. Device 180 may provide
such an indication 360 to service provider 350 to satisfy the
requirement. Further, service provider 350 may transfer various DMPs to
device 180 in connection with the services provided. For example, a
museum may include service provider 350 to provide wireless data access
to various devices though which information about the exhibits may be
accessed. Provider 350 may further propagate a DMP indicating "no
photography". Devices receiving such DMP upon entry to the museum
typically initiate compliance with the "no photography" DMP by disabling
any photography capabilities, such as provided by cell phone cameras,
digital cameras, and digital video recorders. Access to exhibit data may
be subject to indication of compliance.
[0021]In yet another example, the "no photography" DMP may be provided in
the form of a special tag such as a unique watermark (generally not
visible to humans), radio frequency identification ("RFID") device, or
the like located on or near various exhibits, such a tag being detectable
and/or identifiable by a DMP-enabled device via optical, RF, or other
appropriate means. In this example a network, ad-hoc or otherwise, may
not be required for at least some forms of DMP compliance.
[0022]In yet another example, a "no recording" DMP may be provided in the
form of an audio signal, typically inaudible to human listeners, in
connection with music or some other audio or audio/video reproduction.
Such an audio signal may be detected and identified by a DMP-enabled
device such as a digital recorder, a digital video recorder, or the like.
In this example a network, ad-hoc or otherwise, may not be required for
at least some forms of DMP compliance.
[0023]In yet another example, a "no noise" or "no light" DMP may be
provided via a network, audio means, or any other suitable means or
combination of means, the DMP being detectable and/or identifiable by a
DMP-enabled device such as a device that may emit light or sound
including, but not limited to, watches with audible alarms, shoes with
lights (as sometimes worn by children, for example), cameras,
flashlights, cell phones, PDAs, or any other device that may benefit from
compliance with a "no noise" or "no light" DMP or the like.
[0024]In yet further examples, DMPs may be used in particular zones to
limit the speed and/or acceleration of vehicles, to require the use of
lights, to verify an indication of insurance coverage and/or current
registration, or the like. DMPs may be propagated with acceptable usage
times for mobile devices, such as when on an airplane with being
restrictions common at times of landing and/or take-off. DMPs may be used
to cause devices to be reconfigured for silent operation in locations
such as libraries, court rooms, hospitals, meeting rooms, theatres, or
the like.
[0025]In ad-hoc scenarios, DMPs may be the result of voting or a consensus
among current members of an ad-hoc network or the like. For example, the
majority of current bus riders may agree upon and propagate "silence
please" DMPs that cause cell phones to reconfigure for vibrate versus
audible rings, that cause audio devices to work only with headphones,
that cause gaming devise to switch to a silent mode of operation, and the
like.
[0026]In general, DMPs may be applied to devices when within a particular
zone or area to which the DMPs apply. Upon leaving such zones or areas a
device is typically reconfigured to resume it former mode of operation.
For example, a cell phone device reconfigured to a vibrate mode as a
result of detecting a "silence" DMP upon hospital entry will typically
return to its previous ring mode when leaving the hospital zone. In other
scenarios, a device may revert back to a previous configuration when
leaving a virtual community such as may be established via an ad-hoc
network. Such DMP zones, areas, communities, or the like may be defined
and/or indicated in any manner useful for DMP propagation and compliance
purposes.
[0027]DMP 310 typically includes one or more device manners ("DM") that
specify particular device behaviors or rules to which device compliance
is requested or expected. Typically it is the responsibility of the
device itself to comply with any applicable DMs in a recognized DMP, as
well as determining applicability. Device compliance is generally
achieved via self-reconfiguration. Restoration of a device's previous
configuration typically occurs when a DMP is no longer applicable, such
as when the device is no longer in the DMP's zone, area, community, or
the like. Additionally or alternatively, a DMP may include an expiration
time, a time-out period, or the like, upon which a device in compliance
with such a DMP may revert back to a previous configuration. Further, a
DMP may require that a hosting device report its compliance status back
to the source of the DMP such that non-compliant devices, or the
compliance status of devices, may be noted by a DMP environment.
[0028]DMP 310 may be implemented as a data structure, an electronic
signal, represented via extensible markup language ("XML") or the like,
expressed as an image, or otherwise implemented, expressed, and/or
represented sufficient to be recognizable, detectable and/or identifiable
by a DMP-enabled device. In some examples, DMPs may be created, modified,
propagated to/from, and/or stored in example DMP data store 122, example
DMP server 120, example service provider 350, example device 180, and/or
other devices or the like.
[0029]FIG. 4 is a block diagram showing an example process 400 for
recognizing a DMP and configuring a device to comply with the DMP. Block
410 indicates a device recognizing a DMP. In one example, the DMP is
received by the device over a network or the like. In another example,
the DMP is detected via an optical means, acoustic means, electromagnetic
means, or some other means suitable for DMP recognition purposes. In
general, example process 400 continuously seeks to recognize a DMP,
continuing at block 420 once a DMP is recognized.
[0030]Block 420 indicates evaluating the recognized DMP to determine if it
is applicable to the device. If the DMP is applicable, example process
400 continues at block 430; otherwise it continues at block 410. For
example, if the DMP relates to library zone and the device is within the
library zone, then the DMP is considered applicable. But if the device
recognizes the DMP but is not within the library zone, then the DMP is
not considered applicable.
[0031]Block 430 indicates evaluating the applicable DMP to identify any
device manners of the DMP that are relevant to the device. If one or more
of the device manners are relevant, example process 400 continues at
block 440; otherwise it continues at block 410. For example, if the DMP
specifies a "silence please" device manner and the device is a cell
phone, then the device manner is relevant. But if the device is a child's
shoe including flashing lights but no sound feature, then the device
manner is not considered relevant.
[0032]Block 440 indicates configuring the device for compliance with any
relevant device manners specified in the applicable DMP. In one example,
the cell phone is configured for silent operation, disabled entirely, or
the like so as to comply with the DMP. In some examples, the device may
configure itself for compliance. Once the device is configured for
compliance, example process 400 continues at block 450.
[0033]Block 450 indicates testing to determine if a previously-determined
applicable DMP is still applicable. If such a DMP is still applicable,
example process 400 continues at block 410; otherwise it continues at
block 460. Such tests may be performed periodically, continuously, or the
like once a device has been configured for DMP compliance (as indicated
by loop 452), and may continue even while process 400 seeks to recognize
other DMPs. For example, a cell phone may have recognized and complied
with a DMP including a "silence please" device manner for a library zone.
The cell phone may periodically test to determine if the DMP is still
applicable, that is if the cell phone is still in the library zone.
Continued applicability may additionally or alternatively be tested by
other means, such as using GPS data to determine if the cell phone is
still in the library zone. Such a means may not require that a device
maintain or obtain contact with a DMP server or the like. Information
useful for continued applicability testing may be provided, at least in
part, with the DMP, or may be obtained independent of the DMP and/or of a
DMP environment.
[0034]Block 460 indicates restoring a previous configuration once a DMP is
fund to be no longer applicable. For example, if a cell phone had been
configured for silent operation while a "silence please" DMP was
applicable, a previous non-silent configuration may be restored should
the DMP be found to no longer be applicable. Once the device's previous
configuration is restored, example process 400 continues at block 410.
[0035]FIG. 5 is a block diagram showing an example computing environment
500 in which the technologies and processes described above may be
implemented. A suitable computing environment may be implemented with
numerous general purpose or special purpose systems. Examples of well
known systems may include, but are not limited to, cell phones, personal
digital assistants ("PDA"), personal computers ("PC"), hand-held or
laptop devices, microprocessor-based systems, multiprocessor systems,
servers, workstations, consumer electronic devices, set-top boxes, and
the like.
[0036]Computing environment 500 typically includes a general-purpose
computing system in the form of a computing device 501 coupled to various
components, such as peripheral devices 502, 503, 504 and the like. System
500 may couple to various other components, such as input devices 503,
including voice recognition, touch pads, buttons, keyboards and/or
pointing devices, such as a mouse or trackball, via one or more
input/output ("I/O") interfaces 512. The components of computing device
501 may include one or more processors (including central processing
units ("CPU"), graphics processing units ("GPU"), microprocessors
(".mu.P"), and the like) 507, system memory 509, and a system bus 508
that typically couples the various components. Processor 507 typically
processes or executes various computer-executable instructions to control
the operation of computing device 501 and to communicate with other
electronic and/or computing devices, systems or environment (not shown)
via various communications connections such as a network connection 514
or the like. System bus 508 represents any number of several types of bus
structures, including a memory bus or memory controller, a peripheral
bus, a serial bus, an accelerated graphics port, a processor or local bus
using any of a variety of bus architectures, and the like.
[0037]System memory 509 may include computer readable media in the form of
volatile memory, such as random access memory ("RAM"), and/or
non-volatile memory, such as read only memory ("ROM") or flash memory
("FLASH"). A basic input/output system ("BIOS") may be stored in
non-volatile or the like. System memory 509 typically stores data,
computer-executable instructions and/or program modules comprising
computer-executable instructions that are immediately accessible to
and/or presently operated on by one or more of the processors 507.
[0038]Mass storage devices 504 and 510 may be coupled to computing device
501 or incorporated into computing device 501 via coupling to the system
bus. Such mass storage devices 504 and 510 may include non-volatile RAM,
a magnetic disk drive which reads from and/or writes to a removable,
non-volatile magnetic disk (e.g., a "floppy disk") 505, and/or an optical
disk drive that reads from and/or writes to a non-volatile optical disk
such as a CD ROM, DVD ROM 506. Alternatively, a mass storage device, such
as hard disk 510, may include non-removable storage medium. Other mass
storage devices may include memory cards, memory sticks, tape storage
devices, and the like.
[0039]Any number of computer programs, files, data structures, and the
like may be stored in mass storage 510, other storage devices 504, 505,
506 and system memory 509 (typically limited by available space)
including, by way of example and not limitation, operating systems,
application programs, data files, directory structures,
computer-executable instructions, and the like.
[0040]Output components or devices, such as display device 502, may be
coupled to computing device 501, typically via an interface such as a
display adapter 511. Output device 502 may be a liquid crystal display
("LCD"). Other example output devices may include printers, audio
outputs, voice outputs, cathode ray tube ("CRT") displays, tactile
devices or other sensory output mechanisms, or the like. Output devices
may enable computing device 501 to interact with human operators or other
machines, systems, computing environments, or the like. A user may
interface with computing environment 500 via any number of different I/O
devices 503 such as a touch pad, buttons, keyboard, mouse, joystick, game
pad, data port, and the like. These and other I/O devices may be coupled
to processor 507 via I/O interfaces 512 which may be coupled to system
bus 508, and/or may be coupled by other interfaces and bus structures,
such as a parallel port, game port, universal serial bus ("USB"), fire
wire, infrared ("IR") port, and the like.
[0041]Computing device 501 may operate in a networked environment via
communications connections to one or more remote computing devices
through one or more cellular networks, wireless networks, local area
networks ("LAN"), wide area networks ("WAN"), storage area networks
("SAN"), the Internet, radio links, optical links and the like. Computing
device 501 may be coupled to a network via network adapter 513 or the
like, or, alternatively, via a modem, digital subscriber line ("DSL")
link, integrated services digital network ("ISDN") link, Internet link,
wireless link, or the like.
[0042]Communications connection 514, such as a network connection,
typically provides a coupling to communications media, such as a network.
Communications media typically provide computer-readable and
computer-executable instructions, data structures, files, program modules
and other data using a modulated data signal, such as a carrier wave or
other transport mechanism. The term "modulated data signal" typically
means a signal that has one or more of its characteristics set or changed
in such a manner as to encode information in the signal. By way of
example, and not limitation, communications media may include wired
media, such as a wired network or direct-wired connection or the like,
and wireless media, such as acoustic, radio frequency, infrared, or other
wireless communications mechanisms.
[0043]Power source 590, such as a battery or a power supply, typically
provides power for portions or all of computing environment 500. In the
case of the computing environment 500 being a mobile device or portable
device or the like, power source 590 may be a battery. Alternatively, in
the case computing environment 500 is a computer or server or the like,
power source 590 may be a power supply designed to connect to an
alternating current ("AC") source, such as via a wall outlet.
[0044]Some mobile devices may not include many of the components described
in connection with FIG. 5. For example, an electronic badge may be
comprised of a coil of wire along with a simple processing unit 507 or
the like, the coil configured to act as power source 590 when in
proximity to a card reader device or the like. Such a coil may also be
configure to act as an antenna coupled to the processing unit 507 or the
like, the coil antenna capable of providing a form of communication
between the electronic badge and the card reader device. Such
communication may not involve networking, but may alternatively be
general or special purpose communications via telemetry, point-to-point,
RF, IR, audio, or other means. An electronic card may not include display
502, I/O device 503, or many of the other components described in
connection with FIG. 5. Other mobile devices that may not include many of
the components described in connection with FIG. 5, by way of example and
not limitation, include electronic bracelets, electronic tags,
implantable devices, and the like.
[0045]Those skilled in the art will realize that storage devices utilized
to provide computer-readable and computer-executable instructions and
data can be distributed over a network. For example, a remote computer or
storage device may store computer-readable and computer-executable
instructions in the form of software applications and data. A local
computer may access the remote computer or storage device via the network
and download part or all of a software application or data and may
execute any computer-executable instructions. Alternatively, the local
computer may download pieces of the software or data as needed, or
distributively process the software by executing some of the instructions
at the local computer and some at remote computers and/or devices.
[0046]Those skilled in the art will also realize that, by utilizing
conventional techniques, all or portions of the software's
computer-executable instructions may be carried out by a dedicated
electronic circuit such as a digital signal processor ("DSP"),
programmable logic array ("PLA"), discrete circuits, and the like. The
term "electronic apparatus" may include computing devices or consumer
electronic devices comprising any software, firmware or the like, or
electronic devices or circuits comprising no software, firmware or the
like.
[0047]The term "firmware" typically refers to executable instructions,
code or data maintained in an electronic device such as a ROM. The term
"software" generally refers to executable instructions, code, data,
applications, programs, or the like maintained in or on any form of
computer-readable media. The term "computer-readable media" typically
refers to system memory, storage devices and their associated media, and
the like.
[0048]In view of the many possible embodiments to which the principles of
the present invention and the forgoing examples may be applied, it should
be recognized that the examples described herein are meant to be
illustrative only and should not be taken as limiting the scope of the
present invention. Therefore, the invention as described herein
contemplates all such embodiments as may come within the scope of the
following claims and any equivalents thereto.
* * * * *