US20020147766A1 - Operating user profiles with distributed profile model using a hybrid terminal - Google Patents
Operating user profiles with distributed profile model using a hybrid terminal Download PDFInfo
- Publication number
- US20020147766A1 US20020147766A1 US09/824,781 US82478101A US2002147766A1 US 20020147766 A1 US20020147766 A1 US 20020147766A1 US 82478101 A US82478101 A US 82478101A US 2002147766 A1 US2002147766 A1 US 2002147766A1
- Authority
- US
- United States
- Prior art keywords
- user
- service
- profile
- operator
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0407—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
- H04L63/0421—Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2113—Multi-level security, e.g. mandatory access control
Definitions
- the present invention is related to a method and system for managing a privacy level at which a user communicates with other parties and managing access and usage of the user's profile information by other parties.
- a method of managing user privacy in a network environment involves recognizing one or more service opportunities of a service operator by a user operating a user device.
- a privacy level, at which communications is conducted with a service operator, is then determined and communications with the service operator are conducted at the privacy level.
- the discovery of the one or more service opportunities can be recognized automatically.
- a further option anonymously obtains information relating to the one or more service opportunities.
- the information relating to the one or more service opportunities obtained in this manner can include a service category, a service description or a requested viewpoint.
- the service provider can be allowed to obtain access to a subset of profile information of the user according to the service category. In this manner, the service provider can provide personalized service to the user according to the subset of profile information. Alternatively, the service provider can be allowed to obtain access to a subset of profile information of the user according to the requested viewpoint. This option allows the service provider to provide personalized service to the user according to the subset of profile information.
- the present method of managing user privacy in a network environment can include determined privacy levels including Anonymous, Pseudonymous, Anonymous transaction and Authenticated. Further, the privacy level is determined based on (1) the nature of the service negotiations with the service operator, (2) a level of privacy in one or more prior transactions with the specific service operator, (3) the identity of the service operator, based on user-defined parameters, or (4) the user's prior behavior or activity.
- the method can also include obtaining a user identifier to conduct pseudonymous communications with the service operator relating to the one or more service opportunities.
- the method can also include allowing the service provider to obtain access to a predefined subset of profile information.
- the service provider can be charged a fee for obtaining the subset of profile information and the subset of profile information can be obtained from a location remote from the user device.
- the method can include allowing the service provider to determine a profile access level and can include transmitting the profile access level to the service operator.
- the service operator can obtain a subset of profile information of the user from a profile operator according to the profile access level.
- the profile access level can be determined from a service category of the one or more service opportunities or based upon a prior arrangement between the service operator and the user.
- the method can further include updating the profile information of the user and can perform such an update on user information provided by the service operator.
- the user information would be derived from the service operator's interaction with the user during the service session.
- the service operator can be compensated for providing such user information.
- the method can further include tracking user activity on the user device and updating the profile information of the user based on the tracked user activity.
- the method can further include the service provider dynamically changing the service opportunities recognized by the user, for instance, in accordance with the user's profile information.
- the method can allow the user device and the service operator to communicate across a variety of networks, such as a wide are network (WAN) or personal area network (PAN). Further, the user device can be a mobile wireless device, service can be received from the service operator, and payment for the service obtained by the user can be conducted anonymously.
- WAN wide are network
- PAN personal area network
- a method of managing user privacy in a network environment through a distributed user system including a user device and profile operator is also disclosed that recognizes one or more service opportunities of a service operator on a user device operated by a user, determines a privacy level at which communications is conducted with a service operator relating to the one or more service opportunities, determines a profile access level, transmits the profile access level to the service operator, and enables the service operator to obtain a subset of profile information of the user according to the profile access level.
- FIG. 1A is an overview of a network system for enabling a user of a communication device to control a privacy level of communications with other parties and to control access and usage of the user's profile information by other parties in accordance with an advantageous embodiment
- FIG. 1B is a general overview of an example of different network arrangements between a user device and a service operator in the network system of FIG. 1A;
- FIG. 2 is a block diagram of one example of the network system of FIG. 1A in which a user employs a Bluetooth-enabled mobile device to conduct service-related communications with a service operator through a fixed position Bluetooth-enabled wireless device;
- FIG. 3A is an exemplary block diagram of the wireless user device of FIG. 2;
- FIGS. 3B and 3C illustrate an exemplary high level architecture of components of the network system of FIG. 1A in which various application or function layers and sub-layers supported by the user device are shown;
- FIG. 4 is an exemplary block diagram of a service operator
- FIG. 5 is an exemplary block diagram of a profile operator
- FIG. 6A is an overview of one example of an operator arrangement
- FIG. 6B is an overview of another example of an operator arrangement in which service operators may be hierarchically arranged to provide additional profile access levels or profile filtering;
- FIG. 7A is an example of information maintained in a profile database by a profile operator
- FIG. 7B is an example of information maintained in a profile access authority database of a user device.
- FIGS. 8A through 8D illustrate an exemplary process by which a user device controls a privacy level of communications with a service operator and controls access and usage of the user's profile information by the service operator in accordance with an advantageous embodiment.
- FIGS. 1A and 1B show an overview of a network system 100 for enabling a user of a communication device to control a privacy level of the user's communications with other parties and to control access and usage of the user's profile information by other parties in accordance with an advantageous embodiment of the present invention.
- Network system 100 includes a user device 110 operated by a user, profile operator(s) 115 for maintaining the user's profile information, and a service operator(s) 130 for providing services to the user.
- User device 110 , profile operator 115 and service operator 130 communicate with each other across network(s) 140 .
- a radio transceiver 120 provides an access point to enable the user to conduct communications across network(s) 140 .
- Network 140 may be a local area network(s) (LAN), wide area network(s) (WAN), the Internet, wireless network(s) or a combination thereof.
- Radio transceiver 120 may be, for example, a radio tower, a general packet radio service (GPRS) access point, a general system for mobile communications (GSM) access point or a fixed position wireless device implementing the BluetoothTM standard.
- GPRS general packet radio service
- GSM general system for mobile communications
- BluetoothTM is a trademark owned by Telefonaktielbolaget L M Ericsson, Sweden.
- User device 110 may be any computerized system with communication means by which to conduct wire and wireless communications with other parties, such as service operator 130 and profile operator 110 .
- user device 110 may take the form of computer system or a mobile wireless device configured to perform the methods and processes discussed herein.
- user device 110 may be a cellular phone, personal digital assistant (PDA), portable computer, handheld device, etc.
- PDA personal digital assistant
- Service operator 130 may be any computerized system with communication means by which to conduct wire and wireless communications with other parties, such as user device 110 and profile operator 115 .
- service operator 130 may take the form of a server or computer system or a fixed or mobile wireless device configured to perform the methods and processes discussed herein.
- service operator 130 may be a server of a retailer or a cellular phone, personal digital assistant (PDA), portable computer, handheld device, etc.
- PDA personal digital assistant
- Profile operator 130 may be any computerized system with communication means by which to conduct wire and wireless communications with other parties, such as user device 110 and service operator 130 .
- profile operator 115 may take the form either as a server or computer system or a fixed or mobile wireless device configured to perform the methods and processes discussed herein.
- user device 110 may conduct communications with service operator 130 or profile operator 115 using Bluetooth technology or general packet radio service (GPRS) or general system for mobile communications (GSM), or may conduct communications with a mobile service operator 140 using Bluetooth technology or the like to establish a personal area network (PAN).
- GPRS general packet radio service
- GSM general system for mobile communications
- PAN personal area network
- user device 110 is configured to control a privacy level of communications with another party, such as a service operator.
- the user or user device 110 on behalf of the user may determine which level of privacy should be maintained in an ad hoc or user initiated communications environment.
- user device 110 may conduct the communications with another party at varied privacy levels, such as absolute anonymity (e.g., without any provision of a user identifier to the communicating party), with pseudonymity (e.g., with the use of a pseudonym) or with authenticated user identification.
- User device 110 may be set to operate at a default privacy level of anonymous.
- user device 110 may control the privacy level of communications with another party, such as service operator 130 .
- the privacy level may be determined based on a user request or automatically based on the nature of the circumstances surrounding the communications.
- user device 110 may adjust a privacy level, for example, based on the nature of the service negotiations with another party (e.g., service category or context), the level of privacy in one or more prior transactions with the specific service operator, the identity of service operator 130 , user-defined situations, the user's prior behavior or activity (e.g., profile), and so forth.
- the service negotiations may be divided into four layers, i.e., layers one, two, three and four.
- the first negotiation layer may involve an initial service inquiry or discovery, which does not require any identification of a user, e.g., a user ID. This may simply involve user device 110 scanning the environment in a very light and privacy protected way, and obtaining a response from service operator 130 .
- the response may include a service name or identifier, type and definition. Such a negotiation generally occurs automatically without user interactions.
- the second negotiation layer may involve, for example, the provision of user profile information to service operator 130 for service personalization.
- user device 110 may provide service operator 130 with a pseudonym identifier. This identifier may be generated on a per session basis when conducting communications with service operator 130 (i.e., a session ID). In this way, service operators are prevented from collecting profile information individually for each customer.
- the third negotiation layer may involve, for example, anonymous service delivery which may also include anonymous payment possibilities.
- service may still be rendered by service operator 130 without any need to disclose the identity of the user.
- a user may conduct an anonymous service transaction to purchase an item at a point-of-sale.
- Anonymous payment may also be provided through an entrusted third party, such as profile operator 115 .
- the fourth negotiation layer may involve circumstances in which it is necessary for the user to provide identity authentication and user identification to obtain a service.
- One example would where be the user is accessing his/her banking service. Additionally, some service providers may simply require the full identity of the user in negotiating services.
- User device 110 may perform privacy level determinations and changes at anytime, e.g., prior to, during or after a communication with another party, such as service operator 110 . As discussed above, user device 110 may initiate such determinations and changes upon a user request or automatically.
- user device 110 may also control access and usage of the user's profile information by other parties depending upon the nature of the communications with those parties. For example, in a service environment, user device 110 recognizes one or more service opportunities of service operator 130 , and determines a profile access authority or level to identify subsets or viewpoints of profile information which the service operator may access or obtain. The access level may be determined based on service-related information provided by service operator 130 , such as a service category, service description, requested viewpoint, service operator identifier and so forth, or based on a user's pre-existing relationship with the service operator to provide an agreed upon or predefined subset of profile information.
- service-related information provided by service operator 130 , such as a service category, service description, requested viewpoint, service operator identifier and so forth, or based on a user's pre-existing relationship with the service operator to provide an agreed upon or predefined subset of profile information.
- the profile access control may be distributed between user device 110 (e.g., a mobile wireless device) and profile operator 115 (e.g., a server).
- profile operator 115 maintains the user's profile information.
- User device 110 may determine a profile access level to the user's profile information and transmit the access authority to service operator 130 which, in turn, requests and receives a subset of profile information from profile operator 115 according to the determined access authority.
- Calendar and other basic software with their user-specific data (synchronizable between multiple devices, e.g., download, update, use)
- a first handset e.g., a mobile phone
- the user would be provided server-side functionality and capacity including, for example, calendar, basic software, etc.
- the user may activate these functions through an agreement with a service operator.
- the user can select (to some extent based on the operator) the services and service providers the user wishes to use (e.g., profiling, additional software etc.).
- FIG. 1B is a general overview of an example of a network relationship between user device 110 and service operator 130 in accordance with one advantageous embodiment.
- User device 110 may be a wireless device capable of conducting communications and service negotiations with service operator 130 over the Internet 116 or a personal area network (PAN) 118 .
- PAN personal area network
- Service operator 130 may be a fixed or mobile wireless device or a server including content and application programs 132 for performing service negotiations with the user and providing a variety of services to the user. The manner in which service negotiations is performed with user device 110 is discussed in further detail below with reference to FIGS. 8A through 8D.
- User device 110 may include a privacy management application program 112 for controlling the privacy levels (e.g., Anonymous, Pseudonymous, Anonymous transaction and Authenticated) at which the user conducts service-related communications with the service operator.
- the privacy level may be determined based on a user request or automatically based on the nature of the circumstances surrounding the communications.
- user device 110 may adjust a privacy level, for example, based on the nature of the service negotiations with another party (e.g., service category or context), the level of privacy in one or more prior transactions with the specific service operator, the identity of service operator 130 , user-defined situations, the user's prior behavior or activity (e.g., profile), and so forth.
- a privacy management application program 112 for controlling the privacy levels (e.g., Anonymous, Pseudonymous, Anonymous transaction and Authenticated) at which the user conducts service-related communications with the service operator.
- the privacy level may be determined based on a user request or automatically based on the nature of the circumstances surrounding the communications.
- FIG. 2 illustrates one example of a pervasive computing network system implementing the Bluetooth standard.
- the Bluetooth standard is a short-range wireless communication industry specification that allows portable, personal devices to interact which each other and other stationary devices.
- the Bluetooth standard uses the spread spectrum radio frequency and provides omnidirectional multiple connections without requiring communicating devices to be in line of sight. The maximum range is 10 meters, but it can be extended to 100 meters by increasing the power.
- the device's radio operates on the globally available, unlicensed 2.45 GHz radio band, and supports data speeds of up to 721 Kbps.
- Bluetooth devices Each device has a unique 48-bit address similar to that provided in the IEEE 802 standard. Connections can be point-to-point or multipoint. Bluetooth devices are protected from radio interference by changing their frequencies randomly up to a maximum of 1600 times per second, using a frequency hopping protocol. They also use three different but complimentary error correction schemes. Built-in encryption and verification are provided. Bluetooth devices provide a universal bridge to existing data networks, a peripheral interface, and a mechanism to form small private ad hoc groupings of connected devices away from fixed network infrastructures. Bluetooth radio modules avoid interference from other signals by hopping to a new frequency after transmitting or receiving a packet.
- the Bluetooth specification is a de facto standard containing the information required to ensure that diverse devices supporting the Bluetooth wireless technology can communicate with each other worldwide.
- the document is divided into two parts: Volume 1: Core, and Volume 2: Profiles.
- the Core part specifies components such as the radio, baseband, link manager, service discovery protocol, transport layer, and interoperability with different communication protocols.
- the Profiles part specifies the protocols and procedures required for different types of Bluetooth applications.
- a copy of the Bluetooth Specification can be downloaded from the Internet web site http://www.bluetooth.com/developer/specification/specification.asp . Additional information is provided in the book by Nathan J. Muller entitled “Bluetooth Demystified”, published by McGraw Hill, 2000 (ISBN 007-1363238).
- Fixed position device 200 may be arranged in a store to provide location-based shopping services or other services to the user.
- User device 110 is shown having the form of a hand-held personal digital communicator, with an LCD display and a touch overlay screen to enable inputting commands to the microbrowser 202 by touching the portion of the screen displaying the appropriate input button.
- User device 110 includes a programmed central processor, a memory, at least a few alphanumeric input keys, and an RF wireless transceiver module 212 .
- the memory of the user device 110 stores application programs 206 , protocol driver 208 , transport driver 210 , and a user's database or assets 214 .
- User device 110 receives and sends data over a short radio link with fixed position device 200 , for example.
- Microbrowser 202 displays a graphical user interface (GUI) 204 to enable the user to navigate through the pages of data being displayed and to select options that are presented by the microbrowser 202 .
- GUI graphical user interface
- the Wireless Application Protocol (WAP) standard can be used in the application program layer 206 of user device 110 , to provide functionality for the device's microbrowser 202 .
- User device 110 accesses a small file called a deck which is composed of several smaller pages called cards which are small enough to fit into the display area of the device's microbrowser 202 .
- the small size of the microbrowser 202 and the small file sizes accommodate the low memory constraints of the Bluetooth-enabled user device 110 and the low-bandwidth constraints of a wireless network.
- the cards are written in the Wireless Markup Language (WML) which is specifically devised for small screens and one-hand navigation without a keyboard.
- WML Wireless Markup Language
- the WML language is scaleable from two-line text displays on a small screen microbrowser 202 , up through graphic screens such as are found on personal communicators.
- the cards written in the WML language can include programs written in WMLScript, which is similar to JavaScript, but makes minimal demands on memory and CPU power of the user device 110 because it does not contain many of the unnecessary functions found in other scripting languages.
- User device 110 includes a user database or assets 214 that stores the user's private data.
- data may include, for example, a profile access authority database 378 , captured profile-relating information, privacy level parameters for identifying various situations requiring different privacy levels, and so forth.
- Application programs 206 in user device 110 are described in part below with reference to the flow diagrams of FIGS. 8A through 8D and the program descriptions to be provided below with reference to FIGS. 3A through 3C.
- Protocol driver 208 in user device 110 includes the Bluetooth core protocols of Baseband, Link Manager Protocol (LMP), Logical Link Control and Adaptation Protocol (L 2 CAP), and Service Discovery Protocol (SDP) and the Bluetooth serial cable emulation protocol (RFCOMM).
- the Baseband and Link Control layers enable the physical RF link through RF wireless module 212 , between the Bluetooth devices 110 and 200 forming a piconet RF network, coordinating the frequency-hopping spread spectrum system in which packets are transmitted in defined time slots on defined frequencies.
- a piconet RF network consists of one master Bluetooth device and up to seven active member Bluetooth devices.
- a Bluetooth network of multiple piconets is called a scatternet.
- the Link Manager Protocol (LMP) sets up the links between the Bluetooth devices 110 .
- the Logical Link Control and Adaptation Protocol provides data services to the upper layer protocols permitting them to transmit and receive data packets up to 64 kilobytes in length.
- the Service Discovery Protocol (SDP) enables a Bluetooth device 110 to discover available supporting services to enable it to connect to other Bluetooth device(s) 120 .
- RFCOMM is an RS 232 serial emulation protocol that provides transport capabilities for upper level services that emulate a serial line as the transport mechanism.
- Other Bluetooth standard protocols can be included to support the applications of file transfer, Internet bridge, LAN access, information synchronization, multiple service provider telephony, and wireless headset functions.
- the Bluetooth protocol drivers 208 ′ in device 200 have similar features to those of the protocol driver 208 .
- Transport driver 210 in user device 110 includes the host controller firmware and a standardized interface to the RF wireless module 212 .
- An example standardized interface is the RS 232 serial device interface, enabling the exchange of control and data between the protocol driver 208 and the RF wireless module 212 .
- Other standard interfaces for the Bluetooth transport driver 210 include the Universal Serial Bus (USB) and Universal Asynchronous Receiver-Transmitter (UART) protocols.
- the transport drivers 210 ′ in device(s) 120 have similar features to those of the transport driver 210 .
- a store merchant possesses a Bluetooth-enabled fixed position device 200 which the merchant uses to communicate with the user.
- the merchant's Bluetooth-enabled fixed position device 200 includes application programs 206 ′, protocol driver 208 ′, transport driver 210 ′, and RF wireless module 212 ′.
- Fixed position device(s) 200 and service operator 130 are connected by means of wide area network (WAN) interfaces 216 and 236 , respectively, to a wide area network 220 .
- Profile operator 115 is connected by means of TCP/IP interface 246 to Internet 224 which, in turn, is connected to wide area network (WAN) 220 across a protocol gateway 222 .
- FIG. 3A is an exemplary block diagram of a user device 110 of FIG. 2.
- user device 110 may include a radio transmitter 310 , a user input 315 , a central processor 320 , a display 325 and a memory 330 , which are connected across a bus 305 .
- User device 110 may also include an interface for communicating across a line-based network.
- Memory 330 stores an initial menu application program 332 for providing a menu of options to the user for selection and implementation of other application programs or routines according to the user selection.
- menu application program 332 may initiate a session support application program 334 for supporting a session between the user and one or more other parties.
- Session support application program 334 may include a network connection management routine 342 , service discovery routine 344 , privacy level negotiation routine 346 and a service management routine 354 .
- Network connection management routine 342 is a process by which the user can be connected to Cellular Networks and Personal Area Networks (PAN) independently and by which the Bluetooth master and slave relationship can be determined.
- Service discovery routine 344 is a process which enables the user to activate or deactivate visibility to Bluetooth Access points (such as fixed position wireless devices) or enables the terminal to discover Bluetooth nodes in a PAN.
- Privacy level negotiation routine 346 is a process by which the user or the terminal on behalf of the user can determine which level of privacy should be maintained in an ad-hoc or user-initiated service context. As discussed above, the different levels of privacy may include Anonymous, Pseudonymous, Anonymous transaction and Authenticated.
- Service management routine 354 is a process by which the same service session can be maintained over several different network connections.
- Initial menu application program 332 may also provide access to other menu accessible application programs, such as a calendar 348 , games 350 , device control 352 or other additional applications 353 .
- a user database or assets 378 is also maintained to store the user's private assets as well as other information.
- assets may include, for example, profile preferences, rights wallet, presence information (e.g., context, device, location), and Personal Information Manager (PIM).
- Profile preferences involves a process for saving, storing and retrieving profile and preferences of a certain user, e.g., age, gender, social security number, shoe size, favorite food, loyalty card numbers, credit card numbers, etc.
- Rights wallet involves a process for saving, storing and retrieving rights belonging or given to a certain user, e.g., voting rights, access rights, etc., and the parameters to these, e.g., time, location, context, etc.
- Presence involves a process for saving, storing and retrieving context, device and location data of a given user.
- PIM involves a process for saving, storing and retrieving Personal Information data of a given user, e.g., calendar, e-mail, etc.
- Memory 330 may further include additional application programs to facilitate the management of user privacy in communications with other parties. These programs may include a profile capturing program 370 , a privacy management program 372 , and an interface support program 374 . These programs will be discussed with reference to FIG. 3C which illustrates a high level architecture of components of the network system 100 in which various application or function layers and sub-layers supported by the user device are shown.
- profile capturing application program 370 provides a mechanism for capturing profile related information of the user.
- Profile capturing application program 370 may include various routines, such as device adaptation, clickstream recording, location tracking and context determination.
- Device adaptation is a process by which the content elements adapt to the user interface and presentation available in the terminal. The adaptation takes into account screen resolution, colors, free memory size and bandwidth available.
- Clickstream recording is used for calibrating the middleware layer, i.e., for providing data to a recommendation engine or for optimizing menu structures.
- the end user should at any time be able to opt-out from recording or to review the data recorded from the clickstream.
- Location tracking is used for calibrating the middleware layer, i.e., for providing data to a recommendation engine or for optimizing menu structures.
- the end user should at any time be able to opt-out from tracking or to review location data saved during consumption.
- Context determination is used for calibrating the middleware layer, i.e., for providing data to a recommendation engine or for optimizing menu structures.
- Context determination parameters may be, for instance, time, content available at the given time and environment, altitude, heart beat rate, etc. The end user should at any time be able to opt-out from context determination or to review context data saved during interactive activities.
- content adaptation within profile capturing is the mechanism for determining the mark-up language to be used, preferably, but not limited to, WML or XML.
- profile capturing application program 370 interacts with user 380 to capture profile-related information.
- Privacy management application program 372 provides a security layer to access of a user assets 378
- interface support application program 374 enables user device 110 to interact with a service operator to obtain services provided through the service operator's content and applications 390 .
- the Service operator's content and applications 390 may include advertising platforms, content aggregation, CRM-Call Center Applications, one-to-one marketing, chat rooms, network games, and multimedia messaging.
- Advertising platforms may include Internet and mobile Internet advertising platforms.
- Content aggregation may involve a process of combining content from many sources into one service.
- CRM-Call Center Applications may involve a process for managing short term and context sensitive customer relationship data and retrieving it from CRM applications for calibrating middleware services.
- One-to-one marketing may involve service content profiling mechanisms using privacy levels. Chat rooms provide real-time person to person communication services using privacy levels.
- Network game includes real-time network gaming using privacy levels.
- multimedia messaging involves messaging with multimedia elements using privacy elements.
- Privacy management application program 372 for managing security over the user's assets.
- Application program 372 may include various functions, such as service contract management, Anonymity and Public Key Infrastructure (PKI).
- Service contract management involves a process for determining the wishes of the consumer to lower the privacy levels and reveal certain viewpoints to the consumer assets in a certain service session.
- Anonymity is preferably the default level of privacy in the privacy management.
- the Public Key Infrastructure (PKI) is the method by which security is added to the privacy management.
- Interface support application program 374 provides support for interacting with another party, such as a service operator.
- Interface support application program 374 may include various sub-functions, such as ad interfaces, Ubiquitous Customer Relations Management (UbiCRM) and content interfaces.
- Ad interfaces may include context, privacy, device and location sensitive Advertising platform interface mechanisms.
- CRM may include context, privacy, device and location sensitive CRM interface mechanisms.
- Content interfaces context, privacy, device and location sensitive Content interface mechanisms.
- FIG. 4 shows the functional components of an exemplary service operator 130 arranged as an object model.
- the object model groups the object oriented software programs into components that perform the major functions and applications in service operator 130 .
- the object model for memory 430 of service operator 130 employs a three-tier architecture that includes presentation tier 432 , infrastructure objects partition 440 , and business logic tier 450 .
- the object model further divides business logic tier 450 into two partitions, application objects partition 454 and data objects partition 470 .
- Presentation tier 432 retains the programs that manage the device interfaces to service operator 130 .
- presentation tier 432 includes network interface 434 , and bank interface 436 .
- a suitable implementation of presentation tier 432 may use Java servlets to interact with user device via the hypertext transfer protocol (“HTTP”).
- the Java servlets run within a request/response server that manages the exchange of messages between a user device and service operator 130 .
- a Java servlet is a Java program that runs within a Web server environment.
- a Java servlet takes a request as input, parses the data, performs logic operations, and issues a response back to a user device.
- the Java runtime platform pools the Java servlets to simultaneously service many requests.
- Network interface 434 accepts request messages from a user device and passes the information in the request to visit object 452 for further processing. Visit object 452 passes result of that processing to network interface 434 for transmission back to the user device. Network interface 434 may also use network adapter 410 to exchange data with another user device. Bank interface 436 manages the exchange of messages between a financial institution and visit object 452 in a similar manner to network interface 434 .
- Infrastructure objects partition 440 retains the programs that perform administrative and system functions on behalf of business logic tier 450 .
- Infrastructure objects partition 440 includes operating system 448 , and an object oriented software program component for database server interface 442 , and system administrator interface 446 .
- Business logic tier 450 in FIG. 4 includes multiple instances of visit object 452 .
- a separate instance of visit object 452 exists for each bank interface 436 or network interface 434 session.
- Each visit object 452 is a stateful session bean that includes a persistent storage area from initiation through termination of the session, not just during a single interaction or method call. The persistent storage area retains information associated with the session.
- a message is sent to network interface 434 to invoke a method that creates visit object 452 and stores connection information in visit object state 452 .
- Visit object 452 may, in turn, invoke a method in digital signature verification application 456 to verify the source that generated the message.
- Digital signature verification application 456 extracts the digital signature from the message and uses public key data 472 to decode the signature and verify the identity of the source that generated the message.
- FIG. 4 depicts central processor 420 as controlling digital signature verification application 456 , it is to be understood that the function performed by digital signature verification application 456 can be distributed to a separate system configured similarly to service operator 130 .
- a message is sent to network interface 434 to invoke a method that creates visit object 452 and stores connection information in visit object state 452 .
- Visit object 452 may, in turn, invoke a method in data authentication application 458 to authenticate a user device that generated the message.
- Data authentication application 458 uses MAC data 474 to authenticate the identity of the user device that generated the message.
- FIG. 4 depicts central processor 420 as controlling data authentication application 458 , it is to be understood that the function performed by data authentication application 458 can be distributed to a separate system configured similarly to service operator 130 .
- FIGS. 8A through 8C as well as the discussion above with reference to FIGS. 3B and 3C on the service operator's content and application 390 describe the service-related functions of personal service application 460 .
- FIG. 4 depicts central processor 420 as controlling personal service application 460 , it is to be understood that the function performed by personal service application 460 can be distributed to a separate system configured similarly to service operator 130 .
- Visit object 452 may, in turn, invoke a method in payment method application 462 to compute a payment or fee for services rendered through use of payment data 478 .
- FIG. 4 depicts central processor 420 as controlling payment method application 462 , it is to be understood that the function performed by payment method application 462 can be distributed to a separate system configured similarly to service operator 130 .
- a user device sends a message to service operator 130
- a message is sent to network interface 434 to invoke a method that creates visit object 452 and stores connection information in visit object state 452 .
- Visit object 452 may, in turn, invoke a method in profile distribution application 464 to control distribution/access of a user's profile information to lower level service operators through use of profile data 480 .
- An example of a service operator which would implement profile distribution application is SO 3 +PO 3 of FIG. 6B.
- FIG. 4 depicts central processor 420 as controlling profile distribution application 464 , it is to be understood that the function performed by profile distribution application 464 can be distributed to a separate system configured similarly to service operator 130 .
- FIG. 5 shows the functional components of profile operator 115 arranged as an object model.
- the object model groups the object oriented software programs into components that perform the major functions and applications in profile operator 115 .
- the object model for memory 530 of profile operator 115 employs a three-tier architecture that includes presentation tier 532 , infrastructure objects partition 540 , and business logic tier 550 .
- the object model further divides business logic tier 550 into two partitions, application objects partition 554 and data objects partition 570 .
- Presentation tier 532 retains the programs that manage the device interfaces to profile operator 115 .
- presentation tier 532 includes network interface 534 , and bank interface 536 .
- a suitable implementation of presentation tier 532 may use Java servlets to interact with user device via the hypertext transfer protocol (“HTTP”).
- the Java servlets run within a request/response server that manages the exchange of messages between a user device and profile operator 115 .
- a Java servlet is a Java program that runs within a Web server environment.
- a Java servlet takes a request as input, parses the data, performs logic operations, and issues a response back to a user device.
- the Java runtime platform pools the Java servlets to simultaneously service many requests.
- Network interface 534 accepts request messages from a user device and passes the information in the request to visit object 552 for further processing. Visit object 552 passes result of that processing to network interface 534 for transmission back to the user device. Network interface 534 may also use network adapter 510 to exchange data with another user device. Bank interface 536 manages the exchange of messages between a financial institution and visit object 552 in a similar manner to network interface 534 .
- Infrastructure objects partition 540 retains the programs that perform administrative and system functions on behalf of business logic tier 550 .
- Infrastructure objects partition 540 includes operating system 548 , and an object oriented software program component for database server interface 542 , and system administrator interface 546 .
- Business logic tier 550 in FIG. 5 includes multiple instances of visit object 552 .
- a separate instance of visit object 552 exists for each bank interface 536 or network interface 534 session.
- Each visit object 552 is a stateful session bean that includes a persistent storage area from initiation through termination of the session, not just during a single interaction or method call. The persistent storage area retains information associated with the session.
- a message is sent to network interface 534 to invoke a method that creates visit object 552 and stores connection information in visit object state 552 .
- Visit object 552 may, in turn, invoke a method in digital signature verification application 556 to verify the source that generated the message.
- Digital signature verification application 556 extracts the digital signature from the message and uses public key data 572 to decode the signature and verify the identity of the source that generated the message.
- FIG. 5 depicts central processor 520 as controlling digital signature verification application 556 , it is to be understood that the function performed by digital signature verification application 556 can be distributed to a separate system configured similarly to profile operator 115 .
- a message is sent to network interface 534 to invoke a method that creates visit object 552 and stores connection information in visit object state 552 .
- Visit object 552 may, in turn, invoke a method in data authentication application 558 to authenticate a user device that generated the message.
- Data authentication application 558 uses MAC data 574 to authenticate the identity of the user device that generated the message.
- FIG. 5 depicts central processor 520 as controlling data authentication application 558 , it is to be understood that the function performed by data authentication application 558 can be distributed to a separate system configured similarly to profile operator 115 .
- FIGS. 8A through 8D describes, in greater detail, the process of profile distribution application 560 .
- FIG. 5 depicts central processor 520 as controlling profile distribution application 560 , it is to be understood that the function performed by profile distribution application 560 can be distributed to a separate system configured similarly to profile operator 115 .
- a message is sent to network interface 534 to invoke a method that creates visit object 552 and stores connection information in visit object state 552 .
- Visit object 552 may, in turn, invoke a method in profile billing application 562 to bill another party for services rendered (e.g., charge service operator for profile information) through use of billing data 578 .
- FIG. 5 depicts central processor 520 as controlling profile billing application 562 , it is to be understood that the function performed by profile billing application 562 can be distributed to a separate system configured similarly to profile operator 115 .
- a message is sent to network interface 534 to invoke a method that creates visit object 552 and stores connection information in visit object state 552 .
- Visit object 552 may, in turn, invoke a method in anonymous payment application 564 to provide trusted anonymous third payment services for a user through use of payment data 580 .
- FIG. 5 depicts central processor 520 as controlling anonymous payment application 564 it is to be understood that the function performed by anonymous payment application 564 can be distributed to a separate system configured similarly to profile operator 115 .
- service operator 130 and/or profile operator 115 may alternatively, or in addition to, the communication software discussed above, be equipped with a WML Script and WML functionality for communicating with the various system components (e.g., the user device, service operator, and/or profile operator).
- FIG. 6A is an overview of one example of a service operator arrangement in which the user actions, via wireless portable device 110 , are transmitted to service operators using a profile operator.
- each profile operator e.g., PO 1 and PO 2
- viewpoint technology may be employed to enable different parts of the user profile to be accessed and used by different service operators. Viewpoints allow the service operator to access subsets of profile information for different purposes in different contexts.
- a user or profile operator may wish to mask the user's identity from the service operators.
- Profile operators can be configured to perform such identity masking in at least two different levels.
- the one level of masking is pseudonymity which allows service operators to establish a relationship with the users while offering an opportunity to actively conceal or reveal elements of user identity.
- Another level of masking is complete anonymity which does not allow the service operators to identify the users.
- the profile operators can handle the billing of services.
- the service operators may be required to provide the profile operator with profile update information based on the user's service usage behavior. If the users are using the services anonymously, the service operators cannot build their own user profiles and the update information is the only way to develop the quality of profiles. Since the update information is valuable for the profile operators the service operators can be compensated by decreasing the price of the profile information in exchange for updates.
- FIG. 6B is an overview of another example in which service operators may be hierarchically arranged to provide additional privacy levels or filtering in accordance with a further embodiment.
- service operators can be arranged hierarchically (SO 4 -SO 7 ) such that higher level operators serve lower level operators.
- the service operator SO 3 serves the lower level service operators SO 4 through SO 7 .
- the service operator SO 3 may also incorporate a profile operator PO 3 or its functions to provide profiling services for lower level service operators SO 4 through SO 7 .
- the level of identification information revealed to the lower level service operator may vary as well as the level of detail in the update information provided to the upper level operator.
- the service operator SO 3 may be privy to a higher profile access level than the lower level service operators SO 4 through SO 7 since the service operator SO 3 may further filter a user's profile information provided to these lower level service operators.
- the service operator SO 3 may receive user information from the lower level service operators SO 4 through SO 7 to update the user's profile.
- the operator arrangements as shown in FIGS. 6A and 6B provide some potential advantages and disadvantages to the parties involved.
- the advantages of these operator arrangements may, for example, include:
- SO 3 /PO 3 can analyze all visitors to a collection of SO 8 (SO 6 -SO 7 ), which enables personalization at least across services with more complete data, and
- a profile operator does not see all the users accessing a certain service operator.
- FIG. 7A illustrates an exemplary profile database 576 maintained or employed by profile operator 115 .
- Profile database may include a service contract field 705 , a category field 710 , a viewpoint identifier (ID) field 715 and a profile items field 720 . While the various fields and information are self-explanatory, a brief discussion of the database is provided below.
- Service contract field 705 maintains an identity of those parties with pre-existing agreements with the user. These parties may have agreed upon the user profile subset to be provided to them.
- Category field 710 maintains information on the various categories of service contexts or categories a user may encounter. For example, a category may include shopping, meeting, emergency, doctor visit and music bar.
- Viewpoint ID 715 maintains a viewpoint identifier for specifying a particular subset or viewpoint of a user's profile information.
- Profile items 720 define various defined subsets or viewpoints of the user's profile information. These profile items are addressable by profile operator 115 according to a service contract, category or viewpoint ID. For example, in a shopping example, user device 110 may forward the category information (e.g., shopping) or a viewpoint ID (e.g., 1111 ) to service operator 130 which is then provided as part of a request to profile operator 115 for the user's profile information. Based on either the category or viewpoint identifier, profile operator 115 would provide the appropriate subset of profile information, e.g., the user's shopping list, the user's likes and/or dislikes and the user's usual buying habits.
- category information e.g., shopping
- a viewpoint ID e.g., 1111
- FIG. 7B illustrates an exemplary profile access authority database 360 maintained or employed by user device 110 to determine a profile access authority or level.
- Database 360 may include a service contract field 725 , a category field 735 and a viewpoint ID field 735 , which maintain similar information as in fields 705 , 170 and 715 , respectively, as discussed above in FIG. 7A.
- the database 360 is used to determine a viewpoint or subset of profile information to be available to service operator 130 based whether the service operator has a contract with the user or based on the service category.
- FIGS. 8A through 8D illustrate an exemplary process 800 by which a user controls a privacy level of communications with a service operator and controls access and usage of the user's profile information by the service operator via the user's Bluetooth-enabled portable device.
- the process 800 will be discussed with reference to FIGS. 1 and 2.
- user device 110 is a Bluetooth-enabled portable wireless device and fixed position Bluetooth wireless device corresponds, e.g., to device 200 of FIG. 2.
- the fixed position Bluetooth wireless device will be referred hereafter as fixed position device 200 .
- Fixed position device 200 enables location-based services as well as other services to be provided to the user. Communications between user device 110 , service operator 130 and profile operator 115 may be facilitated through fixed position device 200 or other communications means, such as by cellular.
- the process 800 commences at step 802 where user device 110 initiates service discovery automatically or upon a user request.
- user device 110 sends periodic short range identity signal.
- fixed position device 200 detects a user device 110 's presence and, at step 810 , sends an indication of service opportunit(ies) available from service operator 130 .
- User device 110 discovers these opportunities at step 808 , and sends a request for service-related information at step 812 .
- user device 110 may or may not send an identifier depending upon the privacy level determined by the user device. Where user device 110 is simply discovering available service opportunities, the user device would unlikely send any identifier. In other words, the request for service information would be an anonymous request.
- Fixed position device 200 receives the request at step 814 and, at step 820 , sends the service-related information to user device 110 .
- the service-related information may include service category, service description, requested viewpoint or any information which enables user device 110 to make a determination as to a privacy level and/or a profile access level.
- fixed position device 200 may pass the request to service operator 816 so that the service-related information is provided by service operator 130 through steps 816 and 818 .
- user device 110 receives the service-related information. The information may be displayed to the user.
- user device 110 determines whether to proceed with the service negotiation, for example, based upon a user selection. If user device 110 determines not to proceed, then the negotiations are terminated at step 830 . Otherwise, the process 800 proceeds to step 828 in which user device 110 initiates a new session with profile operator 115 .
- user device 110 requests session-based User ID from profile operator 115 .
- user device 110 may send the request directly to profile operator, such as by cellular, or may send the request via fixed position device 200 which passes the request to the profile operator at step 834 .
- Profile operator 115 receives the request for a User ID and generates a session-based User ID.
- profile server 115 sends the User ID to user device 110 .
- profile operator 115 may send the User ID directly to user device 110 , such as by cellular, or may send the request via fixed position device 200 which passes the request to the user device at step 841 .
- user device 110 receives the user ID at step 814 .
- the user ID enables user device to conduct pseudonymous communications with service operator 130 .
- user device 110 may employ the user ID for more than one session, a new user ID is preferably generated for each session to prevent a service operator from collecting any profile information on the user.
- user device initiates a service session profile capturing operation which involves tracking the behavior and/or activities of the user on user device 110 . This may involve, for example, clickstream recording, device adaptation tracking, location tracking and context tracking.
- the profile information of the user may be updated with the tracked information.
- step 846 user device 110 determines whether the user has a pre-existing relationship with service operator 130 , such as a service contract with the service operator. If a service contract exists, user device 110 sends a profile access level or authority, which reflects a previously agreed upon profile access level or authority, (e.g., a predefined viewpoint identifier) to service operator 130 at step 852 via fixed position device 110 at step 854 . Along with the profile access authority, user device 110 may or may not send an identifier depending on the privacy level determined by the user device. In such as situation, user device 110 may send the session-based user ID or, alternatively, an authenticated ID.
- service operator 130 such as a service contract with the service operator. If a service contract exists, user device 110 sends a profile access level or authority, which reflects a previously agreed upon profile access level or authority, (e.g., a predefined viewpoint identifier) to service operator 130 at step 852 via fixed position device 110 at step 854 .
- profile access level or authority reflects
- service operator 130 receives the profile access level or authority and some user identifier (if transmitted), and requests the user profile from profile operator 115 .
- profile operator 115 receives the request, and retrieves a subset of the user's profile information according to the authorized profile access level. Thereafter, profile operator 115 sends the user profile to service operator 130 at step 860 , and may charge or bill the service operator a fee for the profile information at step 874 .
- service operator 130 receives the subset of the user's profile information, and provides personalized service(s) to the user according to the received subset of the profile information.
- service operator 130 may send user information relating to the session, e.g., user activity or behavior, to profile operator 115 automatically or upon request by the profile operator.
- Profile operator 115 may then update the user's profile information with the user information provided by the service operator 130 , and may also compensate the service operator for such information.
- the compensation may take the form of a discount to the fee charged by profile operator 115 for providing profile information to service operator 130 .
- the discount may be increased accordingly based upon the amount of updated information or the number of times updated information is provided by service operator 130 .
- user device 110 receives the personalized service(s), via fixed position device 200 .
- user device 110 terminates the session.
- user device 110 may send tracked user information captured by the session profile tracking operation initiated at step 844 to profile operator 115 .
- profile operator 115 updates the user's profile accordingly based on the received information.
- step 880 the process 800 proceeds to step 880 to continue determine the privacy level if no pre-existing relationship exists between service operator 130 and the user.
- user device 110 determines a profile access level or authority to the user's profile information based on a service category or content or any information provided by service operator 130 , such as a requested viewpoint, etc.
- user device 110 sends the determined profile access level or authority via fixed position device 200 (step 884 ).
- user device 110 may or may not also send an identifier depending upon the privacy level determined by the user device.
- service operator 130 receives the user ID and profile access level, and requests the appropriate user profile from profile operator 115 .
- profile operator 115 receives the request, and retrieves a subset of the user's profile information according to the authorized profile access level. Thereafter, profile operator 115 sends the user profile to service operator 130 at step 887 , and may charge or bill the service operator a fee for the profile information at step 894 .
- service operator 130 receives the subset of the user's profile information, and provides personalized service(s) to the user according to the received subset of profile information.
- service operator 130 may send user information relating to the session, e.g., user activity or behavior, to profile operator 115 automatically or upon a request by the profile operator.
- Profile operator 115 may then update the user's profile information with the user information provided by the service operator 130 , and may also compensate the service operator for such information. As discussed above, the compensation may take the form of a discount to the fee charged by profile operator 115 for providing profile information to service operator 130 .
- user device 110 receives the personalized service(s), via fixed position device 200 .
- user device 110 terminates the session.
- user device 110 may send tracked user information captured by the session profile tracking operation initiated at step 844 .
- profile operator 115 updates the user's profile accordingly based on the received information.
- process 800 shows fixed position device 200 as facilitating the provision of services between service operator 130 and user device 110 , this device may be considered a component of service operator 130 where it performs service functions for the service operator.
- FIGS. 8A through 8D provide one illustrative example of the privacy and profile access features in a specific network arrangement embodiment employing Bluetooth technology. It is apparent that these operations may be implemented between the various parties, e.g., a user device, a profile operator and a service operator, over any communication medium employing different network environments and/or different wireless technologies.
- the fixed position device may be configured as a stand-alone fixed or mobile device (e.g., another person's Bluetooth-enabled device) capable of performing all the operations performed by service operator 130 as discussed above in regard to FIGS. 8A through 8D.
- the stand-alone mobile device may, for example, be service operator 140 as shown in FIGS. 1A and 1B in which user device 110 communicates with service operator 140 over a personal area network (PAN).
- PAN personal area network
- user device 110 may conduct communications with service operator 130 and profile operator 115 over a general packet radio system (GPRS) or general system for mobile communications (GSM).
- GPRS general packet radio system
- GSM general system for mobile communications
- user device 110 may automatically or upon a user request send a request for service-related information (e.g., service category, service description, requested viewpoint, etc.) to service operator 130 .
- service-related information e.g., service category, service description, requested viewpoint, etc.
- system network 100 in different service environments will be described below. These examples include a shopping scenario, a meeting scenario, a medical emergency scenario, a health care scenario and a music bar scenario. As discussed above, the privacy level and profile access level provided by the user may vary depending on the nature of the services.
- a user operating a Bluetooth-enable user device 110 is shopping at a location (e.g., store, mall, etc.) having one or more fixed Bluetooth-enabled devices arranged at various locations within and/or in the vicinity of the shopping location.
- the user may be provided services, such as information on sales or discounts on specific items, location of specific stores in the user's vicinity, advertising, and so forth based on the subset of the user's profile received from the profile server.
- the services may involve a transaction to purchase particular items. For transactions requiring payment by the user, the payment may be performed anonymously through a trusted third party, such as the user's profile operator.
- a user operating a Bluetooth-enable user device 110 attends a meeting at a location having one or more fixed Bluetooth-enabled devices arranged at various locations within and/or in the vicinity of the meeting location.
- the user may be provided services, such as document and file delivery, information on other people attending the meeting and whether every person has arrived, and so forth.
- the services may also include voting at the meeting.
- a user operating a Bluetooth-enabled user device 110 attends a meeting in which one or more people also have a Bluetooth-enabled device.
- user device 110 establishes a communication link with the other person's device (or vice-versa), e.g., service operator, to form a personal area network (PAN).
- the services may include access to the other person's assets, such as personal information, software including games, etc., documents, and so forth. Additionally, the services may involve scheduling a further appointment with the other person, and so forth.
- a user operating a portable user device 110 is faced with a medical emergency.
- the user can obtain services, such as medical consultation, directions to the closest hospital, calling for an ambulance, contacting the user's doctor and so forth.
- a user operating a Bluetooth-enable user device 110 visits the office of his/her doctor.
- the doctor's office has one or more fixed Bluetooth-enabled devices arranged at various locations within and/or outside the office.
- the user may be provided services, such as medical consultation, information relating to the doctor or doctor's office, information relating to whether the doctor is on schedule with his/her appointments, information relating to new medical treatments, advertising for drugs or new medical procedures, and so forth.
- the services may also include transaction-related services, such as scheduling a follow-up doctor's visit, obtaining a drug prescription and so forth.
- a user operating a Bluetooth-enable user device 110 enters a music bar having one or more fixed Bluetooth-enabled devices arranged at various locations within the bar.
- the user may be provided services, such as information services which may include advertising, general information about the music bar (e.g., background information, bar layout, etc.), information on other people at the music bar, information on music being played, information on the identities of music performers as well as the music currently playing, played or to be played at the music bar, a schedule of performances, general statistical information as to the people at the bar (e.g., 15 single females, 13 single males, etc.), and so forth.
- information services which may include advertising, general information about the music bar (e.g., background information, bar layout, etc.), information on other people at the music bar, information on music being played, information on the identities of music performers as well as the music currently playing, played or to be played at the music bar, a schedule of performances, general statistical information as to the people at the bar (e.g., 15 single females,
- Additional services may also include transaction-related services, such as music downloads, purchasing tickets to music performances, purchasing food and beverages, and so forth. Transactions requiring payment by the user may be conducted through anonymous payment with the assistance of a trusted third party or profile operator 115 acting as a trusted third party.
- the services capable of being provided by the service operator may be related or unrelated to the music bar environment.
- a user operating a Bluetooth-enabled user device 110 enters a music bar in which one or more people also have a Bluetooth-enabled device.
- user device 110 establishes a communication link with the other person's device (or vice-versa), e.g., service operator, to form a personal area network (PAN).
- the services may include access to the other person's assets, such as personal information, software including games, etc., documents, and so forth. Additionally, the services may involve playing a game with the other person over the personal area network, setting up a date with the other person and so forth.
- the service operator may provide the services to the user over any communication network arrangement, such as a personal area network (PAN), the Internet, wireless communication network or a combination thereof.
- PAN personal area network
- the Internet such as a Wi-Fi network
- wireless communication network such as a Wi-Fi network
Abstract
A system and method manages user privacy in a network environment through a distributed user system including a user device and profile operator. The management of user privacy involves recognizing one or more service opportunities of a service operator on a user device operated by a user, determining a privacy level at which communications is conducted with a service operator relating to the one or more service opportunities on the user device, determining a profile access level on the user device, transmitting the profile access level to the service operator, and enabling the service operator to obtain a subset of profile information of the user according to the profile access level.
Description
- 1. Technical Field
- The present invention is related to a method and system for managing a privacy level at which a user communicates with other parties and managing access and usage of the user's profile information by other parties.
- 2. Art Background
- The rapid advancements in mobile technology as well as other communication technologies have lead to an information age in which consumers are increasing relying on electronic services accessible through a portable wireless devices. However, at the same time, consumers are becoming increasingly concerned over privacy issues and the dissemination of their personal information.
- A method of managing user privacy in a network environment is disclosed. The method involves recognizing one or more service opportunities of a service operator by a user operating a user device. A privacy level, at which communications is conducted with a service operator, is then determined and communications with the service operator are conducted at the privacy level. Optionally, the discovery of the one or more service opportunities can be recognized automatically.
- A further option anonymously obtains information relating to the one or more service opportunities. The information relating to the one or more service opportunities obtained in this manner can include a service category, a service description or a requested viewpoint. The service provider can be allowed to obtain access to a subset of profile information of the user according to the service category. In this manner, the service provider can provide personalized service to the user according to the subset of profile information. Alternatively, the service provider can be allowed to obtain access to a subset of profile information of the user according to the requested viewpoint. This option allows the service provider to provide personalized service to the user according to the subset of profile information.
- The present method of managing user privacy in a network environment can include determined privacy levels including Anonymous, Pseudonymous, Anonymous transaction and Authenticated. Further, the privacy level is determined based on (1) the nature of the service negotiations with the service operator, (2) a level of privacy in one or more prior transactions with the specific service operator, (3) the identity of the service operator, based on user-defined parameters, or (4) the user's prior behavior or activity.
- The method can also include obtaining a user identifier to conduct pseudonymous communications with the service operator relating to the one or more service opportunities. The method can also include allowing the service provider to obtain access to a predefined subset of profile information. The service provider can be charged a fee for obtaining the subset of profile information and the subset of profile information can be obtained from a location remote from the user device. If the subset of information is obtained remotely, the method can include allowing the service provider to determine a profile access level and can include transmitting the profile access level to the service operator. In this scenario, the service operator can obtain a subset of profile information of the user from a profile operator according to the profile access level. The profile access level can be determined from a service category of the one or more service opportunities or based upon a prior arrangement between the service operator and the user.
- When the service provider obtains access to a subset of profile information, the method can further include updating the profile information of the user and can perform such an update on user information provided by the service operator. The user information would be derived from the service operator's interaction with the user during the service session. Optionally, the service operator can be compensated for providing such user information.
- The method can further include tracking user activity on the user device and updating the profile information of the user based on the tracked user activity.
- The method can further include the service provider dynamically changing the service opportunities recognized by the user, for instance, in accordance with the user's profile information.
- The method can allow the user device and the service operator to communicate across a variety of networks, such as a wide are network (WAN) or personal area network (PAN). Further, the user device can be a mobile wireless device, service can be received from the service operator, and payment for the service obtained by the user can be conducted anonymously.
- A method of managing user privacy in a network environment through a distributed user system including a user device and profile operator is also disclosed that recognizes one or more service opportunities of a service operator on a user device operated by a user, determines a privacy level at which communications is conducted with a service operator relating to the one or more service opportunities, determines a profile access level, transmits the profile access level to the service operator, and enables the service operator to obtain a subset of profile information of the user according to the profile access level.
- FIG. 1A is an overview of a network system for enabling a user of a communication device to control a privacy level of communications with other parties and to control access and usage of the user's profile information by other parties in accordance with an advantageous embodiment;
- FIG. 1B is a general overview of an example of different network arrangements between a user device and a service operator in the network system of FIG. 1A;
- FIG. 2 is a block diagram of one example of the network system of FIG. 1A in which a user employs a Bluetooth-enabled mobile device to conduct service-related communications with a service operator through a fixed position Bluetooth-enabled wireless device;
- FIG. 3A is an exemplary block diagram of the wireless user device of FIG. 2;
- FIGS. 3B and 3C illustrate an exemplary high level architecture of components of the network system of FIG. 1A in which various application or function layers and sub-layers supported by the user device are shown;
- FIG. 4 is an exemplary block diagram of a service operator;
- FIG. 5 is an exemplary block diagram of a profile operator;
- FIG. 6A is an overview of one example of an operator arrangement;
- FIG. 6B is an overview of another example of an operator arrangement in which service operators may be hierarchically arranged to provide additional profile access levels or profile filtering;
- FIG. 7A is an example of information maintained in a profile database by a profile operator;
- FIG. 7B is an example of information maintained in a profile access authority database of a user device; and
- FIGS. 8A through 8D illustrate an exemplary process by which a user device controls a privacy level of communications with a service operator and controls access and usage of the user's profile information by the service operator in accordance with an advantageous embodiment.
- FIGS. 1A and 1B show an overview of a
network system 100 for enabling a user of a communication device to control a privacy level of the user's communications with other parties and to control access and usage of the user's profile information by other parties in accordance with an advantageous embodiment of the present invention. -
Network system 100 includes auser device 110 operated by a user, profile operator(s) 115 for maintaining the user's profile information, and a service operator(s) 130 for providing services to the user.User device 110,profile operator 115 andservice operator 130 communicate with each other across network(s) 140. Aradio transceiver 120 provides an access point to enable the user to conduct communications across network(s) 140.Network 140 may be a local area network(s) (LAN), wide area network(s) (WAN), the Internet, wireless network(s) or a combination thereof.Radio transceiver 120 may be, for example, a radio tower, a general packet radio service (GPRS) access point, a general system for mobile communications (GSM) access point or a fixed position wireless device implementing the Bluetooth™ standard. (“Bluetooth” is a trademark owned by Telefonaktielbolaget L M Ericsson, Sweden.). A detailed discussion of Bluetooth technology will be discussed below with reference to FIG. 2. -
User device 110 may be any computerized system with communication means by which to conduct wire and wireless communications with other parties, such asservice operator 130 andprofile operator 110. In various embodiments,user device 110 may take the form of computer system or a mobile wireless device configured to perform the methods and processes discussed herein. For example,user device 110 may be a cellular phone, personal digital assistant (PDA), portable computer, handheld device, etc. -
Service operator 130 may be any computerized system with communication means by which to conduct wire and wireless communications with other parties, such asuser device 110 andprofile operator 115. In various embodiments,service operator 130 may take the form of a server or computer system or a fixed or mobile wireless device configured to perform the methods and processes discussed herein. For example,service operator 130 may be a server of a retailer or a cellular phone, personal digital assistant (PDA), portable computer, handheld device, etc. -
Profile operator 130 may be any computerized system with communication means by which to conduct wire and wireless communications with other parties, such asuser device 110 andservice operator 130. In various embodiments,profile operator 115 may take the form either as a server or computer system or a fixed or mobile wireless device configured to perform the methods and processes discussed herein. - As shown in FIG. 1A,
user device 110 may conduct communications withservice operator 130 orprofile operator 115 using Bluetooth technology or general packet radio service (GPRS) or general system for mobile communications (GSM), or may conduct communications with amobile service operator 140 using Bluetooth technology or the like to establish a personal area network (PAN). - In accordance with one embodiment,
user device 110 is configured to control a privacy level of communications with another party, such as a service operator. The user oruser device 110 on behalf of the user may determine which level of privacy should be maintained in an ad hoc or user initiated communications environment. In such environment,user device 110 may conduct the communications with another party at varied privacy levels, such as absolute anonymity (e.g., without any provision of a user identifier to the communicating party), with pseudonymity (e.g., with the use of a pseudonym) or with authenticated user identification.User device 110 may be set to operate at a default privacy level of anonymous. - For example, in a service environment,
user device 110 may control the privacy level of communications with another party, such asservice operator 130. The privacy level may be determined based on a user request or automatically based on the nature of the circumstances surrounding the communications. In the automatic implementation,user device 110 may adjust a privacy level, for example, based on the nature of the service negotiations with another party (e.g., service category or context), the level of privacy in one or more prior transactions with the specific service operator, the identity ofservice operator 130, user-defined situations, the user's prior behavior or activity (e.g., profile), and so forth. For the purposes of illustration, the service negotiations may be divided into four layers, i.e., layers one, two, three and four. - The first negotiation layer may involve an initial service inquiry or discovery, which does not require any identification of a user, e.g., a user ID. This may simply involve
user device 110 scanning the environment in a very light and privacy protected way, and obtaining a response fromservice operator 130. The response may include a service name or identifier, type and definition. Such a negotiation generally occurs automatically without user interactions. - The second negotiation layer may involve, for example, the provision of user profile information to
service operator 130 for service personalization. In this situation,user device 110 may provideservice operator 130 with a pseudonym identifier. This identifier may be generated on a per session basis when conducting communications with service operator 130 (i.e., a session ID). In this way, service operators are prevented from collecting profile information individually for each customer. - The third negotiation layer may involve, for example, anonymous service delivery which may also include anonymous payment possibilities. In certain circumstances, service may still be rendered by
service operator 130 without any need to disclose the identity of the user. For example, a user may conduct an anonymous service transaction to purchase an item at a point-of-sale. Anonymous payment may also be provided through an entrusted third party, such asprofile operator 115. - The fourth negotiation layer may involve circumstances in which it is necessary for the user to provide identity authentication and user identification to obtain a service. One example would where be the user is accessing his/her banking service. Additionally, some service providers may simply require the full identity of the user in negotiating services.
-
User device 110 may perform privacy level determinations and changes at anytime, e.g., prior to, during or after a communication with another party, such asservice operator 110. As discussed above,user device 110 may initiate such determinations and changes upon a user request or automatically. - In accordance with another advantageous embodiment,
user device 110 may also control access and usage of the user's profile information by other parties depending upon the nature of the communications with those parties. For example, in a service environment,user device 110 recognizes one or more service opportunities ofservice operator 130, and determines a profile access authority or level to identify subsets or viewpoints of profile information which the service operator may access or obtain. The access level may be determined based on service-related information provided byservice operator 130, such as a service category, service description, requested viewpoint, service operator identifier and so forth, or based on a user's pre-existing relationship with the service operator to provide an agreed upon or predefined subset of profile information. - In a further embodiment, the profile access control may be distributed between user device110 (e.g., a mobile wireless device) and profile operator 115 (e.g., a server). In this case,
profile operator 115 maintains the user's profile information.User device 110 may determine a profile access level to the user's profile information and transmit the access authority toservice operator 130 which, in turn, requests and receives a subset of profile information fromprofile operator 115 according to the determined access authority. - In addition to distributing the functionality and capacity burdens associated with controlling access to a user's profile information, other functions and capacity burdens may be also be distributed to decrease the work load on the user device while providing additional functionality through the use of a partner computing system or server, such as
profile server 115. Such an arrangement may be generally referred to as the “hybrid-terminal model”. - The idea is that a future handset is closer to a“dummy” X terminal than a “smart device” in the sense that the computational power and“intelligence” resides in the network, i.e., at a network-based server. This means that the majority of the storage capacity, as well as the computational capacity, would be stored in the network.
- At the network-based server, the following examples of functions and features may be provided:
- User profile and preferences, such as described above in connection with a Profile Operator
- Calendar and other basic software with their user-specific data (synchronizable between multiple devices, e.g., download, update, use)
- MIDI and other ringing tone library
- Video and image library
- Software library
- At the handset, the following examples of functions and features may be provided:
- Synchronizable copies of changing/updating information (calendar etc.)
- Desired parts of ringing tone, etc., libraries as local copies, others downloadable
- Required parts of the user profile or references/access rights information for different services
- All the above would provide clear benefits for both the user, the device manufacturer and the service operator. For the user, it would mean that he/she would have access to the same information with all his/her devices, and he/she could benefit from the same personalization features. Also, with all of the new capacity and features, the device would still remain very small. For the device manufacturer, the hybrid terminal would offer possibilities to increase the terminal functionality without having to overcome the challenges of optimizing code for small footprint software, tacking issues such as memory requirements and device size, computational power, etc. Server-side part of the hybrid terminal would also probably lower the threshold of buying a new design device (or several devices), if maintaining and synchronizing the data does not prove to be too problematic. For service providers and other companies this would mean great possibilities to offer server-side software and, e.g., to act as trusted third-parties to maintain the personal server-side information (profiles, visibility rules, etc.) for each user.
- In practice, when the user purchases a first handset (e.g., a mobile phone), the user would be provided server-side functionality and capacity including, for example, calendar, basic software, etc. The user may activate these functions through an agreement with a service operator. After activating the hybrid terminal, the user can select (to some extent based on the operator) the services and service providers the user wishes to use (e.g., profiling, additional software etc.).
- Additional embodiments will be discussed below.
- FIG. 1B is a general overview of an example of a network relationship between
user device 110 andservice operator 130 in accordance with one advantageous embodiment.User device 110 may be a wireless device capable of conducting communications and service negotiations withservice operator 130 over theInternet 116 or a personal area network (PAN) 118. -
Service operator 130 may be a fixed or mobile wireless device or a server including content andapplication programs 132 for performing service negotiations with the user and providing a variety of services to the user. The manner in which service negotiations is performed withuser device 110 is discussed in further detail below with reference to FIGS. 8A through 8D. -
User device 110 may include a privacymanagement application program 112 for controlling the privacy levels (e.g., Anonymous, Pseudonymous, Anonymous transaction and Authenticated) at which the user conducts service-related communications with the service operator. As discussed above, the privacy level may be determined based on a user request or automatically based on the nature of the circumstances surrounding the communications. In the automatic implementation,user device 110 may adjust a privacy level, for example, based on the nature of the service negotiations with another party (e.g., service category or context), the level of privacy in one or more prior transactions with the specific service operator, the identity ofservice operator 130, user-defined situations, the user's prior behavior or activity (e.g., profile), and so forth. As one example, in a medical emergency, communications with the user's doctor would most likely be conducted on an authenticated basis. - FIG. 2 illustrates one example of a pervasive computing network system implementing the Bluetooth standard. The Bluetooth standard is a short-range wireless communication industry specification that allows portable, personal devices to interact which each other and other stationary devices. The Bluetooth standard uses the spread spectrum radio frequency and provides omnidirectional multiple connections without requiring communicating devices to be in line of sight. The maximum range is 10 meters, but it can be extended to 100 meters by increasing the power. When one Bluetooth device comes within range of another, they automatically exchange address and capability details. They can then establish a 1-megabit/second link with security and error correction. The device's radio operates on the globally available, unlicensed 2.45 GHz radio band, and supports data speeds of up to 721 Kbps. Each device has a unique 48-bit address similar to that provided in the
IEEE 802 standard. Connections can be point-to-point or multipoint. Bluetooth devices are protected from radio interference by changing their frequencies randomly up to a maximum of 1600 times per second, using a frequency hopping protocol. They also use three different but complimentary error correction schemes. Built-in encryption and verification are provided. Bluetooth devices provide a universal bridge to existing data networks, a peripheral interface, and a mechanism to form small private ad hoc groupings of connected devices away from fixed network infrastructures. Bluetooth radio modules avoid interference from other signals by hopping to a new frequency after transmitting or receiving a packet. - The Bluetooth specification is a de facto standard containing the information required to ensure that diverse devices supporting the Bluetooth wireless technology can communicate with each other worldwide. The document is divided into two parts: Volume 1: Core, and Volume 2: Profiles. The Core part specifies components such as the radio, baseband, link manager, service discovery protocol, transport layer, and interoperability with different communication protocols. The Profiles part specifies the protocols and procedures required for different types of Bluetooth applications. A copy of the Bluetooth Specification can be downloaded from the Internet web site http://www.bluetooth.com/developer/specification/specification.asp . Additional information is provided in the book by Nathan J. Muller entitled “Bluetooth Demystified”, published by McGraw Hill, 2000 (ISBN 007-1363238).
- In the network diagram of FIG. 2, an exemplary relationship is shown between a Bluetooth-enabled
user device 110, a service provider's Bluetooth-enabled fixed position wireless device(s) 200 (hereinafter “fixedposition device 200”) andservice operator 130, andprofile operator 115.Fixed position device 200, for example, may be arranged in a store to provide location-based shopping services or other services to the user. -
User device 110 is shown having the form of a hand-held personal digital communicator, with an LCD display and a touch overlay screen to enable inputting commands to themicrobrowser 202 by touching the portion of the screen displaying the appropriate input button.User device 110 includes a programmed central processor, a memory, at least a few alphanumeric input keys, and an RFwireless transceiver module 212. The memory of theuser device 110stores application programs 206,protocol driver 208,transport driver 210, and a user's database or assets 214. -
User device 110 receives and sends data over a short radio link with fixedposition device 200, for example.Microbrowser 202 displays a graphical user interface (GUI) 204 to enable the user to navigate through the pages of data being displayed and to select options that are presented by themicrobrowser 202. - The Wireless Application Protocol (WAP) standard can be used in the
application program layer 206 ofuser device 110, to provide functionality for the device'smicrobrowser 202.User device 110 accesses a small file called a deck which is composed of several smaller pages called cards which are small enough to fit into the display area of the device'smicrobrowser 202. The small size of themicrobrowser 202 and the small file sizes accommodate the low memory constraints of the Bluetooth-enableduser device 110 and the low-bandwidth constraints of a wireless network. The cards are written in the Wireless Markup Language (WML) which is specifically devised for small screens and one-hand navigation without a keyboard. The WML language is scaleable from two-line text displays on asmall screen microbrowser 202, up through graphic screens such as are found on personal communicators. The cards written in the WML language can include programs written in WMLScript, which is similar to JavaScript, but makes minimal demands on memory and CPU power of theuser device 110 because it does not contain many of the unnecessary functions found in other scripting languages. -
User device 110 includes a user database or assets 214 that stores the user's private data. Such data may include, for example, a profileaccess authority database 378, captured profile-relating information, privacy level parameters for identifying various situations requiring different privacy levels, and so forth. -
Application programs 206 inuser device 110 are described in part below with reference to the flow diagrams of FIGS. 8A through 8D and the program descriptions to be provided below with reference to FIGS. 3A through 3C. -
Protocol driver 208 inuser device 110 includes the Bluetooth core protocols of Baseband, Link Manager Protocol (LMP), Logical Link Control and Adaptation Protocol (L2CAP), and Service Discovery Protocol (SDP) and the Bluetooth serial cable emulation protocol (RFCOMM). The Baseband and Link Control layers enable the physical RF link throughRF wireless module 212, between theBluetooth devices Bluetooth devices 110. The Logical Link Control and Adaptation Protocol (L2CAP) provides data services to the upper layer protocols permitting them to transmit and receive data packets up to 64 kilobytes in length. The Service Discovery Protocol (SDP) enables aBluetooth device 110 to discover available supporting services to enable it to connect to other Bluetooth device(s) 120. RFCOMM is anRS 232 serial emulation protocol that provides transport capabilities for upper level services that emulate a serial line as the transport mechanism. Other Bluetooth standard protocols can be included to support the applications of file transfer, Internet bridge, LAN access, information synchronization, multiple service provider telephony, and wireless headset functions. TheBluetooth protocol drivers 208′ indevice 200 have similar features to those of theprotocol driver 208. -
Transport driver 210 inuser device 110 includes the host controller firmware and a standardized interface to theRF wireless module 212. An example standardized interface is the RS232 serial device interface, enabling the exchange of control and data between theprotocol driver 208 and theRF wireless module 212. Other standard interfaces for theBluetooth transport driver 210 include the Universal Serial Bus (USB) and Universal Asynchronous Receiver-Transmitter (UART) protocols. Thetransport drivers 210′ in device(s) 120 have similar features to those of thetransport driver 210. - In a shopping scenario, a store merchant possesses a Bluetooth-enabled fixed
position device 200 which the merchant uses to communicate with the user. The merchant's Bluetooth-enabled fixedposition device 200 includesapplication programs 206′,protocol driver 208′,transport driver 210′, andRF wireless module 212′. - Fixed position device(s)200 and
service operator 130 are connected by means of wide area network (WAN) interfaces 216 and 236, respectively, to awide area network 220.Profile operator 115 is connected by means of TCP/IP interface 246 toInternet 224 which, in turn, is connected to wide area network (WAN) 220 across aprotocol gateway 222. - FIG. 3A is an exemplary block diagram of a
user device 110 of FIG. 2. As shown,user device 110 may include aradio transmitter 310, auser input 315, acentral processor 320, adisplay 325 and amemory 330, which are connected across a bus 305.User device 110 may also include an interface for communicating across a line-based network. -
Memory 330 stores an initialmenu application program 332 for providing a menu of options to the user for selection and implementation of other application programs or routines according to the user selection. For example,menu application program 332 may initiate a sessionsupport application program 334 for supporting a session between the user and one or more other parties. - Session
support application program 334 may include a networkconnection management routine 342,service discovery routine 344, privacylevel negotiation routine 346 and aservice management routine 354. Networkconnection management routine 342 is a process by which the user can be connected to Cellular Networks and Personal Area Networks (PAN) independently and by which the Bluetooth master and slave relationship can be determined.Service discovery routine 344 is a process which enables the user to activate or deactivate visibility to Bluetooth Access points (such as fixed position wireless devices) or enables the terminal to discover Bluetooth nodes in a PAN. Privacylevel negotiation routine 346 is a process by which the user or the terminal on behalf of the user can determine which level of privacy should be maintained in an ad-hoc or user-initiated service context. As discussed above, the different levels of privacy may include Anonymous, Pseudonymous, Anonymous transaction and Authenticated.Service management routine 354 is a process by which the same service session can be maintained over several different network connections. - Initial
menu application program 332 may also provide access to other menu accessible application programs, such as acalendar 348,games 350,device control 352 or otheradditional applications 353. - A user database or
assets 378 is also maintained to store the user's private assets as well as other information. These assets may include, for example, profile preferences, rights wallet, presence information (e.g., context, device, location), and Personal Information Manager (PIM). Profile preferences involves a process for saving, storing and retrieving profile and preferences of a certain user, e.g., age, gender, social security number, shoe size, favorite food, loyalty card numbers, credit card numbers, etc. Rights wallet involves a process for saving, storing and retrieving rights belonging or given to a certain user, e.g., voting rights, access rights, etc., and the parameters to these, e.g., time, location, context, etc. Presence involves a process for saving, storing and retrieving context, device and location data of a given user. PIM involves a process for saving, storing and retrieving Personal Information data of a given user, e.g., calendar, e-mail, etc. -
Memory 330 may further include additional application programs to facilitate the management of user privacy in communications with other parties. These programs may include aprofile capturing program 370, aprivacy management program 372, and aninterface support program 374. These programs will be discussed with reference to FIG. 3C which illustrates a high level architecture of components of thenetwork system 100 in which various application or function layers and sub-layers supported by the user device are shown. - As shown in FIG. 3C, profile capturing
application program 370 provides a mechanism for capturing profile related information of the user. Profile capturingapplication program 370 may include various routines, such as device adaptation, clickstream recording, location tracking and context determination. Device adaptation is a process by which the content elements adapt to the user interface and presentation available in the terminal. The adaptation takes into account screen resolution, colors, free memory size and bandwidth available. - Clickstream recording is used for calibrating the middleware layer, i.e., for providing data to a recommendation engine or for optimizing menu structures. The end user should at any time be able to opt-out from recording or to review the data recorded from the clickstream.
- Location tracking is used for calibrating the middleware layer, i.e., for providing data to a recommendation engine or for optimizing menu structures. The end user should at any time be able to opt-out from tracking or to review location data saved during consumption.
- Context determination is used for calibrating the middleware layer, i.e., for providing data to a recommendation engine or for optimizing menu structures. Context determination parameters may be, for instance, time, content available at the given time and environment, altitude, heart beat rate, etc. The end user should at any time be able to opt-out from context determination or to review context data saved during interactive activities.
- Furthermore, content adaptation within profile capturing is the mechanism for determining the mark-up language to be used, preferably, but not limited to, WML or XML.
- As shown in FIG. 3B, profile capturing
application program 370 interacts withuser 380 to capture profile-related information. Privacymanagement application program 372 provides a security layer to access of auser assets 378, and interfacesupport application program 374 enablesuser device 110 to interact with a service operator to obtain services provided through the service operator's content andapplications 390. - The Service operator's content and
applications 390 may include advertising platforms, content aggregation, CRM-Call Center Applications, one-to-one marketing, chat rooms, network games, and multimedia messaging. Advertising platforms may include Internet and mobile Internet advertising platforms. Content aggregation may involve a process of combining content from many sources into one service. CRM-Call Center Applications may involve a process for managing short term and context sensitive customer relationship data and retrieving it from CRM applications for calibrating middleware services. One-to-one marketing may involve service content profiling mechanisms using privacy levels. Chat rooms provide real-time person to person communication services using privacy levels. Network game includes real-time network gaming using privacy levels. Finally, multimedia messaging involves messaging with multimedia elements using privacy elements. - Privacy
management application program 372 for managing security over the user's assets.Application program 372 may include various functions, such as service contract management, Anonymity and Public Key Infrastructure (PKI). Service contract management involves a process for determining the wishes of the consumer to lower the privacy levels and reveal certain viewpoints to the consumer assets in a certain service session. Anonymity is preferably the default level of privacy in the privacy management. The Public Key Infrastructure (PKI) is the method by which security is added to the privacy management. - Interface
support application program 374 provides support for interacting with another party, such as a service operator. Interfacesupport application program 374 may include various sub-functions, such as ad interfaces, Ubiquitous Customer Relations Management (UbiCRM) and content interfaces. Ad interfaces may include context, privacy, device and location sensitive Advertising platform interface mechanisms. CRM may include context, privacy, device and location sensitive CRM interface mechanisms. Content interfaces context, privacy, device and location sensitive Content interface mechanisms. - FIG. 4 shows the functional components of an
exemplary service operator 130 arranged as an object model. The object model groups the object oriented software programs into components that perform the major functions and applications inservice operator 130. The object model formemory 430 ofservice operator 130 employs a three-tier architecture that includespresentation tier 432, infrastructure objects partition 440, and business logic tier 450. The object model further divides business logic tier 450 into two partitions, application objectspartition 454 and data objectspartition 470. -
Presentation tier 432 retains the programs that manage the device interfaces toservice operator 130. In FIG. 4,presentation tier 432 includesnetwork interface 434, andbank interface 436. A suitable implementation ofpresentation tier 432 may use Java servlets to interact with user device via the hypertext transfer protocol (“HTTP”). The Java servlets run within a request/response server that manages the exchange of messages between a user device andservice operator 130. A Java servlet is a Java program that runs within a Web server environment. A Java servlet takes a request as input, parses the data, performs logic operations, and issues a response back to a user device. The Java runtime platform pools the Java servlets to simultaneously service many requests.Network interface 434 accepts request messages from a user device and passes the information in the request to visitobject 452 for further processing. Visitobject 452 passes result of that processing tonetwork interface 434 for transmission back to the user device.Network interface 434 may also usenetwork adapter 410 to exchange data with another user device.Bank interface 436 manages the exchange of messages between a financial institution and visitobject 452 in a similar manner to networkinterface 434. - Infrastructure objects partition440 retains the programs that perform administrative and system functions on behalf of business logic tier 450. Infrastructure objects partition 440 includes
operating system 448, and an object oriented software program component fordatabase server interface 442, andsystem administrator interface 446. - Business logic tier450 in FIG. 4 includes multiple instances of
visit object 452. A separate instance ofvisit object 452 exists for eachbank interface 436 ornetwork interface 434 session. Eachvisit object 452 is a stateful session bean that includes a persistent storage area from initiation through termination of the session, not just during a single interaction or method call. The persistent storage area retains information associated with the session. - When a user device sends a message to
service operator 130, a message is sent tonetwork interface 434 to invoke a method that createsvisit object 452 and stores connection information invisit object state 452. Visitobject 452 may, in turn, invoke a method in digitalsignature verification application 456 to verify the source that generated the message. Digitalsignature verification application 456 extracts the digital signature from the message and uses publickey data 472 to decode the signature and verify the identity of the source that generated the message. Even though FIG. 4 depictscentral processor 420 as controlling digitalsignature verification application 456, it is to be understood that the function performed by digitalsignature verification application 456 can be distributed to a separate system configured similarly toservice operator 130. - When a user device sends a message to
service operator 130, a message is sent tonetwork interface 434 to invoke a method that createsvisit object 452 and stores connection information invisit object state 452. Visitobject 452 may, in turn, invoke a method indata authentication application 458 to authenticate a user device that generated the message.Data authentication application 458 usesMAC data 474 to authenticate the identity of the user device that generated the message. Even though FIG. 4 depictscentral processor 420 as controllingdata authentication application 458, it is to be understood that the function performed bydata authentication application 458 can be distributed to a separate system configured similarly toservice operator 130. - When a user device sends a message to
service operator 130, a message is sent tonetwork interface 434 to invoke a method that createsvisit object 452 and stores connection information invisit object state 452. Visitobject 452 may, in turn, invoke a method inpersonal service application 460 to perform the service-related operations including service negotiations, user profile access, the provision of services including personalized services.Personal service application 460 usesservice data 476 to perform such operation. FIGS. 8A through 8C as well as the discussion above with reference to FIGS. 3B and 3C on the service operator's content andapplication 390 describe the service-related functions ofpersonal service application 460. Even though FIG. 4 depictscentral processor 420 as controllingpersonal service application 460, it is to be understood that the function performed bypersonal service application 460 can be distributed to a separate system configured similarly toservice operator 130. - When a user device sends a message to
service operator 130, a message is sent tonetwork interface 434 to invoke a method that createsvisit object 452 and stores connection information invisit object state 452. Visitobject 452 may, in turn, invoke a method inpayment method application 462 to compute a payment or fee for services rendered through use ofpayment data 478. Even though FIG. 4 depictscentral processor 420 as controllingpayment method application 462, it is to be understood that the function performed bypayment method application 462 can be distributed to a separate system configured similarly toservice operator 130. - When a user device sends a message to
service operator 130, a message is sent tonetwork interface 434 to invoke a method that createsvisit object 452 and stores connection information invisit object state 452. Visitobject 452 may, in turn, invoke a method in profile distribution application 464 to control distribution/access of a user's profile information to lower level service operators through use of profile data 480. An example of a service operator which would implement profile distribution application is SO3+PO3 of FIG. 6B. Even though FIG. 4 depictscentral processor 420 as controlling profile distribution application 464, it is to be understood that the function performed by profile distribution application 464 can be distributed to a separate system configured similarly toservice operator 130. - FIG. 5 shows the functional components of
profile operator 115 arranged as an object model. The object model groups the object oriented software programs into components that perform the major functions and applications inprofile operator 115. The object model formemory 530 ofprofile operator 115 employs a three-tier architecture that includespresentation tier 532, infrastructure objectspartition 540, and business logic tier 550. The object model further divides business logic tier 550 into two partitions, application objectspartition 554 and data objectspartition 570. -
Presentation tier 532 retains the programs that manage the device interfaces toprofile operator 115. In FIG. 5,presentation tier 532 includesnetwork interface 534, andbank interface 536. A suitable implementation ofpresentation tier 532 may use Java servlets to interact with user device via the hypertext transfer protocol (“HTTP”). The Java servlets run within a request/response server that manages the exchange of messages between a user device andprofile operator 115. A Java servlet is a Java program that runs within a Web server environment. A Java servlet takes a request as input, parses the data, performs logic operations, and issues a response back to a user device. The Java runtime platform pools the Java servlets to simultaneously service many requests.Network interface 534 accepts request messages from a user device and passes the information in the request to visitobject 552 for further processing. Visitobject 552 passes result of that processing tonetwork interface 534 for transmission back to the user device.Network interface 534 may also usenetwork adapter 510 to exchange data with another user device.Bank interface 536 manages the exchange of messages between a financial institution and visitobject 552 in a similar manner to networkinterface 534. - Infrastructure objects
partition 540 retains the programs that perform administrative and system functions on behalf of business logic tier 550. Infrastructure objectspartition 540 includesoperating system 548, and an object oriented software program component fordatabase server interface 542, andsystem administrator interface 546. - Business logic tier550 in FIG. 5 includes multiple instances of
visit object 552. A separate instance ofvisit object 552 exists for eachbank interface 536 ornetwork interface 534 session. Eachvisit object 552 is a stateful session bean that includes a persistent storage area from initiation through termination of the session, not just during a single interaction or method call. The persistent storage area retains information associated with the session. - When a user device sends a message to profile
operator 115, a message is sent tonetwork interface 534 to invoke a method that createsvisit object 552 and stores connection information invisit object state 552. Visitobject 552 may, in turn, invoke a method in digital signature verification application 556 to verify the source that generated the message. Digital signature verification application 556 extracts the digital signature from the message and uses public key data 572 to decode the signature and verify the identity of the source that generated the message. Even though FIG. 5 depictscentral processor 520 as controlling digital signature verification application 556, it is to be understood that the function performed by digital signature verification application 556 can be distributed to a separate system configured similarly toprofile operator 115. - When a user device sends a message to profile
operator 115, a message is sent tonetwork interface 534 to invoke a method that createsvisit object 552 and stores connection information invisit object state 552. Visitobject 552 may, in turn, invoke a method indata authentication application 558 to authenticate a user device that generated the message.Data authentication application 558 usesMAC data 574 to authenticate the identity of the user device that generated the message. Even though FIG. 5 depictscentral processor 520 as controllingdata authentication application 558, it is to be understood that the function performed bydata authentication application 558 can be distributed to a separate system configured similarly toprofile operator 115. - When a user device sends a message to profile
operator 115, a message is sent tonetwork interface 534 to invoke a method that createsvisit object 552 and stores connection information invisit object state 552. Visitobject 552 may, in turn, invoke a method in profile distribution application 560 to control distribution/access of a user's profile information to lower level service operators through use of profile data 576. FIGS. 8A through 8D describes, in greater detail, the process of profile distribution application 560. Even though FIG. 5 depictscentral processor 520 as controlling profile distribution application 560, it is to be understood that the function performed by profile distribution application 560 can be distributed to a separate system configured similarly toprofile operator 115. - When a user device sends a message to profile
operator 115, a message is sent tonetwork interface 534 to invoke a method that createsvisit object 552 and stores connection information invisit object state 552. Visitobject 552 may, in turn, invoke a method inprofile billing application 562 to bill another party for services rendered (e.g., charge service operator for profile information) through use ofbilling data 578. Even though FIG. 5 depictscentral processor 520 as controllingprofile billing application 562, it is to be understood that the function performed byprofile billing application 562 can be distributed to a separate system configured similarly toprofile operator 115. - When a user device sends a message to profile
operator 115, a message is sent tonetwork interface 534 to invoke a method that createsvisit object 552 and stores connection information invisit object state 552. Visitobject 552 may, in turn, invoke a method inanonymous payment application 564 to provide trusted anonymous third payment services for a user through use ofpayment data 580. Even though FIG. 5 depictscentral processor 520 as controllinganonymous payment application 564 it is to be understood that the function performed byanonymous payment application 564 can be distributed to a separate system configured similarly toprofile operator 115. - It will be readily appreciated that
service operator 130 and/orprofile operator 115 may alternatively, or in addition to, the communication software discussed above, be equipped with a WML Script and WML functionality for communicating with the various system components (e.g., the user device, service operator, and/or profile operator). - FIG. 6A is an overview of one example of a service operator arrangement in which the user actions, via wireless
portable device 110, are transmitted to service operators using a profile operator. As shown, each profile operator, e.g., PO1 and PO2, serves all the service operators SO1 through SO4 that the user may wish to use. To selectively control access and usage of profile information, viewpoint technology may be employed to enable different parts of the user profile to be accessed and used by different service operators. Viewpoints allow the service operator to access subsets of profile information for different purposes in different contexts. - In certain situations, a user or profile operator may wish to mask the user's identity from the service operators. Profile operators can be configured to perform such identity masking in at least two different levels. The one level of masking is pseudonymity which allows service operators to establish a relationship with the users while offering an opportunity to actively conceal or reveal elements of user identity. Another level of masking is complete anonymity which does not allow the service operators to identify the users. In both levels of identity masking, the profile operators can handle the billing of services.
- From the profiling point of view, a significant difference between the two levels of identity masking is that pseudonymity allows each service operator to build its own profiles of user behavior since the service usage behavior of each individual user employing a service can be identified. However, anonymity does not allow service operators to build user profiles since the service operator cannot combine the usage data from multiple sessions for a particular user.
- In order to receive profile information from a profile operator the service operators may be required to provide the profile operator with profile update information based on the user's service usage behavior. If the users are using the services anonymously, the service operators cannot build their own user profiles and the update information is the only way to develop the quality of profiles. Since the update information is valuable for the profile operators the service operators can be compensated by decreasing the price of the profile information in exchange for updates.
- FIG. 6B is an overview of another example in which service operators may be hierarchically arranged to provide additional privacy levels or filtering in accordance with a further embodiment. As shown, service operators can be arranged hierarchically (SO4-SO7) such that higher level operators serve lower level operators. For example, with reference to 610, the service operator SO3 serves the lower level service operators SO4 through SO7. In this kind of arrangement, the service operator SO3 may also incorporate a profile operator PO3 or its functions to provide profiling services for lower level service operators SO4 through SO7.
- In this hierarchical arrangement, the level of identification information revealed to the lower level service operator may vary as well as the level of detail in the update information provided to the upper level operator. For example, the service operator SO3 may be privy to a higher profile access level than the lower level service operators SO4 through SO7 since the service operator SO3 may further filter a user's profile information provided to these lower level service operators. At the same time, the service operator SO3 may receive user information from the lower level service operators SO4 through SO7 to update the user's profile.
- The operator arrangements as shown in FIGS. 6A and 6B provide some potential advantages and disadvantages to the parties involved. For example, the advantages of these operator arrangements may, for example, include:
- support for anonymity,
- personalization over multiple service operators,
- some service access information is available to profile operators without explicit feedback from the service operators,
- personalization operator has access to usage data of all its customers,
- a user can select his profile operator,
- SO3/PO3 can analyze all visitors to a collection of SO8 (SO6-SO7), which enables personalization at least across services with more complete data, and
- hierarchical service operator arrangement supports affiliate companies.
- Some potential disadvantages of such operator arrangements may, for example, include:
- service operators have poorer data for personalization, and
- a profile operator does not see all the users accessing a certain service operator.
- FIG. 7A illustrates an exemplary profile database576 maintained or employed by
profile operator 115. Profile database may include aservice contract field 705, acategory field 710, a viewpoint identifier (ID)field 715 and aprofile items field 720. While the various fields and information are self-explanatory, a brief discussion of the database is provided below. -
Service contract field 705 maintains an identity of those parties with pre-existing agreements with the user. These parties may have agreed upon the user profile subset to be provided to them.Category field 710 maintains information on the various categories of service contexts or categories a user may encounter. For example, a category may include shopping, meeting, emergency, doctor visit and music bar. -
Viewpoint ID 715 maintains a viewpoint identifier for specifying a particular subset or viewpoint of a user's profile information. -
Profile items 720 define various defined subsets or viewpoints of the user's profile information. These profile items are addressable byprofile operator 115 according to a service contract, category or viewpoint ID. For example, in a shopping example,user device 110 may forward the category information (e.g., shopping) or a viewpoint ID (e.g., 1111) toservice operator 130 which is then provided as part of a request to profileoperator 115 for the user's profile information. Based on either the category or viewpoint identifier,profile operator 115 would provide the appropriate subset of profile information, e.g., the user's shopping list, the user's likes and/or dislikes and the user's usual buying habits. - FIG. 7B illustrates an exemplary profile access authority database360 maintained or employed by
user device 110 to determine a profile access authority or level. Database 360 may include a service contract field 725, a category field 735 and a viewpoint ID field 735, which maintain similar information as infields service operator 130 based whether the service operator has a contract with the user or based on the service category. - FIGS. 8A through 8D illustrate an
exemplary process 800 by which a user controls a privacy level of communications with a service operator and controls access and usage of the user's profile information by the service operator via the user's Bluetooth-enabled portable device. Theprocess 800 will be discussed with reference to FIGS. 1 and 2. In thisexample user device 110 is a Bluetooth-enabled portable wireless device and fixed position Bluetooth wireless device corresponds, e.g., todevice 200 of FIG. 2. For the purposes of brevity, the fixed position Bluetooth wireless device will be referred hereafter as fixedposition device 200.Fixed position device 200 enables location-based services as well as other services to be provided to the user. Communications betweenuser device 110,service operator 130 andprofile operator 115 may be facilitated through fixedposition device 200 or other communications means, such as by cellular. - The
process 800 commences atstep 802 whereuser device 110 initiates service discovery automatically or upon a user request. Atstep 804,user device 110 sends periodic short range identity signal. Atstep 806, fixedposition device 200 detects auser device 110's presence and, atstep 810, sends an indication of service opportunit(ies) available fromservice operator 130.User device 110 discovers these opportunities atstep 808, and sends a request for service-related information atstep 812. Along with the request,user device 110 may or may not send an identifier depending upon the privacy level determined by the user device. Whereuser device 110 is simply discovering available service opportunities, the user device would unlikely send any identifier. In other words, the request for service information would be an anonymous request. -
Fixed position device 200 receives the request atstep 814 and, atstep 820, sends the service-related information touser device 110. The service-related information may include service category, service description, requested viewpoint or any information which enablesuser device 110 to make a determination as to a privacy level and/or a profile access level. Alternatively, fixedposition device 200 may pass the request toservice operator 816 so that the service-related information is provided byservice operator 130 throughsteps - At
step 824,user device 110 receives the service-related information. The information may be displayed to the user. Atstep 826,user device 110 determines whether to proceed with the service negotiation, for example, based upon a user selection. Ifuser device 110 determines not to proceed, then the negotiations are terminated atstep 830. Otherwise, theprocess 800 proceeds to step 828 in whichuser device 110 initiates a new session withprofile operator 115. - At
step 832,user device 110 requests session-based User ID fromprofile operator 115. As previously discussed, and as shown in FIG. 8B,user device 110 may send the request directly to profile operator, such as by cellular, or may send the request via fixedposition device 200 which passes the request to the profile operator atstep 834. -
Profile operator 115, insteps step 840,profile server 115 sends the User ID touser device 110. As shown,profile operator 115 may send the User ID directly touser device 110, such as by cellular, or may send the request via fixedposition device 200 which passes the request to the user device atstep 841. Thereafter,user device 110 receives the user ID atstep 814. The user ID enables user device to conduct pseudonymous communications withservice operator 130. Althoughuser device 110 may employ the user ID for more than one session, a new user ID is preferably generated for each session to prevent a service operator from collecting any profile information on the user. - At
step 844, user device initiates a service session profile capturing operation which involves tracking the behavior and/or activities of the user onuser device 110. This may involve, for example, clickstream recording, device adaptation tracking, location tracking and context tracking. The profile information of the user may be updated with the tracked information. - The session continues at
step 846, at which time,user device 110 determines whether the user has a pre-existing relationship withservice operator 130, such as a service contract with the service operator. If a service contract exists,user device 110 sends a profile access level or authority, which reflects a previously agreed upon profile access level or authority, (e.g., a predefined viewpoint identifier) toservice operator 130 atstep 852 via fixedposition device 110 atstep 854. Along with the profile access authority,user device 110 may or may not send an identifier depending on the privacy level determined by the user device. In such as situation,user device 110 may send the session-based user ID or, alternatively, an authenticated ID. - At
step 856,service operator 130 receives the profile access level or authority and some user identifier (if transmitted), and requests the user profile fromprofile operator 115. Atstep 858,profile operator 115 receives the request, and retrieves a subset of the user's profile information according to the authorized profile access level. Thereafter,profile operator 115 sends the user profile toservice operator 130 atstep 860, and may charge or bill the service operator a fee for the profile information atstep 874. - At
step 862,service operator 130 receives the subset of the user's profile information, and provides personalized service(s) to the user according to the received subset of the profile information. Atstep 876,service operator 130 may send user information relating to the session, e.g., user activity or behavior, to profileoperator 115 automatically or upon request by the profile operator.Profile operator 115 may then update the user's profile information with the user information provided by theservice operator 130, and may also compensate the service operator for such information. The compensation may take the form of a discount to the fee charged byprofile operator 115 for providing profile information toservice operator 130. The discount may be increased accordingly based upon the amount of updated information or the number of times updated information is provided byservice operator 130. - Continuing at
steps user device 110 receives the personalized service(s), via fixedposition device 200. Atstep 868,user device 110 terminates the session. Atstep 870,user device 110 may send tracked user information captured by the session profile tracking operation initiated atstep 844 toprofile operator 115. Atstep 872,profile operator 115 updates the user's profile accordingly based on the received information. - Returning to step850 of FIG. C, the
process 800 proceeds to step 880 to continue determine the privacy level if no pre-existing relationship exists betweenservice operator 130 and the user. Atstep 882,user device 110 determines a profile access level or authority to the user's profile information based on a service category or content or any information provided byservice operator 130, such as a requested viewpoint, etc. Atstep 883,user device 110 sends the determined profile access level or authority via fixed position device 200 (step 884). Along with the profile access authority,user device 110 may or may not also send an identifier depending upon the privacy level determined by the user device. - At
step 885,service operator 130 receives the user ID and profile access level, and requests the appropriate user profile fromprofile operator 115. Atstep 886,profile operator 115 receives the request, and retrieves a subset of the user's profile information according to the authorized profile access level. Thereafter,profile operator 115 sends the user profile toservice operator 130 atstep 887, and may charge or bill the service operator a fee for the profile information atstep 894. - At
step 888,service operator 130 receives the subset of the user's profile information, and provides personalized service(s) to the user according to the received subset of profile information. Atstep 895,service operator 130 may send user information relating to the session, e.g., user activity or behavior, to profileoperator 115 automatically or upon a request by the profile operator.Profile operator 115 may then update the user's profile information with the user information provided by theservice operator 130, and may also compensate the service operator for such information. As discussed above, the compensation may take the form of a discount to the fee charged byprofile operator 115 for providing profile information toservice operator 130. - Continuing at
steps user device 110 receives the personalized service(s), via fixedposition device 200. Atstep 891,user device 110 terminates the session. Atstep 892,user device 110 may send tracked user information captured by the session profile tracking operation initiated atstep 844. Atstep 893,profile operator 115 updates the user's profile accordingly based on the received information. - Although the
process 800 shows fixedposition device 200 as facilitating the provision of services betweenservice operator 130 anduser device 110, this device may be considered a component ofservice operator 130 where it performs service functions for the service operator. - Furthermore, FIGS. 8A through 8D provide one illustrative example of the privacy and profile access features in a specific network arrangement embodiment employing Bluetooth technology. It is apparent that these operations may be implemented between the various parties, e.g., a user device, a profile operator and a service operator, over any communication medium employing different network environments and/or different wireless technologies.
- For example, instead of distributing the service-related functions between
service operator 130 and fixedposition device 200, the fixed position device may be configured as a stand-alone fixed or mobile device (e.g., another person's Bluetooth-enabled device) capable of performing all the operations performed byservice operator 130 as discussed above in regard to FIGS. 8A through 8D. The stand-alone mobile device may, for example, beservice operator 140 as shown in FIGS. 1A and 1B in whichuser device 110 communicates withservice operator 140 over a personal area network (PAN). - Alternatively,
user device 110 may conduct communications withservice operator 130 andprofile operator 115 over a general packet radio system (GPRS) or general system for mobile communications (GSM). At an initial stage,user device 110 may automatically or upon a user request send a request for service-related information (e.g., service category, service description, requested viewpoint, etc.) toservice operator 130. The remaining operations performed byuser device 110,service operator 130 andprofile operator 115 thereafter would be similar to those discussed above insteps 826 through 893 of FIGS. 8A-8D. - Various illustrative examples of the operation of
system network 100 in different service environments will be described below. These examples include a shopping scenario, a meeting scenario, a medical emergency scenario, a health care scenario and a music bar scenario. As discussed above, the privacy level and profile access level provided by the user may vary depending on the nature of the services. - In one example, a user operating a Bluetooth-enable
user device 110 is shopping at a location (e.g., store, mall, etc.) having one or more fixed Bluetooth-enabled devices arranged at various locations within and/or in the vicinity of the shopping location. In this environment, the user may be provided services, such as information on sales or discounts on specific items, location of specific stores in the user's vicinity, advertising, and so forth based on the subset of the user's profile received from the profile server. Furthermore, the services may involve a transaction to purchase particular items. For transactions requiring payment by the user, the payment may be performed anonymously through a trusted third party, such as the user's profile operator. - In one example, a user operating a Bluetooth-enable
user device 110 attends a meeting at a location having one or more fixed Bluetooth-enabled devices arranged at various locations within and/or in the vicinity of the meeting location. In this environment, the user may be provided services, such as document and file delivery, information on other people attending the meeting and whether every person has arrived, and so forth. Furthermore, the services may also include voting at the meeting. - In a further example, a user operating a Bluetooth-enabled
user device 110 attends a meeting in which one or more people also have a Bluetooth-enabled device. As the user approaches within communication proximity with another person's device,user device 110 establishes a communication link with the other person's device (or vice-versa), e.g., service operator, to form a personal area network (PAN). In this environment, the services may include access to the other person's assets, such as personal information, software including games, etc., documents, and so forth. Additionally, the services may involve scheduling a further appointment with the other person, and so forth. - In one example, a user operating a
portable user device 110 is faced with a medical emergency. Throughuser device 110, the user can obtain services, such as medical consultation, directions to the closest hospital, calling for an ambulance, contacting the user's doctor and so forth. - In one example, a user operating a Bluetooth-enable
user device 110 visits the office of his/her doctor. The doctor's office has one or more fixed Bluetooth-enabled devices arranged at various locations within and/or outside the office. In this environment, the user may be provided services, such as medical consultation, information relating to the doctor or doctor's office, information relating to whether the doctor is on schedule with his/her appointments, information relating to new medical treatments, advertising for drugs or new medical procedures, and so forth. - Furthermore, the services may also include transaction-related services, such as scheduling a follow-up doctor's visit, obtaining a drug prescription and so forth.
- In one example, a user operating a Bluetooth-enable
user device 110 enters a music bar having one or more fixed Bluetooth-enabled devices arranged at various locations within the bar. In this environment, the user may be provided services, such as information services which may include advertising, general information about the music bar (e.g., background information, bar layout, etc.), information on other people at the music bar, information on music being played, information on the identities of music performers as well as the music currently playing, played or to be played at the music bar, a schedule of performances, general statistical information as to the people at the bar (e.g., 15 single females, 13 single males, etc.), and so forth. - Additional services may also include transaction-related services, such as music downloads, purchasing tickets to music performances, purchasing food and beverages, and so forth. Transactions requiring payment by the user may be conducted through anonymous payment with the assistance of a trusted third party or
profile operator 115 acting as a trusted third party. The services capable of being provided by the service operator may be related or unrelated to the music bar environment. - In a further example, a user operating a Bluetooth-enabled
user device 110 enters a music bar in which one or more people also have a Bluetooth-enabled device. As the user approaches within communication proximity with another person's device,user device 110 establishes a communication link with the other person's device (or vice-versa), e.g., service operator, to form a personal area network (PAN). In this environment, the services may include access to the other person's assets, such as personal information, software including games, etc., documents, and so forth. Additionally, the services may involve playing a game with the other person over the personal area network, setting up a date with the other person and so forth. - While a specific communication arrangement is discussed in these illustrative scenarios, the service operator may provide the services to the user over any communication network arrangement, such as a personal area network (PAN), the Internet, wireless communication network or a combination thereof.
- Although specific embodiments of the invention have been disclosed, it will be understood by those having skill in the art that changes can be made to that the specific embodiments without departing from the spirit and the scope of the invention.
Claims (34)
1. A method of managing user privacy in a network environment, comprising:
recognizing one or more service opportunities of a service operator on a user device operated by a user;
determining a privacy level at which communications is conducted with a service operator; and
conducting the communications with the service operator at the privacy level.
2. The method according to claim 1 , wherein the recognizing comprises automatically discovering the one or more service opportunities.
3. The method according to claim 2 , wherein the user device is a BLUETOOTH—enabled wireless communications device which automatically discovers service opportunities.
4. The method according to claim 1 , wherein the recognizing comprises anonymously obtaining information relating to the one or more service opportunities.
5. The method according to claim 4 , wherein the information relating to the one or more service opportunities comprises one of a service category, a service description and a requested viewpoint.
6. The method according to claim 5 , further comprising allowing the service provider to obtain access to a subset of profile information of the user according to the service category.
7. The method according to claim 6 , further comprising providing personalized service to the user according to the subset of profile information.
8. The method according to claim 5 , further comprising allowing the service provider to obtain a subset of profile information of the user according to the requested viewpoint.
9. The method according to claim 8 , further comprising providing personalized service to the user according to the subset of profile information.
10. The method according to claim 1 , wherein the privacy level includes one of Anonymous, Pseudonymous, Anonymous transaction and Authenticated.
11. The method according to claim 1 , wherein the determining a privacy level determines a privacy level based on the nature of the service negotiations with the service operator.
12. The method according to claim 1 , wherein the determining a privacy level determines a privacy level based on a level of privacy in one or more prior transactions with the specific service operator.
13. The method according to claim 1 , wherein the determining a privacy level determines a privacy level based on the identity of the service operator.
14. The method according to claim 1 , wherein the determining a privacy level determines a privacy level based on user-defined parameters.
15. The method according to claim 1 , wherein the determining a privacy level determines a privacy level based on the user's prior behavior or activity.
16. The method according to claim 1 , further comprising obtaining a user identifier to conduct pseudonymous communications with the service operator relating to the one or more service opportunities.
17. The method according to claim 12 , further comprising allowing the service provider to obtain access to a predefined subset of profile information.
18. The method according to claim 1 , further comprising allowing the service provider to obtain access to a subset of profile information.
19. The method according to claim 18 , wherein the service provider is charged a fee for obtaining the subset of profile information.
20. The method according to claim 18 , wherein the service provider obtains the subset of profile information from a profile operator remotely located from the user device.
21. The method according to claim 20 , wherein the allowing the service provider comprises:
determining a profile access level; and
transmitting the profile access level to the service operator,
wherein the service operator obtains a subset of profile information from a profile operator according to the profile access level.
22. The method according to claim 21 , wherein the determining a profile access determines the profile access level according a service category of the one or more service opportunities.
23. The method according to claim 21 , wherein the determining a profile access determines the profile access level based upon a prior arrangement between the service operator and the user.
24. The method according to claim 18 , further comprising updating the profile information of the user.
25. The method according to claim 24 , wherein the profile information of the user is updated based on user information provided by the service operator.
26. The method according to claim 25 , wherein the service operator is compensated for providing the user information.
27. The method according to claim 24 , further comprising tracking user activity on the user device, wherein the profile information of the user is updated based on the tracked user activity.
28. The method according to claim 1 , wherein the service opportunities recognized by the user are dynamically changed by the service provider.
29. The method according to claim 28 , wherein the service opportunities recognized by the user are dynamically changed by the service provider according to profile information of the user.
30. The method according to claim 1 , wherein the user device and the service operator communicate across a personal area network.
31. The method according to claim 1 , wherein the user device comprises a mobile wireless device.
32. The method according to claim 1 , further comprising receiving service from the service operator.
33. The method according to claim 32 , wherein payment for the service obtained by the user is conducted anonymously.
34. A method of managing user privacy in a network environment through a distributed user system including a user device and profile operator, comprising:
recognizing one or more service opportunities of a service operator on a user device operated by a user;
determining a privacy level at which communications is conducted with a service operator relating to the one or more service opportunities on the user device;
determining a profile access level on the user device;
transmitting the profile access level to the service operator; and
enabling the service operator to obtain a subset of profile information of the user according to the profile access level.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/824,781 US20020147766A1 (en) | 2001-04-04 | 2001-04-04 | Operating user profiles with distributed profile model using a hybrid terminal |
AU2002253424A AU2002253424A1 (en) | 2001-04-04 | 2002-04-03 | Operating user profiles with distributed profile model using a hybrid terminal |
PCT/IB2002/001066 WO2002082205A2 (en) | 2001-04-04 | 2002-04-03 | Operating user profiles with distributed profile model using a hybrid terminal |
EP02722539A EP1405197A2 (en) | 2001-04-04 | 2002-04-03 | Operating user profiles with distributed profile model using a hybrid terminal |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/824,781 US20020147766A1 (en) | 2001-04-04 | 2001-04-04 | Operating user profiles with distributed profile model using a hybrid terminal |
Publications (1)
Publication Number | Publication Date |
---|---|
US20020147766A1 true US20020147766A1 (en) | 2002-10-10 |
Family
ID=25242300
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/824,781 Abandoned US20020147766A1 (en) | 2001-04-04 | 2001-04-04 | Operating user profiles with distributed profile model using a hybrid terminal |
Country Status (4)
Country | Link |
---|---|
US (1) | US20020147766A1 (en) |
EP (1) | EP1405197A2 (en) |
AU (1) | AU2002253424A1 (en) |
WO (1) | WO2002082205A2 (en) |
Cited By (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020173296A1 (en) * | 2001-05-21 | 2002-11-21 | Ian Nordman | Method, system, and apparatus for providing services in a privacy enabled mobile and ubicom environment |
US20020196280A1 (en) * | 2001-06-25 | 2002-12-26 | International Business Machines Corporation | Method, system, and program for accessing calendar information for shadowed users from a database |
US20030041100A1 (en) * | 2001-08-23 | 2003-02-27 | Mikael Nilsson | Method for limiting conveyance information of user profile within mobile internet transactions |
US20030069899A1 (en) * | 2001-10-04 | 2003-04-10 | International Business Machines Corporation | Method, system, and program for providing personal preference information when scheduling events |
US20030104820A1 (en) * | 2001-12-04 | 2003-06-05 | Greene David P. | Location-specific messaging system |
US20030131023A1 (en) * | 2002-01-08 | 2003-07-10 | International Business Machines Corporation | Method, system, and program for providing information on users of wireless devices in a database to a personal information manager |
US20030163427A1 (en) * | 2002-02-27 | 2003-08-28 | Nicholas Ho Chung Fung | Activity management method |
US20030172090A1 (en) * | 2002-01-11 | 2003-09-11 | Petri Asunmaa | Virtual identity apparatus and method for using same |
US20030171975A1 (en) * | 2002-03-07 | 2003-09-11 | Evan R. Kirshenbaum | Customer-side market segmentation |
WO2004023326A1 (en) * | 2002-09-09 | 2004-03-18 | Atitania Ltd. | Method and apparatus for generating unique id packets in a distributed processing system |
US20040067752A1 (en) * | 1999-09-10 | 2004-04-08 | Himmelstein Richard B. | Vehicletalk |
US20040137925A1 (en) * | 2003-01-09 | 2004-07-15 | Jason Lowe | Preselection of resources in a personal area network |
US20040148404A1 (en) * | 2001-04-19 | 2004-07-29 | Hideki Muroya | Apparatus and method for connecting appartuses using radio link, method for creating usable scene table for apparatus connection, and recording medium |
US20040176958A1 (en) * | 2002-02-04 | 2004-09-09 | Jukka-Pekka Salmenkaita | System and method for multimodal short-cuts to digital sevices |
US20040205125A1 (en) * | 2003-02-14 | 2004-10-14 | Fuji Xerox Co., Ltd.. | Apparatus, method and program for supporting conversation, and conversation supporting system |
US20040236590A1 (en) * | 2001-08-29 | 2004-11-25 | Visser Michael Maria | Method and system for simplifying activation of a device and a device activated acccording to such method |
US20060053090A1 (en) * | 2002-11-27 | 2006-03-09 | Paul Cotter | Personalising content provided to a user |
US20060198448A1 (en) * | 2005-03-01 | 2006-09-07 | Selim Aissi | Techniques to manage wireless connections |
US20060294381A1 (en) * | 2005-06-22 | 2006-12-28 | Mitchell Douglas P | Method and apparatus for establishing a secure connection |
US20070015519A1 (en) * | 2005-07-12 | 2007-01-18 | Qwest Communications International Inc. | User defined location based notification for a mobile communications device systems and methods |
EP1745590A2 (en) * | 2004-04-22 | 2007-01-24 | Fortress GB Ltd. | Certified abstracted and anonymous user profiles for restricted network site access and statistical social surveys |
US20070082732A1 (en) * | 2003-11-20 | 2007-04-12 | Holger Krummel | A method and device relating to security in a radio communication network |
US7340438B2 (en) | 2001-05-21 | 2008-03-04 | Nokia Corporation | Method and apparatus for managing and enforcing user privacy |
US7447996B1 (en) * | 2008-02-28 | 2008-11-04 | International Business Machines Corporation | System for using gender analysis of names to assign avatars in instant messaging applications |
US20080288484A1 (en) * | 2005-09-15 | 2008-11-20 | Motorola, Inc. | Distributed User Profile |
US20090138427A1 (en) * | 2007-11-27 | 2009-05-28 | Umber Systems | Method and apparatus for storing data on application-level activity and other user information to enable real-time multi-dimensional reporting about user of a mobile data network |
US20100067695A1 (en) * | 2008-09-15 | 2010-03-18 | Yun-Wei Liao | Message processing apparatus and processing method thereof |
US20100122340A1 (en) * | 2008-11-13 | 2010-05-13 | Palo Alto Research Center Incorporated | Enterprise password reset |
US20100161804A1 (en) * | 2008-12-18 | 2010-06-24 | Electronics And Telecommunications Research Institute | System and method for providing device file using device identifier |
US20110219423A1 (en) * | 2010-03-05 | 2011-09-08 | Nokia Corporation | Method and apparatus for triggering user communications based on privacy information |
US20110288919A1 (en) * | 2007-12-14 | 2011-11-24 | John Nicholas Gross | Integrated Gourmet Item Data Collection, Recommender and Vending System and Method |
US20110313870A1 (en) * | 2009-10-13 | 2011-12-22 | Skycore LLC, | Initiating and Enabling Secure Contactless Transactions and Services with a Mobile Device |
US20120047457A1 (en) * | 2010-08-19 | 2012-02-23 | Samsung Electronics Co., Ltd. | Method and apparatus for searching contents |
US20130007112A1 (en) * | 2006-02-21 | 2013-01-03 | Comtrol Corporation | System, method, and device for communicating with a field device |
US8364136B2 (en) | 1999-02-01 | 2013-01-29 | Steven M Hoffberg | Mobile system, a method of operating mobile system and a non-transitory computer readable medium for a programmable control of a mobile system |
US8369967B2 (en) | 1999-02-01 | 2013-02-05 | Hoffberg Steven M | Alarm system controller and a method for controlling an alarm system |
WO2013137842A1 (en) * | 2011-01-24 | 2013-09-19 | Hewlett-Packard Development Company, L.P. | A system and method for accessing a service |
US20140006512A1 (en) * | 2011-03-22 | 2014-01-02 | Telefonaktiebolaget L M Ericsson (Publ) | Methods for Exchanging User Profile, Profile Mediator Device, Agents, Computer Programs and Computer Program Products |
US8648692B2 (en) | 1999-07-23 | 2014-02-11 | Seong Sang Investments Llc | Accessing an automobile with a transponder |
WO2014064538A2 (en) * | 2012-10-12 | 2014-05-01 | Freedomone Mobile, Inc. | Systems and methods for subscription management in a multi-channel context aware communication environment |
US8775391B2 (en) | 2008-03-26 | 2014-07-08 | Zettics, Inc. | System and method for sharing anonymous user profiles with a third party |
US20140236903A1 (en) * | 2012-09-24 | 2014-08-21 | Andrew L. DiRienzo | Multi-component profiling systems and methods |
US8838784B1 (en) | 2010-08-04 | 2014-09-16 | Zettics, Inc. | Method and apparatus for privacy-safe actionable analytics on mobile data usage |
US20140298214A1 (en) * | 2013-03-29 | 2014-10-02 | Microsoft Corporation | Visual Configuration and Activation |
US8892495B2 (en) | 1991-12-23 | 2014-11-18 | Blanding Hovenweep, Llc | Adaptive pattern recognition based controller apparatus and method and human-interface therefore |
US20150057027A1 (en) * | 2008-06-17 | 2015-02-26 | Nintendo Co., Ltd. | Information processing apparatus, information processing system, and storage medium having stored thereon information processing program |
US20150256515A1 (en) * | 2014-03-06 | 2015-09-10 | Samsung Electronics Co., Ltd. | Proximity communication method and apparatus |
US20150379101A1 (en) * | 2014-06-27 | 2015-12-31 | At&T Intellectual Property I, Lp | Method and apparatus for subscriber management |
WO2017160425A1 (en) * | 2016-03-18 | 2017-09-21 | T-Mobile Usa, Inc. | Preference-aware content streaming |
JP2017215968A (en) * | 2009-12-30 | 2017-12-07 | ヘレ グローバル ベスローテン フェンノートシャップHERE Global B.V. | System and method for providing user control of user's network usage data and personal profile information |
US20180315086A1 (en) * | 2005-06-07 | 2018-11-01 | Oath Inc. | Remote mobile profile detection and modification |
US10193943B2 (en) | 2015-11-09 | 2019-01-29 | T-Mobile Usa, Inc. | Data-plan-based quality setting suggestions and use thereof to manage content provider services |
US20190087604A1 (en) * | 2017-09-21 | 2019-03-21 | International Business Machines Corporation | Applying a differential privacy operation on a cluster of data |
US10305952B2 (en) * | 2015-11-09 | 2019-05-28 | T-Mobile Usa, Inc. | Preference-aware content streaming |
US10361802B1 (en) | 1999-02-01 | 2019-07-23 | Blanding Hovenweep, Llc | Adaptive pattern recognition based control system and method |
US10452222B2 (en) | 2013-05-29 | 2019-10-22 | Microsoft Technology Licensing, Llc | Coordination of system readiness tasks |
US10572531B1 (en) * | 2017-10-25 | 2020-02-25 | Amazon Technologies, Inc. | Predictive session-based search engine |
US10728152B2 (en) | 2016-02-08 | 2020-07-28 | T-Mobile Usa, Inc. | Dynamic network rate control |
US11257502B2 (en) | 2005-08-17 | 2022-02-22 | Tamiras Per Pte. Ltd., Llc | Providing access with a portable device and voice commands |
US20230076960A1 (en) * | 2021-09-03 | 2023-03-09 | Bi Science (2009) Ltd | System and a method for multisession analysis |
US11659385B2 (en) * | 2005-03-22 | 2023-05-23 | Interdigital Ce Patent Holdings, Sas | Method and system for peer-to-peer enforcement |
Citations (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4969096A (en) * | 1988-04-08 | 1990-11-06 | New England Medical Center | Method for selecting communication devices for non-speaking patients |
US5237157A (en) * | 1990-09-13 | 1993-08-17 | Intouch Group, Inc. | Kiosk apparatus and method for point of preview and for compilation of market data |
US5710884A (en) * | 1995-03-29 | 1998-01-20 | Intel Corporation | System for automatically updating personal profile server with updates to additional user information gathered from monitoring user's electronic consuming habits generated on computer during use |
US5722418A (en) * | 1993-08-30 | 1998-03-03 | Bro; L. William | Method for mediating social and behavioral processes in medicine and business through an interactive telecommunications guidance system |
US5743054A (en) * | 1994-12-30 | 1998-04-28 | Steelcase Inc. | Modular utilities cover |
US5754938A (en) * | 1994-11-29 | 1998-05-19 | Herz; Frederick S. M. | Pseudonymous server for system for customized electronic identification of desirable objects |
US5796952A (en) * | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US5815665A (en) * | 1996-04-03 | 1998-09-29 | Microsoft Corporation | System and method for providing trusted brokering services over a distributed network |
US5848396A (en) * | 1996-04-26 | 1998-12-08 | Freedom Of Information, Inc. | Method and apparatus for determining behavioral profile of a computer user |
US5852775A (en) * | 1996-09-12 | 1998-12-22 | Earthweb, Inc. | Cellular telephone advertising system |
US5855008A (en) * | 1995-12-11 | 1998-12-29 | Cybergold, Inc. | Attention brokerage |
US5873068A (en) * | 1994-06-14 | 1999-02-16 | New North Media Inc. | Display based marketing message control system and method |
US5892900A (en) * | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5901246A (en) * | 1995-06-06 | 1999-05-04 | Hoffberg; Steven M. | Ergonomic man-machine interface incorporating adaptive pattern recognition based control system |
US5899025A (en) * | 1996-03-22 | 1999-05-04 | Steelcase Inc. | Furniture system (pathways-spaceframe) |
US5910987A (en) * | 1995-02-13 | 1999-06-08 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5963916A (en) * | 1990-09-13 | 1999-10-05 | Intouch Group, Inc. | Network apparatus and method for preview of music products and compilation of market data |
US5974398A (en) * | 1997-04-11 | 1999-10-26 | At&T Corp. | Method and apparatus enabling valuation of user access of advertising carried by interactive information and entertainment services |
US5987440A (en) * | 1996-07-22 | 1999-11-16 | Cyva Research Corporation | Personal information security and exchange tool |
US6023510A (en) * | 1997-12-24 | 2000-02-08 | Philips Electronics North America Corporation | Method of secure anonymous query by electronic messages transported via a public network and method of response |
US6026438A (en) * | 1997-10-31 | 2000-02-15 | Merrill Lynch & Co., Inc. | Dynamic workstation configuration processor |
US6029195A (en) * | 1994-11-29 | 2000-02-22 | Herz; Frederick S. M. | System for customized electronic identification of desirable objects |
US6041325A (en) * | 1997-10-09 | 2000-03-21 | Alcatel Usa Sourcing, L.P. | System and method for controlling access to a telephony database |
US6047327A (en) * | 1996-02-16 | 2000-04-04 | Intel Corporation | System for distributing electronic information to a targeted group of users |
US6061789A (en) * | 1996-01-12 | 2000-05-09 | International Business Machines Corporation | Secure anonymous information exchange in a network |
US6088598A (en) * | 1996-12-17 | 2000-07-11 | Telefonaktiebolaget L M Ericsson | Method and system for displaying greetings in a mobile radio communications system |
US6091518A (en) * | 1996-06-28 | 2000-07-18 | Fuji Xerox Co., Ltd. | Image transfer apparatus, image transmitter, profile information transmitter, image receiver/reproducer, storage medium, image receiver, program transmitter, and image color correction apparatus |
US6112181A (en) * | 1997-11-06 | 2000-08-29 | Intertrust Technologies Corporation | Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information |
US6115709A (en) * | 1998-09-18 | 2000-09-05 | Tacit Knowledge Systems, Inc. | Method and system for constructing a knowledge profile of a user having unrestricted and restricted access portions according to respective levels of confidence of content of the portions |
US6134548A (en) * | 1998-11-19 | 2000-10-17 | Ac Properties B.V. | System, method and article of manufacture for advanced mobile bargain shopping |
US6133912A (en) * | 1998-05-04 | 2000-10-17 | Montero; Frank J. | Method of delivering information over a communication network |
US6141760A (en) * | 1997-10-31 | 2000-10-31 | Compaq Computer Corporation | System and method for generating unique passwords |
US6154778A (en) * | 1998-05-19 | 2000-11-28 | Hewlett-Packard Company | Utility-based multi-category quality-of-service negotiation in distributed systems |
US6154783A (en) * | 1998-09-18 | 2000-11-28 | Tacit Knowledge Systems | Method and apparatus for addressing an electronic document for transmission over a network |
US6226589B1 (en) * | 1999-03-12 | 2001-05-01 | Fujitsu Limited | System for providing guiding information for use in detecting and accessing a mobile object |
US6253203B1 (en) * | 1998-10-02 | 2001-06-26 | Ncr Corporation | Privacy-enhanced database |
US6266704B1 (en) * | 1997-05-30 | 2001-07-24 | The United States Of America As Represented By The Secretary Of The Navy | Onion routing network for securely moving data through communication networks |
US20010011247A1 (en) * | 1998-10-02 | 2001-08-02 | O'flaherty Kenneth W. | Privacy-enabled loyalty card system and method |
US20010014911A1 (en) * | 2000-02-14 | 2001-08-16 | Kabushiki Kaisha Toshiba | Service providing method and system |
US20010028304A1 (en) * | 2000-04-11 | 2001-10-11 | I'anson Colin | Monitoring of location-associated events |
US6317718B1 (en) * | 1999-02-26 | 2001-11-13 | Accenture Properties (2) B.V. | System, method and article of manufacture for location-based filtering for shopping agent in the physical world |
US6374359B1 (en) * | 1998-11-19 | 2002-04-16 | International Business Machines Corporation | Dynamic use and validation of HTTP cookies for authentication |
US6389533B1 (en) * | 1999-02-05 | 2002-05-14 | Intel Corporation | Anonymity server |
US20020069117A1 (en) * | 2000-12-01 | 2002-06-06 | Carothers Christopher D. | Peer-to-peer electronic marketplace and systems and methods for conducting transactions therein |
US20020107634A1 (en) * | 2001-02-06 | 2002-08-08 | Sergio Luciani | Traffic monitoring system and method |
US6438544B1 (en) * | 1998-10-02 | 2002-08-20 | Ncr Corporation | Method and apparatus for dynamic discovery of data model allowing customization of consumer applications accessing privacy data |
US20020131445A1 (en) * | 2000-11-22 | 2002-09-19 | Janez Skubic | System and method for anonymous bluetooth devices |
US20020147912A1 (en) * | 2000-10-27 | 2002-10-10 | Shimon Shmueli | Preference portability for computing |
US6473609B1 (en) * | 1995-12-11 | 2002-10-29 | Openwave Systems Inc. | Method and architecture for interactive two-way communication devices to interact with a network |
US6480850B1 (en) * | 1998-10-02 | 2002-11-12 | Ncr Corporation | System and method for managing data privacy in a database management system including a dependently connected privacy data mart |
US20020174073A1 (en) * | 2001-05-21 | 2002-11-21 | Ian Nordman | Method and apparatus for managing and enforcing user privacy |
US6496931B1 (en) * | 1998-12-31 | 2002-12-17 | Lucent Technologies Inc. | Anonymous web site user information communication method |
US20030087652A1 (en) * | 2001-04-13 | 2003-05-08 | Daniel Simon | Method and system to facilitate interaction between and content delivery to users of a wireless communications network |
US6571289B1 (en) * | 1998-08-03 | 2003-05-27 | Sun Microsystems, Inc. | Chained registrations for mobile IP |
US20030100315A1 (en) * | 2001-11-24 | 2003-05-29 | Koninklijke Philips Electronics | Location based delivery of service data |
US20030105719A1 (en) * | 2001-11-30 | 2003-06-05 | International Business Machines Corporation | Information content distribution based on privacy and/or personal information |
US6611501B1 (en) * | 1996-08-12 | 2003-08-26 | British Telecommunications Public Limited Company | Process management system |
US6647270B1 (en) * | 1999-09-10 | 2003-11-11 | Richard B. Himmelstein | Vehicletalk |
US6678516B2 (en) * | 2001-05-21 | 2004-01-13 | Nokia Corporation | Method, system, and apparatus for providing services in a privacy enabled mobile and Ubicom environment |
US6690918B2 (en) * | 2001-01-05 | 2004-02-10 | Soundstarts, Inc. | Networking by matching profile information over a data packet-network and a local area network |
US6750883B1 (en) * | 2000-04-05 | 2004-06-15 | Microsoft Corporation | Identity-based context aware computing systems and methods |
US6782253B1 (en) * | 2000-08-10 | 2004-08-24 | Koninklijke Philips Electronics N.V. | Mobile micro portal |
US6798358B2 (en) * | 2001-07-03 | 2004-09-28 | Nortel Networks Limited | Location-based content delivery |
US6982962B1 (en) * | 2000-04-10 | 2006-01-03 | 3Com Corporation | System and method for selecting a network access provider using a portable information device |
-
2001
- 2001-04-04 US US09/824,781 patent/US20020147766A1/en not_active Abandoned
-
2002
- 2002-04-03 AU AU2002253424A patent/AU2002253424A1/en not_active Abandoned
- 2002-04-03 WO PCT/IB2002/001066 patent/WO2002082205A2/en not_active Application Discontinuation
- 2002-04-03 EP EP02722539A patent/EP1405197A2/en not_active Withdrawn
Patent Citations (70)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4969096A (en) * | 1988-04-08 | 1990-11-06 | New England Medical Center | Method for selecting communication devices for non-speaking patients |
US5237157A (en) * | 1990-09-13 | 1993-08-17 | Intouch Group, Inc. | Kiosk apparatus and method for point of preview and for compilation of market data |
US5963916A (en) * | 1990-09-13 | 1999-10-05 | Intouch Group, Inc. | Network apparatus and method for preview of music products and compilation of market data |
US5722418A (en) * | 1993-08-30 | 1998-03-03 | Bro; L. William | Method for mediating social and behavioral processes in medicine and business through an interactive telecommunications guidance system |
US5873068A (en) * | 1994-06-14 | 1999-02-16 | New North Media Inc. | Display based marketing message control system and method |
US5835087A (en) * | 1994-11-29 | 1998-11-10 | Herz; Frederick S. M. | System for generation of object profiles for a system for customized electronic identification of desirable objects |
US5754938A (en) * | 1994-11-29 | 1998-05-19 | Herz; Frederick S. M. | Pseudonymous server for system for customized electronic identification of desirable objects |
US5754939A (en) * | 1994-11-29 | 1998-05-19 | Herz; Frederick S. M. | System for generation of user profiles for a system for customized electronic identification of desirable objects |
US6029195A (en) * | 1994-11-29 | 2000-02-22 | Herz; Frederick S. M. | System for customized electronic identification of desirable objects |
US5743054A (en) * | 1994-12-30 | 1998-04-28 | Steelcase Inc. | Modular utilities cover |
US5982891A (en) * | 1995-02-13 | 1999-11-09 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5917912A (en) * | 1995-02-13 | 1999-06-29 | Intertrust Technologies Corporation | System and methods for secure transaction management and electronic rights protection |
US5949876A (en) * | 1995-02-13 | 1999-09-07 | Intertrust Technologies Corporation | Systems and methods for secure transaction management and electronic rights protection |
US5910987A (en) * | 1995-02-13 | 1999-06-08 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5915019A (en) * | 1995-02-13 | 1999-06-22 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5710884A (en) * | 1995-03-29 | 1998-01-20 | Intel Corporation | System for automatically updating personal profile server with updates to additional user information gathered from monitoring user's electronic consuming habits generated on computer during use |
US5901246A (en) * | 1995-06-06 | 1999-05-04 | Hoffberg; Steven M. | Ergonomic man-machine interface incorporating adaptive pattern recognition based control system |
US6473609B1 (en) * | 1995-12-11 | 2002-10-29 | Openwave Systems Inc. | Method and architecture for interactive two-way communication devices to interact with a network |
US5855008A (en) * | 1995-12-11 | 1998-12-29 | Cybergold, Inc. | Attention brokerage |
US6061789A (en) * | 1996-01-12 | 2000-05-09 | International Business Machines Corporation | Secure anonymous information exchange in a network |
US6047327A (en) * | 1996-02-16 | 2000-04-04 | Intel Corporation | System for distributing electronic information to a targeted group of users |
US5899025A (en) * | 1996-03-22 | 1999-05-04 | Steelcase Inc. | Furniture system (pathways-spaceframe) |
US5815665A (en) * | 1996-04-03 | 1998-09-29 | Microsoft Corporation | System and method for providing trusted brokering services over a distributed network |
US5848396A (en) * | 1996-04-26 | 1998-12-08 | Freedom Of Information, Inc. | Method and apparatus for determining behavioral profile of a computer user |
US6091518A (en) * | 1996-06-28 | 2000-07-18 | Fuji Xerox Co., Ltd. | Image transfer apparatus, image transmitter, profile information transmitter, image receiver/reproducer, storage medium, image receiver, program transmitter, and image color correction apparatus |
US5987440A (en) * | 1996-07-22 | 1999-11-16 | Cyva Research Corporation | Personal information security and exchange tool |
US6611501B1 (en) * | 1996-08-12 | 2003-08-26 | British Telecommunications Public Limited Company | Process management system |
US5892900A (en) * | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5852775A (en) * | 1996-09-12 | 1998-12-22 | Earthweb, Inc. | Cellular telephone advertising system |
US6088598A (en) * | 1996-12-17 | 2000-07-11 | Telefonaktiebolaget L M Ericsson | Method and system for displaying greetings in a mobile radio communications system |
US5796952A (en) * | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US5974398A (en) * | 1997-04-11 | 1999-10-26 | At&T Corp. | Method and apparatus enabling valuation of user access of advertising carried by interactive information and entertainment services |
US6266704B1 (en) * | 1997-05-30 | 2001-07-24 | The United States Of America As Represented By The Secretary Of The Navy | Onion routing network for securely moving data through communication networks |
US6041325A (en) * | 1997-10-09 | 2000-03-21 | Alcatel Usa Sourcing, L.P. | System and method for controlling access to a telephony database |
US6026438A (en) * | 1997-10-31 | 2000-02-15 | Merrill Lynch & Co., Inc. | Dynamic workstation configuration processor |
US6141760A (en) * | 1997-10-31 | 2000-10-31 | Compaq Computer Corporation | System and method for generating unique passwords |
US6112181A (en) * | 1997-11-06 | 2000-08-29 | Intertrust Technologies Corporation | Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information |
US6023510A (en) * | 1997-12-24 | 2000-02-08 | Philips Electronics North America Corporation | Method of secure anonymous query by electronic messages transported via a public network and method of response |
US6133912A (en) * | 1998-05-04 | 2000-10-17 | Montero; Frank J. | Method of delivering information over a communication network |
US6154778A (en) * | 1998-05-19 | 2000-11-28 | Hewlett-Packard Company | Utility-based multi-category quality-of-service negotiation in distributed systems |
US6571289B1 (en) * | 1998-08-03 | 2003-05-27 | Sun Microsystems, Inc. | Chained registrations for mobile IP |
US6115709A (en) * | 1998-09-18 | 2000-09-05 | Tacit Knowledge Systems, Inc. | Method and system for constructing a knowledge profile of a user having unrestricted and restricted access portions according to respective levels of confidence of content of the portions |
US6154783A (en) * | 1998-09-18 | 2000-11-28 | Tacit Knowledge Systems | Method and apparatus for addressing an electronic document for transmission over a network |
US20010011247A1 (en) * | 1998-10-02 | 2001-08-02 | O'flaherty Kenneth W. | Privacy-enabled loyalty card system and method |
US6253203B1 (en) * | 1998-10-02 | 2001-06-26 | Ncr Corporation | Privacy-enhanced database |
US6480850B1 (en) * | 1998-10-02 | 2002-11-12 | Ncr Corporation | System and method for managing data privacy in a database management system including a dependently connected privacy data mart |
US6438544B1 (en) * | 1998-10-02 | 2002-08-20 | Ncr Corporation | Method and apparatus for dynamic discovery of data model allowing customization of consumer applications accessing privacy data |
US6134548A (en) * | 1998-11-19 | 2000-10-17 | Ac Properties B.V. | System, method and article of manufacture for advanced mobile bargain shopping |
US6374359B1 (en) * | 1998-11-19 | 2002-04-16 | International Business Machines Corporation | Dynamic use and validation of HTTP cookies for authentication |
US6496931B1 (en) * | 1998-12-31 | 2002-12-17 | Lucent Technologies Inc. | Anonymous web site user information communication method |
US6389533B1 (en) * | 1999-02-05 | 2002-05-14 | Intel Corporation | Anonymity server |
US6317718B1 (en) * | 1999-02-26 | 2001-11-13 | Accenture Properties (2) B.V. | System, method and article of manufacture for location-based filtering for shopping agent in the physical world |
US6226589B1 (en) * | 1999-03-12 | 2001-05-01 | Fujitsu Limited | System for providing guiding information for use in detecting and accessing a mobile object |
US6647270B1 (en) * | 1999-09-10 | 2003-11-11 | Richard B. Himmelstein | Vehicletalk |
US20010014911A1 (en) * | 2000-02-14 | 2001-08-16 | Kabushiki Kaisha Toshiba | Service providing method and system |
US6750883B1 (en) * | 2000-04-05 | 2004-06-15 | Microsoft Corporation | Identity-based context aware computing systems and methods |
US6982962B1 (en) * | 2000-04-10 | 2006-01-03 | 3Com Corporation | System and method for selecting a network access provider using a portable information device |
US20010028304A1 (en) * | 2000-04-11 | 2001-10-11 | I'anson Colin | Monitoring of location-associated events |
US6782253B1 (en) * | 2000-08-10 | 2004-08-24 | Koninklijke Philips Electronics N.V. | Mobile micro portal |
US20020147912A1 (en) * | 2000-10-27 | 2002-10-10 | Shimon Shmueli | Preference portability for computing |
US20020131445A1 (en) * | 2000-11-22 | 2002-09-19 | Janez Skubic | System and method for anonymous bluetooth devices |
US20020069117A1 (en) * | 2000-12-01 | 2002-06-06 | Carothers Christopher D. | Peer-to-peer electronic marketplace and systems and methods for conducting transactions therein |
US6690918B2 (en) * | 2001-01-05 | 2004-02-10 | Soundstarts, Inc. | Networking by matching profile information over a data packet-network and a local area network |
US20020107634A1 (en) * | 2001-02-06 | 2002-08-08 | Sergio Luciani | Traffic monitoring system and method |
US20030087652A1 (en) * | 2001-04-13 | 2003-05-08 | Daniel Simon | Method and system to facilitate interaction between and content delivery to users of a wireless communications network |
US6678516B2 (en) * | 2001-05-21 | 2004-01-13 | Nokia Corporation | Method, system, and apparatus for providing services in a privacy enabled mobile and Ubicom environment |
US20020174073A1 (en) * | 2001-05-21 | 2002-11-21 | Ian Nordman | Method and apparatus for managing and enforcing user privacy |
US6798358B2 (en) * | 2001-07-03 | 2004-09-28 | Nortel Networks Limited | Location-based content delivery |
US20030100315A1 (en) * | 2001-11-24 | 2003-05-29 | Koninklijke Philips Electronics | Location based delivery of service data |
US20030105719A1 (en) * | 2001-11-30 | 2003-06-05 | International Business Machines Corporation | Information content distribution based on privacy and/or personal information |
Cited By (149)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8892495B2 (en) | 1991-12-23 | 2014-11-18 | Blanding Hovenweep, Llc | Adaptive pattern recognition based controller apparatus and method and human-interface therefore |
US8364136B2 (en) | 1999-02-01 | 2013-01-29 | Steven M Hoffberg | Mobile system, a method of operating mobile system and a non-transitory computer readable medium for a programmable control of a mobile system |
US8369967B2 (en) | 1999-02-01 | 2013-02-05 | Hoffberg Steven M | Alarm system controller and a method for controlling an alarm system |
US10361802B1 (en) | 1999-02-01 | 2019-07-23 | Blanding Hovenweep, Llc | Adaptive pattern recognition based control system and method |
US9535563B2 (en) | 1999-02-01 | 2017-01-03 | Blanding Hovenweep, Llc | Internet appliance system and method |
US10224039B2 (en) | 1999-07-23 | 2019-03-05 | Tamiras Per Pte. Ltd., Llc | Providing access with a portable device and voice commands |
US8648692B2 (en) | 1999-07-23 | 2014-02-11 | Seong Sang Investments Llc | Accessing an automobile with a transponder |
US9406300B2 (en) | 1999-07-23 | 2016-08-02 | Tamiras Per Pte. Ltd., Llc | Accessing an automobile with a transponder |
US7092723B2 (en) | 1999-09-10 | 2006-08-15 | Richard Himmelstein | System and method for communicating between mobile units |
US8565734B2 (en) | 1999-09-10 | 2013-10-22 | Seong Sang Investments Llc | Advanced wireless vehicle services |
US10182319B2 (en) | 1999-09-10 | 2019-01-15 | Intellectual Ventures Ii Llc | Security and safety processing by a vehicle based computer |
US20040067752A1 (en) * | 1999-09-10 | 2004-04-08 | Himmelstein Richard B. | Vehicletalk |
US7505772B2 (en) | 1999-09-10 | 2009-03-17 | Richard B Himmelstein | System and method for location-based user matching |
US20040145459A1 (en) * | 1999-09-10 | 2004-07-29 | Himmelstein Richard B. | System and method for providing information to users based on the user's location |
US7463896B2 (en) | 1999-09-10 | 2008-12-09 | Himmelstein Richard B | System and method for enforcing a vehicle code |
US20040162064A1 (en) * | 1999-09-10 | 2004-08-19 | Himmelstein Richard B. | System and method for matching users based on proximity and/or user-defined profiles |
US7747291B2 (en) | 1999-09-10 | 2010-06-29 | Himmelstein Richard B | Wireless communication method |
US7783304B2 (en) | 1999-09-10 | 2010-08-24 | Himmelstein Richard B | Wireless communication method |
US9326119B2 (en) | 1999-09-10 | 2016-04-26 | Tamiras Per. Pte. Ltd., LLC | Communications between a mobile device and vehicle based computer |
US7450955B2 (en) | 1999-09-10 | 2008-11-11 | Himmelstein Richard B | System and method for tracking vehicle maintenance information |
US7885685B2 (en) | 1999-09-10 | 2011-02-08 | Himmelstein Richard B | Wireless communication method |
US7907976B2 (en) | 1999-09-10 | 2011-03-15 | Himmelstein Richard B | VehicleTalk |
US7536189B2 (en) | 1999-09-10 | 2009-05-19 | Himmelstein Richard B | System and method for sending broadcasts in a social network |
US20080146248A1 (en) * | 1999-09-10 | 2008-06-19 | Himmelstein Richard B | Location dependent user matching |
US20080119212A1 (en) * | 1999-09-10 | 2008-05-22 | Himmelstein Richard B | System and method for communicating between mobile units |
US7123926B2 (en) | 1999-09-10 | 2006-10-17 | Himmelstein Richard B | System and method for providing information to users based on the user's location |
US8600422B2 (en) | 1999-09-10 | 2013-12-03 | Seong Sang Investments Llc | Locating a target unit in a wireless network |
US20070082678A1 (en) * | 1999-09-10 | 2007-04-12 | Himmelstein Richard B | Vehicletalk |
US8224346B2 (en) | 1999-09-10 | 2012-07-17 | Himmelstein Richard B | System and method for matching users in a wireless communication system |
US20070054677A1 (en) * | 1999-09-10 | 2007-03-08 | Himmelstein Richard B | System and Method for Enforcing a Vehicle Code |
US20040148404A1 (en) * | 2001-04-19 | 2004-07-29 | Hideki Muroya | Apparatus and method for connecting appartuses using radio link, method for creating usable scene table for apparatus connection, and recording medium |
US6678516B2 (en) * | 2001-05-21 | 2004-01-13 | Nokia Corporation | Method, system, and apparatus for providing services in a privacy enabled mobile and Ubicom environment |
US7340438B2 (en) | 2001-05-21 | 2008-03-04 | Nokia Corporation | Method and apparatus for managing and enforcing user privacy |
US20020173296A1 (en) * | 2001-05-21 | 2002-11-21 | Ian Nordman | Method, system, and apparatus for providing services in a privacy enabled mobile and ubicom environment |
US20020196280A1 (en) * | 2001-06-25 | 2002-12-26 | International Business Machines Corporation | Method, system, and program for accessing calendar information for shadowed users from a database |
US7340691B2 (en) | 2001-06-25 | 2008-03-04 | International Business Machines Corporation | Method, system, and program for accessing calendar information for shadowed users from a database |
US7120695B2 (en) * | 2001-08-23 | 2006-10-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for limiting conveyance information of user profile within mobile Internet transactions |
US20030041100A1 (en) * | 2001-08-23 | 2003-02-27 | Mikael Nilsson | Method for limiting conveyance information of user profile within mobile internet transactions |
US20040236590A1 (en) * | 2001-08-29 | 2004-11-25 | Visser Michael Maria | Method and system for simplifying activation of a device and a device activated acccording to such method |
US20030069899A1 (en) * | 2001-10-04 | 2003-04-10 | International Business Machines Corporation | Method, system, and program for providing personal preference information when scheduling events |
US20030104820A1 (en) * | 2001-12-04 | 2003-06-05 | Greene David P. | Location-specific messaging system |
US6879835B2 (en) * | 2001-12-04 | 2005-04-12 | International Business Machines Corporation | Location-specific messaging system |
US20030131023A1 (en) * | 2002-01-08 | 2003-07-10 | International Business Machines Corporation | Method, system, and program for providing information on users of wireless devices in a database to a personal information manager |
US7996888B2 (en) * | 2002-01-11 | 2011-08-09 | Nokia Corporation | Virtual identity apparatus and method for using same |
US20030172090A1 (en) * | 2002-01-11 | 2003-09-11 | Petri Asunmaa | Virtual identity apparatus and method for using same |
US9497311B2 (en) | 2002-02-04 | 2016-11-15 | Nokia Technologies Oy | System and method for multimodal short-cuts to digital services |
US10291760B2 (en) | 2002-02-04 | 2019-05-14 | Nokia Technologies Oy | System and method for multimodal short-cuts to digital services |
US20040176958A1 (en) * | 2002-02-04 | 2004-09-09 | Jukka-Pekka Salmenkaita | System and method for multimodal short-cuts to digital sevices |
US9374451B2 (en) * | 2002-02-04 | 2016-06-21 | Nokia Technologies Oy | System and method for multimodal short-cuts to digital services |
US9286603B2 (en) * | 2002-02-27 | 2016-03-15 | Oneempower Pte Ltd | Activity management method |
US20030163427A1 (en) * | 2002-02-27 | 2003-08-28 | Nicholas Ho Chung Fung | Activity management method |
US7353184B2 (en) * | 2002-03-07 | 2008-04-01 | Hewlett-Packard Development Company, L.P. | Customer-side market segmentation |
US20030171975A1 (en) * | 2002-03-07 | 2003-09-11 | Evan R. Kirshenbaum | Customer-side market segmentation |
WO2004023326A1 (en) * | 2002-09-09 | 2004-03-18 | Atitania Ltd. | Method and apparatus for generating unique id packets in a distributed processing system |
US20060053090A1 (en) * | 2002-11-27 | 2006-03-09 | Paul Cotter | Personalising content provided to a user |
US20110252297A1 (en) * | 2002-11-27 | 2011-10-13 | Amdocs Software Systems Limited | Personalising content provided to a user |
US7987426B2 (en) * | 2002-11-27 | 2011-07-26 | Amdocs Software Systems Limited | Personalising content provided to a user |
US9323849B2 (en) * | 2002-11-27 | 2016-04-26 | Amdocs Software Systems Limited | Personalising content provided to a user |
WO2004080046A1 (en) * | 2003-01-09 | 2004-09-16 | Motorola, Inc. | Preselection of resources in a personal area network |
US20040137925A1 (en) * | 2003-01-09 | 2004-07-15 | Jason Lowe | Preselection of resources in a personal area network |
US20040205125A1 (en) * | 2003-02-14 | 2004-10-14 | Fuji Xerox Co., Ltd.. | Apparatus, method and program for supporting conversation, and conversation supporting system |
US7444377B2 (en) * | 2003-02-14 | 2008-10-28 | Fuji Xerox Co., Ltd. | Apparatus, method and program for supporting conversation, and conversation supporting system |
US7783879B2 (en) * | 2003-11-20 | 2010-08-24 | Nokia Corporation | Method and device relating to security in a radio communication network |
US20070082732A1 (en) * | 2003-11-20 | 2007-04-12 | Holger Krummel | A method and device relating to security in a radio communication network |
US20110145570A1 (en) * | 2004-04-22 | 2011-06-16 | Fortress Gb Ltd. | Certified Abstracted and Anonymous User Profiles For Restricted Network Site Access and Statistical Social Surveys |
EP1745590A4 (en) * | 2004-04-22 | 2008-11-26 | Fortress Gb Ltd | Certified abstracted and anonymous user profiles for restricted network site access and statistical social surveys |
EP1745590A2 (en) * | 2004-04-22 | 2007-01-24 | Fortress GB Ltd. | Certified abstracted and anonymous user profiles for restricted network site access and statistical social surveys |
US20060198448A1 (en) * | 2005-03-01 | 2006-09-07 | Selim Aissi | Techniques to manage wireless connections |
US8102901B2 (en) * | 2005-03-01 | 2012-01-24 | Intel Corporation | Techniques to manage wireless connections |
US11659385B2 (en) * | 2005-03-22 | 2023-05-23 | Interdigital Ce Patent Holdings, Sas | Method and system for peer-to-peer enforcement |
US20180315086A1 (en) * | 2005-06-07 | 2018-11-01 | Oath Inc. | Remote mobile profile detection and modification |
US11436637B2 (en) * | 2005-06-07 | 2022-09-06 | Yahoo Assets Llc | Remote mobile profile detection and modification |
US7802099B2 (en) * | 2005-06-22 | 2010-09-21 | Apple Inc. | Method and apparatus for establishing a secure connection |
US20070050625A1 (en) * | 2005-06-22 | 2007-03-01 | Mitchell Douglas P | Method and apparatus for establishing a secure connection |
US20060294381A1 (en) * | 2005-06-22 | 2006-12-28 | Mitchell Douglas P | Method and apparatus for establishing a secure connection |
US7899469B2 (en) * | 2005-07-12 | 2011-03-01 | Qwest Communications International, Inc. | User defined location based notification for a mobile communications device systems and methods |
US9420453B2 (en) | 2005-07-12 | 2016-08-16 | Qwest Communications International Inc. | Correlating and mapping mobile device locations on a mobile device |
US20070015519A1 (en) * | 2005-07-12 | 2007-01-18 | Qwest Communications International Inc. | User defined location based notification for a mobile communications device systems and methods |
US9462462B2 (en) | 2005-07-12 | 2016-10-04 | Qwest Communications International Inc. | Providing location-based information to a user of a mobile communication device |
US9462461B2 (en) | 2005-07-12 | 2016-10-04 | Qwest Communications International Inc. | Correlating mobile device locations |
US20110081921A1 (en) * | 2005-07-12 | 2011-04-07 | Owest Communications International Inc. | User Defined Location Based Notification for a Mobile Communications Device Systems and Methods |
US8725173B2 (en) | 2005-07-12 | 2014-05-13 | Qwest Communications International Inc. | User defined location based notification for a mobile communications device systems and methods |
US11257502B2 (en) | 2005-08-17 | 2022-02-22 | Tamiras Per Pte. Ltd., Llc | Providing access with a portable device and voice commands |
US11830503B2 (en) | 2005-08-17 | 2023-11-28 | Tamiras Per Pte. Ltd., Llc | Providing access with a portable device and voice commands |
US9338249B2 (en) * | 2005-09-15 | 2016-05-10 | Google Technology Holdings, Inc. | Distributed user profile |
US20080288484A1 (en) * | 2005-09-15 | 2008-11-20 | Motorola, Inc. | Distributed User Profile |
WO2007037870A3 (en) * | 2005-09-15 | 2009-04-30 | Motorola Inc | Distributed user profile |
US20130007112A1 (en) * | 2006-02-21 | 2013-01-03 | Comtrol Corporation | System, method, and device for communicating with a field device |
US8958313B2 (en) | 2007-11-27 | 2015-02-17 | Zettics, Inc. | Method and apparatus for storing data on application-level activity and other user information to enable real-time multi-dimensional reporting about user of a mobile data network |
US8935381B2 (en) | 2007-11-27 | 2015-01-13 | Zettics, Inc. | Method and apparatus for real-time collection of information about application level activity and other user information on a mobile data network |
US20090138427A1 (en) * | 2007-11-27 | 2009-05-28 | Umber Systems | Method and apparatus for storing data on application-level activity and other user information to enable real-time multi-dimensional reporting about user of a mobile data network |
US8195661B2 (en) | 2007-11-27 | 2012-06-05 | Umber Systems | Method and apparatus for storing data on application-level activity and other user information to enable real-time multi-dimensional reporting about user of a mobile data network |
US8732170B2 (en) | 2007-11-27 | 2014-05-20 | Zettics, Inc. | Method and apparatus for real-time multi-dimensional reporting and analyzing of data on application level activity and other user information on a mobile data network |
US8755297B2 (en) | 2007-11-27 | 2014-06-17 | Zettics, Inc. | System and method for collecting, reporting, and analyzing data on application-level activity and other user information on a mobile data network |
US10482484B2 (en) | 2007-12-14 | 2019-11-19 | John Nicholas And Kristin Gross Trust U/A/D April 13, 2010 | Item data collection systems and methods with social network integration |
US20130041754A1 (en) * | 2007-12-14 | 2013-02-14 | John Nicholas And Kristin Gross Trust U/A/D April 13, 2010 | Integrated Gourmet Item Data Collection, Recommender and Vending System and Method |
US20110288919A1 (en) * | 2007-12-14 | 2011-11-24 | John Nicholas Gross | Integrated Gourmet Item Data Collection, Recommender and Vending System and Method |
US8521580B2 (en) * | 2007-12-14 | 2013-08-27 | The John Nicholas and Kristin Gross Trust | Targeting promotional electronic coupons based on user item sampling ratings |
US9037515B2 (en) | 2007-12-14 | 2015-05-19 | John Nicholas and Kristin Gross | Social networking websites and systems for publishing sampling event data |
US8620736B2 (en) * | 2007-12-14 | 2013-12-31 | John Nicholas and Kristin Gross | Location-based promotions using data derived from item sampling events |
US7447996B1 (en) * | 2008-02-28 | 2008-11-04 | International Business Machines Corporation | System for using gender analysis of names to assign avatars in instant messaging applications |
US8775391B2 (en) | 2008-03-26 | 2014-07-08 | Zettics, Inc. | System and method for sharing anonymous user profiles with a third party |
US20150057027A1 (en) * | 2008-06-17 | 2015-02-26 | Nintendo Co., Ltd. | Information processing apparatus, information processing system, and storage medium having stored thereon information processing program |
US20100067695A1 (en) * | 2008-09-15 | 2010-03-18 | Yun-Wei Liao | Message processing apparatus and processing method thereof |
US8881266B2 (en) * | 2008-11-13 | 2014-11-04 | Palo Alto Research Center Incorporated | Enterprise password reset |
US20100122340A1 (en) * | 2008-11-13 | 2010-05-13 | Palo Alto Research Center Incorporated | Enterprise password reset |
US20100161804A1 (en) * | 2008-12-18 | 2010-06-24 | Electronics And Telecommunications Research Institute | System and method for providing device file using device identifier |
US8566448B2 (en) * | 2008-12-18 | 2013-10-22 | Electronics And Telecommunications Research Institute | System and method for providing device file using device identifier |
US20110313870A1 (en) * | 2009-10-13 | 2011-12-22 | Skycore LLC, | Initiating and Enabling Secure Contactless Transactions and Services with a Mobile Device |
JP2017215968A (en) * | 2009-12-30 | 2017-12-07 | ヘレ グローバル ベスローテン フェンノートシャップHERE Global B.V. | System and method for providing user control of user's network usage data and personal profile information |
US20110219423A1 (en) * | 2010-03-05 | 2011-09-08 | Nokia Corporation | Method and apparatus for triggering user communications based on privacy information |
US8838784B1 (en) | 2010-08-04 | 2014-09-16 | Zettics, Inc. | Method and apparatus for privacy-safe actionable analytics on mobile data usage |
US20120047457A1 (en) * | 2010-08-19 | 2012-02-23 | Samsung Electronics Co., Ltd. | Method and apparatus for searching contents |
WO2013137842A1 (en) * | 2011-01-24 | 2013-09-19 | Hewlett-Packard Development Company, L.P. | A system and method for accessing a service |
US9590997B2 (en) * | 2011-01-24 | 2017-03-07 | Hewlett Packard Enterprise Development Lp | System and method for accessing a service |
CN103415847A (en) * | 2011-01-24 | 2013-11-27 | 惠普发展公司,有限责任合伙企业 | A system and method for accessing a service |
US20140157434A1 (en) * | 2011-01-24 | 2014-06-05 | David Andrew Graves | System and method for accessing a service |
US10178103B2 (en) | 2011-01-24 | 2019-01-08 | Hewlett Packard Enterprise Development Lp | System and method for accessing a service |
US20140006512A1 (en) * | 2011-03-22 | 2014-01-02 | Telefonaktiebolaget L M Ericsson (Publ) | Methods for Exchanging User Profile, Profile Mediator Device, Agents, Computer Programs and Computer Program Products |
US20140236903A1 (en) * | 2012-09-24 | 2014-08-21 | Andrew L. DiRienzo | Multi-component profiling systems and methods |
US11921669B2 (en) | 2012-09-24 | 2024-03-05 | Airedites, Llc | Computer systems and processes configured to identify behavioral, action, activity, and/or emotional states of a person and to respond to the identity of the states |
US11663158B2 (en) | 2012-09-24 | 2023-05-30 | Andrew L. DiRienzo | Empirical data gathered by ambient computer observation of a person are analyzed to identify an instance of a particular behavior and to respond to its identification |
US9607025B2 (en) * | 2012-09-24 | 2017-03-28 | Andrew L. DiRienzo | Multi-component profiling systems and methods |
US11216410B2 (en) | 2012-09-24 | 2022-01-04 | Andrew L. DiRienzo | Empirical data gathered by ambient computer observation of a person are analyzed to identify an instance of a particular behavior |
US10614029B2 (en) | 2012-09-24 | 2020-04-07 | Andrew L. DiRienzo | Empirical data gathered by ambient observation of a person are correlated vis-à-vis one particular behavior |
WO2014064538A3 (en) * | 2012-10-12 | 2014-09-04 | Freedomone Mobile, Inc. | Systems and methods for subscription management in a multi-channel context aware communication environment |
WO2014064538A2 (en) * | 2012-10-12 | 2014-05-01 | Freedomone Mobile, Inc. | Systems and methods for subscription management in a multi-channel context aware communication environment |
US20140298214A1 (en) * | 2013-03-29 | 2014-10-02 | Microsoft Corporation | Visual Configuration and Activation |
US10656800B2 (en) * | 2013-03-29 | 2020-05-19 | Microsoft Technology Licensing, Llc | Visual configuration and activation |
US10452222B2 (en) | 2013-05-29 | 2019-10-22 | Microsoft Technology Licensing, Llc | Coordination of system readiness tasks |
US20150256515A1 (en) * | 2014-03-06 | 2015-09-10 | Samsung Electronics Co., Ltd. | Proximity communication method and apparatus |
US10554627B2 (en) * | 2014-03-06 | 2020-02-04 | Samsung Electronics Co., Ltd. | Proximity communication method and apparatus |
US9589040B2 (en) * | 2014-06-27 | 2017-03-07 | At&T Intellectual Property I, L.P. | Method and apparatus for subscriber management |
US11119859B2 (en) | 2014-06-27 | 2021-09-14 | At&T Intellectual Property I, L.P. | Method and apparatus for subscriber management |
US10031812B2 (en) | 2014-06-27 | 2018-07-24 | At&T Intellectual Property I, L.P. | Method and apparatus for subscriber management |
US20150379101A1 (en) * | 2014-06-27 | 2015-12-31 | At&T Intellectual Property I, Lp | Method and apparatus for subscriber management |
US10193943B2 (en) | 2015-11-09 | 2019-01-29 | T-Mobile Usa, Inc. | Data-plan-based quality setting suggestions and use thereof to manage content provider services |
US10721283B2 (en) * | 2015-11-09 | 2020-07-21 | T-Mobile Usa, Inc. | Data-plan-based quality setting suggestions and use thereof to manage content provider services |
US11297118B2 (en) | 2015-11-09 | 2022-04-05 | T-Mobile Usa, Inc. | Data-plan-based quality setting suggestions and use thereof to manage content provider services |
US20190141103A1 (en) * | 2015-11-09 | 2019-05-09 | T-Mobile Usa, Inc. | Data-Plan-Based Quality Setting Suggestions and Use Thereof to Manage Content Provider Services |
US10305952B2 (en) * | 2015-11-09 | 2019-05-28 | T-Mobile Usa, Inc. | Preference-aware content streaming |
US10728152B2 (en) | 2016-02-08 | 2020-07-28 | T-Mobile Usa, Inc. | Dynamic network rate control |
CN108886517A (en) * | 2016-03-18 | 2018-11-23 | T移动美国公司 | Know the stream content of preference |
WO2017160425A1 (en) * | 2016-03-18 | 2017-09-21 | T-Mobile Usa, Inc. | Preference-aware content streaming |
US10769306B2 (en) * | 2017-09-21 | 2020-09-08 | International Business Machines Corporation | Applying a differential privacy operation on a cluster of data |
US20190087604A1 (en) * | 2017-09-21 | 2019-03-21 | International Business Machines Corporation | Applying a differential privacy operation on a cluster of data |
US10572531B1 (en) * | 2017-10-25 | 2020-02-25 | Amazon Technologies, Inc. | Predictive session-based search engine |
US20230076960A1 (en) * | 2021-09-03 | 2023-03-09 | Bi Science (2009) Ltd | System and a method for multisession analysis |
US11711419B2 (en) * | 2021-09-03 | 2023-07-25 | Bi Science (2009) Ltd | System and a method for multisession analysis |
Also Published As
Publication number | Publication date |
---|---|
AU2002253424A1 (en) | 2002-10-21 |
EP1405197A2 (en) | 2004-04-07 |
WO2002082205A2 (en) | 2002-10-17 |
WO2002082205A3 (en) | 2003-05-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20020147766A1 (en) | Operating user profiles with distributed profile model using a hybrid terminal | |
US7340438B2 (en) | Method and apparatus for managing and enforcing user privacy | |
US6678516B2 (en) | Method, system, and apparatus for providing services in a privacy enabled mobile and Ubicom environment | |
US9955292B2 (en) | Location-based novelty index value and recommendation system and method | |
Varshney | Location management for mobile commerce applications in wireless internet environment | |
AU2011201041B2 (en) | Mobile computing and communication | |
Siau et al. | Mobile communications and mobile services | |
US7117266B2 (en) | Method for providing user-apparent consistency in a wireless device | |
US7222154B2 (en) | Negotiated wireless peripheral systems | |
US8725851B2 (en) | Contextual data communication platform | |
US20070060117A1 (en) | Short-range wireless architecture | |
US20040015403A1 (en) | Method, system, and business method for wireless fast business | |
US20030018524A1 (en) | Method for marketing and selling products to a user of a wireless device | |
US7737914B2 (en) | Information system | |
AU2002236938A1 (en) | Mobile computing and communication | |
JP2004139525A (en) | System and method for providing personal information | |
US20030088647A1 (en) | Communication process for retrieving information for a computer | |
Siau et al. | Mobile commerce: Current states and future trends | |
Dursch et al. | Bluetooth technology: an exploratory study of the analysis and implementation frameworks | |
WO2008101289A1 (en) | A system and method for a registered user based telecommunications network | |
KR20030024744A (en) | Advertising method using mobile unit | |
Mishra | M-Commerce and It's Issues | |
Sofokleous et al. | Mobile computing: technology challenges, constraints, and standards | |
WO2003009158A1 (en) | Short-range wireless architecture |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOKIA CORPORATION, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VANSKA, MARKO;NORDMAN, IAN;KLEMETTINEN, MIKA;AND OTHERS;REEL/FRAME:012131/0828;SIGNING DATES FROM 20010723 TO 20010813 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |