KR100567219B1 - Method and system for providing update information of a blog - Google Patents

Abstract

According to the present invention, a method for providing blog update information implemented through a blog update information providing system communicatively connected to a customer terminal device through a communication network, the method comprising: (a) receiving a request for providing blog update information to a customer; ; (b) obtaining predetermined 'reference date and time' (T1) data in response to a request for providing blog update information; (c) obtaining a designated blog list of the customer by using previously prepared blog designated history information; (d) obtaining 'recent blog update date and time' (T2) data prepared in advance for each designated blog; (e) comparing T1 and T2 for each designated blog, and if the T2 is later than T1, setting the blog as a notification target blog to secure a 'notified target blog list' for the entire designated blog of the customer; Provided is a blog update information providing method comprising the step of generating the updated blog guide information having the notification target blog number data by using the notification target blog list and transmitting to the customer terminal device of the customer.

Blog, Renewal Information, Renewal Date, Back URL, Inquiry

Description

METHOD AND SYSTEM FOR PROVIDING UPDATE INFORMATION OF A BLOG}

1 is a schematic diagram of a system for providing blog update information and a peripheral system according to an embodiment of the present invention;

2 is a flowchart illustrating a development process of a method for providing blog update information according to an embodiment of the present invention;

3 illustrates an example of a reference date and time data item according to an embodiment of the present invention;

4 is a view showing an example of customer specified blog detail information according to an embodiment of the present invention,

5 is a diagram illustrating an example of blog analysis information according to an embodiment of the present invention;

6 is a diagram illustrating a process of securing blog analysis information according to an embodiment of the present invention;

7 is a flowchart illustrating a subsequent process following one step of the method for providing blog update information according to an embodiment of the present invention shown in FIG. 2;

8A and 8B are diagrams illustrating an example of a screen for providing customer connection confirmation and update blog guide information according to an embodiment of the present invention;

9A and 9B illustrate examples of providing blog update information according to a preferred embodiment of the present invention;

FIG. 10 is a flowchart illustrating a subsequent process following one step of the method for providing blog update information according to an exemplary embodiment of the present invention shown in FIG. 2.

<Description of Symbols for Main Parts of Drawings>

100: blog update information management system 110: customer information DB

120: blog designation history information DB 130: blog analysis information DB

140: blog renewal information DB 150: blog renewal management server

170, 175: communication network 191, 192, 193: blog site

181, 182, 183: customer terminal device

S200: blog update information providing request command receiving step

S210: reference date and time data setting step

S220: step of securing the designated blog list

S230: recent blog update date and data acquisition step of the specified blog

S240: step of securing the notification target blog list

S250: Renewal blog guide information transmission step

S260: update blog guide information transmission temporary update step

The present invention relates to a method and system for providing a blog service, and more particularly, to a method and system for providing blog update information that can further activate the use of a blog service by providing update information of a blog to a user.

Recently, a so-called blog service that replaces or competes with a personal homepage service function through the Internet has attracted attention. Blog (also called blog) is an abbreviation of Web-Log, which is a flow chart defined as 'Internet single media', but it is not a clearly defined concept academically. However, in the art, the meaning of the blog is differentiated compared to the personal homepage service through the name of the blog.

In the case of the homepage, if the content (text or content) is modified or reloaded, the administrator or someone who can handle Html or the corresponding program should write the content and put it in the corresponding location on the web server.

In addition, even in the case of a bulletin board that is relatively free to post, the general public can access the page where the content can be viewed or uploaded by clicking the menu of the bulletin board through the login screen. That is, the general user can use the screen (web page) that can communicate with the individual (homepage owner) after the screen switching and authentication steps of the various steps.

For the above reasons, the public can browse the contents posted by a specific person on one web-page with only one connection without moving the screen, and also can communicate conveniently by uploading the content. The active openness of the function was required, and the blog service appeared as an alternative.

In other words, the blog implements a homepage (Web, including media elements) and a bulletin board (log, recording function) in one web page. Conventionally, the homepage (web) with a strong information transmission function and a bulletin board for leaving a record are generally implemented in different pages, but in a blog, they are all implemented in one page.

The general form of blog that has the above characteristics is as follows. Almost all existing blogs have a blog title and a few descriptive words at the top, and immediately below them are what the owner or manager of the blog wants to convey, followed by the articles attached by the visitors to the blog (usually In order of most recent). That is, a typical blog that appears in the form of a title-> description-> agenda (what you want to deliver)-> comment (a visitor or owner (admin) 's post about an agenda, also known as ripple) In the form of.

Recently, there is a tendency to attach pictures, videos, photo music videos, etc. to the contents (i.e., agenda) to convey to enhance the multimedia elements. It also adds functions such as ',' and also adds 'visitor' and 'related blog collection' to manage and manage the blog. Blogs make it easy for non-expert users to post text or multimedia material on their Web sites, and build a strong network around their agenda over time.

Looking at the prior art related to the blog service providing method as follows. Korean Patent Application Publication No. 2003-0039346 published on May 17, 2003 (Application No .: 10-2003-0018076, Title of the Invention: Blogging tool, a method of creating a web document using the same, and uploading a web document written on a web page) Method) is a user who has a blog page on the Internet (aka blogger or blogger, hereinafter referred to as 'blogger') when writing. Provides a blog service method for posting.

Korean Patent Application Publication No. 2003-0036379 (Application No .: 10-2003-0017309, published on May 9, 2003, title of the invention: a method for building a community site using a ring blog) has a blog page on the Internet. It provides a way for users (bloggers) to have the same blog page, write and share it, to share their common interests.

Korean Patent Application Publication No. 2003-0066515 published on August 9, 2003 (Application No .: 10-2003-0046234, Title of the Invention: Method of Selling Products Using Community or Blog) provides a blog service for online product sales. It provides a way to elicit bloggers' activities by providing cost discounts on product pools based on views, activity, popularity, product sales amount, etc. on product promotion blog pages.

The above-mentioned prior arts provide technologies that contribute to enhancing the function of the blog service and expanding its scope. However, when the blog service is based on the activation of the one-person recording medium through rapid two-way communication between non-expert users, conventionally, the customer is informed that the blog is updated due to the change of blog content such as the addition of agenda and comments. There was no way to make it easy to understand and contribute to the expansion of user's blog service and satisfaction.

That is, users want to view the changed contents when the blog contents are changed due to the characteristics of the blog service. Therefore, when the blog contents are updated to meet the needs of the users, information about the updated blogs (representative You need a method and system to provide the blog's URL address).

The present invention has been made to solve the above problems, an object of the present invention is to provide blog information (blog update information) for the updated blog updates that can contribute to the user's increased use of blog services and increased satisfaction Implement the information providing method and system.

Another object of the present invention is to increase the efficiency of the blog service by reducing the burden on the user's usage fee while reducing the load of the communication network by providing unnecessary blog site access by the user.

According to a first aspect of the present invention for achieving the above object, in a blog update information providing method implemented through a blog update information providing system connected to communicate with a customer terminal device via a communication network, (a) for the customer Receiving a request for providing blog update information; (b) obtaining predetermined 'reference date and time' (T1) data in response to a request for providing blog update information; (c) obtaining a designated blog list of the customer by using previously prepared blog designated history information; (d) obtaining 'recent blog update date and time' (T2) data prepared in advance for each designated blog; (e) comparing T1 and T2 for each designated blog, and if the T2 is later than T1, setting the blog as a notification target blog to secure a 'notified target blog list' for the entire designated blog of the customer; Provided is a blog update information providing method comprising the step of generating the updated blog guide information having the notification target blog number data by using the notification target blog list and transmitting to the customer terminal device of the customer.

According to a second aspect of the present invention for achieving the above object, in a blog update information providing system connected to communicate with a customer terminal device, storing customer information having ID data for the customer and the terminal device ID data of the customer A customer information DB; A blog designation detail information DB having designation blog data for each customer; A blog analysis information DB for storing blog analysis information having a recent blog update date and time (T2) data matched with a unique code thereof for a designated blog; A web server for performing a mediating function for a customer to access each DB through a customer terminal device and a communication network to perform searching and input of necessary information; Use the customer information to control the login process of the customer, obtain the 'standard date' (T1) data prepared in advance in response to the request for providing blog update information, obtain the designated blog list using the blog specified history information, By obtaining 'recent blog update date' (T2) data of a designated blog from the blog analysis information, and comparing the T1 and T2 for each designated blog and setting the blog as the blog to be notified when T2 is later than T1. A blog update management server that secures a 'notice list of blogs' for all of the customer's designated blogs, and uses the notified blog list to generate updated blog guide information having the number of blogs to be notified and send them to the customer's customer terminal device There is provided a blog update information providing system comprising a.

Hereinafter, a method and a system for providing blog update information according to a preferred embodiment of the present invention will be described with reference to the accompanying drawings.

1 is a schematic diagram of a blog update information providing system 100 and its peripheral apparatuses or systems according to a preferred embodiment of the present invention. The blog update information providing system 100 essentially includes a customer information DB 110, a blog specification history information DB 120, a blog update management server 150, and a web server 160. Further includes a blog analysis information DB 130, and may further include a blog update information DB 140. In addition, as the peripheral system of the system 100, communication networks 170 and 175, blog sites (e.g., indicated as 191, 192 and 193 in Fig. 1) and a customer terminal device (e.g., 181 in Fig. 1). 182, 183).

Here, the communication networks 170 and 175 are usually the Internet using Hyper Text Transfer Protocol (HTTP). In the physical sense, the communication networks 170 and 175 may use various communication networks such as a wired communication network, a satellite broadcasting network, and a wireless mobile communication network. The customer terminal device is typically a personal computer (for example, 183 of FIG. 1) provided with a web browser, but is not limited thereto. Various connection devices having a function of accessing a web server to input or read necessary data, For example, a mobile communication terminal (for example, 181 of FIG. 1), a kiosk, a PDA (for example, 182 of FIG. 1), a digital TV, a PC, a laptop, and the like that support IMT-2000 service may be used.

The customer information DB 110 stores customer information, which is essentially provided with customer ID data for identification (ID) of the customer and additionally includes terminal device ID data of the customer. Can be. Customer ID data usually includes, for example, a password and password for the customer to access the Internet site of the system 100. In addition, social security numbers, addresses, telephone numbers, e-mail addresses, etc. It may be provided. In addition, performance and specification information of the customer terminal device may be further provided. The terminal device ID data of the customer may include, for example, an Internet IP address or a mobile communication phone number of the customer terminal device.

The blog designation detail information DB 120 may store blog designation detail information including data (ie, designation blog data for each customer) in which the unique code of the customer and the unique code of the blog (designated blog) designated by the customer are matched. . 4 shows blog designation detail information according to an exemplary embodiment of the present invention.

The blog analysis information DB 130 stores blog analysis information that essentially includes recent update date and time (T2) data of a blog page matched with a blog unique code. The blog analysis information may be preferably further provided with at least one of 'recent blog page analysis data' and a blog name and a blog URL address. This will be described later in detail with reference to FIG. 5.

The web server 160 is connected to the customer terminal devices 181, 182, and 183 through the communication network 170, and the customer accesses each DB in the system 100 through the corresponding customer terminal device to retrieve and input necessary information. It performs an intermediate function.

The blog update management server 150 is responsible for the overall control of the system 100 to provide blog update information. Specifically, the blog update management server 150 basically controls the login process of the user (customer) to the system 100 using the customer information, and receives a request for providing a predetermined blog update information for the (specific) customer. In response to a request for providing blog update information, obtain predetermined 'date and time' (T1) data, and use a pre-prepared blog specification history information to pre-designate a blog for a customer (hereinafter referred to as a 'designated blog'). Get data, get pre-prepared 'last blog update date' (T2) data for each designated blog, compare T1 and T2 for each designated blog, and mark the blog as the target blog when T2 is later than T1 By setting, secure the 'Notification target blog list' for the entire designated blog, and use the notification target blog address list to The function of generating updated blog guide information having the blog number data and transmitting the generated blog guide information to the customer terminal device of the customer.

The blog management server 150 also configures and provides blog update information (described later) when the connection to the customer's system 100 is confirmed through the customer terminal device, and at the same time, updates the blog update information providing date and time. Can be done.

Meanwhile, according to the embodiment, when the system 100 includes the blog update information DB 140, the blog management server 150 generates the (update) blog update information by replacing the previous blog update information to generate the blog update information. After the DB 140 stores the connection to the customer's system 100 through the customer terminal device, the blog update information for the customer is read (read from the blog update information DB 140). It may be provided to the device and at the same time updating the previous 'blog update information providing date and time' (T12) as the current T12.

2 is a flowchart illustrating a development process of a method for providing blog update information according to an exemplary embodiment of the present invention. The blog update information providing method according to the present invention is implemented through a blog update information providing system connected to communicate with a customer terminal device through a communication network, in particular by the blog update information providing system 100 as shown in FIG. It can be optimally implemented. Hereinafter, a method of providing blog update information according to an exemplary embodiment of the present invention will be described with reference to FIGS. 1 to 8 in relation to the structure and operation of the system 100.

First, in step S200 of FIG. 2, the blog management server S200 receives a request for providing blog update information for a customer. 'Blog update information request request command' (hereinafter, simply referred to as 'request command') means that the blog management server 150 receives a request command generated from the corresponding customer terminal device by input selection of a user (customer). Can be. That is, when the customer wants to receive blog update information at a desired date and time, the blog management server 150 may receive the request command to the system 100 through the customer terminal device.

In addition, according to another embodiment of the present invention, a request command is automatically generated according to a predetermined program prepared in advance in the blog management server 150 itself and may be received by the blog management server 150. For example, if a specific customer registers an option of receiving blog update information at a certain time (eg, every hour) every day to the corresponding control program of the blog management server 150 through the web server 160, the request command is accordingly. This can be automatically generated. Alternatively, when the customer accesses the system 100, the blog update management server 150 may be automatically generated by generating a request command.

Following step S200, in step S210, in response to the blog update information providing request command received by step S200 (by the blog update management server 150), the 'standard date and time' prepared in advance (hereinafter, 'T1'). The process of acquiring data is performed. T1 is the latest date and time when the blog update information was provided to the customer, that is, the update blog guide information transmission date (T11) (described later in detail in step S260) or the latest blog update information providing date and time (T12) (later steps) (Described in detail with reference to S280), which is predefined by the system 100 in advance. In addition, a date and time different from the above embodiment may be predetermined as a reference date and time. According to an embodiment, the reference date and time may represent only a date, and may represent up to a minute or a second.

T1 may be provided as one data item (hereinafter, referred to as T1 data item) constituting customer information according to an embodiment of the present invention. 3 shows an example of a T1 data item according to an embodiment of the invention. That is, referring to the example of FIG. 3, the date data that recently provided blog update information for each customer is provided in the T1 data item. According to another embodiment of the present invention, the T1 data item may be separately stored in a dedicated memory (not shown) in the blog management server 150 or a separate T1 DB (not shown) in the system 100.

 That is, in step S200 and S210, the blog update management server 150 reads and secures the T1 data item stored in the customer information DB, the dedicated memory in the server 150, or the T1 DB in response to the request command.

In step S220, the designated blog data (i.e., the designated blog data for the customer) is prepared by using the blog designation history information prepared by the blog update management server 150 (for example, stored in the blog designation history information DB 120). , The designated blog identification data, for example, the designated blog unique code is common and may be the URL address of the blog). Here, the designated blog may be a blog in which the identification data (the blog update management server 150) has secured the identification data in advance by the customer's designation in advance, or the predetermined program by the system 100 (the blog management server 150 in the blog). This may be a blog specified by. In the latter case, for example, the identification data of the blog sites (for example, 191, 192, and 193 of FIG. 1) that have been accessed at least once through the system 100 for the last three months (for the blog update management server). (150) can be secured in advance and stored as a data item of the blog designation history information.

The blog designation history information may include data in which the unique code of the customer specific code and the specific code of the blog (designated blog) designated by the customer are matched (that is, the designated blog data for each customer) (for example, see FIG. 4).

In step S230 (blog management server 150) is performed to secure the 'recent blog update date and time' (T2) data prepared in advance for each designated blog. Here, according to an embodiment of the present invention, the process of preparing T2 in advance may be implemented through various methods.

For example, first, through a contract between an operator of the system 100 and an operator of the blog sites 191, 192, and 193, update date and time data is updated whenever a blog is updated from the management server of each blog site. For example, through the communication network 175) when transmitting to the blog management server 150 of the system 100, the blog management server 150 may receive this and store in a separate memory (not shown) or DB may be utilized. have.

Secondly, the receiving side (for example, the blog update management server 150) extracts and utilizes the updated date and time data of the blog page at a predetermined position in the blog page. In case of obtaining T2 by the first method or the second method, Blog Analysis Information (BAI) having a T2 matched with a blog unique code (hereinafter, abbreviated as 'BAI') may be used. For example, the blog analysis information DB 130 as shown in FIG. 1) may be prepared and used in advance.

Meanwhile, according to another preferred embodiment of the present invention, the designated blog data acquisition operation in step S220 and the T2 data acquisition operation in step S230 may be performed by the latest blog page analysis data (Latest Blog page analysis data). Data: LBD) (hereinafter, abbreviated as 'LBD').

In this case, the BAI includes a recent blog update date (T2) for each blog and 'recent blog page analysis data' of the blog page, and may further include a blog name, a blog URL address, and other information items. 5 illustrates blog analysis information according to an exemplary embodiment of the present invention.

Referring to FIG. 5, LBD has a total number of bytes and a status code value. The total number of bytes means a total number of bytes of a blog page (usually an Html document), and a status code value is, for example, a checksum value or a parity. The index and the CRC index can be referred to as values indicating the status of the blog page. 5 shows checksum values as examples of status code values.

Here, in calculating the total number of bytes and / or status code values, except for data that is not substantially related to changes in the content of the blog (content such as agenda, comments, etc.), such as the date, time, and number of visitors included in the blog page, It is necessary to pay attention to the calculation and accuracy. For those skilled in the art will be able to fully implement based on the above description bar further description will be omitted.

According to a preferred embodiment of the present invention (URL) address data acquisition operation for the designated blog (blog management server 150) previously described blog specification history information (see FIG. 4) and blog analysis information DB 130 stored It can be secured by associating existing BAIs. That is, the URL address data of the blog can be secured among the BAI data items matching the unique code of each designated blog by using the blog designation history information as shown in FIG. 4 and the BAI information as shown in FIG. 5. .

Acquiring the BAI is performed (by the blog update management server 150) prior to step S230, Figure 6 shows the deployment process of the BAI acquisition method according to an embodiment of the present invention.

First, in step S610, when a predetermined inquiry work start condition is satisfied (see step S611 of FIG. 6), each designated blog site is accessed to receive the corresponding blog page contents (see step S612 of FIG. 6). . If the inquiry task start condition is not satisfied, the process ends.

Here, the predetermined inquiry task start condition is predetermined by user's option selection or automatic setting of the system 100. For example, a condition for performing the inquiry task at regular time intervals (for example, inquiry at 08: 00 every day) )

Subsequently, in step S620, the operation of analyzing the corresponding blog page to obtain 'Current Blog page analysis data' (CBD) (hereinafter abbreviated as CBD) is performed (blog update management server). 150). The CBD is the same kind of data as the LBD described above and includes a total number of bytes and a status code value.

After step S620, in step S630, the CBD and the LBD are compared and analyzed to determine whether they are different, and if so, the process proceeds to step S640. Otherwise, the process ends. Criteria for determining whether the CBD and the LBD are different may be implemented in various ways. For example, it is determined that the total number of bytes is different. Further, even if the total number of bytes is the same, if the status code values are different from each other, it can be determined to be different. Although the LBD and the CBD have the same total number of bytes, if the checksum values are different, for example, 0x87KPx5C2 and 0x87KPx6C3, they are determined to be different.

In step S640, the T2 secured in step S230 is updated to the start date and time of the inquiry work (current T2) in step S610, and the latest blog analysis information is updated as a result by updating the LBD to CBD.

Meanwhile, according to another embodiment of the present invention, the date and time at which the latest blog analysis information is updated in step S640 may be set as the recent blog update date and time T2.

After step S230, the process proceeds to step S240, and in step S240 (the blog management server 150) compares T1 and T2 for each designated blog, and when the T2 is later than T1, the blog Is set as the notification target blog to secure the list of notification target blogs for the entire designated blog.

According to an embodiment of the present invention, step S240 may include step S241, step S242, and step S245 as shown in FIG. 2. In step S241, T2 and T1 are compared for each designated blog, and if T2 is later than T1, the process proceeds to step S243, otherwise the process goes to step S245.

For a designated blog, T2 is later than T1, meaning that the designated blog has been updated after the base date (T1), which means that the customer needs to provide additional information about the updated blog.

In step S243, the blog (that is, a blog whose T2 is later than T1) is set as the notification target blog. After that, the process proceeds to step S245, and when the processing is completed for the entire designated blog, the process proceeds to step S250, and otherwise returns to step S241. In this way, a list of blogs to be notified about the entire designated blog is obtained.

In the above, step S200 is preceded by steps S210, S220, and S230 S240, and step S240 is performed after steps S210 and S230, but according to an embodiment, steps S210 and S230 may be performed. In operation S230, the order of execution may be changed. Step S220 may be performed after step S210 but before step S240. In addition, step S220 and step S230 may be performed at the same time.

Subsequent to step S240, in step S250, the updated blog guide information or general guide information, which essentially has the notified blog number data, is stored as a document of any specification (for example, an Html document) using the notified blog list. Then, the content having the address of the document as a back URL or a link URL is transmitted to the customer terminal device (for example, 181) of the corresponding customer (via the communication network 170). It is to be noted that, in addition to the unique address (telephone number, Internet IP address, etc.) of the corresponding customer terminal device of the customer, the format of the updated blog guide information may be sent to the customer information based on the specification or performance information. For example, if the customer terminal device is an IMT-2000 mobile communication terminal with multimedia playback function, it provides update blog guide text data with background music in the background of a previously prepared video (or still image), but only alarm and text display. In the case of a supported terminal, the blog update management server can only transmit text data. Through the above steps (S200 to S250), the development process of the blog update information providing method according to an embodiment of the present invention may be completed.

Meanwhile, according to another preferred embodiment of the present invention, the updated blog guide information transmission date and time (T11) prepared in advance in step S260 after step S250 is updated in the step (S250). Updating as the current T11 may be further included.

8A and 8B are diagrams illustrating an example of customer connection confirmation and update blog guide information according to an operation of steps S270 and S280 according to an embodiment of the present invention. As shown in FIG. 8A, when the customer connection is confirmed, the updated blog guide information essentially having the number of updated blogs may be provided as shown in FIG. 8B.

The updated blog guide information may further include not only the number of updated blogs, but also a recent blog update date (T2) of the updated blog (for example, a portion of 2003/09/10 and 08:01 shown in FIG. 8B) and a name. . In addition, detailed history data of the updated blog, for example, as shown in FIG. 8B, data indicating that 15 agenda items are updated and 25 comments are updated may be provided. In addition, as shown in the example of FIG. 8B (see the expression 9/9/03 after 8:00 AM), a reference date and time may be indirectly provided. And, in the case of being associated with the example of FIG. 7 to be described below, in the update guide information, the link URL address (or back URL address) of each blog, the link URL address in the following specification and claims include the back URL address. It can be used as a broad concept).

Blog update information providing method according to another preferred embodiment of the present invention may further comprise step (S270) and step (S280).

In step S270 (by the blog management server 150) is performed to confirm that the customer is connected to the system (for example through the customer terminal device), if the connection is not confirmed, the process is When the connection is terminated and the connection is confirmed, the blog update information is immediately configured (by the blog management server 150) in step S280 and provided (for example, so that the customer can access and view through the web server 160). Publish as a web page) or provide a document corresponding to the blog update information that you have already configured when sending the guidance information, and update its delivery date (ie, the blog update information delivery date (T12)) (i.e., the previous T12 Is currently updated to T12). This concludes the process.

Here, the blog update information may be composed of data only for the updated blog, for example, as shown in FIG. 9A, or alternatively, not only the updated blog as shown in FIG. 9B, but also the entire designated blog designated by the customer. It may also consist of data. In the latter case, in order to distinguish the updated blog separately, for example, as shown in the example of FIG. The blog update information generally includes a name (title) of the blog and a recent blog update date and time (T2) by default. In addition, the number of updated blogs and / or the total number of designated blogs may also be provided.

FIG. 7 is a flowchart illustrating a subsequent process following step S260 of the method of providing blog update information according to an exemplary embodiment of the present invention shown in FIG. 2. According to one preferred embodiment of the present invention, after the method of providing blog update information is performed from step S200 to step S260, the method may further include a subsequent process (by the customer terminal device) as illustrated in FIG. 7. Can be. However, this subsequent process assumes that the update guide information includes a link URL address of each blog.

In step S261, an operation of displaying the updated blog guide information (on the display screen of the client terminal device) transmitted in step S250 is performed. Subsequently, in step S262, it is determined whether a connection request signal to the link URL included in the updated blog guide information is generated. When a connection request signal is generated, the subsequent process proceeds to step S263, and accesses the link URL address. The movement is done. If the access request signal does not occur in step S262, the subsequent process is terminated.

Thereafter, in step S264, (the client terminal device) downloads and displays the blog update information prepared in advance or the update information configured by the update blog management server 150 at the time of the connection / move confirmation in step S263. do.

Here, a significant time difference may be issued between the execution date and time of step S261 and the execution date and time of step S264, in which case the number of blogs to be notified included in the updated blog guide information provided in step S261 and It should be noted that there may be a significant difference from the number of blogs to be notified included in the blog update information provided in step S264.

 In a subsequent step S265, if it is determined by the (customer terminal device) whether or not a connection / movement request signal to a specific blog has occurred, go to step S267, otherwise proceed to step S266. In step S267, after accessing / moving to the URL address of the blog, the corresponding blog page is downloaded and displayed, thereby ending the subsequent process.

In step S266, if a return request signal (return signal or 'move back' signal) occurs (at the customer terminal device), the process returns to step S264 again, otherwise the process is terminated.

FIG. 10 is a flowchart illustrating a subsequent process following step S260 of the method of providing blog update information according to an exemplary embodiment of the present invention shown in FIG. 2. According to an embodiment of the present invention, as shown in FIG. 10 (performed by the updated blog management server 150) after the method of providing blog update information is performed from step S200 to step S260 of FIG. 2. Steps S290, S295, and S297 may be further included.

In step S290, the current blog update information is generated by replacing the previous blog update information prepared in advance (for example, previously stored in the blog update information DB 140) to generate the current blog update information (for example, the blog update information DB 140). )). Subsequently, in step S295, step S295, which is the same as the step S270 of FIG. 2, is performed. That is, the operation of confirming that the customer connects to the system 100 (for example, through the customer terminal device) is performed (by the blog management server 150). When the connection is terminated, the process proceeds to step S297.

In step S297 (update blog management server 150) provides the current blog update information generated and stored in the step (S290) (for example, provided as a web page through the web server 160), and transfer Update T12 as the current T12 and end the process.

Although the above description is limited to specific embodiments of the present invention, those skilled in the art can make various modifications without departing from the scope of the technical idea described in the claims of the present invention defined below.

As described above, according to the present invention, by providing blog update information, the user can increase his or her use of the blog service and increase satisfaction. Also, by allowing the user to access the blog site only when the blog is updated, unnecessary blog site access is provided. By reducing the number of times, you can reduce the load on the network, while reducing the user's charges and increasing the efficiency of the blog service.

Claims (20)

In the blog update information providing method implemented through a blog update information providing system connected to communicate with a customer terminal device via a communication network, (a) receiving a request for providing blog update information for a customer; (b) obtaining predetermined 'reference date and time' (T1) data in response to the request for providing blog update information; (c) securing a designated blog list of the customer by using previously prepared blog designation history information; (d) obtaining 'recent blog update date and time' (T2) data prepared in advance for each of the designated blogs; (e) comparing the T1 and T2 for each designated blog, and if the T2 is later than T1, setting the blog as a notification target blog to secure a 'notified target blog list' for the entire designated blog of the customer; ; (f) a blog comprising generating updated blog guide information having notification number of blog number data and a link URL address of each notification target blog using the notification target blog list, and transmitting the updated blog guide information to the customer terminal device of the customer; How to provide renewal information. The method of claim 1, And the blog update information providing request command is received from a customer terminal device of the customer or generated and received by a predetermined program of the system itself. The method of claim 1, wherein after step (f) (g) updating a previously prepared 'update blog guide information transmission date and time' (T11) to the current T11 which is the transmission date and time in the step (f). The method of claim 3, wherein after step (g) (h) confirming that the customer accesses the system through the customer terminal device; (i) When the connection is confirmed in the step (h), the 'blog update information' having the name and T2 for each of the notification target blogs is configured and provided to the customer terminal device using the notification target blog list. And updating the previously prepared 'blog update information providing date and time' (T12) as the current T12. The method of claim 3, wherein after step (g) (g1) generating and storing current blog update information in place of previously prepared blog update information, wherein each blog update information is provided with a name and T2 for the notification target blog; (g2) confirming that the customer accesses the system through the customer terminal device; (g3) when the connection is confirmed in step (g2), providing the current blog update information to the client terminal device, and updating a previously prepared 'blog update information providing date and time' (T12) as the current T12. Blog update information providing method characterized in that it further comprises. The method of claim 3, wherein In step (d), the T2 is secured by extracting from the previously prepared 'Blog Analysis Information (BAI)' (hereinafter abbreviated as BAI). A method for providing blog update information, characterized in that it has 'Latest Blog page analysis data (LBD)' (hereinafter abbreviated as LBD) and the recent blog update date and time (T2). The method of claim 4, wherein the updated blog guide information further has a title and T2 of the blog. The method according to claim 4 or 5, And wherein T1 is predetermined as either one of the previous T11 and the previous T12. The method of claim 6, wherein the technique for preparing the BAI in advance (d1) 'accessing a designated blog site / obtaining a corresponding blog page' step of accessing a corresponding site of each designated blog and receiving a corresponding blog page when a predetermined inquiry work start condition is satisfied; (d2) analyzing contents of the corresponding blog page to obtain 'Current Blog page analysis data' (CBD) (hereinafter abbreviated as CBD); (d3) updating the latest blog analysis information by updating the T2 (previous T2) to the inquiry task start date and time (current T2) in step d1 and updating the LBD to the CBD when the CBD is different from the LBD; Blog update information providing method, characterized in that performed through. The method of claim 6, The designated blog information includes a data item in which a customer specific code and a designated blog unique code are matched, and the T2 data securing operation in step (d) is performed by associating the designated blog information with T2 included in the BAI. How to provide blog update information characterized by. 8. The method of claim 7, wherein after step (g) (j) downloading and displaying the updated blog guide information; (k) accessing / moving to the link URL site when a connection request signal to the link URL included in the updated blog guide information is generated; (l) downloading and displaying blog update information from the link URL site; (m) When a request for access / move to a specific blog occurs, the step of downloading and displaying the blog page after access / move to the URL address of the blog is performed by the client terminal device. How to provide blog update information. 8. The blog update information providing method according to claim 7, wherein the blog update information has its name and T2 for the entire designated blog including the notification target blog, respectively. The method of claim 9, Each of the LBD and the CBD has a total number of bytes and a status code value of the corresponding blog page. If the total number of bytes and the status code value of the LBD and the CBD are different in step (d3), the LBD and the CVD are different from each other. The blog update information providing method characterized in that it is determined to be different. The method of claim 9, In step (d1), it is determined whether an inquiry task start condition is satisfied based on a predetermined BAI inquiry option, and the condition data for which method to access which designated site at which time and how to query the predetermined BAI inquiry option. Blog update information providing method characterized in that the provided. In the blog update information providing system connected to communicate with the customer terminal device, A customer information DB for storing customer information having ID data of the customer and terminal device ID data of the customer; A blog designation detail information DB having designation blog data for each customer; A blog analysis information DB for storing blog analysis information having a recent blog update date and time (T2) data matched with a unique code thereof for a designated blog; A web server for performing a mediating function such that a customer accesses the respective DBs through the customer terminal device and the communication network and searches and inputs necessary information; Control the login process of the customer by using the customer information, secure the 'standard date and time' (T1) data prepared in advance in response to a request for providing blog update information, and designate the customer by using the blog designation history information. Obtain a list of blogs, obtain 'recent blog update date' (T2) data of the designated blog from the blog analysis information, and compare the T1 and T2 for each designated blog, so that T2 is later than T1. In this case, by setting the blog as a notification target blog, a 'notification target blog list' of the entire designated blog of the customer is secured, and the updated blog guide information having the number of blog target notification data is generated using the notification target blog list. It includes a blog update management server for transmitting to the customer terminal device of the customer Blog update information providing system characterized by. The blog update information providing system according to claim 15, wherein the T1 is provided as one data item in the customer information. The method of claim 15, And the blog update information providing request command is received from the client terminal device or generated and received by a predetermined program of the blog management server itself. 16. The method of claim 15, wherein if the blog update management server is confirmed that the customer's access through the customer terminal device ++, the blog update information is configured and provided through the web server and the previous 'blog update information providing date and time' ( T12), wherein the blog update information is provided with a name and T2 for the notification target blog. The blog update information DB is further included in the system, and the blog update management server generates the current blog update information by replacing the previous blog update information previously stored in the blog update information DB. After storing in the update information DB, if the customer's access through the customer terminal device is confirmed, the current blog update information for the customer is provided through the web server and the previous 'blog update information provision date and time' (T12) And updating the current blog as T12, wherein the blog update information includes a name and T2 for the notification target blog. The method according to claim 15, wherein the blog analysis information (abbreviated as BAI) has 'recent blog page analysis data' (hereinafter abbreviated as LBD) of each blog page and the latest blog update date and time (T2), The blog update management server, When a predetermined inquiry task start condition is satisfied, the corresponding blog page is accessed to receive the blog page, and the content of the blog page is analyzed to obtain 'current blog page analysis data' (hereinafter abbreviated as CBD). Next, if the CBD is different from the LBD, the function of updating the latest blog analysis information by updating the T2 (previous T2) to the search task start date and time (current T2) and updating the LBD to the CBD. Blog update information providing system.

Images