KR20100063965A - Method and system for operating life log based on web service - Google Patents

Abstract

PURPOSE: A web service-based life log operating method and a system are provided to collect life log data which is created naturally in daily life of a client without a special dedicated machine thereby providing the collected data to the client. CONSTITUTION: A data collecting agent(110) collects web data from web server. A file data processing unit(120) collects file data saved in a client terminal. A database(140) stores the collected web data and the file data as life log data. A life log web server(130) provides the life log data by a request of a client.

Description

Method and system for web service based lifelog {Method and System for Operating Life Log Based on Web Service}

The present invention relates to a personal lifelog operation technology, and more particularly, to a web service-based lifelog operation method and system that can automatically record and later retrieve an event that an individual experiences during daily life.

Memex, meaning 'memory extender', first appeared in Dr. Bush's paper in 1945. Mimex is defined as 'a device that can be used to collect a book, document, or communication record of a person so that it can be conveniently and quickly referred to when it is desired' and is regarded as the origin of the current hyperlink or web. Recently, various attempts have been made to organize and provide a life log, which is information on an individual's daily life, to a user in relation to Mmex.

As an example of such an attempt, a method of recording a daily life by a person equipped with a camera called SenseCam and sensors for measuring light intensity and the like are known. The SenseCam device, mounted around the face, automatically captures "good times" and drives the camera with a few sensors. This technology can systematically store and synthesize data, effectively giving results to user queries.

However, such a prior art has a problem that a user must always carry or attach a dedicated device for data collection in order to collect personal lifelog data.

Accordingly, the present invention has been made to solve the problems of the prior art, an object of the present invention is to collect the lifelog data naturally generated in the user's daily life without a special dedicated device to provide to the user.

The lifelog operation method according to the present invention provided to achieve the above object comprises the steps of: collecting the web data from a web server providing a service of the web data; and collecting file data stored in a client terminal; And storing the stored web data and the file data as lifelog data, and providing the stored lifelog data according to a user's request.

In the lifelog operation method of the present invention, the web data collection step may directly collect the web data through the web service.

The web data collecting step may collect the web data through universal description, discovery and integration (UDDI).

The storing of the lifelog data may include index information including at least one of time, where, who, object, and how in the lifelog data. The extracted index information and the lifelog data may be mapped and stored.

In this case, the providing of the lifelog data may reconstruct and provide the lifelog data according to the stored index information of the lifelog data.

On the other hand, the lifelog management system according to the present invention, a data collection agent for collecting the web data from a web server providing a service of the web data, a file data processor for collecting the file data stored in the client terminal, the collected And a database for storing web data and the file data as lifelog data, and a lifelog web server for providing the stored lifelog data according to a user's request.

In the lifelog operation system of the present invention, the data collection agent may directly collect the web data through the web service.

Also, the data collection agent may collect the web data through universal description, discovery and integration (UDDI).

In addition, the database extracts index information including at least one of a time, a place, a who, an object, a how, and the like from the lifelog data. The index information and the lifelog data may be mapped and stored.

In this case, the lifelog web server may reconstruct and provide the lifelog data according to the stored index information of the lifelog data.

According to the present invention, by using the digital media used by people today, as a medium containing the daily life of the individual automatically collects and stores the daily life information of the individual scattered in these media without having to rely on a separate dedicated device Automatically record and document important events that occur in an individual's daily life.

The present invention can automatically organize the daily life information of individuals collected into lifelog data and provide various forms, and provide a business model through advertisements associated with such lifelog data.

Hereinafter, with reference to the accompanying drawings will be described in detail an embodiment of the present invention. However, in describing the embodiments, the descriptions may be omitted to clearly convey matters that are well known in the art to which the present invention pertains and are not directly related to the present invention without obscuring the core of the present invention.

The present invention is to collect various lifelog data that can leave a record of the daily life of the individual user, and to process and provide such lifelog data in the form required by the user.

The lifelog data according to an embodiment of the present invention includes various 'file data' that can be generated using a digital device, and 'web data' that is generated according to web use.

In the exemplary embodiment of the present invention, 'file data' refers to data generated by using a digital device among lifelog data, and particularly includes time information for identifying the generated time. For example, a digital picture generated using a digital camera or the like has time information on which the digital picture was taken, and a digital document generated by a specific user has time information on which the digital document was created.

When a user uses a particular service, there is a website that provides a history of that service. In the embodiment of the present invention, 'web data' means data including a use record of the service and a use record accordingly. For example, when a user travels on board an aircraft, a boarding log in which the user boards the aircraft may be searched through a web site of a corresponding aircraft company. Similarly, the mobile service provider's website contains call and text usage history, and the credit card website has credit card usage history. As such, the web data may be usage information using a specific service.

Hereinafter, a lifelog operation system according to an embodiment of the present invention for collecting and providing lifelog data to a user will be described. 1 is a block diagram showing a schematic configuration of a lifelog management system according to an embodiment of the present invention.

Referring to FIG. 1, the lifelog management system 100 includes a data collection agent 110, a file handler 120, a lifex web server 130, a database ( 140).

The data collection agent 110 collects lifelog data from the web. That is, the data collection agent 110 collects web data of lifelog data using a web service. Data collection through web services can be done in two ways: The first is to collect data through universal description, discovery and integration (UDDI), and the second is to collect data from a direct web service.

First, a data collection method through UDDI will be described. First, a service provider such as a credit card company registers its service described in a web service description language (WSDL) with UDDI, which is a service broker. Then, the data collection agent 110, which is a service requester, searches the UDDI to find a desired web service.

If the service can be found, the data collection agent 110 requests the service from the service provider and receives the result (requested data). Such service request and data reception may be made using a simple object access protocol or service oriented access protocol (SOAP).

Next, the data collection method through direct web service will be described. Since the web service is provided through a web server, the data collection agent 110 may collect web data through the web server. In other words, the method of collecting data through a direct web service rather than through UDDI is that a service requester directly calls a public web service of a service provider.

In this case, the data collection agent 110 collects data from the web server based on the web service (web server) of the service provider registered by the user through the lifelog web server 130. For example, the web service (web server) of the service provider may be a mail server, a mobile phone company web service, or a credit card web service.

The data collection agent 110 may be connected to an e-mail server to receive an e-mail stored in the e-mail server. In addition, the data collection agent 110 may access a web server of a credit card company to collect credit card logs. In addition, the data collection agent 110 may access a web server operated by a wired or wireless communication network operator and collect a phone log. In addition, the data collection agent 110 may collect related web data through a web service registered by a user, such as a web service of a travel agency.

Web data can be collected through the web service in any of the two methods described above, but in the embodiment of the present invention, it is assumed that the web service of the airline is a web service through UDDI, and the mobile phone usage history and credit card use are used. It is assumed that the history, e-mail, etc. consist of direct web service calls.

The airline web server 300 provides an airline web service to the application, and the airline web service provides a boarding record through the interface UDDI.

Meanwhile, the data collection agent 110 may access the mobile communication company web server 400 and collect call records through the mobile communication web service. In addition, after the data collection agent 110 accesses the credit card web server 500, the data collection agent 110 may collect credit card usage history using a credit card web service, and collect e-mail through the mail server 600. can do. Web data collected by the data collection agent 110 is stored in the database 140.

The file data processor 120 takes file data stored in the client terminal 200 of the user and stores the file data in the database 140. Here, the client terminal 200 may be a user's personal computer or various portable terminals. Lifelog system 100 according to an embodiment of the present invention may be basically a kind of server using IP. Accordingly, the client terminal 200 may access the lifelog system 100 through an IP network. When the client terminal 200 is a personal computer of the user, the client terminal 200 may be connected to an IP network through an Internet service provider (ISP) network or the like to access the lifelog system 100. In addition, in the case of a mobile terminal capable of using the wireless Internet, the mobile terminal accesses a core network using radio link access through an access point or a base station. Then, the lifelog system 100 may be connected to the IP network through a gateway of the core network.

As described above, in the state where the client terminal 200 is connected to the lifelog system 100, the file data processor 120 takes file data stored in the client terminal 200 and stores the file data in the database 140. As described above, the file data is generated through digital devices such as a digital camera, a digital voice recorder, and a mobile phone among lifelog files. That is, the file data according to the embodiment of the present invention may be an image file, a video file, an audio file, or the like.

For example, a user may store a digital picture taken by a digital camera in his computer through an interface provided by the digital camera. Then, the file data processor 120 may take a digital picture stored in the user's computer and store it in the database 140. In this case, the user may access the lifelog web server 130 and upload file data. Such file data may be stored in the database 140 in the form of ontology.

The lifelog web server 130 provides a service for designating a location from which data or a file is to be retrieved, and extracts the stored lifelog data from the database 140 to provide the user. As such, the lifelog web server 130 in charge of the conversation with the user receives the user's query, retrieves the lifelog data, and displays the data to the user.

The user may access the lifelog web server 130 using the client terminal 200 and retrieve the lifelog data through the web page of the lifelog web server 130. The lifelog web server 130 provides the user with all lifelog data related to the user who has successfully logged in. For example, lifelog web server 130 displays lifelog data in chronological order or vice versa.

The lifelog web server 130 may display only lifelog data including a keyword when the user searches using a specific keyword. In addition, the lifelog web server 130 may display the lifelog data corresponding to the period when the user searches for the period. If there is a query for requesting a user's specific lifelog data, the lifelog web server 130 may provide lifelog data according to the query.

The lifelog web server 130 extracts the above-described lifelog data from the database 140 and provides the same to the user. In particular, the lifelog web server 130 may provide only necessary lifelog data according to a user's search and response to a query. At this time, an index structure for searching the lifelog data with a specific keyword is required. Several indexing techniques for text documents include inverted files, suffix trees, and signature files. In the embodiment of the present invention, an inverted file is used. Reverse file indexing is a technique for extracting words that appear in text and having those words appear in the index. In the case of Korean, words are extracted through morphological analysis, and in the case of English, root extraction is performed using Porter's algorithm.

Meanwhile, the lifelog web server 130 provides a user interface for the user to register and remove a web service for the data collection agent 110 to collect lifelog data.

Hereinafter, a data collection method, a database construction method using collected data, and a data providing method according to an embodiment of the present invention will be described in more detail.

First, prior to the description of the lifelog data collection method according to an embodiment of the present invention, a web service setting method will be described with reference to FIG. 2 is an exemplary screen illustrating a web service setting method according to an exemplary embodiment of the present invention.

Before collecting lifelog data, it is necessary to select a web service among the lifelog data to collect web data. For this selection, the lifelog web server 130 provides an interface for selecting a web service.

The user may access the lifelog web server 130 to select, delete, and add a web service for collecting data. 2 is an example of a screen provided by the web server 130 to determine a web service to collect web data. As shown, the web server 130 displays each web service having the online data to be collected by the data collection agent 110 and shows the information necessary to connect to this web service. At this time, the user can add or delete a web service by using the 'Add Service' and 'Delete Service' buttons. In addition, the user may delete a plurality of corresponding web services by selecting a check box among the displayed web services.

Next, a method of collecting lifelog data according to an embodiment of the present invention will be described. 3 is a flowchart illustrating a method of collecting lifelog data according to an embodiment of the present invention.

3 illustrates a multimedia device 210, a client terminal 200, a lifelog system 100, a UDDI common registry 310, an airline web server 300, and a card company web server 500.

The multimedia device 210 collectively refers to various digital devices for generating file data according to an embodiment of the present invention, and may be representatively a digital camera. The client terminal 200 may be a variety of devices that can use the IP network, for example, a personal computer. As a web server for providing web data, there is an airline web server 300 and a card company web server 500. Among them, the airline web server 300 supports UDDI and the card company web server 500 does not support UDDI. Assume that

The client terminal 200 sets or registers a web service to collect web data in step S301. This is as described in FIG. In this case, it is assumed that the client terminal 200 sets the web service of the airline and the web service of a card company as a web service to collect web data.

Accordingly, the lifelog system 100 searches whether the airline web server 300 and the card company web server 300 support UDDI in operation S305. This retrieval takes place via the data collection agent 110. In this case, the web service supporting UDDI means that the web service is registered in the UDDI common registry 310. Accordingly, the data collection agent 110 may search the UDDI public registry 310 to determine whether the corresponding web service supports UDDI. In this case, it is assumed that the airline web server 300 has registered the airline web service in the UDDI public registry 310 in step S303 before step S305.

The lifelog system 100 may find that the web service of the airline supports UDDI and that the card company's web service does not support UDDI. Therefore, the lifelog system 100 requests the web data from the airline web server 300 in step S307. Then, the airline web server 300 provides the web data (boarding record) to the lifelog system 100 in step S309.

Meanwhile, since the card company web service does not support UDDI, the lifelog system 100 accesses the card company web server 500 in step S311, and downloads the corresponding web data (card usage history) in step S313.

These steps S305 to S313 are processes of collecting web data, and are performed by the data collection agent 110.

On the other hand, in the case of file data, the file data processor 120 collects the file data. First, the multimedia device 210 stores the lifelog data (file data) generated by the multimedia device 210 in the client terminal 200 in step S315. Then, the client terminal 200 accesses the lifelog system 100 in step S317 and uploads a corresponding data file (eg, a digital photo). In this case, the client terminal 200 accesses the lifelog system 100 through a web server, and the application for upload is provided by the file data processor 120. That is, unlike the web data, the photo, video, audio file, etc. stored in the personal computer of the user who is the client terminal 200 may be collected by the file data processor 120 providing an application for uploading.

Next, a method of constructing a database using lifelog data collected by the above method will be described.

Table 1 below is for explaining the storage structure of the lifelog data according to an embodiment of the present invention.

Lifelog
data time
(when) Place
(where) Subject
(who) Object
(what) Preview
(how)

As shown in Table 1, the lifelog data according to an embodiment of the present invention is a data field for storing each collected lifelog data, and a time and a place indicating index information corresponding to each lifelog data. , Who, what, and how fields.

That is, the lifelog data is extracted and stored from the lifelog data, index information about time, where, where, who, object, and how. Such index information may be extracted only from the link, or the index information itself may be extracted and recorded as a field value. The time, where, who, what, and how fields may be used as indexes for searching and displaying data.

In the time (when) field, time information on which corresponding lifelog data is generated is recorded. For example, when the lifelog data is an e-mail, the time information may be a time when the e-mail is transmitted. Similarly, credit card usage time for credit card usage history, call start time for call record, flight boarding time for flight boarding record, photo shooting time for photo, and video recording It may be a time or a time when the video is received.

The where field is generated when the place where the lifelog data is generated can be extracted from the lifelog data. When the generated place can be extracted from the lifelog data, it may be a credit card usage history, a boarding history, a photographing location, and the like.

The who field records information of a user related to lifelog data. For example, in the case of a call log or an e-mail, both the sender and the called party may be recorded in the subject field. The information recorded in the who field may be a name, an e-mail address, a telephone number, and the like. That is, it may include all information for identifying a specific user. In order to determine whether or not the identity of the who (who), the user identification information is mapped and stored in the address book. The address book stores the user's name, e-mail address, office / home phone number, and mobile phone number. This address book is previously stored in the database 140.

The user's address book may be referred to to determine that they have the same who in the lifelog data. The lifelog web server 130 provides an interface for storing such address book. 4 is an exemplary screen illustrating an interface of an address book according to an exemplary embodiment of the present invention.

As shown in FIG. 4, the address book lists a name and a contact list of the other party. Contacts include telephone numbers (home, office, cell phones) and e-mail addresses. Contacts in this list are considered as who. You can also add new contacts or delete existing ones using 'Add Contact' and 'Delete Contact'.

In the what field, the types of lifelog data are classified and recorded. Basically, the object (what) field describes the types of lifelog data such as e-mail, call log, credit card usage history, images, video, audio, and text, and may classify each type of data. For example, in the case of an e-mail, it describes whether it is an outgoing e-mail or a receiving e-mail. In the case of a call record, describe whether the call is made or not. In the case of a boarding record, the entry and departure can be described separately. In the case of card use history, items of card use (meal, purchase of goods, hospital expenses, etc.) can be described separately.

In the how field, the data (or link) for previewing a part of the lifelog data is recorded. For example, when the type of lifelog data is an e-mail or a text message, the preview may be the first part of the text, and in the case of an image, audio, or video, the preview may be a thumbnail.

So far, the method of storing lifelog data has been described. Next, a method of providing lifelog data to the user will be described.

As described above, the lifelog data is stored by mapping with a plurality of index information. The lifelog web server reconstructs the lifelog data based on this index information and provides it to the user. That is, based on the index information, it is possible to provide a lifelog data search function and the like, and to provide lifelog data in a manner that responds to a user's query. In addition, by generating a statistical index using lifelog data based on the index information, such statistical data can be provided. In addition, lifelog data associated with each other may be provided to the user based on the index information.

5A through 5D are screen diagrams illustrating a lifelog operating method according to an exemplary embodiment of the present invention.

The user may access the web server 130 of the system through the client terminal 100. When the user accesses the web server and logs in successfully, the web server 130 provides a screen as shown in FIG. 5A. In other words, the web server 130 indexes the lifelog data for the user from the database 140 (ie, when, where, who, what, and how). Display)) on the screen. The logged-in user name is displayed on the upper right of the screen, and lifelog data is displayed on the main screen, starting with the most recent event. By default, 50 data are displayed, and you can go back and forth by clicking the links 'Older' and 'Newer'.

According to an embodiment of the present invention, the lifelog web server 130 may sort the corresponding data based on at least one of the provided indices according to a user input. You can also sort lifelog data through more than one index.

In addition, web server 130 may provide the user with a set of relevant lifelog data. A series of related lifelog data is generated through the generation of correlated lifelog events (hereinafter referred to as 'lifelog event clusters'). As shown in FIG. 5A, a lifelog event cluster may be distinguished by grouping a series of related lifelog events into one and displaying a background color differently. A series of related events can be determined based on several criteria, but telephone call records, text message transmission and reception records, e-mail transmission and reception records, etc. can form a lifelog event cluster having the same who at a similar time. In addition, in the case of digital media such as digital photography, a series of events having a similar place and time may form a lifelog event cluster. Also, when used for a specific purpose, such as credit card usage history, such usage history (meal, various charges, installments, etc.) may form a lifelog event cluster.

In addition, when the web server 130 shows the lifelog to the user, the web server 130 may show a story view format instead of a table format. This is illustrated in FIG. 5B. When the story view is clicked on the screen of FIG. 5A, the screen of FIG. 5B is displayed. As shown in the example, the Memex data is shown converted into one or two sentences. For one piece of Memex data, the 4W part (i.e., time, where, who, what) is converted into one sentence, and the 1H part (i.e., how) is text. If is converted to another sentence. As the figure shows, the Memex event cluster, a group of related events, is transformed into a paragraph. In story view, by default, sentences are ordered from past to present. Clicking 'Table View' on the screen of FIG. 5B moves to the screen of FIG. 5A again. The Story View feature is useful for automatic story composition or automatic diary creation, which allows the story to be automatically composed from Memex events, and automatically organizes the traveler after the trip.

On the other hand, the web server 130 according to an embodiment of the present invention also provides a query input search function. When a user enters a query in a dialog box and selects a 'Search' button, the web server 130 may display data extracted through a search corresponding to the query.

In addition, when the user clicks 'Advanced Search', the web server 130 may perform a query for inputting a specific value in each index field. An example of such a screen is illustrated in FIG. 5C.

Referring to FIG. 5C, a query may be input for each index of lifelog data. In particular, the what index is a pull-down menu that can be selected from lifelog events such as e-mail, cell phones, credit cards, images, video, audio, and text. Enter the query and click the 'Search' button to execute the query. According to the query, the lifelog web server 130 extracts the lifelog data according to the index from the database 140 and provides the user with the lifelog data.

In addition, the web server 130 may provide lifelog data in statistics. When the user clicks 'Statistics' on the screen of FIG. 5A, the web server 130 may generate statistics for all lifelog data and provide them to the user. A screen example of such statistics provision is shown in FIG. 5D. The screen example of FIG. 5D shows who and who has the most lifelog events are arranged in descending order. Then, where, time, and what appear in descending order along with the number of occurrences.

As described above, according to an embodiment of the present invention, the lifelog data is reconstructed through various methods and the list of the corresponding data is displayed through the index. When a user selects one from the displayed list, the lifelog web server displays that lifelog data. Thus, the user can view lifelog data such as textual content, voice, video, and pictures. At this time, an advertisement related to the lifelog data is displayed beside the screen so that the user can click on the advertisement. For example, a text, e-mail, or photograph related to a bachelor's graduation can place an advertisement related to the graduation gown.

With the use of various digital devices such as mobile phones, credit cards, digital cameras, and e-mail, modern people have exposed their daily lives to digital media. The present applicant pays attention to the media used by the modern people as a medium for the daily life of the individual, and suggests a method to systematically store and quickly refer to the individual's daily life information scattered in these media. The present invention provides a lifelog operation technology capable of automatically recording and documenting important events occurring in an individual's daily life without relying on a dedicated device for collecting data.

So far, the lifelog operation method and system according to the present invention have been described through the embodiments. In the present specification and drawings, preferred embodiments of the present invention have been disclosed, and although specific terms have been used, these are merely used in a general sense to easily explain the technical contents of the present invention and to help the understanding of the present invention. It is not intended to limit the scope. It is to be understood by those skilled in the art that other modifications based on the technical idea of the present invention are possible in addition to the embodiments disclosed herein.

1 is a block diagram showing a schematic configuration of a lifelog management system according to an embodiment of the present invention.

Figure 2 is an exemplary screen showing a web service setting method according to an embodiment of the present invention.

3 is a flowchart illustrating a method of collecting lifelog data according to an embodiment of the present invention.

4 is an exemplary screen illustrating an interface of an address book according to an exemplary embodiment of the present invention.

5A to 5D are screen diagrams illustrating a lifelog operating method according to an exemplary embodiment of the present invention.

Claims (10)

Collecting the web data from a web server providing a service of the web data; Collecting file data stored in the client terminal; Storing the collected web data and the file data as lifelog data; Providing the stored lifelog data according to a user's request; Lifelog operation method comprising a. The method according to claim 1, The web data collection step, the lifelog operation method, characterized in that for directly collecting the web data through the web service. The method according to claim 1, In the web data collection step, the web data is collected through universal description, discovery and integration (UDDI). The method according to claim 1, The storing of the lifelog data may include extracting index information including at least one of when, where, who, object, and how from the lifelog data. And mapping and storing the extracted index information and the lifelog data. The method according to claim 4, The providing of the lifelog data may include reconstructing and providing the lifelog data according to the stored index information of the lifelog data. A data collection agent that collects the web data from a web server that provides a service of web data; A file data processor for collecting file data stored in the client terminal; A database for storing the collected web data and the file data as lifelog data; A lifelog web server providing the stored lifelog data according to a request of a user; Lifelog management system comprising a. The method according to claim 6, And the data collection agent collects the web data directly through a corresponding web service. The method according to claim 6, The data collection agent collects the web data through universal description, discovery and integration (UDDI). The method according to claim 6, The database extracts index information including at least one of a time, a place, a who, an object, and a preview from the lifelog data, and extracts the index information. Lifelog management system, characterized in that for mapping the information and the lifelog data stored. The method according to claim 9, And the lifelog web server reconstructs and provides the lifelog data according to the stored index information of the lifelog data.

Images