Patent Description:
Service providers may provide users with a personalized service by collecting various information associated with a user, analyzing the collected information, and generating a user profile.

In this process, it is not easy for the service providers to directly establish a user profile generating module. For example, it is impossible or difficult for the service providers to collect personal information. Accordingly, a service that provides a user profile may be operated separately. The service providers may make a request for information about the user profile to an external server and may provide the personalized service based on the user profile received from the external server, without directly generating the user profile.

<CIT> is about a software tool that allows a computer user to view only search results that have become available since he last performed the same search. A user enters a search term by way of an input/output device, and the CPU performs the requested search. The computer identifies and displays only the new results. The user can toggle this feature on and off.

In a system providing a user profile, when there are various services, a type of user profile necessary for each service and a type of user profile to be collected may be different. Even though the corresponding system collects various pieces of data based on various services and profiles, there may be a case in which information desired by a user utilizing a third party service is not capable of being provided.

The present disclosure has been made to address the above-mentioned problems and disadvantages, and to provide at least the advantages described below.

According to various embodiments of the disclosure, it is possible to newly generate a profile based on a request for a profile even if the profile has not yet been prepared. A newly generated profile may be provided in response to the request.

Various embodiments of the disclosure are described with reference to the accompanying drawings. However, various embodiments of the disclosure are not limited to particular embodiments, and it should be understood that modifications, equivalents, and/or alternatives of the embodiments described herein can be variously made. With regard to description of drawings, similar components may be marked by similar reference numerals.

An aspect of the disclosure is to provide a server device that may provide data suitable for a request when a profile that was not previously prepared is requested, and a system thereof <FIG> is a block diagram of an electronic device <NUM> in a network environment <NUM>, according to various embodiments.

Referring to <FIG>, the electronic device <NUM> in the network environment <NUM> may communicate with an electronic device <NUM> over a first network <NUM> (e.g., a short range wireless communication) or may communicate with an electronic device <NUM> or a server <NUM> over a second network <NUM> (e.g., a long range wireless communication). The electronic device <NUM> may communicate with the electronic device <NUM> through the server <NUM>. According to an embodiment, the electronic device <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a sound output device <NUM>, a display device <NUM>, an audio module <NUM>, a sensor module <NUM>, an interface <NUM>, a haptic module <NUM>, a camera module <NUM>, a power management module <NUM>, a battery <NUM>, a communication module <NUM>, a subscriber identification module <NUM>, or an antenna module <NUM>. In any embodiment, the electronic device <NUM> may not include at least one (e.g., the display device <NUM> or the camera module <NUM>) of the above-described components or may further include one or more other components. In any embodiment, some of the components may be implemented as a single integrated circuit. For example, the sensor module <NUM> (e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be implemented while being embedded in the display device <NUM> (e.g., a display).

For example, the processor <NUM> may execute software (e.g., a program) to control at least another component (e.g., hardware or software component) of the electronic device <NUM> connected to the processor <NUM>, and may process and calculate various types of data. According to an embodiment, as at least part of data processing or calculation, the processor <NUM> may load instructions or data received from other components (e.g., the sensor module <NUM> or the communication module <NUM>) into a volatile memory <NUM>, may process instructions or data stored in the volatile memory <NUM>, and may store the result data in a nonvolatile memory <NUM>. According to an embodiment, the processor <NUM> may include a main processor <NUM> (e.g., a central processing unit or an application processor) and an auxiliary processor <NUM> (e.g., a graphic processing unit, an image signal processor, a sensor hub processor, or a communication processor) capable of operating independently or together with the main processor. Additionally or alternatively, the auxiliary processor <NUM> may use lower power than main processor <NUM> or may be configured to be specialized to a specified function. The auxiliary processor <NUM> may be implemented separately from the main processor <NUM> or as part of the main processor <NUM>.

For example, the auxiliary processor <NUM> may control at least part of the functions or states associated with at least one (e.g., the display device <NUM>, the sensor module <NUM>, or the communication module <NUM>) of the components of the electronic device <NUM>, instead of the main processor <NUM> while the main processor <NUM> is in an inactive (e.g., sleep) state or together with the main processor <NUM> while the main processor <NUM> is in an active (e.g., the execution of an application) state. According to an embodiment, the auxiliary processor <NUM> (e.g., an image signal processor or a communication processor) may be implemented as a part of operatively associated other components (e.g., the camera module <NUM> or the communication module <NUM>). The memory <NUM> may store various pieces of data used by at least one component (e.g., the processor <NUM> or the sensor module <NUM>) of the electronic device <NUM>. For example, data may include software (e.g., a program <NUM>) and input data or output data for instructions associated with the software. The memory <NUM> may include, for example, the volatile memory <NUM> or the nonvolatile memory <NUM>.

The program <NUM> may be stored as software in the memory <NUM> and may include, for example, an operating system <NUM>, a middleware <NUM>, or an application <NUM>.

The input device <NUM> may receive instructions or data to be used for the component (e.g., the processor <NUM>) of the electronic device <NUM>, from the outside (e.g., a user) of the electronic device <NUM>.

The sound output device <NUM> may output a sound signal to the outside of the electronic device <NUM>. The speaker may be used for a general purpose, such as multimedia play or recording play, and the receiver may be used to receive an incoming call. According to an embodiment, the receiver may be implemented separately from the speaker or may be implemented as a part of the speaker.

The display device <NUM> may visually provide information to the outside (e.g., the user) of the electronic device <NUM>. The display device <NUM> may include, for example, a display, a hologram device, or a projector and a control circuit for controlling a corresponding device. According to an embodiment, the display device <NUM> may include a touch circuitry configured to sense a touch, or a sensor circuitry (e.g., a pressure sensor) configured to measure the strength of force generated by the touch.

The audio module <NUM> may convert sound to an electrical signal, or reversely, may convert an electrical signal to sound. According to an embodiment, the audio module <NUM> may obtain sound through the input device <NUM>, or may output sound through the sound output device <NUM>, or through an external electronic device (e.g., the electronic device <NUM>) (e.g., a speaker or a headphone) directly or wirelessly connected with the electronic device <NUM>.

The sensor module <NUM> may sense an operation state (e.g., power or a temperature) of the electronic device <NUM> or an external environment state (e.g., a user state), and may generate an electrical signal or a data value corresponding the sensed state. According to an embodiment, the sensor module <NUM> may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

The interface <NUM> may support one or more specified protocols that may be used to directly and wirelessly connect the electronic device <NUM> with an external electronic device (e.g., the electronic device <NUM>).

A connecting terminal <NUM> may include a connector that may allow the electronic device <NUM> to be physically connected with an external electronic device (e.g., the electronic device <NUM>).

The haptic module <NUM> may convert an electrical signal to a mechanical stimulation (e.g., vibration or movement) or an electrical stimulation which the user may perceive through the sense of touch or the sense of movement. According to an embodiment, the haptic module <NUM> may include, for example, a motor, a piezoelectric sensor, or an electrical stimulation device. The camera module <NUM> may photograph a still image and a video. According to an embodiment, the camera module <NUM> may include one or more lenses, image sensors, image signal processors, or flashes (or electrical flashes).

The power management module <NUM> may manage the power which is supplied to the electronic device <NUM>. According to an embodiment, the power management module <NUM> may be implemented, for example, as at least part of a power management integrated circuit (PMIC). The battery <NUM> may power at least one component of the electronic device <NUM>. According to an embodiment, the battery <NUM> may include, for example, a primary cell not rechargeable, a secondary cell rechargeable, or a fuel cell.

The communication module <NUM> may establish a direct (or wired) communication channel or a wireless communication channel between the electronic device <NUM> and an external electronic device (e.g., the electronic device <NUM>, the electronic device <NUM>, or the server <NUM>) and may perform communication through the established communication channel. The communication module <NUM> may include one or more communication processors which are operated independently of the processor <NUM> (e.g., an application processor) and support direct (or wired) communication or wireless communication. According to an embodiment, the communication module <NUM> may include a wireless communication module <NUM> (e.g., a cellular communication module, a short range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module <NUM> (e.g., a local area network (LAN) communication module or a power line communication module). A corresponding communication module of such communication modules may communicate with an external electronic device over the first network <NUM> (e.g., a short range communication network such as Bluetooth, Wi-Fi direct, or infrared data association (IrDA)) or the second network <NUM> (e.g., a long distance communication network such as a cellular network, an Internet, or a computer network (e.g., LAN or WAN)). The above-described kinds of communication modules may be integrated in one component (e.g., a single chip) or may be implemented with a plurality of components (e.g., a plurality of chips) which are independent of each other. The wireless communication module <NUM> may identify and authenticate the electronic device <NUM> within a communication network, such as the first network <NUM> or the second network <NUM>, by using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module <NUM>.

The antenna module <NUM> may transmit a signal or a power to the outside (e.g., an external electronic device) or may receive a signal or a power from the outside. According to an embodiment, the antenna module may include one antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In this case, at least one antenna suitable for a communication scheme used in a communication network such as the first network <NUM> or the second network <NUM> may be selected, for example, by the communication module <NUM> from the plurality of antennas. The signal or power may be exchanged between the communication module <NUM> and an external electronic device through the selected at least one antenna or may be received from the external electronic device through the selected at least one antenna and the communication module <NUM>. According to any embodiment, another component (e.g., RFIC) in addition to the radiator may be further formed as the part of the antenna module <NUM>.

At least part of the components may be connected to each other through a communication scheme (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) between peripheral devices and may exchange signals (e.g., commands or data) with each other.

According to an embodiment, a command or data may be transmitted or received (or exchanged) between the electronic device <NUM> and the external electronic device <NUM> through the server <NUM> connected to the second network <NUM>. Each of the electronic devices <NUM> and <NUM> may be a device of which the type is different from or the same as that of the electronic device <NUM>. According to an embodiment, all or a part of operations to be executed in the electronic device <NUM> may be executed in one or more external devices of the external electronic devices <NUM>, <NUM>, or <NUM>. For example, in the case where the electronic device <NUM> should perform any function or service automatically or in response to a request from the user or any other device, the electronic device <NUM> may additionally request one or more external electronic devices to perform at least part of the function or service, instead of internally executing the function or service. The one or more external electronic devices which receive the request may execute at least a part of the function or service thus requested or an additional function or service associated with the request, and may provide a result of the execution to the electronic device <NUM>. The electronic device <NUM> may process the result as it is or additionally, and may provide the processed result as at least part of the response to the request. To this end, for example, a cloud computing, distributed computing, or client-server computing technology may be used. The electronic device according to various embodiments disclosed in the disclosure may be various types of devices. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a mobile medical appliance, a camera, a wearable device, or a home appliance. The electronic device according to an embodiment of the disclosure should not be limited to the above-mentioned devices.

Various embodiments of the disclosure and terms used herein are not intended to limit the technical features described in the disclosure to specific embodiments, and it should be understood that the embodiments and the terms include modification, equivalent, or alternative on the corresponding embodiments described herein. With regard to description of drawings, similar or related components may be marked by similar reference marks/numerals. The singular form of the noun corresponding to an item may include one or more of items, unless interpreted otherwise in context. In the disclosure, the expressions "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" may include any and all combinations of one or more of the associated listed items. The terms, such as "first" or "second" may be used to simply distinguish the corresponding component from the other component, but do not limit the corresponding components in other aspects (e.g., importance or order). When a component (e.g., a first component) is referred to as being "coupled with/to" or "connected to" another component (e.g., a second component) with or without the term of "operatively" or "communicatively", it may mean that a component is connectable to the other component, directly (e.g., by wire), wirelessly, or through the third component.

The term "module" used herein may include a unit, which is implemented with hardware, software, or firmware, and may be interchangeably used with the terms "logic", "logical block", "part", "circuit", or the like. The "module" may be a minimum unit of an integrated part or may be a minimum unit of the part for performing one or more functions or a part thereof. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the disclosure may be implemented with software (e.g., the program <NUM>) including one or more instructions stored in a storage medium (e.g., the internal memory <NUM> or the external memory <NUM>) readable by a machine (e.g., the electronic device <NUM>). For example, the processor (e.g., the processor <NUM>) of the machine (e.g., the electronic device <NUM>) may call at least one instruction of the stored one or more instructions from a storage medium and then may execute the at least one instruction. This enables the machine to operate to perform at least one function depending on the called at least one instruction. Herein, 'non-transitory' just means that the storage medium is a tangible device and does not include a signal (e.g., electromagnetic waves), and this term does not distinguish between the case where data is semi-permanently stored in the storage medium and the case where the data is stored temporarily.

<FIG> illustrates an operating environment of an intelligent system, according to an embodiment.

Referring to <FIG>, an intelligent environment <NUM> includes a first server device <NUM> (or the first server system) and a second server device <NUM>. The first server device <NUM> may provide various services in conjunction with the plurality of second server devices <NUM>. The second server device <NUM> may be a server device operated by a specific service provider. The operator of the second server device <NUM> may be the same as the operator of the first server device <NUM> or may be a third party different from the operator of the first server device <NUM>. When the operator of the first server device <NUM> is the same as the operator of the second server device <NUM>, the second server device <NUM> may be designed to have high access permission to data recorded in the first server device <NUM>. When the operator of the first server device <NUM> is different from the operator of the second server device <NUM>, the second server device <NUM> may be designed to have low access permission to data recorded in the first server device <NUM>.

The first server device <NUM> may communicate with the second server device <NUM> operated by the same operator or a different operator and may transmit or receive data to or from each other. The first server device <NUM> may communicate with an electronic device <NUM> (e.g., a smartphone or a tablet PC) in which an application distributed by the second server device <NUM> is installed and may transmit or receive data to or from the corresponding electronic device. For example, the first server device <NUM> may collect and manage the data entered by the user of an electronic device <NUM> or the data pre-stored in an electronic device <NUM> associated with the user. The first server device <NUM> may generate a user profile based on the collected data. The second server device <NUM> may make a request for the data associated with a specific user to the first server device <NUM>, and the first server device <NUM> may provide the data associated with the specific user to the second server device <NUM> based on the user profile. The second server device <NUM> may provide a specific user with the customized service based on the received data. The first server device <NUM> may constitute user-related data or a user profile in a form including an index (e.g., a name, a gender, an age, and a preferred food) and an item (e.g., Hong Gil-dong, male, <NUM> years, and tomato/onion) mapped to or matched with the corresponding index.

When a user device accesses the second server device <NUM>, the second server device <NUM> may transmit, to the first server device <NUM>, a query message for data associated with the accessing user device or data associated with a user operating the user device. The first server device <NUM> receiving the query message may extract at least one keyword from the query message and may detect information associated with the extracted keyword from the pre-stored user-related data. For example, the first server device <NUM> may detect the index associated with the keyword from the user-related data in which the index and the at least one item are matched with each other and may provide the second server device <NUM> with items associated with the detected index as a response message. Alternatively, when the index corresponding to the keyword is not present, the first server device <NUM> may determine the relationship between indexes and the keyword to select at least one index and may identify the relationship between at least one items mapped to the selected index to generate the response message. Further, when the index corresponding to the keyword is not present, the first server device <NUM> may detect an index of which the similarity with the keyword is not less than a specified value, and the first server device <NUM> may provide the second server device <NUM> with items matched with the corresponding index or a combination of items through the response message, or may identify the relationship between the items to provide data according to a relationship identification as the response message. <FIG> is a block diagram of a server device, according to an embodiment. <FIG> is an example of data stored in a profile database, according to an embodiment.

Referring to <FIG> and <FIG>, the first server device <NUM> includes a network interface <NUM>, a processor <NUM>, a memory <NUM>, and a profile database <NUM>.

Referring to <FIG>, the first server device <NUM> may communicate with an external device through the network interface <NUM>. For example, the external device may be another server device <NUM> or an electronic device <NUM>. The memory <NUM> includes (or stores) a profile generation module <NUM> and a profile conversion module <NUM>. The profile generation module <NUM> may collect data associated with a user and may generate the personalized user profile. For example, the user profile may include data associated with a specific user registered in a service provided through the first server device <NUM> and/or the second server device <NUM>. The user profile may include data for at least one of the personal information about the specific user, the interest of the specific user, or a favorite characteristic of the specific user.

The profile generation module <NUM> includes a meta data analysis module <NUM>, a profiling module <NUM>, a data delivery module <NUM>, and a data aggregate module <NUM>. The profile generation module <NUM> may be implemented by merging at least two or more of the above-described modules (i.e., the meta data analysis module <NUM>, the profiling module <NUM>, the data delivery module <NUM>, and the data aggregate module <NUM>). The profile generation module <NUM> (or modules) may be implemented with one or more hardware processors or one or more software modules, and may operate so as to be driven by at least one processor to process a corresponding function.

The data aggregate module <NUM> may collect data from the electronic device of a user or the server operated by a service provider. The collected data may be stored as log data <NUM>. The meta data analysis module <NUM> may analyze meta data for the log data <NUM>. For example, when the specific user executes a pizza-related application (e.g., pizza order application) and then orders a pizza by using the corresponding application, the log data <NUM> may include log information such as the execution of the pizza-related application, the access to a pizza providing service device, transmission and reception of a message, or a payment for ordering a pizza. In this procedure, the meta data analysis module <NUM> may obtain data for a pizza related service (a first service) as a type of meta data. For example, when obtaining a pizza related application identification (ID) "kr. A" (a first related application ID), a pizza related universal resource locator (URL) (a first URL), "www. kr", and a pizza related keyword (e.g., "pizza 'A', "A") (a first keyword) as the meta data, the meta data analysis module <NUM> may analyze the obtained meta data to select data capable of being applied to a user profile.

The profiling module <NUM> may generate or update a user profile based on the data analyzed by the meta data analysis module <NUM>. For example, the profiling module <NUM> may add "pizza" as a new index in the meta data and then may write a pizza menu (e.g., shrimp pizza) ordered by the user, as the matching item for "pizza". Alternatively, when the "pizza" index is already present, the profiling module <NUM> may add "shrimp pizza" as a new item. Alternatively, when both the index "pizza" and the index "shrimp pizza" are present, the preference or usage count of the index "pizza" and "shrimp pizza" may be updated. When receiving a query message from the second server device <NUM>, the data delivery module <NUM> may deliver a response message in response to the received query message. In this regard, the data delivery module <NUM> may provide a communication interface (e.g., public application program interface (API)) between an external device and the electronic device of the user.

The profile generation module <NUM> and the profile conversion module <NUM> may include instructions executed by the processor <NUM>. Modules described herein may be implemented by hardware or software. The operation performed by the profile generation module <NUM> and the profile conversion module <NUM> may be performed by the processor <NUM> of the first server device <NUM>. Two or more modules of the meta data analysis module <NUM>, the profiling module <NUM>, the data delivery module <NUM>, and the data aggregate module <NUM> may be integrated.

The data associated with a user may include data in various forms. For example, the data associated with the user may include the log data <NUM> associated with the user. The log data <NUM> may include the usage records of an application or the setting state of the electronic device of the user. The log data <NUM> may include the data history (e.g., account information or a user log generated by the first server device <NUM>) transmitted or received between the electronic device of the user and the first server device <NUM>. The profile generation module <NUM> may analyze the log data <NUM> and may generate a user profile <NUM>.

The log data <NUM> and the profile <NUM> may be stored in the profile database <NUM>. However embodiments are not limited thereto. The log data <NUM> and/or the profile <NUM> may be stored in the memory <NUM> or may be stored in another type of database. Alternatively, the log data <NUM> and the profile <NUM> may be stored in a separate memory distribution server device and may be implemented to provide the first server device <NUM> with log data and a profile through a communication interface.

The log data <NUM> may include log data associated with application usage of an electronic device, log data associated with web browsing, log data for the found keywords, log data for tags included in an image file, log data associated with voice function usage, and log data associated with the user's location. The profile <NUM> may include the index and at least one item generated based on the log data <NUM>. The profile <NUM> may include various categories such as the user's personal information, interests, favorite characteristics, news preferences, and/or activities. At least one index may belong to each category, or at least one or more items may be matched with at least one index. Hereinafter, each of the items may be referred to as an "index".

For example, the log data <NUM> and the profile <NUM> may be mapped to a specific user (or the electronic device of the specific user) and then may be stored. In this case, the log data <NUM> and the profile <NUM> associated with the specific user may correspond to a user profile. Alternatively, when the log data <NUM> and the profile <NUM> are not mapped to the specific user, the log data <NUM> and the profile <NUM> may correspond to (or be mapped to) the general profile for general users. The profile <NUM> may include a group profile for a plurality of users. The group profile may be generated based on the log data <NUM> obtained from users included in a specific group.

The first server device <NUM> may transmit at least part of a user profile to the second server device <NUM> at the request of the second server device <NUM>. When receiving a request for the item pre-stored in the profile <NUM>, the first server device <NUM> may transmit the response including the stored item to the second server device <NUM>.

When receiving a request for an item, which is not currently stored in the profile <NUM>, from an external device (e.g., the second server device <NUM>), the first server device <NUM> may generate a new item. The profile conversion module <NUM> may analyze the log data <NUM> and/or the profile <NUM>, may generate a new item based on the analysis result, and may transmit a response including the newly generated item to the second server device <NUM>. The profile conversion module <NUM> may update a user profile based on the received requests. For example, when receiving requests associated with the specific service, the newly generated item may be mapped to the specific service and then may be stored in the memory <NUM> or the profile database <NUM>.

In at least part of the specific user profile, "workout" may be present as a category; in at least part of the specific user profile, "baseball" may be present as the index of "workout"; and at least part of the specific user profile may include "Samsung or SK" as an item for "baseball". When receiving a request for information about a soccer team, which a user likes, from the second server device <NUM>, the first server device <NUM> may generate "soccer" as an index, may generate "Seoul football club (FC)" as a new item through the relationship analysis for the items. For example, "Samsung or SK" may be provided to the second server device <NUM> with a response message including the new item. In the provision procedure, the first server device <NUM> may provide a notification that there is no direct information about the soccer team that the user likes and may provide a notification that the Seoul FC information is information inferred based on the baseball team that the user likes. In a procedure of generating the new item, the first server device <NUM> may select a soccer team, which the user prefers based on items for the "baseball" index, (e.g., the home of Samsung or SK) as a new item or may select the soccer team, which the user is likely to prefer based on items for the "baseball" index (e.g., the season score of Samsung or SK), as a new item. When the new item is selected, the first server device <NUM> may newly add "soccer" index and "Seoul FC" item to the user profile. The first server device <NUM> may notify a user device (e.g., the electronic device <NUM> of <FIG>) that the user profile is scheduled to be updated and may apply the update after the approval is obtained from a user device.

A profile specification <NUM> may include a static profile and a dynamic profile. The profile <NUM> may be classified depending on the specification. The profile capable of being instantly provided to the plurality of second server devices <NUM> may be classified as the static profile. The profile newly generated by the request of the second server device <NUM> may be classified as the dynamic profile.

The static profile may include the item that is analyzed in advance and then is stored. Alternatively, the static profile may include an item corresponding to the predefined index. When the item not stored in advance is requested, the dynamic profile may include an item included in the newly generated response. The second server device <NUM> may not need to process and analyze raw data. In various embodiments, the analysis results stored in the dynamic profile may be shared with the second server device <NUM> and may be used again.

In a state where the second server device <NUM> knows a plurality of items included in the static profile, the second server device <NUM> may transmit a query for making a request for all or part of the plurality of items, to the first server device <NUM>. For example, the profile <NUM> provided by the first server device <NUM> may have three indexes including "name", "gender", and "age"; it is assumed that each respective index has items of "Hong Gil-dong", "male", and "thirties". The second server device <NUM> may make a request for all or part of the three items. The profile conversion module <NUM> of the first server device <NUM> may transmit a response to the query, which includes all or part of the profile <NUM>, to the second server device <NUM>. When a query for making a request for information about the user's "age" is received, the profile conversion module <NUM> may transmit a response including "thirties" as the item written in the "age" index, to the second server device <NUM>.

The second server device <NUM> may transmit, to the first server device <NUM>, a query including a request for a new item. The profile conversion module <NUM> may analyze the log data <NUM> and the profile <NUM> stored in the first server device <NUM> and may generate the new item as the dynamic profile.

In a state where indexes include a name, a gender, an age, a home address, and favorite ingredients in at least part of the user profile stored in the first server device <NUM>, the second server device <NUM> providing a pizza-related service may make a request for an item of "the user's favorite pizza menu", to the first server device <NUM>. When the search of an index corresponding to "the user's favorite pizza menu" fails, the profile conversion module <NUM> of the first server device <NUM> may infer "favorite pizza menus" based on pieces of pre-stored information. For example, when "pineapple" or "potato" items are present in the stored "favorite ingredients" index, the profile conversion module <NUM> may infer "the user's favorite pizza menu" item as "Hawaiian pizza" associated with "pineapple" or "potato" pizza based on the fact that "pineapple" or "potato" items are present in the stored "favorite ingredients" index. In this operation, the profile conversion module <NUM> may obtain the pizza menu sold by the second server device <NUM> and recipe information of the pizza menu and may generate a pizza menu associated with the pineapple and the potato as a new item. The first server device <NUM> may generate "Hawaiian pizza" and "potato pizza" as an item for the "user's favorite pizza menu" index and may transmit a response including the generated item to the second server device <NUM>. A method for generating a dynamic profile will be described with reference to <FIG>.

The profile conversion module <NUM> may extract the keywords of "favorite" and "pizza" from the query message, the relationship between the extracted keywords, and at least one of the indexes. For example, the profile conversion module <NUM> may select "age" and "gender" as the index of the relationship for "favorite pizza" and may generate a new item corresponding to the "favorite pizza" (new index) based on the relationship between the item "the thirties" matched with the selected index "age" and the item "male" matched with the selected index "gender". Alternatively, the profile conversion module <NUM> may collect the preference item based on the items "thirties" and "male" and may generate a new item corresponding to the favorite pizza based on the collected preference item. The profile conversion module <NUM> may search for profiles of a plurality of other users with "thirties" and "male" as an item value. When "cheese pizza" is found in the preference item of the profiles of other users a specified number of times (e.g., <NUM> times) or more, the profile conversion module <NUM> may identify "cheese pizza" as reliable data and may generate "cheese pizza" as a new item for the new index "favorite pizza". With regard to generating the new index, the profile conversion module <NUM> may generate the new index using at least one or more keywords extracted from the query message or may generate a natural language based on at least one keyword to utilize the natural language as the new index. With regard to item extraction corresponding to the new index, the profile conversion module <NUM> may randomly select at least one pre-stored indexes. Alternatively, the profile conversion module <NUM> may select at least one index based on a previous history (e.g., a history used to generate a new index), or may calculate the relationship between the new index and pre-stored indexes based on the at least one algorithm used to calculate the specified relationship and then may select indexes of the specific number, the result value of each of which is relatively high.

The first server device <NUM> may fail to infer the item requested by the query of the second server device <NUM>. For example, in a state where the profile <NUM> has indexes including "name, gender, and age" and three items are respectively matched with each index, the first server device <NUM> may receive a query for making a request for the item of "preferred pizza menus", from the second server device <NUM>. It may be difficult for the first server device <NUM> to infer the item of "preferred pizza menus" based on only the items included in the name, the gender, and the age. In this case, the first server device <NUM> may transmit a message to the second server device <NUM> indicating that it is impossible to send a response to the query. When the first server device <NUM> may not identify the index associated with the query of the second server device <NUM>, the first server device <NUM> may fail to infer the item requested by the query. When the profile <NUM> includes only the item "Il-do Park" for the index of "name", the first server device <NUM> may not identify the index associated with the query of "preferred pizza menus". In this case, the first server device <NUM> may transmit a message to the second server device <NUM> indicating that it is impossible to send a response to the query.

The first server device <NUM> may select a common item among the collected items, as the preferred pizza menu. For example, when the number of the factors (e.g., index "name" or item "Il-do Park") used in the relationship calculation is less than the specified number, the first server device <NUM> may provide a notification that it is impossible to respond to the query. Alternatively, the first server device <NUM> may generate a new item through the relationship calculation using finite factors to respond to the second server device <NUM>, and the first server device <NUM> may provide a notification that the reliability of the corresponding item is less than the specified value (e.g., send a message indicating that the reliability is not greater than the specified value).

The query including a request for a new item may have two forms. The first form may correspond to the response in the unrestricted form. When receiving a query in the first form, the profile conversion module <NUM> may generate a response in a general form, not a fixed form.

The query may include one or more interrogatives such as who, what, when, where, why, how, or which. The second form may correspond to the response in the restricted form. When receiving a query in the second form, the profile conversion module <NUM> may generate a response in the specified form based on the type of query, as shown below in Table <NUM>.

<FIG> is a signal flowchart illustrating a user profile providing method, according to an embodiment.

Referring to <FIG>, the user profile providing method includes steps <NUM> to <NUM>. Steps <NUM> to <NUM> may be executed by the first server device <NUM> illustrated in <FIG>. For example, steps <NUM> to <NUM> may be respectively implemented with instructions capable of being performed (or executed) by the processor <NUM> of the first server device <NUM>. The instructions may be stored in a computer-readable recording medium or the memory <NUM> of the first server device <NUM> illustrated in <FIG>. Hereinafter, with respect to the descriptions about steps <NUM> to steps <NUM>, descriptions which are equivalent to those shown in <FIG> may not be repeated.

In step <NUM>, the first server device <NUM> receives a query associated with a user profile from an external device <NUM>. For example, the query may be a query for making a request for the user profile necessary for the service (hereinafter referred to as a "first service") provided by the external device <NUM> (or a service providing server device). The query may be a query for making a request for the user profile for a user of the first service (e.g., a user has an account registered in an external device providing the first service to utilize the first service).

In step <NUM>, the first server device <NUM> determines whether the query received from the external device <NUM> is a query corresponding to the item matched with the pre-stored index or the corresponding index. For example, the first server device <NUM> may identify the index associated with the received query and may determine whether the received query is a query corresponding to the pre-stored item, based on the identified index.

In step <NUM>, the first server device <NUM> transmits the response including an item corresponding to the query to the external device <NUM>, when the query is a query corresponding to the pre-stored item. The profile conversion module <NUM> may generate a response including the items corresponding to the query without a separate conversion for the items stored in the profile <NUM> and may transmit the generated response to the external device <NUM>.

In step <NUM>, when the query is a request for an item not stored in advance, the first server device <NUM> determines whether the item associated with at least one keyword included in the query is included in the profile <NUM>. The first server device <NUM> may extract at least one keyword included in the query and may identify the relationship between the extracted keyword and an index. With regard to identifying the relationship, the first server device <NUM> may operate an algorithm or database that defines the relationship between an index and various keywords. Alternatively, the first server device <NUM> may communicate with a separate server device providing information about the corresponding relationship and may provide the corresponding server device with a keyword to identify the index having the relationship.

A plurality of items included in the profile <NUM> may have a relationship between each other. The plurality of items may have ontology depending on the relationship. The first server device <NUM> may use numerical data indicating the relationship between the plurality of items. If the relationship is relatively strong, then the numerical data may be configured to have a relatively high value. The numerical data may be stored in the profile database <NUM> in advance.

At least one keyword included in the query may include a word the same as or similar to the pre-stored at least one index. For example, when the query is "what is the preference order of "potato", "Hawaiian", or "super supreme" in pizza menus?", the keyword may be determined as at least one of "pizza", "potato", "Hawaiian", or "super supreme". When the relationship between the pre-stored first index and the determined keyword is high, the first server device <NUM> may generate the response including at least one item matched with the first index, as will be described with reference to <FIG>.

When the numerical data is not less than predetermined threshold value, the first server device <NUM> may determine that the keyword is associated with the index. The threshold value may be updated according to a software update.

In step <NUM>, when it is determined that the keyword included in the query is associated with the index, the first server device <NUM> transmits a response (e.g., a response including an item matched with the index) determined based on the associated index, to the external device <NUM>. When it is determined that the associated index is not present, the first server device <NUM> may add the keyword included in the query as a new item to the profile <NUM>. For example, the keyword included in the query may be added as one index included in the profile <NUM>. The keyword may correspond to (e.g., be included in or be mapped to) the name of the index to be added. The name of the index to be added may not be limited to the keyword included in the query, and the word associated with the query may be the name of the index to be added.

In step <NUM>, the first server device <NUM> determines whether the received query is the frequently received query. For example, when the query including the same keyword is received during the specified period for the specified number of times or more, the first server device <NUM> determines that the query as the frequently received query.

With respect to the frequently received query, in step <NUM>, the first server device <NUM> adds the keyword included in the query as one index to the profile <NUM>. In step <NUM>, the first server device <NUM> collects data for the additional index (e.g., collect and determine the item to be matched with the additional index) and may perform analysis (e.g., a profiling task).

Instead of step <NUM>, the first server device <NUM> may transmit a message to the external device <NUM> asking whether to add a query to the index of the profile <NUM>. When a positive response to the message is received, the first server device <NUM> may add the keyword included in the query to the index of the profile <NUM>.

An index management module that determines whether to add the index for items that are requested to be added by the external device may be included in the first server device <NUM>. In addition to the above-described method, the number of indexes and the number of items to be matched with an index may be restricted depending on the feature (i.e., type) of data to be collected and the environment in which the data is collected. For example, the index management module may restrict the addition of the item corresponding to the enquiry made by an external device that is not authorized for specific personal information or may restrict the addition of the item capable of being abused. The index management module may also delete indexes with few query response requests by external devices (when response requests occur during the specified period the number of times or less), and may delete items matched with the indexes with few response requests. Furthermore, the index management module may predict the demand of external devices and then may also add indexes and items according to the demand.

<FIG> is a view for describing a method of generating a profile, according to an embodiment. Referring to <FIG>, the first server device <NUM> obtains the log data <NUM> of various categories from a user device <NUM> in step <NUM>. For example, the log data <NUM> may include log data associated with application usage, log data associated with web browsing, log data for the found keywords, log data for tags included in an image file, log data associated with voice function usage, and log data associated with the user's location. The first server device <NUM> analyzes the log data <NUM> and then generates the profile <NUM> in steps <NUM> and <NUM>. The processor <NUM> of the first server device <NUM> may generate the profile <NUM> through the procedure of a predetermined processing <NUM>. The profile <NUM> may include at least one index associated with a user profile and at least one item matched with the index. The profile <NUM> may further include at least one category corresponding to the category of the at least one index. The item may be composed of a piece of data or one data set.

The profile <NUM> may have a plurality of indexes, and at least one item may be mapped to one index. The category may include user personal information, interests, favorite items, news preferences, activities, and possible activities. The index associated with the user personal information may include information such as a user name, a gender, an age, a height, and a weight. The index associated with the interests may include information such as music, a movie, and cooking. The index associated with the favorite items may include information such as a location, a brand, and a color. The index associated with the news preferences may include information such as stocks, society, politics, and economy. The index associated with the activities or the possible activities may include information such as climbing, swimming, and golf.

The first server device <NUM> may determine whether the received query is associated with at least one index among a plurality of indexes. When the relation between at least one index and the received query is more than a specified value, the first server device <NUM> may determine at least one item included in the at least one index as a response to the query.

The profile <NUM> is classified depending on the specification in step <NUM>. The profile determined as being provided to service providing servers (e.g., the at least one external device <NUM>) providing a user with a specified service may be classified as a static profile; the profile generated depending on the request (query) without being predetermined may be classified as a dynamic profile.

The profile <NUM> may be stored in the first server device <NUM> or may be stored in the user device <NUM>. The first server device <NUM> transmits a part of the profile <NUM> to the user device <NUM> in step <NUM> and in step <NUM>. When the profile <NUM> is stored in the user device <NUM>, the external device <NUM> directly transmits a query to the user device <NUM> in step <NUM>. When the profile <NUM> is stored in the first server device <NUM>, the external device <NUM> transmits a query to the first server device <NUM> in step <NUM>. The query is generated based on the public API previously distributed for the first server device <NUM> in step <NUM>.

<FIG> is a view illustrating an example of a data structure of profile data, according to an embodiment.

The profile <NUM> may include a plurality of categories, a plurality of indexes, and a plurality of items. The plurality of indexes may belong to one category; furthermore, at least one item may belong to one index. Referring to <FIG>, profile data includes a category <NUM>, an index <NUM>, an index code <NUM>, a value type <NUM>, a place <NUM> at which an item is stored, and an item example <NUM>.

The profile <NUM> may be stored in a platform (e.g., the intelligent environment <NUM> of <FIG>) including a device <NUM> of a user and/or the first server device <NUM>. Information corresponding to the platform may be included in the field <NUM>.

Only the value of a specific item may be stored in the user device <NUM>. In this case, when a query for an item is received from the external device <NUM>, the first server device <NUM> may obtain a value from the user device <NUM> to generate the response to the query or the user device <NUM> may directly generate the response to transmit the response to the external device <NUM>. Public API for the query for the item stored in only the first server device <NUM> may be provided. For example, when an index code "demo. income" is stored in only the first server device <NUM>, the external device <NUM> may generate the query for "demo. income", using the distributed public API and may transmit the query to the first server device <NUM>. The item may be exemplified as USD <NUM>-<NUM>, and the response including the corresponding value may be transmitted from the first server device <NUM> to the external device <NUM>.

The profile <NUM> may be classified into a static profile and a dynamic profile. The static profile may include items stored in the profile database <NUM> in advance. For example, fields <NUM> and <NUM> may be included in the static profile. The field <NUM> may include predetermined factors depending on the settings of the intelligent environment <NUM>. A field <NUM> may include factors added to the profile <NUM> at the request of the external second server device <NUM>. For example, factors included in the field <NUM> may be the index and the item, which are added in step <NUM> to step <NUM> in <FIG>.

In step <NUM> of <FIG>, the first server device <NUM> determines whether the received query is a request for the static profile or whether the received query is a request for the dynamic profile. When the received query includes a request for an item, which is included in the pre-stored profile <NUM>, in the profile database <NUM>, the received query may include the request for the static profile. When the received query includes a request for an item not included in the profile <NUM>, the received query may include the request for the dynamic profile.

The first server device <NUM> may identify the index associated with the received query and may determine whether the query is a query corresponding to the pre-stored item based on the identified index. When the first index (e.g., the gender, name, income, marital status, and/or birthday provided in field <NUM>) corresponding to at least one item included in the static profile is identified, the first server device <NUM> may determine the query as the query for the pre-stored item. When at least one index included in the dynamic profile or the second index (e.g., yes-no, choice, or ad-hoc ranking corresponding to field <NUM>) corresponding to an item is identified, the first server device <NUM> may determine that the query as the query for the item is not pre-stored.

The dynamic profile may include the index or items, which are not stored in the profile database <NUM> and which are requested by the second server device <NUM>. The index or items included in the dynamic profile may include the index or items generated through the analysis procedure based on the log data <NUM> and the profile <NUM> currently stored in the first server device <NUM>. The field <NUM> may be included in the dynamic profile. The field <NUM> may include the index or items that are stored in the different forms depending on the building form of the query. In the query of the above-described second form, the index name generated by the query corresponding to form <NUM>-<NUM> of Table <NUM> may be "yes-no"; an index code "adhoc. yes-no?q=espresso" and the stored item form may be stored in the form of yes (TRUE) or no (False).

<FIG> is a flowchart illustrating an operation of generating a response to a query for an item that is not stored, according to an embodiment.

Referring to <FIG>, it may be assumed that the external device <NUM> operated by "pizza company A" transmits query <NUM> to the first server device <NUM>, and receives a response <NUM> to the query <NUM>. For example, the external device <NUM> of the "pizza company A" may include the external device <NUM> for supporting the service of a company providing a service (e.g., pizza recommendation service) associated with pizza.

The first server device <NUM> may receive the query <NUM> for user <NUM> that is a specific user, from the external device <NUM>. The query <NUM> may include "what is the favorite pizza of user <NUM> from among "super supreme pizza", "potato pizza", and "Hawaiian pizza?". The query <NUM> may correspond to the query in form <NUM>-<NUM> of Table <NUM>.

Referring to a profile <NUM> associated with user <NUM>, because items included in the query <NUM> are not stored, the query <NUM> may correspond to a query including a request for items not included in the existing profile <NUM>.

The profile conversion module <NUM> of the first server device <NUM> may determine the relationship between a super supreme pizza, a potato pizza, and a Hawaiian pizza being the keywords included in the query <NUM> and the pre-stored profile <NUM>. Referring to the profile <NUM>, a garlic chicken <NUM>-<NUM> and a pineapple <NUM>-<NUM> may be pre-stored items.

A general profile <NUM> that digitizes the relationship between stored items for all users including user <NUM> may be defined. The general profile <NUM> may be stored in the profile database <NUM>. Referring to the general profile <NUM>, a "Hawaiian" item <NUM> included in the query <NUM> may be defined as having a strong relationship (e.g., a relationship whose the index is more than a specified value) with a "pineapple" item <NUM> previously stored in the profile <NUM> of user <NUM>. The distance between two items stored after being digitized may be within a specified distance (e.g., when the digitized information is entered in the specified coordinate system, the distance between two entered coordinates is within the specified distance). The "potato" item <NUM> included in the query <NUM> may be defined as having a very strong relationship with "garlic chicken" item <NUM>. For example, it may be understood that the distance between two items is a distance closer than the distance between item <NUM> and item <NUM>. On the other hand, the "super supreme" item <NUM> included in the query <NUM> may be defined as having a weak relationship (e.g., a relationship of which the index is less than a specified value) with the associated "pineapple" item <NUM>.

The first server device <NUM> may determine the preference order of user <NUM> as "potato pizza", "Hawaiian pizza", and "super supreme" based on the relationship defined in the general profile <NUM> and may generate a new item. The first server device <NUM> may transmit the response <NUM> including the newly generated item to the external device <NUM>.

<FIG> illustrates an operation of adding a new item, according to an embodiment. <FIG> is one example of a data structure of newly added profile data, according to an embodiment.

Referring to <FIG> and <FIG>, the index and item, which are generated depending on the received query, may be added to the profile <NUM> by the external device <NUM>. When the response to the query is not possible using items stored in the profile <NUM>, the item included in the query and the index corresponding to the item may be newly added to the profile <NUM>. Parts of the description describing <FIG> which are equivalent and/or correspond to features that are illustrated in <FIG> may not be repeated here.

The analysis algorithm for a new index and an item matched with the new index may be added such that the analysis of new items is possible based on the existing log data <NUM> and the existing profile <NUM>. The newly added algorithm may be applied to the profiling process <NUM> (e.g., the algorithm for service "A" or the algorithm for service "B"). The different algorithms may be added for each external device of service providers that are different from one another.

The first server device <NUM> may add the category of the collected log data <NUM>. The new index may be added to the log data <NUM>; alternatively, a new item may be added to an existing index. In addition, the first server device <NUM> may receive data necessary for the new index and/or new item, from the external device <NUM>. The first server device <NUM> may process a new query based on the newly added log data <NUM>.

The new index or new item may be configured to be provided to only the external device of the corresponding service provider or may be configured to be provided to the external devices of all service providers. The public API may be updated to build the query for the new index or the new item. The external device <NUM> may generate a request for the newly added index or the newly added item as a query, using the public API in step <NUM> and <NUM>.

Referring to <FIG>, the first server device <NUM> may map the items added in association with a specific service to an index for the specific service to manage the mapped result. The first server device <NUM> may allocate a separate index <NUM> and a separate index code <NUM> such that the added first index and the added first item, depending on the request by a service providing server device "A" operated by a service provider "A" are distinguished from the added second index and the added second item, depending on the request by a service providing server device "B" operated by a service provider "B".

The service providing server device may deliver information about the logic or algorithm, which analyzes the log data <NUM> and the profile <NUM>, to the first server device <NUM> to obtain a new item. For example, the "favorite pizza menu" index requested by the service providing server device "A" may be determined by the analysis task that identifies the item associated with pizza in the log data of the web search of a user and adds the rank of pizza menus to the item depending on the frequency of which the item associated with the pizza menu occurs (i.e., appears in a search of the user). When it is determined that the favorite pizza menu is added, a module implemented to perform the corresponding analysis task may be added to the memory <NUM> of the first server device <NUM>. The favorite pizza menu of the index <NUM> may belong to a service category "A"; the index code <NUM>, the value type <NUM>, the item assignment state <NUM>, and the logic or algorithm <NUM> corresponding to the index may be written as a profile value. <FIG> illustrates the single index <NUM>, the single index code <NUM>, the single value type <NUM>, the single item setting <NUM> and the single logic/algorithm <NUM> being assigned to one service (e.g., service "A"). However, the disclosure is not limited thereto. For example, a plurality of indexes may be included in one service; and a plurality of items may be included in one index. <FIG> illustrates an example of an interface of an electronic device of a user, according to an embodiment.

Referring to <FIG>, an interface <NUM> including a list of information collected from the user device <NUM> is illustrated. A user may determine what category of information is collected through the interface <NUM> and is generated as a profile. The user may determine whether the collection is turned on/off depending on the category of data through the interface <NUM>. When the size or category of data collected or analyzed is changed, an interface for providing a notification that the size or category of data is changed may be provided to the user. Also, an interface for determining whether the user agrees with the notification may be provided. When an additional request for a new item of a service provider occurs, an interface for notifying the user that the additional request occurs and for receiving consent may be provided.

An electronic device (e.g., the first server device <NUM>) may include a network interface <NUM> communicating with an external device operated by a service provider providing a first service, at least one memory <NUM> storing a user profile including at least one item, and at least one processor <NUM> operatively connected to the network interface <NUM> and the at least one memory <NUM>. The at least one processor <NUM> may be configured to receive a query associated with the user profile from the external device, to determine whether the query corresponds to the at least one item included in the user profile, to transmit a response including the at least one item to the external device when the query corresponds to the at least one item, to generate a new item, which corresponds to the query and which is not included in the user profile when the query does not correspond to the at least one item, and to transmit a response determined based on the new item, to the external device.

The user profile may include at least one index, and the at least one item may be matched with the at least one index.

The at least one processor may be configured to extract at least one keyword included in the query, to select an index in which a correlation indicating a relationship between the keyword and the at least one index is not less than a specified value, and to generate the new item based on at least one item included in the selected index.

The at least one processor may be configured to determine that the at least one index is associated with the at least one keyword, when a value defined between the at least one keyword and the at least one index is not less than a threshold value based on numerical data indicating the relationship.

When the at least one keyword included in the query coincides with a first index of the at least one index, the at least one processor may be configured to transmit a stored item corresponding to the first index as the response to the external device.

The at least one processor may be configured to add an additional index or an additional item corresponding to the at least one keyword, to the at least one memory when the query does not correspond to the at least one item.

The at least one processor may be configured to determine that the associated index associated with the at least one keyword is not present, when a value defined between the at least one keyword and the at least one index is less than a threshold value based on numerical data indicating the relationship, and to add the additional index or the additional item to the at least one memory when the associated index is not present.

The at least one processor may be configured to add the additional index or additional item to the at least one memory when the query is received a predetermined number of times or more. The at least one processor may be configured to transmit a message for determining whether to add the at least one keyword, to the external device when the query does not correspond to the at least one item, and to add the additional index or the additional item when a response to the message is received from the external device.

The at least one memory may store an analysis module corresponding to the additional index or the additional item, and the at least one processor may be configured to set a value corresponding to the additional item based on the analysis module and the at least one index. The at least one processor may be configured to map the additional index or the additional item to the first service to store the mapped result in the at least one memory.

The at least one processor may be configured to receive a second query from an external device operated by a service provider of a second service and to add a second additional index or a second additional item corresponding to the at least one keyword included in the second query, to the at least one memory when the second query does not correspond to the at least one item. The second additional index or the second additional item may be mapped to the second service and stored in the at least one memory.

The at least one memory may store log data associated with the user.

The at least one processor may be configured to obtain the log data from a user device communicating through the network interface or the external device.

As described above, a system (e.g., the first server device <NUM>) may include a network interface <NUM>, at least one processor <NUM> operatively connected to the network interface <NUM>, and at least one memory <NUM> operatively connected to the processor <NUM>. The at least one memory <NUM> may be configured to store a user profile including a plurality of indexes and a plurality of items associated with the plurality of indexes, and the at least one memory <NUM> may store instructions that, when executed, cause the processor <NUM> to receive a query associated with the user profile from an external server through the network interface, to identify whether the query is associated with at least one index among the plurality of indexes, to identify a relationship between at least one item of the plurality of items based on ontology when the query is not associated with the at least one index among the indexes, to determine a response to the query based at least partly on the relationship, and to provide the response to the external server through the network interface.

The instructions may cause the processor to determine at least part of the user profile as a response to the query when the query is associated with the at least one index among the plurality of indexes.

The relationship may include a value indicating a correlation corresponding to the at least one item of the plurality of items.

The instructions may cause the processor to determine whether the value exceeds a threshold value, and to determine at least one item different from the at least one item of the plurality of items, as a response to the query when the value exceeds the threshold value.

The at least one memory may store a database including first data at least partly used to generate the user profile. The instructions may cause the processor to change the database such that the database further stores items at least partly associated with the query when the value does not exceed the threshold value.

The instructions may cause the processor to further use second data, which is included in the database and which is different from the first data, to generate a profile when the value does not exceed the threshold value.

A method according to various embodiments disclosed herein may be provided to be included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)) or may be distributed (e.g., downloaded or uploaded), through an application store (e.g., PlayStoretm), directly between two user devices (e.g., smartphones), or online. In the case of on-line distribution, at least part of the computer program product may be at least temporarily stored in the machine-readable storage medium such as the memory of a manufacturer's server, an application store's server, or a relay server, or may be generated temporarily.

Claim 1:
A server device (<NUM>), comprising:
a network interface (<NUM>) configured to communicate with an external device (<NUM>) operated by a service provider providing a first service;
at least one processor;
a memory (<NUM>) for storing a user profile (<NUM>) including information associated with a user, the user profile comprising a plurality of indexes and a plurality of items, wherein each of the plurality of indexes includes data associated with at least one category of the information associated with the user, wherein each of the plurality of items is an instance of the data included in at least one index of the plurality of indexes, wherein the memory further storing instructions that, when executed by the at least one processor individually or collectively, cause the server device to:
receive (<NUM>, <NUM>) a query message associated with the user profile from the external device through a communication channel established between the server device and the external device,
extract at least one keyword included in the query message,
detect information associated with the extracted keyword from the stored user profile,
detect whether the extracted keyword corresponds to an index of the plurality of indexes included in the user profile,
when the extracted keyword in the query message corresponds to the index of the plurality indexes included in the user profile, transmit (<NUM>), to the external device, a response including the at least one item to which the index is mapped, and, characterized in that
when the extracted keyword in the query message does not correspond to an index of the plurality indexes included in the user profile:
select a further index included in the plurality of indexes in which a correlation corresponding numerical data indicating a relationship between the keyword and the selected index is not less than a threshold value
when a value defined between the keyword and the further index is not less than the threshold value, based on numerical data indicating the relationship, determine that the further index is associated with the keyword;
generate, based on at least one item included in the selected index, a new item, which corresponds to the query message and which is not included in the user profile, and
transmit (<NUM>) a response determined based on the new item, to the external device.