THOMSON TR-069 Configuration Manual page 108

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
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.
For more information on firmware upgrades, see
The ACS uses the data model to configure the Thomson Gateway via the
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).
For more information on service provisioning, see
The ACS can use a
by the data model.
For more information on configuration updates, see
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
(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
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:
Pre-provisioned ISP.def
(default ACS, default auth)
4) Apply parameters
(and env variables)
7) Close connection
102
configuration file or script file download
associates the CPE with the subscriber and configures the CPE with the proper
does all of the per-subscriber-per-service provisioning. So once the provider ACS is
CPE
1) Inform (Event Bootstrap)
NoMoreRequests = 1
3) InformResponse,
SetParameterValues
5) SetParameterValuesResponse
6) 200 OK (Empty)
"3.1 Firmware Upgrade" on page
"6 Service Provisioning" on page
to configure all modules not (yet) supported
"3.2 Configuration Update" on page
Walled garden
ACS
2) Relate CPE to user/subscription
PPP Username
PPP Password
ACS URL
ACS Username
ACS Password
8) Inform (Event Bootstrap)
NoMoreRequests = 1
9) InformResponse
10) HTTP POST (Empty)
11) 200 OK (Empty)
firmware upgrade
32.
SetParameterValues RPC. This
69.
41.
Provider
ACS
E-DOC-CTC-20071119-0003 v1.0
to