|Publication number||US7242946 B2|
|Application number||US 10/495,793|
|Publication date||Jul 10, 2007|
|Filing date||Oct 9, 2002|
|Priority date||Nov 21, 2001|
|Also published as||CA2467516A1, CA2467516C, CN1602645A, CN1602645B, DE60227977D1, EP1446978A1, EP1446978B1, US20050014485, WO2003045078A1, WO2003045099A1, WO2003047297A1|
|Publication number||10495793, 495793, PCT/2002/4400, PCT/IB/2/004400, PCT/IB/2/04400, PCT/IB/2002/004400, PCT/IB/2002/04400, PCT/IB2/004400, PCT/IB2/04400, PCT/IB2002/004400, PCT/IB2002/04400, PCT/IB2002004400, PCT/IB200204400, PCT/IB2004400, PCT/IB204400, US 7242946 B2, US 7242946B2, US-B2-7242946, US7242946 B2, US7242946B2|
|Inventors||Petri Kokkonen, Markus Maanoja, Tomi Varonen, Jan Ignatius|
|Original Assignee||Nokia Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (20), Non-Patent Citations (1), Referenced by (49), Classifications (21), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to a method for controlling the privacy of a user in a network and to a telecommunications network.
Communication systems providing mobility for the users thereof are known. A well known example of the mobile communication systems is the public land line mobile network (PLMN), a cellular communication network being an example of the PLMN. Another example is a mobile communication system that is based, at least partially, on use of communication satellites.
The mobile network apparatus and/or user equipment such as a mobile station can be employed for provision of information regarding the geographical location of the user equipment and thus the user thereof. A mobile user equipment and thus the user thereof can be positioned by various different techniques. For example, substantially accurate geographical location information that associates with a user equipment can be obtained based on the known satellite based GPS (Global Positioning System). More accurate location information can be obtained through a differential GPS.
Another possibility is to use a location service that associates with a cellular telecommunications system for the provision of the location information. In this approach the cells or similar geographically limited radio access entities and associated controllers of the communication system are utilised in production of at least a rough location information estimate concerning the current location of the mobile user equipment. To improve the accuracy of the location information the communication system may be provided with specific location measurement units that provide more accurate data concerning the location of a user equipment within the service area of the cellular system. It is also possible to determine geographical location when the mobile user equipment is located within the coverage area of a visited or “foreign” network. The visited network may be made capable of transmitting the location of the mobile user equipment back to the home network, e.g. to support services that are based on location information or for the purposes of routing and charging.
The location data may be processed in a specific location service entity that is implemented either within the cellular system or connected thereto. The location data may also be processed in the user equipment that is provided with appropriate processing capacity. The location service entity provided by the communication system may serve different clients via an appropriate interface.
The location information may be used for various purposes, such as for location of a mobile telephone that has made an emergency call, for locating vehicles or given mobile subscribers and so on. In general, a client such as user equipment or another entity wishing to receive location information regarding user equipment may send a request for such information to the location service provision entity. The location service provisioning entity will then process the request, obtain the required data and generate an appropriate response.
An example of the provision of location information by a PLMN is described in more detail in 3rd Generation Partnership Project (3GPP) technical specifications, see e.g. 3GPP TS 23.271 version 4.2.0, titled “Functional stage 2 description of LCS”, June 2001.
According to the 3GPP specification a location service (LCS) server entity referred to as a Gateway Mobile Location Center (GMLC) is provided for managing the location services. The GMLC is for gathering and storing various data that may be used in the provision of location information for location service clients (LCS clients). The LCS Client may make use of that location information for various services/applications. A possible application comprises a LCS client arranged to provide location information in response to a request for non-call related location information. Such a request for location information is referred to in the 3GPP specifications as a non-call related MT-LR (Mobile Terminated Location Request).
Use of a so called “Authorized UE List” has been proposed. This list contains Mobile Subscriber ISDN (MSISDN) (ISDN—Integrated Services Digital Network) numbers or groups of MSISDNs which are authorised to initiate a location information provision procedure. That is, MSISDNs or groups of MSISDN are listed for which the LCS Client may issue a non-call related MT-LR. Separate lists of MSISDNs may be associated with each distinct external or non-call related client identity. Location information may be provided by the LCS server to the LCS client in response to a request for location information from a user with a MSISDN number that appears in the list.
The LCS Client who is external to the PLMN system may only be enabled to validly issue location information requests for those MSISDNs which are found on the “Authorized UE List”. That is, the LCS clients request may only be responded for subscribers who subscribe to the location services provided by the PLMN, as their MSISDNs would not otherwise appear on the list.
Requests from the LCS Client are authenticated based on a combination of a Client ID and password stored in a LCS Client profile at the LSC server (e.g. the GMLC) and authorized based on the “Authorized UE List”. That is, the LCS client is authorised to receive location information from the GMLC entity if the requesting user equipment (UE) is found from the list.
LCS clients are typically Application Service Providers (ASP) who are not a part of the PLMN system.
One important issue in Mobile Location Services (MLS) is the subscriber's privacy. In particular the user is able to define only broad privacy requirements which are stored in the home location register HLR. The current privacy requirements allow a user to define whether or not the user's location information can be provided and if so to which clients. Currently these privacy requirements have been handled by Mobile Services Switching Centre (MSC), GMLC, and the mobile terminal based on the information stored in the home location register. For example, Client screening is done in the GMLC (that is clients can request location information via the GMLC network operator) and in the MSC/VLR (that is clients can request for example a user's subscriber's location information) (VLR=Visitor Location Register).
The subscriber specific privacy parameter information is stored in the HLR and copied to VLR, if required. This information is generally called LCS privacy parameters. The problem with the existing system is that it is limited and inflexible.
Embodiments of the present invention aim to address one or several of the above problems.
According to a first aspect of the invention, there is provided a telecommunications system comprising: at least one user; a first entity for storing information defining a privacy profile for said at least one user; a second entity arranged to store an association between at least one user and said first entity; wherein said system is such that in response to a request for information relating to said user, said association stored in said second entity is used to identify said first entity so that a check can be made with respect to the privacy profile as to whether or not the requested information can be provided.
According to a second aspect of the invention, there is provided a method for controlling the privacy of a user in a telecommunications system comprising the steps of: receiving a request for information relating to said user; obtaining information from a second entity identifying a first entity, said first entity storing information defining a privacy profile for said user; and carrying out a check with respect to the privacy profile as to whether or not the requested information can be provided.
According to a third aspect of the present invention, there is provided an entity for use in a telecommunications system, said entity being arranged to store information defining a privacy profile for at least one user, said privacy profile comprising at least one of the following types of information: information defining time when the information on the user can be provided; information defining time when the information on the user can not be provided; information defining locations of the user when the information on the user can be provided; and information defining locations of the user when the information on the user can not be provided.
According to a further aspect, there is provided a home location register for use in a telecommunication system, said home location register being arranged to store information for a plurality of users identifying for each user an entity, the or each entity being arranged to store a privacy profile for the respective plurality of users.
For better understanding of the present invention, and as to how the same may be carried into effect, reference will now be made by way of example to the accompanying drawings in which:
Reference is made to
Two user equipment such as mobile stations (MS) 6 are also shown. It shall be appreciated that typically a number of user equipment will be in communication with each base station. Each base station is arranged to transmit signals to and receive signals from the mobile user equipment (UE) 6 via a wireless interface. Likewise, the user equipment 6 are able to transmit signals to and receive signals from the base stations.
Each of the base stations is connected to an access network controller such as a radio network controller (RNC) 7 of a UMTS terrestrial radio access network (UTRAN) or a base station controller of a GSM type system. The radio network controller may be connected to appropriate core network entities of the cellular system, such as a MSC (mobile switching centre) 8 and/or SGSN (serving general packet radio service support node) 11, via a suitable interface arrangement.
The location of a mobile user equipment may vary in time as the user equipment is free to move within the coverage area of a base station and also from a coverage area to another coverage area. The modern communication systems are capable of providing information regarding the geographical location of a user equipment within the coverage area thereof. The geographical location may be defined on the basis of the position of the mobile station relative to the base station(s) of the mobile telecommunications network.
The geographical location of the user equipment may be defined, for example, in X and Y co-ordinates or in latitudes and longitudes. A possibility is to use the relation between defined radiuses and angles, e.g. based on the spherical coordinate system or alike. It is also possible to define the location of the base stations and/or mobile stations in vertical directions. For example, z co-ordinate may be used when providing the location information in the vertical direction. The vertical location may be needed e.g. in mountainous environments or in cities with tall buildings.
Reference is made to
The location service (LCS) functionality of the communication system is provided by a Gateway Mobile Location Center (GMLC) entity 10. The GMLC location service node 10 is for gathering and storing data that is required for the provision of the location information. The location service node 10 is arranged to receive via appropriate interface means information concerning the location of the mobile user equipment from the cellular system.
The cellular system may be provided with various different means for processing information gathered from the cells and/or some other parameters and/or for computing by processor means appropriate calculations for determining and outputting the geographical location of the target user equipment. The location information may be obtained by using one or more of the appropriate location techniques. At least a part of the location information may be provided based on information provided by system that is separate from the communication system, such as by means of the Global Positioning System (GPS) or similar. Since there are various possibilities how to implement the location services in the cellular system and since the invention is not dependent on the used location determination technology, these are not be described in any greater detail herein.
In order to be able to separate the user equipment from each other, the location service entity 10 is capable of processing at least one form of identifiers. The identity information may be provided e.g. by means of a mobile subscriber ISDN number (MSISDN), an international mobile subscriber identifier (IMSI) or a temporary identifier (such as a temporary international mobile subscriber identifier: TIMSI) of the mobile user equipment, passwords, or any other form of identifier that can be reliably used for identifying a user equipment and/or a user.
The GMLC server 10 is arranged to receive location information from the radio access network 14 via appropriate controller entities such as the MSC 8 and/or SGSN (not shown) connected by the appropriate interface means to the access network.
The GMLC 10 may provide the location information in a predefined manner to a location services (LCS) client 12. A LCS Client 12 can be any entity that makes use of the location information. The LCS client 12 can be seen as a logical functional entity that may make a request to the location service entity 10 for the location information of one or more target user equipment. The LCS client 12 may be an entity that is external to the communication network, the client entity 12 being provided in an ASP domain 4. Examples of an ASP are Yahoo and Aktivist. The LCS client may also be an internal client (ILCS) i.e. reside in any entity or node (including the mobile station) within the communication system 1.
The LCS clients are entitled to receive at least some degree of information concerning the location (or location history) of a target user equipment. The particular requirements and characteristics of a LCS Client are typically known to the location service server of the communication system by its LCS client subscription profile. This is discussed in more detail hereinafter.
The GMLC 10 may consist of components and bearers needed to serve the LCS client 12. The GMLC 10 may provide a platform which will enable the support of location based services in parallel with other telecommunication services such as speech, data, messaging, other teleservices, user applications and supplementary services. The GMLC 10 may thus provide the client 12, on request or periodically, the current or most recent geographic location (if available) of the target user equipment or, if the location fails, an error indication and optionally the reason for the failure. A more detailed description of a LCS entity that may be employed in the embodiments of the invention can be found e.g. from the above referenced 3GPP technical specification No. 3GPP TS23.271.
A home location register 20 is provided. The home location register may store the same privacy parameters which are currently proposed. Alternatively or additionally, the home location register will store the address of an entity which stores privacy parameters for the user. In preferred embodiments of the present invention, the home location register does not include any privacy parameters. Rather, they are stored in the separate privacy entity referenced 22 in
Reference is made to
In step S10, a response is sent by the MSC to the GMLC which provides the MSISDN of the user and its location.
In preferred embodiments of the present invention, the GMLC has been described as sending the privacy check requests. However, in alternative embodiments of the present invention, other entities may provide that request, for example, the SGSN or MSC or indeed any other suitable entity.
Reference is made to
In step T1, the LCS client sends a request to the GMLC. This corresponds to step S2 in
In step T5, the privacy profile register 22 provides two responses. One response is call/session related. That is, the response indicating whether or not location information on the user can be provided will take into account the fact that the user has requested the particular location service. However, there may be, for example, bars on the user's subscription which prevent the user from obtaining a particular location service. The second result assumes that the user has not initiated a call/session. It may well be that the call/session related response and the call/session unrelated response may be different or the same.
In step T6, the GMLC 10 sends the provide subscriber location message to the MSC or SGSN, depending on the network. This message can contain two results, one call/session related and second call/session unrelated. Depending on whether or not the user has initiated the call/session, one of the two responses from the privacy profile holder 22 will be used. The remaining steps of
In one modification to the embodiment of the present invention, the GMLC may have already received information either from the MSC/SGSN directly or, for example from the LCS client indicating whether or not there is a call/session in place. If so, the GMLC request in step T4 would specify whether or not there was a call/session in place. The privacy profile register would then need only to provide a single response.
In one modification to the embodiment of the present invention, the GMLC may receive information in the provide subscriber location response message either from the MSC/SGSN indicating whether or not there is a call/session, in place. The GMLC can forward this information and the location information to the privacy profile register before sending the LCS response to the LCS client as in step S13. Based on call/session information and location information the privacy profile register can reject or approve the location request.
In yet another embodiment of the present invention, the response from the privacy profile register could instead be sent directly to the MSC/SGSN and not to the GMLC entity.
One further modification to the present invention will now be described. A concept called anonymous target subscriber has been proposed in the context of the location request procedure. In this concept the target subscriber can hide his true identity from LCS client (application). In this case the LCS service request is send from the LCS client to the LCS server (GMLC) containing only the pseudonym of the target subscriber. In one preferred modification to the present invention, it is possible for the target subscriber to allow only location requests where the true identity of the target subscriber is hidden from the LCS client. The target subscriber can be kept anonymous from the LCS client when the LSC service request only contains the pseudonym of the target subscriber.
Embodiments of the present invention may be such that the subscriber can be sure that only location requests where the true identity of the subscriber is hidden shall be allowed. In an embodiment of the present invention, the target subscriber is able to use this anonymity as a part of his privacy profile, as discussed previously and to be used in the privacy check.
This embodiment enhances the subscriber's privacy.
Reference is made to the two third generation specifications LSC3GPP TS 23.071 and LCS 3GPP TS 23.271 which currently define location requests.
Embodiments of the present invention have been described in the context of privacy relating to location services. However, it should be appreciated that alternative embodiments of the present invention can be used with additional or alternative services such as presence services and other services which contain information about the subscriber, e.g. dating services. It should also be appreciated that general and specific information regarding the user, the subscriber, the client, ASP or service may be stored in the profile data base. Thus the information stored in the entity may define a user profile, a subscriber profile, a client profile, an ASP profile or a service profile, these profiles may or may not include privacy information. Where the information relates to the client, the ASP or the service, there may be no information or there may be information relating to a subscriber or a user.
It should be appreciated that when the user 3 roams to a different network, the so-called “visited network”, the information associated with that user is copied from the home location register 20 to the visitor location register of the visited network. The check as to whether or not the user can receive the information is made in a MSC of the visited network using the information temporarily stored in the VLR. The visited network may access the privacy entity 22.
Whilst the invention has been particularly described herein with reference to MSCs and VLRS, the invention is not limited to such and applies equally, for example to GPRS arrangements and consequently SGSNs.
It should be appreciated that whilst embodiments of the present invention have been described in relation to user equipment such as mobile stations, embodiments of the present invention are applicable to any other suitable type of user equipment.
The entity which stores the address of the privacy entity is described in preferred embodiments of the invention as being the HLR but in alternative embodiments of the invention can be provided in user equipment, mobile services switching centre or a mobile station. The entity making the location request or the like is preferably the GMLC, SGSN or MSC but may in alternative embodiments be the HLR, mobile station or, user equipment. The privacy entity may be a server, user equipment or mobile station.
The embodiment of the present invention has been described in the context of a third generation communication system. This invention is also applicable to any other communication system.
It is also noted herein that while the above describes exemplifying embodiments of the invention, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention as defined in the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5493692||Dec 3, 1993||Feb 20, 1996||Xerox Corporation||Selective delivery of electronic messages in a multiple computer system based on context and environment of a user|
|US5790665 *||Jan 17, 1997||Aug 4, 1998||Micali; Silvio||Anonymous information retrieval system (ARS)|
|US6195557 *||Apr 20, 1998||Feb 27, 2001||Ericsson Inc.||System and method for use of override keys for location services|
|US6269244 *||Sep 22, 1999||Jul 31, 2001||Ericsson Inc.||Enhanced cellular network architecture|
|US6311069||Mar 18, 1999||Oct 30, 2001||Ericsson Inc.||System and method for alerting a mobile subscriber being positioned|
|US6463289 *||Aug 9, 1999||Oct 8, 2002||Ericsson Inc.||System and method for providing restricting positioning of a target mobile station based on the calculated location estimate|
|US6519249 *||Dec 23, 1998||Feb 11, 2003||Nortel Networks Ltd||Scalable gatekeepers in an internet telephony system and a method of operation|
|US20020098832 *||Jan 22, 2001||Jul 25, 2002||Wolfgang Fleischer||Intelligent personalized customer service|
|US20020110096 *||Jun 22, 2001||Aug 15, 2002||Hans Carlsson||Wireless network architechture and protocol for location services in GPRS packet data network|
|US20020137525 *||Mar 23, 2001||Sep 26, 2002||Wolfgang Fleischer||Providing location based directory numbers for personalized services|
|US20020138601 *||Sep 21, 2001||Sep 26, 2002||Nixu Oy||Proxy for content service|
|US20020154642 *||Apr 24, 2001||Oct 24, 2002||Hassan Hagirahim||Method of transmitting packets in a mobile 3G network system|
|US20020160810 *||Mar 14, 2001||Oct 31, 2002||Telefonaktiebolaget Lm Ericsson (Publ)||Intelligent network service control point and method of implementing user services utilizing call processing language scripts|
|US20020174363 *||May 17, 2001||Nov 21, 2002||International Business Machines Corporation||Method and apparatus for providing an anonymous identity for a user|
|US20030011511 *||Jun 3, 2002||Jan 16, 2003||King Thomas M.||Method and apparatus for assisted GPS|
|US20030074456 *||Oct 12, 2001||Apr 17, 2003||Peter Yeung||System and a method relating to access control|
|US20030134648 *||Sep 24, 2002||Jul 17, 2003||Reed Mark Jefferson||Machine for providing a dynamic data base of geographic location information for a plurality of wireless devices and process for making same|
|EP1113678A2||Dec 29, 2000||Jul 4, 2001||SAMSUNG ELECTRONICS Co. Ltd.||Location privacy feature for wireless mobile stations and method of operation|
|WO1999027746A1||Nov 23, 1998||Jun 3, 1999||Ericsson Inc.||System and method for authorization of location services|
|WO2001028273A1||Oct 11, 2000||Apr 19, 2001||Sonera Oyj||A method and system for protecting a user identifier|
|1||ETSI TS 123 271 V4.3.0 (Oct. 2001) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Functional stage 2 description of location services (3GP TS 23.271 version 4.3.0 Release 4).|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7627331 *||Oct 25, 2005||Dec 1, 2009||Nortel Networks Limited||Relating to internet protocol (IP) location, privacy and presence|
|US7729705 *||Apr 21, 2006||Jun 1, 2010||Samsung Electronics Co., Ltd.||Method of providing location service over IMS network|
|US7869814 *||May 11, 2009||Jan 11, 2011||Nortel Networks Limited||Internet protocol (IP) location, privacy and presence|
|US7992195 *||Mar 26, 2003||Aug 2, 2011||International Business Machines Corporation||Efficient browser-based identity management providing personal control and anonymity|
|US8050690||Aug 14, 2007||Nov 1, 2011||Mpanion, Inc.||Location based presence and privacy management|
|US8160560||Feb 29, 2008||Apr 17, 2012||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US8190169 *||Dec 5, 2005||May 29, 2012||Lg Electronics Inc.||Method of canceling location information request|
|US8224353||Sep 22, 2008||Jul 17, 2012||Aegis Mobility, Inc.||Disseminating targeted location-based content to mobile device users|
|US8285308 *||May 5, 2009||Oct 9, 2012||Aegis Mobility, Inc.||Disseminating targeted location-based content to mobile device users|
|US8385901||Jul 1, 2011||Feb 26, 2013||Aegis Mobility, Inc.||System and methods for monitoring the context associated with a mobile communication device|
|US8489111||Mar 20, 2010||Jul 16, 2013||Mpanion, Inc.||Real-time location and presence using a push-location client and server|
|US8521182||May 21, 2012||Aug 27, 2013||Lg Electronics Inc.||Method of canceling location information request|
|US8526942||Oct 24, 2011||Sep 3, 2013||Aegis Mobility, Inc.||Mobility call management|
|US8532667||Feb 29, 2008||Sep 10, 2013||Aegis Mobility, Inc.||System and methods for monitoring the geospatial context associated with a mobile communication device|
|US8583079||Mar 22, 2011||Nov 12, 2013||Mpanion, Inc.||Rich presence status based on location, activity, availability and transit status of a user|
|US8626201||Oct 5, 2012||Jan 7, 2014||Aegis Mobility, Inc.||Disseminating targeted location-based content to mobile device users|
|US8634788||Feb 29, 2008||Jan 21, 2014||Aegis Mobility, Inc.||System and methods for monitoring the context associated with a mobile communication device|
|US8738005||Feb 29, 2008||May 27, 2014||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US8756676 *||Oct 1, 2010||Jun 17, 2014||Citicorp Development Center, Inc.||System and method for secure message reply|
|US8761821||Jul 21, 2010||Jun 24, 2014||Katasi Llc||Method and system for controlling a mobile communication device in a moving vehicle|
|US8781491||Feb 29, 2008||Jul 15, 2014||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US8787936||Jul 21, 2010||Jul 22, 2014||Katasi Llc||Method and system for controlling a mobile communication device in a moving vehicle|
|US8923826||Aug 30, 2013||Dec 30, 2014||Aegis Mobility, Inc.||Mobility call management|
|US8929917||Jul 18, 2013||Jan 6, 2015||Lg Electronics Inc.||Method of canceling location information request|
|US8942686||Sep 4, 2009||Jan 27, 2015||Aegis Mobility, Inc.||Providing and managing bypass of enhanced services|
|US8948784||Sep 9, 2013||Feb 3, 2015||Aegis Mobility, Inc.||Monitoring geospatial context of a mobile device|
|US8958830||Sep 22, 2011||Feb 17, 2015||Mpanion, Inc.||Location based presence and privacy management|
|US8965464||Jun 21, 2013||Feb 24, 2015||Mpanion, Inc.||Real-time location and presence using a push-location client and server|
|US8983412||Feb 22, 2013||Mar 17, 2015||Aegis Mobility, Inc.||Monitoring mobile device context|
|US9094533||Apr 16, 2012||Jul 28, 2015||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US9369452 *||Jun 13, 2014||Jun 14, 2016||Citicorp Credit Services, Inc. (Usa)||System and method for secure message reply|
|US9386447||Sep 12, 2012||Jul 5, 2016||Scott Ferrill Tibbitts||Method and system for controlling a mobile communication device|
|US9450897||Oct 17, 2013||Sep 20, 2016||Mpanion, Inc.||Rich presence status based on location, activity, availability and transit status of a user|
|US9451447||Jul 21, 2014||Sep 20, 2016||Katasi Llc||Method and system for controlling a mobile communication device in a moving vehicle|
|US9615213||Dec 23, 2013||Apr 4, 2017||Katasi Llc||Method and system for controlling and modifying driving behaviors|
|US20060120320 *||Dec 5, 2005||Jun 8, 2006||Lg Electronics Inc.||Method of canceling location information reques|
|US20060135177 *||Oct 25, 2005||Jun 22, 2006||James Winterbottom||Relating to internet protocol (IP) location, privacy and presence|
|US20060242307 *||Apr 21, 2006||Oct 26, 2006||Samsung Electronics Co., Ltd.||Method of providing location service over IMS network|
|US20070130460 *||Mar 26, 2003||Jun 7, 2007||Birgit Pfitzmann||Efficient browser-based identity management providing personal control and anonymity|
|US20080299954 *||Feb 29, 2008||Dec 4, 2008||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US20080299959 *||Feb 29, 2008||Dec 4, 2008||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US20080305779 *||Feb 29, 2008||Dec 11, 2008||Aegis Mobility, Inc.||System and methods for monitoring the context associated with a mobile communication device|
|US20080305780 *||Feb 29, 2008||Dec 11, 2008||Aegis Mobility, Inc.||Management of mobile device communication sessions to reduce user distraction|
|US20080305808 *||Feb 29, 2008||Dec 11, 2008||Aegis Mobility, Inc.||System and methods for monitoring the geospatial context associated with a mobile communication device|
|US20080318562 *||Feb 29, 2008||Dec 25, 2008||Aegis Mobility, Inc.||System and methods for monitoring the context associated with a mobile communication device|
|US20090239553 *||Sep 22, 2008||Sep 24, 2009||Aegis Mobility, Inc.||Disseminating targeted location-based content to mobile device users|
|US20090255000 *||May 11, 2009||Oct 8, 2009||Nortel Networks Limted||Internet Protocol (IP) Location, Privacy and Presence|
|US20100029270 *||Apr 4, 2007||Feb 4, 2010||David John Kiddie||Mobility call management|
|US20100284290 *||Apr 9, 2010||Nov 11, 2010||Aegis Mobility, Inc.||Context based data mediation|
|U.S. Classification||455/456.1, 455/456.2, 455/457, 455/456.3|
|International Classification||H04M1/68, H04W8/18, H04W4/02, H04W12/02, H04W8/16|
|Cooperative Classification||H04M3/42068, H04M2242/22, H04M3/42059, H04W12/02, H04W8/16, H04M2203/6009, H04W4/02, H04L63/101, H04W8/18|
|European Classification||H04L63/10A, H04W8/16, H04W12/02|
|Sep 7, 2004||AS||Assignment|
Owner name: NOKIA CORPORATION, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOKKONEN, PETRI;MAANOJA, MARKUS;VARONEN, TOMI;AND OTHERS;REEL/FRAME:015772/0149;SIGNING DATES FROM 20040618 TO 20040830
|Feb 21, 2008||AS||Assignment|
Owner name: NOKIA SIEMENS NETWORKS OY, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:020550/0001
Effective date: 20070913
Owner name: NOKIA SIEMENS NETWORKS OY,FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:020550/0001
Effective date: 20070913
|Jan 6, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Nov 19, 2014||AS||Assignment|
Owner name: NOKIA SOLUTIONS AND NETWORKS OY, FINLAND
Free format text: CHANGE OF NAME;ASSIGNOR:NOKIA SIEMENS NETWORKS OY;REEL/FRAME:034294/0603
Effective date: 20130819
|Dec 31, 2014||FPAY||Fee payment|
Year of fee payment: 8