WO2005122013A1 - ユーザプロファイル管理システム - Google Patents
ユーザプロファイル管理システム Download PDFInfo
- Publication number
- WO2005122013A1 WO2005122013A1 PCT/JP2005/010658 JP2005010658W WO2005122013A1 WO 2005122013 A1 WO2005122013 A1 WO 2005122013A1 JP 2005010658 W JP2005010658 W JP 2005010658W WO 2005122013 A1 WO2005122013 A1 WO 2005122013A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- user profile
- profile
- situation
- status
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Definitions
- the present invention relates to a technique for generating a user profile.
- Patent Document 1 provides a user profile construction system and method for integrating user profiles generated on a plurality of servers in a central server and providing the profiles to another server as necessary. ing.
- a user profile generated for a user by a certain service server can be used by another service server, and the quality of the personalized service can be improved.
- a user profile varies greatly depending on the situation of the user when the user profile was generated.
- the information required by the user differs between work and home, so the user profile inevitably differs.
- the occurrence status of the user profile is closely related to the user profile file. Therefore, a user profile generated ignoring the occurrence situation has poor effectiveness and is not easily used.
- work-related information such as IT-related information.
- on vacation the user preferentially collects information on hobbies and entertainment, for example, information on music and travel.
- the user profile varies depending on the situation of the user.
- Patent Document 1 monitors which category of content or service has been used for how long, how frequently the content or service has been used, and based on the results, weights the user profiles collected from each Sano and integrates them. The method of doing it is taken. With this, although it is possible to use information such as the time when the user profile was generated and the category of the content used by the user, it monitors the user status independent of applications and services, and manages the user profile. It is difficult to use for
- the present invention provides a technology that enables generation of a user profile and use of the generated user profile in consideration of a situation where a user is placed when the user profile is generated and when the user profile is used. With the goal.
- Patent Document 1 JP-T-2003-526824
- FIG. 1 shows a configuration of a user profile sharing system to which a management device according to a first embodiment of the present invention is applied.
- FIG. 4 is a conceptual explanatory diagram of situation data stored in a situation data table.
- FIG. 5 is a conceptual explanatory diagram of a user profile received by the management device.
- FIG. 8 is an explanatory diagram showing an example of the flow of a user profile acquisition process
- FIG. 9 is an explanatory diagram showing an example of the flow of a comprehensive user profile provision process
- FIG. 14 (a) Relevance data table in the first embodiment (b) Situation data tape table in the first embodiment
- FIG. 18 (a) Relevance data table in second embodiment (b) Status data tape table in second embodiment
- the user profile generated by the Web browser and its conversion (a) The user profile generated by the Web browser (b) The weighted and merged user profile ( c ) The user profile after format conversion Nore
- FIG. 20 A user profile generated by IM and its conversion in the second embodiment (a) A user profile generated by IM (b) A weighted and merged user profile (c) A user profile after format conversion Nore
- the user profile generated by the mailer and its conversion (a) The user profile generated by the mailer (b) The user profile after weighting and ontology conversion ( c ) format User profile after conversion
- Invention 1 provides a management device that is connected to a user terminal on which one or more arbitrary applications operate and collects a user profile from the user terminal.
- This device has the following means.
- a criterion storage means for storing a user situation criterion for determining a user situation
- Collection means for collecting and storing user profiles generated by the application
- 'User status management means for determining a current user status based on the user status criteria in response to the request
- Transmission means for transmitting the user profile generated by the user profile generation means to a request source.
- the comprehensive user profile is generated based on the user profile related to the situation when using the user profile, And provide a comprehensive user profile.
- Invention 2 provides the management device according to invention 1, wherein the user status management means further receives registration of a user status determination criterion. [0013] By registering a user's own user situation determination standard, the situation of each user can be accurately determined.
- the user status management unit determines the user status at the time of collection based on the user status determination criterion each time the profile collection unit collects a user profile.
- the collection means stores the user status determined by the user status management means in association with the collected user profile.
- the generating means extracts a user profile file corresponding to the current user situation, and generates the comprehensive user profile based on the extracted user profile.
- This management device stores the user status at the time of collecting the user profile and the user profile in association with each other. Therefore, the user situation at the time when the user profile was requested, that is, the user profile corresponding to the current user situation can be easily extracted.
- the user status management means provides a management device that stores a predetermined user status and predetermined link information in association with each other.
- the collecting means stores the collected user profile in association with the link information.
- the generating means extracts a user profile using the link information corresponding to the current user status as a key, and generates the comprehensive user profile based on the extracted user profile.
- Examples of the link information include time information and an application identifier.
- the application identifier is information for specifying an application. If the link information is time information, a time such as "9:00 to 17:00 is on duty", “17:00 to 19:00 is commuting", "19:00 to 7:00 is at home", etc. The band and the user status are associated with each other. If the link information is an application identifier, "9: 00-17: 00 is a web browser", “17: 00-19: 00 is a media player", "19: 00-7: 00 is an instant messenger", etc. The time zone is associated with the application identifier.
- the user profile at the time of requesting the user profile that is, the user profile corresponding to the current user status is stored. Isles can be extracted based on collection time. Specifically, if the current user status is “at home”, the user profiles collected between 19:00 and 7:00 are extracted, and based on this, the total user profile is extracted. Provide to requester.
- the user profile can be linked to the user status by the link information.
- Invention 5 provides the management device according to invention 1, wherein the user situation management means stores an association degree table that defines an association degree of a plurality of predetermined user situations.
- the generating means specifies another user situation (hereinafter, referred to as a related user situation) related to the current user situation from the association degree table and adds the user situation to the user profile related to the current user situation. Then, a user profile related to the related user situation is further extracted, and the comprehensive user profile is generated based on the extracted user profile.
- the total user profile can be made more useful. For example, assume that the predetermined user status is “working”, “commuting”, and “at home”. In this case, it is considered that the user state “working” and the user state “commuting” have a high degree of association. Conversely, the user statuses “at work” and “commuting” and the user status “at home” are considered to have little association. Such a degree of relevance of the user situation is defined in the degree of relation table. Since a user profile directly related to the current user situation is used instead of a user profile directly, it is possible to generate a more flexible and applicable general user profile.
- the generating means weights the user profiles extracted based on the degree of association between the current user status and the related user status, and based on each of the weighted user profiles.
- a management device for generating the comprehensive user profile is provided.
- the request receiving means provides a management device that receives the user profile request and a user profile format that can be interpreted by the application.
- the generating means converts the format of the generated general user portal file into the above format and transmits it.
- a description language of the comprehensive user profile, a tag name in the user profile, and the like are converted into a format according to each application.
- An ontology file can also be used for the conversion. This allows arbitrary applications to share a user profile.
- Invention 8 provides a management method that is connected to a user terminal on which one or more arbitrary applications operate and collects the user terminal power user profile. The method includes the following steps.
- a criterion storage step for storing a user situation criterion for determining a user situation
- This invention has the same functions and effects as the first invention.
- Invention 9 provides a management program that is connected to a user terminal on which one or more arbitrary applications operate, and causes a computer terminal to function as a management device that collects the user profile. This program uses this combination as the following means: Make the Utah terminal work.
- Criteria storage means for storing user status criteria for determining user status
- Collection means for collecting and storing user profiles generated by the application
- 'User status management means for determining a current user status based on the user status criteria in response to the request
- Transmission means for transmitting the user profile generated by the user profile generation means to a request source.
- the present invention has the same function and effect as the first invention.
- FIG. 1 shows a configuration of a user profile sharing system to which a management device according to the present invention is applied.
- the user profile sharing system includes a management device 100 and one or more applications 110a, b.
- the management device 100 receives a request from the application 110, generates a new user profile (hereinafter, referred to as a comprehensive user profile) based on the plurality of user profiles, and sends the generated new user profile to the application 110. provide.
- a comprehensive user profile Prior to the generation of the comprehensive profile, each of the plurality of applications 110 generates a user profile and registers it in the management device 100.
- the management device 100 constantly monitors the user status, and directly or indirectly associates the user status at the time of registering the user profile with the user profile. I remember it.
- the user status corresponding to the user status at the time of requesting the user profile or the user status specified by the application (hereinafter, the current user status including both) is used.
- the user profile corresponding to the current user situation is a user profile generated by any application in the same user situation as the current user situation.
- each application can perform a process that matches the current user status based on the comprehensive user profile. For example, consider the case where the application is a Web browser. If the current user status is “at home”, processing such as searching for Web pages related to the user's hobbies can be performed. On the other hand, if the current user status is “at work”, processing such as searching for a web page frequently used by a user at work becomes possible.
- a user profile is information relating to user preferences.
- the information included in the user profile is not limited to this.
- the user profile may include the user's movement history, human relationships, career, and the like.
- the user profile may be a dictionary file in which a user registers words in a text editing application. Further, the format of the user profile is not particularly limited.
- FIG. 1 shows a configuration of a user profile sharing system to which a management device according to a first embodiment of the present invention is applied.
- the user profile sharing system includes a management device 100, one or more applications 110a and 110b, and a data source 111.
- the application 110 operates on a computer terminal such as a personal computer, a mobile phone, a PDA (Personal Digital Assistant), or a GPS device. It communicates with the management device 100 via a network such as AN. The application 110 may exchange data with the management device 100 via a recording medium such as an SD card, a CF card, and a DVD.
- a computer terminal such as a personal computer, a mobile phone, a PDA (Personal Digital Assistant), or a GPS device. It communicates with the management device 100 via a network such as AN.
- the application 110 may exchange data with the management device 100 via a recording medium such as an SD card, a CF card, and a DVD.
- the application 110 generates a user profile in addition to the processing unique to the application, and provides the generated user profile to the management device 100. Further, the application 110 requests the user profile from the management device 100, acquires the user profile, and performs a process based on the acquired information.
- Such applications include, for example, web browsers, instant messengers (hereinafter, IM), and mailers.
- the data source 111 is a device or application that provides information about the user, and provides the management device 100 with basic information for determining a user situation. For example, a GPS device owned by a user, a sensor attached to an arbitrary place such as a ticket gate of a station or a meeting room of a company, and a scheduler containing a schedule of user actions can be cited as the data source 111. In this embodiment, it is assumed that the data source 111 exchanges data with the management device 100 via a network! /, But the data source 111 is located on the same terminal as the management device 100.
- a GPS device owned by a user
- a sensor attached to an arbitrary place such as a ticket gate of a station or a meeting room of a company
- a scheduler containing a schedule of user actions can be cited as the data source 111.
- the data source 111 exchanges data with the management device 100 via a network! /, But the data source 111 is located on the same terminal as the management device 100
- the management device 100 includes the following components (a) to (g).
- Knowledge database (DB) 101 (corresponding to a judgment criterion storage means): stores a user criterion judgment criterion for judging a user situation. The details of the user situation judgment criteria will be described later.
- User status management unit 102 (corresponding to a user status management means): Based on information from the data source 111 and a user status determination criterion, an ever-changing user status is determined each time. Further, the determined user status is written to the status data table 102a.
- User profile collection unit 103 (corresponding to collection means): collects the abbreviated data from the application 110. Further, the registration of the user situation criteria by the user may be accepted.
- Request receiving section 104 (corresponding to request receiving means): receives a request for a user profile from the application 110.
- User profile providing unit 105 (corresponding to generation means and transmission means): Stores a user profile that matches the user situation when the user profile was requested (hereinafter referred to as the current user situation). Based on the current user profile and provide it to the requester of the user profile.
- User profile management unit 106 (corresponding to a collection unit): Stores a user profile in the user profile DB 106a and reads it out.
- the user profile DB 106a stores the user profile generated by the application 110 in association with the user status at the time of generation.
- User status collection unit 107 Obtains information from data source 111 and passes it to user status management unit 102.
- the management device 100 having the above components is assumed to be realized as a service providing device on a user's home server or service server. However, it may be implemented as a service on a user's mobile terminal that does not necessarily need to be implemented on a fixed computer terminal. Note that all of the components 101 to 107 of the management device 100 do not need to be present on the same computer terminal. If desired, each component can be implemented on a different computer terminal. In such a case, it is preferable that each component can exchange data with each other through means such as a data communication network such as a LAN and the Internet.
- FIG. 2 is a conceptual explanatory diagram of the user situation determination criterion table 101a stored in the knowledge DB 101.
- Criteria data is registered in the user situation criteria table 101a.
- the criterion data is used by the user status management unit 102 to determine the user status.
- the default value of the criterion data may be set in advance in the user situation criterion table 10 la, it is preferable that the management device 100 accepts the registration of the user.
- the situation of each user can be finely and accurately determined based on the judgment reference data for each user.
- judgment criteria data is registered for each user. Think about when you are.
- the criterion data associates a user situation that can occur for the user with the state derivation data.
- three possible user situations are registered: "working", “commuting", and "home”.
- the user status may be represented by a UUID or a URI as long as the value can be uniquely identified in the management device 100, or may be a character string.
- the value of each user status can be arbitrarily determined by the user.
- situation derivation data associated with each user situation information that can be collected by the data resource 111 or time information that can be detected by the management device 100 is used.
- time zone of each user situation
- location information of the user at that time
- used terminal and “used application” used by the user are shown as the situation derived data. It is sufficient to use at least one that does not need to use the time period, the location information, the terminal used, and the application used as the situation-derived data.
- the situation-derived data is not limited to those listed here.
- a specific example of determining the user status using the user status determination criterion table 101a in FIG. 2 will be described. For example, it is assumed that information such as “location information: Kadoma”, “user terminal: notebook PC”, and “application used: Web browser” is collected from the data source 111 at the internal clock time 08:30 of the management device 100. In this case, the user status is determined to be “working”. Further, for example, the user status may be determined to be “working” based only on the time “08:30” of the internal clock of the management device 100. Further, priorities may be set for a plurality of situation derived data, and when the user situation indicated by each situation derived data does not match, the user situation may be determined according to the situation derived data having a higher priority.
- FIG. 3 is a conceptual explanatory diagram of a relevance data table 10 lb stored in the knowledge DB 101.
- Relevance data is registered in the relevance data table.
- the relevance data defines the relevance between user statuses registered in the user status determination criterion table 101a.
- the setting of the relevance data may be performed by the provider of the management device 100, but the management device 100 may accept the setting by the user.
- the user himself / herself registers the degree of association between each user situation included in the criterion data.
- the user status "working” is more relevant for the user status "commuting", while the user status "vacation” is less relevant for the user status "working”. Is set.
- the relevance data is used to extract the user profile generated in the relevant situation from the profile DB 106a.
- a related situation is another user situation that is related to the current user situation.
- the current user status is the user status when the application 110 requests the user profile.
- FIG. 4 is a conceptual explanatory diagram of the situation data stored in the situation data table 102a.
- the status data table 102a is preferably generated for each user.
- user situations determined by the user situation management unit 102 based on the criterion data and the information from the data source 111 are written one after another.
- the situation data includes a user situation and accompanying information related to the user situation.
- the user status is “Working” from 13:00 to 19:00 in 20004Z2Z3, “Commuting” from 19:00 to 21:00, and “At home” after 21:00. Indicates that there was.
- the date and time and the application used by the user at that time are stored.
- the accompanying information is not limited to this example. Any information that can be collected from the data source 111 can be included in the situation data as accompanying information. For example, location information and schedule information can be cited as other accompanying information. By including the accompanying information in the situation data, the user situation can be determined based on the accompanying information.
- the status data is used to determine which user status the user profile generated by the application 110 corresponds to, and to determine the current user status.
- FIG. 5 5 is a conceptual explanatory diagram of a user profile received by the management device 100.
- the user profile includes at least data, and in this example, further includes an update date and time and importance. “Severity” indicates the level of interest of the user in a specific category. The “update date and time” indicates time data at which the importance was updated.
- FIG. 6 is a conceptual explanatory diagram of information stored in profile DB 106a.
- the management device 100 when receiving the user profile exemplified in FIG. 5, the management device 100 stores the user status at the time of reception and the user profile in association with each other as shown in FIG. Figure 6 shows that user profiles related to IT and AV equipment were received during “work”, and user profiles related to Western music and skiing were received “on vacation”.
- the association between the user status at the time of reception and the user profile is almost the same as the user status at the time of generation of the user profile, and therefore, the user status at the time of generation of the user profile is associated with the user profile. It is because of, for example.
- the management device 100 roughly has three functions: (1) acquisition of a user status, (2) acquisition of a user profile, and (3) provision of a comprehensive user profile. Hereinafter, these functions will be sequentially described.
- the management device 100 collects information from the data source 111, and determines the user status at the time of collection based on the collected information and the criterion data. The determined user status is written to the status data table 102a.
- the user status collection unit 107 collects user information from the data source 111.
- the user information provided by the data source 111 include time information, position information, schedule information, nearby store information, nearby user information, and information on an application used by the user. Further, a user identifier for specifying a user may be included in the user information.
- the collected user information is passed from the user status collection unit 107 to the user status management unit 102.
- known means such as a mailer and an instant messenger (IM) can be used.
- IM instant messenger
- the user status management unit 102 compares the collected user information with the status derivation data of the criterion data, and determines the user status at the time of collection.
- the user situation management unit 102 determines situation data based on the format of the situation data table 102a.
- the determined user status is written to the status data table 102a. For example, when the format of the judgment reference data shown in FIG. 2 and the format of the situation data table 102a shown in FIG. 4 are given, the user information “ ⁇ . ( ⁇ And ⁇ ⁇ ! Then, the user status management unit 102 determines from the determination criterion data that the user status is “working.” The user status management unit 102 further determines the date and time “2004Z 4/2 9:00 ”, User status“ at work ”, and usage application“ Web browser ”are generated and registered in the status data table 102a.
- the management device 100 acquires a user profile generated by an arbitrary application 110, and stores the user profile in association with the user status at the time of acquisition.
- the user profile collection unit 103 of the management device 100 receives a user profile generated or updated by an arbitrary application 110 at an arbitrary timing. At this time, the management device 100 receives the generated Z update time information of the user profile and an application profile (hereinafter, referred to as an application profile) describing information on the application itself, together with the user profile.
- the user profile may include time information.
- the application profile includes an identifier of the application, a purpose of use, a usage environment such as an OS, a format of a usable user profile, information on a terminal on which the application is executed, and the like.
- the received user profile and application profile are passed from the user profile management unit 103 to the user profile management unit 106.
- the user profile collection unit 103 secures security such as authentication for the external application 110. It has a function for
- the user profile management unit 106 extracts data that the received information is sufficient to specify the user status, and passes the data to the user status management unit 102. For example, it is an application identifier or time information.
- the user status management unit 102 extracts corresponding status data from the status data table 102a based on the passed data, and returns the extracted status data to the user profile management unit 106.
- the user profile management unit 106 stores at least the user status in the returned status data in the profile DB 106a in association with the user profile.
- the user profile and the user status can be stored in the profile DB 106a in association with each other.
- a user profile may be associated with a plurality of user situations.
- the management device 100 In response to a request from an arbitrary application 110, the management device 100 generates a comprehensive user profile according to the user situation at the time of the request, and provides this to the request source.
- the request receiving unit 104 of the management device 100 receives an application profile of an application itself from an arbitrary application 110 at an arbitrary timing. Status data may be received along with the application profile.
- the request receiving unit 104 analyzes the data received from the application 110. When the received data includes the status data, the request receiving unit 104 passes the status data and the abli profile to the user profile providing unit 105 . This is because the user situation included in the received situation data may be regarded as the current user situation and the comprehensive user profile may be generated.
- the request receiving unit 104 inquires the current user status to the user status management unit 102.
- the user status management unit 102 extracts the latest status data from the status data table 102a and receives the request. Return to Appendix 104.
- the request receiving unit 104 passes the received status data and application profile to the user profile providing unit 105. This is because the latest user status included in the status data is regarded as the current user status, and a comprehensive user profile is generated.
- the user profile providing unit 105 specifies the user status included in the status data, and acquires the relevance data including the relevant status of the specified user status from the user status management unit 102.
- the user profile providing unit 105 requests the user profile management unit 106 for a user profile corresponding to the current user situation and the specified related situation.
- the user profile management unit 106 extracts a user profile corresponding to the current user situation and the related situation from the profile DB 106a, and passes it to the user profile providing unit 105. To generate a comprehensive user profile based on these
- the user profile management unit 106 passes these to the user profile providing unit 105.
- the user profile providing unit 105 weights the user profile obtained using the relevance data, and integrates the user profile corresponding to the current user status and the relevant status.
- FIG. 7 is an explanatory diagram showing an example of weighting a user profile using relevance data.
- Fig. 7 (a) shows a user profile corresponding to the related situation.
- Figure 7 (b) shows the integrated user profile.
- This figure shows an example in which the relevance data table 102a shown in FIG. 3 is given and the current user status is "commuting".
- other user statuses related to the user status "commuting” are "working” and “resting”
- “Working” has a relevance of "high”
- “during break” has a relevance of "small”. Therefore, the “importance” of the user profile corresponding to the user state “working” is increased by weighting.
- weighting for converting “low” to “medium” and “medium” to “high” is performed.
- the “importance” of the user profile corresponding to the user state “resting” is reduced by weighting. That is, weighting is performed to reduce “high” to “medium” and “medium” to “low”.
- the method of calculating the weights of the user profiles in this example is merely an example. Similarly, when generating a comprehensive user profile, the value of the current user status or the user profile corresponding to the relevant status is changed based on the relevance data.
- the user profile providing unit 105 converts the format of the integrated user profile based on the information described in the application profile, and generates a comprehensive user profile. This is because the integrated user profile is converted into a format that can be used by the requesting application 110. Thereafter, the user profile providing unit 105 transmits the general user profile to the request source application 110.
- FIG. 8 is an explanatory diagram showing an example of the flow of a user profile acquisition process.
- the application 110 generates a user profile (# 11) and sends it to the management device 100 together with the application profile (# 12).
- the management device 100 When receiving the user profile and the application profile (# 13), the management device 100 extracts data for specifying the user status at the time of reception (# 14). For example, the management device 100 extracts the time information and the identifier of the application, and reads out the situation data including the information from the situation data table 102a (# 15). Finally, the management device 100 associates the received user profile with at least the user status in the status data, and Store it in the file DB 106a (# 16).
- the received user profile is directly associated with the user status.
- FIG. 9 is an explanatory diagram showing an example of the flow of the provision process of the comprehensive user profile.
- the application 110 transmits a request for a user profile to the management device 100.
- the application profile is transmitted together with or in place of the request (# 21).
- the management device 100 When receiving the application profile (# 22), the management device 100 specifies situation data including the current user situation (# 23). Next, the management device 100 specifies relevance data including a relevant situation related to the current user situation (# 24). Further, the management device 100 reads a user profile corresponding to the current user situation and the related situation from the profile DB 106a (# 25), performs weighting and conversion, and generates a comprehensive user profile (# 26). Finally, the management device 100 transmits the generated total user profile to the request source application 110 (# 27, # 28).
- the user situation information can be sequentially monitored.
- the user profile collected from the application 110 can be stored in association with the situation of the user when the user profile was generated.
- a situation (related situation) related to a situation (current user situation) in which a user profile requested by an application is used is obtained based on the relevance data, whereby a comprehensive user profile suitable for the use situation of the user profile is obtained.
- the user profile collected from the application 110 is associated with the user status, and the user profile stored in the profile DB 106a is associated with the user profile when the general user profile is generated. Is also possible.
- the configuration of the user profile sharing system according to the second embodiment is the same as that shown in FIG. However, the information stored in the profile DB 106a is different. Also, the conversion method of the user open file is different. Hereinafter, points different from the first embodiment will be described.
- FIG. 10 is a conceptual explanatory diagram of information stored in the profile DB 106a.
- the collected user profile is stored in the profile DB 106a in association with the link information.
- This example shows an example in which a user profile is stored for each application.
- the link information links the user profile for which the user profile was created with the user profile.
- the link information is not particularly limited, but may be an update date and time of a user profile, an application identifier, or the like.
- Information included in the user profile can be used as link information.
- FIG. 11 is an explanatory diagram of a user profile corresponding to the current user situation and the related situation by the user profile providing unit 105.
- FIG. 11 (a) shows a user profile file before conversion
- FIG. 11 (b) shows a user profile after conversion using the specified user profile.
- the relevance data table 101b shown in FIG. 3 and the situation data table shown in FIG. 4 are given, and the current user situation is “commuting” and the link information is time information as an example. I have.
- the user statuses “working” and “during break” related to the current user status “commuting” correspond to the web browser.
- the user profile updated during a certain time period is a user profile corresponding to a Web browser. Further, the user profile updated during the “rest” is not stored. Therefore, by extracting only the user profiles updated from 13:00 to 19:00 during the time period corresponding to “on duty”, the “importance” in the user profile is changed by weighting, as shown in FIG. Obtain the integrated user profile of (b).
- FIG. 12 is an explanatory diagram showing an example of a flow of a user profile acquisition process according to the second embodiment.
- the application 110 generates a user profile (# 31) and sends it to the management device 100 together with the application profile (# 32).
- the user profile collection unit 103 of the management device 100 Upon receiving the user profile and the application profile (# 33), the user profile collection unit 103 of the management device 100 passes the profile to the user profile management unit 106. If the user profile includes link information, the user port file management unit 106 stores the user profile in the profile DB 106a as it is. If the user profile does not include the link information, the user profile management unit 106 stores the user profile in association with the link information. For example, the user profile management unit 106 may store a user profile in association with time information at the time of reception or an application identifier.
- the user profile can be associated with the link information.
- FIG. 13 is an explanatory diagram showing an example of a flow of a comprehensive user profile providing process according to the second embodiment.
- the application 110 transmits a request for a user profile to the management device 100.
- the application profile is transmitted together with or in place of the request (# 41).
- the management device 100 When the request receiving unit 104 receives the application profile (# 42), the management device 100 specifies situation data including the current user situation (# 43). Then, the management device 100 Identify relevance data, including relevant situations related to the current user situation (# 44). Further, link information is extracted from the situation data including the current user situation and the situation data including the related situation (# 44). For example, if the link information is time information, time information is extracted.
- the user profile providing unit 105 of the management device extracts a user profile corresponding to the current user situation and the related situation from the profile DB 106a (# 45). That is, the link information corresponding to the user profile is compared with the link information extracted from the status data, and the user profile corresponding to the current user status or the related status is searched. After that, a comprehensive user profile is generated based on the searched user profile and sent to the requester (# 46 to # 48).
- the user profile and the user status are directly associated with each other and stored, so that, even in the case of V, N, it is possible to generate a comprehensive user opening file according to the user status when using the user profile. It becomes.
- an integrated profile is generated by weighting a plurality of user profiles using the update date / time and importance included in the user profiles.
- weighting is possible. For example, the following method can be mentioned.
- the user profile management unit 106 writes the date and time when the user profile was received and the user profile file into the profile DB 106a in association with each other. At the time of providing the user profile, the user profile management unit 106 extracts the user profile corresponding to the current situation and the related situation based on the stored date and time and the situation data table, and provides the user profile. Pass to part 105. Thereafter, the user profile providing unit 105 weights! / Based on the relevance data table.
- the user profile management unit 106 determines the user status to be associated with the user profile based on the date and time when the user profile was received and the status data table, and associates the user status with the user profile. Write to profile DB106a No.
- the management device 100 performs weighting in the same manner as in the first embodiment.
- the management apparatus increases the importance of the user profile corresponding to the user situation at that time.
- the user profile providing unit 105 obtains the current user status from the date and time when the request for the user profile is received, sets the importance of the user profile corresponding to the current user status to “high”, and performs weighting. For example, when the user profile request reception time is “commuting”, an integrated user profile is generated with a weight on the “commuting” user profile. In this way, the user profile does not need to include the update date and time or the importance, and the weighting can be performed without using the relevance data table.
- the user profile providing unit 105 determines the importance based on the update date and time.
- the degree may be set. For example, when receiving user profile requests, set the importance of user profiles within the past week to “high”, those within the past week and within one month to “medium”, and user profiles in the past Is set to “low”.
- the user profile providing unit 105 can perform weighting based on the importance set in this way, and generate an integrated user profile. In this way, it is not only necessary that the user profile does not include the importance, but also the weighting can be performed without using the relevance data table. This weighting method can also be applied to the above (a).
- FIGS. 14A and 14B show the relevance data table 101b and the situation data table 102a in the first embodiment, respectively.
- Figure 14 (a) shows “mealing”, “working”, “commuting”, The degree of association with “at home” and “during a break” is shown.
- Figure 14 (b) shows that the user is using a Web browser or a media player during "work,”"athome,” and “mealing.”
- a web browser and a media player are illustrated as the applications 110a and 110b.
- the Web browser 110a generates a user profile regarding what information the user is interested in based on the page browsing record and the input record of the search vocabulary.
- the media player 110b generates a user profile related to the user's preference based on the user's content viewing history and the like.
- FIG. 15 is an explanatory diagram of acquisition and storage of a user profile.
- the user profiles generated by the applications 110a and 110b are stored in association with the user status.
- FIG. 12A shows the state of the profile DB 106a in the initial state (before 2004Z2Z3 13:00). Thereafter, the Web browser 110a used by the user during work generates the user profile shown in FIG. In this example, the web browser has generated an extensible markup language (XML) style user profile.
- XML extensible markup language
- the user profile management unit 106 of the management device 100 understands the format of the user profile generated by the Web browser from the application profile, and the received user profiler also obtains information on the part corresponding to the generation time and user preference information. Is extracted.
- the user profile management unit 106 passes the extracted creation time and application profile to the user status management unit 102, and acquires corresponding status data.
- the status data “working” corresponding to the user profile generation time in FIG. 15B is returned, and the user profile management unit stores the status data in association with the extracted user preference information.
- Fig. 15 (c) shows the result of storing the preference information in Fig. 15 (b), which also extracted the user profile power, in the profile DB 106a in association with the user status "working". You.
- FIG. 15 (d) shows a user profile generated by the home user who has been using the media player after completing the work.
- the media player has generated a user profile in CSV format.
- the generated user profile is transmitted to the management device 100 together with the application profile of the media player.
- the user profile management unit 106 of the management device 100 understands the format of the user profile generated by the media player in terms of the application profile capability, and generates the information corresponding to the generation time and the user preference information from the received user profile file. Extract. Next, the user profile management unit 106 passes the extracted creation time and application profile to the user status management unit 102, and acquires corresponding status data. In this example, the status data “at home” corresponding to the user profile generation time in FIG. 15D is returned. The user profile management unit 106 stores the status data in association with the extracted user preference information.
- FIG. 15 (e) shows the result of storing the preference information in FIG. 15 (d), which also extracted the user profile power, in the profile DB 106a in association with the user status “at home”.
- the user profile management unit 106 stores pointers and links to preference information, which do not associate the preference information itself with the user status, in association with the user status.
- the association between the user status and the preference information may be performed when the user profile is provided, not when the user profile is received.
- Web browser 110a used by a user during a meal transmits the application file to management device 100 at the start of work.
- the management device 100 which has received the application profile, sends status data corresponding to the current user status by the user status management unit 102. It is read from the status data table 102a. In this example, it is assumed that the user's status data “mealing” is returned.
- user status management section 102 transmits the read data to user profile providing section 105.
- the user profile providing unit 105 acquires the situation data and the degree of association data relating to “during meal” from the user situation management unit 102 and transmits the acquired situation data and the degree of association data to the user profile providing unit 109.
- User profile providing section 105 acquires a user profile corresponding to the situation data. For example, the user profile corresponding to “during meal” and the user profile corresponding to “during work” related to “working”, “commuting”, “at home” and “during a break” Obtained from the profile management unit 106. In this example, the entire user profile of FIG. 15 (e) is acquired.
- the user profile providing unit 105 weights and sorts the user profiles associated with the respective situation data based on the relevance data of FIG. 14 (a), and further sorts the sorted user profiles on the Web. Convert to a format suitable for browser 110a.
- FIG. 16 shows an example of weighting and sorting according to the degree of relevance to a user profile.
- FIG. 17 shows the overall user profile converted to a format that can be used by Web browser 110a.
- the Web browser and the media player can share a user profile suitable for the user situation with each other.
- the Web browser 110a generates the same user profile as in the first embodiment.
- the IMlOb and the portable mail 110c generate a user profile relating to the user's preference based on the topic the user likes, the history of the types of files to be exchanged, and the like.
- FIGS. 18 (a) and (b) show the relevance data table 101b and the situation data in this embodiment.
- Table 102a is shown respectively.
- FIG. 9A shows the degree of association between the user status “commuting” and “working”, “coming home” and “at home”.
- Figure (b) shows that the user is using the Web browser, IM, and mobile mail while “working”, “returning home”, “at home”, and “commuting”.
- the Web browser 110a registers the user profile shown in FIG. 19A in the management device 100 as in the first embodiment.
- the user profile management unit 106 of the management device 100 stores the received user profile for each application.
- FIG. 19 (a) shows that an IT-related profile file generated during work, a Western-related profile generated while returning home, and a user profile generated by the power web browser 110a are stored.
- the user profile management unit 106 confirms that the user profile has been generated by the Web browser 110a based on the received application profile, and saves the user profile in a Web browser directory or the like.
- IMlOb used by the user during work and at home generates a user profile after the work is completed.
- Fig. 20 (a) shows an example of a user profile generated by IM.
- IM generates a user profile in CSV format.
- the user profile management unit 106 confirms that the user profile has been generated by the user profile power M based on the received application profile, and stores the user profile in an IM directory or the like. In this embodiment, the user profile is not directly associated with the situation data.
- the mobile email 110c used by the user during commuting is At first, the application profile is transmitted to the management device 100.
- the request receiving unit 104 of the management device 100 that has received the application profile acquires, from the user status management unit 102, status data corresponding to the current user status. In this example, the status data of the user "commuting" is returned. Next, the request receiving unit 104 passes the acquired situation data to the user profile providing unit 105.
- the user profile providing unit 105 acquires status data and relevance data relating to "during commuting" from the user status management unit 102, and passes them to the user profile management unit 106.
- the user profile providing unit 105 acquires a user profile corresponding to the situation data from the user profile management unit 106.
- the user profiles associated with “working”, “returning home”, and “at home”, which are related to “commuting”, are acquired.
- the user profile management unit 106 uses the time data corresponding to the situation data as link information, and stores the user profile stored for each application. Get profile.
- the user profile management unit 106 obtains the user profile generated during "at work” in order to obtain the time "2004Z2Z3 13: 00- Search for the user profile generated at “19:00”.
- an IT-related user profile is selected from the user profile of the Web browser 110a
- an AV device-related user profile is selected from the IMlOb user profile.
- the user profiles generated in the time zone corresponding to “coming home” are respectively selected and passed to the user profile providing unit 105.
- the user profile providing unit 105 weights a user profile associated with each situation data based on the relevance data of FIG. 18 (a), and assigns a weight to each application. Merge user profile data.
- FIG. 19B shows a result obtained by weighting and merging the user profile of the Web browser 110a.
- FIG. 20 (b) shows an example in which the user profile of IM 110b is weighted and merged.
- the user profile providing unit 105 converts the merged user profile of each application into a format that can be used by another application by requesting the user profile.
- FIGS. 19 (c) and 20 (c) show examples in which the user profiles for the web browser 110a and the IM 110b have been converted into formats that can be used for mobile mail.
- the user profile providing unit 105 provides these to the mobile mail 110c after merging these user profiles.
- FIG. 21 shows a total user profile generated by merging the user profiles shown in FIGS. 19 (c) and 20 (c).
- the Web browser 110a generates a user profile as in the first embodiment.
- the mailer generates a user profile related to the user's preferences in the same way as a Web browser, based on the topics the user likes and the history of the types of files to be exchanged.
- FIGS. 22A and 22B show a relevance data table 101b and a situation data table 102a in this embodiment, respectively.
- FIG. 9A shows the degree of association with the user statuses “at work”, “at home”, and “at home”.
- FIG. 2B shows that the user uses a Web browser, IM, or car navigation system while “working”, “returning home”, “at home”, and “commuting”.
- Ontology files are used to convert user profiles.
- FIG. 23 (a) and FIG. 24 (a) are conceptual illustrations of user profiles stored for each application.
- the user profile is directly associated with the situation data.
- the car navigation system 110c used by the user during commuting transmits an application profile to the management device 100 at the start of work.
- the request receiving unit 104 of the management device 100 acquires from the user status management unit 102 status data corresponding to the current user status. In this example, the status data of the user "commuting" is returned. Next, the acquired status data is passed to the user status management unit 102 via the user profile providing unit 105.
- the user status management unit 102 obtains status data and relevance data related to “commuting” from the status data table 102a, and passes the obtained data to the user profile providing unit 105.
- the user profile providing unit 105 acquires the user profile corresponding to the situation data from the user profile management unit 106.
- the user profile corresponding to “working”, “returning home”, and “at home”, which are related to “commuting”, is acquired from the user opening file management unit 106.
- the user profile is not directly associated with the situation data. Therefore, the user profile management unit 106 uses the time data corresponding to the situation data as the link information and acquires a user profile stored for each application.
- the user profile management unit 106 obtains the user profile generated during "at work” in order to obtain the time "2004Z2Z3 13: 00- Search for the user profile generated at “19:00”.
- the IT-related user profiles shown in the upper part of Fig. 23 (a) are extracted.
- the Western music-related A user profile is extracted.
- a mailer user profile shown in FIG. 24A is extracted as a user profile generated in a time zone corresponding to “at home”, and is passed to the user profile providing unit 105.
- the user profile providing unit 105 weights a user profile associated with each situation data based on the relevance data, and merges the user profile data for each application.
- Figure 23 (b) shows an example in which two user profiles of a Web browser are weighted and merged.
- the user profile providing unit 105 converts the merged user profile of each application into a format that can be used by another application by requesting the user profile.
- FIG. 24C shows an example in which the user profile shown in FIG. 24B is converted into a format that can be used by the car navigation system 110c.
- the car navigation system 110c and the web browser 110a use the same user profile format. Therefore, the conversion process for the user profile of the Web browser 110a is not performed, and the user profile for the mailer 110b is converted to the format for the car navigation system 110c.
- the user profile providing unit 105 converts the user profile of the mailer 110b shown in FIG. 24 (b) into a format for the car navigation system 110c. Further, the user profile providing unit 105 merges the user profiles of the Web browser and the mailer and provides the merged profile to the car navigation system 110c.
- the user profile can be shared between the applications.
- the method executed by the management device 100, a program for executing the method, and a computer-readable recording medium on which the program is recorded are included in the scope of the present invention.
- the recording medium include a flexible disk that can be read and written by a computer, a hard disk, a semiconductor memory, a CD-ROM, a DVD, a magneto-optical disk (MO), and others.
- a device / service can be personalized by sharing a user open file among a plurality of device 'services in consideration of a user's situation.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2006514578A JP4660475B2 (ja) | 2004-06-10 | 2005-06-10 | ユーザプロファイル管理システム |
US11/628,952 US7650342B2 (en) | 2004-06-10 | 2005-06-10 | User profile management system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004172030 | 2004-06-10 | ||
JP2004-172030 | 2004-06-10 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005122013A1 true WO2005122013A1 (ja) | 2005-12-22 |
Family
ID=35503268
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/010658 WO2005122013A1 (ja) | 2004-06-10 | 2005-06-10 | ユーザプロファイル管理システム |
Country Status (4)
Country | Link |
---|---|
US (1) | US7650342B2 (ja) |
JP (1) | JP4660475B2 (ja) |
CN (1) | CN1969292A (ja) |
WO (1) | WO2005122013A1 (ja) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007323225A (ja) * | 2006-05-31 | 2007-12-13 | Access Co Ltd | システム、端末、サーバ、及び、動的情報提供方法 |
JP2008129886A (ja) * | 2006-11-22 | 2008-06-05 | Nec Corp | 情報交換装置、情報交換システム及びそれらに用いる情報交換方法並びにそのプログラム |
JP2010510606A (ja) * | 2006-11-22 | 2010-04-02 | ヤフー! インコーポレイテッド | メディアの配信のための方法、システム、及び装置 |
JP2013242718A (ja) * | 2012-05-21 | 2013-12-05 | Yahoo Japan Corp | 興味推定装置、興味推定方法およびプログラム |
JP2014528123A (ja) * | 2011-09-12 | 2014-10-23 | インテル・コーポレーション | 精密なユーザー嗜好データの収集及び管理 |
US8892495B2 (en) | 1991-12-23 | 2014-11-18 | Blanding Hovenweep, Llc | Adaptive pattern recognition based controller apparatus and method and human-interface therefore |
US9110903B2 (en) | 2006-11-22 | 2015-08-18 | Yahoo! Inc. | Method, system and apparatus for using user profile electronic device data in media delivery |
JP2015531909A (ja) * | 2012-07-20 | 2015-11-05 | インタートラスト テクノロジーズ コーポレイション | 情報ターゲティングシステムおよび方法 |
US9535563B2 (en) | 1999-02-01 | 2017-01-03 | Blanding Hovenweep, Llc | Internet appliance system and method |
WO2017098617A1 (ja) * | 2015-12-09 | 2017-06-15 | 富士通株式会社 | 情報提供方法、情報提供プログラムおよび情報提供装置 |
JP2020523707A (ja) * | 2017-06-16 | 2020-08-06 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | ユーザプロファイル生成方法および端末 |
JP2020536299A (ja) * | 2017-09-21 | 2020-12-10 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | 改善されたパフォーマンスのためのユーザ・プロファイルの動的かつ自動的な変更を実施するための方法、コンピュータ・システム及びプログラム |
Families Citing this family (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8073719B2 (en) | 2006-06-30 | 2011-12-06 | Rearden Commerce, Inc. | System and method for core identity with personas across multiple domains with permissions on profile data based on rights of domain |
US7966321B2 (en) * | 2007-01-17 | 2011-06-21 | Google Inc. | Presentation of local results |
US8326858B2 (en) * | 2007-01-17 | 2012-12-04 | Google Inc. | Synchronization of fixed and mobile data |
US8966407B2 (en) | 2007-01-17 | 2015-02-24 | Google Inc. | Expandable homepage modules |
US7966309B2 (en) | 2007-01-17 | 2011-06-21 | Google Inc. | Providing relevance-ordered categories of information |
US8005822B2 (en) | 2007-01-17 | 2011-08-23 | Google Inc. | Location in search queries |
US9530117B2 (en) * | 2007-02-13 | 2016-12-27 | International Business Machines Corporation | Method and apparatus for transforming user requests and responses based on a persona |
US20080201432A1 (en) * | 2007-02-16 | 2008-08-21 | Rearden Commerce, Inc. | System and Method for Facilitating Transfer of Experience Data in to Generate a New Member Profile for a Online Service Portal |
US9596308B2 (en) | 2007-07-25 | 2017-03-14 | Yahoo! Inc. | Display of person based information including person notes |
US9584343B2 (en) | 2008-01-03 | 2017-02-28 | Yahoo! Inc. | Presentation of organized personal and public data using communication mediums |
KR20100058833A (ko) * | 2008-11-25 | 2010-06-04 | 삼성전자주식회사 | 모바일 기기에서 감지 가능한 사용자의 행위 기반의 사용자기호 마이닝 방법 |
US8180388B1 (en) * | 2008-12-10 | 2012-05-15 | Sprint Spectrum L.P. | Methods and systems for improving session establishment with wireless communication devices |
US20120046995A1 (en) | 2009-04-29 | 2012-02-23 | Waldeck Technology, Llc | Anonymous crowd comparison |
EP2438571A4 (en) | 2009-06-02 | 2014-04-30 | Yahoo Inc | AUTOMATICALLY ADDRESSED ADDRESS BOOK |
US8990323B2 (en) | 2009-07-08 | 2015-03-24 | Yahoo! Inc. | Defining a social network model implied by communications data |
US7930430B2 (en) | 2009-07-08 | 2011-04-19 | Xobni Corporation | Systems and methods to provide assistance during address input |
US9721228B2 (en) | 2009-07-08 | 2017-08-01 | Yahoo! Inc. | Locally hosting a social network using social data stored on a user's computer |
US8984074B2 (en) | 2009-07-08 | 2015-03-17 | Yahoo! Inc. | Sender-based ranking of person profiles and multi-person automatic suggestions |
US20110016119A1 (en) * | 2009-07-15 | 2011-01-20 | Alcatel-Lucent Usa Inc. | System and method for managing user profiles |
US9087323B2 (en) | 2009-10-14 | 2015-07-21 | Yahoo! Inc. | Systems and methods to automatically generate a signature block |
US20110093367A1 (en) * | 2009-10-20 | 2011-04-21 | At&T Intellectual Property I, L.P. | Method, apparatus, and computer product for centralized account provisioning |
US8473512B2 (en) | 2009-11-06 | 2013-06-25 | Waldeck Technology, Llc | Dynamic profile slice |
US9514466B2 (en) | 2009-11-16 | 2016-12-06 | Yahoo! Inc. | Collecting and presenting data including links from communications sent to or from a user |
US9760866B2 (en) | 2009-12-15 | 2017-09-12 | Yahoo Holdings, Inc. | Systems and methods to provide server side profile information |
US8924956B2 (en) | 2010-02-03 | 2014-12-30 | Yahoo! Inc. | Systems and methods to identify users using an automated learning process |
US8423545B2 (en) | 2010-02-03 | 2013-04-16 | Xobni Corporation | Providing user input suggestions for conflicting data using rank determinations |
US8754848B2 (en) | 2010-05-27 | 2014-06-17 | Yahoo! Inc. | Presenting information to a user based on the current state of a user device |
US8620935B2 (en) | 2011-06-24 | 2013-12-31 | Yahoo! Inc. | Personalizing an online service based on data collected for a user of a computing device |
US8972257B2 (en) | 2010-06-02 | 2015-03-03 | Yahoo! Inc. | Systems and methods to present voice message information to a user of a computing device |
US8732147B2 (en) * | 2011-03-18 | 2014-05-20 | Microsoft Corporation | Data collections on a mobile device |
US10078819B2 (en) | 2011-06-21 | 2018-09-18 | Oath Inc. | Presenting favorite contacts information to a user of a computing device |
US9747583B2 (en) | 2011-06-30 | 2017-08-29 | Yahoo Holdings, Inc. | Presenting entity profile information to a user of a computing device |
US8949873B1 (en) * | 2011-07-31 | 2015-02-03 | Google Inc. | Systems and methods for sharing media content viewing history |
US9253282B2 (en) * | 2011-10-18 | 2016-02-02 | Qualcomm Incorporated | Method and apparatus for generating, using, or updating an enriched user profile |
US10977285B2 (en) | 2012-03-28 | 2021-04-13 | Verizon Media Inc. | Using observations of a person to determine if data corresponds to the person |
US10096041B2 (en) * | 2012-07-31 | 2018-10-09 | The Spoken Thought, Inc. | Method of advertising to a targeted buyer |
US10013672B2 (en) | 2012-11-02 | 2018-07-03 | Oath Inc. | Address extraction from a communication |
US10192200B2 (en) | 2012-12-04 | 2019-01-29 | Oath Inc. | Classifying a portion of user contact data into local contacts |
US10372921B2 (en) | 2017-03-15 | 2019-08-06 | International Business Machines Corporation | Dynamic security policies |
US11799974B2 (en) * | 2017-08-31 | 2023-10-24 | Microsoft Technology Licensing, Llc | User profile aggregation and inference generation |
US20220006804A1 (en) * | 2020-07-03 | 2022-01-06 | Toyota Motor North America, Inc. | Gateway and proxy for vehicle head unit certificate validation |
US20230401049A1 (en) * | 2022-06-09 | 2023-12-14 | Vmware, Inc. | Multi-mode support for a launcher |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001188992A (ja) * | 1999-12-27 | 2001-07-10 | Nippon Telegr & Teleph Corp <Ntt> | 情報提供方法及び情報提供システム |
JP2001290727A (ja) * | 2000-04-06 | 2001-10-19 | Nec Corp | 情報提供システムおよび情報提供方法 |
JP2002117066A (ja) * | 2000-10-10 | 2002-04-19 | Canon Inc | 携帯端末装置、基地端末装置、位置管理装置、情報登録装置、携帯端末制御方法、基地端末制御方法、位置管理方法、情報登録方法及び記憶媒体 |
JP2003122992A (ja) * | 2001-10-11 | 2003-04-25 | Nippon Telegr & Teleph Corp <Ntt> | 情報とメディアの選択システム、及び情報とメディアの選択方法 |
JP2003122786A (ja) * | 2001-10-11 | 2003-04-25 | Nippon Telegr & Teleph Corp <Ntt> | ユーザ間情報共有システム、及びユーザ間情報共有方法 |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7242988B1 (en) * | 1991-12-23 | 2007-07-10 | Linda Irene Hoffberg | Adaptive pattern recognition based controller apparatus and method and human-factored interface therefore |
US5978766A (en) * | 1995-12-20 | 1999-11-02 | Starwave Corporation | Machine, method and medium for assisted selection of information from a choice space |
US5715371A (en) * | 1996-05-31 | 1998-02-03 | Lucent Technologies Inc. | Personal computer-based intelligent networks |
US20010056405A1 (en) * | 1997-09-11 | 2001-12-27 | Muyres Matthew R. | Behavior tracking and user profiling system |
AU1195599A (en) * | 1997-10-24 | 1999-05-17 | Cioview Corp. | Systems and methods for software evaluation and performance measurement |
CA2322026A1 (en) | 1998-02-27 | 1999-09-02 | Daniel Jaye | System and method for building user profiles |
US7904187B2 (en) * | 1999-02-01 | 2011-03-08 | Hoffberg Steven M | Internet appliance system and method |
US6510430B1 (en) * | 1999-02-24 | 2003-01-21 | Acumins, Inc. | Diagnosis and interpretation methods and apparatus for a personal nutrition program |
DE10005780A1 (de) * | 2000-02-10 | 2001-08-16 | Bosch Gmbh Robert | Verfahren zur Routenplanung in einem Navigationssystem |
US7505921B1 (en) * | 2000-03-03 | 2009-03-17 | Finali Corporation | System and method for optimizing a product configuration |
US7725525B2 (en) * | 2000-05-09 | 2010-05-25 | James Duncan Work | Method and apparatus for internet-based human network brokering |
US6691106B1 (en) * | 2000-05-23 | 2004-02-10 | Intel Corporation | Profile driven instant web portal |
WO2001093096A2 (en) * | 2000-05-30 | 2001-12-06 | Koki Uchiyama | Distributed monitoring system providing knowledge services |
US7739335B2 (en) * | 2000-06-22 | 2010-06-15 | Sony Corporation | Method and apparatus for providing a customized selection of audio content over the internet |
AU2002227514A1 (en) * | 2000-07-27 | 2002-02-13 | Polygnostics Limited | Collaborative filtering |
US8020183B2 (en) * | 2000-09-14 | 2011-09-13 | Sharp Laboratories Of America, Inc. | Audiovisual management system |
US7319992B2 (en) * | 2000-09-25 | 2008-01-15 | The Mission Corporation | Method and apparatus for delivering a virtual reality environment |
CA2403300A1 (en) * | 2002-09-12 | 2004-03-12 | Pranil Ram | A method of buying or selling items and a user interface to facilitate the same |
US20030033353A1 (en) * | 2001-08-08 | 2003-02-13 | Simpson Shell S. | Method for web-based imaging service to redirect to a preferred destination based on a criteria |
US20030206710A1 (en) * | 2001-09-14 | 2003-11-06 | Ferman Ahmet Mufit | Audiovisual management system |
US20050021398A1 (en) * | 2001-11-21 | 2005-01-27 | Webhound Corporation | Method and system for downloading digital content over a network |
DE10217300C1 (de) * | 2002-04-18 | 2003-11-20 | Fraunhofer Ges Forschung | Ortsabhängige Informationswiedergabe unter Anpassung eines geographischen Auswahlparameters |
US7216119B1 (en) * | 2002-06-20 | 2007-05-08 | Raytheon Company | Method and apparatus for intelligent information retrieval |
US20050021666A1 (en) * | 2002-10-08 | 2005-01-27 | Dinnage David M. | System and method for interactive communication between matched users |
US20040205394A1 (en) * | 2003-03-17 | 2004-10-14 | Plutowski Mark Earl | Method and apparatus to implement an errands engine |
US7725842B2 (en) * | 2003-04-24 | 2010-05-25 | Bronkema Valentina G | Self-attainable analytic tool and method for adaptive behavior modification |
US20040254957A1 (en) * | 2003-06-13 | 2004-12-16 | Nokia Corporation | Method and a system for modeling user preferences |
US20050222895A1 (en) * | 2004-04-03 | 2005-10-06 | Altusys Corp | Method and Apparatus for Creating and Using Situation Transition Graphs in Situation-Based Management |
US7283803B2 (en) * | 2004-04-16 | 2007-10-16 | Broadcom Corporation | Location-aware application based quality of service (QOS) via a broadband access gateway |
-
2005
- 2005-06-10 CN CNA2005800191506A patent/CN1969292A/zh active Pending
- 2005-06-10 WO PCT/JP2005/010658 patent/WO2005122013A1/ja active Application Filing
- 2005-06-10 JP JP2006514578A patent/JP4660475B2/ja not_active Expired - Fee Related
- 2005-06-10 US US11/628,952 patent/US7650342B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001188992A (ja) * | 1999-12-27 | 2001-07-10 | Nippon Telegr & Teleph Corp <Ntt> | 情報提供方法及び情報提供システム |
JP2001290727A (ja) * | 2000-04-06 | 2001-10-19 | Nec Corp | 情報提供システムおよび情報提供方法 |
JP2002117066A (ja) * | 2000-10-10 | 2002-04-19 | Canon Inc | 携帯端末装置、基地端末装置、位置管理装置、情報登録装置、携帯端末制御方法、基地端末制御方法、位置管理方法、情報登録方法及び記憶媒体 |
JP2003122992A (ja) * | 2001-10-11 | 2003-04-25 | Nippon Telegr & Teleph Corp <Ntt> | 情報とメディアの選択システム、及び情報とメディアの選択方法 |
JP2003122786A (ja) * | 2001-10-11 | 2003-04-25 | Nippon Telegr & Teleph Corp <Ntt> | ユーザ間情報共有システム、及びユーザ間情報共有方法 |
Cited By (19)
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 |
US9535563B2 (en) | 1999-02-01 | 2017-01-03 | Blanding Hovenweep, Llc | Internet appliance system and method |
JP2007323225A (ja) * | 2006-05-31 | 2007-12-13 | Access Co Ltd | システム、端末、サーバ、及び、動的情報提供方法 |
JP2008129886A (ja) * | 2006-11-22 | 2008-06-05 | Nec Corp | 情報交換装置、情報交換システム及びそれらに用いる情報交換方法並びにそのプログラム |
JP2010510606A (ja) * | 2006-11-22 | 2010-04-02 | ヤフー! インコーポレイテッド | メディアの配信のための方法、システム、及び装置 |
JP2013050957A (ja) * | 2006-11-22 | 2013-03-14 | Yahoo Inc | メディアの配信のための方法、システム、及び装置 |
US9110903B2 (en) | 2006-11-22 | 2015-08-18 | Yahoo! Inc. | Method, system and apparatus for using user profile electronic device data in media delivery |
US10095793B2 (en) | 2011-09-12 | 2018-10-09 | Intel Corporation | Collection and management of precision user preference data |
JP2014528123A (ja) * | 2011-09-12 | 2014-10-23 | インテル・コーポレーション | 精密なユーザー嗜好データの収集及び管理 |
JP2013242718A (ja) * | 2012-05-21 | 2013-12-05 | Yahoo Japan Corp | 興味推定装置、興味推定方法およびプログラム |
JP2015531909A (ja) * | 2012-07-20 | 2015-11-05 | インタートラスト テクノロジーズ コーポレイション | 情報ターゲティングシステムおよび方法 |
US10061847B2 (en) | 2012-07-20 | 2018-08-28 | Intertrust Technologies Corporation | Information targeting systems and methods |
JPWO2017098617A1 (ja) * | 2015-12-09 | 2018-09-27 | 富士通株式会社 | 情報提供方法、情報提供プログラムおよび情報提供装置 |
WO2017098617A1 (ja) * | 2015-12-09 | 2017-06-15 | 富士通株式会社 | 情報提供方法、情報提供プログラムおよび情報提供装置 |
JP2020523707A (ja) * | 2017-06-16 | 2020-08-06 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | ユーザプロファイル生成方法および端末 |
JP2020536299A (ja) * | 2017-09-21 | 2020-12-10 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | 改善されたパフォーマンスのためのユーザ・プロファイルの動的かつ自動的な変更を実施するための方法、コンピュータ・システム及びプログラム |
JP7257726B2 (ja) | 2017-09-21 | 2023-04-14 | インターナショナル・ビジネス・マシーンズ・コーポレーション | 改善されたパフォーマンスのためのユーザ・プロファイルの動的かつ自動的な変更を実施するための方法、コンピュータ・システム及びプログラム |
JP7429087B2 (ja) | 2017-09-21 | 2024-02-07 | インターナショナル・ビジネス・マシーンズ・コーポレーション | 改善されたパフォーマンスのためのユーザ・プロファイルの動的かつ自動的な変更を実施するための方法、コンピュータ・システム及びプログラム |
US11954564B2 (en) | 2017-09-21 | 2024-04-09 | International Business Machines Corporation | Implementing dynamically and automatically altering user profile for enhanced performance |
Also Published As
Publication number | Publication date |
---|---|
CN1969292A (zh) | 2007-05-23 |
US20080301166A1 (en) | 2008-12-04 |
JPWO2005122013A1 (ja) | 2008-04-10 |
US7650342B2 (en) | 2010-01-19 |
JP4660475B2 (ja) | 2011-03-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2005122013A1 (ja) | ユーザプロファイル管理システム | |
US6944651B2 (en) | Single click synchronization of data from a public information store to a private information store | |
US7533079B2 (en) | Device and method for processing situated information | |
US7440976B2 (en) | Method and apparatus for performing collaborative searches | |
US9391946B2 (en) | System and method for enabling identification of network users having similar interests and facilitating communication between them | |
US9183291B2 (en) | Mobile content capture and discovery system based on augmented user identity | |
CN102037467B (zh) | 按时间和位置转动搜索结果 | |
KR100478019B1 (ko) | 지역 정보 검색 결과 제공 방법 및 시스템 | |
US8078977B2 (en) | Method and system for intelligent processing of electronic information | |
JP4489994B2 (ja) | 話題抽出装置、方法、プログラム及びそのプログラムを記録する記録媒体 | |
US7761441B2 (en) | Community search system through network and method thereof | |
JP2006520939A (ja) | インターネット使用者の接続意図判断方法およびこれを用いたインターネット上の広告方法とそのシステム | |
US20070073667A1 (en) | Search system and method using a plurality of searching criterion | |
JP2002032401A (ja) | 文書検索方法及び文書検索装置及び文書検索方法をコンピュータに実現させるためのプログラムを記録したコンピュータで読取可能な記録媒体 | |
JP5799808B2 (ja) | 情報管理装置、そのデータ処理方法、およびコンピュータプログラム | |
US20040049413A1 (en) | Apparatus, method, and computer program for reservation of accommodation | |
KR20000054312A (ko) | 맞춤 웹정보 구축 제공 방법 | |
Ben Njima et al. | Development of a mobile web services discovery and composition model | |
JP2012014518A (ja) | コンテンツ間類似度算出装置及びコンテンツ間類似度算出方法 | |
Stoica et al. | An architecture to support personalized interaction across multiple digitally augmented spaces | |
KR101020895B1 (ko) | 지역 정보 검색 결과 제공 방법 및 시스템 | |
Makripoulias et al. | Towards ubiquitous computing with quality of web service support | |
JPH11265402A (ja) | データ処理システム及びデータ処理システムを制御するプログラムを記録した記録媒体 | |
Coyle et al. | Supplementing Case-based Recommenders with Context Data. | |
WO2000025233A1 (fr) | Procede de partage d'adresse de liaison au moyen d'un reseau, systeme de reseau, et support |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006514578 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11628952 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580019150.6 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase |