WO2013089390A1 - Système de fourniture d'informations personnelles sur la base de la création et de la consommation d'un contenu - Google Patents

Système de fourniture d'informations personnelles sur la base de la création et de la consommation d'un contenu Download PDF

Info

Publication number
WO2013089390A1
WO2013089390A1 PCT/KR2012/010535 KR2012010535W WO2013089390A1 WO 2013089390 A1 WO2013089390 A1 WO 2013089390A1 KR 2012010535 W KR2012010535 W KR 2012010535W WO 2013089390 A1 WO2013089390 A1 WO 2013089390A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
user
metadata
information
server
Prior art date
Application number
PCT/KR2012/010535
Other languages
English (en)
Korean (ko)
Inventor
박효진
최준균
Original Assignee
한국과학기술원
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 한국과학기술원 filed Critical 한국과학기술원
Publication of WO2013089390A1 publication Critical patent/WO2013089390A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services

Definitions

  • 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.
  • the user's device include a personal computer (PC), a laptop, a smart phone, a tablet, and the like.
  • PC personal computer
  • laptop a laptop
  • smart phone a tablet
  • tablet a smart phone
  • users can produce content directly in an environment where they can use PCs and laptops.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • the server may further include an existence confirmation unit that manages information of available devices among the plurality of devices.
  • 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.
  • the agent may periodically upload 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, 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.
  • 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.
  • 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.
  • FIG. 1 is a block diagram of a cloud system according to an exemplary embodiment. A block diagram of the server.
  • FIG. 2 is a block diagram of a server of a cloud system according to an exemplary embodiment.
  • FIG. 3 is a block diagram of a device of a cloud system according to an embodiment.
  • FIG. 5 illustrates information about a user's behavior for content consumption or content generation according to an example.
  • FIG 6 illustrates an association between metadata according to an example.
  • FIG. 7 is a flowchart illustrating a cloud service providing method according to an exemplary embodiment.
  • 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 a metadata server and a presence server according to an example.
  • FIG. 12 illustrates functions of a metadata server and an RDF server according to an example.
  • the user may want to manage the digital content produced by the user himself or participated in the production process in a batch form.
  • a user may directly produce specific content through social media and participate in the process of producing specific content.
  • 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.
  • the content may be embodied as digital content.
  • 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 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.
  • the details transmitted and received between the users may include electronic mail, pictures, bills, and movie files.
  • lifestream can be considered a concept focused on generating a digital log.
  • 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.
  • 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.
  • 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.
  • UI user interface
  • a service which provides a consistent form of management function for content produced by a user or participated in the production process.
  • 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.
  • FIG. 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.
  • 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.
  • the device 120 may be a client device used by individual users in a multi-device environment.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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".
  • 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.
  • 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.
  • server 110 may be provided with metadata through the Internet.
  • FIG. 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.
  • GUI Graphic User Interface
  • 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.
  • FIG. 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.
  • Agent 310 may synchronize content and metadata associated with the content with 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.
  • 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 office files, Portable Document Format (PDF) files, text files, and the like.
  • 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.
  • 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. .
  • types of content have been classified into images, music, video, documents, text from voice, and web pages.
  • the above classification may be merely exemplary.
  • 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.
  • 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.
  • 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.
  • ID unique identifier
  • URL unique resource locator
  • file type or file extension
  • file registration date file modification date
  • file deletion date resolution
  • location Information or latitude and longitude information
  • 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.
  • FIG. 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.
  • 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.
  • 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.
  • a PC agent, a mobile agent, a cloud, and an external web server are shown as subjects for extracting user behavior metadata.
  • 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.
  • functional feature each subject can extract user behavior metadata.
  • 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. .
  • 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.
  • FIG 6 illustrates an association between metadata according to an example.
  • 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.
  • a document file eg, a presentation file or a word processor file
  • 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.
  • 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.
  • 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.
  • the completion (done) 650 of the file generated by the user may indicate the end of the accident of the user.
  • 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.
  • FIG. 7 is a flowchart illustrating a cloud service providing method according to an exemplary embodiment.
  • the following 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.
  • the device 120 may generate content.
  • the above content may be generated by a user's manipulation.
  • the agent 310 of the device 120 may monitor the physical change of the content.
  • Agent 310 may monitor a folder or storage space.
  • 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.
  • the agent 310 may perform the synchronization in step 730.
  • Step 720 may be considered as an aggregation and capture process.
  • the metadata extractor 320 of the device 120 may extract metadata based on the content and the user's access to the content.
  • 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.
  • 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.
  • 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.
  • 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.
  • the synchronized device 120 and the server 110 may mean sharing content and metadata related to the content.
  • the agent 310 may periodically upload metadata to the cloud storage 210 of the server 110.
  • 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.
  • 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.
  • 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.
  • 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.
  • the cloud storage 210 may receive metadata from an external service provider through a public API provided by an external service provider.
  • 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.
  • 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.
  • the cloud storage 210 may request re-authentication from the external service provider.
  • 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.
  • the content consumption may refer to the above-described user behavior.
  • Steps 750-780 can be considered a storage and analysis process.
  • 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.
  • 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.
  • the device 120 and the server 110 may repeatedly perform the above-described steps 710 to 790 until a specific condition is met.
  • 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.
  • 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).
  • 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
  • FIG 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.
  • 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.
  • extracted keywords 930 and 940 are shown.
  • the first extracted keyword 930 is "FP7 WoO" and the second extracted keyword 940 is "Reference”.
  • information 952 by M2M, information 954 on the Internet of things, and information 956 on the web in an operating system are shown.
  • 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.
  • 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.
  • RDF resource description framework
  • 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 determines the correlation between the content and the event that is the reference. You can connect in chronological order.
  • 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.
  • 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. 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 can be identified by linking data for content converted to RDF state.
  • certain information eg, metadata
  • 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.
  • the field of interest may be a keyword used to generate the association.
  • FIG. 10 illustrates a cloud system using multiple servers according to an example.
  • 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.
  • the storage area may include a network attached storage (NAS) that stores content.
  • NAS network attached storage
  • 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.
  • WAS PC-Web Application Server
  • WEB-WAS Heterogeneous Service-WAS
  • Meta WAS Meta WAS
  • RDF Server Presence Server
  • 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.
  • DB core database
  • FIG. 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.
  • 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.
  • the presence server may perform a function of the existence checker 240.
  • 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.
  • FIG. 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.
  • 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.
  • the RDF process can extract the kiwide on the RDE.
  • 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.
  • Program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Human Resources & Organizations (AREA)
  • Computer Hardware Design (AREA)
  • Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un système de fourniture d'informations personnelles sur la base de la création et de la consommation d'un contenu. Le dispositif du système extrait des métadonnées sur la base d'un contenu et d'un accès, par un utilisateur, à un contenu. Le serveur du système crée des informations sur l'association entre une consommation de contenu et une création de contenu par un utilisateur. Le dispositif et le serveur synchronisent un contenu avec les métadonnées associées au contenu. Les métadonnées comprennent une ou plusieurs parmi des informations sur une consommation de contenu par l'utilisateur, des informations sur une création de contenu par l'utilisateur, des informations sur l'action de l'utilisateur pour une consommation de contenu, et des informations sur l'action de l'utilisateur pour une création de contenu.
PCT/KR2012/010535 2011-12-15 2012-12-06 Système de fourniture d'informations personnelles sur la base de la création et de la consommation d'un contenu WO2013089390A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2011-0135151 2011-12-15
KR1020110135151A KR101471522B1 (ko) 2011-12-15 2011-12-15 콘텐츠의 생성 및 소비에 기반한 개인 정보 제공 시스템

Publications (1)

Publication Number Publication Date
WO2013089390A1 true WO2013089390A1 (fr) 2013-06-20

Family

ID=48612785

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/010535 WO2013089390A1 (fr) 2011-12-15 2012-12-06 Système de fourniture d'informations personnelles sur la base de la création et de la consommation d'un contenu

Country Status (2)

Country Link
KR (1) KR101471522B1 (fr)
WO (1) WO2013089390A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017065443A1 (fr) * 2015-10-16 2017-04-20 명지대학교 산학협력단 Objet multimédia basé sur l'internet des objets centré sur un média et son procédé de fonctionnement

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017126725A1 (fr) * 2016-01-21 2017-07-27 (주)알티캐스트 Procédé et système de gestion de service de contenu de type croissant basé sur des informations relationnelles
WO2017126724A1 (fr) * 2016-01-21 2017-07-27 (주)알티캐스트 Procédé et système de gestion de service de contenu de type croissant basé sur des informations relationnelles

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050109719A (ko) * 2004-05-17 2005-11-22 전자부품연구원 사용자 친화형 멀티미디어 재생 장치 및 그 방법
KR20090058042A (ko) * 2007-12-04 2009-06-09 에스케이 텔레콤주식회사 이동통신 시스템에서 컨텐츠 메타데이터를 이용한 컨텐츠검색 방법 및 장치
KR20090076664A (ko) * 2008-01-09 2009-07-13 에스케이 텔레콤주식회사 사용자 선호에 기반한 영상 정보 서비스 방법 및 시스템
KR20100062104A (ko) * 2008-12-01 2010-06-10 (주)파인원커뮤니케이션즈 사용자 그룹 또는 그 그룹 간 콘텐츠 동기화 방법

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100087935A (ko) * 2009-01-29 2010-08-06 단국대학교 산학협력단 미디어 조합을 통한 적응적 컨텐츠 제공 시스템 및 그 방법
KR20110037354A (ko) * 2009-10-06 2011-04-13 에스케이 텔레콤주식회사 컨텐츠 소비 이력 배포 장치와 이를 이용한 서비스 시스템 및 그 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050109719A (ko) * 2004-05-17 2005-11-22 전자부품연구원 사용자 친화형 멀티미디어 재생 장치 및 그 방법
KR20090058042A (ko) * 2007-12-04 2009-06-09 에스케이 텔레콤주식회사 이동통신 시스템에서 컨텐츠 메타데이터를 이용한 컨텐츠검색 방법 및 장치
KR20090076664A (ko) * 2008-01-09 2009-07-13 에스케이 텔레콤주식회사 사용자 선호에 기반한 영상 정보 서비스 방법 및 시스템
KR20100062104A (ko) * 2008-12-01 2010-06-10 (주)파인원커뮤니케이션즈 사용자 그룹 또는 그 그룹 간 콘텐츠 동기화 방법

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017065443A1 (fr) * 2015-10-16 2017-04-20 명지대학교 산학협력단 Objet multimédia basé sur l'internet des objets centré sur un média et son procédé de fonctionnement

Also Published As

Publication number Publication date
KR20130082712A (ko) 2013-07-22
KR101471522B1 (ko) 2014-12-15

Similar Documents

Publication Publication Date Title
US20080201299A1 (en) Method and System for Managing Metadata
WO2016093552A2 (fr) Dispositif terminal et son procédé de traitement de données
WO2014069755A1 (fr) Système et procédé permettant de fournir un service de recommandation de contenu
WO2006011900A2 (fr) Procédé et système pour la gestion de métadonnées
WO2015066995A1 (fr) Procédé de collection et de partage intelligents et terminal mobile
EP3230902A2 (fr) Dispositif terminal et son procédé de traitement de données
WO2015088155A1 (fr) Système interactif, serveur et procédé de commande associé
WO2020190103A1 (fr) Procédé et système de fourniture d'objets multimodaux personnalisés en temps réel
WO2014058153A1 (fr) Système de service d'informations de carnets d'adresses, et procédé et dispositif pour service d'informations de carnets d'adresses dans celui-ci
WO2013081405A1 (fr) Procédé et dispositif destinés à fournir des informations
WO2020077832A1 (fr) Procédé, appareil et dispositif d'accès à un bureau dans le nuage et support de stockage
WO2024096146A1 (fr) Procédé de recommandation d'utilisateur au moyen de données de production et de données d'utilisation, et appareil associé
WO2020233060A1 (fr) Procédé et appareil de notification d'événement, serveur de notification d'événement et support de stockage
WO2013089390A1 (fr) Système de fourniture d'informations personnelles sur la base de la création et de la consommation d'un contenu
WO2016021878A1 (fr) Système et procédé de fourniture d'informations
WO2016093652A2 (fr) Procédé de fourniture de service d'album familial permettant d'utiliser un album familial en permettant aux membres d'une famille d'accéder à un serveur cloud par un numéro de téléphone
WO2020085558A1 (fr) Appareil de traitement d'image d'analyse à grande vitesse et procédé de commande associé
WO2024087821A1 (fr) Procédé et appareil de traitement d'informations et dispositif électronique
WO2017082551A1 (fr) Système de distribution d'informations en temps réel basée sur une chaîne de chiffres utilisant un terminal intelligent et procédé de distribution d'informations
WO2016129804A1 (fr) Procédé pour générer une page web sur la base de modèles de comportement de consommateurs et procédé d'utilisation de page web
WO2016093631A1 (fr) Appareil terminal et procédé de recherche de contenus
WO2013051844A1 (fr) Système publicitaire plurilingue interactif et procédé de commande associé
WO2018151458A1 (fr) Système et procédé de gestion de données se basant sur des mots-clés
WO2019146864A1 (fr) Dispositif électronique et procédé de commande associé
WO2015167198A1 (fr) Appareil et procédé pour collecter des contenus multimédias

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12857698

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12857698

Country of ref document: EP

Kind code of ref document: A1