THOMSON TR-069, Configuration Manual

Page: 108 / 110

E-DOC-CTC-20071119-0003 v1.0
102
7| Zero-Provisioning
Description
First, the Thomson Gateway connects to the (potentially walled garden) ACS that learns the subscriber
information and services.
Next, following actions can be taken:
Before any configuration changes are made, the ACS can be configured to start a firmware upgrade to
the most recent firmware version. This firmware would include the same ISP defaults (ISP.def) so after
the firmware upgrade, the Thomson Gateway connects to the ACS again.
The ACS uses the data model to configure the Thomson Gateway via the SetParameterValues RPC . This
typically includes customer specific parameters (PPP user name/password, ACS URL, ACS connection
request authentication, wireless settings and optionally voice settings (e.g. SIP URI and authentication).
The ACS can use a configuration file or script file download to configure all modules not (yet) supported
by the data model.
The case where only data model parameters are configured on top of the pre-provisioned settings (ISP.def) is
the most straightforward. The ACS sends a SetParameterValues RPC for the parameters that need to be
configured. These parameters are applied and saved persistent on the Thomson Gateway.
Message flow: minimal walled garden provisioning
This use case makes use of two types of ACS:
The walled garden ACS associates the CPE with the subscriber and configures the CPE with the proper
(user specific) connectivity parameters. So the difference with the “zero-provisioning” use case is that the
walled garden ACS is dedicated to configuring the CPE out of the walled garden.
The provider ACS does all of the per-subscriber-per-service provisioning. So once the provider ACS is
contacted, firmware upgrade, configuration update, service activation and remote intervention use cases
are supported.
Following illustration shows the message flow for the “Minimal walled garden provisioning” use case:
For more information on firmware upgrades, see “3.1 Firmware Upgrade” on page 32 .
For more information on service provisioning, see “6 Service Provisioning” on page 69 .
For more information on configuration updates, see “3.2 Configuration Update” on page 41 .
6) 200 OK (Empty)
Walled garden
ACS
CPE
1) Inform (Event Bootstrap)
NoMoreRequests = 1
3) InformResponse,
SetParameterValues
5) SetParameterValuesResponse
7) Close connection
Pre-provisioned ISP.def
(default ACS, default auth)
Provider
ACS
2) Relate CPE to user/subscription
4) Apply parameters
(and env variables)
11) 200 OK (Empty)
8) Inform (Event Bootstrap)
NoMoreRequests = 1
9) InformResponse
10) HTTP POST (Empty)
PPP Username
PPP Password
ACS URL
ACS Username
ACS Password