JP2003333241A - User information managing method and image forming device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a user information managing method which enable one or more applications to share user information and can unitedly manage the user information, and to provide an image forming device. <P>SOLUTION: The user information managing method for the image forming device which has one or more applications performing image forming processes includes a request stage wherein an application requests a user information managing means 49 to acquire user information and a supply stage wherein the user information managing means 49 acquires the user information complying with the request from the applications and supplies the acquired user information to the application having made the request. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a user information management method and an image forming apparatus, and more particularly to a user information management method and an image forming apparatus for providing user information to one or more applications.

[0002]

2. Description of the Related Art In recent years, an image forming apparatus (hereinafter referred to as a fusion machine) in which the functions of each device such as a printer, a copy machine, a facsimile machine, and a scanner are housed in one housing has become known. This fusion machine has a display unit in one housing,
A printing unit, an image pickup unit, and the like are provided, and four types of software corresponding to the printer, the copy, the facsimile, and the scanner are provided, and the software is switched to operate as the printer, the copy, the facsimile, and the scanner.

Such a multi-function peripheral is connected to another multi-function peripheral or a computer via a network, and distributes image information, for example, using a distribution function. The multi-function peripheral having a distribution function has, for example, distribution destination information and usage restriction / billing information as user information.

The distribution destination information manages a distribution destination and a sender. The distribution destination information has a low update frequency and is relatively easy to back up. In addition, since the distribution destination information is not limited to the users who use the multi-function peripheral, the users who need to be managed increase the number of users who need to be managed.

On the other hand, the usage restriction / billing information manages the availability of various functions and the number of usable functions. Since the usage restriction / billing information is updated every time the device is used, the updating frequency is high and backup is difficult.
In addition, since the use restriction / billing information is limited to the users who use the multi-function peripheral, the users who need to be managed are reduced in number.

As described above, since the distribution destination information and the usage restriction / billing information differ in the ease of backup and the number of users who need to be managed, the conditions required for the storage device as the storage means are different. . For example, the delivery destination information requires a large-capacity storage device at the expense of speed and reliability. Further, the usage restriction / billing information requires a high-speed and highly reliable storage device at the cost of cost and capacity.

In the conventional fusion machine, for example, distribution destination information is stored in a hard disk device for management, and usage restriction / billing information is stored in a non-volatile RAM for management.

In Patent Document 1, a display unit is provided in one housing,
An example of a multi-function machine that operates as a printer, copy, facsimile, and scanner by providing a printing unit, an imaging unit, and the like, and providing four types of software corresponding to the printer, copy, facsimile, and scanner, respectively, and switching the software Is listed.

[0009]

[Patent Document 1] Japanese Patent Laid-Open No. 2002-84383

[0010]

A conventional multi-function machine has an application for performing a process unique to a user service related to image forming processing such as a printer, a copy machine, a facsimile machine, and a scanner. Each application separately managed the delivery destination information for using the delivery function.

Therefore, in the conventional fusion machine, there is a problem that each application must have a similar function of managing distribution destination information. It is useless to have the same function for each application in this way, and the similar program error (Bu
There was a problem that the possibility of including g) would increase.

The present invention has been made in view of the above points, and provides a user information management method and an image forming apparatus that allow one or more applications to share user information and centrally manage the user information. The purpose is to do.

[0013]

In order to solve the above problems, an invention according to claim 1 provides a user information management method for an image forming apparatus having at least one application for performing an image forming process. , The request stage in which the application requests the user information management means to acquire the user information, and the user information management means acquires the user information in response to the request from the application, and requests the acquired user information. And a supply stage for supplying the application.

In such a user information management method, the user information management means acquires the user information in response to the request from the application and supplies it to the requesting application so that the user information can be shared and the user information can be shared. It is possible to manage centrally.

Further, the invention according to claim 2 is characterized in that, in the supplying step, the user information management means obtains user information in response to a request from an application from the storage means.

According to such a user information management method, the user information corresponding to the request from the application can be acquired from the storage means.

Further, in the invention according to claim 3, in the supplying step, the user information management means determines a storage means in which user information in response to a request from an application is stored, and the determined storage means determines a user. It is characterized by acquiring information.

In such a user information management method, it is possible to determine the storage means in which the user information corresponding to the request from the application is stored and acquire the user information from the determined storage means. Desired user information can be acquired even if the user information is sorted and stored in the means.

Further, the invention according to claim 4 is characterized in that the user information includes distribution destination information and usage authority / billing information.

In such a user information management method, the user information can be configured to include distribution destination information and usage authority / billing information.

According to a fifth aspect of the present invention, the storage means stores the distribution destination information in which the distribution destination information is stored, and the usage authority / charge information in which the usage authority / billing information is stored.
And a billing information storage means.

In such a user information management method, the storage means can be configured to include the distribution destination information storage means and the usage authority / billing information storage means.

The invention according to claim 6 is characterized in that, in the requesting step, the application requests the user information managing means to acquire the user information by a predefined function.

In such a user information management method, the application can request the user information management means to acquire the user information by using a predefined function.

Further, the invention according to claim 7 is characterized in that the function requests acquisition of function information possessed by the user information management means.

In such a user information management method, it is possible to request the user information management means to acquire the function information possessed by the user information management means by using a predetermined function. Here, the function information represents the function of the user information management means.

Further, the invention according to claim 8 is characterized in that the function requests an update notification to be notified when the user information is updated.

In such a user information management method, an update notification can be requested to the user information management means by using a predetermined function.

The invention according to claim 9 is characterized in that the function requests acquisition of a header for classifying the distribution destination information for each predetermined item.

In such a user information management method, it is possible to request the user information management means to acquire a headline by using a predetermined function.

The invention according to claim 10 is characterized in that the function requests acquisition of distribution destination information belonging to the index.

In such a user information management method, it is possible to request the user information management means to acquire the delivery destination information belonging to the headline by using a predetermined function.

Further, the invention according to claim 11 is characterized in that the function requests acquisition of the rank within the header of the distribution destination information belonging to the header.

In such a user information management method, it is possible to request the user information management means to obtain the rank of the delivery destination information belonging to the headline within the headline by using a predetermined function.

Further, the invention according to claim 12 is characterized in that the function requests acquisition of a management number of distribution destination information corresponding to a registration number inputted by a user.

In such a user information management method, it is possible to request the user information management means to acquire the management number of the distribution destination information corresponding to the registration number by using a predetermined function.

The invention according to claim 13 is characterized in that the function requests acquisition of a header to which the delivery destination information corresponding to the management number belongs.

In such a user information management method, it is possible to request the user information management means to acquire the headline to which the distribution destination information corresponding to the management number belongs by using a predetermined function.

The invention according to claim 14 is characterized in that the function requests acquisition of electronic mail destination information corresponding to the management number.

In such a user information management method, it is possible to request the user information management means to acquire the electronic mail destination information corresponding to the management number by using a predetermined function.

The invention according to claim 15 is characterized in that the function requests acquisition of sender authentication information corresponding to the management number.

In such a user information management method, it is possible to request the user information management means to acquire the sender authentication information corresponding to the management number by using a predetermined function.

The invention according to claim 16 is characterized in that the function requests acquisition of usage restriction information corresponding to the management number.

In such a user information management method, it is possible to request the user information management means to acquire the usage restriction information corresponding to the management number by using a predetermined function.

The invention according to claim 17 is characterized in that the function requests acquisition of electronic mail group information corresponding to the management number.

In such a user information management method, it is possible to request the user information management means to acquire the electronic mail group information corresponding to the management number by using a predetermined function.

Further, the invention according to claim 18 is characterized in that the function requests the retrieval of the delivery destination information according to the retrieval condition.

In such a user information management method, it is possible to request the user information management means to search the distribution destination information according to the search condition by using a predetermined function.

Further, in order to solve the above-mentioned problems, a first aspect of the present invention is provided.
According to a ninth aspect of the present invention, there is provided an image forming apparatus including at least one application for performing an image forming process, the storing means storing user information, and the user information from the storing means in response to a request from the application. And a user information management unit that supplies the acquired user information to the application that has made the request.

In such an image forming apparatus, the user information managing means acquires the user information corresponding to the request from the application from the storing means and supplies the user information to the requesting application so that the user information can be shared and the user information can be shared. Can be centrally managed.

In the invention according to claim 20, the user information management means determines a storage means in which the user information corresponding to a request from the application is stored, and stores the user information from the determined storage means. It is characterized by acquiring.

In such an image forming apparatus, it is possible to determine the storage means in which the user information corresponding to the request from the application is stored and acquire the user information from the determined storage means. The desired user information can be acquired even if the user information is sorted and stored in the.

Further, the invention according to claim 21 is characterized in that the user information management means is a process of a user information management service.

In such an image forming apparatus, the user information management means can be constituted by the process of the user information management service.

The invention according to claim 22 is characterized in that the user information includes distribution destination information and usage authority / billing information.

In such an image forming apparatus, the user information can be configured to include distribution destination information and usage authority / billing information.

Further, in the invention according to claim 23, the storage means stores the distribution destination information storage means storing the distribution destination information included in the user information, and the use authority / billing information included in the user information. It is characterized in that it includes a usage authority / billing information storage means.

In such an image forming apparatus, the storage means can be configured to include the distribution destination information storage means and the usage authorization / billing information storage means.

The invention according to claim 24 is characterized in that the user information management means is requested to acquire the user information from the application by a predefined function.

In such an image forming apparatus, the application can request the user information management means to acquire the user information by using the function defined in advance.

The invention according to claim 25 is characterized in that the function requests acquisition of the function information held by the user information management means.

In such an image forming apparatus, it is possible to request the user information managing means to acquire the function information possessed by the user information managing means by using a predetermined function. The function information represents the function of the user information management means.

The invention according to claim 26 is characterized in that the function requests an update notification to be notified when the user information is updated.

In such an image forming apparatus, an update notification can be requested to the user information management means by using a predetermined function.

Further, the invention according to claim 27 is characterized in that the function requests acquisition of a header for classifying the distribution destination information for each predetermined item.

In such an image forming apparatus, it is possible to request the user information managing means to acquire the headline by using a predetermined function.

The invention according to claim 28 is characterized in that the function requests acquisition of distribution destination information belonging to the headline.

In such an image forming apparatus, it is possible to request the user information managing means to acquire the delivery destination information belonging to the headline by using a predetermined function.

[0069] Further, the invention according to claim 29 is characterized in that the function requests acquisition of the rank in the header of the distribution destination information belonging to the header.

In such an image forming apparatus, it is possible to request the user information managing means to obtain the rank of the delivery destination information belonging to the headline in the headline by using a predetermined function.

Further, the invention according to claim 30 is characterized in that the function requests acquisition of the management number of the distribution destination information corresponding to the registration number inputted by the user.

In such an image forming apparatus, it is possible to request the user information management means to acquire the management number of the distribution destination information corresponding to the registration number by using a predetermined function.

Further, the invention according to claim 31 is characterized in that the function requests acquisition of a header to which the delivery destination information corresponding to the management number belongs.

In such an image forming apparatus, it is possible to request the user information managing means to acquire the headline to which the distribution destination information corresponding to the management number belongs, by using a predetermined function.

The invention according to claim 32 is characterized in that the function requests acquisition of electronic mail destination information corresponding to the management number.

In such an image forming apparatus, it is possible to request the user information management means to acquire the electronic mail destination information corresponding to the management number by using a predetermined function.

The invention according to claim 33 is characterized in that the function requests acquisition of sender authentication information corresponding to the management number.

In such an image forming apparatus, it is possible to request the user information managing means to acquire the sender authentication information corresponding to the management number by using a predetermined function.

Further, the invention according to claim 34 is characterized in that the function requests acquisition of use restriction information corresponding to the management number.

In such an image forming apparatus, it is possible to request the user information management means to acquire the usage restriction information corresponding to the management number by using a predetermined function.

The invention according to claim 35 is characterized in that the function requests acquisition of electronic mail group information corresponding to the management number.

In such an image forming apparatus, it is possible to request the user information management means to acquire the electronic mail group information corresponding to the management number by using a predetermined function.

Further, the invention according to claim 36 is characterized in that the function requests the retrieval of the delivery destination information according to the retrieval condition.

In such an image forming apparatus, it is possible to request the user information management means to search the distribution destination information according to the search condition by using a predetermined function.

The thirty-seventh aspect of the present invention is characterized by further comprising a control means for managing the hardware resources used in the image forming processing and an operating system.

Such an image forming apparatus can be configured to further include a control means and an operating system.

[0087]

BEST MODE FOR CARRYING OUT THE INVENTION Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the compound machine according to the present invention. The compound machine 1 is a black and white line printer 11
A color line printer 12, a hardware resource 13 such as a scanner or a facsimile, a software group 20, and a multi-function peripheral activation unit 50. The software group 20 is an application 30.
And a platform 40.

The platform 40 interprets a processing request from the application 30 to generate a hardware resource acquisition request, and manages one or more hardware resources to arbitrate the acquisition request from the control service. It has a system resource manager (hereinafter referred to as SRM) 43 and an operating system (hereinafter referred to as OS) 41.

The control service includes a system control service (hereinafter referred to as SCS) 42, an engine control service (hereinafter referred to as ECS) 44, and a memory control service (hereinafter referred to as MCS) 4
5, operation panel control service (hereinafter referred to as OCS) 46, fax control service (hereinafter referred to as FCS) 47, network control service (hereinafter referred to as NCS) 48, user information management service (hereinafter referred to as UCS) 49, etc. It is configured to have the above service modules.

The platform 40 is configured to have an application program interface (hereinafter referred to as API) that enables the processing request from the application 30 to be received by a predefined function.

The OS 41 is an operating system such as UNIX (registered trademark), and executes each software of the platform 40 and the application 30 as processes in parallel.

The SRM 43 process controls the system and manages resources together with the SCS 42. For example, the SRM 43 process includes an engine such as a scanner unit and a printer unit, a memory, a hard disk device (HDD) file, a host I / O (Centro interface, network interface, IEEE1).
Arbitration is performed and execution control is performed according to a request from an upper layer that uses hardware resources such as the 394 interface and the RS232C interface.

Specifically, the SRM 43 determines whether the requested hardware resource is available (whether it is not used by another request), and if it is available, the requested hardware resource is used. Notify upper layers that it is possible. Further, the SRM 43 schedules the use of hardware resources in response to a request from the upper layer, and directly executes request contents such as paper conveyance and image forming operation by the printer engine, memory reservation, and file generation.

The SCS 42 process includes application management, operation unit control, system screen display, LED display,
Performs resource management and interrupt application control.
The ECS 44 process controls the engines of the monochrome line printer 11, the color line printer 12, and the hardware resources 13.

The process of MCS 45 includes acquisition and release of image memory, use of hard disk device (HDD),
It compresses and decompresses image data. The process of OCS 46 controls the operation panel which is a means for transmitting information between the operator and the main body control.

The process of FCS 47 is performed by the PSTN or IS from each application layer of the system controller.
An application is provided for performing facsimile transmission / reception using a DN network, registration / quotation of various facsimile data managed by BKM (backup SRAM), facsimile reading, facsimile reception printing, and fusion transmission / reception.

The NCS 48 process uses the network I
It provides a service that can be used in common to applications that require I / O. When distributing the data received by each protocol from the network side to each application, or when transmitting the data from the application to the network side, Mediate.

The process of the UCS 49 manages user information, determines the storage device storing the user information according to the request, acquires the user information from the determined storage device, and supplies it to each application. To do.

Further, the application 30 performs processing unique to each user service related to image forming processing such as printer, copy, facsimile, and scanner. The application 30 includes a printer application 31 that is a printer application having a page description language (PDL, PCL) and Postscript (PS), a copy application 32 that is a copy application, and a fax application 33 that is a facsimile application. The scanner application 34 is a scanner application, the network file application 35 is a network file application, and the process inspection application 36 is a process inspection application.

The compound machine starting section 50 is first executed when the compound machine 1 is powered on, and starts the application 30 and the platform 40. For example, the multi-function peripheral activation unit 50 reads programs for control services and applications from a flash memory described later,
The read programs are transferred to a memory area secured on the SRAM or SDRAM and activated.

FIG. 2 is a hardware block diagram of an embodiment of the compound machine according to the present invention. The compound machine 1 of FIG. 2 has a controller board 60, an operation panel 70, and a fax control unit (hereinafter referred to as FCU).
80, a USB device 90, an IEEE 1394 device 100, and an engine unit 110. The FCU 80 has a memory. FC
The memory of U80 has,
It is used to temporarily store the facsimile data received at F.

The operation panel 70 is directly connected to the ASIC 62 of the controller board 60. In addition, FCU80, USB device 90, IEEE139
4 device 100 and engine unit 110 are connected to ASIC 62 of controller board 60 by PCI bus (Peripher
al Component Interconnect bus) etc. are connected.

The controller board 60 is a CPU
61, ASIC 62, SRAM (Static RAM) 63
, An SDRAM (Synchronous DRAM) 64, a flash memory 65, an HDD 66, and a network I / F controller 67. The controller board 60 includes a CPU 61, SRAM 63, SDR
The AM 64, the flash memory 65, the HDD 66, the network I / F controller 67, and the like are connected to the ASIC 62.

The CPU 61 controls the entire compound machine 1. The CPU 61 uses the OS 41 to form the platform 40 in SCS 42, SRM 43, ECS 4
4, MCS45, OCS46, FCS47 and NCS
The printer application 3 that starts and executes 48 as processes and forms the application 30.
1, to activate and execute the copy application 32, the fax application 33, the scanner application 34, the net file application 35, and the process inspection application 36.

The ASIC 62 is an IC for image processing applications having a hardware element for image processing. SRA
Virtual memory areas such as kernels and processes are mapped to the physical memory areas of the M63 and the SDRAM 64.

Flash memory 6 as nonvolatile RAM
5 is an application 30 or platform 4
Each application, control service, and SRM that make up 0
Each program such as 43 and usage restrictions / billing information are stored. The HDD 66 is a storage for accumulating image data, programs, font data, forms, and distribution destination information. The operation panel 70 is an operation unit that receives an input operation from an operator and displays a message for the operator.

Such a multi-function machine 1 is connected to, for example, another multi-function machine or a computer via a network.
Image information is distributed using the distribution function. The multi-function peripheral 1 equipped with the distribution function can distribute the distribution destination information and use restrictions /
It has billing information as user information. The multi-function peripheral 1 that does not have a distribution function has usage restriction / billing information as user information.

The user information management method of the present invention will be described below. FIG. 3 is a diagram for explaining the user information management method of the present invention. Flash memory 6
The usage restriction / billing information stored in 5 manages the availability of various functions and the number of usable functions, and is configured as shown in FIG. 4, for example.

FIG. 4 is a block diagram showing an example of usage restriction / billing information. The usage restriction / billing information in FIG. 4 includes data items such as a management number, a registration number, a user name, a user code, whether or not the copying function can be used, the number of times the copying function is used, whether or not the distribution function can be used, and the number of times the distribution function is used. . The usage restriction / billing information stored in the flash memory 65 is stored in the SCS42.
It is managed by the billing information management module 121 included in.

The flash memory 65 also stores management parameters for various services, modules, and applications, which are managed by the system initialization module 122 included in the SCS 42.

The distribution destination information stored in the HDD 66 manages the distribution destination and the sender.
For example, it is configured as shown in FIG. FIG. 5 shows a configuration diagram of an example of distribution destination information. The distribution destination information in FIG. 5 has data items such as a management number, a registration number, a user name, an electronic mail address, and sender availability. The distribution destination information stored in the HDD 66 is managed by the USC 49.

The UCS 49 directly manages the distribution destination information stored in the HDD 66, while managing the usage restriction / billing information stored in the flash memory 65 via the billing information management module 121.

In the case of the compound machine 1 having no distribution function, there is no distribution destination information stored in the HDD 66. UCS even if the multi-function machine 1 does not have a distribution function
49 manages the usage restriction / billing information stored in the flash memory 65 via the billing information management module 121, so that the interface can be unified regardless of the presence or absence of the distribution function.

Although FIG. 3 shows an example in which the usage restriction / billing information is stored in the flash memory 65 and the distribution destination information is stored in the HDD 66, the usage restriction / billing information or the distribution destination information is stored in the memory of the FCU 80. You may Further, a part of the usage restriction / billing information or the delivery destination information may be stored in the memory of the FCU 80.

Next, as an example of the application, the fax application 33 or the scanner application 34 uses the UCS4
An example in which user information is referred to via 9 will be described with reference to the drawings.

FIG. 6 is a diagram for explaining the user information reference processing. The fax application 33 and the scanner application 34 as clients are the UCS 49
Requests reference to user information using the API provided by.

The UCS 49 determines in which of the flash memory 65 and the HDD 66 the user information requested to be referenced by the fax application 33 or the scanner application 34 is stored. Then, the UCS 49 determines the flash memory 6 that has determined the user information for which the reference request has been made.
5 or HDD 66, and supplies the acquired user information to the fax application 33 or the scanner application 34.

Specifically, when the UCS 49 receives a distribution destination information reference request from the fax application 33 or the scanner application 34, it acquires the distribution destination information from the HDD 66 and supplies it to the fax application 33 or the scanner application 34. In addition, when the UCS 49 receives a usage restriction / accounting information reference request from the fax application 33 or the scanner application 34, the UCS 49 acquires the usage restriction / accounting information from the flash memory 65 via the accounting information management module 121 and acquires the fax application 33 or scanner. Supply to the application 34.

As described above, the fax application 33 and the scanner application 34 can acquire the user information from the UCS 49 without designating the storage location of the user information desired to be referred. The processing for the fax application 33 and the scanner application 34 to start using the UCS 49 is as follows.

First, the UCS 49 as a server creates a request waiting thread, opens a socket and waits for a request. Further, the fax application 33 and the scanner application 34 as clients create an event waiting thread, open a socket to wait for an event, and perform usage registration through the opened socket of the UCS 49.

Requests from the fax application 33 and the scanner application 34 perform interprocess communication through the socket of the UCS 49, and an event from the UCS 49 performs interprocess communication through the sockets of the fax application 33 and the scanner application 34.
Fax application 33, scanner application 34 and UC
The cooperative operation with S49 is realized.

Next, as an example of a process in which the fax application 33 or the scanner application 34 refers to the user information, a process in which the scanner application 34 displays the delivery destination information on the operation panel 70 will be described with reference to the drawings. FIG. 7 shows a flowchart of an example of a process of referring to the distribution destination information.

In step S10, the scanner application 34
Uses UCS49 specifications information in UCS49
The specification information acquisition process to be acquired from is performed. What is specification information?
It is information of various elements of the UCS 49 itself, and is composed of built-in information of the UCS 49 and the billing information management module 121 and setting parameter information. Details of the specification information acquisition process will be described later.

In step S11 following step S10, the scanner application 34 determines an available function from the obtained specification information and determines the function to be used by using the API.
Use function registration processing to be registered in the CS 49 is performed. In this way, if the function to be used is registered in the UCS 49, the scanner application 34 will use the UCS 49 when the user information is updated.
You will receive update notifications from.

For example, when the e-mail destination information is a usable function, the scanner application 34 registers it in the UCS 49 as a function of using the e-mail destination information. Then,
The scanner application 34 will receive the update notification from the UCS 49 when the email destination information is updated. The details of the use function registration process will be described later.

In step S12 following step S11, the scanner application 34 performs heading set information and heading information acquisition processing for acquiring heading set information and heading information from the UCS 49 using the API.

FIG. 8 shows an image diagram of an example of a set of headings and headings. In FIG. 8, the headline set 122 and the headline 123 are additional information in consideration of the user interface. The heading set 122 is, for example, “regular”,
It is an ordered set of headings 123 such as “A”, and holds information of the heading to which it belongs. Further, the headline 123 is a labeled set of an ordered set of entries, which will be described later, and holds the label and information of the entry to which it belongs.

[0129] Of the headings 123, "usually used" is a special heading belonging to all heading sets. "Regular use"
Other headings 123 do not belong to a plurality of heading sets.
Details of the heading set information and the heading information acquisition processing will be described later.

In step S13 following step S12, the scanner application 34 performs an entry list information acquisition process for acquiring a list of entries belonging to the selected heading from the UCS 49 using the API.

FIG. 9 shows an image diagram of an example of an entry. In FIG. 9, one or more entries 125 constituting the list 124 of entries are roughly classified into accounts corresponding to individual users and groups corresponding to the listed accounts. The details of the entry list information acquisition process will be described later.

In step S14 following step S13, the scanner application 34 creates an entry selection screen as shown in FIG. 10 and displays it on the operation panel 70. FIG. 10 shows an image diagram of an example of the entry selection screen.

The entry selection screen of FIG. 10 can be created by using a list of headings, headings, and entries belonging to the headings. The entry selection screen of FIG. 10 distinguishes an account from a group by attaching an icon with three people lined up to an entry button representing a group.

Progressing to step S15 following step S14, the scanner application 34 determines whether or not an entry has been selected from the entry selection screen. If it is determined that the entry has been selected (YES in S15), the scanner application 34 proceeds to step S16. On the other hand, when it is determined that the entry is not selected (NO in S15), the scanner application 34 proceeds to step S17.

In step S16, the scanner application 34
However, the AP will enter the detailed entry information of the selected entry.
After performing the detailed entry information acquisition processing for acquiring from the UCS 49 using I, the process proceeds to step S17. For example, the scanner application 34 displays the acquired detailed entry information in the information display field 127 of the entry selection screen of FIG.

In step S17, the scanner application 34
However, it is determined whether another headline is selected from the entry selection screen. When it is determined that another headline is selected (YES in S17), the scanner application 34 proceeds to step S13. On the other hand, when it is determined that another headline is not selected (NO in S17), the scanner application 34 proceeds to step S18.

In step S18, the scanner application 34
Determines whether the update notification is received from the UCS 49. If it is determined that the update notification has been received (YES in S18), the scanner application 34 proceeds to step S12. On the other hand, if it is determined that the update notification has not been received (S
18, NO), the scanner application 34 is step S
Proceed to 15.

Further, the processing of the flowchart of FIG. 7 will be described in detail with reference to the drawings. FIG. 11 shows a flowchart of an example of the specification information acquisition process of step S10. In step S21, the scanner application 34 uses the API for obtaining the specification information to request the specification information from the UCS 49. FIG. 12 is an API for acquiring specification information.
The block diagram of an example is shown.

In step S22 following step S21, the UCS 49 supplies the scanner application 34 with a copy of the specification information created in advance. In addition, UCS49
Creates specification information from the built-in information, management parameters, device configuration information, and charging information specifications acquired from the charging information management module 121. Billing information management module 121
Sets billing information specifications from built-in information, management parameters, and device configuration information.

FIG. 13 is a block diagram showing an example of the specification information. The specification information shown in FIG. 13 includes data items such as service version, available functions, and maximum number of registered entries. The service version is UCS 49 built-in information. The available function is UCS49 from the device configuration information.
Is determined and created, and represents, for example, the presence or absence of billing information and the presence or absence of e-mail destination information. The maximum entry registration number is a management parameter of the UCS 49 and represents the maximum entry registration number. Entry is delivery address, sender,
It has a name, a management number, etc. as information in the minimum unit such as a chargeable user.

Next, the use function registration process of step S11 will be described. FIG. 14 shows a flowchart of an example of the used function registration processing in step S11. Step S
In 31, the scanner application 34 determines an available function from the specification information acquired in step S22.

In step S32 following step S31, the scanner application 34 selects a function to be used from the available functions determined in step S31. Step S
After 32, the process proceeds to step S33, and the scanner application 3
Step 4 uses the API for registering the function to be used, and step S
It requests the UCS 49 to register the function selected in 32. FIG. 15 is a block diagram of an example of an API that performs usage function registration.

In step S34 following step S33, the UCS 49 requests the scanner application 34 which has requested registration.
And the registered function are stored in association with each other. Step S3
When the process of 4 is completed, the UCS 49 will supply the update notification to the scanner application 34 when the user information is updated.

Therefore, the scanner application 34 can know that the user information has been updated by receiving the update notification, and can reacquire the user information when the user information is updated.

Next, the heading set information and heading information acquisition processing in step S12 will be described. 16
The flow chart of an example of heading set information and heading information acquisition processing of Step S12 is shown.

In step S41, the scanner application 34
UCS4 using API to get heading set information
9 request all heading set information. FIG. 17 is a block diagram showing an example of an API for acquiring the headline set information.

In step S 42 following step S 41, the UCS 49 supplies all heading set information to the scanner application 34. FIG. 18 is a block diagram showing an example of the headline set information. The heading set information in FIG. 18 includes data items such as a heading set management number, the number of headings to which it belongs, and headings to which it belongs. The heading to which it belongs represents an array of heading management numbers.

In step S43 following step S42, the scanner application 34 selects a heading set and a heading according to the heading set and the specified value of the heading as the management parameters.

After step S43, the process proceeds to step S44, at which the scanner application 34 acquires the heading information.
Using I, the UCS 49 is requested to obtain all the header information of the header set selected in step S43. FIG. 19 shows
The block diagram of an example of API which acquires heading information is shown.

In step S45 following step S44, the UCS 49 reads the headline information from the HDD 66 and supplies it to the scanner application 34. FIG. 20 shows a configuration diagram of an example of the headline information. The headline information in FIG. 20 includes data items such as a headline management number, a headline type, and a label. The heading type identifies whether or not it is a regular item.

Next, the entry list information acquisition process of step S13 will be described. FIG. 21 shows step S1.
The flowchart of an example of the entry list information acquisition process of 3 is shown.

In step S51, the scanner application 34
Requests the UCS 49 for the list information of the entries belonging to the headline selected in step S43, using the API for obtaining the list information of the entries. FIG. 22 shows
The block diagram of an example of API which acquires the list information of an entry is shown.

In step S52 following step S51, the UCS 49 displays the entry list information in the HDD 66.
It is read from and supplied to the scanner application 34. FIG. 23
Shows a configuration diagram of an example of entry list information. Figure 2
The list information of the entry 3 includes data items such as entry management number, entry registration number, entry type, and user name. The entry registration number is a number stored by the user. The entry type indicates whether or not it becomes a distribution destination, whether or not it becomes a sender, and whether or not the account is a group.

In step S52, it is not always necessary to acquire all the entries belonging to the headline, and only the entries displayed on one screen of the operation panel 70 may be acquired. Further, the filter information may be designated, such as only entries having an e-mail address or entries that can be senders.

Next, the processing when the entry registration number is entered in the direct entry field 126 of the entry selection screen of FIG. 10 will be described. FIG. 24 shows a flowchart of an example of the entry registration number input process.

In step S61, the scanner application 34
Uses the API to obtain the entry management number from the entry registration number, and uses the API to obtain the entry management number corresponding to the entry registration number directly entered in the input field 126.
Obtain from CS49. FIG. 25 is a block diagram of an example of an API that acquires an entry management number from an entry registration number.

Progressing to step S62 following step S61, the scanner application 34 uses the API for acquiring the heading to which the entry belongs from the entry management number to find the heading to which the entry belongs from the entry management number acquired in step S61. Obtained from UCS49. FIG. 26 is a block diagram of an example of an API that acquires the heading to which an entry belongs from the entry management number.

Progressing to step S63 following step S62, the scanner application 34 determines whether or not the currently selected headline set includes the headline acquired in step S62.

When the heading acquired in step S62 is included in the currently selected heading set (YES in S63), the scanner application 34 proceeds to step S64 and selects the heading currently selected among the headings acquired in step S62. Select one of the headings included in the set.
When there are a plurality of headings included in the currently selected heading set among the headings acquired in step S62, one heading is selected based on an appropriate criterion (for example, the heading management number is the smallest).

On the other hand, if the headline acquired in step S62 is not included in the currently selected headline set (S63).
, NO), the scanner application 34 is step S65.
Go to and select one heading set and one heading based on appropriate criteria.

Progressing to step S66 following step S64 or step S65, the scanner application 34 uses the API for acquiring the list of entries belonging to the headline selected in step S64 or step S65 by using the API for acquiring the entry list information. To get from. And
The scanner application 34 creates an entry selection screen as shown in FIG. 10 by using the acquired list of entries and displays it on the operation panel 70.

In step S66, if the order of the entries belonging to the headline is known, the following efficient processing becomes possible. For example, if the number of entries displayed on one screen of the operation panel 70 is 12 and the rank of the desired entry belonging to the heading is 20th, 13
It suffices to obtain a list of entries including 12 entries from the second entry.

The scanner application 34 acquires the rank of the entry belonging to the heading from the UCS 49 using the API for acquiring the entry rank. FIG. 27 is a block diagram of an example of the API for acquiring the entry rank.

As described above, A for obtaining the entry ranking
By using the PI, it is possible to avoid the trouble of acquiring 12 entries from the beginning and checking whether or not the acquired entry includes a desired entry.

The UCS 49 can also provide the following API. FIG. 28 is a block diagram showing an example of an API for acquiring mail information. The scanner application 34 can acquire mail information such as an electronic mail address from the UCS 49 using the API for acquiring mail information.

FIG. 29 is an AP for acquiring sender authentication information.
The block diagram of an example of I is shown. The scanner application 34 acquires the sender authentication information from the UCS 49 using the API that acquires the sender authentication information. The sender authentication information is, for example, a password and is used to identify the sender.

FIG. 30 is an AP for acquiring user restriction information.
The block diagram of an example of I is shown. The scanner application 34 acquires the user restriction information from the UCS 49 by using the API for acquiring the user restriction information. It should be noted that the user restriction information is a string of flags indicating the prohibition of subdivided functions such as use prohibition, color prohibition, black and white prohibition.

FIG. 31 is a block diagram showing an example of an API for acquiring electronic mail group information. Scanner application 34
Acquires e-mail group information from the UCS 49 using the API for acquiring e-mail group information.
The electronic mail group information is information such as the number of accounts to which the user belongs and the accounts to which the user belongs.

FIG. 32 is a block diagram showing an example of API for retrieving an entry. The scanner application 34 causes the UCS 49 to search for an entry using the API for searching for an entry. In addition, the search of the entry is prefix match,
You can use search conditions such as trailing match and partial match.

In the user information reference process shown in FIG. 6, the fax application 33 or the scanner application 34 is used.
Although the example has been described in which the screen displayed on the operation panel 70 is created, a screen creation module for creating the screen displayed on the operation panel 70 may be separately provided.

FIG. 33 is a diagram for explaining the processing of the screen creation module. The screen creation module 130 included in the SCS 42 creates a screen to be displayed on the operation panel 70 in response to a request from the fax application 33 or the scanner application 34.

As described above, by separately providing the screen creating module 130, the screen creating function is provided by the fax application 3.
3 and the scanner application 34 need not be prepared,
The screen creation function can be shared.

As described above, the fusion machine 1 according to the present invention is U
By installing CS49, fax application 33,
User information can be shared by a plurality of applications such as the scanner application 34, and the user information is stored in the flash memory 65 or H.
It is no longer necessary for the application to consider in which of the DDs 66 the data is stored.

Although the UCS 49 is included in the control service in the configuration diagram of FIG. 1, the present invention is not limited to this example. For example, UCS49 uses application 3
It may be included in 0. Further, in FIG. 6 and the like, the fax application 33 and the scanner application 34 are the UCS4
Although an example of requesting reference of user information by using the API provided by No. 9 is shown, the present invention is not limited to this example. For example, the control service may request the reference of the user information by using the API provided by the UCS 49.

[0175]

As described above, according to the present invention, the user information managing means acquires the user information according to the request from the application and supplies it to the requesting application, so that the user information can be shared and the user information can be shared. Information can be centrally managed.

[0176]

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of a compound machine according to the present invention.

FIG. 2 is a hardware configuration diagram of an embodiment of the compound machine according to the present invention.

FIG. 3 is a diagram for explaining a user information management method of the present invention.

FIG. 4 is a configuration diagram of an example of usage restriction / billing information.

FIG. 5 is a configuration diagram of an example of distribution destination information.

FIG. 6 is a diagram illustrating a user information reference process.

FIG. 7 is a flowchart of an example of a process of referring to distribution destination information.

FIG. 8 is an image diagram of an example of a set of headings and headings.

FIG. 9 is an image diagram of an example of an entry.

FIG. 10 is an image diagram of an example of an entry selection screen.

FIG. 11 is a flowchart of an example of specification information acquisition processing in step S10.

FIG. 12 is a configuration diagram of an example of an API that acquires specification information.

FIG. 13 is a configuration diagram of an example of specification information.

FIG. 14 is a flowchart of an example of a used function registration process in step S11.

FIG. 15 is a block diagram of an example of an API for performing use function registration.

FIG. 16 is a flowchart of an example of the heading set information and heading information acquisition processing in step S12.

FIG. 17 is a configuration diagram of an example of an API for acquiring heading set information.

FIG. 18 is a configuration diagram of an example of heading set information.

FIG. 19 is a block diagram of an example of an API for acquiring heading information.

FIG. 20 is a configuration diagram of an example of heading information.

FIG. 21 is a flowchart of an example of entry list information acquisition processing in step S13.

FIG. 22 is a configuration diagram of an example of an API that acquires entry list information.

FIG. 23 is a configuration diagram of an example of entry list information.

FIG. 24 is a flowchart of an example of an entry registration number input process.

FIG. 25 is a block diagram of an example of an API that acquires an entry management number from an entry registration number.

[Fig. 26] Fig. 26 is a configuration diagram of an example of an API for acquiring a heading to which an entry belongs from an entry management number.

FIG. 27 is a configuration diagram of an example of an API for acquiring an entry rank.

FIG. 28 is a block diagram of an example of an API for acquiring mail information.

FIG. 29 is a configuration diagram of an example of an API for acquiring sender authentication information.

FIG. 30 is a block diagram of an example of an API for acquiring user restriction information.

FIG. 31 is a configuration diagram of an example of an API for acquiring electronic mail group information.

FIG. 32 is a configuration diagram of an example of an API for searching for an entry.

FIG. 33 is a diagram for explaining the processing of the screen creation module.

[Explanation of symbols]

1 Fusion Machine 11 Monochrome Line Printer 12 Color Line Printer 13 Hardware Resources 20 Software Group 30 Application 40 Platform 41 Operating System (OS) 42 System Control Service (SCS) 43 System Resource Manager (SRM) 44 Engine Control Service (ECS) 45 Memory control service (MCS) 46 Operation panel control service (OCS) 47 Fax control service (FCS) 48 Network control service (NCS) 49 User information management service (UCS) 50 Multifunction machine startup unit 60 Controller board 61 CPU 62 ASIC (Application) Specific Integrated
Circuit 63 SRAM (Static RAM) 64 SDRAM (Synchronous DRAM) 65 Flash memory 66 Hard disk device (HDD) 67 Network I / F controller 70 Operation panel 80 Fax control unit (FCU) 90 USB device 100 IEEE 1394 device 110 Engine unit 121 Billing Information management module 122 Headline set 123 Headline 124 List of entries 125 Entry 126 Direct input field 127 Information display field 130 Screen creation module

─────────────────────────────────────────────────── ─── Continuation of front page (51) Int.Cl. ⁷ Identification code FI theme code (reference) G06F 3/12 H04N 1/44 H04N 1/32 G03G 21/00 390 1/44 392 F term (reference) 2C061 AP07 HJ08 HJ10 HX10 2H027 EE07 EE08 EJ04 EJ06 EJ08 ZA07 5B021 AA01 AA05 AA19 CC05 NN00 NN18 5C062 AA05 AA14 AA16 AB11 AB21 AB41 AB42 AF02 5C075 BA05 EE90

Claims (37)

[Claims] 1. A user information management method for an image forming apparatus having at least one application for performing an image forming process, wherein the application requests the user information management means to acquire user information, and The user information management means acquires the user information according to the request from the application, and supplies the acquired user information to the application that has made the request, the user information management method. 2. The user information management method according to claim 1, wherein in the supplying step, the user information management means acquires user information in response to a request from an application from the storage means. 3. In the supplying step, the user information management means determines a storage means that stores user information in response to a request from an application, and acquires the user information from the determined storage means. The user information management method according to claim 2. 4. The user information management method according to claim 1, wherein the user information includes distribution destination information and usage authority / billing information. 5. The storage means includes distribution destination information storage means for storing the distribution destination information and usage authority / charging information storage means for storing the usage authority / billing information. 4. The user information management method described in 4. 6. The requesting step, wherein the application requests the user information managing means to acquire the user information by a predefined function.
5. The user information management method according to any one of 5 to 5. 7. The user information management method according to claim 6, wherein the function requests acquisition of function information possessed by the user information management means. 8. The user information management method according to claim 6, wherein the function requests an update notification to be notified when the user information is updated. 9. The user information management method according to claim 6, wherein the function requests acquisition of a header for classifying the distribution destination information for each predetermined item. 10. The user information management method according to claim 9, wherein the function requests acquisition of distribution destination information belonging to the headline. 11. The user information management method according to claim 9, wherein the function requests acquisition of the rank of the distribution destination information belonging to the headline within the headline. 12. The user information management method according to claim 6, wherein the function requests acquisition of a management number of distribution destination information corresponding to a registration number input by a user. 13. The user information management method according to claim 12, wherein the function requests acquisition of a header to which the distribution destination information corresponding to the management number belongs. 14. The user information management method according to claim 12, wherein the function requests acquisition of electronic mail destination information corresponding to the management number. 15. The user information management method according to claim 12, wherein the function requests acquisition of sender authentication information corresponding to the management number. 16. The user information management method according to claim 12, wherein the function requests acquisition of usage restriction information corresponding to the management number. 17. The user information management method according to claim 12, wherein the function requests acquisition of electronic mail group information corresponding to the management number. 18. The user information management method according to claim 6, wherein the function requests a search for distribution destination information according to a search condition. 19. An image forming apparatus having at least one application for performing an image forming process, comprising: storing means for storing user information; and obtaining user information from the storing means in response to a request from the application. The image forming apparatus further includes a user information management unit that supplies the acquired user information to the application that has made the request. 20. The user information management means determines a storage means that stores user information in response to a request from the application, and acquires user information from the determined storage means. 19. The image forming apparatus according to item 19. 21. The image forming apparatus according to claim 19, wherein the user information management means is a process of a user information management service. 22. The user information includes distribution destination information and usage authority / billing information.
The image forming apparatus according to any one of 9 to 21. 23. The storage means stores a distribution destination information storage means for storing distribution destination information included in the user information, and a use authority / charge information storage means for storing use authority / charge information included in the user information. 23. The image forming apparatus according to claim 22, further comprising: 24. The image forming apparatus according to claim 19, wherein the user information management unit is requested to acquire the user information from the application by a predefined function. 25. The image forming apparatus according to claim 24, wherein the function requests acquisition of function information held by the user information management unit. 26. The image forming apparatus according to claim 24, wherein the function requests an update notification to be notified when the user information is updated. 27. The image forming apparatus according to claim 24, wherein the function requests acquisition of an index for classifying the distribution destination information for each predetermined item. 28. The image forming apparatus according to claim 27, wherein the function requests acquisition of distribution destination information belonging to the headline. 29. The image forming apparatus according to claim 27, wherein the function requests acquisition of a rank of delivery destination information belonging to the heading within the heading. 30. The image forming apparatus according to claim 24, wherein the function requests acquisition of a management number of distribution destination information corresponding to a registration number input by a user. 31. The image forming apparatus according to claim 30, wherein the function requests acquisition of a header to which the distribution destination information corresponding to the management number belongs. 32. The image forming apparatus according to claim 30, wherein the function requests acquisition of electronic mail destination information corresponding to the management number. 33. The image forming apparatus according to claim 30, wherein the function requests acquisition of sender authentication information corresponding to the management number. 34. The image forming apparatus according to claim 30, wherein the function requests acquisition of usage restriction information corresponding to the management number. 35. The image forming apparatus according to claim 30, wherein the function requests acquisition of electronic mail group information corresponding to the management number. 36. The image forming apparatus according to claim 24, wherein the function requests a search for distribution destination information according to a search condition. 37. The image forming apparatus according to claim 19, further comprising a control means for managing hardware resources used in the image forming processing, and an operating system.