JP6950343B2 - Operation unit, reader, program - Google Patents

Description

The present invention relates to an operating unit , a reading device, and a program.

When a user uses a device or service, an operation called authentication may be required. Authentication refers to the work of confirming whether or not a user is the person himself / herself when the user uses a resource on an information processing device or a network. Authentication allows users to receive appropriate services for themselves and prevents unauthorized persons from using information processing devices and resources.

It is being studied to improve operability and convenience by using authentication. For example, authentication may be required when using a multifunction device in an office, and a technique for providing appropriate information to the multifunction device using this authentication has been devised (see, for example, Patent Document 1). .). Patent Document 1 includes a program that receives the first data according to the storage of authentication information, receives the second data according to the fact that the authentication information is not stored, and changes the data to be displayed. It is disclosed.

However, the conventional technique has a problem that the presence or absence of display parts cannot be appropriately controlled according to the authentication status. For example, there may be a case where you want to display a display component that terminates the application on the screen of the application, but there is a display component (logout button) that is conventionally displayed when the user is authenticated, and this display component and the application are terminated. Appropriate control of the display of display components was not performed.

In view of the above problems, an object of the present invention is to provide an information processing device capable of controlling the presence or absence of display components according to the authentication status.

The present invention is an operation unit of the reading device that communicates with the main body of the reading device that can set whether or not authentication is required when accepting an operation, and when a program is started by the operation unit, the reading device Authentication setting information for acquiring authentication setting information including whether or not authentication is required from an authentication management means that manages whether or not authentication is required and whether or not the user has obtained authentication for using the reader. Setting information set to synchronize with the acquisition means, the user information registered in the information processing device communicating via the network, or the user information managed by the reading device. When the storage means and the authentication setting information are set to require authentication and the user has been authenticated, the first display component for terminating the program is displayed on the display device of the reader. However, when the authentication setting information is not set to require authentication and the user has not obtained the authentication, the screen display means for displaying the first display component on the display device and the user authenticate. Information on whether or not the user has obtained the authentication is obtained from the authentication management means, and when the user has obtained the authentication, a second display component for logging out from the reading device is displayed on the display device, and the user can display the information. The screen display means includes a component display means that does not display the second display component on the display device when the authentication is not obtained, and the screen display means refers to the setting information and displays a third display related to the user information. When the display / non-display of the component is switched and the component display means displays the second display component, the screen display means does not display the first display component, and the component display means displays the second display component. When the display component is not displayed, the screen display means displays the first display component, and the first display component and the second display component are not displayed at the same time .

It is possible to provide an information processing device that can control the presence / absence of display components according to the authentication status.

This is an example of a diagram explaining the inconvenience caused by the menu screen created by the conventional receipt application. It is an example of the figure explaining the menu screen of this embodiment. This is an example of a schematic configuration diagram of an information registration system. It is a figure which shows an example of the hardware composition of a multifunction device. This is an example of a hardware configuration diagram of a registration server, a management server, or a user terminal. It is a schematic diagram which shows an example of the software structure of a multifunction device. This is an example of a diagram for explaining the functional configuration of the multifunction device. It is a figure which shows an example of the authentication setting screen displayed by the screen control application for an authentication setting application. This is an example of a functional block diagram of a multifunction device, a registration server, a management server, and a user terminal of an information registration system. It is a figure explaining the transition example of the screen which the multifunction device displays on the operation panel. This is an example of a sequence diagram for explaining a procedure for a user to operate an operation unit to set an authentication. This is an example of a sequence diagram explaining the procedure for the user to log in to the multifunction device and start the receipt application. It is a figure which shows an example of a lock screen and a home screen. It is a figure which shows an example of an OS generation screen and a login screen. This is an example of a diagram illustrating the relationship between the person and the agent. This is an example of a sequence diagram showing the procedure for communicating with the management server by starting the receipt application. This is an example of a sequence diagram showing a procedure in which a multifunction device registers electronic data of a receipt in a management server. This is an example of a sequence diagram showing a procedure in which a multifunction device registers electronic data of a receipt in a management server. It is a figure which shows an example of a new report creation screen, a scan screen. It is a figure which shows an example of the scanning screen and the receipt analysis result screen. It is an example of the figure explaining the inconvenience solved by the second embodiment. It is a figure which shows an example of the menu screen setting screen for the user to set the screen at the time of starting an application. This is an example of a sequence diagram showing a procedure for the receipt application to change the configuration of the menu screen using the role setting. This is an example of a sequence diagram showing a procedure for the receipt application to change the configuration of the menu screen using the role setting. It is a figure which shows an example of the menu screen according to a role setting. This is an example of a diagram illustrating a screen displayed by the display control unit when the administrator setting button is pressed. It is a figure which shows an example of an administrator authentication screen and an administrator setting screen.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

<Inconvenience based on the conventional screen example>
FIG. 1 is an example of a diagram for explaining the inconvenience caused by the menu screen 441 created by the conventional receipt application. First, when the user uses the multifunction device 9, he / she may log in to the multifunction device 9. The user logs in and then launches the receipt app.

As shown in FIG. 1A, when the user logs in, a logout button 502 for the user to "log out" is displayed in the OS column 501 on the upper side of the menu screen 441. In addition, the home button 503 is displayed in the lower OS column 501. The multifunction device 9 operates as follows.
-When the logout button 502 is pressed, a program on the system side such as the OS (Operating System) cancels the authentication given to the user that the multifunction device 9 can be used, and erases the data used by the receipt application from the memory. In addition, a lock screen for the user to log in to the multifunction device 9 is displayed.
-When the home button 503 is pressed, a program on the system side such as the OS displays the home screen while leaving the data used by the receipt application in the memory. The next time the receipt app is launched, the receipt app will erase the data remaining in memory.

Therefore, when the home button 503 is pressed, the data remains in the memory, and it is not easy for a third party to retrieve the data, but the possibility remains. For example, if it is not necessary to log in to the multifunction device 9, there is a possibility that a third party will retrieve the data. The user should press the logout button 502, but there may be a case where a user who is supposed to press the home button 503 presses the home button 503.

Therefore, as shown in FIG. 1 (b), it is considered to provide an end button 446 in the receipt application. In FIG. 1B, the end button 446 is displayed on the upper right of the menu screen 441. The receipt app works as follows.
-When the end button 446 is pressed The receipt application erases the data used by the user from the memory and ends, and the system-side program such as the OS displays the home screen.

Therefore, when the user terminates the receipt application, the above inconvenience can be resolved by pressing the exit button 446. Since the end button 446 is a button for the multifunction device 9 to terminate the receipt application and erase the data from the memory, the multifunction device 9 can return to the home screen without leaving the data in the memory.

However, on the menu screen 441 of FIG. 1B, when it is necessary to log in to the multifunction device 9, two buttons having similar functions, the logout button 502 and the end button 446, are displayed, which is another inconvenience. Bring. There is a risk that the user may get lost in the operation, and it cannot be said that it is preferable in terms of design.

<Outline of the menu screen of this embodiment>
Conventionally, the multifunction device 9 has a setting item called an authentication setting set by the administrator of the multifunction device 9. The authentication setting is a button for the administrator to set, for example, whether or not login is required when the user uses the multifunction device 9. When the authentication setting is ON, the multifunction device 9 cannot be used unless the user logs in. When the authentication setting = OFF, the multifunction device 9 can be used without the user logging in. The multifunction device 9 of the present embodiment controls the display / non-display of the end button 446 by using the authentication setting.

FIG. 2 is an example of a diagram illustrating the menu screen 441 of the present embodiment. FIG. 2A shows a menu screen 441 when the authentication setting of the multifunction device 9 is set to ON. When the authentication setting is ON, the multifunction device 9 does not display the end button 446. Therefore, the user can terminate the receipt application by pressing the logout button 502 or the home button 503. When the home button 503 is pressed, data remains in the memory, but since the authentication setting is ON, the next user cannot use the multifunction device 9 unless he / she logs in, and the possibility of data leakage can be reduced.

FIG. 2B shows a menu screen 441 when the authentication setting of the multifunction device 9 is set to OFF. When the authentication setting is OFF, the multifunction device 9 displays the end button 446. Also, since the authentication setting is OFF (the user never logs in), the OS does not display the logout button 502. Therefore, the user will press the explicitly indicated end button 446 instead of the home button 503, and the receipt application can be reliably terminated.

As shown in FIG. 2, the logout button 502 and the end button 446 are not displayed at the same time on the menu screen 441 of the present embodiment regardless of whether the authentication setting is ON or OFF. Therefore, it is possible to prevent the user from getting lost in the operation and deteriorating the design.

<Terminology>
The display component is a part of the elements that make up the screen. It does not necessarily have to be clearly and independently displayed, and may be in contact with other display components. Further, the display component may or may not be a target of being pressed by the user. The display parts that are not the target of pressing are characters and icons that present the operation method.

Similar functions of display components means that similar situations can be realized with two display components. For example, the logout and exit buttons have different internal processes, but the user cannot use the receipt app.

As an example, the first display component is, for example, an end button, and the second display component is, for example, a logout button. The third display component is, for example, an administrator setting button.

A display component related to a program is a display component that affects the operation of the program. For example, it includes changing the user interface according to the authentication setting, and includes not displaying the display component of a predetermined function. In this embodiment, when the authentication setting is ON, the end button is not displayed.

<System configuration example>
FIG. 3 shows an example of a schematic configuration diagram of the information registration system 100 of the present embodiment. The information registration system 100 mainly includes a multifunction device 9, a registration server 30, a management server 40, and a user terminal 50. Since the information registration system 100 includes a function of analyzing information, it may be referred to as an information analysis system. Further, it may be referred to as an image processing system for performing image processing, or may be referred to as an authentication system for performing authentication. The information registration system 100 analyzes the read data and displays the analysis result on a display device such as the multifunction device 9.

The multifunction device 9 and the registration server 30 are connected to each other via the network 8, the registration server 30 and the management server 40 can communicate with each other, and the user terminal 50 can communicate with the management server 40. Actually, the multifunction device 9, the registration server 30, the management server 40, and the user terminal 50 are connected to the network 8, but the connection with the network 8 is omitted for the purpose of explaining the configuration. Further, the management server 40 is expected to provide a service as a so-called cloud service. The registration server 30 plays a role of mediating between the multifunction device 9 which is the entrance of the receipt and the management server 40 which is the exit thereof, and can correspond to the receipt management service provided by each of a plurality of vendors. be. Similarly, it is possible to support the multifunction device 9 sold by a plurality of vendors.

The network 8 connecting the multifunction device 9 and the registration server 30 is a LAN installed in the facility where the multifunction device 9 is installed, a wide area Ethernet (registered trademark), a WAN in which a plurality of LANs are connected by a router or the like. In addition, it may be via the Internet. The network 8 may be constructed either wired or wireless, and may be a combination of wired and wireless. Further, in the case of wireless, a network of communication standards such as 3G, 4G or LTE may be included.

The multifunction device 9 is a reading device that optically reads a document and generates image data. Such a device is called a scanner or a scanner device. The reason why the multifunction device 9 includes the character "composite" is that it may have a function other than the function of the reading device. The multifunction device 9 may be called an MFP (Multi-Function Peripherals). That is, the multifunction device 9 further has a printer function for forming an image on a print medium such as paper, a copy function realized by a scanner and a printer function, and a fax function realized by a scanner and a telephone line (or a network). You may be doing it. Further, the multifunction device 9 may be called an image forming apparatus, a printer, a copying machine, a copier, a fax apparatus, or the like due to these functions.

The multifunction device 9 of the present embodiment preferably has a function of capturing a plurality of receipts at once, and in this sense, a document camera, a digital camera, a Web camera, etc. mainly used in a video conference are used as books. The device may have a function equivalent to the function provided by the multifunction device 9 with respect to the invention. Further, a PC (Personal Computer) equipped with a digital camera or connected to an external digital camera may be used.

The multifunction device 9 has an operation panel, which will be described later, and displays electronic data of a receipt or the like on the operation panel. The operation panel has functions such as a touch panel and a keyboard for accepting editing of electronic data, and a display or a display device.

The multifunction device 9 has a main body and an operation unit, which will be described later, and an application can be mounted on each of them. In the present embodiment, the operation unit is equipped with an application (hereinafter, referred to as a receipt application) that cooperates with the registration server 30 in order to register image data of a plurality of receipts in the management server 40. However, the receipt application may be installed in the main body 10.

The registration server 30 is an information processing device that registers electronic data of receipts in the management server 40. That is, the registration server 30 trims each receipt from the image data of the plurality of receipts, performs character recognition processing, and transmits the electronic data of the receipts to the multifunction device 9. When the user confirms the content and presses the send button described later, the registration server 30 receives the electronic data of the receipt excluding the image and sends it to the management server 40 together with the user's e-mail address (information that identifies the user).

The management server 40 is an information processing device that manages electronic data of receipts. The management server 40 takes a management form in which individual users are managed in association with the administrator. The administrator can register individual users based on the administrator authority, and has the execution authority for a predetermined process for each registered user as described later. That is, the administrator can use the management server 40 with administrator privileges and execute a predetermined process for the registered user. Therefore, for example, if a company A wants to use the service provided by the management server 40, one administrator may be registered, and other employees may be registered based on this administrator, and all employees may be registered. Does not need to be registered as an administrator. Further, it is conceivable that the service provider side of the management server 40 does not want a usage pattern in which each employee is registered as an administrator. This is because there may be a request on the service provider side to manage the service provided by the management server 40 in units of companies, groups, individuals, and the like. As an example, as shown below, one administrator and one or more users are associated with each other in the management server 40.

Administrator: User 1, User 2, ..., User N
The administrator means a person who keeps logged in to the management server 40 on behalf of each user. The administrator can be said to be a predetermined person in charge of coordinating a plurality of users in a company or the like that uses the service provided by the management server 40, but this person in charge does not have to actually exist. Details will be described later, but since each user needs complicated processing or operation to log in to the management server 40 via the registration server 30, in principle, the administrator should log in to the management server 40. , Each user who uses the multifunction device 9 uses the management server 40 with the authority of the administrator. The administrator ID and the e-mail address of each user registered based on the administrator ID are associated with the management server 40, and the electronic data transmitted by each user is associated with the e-mail address and registered. However, each user can also log in to the management server 40.

Therefore, the e-mail address becomes a user ID that identifies the user. ID is an abbreviation for Identification and means an identifier or identification information. An ID refers to a name, a code, a character string, a numerical value, or a combination thereof used to uniquely distinguish a specific object from a plurality of objects. The same applies to IDs other than user IDs. In the present embodiment, an e-mail address is used as the user ID, but the e-mail address is not limited as long as the user can be identified.

The user terminal 50 is an information processing device for a user to confirm, edit, and apply for electronic data from the registration server 30. Browser software or application software having a function equivalent thereto operates on the user terminal 50. The user operates the user terminal 50 to log in with the user's authority and displays the electronic data of the receipt associated with the e-mail address. After confirming and editing the receipt, the boss approves the receipt and withdraws by accounting by sending electronic data to the workflow for applying for approval of the receipt. Further, the user terminal 50 can access the management server 40 and register the image data of the receipt held in the management server 40 in the management server 40. Furthermore, if the user terminal 50 has an imaging function such as a camera, the image data obtained by imaging the receipt can be registered in the management server 40.

Specifically, the user terminal 50 is a PC, a smartphone, a tablet type terminal, a wearable PC such as a sunglasses type or a wristwatch type, a PDA (Personal Digital Assistant), a game machine, a navigation device, etc. Equivalent application software should work. For example, when the user terminal 50 is a smartphone, the service provider of the management server 40 can generate a dedicated application running on the smartphone and distribute it in a form of being downloaded by the user terminal 50.

<Hardware configuration example>
<< Multifunction device 9 >>
FIG. 4 is a diagram showing an example of the hardware configuration of the multifunction device 9. As shown in FIG. 4, the multifunction device 9 includes a main body 10 and an operation unit 20. The main body 10 and the operation unit 20 are connected to each other so as to be able to communicate with each other via a dedicated communication path 300. As the communication path 300, for example, a USB (Universal Serial Bus) standard can be used, but any standard may be used regardless of whether it is wired or wireless.

The main body 10 can perform an operation according to the operation received by the operation unit 20. Further, the main body 10 can also communicate with an external device such as a client PC (personal computer), and can perform an operation according to an instruction received from the external device.

Next, the hardware configuration of the main body 10 will be described. As shown in FIG. 4, the main body 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an HDD (Hard Disk Drive) 14, and a communication I / The F (Interface) 15, the connection I / F 16, and the engine unit 17 are provided, and these are connected to each other via the system bus 18. For convenience of explanation, in FIG. 4, the configuration in which the main body 10 has the HDD 14 has been described as an example, but for example, there may be a configuration in which the main body 10 does not have the HDD 14 and a sufficient storage area cannot be secured.

The CPU 11 comprehensively controls the operation of the main body 10. The CPU 11 controls the operation of the entire main body 10 by executing a program stored in the ROM 12 or the HDD 14 or the like using the RAM 13 as a work area (work area), and has the above-mentioned copy function, scanner function, fax function, printer function, etc. Realize various functions of.

The communication I / F 15 is an interface for connecting to the network 8. The connection I / F 16 is an interface for communicating with the operation unit 20 via the communication path 300.

The engine unit 17 is hardware that performs general-purpose information processing and processing other than communication in order to realize a copy function, a scanner function, a fax function, and a printer function. For example, it is equipped with a scanner that scans and reads an image of a document (corresponding to the reading unit 33 described later), a plotter (image forming unit) that prints on a sheet material such as paper, and a fax unit that performs fax communication. .. Further, it may be provided with specific options such as a finisher for sorting printed sheet materials and an ADF (automatic document feeder) that automatically feeds documents.

Next, the hardware configuration of the operation unit 20 will be described. As shown in FIG. 4, the operation unit 20 has a function of an information processing device. The operation unit 20 includes a CPU 21, a ROM 22, a RAM 23, a flash memory 24, a communication I / F 25, a connection I / F 26, and an operation panel 27, which are connected to each other via a system bus 28. ing. For convenience of explanation, in FIG. 4, the configuration in which the operation unit 20 has the flash memory 24 has been described as an example, but for example, there may be a configuration in which the operation unit 20 does not have the flash memory 24. In short, the multifunction device 9 may not have a storage device for storing received contents.

<< Registration server 30, management server 40, user terminal 50 >>
FIG. 5 is an example of a hardware configuration diagram of the registration server 30, the management server 40, or the user terminal 50. Here, the registration server 30 will be described. The registration server 30 includes a CPU 301, a ROM 302, a RAM 303, a communication I / F 304, an input device 305, and a display device 306. The CPU 301 comprehensively controls the operation of the registration server 30. The ROM 302 is a non-volatile memory that stores various data such as programs. The RAM 303 is a volatile memory that functions as a work area (work area) for various processes executed by the CPU 301. The communication I / F 304 is an interface for connecting to the network 8. The input device 305 is a device used for inputting an operation by a user, and is composed of, for example, a mouse or a keyboard. The display device 306 is a device that displays various types of information, and is composed of, for example, a liquid crystal display device.

Even if the hardware configurations of the management server 40 and the user terminal 50 are the same as or different from those of the registration server 30, there is no problem in the description of the present embodiment.

The management server 40 preferably supports cloud computing, but is not essential. On the other hand, the registration server 30 is assumed to be installed in a network constructed by a company that uses the multifunction device 9, but it may support cloud computing and provide its function as a cloud service. .. Cloud computing refers to a usage pattern in which resources on a network are used without being aware of specific hardware resources.

The illustrated hardware configuration does not need to be housed in one housing or provided as a group of devices, and is preferably provided by the registration server 30 or the management server 40. show. Further, in order to support cloud computing, the physical configuration of the registration server 30 or the management server 40 of this embodiment does not have to be fixed, and hardware resources are dynamically connected according to the load. It may be configured by being disconnected.

<Software configuration>
FIG. 6 is a schematic view showing an example of the software configuration of the multifunction device 9. As shown in FIG. 6, the main body 10 has an application layer 101, a service layer 102, and an OS layer 103. The substance of the application layer 101, the service layer 102, and the OS layer 103 is various software stored in the ROM 12, HDD 14, and the like. Various functions are provided by the CPU 11 executing these software.

The software of the application layer 101 is application software for operating hardware resources to provide a predetermined function (in the following description, it may be simply referred to as an "application"). For example, as an application, a copy application for providing a copy function, a scanner application for providing a scanner function, a fax application for providing a fax function, a printer application for providing a printer function, and information on a multifunction device 9. There is a device information notification application that notifies the user.

The software of the service layer 102 is software that intervenes between the application layer 101 and the OS layer 103 and provides the application with an interface for using the hardware resources included in the main body 10. More specifically, it is software for providing a function of accepting an operation request for a hardware resource and arbitrating the operation request. As the operation request received by the service layer 102, a request such as reading by a scanner or printing by a plotter can be considered.

The interface function by the service layer 102 is provided not only to the application layer 101 of the main body 10 but also to the application layer 201 of the operation unit 20. That is, the application layer 201 (application) of the operation unit 20 can also realize a function using the hardware resources of the main body 10 (for example, the engine unit 17) through the interface function of the service layer 102. For example, the interface function of the service layer 102 is provided by WebAPI. The operation unit 20 and the main body 10 can communicate with each other using the communication path 300 as a network.

The software of the OS layer 103 is basic software (operating system (OS)) for providing basic functions for controlling the hardware included in the main body 10. The software of the service layer 102 converts the usage request of the hardware resource from various applications into a command that can be interpreted by the OS layer 103 and passes it to the OS layer 103. Then, when the command is executed by the software of the OS layer 103, the hardware resource operates according to the request of the application.

Similarly, the operation unit 20 has an application layer 201, a service layer 202, and an OS layer 203. The application layer 201, the service layer 202, and the OS layer 203 included in the operation unit 20 also have the same hierarchical structure as that of the main body 10. However, the functions provided by the application of the application layer 201 and the types of operation requests that the service layer 202 can accept are different from those of the main body 10. The application of the application layer 201 may be software for operating the hardware resources included in the operation unit 20 to provide a predetermined function, but the functions (copy function, scanner function, fax function) mainly provided in the main body 10 may be provided. , Printer function, Initial setting function) UI (user interface) function (copy UI function, scanner UI function, fax UI function, printer UI function, initial setting UI function, etc. ) And software for providing browser functions. Here, the application of the application layer 201 includes an authentication setting application and the like.

In the present embodiment, the software of the OS layer 103 on the main body 10 side and the software of the OS layer 203 on the operation unit 20 side are different from each other in order to maintain the independence of the functions. That is, the main body 10 and the operation unit 20 operate independently of each other in different operating systems. For example, it is possible to use NetBSD (registered trademark) as the software of the OS layer 103 on the main body 10 side and Android (registered trademark) as the software of the OS layer 203 on the operation unit 20 side.

As described above, in the multifunction device 9 of the present embodiment, since the main body 10 and the operation unit 20 operate on different operating systems, communication between the main body 10 and the operation unit 20 is between processes in a common device. It is not communication, but communication between different devices. An operation (command communication) of transmitting information (instruction content from the user) received by the operation unit 20 to the main body 10 and an operation of the main body 10 notifying the operation unit 20 of an event correspond to this. Here, the function of the main body 10 can be used by the operation unit 20 performing command communication to the main body 10. In addition, the event notified from the main body 10 to the operation unit 20 includes the execution status of the operation in the main body 10, the contents set on the main body 10 side, and the like.

Further, in the present embodiment, since the power supply to the operation unit 20 is performed from the main body 10 via the communication path 300, the power control of the operation unit 20 is separated from the power control of the main body 10 (independently). Can be done.

FIG. 7 is a diagram illustrating a functional configuration of the multifunction device 9. Explaining the correspondence with FIG. 6, the application layer 101 has the SDK application 124 and the SDK platform 123, and the service layer 102 has the control service 122. The OS layer 103 has an OS 121. Further, the application layer 201 has a rich UI application 251 (including a receipt application 60), and the service layer 202 has a panel filter unit 252, an application management unit 254, and a controller communication unit 253. The OS layer 203 has a rich UIOS 255.

The control service 122 is a group of software modules having a function for controlling various hardware resources and the like, and providing an interface for allowing a higher-level application or the like to use the function. The control service 122 has, for example, a function related to authentication, a function related to network communication, a control function of the engine unit 17, a memory (RAM 13, ROM 12, etc.) management function, and the like. The control service 122 also has a display control function (hereinafter, referred to as a conventional display) that the multifunction device 9 of the present embodiment does not have.

The control service 122 includes a panel management unit 1231, a terminal communication unit 1232, and the like. The panel management unit 1231 has the original responsibility of controlling the display of the conventional display. That is, the panel management unit 1231 provides a control function related to the display control of the conventional display, and controls the display of the conventional display. For example, the panel management unit 1231 receives a request for changing the display state of the display component from the SDK application 124 or another application (authentication setting application 125, etc.). The panel management unit 1231 changes the display state of the display component on the conventional display. The change of the display state of the display component includes the display and non-display of the display component, the reversal of the display component, and the like.

However, the panel management unit 1231 in the present embodiment executes a process for reflecting the change in the display state in response to the request for display control of the conventional display on the operation unit 20. For example, the panel management unit 1231 transmits a request for changing the display state of the display component from the SDK application 124 or another application to the operation unit 20 via the terminal communication unit 1232. As a result, the display control by the SDK application 124 or other applications can be linked or synchronized with the display control by the rich UI application 251 in the operation unit 20.

The display component is a variety of components that are components of the screen. The display component is displayed, for example, for causing the multifunction device 9 to execute a process (job). Examples of display components include buttons, soft keys, soft keyboards, windows, labels for displaying character strings, and the like. The soft key is a group of software keys displayed for accepting input of a character string on, for example, a smartphone or a tablet terminal.

The terminal communication unit 1232 controls communication with the operation unit 20. The terminal communication unit 1232 communicates with the operation unit 20 by, for example, HTTP (HyperText Transfer Protocol) using WebAPI. However, the communication protocol used between the multifunction device 9 and the operation unit 20 does not have to be limited to HTTP.

The SDK platform 123 includes an API (Application Program Interface) for developing the SDK application 124, and provides an execution environment for the SDK application 124. The SDK application 124 enables the control service 122 to be used. The form of the API may be, for example, a function, an object-oriented class, a method of the class, or the like. Hereinafter, the API provided by the SDK platform 123 is referred to as "SDK API". For example, the SDK platform 123 provides the SDK application 124 with an SDK API related to a scanning function, an SDK API related to a printing function, an SDK API related to a copy function, and the like. The SDK API is open to the public, and the SDK application 124 can be developed by a third vendor or the like. The SDK platform 123 may include a Java (registered trademark) VM (Virtual Machine). In this case, the SDK application 124 is implemented in the Java® language.

The programs that can be installed on the multifunction device 9 are not limited to the SDK application 124, the SDK platform 123, and the like, and the programs that can be installed on the multifunction device 9 may include all the programs that are installed on the multifunction device 9. In this embodiment, the authentication setting application 125 corresponds. Since the authentication setting application 125 is a so-called native application (written in a language suitable for hardware and OS), the control service 122 can be used without going through the SDK platform 123.

The SDK application 124 is an application program (also referred to as a plug-in) that is additionally installed after the shipment of the multifunction device 9 in order to expand the functions of the multifunction device 9. In FIG. 7, the legacy application A1241 is illustrated as the SDK application 124. The "legacy" of the legacy application A1241 is added for convenience as a relative expression to the rich UI application 251 described later, and is not a wording intended to limit the functions and uses of the legacy application A1241.

The operation unit 20 will be described. As described above, the rich UIOS 255 may be an OS used in smartphones, tablet terminals, and the like in recent years.

The controller communication unit 253 controls communication with the terminal communication unit 1232 of the multifunction device 9. The application management unit 254 manages the correspondence between the rich UI application 251 and the SDK application 124 and other applications. Some rich UI apps 251 do not correspond to the SDK app 124 or other apps (receipt app 60 in this embodiment).

The panel filter unit 252 provides the rich UI application 251 with an interface for cooperation or synchronization of display control between the rich UI application 251 and the SDK application 124 or other applications.

The rich UI application 251 is an application program installed in the operation unit 20 in order to reflect the display control on the conventional display by the SDK application 124 or other applications on the operation unit 20. Basically, the rich UI application 251 and the SDK application 124 or other applications have a one-to-one relationship. For example, the screen control application 126 for the authentication setting application is a rich UI application 251 for realizing the GUI of the authentication setting application 125 on the rich UIOS 225. The screen control application 126 for the authentication setting application only provides the GUI, and the authentication setting application 125 is responsible for the functions related to the authentication setting.

On the other hand, the receipt application 60 operates without using the functions of the SDK application 124 of the main body 10 or other applications.

The "rich" of the rich UIOS 225 and the rich UI application 251 is added for convenience as a relative expression to the legacy application A1241, and the purpose is to limit the functions and uses of the rich UIOS 225 and the rich UI application 251. It is not the wording of.

The procedure for displaying the screen on the operation unit 20 by the SDK application 124 or other application will be described. Here, the authentication setting application 125 is taken as an example. The user presses the icon of the authentication setting application 125 from the home screen of the operation panel 27. The application management unit 254 notifies the controller communication unit 253 that the authentication setting application 125 has been pressed. The control service 122 activates the authentication setting application 125.

When the authentication setting application 125 requests the panel management unit 1231 to generate some display component (hereinafter referred to as "display component A"), the panel management unit 1231 generates the display component A as before and the terminal communication unit. Notify 1232 that the display component A has been generated. However, since the conventional display does not actually exist, the generated display component A is not displayed.

On the other hand, the terminal communication unit 1232 transmits the generation notification of the display component A to the controller communication unit 253. The controller communication unit 253 notifies the panel filter unit 252 of the generation of the display component A. The panel filter unit 252 notifies the screen control application 126 for the authentication setting application of the generation request. The screen control application 126 for the authentication setting application generates the display component A. The generated display component A is displayed on the operation panel 27. In this way, the screen generated by the SDK application 124 or other application of the main body 10 and the screen displayed by the operation unit 20 can be synchronized.

<Authentication setting screen>
FIG. 8 shows an example of the authentication setting screen 491 displayed by the screen control application 126 for the authentication setting application. The authentication setting screen 491 is a screen for setting whether or not the administrator of the multifunction device 9 mainly performs user authentication for using the multifunction device 9. The authentication setting screen 491 has a radio button 492 associated with ON and a radio button 493 associated with OFF. When the multifunction device 9 is to perform user authentication, the user presses the ON radio button 492, and otherwise presses the OFF radio button 493. Further, the authentication setting screen 491 has a radio button 494 for the user to set the authentication method. When the authentication setting is ON, the user can select either authentication using "user name / password", authentication using "ID card", or authentication using "ID card / password".

The authentication setting information set in this way is stored in the main body 10 and managed by the authentication setting application 125. To refer to the authentication setting information by another program, obtain it from the authentication setting application 125.

<About functions>
The functions of each device of the information registration system 100 will be described with reference to FIG. FIG. 9 is an example of a functional block diagram of the multifunction device 9, the registration server 30, the management server 40, and the user terminal 50 included in the information registration system 100.

<< Multifunction device 9 >>
The multifunction device 9 has a main body 10 and an operation unit 20, and the main body 10 has a transmission / reception unit 31, an authentication processing unit 32, a reading unit 33, and a main body communication unit 38. Each of these functional units included in the main body 10 is a function or means realized by operating any of the components shown in FIG. 4 by an instruction from the CPU 11 according to a program developed from the HDD 14 to the RAM 13. Is. This program is distributed from a server for program distribution or stored in a storage medium.

Further, the main body has a storage unit 39. The storage unit 39 is a storage means for storing various types of information realized by the HDD 14, ROM 12 or RAM 13 of FIG. The multifunction device user information DB3901 is constructed in the storage unit 39, and further, the authentication setting information 3902 and the logged-in user (when logged in) 3903 are stored.

表１は複合機ユーザ情報ＤＢ３９０１に記憶されている情報の一例をテーブル状に示す。複合機ユーザ情報ＤＢ３９０１には例えば、ユーザ名、パスワード、カードＩＤ、メールアドレス、及びロールが登録されている。ユーザ名、パスワード、及び、カードＩＤは、ユーザが複合機９にログインするための認証情報である。複合機ユーザ情報ＤＢ３９０１には管理サーバ４０にログインするための認証情報は登録されない点に注意されたい。複合機ユーザ情報ＤＢ３９０１に各種のサーバの認証情報を登録すると複合機ユーザ情報ＤＢ３９０１の管理が煩雑になってしまう。本実施形態では、ユーザが複合機９にログインすると管理者権限で管理サーバ４０を使用できるため、複合機ユーザ情報ＤＢ３９０１は複合機９へのログインのための認証情報を保持していればよい。したがって、ユーザはシングルサインオンと同様に1回の認証操作で複合機９と管理サーバ４０を使用できる。

Table 1 shows an example of the information stored in the multifunction device user information DB3901 in a table. For example, a user name, a password, a card ID, an e-mail address, and a role are registered in the multifunction device user information DB3901. The user name, password, and card ID are authentication information for the user to log in to the multifunction device 9. Note that the authentication information for logging in to the management server 40 is not registered in the multifunction device user information DB3901. If the authentication information of various servers is registered in the multifunction device user information DB3901, the management of the multifunction device user information DB3901 becomes complicated. In the present embodiment, when the user logs in to the multifunction device 9, the management server 40 can be used with administrator privileges. Therefore, the multifunction device user information DB3901 may hold the authentication information for logging in to the multifunction device 9. Therefore, the user can use the multifunction device 9 and the management server 40 with one authentication operation as in the case of single sign-on.

The e-mail address is used as information for identifying the user on the management server 40. This is because the e-mail address is unique and is also used by the management server 40, so that it is appropriate as information for identifying the user.

The role means the role of each user. There are at least two roles, general or administrator. Generally, it means a normal user, and the administrator corresponds to a system administrator or the like who manages the settings of the multifunction device 9. It is mainly the administrator who sets ON or OFF of the authentication setting. As described in the second embodiment, the role is used to control the display of the administrator setting button on the menu screen 441.

For example, Active Directory (registered trademark) may be applied to user authentication. Further, the multifunction device user information DB3901 does not have to be possessed by the multifunction device 9, and may be in a resource on the network that the multifunction device 9 can communicate with.

(Function of the main body)
The transmission / reception unit 31 transmits / receives various data to / from the registration server 30 via the network 8. The transmission / reception unit 31 is realized by the CPU 11 of FIG. 4 executing a program and controlling the communication I / F15.

The authentication processing unit 32 authenticates the user based on the authentication method set when the authentication setting is ON. When the authentication method is "user name / password", the authentication processing unit 32 refers to the compound machine user information DB3901 and authenticates when the e-mail address and password entered by the user match those of the complex machine user information DB3901. Is determined to be established, and if they do not match, it is determined that authentication is not established. When the authentication method is "ID card", the authentication processing unit 32 reads the ID card information of the ID card carried by the user with a reader / writer, and authentication is established when the ID card information matches that of the compound machine user information DB3901. Then, it is judged that the authentication is not established if they do not match. When the authentication method is "ID card / password", the authentication processing unit 32 refers to the compound machine user information DB3901 and the password entered by the user and the ID card information read by the reader / writer are the compound machine user information DB3901. If it matches the one, it is judged that the authentication is established, and if it does not match, it is judged that the authentication is not established. When the authentication is established, the authentication processing unit 32 permits the user to log in, and stores the logged-in user in the storage unit 39. That is, the receipt application 60 and the like can be used. Biological information such as a fingerprint may be used for the ID card. The authentication processing unit 32 is realized by the CPU 11 of FIG. 4 executing a program or the like.

The reading unit 33 reads the document on the contact glass by the function of the scanner included in the multifunction device 9 and generates image data. The reading unit 33 is realized by the CPU 11 of FIG. 4 executing a program and controlling the engine unit 17.

The main body communication unit 38 communicates with the rich UIOS 255 and the rich UI application 251 of the operation unit 20 by using the function of the terminal communication unit 1232. In the present embodiment, the authentication setting information, the logged-in user, and the like are transmitted to the operation unit 20. As described above, the main body and the operation unit 20 communicate with each other by WebAPI, and the main body communication unit 38 distributes the request specified by WebAPI to the transmission / reception unit 31, the authentication processing unit 32, the reading unit 33, and the like. The main body communication unit 38 is realized by the CPU 11 of FIG. 4 controlling the connection I / F16 or the like.

(Function of receipt application 60)
The receipt application 60 has an operation reception unit 34, a multifunction device control unit 35, a display control unit 36, and an operation unit communication unit 37. Each functional unit of the receipt application 60 is realized by operating any of the components shown in FIG. 4 by an instruction from the CPU 21 according to a program expanded from the flash memory 24 to the RAM 23. A function or means. This program is distributed from a server for program distribution or stored in a storage medium.

The operation reception unit 34 receives various operations for the operation application from the user. The operation reception unit 34 is realized by the CPU 21 of FIG. 4 executing a program and controlling the operation panel 27.

The multifunction device control unit 35 is realized by the CPU 21 of FIG. 4 executing a program or the like, and controls the overall operation of the receipt application 60. That is, the functions of the receipt application 60 are controlled in an integrated manner.

The display control unit 36 generates various screens of the receipt application 60 and displays them on the operation panel 27. The receipt application 60 has a screen component in advance, and forms the screen by arranging the information transmitted from the management server 40 on the component. In the present embodiment, the display / non-display of the end button 446 is switched based on whether the authentication setting is ON or OFF. The display control unit 36 is realized by the CPU 21 of FIG. 4 executing a program and controlling the operation panel 27.

The operation unit communication unit 37 transmits and receives various information to and from the main body. More specifically, the function of the controller communication unit 253 is used to transmit commands and parameters according to WebAPI. The operation unit communication unit 37 is realized by the CPU 21 of FIG. 4 controlling the connection I / F 26 or the like.

The main body 10 mainly has a storage unit 71 used by the receipt application 60, and the roll setting is stored in the storage unit 71. The role setting is information set as to which role of the multifunction device 9 or the management server 40 is to be synchronized with the receipt application 60 (details will be described in the second embodiment).

<< Registration Server 30 >>
The registration server 30 includes a recognition processing unit 41, an extraction unit 42, a multifunction device communication unit 43, a server control unit 44, an image creation unit 45, a term detection unit 46, and a management server communication unit 47. Each of these functional units of the registration server 30 has a function realized by operating any of the components shown in FIG. 5 by an instruction from the CPU 301 according to a program expanded from the HDD 307 to the RAM 303. It is a means. This program is distributed from a server for program distribution or stored in a storage medium.

Further, the registration server 30 has a storage unit 49. The storage unit 49 is a storage means for storing various types of information realized by the HDD 307, ROM 302, or RAM 303 of FIG. Token A and token B are constructed in the storage unit 49. The token A is logged-in information transmitted from the management server 40 to the registration server 30 when the administrator logs in to the management server 40. That is, when the administrator is logged in, the registration server 30 holds the token A. The management server 40 keeps the logged-in state for about one year after the administrator last logs in. As a result, each user can use the management server 40 with administrator privileges. When the e-mail address of the user logged in to the multifunction device 9 is registered in the management server 40, the e-mail address and the session ID 1 are associated with the token A. The multifunction device 9 communicates with the registration server 30 using this session ID 1.

The token B is logged-in information transmitted from the management server 40 to the registration server 30 when an agent described later logs in to the management server 40. The agent can register the electronic data of the receipt in the management server 40 on behalf of the person.

The multifunction device communication unit 43 is realized by the CPU 301 of FIG. 5 executing a program and controlling the communication I / F 304, and communicates various information with the multifunction device 9.

The extraction unit 42 is realized by the CPU 301 of FIG. 5 executing a program or the like, and extracts (trims) an image of each receipt from image data including a plurality of receipts.

The recognition processing unit 41 is realized by the CPU 301 of FIG. 5 executing a program or the like, and performs character recognition processing on each image to convert it into text data. This text data contains at least the date and amount.

The image creation unit 45 is realized by the CPU 301 of FIG. 5 executing a program or the like, and creates thumbnails of each image. A thumbnail is an image in which the image is reduced or enlarged.

The term detection unit 46 is realized by the CPU 301 of FIG. 5 executing a program or the like, and detects a fixed term such as an amount of money or a date from the text data obtained by the character recognition process.

The server control unit 44 is realized by the CPU 301 of FIG. 5 executing a program or the like, and controls the overall operation of the registration server 30.

The management server communication unit 47 is realized by the CPU 301 of FIG. 5 executing a program and controlling the communication I / F 304, and communicates various information via a Web API (Web Application Programming Interface) published by the management server 40. do. WebAPI refers to an agreement (method of requesting processing, method of designating data, etc.) when two devices perform processing via a network.

<< Management Server 40 >>
The management server 40 has a user recognition unit 51, a registration server communication unit 52, an overall control unit 53, an information registration unit 54, and a server unit 55. Each of these functional units included in the management server 40 has a function realized by operating any of the components shown in FIG. 5 by an instruction from the CPU 301 according to a program expanded from the HDD 307 to the RAM 303. It is a means.

Further, the management server 40 has a storage unit 59. The storage unit 59 is a storage means for storing various types of information realized by the HDD 307, ROM 302, or RAM 303 of FIG. A customer information DB 5901, an electronic data DB 5902, an agent DB 5903, and a management server user information DB 5904 are constructed in the storage unit 59.

表２は、顧客情報ＤＢ５９０１に登録されている情報の一例をテーブル状に示す。顧客情報ＤＢ５９０１には管理者ＩＤに対応付けて、管理者パスワード、ユーザＩＤ、パスワード、表示名、及び支出タイプが登録されている。管理者ＩＤは管理者を特定する情報であり例えば管理者のメールアドレスである。管理者ＩＤと管理者パスワードは管理者が管理サーバ４０にログインするための認証情報となる。ユーザＩＤはこの管理者の管理下にあるユーザを示す。管理下にあるとは、管理者の権限で各ユーザが電子データを登録できることをいう。パスワードは各ユーザのパスワードであり、ユーザはメールアドレスとパスワードで管理サーバ４０にログインすることもできる。また、表示名は、複合機９の領収書アプリ６０がログインしているユーザ等を表すための名称である。支出タイプは領収書アプリ６０が表示する各ユーザの支出のタイプをリスト状に有する。

Table 2 shows an example of the information registered in the customer information DB 5901 in a table form. In the customer information DB 5901, an administrator password, a user ID, a password, a display name, and an expenditure type are registered in association with the administrator ID. The administrator ID is information that identifies the administrator, for example, an email address of the administrator. The administrator ID and the administrator password are authentication information for the administrator to log in to the management server 40. The user ID indicates a user under the control of this administrator. Being under control means that each user can register electronic data with the authority of the administrator. The password is the password of each user, and the user can also log in to the management server 40 with the e-mail address and password. The display name is a name for representing a user or the like logged in to the receipt application 60 of the multifunction device 9. The expenditure type has a list of expenditure types of each user displayed by the receipt application 60.

In addition, token A may be associated with the administrator ID. As described above, token A is the logged-in information of the administrator, so when the administrator logs in, it is retained for about one year. When this token A is transmitted, the management server 40 permits the user to use it.

表３（ａ）は、電子データＤＢ５９０２に登録されている各領収書に関する情報の一例をテーブル状に示す。領収書に関する情報として、ユーザＩＤ（メールアドレス）に対応付けて、レポートＩＤ、領収書ＩＤ、日付、金額及びイメージが登録されている。ユーザ（例えば従業員）が領収書を申請する際に複数の領収書をまとめた方が従業員と会社にとって便利な場合があり、レポートはこの複数の領収書の申請の単位である。関連性が高い複数の領収書は１つのレポートに対応付けられる。ユーザは後述するようにレポート単位で領収書を登録できる。日付と金額は文字認識処理により認識された結果であり、イメージは各領収書の画像データである。１つの領収書には管理サーバ４０が管理するための領収書ＩＤが付されているが、ユーザが意識する必要はない。

Table 3 (a) shows an example of information regarding each receipt registered in the electronic data DB5902 in a table form. As information about the receipt, a report ID, a receipt ID, a date, an amount, and an image are registered in association with the user ID (email address). When a user (eg, an employee) applies for a receipt, it may be more convenient for the employee and the company to combine multiple receipts, and a report is the unit of application for these multiple receipts. Multiple highly relevant receipts are associated with a single report. The user can register a receipt for each report as described later. The date and amount are the results recognized by the character recognition process, and the image is the image data of each receipt. A receipt ID for management by the management server 40 is attached to one receipt, but the user does not need to be aware of it.

Table 3 (b) shows an example of report information for each report registered in the electronic data DB5902 in a table form. As the report information, the report name, the report creation date, the total amount, and the status are registered in association with the report ID. The report name is the name of the report given by the user. The report creation date is the date when the user created a new report. The total amount is the sum of the amounts for each receipt in the report. The status includes "not submitted" for which the application has not been completed, "applied" for which the application has been completed, "application permission" for which the company has been granted, and "return" for which the company has refused.

表４は、代理人ＤＢ５９０３に登録されている情報の一例をテーブル状に示す。代理人ＤＢ５９０３には本人と代理人が対応付けて登録されている。本人とはユーザ本人であり、代理人とは本人を代理するユーザである。例えば、本人が社長、代理人が秘書の関係にあり、秘書が社長の代わりに領収書を登録するような使い方が可能になる。あるいは、本人が営業担当者、代理人が庶務の関係にあり、庶務が営業担当者の代わりに領収書を登録するような使い方が可能になる。

Table 4 shows an example of the information registered in the agent DB5903 in a table form. In the agent DB5903, the person and the agent are registered in association with each other. The principal is the user himself / herself, and the agent is the user acting on behalf of the principal. For example, the person himself is the president and the agent is the secretary, and the secretary can register the receipt on behalf of the president. Alternatively, the person in charge of sales and the agent are in a general affairs relationship, and the general affairs can be used to register a receipt on behalf of the sales staff.

Note that one user can designate a plurality of users as agents, and one user can be nominated as an agent by a plurality of users.

表５は、管理サーバユーザ情報ＤＢ５９０４に登録されている情報の一例をテーブル状に示す。管理サーバユーザ情報ＤＢ５９０４には各ユーザのロールが登録されている。管理サーバユーザ情報ＤＢ５９０４はアカウント、ユーザ名、及び、ロールの各項目を有する。アカウントはユーザを特定する情報であり例えばメールアドレスである。ユーザ名は説明のために記載されており、管理サーバユーザ情報ＤＢ５９０４にはなくてもよい。ロールは管理サーバ４０におけるユーザの役割を示す。複合機ユーザ情報ＤＢのロールとは一致しない場合があることに注意されたい。

Table 5 shows an example of the information registered in the management server user information DB 5904 in a table form. The role of each user is registered in the management server user information DB 5904. The management server user information DB 5904 has account, user name, and role items. An account is information that identifies a user, such as an email address. The user name is described for the sake of explanation, and may not be included in the management server user information DB 5904. The role indicates the role of the user in the management server 40. Note that it may not match the role of the multifunction device user information DB.

The role of the multifunction device user information DB3901 indicates whether the multifunction device 9 has administrator authority (administrator) or not (general), and the role of the management server user information DB5904 has administrator authority over the management server 40. Indicates (administrator) or not (general).

(Management server 40)
The registration server communication unit 52 is realized by the CPU 301 of FIG. 5 executing a program and controlling the communication I / F 304, and communicates various information with the registration server 30.

The user recognition unit 51 is realized by the CPU 301 of FIG. 5 executing a program or the like, and authenticates the user. When the token A and the e-mail address are transmitted, it is determined by the token A that the login is performed by the administrator, and when the e-mail address is registered in the customer information DB5901, the user is permitted to use. When the e-mail address and password are sent When the e-mail address and password are registered in the customer information DB5901, the user is permitted to use as if the user has been authenticated.

The overall control unit 53 is realized by the CPU 301 of FIG. 5 executing a program or the like, and controls the entire operation of the management server 40.

The information registration unit 54 is realized by the CPU 301 of FIG. 5 executing a program or the like, and is held by the registration server 30 and electronic data that does not include an image transmitted from the multifunction device 9 via the registration server 30. The image is registered in the electronic data DB 5902.

The server unit 55 is realized by the CPU 301 of FIG. 5 executing a program or the like, operates as a Web server, and also provides a Web application. That is, in response to the request from the user terminal 50, screen information described in HTML, a script language, CSS, or the like is transmitted.

<< User terminal 50 >>
The user terminal 50 has a server communication unit 61, an operation reception unit 62, and a display control unit 63. Each of these functional units of the user terminal 50 has an instruction from the CPU 301 according to the program expanded from the HDD 307 to the RAM 303 and the screen information transmitted from the server unit 55 by any of the components shown in FIG. It is a function or means realized by operating by. This program is distributed from a server for program distribution or stored in a storage medium.

The server communication unit 61 is realized by the CPU 301 of FIG. 5 executing the program and screen information to control the communication I / F 304, and communicates with the management server 40 by a communication protocol such as HTTP or HTTPs.

The operation reception unit 62 is realized by the CPU 301 of FIG. 5 executing a program and screen information to control the input device 305, and receives various user operations on the user terminal 50.

The display control unit 63 is realized by the CPU 301 of FIG. 5 executing a program and screen information to control the display device 306, analyzes the screen information transmitted from the management server 40, and displays the screen on the display device 306. do.

<Screen transition example>
FIG. 10 is a diagram illustrating a transition example of a screen displayed on the operation panel 27 by the multifunction device 9 of this embodiment. Details of each screen are described later except for the proxy input user selection screen 511, the transmission completion screen 551, and the existing report selection screen 451-2.

The lock screen 401 is displayed when the authentication setting is ON and the user is not logged in to the multifunction device 9. It can be called an authentication screen. When the user successfully logs in, the home screen 411 is displayed. When the authentication setting is OFF, the home screen is the initial screen of the multifunction device 9.

When the authentication setting is OFF, the home screen 411 is displayed when the multifunction device 9 is started. When the authentication setting is ON, the lock screen is displayed when the multifunction device 9 is started, and the home screen 411 is displayed when the user logs in. The icon of the receipt application 60 is displayed on the home screen 411.

When the user activates the receipt application 60, the menu screen 441 is displayed. From the menu screen 441, the home screen 411, the proxy input user selection screen 511, the administrator setting screen 521 (may or may not pass the administrator authentication screen 561), the login screen 431, the new report creation screen 451 or the like. , Transition to the existing report selection screen 451-2. In the present embodiment, the processing when transitioning from the home screen 411 to the menu screen 441 will be mainly described.

The proxy input user selection screen 511 transitions to the menu screen 441. The administrator setting screen 521 transitions to the menu screen 441 or various setting screens 531. The proxy input user selection screen 511 is a screen for the user to select the person who will be the proxy. The administrator setting screen 521 is a screen for setting items that can be set only by the administrator.

The login screen 431 is a button for the user to log in to the management server 40 (not the multifunction device 9). In the present embodiment, if the user logs in to the multifunction device 9, it is possible to omit logging in to the management server 40. Therefore, the login screen 431 is displayed when the user (email address) specified by the multifunction device 9 by login is not registered in the management server 40, or when the authentication setting of the multifunction device 9 is OFF. Is. The login screen identifies the user (email address) on the management server 40.

From the new report creation screen 451 or the existing report selection screen 451-2, the screen transitions to the scan screen 461. The new report creation screen 451 is a screen for the user to newly create a report in which the receipt is registered and register the receipt. The existing report selection screen 451-2 is a screen for registering a new receipt in the existing report.

The scan screen 461 transitions to the scanning screen 471, the scanning screen 471 transitions to the receipt analysis result screen 481, and the receipt analysis result screen 481 transitions to the transmission completion screen 551. The transmission completion screen 551 transitions to the menu screen 441.

Note that the screen transition example of FIG. 10 only shows the transition of the main screen, and another screen may be included between each transition. You can also return to the previous screen by pressing the back button from any screen. If the home button 503 is pressed from any screen, the screen returns to the home screen 411.

<Procedure for user to set authentication>
FIG. 11 is an example of a sequence diagram illustrating a procedure in which the user operates the operation unit 20 to set the authentication. It is assumed that the administrator mainly sets the authentication, but for convenience of explanation, it will be described as being performed by the user. Further, when the authentication setting is ON, the user logs in to the multifunction device 9, but in FIG. 11, it is assumed that the user has already logged in. The login process will be described with reference to FIG.

S1: The user presses the icon of the screen control application 126 for the authentication setting application displayed on the home screen 411 of the operation unit 20 to activate the screen control application 126 for the authentication setting application.

S2: First, the screen control application 126 for the authentication setting application requests the controller communication unit 253 to acquire the authentication setting information in order to display the authentication setting information that has already been set.

S3: The controller communication unit 253 requests the main body 10 to acquire the authentication setting information.

S4: The terminal communication unit 1232 of the main body 10 receives the request for acquiring the authentication setting information, and notifies the authentication setting application 125 because it is a request related to authentication.

S5: The authentication setting application 125 acquires the authentication setting information 3902 from the storage unit 39.

S6: The authentication setting application 125 sends a screen generation request for displaying the authentication setting information and the authentication setting information to the terminal communication unit 1232.

S7: The terminal communication unit 1232 transmits the screen generation request and the authentication setting information to the operation unit 20.

S8: The controller communication unit 253 sends a screen generation request and authentication setting information to the panel filter unit 252.

S9: The panel filter unit 252 determines the display component of the authentication setting screen 491 based on the screen generation request, and sends it to the screen control application 126 for the authentication setting application together with the authentication setting information.

S10: The screen control application 126 for the authentication setting application displays the authentication setting screen 491 using the instructed display component and the authentication setting information.

S11: The user sets ON / OFF of the authentication setting and the authentication method on the authentication setting screen 491.

S12: The screen control application 126 for the authentication setting application accepts the setting.

S13: When the user inputs an operation indicating that the authentication setting screen 491 has been confirmed, the screen control application 126 for the authentication setting application requests the controller communication unit 253 to register the authentication setting information.

S14: The controller communication unit 253 transmits a registration request for authentication setting information to the terminal communication unit 1232.

S15: The terminal communication unit 1232 receives the authentication setting information registration request, and notifies the authentication setting application 125 because it is a request related to authentication.

S16: The authentication setting application 125 stores the authentication setting information in the storage unit 39.

In this way, the user can operate the operation unit 20 to store the authentication setting information in the storage unit 39 of the main body 10.

<Procedure for the multifunction device to display the menu screen>
Next, the display of the menu screen 441 using the authentication setting information will be described with reference to FIG. FIG. 12 is an example of a sequence diagram illustrating a procedure until the user logs in to the multifunction device 9 and activates the receipt application 60.

When the authentication setting is ON, the user logs in to the multifunction device 9. The authentication method is assumed to be an "ID card", but the same applies to other authentication methods.

S1: The multifunction device 9 is displaying the lock screen 401. The user holds the ID card over the reader / writer of the main body 10. An example of the lock screen 401 is shown in FIG. 13 (a).

S2: The authentication processing unit 32 determines whether or not the authentication is established based on whether or not the card ID of the ID card is stored in the multifunction device user information DB. In FIG. 12, it is assumed that the authentication has been established.

S3: The authentication processing unit 32 stores the user name and the like of the logged-in user specified by the establishment of the authentication in the storage unit 39. The login user may be any information that can identify the user in addition to the user name.

If the main body 10 and the operation unit 20 do not share the authentication setting and the login state, the operation unit 20 cannot display or release the lock screen 401. Therefore, the main body 10 and the operation unit 20 share the authentication setting and the login state.

S4: When the login status is changed or the operation unit 20 requests, the authentication processing unit 32 reads the authentication setting and the login status from the storage unit 39. The login status means at least the presence or absence of login, and generally includes the logged-in user name.

S5: The authentication processing unit 32 requests the main body communication unit 38 to transmit the authentication setting and the login status.

S6: The main body communication unit 38 notifies the rich UIOS 255 of the operation unit 20 of the authentication setting and the login status. Therefore, the operation unit 20 can always grasp the login state of the main body 10. The notification destination does not have to be Rich UIOS 255, and may be a program that manages the authentication setting and login status on the operation unit 20 side separately from various applications. Rich UIOS 255 does not display the lock screen 401 when the authentication setting is OFF. Further, the rich UIOS 255 displays the lock screen 401 when the authentication setting is ON and there is no login, and does not display the lock screen 401 when the authentication setting is ON and there is a login. When the lock screen 401 is not displayed, the rich UIOS 255 displays the home screen 411. FIG. 13 (b) shows an example of the home screen 411.

S7: The user activates the receipt application 60 from the home screen 411 without logging in when the authentication setting is ON and without logging in when the authentication setting is OFF.

S8: Rich UIOS 255 appropriately generates an OS generation screen. This is because the display of the logout button 502 and the home button 503 is controlled by a program other than the application. In this embodiment, it is described that this control is performed by the rich UIOS, but any program may perform this control. FIG. 14A shows an example of the OS generation screen 571.
-The rich UIOS 255 displays the logout button 502 on the OS generation screen 571 when the login status is logged in. If you are logged in, the authentication setting is always ON.
-If the login status is no login, the logout button 502 is not displayed on the OS generation screen 571. If there is no login, the authentication setting is always OFF (authentication setting = ON and no application can be started without login).

S9: When the receipt application 60 is activated, the operation unit communication unit 37 requests the main body 10 to perform an authentication setting in order to control the display / non-display of the end button 446.

S10: When the main body communication unit 38 receives the authentication setting request, it determines that the request is related to authentication and sends it to the authentication processing unit 32.

S11: The authentication processing unit 32 reads the authentication setting information 3902 from the storage unit 39 in response to the authentication setting request.

S12: The authentication process sends at least the authentication setting (ON or OFF) to the main body communication unit 38.

S13: The main body communication unit 38 transmits the authentication setting (ON or OFF) to the operation unit 20.

S14: The operation unit communication unit 37 of the operation unit 20 receives the authentication setting (ON or OFF), and notifies the display control unit 36 of the authentication setting. As a result, the display control unit 36 can display the menu screen 441 according to whether the authentication setting is ON or OFF.

S15: When the authentication setting is ON, the display control unit 36 does not display the end button 446 on the menu screen 441.

S16: When the authentication setting is OFF, the display control unit 36 displays the end button 446 on the menu screen 441.

In this way, the receipt application 60 can control the display / non-display of the end button 446 according to the authentication setting set in another device called the main body 10. If there is a login, the authentication setting is always ON, and if there is no login, the authentication setting is always OFF, so that the end button 446 and the logout button 502 are not displayed at the same time.

<Screen example of lock screen, home screen, menu screen>
FIG. 13A shows an example of the lock screen 401, and FIG. 13B shows an example of the home screen 411. A message 402 and an icon 403 indicating that the IC card is held up are displayed on the lock screen 401, indicating that the user should hold the IC card over to release the lock screen 401. The icon 412 representing the receipt application 60 is displayed on the home screen 411. Although a plurality of applications are often displayed, they are omitted in FIG. 13 (b).

FIG. 14A shows an example of the OS generation screen 571, and FIG. 14B shows an example of the login screen 431. The OS generation screen 571 is an area other than an application, such as an OS, such as Rich UIOS 255, and there is no chance that the illustrated OS generation screen 571 is displayed as it is. FIG. 14A is a diagram for explanation. The receipt application 60 superimposes (synthesizes) a menu screen or the like on the OS generation screen 571 and displays the final screen. The OS generation screen 571 has a logout button 502, a home button 503, and the like.

The menu screen 441 is as shown in FIGS. 2A and 2B. As described above, the end button 446 and the logout button 502 of the menu screen 441 may or may not be displayed. In addition, on the menu screen 441, there are a "send report and expense" button 442, a "add expense to report" button 443, a "send expense" button 444, an operation button 445 as another user, and so on. The home button 503 is displayed.

The "send report and expense" button 442 is a button for the user to create a new report and register (scan) a receipt. The "Add Expense to Report" button 443 is a button for adding a receipt to the created report. The "send expense" button 444 is a button for registering only the receipt without associating it with the report.

The operation button 445 as another user is a button for the user to operate the receipt application 60 as an agent. When the operation button 445 is pressed as another user, the proxy input user selection screen 511 is displayed. On the proxy input user selection screen 511, it is possible to input a password for being authenticated as another user (the person himself / herself when viewed from the current user), and the user can log in to the multifunction device 9 as a proxy.

The login screen 431 has a login ID field 432 and a password field 433. As described above, the user logged in to the multifunction device 9 does not need to log in to the management server 40, but the management server 40 may not have the e-mail address associated with the administrator ID (token A). sell. However, there is a possibility that the user has registered another e-mail address and password pair in the management server 40. In this case, the user can log in to the management server 40 by performing the second authentication operation of entering his / her e-mail address and password after logging in to the multifunction device 9 with the IC card. Alternatively, when the authentication setting of the multifunction device 9 is OFF, the user is used to log in to the management server 40.

<Registration of agent>
FIG. 15 is an example of a diagram illustrating the relationship between the principal 68 and the agent 69. The relationship between the principal 68 and the agent 69 is established when the principal 68 designates an arbitrary user. Since the agent 69 cannot be specified with the administrator authority, the user who is the principal logs in to the management server 40 with the user authority and specifies the user to be appointed as the agent 69. Since the display name of the person and the e-mail to the effect that the agent 69 has been designated are sent to the nominated user, the user designated as the agent 69 permits or denies it. For example, the user clicks the URL of the e-mail to open the Web page and presses Yes or No. When the user presses Yes, the person and the agent are registered in the agent DB 5903 of the management server 40 in association with each other.

As shown in FIG. 15, it is possible for a plurality of principals 68 to appoint one agent 69, and for one principal 68 to appoint a plurality of agents 69.

<Communication with management server>
The receipt application 60 starts communication with the management server 40 by starting. The management server 40 determines whether or not the user is registered.

FIG. 16 is an example of a sequence diagram showing a procedure for communicating with the management server 40 by starting the receipt application 60. The process of FIG. 16 is executed in parallel with FIG. In the process of FIG. 16, the communication between the main body 10 and the operation unit 20 will be simplified and described so that the receipt application 60 communicates with the registration server 30. However, in reality, the main body 10 communicates with the registration server 30 at the request of the operation unit 20.

S1: The user starts the receipt application 60.

S2: The multifunction device control unit 35 of the receipt application 60 acquires the current login status from the authentication processing unit 32. As described with reference to FIG. 12, if the authentication setting is ON, the user is logged in. If the authentication setting is OFF, the login screen 431 is automatically displayed. Alternatively, the login screen 431 is displayed when any button such as the "send report and expense" button 442, the "add expense to report" button 443, or the "send expense" button 444 is pressed. This identifies the user's email address.

S3: When the authentication setting is ON, the main body 10 has an e-mail address, so the multifunction device control unit 35 acquires the e-mail address of the logged-in user from the authentication processing unit 32. When the login screen 431 is displayed because the authentication setting is OFF and the login to the management server 40 is successful, the display control unit 36 of the operation unit 20 holds the user's e-mail address.

S4: The multifunction device control unit 35 transmits the e-mail address of the user logged in to the multifunction device 9 to the registration server 30 together with the login request. To be precise, when the multifunction device 9 communicates with the registration server 30, the multifunction device control unit 35 communicates using the transmission / reception unit 31 of the main body 10, but this procedure is omitted for simplification. The same applies to the following communications.

S5: The multifunction device communication unit 43 of the registration server 30 receives the login request together with the e-mail address and sends it to the server control unit 44. When the server control unit 44 determines that the login request is made, the server control unit 44 requests the management server 40 to acquire the display name together with the e-mail address and the token A. The registration server communication unit 52 of the management server 40 receives the request for the display name, and the general control unit 53 acquires the e-mail address and the token A. The general control unit 53 permits the use of the user by the token A, and reads the display name associated with the e-mail address from the customer information DB 5901. The registration server communication unit 52 of the management server 40 transmits the display name to the registration server 30.

S6: The management server communication unit 47 of the registration server 30 receives the display name and sends it to the server control unit 44. If the display name can be received, it means that the e-mail address has been registered in the management server 40. Therefore, it is determined that this user can use the management server 40, and the server control unit 44 determines the session ID 1 for identifying the session. Is generated, and the session ID 1 and the e-mail address are associated with the token A. Further, the multifunction device communication unit 43 transmits the session ID 1 and the display name to the receipt application 60. The display control unit 36 of the receipt application 60 arranges and displays a display name on the operation button 445 as another user, for example, on the menu screen 441.

S7: Further, when the display name can be received, the server control unit 44 of the registration server 30 requests the management server 40 for the group policy. Group Policy is a rule regarding the registration of user receipts. For example, the item name (for example, expenditure type) displayed by the receipt application 60. The registration server communication unit 52 of the management server 40 transmits the text (for example, expenditure type) used in the item to the registration server 30 as a group policy.

S8: The server control unit 44 of the registration server 30 acquires the initial value of the expenditure type from the text used in the items on the screen.

By logging in to the multifunction device 9 in this way, the registration server 30 communicates with the management server 40 with the token A, so that the user can register the receipt in the management server 40 with one authentication operation.

Here, if the display name associated with the e-mail address is not found in step S5 of FIG. 16, the receipt application 60 is notified that the e-mail address cannot be found from the management server 40 via the registration server 30. In this case, the receipt application 60 displays the login screen 431.

<What happens when the "Send Report and Expenses" button is pressed>
17 and 18 are examples of sequence diagrams showing a procedure in which the multifunction device 9 registers electronic data of a receipt in the management server 40.

S13: The user presses the "send report and expense" button 442 from the three buttons on the menu screen 441, and the operation reception unit 34 accepts the press of this button.

S14: Since the multifunction device control unit 35 of the receipt application 60 requests the registration server 30 for the list of expenditure types, the list of expenditure types and the initial value are acquired from the registration server 30. The session ID is used for communication between the receipt application 60 and the registration server 30. The display control unit 36 of the receipt application 60 displays the new report creation screen 451. FIG. 19A shows an example of the new report creation screen 451.

S15: When the user inputs necessary items and transitions the screen, the display control unit 36 displays the scan screen 461. FIG. 19B shows an example of the scan screen 461.

S16: The user places multiple receipts on the contact glass (the area where the receipts to be read are physically placed and the reading area where the scanner device reads), presses the scan button, and the operation reception unit. When the operation is accepted by 34, the multifunction device control unit 35 of the receipt application 60 requests the reading unit 33 of the main body 10 to execute scanning. The multifunction device control unit 35 acquires image data including a plurality of receipts. When the user presses the scan button, the display control unit 36 displays the scanning screen 471. FIG. 20A shows an example of the scanning screen 471.

S17: The multifunction device control unit 35 transmits an image processing request to the registration server 30 together with the session ID 1 and the image data.

S18: The multifunction device communication unit 43 of the registration server 30 receives the image processing request together with the session ID 1 and the image data, and sends the image processing request to the server control unit 44. The server control unit 44 determines that each receipt is extracted in response to the image processing request. The extraction unit 42 extracts each receipt from one image data.

S19: When the extraction is completed, the server control unit 44 transmits the image ID and the total number of receipts to the receipt application 60. The image ID is information that identifies image data including a plurality of receipts. The transmission / reception unit 31 of the multifunction device 9 receives the image ID and the total number of receipts.

S20: Next, the server control unit 44 causes the recognition processing unit 41 to perform character recognition processing on the image of each receipt. Further, the server control unit 44 causes the image creation unit 45 to generate a thumbnail image of the image.

S21: The receipt application 60 specifies an image ID and requests an image of each receipt from the registration server 30. Since the image is requested from the multifunction device 9, the registration server 30 can transmit the image through the firewall. The electronic data includes a monetary amount, a date, and an image (thumbnail image), and a monetary amount and a date position, which will be described later. When the display control unit 36 of the receipt application 60 receives the electronic data, the receipt analysis result screen 481 is displayed. FIG. 20B shows an example of the receipt analysis result screen 481.

S22, S23, S26: The server control unit 44 of the registration server 30 performs character recognition processing and thumbnail image creation in order for all images. Instead of performing in sequence, processing threads for multiple receipts may be executed in parallel.

S24: The multifunction device control unit 35 of the receipt application 60 specifies the image ID and sequentially requests the registration server 30 for the electronic data of each receipt until the electronic data of the total number of receipts is acquired. When the display control unit 36 of the receipt application 60 receives new electronic data, the receipt analysis result screen 481 is updated.

S25, S27: The user can switch and display each electronic data by pressing the feed button 484 on the receipt analysis result screen 481. The multifunction device control unit 35 of the receipt application 60 counts the number of received electronic data, and when the electronic data of the total number of receipts is acquired, the transmission button described later can be pressed. As a result, the user can transmit the electronic data of the receipt (to the effect that the reception of the electronic data is completed) to the registration server 30. That is, it becomes possible to transmit to the registration server 30 that the reception of the electronic data is completed.

S28: The user presses the send button 485 on the receipt analysis result screen 481.

S29: The operation reception unit 34 accepts the operation, and the multifunction device control unit 35 transmits the electronic data of each receipt together with the report information, the image ID and the session ID 1 to the registration server 30. The report information is information input on the new report creation screen 451 and includes, for example, a report name, a date (a report creation date, not a receipt date), a Business Purpose, a comment, and the like. In addition, each electronic data is used / not used, expenditure type, date, and amount. The image of each receipt is not included. This is because it can be specified by the image ID. As a result, the communication time can be shortened. Use / not use means whether or not to register the electronic data of the receipt (selected by the user).

S30: The multifunction device communication unit 43 of the registration server 30 receives the electronic data (not including the thumbnail image) of each receipt together with the report information, the image ID and the session ID 1. The server control unit 44 requests the management server 40 to create a new report together with the e-mail address and the token A specified by the session ID 1.

S31: When the report can be created, the server control unit 44 of the registration server 30 identifies the image of each receipt by the image ID via the management server communication unit 47, and regarding the electronic data that is "used", A request to create an expense is sent to the management server 40 along with the expense type, date, and amount. In this case as well, the e-mail address and token A are attached.

S32: Next, the server control unit 44 of the registration server 30 transmits the image of the receipt to which the expense creation request is transmitted to the management server 40 via the management server communication unit 47. That is, the electronic data in step S31 and the image in step S32 are paired. Further, this image is not a thumbnail, but an original image extracted by the extraction unit 42. By doing so, the management server 40 can save the image of the receipt with less deterioration in image quality. The server control unit 44 of the registration server 30 repeats steps S30 and S31 for the total number of receipts.

S33: When the completion of registration of the electronic data of the total number of receipts is notified, the multifunction device control unit 35 of the receipt application 60 specifies the image ID including the session ID 1 and discards the image data to the registration server 30. Request.

S34: The multifunction device communication unit 43 of the registration server 30 receives the session ID 1, the image ID, and the discard request, and the server control unit 44 discards the image data specified by the image ID and all the images (including thumbnails). (delete).

S35: The user logs out. When the end button is pressed, the user is not logged out, but when he / she leaves the multifunction device 9 or the no-operation time elapses, he / she automatically logs out.

S36: The authentication processing unit 32 of the main body 10 accepts the logout, and requests the logout request to the registration server 30 together with the session ID 1.

S37: The server control unit 44 of the registration server 30 deletes the session ID 1 and the e-mail address. As a result, the registration server 30 still holds the token A (can communicate with the management server 40), but cannot communicate with the registration server 30 even if the user operates the multifunction device 9.

<Screen example>
FIG. 19A shows an example of the new report creation screen 451 and FIG. 19B shows an example of the scan screen 461. The new report creation screen 451 has a report name column 452, a date column 453, and a comment column 454. At a minimum, the user may enter the report name in the report name field 452. The date in the date field 453 is the date when the report was created and is automatically entered. The input of the comment field 454 is optional.

The scan screen 461 has an icon 462 for placing the receipt on the contact glass, a message 463 for placing the receipt on the contact glass, and a scan button 464. The user arranges the receipts on the contact glass surface and presses the scan button 464, but does not close the cover of the multifunction device 9. As a result, the portion of the image data that does not have a receipt becomes a black pixel, so that the extraction unit 42 can easily extract each receipt.

FIG. 20A shows an example of the scanning screen 471, and FIG. 20B shows an example of the receipt analysis result screen 481. The scanning screen 471 has an icon 472 meaning that it is being scanned and a message 473 that means that it is being scanned.

The receipt analysis result screen 481 has a type column 487, a date column 488, an amount column 489, an image column 490, a forward button 484, a return button 483, a delete button 482, a send button 485, and progress information 486. In the type column 487, a list of expenditure types is displayed, and the initial value is displayed if the user does not operate. The date and amount as a result of character recognition are displayed in the date field 488 and the amount field 489. The image column 490 is an image display column, and the receipt image (thumbnail image) is displayed in the image column 490. The send button 484 is a button for displaying the electronic data of the receipt for which the character recognition process and the generation of the thumbnail image have been completed after the registration server 30 has completed one of the plurality of receipts. The return button 483 is a button for displaying the electronic data of the receipt in which the registration server 30 has completed the character recognition processing and the generation of the thumbnail image one of the plurality of receipts. The delete button 482 is a button for the user to delete the electronic data. This electronic data is determined to be "not used" and notified to the registration server 30.

The transmission button 485 is a button for the multifunction device 9 to receive an instruction for the user to transmit the electronic data of the total number of receipts to the registration server 30. The send button 485 is displayed or displayed in a reduced brightness state (or a semi-transparent state) even if it is displayed until the receipt application 60 receives the electronic data of the total number of receipts from the registration server 30. Not done. The state in which the brightness is lowered indicates that the transmission button 485 cannot be pressed, and even if the user presses the transmission button 485, the operation receiving unit 34 does not accept the pressing of the transmission button 485. When the multifunction device control unit 35 determines that the electronic data of the total number of receipts is being received, the display control unit 36 displays the transmission button 485 in a mode in which the brightness can be pressed in a normal state.

The progress information 486 indicates how many electronic data out of the total number of receipts have been received by the receipt application 60. The display control unit 36 sets the total number of receipts in N of the message of "M out of N", and sets the number of electronic data received from the registration server 30 at the present time in M. The M cases are sequentially updated every time the receipt application 60 receives electronic data from the registration server 30. The user can grasp how much progress is being made during the waiting time, and the multifunction device 9 can give the user a sense of security.

When the user presses the date field 488, the operation reception unit 34 accepts that the date field 488 is selected, and the display control unit 36 displays the soft keys (numeric keypad) 0 to 9 on the operation panel 27. Further, the display control unit 36 acquires the date position from the metadata attached to the image, aligns the date position of the image with the center of the image field 490, and arranges the image. This automatically displays the date in the image in the center when the user edits the date, making it easier for the user to see. The same applies when the amount field 489 is selected.

Further, when displaying the date or the amount of money, the display control unit 36 may enlarge the image and display it in the center of the image column 490. When the operation panel 27 is small, it becomes easy for the user to confirm the date or amount.

<Summary>
As described above, in the information registration system of the present embodiment, the logout button 502 and the end button 446 are not displayed at the same time on the menu screen 441 of the present embodiment regardless of whether the authentication setting is ON or OFF, so that the user can use the information registration system. It is possible to prevent the operation from being lost and the design from being deteriorated.

In the first embodiment, the display / non-display of the end button 446 is controlled on the menu screen 441 according to the authentication setting, but in this embodiment, the display / non-display of the administrator setting button on the menu screen 441 is further controlled by the role of the user. The controlled information registration system 100 will be described.

FIG. 21 is an example of a diagram illustrating the inconvenience solved by this embodiment. According to the first embodiment, the display / non-display of the end button 446 is controlled by turning the authentication setting ON or OFF. FIG. 21A shows a menu screen 441 when the authentication setting is ON, and FIG. 21B shows a menu screen 441 when the authentication setting is OFF.

In FIG. 21, unlike the first embodiment, the administrator setting button 448 is displayed. The administrator is a person who is permitted to set the receipt application 60, which cannot be set by a general user. In FIG. 21, the administrator setting button 448 is displayed on the menu screen 441 regardless of whether the user is an administrator or a general user. Therefore, any administrator can change the settings of the receipt application 60, which can only be done by the administrator. However, since the general user uses the receipt application 60 more frequently than the administrator uses it, the administrator setting button 448 is often not used. Therefore, the information registration system 100 of this embodiment controls the display / non-display of the administrator setting button 448 of the menu screen 441 by the role setting of the user.

<Screen settings when starting the application>
First, the setting of the role of the administrator of the receipt application 60 will be described. In this embodiment, the administrator is not registered in the receipt application 60 itself, but the role of the user registered in the multifunction device 9 or the role of the user registered in the management server 40 is assigned to the receipt application. Synchronize (use) as 60 rolls.

FIG. 22 shows an example of the menu screen setting screen 541 for the user to set the screen when the application is started. The menu screen setting screen 541 is a screen for the user to set whether the multifunction device 9 displays the menu screen 441 in synchronization with which role of the multifunction device 9 or the management server 40. On the menu screen setting screen 541, a setting 542 of "normal (general and administrator menus can be selected)", a setting 543 of "synchronizing with the role of the user of the multifunction device 9", and a role of the user of the management server are displayed. The setting "Synchronize with" 544 and each radio button are displayed.

I explained that roles are set for each user on both the multifunction device 9 and the management server 40, but the role of the multifunction device 9 and the role of the administrator are those who play a role like an administrator in the receipt application 60. Which one you want to use depends on the customer. Therefore, in the present embodiment, the user can set in advance which role of the multifunction device 9 or the management server 40 is synchronized with which the multifunction device 9 displays the menu screen 441. It should be noted that the user who makes such a setting is assumed to be the administrator of the multifunction device 9 rather than a general user.

Specifically, "Synchronize with the role of the user of the multifunction device 9" or "Synchronize with the role of the user of the management server" is selected, and it is determined that the role of the multifunction device 9 or the role of the management server 40 is the administrator. Then, the administrator setting button 448 is displayed on the menu screen 441. If it is determined that the role of the multifunction device 9 or the role of the management server 40 is general, the administrator setting button 448 is not displayed on the menu screen 441. When "normal" is selected, the administrator setting button 448 is always displayed regardless of the role.

The receipt application 60 holds the role setting set from the menu screen setting screen 541 in the storage unit 71. The menu screen setting screen 541 may be set by the user starting the receipt application 60 at an arbitrary timing.

<Screen switching using role settings>
23 and 24 are examples of sequence diagrams showing a procedure in which the receipt application 60 changes the configuration of the menu screen 441 using the role setting. The processing of FIGS. 23 and 24 starts when the receipt application 60 is activated. Therefore, the processes related to the display and non-display of the end button 446 based on the ON and OFF of the authentication setting described in the first embodiment are executed in parallel (or in order).

S1: When the user activates the receipt application 60, the operation unit communication unit 37 of the operation unit 20 requests the login user from the main body 10.

S2: The main body communication unit 38 of the main body 10 receives the login user acquisition request and sends it to the authentication processing unit 32.

S3: The authentication processing unit 32 reads the login user from the storage unit 39. If the authentication setting is OFF, it is determined that there is no logged-in user (no login). The login user is, for example, a user name.

S4: The authentication processing unit 32 returns the logged-in user or no login to the main body communication unit 38.

S5: The main body communication unit 38 transmits a logged-in user or no login to the operation unit 20.
-If you are already logged in, the following processing will be performed.

S6: The operation unit communication unit 37 sends a logged-in user to the display control unit 36. As a result, the display control unit 36 can identify the logged-in user.

S7: Further, the display control unit 36 reads the roll setting from the storage unit 71. That is, on the menu screen setting screen 541, which of "normal (general and administrator menus can be selected)", "synchronization with the role of the user of the multifunction device 9", and "synchronization with the role of the user of the management server" is set. Determine if it has been done.
-If you are not logged in, the following processing will be performed.

S8: The operation unit communication unit 37 sends a message to the display control unit 36 that there is no login. As a result, the display control unit 36 detects that the user cannot be specified.

S9: The display control unit 36 displays the login screen 431. At present, the user is not specified, so the user is specified by login. Therefore, even if the authentication setting is OFF, the user (email address because the authentication is performed by the management server 40) is specified in step S9. The login screen may be displayed when the user inputs some operation.

S10: When the user is specified, the display control unit 36 reads the role setting from the storage unit 71.

Subsequently, the processing based on each role setting will be described.
In the case of "normal (general and administrator menus can be selected)" setting
S11: The display control unit 36 displays the menu screen 441 of FIG. 25 (a). That is, since the role is not considered in this setting, the administrator setting button 448 is always displayed.

In the case of "Synchronize with user role of multifunction device 9" setting
S12: The display control unit 36 sends a role acquisition request together with the user name to the operation unit communication unit 37. When a user is identified by the login screen, an email address is sent instead of the user name.

S13: The operation unit communication unit 37 transmits a role acquisition request to the main body 10 together with the user name.

S14: The main body communication unit 38 of the main body 10 sends a role acquisition request to the authentication processing unit 32 together with the user name.

S15: The authentication processing unit 32 of the main body 10 reads the role associated with the user name from the multifunction device user information DB3901. Therefore, it is possible to obtain whether the logged-in user is a general user or an administrator.

S16: The authentication processing unit 32 of the main body 10 sends a roll to the main body communication unit 38.

S17: The main body communication unit 38 of the main body 10 transmits a roll to the operation unit 20.

S18: The operation unit communication unit 37 of the operation unit 20 receives the roll and sends the roll to the display control unit 36.

S19: The display control unit 36 displays the menu screen 441 of FIG. 25 (a) or FIG. 25 (b) according to the roll. That is, the menu screen 441 with the administrator setting button 448 or the menu screen 441 without the administrator setting button 448 is displayed.

In case of "Synchronize with user role of management server" setting
S20: The display control unit 36 sends an e-mail address acquisition request together with the user name to the operation unit communication unit 37. The reason for acquiring the e-mail address is that the management server 40 identifies the user by the e-mail address. Therefore, when the user is specified by the login screen, steps S20 to S26 are unnecessary.

S21: The operation unit communication unit 37 transmits an e-mail address acquisition request to the main body 10 together with the user name.

S22: The main body communication unit 38 of the main body 10 sends an e-mail address acquisition request to the authentication processing unit together with the user name.

S23: The authentication processing unit 32 of the main body 10 receives the e-mail address acquisition request and reads the e-mail address associated with the user name from the multifunction device user information DB3901.

S24: The authentication processing unit 32 of the main body 10 sends an e-mail address to the main body communication unit 38.

S25: The main body communication unit 38 of the main body 10 transmits an e-mail address to the operation unit 20.

S26: The operation unit communication unit 37 of the operation unit 20 receives the e-mail address and sends the e-mail address to the display control unit 36.

S27: In order to acquire the role of the user specified by the e-mail address from the management server 40, the display control unit 36 sends a role acquisition request addressed to the management server 40 to the operation unit communication unit 37.

S28: The operation unit communication unit 37 transmits a role acquisition request to the main body 10 together with the e-mail address.

S29: The main body communication unit 38 of the main body 10 determines that the notification is addressed to the management server 40, and sends a role acquisition request to the transmission / reception unit 31 together with the e-mail address.

S30: The transmission / reception unit 31 of the main body 10 transmits a role acquisition request to the registration server 30 together with the e-mail address and the session ID.

S31: The multifunction device communication unit 43 of the registration server 30 receives the role acquisition request. In this embodiment, it is assumed that the session ID has already been generated. The management server communication unit 47 of the registration server 30 transmits a role acquisition request to the management server 40 together with the e-mail address and the token A.

S32: The user recognition unit 51 of the management server 40 refers to the customer information DB 5901 and determines whether or not the e-mail address associated with the token A includes the e-mail address transmitted from the registration server 30. As a result, user authentication is performed by the management server 40. When the authentication is established, the user recognition unit 51 reads the role associated with the e-mail address from the management server user information DB 5904.

S33: The registration server communication unit 52 of the management server 40 transmits the role to the registration server 30.

S34: The management server communication unit 47 of the registration server 30 receives the role, and the multifunction device communication unit 43 transmits the role together with the session ID to the main body 10 of the multifunction device 9.

S35: The transmission / reception unit 31 of the main body 10 determines that it is a response to the role acquisition request based on the session ID, and receives the roll. The transmission / reception unit 31 sends the roll to the main body communication unit 38.

S36: The main body communication unit 38 of the main body 10 transmits a roll to the operation unit 20.

S37: The operation unit communication unit 37 of the operation unit 20 receives the roll and sends the roll to the display control unit 36.

S38: The display control unit 36 displays the menu screen 441 of FIG. 25 (a) or FIG. 25 (b) according to the roll. That is, the menu screen 441 with the administrator setting button 448 or the menu screen 441 without the administrator setting button 448 is displayed.

In this way, the receipt application 60 can determine whether or not to acquire the role from the multifunction device 9 or the management server 40 and display the administrator setting button 448 on the menu screen 441 by setting the role.

<Example of menu screen according to role setting>
FIG. 25 is a diagram showing an example of the menu screen 441 according to the roll setting. Since the case where the authentication setting is ON is taken as an example in FIG. 25, the logout button 502 is displayed. Since the logout button 502 is displayed, the end button 446 is not displayed.

FIG. 25A shows a menu screen 441 when the role setting is “synchronized with the role of the user of the multifunction device 9” or “synchronized with the role of the user of the management server” and the role is the administrator. Since the role is an administrator, the administrator setting button 448 is displayed in FIG. 25 (a).

FIG. 25B shows a menu screen 441 when the role setting is "synchronized with the role of the user of the multifunction device 9" or "synchronized with the role of the user of the management server" and the role is general. Since the role is general, the administrator setting button 448 is not displayed in FIG. 25 (b).

In the case of the "normal (general and administrator menus can be selected)" setting, the menu screen 441 of FIG. 25 (a) is displayed regardless of the role.

<Processing when the administrator setting button is pressed>
As described above, regardless of whether the role setting is "synchronize with the role of the user of the multifunction device 9" or "synchronize with the role of the user of the management server", if the user is an administrator, the administrator setting Button 448 is displayed. The administrator may press the administrator setting button 448, but since the user has already been identified, the login screen 431 is not displayed. When the authentication setting is ON, the user is specified when the administrator logs in to the multifunction device 9, and when the authentication setting is OFF, the login screen 431 is displayed when the receipt application 60 cannot acquire the logged-in user. This is because it is displayed. Therefore, when the administrator setting button 448 is pressed, the administrator authentication screen 561 is displayed. The administrator authentication screen 561 is a screen for authenticating that the user has the administrator authority. The administrator authentication screen 561 is shown in FIG. 27 (a).

On the other hand, when the role setting is "normal (general and administrator menus can be selected)", the administrator setting button 448 is always displayed. When the administrator setting button 448 is pressed, the login screen 431 is displayed only when the user is not specified at the time when the administrator setting button 448 is pressed. Then, when the user is identified by login, the administrator authentication screen 561 is displayed.

In summary, if the user is specified when the administrator setting button 448 is pressed, the administrator authentication screen 561 is displayed, and if the user is not specified, the login screen 431 is displayed. When the user can be identified by login, the administrator authentication screen 561 is displayed.

FIG. 26 is an example of a diagram illustrating a screen displayed by the display control unit 36 when the administrator setting button 448 is pressed.

The display control unit 36 determines whether or not the administrator setting button 448 has been pressed (S10). When the administrator setting button 448 is pressed, the display control unit 36 determines whether or not the logged-in user has been specified (S20). For example, it is determined whether the e-mail address has been acquired from the main body 10 or whether the e-mail address has been authenticated by the login screen 431. If the user has already logged in, the login screen is unnecessary, so the process proceeds to step S50.

If not logged in, the display control unit 36 displays the login screen 431 on the operation panel 27 (S30). Since the user inputs the password and the e-mail address, it is determined whether or not the management server 40 can identify the user (S40).

If the user cannot be identified, the display control unit 36 displays an error message on the login screen 431. For example, "Could not log in to the management server." Is displayed. In this case, the user can try to log in with a different email address and password.

When the user can be identified, the display control unit 36 displays the administrator authentication screen 561 (S50).

The display control unit 36 determines whether or not the user is an administrator depending on whether or not the user has entered the correct administrator authentication number (S60). The administrator authentication number is the same even if the administrator (user) is different, and it is the authentication information for determining whether or not the receipt application 60 does not communicate with the management server 40 and matches the number held in advance. be.

If the administrator authentication is not established, the display control unit 36 displays an error message (S80). For example, "The administrator authentication number is incorrect." Is displayed. The administrator can confirm the administrator authentication number again and try the authentication again.

When the administrator authentication is established, the display control unit 36 displays the administrator setting screen 521 (S70). FIG. 27B shows the administrator setting screen 521.

As described above, depending on whether or not the user is specified, the login screen can be displayed if necessary, and the administrator authentication screen 561 can be displayed if the user can be specified. Therefore, even if the administrator setting button 448 is displayed, only the administrator can change the administrator setting, and it is possible to prevent any user from changing the setting.

<Example of administrator authentication screen and administrator setting screen>
FIG. 27A is a diagram showing an example of the administrator authentication screen 561. The administrator authentication screen 561 has a message 562 "Please enter the administrator authentication number", an input field 563 for the administrator authentication number, an OK button 564, and a cancel button 565. The user can be authenticated as an administrator by inputting the administrator authentication number and pressing the OK button. Therefore, only the administrator can change the administrator settings.

FIG. 27B shows an example of the administrator setting screen 521. The administrator setting screen 521 is a screen for setting items that can be set only by the administrator. The administrator setting screen 521 has a network setting button 522, an administrator authentication number setting button 523, and a display setting button 524. The network setting button 522 is information for the multifunction device 9 to communicate with the registration server 30, such as the IP address, port number, and authentication information of the registration server 30. The administrator authentication number setting button 523 is a button for the administrator to update the administrator authentication number. The display setting button 524 is a button for changing various screen settings.

In this way, the administrator can make settings that are difficult for a general user. In other words, settings that do not need to be set by a general user can be set when the administrator operates the multifunction device 9.

<Summary>
As described above, the information registration system 100 of the present embodiment can switch the display and non-display of the administrator setting button 448 according to the role of the user. Further, when the administrator setting button 448 is displayed, the administrator can be authenticated on the administrator authentication screen 561.

<Other application examples>
Although the best mode for carrying out the present invention has been described above with reference to examples, the present invention is not limited to these examples, and various modifications are made without departing from the gist of the present invention. And substitutions can be made.

For example, although the registration of a receipt has been described in this embodiment, it can be suitably applied to the registration of various slips, not limited to the receipt. For example, it can be applied to order slips, order slips, invoices, and the like.

Also, login may be referred to as sign-in or logon, and logout may be referred to as sign-out or logoff.

Further, in the present embodiment, the end button is not displayed when the authentication setting is ON, but some display component may be displayed when the authentication setting is ON.

Further, in the present embodiment, the administrator setting button 448 is displayed when the user is the role of the administrator, but a predetermined button may be displayed when the role is general. In addition to the manager and the general, the role may be the position of the organization, the gender of men and women, the age group, the department to which the role belongs, and the like, and the display / non-display of the button may be controlled according to these.

Further, at least one of the registration server 30 and the management server 40 may be realized by a plurality of server devices, or the registration server 30 and the management server 40 may be realized by one server device. Further, there may be a plurality of registration servers 30 or a plurality of management servers 40.

Further, the configuration examples shown in FIG. 9 and the like are divided according to the main functions in order to facilitate understanding of the processing by the multifunction device 9, the registration server 30, the management server 40, and the user terminal 50. The present invention is not limited by the method of dividing the processing unit or the name. The processing of the multifunction device 9, the registration server 30, the management server 40, and the user terminal 50 can be divided into more processing units according to the processing content. It is also possible to divide one processing unit so as to include more processing.

The operation unit communication unit 37 is an example of authentication setting information acquisition means, the authentication setting application 125 is an example of authentication management means, the display control unit 36 is an example of screen display means, and the rich UIOS 255 is a component display means. The management server 40 is an example of a second information processing device.

9 Multifunction device 10 Main unit 20 Operation unit 30 Registration server 40 Management server 50 User terminal 60 Receipt application 100 Information registration system

Japanese Unexamined Patent Publication No. 2016-071488

Claims (7)

An operation unit of the reading device that communicates with the main body of the reading device that can set whether or not authentication is required when accepting an operation.
When the program is started by the operation unit, the authentication is performed from the authentication management means that manages whether or not the reader needs to be authenticated and whether or not the user has been authenticated to use the reader. Authentication setting information acquisition means for acquiring authentication setting information including whether or not it is necessary, and
A means for storing user information registered in an information processing device that communicates via a network, a means for storing setting information in which the program is set to be used in synchronization with the user information managed by the reading device, and the like.
When the authentication setting information is set to require authentication and the user has been authenticated, the first display component for terminating the program is not displayed on the display device of the reader, and the authentication is performed. A screen display means for displaying the first display component on the display device when the setting information is not set to require authentication and the user has not obtained the authentication.
Information on whether or not the user has been authenticated is acquired from the authentication management means, and when the user is authenticated, a second display component for logging out from the reading device is displayed on the display device. , A component display means that does not display the second display component on the display device when the user has not obtained authentication.
Have,
The screen display means switches between display and non-display of a third display component related to the user information with reference to the setting information .
When the component display means displays the second display component, the screen display means does not display the first display component, and when the component display means does not display the second display component, the screen. The display means displays the first display component and displays the first display component.
Operation unit you wherein the second display part and the first display part is not displayed simultaneously. The first display component is an end button for terminating the program, and the second display component is a button for terminating the program by revoking the authentication for the user to use the reader. The operation unit according to claim 1. The role of the user is registered in the user information, and the role of the user is registered.
The third display component is a button operated by a user having a predetermined role.
Any one of claims 1 or 2 , wherein the screen display means switches between display and non-display of the third display component according to the role of the user acquired from the information processing device or the reading device. The operation unit according to item 1. The third display component is a button used by the administrator of the program.
Whether the user information is an administrator or not is set in the user information.
When the setting information is set to use the program in synchronization with the role of the user information registered in the information processing apparatus.
The screen display means switches between display and non-display of the third display component according to the role of the user acquired from the information processing device.
When the setting information is set to use the program in synchronization with the role of the user information registered in the reading device.
The operation unit according to claim 3 , wherein the screen display means switches between display and non-display of the third display component according to the role of the user acquired from the reading device. When the third display component is pressed and the user is specified, the screen display means displays an administrator authentication screen for authenticating whether or not the administrator has the authority. When the authentication is successful, the administrator setting screen is displayed and
When the third display component is pressed and the user is not specified, the screen display means displays a login screen for authenticating the user, and when the user authentication is established, the administrator. The operation unit according to claim 4 , which displays the administrator authentication screen for authenticating whether or not the user has the authority of the above, and displays the administrator setting screen when the authentication is established. A reader that can set whether or not authentication is required when accepting operations.
An authentication management means for setting whether or not authentication is required and managing whether or not the user has been authenticated for using the reading device, and
When the program is started, the authentication setting information acquisition means for acquiring the authentication setting information including whether or not authentication is required from the authentication management means, and the authentication setting information acquisition means.
A means for storing user information registered in an information processing device that communicates via a network, a means for storing setting information in which the program is set to be used in synchronization with the user information managed by the reading device, and the like.
When the authentication setting information is set to require authentication and the user has been authenticated, the first display component for terminating the program is not displayed on the display device of the reader, and the authentication is performed. A screen display means for displaying the first display component on the display device when the setting information is not set to require authentication and the user has not obtained the authentication.
Information on whether or not the user has been authenticated is acquired from the authentication management means, and when the user is authenticated, a second display component for logging out from the reading device is displayed on the display device. , A component display means that does not display the second display component on the display device when the user has not obtained authentication.
Have,
The screen display means switches between display and non-display of a third display component related to the user information with reference to the setting information .
When the component display means displays the second display component, the screen display means does not display the first display component, and when the component display means does not display the second display component, the screen. The display means displays the first display component and displays the first display component.
To that reader, characterized in that the said the first display part second display parts are not displayed simultaneously. An operation unit of the reading device that communicates with the main body of the reading device, which can set whether or not authentication is required when accepting an operation.
When the program is started by the operation unit, the authentication is performed from the authentication management means that manages whether or not the reader needs to be authenticated and whether or not the user has been authenticated to use the reader. Authentication setting information acquisition means for acquiring authentication setting information including whether or not it is necessary, and
A means for storing user information registered in an information processing device that communicates via a network, a means for storing setting information in which the program is set to be used in synchronization with the user information managed by the reading device, and the like.
When the authentication setting information is set to require authentication and the user has been authenticated, the first display component for terminating the program is not displayed on the display device of the reader, and the authentication is performed. A screen display means for displaying the first display component on the display device when the setting information is not set to require authentication and the user has not obtained the authentication.
Information on whether or not the user has been authenticated is acquired from the authentication management means, and when the user is authenticated, a second display component for logging out from the reading device is displayed on the display device. , A component display means that does not display the second display component on the display device when the user has not obtained authentication.
It is a program to function as
The screen display means switches between display and non-display of a third display component related to the user information with reference to the setting information .
When the component display means displays the second display component, the screen display means does not display the first display component, and when the component display means does not display the second display component, the screen. The display means displays the first display component and displays the first display component.
Wherein the first display part the second display part program that is characterized in that not displayed simultaneously.

Images