KR101471522B1 - System for providing personal information based on generation and consumption of content - Google Patents

Abstract

A personal information providing system based on generation and consumption of contents is disclosed.
The device of the system extracts the metadata based on the contents and the user's access to the contents. The server of the system generates information about the association between the user's content consumption and content creation. Devices and servers synchronize content and metadata associated with content. The metadata may include at least one of information about the content consumption of the user, information about the user's content creation, information about the user's behavior for content consumption, and information about the behavior of the user for content creation.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a personal information providing system based on generation and consumption of content,

The following embodiments relate to a personal information providing system.

Disclosed is a system for providing personal information about a user based on user's content creation and content consumption.

This study was conducted as a result of the research project supported by the IT Research Center of the Ministry of Knowledge Economy and the Korea IT Industry Promotion Agency. (NIPA-2011- (C1090-1111-0013))

Users produce and consume personal digital content through the various devices they own. As a user device, there are a personal computer (PC), a laptop, a smart phone, and a tablet. As various devices are used, users can directly produce content in an environment where they can use PCs and laptops. In addition, the user can apply and consume the produced content through a smartphone or tablet in a poor service access environment, such as when traveling on a vehicle or on foot.

As users produce and consume information in a variety of environments, the user desires to be able to access and consume the content at any time through the multi screen provided by the environment-aware device.

To meet the needs of users such as those described above, various personal cloud services have been introduced. The cloud service may provide an automatic synchronization service for the content between multiple devices.

Cloud services can improve accessibility to users' content in a variety of environments where multiple devices can be used.

One embodiment may provide an apparatus and method for generating information about an association between a user's content consumption and content generation.

One embodiment may provide an apparatus and method for extracting metadata based on a user ' s access to content and content.

In one aspect, a cloud storage for synchronizing content and metadata associated with the content with a device, the metadata including information about a user's content consumption, information about the user's content creation, Wherein the metadata includes at least one of information about an activity of the user and information about an action of the user for content creation, metadata that generates information about an association between the content consumption of the user and the content generation based on the metadata A knowledge engine, and a provider for providing the information.

The association may be an association between the first content generated by the user and the at least one second content the user has consumed.

The at least one second content may be the basis of generation of the first content.

The providing unit may provide the list of the at least one second content in the order of time or keyword.

The metadata knowledge engine may represent the association as a graph.

The metadata knowledge engine may extract the user's interest based on the association information.

The cloud storage unit may generate the metadata based on the access of the device to the content.

The cloud storage unit may receive the metadata from the device through the synchronization.

The cloud storage unit may receive the metadata from the external service provider through a public application programming interface provided by an external service provider.

The device may be a plurality of devices.

The server may further include a presence confirmation unit that manages information of available devices among the plurality of devices.

In another aspect, there is provided an agent for synchronizing content and metadata associated with the content with a server, the metadata including information about a user's content consumption, information about the user's content creation, And a metadata extraction unit for extracting the metadata based on the content and the user's access to the content. The device according to claim 1, Is provided.

The agent may periodically upload the metadata to the server.

In another aspect, there is provided a method comprising: synchronizing content and metadata associated with the content with a device, the metadata comprising information about a user's content consumption, information about the user's content creation, Wherein the metadata includes at least one of information about an activity of the user and information about an action of the user for content creation; generating information about an association between the content consumption of the user and the content generation based on the metadata; And providing said information. ≪ Desc / Clms Page number 2 >

In another aspect, there is provided a method comprising: synchronizing content and metadata associated with the content with a server, the metadata comprising information about a user's content consumption, information about the user's content creation, Wherein the metadata includes at least one of information about an activity of the user and information about an action of the user for creating content, and extracting the metadata based on the content and a user's access to the content. A providing method is provided.

In another aspect, the at least one device includes at least one device and a server, wherein the at least one device is an agent that synchronizes content and metadata associated with the content with a server, the metadata comprising information , Information about the user's content creation and information about the user's behavior for content consumption, information about the user's behavior for content creation, and information about the user's behavior for the content and the content And a metadata extraction unit for extracting the metadata based on the access, wherein the server synchronizes the content and the metadata associated with the content with the device. A metadata knowledge engine that generates information about an association between the content consumption of the user and the content generation based on the metadata, and a providing unit that provides the information.

An apparatus and method for generating information about an association between a user's content consumption and content generation is provided.

An apparatus and method for extracting metadata based on user ' s access to content and content are provided.

1 is a configuration diagram of a cloud system according to an embodiment. A block diagram of the server.
2 is a block diagram of a server of a cloud system according to one embodiment.
3 is a block diagram of a device in a cloud system in accordance with one embodiment.
FIG. 4 shows metadata of content according to an example.
FIG. 5 shows information on a user's behavior for content consumption or content creation according to an example.
FIG. 6 illustrates an association between metadata according to an example.
7 is a flowchart of a method of providing a cloud service according to an embodiment.
FIG. 8 illustrates personal information life management according to an example.
FIG. 9 illustrates a user interface of personal information life management according to an example.
FIG. 10 illustrates a cloud system using multiple servers according to an example.
FIG. 11 illustrates functions of the metadata server and the presence server according to an example.
12 illustrates functions of the metadata server and the RDF server according to an example.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to or limited by the embodiments. Like reference symbols in the drawings denote like elements.

The user may want to manage the digital content produced by the user himself or in the form of a batch of digital content participating in the production process. For example, a user can directly produce specific content through social media, and participate in the process of producing specific content. Here, the management of content refers to information on what search the user has performed, information on what kind of data the user has read, information on what kind of data the user has bookmarked, Information about whether or not the user has downloaded the document, or information on what kind of document the user has created.

In the following, the content may be embodied as digital content. In addition, the terms " client "," client device ", and " device " may be used interchangeably and may be interchanged. The term 'metadata' can be replaced by 'meta information'. The 'information' may include 'metadata' or 'meta information'. The term 'cloud system' can be replaced by 'meta cloud system'.

Communication through electronic equipment and the production of digital contents become common and it becomes possible to record and retrieve an individual's digital life. Related research has been conducted under the name of "lifestream" or "life log". In recent years, as users' staying time on social services has increased, user activity on social network services has increased. Social lifestream "and life 2.0 (" life 2.0 ").

The life stream may mean that the information generated by the user through the device and stored in the form of a document in which the generated information is exchanged with another user is stored. Here, details transmitted and received between users may include electronic mail, picture, bill, and movie files. That is, the life stream can be considered a concept focused on generating a digital log. As the use of the world wide web has become commonplace, the need for recording and updating of digital life has increased.

As the penetration rate of PCs increased and the Internet became available through networking enabled terminals, the necessity of recording content creation and content consumption in the user's point of view emerged in earnest. As the access to online content through a web browser is facilitated and the frequency of the access is increased, a service can be provided that enables sharing of records related to individual users' use of the Internet service.

Such a service can provide the same content access function as in the previous environment based on the consumption history to the user even in a changed environment such as a different PC or a different browser by confirming and memorizing the consumption history of the user for the content or the Internet service . Such a service can provide services such as mutual recommendation based on the degree of similarity between bookmark information of users at a time when data of a large number of users is acquired over time.

In addition, the above service can prevent a user from accessing or consuming contents redundantly by providing a history of contents consumed by a user, and can prevent a user from using various devices in different environments where different devices are used Access the same content list.

In addition, in the aspect of a user interface (UI), the above-described service enables a user to register and utilize URLs related to contents more easily by using JavaScript or the like.

In the following, a service is provided that provides a consistent form of management functionality for content that is directly produced by the user or participated in the production process. For example, the above-described service can provide a technique of utilizing the bookmark information generated by the user in terms of the flow of information consumption by the user.

1 is a configuration diagram of a cloud system according to an embodiment. A block diagram of the server.

The cloud system 100 may be a system for providing personal information. The cloud system 100 may include a server 110 and a device 120.

The device 120 may be a plurality of devices. The device 120 may be a client receiving a service from the server 110. The device 120 may be a device that can be used by a user, such as a mobile device and a PC. A mobile device may include smart phones, tablets, laptops, and the like. That is, the device 120 may be a client device used by users in a multi-device environment.

1, a cloud is a service that enables each user to effectively access and manage content consumed or produced by the user himself or herself and metadata associated with the content in a multi-device environment, based on a computing infra It can mean. That is, the cloud of FIG. 1 may represent a cloud system that provides metadata management.

Here, the content may refer to various files that can be created by a user directly using a PC or a software or application of a mobile device. Here, the file may include a video file, an audio file, and a rich text file.

Metadata may refer to information gathered through the device 120 or collected by a service used by a user in a web environment, all the way in which a user creates and consumes content.

The metadata may include metadata of contents, metadata of services, or metadata of users, which occurs when a user consumes contents or services. The user's metadata may include an audience measurement. That is, the metadata includes information on 1) content, 2) information on user's content consumption, 3) information on user's content creation, 4) information on the user's behavior for content consumption, and 5) And information on the behavior of the user for the user.

The server 110 may receive metadata from various entities connected to the cloud system 100. Thus, the cloud system 100 may be referred to as a meta cloud system.

The server 110 may receive metadata from at least one device 120. [ The above metadata may include communication metadata mainly due to communication among users. The communication metadata may be metadata for voice data. In addition, the metadata may be file-based metadata. File-based metadata may be metadata about playing, creating, editing, reading, and deleting a file. At least one device 120 may communicate with the server 110 via an agent. In Fig. 1, the agent is indicated using the symbol "A ".

In addition, the server 110 may receive metadata from a browser of the device 110 that receives the web from the browser of the server 110 or the server 110. The metadata may be browsing based metadata. Browsing-based metadata may be metadata about playback or reading of content provided through a browser.

In addition, the server 110 may receive social metadata from an external web server 130 (or a social network service server) that provides a social network service. The social metadata may be metadata about a user's behavior, a user's behavior, and a user's communication. The social metadata may be metadata about a message, location, and like.

In addition, the server 110 may receive meta data via the Internet.

2 is a block diagram of a server of a cloud system according to one embodiment.

The server 110 may include a cloud storage unit 210, a metadata knowledge engine 220, a provider 230, and a presence confirmation unit 240.

The cloud storage 210 may synchronize the content and the metadata associated with the content with the device 120. The cloud storage unit 210 may store the details of the contents consumed by each of the users and the contents and contents that should always be accessible by the device 120 among the contents produced directly by the users.

The metadata knowledge engine 220 may generate information about the association between the user's content consumption and content creation based on the metadata. The metadata knowledge engine 220 can extract and process metadata about dozens of contents for each user, and can provide a flow of information consumption and information generation by the user.

The provider 230 may provide the information generated by the metadata knowledge engine 220. The providing unit 230 can allow the user to easily grasp the details of utilizing the contents. The providing unit 230 may provide information generated by the metadata knowledge engine 220 through a graphical user interface (GUI) in the form of a media library. The GUI can be Web based.

The presence verification unit 240 manages information of the available (i.e., accessible) device 120 of at least one device 120 in the cloud system 100 and tracks movement and change history for each device 120 can do.

3 is a block diagram of a device in a cloud system in accordance with one embodiment.

The device 120 may include an agent 310 and a metadata extractor 320.

The agent 310 may synchronize content and metadata associated with the content with the server 110. The agent 310 may synchronize the content (i.e., the physical file) and the metadata related to the content with the cloud storage unit 210 of the server 110, in accordance with the type of the various devices. In addition, agent 310 may support remote sharing of content.

The agent 310 may be downloaded and installed into the device 120 in the form of an application.

The metadata extraction unit 320 may extract metadata based on the user's access to the content and the content. The metadata extracting unit 320 may extract various types of devices, extract the details of the user's content consumption through the device, and metadata about the content production.

FIG. 4 shows metadata of content according to an example.

Metadata can be generated based on content. That is, the content may provide different types of metadata depending on the type. The metadata generated based on the content can be named as the content metadata.

The content may include: 1) personal settings and statistic data on the application, 2) multimedia files, 3) text from voice, 4) document files, 5) Web files, and 6) tags. The multimedia file includes an audio file, a video file, and an image file. Document files include an office file, a Portable Document Format (PDF) file, and a text file. The web file includes a web page and a search log. A tag is generated by a user tagging information of a specific content at will. The tag can increase the accuracy of the metadata for the content.

Here, the content may be a general file. That is, the metadata extracting unit 320 can check a general file, determine the type of the content provided by the file, and extract various types of metadata from the file according to the type of the content .

In Figure 4, the type of content has been categorized as video, music, video, text, text from audio, and web pages. The above classification may be exemplary only. For example, the type of content may further include personal settings on the above-described application, statistical data on the application, search logs, and tags. In addition, in Fig. 4, the names and descriptions of the types of metadata that can be extracted from the contents are shown for each type of contents. The name may be a name that the cloud system 100 uses to identify the type of metadata, and may be replaced with another name indicating the same or similar meaning.

For example, when the content is a video, the metadata extraction unit 320 extracts, from the file, a unique identifier (ID) of the content, an ID of the owner of the file, a device (or storage) A file name, a file size, a Uniform Resource Locator (URL), a file type (or a file extension), a file registration date, a file modification date, a file deletion date, a resolution, Information (or latitude and longitude information) and grade, and the like can be extracted as metadata.

The name and description of the metadata shown in FIG. 4 may be an example for explaining that the types of metadata extracted by the metadata extraction unit 320 may differ from each other only depending on the type of the content. The metadata extracting unit 320 may extract various types of metadata from contents having a specific type, in addition to those shown in the figure.

FIG. 5 shows information on a user's behavior for content consumption or content creation according to an example.

Metadata can be generated based on user behavior. The metadata generated based on the user's action can be named as the user's action metadata.

The agent 310 may be a subject that collects user actions. Here, the user action may be for content consumption or content creation. That is, the content may be consumed or created by user action. The agent 310 receives information on the user's content consumption, information on the user's content creation, information on the user's behavior for content consumption, and on the user's behavior for content creation based on the collected user activity. And the like can be generated.

Table 1 below lists the types of user actions and describes each type.

User action type Explanation File access Access to multimedia files, document files and web files read Reading personal settings and statistical data, documents and web files on the application Save or write, Writing personal settings and statistical data in the application, multimedia files, document files, web files, etc.
Recognition, voice recording, etc. play Play multimedia files and music communication File transfer (send), file sharing (sharing), and voice communication Social behavior Like, likewise, retwit, and following

The user behavior types listed in Table 1 and the description of each type are merely illustrative.

The subject for extracting the user behavior metadata may be the agent 310 of the device 120, the metadata knowledge engine 220 of the server 110 and the external web server 130 (or the external web server 130 An open application programming interface (API), etc. The agent 310 can be classified into a PC agent operating on a PC and a mobile agent operating on a mobile device.

5, a PC agent, a mobile agent, a cloud, and an external web server are shown as subjects for extracting user behavior metadata. Here, the cloud may represent a meta cloud or server 110. The PC agent and the mobile agent may represent the agent 310 of the PC and the agent 310 of the mobile device, respectively. Also, in Fig. 5, it is enumerated whether each subject can extract user behavior metadata having a functional feature. In addition, for each subject and each functional characteristic, a criterion for the subject to extract the user behavior metadata, a manner in which the subject extracts the user behavior metadata, and a condition for the subject to extract the user behavior metadata have been described .

In FIG. 5, the circular symbol may indicate that the subject is able to extract user behavior metadata with a particular functional trait. The triangle symbol may indicate that the subject can extract some or some of the user behavior metadata with a particular functional trait.

FIG. 6 illustrates an association between metadata according to an example.

In a typical proposal generation job or document generation job, user behavior may include 1) file creation and file content creation, 2) data reference, and 3) opinion convergence.

The file creation includes: 1) creating a document file (e.g., a presentation file or a word processor file), 2) determining a template to be used for the generated file, and 3) And the like.

References to data include: 1) referencing a web page, a PDF file, a word processor file, and a presentation file to create the contents of a proposal (or document) on the Internet, for example, and 2) Downloading, and the like.

Observations may include: 1) gathering opinions from others through discussions, 2) performing voice recording of the opinions of others, and 3) extracting text from the recorded voice.

The thinking process of the user and the content created by the user can develop into a mutually similar form. Here, the user's thinking process can be expressed in the direction of development of thinking and thinking. That is, file-based or voice-based content referenced (or utilized) by the user as the user develops the incident may be considered to reflect the user's accident. Accordingly, the agent 310 or the like extracts the content metadata of the content or the user behavior metadata about the content, and analyzes the extracted metadata in text form by the metadata knowledge engine 220 or the agent 310, And what kind of thinking is centering on the thinking process.

In FIG. 7, the creation 610 of a file generated by the user may indicate the beginning of the user's accident, and the local files 620, web pages 630, Voice 640, etc. may indicate the direction of development of the user's thoughts and thoughts. Also, a done done 650 of the file generated by the user may indicate the end of the user's accident. Here, the local files 620 may be content that exists inside the cloud system 100 and can be referred to in the cloud system 100. Web pages 630 may refer to content that is external to the cloud system 100.

7 is a flowchart of a method of providing a cloud service according to an embodiment.

The following cloud service providing method (or meta cloud service providing method) can be regarded as a personal information providing method. That is, the device 120 and the server 110 may be regarded as providing the user's personal information, respectively.

In step 710, the device 120 may generate the content. The content may be generated by a user's operation.

At step 720, the agent 310 of the device 120 may monitor physical changes in the content. The agent 310 may monitor a folder or storage space. Here, the folder or storage space may be a specific folder or storage space, and may be a specified folder or storage space, for example, according to the setting of the user. If the agent 310 detects a change in the folder or the storage space as a result of the monitoring, the agent 310 may perform the synchronization of the step 730.

Step 720 may be referred to as an aggregation and capture process.

At step 730, the metadata extraction unit 320 of the device 120 may extract metadata based on the content and the user's access to the content. Here, the metadata extracted based on the content may be the above-described content metadata. The extracted metadata based on the user's access to the content may be the above-described user behavior metadata.

The device 120 may be a plurality of devices. The plurality of devices 120 may extract metadata based on the content stored by the device 120 and the user's access to the content.

The existence confirmation unit 240 manages the information of the available (i.e., accessible) devices 120 among the plurality of devices 120 in the cloud system 100, And change history.

Step 740 may be considered a presence and an accessibility process.

At step 750 the agent 310 of the device 120 and the cloud storage 210 of the server 110 may synchronize the content and the metadata associated with the content with each other. Here, it may mean that the synchronized device 120 and the server 110 share metadata related to content and content. For synchronization, the agent 310 may periodically upload the metadata to the cloud storage 210 of the server 110. In the above upload, the agent 310 can upload only the metadata, not the physical content (that is, the file), to the cloud storage 210. The device 120 in which the server and the metadata related to the content and the content are synchronized may be the device 120 determined to be usable by the existence confirmation unit 240.

The cloud storage unit 210 stores contents of the storage unit 210 based on the storage capacity of the cloud storage unit 210, the bandwidth of the network between the server 110 and the device 120, , File) can be synchronized only with the metadata.

The cloud storage 210 may receive metadata from the device 120 through synchronization.

In step 760, the cloud storage 210 may generate metadata based on the access of the device 120 to the content. That is, the metadata can be extracted for the content passing through the cloud storage unit 210. [ When the physical content exists in the cloud storage unit 210, the user can upload the content to the cloud storage unit 210 through a method using the cloud storage unit, and the user can upload the content stored in the cloud storage unit 210 It is accessible. In addition, the content stored in the cloud storage unit 210 may include content transmitted to the cloud storage unit 210 through synchronization, and may include content in a synchronized folder or storage space. The user may access the content via the device 120.

In step 770, the cloud storage 210 may receive metadata from an external service provider through an open API provided by the external service provider. Here, the external service provider may be the external web server 130 described above.

Metadata received from external service providers can be viewed as user's personal information. The cloud storage unit 210 may provide the user (or the device 120 with which the user operates) the functions necessary for collecting personal information from the external service provider and the above consent for the collection. The cloud storage unit 210 can perform third-party authentication on the external service and can store information (for example, user log-in information) necessary for performing the above-described operations. have. In addition, the cloud storage unit 210 may provide the user with a third party authentication and a consent procedure for collecting the above information. The cloud storage unit 210 may periodically perform data collection on the collected information. In addition, the cloud storage unit 210 may request re-authentication from the external service provider when the account authentication for the external service is aborted.

At step 780, the metadata knowledge engine 220 of the server 110 may generate information about the association between the user's content consumption and content creation based on metadata. Here, the content consumption may mean the above-described user action.

Steps 750 through 780 may be considered a storage and analysis process.

At step 790, the provider 230 of the server 110 may provide information about the association between content consumption and content creation.

The association may be an association between the first content created by the user and the at least one second content the user has consumed. The consumption may refer to the user's access to the second content or the user's behavior to the second content. The at least one second content may be content based on generation of the first content. That is, the first content may be generated through a user's access, reference, or action to at least one second content.

The provider 230 may provide a list of at least one second content in the order of time or keyword.

The order of the steps 710 to 790 described above is merely exemplary. The above-described steps 710 to 790 may be performed concurrently (e.g., by each of device 120 and server 110) and may be performed in reverse order with respect to each other. In addition, the device 120 and the server 110 may repeat the above-described steps 710 to 790 repeatedly until a specific condition is met.

FIG. 8 illustrates personal information life management according to an example.

The personal information lifecycle management is a function that allows the providing unit 230 to confirm contents of a series of actions performed by the user from the time when the user creates a specific content to the time when the generation is completed And management functions. Here, a series of actions performed by the user may mean that the user refers to the content (e.g., file), and the content may refer to a history of the user's content reference. The provider 230 may provide the above history in the order of time, subject or keyword (descending or ascending order).

The cloud storage unit 210 of the cloud system 100 may use the process applied to the content creation, the generated content, and the metadata for the referenced content and the (generated or referred to) content to provide a history Can be archived in the metadata database

FIG. 9 illustrates a user interface of personal information life management according to an example.

The metadata knowledge engine 220 may graphically represent the association between the first content generated by the user and the at least one second content consumed by the user.

The graph 900 may include content, user behavior, keywords (or tags). That is, UI objects in the graph may include content, behavior, and keywords. The objects may be ordered by date. This sorting can represent the user's flow of thought and the relationship between objects in a time series. Associations between objects can be represented by arrows.

In Fig. 9, the consumed contents 910 and 920 are shown for generating content. The name or keyword of the first consumed content 910 is a " WoO Proposal ", and the type of content is a word processor file outlined in "DOCX ". The name or keyword of the second consumed content 920 is "# 2 Proposal ", and the content type is voice. Also, extracted keywords 930 and 940 are shown. The first extracted keyword 930 is "FP7 WoO ", and the second extracted keyword 940 is" Reference ". As external information, information 952 by the device-to-communication M2M, information 954 about the internet of things, and information 956 about the web in the operating system are shown. Also, the generated content 960 is displayed. The name or keyword of the generated content 960 is "WoO Proposal ", and the content type is a presentation file outlined in" PPTX ". The graph 900 may be regarded as a UI created based on the generated content 960. [

If the external information points to a keyword through an arrow, the arrows above may indicate that the external information and the keyword are relevant.

The metadata knowledge engine 320 and the agent 310 may extract the metadata by processing the content (i.e., file) and the content of the user's action in the form of a text.

The metadata knowledge engine 320 may extract keywords having a high weight from the reference content (e.g., content 960 generated by the user). The metadata extraction unit 320 can generate an association based on the extracted keyword. The metadata extracting unit 320 may connect the content metadata, the use of the content, and the user's action metadata based on the extracted keyword.

The metadata knowledge engine 220 may extract keywords based on the name of the content and the text weight on the content of the document type and the like. The text weights may be determined based on the repetition of the same word or sentence, whether the word or sentence is used as the title or name, and the like. The extracted keyword, which is the metadata knowledge engine 320, can be converted into a resource description framework (RDF) format.

The keyword may have a representative (e.g., document) and a focus on the behavior of the user. The metadata knowledge engine 220 may link the keywords according to the correlation through a query of linking data. The associated keywords are relevant.

The metadata knowledge engine 220 analyzes the events before and after the update based on the update based on the keyword when the update of the reference content occurs, You can connect in chronological order. Here, an event may mean an event for a content or an event for a user action, and may include creation and modification of content metadata, and may include creation and modification of user behavior metadata.

The start of the above-described user's accident can correspond to the generation of the content. Content creation may include creating a file, posting a document, creating (or distributing) an e-mail, and so on.

Also, the termination of the accident of the user can correspond to the completion of the update of the content. The end point of the accident may be a certain time after the content is finally updated. The end of the accident may occur when information related to the keyword (or subject) is not updated around a specific keyword (or subject).

Whether an association between objects (i.e., whether objects represent information (e.g., metadata) related to each other) can be grasped by linking data on the content that has been converted into the RDF state. In the UI environment, when the specific information (e.g., metadata) is branched into completely different information in the process of the user's thinking, the pruning can be expressed by a line indicating the correlation.

The metadata knowledge engine 220 may extract the user's interest based on the information about the association. Here, the field of interest may be the keyword used to generate the association.

FIG. 10 illustrates a cloud system using multiple servers according to an example.

In Fig. 10, various devices 120 are shown.

The server 110 of the cloud system 100 may physically include a plurality of servers. Each of the plurality of servers may perform a part of the functions of the server 110 described above.

The plurality of servers may be divided into a storage area, a service area, and a database area.

The storage area may represent servers storing content. For example, the storage area may include a network attached storage (NAS) that stores content.

The service area may represent servers providing cloud services. The service area includes a PC-Web application server (WAS), a heterogeneous service-WAS, a WEB-WAS, a meta WAS, an RDF server, a presense server and a linking data server .

The database area may represent servers storing metadata. The database area may include a data base (DB) server, a statistical DB server, a user index server, and a metadata DB server.

FIG. 11 illustrates functions of the metadata server and the presence server according to an example.

The metadata server represents a server that performs all or a part of the functions of the server 110 described above. For example, the metadata server may store the content metadata in the metadata DB server. The metadata server can inquire information on the member (i.e., user) through the user index server.

In addition, the presence server may perform the function of the existence confirmation unit 240. [ For example, the presence server may provide management of the connection with the agent 310 and may provide a push function for the notification from the agent 310 or the metadata server. That is, the presence server may push notifications from the agent 310 to the metadata server, and may push notifications from the metadata server to the agent 310.

12 illustrates functions of the metadata server and the RDF server according to an example.

The metadata server can interconnect the metadata DB server and the linking data server. Thus, the metadata server may store the content metadata associated with the linking data server in the metadata DB server.

The RDF server may also be interconnected with a metadata server. RDF can perform RDF processing on content and user behavior. That is, the RDF server can perform RDF processing on the content metadata and the user behavior metadata. After RDF processing, RDF processing can extract key weed on RDE. Here, the keyword may be a keyword for a subject or a keyword for an object. The extracted keyword may be provided to the linking data server.

The method according to one embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the equivalents of the claims, as well as the claims.

100: Cloud system
110: Server
120: Device

Claims (15)

A user information providing server for providing information on a user, comprising:
A cloud storage unit for synchronizing content and metadata of the content with a content providing terminal providing access to the content to the user, the metadata including information on generation of a first content by the user, At least one of information on consumption of at least one second content, information about the behavior of the user for generating the first content, and information about the behavior of the user for consumption of the second content, The second content being related to each other by becoming the basis of generation of the first content;
A metadata knowledge engine for generating information about association between the first content and the second content by generation of the first content by consumption of the second content by the user based on the metadata; Wherein the information on association is a flow of generation of the first content by consumption of the second content; And information indicating a series of actions of the user in a process of generating the first content by consumption of the second content; And
[0040] In order to provide the generated information,
Lt; / RTI >
Wherein each of the first content and the second content is consumable by the user. The method according to claim 1,
Wherein the first content is generated through a user's access to the second content, a reference or a predetermined action. The method according to claim 1,
Wherein the providing unit provides the list of the at least one second content in the order of time or keyword. The method according to claim 1,
Wherein the metadata knowledge engine comprises: a flow of generation of the first content by consumption of the second content that information about the association comprises; And a graph representing information indicating a series of actions of the user in a process of generating the first content by consumption of the second content. The method according to claim 1,
Wherein the metadata knowledge engine extracts an interest field of the user based on the association information,
Wherein the field of interest includes a keyword related to a series of actions of the user in a process of consuming the second content, generating the first content, or generating the first content. The method according to claim 1,
Wherein the cloud storage unit generates the metadata based on the access of the content providing terminal to the second content. The method according to claim 1,
Wherein the cloud storage unit receives the metadata from the content providing terminal through the synchronization. The method according to claim 1,
Wherein the cloud storage unit receives the metadata from the external service provider through a public application programming interface provided by an external service provider. The method according to claim 1,
Wherein the content providing terminal providing access to the second content to the user is a plurality of users. 10. The method of claim 9,
An existence confirmation unit for managing information of available contents providing terminals among the plurality of contents providing terminals providing access to the second contents to the user,
Further comprising a user information providing server A content providing terminal for providing a user with access to content,
An agent for synchronizing the content and metadata of the content with a user information providing server providing information about the user;
A metadata extracting unit for extracting the metadata from a file providing the content,
Lt; / RTI >
Wherein the metadata includes content metadata generated based on the content and user behavior metadata generated based on the user's behavior on the content,
Wherein the metadata includes at least one of information about generation of a first content by the user, information about consumption of at least one second content by the user, information about an action of the user for generating the first content, And information on the behavior of the user for consumption of the second content,
The second content being associated with each other by becoming the basis of generation of the first content,
Wherein the metadata is used to generate information about an association between the first content and the second content by generation of the first content by consumption of the second content, The generation of the first content by consumption of the first content; And information indicating a series of actions of the user in a process of generating the first content by consumption of the second content,
Wherein each of the first content and the second content is consumable by the user. 12. The method of claim 11,
Wherein the agent periodically uploads the metadata to the user information providing server. Comprising the steps of: synchronizing content and metadata of the content with a content providing terminal providing access to the content to a user, the metadata comprising information about creation of a first content by the user, Information on consumption of the second content, information on the behavior of the user for the generation of the first content, and information on the behavior of the user for consumption of the second content, Wherein the content is related to each other by being the basis of generation of the first content;
Generating information about an association between the first content and the second content by creation of the first content by consumption of the second content by the user based on the metadata, Information is a flow of generation of the first content by consumption of the second content; And information indicating a series of actions of the user in a process of generating the first content by consumption of the second content; And
Providing the generated information
Lt; / RTI >
Wherein each of the first content and the second content is consumable by the user. Synchronizing content and metadata of the content with a user information providing server providing information about the user; And
Extracting the metadata from a file providing the content
Lt; / RTI >
Wherein the metadata includes content metadata generated based on the content and user behavior metadata generated based on the user's behavior on the content,
Wherein the metadata includes at least one of information about generation of a first content by the user, information about consumption of at least one second content by the user, information about an action of the user for generating the first content, And information on the behavior of the user for consumption of the second content,
The second content being associated with each other by becoming the basis of generation of the first content,
Wherein the metadata is used to generate information about an association between the first content and the second content by generation of the first content by consumption of the second content, The generation of the first content by consumption of the first content; And information indicating a series of actions of the user in a process of generating the first content by consumption of the second content,
Wherein each of the first content and the second content is consumable by the user. At least one content providing terminal for providing the user with access to the content; And
A user information providing server for providing information on the user
Lt; / RTI >
Wherein the at least one content providing terminal comprises:
An agent for synchronizing the content and metadata of the content with the user information providing server; And
A metadata extracting unit for extracting the metadata from a file providing the content,
Lt; / RTI >
Wherein the metadata includes content metadata generated based on the content and user behavior metadata generated based on the user's behavior on the content,
Wherein the metadata includes at least one of information about generation of a first content by the user, information about consumption of at least one second content by the user, information about an action of the user for generating the first content, And information on the behavior of the user for consumption of the second content,
Wherein the second content is related to each other by becoming the basis of generation of the first content,
A cloud storage unit for synchronizing the content and the metadata of the content with the content providing terminal;
A metadata knowledge engine for generating information about association between the first content and the second content by generation of the first content by consumption of the second content by the user based on the metadata; Wherein the information on association is a flow of generation of the first content by consumption of the second content; And information indicating a series of actions of the user in a process of generating the first content by consumption of the second content; And
[0040] In order to provide the generated information,
Lt; / RTI >
Wherein each of the first content and the second content is consumable by the user.

Images