JP4843470B2 - User information distribution apparatus, program, user information distribution system, and user information distribution method - Google Patents

Description

  The present invention relates to a user information distribution apparatus, a program, a user information distribution system, and a user information distribution method to which a plurality of application execution apparatuses that execute respective application programs are connected.

  Due to the frequent occurrence of information security accidents and the strengthening of laws and regulations, there is a need for a system that strengthens security by linking security systems of people, goods, and information alone.

  However, each application manages its own user information. For this reason, for example, in applications such as entry / exit management and PC login management, personnel changes (new employees, retired employees, department When (change) occurs, it is necessary to newly register, delete, and change user information for each application. Such operation is inefficient and labor intensive, and the burden on the operation manager is greater for users who perform large-scale personnel changes.

Conventionally, the client retrieves the failure information and the latest information held by the application vendor and acquires the correction module that has been applied to the application failure of the client, or the application vendor distributes the latest correction module to the client and the client There is known an application maintenance system and method for reducing the trouble of information retrieval and making it easy to grasp the latest failure information and client correction information (see, for example, Patent Document 1).
Japanese Patent Laying-Open No. 2003-177921 (paragraph “0008”, FIG. 1)

  According to the technique disclosed in Patent Document 1 described above, the application vendor manages the version information of the correction module used by the client in an integrated manner, thereby reducing the time and effort of the application manager of the client when acquiring the correction module. Can do. However, the client needs to monitor application failures and correction information that are periodically transmitted from the application vendor, and requires time and effort to obtain the latest correction module as appropriate.

  In addition, in the above-described security system, when new registration, deletion, or change of user information is performed for each application when a person change occurs, there is a possibility that a difference occurs in user information managed by each application. It becomes high and reliability deteriorates. In addition, when the application is expanded, such as adding an entry / exit management server, user information for the target personnel is newly registered, which increases man-hours.

  The present invention has been made to solve the above-described problems, and in applications that use information that is updated regularly or irregularly, such as user information, changes necessary for each application every time user information is updated. User information distribution device, program, and usage to improve the reliability of user information and reduce the man-hours for application expansion by building a mechanism to automatically distribute the user information to the required application It is an object to provide a person information distribution system and a user information distribution method.

In order to solve the above-described problems, the user information distribution apparatus of the present invention acquires user information that is updated regularly or irregularly, and updates the user information acquisition unit that stores the user information in the storage device and each application program. Information that searches the storage device with reference to a distribution condition table in which conditions for distributing the user information set in advance are registered, extracts the corresponding user information, and distributes it to the application execution device to be distributed A distribution unit ,
The user information acquisition unit acquires user information provided by a file or function and stores it in a storage device. When the acquired user information does not exist in the storage device, it is added as data and updated. When the acquired user information exists, the data is updated and the update date / time is set, and the user information that matches the deletion condition preset in the deletion condition table is already stored in the storage device. In this case, the data is extracted from the corresponding data, the items other than the user ID as a key item are deleted, the data is updated, and the deletion date and time is set for the data to be deleted.

  According to the present invention, in an application that uses information that is regularly or irregularly updated, such as user information, the user information that is necessary for each application is automatically updated to the necessary application each time the user information is updated. By constructing a distribution mechanism, the reliability of user information can be improved, and the number of man-hours for application expansion can be reduced.

  FIG. 1 is a diagram showing an example of a system configuration of a user information distribution system according to an embodiment of the present invention. As shown in FIG. 1, the user information distribution system according to the embodiment of the present invention acquires a plurality of application execution apparatuses 1 that execute respective application programs using user information, and user information. An external system 2 such as LDAP (Lightweight Directory Access Protocol), a user information distribution device 3 that distributes necessary information among the above-described user information to the necessary application execution device 1, and objects such as user information And a DB server (storage device) 4 to be managed. DB is an abbreviation for Data Base.

  The application execution apparatus 1 executes a security application program that performs entry / exit management, login management, and the like based on user attribute information such as finger vein authentication, RFID (Radio Frequency Identifier) chip, and IC card.

  The external system 2 is, for example, LDAP, which is a protocol for accessing a directory (database) using a TCP / IP (Transmission Control Protocol / Internet Protocol) protocol such as the Internet or an intranet. Information can be searched. Instead of using LDAP, a text file by CSV (Comma Separated Values) or the like may be obtained from an in-house user information management system or the like.

  As will be described later, the user information distribution apparatus 3 acquires user information that is updated regularly or irregularly, stores it in the DB server 4, and distributes the updated user information for each application program. The DB server 4 is searched with reference to a distribution condition table which will be set and registered in advance, and corresponding user information is extracted and distributed to the application execution apparatus 1 to be distributed.

  Each of the application execution device 1, the external system 2, the user information distribution device 3, and the DB server 4 is connected via a communication network such as a LAN (Local Area Network) 5. Here, the LAN 5 is used as the communication network, but the connection is not limited to the LAN and may be replaced by a WAN (Wide Area Network).

  FIG. 2 is a functional configuration diagram of the user information distribution apparatus 3 according to the embodiment of the present invention. As shown in FIG. 2, the user information distribution apparatus 3 according to the embodiment of the present invention includes a user information acquisition unit 31, a distribution condition registration unit 32, a user information distribution unit 33, and an interface unit 34. The deletion condition registration unit 35 is configured. In FIG. 2, blocks denoted by the same reference numerals as those in FIG. 1 have the same names and functions as those shown in FIG.

  The user information acquisition unit 31 has a function of acquiring user information updated regularly or irregularly and storing it in the DB server 4. When the user information acquisition unit 31 acquires user information provided by a file or a function and transfers it to the DB server 4, the user information acquisition unit 31 deletes user information that matches a deletion condition (deletion condition table 310) specified in advance. The date / time of processing is added, and if the acquired user information does not exist in the DB server 4, the added date / time is added to the user information. Details will be described later.

  The distribution condition registration unit 32 has a function of registering the extraction condition of the user information 41 for distribution to each application execution device 1, and the deletion condition registration unit 35 is for distribution to each application execution device 1. It has a function of registering deletion conditions for user information 41. As a result, only user information required by the application execution apparatus 1 can be extracted, and user information to be added to or deleted from the application execution apparatus 1 can be extracted by changing the extraction condition. Here, the distribution condition table 320 is stored in a storage device (not shown) built in the distribution condition registration unit 32, and the deletion condition table 310 is stored in a storage device (not shown) built in the deletion condition registration unit 35. Stored.

  The user information distribution unit 33 searches the DB server 4 with reference to the distribution condition table 320 in which conditions for distributing user information updated for each application program are registered in advance, and retrieves the corresponding user information 41. It has a function of extracting and distributing to the application execution apparatus 1 to be distributed. Further, the user information distribution unit 33, for the distribution status returned from each application execution device 1 as a result of distributing the user information, for each information (ID) indicating the user of the distributed user information, a DB server 4 is set in the distribution state management table 42 allocated and stored in advance, and has a function of updating the data item of “last delivery date” set in the delivery condition table 320 with the delivery date.

  When distributing user information from the DB server 4 to the application execution apparatus 1, the interface unit 34 controls the interface function when adding, updating, and deleting user information, and is designated by an application created by the user. It becomes a data transfer path for distribution to the executed application execution apparatus 1.

  The DB server 4 stores at least “name”, “ID”, “affiliation”, “job title”, etc. in the storage area of the DB server 4 as shown in FIG. At least a user information 41 composed of the data items and a distribution status management table 42 indicating a distribution status of the user information 41 are allocated and stored. User information 41 is defined as an object by user input. The data structure of the distribution status management table 42 will be described later.

  FIG. 3 is a flowchart cited for explaining the operation of the user information distribution apparatus of the present invention. Here, only the operation of the user information acquisition unit 31 is extracted and shown.

  For example, the user information acquisition unit 31 acquires user information provided from the external system 2 that manages employee information, and adds, updates, and deletes the contents of the user information 41 stored in the DB server 4. Have Specifically, as shown in the flowchart of FIG. 3, when the user information acquisition unit 31 is activated from the inside (S301, internal), first, user information provided in a CSV file (in accordance with user input) ( The definition content of the (capture information) and the condition for deleting the data of the user information 41 are set (S302). The conditions set here are set and stored in the deletion condition table 310.

  Subsequently, user information (CSV file) to be imported from the external system 2 is designated, and the user information acquisition unit 31 reads the designated user information 41 (CSV file) (S303). Then, the read CSV file for the change is compared with the contents set in the deletion condition table 310 (S304). If they match, the deletion data (S304, = and S305) is added. The contents of the user information 41 in the DB server 4 are updated as update data (S304, ≠ and S306).

  On the other hand, when the user information acquisition unit 31 is activated from the outside (S301, external), a function for adding, updating, or deleting user information is called to capture the changed user information. (S307 to S310). The function call is based on an application created by the user.

  Thereafter, the user information acquisition unit 31 reads the user information (CSV file) designated from the external system 2 (S303), and the read CSV file for the change and the contents set in the deletion condition table 310 are read. (S304, ≠, S305), if it does not match, the content of the user information 41 in the DB server 4 is updated as addition or update data if it does not match (S304, ≠, and S306).

  FIG. 4 is an operation conceptual diagram for explaining a user information acquisition operation by the user information acquisition unit. Here, (a) user information before the change, (b) user information updated on May 21, 2006, (c) the contents of the deletion condition table 310, (d) after being captured ( User information after change) is shown.

  As described above, the user information acquisition unit 31 has a function of taking in user information provided by a CSV file or a function and registering it in the DB server 4. Specifically, as shown in FIG. 4, the user information 41 that matches the content set in the deletion condition table 320 at the timing of registering the user information is “update date” and “delete date”. The date and time of processing is set, and information other than the ID as a key item is returned to the initial value. In addition, when it does not exist in the user information 41, it is set as additional data, and when it exists, it is set as update data. Here, for addition and update, only the update date and time is set as the date and time of processing. However, as a premise, the deletion conditions (here, when the affiliation is “retirement” and the work location is “XX”) are set in the deletion condition table 320 in advance, and the user information data item It is assumed that the items “update date and time” and “deletion date and time” are added.

  Specifically, as shown in FIG. 4D, Mr. A has been changed from the chief to the section manager, and Mr. B has been deleted because he retired. Mr. C has no change. The corresponding item in the rows of Mr. A and Mr. B in the user information 41 is updated at 5:00 on May 21, 2006. Further, the corresponding item in the row of Mr. B in the user information 41 is deleted at 5:00 on May 21, 2006. In the figure, 2006/05/21 05:00 means May 21, 2006, 5:00.

  FIG. 5 is a flowchart for explaining the operation of the user information distribution apparatus of the present invention. Here, only the operation of the user information distribution unit 33 is extracted and shown. The user information distribution unit 33 provides a function of distributing user information necessary for an application based on the contents of the defined distribution condition table 320. In the distribution condition table 320, information related to an application for distributing the user information 41 and distribution conditions are set.

  Specifically, as shown in the flowchart of FIG. 5, when the user information distribution unit 33 is activated from the inside (inside S501), first, the distribution condition table 320 includes “application name” and “IP address”. , “Delivery condition”, “Last update date and time” data items are set (S502), and for the specified application (S503, Yes), the distribution condition table 320, the specified extraction start date, Based on the distribution status management table 42, target user information is extracted from the user information 41 stored in the DB server 4 (S504), and an interface for adding / updating / deleting data created by the user The part 34 is called and distributed to the designated application execution apparatus 1 (S505). As a result of distributing the user information 41 as described above, the distribution status returned from each application execution device 1 (S506, Yes) is set in the distribution status management table 42 allocated and stored in the DB server 4. (S507). In S503, when a distribution application is not designated (S503, No), the user information distribution unit 33 enters a process waiting state. Similarly, if no response is returned from the application execution apparatus 1 in S506 (S506, No), the user information distribution unit 33 enters a process waiting state.

  On the other hand, when the user information distribution unit 33 is activated from the outside (S501, external), information on the application for distributing the user information 41 and distribution conditions are set (S508), and the user information 41 is distributed from the outside. Provides a function to perform startup. Here, a user creates an application that calls a function. When the above-mentioned function is called (S509, Yes), it is stored in the DB server 4 for the specified application based on the distribution condition table 320, the specified extraction start date, and the distribution state management table 42. The target user information is extracted from the user information 41 (S504), and the interface unit 34 for data addition / update / deletion is called and distributed to the designated application execution device 1 (S505). The same applies to the update management of the delivery status management table 42 after waiting for a delivery status reply (S506, Yes) from the application execution device 1 (S507). In S509, when the above-described function is not called (S509, No), the user information distribution unit 33 enters a process waiting state.

  Here, the interface unit 34 for data addition / update / deletion is an interface through which the user information distribution unit 33 distributes the extracted information to the application execution apparatus 1. Here, only the interface is defined so that the application can exchange data in an arbitrary format, and coding is performed for each application. The distribution status management table 42 is used to manage the distribution status of the user information 41 indicating who distributed to which application and when (or distribution was canceled).

  FIG. 6 is an operation conceptual diagram for explaining the user information distribution operation by the user information distribution unit. Here, (a) user information 41, (b) distribution status management table 42, (c) distribution condition table 320, and (d) entry / exit management application (application execution apparatus 1) are shown. . As described above, the user information acquisition unit 31 converts the user information 41 stored in the DB server 4 into an application execution device according to the distribution condition (distribution condition table 320) and the distribution state (distribution state management table 42). The function to deliver to 1 is provided. As an example of the application execution apparatus 1, application of entry / exit management (finger) using a finger vein, entry / exit management (μ) using a μ chip, and entry / exit management (IC) using an IC card are shown.

  Specifically, as shown in FIG. 6, the user information distribution unit 33 creates a DB based on the distribution condition table 320, the specified extraction start date, and the distribution state management table 42 for the specified application. The target user information is extracted from the user information 41 stored in the server 4, and the specified application execution is performed by calling the interface unit 34 for data addition / update / deletion created (coded) by the user. Deliver to the device 1.

  Then, at the timing when the distribution result is received from the application execution device 1, the distribution status for each user is set in the distribution status management table 42, and the “final distribution date” in the distribution condition table 320 is updated with the date when the processing is started. In addition, when a user is added to an application, who is distributed to which application is added to the distribution status management table 42. When updated, only the distribution status is changed.

  FIG. 7 shows operations during operation of the user information distribution apparatus (first-time user information distribution, user information distribution when user information is changed, and user information distribution when distribution conditions are changed). Is a flowchart showing an operation from registration of user information to distribution for each.

  FIG. 8 and FIG. 9 are operation explanatory diagrams for the first-time user information distribution. 10 to 15 are operation explanatory diagrams regarding user information distribution when the user information is changed. 16 to 18 are diagrams for explaining the operation of user information distribution when the distribution conditions are changed. 8 to 18, the blocks denoted by the same reference numerals as the blocks illustrated in FIGS. 1 and 2 are the same as the blocks having the same name and function as those illustrated in FIGS. 1 and 2.

  Hereinafter, the operation of the user information distribution apparatus according to the embodiment of the present invention shown in FIGS. 1 and 2 will be described in detail with reference to FIGS.

  When the user information distribution device (user information distribution unit 33) distributes the user information for the first time (S701, new), as shown in FIG. The distribution condition table 320 is set and registered (S702). Here, since the distribution status management table 42 is the first distribution (new) of user information, only a storage area is allocated to the DB server 4, and blank data is set here.

  Next, as shown in FIG. 9, the user information distribution unit 33 follows the contents set and registered in the distribution condition table 320, and the application that becomes the distribution destination of the user information not registered in the distribution state management table 42. It is distributed to the execution apparatus 1 (here, referred to as A system that performs entry / exit management by finger vein authentication) (S703). At the same time, “information (ID) indicating the user of the distributed user information”, “distribution destination”, and “distribution status” are added to the distribution status management table 42, and the distribution date and time are updated (S704). .

  Specifically, as shown in FIG. 9, in the delivery conditions of the A system set in the delivery condition table 320, the job title is a section manager or higher. The user information distribution apparatus 3 distributes the user information of “Hitachi Taro”, “Hitachi Jiro”, and “Hitachi Saburo”, who are section managers or higher, to the A system of the application execution apparatus 1 that is the distribution destination. In the distribution status management table 42, an ID (1001, 1002, 1003), a distribution destination (A system), and a distribution status (distributed) are added. The final delivery date is June 11, 2006, 00:00.

  On the other hand, when the user information is changed (S701, change), the user information distribution unit 33, as indicated by a thick frame in FIG. 10, the last update date and time set in the distribution condition table 320 User information after (previous delivery date and time) is extracted (S705).

  Then, as shown in FIG. 11, the user information distribution unit 33 selects “not less than the section manager” from the target user information 41 (thick frame in the figure) that is not registered in the distribution status management table 42. User information (matching the distribution condition) is distributed (S706, match, and S707). At the same time, the information indicating the user of the distributed user information, the distribution destination, and the distribution state are added, and the distribution date is updated (S708).

  Specifically, as shown in FIG. 11, the user information distribution device 3 distributes user information of “Shiro Hitachi”, who is a section manager or higher, to the A system of the application execution device 1 that is the distribution destination. In the distribution status management table 42, ID (1004), distribution destination (A system), and distribution status (distributed) are added. The final delivery date is June 13, 2006, 00:00.

  Next, as shown in FIG. 12, the user information distribution unit 33 uses the user information that does not match the distribution condition set in the distribution condition table 320 (S706, does not match), and stores it in the distribution state management table 320. It is determined whether or not “distributed” is set (S709). If already distributed (S709, Yes), user information is extracted as deletion data.

  Then, as shown in FIG. 13, the user information distribution unit 33 distributes the extracted user information as deletion data to the distribution destination application execution device 1 (S710), and the distribution destination application execution device 1 Delete the extracted user information. Then, the user information distribution unit 33 changes the distribution state of the deleted user information in the distribution state management table 320 to “undistributed” (S711). Note that if the distribution has not been completed in S709 (S709, No), the series of processing ends.

  Specifically, as shown in FIG. 13, the user information distribution device 3 distributes the user information of “Hitachi Saburo” as deletion data to the A system of the application execution device 1 that is the distribution destination. The delivery status management table 42 is updated to ID (1003), delivery destination (A system), and delivery status (undelivered).

  On the other hand, when the distribution condition is changed (S701, change), the user information distribution unit 33, as shown by a thick frame in FIG. All user information that matches (section 712 or “general”) (S712, match) is extracted.

  Then, as shown in FIG. 15, the user information distribution unit 33 is set to “unregistered” or “undistributed” in the distribution status of the distribution status management table 320 from the target user information. (S713, match) User information is extracted. Subsequently, as shown in FIG. 16, the extracted user information is distributed as additional data to the application execution apparatus 1 as a distribution destination (S714). The information (ID) indicating the user of the user information distributed at the same time, “distribution destination”, and “distribution status” are added or “distribution status” is updated to “distributed”, and the distribution date and time are updated. (S715). In S713, if they do not match (S713, do not match), the series of processing ends.

  Specifically, as shown in FIG. 14, the users corresponding to the distribution condition table 320 are “Hitachi Jiro”, “Hitachi Saburo”, and “Hitachi Shiro”. As shown in FIG. 15, “Hitachi Saburo” is not distributed in the distribution status management table 42. The user information distribution apparatus 3 distributes the user information of “Hitachi Saburo” to the A system of the application execution apparatus 1 that is the distribution destination. “Saburo Hitachi” is added to the user information of the A system. Also, the distribution status management table 42 is updated to ID (1003), distribution destination (A system), and distribution status (distributed).

  On the other hand, the user information distribution unit 33 is user information that does not match the distribution conditions set in the distribution condition table 320 (S712, does not match), as shown by a thick frame in FIG. User information set as “distributed” in 42 (Yes in S718) is extracted as deletion data.

  Then, as shown in FIG. 18, the extracted user information is distributed as deletion data to the distribution destination application execution apparatus 1 (S719), and is deleted by the distribution destination application execution apparatus 1. Also, the distribution status in the distribution status management table 42 of the user information extracted as the deletion data is changed to “undistributed” (S720). Note that if the distribution has not been completed in S718 (S718, No), the series of processing ends.

  Specifically, as shown in FIG. 17, the user who does not correspond to the distribution condition table 320 is “Hitachi Taro”. In the distribution status management table 42, “Hitachi Taro” is already distributed. As shown in FIG. 18, the user information distribution apparatus 3 distributes the user information of “Hitachi Taro” as deletion data to the A system of the application execution apparatus 1 that is the distribution destination. Also, the distribution status management table 42 is updated to ID (1001), distribution destination (A system), and distribution status (undistributed).

  Although not shown in the flowchart shown in FIG. 7, the deletion condition may be changed during operation. For example, it is assumed that the content of the deletion condition table 310 is changed from “when the position is“ retirement ”” to “the position is“ retirement ”or“ change ””. At this time, the user information acquisition unit 31 acquires the changed deletion condition table 310 registered by the deletion condition registration unit 35. Then, user information that matches the deletion condition of the deletion condition table 310 changed at this timing, “job title is“ retirement ”or“ transfer ”” is extracted, and the user information of the DB server 4 is deleted. In addition, when the deleted user information is set to “distributed” in the distribution status of the distribution status management table 42, the user information distribution unit 33 uses the distribution destination application execution device as the deletion information. Deliver to 1 and request deletion. Then, the user information distribution unit 33 changes the distribution state of the deleted user information in the distribution state management table 42 to “undistributed” when a notification of the end of deletion is received from the application execution device.

  As described above, according to the user information distribution apparatus according to the embodiment of the present invention, user information that is updated regularly or irregularly is acquired, stored in the DB server 4, and updated for each application. By searching the user information with reference to the distribution condition table 320 in which the distribution conditions are set and registered in advance, extracting the corresponding user information and distributing it to the application execution device 1 to be distributed, Even if people change frequently, it is not necessary to register, delete, or change user information for each application, improving work efficiency. Therefore, especially when people change frequently. The effect obtained by a scale user is great.

  In addition, since there is no need to newly register, delete, or change user information for each application, there is no difference in user information managed for each application. Therefore, user information used in each application Increased reliability. Furthermore, for example, it is not necessary to newly register user information for the target personnel at the time of application expansion, such as adding a server (application execution device 1) for entrance / exit management. The burden on the operations manager is greatly reduced.

  The flowcharts shown in FIGS. 3 and 5 also show the processing procedure by the program according to the embodiment of the present invention, in addition to the operation of the user information distribution apparatus according to the embodiment of the present invention. . That is, the program according to the embodiment of the present invention is a program used for a user information distribution apparatus 3 to which a plurality of application execution apparatuses 1 that execute respective application programs using user information is connected. Process for acquiring user information updated regularly or irregularly and storing it in a storage device (for example, DB server 4) (S301 to S306 in FIG. 3), and distributing user information updated for each application program Processing for searching the storage device with reference to the distribution condition table 320 in which the conditions to be registered are registered in advance (S501 to S504 in FIG. 5), and the application execution device to be distributed by extracting the corresponding user information by the search 1 is executed by the computer (S505 in FIG. 5).

  According to the above-described program of the present invention, in an application that uses user information that is updated regularly or irregularly, only the user information necessary for each application is automatically distributed to the necessary application each time the user information is updated. By doing so, the reliability of user information is improved, and the number of work steps when expanding the application can be reduced.

  The constituent blocks of the user information acquisition unit 31, the distribution condition registration unit 32, the user information distribution unit 33, the interface unit 34, and the deletion condition registration unit 35 that constitute the user information distribution apparatus 3 shown in FIG. Specifically, the functions possessed are realized by the CPU that is the control center of the user information distribution apparatus 3 sequentially reading and executing the programs recorded in the memory. Both the CPU and the memory are not shown. The functions of the constituent blocks of the user information distribution apparatus 3 described above may be realized entirely by software, or at least a part thereof may be realized by hardware.

  According to the above-described embodiment of the present invention, the DB server 4 has been described as existing independently of the user information distribution device 3, but the user information distribution device 3 is the database server 4. You may take in the function which has. In this case, the load on the user information distribution device 3 is increased, but the DB server 4 is not required, so that the configuration is compact.

It is a figure which shows an example of the system configuration | structure of a user information delivery system. It is a functional block diagram of a user information delivery apparatus. It is a flowchart for demonstrating operation | movement of a user information delivery apparatus. It is an operation | movement conceptual diagram for demonstrating operation | movement of a user information delivery apparatus. It is a flowchart for demonstrating operation | movement of a user information delivery apparatus. It is an operation | movement conceptual diagram for demonstrating operation | movement of a user information delivery apparatus. Examples of operations during the operation of the user information distribution device (first-time user information distribution, user information distribution when user information is changed, user information distribution when distribution conditions are changed) 4 is a flowchart showing operations from registration of user information to distribution for each. It is operation | movement explanatory drawing about the first time user information delivery. It is operation | movement explanatory drawing about the first time user information delivery. It is operation | movement explanatory drawing about user information delivery when user information is changed. It is operation | movement explanatory drawing about user information delivery when user information is changed. It is operation | movement explanatory drawing about user information delivery when user information is changed. It is operation | movement explanatory drawing about user information delivery when user information is changed. It is operation | movement explanatory drawing about user information delivery when user information is changed. It is operation | movement explanatory drawing about user information delivery when user information is changed. It is operation | movement explanatory drawing of user information delivery when a delivery condition is changed. It is operation | movement explanatory drawing of user information delivery when a delivery condition is changed. It is operation | movement explanatory drawing of user information delivery when a delivery condition is changed.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Application execution apparatus 2 External system 3 User information delivery apparatus 4 DB server 5 Communication network (LAN)
DESCRIPTION OF SYMBOLS 31 User information acquisition part 32 Delivery condition registration part 33 User information delivery part 34 Interface part 35 Deletion condition registration part 41 User information 42 Delivery status management table 310 Deletion condition table 320 Delivery condition table

Claims (9)

A user information distribution device to which a plurality of application execution devices that execute respective application programs using user information is connected,
A user information acquisition unit that acquires user information that is updated regularly or irregularly and stores it in a storage device;
An application to be distributed by searching the storage device with reference to a distribution condition table in which conditions for distributing the updated user information for each application program are preset and registered, and extracting corresponding user information and user information delivery unit to be delivered to the execution unit, the possess,
The user information acquisition unit
When acquiring user information provided in a file or function and storing it in the storage device, if the acquired user information does not exist in the storage device, add it as data and set the update date and time, When the acquired user information exists, update the data and set the update date and time,
When the user information that matches the deletion condition set and registered in advance in the deletion condition table is already stored in the storage device, it is extracted from the corresponding data, and the items other than the user ID as the key item Delete and update the data, and set the deletion date and time for the data to be deleted
A user information distribution apparatus characterized by: The user information distribution unit preallocates to the storage device, for each piece of information indicating a user of the distributed user information, about the distribution status returned from each application execution device as a result of distributing the user information. The user information distribution apparatus according to claim 1, wherein the user information distribution device is set in the distribution status management table stored and stored, and the data item of the last distribution date and time set in the distribution condition table is updated with the distribution date and time . The user information delivery unit, the first time the user's information delivery, said the user information and the distribution condition table setting is registered, not to the delivery status management table in accordance with the contents that have been set and registered in the delivery condition table Distributing registered user information to a distribution destination application execution device, adding information indicating a user of the distributed user information, a distribution destination and a distribution state, and updating the distribution date and time The user information distribution apparatus according to claim 2 . The user information delivery unit, if the user information is changed, the update date and time that is set in the distribution condition table to extract the user information of the distribution conditions last distribution date after that is set to table Distributing user information that matches the distribution conditions, adding information indicating a user of the distributed user information, a distribution destination and a distribution state, and updating the distribution date and time,
With user information that does not match the delivery conditions set in the delivery condition table, the user information set as delivered in the delivery status management table is extracted and delivered to the application execution device of the delivery destination for deletion. 3. The user information distribution apparatus according to claim 2 , wherein a distribution state of the user information to be deleted in the distribution state management table is changed to undistributed. A user information distribution device to which a plurality of application execution devices that execute respective application programs using user information is connected,
A user information acquisition unit that acquires user information that is updated regularly or irregularly and stores it in a storage device;
An application to be distributed by searching the storage device with reference to a distribution condition table in which conditions for distributing the updated user information for each application program are preset and registered, and extracting corresponding user information A user information distribution unit that distributes to the execution device,
The user information distribution unit preallocates to the storage device, for each piece of information indicating a user of the distributed user information, about the distribution status returned from each application execution device as a result of distributing the user information. Set in the distribution status management table stored, and update the data item of the final distribution date and time set in the distribution condition table with the distribution date and time,
When the distribution condition table is changed, the user information distribution unit extracts all user information that matches the distribution condition set and registered in the distribution condition table, and includes the extracted user information. Information indicating the user of the distributed user information, extracting user information that is set as unregistered or non-distributed in the distribution status of the distribution status management table from Add or update the delivery destination and delivery status to update the delivery date and time,
In the user information that does not match the delivery conditions set in the delivery condition table, the user information set as delivered in the delivery status management table is extracted, delivered to the application execution apparatus of the delivery destination, and deleted. the deleted the user information of the delivery status management table to change an undelivered delivery status of a Subscriber information distribution device you characterized. A user information distribution device to which a plurality of application execution devices that execute respective application programs using user information is connected,
A user information acquisition unit that acquires user information that is updated regularly or irregularly and stores it in a storage device;
An application to be distributed by searching the storage device with reference to a distribution condition table in which conditions for distributing the updated user information for each application program are preset and registered, and extracting corresponding user information A user information distribution unit that distributes to the execution device,
The user information acquisition unit
When acquiring user information provided in a file or function and storing it in the storage device, if the acquired user information does not exist in the storage device, add it as data and set the update date and time, When the acquired user information exists, update the data and set the update date and time,
When the user information that matches the deletion condition set and registered in advance in the deletion condition table is already stored in the storage device, it is extracted from the corresponding data, and the items other than the user ID as the key item Delete and update the data, and set the deletion date and time for the data to be deleted
And
When the deletion condition table is changed, the user information distribution unit extracts all user information that matches the deleted deletion condition set and registered in the deletion condition table, and extracts the extracted user The user information set as distributed in the distribution status of the distribution status management table is extracted from the information, distributed to the application execution apparatus of the distribution destination, deleted, and the distribution of the deleted user information a Subscriber information distributing apparatus you and changing the undelivered delivery status in the status management table. A program used in a user information distribution device to which a plurality of application execution devices that execute respective application programs using user information is connected,
Processing to acquire user information updated regularly or irregularly and store it in a storage device;
Processing for searching the storage device with reference to a distribution condition table in which conditions for distributing the updated user information for each application program are registered in advance;
When the computer executes the process of extracting the corresponding user information by the search and distributing it to the application execution device to be distributed ,
In the process of storing in the storage device,
When acquiring user information provided in a file or function and storing it in the storage device, if the acquired user information does not exist in the storage device, add it as data and set the update date and time, When the acquired user information exists, update the data and set the update date and time,
When the user information that matches the deletion condition set and registered in advance in the deletion condition table is already stored in the storage device, it is extracted from the corresponding data, and the items other than the user ID as the key item Delete and update the data, and execute the process to set the deletion date and time for the data to be deleted
Program for. A plurality of application execution devices that execute each application program using user information;
User information that is connected to the plurality of application execution devices via a communication network, obtains user information that is updated regularly or irregularly from the outside, stores the user information in a storage device, and is updated for each application program searching the storage device with reference to the delivery condition table conditions are registered in advance to deliver, it has a, a user information distribution device for distributing the extracted and the relevant application execution apparatus user information relevant ,
The user information distribution device includes:
When acquiring user information provided in a file or function and storing it in the storage device, if the acquired user information does not exist in the storage device, add it as data and set the update date and time, When the acquired user information exists, update the data and set the update date and time,
When the user information that matches the deletion condition set and registered in advance in the deletion condition table is already stored in the storage device, it is extracted from the corresponding data, and the items other than the user ID as the key item A user information distribution system comprising: deleting and updating data; and setting a deletion date and time for the data to be deleted . A user information distribution method for a user information distribution apparatus that distributes the user information to a plurality of application execution apparatuses that execute respective application programs using user information,
The user information distribution device includes a user information acquisition unit, a user information distribution unit, and a storage unit,
The user information acquisition unit stores in the storage unit acquires user information that is updated regularly or irregularly,
The user information distribution unit searches the storage unit with reference to a distribution condition table in which conditions for distributing the updated user information for each application program are registered in advance, and retrieves the corresponding user information. When extracting and distributing to the application execution device to be distributed ,
The user information distribution device includes:
When acquiring the user information provided in a file or function and storing it in the storage unit, if the acquired user information does not exist in the storage unit, add it as data and set the update date and time, When the acquired user information exists, update the data and set the update date and time,
When the user information that matches the deletion condition set and registered in advance in the deletion condition table is already stored in the storage unit, it is extracted from the corresponding data and the items other than the user ID as the key item are extracted. A user information distribution method comprising deleting and updating data, and setting a deletion date and time for the data to be deleted .

Images