|Publication number||US7860516 B2|
|Application number||US 11/566,860|
|Publication date||Dec 28, 2010|
|Filing date||Dec 5, 2006|
|Priority date||Dec 5, 2006|
|Also published as||CN101554067A, CN101554067B, EP2089996A1, US20080133791, WO2008070690A1|
|Publication number||11566860, 566860, US 7860516 B2, US 7860516B2, US-B2-7860516, US7860516 B2, US7860516B2|
|Inventors||Stephen Hodges, John Chiloyan|
|Original Assignee||Microsoft Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (29), Non-Patent Citations (10), Referenced by (15), Classifications (8), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
In order that a software product can be released in many countries, the software product goes through a process known as ‘localization’ in which various aspects of the user interface (UI) are modified for the specific country. Localization often includes translation of all the string elements within the UI of the product and any other language specific parts (e.g. hotkeys, units, sizes) from the language in which it was originally written to the language for the specific country.
For some software products and also for hardware products, changes must also be made to ensure that the operation of the product complies with local legislation. For example, there may be different regulations controlling the permitted electromagnetic emissions of a device and some countries require that a camera phone provides an audible indication when an image is captured. These different regulations often lead to manufacturers producing different models of a product where each model is aimed at a specific market and has been tailored to meet the appropriate standards and comply with the legislation in that market.
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.
A device is described which changes its operation dependent upon the location of the device. The device accesses parameters which are specific to its location and uses these to determine how the operation of the device should be changed.
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.
The present description will be better understood from the following detailed description read in light of the accompanying drawings, wherein:
Like reference numerals are used to designate like parts in the accompanying drawings.
The detailed description provided 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 example and the sequence of steps for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.
Although mobile electronic devices such as mobile telephones and personal digital assistants (PDAs) may be built for a single market, it is likely that they will be used in many different countries as the user travels. In order to ensure that the mobile electronic device does not break any laws in countries to which the user travels, one solution is to develop mobile electronic devices which comply with the legislation in all countries or in a collection of countries (e.g. a device which complies with all European and US legislation). However, this may result in sub-optimum performance of the device and in some cases may not be possible where the regulations specify conflicting parameters (e.g. relating to frequencies for transmission of data).
Another solution is to change the operation of the device dependent upon the location of the device. This enables the device to perform optimally in any particular location whilst still ensuring that it complies with local legislation. In addition to automatically changing the operation of the device to comply with local legislation, the operation of the device (hardware/software) may also be changed to suit the appropriate lingual, social and cultural requirements. The changes made may be different dependent on whether the device is mobile or non-mobile (i.e. generally used in one place, such as a desktop PC). For example, for mobile devices moving from a first country to a second country, the user is unlikely to change (e.g. when a user goes abroad) and therefore the lingual requirements will not change (the device should still use a UI in the language of the first country). However, where a typically non-mobile device (e.g. a larger device) is moved from a first country to a second country, this may be for deployment (or redeployment) and therefore the user may be from the second country and therefore the lingual requirements may change.
As shown in
In another example, as shown in
The networks shown in
The location specific data may comprise a set of rules that the device must comply with and/or sets of parameters to be used by the device at the particular location. These rules and/or parameters may relate to any aspect of the device's operation, for example:
The location specific data may further comprise other data relating to location specific laws or regulations, such as data relating to location specific airport regulations (e.g. customs information, security information), location specific driving laws (e.g. the ten most important traffic laws), location specific safety/security advice etc. This other data and/or the rules/parameters described above may be presented to the user via a user interface (e.g. through a custom application on the device or using an existing application).
As described above, the location specific data may be accessed by the device from any location including local memory (e.g. from a memory within the device), removable media or a remote data store. In an example a central service provider (or a network provider) may maintain a central repository of location specific data. This central repository may be a database containing the location specific data for some/all locations or it may contain details of where location specific data is located for each country. In an example, a service provider may host a web site with links to the locations of location specific data for each country. The location specific data may then be maintained within each country, for example by a central agency or government body. In a further example, the device may use a search tool to find the location specific data (e.g. using www.live.com to search for “communications regulations in France”). In another example, a device manufacturer may provide a library of device settings (which comprises the location specific data) for particular locations which may be accessed by the device. The data stored remotely to the device may be accessed whenever the device moves location in order to obtain the specific data for the new location or alternatively, the data may be copied from the remote data store(s) and stored locally on the device. The device may then periodically access the remote data store(s) to obtain any updates to the data. Such a method may be particularly suitable where the location specific data is changed infrequently and/or where it is undesirable for the device to need to disclose its current location to the provider of the data store(s). Where a device is not (or is not normally) connected to a network, such updates to locally stored location specific data may be periodically downloaded to the device via a networked device, such as a computer.
In another example, the location specific data may be accessed by the device as a result of the data being pushed to the device. The data may be pushed by the network operator or by a service provider based on the location of the device (e.g. based on the network or the access point to which the device is connected). The data may be pushed in the form of a SMS message, a MMS message, a WAP push or any other suitable technology. The data may be pushed from the network (e.g. via the appropriate access point) or from a local transmitter. A user may be prompted to accept the pushed data or the data may be automatically accepted by the device. The data may be pushed to the device each time it changes region or alternatively the data may only be pushed to a device upon entry to a new region if the device does not already have the current location specific data for that region. In such an example, data may be pushed to the device where the stored location specific data for that region is out of date.
The regions referred to in the description above and shown in
The network may detect the location of the device using any suitable method, including, but not limited to the network or the access point (e.g. base station) to which the device is connected or the IP (Internet Protocol) address of the device. Techniques developed for locating devices where emergency calls originate (particularly where the device is a wireless device or is connected to an IP network) or for tracking devices may be used to provide location information for the device. This location information is then transmitted to the device such that the device can identify its location (step 401). In addition to, or instead of, transmitting this location information, the network may transmit details describing where the location specific data may be accessed from (e.g. in the form of a URL or IP address) or the network may push the location specific data (as described above).
The device may detect its location using any suitable method, including, but not limited to use of a GPS receiver or the network or the access point (e.g. base station) to which the device is connected. Where the device can detect signals from more than one access point (e.g. from more than one base station) then this data may be used to provide more accurate location information (e.g. using triangulation or any other combination of location information). Where data is accessed from a remote location via a network, the network used for accessing the data may be the same network that may be used for identifying location of the device or may be a different network. In an example, a device may determine its location based on its connection to a Wifi hotspot, however the relevant location specific data may be accessed via a GPRS network. In further examples, the device may identify location based on other factors (e.g. mains voltage, power lead used etc).
Different methods of location detection (by the network or the device) provide different levels of granularity of location information, for example, knowledge of the network to which a device is connected is likely to provide information on the country in which the device is located, whilst knowledge of the access point to which a device is connected is likely to provide much more precise location information particularly where the access point is wireless and the range of the wireless is link is short (e.g. a WiFi hotspot or a Bluetooth access point). Where the device is connected to a fixed network, the location may be known precisely (e.g. where a port is registered to a particular location) or the location may be determined less precisely (as described above).
In an example, a mobile telephone may be purchased in the UK by a UK based user. The mobile telephone therefore complies with UK legislation. If the user travels to Dubai, the mobile telephone roams and connects to the local mobile telephone network. The mobile telephone detects that it is connected to a network in Dubai and therefore accesses a remote data source containing rules for operation of mobile telephones in Dubai and changes the operation of the mobile telephone to comply with those rules. This enables the mobile telephone to optimize its performance for use in Dubai without contravening any legislation. When the user returns to the UK, the telephone detects that it has connected to a UK network. In this situation it may access UK specific data or alternatively may return to the ‘default’ or ‘home’ operation of the telephone which cancels any of the changes made when the device traveled to Dubai.
In a second example, a computer may be built and tested in the UK to comply with UK legislation. The computer may subsequently be shipped to France and deployed in France e.g. by connection to a corporate network in France by means of an Ethernet connection. Location information may be passed to the computer via the corporate network and as a result, the computer may access a locally stored library of rules for France. On the basis of these rules, the computer may alter its operation such that it complies with French legislation, launches the French versions of the operating system and any applications and offers a custom set of backgrounds and screensavers which has been provided for use in France.
In the above examples, location specific data for a single location is accessed by each device at any time, for example, as shown in
The triggers for accessing the location specific data in the two regions E and F may be different. For example, region E may be a country and on entry to region E the device may identify the location of the device (e.g. using one of the techniques described above) and this may trigger the accessing of the location specific data for region E (as shown in
The location specific data in the two regions E and F may relate to different aspects of the device's operation or alternatively may result in complying with different sets of legislation/regulations. For example, the larger region's location specific data may be such as to ensure that the device complies with the relevant legislation for that country/region/state etc, whilst the smaller region's location specific data may be such as to make the device comply with local policy (e.g. no images to be captured, no audible alerts or ring tones, automatically switching to ‘flight mode’ when on an airplane or going through immigration etc). Where two regions overlap, the location specific data may be flagged to indicate that the new location specific data is to be complied with in addition to the previously received location specific data and not instead of the previously received location specific data. In another example, data sets may be flagged to identify which regions lie within other regions and/or to identify which location specific data sets have priority over other data sets.
By using such a tiered approach, as shown in
Whilst the above examples relate to devices which connect to a network, the methods are equally applicable to devices which do not connect to a network, such as a camera. In such an example, the device may detect the presence of a network, whilst not connecting to that network, and use the information detected to determine location. In another example the device may detect location using other techniques (e.g. GPS or other positioning system) and access location specific data based on the location determination. In a further example, the device may identify location based on other factors (e.g. mains voltage, power lead used etc). Where the device is not connected to a network, the location specific data may be stored locally or may be pushed to the device (e.g. via a Bluetooth or IRDA link).
The above methods are applicable to any mobile or portable device, including, but not limited to, electronic devices such as laptop computers, tablet PCs, mobile telephones, PDAs, cameras and watches. The above methods are also applicable to any non-mobile device, including, but not limited to, computers, televisions, radios, RFID (radio frequency identification) readers, ATMs (automated teller machine), cash registers, point of sale machines (e.g. chip and pin machines for credit/debit cards) and home appliances (e.g. microwave ovens, fridge freezers etc).
Although the present examples are described and illustrated herein as being implemented in a communications network, the system 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 systems and the method may be implemented in devices without any network connection (e.g. devices with GPS capability or other location detection capability).
The term ‘computer’ is used herein to refer to any device with processing capability such that it can execute instructions. Those skilled in the art will realize that such processing capabilities are incorporated into many different devices and therefore the term ‘computer’ includes PCs, servers, mobile telephones, personal digital assistants and many other devices.
The methods described herein may be performed by software in machine readable form on a storage medium. The software can be suitable for execution on a parallel processor or a serial processor such that the method steps may be carried out in any suitable order, or simultaneously.
This acknowledges that software can be a valuable, separately tradable commodity. It is intended to encompass software, which runs on or controls “dumb” or standard hardware, to carry out the desired functions. It is also intended to encompass software which “describes” or defines the configuration of hardware, such as HDL (hardware description language) software, as is used for designing silicon chips, or for configuring universal programmable chips, to carry out desired functions.
Those skilled in the art will realize that storage devices utilized to store program instructions can be distributed across a network. For example, a remote computer may store an example of the process described as software. A local or terminal computer may access the remote computer and download a part or all of the software to run the program. Alternatively, the local computer may download pieces of the software as needed, or execute some software instructions at the local terminal and some at the remote computer (or computer network). Those skilled in the art will also realize that by utilizing conventional techniques known to those skilled in the art that all, or a portion of the software instructions may be carried out by a dedicated circuit, such as a DSP, programmable logic array, or the like.
Any range or device value given herein may be extended or altered without losing the effect sought, as will be apparent to the skilled person.
It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. It will further be understood that references to ‘an’ item refer to one or more of those items.
The steps of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate.
It will be understood that the above description of a preferred embodiment is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments of the invention. Although various embodiments of the invention have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from the spirit or scope of this invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6415220||May 24, 2000||Jul 2, 2002||Sony International (Europe) Gmbh||Geolocation determination|
|US6484029 *||Oct 13, 1998||Nov 19, 2002||Symbol Technologies, Inc.||Apparatus and methods for adapting mobile unit to wireless LAN|
|US6539230||Aug 19, 1999||Mar 25, 2003||Lucent Technologies Inc.||Dynamic maintenance of location dependent operating parameters in a wireless terminal|
|US6750813||Jul 24, 2002||Jun 15, 2004||Mcnc Research & Development Institute||Position optimized wireless communication|
|US6879838||Apr 20, 2001||Apr 12, 2005||Koninklijke Philips Electronics N.V.||Distributed location based service system|
|US6931130 *||Oct 7, 1999||Aug 16, 2005||International Business Machines Corporation||Dynamically adjustable software encryption|
|US6963749||Jul 2, 2002||Nov 8, 2005||Denso Corporation||Radio communication terminal unit and method of transmitting location information|
|US20020054097 *||Dec 15, 1998||May 9, 2002||David James Hetherington||Method, system and computer program product for dynamic language switching via messaging|
|US20020082022 *||Dec 20, 2001||Jun 27, 2002||Pace Micro Technology Plc.||Channel selection procedure for mobile communication devices|
|US20020119788 *||Dec 22, 2000||Aug 29, 2002||Gopal Parupudi||Context-aware and location-aware cellular phones and methods|
|US20020143930||Jan 31, 2001||Oct 3, 2002||International Business Machines Corporation||System and method for handling location information|
|US20020145984||Jan 31, 2001||Oct 10, 2002||International Business Machines Corporation||System and method for aggregating information to determine users' locations|
|US20040010404 *||Jul 9, 2002||Jan 15, 2004||Stone Cheng||Method for replacing language of user interface without having to restart application|
|US20050064856 *||Sep 18, 2003||Mar 24, 2005||International Business Machines Corporation||Method and apparatus for managing functions in a camera phone|
|US20050064877||Sep 19, 2003||Mar 24, 2005||Gum Arnold J.||System and method for integration of wireless computer network in position determining technology|
|US20050114800 *||Nov 21, 2003||May 26, 2005||Sumita Rao||System and method for arranging and playing a media presentation|
|US20050181808 *||Feb 12, 2004||Aug 18, 2005||Lucent Technologies Inc.||Location based service restrictions for mobile applications|
|US20050203757 *||Mar 11, 2004||Sep 15, 2005||Hui Lei||System and method for pervasive enablement of business processes|
|US20050221841||Mar 28, 2005||Oct 6, 2005||Piccionelli Gregory A||Location-based control of functions of electronic devices|
|US20060089792||Oct 25, 2004||Apr 27, 2006||Udi Manber||System and method for displaying location-specific images on a mobile device|
|US20060107219 *||May 26, 2004||May 18, 2006||Motorola, Inc.||Method to enhance user interface and target applications based on context awareness|
|US20060135067 *||Dec 20, 2004||Jun 22, 2006||Dunko Gregory A||Method and apparatus for configuring a WLAN|
|US20060154605 *||Dec 29, 2005||Jul 13, 2006||Young-Cheol Ham||Changing operation parameter of communication terminal|
|US20060258368||Sep 29, 2005||Nov 16, 2006||Jennifer Granito||Personalized location information for mobile devices|
|WO2001061671A1||Feb 16, 2001||Aug 23, 2001||Ofer Goren||Location specific marketing using gps|
|WO2004044670A2||Nov 13, 2003||May 27, 2004||John Metcalf||Position sensitive key and lock (pskl)|
|WO2005120120A1 *||May 31, 2005||Dec 15, 2005||Matsushita Electric Industrial Co., Ltd.||Mobile terminal device, mobile function limit system, function limit method, and recording medium|
|WO2006068661A1||Jun 30, 2005||Jun 29, 2006||Sony Ericsson Mobile Communications Ab||Mobile terminal with region dependent operational parameter settings|
|WO2006079165A1||Jan 25, 2006||Aug 3, 2006||Alert Systems Pty Ltd||Proximity warning system|
|1||Chen, et al., "A Survey of Context-Aware Mobile Computing Research", available at least as early as >, at >, pp. 1-16.|
|2||Chen, et al., "A Survey of Context-Aware Mobile Computing Research", available at least as early as <<Nov. 21, 2006>>, at <<http://shamir.eas.asu.edu/˜cse591uc/papers/chen00survey.pdf>>, pp. 1-16.|
|3||*||Jiang et al., "A Hybrid Location Model with a Computable Location Identifier for Ubiquitous Computing", UbiComp 2002, LNCS 2498, pp. 246-263, 2002.|
|4||*||Jiang et al., "A Hybrid Location Model with Computable Location Identifier for Ubiquitous Computing". UbiComp 2002, LNCS 2498, pp. 246-263, 2002.|
|5||PCT International Search Report dated May 13, 2008 for corresponding PCT Application No. PCT/US07/86427, 4 pages.|
|6||Pescovitz, "Location, Location, Location Place Lab and the Boostrapping of Location-Enhanced Computing", at >,Intel Corporation 2003, Version # 3, May 3, 2004, pp. 1-7.|
|7||Pescovitz, "Location, Location, Location Place Lab and the Boostrapping of Location-Enhanced Computing", at <<http://www.intel.com/research/print/Place—Lab.pdf>>,Intel Corporation 2003, Version # 3, May 3, 2004, pp. 1-7.|
|8||*||Pescovitz, David, Location, Location, Location: Place Lab and the Bootstrapping of Location-Enhanced Computing, May 3, 2004, Intel Research and Development, version 3.|
|9||Swedberg, "Ericsson's Mobile Location Solution", available at least as early as >, at >, pp. 214-221.|
|10||Swedberg, "Ericsson's Mobile Location Solution", available at least as early as <<Nov. 21, 2006>>, at <<http://www.ericsson.com/ericsson/corpinfo/publications/review/1999—04/files/1990406.pdf>>, pp. 214-221.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8265590 *||Oct 2, 2009||Sep 11, 2012||At&T Mobility Ii Llc||Providing information pertaining to usage of a mobile wireless communications device|
|US8321212 *||Nov 27, 2012||Lg Electronics Inc.||Terminal and method for supporting multi-language|
|US8447270 *||May 21, 2013||At&T Mobility Ii Llc||Providing information pertaining usage of a mobile wireless communications|
|US8594695 *||Feb 16, 2007||Nov 26, 2013||Intel Corporation||Using location information to set radio transmitter characteristics for regulatory compliance|
|US8682287||Apr 17, 2013||Mar 25, 2014||At&T Mobility Ii Llc||Providing information pertaining usage of a mobile wireless communications device|
|US9264920 *||Feb 25, 2014||Feb 16, 2016||Wiston NeWeb Corporation||Network managing method and device for wireless network system|
|US20080200180 *||Feb 16, 2007||Aug 21, 2008||Sean Dunn||Using location information to set radio transmitter characteristics for regulatory compliance|
|US20080319734 *||Mar 10, 2008||Dec 25, 2008||Mi-Sun Kim||Terminal and method for supporting multi-language|
|US20100265848 *||Apr 21, 2009||Oct 21, 2010||Thomas Kummetz||System for automatic configuration of a mobile communication system|
|US20110081885 *||Oct 2, 2009||Apr 7, 2011||At&T Mobility Ii Llc||Providing Information Pertaining Usage Of A Mobile Wireless Communications Device|
|US20120309343 *||Dec 6, 2012||At&T Mobility Ii Llc||Providing Information Pertaining Usage Of A Mobile Wireless Communications Device|
|US20140003606 *||Jun 29, 2012||Jan 2, 2014||David Birnbaum||Systems and methods for complying with wireless guidelines based on location|
|US20140349258 *||May 26, 2013||Nov 27, 2014||Dean Joseph Lore||System for promoting travel education|
|US20150016296 *||Sep 29, 2014||Jan 15, 2015||Andrew Llc||Radio communication systems with integrated location-based measurements for diagnostics and performance optimization|
|US20150078199 *||Feb 25, 2014||Mar 19, 2015||Wistron Neweb Corporation||Network Managing Method and Device for Wireless Network System|
|U.S. Classification||455/456.1, 455/456.4|
|International Classification||H04W8/22, H04W24/00, H04W4/02|
|Cooperative Classification||H04W4/02, H04W8/22|
|Feb 1, 2006||AS||Assignment|
Owner name: KIMBERLY-CLARK WORLDWIDE, INC., WISCONSIN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZWICK, KENNETH JOHN;SHANNON, THOMAS GERARD;REKOSKE, MICHAEL JOHN;AND OTHERS;REEL/FRAME:017535/0411;SIGNING DATES FROM 20060119 TO 20060130
|Feb 14, 2007||AS||Assignment|
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HODGES, STEPHEN;CHILOYAN, JOHN;REEL/FRAME:018905/0542;SIGNING DATES FROM 20070128 TO 20070206
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HODGES, STEPHEN;CHILOYAN, JOHN;SIGNING DATES FROM 20070128 TO 20070206;REEL/FRAME:018905/0542
|Aug 8, 2014||REMI||Maintenance fee reminder mailed|
|Dec 9, 2014||AS||Assignment|
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034542/0001
Effective date: 20141014
|Dec 28, 2014||LAPS||Lapse for failure to pay maintenance fees|
|Feb 17, 2015||FP||Expired due to failure to pay maintenance fee|
Effective date: 20141228