JP2001014248A - Information notifying device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make transmittable relevant data even to the source of a person in charge SE registered after the transmission of the relevant data about used system resources without the omission of the relevant data in the case of a system resource distributing, especially generated information to a person in charge SE utilizing the system resource without omission in the transmission of system resource information stored in a server. SOLUTION: This device is configured so as to notify a user of information. In such a case, the device is constructed with a storing means 1001 which makes information to be notified to the user correspond to a date and stores the information, a registering means 1002 which registers information on the notification starting date of the information about the user receiving the information notification, an extracting means 1003 which extracts the information after the corresponding date among the information stored by the means 1001 on the basis of the information on the date registered by the means 1002, and a notifying means 1004 which notifies the corresponding user of extracted information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the transmission of PUSH type information of system resources stored in a server, and more particularly, to a system resource information notifying apparatus for delivering generated information to an SE in charge of using system resources without fail.

[0002]

2. Description of the Related Art In a conventional PUSH type information transmission system, various information relating to system resources is registered in advance in a server of a management system together with a user name of the information, and new information relating to the information is registered in the server. At the time the server received the information, the server was simultaneously distributing the newly received information to the user.

[0006] Incidentally, the PUSH type information transmission system is a system resource name to be used, a scheduled operation date of the system resource, and the like, and a user name (SE; System E in charge) in advance.
ngineer, information processing technician)) and register the new information related to the system resource to the server at the time when the server is notified of the new information. It is a transmitting system.

FIG. 7 is an explanatory diagram of the whole system.
100 is a server installed at the center. In the server 100, a customer number 101, a database 102 of all available system resources, a management number and an e-mail address assigned to a SE in charge of designing and operating a system construction such as a customer site are registered together with the name of the SE in charge. An assigned SE registration list 103 and a system resource use list 104 in which system resource names used by the assigned SE are registered are stored.

A business unit 200 is a department for designing / manufacturing system resources, a support center 201 is a department for supporting a problem occurring in the business unit or at a customer, etc., and 202 is a business unit 200. And support center 2
It is a technical management section which is a section that supervises various technical information from 01 and the like.

Reference numerals 301 to 303 denote SEs in charge of customers, and the server 100 and each SE (3
01, 302, and 303), for example, exchange information via the Internet, while the business unit 200 and the support center 2
01, the technology management unit 202, etc., on the Internet or LA
Information is exchanged at N (Local Area Network) or the like.

The above SE (301, 302, 30)
Details of the registration list 103, the system resource use list 104, the system resource database 102, and the like in which 3) is registered are described in FIG. 4, but the description will be given later.

FIG. 8 is a flowchart of a conventional transmission process.

Step R1: The server 100 is in the business unit 20
0 (FIG. 7) and the like are received via a LAN or the like.

The related data 50 includes a product name, a product code, a date of occurrence, and a text describing details of the data (for example, troubleshooting).

Step R2: The product code in the related data 50 is set as a key, and the TBL-A 20 (FIG. 7; corresponding to the system resource use list 104) is searched. If a matching product code is detected, the management number of the corresponding SE in charge is acquired.

Step R3: Next, this management number is set as a key, and the TBL-B10 (FIG. 7; corresponding to the registration list 103 in which the SE in charge of designing and operating the system construction such as the customer site) is registered is searched. . If a matching management number is detected, a mail list 79 for each management number is created.

Step R4: Finally, the related data 50 is transmitted to the SE in charge of the created list destination.

[0014]

However, the conventional processing procedure described above has the following disadvantages.

FIG. 9 is a diagram for explaining the consistency between the conventional registration time and the transmission time. In FIG. 9, reference numeral 24 denotes an instant transmission time chart, and t1 to t7 denote dates.

As shown in the figure, for example, it is assumed that SEs (1, 2, 3) in charge of system construction at each customer use the same system resources (for example, zzz software), and SE1 is connected to the Internet at t1. SE2 registers the scheduled operation date as t6, and SE2 registers the scheduled operation date as t4 via the Internet at t2.
No. 3 registered at t5 via the Internet with the scheduled operation date as t7.

When the registration date and the scheduled operation date are as described above, the upgrade information on the zzz software is transmitted from the business unit 200 (FIG. 7) at the timing of t3 to the related data 50 (product code, date of occurrence, text; The mail shown in Fig. 8) has been notified.

Therefore, according to the conventional transmission processing flow chart of FIG. 8 described above, the mail is immediately transmitted to the SE in charge using the resource on the mail reception date, and the related data 50 is not retransmitted. System resource database 1
Perform only 02.

Since the responsible SE1 and the responsible SE2 have already been registered at the timings t1 and t2, the relevant data 50 can be received and the scheduled operation dates t4 and t6.
In time.

However, for the SE3 in charge, the registration date is t
5, which is after the mail transmission date t3, the related data 50 cannot be automatically received from the server 100. Therefore, the SE 3 in charge must search the system resource database 102 in the server 100 during the period from t5 at the time of registration to t7 at the scheduled operation date. It is.

On the other hand, another problem may occur for the assigned SE1. That is, the reception date t of the related data 50
If the period from 3 to the scheduled operation date t6 is a long time, the related data 50 received during that time may be lost. If the receipt record remains, it is possible to request the server 100 to resend it again, but this guarantee is not sufficient.

In view of such a point, the present invention ensures that the above-mentioned related data is transmitted without fail to the registered SE registered after the transmission of the related data relating to the used system resources. It is an object to provide means.

[0023]

The above-mentioned object is achieved by the present invention having the following construction.

FIG. 1 is a block diagram of the principle according to claim 1 of the present invention.

A storage unit 1001 for storing information to be notified to a user in association with a date, a registration unit 1002 for registering information on a notification start date of a user who receives a notification of information, Based on the information on the registered date, extracting means 1003 for extracting information from the information stored in the storage means on or after the relevant date, and notifying means 1004 for notifying the user of the extracted information. It comprises.

[0026]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the drawings.

FIG. 2 is an explanatory diagram of the system configuration of the present invention.

As shown in the figure, the system construction (and / or
Alternatively, the present invention is applied to a server that accumulates system resources used for operation and transmits information about the system resources to users of registered system resources.

A registration unit 1 for a user who uses the system resources, and a registration unit for a system resource for registering a system resource name to which date information has been added and notified by a user registered in the registration unit for the user 2, a search / extraction unit 3 for setting a date and collecting a system resource name provided with date information to be matched with the date, and a system resource name having the same date information collected by the search / extraction unit A system resource storage unit 4 for storing additional information relating to system resources stored in the system resource information notifying device; a system resource storage unit having the same date information; Collating means 6 for collating the system resource names stored in each of the information accumulating units, and a system resource collated by the collating means, And editing means 7 for editing as transmission information to the user registered, comprises means 8 for transmitting transmission information wherein the editing means creates the user.

FIG. 3 is a diagram for explaining the consistency between the registration time and the transmission time according to the present invention. In the drawing, reference numeral 25 denotes a transmission time chart corresponding to a scheduled date, and t1 to t33 indicate dates.

Here, the registration date (t1, t2, t5) of the assigned SE (1, 2, 3), the type of system resource to be used (zzz software), and the assigned SE (1, 2, 2, 3)
The scheduled operation dates (t6, t4, t7) of the system resources to be used by 3) are all the same as those used in FIG. 9 described in the related art for convenience of explanation. It is also the same that the upgrade information on the zzz software is notified by the business unit 200 of the related data 50 (FIG. 8) at the timing of t3 between the registration date and the scheduled operation date.

Here, in the case of the present invention, each assigned SE (1,
The transmission date is shifted to 2, 3).

That is, the assigned SE2 scheduled to operate at t4
Is transmitted at the timing of t31, and is transmitted at the timing of t32 to the assigned SE1 scheduled to operate at the timing of t6.
Is transmitted at the timing of t33 to the responsible SE3 scheduled to operate at the timing of t33.

This timing is calculated, for example, by standardizing one month before each scheduled operation date, so that the server automatically sends the system resources to the SE3 in charge registered after the mail reception date. Related data can be transmitted.

First, the format of the table used will be described.

FIG. 4 is a detailed explanatory diagram of various tables.
0 is a table in which SEs in charge of customers are registered (TBL-B)
As shown in FIG.
(Fujikawa, Yamada, etc.) are individually assigned management numbers (000
1,0002,. . . ), And a mail address (fuji @ tokyo, yama @) of the Internet or the like.
tokyo,. . . Etc.) and contact information such as telephones are registered.

Reference numeral 20 denotes a table (TBL-A) in which the customer installation system resources are registered, and the assigned SE (Fujikawa, Yamada,..., Etc.) has an individual management number (0001, 0).
002,. . . The name of the system resource (product code, product name, action time, etc.) to be used for each is registered. For example, Fujikawa (management number: 0001) of the SE in charge registers two types of system resources (zzz software with product code S0010 and yyy control with product code S0020) as scheduled operation dates of December 10, 1999, respectively. ing.

Reference numeral 51 denotes related data for each system resource, and at the same time, a copy of transmission to each assigned SE. That is, a mail is transmitted from the business unit 200 or the like in the format of “expiration date, product code, title, text” for each individual resource.

Reference numeral 70 denotes a transmission file to each SE in charge. A header 70-1 describes a management number, a name, a mail address, and the like, and a body 70-2 describes a product code, a title, a body, and the like. .

Reference numeral 30 denotes a list of products which have been notified from the SE in charge that the scheduled operation dates are the same.

FIG. 5 is an explanatory diagram of the functional configuration of the embodiment of the present invention.

In the figure, 31 is a date management unit, 32 is calendar data, 33 is a timer, 72 is a transmission data editing unit, 71 is a transmission file creation unit, 81 is a transmission unit, and 82 is a reception unit. The reference numerals used in the figures indicate the same items.

The use system resource data requested to be registered by the responsible SE via the receiving unit 82 is registered in the TBL-A 20, and the responsible SE information determined by the responsible customer is stored in the TBL-B.
10 and the relevant data of the system resources from the business unit 200 and the like are registered in the TBL-C51.

The date management unit 31 reads out the date of the current day of the running server from the built-in timer 33, and
2 is read out, and the date one month after that day is calculated.

Using the calculated date as a key, TBL-A20
Then, a product list 30 is generated by searching for an item whose action time (scheduled operation date) matches the calculated date, extracting corresponding information (management number, product code, etc.).

Next, the transmission file creation unit 71 sets the TBL-
B10 is accessed to read the management number, name, mail address, etc., and generate the header 70-1 of the transmission file 70 for each management number.

Subsequently, the transmission data editing section 72 reads the product code from the product list 30 and accesses the TBL-C 51 using the product code as a key. If there is a matching product code, the corresponding information (expiration date, product code, title, text, etc.) is extracted, and the transmission file creation unit 71 generates the body 70-2 of the transmission file 70 that has been generated in advance. I do.

The generated transmission file 70 is transmitted by the transmission unit 81 to the SE in charge based on the mail address.

In the above configuration, the related data is transmitted a predetermined number of days before the scheduled operation date of the system resource on the responsible SE side. However, the same-day transmission that has been conventionally performed can be used together.

FIG. 6 is a flow chart of the instant transmission process of the present invention. Step S1: The related data 50 is transmitted from the business unit 200 or the like.
It is received in a mail format via a LAN or the like.

Step S2: The received mail is sent to TBL-
Store it in C51.

Step S3: T using product code as a key
The BL-A 20 is searched to obtain the management number of the assigned SE.

Step S4: TBL-B using this management number
10 to generate a header 70-1 of the transmission file 70 for each management number.

Step S5: TBL to SE corresponding to management number
-Generate and transmit a mail with the content of C51 as the body 70-2.

A program for processing the functions of the embodiment shown in FIG. 5 and a procedure program and data for executing the flowchart shown in FIG. 6 are externally provided, that is, via a line or a portable medium such as a floppy disk. Or a CD-ROM, MO, or the like.

FIG. 10 is an explanatory diagram for loading the computer program and data into the processing device. In the figure, reference numeral 900 denotes a processing device; 901, a display provided in the processing device; 903, a driver for reading a computer program recorded on a portable medium;
Denotes a memory of the processing device 900, 904 denotes a portable medium such as a floppy disk or a CD-ROM, 905 denotes another device which is a provider of the computer program, and 906 denotes a line.

As shown in the figure, when the computer program is provided from another device 905 connected online such as a network, the computer program is installed in the processing device 900 via the line 906 and then loaded into the memory 902. Executed. When the portable medium 904 is provided directly on the portable medium 904, the portable medium 904 is set in the driver 903 and installed in the processing device 900, and then loaded into the memory 902 and executed.

[0058]

The effects of the present invention having the configuration described in detail above are as follows: 1) There is no restriction on the registration time of the assigned SE, and the scheduled operation date of the system resource notified by the assigned SE is as follows. Until a predetermined date, related data generated in the business department or the like can always be received.

2) Since the registration table of the system resource information used by the assigned SE and the action (scheduled operation date) time is different from the registration table of the assigned SE, the assigned S
Even when E is changed, it can be easily dealt with. That is, even if the SE in charge of the design is replaced by another SE in the middle of the project, and the SE in charge is newly registered, the reception of the related data can be completely prevented.

3) A plurality of e-mail addresses can be managed by registering the responsible SE, and even when the responsible SE moves from one work place to another, the relevant data can be received at the destination.

4) Since the transmission file is generated and transmitted for each SE in charge, the same related data is not transmitted to the same SE in charge a plurality of times.

5) By using the immediate transmission procedure and the transmission procedure according to the scheduled operation date, reception of related data can be flexibly operated. It has a special effect.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the principle of the present invention.

FIG. 2 is a system configuration diagram of the present invention.

FIG. 3 is an explanatory diagram of consistency between a registration time and a transmission time according to the present invention.

FIG. 4 is a detailed explanatory diagram of various tables.

FIG. 5 is an explanatory diagram of a functional configuration of an embodiment of the present invention.

FIG. 6 is a processing flowchart of immediate transmission according to the present invention.

FIG. 7 is an explanatory diagram of the entire system.

FIG. 8 is a flowchart of a conventional transmission process.

FIG. 9 is an explanatory diagram of consistency between a conventional registration time and a transmission time.

FIG. 10 is an explanatory diagram for loading a program into a processing device.

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 user registration unit 2 registration unit for use system resources with date information 3 search / extraction means using date information as key 4 system resource storage unit for same date information 5 storage unit for related information 6 collation means 7 editing means 8 transmission Means 10 TBL-B 20 TBL-A 24 Immediate transmission time chart 25 Expected date corresponding transmission time chart 30 Product list 31 Date management section 32 Calendar data 33 Timer 50 Related data 51 TBL-C 70 Transmission file 71 Transmission file creation section 72 Transmission Data editing unit 79 Mail list 81 Transmission unit 82 Receiving unit 100 Server 101 Customer information 102 System resource database 103 SE registration list in charge 104 System resource list 200 Business unit 201 Support center 202 Technology management unit 301, 302, 303 SE 900 in charge Processing unit 901 Display 902 Memory 903 Driver 904 Portable medium 905 Other device 906 Line 1001 Storage unit 1002 Registration unit 1003 Extraction unit 1004 Notification unit

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B042 JJ19 JJ27 KK13 LA08 5B075 PQ05 UU24 5B089 GA11 GA21 GB02 HA10 JA40 JB22 KA04 KB06 KB11 KC36 KC53 5K030 KA02 KA07 LD13 9A001 DD10 FF03 JJ14

Claims (4)

[Claims] 1. An information notification device for notifying a user of information, a storage means for storing information to be notified to a user in association with a date, and an information notification start date for a user who receives the information notification. Registering means for registering information about, and information extracting means for extracting information from the information stored in the storage means on or after a corresponding date, based on the information on the date registered by the registering means, An information notification device, comprising: a notification unit that notifies information to a corresponding user. 2. The method according to claim 1, wherein the information on the notification start date of the information to be registered by the registration unit is an operation start date, and the extraction unit determines the information required for the operation based on a date that is a predetermined period before the operation start date. The information notification device according to claim 1, wherein the information is extracted. 3. The information notification device according to claim 1, wherein the storage unit assigns an expiration date to the information to be notified to the user, and the extraction unit extracts information within the expiration date. 4. A computer-readable storage medium storing a program for notifying a user of information, a storage unit for storing information to be notified to a user in association with a date, and receiving the notification of information. A registration unit for registering information on a notification start date of the information about the user; and, based on the information on the date registered by the registration unit, information stored in the storage unit after the corresponding date. A computer-readable storage medium storing a program for causing an extracting unit to extract and a notifying unit for notifying a corresponding user of the extracted information.