JP3740330B2 - Server device and network system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a server apparatus in a client server system constructed on a computer network such as a LAN. When the same network is shared by a plurality of groups, the use of a plurality of shared devices arranged on the network Is related to a plurality of user groups.
[0002]
[Prior art]
A computer network environment in an office is being prepared, and a network printer system is generally used as a typical network connection device.
[0003]
Recently, not only printers but also scanners, facsimile communication devices, and the like are being connected to a network and operated. In addition, multifunction devices having two or more functions of a printer function (image forming function), a scanner function (image reading function), and a facsimile document transmission / reception function are increasingly connected as a shared device on a network.
[0004]
[Problems to be solved by the invention]
As described above, a large number of various devices are connected to the network, and the way to maintain and operate them has become a problem.
[0005]
In particular, in order to perform business efficiently in an environment where many users use many devices on the same network, it is essential to provide an optimal operation form.
[0006]
In view of such a problem, the present invention provides a server device connected to a plurality of shared devices and a plurality of clients via a common network to constitute a network system, and uses a shared device for each group to which a user using the client belongs. It is an object of the present invention to provide a server device that can be managed.
[0007]
That is, the gist of the present invention is as follows. A server device that communicates with a device and a client device and manages received data; a storage unit that stores information related to an access authority of a group to which a plurality of users belong to a predetermined storage region; and a predetermined storage region; A management unit that manages devices in association with each other, a storage unit that stores data in a predetermined storage area associated with the device when data is received from the device, and a predetermined group for the predetermined storage area If there is an access request from a predetermined user belonging to the group, whether or not the predetermined user can access the data stored in the predetermined storage area is determined based on information related to the access authority stored in the storage means. And a determination means for determining It exists in the server apparatus characterized by this.
[0008]
Another gist of the present invention is as follows. A method for controlling a server device that communicates with a device and a client device and manages received data, the storage step storing information related to the access authority of a group to which a plurality of users belong to a predetermined storage area in a storage means; A management process for managing a predetermined storage area in association with a device; a storage process for storing data in a predetermined storage area associated with the device when data is received from the device; and a predetermined storage area In response to an access request from a predetermined user belonging to a predetermined group, data stored in a predetermined storage area of the predetermined user based on information relating to the access authority stored in the storage means And a determination step for determining whether or not access to the server is possible. Exist.
[0009]
Another gist of the present invention is as follows. Computer-readable recording medium storing a control program for causing a computer device to execute the control method of the server device of the present invention Exist.
[0010]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. In the following description, an example in which the present invention is applied to a document distribution server in a network system using a multifunction device as a shared device will be described as an embodiment of the present invention.
[0011]
(System configuration)
FIG. 1 is a diagram showing a configuration example of a document distribution system according to an embodiment of the present invention. In the figure, 1000 is a document distribution server.
Reference numerals 1010 to 1013 denote clients (client 1 to client 4) that use this server.
[0012]
Reference numerals 1020 and 1021 denote multifunction devices (MFD1 and MFD2) connected to the server. The multi-function device is an apparatus having functions of, for example, a printer, a scanner, and a facsimile machine.
[0013]
Here, the client 1 and the client 2 share and operate the multifunction device MFD1, and this is assumed to be group A.
Similarly, the client 3 and the client 4 share and operate the device MFD2, and this is assumed to be a group B.
Such operation management is performed by 1000 document distribution servers.
[0014]
(Client configuration)
FIG. 2 is a block diagram illustrating a functional configuration example of the client.
5001 is a general document creation application, 5002 is a graphic device interface provided by the OS, and 5003 is a printer driver. A print manager 5004 is generally provided by the OS. A print job requested by the application 5001 passes through these modules (5002 to 5004), and the network OS passes through the LAN controller 5030. Processed on the printing system provided.
[0015]
Reference numeral 5005 denotes a FAX driver. When a document is transmitted by FAX from the document creation application 5001, this driver is selected and processed as a transmission request job via the job management unit 5020 described later.
[0016]
Reference numeral 5006 denotes a scanner application that reads an image from the local scanner device 5050 and edits the read image, 5007 denotes a scanner driver interface that interfaces the scanner application 5006 and a scanner driver 5008 described later, and 5008 denotes a scanner unique to the device. An image reading request by the scanner application 5006 as a driver is processed as a scanner reading job via a job management unit 5020 described later. In the configuration example of FIG. 2, the case where the local scanner device 5050 directly connected to the client is used as the image reading apparatus is shown. However, a configuration in which an image is read using a remote scanner connected to the LAN. Is possible.
[0017]
A document distribution / management application 5010 provides the user with access to the document distribution server, various setting functions, and the like using a GUI.
[0018]
Specifically, display of various data (FAX transmission / reception document, scanner document, communication history information, etc.), document editing function, various setting functions (including mode setting that makes a personal document a shared document, address book setting), various job designations Provides operations (FAX transmission, document printing, etc.).
[0019]
In addition, in the client of FIG. 2, in addition to the general user application, several administrator applications (not shown) are also prepared.
One of them is a manual distribution application for received documents. This is because the contents of the received document temporarily stored in the document distribution server when the destination is unknown (including that it cannot be analyzed) is displayed using a viewer application, and the destination of the document can be visually confirmed. The document is distributed as a document addressed to a predetermined user.
In addition, as an application for the server administrator, an administrator application that can perform client (user) setting, remote device setting, and the like using the server is also prepared.
[0020]
A document distribution / management driver 5011 handles various job data requested from the document distribution / management application 5010 via the job management unit 5020.
A job management unit 5020 manages various jobs requested from various applications 5001, 5006, and 5010.
[0021]
A server job control unit 5021 performs data transfer processing with a server for jobs via various servers. 5030 is a LAN control unit. Controls communication on the provided LAN.
Reference numeral 5022 denotes a local job control unit which controls a job for a local device via the I / O control unit 5040.
Reference numeral 5023 denotes a local job database, which manages various job data.
[0022]
Such a client has a hardware configuration such as a CPU, ROM, RAM, HDD, CRT, network interface, peripheral device interface, keyboard, mouse, etc., and a general-purpose computer device capable of operating an OS using a GUI Can be realized.
[0023]
(Client processing behavior)
Next, the processing operation of the client will be described using the flowchart shown in FIG.
In step S5101, connection (Login) processing to the document distribution server 1000 is performed.
First, authentication as a user of the document distribution / management system is performed by entering a user ID and password on a login screen or the like.
[0024]
Step S5102 is data upload and display processing from the server. As a result of the successful login, the client side uses a predetermined GUI on the client side using data already managed on the server side as data for the user. Display data.
Step S5110 detects the presence or absence of a job request from the user, and step S5111 performs processing if there is any job request.
[0025]
In step S5120, the end request of the document distribution / management application 5010 is viewed. If there is no end request, the process returns to step S5102, and the server side data is again overflowed, and the status regarding the presence or absence of the distributed document is confirmed.
In step S5121, a disconnection (Logout) process with the server is performed in the process when there is an application termination request in step S5120, and the process is terminated.
[0026]
(Configuration of multi-function device)
FIG. 4 is a block diagram illustrating a configuration example of a multifunction device (MFD) that can be used in the present embodiment.
Reference numeral 2001 denotes a resource management unit that manages all of the various resources supported as a device and performs scheduling of various requested jobs.
[0027]
An operation unit 2010 is a user interface for providing a user with a function as a terminal.
A reading control unit 2015 controls the scanner unit 2016.
[0028]
A recording control unit 2020 controls the printer unit 2021. In addition, as an option, the printer unit 2021 can be mounted and controlled with a sorter unit 2022 and a duplex recording unit 2023.
[0029]
A communication control unit 2025 controls normal FAX transmission / reception via the line control unit 2026.
Reference numeral 2030 denotes a memory management unit that allocates memory 2031 resources to each control unit, and performs storage management of various document data and the like.
[0030]
An image processing unit 2035 performs image processing necessary for FAX transmission and reception recording, such as paper size conversion, resolution conversion, and smoothing processing.
An encoding processing unit 2040 mainly performs encoding and decoding processes such as MH, MR, and MMR, which are typically used for FAX transmission / reception.
[0031]
Reference numeral 2045 denotes a PDL control unit. In this embodiment, PDL (page description language) data received via the LAN is converted into video data by the PDL processing unit 2046. The converted video data is transferred to the recording control unit 2020 and output from the printer unit 2021.
[0032]
Reference numeral 2050 denotes an external i / f control unit. In this example, a system for performing predetermined data communication, job management and control with a server on the LAN via the LAN control unit 2051, and a WSi / f control unit 2052 are used. And a system for performing predetermined processing with a workstation (WS) connected externally.
[0033]
Such a multifunction device, for example, receives a transmission job and print job from the server / WS, and transfers received data and scanner read data to the server / WS side under the management of the resource management unit 2001. .
[0034]
Also, means for designating the client from the operation unit 2010 is provided to transfer the scanner read data to the server for a specific user (client) on the network. The following supplements the operation of a single multifunction device.
[0035]
"Copy operation"
Each related control unit is controlled under the management of the resource management unit 2001 so that an original set on the scanner unit 2016 is read by an operation from the operation unit 2010 and output to the printer unit 2021.
[0036]
"FAX transmission"
Resource management so that the manuscript set on the scanner unit 2016 is read by the operation from the operation unit 2010, the facsimile processing is performed by the coding processing unit 2040, and the facsimile data is transferred from the line control unit 2026. Each related control unit is controlled under the management of the unit 2001.
[0037]
"FAX reception"
Data received from the line control unit 2060 is temporarily stored in the memory 2031. In general, this image data is output as a received document output, decoded by the encoding processing unit 2040, and printed out from the printer unit 2021. Thus, each related control unit is controlled under the management of the resource management unit 2001 so that data is transferred to the server via the LAN control 2051.
[0038]
(Processing of multi-function devices)
FIG. 5 is a flowchart showing the processing operation of the above-described multifunction device, particularly the operation when various jobs are processed in cooperation with the server connected to the server on the LAN.
[0039]
In step S2101, it is first confirmed whether a connection request with the server has been made. If there is no request, the process waits until the request is made. The connection request instruction with the server can be received from the operation unit 2010 of the multifunction device or from the network. At this time, the server to be connected can also be specified.
[0040]
Step S2102 is a connection process when a connection request to the server is made in step S2101. When the server name to be connected is specified, the parameter value is added to the data transmitted on the LAN. Thus, it is connected to a predetermined server. Further, when connected to the server, address book data and the like described later are downloaded from the server side.
[0041]
In step S2110, it is checked whether or not there is job data to be transferred to the server in the multi-function device. For example, if there is a received document transfer job, a scanner reading job, etc., job data is transferred to the server in step S2111. Processing such as transfer is performed.
[0042]
In step S2120, first, the availability of resources in the multifunction device is confirmed. If the job can be accepted, in step S2121, the server confirms whether there is a job request to the multifunction device (job request). If there is a requested job, job data is received in step S2122 and job processing is performed. Generally, job data is temporarily stored in a memory, and then necessary processing such as FAX transmission processing and printout processing is performed.
[0043]
In step S2125, the server is notified of the status of the device, such as during job processing or idle.
[0044]
In step S2130, it is confirmed whether or not a request for disconnecting from the server has been issued. If there is no instruction, the process proceeds to step S2110 again to continue the process. If there is a request to disconnect from the server, the server disconnects the server in step S2131 and waits for a connection request to the server in step S2101. Also, when connected to the WS instead of the server, basically the same processing as the processing shown here is performed.
[0045]
(Document distribution server configuration)
FIG. 6 is a block diagram illustrating a functional configuration example of the document distribution server 1000 according to the present embodiment.
In the figure, reference numeral 3001 denotes a LAN control unit, and a basic function is provided by a network OS in which a server application is installed.
[0046]
A transaction management unit 3002 performs individual communication processing with a device and a client under server management via the LAN control unit 3001 based on the result of internal processing.
[0047]
A request queue management unit 3003 basically temporarily queues various request messages transferred asynchronously from the device and the client, and sequentially performs processing according to the request contents. However, it is assumed that a request requiring scheduling occurs in the server.
[0048]
Reference numeral 3004 denotes a service management unit, which passes processing to various job processing units in accordance with request contents from a device or client, or in some cases, from the server.
A user / device management unit 3005 processes a job related to a user (client) or a device, and basically performs job processing related to management of a connected user (client) and a device.
[0049]
For example, determination of connection (login) request processing from each client (1010-1013) and device (1020, 1021), handling of document information managed for each user, address information, device processing capability, job processing Manage and control status, resource status, etc.
[0050]
3006 processes a job related to server management, and basically provides service functions such as server settings, data backup, and service log data acquisition to server administrators.
A server 3007 handles management related to overall job processing in this server. Here, the control right is transferred to the scheduler 3010 as necessary, and various jobs 3020 are executed under the management.
[0051]
Reference numeral 3030 denotes a memory management unit, and various data handled by the server are stored and managed in the database 3031 under the management in principle, and are referred to and read out as necessary.
[0052]
Reference numeral 3050 denotes a modem control unit that controls a modem mounted / connected to the server, and is controlled under the management of the FAX control unit 3051. The FAX control unit 3051 has a function of processing a FAX transmission job managed by the server via the transaction management unit 3002 or transferring a FAX reception document subjected to direct reception processing to the server side.
[0053]
(Document processing job group)
FIG. 7 is a diagram showing various document processing job groups of the document distribution server in this embodiment.
The document processing job of the document distribution server is, as a general rule, a device job group 3110 that is a job that involves job data transfer processing between the server and the device, and data processed between the server or server = client. It can be roughly divided into various document processing job groups 3120 limited to processing, and each is managed and controlled by a scheduler 3010 in the server. Hereinafter, jobs belonging to each job group will be described.
[0054]
<Device job group>
Reference numeral 3111 denotes a fax transmission job, which receives transmission request job data from each client and requests fax transmission from a device corresponding to the client that has requested transmission.
Reference numeral 3112 denotes a fax reception job, which receives fax reception data from the device and stores and manages the reception data in the server.
[0055]
Reference numeral 3113 denotes a print job, which controls processing related to a print request job for an image document such as fax reception data stored and managed from the client side, particularly in the server.
Reference numeral 3114 denotes a scan job, which receives document data read by the device, is normally managed as a file in a read-only folder of a predetermined user, and can be accessed by the user. It also supports a function for broadcast processing as a scan job.
[0056]
<Document processing job group>
Reference numeral 3121 denotes an OCR analysis job, which performs OCR processing on received documents, scanner-read documents, and the like that are stored and managed as image data.
In this case, it is possible to perform an OCR process on the entire directly designated document and to start up from another document summary job 3122 and a routing job 3126 according to the purpose.
[0057]
For example, the destination data can be extracted from the received document, or the entire image data can be subjected to OCR processing, and converted into document data composed of character codes (including image data).
Reference numeral 3122 denotes a document summarization job for performing content summarization processing on the character-coded documents stored in the server.
[0058]
Reference numeral 3123 denotes a document search job, which provides a search means for documents stored in the server.
An encryption processing unit 3124 performs encryption processing on the document stored in the server as necessary, and guarantees the security for the document.
[0059]
Reference numeral 3125 denotes a document data transfer job, which transfers image data to the client side. At this time, if there is a request for reducing the display size, the reduced display data is transferred.
Reference numeral 3126 denotes an automatic routing job, in which distribution processing for a received document is performed by extracting a destination by the OCR analysis job 3121 and moving the document to a management area for each user corresponding to the extracted destination. Perform processing.
[0060]
Reference numeral 3127 denotes a manual routing job. In particular, for a received document stored temporarily, a user of a specially authorized client visually shows the contents of each document and confirms a predetermined destination. And means for manually moving the document within the server to each user's folder on the network.
Reference numeral 3128 denotes a document registration job, which can register a document in the server in response to a request from the client side.
[0061]
(Operation of document distribution server)
FIG. 8 is a flowchart showing the basic operation of the document distribution server.
Step S3401 is a database check performed at power-on.
Step S3410 is confirmation of a login request to the server from various clients and devices. If there is a Login request, in Step S3411 Login processing including password check and the like is performed.
[0062]
Step S3415 is confirmation of a user information request from the client. If there is a user information request, in step S3416, each user's individual data and shared data are transferred to the client side in accordance with the request contents.
[0063]
Step S3420 is confirmation of the server information request from the client. If there is a system information request, in step S3421, server-specific data, information on the connected device, and the like are transferred to the client side according to the request content.
Step S3425 is confirmation of the document data request from the client. If there is a document data request, data transfer processing of the designated document is performed in step S3426.
[0064]
Step S3430 is confirmation of various job requests from the client and device. If there is a job request, in step S3431, the job data corresponding to the designated job type is processed.
Step S3435 is confirmation of a processing request relating to address book processing. If there is a processing request, processing relating to collection, registration, and change of address information is performed in step S3436.
[0065]
Step S3440 is confirmation of the information notification request from the device. Here, capability notifications and status notifications from the device are acquired and managed.
Step S3445 is confirmation of the Logout request. If there is a logout request, logout processing is performed in step S3446.
[0066]
Step S3490 is confirmation of a server shutdown request. If there is a request, a shutdown process is performed in step S3491.
[0067]
(Scheduler operation)
FIG. 9 is a flowchart for explaining the operation of the scheduler.
Here, how the job is processed in the document distribution server in cooperation with the client and the device will be described.
In step S4201, it is determined whether a reception notification from the device has been received. If received, the above-described FAX reception job is activated, and the subsequent processing is left to the FAX reception processing.
[0068]
In step S4205, it is determined whether a scan job notification is received from the device. If received, the scan job described above is activated, and the subsequent processing is left to that.
In step S4210, it is determined whether a job request from the device has been received. If received, the request source device is first checked in step S4211, and the job table is searched for the presence or absence of a job for the device. In step S4212, based on the search result, if there is a job, the job data is transferred to the device side in step S4213. If there is no job, the device side is notified in step S4214.
[0069]
By processing in this way, a job for which a device has been specified is requested for that device, but in particular for a job in which the device is not limited, a job is sequentially performed for a device for which a predetermined functional resource is available. Is allocated, the job is processed efficiently.
[0070]
In step S4220, it is determined whether a FAX transmission request from the client is received. If received, first, in step S4221, whether the group of the user of the client who requested the job matches the specified device group. Is determined based on the user management table and the device management table. If possible, job data transfer processing is performed in step S4222 and job registration is performed. If not possible, error processing is performed in step S4223. For error processing, notify the client of the error content, etc., and prompt the user to change the device specified on the client side, or automatically select a device that can handle the job, change the device name, etc. It is possible to adopt means such as notifying the client that requested the job.
[0071]
In step S4230, it is determined whether a print request from the client has been received. If received, in step S4231, it is confirmed whether the client user group matches the specified device group. If there is no problem, job data transfer processing is performed in step S4232, and job registration is performed.
[0072]
In step S4240, it is determined whether a document processing service request supported by another server has been received. If received, a predetermined document processing job is started in step S4141, and the subsequent processing is left to that.
By repeating these processes, the job is appropriately processed.
[0073]
(User management table)
FIG. 10 is a diagram showing an example of a user management table stored in the shared data part of the database 3031 by the document distribution server in this embodiment.
Items and registration contents are as follows.
(1) Number: A number for managing each registered user internally.
(2) User name: Basically, a network user name is registered, but separately, a user name as a FAX transmission destination, a user name registered in a group, and the like can be registered.
This data is sent directly to the device side so that it can be displayed and instructed as a delivery destination on the device.
-In addition, by registering a device having a printer function such as MFD as a user, for example, a printer that outputs an image read by a scanner can be specified, or a group user can include a printer to print out as part of a broadcast instruction. It can be instructed.
[0074]
(3) Attribute: The attribute of the registered user, specifically, network user (client), FAX number, group user, printer (MFD) is identified.
(4) Member: In the case of a group user, a group member is designated by a user number. In the example of FIG. 10, the users AAAA and BBBB are members of the A group, and the users CCCC and DDDD are members of the B group.
(5) Dial number: In the case of a FAX transmission destination user, the FAX number is registered.
(6) System administrator: The administrator of the entire system is registered.
-Only system administrators can manage and manage shared resources in the system.
[0075]
(7) Group administrator: Registers the group system administrator when a group is set.
-Has the authority to manage and manage shared resources within a group.
(8) Scanner registration
Set whether to transfer to a device having a scanner function such as MFD as a user name, and transfer only those set to “register” to the device.
In addition, as default settings, “network user” and “group user” are registered in the device, and “FAX transmission destination user” is not registered.
Note that all of these address data can be used as a document distribution destination from each client.
[0076]
(Device management table)
FIG. 11 is a diagram showing an example of a device management table stored in the shared data section of the database 3031 by the document distribution server in the present embodiment.
Items and registration contents are as follows.
(1) Number: A number for managing each device internally.
(2) Device name: Device name registered by the user to each device.
(3) Function-specific use restrictions: Access (use rights) is set for each function of each device.
[0077]
When a job from each client (user) is distributed to each device, or when a job from each device is received, control is performed with reference to this table.
For example, a device called MFD 1 is controlled so as to process a job corresponding to a user belonging to the A group in principle regarding the print function, FAX transmission, and FAX reception function.
[0078]
However, since the FAX reception has a separate automatic distribution function, when a distribution destination in the system is uniquely determined, it can be distributed to users outside a predetermined group. However, for a received document whose distribution destination is not specified, the document is managed in a shared area dedicated to the group. In addition, when the use user restriction is not set in the FAX reception function, the received document whose distribution destination is not specified is managed in a common management area for the system.
[0079]
(Database configuration)
FIG. 12 is a diagram illustrating a configuration example of the database 3031 included in the document distribution server according to the present embodiment.
[Shared data]: The following data is managed as shared data. Items and contents are as follows.
(1) User management information
User name, user password, user-specific settings, device setting information, user management table, etc.
(2) Server management information
-Number of user licenses, time, server application version, etc.
[0080]
(3) Device management information
・ Device management table, device functions, status, etc.
(4) Shared address data: shared address data.
-Automatically register each user's LAN address on the network.
(5) Shared document data: Document data to be shared
(6) Shared document annotation data
Annotation information for shared documents.
[0081]
(7) Communication log data
-Communication log (history) data related to FAX transmission / reception, such as FAX document management table.
(8) Job / billing log data
-Log data required for billing management (communication time, print request count, etc.).
(9) Temporary storage data
-In particular, fax-received documents that are forwarded without an explicit destination.
[0082]
[Individual user data]: The following data is managed as data for each user. Items and contents are as follows.
(1) Inbox data: received document data mainly transferred from the device side.
(2) OutBox data: unprocessed job information to be transferred to the device side.
(3) Scan data: Document data transferred after scanning.
(4) SentFax data: document data that has been transmitted.
(5) Trash data: Document data temporarily instructed unnecessary.
(6) User dedicated folder data
Documents that are moved and copied by the user to folders individually set by the user are managed.
(7) User-specific address data
-Address information set by the user.
[0083]
[Individual group data]: Manage the following data as data for each group.
(1) Inbox data: received document data transferred from the device side in the group.
(2) OutBox data: job information requested to devices in the group.
(3) Scan data: Scan document data designated by a group user.
(4) Group dedicated folder data: a folder uniquely set by a group user.
(5) Group dedicated address data: Address information dedicated to group users.
[0084]
(data flow)
FIG. 13 is a diagram showing a data flow in the document distribution system of the present embodiment shown in FIG.
The server 1000 and the multi-function devices (MFD1, 2) (1020, 1021) perform data transfer processing via the data buffer 3310 in the server 1000, and the data buffer 3310
(1) FAX transmission request data buffer
(2) FAX reception data buffer
(3) Data buffer for print data
(4) Data buffer for scanner data
Are prepared for each, and these data can be transferred in a packet unit between devices = servers.
[0085]
In the server, data transfer is performed internally between the data buffer 3310 and the database 3031 as necessary.
Each user (1010 to 1013) is basically provided with various services by performing data transfer (access) to a database in the server.
[0086]
For example, the user 1 (1010) as the client 1 accesses the data area of the common data area in the server, the user 1 data area managed individually for the user 1, and the data area dedicated to the group A to which the user 1 belongs. Various services and data can be received.
[0087]
(FAX received document management table)
FIG. 14 is a diagram illustrating an example of a FAX reception document management table stored in the database 3031 by the document distribution server in the present embodiment.
Here, the folder for each transmission source can be managed in the shared data area, and access can be restricted as necessary.
[0088]
Items and registration contents are as follows.
(1) Shared folder name
Here, a folder name is set for each predetermined destination number and folder ID so that the user can access the FAX received document for each folder.
-Documents whose distribution destinations cannot be automatically identified in FAX reception documents when no folder is set are managed as general reception documents (default).
A FAX reception document from a group-designated device is managed by a group-specific InBox.
-It is also possible to set the automatic print output for the default document without determining the delivery destination, and record the received document.
In addition, it is possible to temporarily store a document whose distribution destination is not fixed and distribute it by manual routing processing.
[0089]
(2) Destination number
・ Set the fax source dial number for each folder.
The dialed number corresponding to the received document notified from the FAX device is compared with the number set here, and the received document is managed in the corresponding folder.
• Use dial numbers that are exchanged by means supported by international standard FAX procedures.
-By registering a plurality of dial numbers, it is possible to collectively manage FAX reception between common groups.
[0090]
(3) Folder ID
-For example, ITU-T TT. A folder can be selected by directly specifying an ID using a sub-address defined by 30 or the like.
(4) Document number
・ Manage document numbers for each folder.
(5) Access rights
・ Users (clients) that can access each folder can be arbitrarily set in preparation for the case where access from a client outside the department is not permitted, although managed as a received document in the shared area. ing.
[0091]
Note that the table shown here is a table for processing related to the shared folder. Separately, by setting a folder ID corresponding to the InBox for each user, the table is directly set to the user dedicated folder. It is also possible to transfer the received document.
[0092]
(Scan job)
FIG. 15 shows a processing flow diagram for a scan job.
In step S3601, first, scan job data from the MFD is received. The job data includes an image data portion made up of image data read by the scanner and a delivery destination data portion made up of the delivery destination data.
[0093]
In step S3602, the image data portion is first registered in the database as a temporarily saved document file.
In step S3603, the contents of the distribution destination data part are analyzed to detect the number of distributions to be processed.
In step S3610, unprocessed individual destination data (user name) is extracted.
[0094]
In step S3615, it is determined whether or not the attribute is “client”. If so, in step S3616, an internal distribution process is performed for a predetermined user folder, and the process proceeds to step S3630.
In step S3620, it is determined whether the destination data attribute is “FAX transmission destination”. If so, registration as a new transmission job is performed internally in step S3621, and the flow advances to step S3630.
[0095]
In step S3630, it is determined whether the destination data corresponds to the printer device. If so, the job is registered as a print job in step S3631.
In step S3640, it is checked whether there is any other data to be distributed, and if there is still unprocessed data, the process returns to step S3610.
When the distribution (registration) process is completed, post-processing such as a temporarily stored document is performed in step S3650, and the process ends.
[0096]
(FAX reception job)
FIG. 16 shows a FAX reception job processing flowchart.
In step S3801, job data including FAX reception data and distribution processing data is received from the device side.
[0097]
In step S3802, the image data is provisionally registered as a general received document.
In step S3803, the contents of the added distribution processing data are analyzed.
[0098]
In step S3810, it is confirmed whether or not a folder ID (client-dedicated folder or a predetermined shared folder) is explicitly designated as a transmission destination. If an instruction is given, the document is stored in the user folder designated in step S3811. Re-register and end the process.
[0099]
In step S3820, it is confirmed whether FAX transmission source dial data is added. If there is transmission source dial data, it is confirmed in step S3821 whether a corresponding folder by FAX transmission source is set. Is set, the document is re-registered in the corresponding folder in step S3822, and the process is terminated.
[0100]
In step S3830, the setting of the automatic distribution processing mode for the document whose distribution destination is undetermined is confirmed. Processing is terminated by entrusting.
[0101]
In step S3840, it is confirmed whether the right to use the device is set. If there is a setting, the document is re-registered in a predetermined folder in step S3841, and the process ends.
[0102]
In step S3850, it is confirmed whether or not the automatic print mode is set. If it is set, a document whose destination has not been determined so far is registered and processed so as to be processed as a print job in step S3851. Exit.
[0103]
A received document whose folder to be registered is not fixed so far is forcibly registered in the default common folder, and is stored and managed as a general received document. A manual routing job 3127 is started from a predetermined client and manually operated. A document is transferred to a predetermined user folder.
[0104]
[Other Embodiments]
Note that the present invention can be applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, and a printer), and a device (for example, a copying machine and a facsimile device) including a single device. You may apply to.
[0105]
Another object of the present invention is to supply a storage medium (or recording medium) in which a program code of software that realizes the functions of the above-described embodiments is recorded to a system or apparatus, and the computer (or CPU or CPU) of the system or apparatus. Needless to say, this can also be achieved by the MPU) reading and executing the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention. Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.
[0106]
Furthermore, after the program code read from the storage medium is written into a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer, the function is determined based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion card or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.
[0107]
When the present invention is applied to the above storage medium, the storage medium corresponds to the flowchart described above (shown in one or more of FIGS. 3, 5, 8, 9, 15, and 16). Program code will be stored.
[0108]
【The invention's effect】
As described above, according to the present invention, by registering and managing the user who uses the client as a group user, and setting the usage authority of each shared device for each user group,
(1) A predetermined shared device group can be used exclusively by a predetermined user group.
(2) A document received from a device can be managed in a form limited to users in the group.
(3) Document information and address information can be shared among group users.
Furthermore, by setting the access conditions for each function of the device, the facsimile communication function can be opened only to a predetermined user, and the printer function can be used by any user. There is an effect that can be.
[Brief description of the drawings]
FIG. 1 is a block diagram illustrating a configuration example of a document distribution system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a configuration example of a client.
FIG. 3 is a flowchart showing a processing operation of a client.
FIG. 4 is a block diagram illustrating a configuration example of a multifunction device.
FIG. 5 is a flowchart showing processing operations of the multifunction device.
FIG. 6 is a block diagram illustrating a configuration example of a document distribution server according to the embodiment of the present invention.
FIG. 7 is a diagram illustrating an example of a job group of a document distribution server.
FIG. 8 is a flowchart showing a basic processing operation of the document distribution server.
FIG. 9 is a flowchart showing the processing operation of the scheduler of the document distribution server.
FIG. 10 is a diagram illustrating an example of a user management table.
FIG. 11 is a diagram illustrating an example of a device management table.
FIG. 12 is a diagram showing a database configuration example of a document distribution server.
FIG. 13 is a diagram showing a data flow in the document distribution system shown in FIG. 1;
FIG. 14 illustrates an example of a FAX received document management table.
FIG. 15 is a flowchart illustrating details of scan job processing.
FIG. 16 is a flowchart illustrating details of FAX reception job processing.

Claims (7)

A server device that communicates with a device and a client device and manages received data,
Storage means for storing information related to the access authority of a group to which a plurality of users belong to a predetermined storage area;
Management means for managing the predetermined storage area and the device in association with each other;
When receiving data from the device, storage means for storing the data in a predetermined storage area associated with the device;
When there is an access request from a predetermined user belonging to a predetermined group to the predetermined storage area, the predetermined user's predetermined Determining means for determining whether or not the data stored in the storage area can be accessed;
Server device comprising: a. The device is, transmission and reception functions of the facsimile document, the image reading function and the server apparatus according to claim 1, wherein the at least one function of the image forming function. In each group, the users share belonging to that group, a plurality of devices as claimed in claim 1 or claim 2, wherein the has a region collectively stores data obtained from either Server device. The device is, transmission and reception functions of the facsimile document, having at least two functions of the image reading function and an image forming function,
It said management means, information regarding the authority to use the device, the server device according to any one of claims 1 to 3, characterized in memorize to Rukoto for each function of the device. The data received from the device is a server device according to any one of claims 1 to 4, wherein the device is a facsimile document data received. A method for controlling a server device that communicates with a device and a client device and manages received data,
A storage step of storing in the storage means information relating to the access authority of a group to which a plurality of users belong to a predetermined storage area;
A management step of managing the predetermined storage area and the device in association with each other;
When receiving data from the device, storing the data in a predetermined storage area associated with the device;
When there is an access request from a predetermined user belonging to a predetermined group to the predetermined storage area, the predetermined user's predetermined A determination step for determining whether or not to access data stored in the storage area of
  A control method for a server device, comprising:   A computer-readable recording medium storing a control program for causing a computer device to execute the control method for a server device according to claim 6.

Images