2.5.3.7.4 Submitting a Print Job Using Branch Office Print Mode
Goal: To print a document.
Context of Use: The user who uses an application that can print a document wants to print. A connection to a shared print queue has been previously established. The shared print queue is in branch office print mode. The user initiates printing from the application.
The print client uses the functionality in the Print System Remote Protocol [MS-RPRN] in this use case unless noted otherwise.
Direct Actor: The direct actor is the print client.
Primary Actor: The primary actor is the user.
Supporting Actors: The supporting actor is the print server.
Stakeholders and Interests:
Print client: The print client sends the print job data directly to the print device.
Print server: The print server receives branch office print remote logging entries corresponding to the print job status from the print client.
User: The user wants to print a copy of content on the computer.
Preconditions: The print spooler service is operational on the print client. The print client is a member of a domain and is connected to a network. The network is operational. The Active Directory system is available and operational.
Minimal Guarantee: The print job is submitted directly to the print device.
Success Guarantee: The job is submitted, and the job progress status is received and displayed to the user.
Trigger: A user initiates this use case by using a printing command from a printing-capable application.
Main Success Scenario:
The print client renders the metafile to the printer-specific raw format before sending it as a data-stream payload directly to the print device.
The print client starts a new print job to the print device using either the TCPMON port monitor module ([MS-RPRN] section 3.1.4.11.3), WSDMON ([MS-RPRN] section 3.1.4.11.4), or APMON ([MS-RPRN] section 3.1.4.11.5).
After sending all the pages of the print job to the print device, the print client ends the print job.
Extension (a) – The print client sends branch office print remote logging entries to the print server:
Following the preceding step 3:
4. The print client checks the branch office print configuration data if branch office print remote logging is enabled.
5. If it is enabled, the print client opens a printer handle.
6. The print client creates and sends applicable branch office print remote logging entries to the print server for processing.
7. The print client checks the branch office print offline archive, and if populated, sends the contained branch office print remote logging entries to the print server for processing.
8. The print client closes the printer handle.
Extension (b) - The print client archives branch office print remote logging entries for an offline print server:
Following the preceding step 3:
4. The print client checks branch office print configuration data if branch office print remote logging is enabled.
5. If it is enabled, the print client attempts to open a printer handle.
6. If the print server is not available, the print client creates the branch office print remote logging entries in the branch office print offline archive.
Variation (a) - Performing the use case by using an asynchronous printing: All details are identical to the use case described in this section, except that the Print System Asynchronous Remote Protocol [MS-PAR] is used instead of the Print System Remote Protocol.