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

Abstract

PURPOSE: A personal information providing system is provided to create data about the relation between content generation and content consumption of users and to extract metadata based on the content and the user access to the content. CONSTITUTION: A server (110) checks a cloud storage (210), a meta data knowledge engine (220), a providing unit (230), and an existence check unit (240). The cloud storage synchronizes content and metadata about the content with a device (120). Based on the metadata, the metadata knowledge engine creates data about the relation between content generation and content consumption of users. The providing unit provides the created data by the metadata knowledge engine. The metadata includes at least one among data about content consumption of users, data about content generation of users, data about user actions for content consumption, and data about user actions for content generation. [Reference numerals] (210) Cloud storage; (220) Meta data knowledge engine; (230) Providing unit; (240) Existence check unit

Description

SYSTEM FOR PROVIDING PERSONAL INFORMATION BASED ON GENERATION AND CONSUMPTION OF CONTENT}

The following embodiments relate to a personal information providing system.

A system for providing personal information for a user based on the user's content creation and content consumption is disclosed.

This study was conducted as a result of the research project of the university IT research center of the Ministry of Knowledge Economy and ICT Industry Promotion Agency. (NIPA-2011- (C1090-1111-0013))

Users produce and consume personal digital content through various devices they own. Examples of the user's device include a personal computer (PC), a laptop, a smart phone, a tablet, and the like. As various devices are used, users can produce content directly in an environment where they can use PCs and laptops. In addition, the user can apply and consume the produced content via a smart phone or tablet in an environment where service accessibility is poor, such as when traveling by car or on foot.

As the user produces and consumes information in various environments, the user wants to be able to access and consume the content at any time through the multi-screen provided by the device suitable for the environment.

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

Cloud services can improve the accessibility of a user's content in various 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 creation.

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

In one aspect, a cloud storage for synchronizing content and metadata associated with the content with a device, wherein the metadata is information about the user's content consumption, information about the user's content generation, the user's content for content consumption And at least one of information about the behavior and information about the user's behavior for generating content-metadata for generating information about the association between the content consumption of the user and the content generation based on the metadata A server is provided, including a knowledge engine and a providing unit for providing the information.

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

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

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

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

The metadata knowledge engine may extract a field of interest of the user based on the information about the association.

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 may receive the metadata from the external service provider through an open application programming interface provided by an external service provider.

There may be a plurality of devices.

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

In another aspect, an agent that synchronizes content and metadata associated with the content with a server, wherein the metadata includes information about the user's content consumption, information about the user's content creation, and the user's behavior for content consumption. And at least one of information about and information about the user's behavior for generating content-and a metadata extractor that extracts the metadata based on the content and the user's access to the content. Is provided.

The agent may periodically upload the metadata to the server.

In another aspect, synchronizing content and metadata associated with the content with a device, wherein the metadata includes information about the user's content consumption, information about the user's content creation, and the user's content for content consumption. And at least one of information about an action and information about the user's action for generating content, the method comprising: generating information about an association between the content consumption of the user and the content generation based on the metadata; Provided is a personal information providing method comprising the step of providing the information.

In another aspect, synchronizing content and metadata associated with the content with a server, wherein the metadata includes information about the user's content consumption, information about the user's content creation, and the user's content consumption. And at least one of information about the action and information about the user's action for generating content—and extracting the metadata based on the content and the user's access to the content. A provision method is provided.

In another aspect, the device includes at least one device and a server, the at least one device comprising: an agent that synchronizes content and metadata associated with the content with a server, wherein the metadata is information about a user's content consumption. At least one of information about the user's content creation, information about the user's behavior for content consumption, information about the user's behavior for content creation, and information about the content and the content of the user. And a metadata extractor configured to extract the metadata based on an access, wherein the server synchronizes the content and the metadata related to the content with the device. A personal information providing system is provided, comprising a metadata knowledge engine for generating information about an association between the content consumption of the user and the content generation based on the metadata and a providing unit for providing the information.

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

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

1 is a block diagram of a cloud system according to an exemplary embodiment. A block diagram of the server.
2 is a block diagram of a server of a cloud system according to an exemplary embodiment.
3 is a block diagram of a device of a cloud system according to an embodiment.
4 illustrates metadata of content according to an example.
5 illustrates information about a user's behavior for content consumption or content generation according to an example.
6 illustrates an association between metadata according to an example.
7 is a flowchart illustrating a cloud service providing method according to an exemplary embodiment.
8 illustrates personal information lifetime management according to an example.
9 illustrates a user interface of personal information life management according to an example.
10 illustrates a cloud system using multiple servers according to an example.
11 illustrates functions of a metadata server and a presence server according to an example.
12 illustrates functions of a metadata server and an 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 participated in the production process in a batch form. For example, a user may directly produce specific content through social media and participate in the process of producing specific content. Here, the content management means information about what search the user has performed, information about what material the user has read, information about what material the user has bookmarked, and what file the user has read. This may mean providing information on whether the user has downloaded or information about what document the user has written.

In the following, the content may be embodied as digital content. In addition, the terms 'client', 'client device' and 'device' may be used in the same sense and may be replaced with each other. The term 'metadata' may be replaced with 'meta information'. 'Information' may include 'meta data' or 'meta information'. The term 'cloud system' may be replaced with 'meta cloud system'.

The production of communication and digital content through electronic equipment has become commonplace, enabling the recording and retrieval of an individual's digital life. Related research has been conducted under the name (or topic) of lifestream or life log, and in recent years, user activity on social network services as users have long residence time on social services. Terms such as social lifestream and life 2.0 emerged.

The lifestream may mean storing information generated by the user through the device and details of the generated information exchanged with other users in the form of a document. Here, the details transmitted and received between the users may include electronic mail, pictures, bills, and movie files. In other words, lifestream 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 was used in earnest through networking-enabled terminals, the necessity of recording content creation and consumption of contents has emerged from the user's point of view. As access to online content via a web browser is facilitated and the frequency of such accesses increases, a service may be provided that allows individuals to share records regarding their use of the Internet service.

By identifying and storing the user's consumption history of content or Internet services, these services can provide users with the same content access capabilities as in previous environments, based on the consumption history, even in changed environments such as different PCs or different browsers. Can be. In addition, such a service may provide a service such as a mutual recommendation based on the similarity between bookmark information of each of users when a data of many users is secured over time.

In addition, the service may provide a history of content consumed by a user, thereby preventing a user from accessing or consuming content in duplicate, and in a variety of environments where users use different devices. Make the same list of content accessible.

In addition, the above-described service, in terms of a user interface (UI), allows a user to more easily register and utilize a URL related to content using javascript.

In the following, a service is disclosed which provides a consistent form of management function for content produced by a user or participated in the production process. For example, the above service may provide a technique for utilizing the bookmark information generated by the user in terms of the flow of information consumption by the user.

1 is a block diagram of a cloud system according to an exemplary 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.

There may be a plurality of devices 120. The device 120 may be a client provided with a service from the server 110. The device 120 may be a device usable by a user such as a mobile device and a PC. Mobile devices may include smart phones, tablets, laptops, and the like. In other words, the device 120 may be a client device used by individual users in a multi-device environment.

In FIG. 1, the cloud provides a service that enables each user to effectively access and manage content consumed or produced by the user and metadata related to the content in a multi-device environment based on a computing infrastructure. 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 a user can create by directly using software or an application of a PC or a mobile device. Here, the file may include a video file, an audio file, a rich text file, and the like.

Metadata may refer to information collected through the device 120 or collected by a service used by a user in a web environment in the entire process of creating and consuming content.

The metadata may include metadata of the content, metadata of the service, or metadata of the user, which occurs as the user consumes the content or the service. The metadata of the user may include an audience measurement. That is, metadata includes: 1) information about the content, 2) information about the user's content consumption, 3) information about the user's content creation, 4) information about the user's behavior for content consumption, and 5) content creation. It may include one or more of information about the user's actions for.

The server 110 may receive metadata from various entities connected with 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 metadata may include communication metadata, primarily due to communication between users. The communication metadata may be metadata for voice data. In addition, the metadata may be metadata based on a file. The file-based metadata may be metadata about playing, creating, editing, reading, and deleting the file. At least one device 120 may communicate with the server 110 through 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 server 110 or a browser of a device that receives a web from the server 110. The metadata may be browsing-based metadata. The browsing-based metadata may be metadata about playing or reading 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, a user's communication, and the like. The social metadata may be metadata about a message, a location, a preference, and the like.

In addition, the server 110 may be provided with metadata through the Internet.

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

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

The cloud storage 210 may synchronize the content and metadata related to the content with the device 120. The cloud storage unit 210 may store details and contents that each user consumes the content and details that the user 120 should always be accessible by the device 120 among the contents produced by each user.

The metadata knowledge engine 220 may generate information about an association between content consumption and content generation of the user based on the metadata. The metadata knowledge engine 220 may extract and process metadata about content that is dozens for each user, and provide a flow of information consumption and information generation of the user.

The provider 230 may provide information generated by the metadata knowledge engine 220. The providing unit 230 may enable the user to easily grasp the details using the content. The provider 230 may provide information generated by the metadata knowledge engine 220 through a Graphic User Interface (GUI) in the form of a media library. The GUI can be based on the web.

The existence confirmation unit 240 manages information of available (ie, accessible) device 120 among 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 of a cloud system according to an 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 content (ie, a physical file) and metadata related to the content with the cloud storage 210 of the server 110 according to various device types. Agent 310 may also support remote sharing of content.

Agent 310 may be downloaded and installed to device 120 in the form of an application.

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

4 illustrates metadata of content according to an example.

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

Content may include: 1) personal setting and statistical 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, an image file, and the like. 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. Tags are created by a user tagging information of a particular content. Tags can increase the accuracy of metadata about content.

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

In FIG. 4, types of content have been classified into images, music, video, documents, text from voice, and web pages. The above classification may be merely exemplary. For example, the type of content may further include personal settings on the application described above, statistical data on the application, search logs and tags, and the like. In addition, in FIG. 4, names and descriptions of types of metadata that may be extracted from content are illustrated for each type of content. The above name may be a name used by the cloud system 100 to distinguish the type of metadata, and may be replaced with another name indicating the same or similar meaning.

For example, when the content is an image, the metadata extracting unit 320 may determine, from the file, a unique identifier (ID) of the content, an ID of the owner of the file, a device (or storage). ID, title, file name, file size, unique resource locator (URL), file type (or file extension), file registration date, file modification date, file deletion date, resolution, location Information (or latitude and longitude information), grade, and the like can be extracted as metadata.

The name and description of metadata illustrated in FIG. 4 may be merely an example for explaining that the types of metadata extracted by the metadata extracting unit 320 may be different from each other according to the type of content. The metadata extracting unit 320 may extract various types of metadata from contents having a specific type in addition to those illustrated.

5 illustrates information about a user's behavior for content consumption or content generation according to an example.

Metadata may be generated based on user behavior. Metadata generated based on user behavior may be referred to as user behavior metadata.

Agent 310 may be a subject collecting user actions. Here, the user action may be for content consumption or content generation. That is, content may be consumed or generated by user actions. Agent 310 is based on the information of the user's content consumption based on the collected user behavior, the information on the user's content generation, the information on the user's behavior for content consumption, and the user's behavior for the content generation Information may be generated.

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

User behavior type Explanation Access files 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 Write personal and statistical data, multimedia files, document files, web files, etc.
Voice recognition, voice recording, etc. play Play multimedia files and music communication File send, file sharing and voice communication Social behavior Like likes, retweets, and following

The user behavior types listed in Table 1 and descriptions of each type are exemplary only.

The subject extracting user behavior metadata may be provided by 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). There may be an open application programming interface (API), etc. The agent 310 may be divided into a PC agent running on a PC and a mobile agent running on a mobile device.

In FIG. 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 the meta cloud or the 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. In addition, in Fig. 5, it is listed which functional feature each subject can extract user behavior metadata. In addition, for each subject and each functional feature, a criterion for the subject to extract the user behavior metadata, a manner in which the subject extracts the user behavior metadata, a condition for the subject to extract the user behavior metadata, and the like have been described. .

In FIG. 5, the circular symbol may indicate that the subject may extract user behavior metadata having a specific functional feature. The triangular symbol may indicate that the subject may extract, depending on the condition or part, user behavior metadata having a specific functional characteristic.

6 illustrates an association between metadata according to an example.

In general proposal generation work or document generation work, user actions may include 1) file creation and file contents creation, 2) data reference, and 3) opinion collection.

File generation may include 1) creating a document file (eg, a presentation file or a word processor file), 2) determining a template to use for the generated file, and 3) creating a content under the determined template. This may include writing.

Material references may include: 1) referencing web pages, PDF files, word processor files, presentation files, etc., to create the content of a proposal (or document), for example on the Internet; May include downloading.

Opinion gathering may include 1) collecting opinions of others through discussion, 2) voice recording another person's opinion, and 3) extracting text from the recorded voice.

The thinking process of the user and the contents created by the user may develop in a similar form. Here, the thinking process of the user may be represented in the direction of development of thinking and thinking. That is, as the user develops an accident, file-based or voice-based contents referenced (or utilized) by the user may be considered to reflect the user's thinking. Therefore, the agent 310 or the like extracts the content metadata of the content or the user behavior metadata for the content, and the metadata knowledge engine 220 or the agent 310 analyzes the extracted metadata in the form of text, thereby providing a user with the user. Can figure out what kind of thoughts they are thinking about.

In FIG. 7, the creation 610 of a file generated by the user may indicate the start of an accident of the user, and the local files 620, the web pages 630 and the referenced files in the process of completing the creation of the file. The voice 640 or the like may represent a direction of development of a user's thinking and thinking. In addition, the completion (done) 650 of the file generated by the user may indicate the end of the accident of the user. Here, the local files 620 may mean contents that exist in the cloud system 100 and may be referred to in the cloud system 100. The web pages 630 may refer to contents existing outside the cloud system 100.

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

The following cloud service providing method (or meta cloud service providing method) may be regarded as a personal information providing method. That is, device 120 and server 110 may each be considered to provide personal information of a user.

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

In step 720, the agent 310 of the device 120 may monitor the physical change of the content. Agent 310 may monitor a folder or storage space. Here, the folder or storage space may be a specific folder or storage space, for example, it may be a designated folder or storage space according to a user's setting. When the agent 310 detects a change in the folder or storage space as a result of the monitoring, the agent 310 may perform the synchronization in step 730.

Step 720 may be considered as an aggregation and capture process.

In operation 730, the metadata extractor 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 metadata extracted based on the user's access to the content may be the above-described user behavior metadata.

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

In step 740, the existence confirmation unit 240 manages information of the available device 120 among the plurality of devices 120 in the cloud system 100 and moves by device 120. And change history.

Step 740 may be considered a presence and accessibility process.

In operation 750, the agent 310 of the device 120 and the cloud storage 210 of the server 110 may synchronize content and metadata associated with the content. Here, the synchronized device 120 and the server 110 may mean sharing content and metadata related to the content. For synchronization, the agent 310 may periodically upload metadata to the cloud storage 210 of the server 110. In the above upload, the agent 310 may upload only the metadata to the cloud storage 210, not the physical content (ie, file). The device 120 to which the server and the content and the metadata related to the content are synchronized may be the device 120 determined as available by the existence checker 240.

The cloud storage 210 may store content (ie, based on a storage capacity of the cloud storage 210, a bandwidth of a network between the server 110 and the device 120, and a battery state of the device 120. You can only sync metadata, not files.

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

In operation 760, the cloud storage 210 may generate metadata based on the device 120 's access to the content. That is, metadata may be extracted for the content passing through the cloud storage 210. When the physical content exists in the cloud storage 210, the user can upload the content to the cloud storage 210 through a method of using the cloud storage generally, and the content stored in the cloud storage 210 is stored in the cloud storage 210. I can access it. In addition, the content stored in the cloud storage 210 may include content transmitted to the cloud storage 210 through synchronization, and may include content in a synchronized folder or storage space. The user may access the above content through the device 120.

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

Metadata received from an external service provider may be viewed as personal information of a user. The cloud storage 210 may provide a user (or a device 120 operated by the user) with a function necessary for collecting personal information from an external service provider and a consent procedure for the collection. The cloud storage 210 may perform third party authentication on an external service, and store information necessary for performing the above (eg, user log-in information). have. In addition, the cloud storage 210 may provide a user with a consent process for the third party authentication and the collection of the information. The cloud storage 210 may periodically perform data collecting on the collected information. In addition, when the account storage for the external service is abort (abort), the cloud storage 210 may request re-authentication from the external service provider.

In 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 generation based on the metadata. Here, the content consumption may refer to the above-described user behavior.

Steps 750-780 can be considered a storage and analysis process.

In operation 790, the providing unit 230 of the server 110 may provide information about an association between content consumption and content generation.

The association may be an association between the first content generated by the user and at least one second content consumed by the user. The consumption may refer to the user's access to the second content or the user's action on the second content. The at least one second content may be content that is the basis of 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 keywords.

The order of the steps 710-790 described above is merely illustrative. The above-described steps 710 to 790 may be performed simultaneously (eg, by the device 120 and the server 110, respectively) and may be performed in a different order from each other. In addition, the device 120 and the server 110 may repeatedly perform the above-described steps 710 to 790 until a specific condition is met.

8 illustrates personal information lifetime management according to an example.

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

In order to provide a history, the cloud storage 210 of the cloud system 100 may include a process applied to content generation, generated content and metadata about content (generated or referenced) and content referred to for content generation. Can be archived in a metadata database

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

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

The graph 900 may include content, user behavior, and keywords (or tags). That is, the UI object in the graph may include content, actions, and keywords. The objects can be sorted by date. This alignment can represent a time-series representation of the flow of thoughts and objects of the user. Associations between objects may be represented by arrows.

In FIG. 9, the contents 910 and 920 consumed to create the content are shown. The name or keyword of the first consumed content 910 is "WoO Proposal" and the type of content is a word processor file abbreviated as "DOCX". The name or keyword of the second consumed content 920 is "# 2 Proposal" and the type of content 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 M2M, information 954 on the Internet of things, and information 956 on the web in an operating system are shown. In addition, the generated content 960 is displayed. The name or keyword of the generated content 960 is "WoO Proposal" and the type of content is a presentation file abbreviated as "PPTX". The graph 900 may be regarded as a UI written based on the generated content 960.

When the external information indicates a keyword through the arrow, the arrow may indicate that the external information is related to the keyword.

The metadata knowledge engine 320 and the agent 310 may extract metadata by processing the content (that is, file) and the content of the user's behavior in text form.

The metadata knowledge engine 320 may extract a keyword having a high weight from the reference content (eg, the content 960 generated by the user). The metadata extracting unit 320 may generate an association around the extracted keyword. The metadata extracting unit 320 may connect content metadata, use of content, user behavior metadata, and the like 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. The text weight may be determined according to repetition of the same word or sentence, whether the word or sentence is used as a title or name, and the like. The extracted keyword, which is the metadata knowledge engine 320, may be converted into a resource description framework (RDF) format.

The keywords may have representativeness based on the content (eg, document) and the user's actions. The metadata knowledge engine 220 may link keywords according to a correlation through a query of linking data. Linked keywords become relevant.

The metadata knowledge engine 220 analyzes the events occurring before and after the update based on the keyword based on the above-mentioned update when the update of the content that is the reference occurs, and then determines the correlation between the content and the event that is the reference. You can connect in chronological order. Here, the event may mean an event for the content or an event for the user's actions, may include generation and change of content metadata, and may include generation and change of user action metadata.

The initiation of the thinking of the user described above may correspond to the creation of content. The generation of content may include the creation of a file, the posting of a document, the generation (or distribution) of an email, and the like.

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

Associations between objects (ie, whether the objects represent information related to each other (eg, metadata)) can be identified by linking data for content converted to RDF state. When certain information (eg, metadata) is branched to completely different information in the course of a user's thinking, the pruning in the UI environment may be represented by a line representing a correlation.

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

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. The plurality of servers may each perform some 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 that store content. For example, the storage area may include a network attached storage (NAS) that stores content.

The service area may represent servers that provide cloud services. The service area includes PC-Web Application Server (WAS), Heterogeneous Service-WAS, WEB-WAS, Meta WAS, RDF Server, Presence Server and Linking Data Server. It may include.

The database area may represent servers that store metadata. The database area may include a core database (DB) server, a statistics DB server, a user index server, a metadata DB server, and the like.

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

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

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

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

The metadata server may interconnect the metadata DB server and the linking data server. Accordingly, the metadata server may store content metadata related to the linking data server in the metadata DB server.

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

Method according to an embodiment is implemented in the form of program instructions that can be executed by various computer means may be recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. 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 recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, 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 not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains various modifications and variations from such descriptions. 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)

Cloud storage unit for synchronizing the content and metadata associated with the content with the device, the metadata is information about the user's content consumption, information about the user's content creation, information about the user's behavior for content consumption and One or more of information about the user's behavior for content creation;
A metadata knowledge engine that generates information about the association between the content consumption of the user and the content generation based on the metadata; And
Providing unit for providing the information
. The method of claim 1,
The association is an association between the first content generated by the user and at least one second content consumed by the user, wherein the at least one second content is the basis of generation of the first content. The method of claim 2,
The providing unit provides the list of the at least one second content in the order of time or keywords. The method of claim 2,
The metadata knowledge engine is a graphical representation of the association. The method of claim 1,
The metadata knowledge engine extracts the user's field of interest based on the information about the association. The method of claim 1,
The cloud storage unit generates the metadata based on the device's access to the content. The method of claim 1,
The cloud storage unit receives the metadata from the device through the synchronization. The method of claim 1,
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 of claim 1,
The device is a plurality of individuals, a server. 10. The method of claim 9,
Existence check unit for managing the information of the available devices of the plurality of devices
Further comprising a server An agent that synchronizes content and metadata associated with the content with a server, wherein the metadata includes information about the user's content consumption, information about the user's content creation, information about the user's behavior for content consumption and content generation One or more of information about the user's action for; And
A metadata extracting unit extracting the metadata based on the content and a user's access to the content
. The method of claim 10,
The agent periodically uploads the metadata to the server. Synchronizing content and metadata associated with the content with a device, wherein the metadata includes information about the user's content consumption, information about the user's content creation, information about the user's behavior for content consumption and content generation One or more of information about the user's action for;
Generating information about an association between the content consumption of the user and the content generation based on the metadata; And
Providing the information
Including, personal information providing method. Synchronizing content and metadata associated with the content with a server, wherein the metadata includes information about the user's content consumption, information about the user's content creation, information about the user's behavior for content consumption and content generation One or more of information about the user's action for; And
Extracting the metadata based on the content and a user's access to the content
Including, personal information providing method. At least one device; And
server
Lt; / RTI >
The at least one device,
An agent that synchronizes content and metadata associated with the content with a server, the metadata comprising information about the user's content consumption, information about the user's content creation and information about the user's behavior for content consumption, content generation One or more of information about the user's action for; And
A metadata extracting unit extracting the metadata based on the content and a user's access to the content
Lt; / RTI >
The server comprises:
A cloud storage for synchronizing the content and the metadata related to the content with the device;
A metadata knowledge engine that generates information about the association between the content consumption of the user and the content generation based on the metadata; And
Providing unit for providing the information
Including, a personal information providing system.

Images