Information processing system, information processing server, and information processing method

Abstract

To provide an information processing system, an information processing server, and an information processing method capable of improving convenience when providing useful information such as patent information to a user.SOLUTION: In the information processing system 10 or an information processing method, when a first monitoring unit 74 detects the occurrence of a target event (such as a decision to grant a patent), an information processing server 30 reports the occurrence of the target event to a user terminal 20. The information processing server 30 then collectively notifies each user terminal 20 of the determination result including the target application in which the occurrence of the target event has not been detected.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing server, and an information processing method.

Background Art

[0002] In Patent Document 1, it is an issue to propose an apparatus for calculating patent power in accordance with an evaluation method capable of specifying the causal relationship with economic activities (the exclusive right of a patent right) (

[0006] , summary). To solve this issue, the patent power calculation apparatus of Patent Document 1 (summary) includes an arrangement standardization data acquisition unit, an item content extraction unit, a search result holding unit, a cost table holding unit, an obsolescence function storage unit, an obsolescence cost calculation unit, a summation unit, and an output unit.

[0003] The item content extraction unit searches for a combination of standard item names indicating legal procedures, and extracts item content together with the procedure date according to the searched combination of standard item names. The search result holding unit holds the extracted item content and the procedure date. The cost table holding unit holds a cost table in which costs prepared in advance for each combination of item contents are associated. The obsolescence function storage unit stores an obsolescence function serving as a standard for obsolescence of the technology for each technical field. The obsolescence cost calculation unit acquires costs using the cost table, and calculates the obsolescence cost on the calculation reference date using the calculation reference date, the procedure date, the filing date, and the obsolescence function. The summation unit sums up all the calculated obsolescence costs for the application. The output unit outputs the summation value obtained by the summation unit.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] As described above, the patent strength calculation device described in Patent Document 1 (abstract) is intended to calculate patent strength in accordance with an evaluation method that can identify a causal relationship with economic activity (the exclusive power of patent rights). Such a device is understood to be usable for evaluating a company's competitiveness, investment activities in companies, etc. However, Patent Document 1 has room for improvement in terms of user convenience when providing the calculated patent strength (useful information). Similar issues exist in applications other than the presentation of patent strength.

[0006] This invention was made in consideration of the above-mentioned problems, and aims to provide an information processing system, an information processing server, and an information processing method that can improve the convenience of providing useful information such as patent information to users. [Means for solving the problem]

[0007] The information processing system according to the present invention comprises a user terminal and an information processing server, The aforementioned user terminal is The user-side communication unit that transmits and receives information with the aforementioned information processing server, An input unit that accepts input of application number identification information or the said application number for identifying the target application that is the application to be searched, A user-side control unit that transmits the application number identification information or the target application number entered in the input unit, along with the user's identification information, to the information processing server via the user-side communication unit. Equipped with, The aforementioned information processing server is The server-side communication unit that sends and receives data with the user terminal, A search target database that stores the aforementioned application number identification information or the aforementioned target application number in association with the user's identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the target application or the application number identification information at a first predetermined timing, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit, Equipped with, When the first monitoring unit detects the occurrence of the target event, the server-side control unit promptly notifies the user terminal of the occurrence of the target event via the server-side communication unit, and then notifies each user terminal of the determination results, including the target application for which the occurrence of the target event was not detected. It is characterized by the following:

[0008] According to the present invention, when the occurrence of a target event is detected, a notification is sent to the user terminal. Therefore, the user can immediately know that a target event has occurred related to the target application or application number identification information. Subsequently, the determination results, including target applications for which no target event was detected, are notified to each user terminal in a condensed manner. Therefore, the user can know the overall determination results at that time. Thus, user convenience can be improved.

[0009] When the first monitoring unit detects the occurrence of the target event on a specific day of the week, the server-side control unit may promptly notify the user terminal of the occurrence of the target event via the server-side communication unit, and then notify each user terminal of the determination results, including the target applications for which the occurrence of the target event was not detected. Alternatively, when the first monitoring unit detects the occurrence of the target event on a day other than the specific day of the week, the server-side control unit may promptly notify the user terminal of the occurrence of the target event via the server-side communication unit, while omitting notification of the determination results, including the target applications for which the occurrence of the target event was not detected. This makes it possible to avoid the inconvenience of receiving notifications of determination results, including target applications for which the occurrence of the target event was not detected, on days other than the specific day of the week, if the occurrence of the target event tends to be concentrated on a specific day of the week.

[0010] The input unit may accept input of the target event for each application number identification information, each target application number, or each user, in addition to the application number identification information or the target application number. The user-side control unit may transmit the target event input to the input unit to the information processing server via the user-side communication unit. The first monitoring unit may determine, at each first timing, whether or not the target event has occurred for each target application number, each application number identification information, or each user. This makes it possible to select the target event for each target application or each user. Therefore, it is possible to further improve user convenience.

[0011] The search target database may include an application information storage unit that stores the target application number and the current status of the target application in association with the user's identification information. The server-side control unit may extract the target application number from the application information storage unit in a manner that avoids duplication. The first monitoring unit may determine whether or not the target event has occurred for each of the extracted target application numbers. When the first monitoring unit detects the occurrence of the target event, the server-side control unit may, in the application information storage unit, promptly notify each of the user terminals associated with the target application in which the target event occurred of the occurrence of the target event. Alternatively, the server-side control unit may determine whether or not the target event has occurred for all of the target application numbers extracted from the application information storage unit, and then notify each user terminal of the determination results collectively.

[0012] This eliminates duplicate application numbers, reducing the computational load and processing time required to determine whether or not a target event has occurred, and enabling earlier notification of the determination results. Consequently, user convenience can be further improved.

[0013] If the application number identification information includes the name of the applicant of the target application, the information processing server or the user terminal may have an application number search unit that searches for the target application number based on the name of the target applicant. This allows the user to identify the target application simply by entering the name of the target applicant.

[0014] The server-side control unit may include a first evaluation unit that evaluates the degree of impact of the target application on the business of the target applicant, who is the applicant of the target application. The search target database may store the degree of impact for each application number identification information or for each target application number. When the first monitoring unit detects the occurrence of the target event, the server-side control unit may promptly notify the user terminal of the occurrence of the target event and the degree of impact via the server-side communication unit. This makes it possible for the user to refer not only to the occurrence of a target event related to the target application, but also to the degree of impact of the target application on the business of the target applicant.

[0015] The first evaluation unit may search the internet for articles concerning the target applicant. The first evaluation unit may also determine the degree of relevance between the content included in the target application and the internet articles. Furthermore, the first evaluation unit may determine the degree of influence based on the degree of relevance. It is considered that internet articles may contain content that is highly relevant to the target applicant's business. Therefore, by using an influence level based on the degree of relevance between the invention content included in the target application and the internet articles, it becomes possible to present a more accurate influence level to the user.

[0016] The first monitoring unit may be a plurality of virtual servers configured by the server-side control unit. The plurality of virtual servers may obtain the target application number for which they are responsible from the server-side control unit, determine whether or not the target event has occurred for the obtained target application number, and transmit the determination result to the server-side control unit. By using the first monitoring unit as a plurality of virtual servers, it is possible to reduce the overall processing time and to notify the determination result earlier. Therefore, it is possible to further improve user convenience.

[0017] The information processing server may include a second monitoring unit that determines, at second predetermined intervals, whether there are any new articles on the internet for each of the target applicants of the target application after the occurrence of the target event has been detected, and a second evaluation unit that determines the degree of agreement between the content included in the target application after the occurrence of the target event has been detected and the new article. Furthermore, when the degree of agreement indicates that the new article relates to the target application, the server-side control unit may notify the user terminal of the occurrence of the new article via the server-side communication unit. This allows, for example, the user to know that an IR (Investor Relations) announcement regarding a patent grant has been made for a target application for which a patent grant has been issued as a target event.

[0018] The information processing server according to the present invention is A server-side communication unit that receives application number identification information or the said application number from a user terminal to identify the target application number which is the application to be searched, A searchable database that stores the aforementioned application number identification information or the aforementioned target application number in association with user identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the target application or the application number identification information at a first predetermined timing, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit, comprises, when the first monitoring unit detects the occurrence of the target event, the server-side control unit promptly reports the occurrence of the target event to the user terminal via the server-side communication unit, and then notifies the determination result including the target application for which the occurrence of the target event has not been detected for each user terminal in a summary manner characterized in that

[0019] The information processing server according to the present invention a server-side communication unit that receives application number identification information for specifying a target application number as the application number of a target application to be searched or the target application number from a user terminal, a search target database that stores the application number identification information or the target application number in association with user identification information, a first monitoring unit that determines the presence or absence of the occurrence of a target event, which is an event to be searched, for each of the target application or the application number identification information at each first predetermined timing, a server-side control unit that controls the operations of the server-side communication unit, the search target database, and the first monitoring unit comprises, the server-side control unit includes a first evaluation unit that evaluates the degree of influence of the target application on the business of the target applicant who is the applicant of the target application, the search target database stores the degree of influence for each application number identification information or each target application number, when the first monitoring unit detects the occurrence of the target event, the server-side control unit notifies the user terminal of the occurrence of the target event and the degree of influence via the server-side communication unit characterized in that

[0020] The information processing server according to the present invention a server-side communication unit that receives application number identification information for specifying a target application number as the application number of a target application to be searched or the target application number from a user terminal, A searchable database that stores the aforementioned application number identification information or the aforementioned target application number in association with user identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the target application or the application number identification information at a first predetermined timing, A second monitoring unit determines, at predetermined intervals, whether there are any new articles on the internet for each of the target applicants who are applicants of the aforementioned target application, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit and the second monitoring unit. It is equipped with, The server-side control unit includes a second evaluation unit that determines the degree of agreement between the content included in the target application after the occurrence of the target event is detected and the new article on the internet. The server-side control unit, When the first monitoring unit detects the occurrence of the target event, it notifies the user terminal of the occurrence of the target event via the server-side communication unit. When the degree of similarity indicates that the new article relates to the target application, the server-side communication unit notifies the user terminal of the occurrence of the new article. It is characterized by the following:

[0021] The information processing method according to the present invention is a method used in an information processing system having a user terminal and an information processing server, The aforementioned user terminal is The user-side communication unit that transmits and receives information with the aforementioned information processing server, An input unit that accepts input of application number identification information or the said application number for identifying the target application that is the application to be searched, A user-side control unit that transmits the application number identification information or the target application number entered in the input unit, along with the user's identification information, to the information processing server via the user-side communication unit. Equipped with, The aforementioned information processing server is The server-side communication unit that sends and receives data with the user terminal, A search target database that stores the aforementioned application number identification information or the aforementioned target application number in association with the user's identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the aforementioned target applications at a first predetermined timing, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit, Equipped with, When the first monitoring unit detects the occurrence of the target event, the server-side control unit promptly notifies the user terminal of the occurrence of the target event via the server-side communication unit, and then notifies each user terminal of the determination results, including the target application for which the occurrence of the target event was not detected. It is characterized by the following: [Effects of the Invention]

[0022] According to the present invention, it becomes possible to improve the convenience of providing useful information such as patent information to users. [Brief explanation of the drawing]

[0023] [Figure 1] This is a schematic diagram of an information processing system according to the first embodiment of the present invention. [Figure 2] This is a block diagram of the components of the information processing system according to the first embodiment. [Figure 3A] This is a simplified diagram showing the user table of the first embodiment. [Figure 3B] This is a simplified diagram showing the application table of the first embodiment. [Figure 3C] This diagram shows a simplified report timing determination table for the first embodiment. [Figure 4] This is a flowchart of the crawler control according to the first embodiment. [Figure 5] This is an explanatory diagram showing a part of the crawler control in the first embodiment. [Figure 6]It is a block configuration diagram of an information processing server of an information processing system according to the second embodiment. [Figure 7] It is a flowchart of application registration control of the second embodiment. [Figure 8] It is a flowchart of second crawler control of the second embodiment.

Mode for Carrying Out the Invention

[0024] A. First Embodiment <A-1. Configuration of the First Embodiment> [A-1-1. Overall Configuration] FIG. 1 is a schematic configuration diagram of an information processing system 10 according to the first embodiment of the present invention. FIG. 2 is a block configuration diagram of each part of the information processing system 10 according to the first embodiment. As shown in FIGS. 1 and 2, the information processing system 10 (hereinafter also referred to as "system 10") includes a plurality of user terminals 20, an information processing server 30, and a data providing server 40. The user terminal 20, the information processing server 30, and the data providing server 40 can communicate with each other via the Internet 50.

[0025] The user terminal 20 is an input device for inputting a patent application number to be searched (hereinafter referred to as "target application number ANtar" or "target number ANtar"), and is also a display device or an output device for displaying or outputting a report from the information processing server 30. The information processing server 30 accesses the data providing server 40 at a predetermined timing, searches whether a target event Etar has occurred for the target application number ANtar specified by the user, and notifies the search result to the user terminal 20.

[0026] The target event Etar is an event that requests a search for the target application number ANtar, and is fixed in the first embodiment. In the case of a Japanese patent application, the target event Etar includes, for example, a patent grant and a rejection decision. In the case of a US patent application, the target event Etar includes, for example, a Notice of Allowance, a Notice of Allowability, and a Final Office Action.

[0027] The data provision server 40 has a patent database 432 (Figure 2) that stores data (patent data Dpat) related to bibliographic and progress information of patent applications. The data provision server 40 provides or transmits patent data Dpat in response to requests from external devices such as the data processing server 30. For example, the server of the Japan Patent Information Platform (J-PlatPat) (both registered trademarks) can be used as the data provision server 40.

[0028] Based on the search results received from the information processing server 30 to the user terminal 20, the user can learn whether or not a target event Etar has occurred for a patent application identified by the target application number ANtar (hereinafter also referred to as "target application APNtar"). Then, for example, the user can use the information on the occurrence of the target event Etar to carry out business activities, investment activities, etc.

[0029] [A-1-2. User terminal 20] As described above, the user terminal 20 receives the target application number ANtar from the user and transmits it to the information processing server 30. It also notifies the user of the search results received from the information processing server 30. As shown in Figure 2, the user terminal 20 comprises an input / output unit 200, a communication unit 210, an arithmetic unit 220, and a storage unit 230, and is composed of, for example, a general personal computer, a tablet terminal, or a smartphone.

[0030] The input / output unit 200 performs input and output with the user. The input / output unit 200 has, for example, a keyboard, mouse, touch panel, microphone, etc. as an input unit. The input / output unit 200 also has, for example, a display, touch panel, etc. as an output unit. The communication unit 210 has, for example, a modem (not shown) and communicates with the information processing server 30 etc. via the internet 50 (Figure 1).

[0031] The arithmetic unit 220 includes a central processing unit (CPU) and operates by executing a program stored in the memory unit 230. Some of the functions performed by the arithmetic unit 220 can also be implemented using logic ICs (Integrated Circuits). The arithmetic unit 220 can also implement some of the aforementioned programs using hardware (circuit components). The same applies to the arithmetic units 320 and 420 of the information processing server 30 and data provision server 40, which will be described later.

[0032] The storage unit 230 stores programs and data used by the arithmetic unit 220 and includes random access memory (hereinafter referred to as "RAM"). The RAM can be volatile memory such as registers, or non-volatile memory such as hard disks or flash memory. In addition to RAM, the storage unit 230 may also have read-only memory (ROM). The storage units 330 and 430 of the information processing server 30 and data provision server 40, described later, are similar.

[0033] [A-1-3. Information Processing Server 30] (A-1-3-1. Overview) As described above, the information processing server 30 determines whether or not a target event Etar has occurred for the target application number ANtar received from the user terminal 20, using the patent data Dpat from the data provision server 40, and notifies the user terminal 20 of the determination result. As shown in Figure 2, the information processing server 30 has an input / output unit 300, a communication unit 310, an arithmetic unit 320, and a storage unit 330. The input / output unit 300 has a communication port, etc. (not shown). The communication unit 310 has a modem, etc. (not shown) and communicates with the user terminal 20 and the data provision server 40 via the internet 50. The arithmetic unit 320 includes a CPU and operates by executing a program stored in the storage unit 330. The storage unit 330 stores the program and data used by the arithmetic unit 320.

[0034] (A-1-3-2. Arithmetic unit 320) As shown in Figure 2, the calculation unit 320 of the information processing server 30 includes a user management unit 322, an application information management unit 324, and a crawler management unit 326. The user management unit 322 performs user management control to manage user information. User information includes user identification information (user ID) and user attribute information (name, address, email address, etc.). The application information management unit 324 performs application information management control to manage information on target patent applications (target application information). The crawler management unit 326 performs crawler control to perform crawler processing to determine whether a target event Etar has occurred for a patent application (target application APNtar) that the user wishes to monitor.

[0035] (A-1-3-3. Storage section 330) As shown in Figure 2, the storage unit 330 of the information processing server 30 has an information processing database 322 (hereinafter referred to as "information processing DB 322"). The information processing DB 322 has a user table 340, an application table 342, and a reporting timing determination table 344.

[0036] Figure 3A is a simplified diagram of the user table 340 in the first embodiment. The user table 340 manages user information. As shown in Figure 3A, the user information includes user identification information (user ID), username, address, email address, and telephone number. The user table 340 may also include other user information (e.g., service plan name).

[0037] Figure 3B is a simplified diagram of the application table 342 of the first embodiment. The application table 342 manages information about the target application APNtar (application information). As shown in Figure 3B, the application information includes the application number of the target application APNtar, the user ID, the current status of the target application APNtar, and the report flag. The application table 342 may also include other application information (e.g., publication date, registration date, and remarks). The current status includes, for example, under examination, patent granted, and rejection. The report flag will be described later with reference to Figure 5.

[0038] Figure 3C is a simplified diagram showing the reporting timing determination table 344 of the first embodiment. The reporting timing determination table 344 is a table used to determine the timing for normal reporting in this crawler processing, and includes the current status and update time of each part (details will be described later with reference to Figure 5).

[0039] [A-1-4. Data provision server 40] As described above, the data providing server 40 provides patent application data (patent data Dpat) in response to requests from external devices such as the user terminal 20 and the information processing server 30. As shown in FIG. 2, the data providing server 40 includes an input / output unit 400, a communication unit 410, an arithmetic unit 420, and a storage unit 430. The input / output unit 400 has a communication port (not shown) or the like. The communication unit 410 has a modem (not shown) or the like and communicates with the user terminal 20 and the information processing server 30 via the Internet 50. The arithmetic unit 420 includes a CPU and operates by executing a program stored in the storage unit 430. The storage unit 430 stores programs and data used by the arithmetic unit 420 and has a patent database 432 (hereinafter referred to as "patent DB 432"). The patent DB 432 accumulates patent data Dpat.

[0040] <A-2. Control in the First Embodiment> [A-2-1. Overview] As described above, the information processing server 30 of the first embodiment executes user management control, application information management control, and crawler control.

[0041] [A-2-2. User Management Control] As described above, the user management control manages user information. The user management control includes a new user registration control that accepts new user registration and a user information update control that updates registered user information.

[0042] In the new user registration control, the information processing server 30 (user management unit 322) transmits data of a new user input screen to the user terminal 20 in response to a request from the user terminal 20. The user terminal 20 displays the received data of the new user input screen and accepts input of user information from the user. Then, the user terminal 20 transmits the input user information to the information processing server 30. The information processing server 30 accumulates the user information received from the user terminal 20 in the information processing DB 322 (user table 340).

[0043] In user information update control, the information processing server 30 (user management unit 322) sends data from the user information update screen to the user terminal 20 in response to a request from the user terminal 20. The user terminal 20 displays the received data from the user information update screen and accepts user information (update information) input from the user. The user terminal 20 then sends the entered update information to the information processing server 30. The information processing server 30 stores the update information received from the user terminal 20 in the information processing DB 322 (user table 340).

[0044] [A-2-3. Application Information Management and Control] The application information management control manages information (application information) for target application numbers ANtar. The application information management control includes an application registration control for registering new target application numbers ANtar and an application information update control for updating registered application information.

[0045] In the application registration control, the information processing server 30 (application information management unit 324) sends data from the application input screen to the user terminal 20 in response to a request from the user terminal 20. The user terminal 20 displays the received data from the application input screen and accepts input of a new target application number ANtar from the user. The user terminal 20 then sends the entered target application number ANtar and user ID to the information processing server 30. The information processing server 30 stores the target application number ANtar received from the user terminal 20 in the information processing DB 322 (application table 342), associating it with the user ID.

[0046] In the application information update control, the information processing server 30 (application information management unit 324) sends data from the application information update screen to the user terminal 20 in response to a request from the user terminal 20. The user terminal 20 displays the received data from the application information update screen and accepts input of patent information (update information) from the user. The user terminal 20 then sends the entered update information to the information processing server 30. The information processing server 30 stores the update information received from the user terminal 20 in the information processing DB 322 (application table 342).

[0047] [A-2-4. Crawler Control] (A-2-4-1. Overview) Figure 4 is a flowchart of the crawler control according to the first embodiment. In step S11, the information processing server 30 (crawler management unit 326) determines whether or not to start the crawler management process (in other words, whether or not the timing to start the crawler management process has arrived). The start timing referred to here can be, for example, the timing immediately after the data update of the patent DB 432 in the data provision server 40. If the crawler management process is to be started (S11: true), the process proceeds to step S12.

[0048] In step S12, the information processing server 30 executes crawler management processing. In the crawler management processing, it is determined whether or not a target event Etar has occurred for the target application APNtar. As shown in Figure 4, the crawler management processing includes general management processing (S121), crawler processing (S122), rapid reporting processing (S123), and normal reporting processing (S124).

[0049] The general management process (S121) manages the entire crawler management process. The crawler process (S122) determines whether a target event Etar has occurred for the target application number ANtar via data communication with the data provision server 40, and performs processing according to the determination result. The rapid reporting process (S123) is the process of issuing a rapid report prior to the regular report (described later) if a target event Etar is detected for the target number ANtar. The regular reporting process (S124) is the process of reporting the search results regardless of whether a target event Etar has been detected for the target number ANtar. Note that the regular reporting process (S124) may be performed only on specific days of the week (for example, only on Wednesdays), while the rapid reporting process (S123) may be performed on multiple days of the week, including a specific day of the week (for example, every day). Details of these processes (S121~S124) will be described later with reference to Figure 5.

[0050] After the crawler management process is complete, return to step S11.

[0051] (A-2-4-2. Crawler management process) Figure 5 is an explanatory diagram showing a part of the crawler control in the first embodiment. As shown in Figure 5, the calculation unit 320 (crawler management unit 326) of the information processing server 30 has an overall management unit 70, a request queue 72, a crawler unit 74, a rapid report queue 76, a first mail unit 78, a normal report queue 80, and a second mail unit 82. The overall management unit 70 has a data reading unit 700, a data update unit 702, a rapid report unit 704, and a normal report unit 706. Each unit is a functional unit (in other words, control or processing) that is realized by the execution of a program.

[0052] The crawler management process flow will be explained with reference to Figure 5. Upon commencement of the crawler management process, the overall management unit 70 and each crawler unit 74 begin operation (or control or processing). Specifically, the data reading unit 700 of the overall management unit 70 begins the processing described later. The data update unit 702 of the overall management unit 70 monitors at a first predetermined period whether the combination of target application number ANtar and target event Etar is stored in the normal reporting queue 80. Furthermore, the rapid reporting unit 704 monitors at a second predetermined period whether the combination of target application number ANtar and target event Etar is stored in the rapid reporting queue 76. In addition, the normal reporting unit 706 monitors the state of the reporting timing determination table 340 at a third predetermined period. Moreover, each crawler unit 74 monitors at a fourth predetermined period whether the target application number ANtar is stored in the request queue 72. Furthermore, at the start of the crawler management process, each part of the reporting timing determination table 340 (Figure 3C) sets its status to "standby" and records the date and time (update date and time) at that time.

[0053] In the crawler management process, the data reading unit 700 of the overall management unit 70 first reads all target number ANtars with a report flag of 1 (report required) from the application table 342 (Figure 3B) of the information processing DB 322. In the application table 342, target number ANtars and user IDs are recorded in pairs (Figure 3B), but the data reading unit 700 reads the target number ANtars in a way that avoids duplication of target number ANtars, for example, by using the DISTINCT method of Ruby on Rails (step S21 in Figure 5). In addition, when the data reading unit 700 starts reading, it changes the status of the overall management unit 70 in the report timing determination table 340 (Figure 3C) to "active" and updates the update date and time.

[0054] The data reading unit 700 then sets the number of crawler units 74 to be started according to the number of target numbers ANtar read, and starts the set number of crawler units 74 (virtual servers). The more target numbers ANtar read, the more crawler units 74 are started. The data reading unit 700 also generates a record for each crawler unit 74 in the reporting timing determination table 340 corresponding to the started crawler units 74, sets the status of each crawler unit 74 to "standby," and updates the update date and time.

[0055] Next, the data reading unit 700 writes or copies all of the read target number ANtar to the request queue 72 (step S22). After writing or copying is complete, the data reading unit 700 returns the state of the overall management unit 70 in the reporting timing determination table 340 to "standby" and updates the update date and time. Each crawler unit 74 reads one of the target number ANtar stored or copied in the request queue 72 and deletes the read target number ANtar from the request queue 72 (step S23). In addition, each crawler unit 74 that has read one of the target number ANtar changes its own state in the reporting timing determination table 340 to "active" and updates the update date and time.

[0056] Each crawler unit 74 accesses the data provision server 40 via the internet 50 and determines whether or not a target event Etar has occurred for the target number ANtar read from the request queue 72 (step S24). More specifically, each crawler unit 74 accesses the data provision server 40 using a URL (Uniform Resource Locator) stored in the storage unit 330. Then, it enters the target number ANtar on the history search screen of the data provision server 40 and obtains the data (patent data Dpat) from the history screen of the target number ANtar.

[0057] Then, the crawler unit 74 determines whether there is a text data in the history screen that has the same name as the target event Etar. If there are multiple target events Etar, the determination is made for the event with the highest priority. For example, if the target event Etar includes both a patent grant and a rejection decision, the patent grant is searched for first, and then the rejection decision is searched for. If there is a text data in the history screen that has the same name as the target event Etar, the crawler unit 74 determines that the target event Etar has occurred. If there is no text data in the history screen that has the same name as the target event Etar, the crawler unit 74 determines that the target event Etar has not occurred.

[0058] If it is determined that the target event Etar has occurred, each crawler unit 74 writes or copies the target number ANtar and the current status Scur to the rapid notification queue 76 (step S25). The current status Scur here refers to the name of the target event Etar if it has occurred, and to, for example, pending if the target event Etar has not occurred. Next, the rapid notification unit 704 reads one of the combinations of the target application number ANtar and the current status Scur that has been written or copied to the rapid notification queue 76, and deletes the read combination from the rapid notification queue 76 (step S26).

[0059] Next, the rapid notification unit 704 reads all user IDs corresponding to the target number ANtar read from the rapid notification queue 76 from the application table 342 (Figure 3B), and reads user information (user name and email address) corresponding to each read user ID from the user table 340 (Figure 3A) (step S27).

[0060] Next, the rapid notification unit 704 outputs a rapid notification command and rapid notification content to the first mail unit 78 (step S28). The rapid notification content includes a combination of the target application number ANtar, the current status Scur, the username, and the email address. Upon receiving the rapid notification command and rapid notification content, the first mail unit 78 generates and sends a rapid notification email based on the rapid notification content (step S29). The rapid notification email includes text data notifying that the current status Scur (one of the target events Etar) has occurred for the target application APNtar. The recipient of the rapid notification email is the email address included in the rapid notification content.

[0061] Returning to the description of each crawler unit 74, whether it is determined that the target event Etar has occurred or not, each crawler unit 74 writes or copies the target application number ANtar and the current status Scur to the normal reporting queue 80 (step S30). If it is determined that the target event Etar has occurred, step S30 is performed after step S25. After writing or copying to the normal reporting queue 80, the crawler unit 74 changes its status in the reporting timing determination table 340 from "active" to "standby", updates the update date and time, and then returns to step S23.

[0062] After step S30, the data update unit 702 of the overall management unit 70 reads one of the combinations of target application number ANtar and current status Scur that has been written to or copied to the normal reporting queue 80, and deletes the read combination from the normal reporting queue 80 (step S31). If the data update unit 702 detects that a combination of target number ANtar and current status Scur is stored in the normal reporting queue 80, it switches the status of the overall management unit 70 in the reporting timing determination table 340 to "active" and updates the update date and time.

[0063] Next, the data update unit 702 determines whether the combination of target number ANtar and current status Scur read from the normal reporting queue 80 differs from the combination of target application number ANtar and current status Scur stored in the application table 342 (step S32). If the combinations of target application number ANtar and current status Scur do not differ, the data update unit 702 updates only the update time in the application table 342. If the combinations of target application number ANtar and current status Scur differ, the data update unit 702 updates the current status and update time in the application table 342 for all records corresponding to target application number ANtar. After completing these processes, the data update unit 702 returns the status of the overall management unit 70 in the reporting timing determination table 340 to "standby". After that, the data update unit 702 continues to monitor whether the combination of target application number ANtar and current status Scur is stored in the normal reporting queue 80 (attempting to read in step S31).

[0064] The normal reporting unit 706 determines whether crawler processing has been performed for all target numbers ANtar written to the request queue 72, based on the current status and update date and time of each in the normal reporting timing determination table 340 (Figure 3C). Specifically, the normal reporting unit 706 determines at the third predetermined period whether all of the statuses in the normal reporting timing determination table 340 are "standby". If all of the statuses are "standby", the normal reporting unit 706 determines whether the update date and time of each status is more than a predetermined period before the current date and time. If all of the statuses are "standby" AND the update date and time of each status is more than a predetermined period before the current date and time, it determines that crawler processing has been performed for all target numbers ANtar written to the request queue 72.

[0065] If the crawler determines that crawler processing has been performed for all target application numbers ANtar stored in the request queue 72, the normal reporting unit 706 reads one of the user records (Figure 3A) contained in the user table 340 (step S33). The contents of the user record to be read include the user ID, username, and email address. The normal reporting unit 706 then searches the application table 342 (Figure 3B) for the application record corresponding to the read user ID, and reads all of the extracted application records whose report flag is 1 (report required).

[0066] In this case, if the current status of Scur is one that does not require further reporting (for example, patent granted), the report flag is changed from 1 (report required) to 0 (report not required). By doing this, it is possible to make the reporting of application number ANtar, which is in a status that does not require further reporting, the last time it is reported in this regular report, and it will not be included in future regular reports.

[0067] Next, the normal reporting unit 706 outputs a normal reporting command and normal reporting content to the user terminal 20 for the second mail unit 82 (step S34). The normal reporting content includes all of the target applications APNtar registered by the user (in other words, all of the target applications APNtar with the same user ID) for which the report flag is 1 (report required), the combination of their current status Scur, and the set of the user name and email address.

[0068] Upon receiving the normal reporting command and normal reporting content, the second mail unit 82 generates and transmits a normal reporting mail based on the normal reporting content (step S35). The normal reporting mail includes text data for notifying the current status Scur of each target application APNtar (only those with a report flag of 1 (report required)) to the person with the user name. Also, the destination of the normal reporting mail is the email address included in the normal reporting content. The express mail was transmitted for each one target application APNtar for which the target event Etar occurred. In contrast, the normal reporting mail is transmitted for each user and includes text data listing the current status Scur of all applications with a report flag of 1 among the target applications APNtar corresponding to a specific user ID.

[0069] The normal reporting unit 706 and the second mail unit 82 perform steps S33 to S34 for all user records included in the user table 340. The order at this time can be, for example, in ascending or descending order of the user ID. When the normal reporting unit 706 and the second mail unit 82 perform steps S33 to S34 for all user records included in the user table 340, the current crawler management process ends.

[0070] <A-3. Effects of the First Embodiment> According to the first embodiment described above, when the occurrence of the target event Etar is detected, this fact is immediately reported to the user terminal 20 (S25-S29 in Figure 5). Therefore, the user can immediately know that the target event Etar related to the target application number ANtar has occurred. Subsequently, the judgment results, including the target application APNtar for which the occurrence of the target event Etar was not detected, are notified to each user terminal 20 (or each user) in a condensed manner (S30-S35 in Figure 5). Therefore, the user can know the overall judgment results at this time. Thus, it is possible to improve user convenience.

[0071] In the first embodiment, when the crawler unit 74 (first monitoring unit) of the information processing server 30 detects the occurrence of a target event Etar on a specific day of the week, the calculation unit 320 (server-side control unit) promptly notifies the user terminal 20 of the occurrence of the target event Etar via the communication unit 310 (server-side communication unit) (S25-S29 in Figure 5), and then notifies each user terminal 20 of the determination results, including target application APNtars for which no occurrence of the target event Etar was detected (S30-S35 in Figure 5). Furthermore, when the crawler unit 74 detects the occurrence of a target event Etar on a day other than the specific day of the week, the calculation unit 320 promptly notifies the user terminal 20 of the occurrence of the target event Etar via the communication unit 210 (S25-S29 in Figure 5), while omitting the notification of the determination results, including target application APNtars for which no occurrence of the target event Etar was detected (S30-S35 in Figure 5). This makes it possible to avoid the inconvenience of receiving notifications of determination results that include target application APNtars for which no occurrence of the target event Etar was detected on days other than the specific day of the week, in cases where the occurrence of the target event Etar tends to be concentrated on certain days of the week.

[0072] In the first embodiment, the information processing DB 322 (search target database) includes an application table 342 (application information storage unit) that stores the current status Scur of the target application number ANtar and target application APNtar in association with the user ID (user identification information) (Figure 3B). The calculation unit 320 (server-side control unit) of the information processing server 30 extracts the target application number ANtar from the application table 342 in a manner that avoids duplication (S21 in Figure 5). The crawler unit 74 (monitoring unit) determines whether or not a target event Etar has occurred for each of the extracted target application APNtars (S24). Furthermore, when the crawler unit 74 detects the occurrence of a target event Etar, the calculation unit 320 promptly notifies each user associated with the target application APNtar on which the target event Etar occurred in the application table 342 (S25-S29). Furthermore, the calculation unit 320 determines whether or not the target event Etar has occurred for all target application numbers ANtar extracted from the application table 342, and then notifies each user terminal 20 (or each user) of the determination result (S30-S35).

[0073] This eliminates duplicate application numbers (ANtar), reducing the computational load and processing time required to determine whether or not the target event (Etar) has occurred, and enabling earlier notification of the determination results. Consequently, user convenience can be further improved.

[0074] In the above embodiment, the crawler unit 74 (monitoring unit) is a plurality of virtual servers set by the arithmetic unit 320 (server-side control unit) of the information processing server 30. Also, each crawler unit 74 as a plurality of virtual servers acquires the target application number ANtar for which it is responsible from the request queue 72 of the arithmetic unit 320, determines whether or not the target event Etar has occurred for the acquired target application number ANtar, and transmits the determination result to the overall management unit 70 (S25 and S30 in FIG. 5). By using the crawler units 74 as a plurality of virtual servers, it is possible to reduce the overall processing time and to notify the determination result earlier. Therefore, it is possible to further improve the convenience for the user.

[0075] B. Second Embodiment <B-1. Configuration of the Second Embodiment> [B-1-1. Overall Configuration] FIG. 6 is a block configuration diagram of an information processing server 30a of an information processing system 10A according to the second embodiment. The information processing system 10A of the second embodiment (hereinafter also referred to as "system 10A") basically has the same configuration as the information processing system 10 of the first embodiment. Among the components of the second embodiment, those that are the same as those of the first embodiment are denoted by the same reference numerals and detailed description thereof is omitted.

[0076] In the first embodiment, the user terminal 20 inputs the target application number ANtar and sends it to the information processing server 30. The information processing server 30 registers the received target application number ANtar in the application table 342 and then performs subsequent crawler processing. In contrast, in the second embodiment, the user terminal 20 inputs the name of the applicant to be monitored (hereinafter referred to as "target applicant APTtar") (hereinafter referred to as "target applicant name NAPTtar") and sends it to the information processing server 30a. The information processing server 30a accesses the data provision server 40 and searches for the target application number ANtar of the target applicant APTtar using the target applicant name NAPTtar as a keyword. The information processing server 30a then registers the searched target application number ANtar in the application table 342. At this time, the searched target application number ANtar is limited to those for which the target event Etar may occur in the future. In addition, the information processing server 30a registers the target applicant name NAPTtar itself in the information processing DB 322 (user table 340).

[0077] Furthermore, the information processing server 30a of the second embodiment evaluates the influence Di of the target application APNtar on the business of the target applicant APTtar and records it in the application table 342 together with the target application number ANtar.

[0078] [B-1-2. Information Processing Server 30a] As shown in Figure 6, the information processing server 30a has an input / output unit 300, a communication unit 310, a calculation unit 320a, and a storage unit 330. The calculation unit 320a has a user management unit 322, an application information management unit 324a, a crawler management unit 326, and a second crawler management unit 328.

[0079] The application information management unit 324a includes an application number search unit 360, a first evaluation unit 362, and a second evaluation unit 364. The application number search unit 360 accesses the data providing server 40 and searches for the target application number ANtar using the target applicant name NAPTtar received from the user terminal 20 as a keyword. The first evaluation unit 362 evaluates the degree of influence Di of the target application APNtar on the business of the target applicant APTtar. The searched target application number ANtar and its degree of influence Di are registered in the application table 342 together with the user ID. The second evaluation unit 364 determines the degree of coincidence Da between the content included in the target application APNtar after the occurrence of the target event Etar is detected and a new article on the Internet.

[0080] The second crawler management unit 328 (second monitoring unit) determines the presence or absence of new articles on the Internet for each of the applicants (target applicants APTtar) of the target application APNtar after the occurrence of the target event Etar (e.g., patent examination) is detected, at every second predetermined timing. The determination of the presence or absence of new articles by the second crawler management unit 328 may be limited to a predetermined period (e.g., 3 to 6 months) after the detection of the occurrence of the target event Etar.

[0081] <B-2. Control of the Second Embodiment><A [B-2-1. Overview] Similar to the information processing server 30 of the first embodiment, the information processing server 30a of the second embodiment executes user management control, application information management control, and crawler control. In addition, the information processing server 30a of the second embodiment executes second crawler control. The second crawler control is a control for determining the presence or absence of new articles on the Internet for each of the applicants (target applicants APTtar) of the target application APNtar after the occurrence of the target event Etar (e.g., patent examination) is detected, at every second predetermined timing.

[0082] [B-2-2. Application Information Management Control] The application information management control manages information (application information) related to the target application number ANtar. The application information management control includes application registration control for registering new target application numbers ANtar and application information update control for updating registered target application numbers ANtar, etc.

[0083] Figure 7 is a flowchart of the application registration control in the second embodiment. In the application registration control, the information processing server 30a (application information management unit 324a) sends data from the applicant name input screen to the user terminal 20 in response to a request from the user terminal 20 (step S51). The user terminal 20 displays the received data from the applicant name input screen and accepts input from the user for the name of a new target applicant APTtar (target applicant name NAPTtar). The user terminal 20 then sends the entered target applicant name NAPTtar and user ID to the information processing server 30a. The information processing server 30a receives the target applicant name NAPTtar from the user terminal 20 and stores it in the information processing DB 322 (user table 340) in association with the user ID (step S52).

[0084] Next, the application information management unit 324a accesses the data provision server 40 via the communication unit 310 and searches for currently pending patent applications of the target applicant APTtar as target applications APNtar using the target applicant name NAPTtar as a keyword (step S53). Then, the application information management unit 324 registers the application numbers of one or more of the found target applications APNtar as target application numbers ANtar, along with the user ID, as application records in the application table 342 (step S54). The search results may also be notified to the user terminal 20.

[0085] Next, the first evaluation unit 362 of the information processing server 30a calculates the influence Di of the target application APNtar on the business of the target applicant APTtar (step S55). Specifically, the first evaluation unit 362 searches the internet for articles via a search site using the target applicant name NAPTtar as a keyword (step S551). Next, the first evaluation unit 362 calculates the content relevance Dr between the invention content contained in the application documents (specification, etc.) of the target application APNtar and the internet articles (step S552). The content relevance Dr is a score indicating the degree of relevance between the content of the two. For example, the content relevance Dr can be calculated by using the degree of agreement between the text data in the application documents (specification, etc.) of the target application APNtar and the text data contained in the internet articles. In addition to or instead of this, the degree of agreement of the drawings may be used.

[0086] Next, the first evaluation unit 362 determines the influence level Di based on the content relevance level Dr. For example, if the content relevance level Dr is greater than or equal to the first threshold, the influence level Di is set to large; if the content relevance level Dr is less than the first threshold but greater than or equal to the second threshold, the influence level Di is set to medium; and if the content relevance level Dr is less than the second threshold, the influence level Di is set to small. The first evaluation unit 362 registers the determined influence level Di in the application record of the corresponding target application number ANtar in the application table 342 (step S56). At this time, the target application APNtar and the location (URL) of the internet article with a high content relevance level Dr may also be registered in the application record.

[0087] In the application information update control, the information processing server 30a sends data from the application information update screen to the user terminal 20 in response to a request from the user terminal 20. The user terminal 20 displays the received data from the application information update screen and accepts input of patent information (update information) from the user. The update information entered here may include the target applicant name NAPTtar. The user terminal 20 then sends the entered update information to the information processing server 30a. The information processing server 30a stores the update information received from the user terminal 20 in the information processing DB 322 (application table 342). If the update information includes the target applicant name NAPTtar, the target application number ANtar, influence level Di, etc., are identified and included in the application record, similar to the application registration control case.

[0088] [B-2-3. Crawler Control (First Crawler Control)] The crawler control in the second embodiment is basically the same as the crawler control in the first embodiment (Figures 4 and 5). However, the breaking news email (S29 in Figure 5) includes not only the fact that the current status Scur (one of the target events Etar) has occurred for the target application APNtar, but also the influence level Di of the target application APNtar. Furthermore, if the location (URL) of an internet article with a high content relevance Dr to the target application APNtar is registered as an application record in the application table 342, that location may also be included in the breaking news email.

[0089] Furthermore, in the crawler control of the second embodiment, it is determined whether there is a new application publication or something similar (for example, an application publication and re-publication in Japan) for the target applicant name NAPTtar. If a new application publication, etc. is detected, the application number of the new application publication, etc. is registered in the application table 342 along with the user ID as the target application number ANtar.

[0090] [B-2-4. Second Crawler Control] Figure 8 is a flowchart of the second crawler control in the second embodiment. As described above, the second crawler control is a control that determines, at second predetermined intervals, whether or not there are new articles (e.g., IR information) on the internet for each applicant (target applicant APTtar) of the target application APNtar after the occurrence of the target event Etar (e.g., patent grant) has been detected.

[0091] In step S61 of Figure 8, the information processing server 30 (second crawler management unit 328) determines whether or not to start the second crawler management process (in other words, whether or not the timing to start the second crawler management process has arrived). The start timing referred to here can be, for example, the timing immediately after a new article (IR information, etc.) is updated on the second data provision server (not shown) managed and operated by the corporate applicant APTtar (for example, 3 p.m. on a weekday). If the second crawler management process is to be started (S61: true), the process proceeds to step S62.

[0092] In step S62, the information processing server 30 executes the second crawler management process. The second crawler management process determines whether a new article has been generated for the applicant of the target application APNtar (target applicant APTtar) after the occurrence of the target event Etar has been detected. As shown in Figure 8, the second crawler management process includes a general management process (S621), a second crawler process (S622), a matching degree determination process (S623), and a notification process (S624).

[0093] The general management process (S621) manages the entire second crawler management process. The second crawler process (S622) determines, via data communication with the second data provision server, whether a new article has been generated for the target applicant APTtar of the target application APNtar after the occurrence of the target event Etar has been detected.

[0094] The consistency determination process (S623) determines the degree of consistency Da between the content included in the target application APNtar after the occurrence of the target event Etar is detected and a new article on the Internet. For example, it determines whether the patent application number or patent number included in the new article matches the application number or the corresponding patent number of the target application APNtar after the occurrence of the target event Etar is detected. Alternatively, the degree of consistency Da may be determined using the content relevance Dr in the same manner as the first evaluation unit 352.

[0095] The notification process (S624) is a process of notifying the user terminal 20 of the occurrence of a new article via the communication unit 210 when the degree of consistency Da indicates that the new article is related to the target application APNtar.

[0096] After the second crawler management process ends, the process returns to step S61.

[0097] <B-3. Effects of the Second Embodiment> According to the second embodiment as described above, in addition to or instead of the effects of the first embodiment, the following effects can be achieved.

[0098] In the second embodiment, the information (application number specifying information) input by the user includes the target applicant name NAPTtar (S52 in FIG. 7). Further, the information processing server 30a has an application number search unit 360 that searches for the target application number ANtar based on the target applicant name NAPTtar (FIG. 6). Thereby, the user can specify the target application number ANtar only by inputting the target applicant name NAPTtar.

[0099] In the second embodiment, the information processing server 30a includes a first evaluation unit 362 that evaluates the degree of influence Di of the target application APNtar on the business of the target applicant APTtar (Figure 6). The information processing DB 332 (search target database) also stores the degree of influence Di for each target application number ANtar (S56 in Figure 7). Furthermore, when the crawler management unit 326 (first monitoring unit) detects the occurrence of a target event Etar, the calculation unit 320a (server-side control unit) of the information processing server 30a immediately reports the occurrence of the target event Etar and its degree of influence Di to the user terminal 20 via the communication unit 310 (server-side communication unit) (see S29 in Figure 5). This makes it possible for the user to refer not only to the occurrence of a target event Etar related to the target application APNtar, but also to the degree of influence Di of the target application APNtar on the business of the target applicant APTtar.

[0100] In the second embodiment, the first evaluation unit 362 (Figure 6) searches the internet for articles about the target applicant APTtar (S551 in Figure 7), determines the content relevance Dr between the inventive content included in the target application APNtar and the internet articles (S552), and calculates the influence Di based on the content relevance Dr (S553). It is considered that the internet articles may contain content that is highly relevant to the business of the target applicant APTtar. Therefore, by using the influence Di based on the content relevance Dr between the inventive content included in the target application APNtar and the internet articles, it becomes possible to present a more accurate influence Di to the user.

[0101] In the second embodiment, the information processing server 30a includes a second crawler management unit 364 (second monitoring unit) that determines the presence or absence of new articles on the Internet at every second predetermined timing for each of the target applicants APTtar who are the applicants of the target application APNtar after the occurrence of the target event Etar, and a second evaluation unit 364 that determines the degree of coincidence Da between the content included in the target application APNtar after the occurrence of the target event Etar and the new articles (FIG. 6). Further, when the degree of coincidence Da indicates that the new article is related to the target application APNtar, the arithmetic unit 320a (server-side control unit) of the information processing server 30a notifies the user terminal 20 of the occurrence of the new article via the communication unit 310 (server-side communication unit) (S624 in FIG. 8). Thereby, for example, the user can know that an IR announcement regarding the patent examination has been made for the target application APNtar for which the patent examination as the target event Etar has been issued.

[0102] C. Modification Example Note that the present invention is not limited to the above-described embodiments, and it is needless to say that various configurations can be adopted based on the description in this specification. For example, the following configurations can be adopted.

[0103] <C-1. Configuration> In the information processing system 10 of the first embodiment, the information processing server 30 was configured as a single server (FIGS. 1 and 2). However, for example, from the viewpoint of executing crawler control (FIGS. 4 and 5), it is not limited to this. For example, the information processing server 30 may be configured from a plurality of servers (hardware). The same applies to the information providing server 40. The same also applies to the second embodiment.

[0104] In the second embodiment, the application number search unit 360 is provided in the information processing server 30a (FIG. 6). However, for example, from the viewpoint of specifying the target application number ANtar based on the target applicant name NAPTtar, it is not limited to this. The application number search unit 360 may be provided in the user terminal 20, for example.

[0105] In the second embodiment, the first evaluation unit 362 is provided in the information processing server 30a (FIG. 6). However, for example, from the perspective of evaluating the degree of influence Di that the target application APTtar has on the business of the target applicant APTtar, it is not limited to this. The first evaluation unit 362 may be provided in the user terminal 20, for example. The same applies to the second evaluation unit 364.

[0106] <C-2. Control> [C-2-1. Setting of target event Etar] In the first embodiment, the target event Etar detected by the crawler process (S122 in FIG. 4 and S24 in FIG. 5) is set on the information processing server 30 side and cannot be set by the user (S24 etc. in FIG. 5). However, for example, from the perspective of improving user convenience, it is not limited to this, and the user may be able to set the target event Etar for each target application APNtar. Such control can be realized as follows, for example.

[0107] That is, the information processing server 30 transmits the data of the screen for inputting the target application number ANtar to the user terminal 20 in response to a command from the user terminal 20. The user terminal 20 displays the screen based on the received data and accepts the input of the target application number ANtar from the user. At that time, the input of the target event Etar is also accepted for each target application number ANtar. The user terminal 20 transmits the input target application number ANtar and target event Etar to the information processing server 30. The information processing server 30 that has received these registers them in the application table 342 of the information processing DB 332.

[0108] When the current status Scur is changed as a result of the crawler process, the information processing server 30 compares the new current status Scur with the target event Etar, and if both match, notifies the user promptly. Also, in the normal report, the new current status Scur is reported. As a result, it becomes possible to select the target event Etar for each target application number ANtar. Therefore, it becomes possible to improve user convenience. The same applies to the second embodiment.

[0109] Alternatively, the input of the target event Etar may be set as a batch setting per user, rather than per target application number ANtar. In that case, as described above, the target event Etar may be registered for each target application number ANtar in the application table 342. Alternatively, since it is a setting per user, the target event Etar may be registered in the user table 340 and used there. In that case, when the current status Scur of the target application number ANtar changes, the target event Etar in the user record of the user table 340 corresponding to the user ID in the application table 342 may be read and used to determine whether the changed current status Scur matches the target event Etar. This makes it possible to select the target event Etar on a per-user basis. Therefore, it is possible to further improve user convenience. The second embodiment is similar.

[0110] [C-2-2. Determination of the occurrence of the target event Etar] In the first embodiment, the occurrence of the target event Etar was determined by checking whether or not there was a text data with the same name as the target event Etar in the history screen of the target application number ANtar (S24 in Figure 5). However, the occurrence of the target event Etar may be determined by other methods. For example, if the history screen of the target application number ANtar includes the dates of each event or various documents, it is also possible to determine the occurrence of the target event Etar based on the event name or document name corresponding to the most recent date.

[0111] [C-2-3. Execution timing of crawler management processing] In the first embodiment, the timing for starting or executing the crawler management process (S12 in Figure 4) was common to each target application APNtar recorded in the application table 342 (Figure 4). In other words, the user could not set the timing of the execution of the crawler management process. However, from the standpoint of improving user convenience, for example, the timing of the crawler management process could be set by the user, not limited to this. Such control can be realized, for example, as follows.

[0112] In other words, the information processing server 30 sends data for a screen that inputs the execution timing of the crawler management process to the user terminal 20 in response to a command from the user terminal 20. The user terminal 20 displays the screen based on the received data and accepts timing input from the user. The user terminal 20 sends the entered execution timing of the crawler management process to the information processing server 30. Upon receiving this, the information processing server 30 registers it in the execution timing table (not shown) of the information processing DB 332. However, if the execution timing is the same as one already registered, no new registration is made.

[0113] Each time an execution timing is registered and each time the crawler management process is executed, the information processing server 30 determines the most recent execution timing recorded in the execution timing table and stores it in memory. Then, when the most recent execution timing arrives, the information processing server 30 executes the crawler management process.

[0114] Furthermore, when a new execution timing is registered, the identifier of the execution timing is also recorded in the user table 340. The information processing server 30 then sends both a preliminary report and a regular report only to the user terminal 20 that has registered the current crawler management process as an execution timing. The crawler management process and the second crawler management process in the second embodiment are the same.

[0115] [C-2-4. Breaking News and Regular Reports] In the first embodiment, when the occurrence of a target event Etar was detected, a rapid notification was sent to the user terminal 20 (S25-S29 in Figure 5), and thereafter, the determination results for all target application APNtars that had been processed by the crawler were notified to the user terminal 20 (S30-S35). However, this is not limited to this, for example, if a rapid notification is sent only for target application APNtars in which a target event Etar was detected, and the others are reported together in a regular report.

[0116] For example, a regular report does not necessarily have to include the target application APNtar for which a preliminary report has been issued. Alternatively, from the perspective of issuing a preliminary report for the target application APNtar in which the target event Etar has been detected, a configuration or control that does not issue a regular report is also possible. The same applies to the second embodiment. Alternatively, for example, by focusing on the functions of the application number search unit 360 or the first evaluation unit 362 or the second evaluation unit 364 in the second embodiment, a configuration or control that performs only one of the preliminary report or the regular report, and does not perform the other, is also possible.

[0117] [C-2-5. Target application number ANtar] In the first embodiment, the occurrence of the target event Etar was detected for the target application number ANtar (S24 in Figure 5). However, this is not limited to the first embodiment, for example, from the standpoint of providing rapid or regular reports on the progress of the target event Etar using crawler processing. For example, in addition to or instead of the target application number ANtar, the target patent number (the target patent number) may be used. Alternatively, the number used here may not be related to a patent, but to another intellectual property right (design, trademark, etc.). Alternatively, the present invention can also be applied to applications other than intellectual property rights (for example, applications for approval of pharmaceuticals). The second embodiment is similar.

[0118] In the second embodiment, the applicant name NAPTtar was used as information that can identify the target application number ANtar (application number identification information) (Figure 7). However, this is not limited to the above, for example, from the perspective of providing rapid or regular reports on the progress of the target event Etar using crawler processing. For example, the target application number ANtar may be identified using the name of the technical field as the name of the technical field. Alternatively, the target application number ANtar may be identified using a patent classification code (International Patent Classification, etc.).

[0119] [C-2-6. Data storage in the information processing DB332] In the first embodiment, the information processing DB332 (application table 342) created an application record for each combination of the target application number ANtar and the user ID (Figure 3B). However, this is not the only way, for example, to create an application record by associating the target application number ANtar with the user ID. For example, it is also possible to generate a table for each user ID and store the target application number ANtar in each table. The second embodiment is similar. [Explanation of symbols]

[0120] 10, 10A... Information processing system 20... User terminal 30, 30a... Information processing server; 40... Data provision server 74...Crawler section (1st monitoring section) 200...Input / output section (Input section) 210...Communication unit (user-side communication unit) 220...Calculation unit (user-side control unit) 310...Communication unit (server-side communication unit) 320...Calculation unit (server-side control unit) 328...2nd Crawler Management Department (2nd Monitoring Department) 332... Information processing database (database to be searched) 342…Application Table (Application Information Storage Unit) 360...Application number search unit 362...First evaluation unit 364...2nd Evaluation Department ANtar...Target application number APNtar...Target application APTtar…Taree applicant Da…Degree of match Di...Influence Dr...Relevance to content NAPTtar…Target applicant name Scur…Current status Etar…Target Event

Claims

1. An information processing system having user terminals and an information processing server, The aforementioned user terminal is The user-side communication unit that transmits and receives information with the aforementioned information processing server, An input unit that accepts input of application number identification information or the said application number for identifying the target application that is the application to be searched, A user-side control unit that transmits the application number identification information or the target application number entered in the input unit, along with the user's identification information, to the information processing server via the user-side communication unit. Equipped with, The aforementioned information processing server is The server-side communication unit that sends and receives data with the user terminal, A search target database that stores the aforementioned application number identification information or the aforementioned target application number in association with the user's identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the target application or the application number identification information at a first predetermined timing, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit, Equipped with, The first monitoring unit is a plurality of virtual servers configured by the server-side control unit, The multiple virtual servers obtain the target application number they are responsible for from the server-side control unit, determine whether or not the target event has occurred for the obtained target application number, and transmit the determination result to the server-side control unit. When the first monitoring unit detects the occurrence of the target event, the server-side control unit promptly notifies the user terminal of the occurrence of the target event via the server-side communication unit, and then notifies each user terminal of the determination results, including the target application for which no target event was detected. An information processing system characterized by the following:

2. A server-side communication unit that receives application number identification information or the said application number from a user terminal to identify the target application number which is the application to be searched, A searchable database that stores the aforementioned application number identification information or the aforementioned target application number in association with user identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the target application or the application number identification information at a first predetermined timing, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit, An information processing server equipped with, The first monitoring unit is a plurality of virtual servers configured by the server-side control unit, The multiple virtual servers obtain the target application number they are responsible for from the server-side control unit, determine whether or not the target event has occurred for the obtained target application number, and transmit the determination result to the server-side control unit. When the first monitoring unit detects the occurrence of the target event, the server-side control unit promptly notifies the user terminal of the occurrence of the target event via the server-side communication unit, and then notifies each user terminal of the determination results, including the target application for which no target event was detected. An information processing server characterized by the following features.

3. An information processing method used in an information processing system having user terminals and an information processing server, The aforementioned user terminal is The user-side communication unit that transmits and receives information with the aforementioned information processing server, An input unit that accepts input of application number identification information or the said application number for identifying the target application that is the application to be searched, A user-side control unit that transmits the application number identification information or the target application number entered in the input unit, along with the user's identification information, to the information processing server via the user-side communication unit. Equipped with, The aforementioned information processing server is The server-side communication unit that sends and receives data with the user terminal, A search target database that stores the aforementioned application number identification information or the aforementioned target application number in association with the user's identification information, A first monitoring unit determines whether or not a target event, which is the event to be searched, has occurred for each of the target application or the application number identification information at a first predetermined timing, The server-side communication unit, the search target database, and the server-side control unit that controls the operation of the first monitoring unit, Equipped with, The first monitoring unit is a plurality of virtual servers configured by the server-side control unit, The multiple virtual servers obtain the target application number they are responsible for from the server-side control unit, determine whether or not the target event has occurred for the obtained target application number, and transmit the determination result to the server-side control unit. When the first monitoring unit detects the occurrence of the target event, the server-side control unit promptly notifies the user terminal of the occurrence of the target event via the server-side communication unit, and then notifies each user terminal of the determination results, including the target application for which no target event was detected. An information processing method characterized by the following:

Images