System and method to allocate and administer guest printing
The system addresses guest printing challenges by allowing host companies to designate guest companies via shared domains, enabling visitor printing with guest PINs, thus streamlining the process and maintaining control over privileges and costs.
Patent Information
- Application Number
- JP2025021509
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-02-16
- Filing Date
- 2025-02-13
- Publication Date
- 2025-08-28
AI Technical Summary
Existing systems face challenges in efficiently managing guest printing privileges for visitors in corporate networks, particularly when using cloud printing services, as creating guest accounts for each visitor is time-consuming and cumbersome, especially in large companies with many visitors.
A system that allows host companies to designate guest companies through shared top-level domains, enabling visitors to use a guest login PIN for printing on MFPs without individual account creation, with PIN validity controlled by the host administrator.
Enables seamless guest printing by eliminating the need for manual account creation, allowing visitors to print on host company MFPs while maintaining control over privileges and costs, and facilitating efficient job management through automated PIN validation and expiration.
Smart Images

Figure 2025126153000001_ABST
Abstract
Description
[Technical Field]
[0001] This application relates generally to document processing operations such as network printing, and more particularly to assigning and managing printing privileges for guest users. [Background technology]
[0002] Document processing devices include printers, copiers, scanners, email gateways, etc. Recently, devices that combine two or more of these functions have also been found in office environments. These devices are referred to as multifunction peripherals (MFPs) or multifunction devices (MFDs). As used herein, an MFP is understood to consist of a printer alone or in combination with the other functions described above. It is further understood that any suitable document processing device may be used.
[0003] Companies and other institutions often have one or more MFPs within their network. Access and usage is typically controlled by an administrator. Users may send document processing jobs, such as print jobs, to the MFP of their choice. They can then log in to this MFP using their user credentials and release their jobs. A problem arises when company guests want to print their own jobs. For example, an administrator must create a guest login account for each such guest. This can be very time-consuming, especially in large companies with many visitors.
[0004] The above situation can become even more complicated when printing is performed in conjunction with a cloud printing service (CPS). Cloud printing services allow users to print from any device connected to the Internet. Users can submit print jobs remotely, for example, by submitting jobs from a workstation or handheld device, without being physically near the printer. Cloud printing services eliminate the need to install local printer drivers on individual devices. Print jobs are sent to the printer via a cloud data center. Users can easily find available printers without manual setup. Cloud printing services also provide flexibility to work from anywhere employees, allowing them to be productive from various locations. [Brief explanation of the drawings]
[0005] Various embodiments are better understood with reference to the following description, claims, and accompanying drawings.
[0006] [Figure 1] FIG. 1 illustrates an example embodiment of a system for allocating and managing guest printing. [Figure 2] FIG. 1 illustrates an example embodiment of a networked digital device, such as a multifunction peripheral. [Figure 3] FIG. 1 illustrates an example embodiment of a digital device system. [Figure 4] 1 is a flow chart according to an example embodiment of a system for allocating and managing guest printing. [Figure 5] FIG. 2 is a block diagram illustrating an example embodiment of operations performed by a host company administrator. [Figure 6] FIG. 10 is a block diagram illustrating an example of an embodiment of an operation performed by a guest user. [Figure 7] FIG. 10 is a block diagram illustrating an example embodiment of a guest user's actions to release one or more listed jobs for processing. [Figure 8]FIG. 10 is a block diagram illustrating an example embodiment of a cleanup operation for an expired PIN. DETAILED DESCRIPTION OF THE INVENTION
[0007] The systems and methods of the present disclosure will now be described in detail, by way of example, with reference to the drawings. It will be understood that appropriate changes can be made to the examples, configurations, structures, components, elements, devices, apparatus, methods, systems, and the like disclosed and described herein, and that such changes may be desirable for particular applications. In this disclosure, descriptions identifying specific techniques, configurations, and the like are either related to the particular example presented or are merely a general description of such techniques, configurations, and the like. Descriptions identifying specific details or examples are not intended to, and should not be construed as essential to, or limiting of, the present disclosure, unless specifically specified otherwise.
[0008] A cloud printing service may register users based on the company associated with the domain name of the user's email address. Many companies can use the same cloud printing service. With cloud printing, a user can print or release jobs on the cloud from any MFP registered in the system, as long as the user and MFP belong to the same company. Users are associated with a company through a pre-configured company domain. For example, a user with the email domain "companyA.com" can be automatically registered to a company that also has the "companyA.com" domain in the system. After a user is registered, the same email address may not be registered with other companies that use the same cloud printing service. When a user submits a print job, the print job is associated with the company and the user. A user can only release jobs associated with their own company and themselves. Furthermore, the user may not be able to release jobs on MFPs owned by other companies. Therefore, when a guest visits a certain company, even if the guest is registered with a common cloud printing service, the guest cannot print his or her own job on the guest company's MFP because the guest belongs to a different company.
[0009] In the following description, a "host company" refers to the company that owns the MFP and allows guest printing, and a "guest company" refers to the company whose employees are visiting the host company. The example embodiments described herein provide systems and methods that allow visitors to print without creating a guest account for each visitor.
[0010] In the example embodiments detailed herein, a host company administrator adds a company as a guest company instead of creating guest users. This privilege can be revoked at any time. Users at a company with guest company privileges can choose to generate their own guest MFP login PIN (Personal Identification Number) for the host company. The administrator can set the validity period of the PIN, which may be short. Guests log in to the host MFP as guests using their guest login PIN. Guests can then review and release their submitted jobs as if they were authorized users of the host company. This allows the host company administrator to control which companies are granted guest company privileges. The system can also be configured to automatically consider all companies with a certain top-level domain as guest domains. Thus, companies with email domains "xyz.abc.com" and "pqrs.abc.com" are automatically considered guest companies by each other. Companies can negotiate which company (e.g., the guest or the host) pays for document processing jobs. This allows a user registered with another company to release their own jobs on an MFP registered with a company other than their own. This also allows a host company to set a company as a guest company. A preferred mode is one that allows companies with the same top-level domain to be automatically set as guest companies. Guest company privileges and the validity period of guest PINs can be determined between the companies. Furthermore, the companies can determine whether guest jobs should be counted as belonging to the host company or the guest company.
[0011] In one specific example, a user at Company B, "CompanyBuser1@companyB.com," is a registered user of the cloud printing service and is visiting Company A in the same region. This user cannot release jobs submitted to the commonly used cloud printing service from any of Company A's MFPs. In this example, an administrator at Company A configures, through their company portal, which companies qualify as guest companies and the maximum duration of guest logins to their MFPs. Company A may not allow this feature at all. The system is preferably configured so that companies with matching top-level domains automatically become guest companies of each other.
[0012] In a further example, a user at Company B logs into the cloud printing portal and creates a guest login PIN for any company that Company B allows as a guest. The guest login PIN is associated with the user, the user's company (Company B), and the host company (Company A). When CompanyBuser1 logs into Company A's MFP as a guest, CompanyBuser1 is authenticated as a guest user at Company A. At the same time, the cloud printing service also knows the guest user's actual company and is able to view documents the guest user has sent from their own account (Company B). Because the guest login PIN is associated with both the guest company and the host company, job costs can be attributed to either company based on the agreement between the two companies.
[0013] FIG. 1 illustrates an example embodiment of a system 100 for allocating and managing guest printing. One or more MFPs, such as MFP 104, communicate data via network cloud 108. Network cloud 108 preferably comprises a local area network (LAN), a wide area network (WAN) (which may include the Internet), or any suitable combination thereof. Network cloud 108 comprises any suitable wireless or wired data connection, or combination thereof, that enables data transfer between devices. Cloud print service server 112 also communicates data with network cloud 108. In the illustrated example, cloud print service server 112 provides the cloud printing service described above and operates a cloud print portal (hereinafter, the portal), which manages printing for a host company and guest company users who are visiting users from a guest company and who want to obtain printed materials while on the host company's premises. Guest company user 116 wishes to submit a document processing job, such as a print job, for rendering on MFP 104. The print job may be submitted from any suitable device in data communication with the network cloud 108 , such as via a workstation 128 or a smartphone or tablet 132 .
[0014] Prior to the above, the host company administrator 120 generates a list of approved companies. Preferably, the list is generated on the workstation 124. Guest printing can be permitted for visiting users with email address domains associated with entries in the approved company list. The approved company list is provided to the guest company user 116. Preferably, the list is displayed on the display of the user interface of the workstation 128. The guest company user 116 selects one or more approved companies for which he or she has printing privileges. This company may be the company associated with the domain name of the user's email address (if this option is allowed). The user may also be authorized for one or more companies in different domains. Once the user is associated with an approved company, the user is prompted to create a PIN. Once the PIN is created, the user can send print jobs to one or more target MFPs, such as MFP 104. The selected PIN is associated with the guest company user 116, the company associated with the user's email domain, and each selected guest company for which the user is authorized. As long as the cloud print service 112 is utilized, the print job awaits release from the MFP. The user then approaches MFP 104 and logs in using the PIN. If the PIN is valid, the user is authenticated as a host company user. A list containing the user's print jobs (preferably along with other jobs associated with the user or the user's company) is displayed.
[0015] Next, FIG. 2 illustrates an example embodiment of a networked digital device 200 configured as a document rendering system. The networked digital device 200 is preferably configured within an MFP, such as MFP 104 of FIG. 1. It will be appreciated that the MFP includes an intelligent controller 204, which is itself a computer system. Thus, the MFP itself can function as a server with the functionality described herein. The intelligent controller 204 includes one or more processors, exemplified by processor (CPU) 208. Each processor is preferably associated with non-volatile memory, such as read-only memory (ROM) 212 and random access memory (RAM) 216, via a data bus 220.
[0016] The processor 208 is also in data communication with an input / output interface 222. The input / output interface 222 preferably includes a user touchscreen. While the example embodiments described herein describe a touchscreen, it should be understood that any suitable user interface may be used, such as a keyboard, switches, a display, a trackball, a mouse, or the like.
[0017] The processor 208 is also in data communication with a storage interface 224 for reading from or writing to a storage device 228. The storage device 228 preferably comprises a hard disk, optical disk, solid state disk, cloud-based storage, or other suitable data storage device as will be appreciated by those skilled in the art.
[0018] The processor 208 also communicates data with additional interfaces, such as a Bluetooth interface 226 and an NFC interface 230 .
[0019] The processor 208 is also in data communication with a network interface 236. The network interface 236 provides an interface to a network interface controller (NIC) 240, which in turn provides a data interface to any suitable wired interface or physical network connection 244. Alternatively, the network interface 236 provides a wireless data connection via a wireless network interface 248. Examples of wireless network interfaces include optical, cellular, Wi-Fi, wireless universal serial bus (wireless USB), satellite, etc. Examples of wired interfaces include Ethernet, USB, IEEE 1394 (FireWire), Lightning, telephone line, etc.
[0020] The processor 208 may also be in data communication with any suitable user input / output (I / O) network interface 222 that provides data communication for interfacing with user peripherals such as a display, keyboard, mouse, trackball, touch screen, etc. The processor 208 may also be in communication with hardware monitors 252 such as page counters, temperature sensors, toner or ink level sensors, paper level sensors, etc.
[0021] Document processor interface 256 is also in data communication with data bus 220. Document processor interface 256 is an interface suitable for data communication with document rendering system 260, which includes MFP functional units. In the illustrated example, these units include a copy engine comprised of copy engine hardware 264, a scan engine comprised of scan engine hardware 268, a print engine comprised of print engine hardware 272, and a fax engine comprised of fax engine hardware 276, all of which comprise document rendering system 260. It will be understood that the functional units are preferably comprised of intelligent units including any suitable hardware or software platform.
[0022] FIG. 3 illustrates an exemplary embodiment of a digital data processing device 300, such as the cloud print service server 112, workstations 124 and 128, and smartphone or tablet 132 of FIG. 1. It should be understood that some of the components listed herein may not be necessary in a particular configuration. The components of the digital data processing device 300 preferably include one or more processors, exemplified by processor 304, memory, and bulk or other non-volatile storage 316. Preferably, the memory is comprised of ROM 308 and RAM 312, and the bulk or other non-volatile storage 316 is connected via a storage interface 320. Data communication between the components is achieved via a data bus 324. A network interface controller 328 preferably provides a gateway for data communication with other devices via any wireless or wired connection, such as a wireless network interface 332 or a wired connection. A user input / output (I / O) interface 336 preferably includes a display generator 340 that interfaces with a touchscreen display 344. As noted above, any suitable user input and display components may be used.
[0023] FIG. 4 is a flowchart 400 illustrating an example embodiment of a system for allocating and managing guest printing. In FIG. 4 , various operations by a guest company user and information presented to the guest company user are assumed to be performed using a workstation 128, a smartphone, or a tablet 132, unless otherwise specified. The process begins at block 404, where the guest company user logs in to a portal of the host company network at block 408. Upon the guest company user's login, a list of approved companies is displayed at block 412. The guest company user selects one or more companies for which the guest company user is authorized at block 416. The guest company user is then prompted to create a PIN, which the guest company user creates at block 420. Next, at block 424, the guest company user sends one or more print jobs to a selected MFP 104 owned by the host company. At block 428, the guest company user approaches the selected MFP 104 and logs in with the PIN via the MFP 104's user interface. At block 432, the cloud print service server 112 determines whether the entered PIN is valid. A PIN may become invalid due to a user input error, privilege revocation by the host company administrator 120, or a PIN expiration timeout. Additionally, a PIN may preferably expire after a pre-defined usage volume of document processing operations has been reached. Preferably, the expiration of one or more PINs associated with a pending guest company queue may trigger the removal of one or more corresponding print jobs from that queue. If the PIN is determined to be invalid (block 432, No), the MFP 104 displays an appropriate message to the user at block 436, and the process terminates at block 440. If the PIN is determined to be valid (block 432, Yes), the MFP 104 displays a list of the user's pending jobs (possibly along with a list of other jobs at authorized companies associated with the user) at block 444. Finally, the one or more print jobs submitted by the guest company user are released at block 448, and the process terminates at block 440.
[0024] 5 is a block diagram 500 illustrating an example embodiment of operations by a host company administrator. The host company administrator logs into the host company network portal via workstation 124 at block 504 and creates a list of approved guest companies managed by cloud print service server 112 at block 508. The administrator system can be configured to automatically add companies that share a top-level domain or a selected domain tree as approved companies.
[0025] 6 is a block diagram 600 illustrating an example embodiment of a guest company user's operations. The guest company user logs into the host company network portal via a workstation 128, smartphone, or tablet 132 at block 604 and selects from a list of approved companies at block 608. After making a selection, the guest company user is prompted to create a PIN, which is created at block 612. This PIN is associated with the user's company, one or more approved guest companies, and the guest company user.
[0026] 7 is a block diagram 700 illustrating an example embodiment of the operations a guest user performs to release one or more listed jobs for processing. At block 704, via workstation 128 or smartphone or tablet 132, the guest corporate user submits a job using their regular account. Next, at block 708, the guest corporate user approaches the MFP selected for the job and logs in with a PIN. At block 712, via workstation 128 or smartphone or tablet 132, one or more jobs for the guest corporate user, and possibly one or more jobs from other users belonging to the same company, are displayed. At block 714, via workstation 128 or smartphone or tablet 132, the user selects each job they wish to release. The jobs are then processed as if the user were an authorized user under the host corporate network.
[0027] 8 is a block diagram 800 illustrating an example embodiment of a cleanup operation for an expired PIN. When a PIN expires, the associated account is deleted by the cloud print service server 112 at block 804.
[0028] While specific embodiments have been described, these embodiments are merely examples and are not intended to limit the scope of the present invention. The novel embodiments described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions, and modifications may be made to the forms of the embodiments described herein without departing from the spirit of the present invention. The appended claims and their equivalents are intended to cover such forms and modifications as fall within the spirit and scope of the present invention.
Claims
1. a user interface including one or more user inputs and one or more displays; a data interface configured to receive and store in memory a guest company list indicating pre-registered guest companies; one or more processors, receiving a user login via the user interface; displaying an indicia corresponding to the guest business list on the user interface; receiving, via the user interface, a selection by the user of a guest business from the guest business list; Displaying a PIN selection prompt on the user interface; receiving, via the user interface, a selection of a PIN by the user in response to the PIN selection prompt; Associating the selected PIN with the selected guest company; transmitting a document processing job associated with the user to an image rendering device; receiving a login of the user using the selected PIN; displaying an indicia corresponding to the document processing job on the user interface; receiving a selection of the indicia by the user via the user interface; and one or more processors configured to release the document processing job for printing by an associated print engine in response to the indication being selected; A system comprising:
2. 2. The system of claim 1, wherein the one or more processors are further configured to determine whether the PIN selection is valid and selectively release the document processing job based on determining that the selected PIN is valid.
3. The system of claim 2 , wherein the one or more processors are further configured to delete pending document processing jobs associated with the user if the one or more processors determine that the PIN is invalid.
4. receiving a list of pre-registered guest businesses via a data interface and storing it in a memory; receiving a user login via a user interface including one or more user inputs and one or more displays; displaying an indicia corresponding to the guest business list on the user interface; receiving, via the user interface, a selection by the user of a business from the guest business list; displaying a PIN selection prompt on the user interface; receiving, via the user interface, a selection of a PIN by the user in response to the PIN selection prompt; Associating the selected PIN with the selected guest company; transmitting a document processing job associated with the user to an image rendering device; receiving a login of the user using the selected PIN; displaying an indicia corresponding to the document processing job on the user interface; receiving a selection of the indicia by the user via the user interface; responsive to said indication being selected, releasing said document processing job for printing by an associated print engine; Executed by at least one processor.
5. receiving and storing in memory company data identifying the guest company; generating a guest print permission list indicating guest companies that are permitted to print according to the received company data; transmitting said permission list to an associated multifunction peripheral device via a data interface; receiving, via the data interface, a selection of a guest business from the permission list; receiving, via the data interface, a selection of a PIN corresponding to the selected guest business; Associating the selected PIN with the selected business; receiving, via the data interface, a user login using the selected PIN; determining the validity of the selected PIN; if the selected PIN is determined to be valid, transmitting via the data interface a job list of pending document processing jobs associated with the selected business; receiving a job release selection for one or more document processing jobs in the job list; Releasing each selected document processing job for processing; Executed by at least one processor.