Managing New Devices on the Fly
The
Interaction in Your
OSS Environment
The
Figure 5. Multiple Device Activation Scenarios
primitives provide a powerful means for OSS applications to perform management operations on one or several devices with a single command.
System Architecture
The
Zero-Touch Activation Processes
(All processes are fully automated; no customer or operator intervention)
|
|
|
| Customer | ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Initial Device Status |
| Unique Credentials |
|
|
|
|
| (User name, password, |
| Default Credentials |
| Default Credentials | |
(Factory |
|
|
| |||
| management system URL) |
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Process Highlights |
| Configure Device |
| Set Unique Credentials |
| Set Unique Credentials |
| for Service |
| Configure Device for Service |
| Configure Device for Service | |
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Limited Upfront OSS |
| Device Configured |
| Devices Configured on the Fly |
Pros |
|
|
| Support for Customer | ||
| Adaptations |
| on the Fly |
| ||
|
|
|
| |||
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
| Factory |
|
|
|
|
Cons |
| Implies Logistic |
| Need Upfront OSS |
| Need Upfront OSS |
| Challenge and Device |
| Adaptations |
| Adaptations | |
|
|
|
| |||
|
| Delivery Lead Time |
|
|
|
|
|
|
|
|
|
|
|