WPP Gen2

Registration

Jan - 2017

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Agenda
• What is Registration?
• Gen1 Registration-
• 10 thousand feet view
• Failure waterfall & Production data
• Gen2 – Design Principles
• Registration in Gen2
• Key problems and their solutions
• Deployment Architecture
WPP – Enabler for Cloud Use cases
Meter Reads
Print Solutions
Supplies Data
Print

Connectivity
PaaS
Supplies
Enterprise Consumer
Replenishment
Cloud Platform

Big Data

Signup Fleet Management

Registration – What
• Registration is a one time signup process triggered by user.

• Registration gives a remote identity to the printer

o Cloud_id – used by web clients to identify a printer remotely
Cloud Platform
o email_address
Connection
• Using cloud_id, printer will maintain a connection with cloud. cloud_id
with cloud
email_address

• Driver less printing

• Primary Solutions
• Email print using email_id
• Scan to cloud.
Gen-1 : Current State

2200+ 50k 73M

Models reg/day Printers

99% 99.9%
Reliability Availability
Gen1
Registration

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Gen1 – Device onboarding/Registration
APIs Processing Connectivity

X
M
P Persistent Connection
P

Pull Print Content

Register Device
Channel
Worker
Registration

DB CPGDB CPGDB Shard

HPIT Infrastructure
Registration Flow – Failure Waterfall

1. REGISTER 2. XMPP CONNECT 3. DISCOVER 4. SUBMIT INFO

API • Printer Connects to CAPABILITIES PAGE
• Printer connects to cloud over XMPP • Cloud Discovers the • Cloud Prints an
cloud and gets an Capabilities of the Instruction page.
identity( PrinterID, Printer
EmailAddress, JabberID).

1.1 - Invalid Schema
(FW)
1.2 - WPP Error
2.1 - XMPP Connection Not
Established
2.2 - XMPP Tigase Error (WPP)
3.1 - Printer failed to respond to 4.1 - WPP Error
discovery call (FW)
3.2 - Printer already de-registered
3.3 - Device Error (FW)
3.4 - WPP Error

Key Focus Areas based on analytics data

Waterfall – Distribution by Components for all other ICS Models
Data considered is from 02/01/14 to 02/28/2014

CPG registration steps

WPP Pipe Printer

(All ICS Models) 682,956 657,484 639,435

Total Reg Request 693,062 98.54% 94.87% 92.19%

2.1 - XMPP Connection Not Established 3.67%

3.1 - Printer failed to respond to

1.38%
discovery call

3.2 - Printer already de-registered 2.68%

4.1 – Failed Welcome Page Submission 0.08%

Limitations
• DB
• Shared central DB
• Connectivity
• Persistent connection required for success
• Timing
• Distributed timing sync required.
• Security – Shared secret model.
• Supported only device data model and limited to extension for IOT
use cases.
Gen2
Registration

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Design Principles
• Small atomic registration steps
• Extensibility between devices and solutions
• Increased security
• Micro-services
• No shared DB
• Printer as a client.
• No persistent connection required for onboarding
Gen2 Registration
Step -1: Identity Bootstrapping
• Generates cloud_id
• Uses POSTCARD Protocol
Connectivity Identity Device • Once in printer lifetime
Configuration Bootstrapping Configuration

Step1
Step 2 Step3
Gen2 Registration

Connectivity Identity Device

Configuration Bootstrapping Configuration
Step-2: Connectivity Configuration
• Signaling – UDP & HTTP
Step 2 • Websocket Tunneling
Step1 • Signal bits on Printer
Step3 • Kick, MCS, Print, Scan and Device
UDP/HTTP Configuration etc…
Signaling polling
• control plane - data plane design pattern
• Using signal bit we can control the
behavior of printer
• Printer acts based on signal bit
request.
Web Socket Tunneling
Gen2 Registration

Connectivity Identity Device

Configuration Bootstrapping Configuration

Step1
Step 2 Step3

Step-3: Device Configuration

• Generates Email-id.
• Printer capabilities will be pushed to cloud
(using HTTP).
• Printer native welcome page.
Cloud-Id Algorithm
JAMC Service Registration
Step -1: Identity Bootstrapping
• Generates cloud_id
Connectivity Identity JAMC Service • Uses POSTCARD Protocol
Configuration Bootstrapping
• Once in Service lifetime

Step 2
Step-2: Connectivity Configuration
Step1 Signal • Signaling – Only HTTP
Management • JAMC Signal bit
HTTP
• On signal bit request from JAMC
Signaling Service, JAMC Client would push
the printers data payload to JAMC
Service.
Enterprise
JAMC Client
Gen2 registration enabling Solution
Solutions
• Registration doesn’t need persistent connection (Signaling or websocket)
• Three independent steps
• Printer as a client
• Cloud_id embedded with pod_id

Extending Solution
• JAMC Service registration
• HPC Claim before registration (using printer-code generated by printer)
• Simplify II enrollment by reduced dependency on Registration
• Ability to host Region based POD
• IOT platform
 Deployment View

• Each POD capable to handle 7.5 Million printers

• POD based scale-out deployment model
• Flex-up and Flex-down of services as needed/scale
• Deployment in AWS 19
Thank you

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.