JP2018125691A - Apparatus, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an apparatus for controlling a storage area according to a user access situation.SOLUTION: In accordance with access from a user, a storage area for data corresponding to the user is generated. In accordance with logout by the user, the generated storage area is deleted when a condition is satisfied.SELECTED DRAWING: Figure 6

Description

  The present invention relates to an apparatus having a storage area corresponding to a user, a control method, and a program.

  2. Description of the Related Art Conventionally, when an information processing apparatus such as an image forming apparatus accepts a user login, a user-specific setting may be read and processing may be performed based on the read setting value. Here, the user-specific settings are, for example, device settings relating to display and operation modes, settings for simply calling functions such as copying and FAX, and settings relating to transmission destinations such as FAX. If these are changed while the user is logged in, the changed setting information is stored in the apparatus.

  In addition, a system that synchronizes user setting information stored as described above between devices is known. In such a system, the setting information of the user is notified to a server that manages the user information, and the other device acquires the setting information. As a result, the user can use the device with the same setting information in any device in the system.

  In the system as described above, there may be a situation in which user setting information is deleted. For example, when a user stops using the system for reasons such as retirement, the setting information of the user is deleted. Japanese Patent Application Laid-Open No. 2004-151561 describes that an apparatus different from an apparatus in which user setting information is stored notifies a deletion request to delete unnecessary setting information.

JP 2010-135910 A

  When a job is submitted to one apparatus of the system as described above, a user information area corresponding to the user is secured in the apparatus. The user information area is also secured when the user logs in to another device in the system. Further, user setting information is synchronized via the server. Such an operation is performed, for example, in a system in which printing is performed in an apparatus different from the apparatus to which the print job is input.

  Generally, the reserved user information area is released when all the user jobs are executed. Each time a user logs in to a plurality of devices, the user information area is secured in each device and the setting information is synchronized. Even though the user logs out, the same user information area remains in the plurality of devices. There can be a situation where Such a situation can strain the storage area of the device and consequently reduce the number of available users.

  An object of the present invention is to solve such conventional problems. In view of the above points, an object of the present invention is to provide an apparatus, a control method, and a program for controlling a storage area corresponding to a user in accordance with the access status of the user.

  In order to solve the above-described problem, the apparatus according to the present invention is configured to generate a storage area for data corresponding to a user according to an access from the user, and to satisfy a condition according to the logout of the user And a deletion unit that deletes the storage area generated by the generation unit.

  According to the present invention, it is possible to control a storage area corresponding to a user according to the access status of the user.

It is a figure which shows the structure of the whole system. FIG. 2 is a diagram illustrating a block configuration of a multifunction machine. It is a figure which shows the block configuration of a server. FIG. 3 is a diagram illustrating a block configuration of an application that controls a multifunction peripheral and a server. 4 is a flowchart illustrating processing for storing a submitted print job. 6 is a flowchart illustrating an operation when processing a print job. It is a figure which shows the transition of the state of a repository. 4 is a flowchart illustrating processing for storing a submitted print job. It is a flowchart which shows the process of S801. 6 is a flowchart illustrating an operation when processing a print job. It is a flowchart which shows a process when the completion of execution of a job is notified. FIG. 10 is a diagram for explaining an execution example of printing in a multifunction peripheral.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The following embodiments do not limit the present invention according to the claims, and all combinations of features described in the embodiments are not necessarily essential to the solution means of the present invention. . The same constituent elements are denoted by the same reference numerals, and the description thereof is omitted.

[First Embodiment]
FIG. 1 is a diagram showing a configuration of the entire system. The system 100 includes digital multifunction peripherals (hereinafter simply referred to as multifunction peripherals) 110a and 110b, and a server 120, which are connected to each other via a wired or wireless network 130 so as to communicate with each other. The system 100 is, for example, a printing system that performs printing with a multifunction peripheral. For example, when a job is input to the multi-function peripheral 110a, the system 100 performs not only an operation of outputting a printed matter by the multi-function peripheral 110a but also an operation of outputting a printed matter by a multi-function peripheral 110b different from the multi-function peripheral 110a to which the job is input. Is possible. For example, when a user submits a job to the multifunction peripheral 110a from a PC or the like, the job is temporarily retained in the multifunction peripheral 110a. Then, the user obtains and executes a print job retained in the multifunction device 110a via the server 120 in the multifunction device 110b, thereby causing the multifunction device 110b to output a printed matter.

  The server 120 manages setting information included in each device in the system 100. When the setting information stored in the MFPs 110a and 110b is changed or when new setting information is stored, the information about the change or the newly added information is sent to the server 120. Notice. With such a configuration, the setting information can be synchronized between the server 120 and the multifunction peripherals 110a and 110b. Here, the setting information includes device information and user information. The device information is, for example, device configuration information or license information, and the user information is, for example, a custom setting value or an address book. In the system 100, when a user logs in to a desired multifunction device, synchronous communication is performed between the multifunction device and the server 120, and the logged-in multifunction device can acquire setting information corresponding to the logged-in user.

  In FIG. 1, the server 120 is shown as an apparatus independent of the multifunction peripherals 110a and 110b, but may be included in the multifunction peripheral 110a or the multifunction peripheral 110b. In that case, one of the multifunction machines operates as the server 120. In FIG. 1, two MFPs 110a and 110b are shown, but the number is not limited to two, and other types of devices such as PCs may be connected to the network 130. good. Moreover, although only one server 120 is shown, a plurality of servers 120 may be configured.

  FIG. 2 is a diagram illustrating a block configuration of the multifunction peripherals 110a and 110b. Hereinafter, unless otherwise specified, the multifunction peripheral 110a and the multifunction peripheral 110b are collectively referred to as the multifunction peripheral 110. The multifunction device 110 includes a controller unit 200, an operation unit 220, a printer 230, and a scanner 240. The controller unit 200 is a control board that comprehensively controls the multifunction peripheral 110, and is connected to the operation unit 220, the printer 230, and the scanner 240.

  The operation unit 220 includes a touch panel and hardware keys, and can display a user interface screen such as a setting screen for functions that can be executed by the multifunction peripheral 110, and can accept setting operations and instruction operations from the user. The printer 230 has a configuration (print engine) corresponding to an electrophotographic system, an inkjet recording system, and the like, and records an image on a recording medium such as paper. The scanner 240 has a configuration (scan engine) that optically reads a document placed on a document table (not shown) and a document fed from an automatic document feeder (ADF).

  The controller unit 200 includes a CPU 201, operation unit I / F 202, RAM 203, image processing unit 204, engine I / F 205, HDD 206, ROM 207, and LANC 208. They are connected to each other via a system bus 210. The CPU 201 reads and executes the operating system stored in the HDD 206 by the boot program stored in the ROM 207. The operating system executes various processes by executing application programs stored in the HDD 206. The RAM 203 is also used as a work area for the CPU 201. In addition to the above setting information, the HDD 206 stores various data necessary for the operation of the multifunction peripheral 110 such as a table.

  The operation unit I / F 202 is an interface with the operation unit 220, transmits various information such as data to be displayed on the operation unit 220, and transmits information operated by the user on the operation unit 220 to the CPU 201. A printer 230 and a scanner 240 are connected to the engine I / F 205, and image data and control signals are input and output. The LANC 208 is connected to the network 100 and performs data communication with each device via the network 100. The image processing unit 204 performs image processing such as conversion, correction, and editing on the read data input from the scanner 240 and the image data output to the printer 230.

  FIG. 3 is a diagram illustrating a block configuration of the server 120. The CPU 301 controls the server 120 in an integrated manner. A RAM 303 is used as a main memory of the CPU 301 and functions as an execution program area and various data areas. The ROM 306 stores a system program for controlling the device of the server 120, and calls and executes an operating system stored in the HDD 305. The LANC 307 performs data communication with other devices via the network 100. The VRAM 302 is a memory in which display data to be displayed on the display 310 of the server 120 is expanded.

  The I / O 304 is an interface for connecting an external input device for accepting a user operation. In FIG. 3, for example, a keyboard 320 and a pointing device 330 are connected. The HDD 305 stores application programs and various data. The CPU 301, VRAM 302, RAM 303, I / O 304, HDD 305, ROM 306, and LANC 307 are connected to each other via a system bus 300.

  FIG. 4 is a diagram illustrating a block configuration of an application that controls the multifunction peripheral 110 and the server 120. The job reception unit 401 of the multifunction peripheral 110 receives the print job by controlling the LANC 208 and stores the print job in the RAM 203. The job storage unit 402 manages the print job stored in the RAM 203 by the job receiving unit 401 by storing it in the HDD 206.

  The job control unit 403 displays a user interface screen for controlling execution of the print job stored in the HDD 206 by the job storage unit 402 on the operation unit 220 and accepts a user operation. The job control unit 403 instructs the job execution unit 407 to perform print processing based on the received user operation. The job execution unit 407 controls the image processing unit 204 and the printer 230 to process a designated print job.

  The login control unit 404 displays a user interface screen for a user to log in to the multifunction peripheral 110 on the operation unit 220 and accepts an operation. The account information management unit 405 is a database that manages account information of users who can log in by the login control unit 404. The user information storage unit 406 is a database that creates a repository, which is a storage area corresponding to each user, and manages information related to the user. The user information synchronization unit 407 controls the LANC 208 and performs data communication with the user information management unit 410 of the server 120. The user information synchronization unit 407 synchronizes the setting information stored in the MFP 110 and the server 120.

  The user information management unit 410 of the server 120 controls the LANC 307 to perform data communication with the MFP 110 and synchronizes setting information stored in the user information storage unit 411. The user information storage unit 411 is a database that stores and manages the setting information notified from the user information management unit 410 in the HDD 305.

  As the blocks of the application in FIG. 4 operate in cooperation, the print job received by the job receiving unit 401 of the multifunction peripheral 110 is stored in the job storage unit 402. Further, the job control unit 403 executes a print job stored in the job storage unit 402 of any multi-function peripheral connected to the system 100. In this case, the multifunction device is a multifunction device that has received a print job or a multifunction device that is different from the multifunction device that has received a print job. Hereinafter, a print job storage process and a stored print job execution process according to this embodiment will be described.

  FIG. 5 is a flowchart illustrating processing for storing a print job input from the user to the multifunction peripheral 110. The processing in FIG. 5 is realized by the CPU 201 reading out the program stored in the ROM 207 to the RAM 203 and executing it.

  In step S <b> 501, when the job reception unit 401 detects reception of a print job by the LANC 208, the job reception unit 401 stores at least data corresponding to the print job header in the RAM 203. In the present embodiment, the user information that transmitted the print job and the setting information for determining whether the print job is to be retained immediately without printing are set in the header of the print job.

  In step S <b> 502, the job receiving unit 401 determines whether or not to immediately print the print job based on user information, MFP setting information, and the like included in the print job header stored in the RAM 203. Here, the setting information of the MFP is a setting value for controlling not to directly print all received print jobs, for example. Note that such setting values of the multifunction peripheral are stored in the HDD 206 or the ROM 207 when received.

  If it is determined in S502 that printing is to be performed immediately, in S503, the job reception unit 401 instructs the job execution unit 407 to print the print job while receiving the remaining print job and storing it in the RAM 203. After S502, the process of FIG.

  If it is determined in step S502 that printing is not performed immediately, that is, it is determined that the job is to be retained, in step S504, the job reception unit 401 receives the remaining print job and stores the print job in the HDD 206 while storing the print job in the HDD 206. The storage unit 402 is instructed. When storing in the HDD 206, the job storage unit 402 generates an identifier in association with the print job to be stored. This identifier includes, for example, unique information of the MFP 110, such as a serial number and a network address. The job storage unit 402 stores the received print job and identifier in the HDD 206.

  In step S <b> 505, the job storage unit 402 extracts user information by analyzing the header of the print job. The job storage unit 402 notifies the user information storage unit 406 of the extracted user information and the identifier of the print job stored in the HDD 206. Here, the user information is information for specifying the owner of the print job, and corresponds to the user name managed by the account information management unit 405 or an alias of the user name.

  In step S <b> 506, the user information storage unit 406 determines whether there is a repository corresponding to the user information notified from the job storage unit 402. When it is determined that there is a repository corresponding to the notified user information, in step S507, the user information storage unit 406 additionally registers the notified print job identifier in the repository. In step S <b> 508, when the repository is updated, the user information storage unit 406 uses the user information synchronization unit 407 to notify the server 120 of user information and information added to the repository (print job information). After S508, the process of FIG.

  If it is determined in S506 that there is no repository corresponding to the notified user information, the user information storage unit 406 tries to generate a new repository in S509. If a new repository cannot be generated, in step S510, the user information storage unit 406 notifies the job storage unit 402 to delete the print job corresponding to the notified print job identifier. Upon receiving the notification, the job storage unit 402 performs print job discard processing. At this time, in order to notify the user that the storage of the print job has failed, a message may be displayed or recorded in a log file. On the other hand, if a new repository can be generated, in step S507, the user information storage unit 406 sets user information in the generated repository and additionally registers the print job identifier. In addition to the user information, the user information storage unit 406 may store print job information stored in the job storage unit 402, such as print settings, output paper size, and color attributes. In this case, for example, the job storage unit 402 may analyze the stored print job, format the analyzed information in, for example, an XML format, and notify the user information storage unit 407 of the information. After S507, the process proceeds to S508.

  As described above, the stored print job information and user information are transmitted to the server 120 from each of all connected multifunction peripherals 110. When receiving the print job information and the user information, the user information management unit 410 of the server 120 notifies the user information storage unit 411 of the information together with the time information of the server 120 at the time of reception. The time information is used when synchronizing with the multifunction device 110. The user information storage unit 411 is a database, and stores user information, print job information, and time information in association with each other.

  FIG. 6 is a flowchart illustrating an operation when the MFP 110 processes a print job stored in any MFP connected to the system. The processing in FIG. 6 is realized, for example, when the CPU 201 of the multifunction peripheral 110 that processes a print job reads the program stored in the ROM 207 into the RAM 203 and executes it.

  In step S <b> 601, the login control unit 404 displays a login screen including an input area for an ID and a password for accepting login on the operation unit 220, and waits for the user to log in. When the login of the user is detected, the login control unit 404 performs authentication processing by comparing the input information with information included in the account information management unit 405. If the login is successful as a result of the authentication, the login control unit 404 notifies the job control unit 403 of login user information of the logged-in user. Here, the login user information is the user name of the logged-in user stored in the account information management unit 405 or an alias of the user name.

  In step S <b> 602, the job control unit 403 determines whether a repository corresponding to the notified login user information exists in the user information storage unit 406. If it is determined that it exists, in step S <b> 603, the job control unit 403 instructs the user information storage unit 406 to synchronize the repository of the user information storage unit 406 with the server 120. With such a configuration, the repository corresponding to the login user information stored in the user information storage unit 406 is synchronized with the server 120. The synchronization process will be described later.

  If it is determined in S602 that the repository does not exist, the job control unit 403 tries to generate a new repository in S604. If a new repository cannot be generated, in step S606, the job control unit 403 displays an error message, and then ends the process of FIG. On the other hand, if a new repository can be generated, the job control unit 403 sets login user information in the generated repository in S605, and performs synchronization processing with the server 120 in S603.

  In step S <b> 607, the job control unit 403 displays a user interface screen including print job information included in the repository corresponding to the login user information stored in the user information storage unit 406 on the operation unit 220. On this user interface screen, a list of print jobs is displayed, and selection of a print job from the list and operations (print, delete, preview, etc.) on the selected print job can be accepted as user operations. The job control unit 403 controls a print job based on a user operation received on the user interface screen. At this time, when the user information included in the repository is changed (for example, deletion), the job control unit 403 notifies the server 120 of the information. When execution of a print job is instructed, the job control unit 403 instructs the job execution unit 407 to execute the designated print job. The instructed job execution unit 407 notifies the job control unit 403 of the job identifier for each instructed job. As a result, the job control unit 403 can know the status of the print job executed by the job execution unit 407.

  In step S608, the job control unit 403 determines whether a logout operation has been detected. If it is determined that the logout operation has not been detected, the processing from S607 is repeated. If it is determined that a logout operation has been detected, the process proceeds to S609.

  When the job control unit 403 detects a logout operation, in step S <b> 609, the job control unit 403 determines whether to delete the repository corresponding to the notified login user information from the user information storage unit 406. In this embodiment, the print job identifier included in the repository corresponding to the login user information does not include the print job stored in the user information storage unit 406 of the multifunction peripheral 100 in which the job control unit 403 is operating. If it is determined to be deleted. If it is determined in S609 not to delete, the job control unit 403 performs logout processing in S610. On the other hand, if it is determined to be deleted, in step S611, the job control unit 403 instructs the user information storage unit 406 to delete the repository corresponding to the login user information. In step S611, the user information storage unit 406 deletes the repository based on the instruction.

  Next, synchronization of user information between the MFP 110 and the server 120 will be described. Synchronization of user information between the multifunction device 110 and the server 120 is performed by transmitting and receiving difference information determined based on time information issued by the server 120. That is, the user information storage unit 406 of the MFP 110 stores time information for each repository, and transmits the time information and user information when synchronizing with the server 120. If the user information storage unit 406 does not store time information, that is, if it has never been synchronized with the server 120, 0 is transmitted to the server 120 as time information.

  The user information management unit 410 of the server 120 that has received the synchronization request from the multifunction device 110 searches the user information storage unit 411 for information notified after the time of the received time information, and transmits the synchronization information to the retrieved information. A reply is sent to the multifunction device 110. The information to be returned includes the identifier of the added print job, the print job information, and the identifier of the deleted print job. These pieces of information are formatted in, for example, the XML format, and the MFP that has transmitted the synchronization request. Reply to 110. The formatted information can include time information when the server 120 returns. When the time information 0 is transmitted from the multifunction device 110, the server 120 formats and returns all information stored in the user information storage unit 411 corresponding to the notified user information.

  Upon receiving the formatted information, the user information synchronization unit 407 of the multifunction peripheral 110 updates the repository stored in the user information storage unit 406 based on the received information. Further, the user information storage unit 406 sets time information included in the received information in the repository. If there is no print job information stored in the repository, the user information synchronization unit 407 deletes the repository.

  As shown in FIGS. 5 and 6, in this embodiment, the MFP 110 does not synchronize with the server 120 when a print job is received, but synchronizes when the user logs in. Therefore, when the user who transmitted the print job logs in, the print job information registered in the job storage unit 402 is transmitted from the server 120 as difference information. However, since the user information synchronization unit 407 only updates the information when a print job having the same identifier is notified from the server 120, no contradiction occurs. In the present exemplary embodiment, it has been described that synchronization with the server 120 is not performed when a print job is received. However, the MFP 110 may perform synchronization processing with the server 120 when a print job is received.

  As shown in FIG. 12, a case is considered where user A logs in the multifunction peripheral 110b after transmitting a print job to the multifunction peripheral 110a. In this embodiment, in this case, the user A's repository is deleted when the user logs out from the multifunction peripheral 110b. Therefore, even when there is an upper limit on the number of users (the number of repositories) that can be registered in the user information of the multifunction peripheral, it is possible to secure a user information area for other users.

[Second Embodiment]
In the first embodiment, it has been described that the repository is deleted when the user logs out. In the present embodiment, when the user logs out, the repository is deleted when a predetermined condition is satisfied. Hereinafter, the present embodiment will be described with respect to differences from the first embodiment.

  The repository for each user stored in the user information storage unit 406 in the present embodiment has the three states shown in FIG. 7 based on the access status of the user to the MFP 110 and the job processing status. The normal state 701 is a state when a repository is created or when a user logs in. The repository that is in the normal state 701 is not deleted. If the repository is in the normal state 701 and the job is not executed at the time of deletion / logout, the repository transits to a deletion waiting state 703. If the repository is in the normal state 701 and the job is being executed at the time of deletion / logout, the repository transits from the normal state 701 to the job execution completion waiting state 702.

  The job execution end wait state 702 is a state indicating that it is necessary to wait for the end of the job being executed before deleting the repository. If the repository is in the job execution completion waiting state 702 and the login is performed, the repository changes from the job execution completion waiting state 702 to the normal state 701. When the repository is in the job execution completion waiting state 702 and the job execution is completed and notified to the server 120, the repository transitions from the job execution completion waiting state 702 to the deletion waiting state 703.

  The deletion waiting state 703 is a state indicating that the repository may be deleted. Deletion of a repository waiting for deletion is performed when a repository for a new user becomes necessary. When the repository is in the deletion waiting state 703 and the login is performed, the repository changes from the deletion waiting state 703 to the normal state 701.

  The job execution completion waiting state 702 is a state necessary when the user information included in the repository includes the execution result of the printing process. In order to notify the server 120 of the result of the print processing after the execution of the print job is completed, user information is required. In other words, the repository must not have been deleted. For this reason, when the printing process is being executed at the time of logout, the state temporarily changes to the job execution completion waiting state 702 and waits for the completion of the printing execution. Then, after registering the print result in the user information and performing synchronization processing with the server 120, the process transits to a deletion waiting state 703, and in step 704, the repository is deleted.

  FIG. 8 is a flowchart illustrating processing for storing a print job in which the multi-function peripheral 110 according to this embodiment is input. The processing in FIG. 8 differs from that in FIG. 5 in S801. In this embodiment, when it is determined in S506 that there is no repository corresponding to the user information notified from the job storage unit 402, the user information storage unit 406 tries to generate a repository according to the flowchart shown in FIG.

  FIG. 9 is a flowchart showing the processing of S801. In step S901, the user information storage unit 406 determines whether there is a predetermined capacity for the repository. If it is determined that there is a free space, a repository is generated, it is determined that the repository has been successfully generated, and the process proceeds to S507 in FIG. On the other hand, if it is determined that there is no space, the user information storage unit 406 determines in step S902 whether there is a repository in the deletion waiting state 703. When it is determined that there is a repository in the deletion waiting state 703, in step S903, the user information storage unit 406 generates a repository after deleting the repository, determines that the repository has been successfully generated, and determines the repository of FIG. The process proceeds to S507. If it is determined in S902 that there is no repository in the deletion waiting state 703, it is determined that repository generation has failed, and the process proceeds to S510 in FIG.

  FIG. 10 is a flowchart illustrating an operation when the MFP 110 according to this embodiment processes a print job stored in any MFP connected to the system. The processing in FIG. 10 differs from that in FIG. 6 in terms of S1001, S1002, and S1003. In this embodiment, when it is determined in S602 that the repository does not exist, in S1001, the user information storage unit 406 attempts to generate a repository according to the process illustrated in FIG.

  If it is determined in step S602 that the repository exists, or if the job control unit 403 sets login user information in the repository in step S605, the job control unit 403 determines the repository status before synchronizing with the server 120 in step S1002. To the normal state 701.

  If it is determined in S609 that the repository corresponding to the login user information is to be deleted from the user information storage unit 406, in S1003, the job control unit 403 determines whether or not the job of the user to be logged out is being executed. . If it is determined that the job is being executed, in step S <b> 1004, the job control unit 403 changes the state of the repository of the user who logs out to the job execution completion wait state 702. When the execution of the job is completed, the repository state is shifted to the deletion waiting state 703, and the process proceeds to S610.

  On the other hand, if it is determined in S1003 that the job is not being executed, in S1005, the job control unit 403 changes the state of the repository of the user who logs out to the deletion waiting state 703. After S1005, the process proceeds to S610 in FIG.

  After transitioning to the job execution completion wait state 702 in step S1004, the job execution unit 407 notifies the job control unit 403 of the completion of print job execution. FIG. 11 is a flowchart illustrating processing when the job control unit 403 is notified of the end of job execution. The processing in FIG. 11 is realized, for example, by the CPU 201 reading a program stored in the ROM 207 into the RAM 203 and executing it.

  When the job execution completion is notified, in step S1101, the job control unit 403 searches for a repository including the notified print job, updates the user information in the searched repository, and performs synchronization processing with the server 120. I do. In step S1102, the job control unit 403 determines whether the repository is in a job execution completion wait state 702. If it is determined that the job execution completion waiting state 702 is reached, the job control unit 403 changes the repository to the deletion waiting state 703 in step S1103. After S1103, the processing in FIG. 11 is terminated, and logout is performed in S610 in FIG. If it is determined in S1102 that the job execution completion waiting state 702 is not reached, the repository state is set to the job execution completion waiting state 702, and the processing of S1102 is repeated again.

  Further, FIG. 11 illustrates the case where the job execution end is notified, but when the job execution end is not notified for a predetermined time, the process proceeds from S1004 to S610 in FIG. Logout may be performed. For example, the job execution is interrupted due to a failure or the like. In this case, if there is another login, the repository state transitions from the job execution completion waiting state 702 to the normal state 701 according to FIG.

  As described above, in this embodiment, the repository stored in the multifunction peripheral is not deleted until the deletion waiting state 703 is entered. Therefore, when the user corresponding to the user information stored in the repository logs in to the copier 110 again, if the repository is not deleted, the user information is not deleted, so the amount of communication synchronized with the server 120 is unnecessary. Can be prevented.

(Other examples)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  110a, 110b MFP: 120 Server: 201, 301 CPU: 207, 306 ROM: 203, 303 RAM

Claims (16)

Generating means for generating a data storage area corresponding to the user in response to an access from the user;
A deletion unit that deletes the storage area generated by the generation unit when a condition is satisfied in response to the user logout;
A device comprising:   The apparatus according to claim 1, wherein the deletion unit deletes the storage area when there is no job in progress corresponding to the user in the apparatus as the condition. Transition means for transitioning the state of the storage area between a plurality of states;
The apparatus according to claim 1, wherein the deletion unit deletes the storage area when the state of the storage area is a predetermined state due to the transition by the transition unit as the condition.   The apparatus according to claim 3, wherein the transition unit transitions the state of the storage area based on at least one of a user operation and a job processing status.   5. The apparatus according to claim 3, wherein the plurality of states include a normal state, a job execution completion waiting state, and a deletion waiting state, and the predetermined state is the deletion waiting state. . The apparatus is capable of communicating with a server that manages data corresponding to a user,
The acquisition unit according to claim 1, further comprising: an acquisition unit configured to acquire, from the server, data corresponding to the user when the storage area is generated by the generation unit in response to an access from the user. The apparatus of any one of Claims.   The apparatus according to claim 6, wherein the obtaining unit obtains data corresponding to the user from the server in response to an access from the user in order to synchronize data with the server.   The apparatus according to claim 6 or 7, wherein the access from the user is a login to the apparatus.   The apparatus according to claim 6, further comprising: a transmission unit configured to transmit information regarding the change to the server when data stored in the storage area is changed. . A receiving means for receiving a job;
Storage means for storing job information received by the receiving means in the storage area;
The apparatus according to claim 6, further comprising:   The apparatus according to claim 10, wherein the acquisition by the acquisition unit is not performed by receiving a job by the reception unit. Display means for displaying a list of jobs based on data corresponding to the user stored in the storage area generated by the generating means;
Execution means for executing a job selected from the list of jobs displayed by the display means;
The apparatus according to claim 1, further comprising:   The apparatus according to claim 1, wherein the storage area is a repository.   The apparatus according to claim 1, wherein the job is a print job, and the apparatus is a printing apparatus capable of executing printing based on the print job. A control method executable in the apparatus,
A generation step of generating a data storage area corresponding to the user in response to access from the user;
A deletion step of deleting the storage area generated in the generation step when a condition is satisfied according to the logout of the user,
A control method characterized by comprising:   The program for functioning a computer as each means of the apparatus of any one of Claims 1 thru | or 14.

Images