Cloud Deployment Model: Architecture

The diagram below shows, at a very high level, the overall process of printing a document with Breezy:

1. From the app, the user selects desired printer, the document is then encrypted and uploaded to the Breezy Cloud.
2. Next, the Connector detects and downloads the pending document.
3. Connector downloads and decrypts the document using its own private key.
4. Finally, the Connector sends the document to the printer.

Astute observers will recognize that the diagram above leave some questions unanswered. The following outline specifies, step by step, exactly what happens when a user prints with Breezy.

1. The mobile user selects content to print and chooses a printer.
2. The Breezy mobile app receives an encryption key associated with a Rendering Engine, which it uses to encrypt the content (hereafter called a "document").
3. The Breezy mobile app uploads the encrypted document to a temporary storage location specified by the local Breezy administrator.
4. The Breezy mobile app sends Routing Information to the Breezy API, informing the API that the document is ready to be rendered.
5. The Rendering Engine (not shown in the diagram above):
1. retrieves the encrypted document from temporary storage;
2. decrypts the document using its own private key;
3. renders to the appropriate format (PDF, PCL, PostScript, etc.);
4. re-encrypts the document, using an encryption key associated with the Breezy Connector connected to the printer the user chose;
5. uploads the re-encrypted document to the temporary storage location; and
6. notifies the Breezy API that rendering is complete.
6. The Breezy Connector, upon notification from the Breezy API that rendering is complete:
1. retrieves the document from from temporary storage;
2. decrypts the document using its own private key;
3. submits the document to the printer; and
4. notifies the Breezy API that the document has been printed.