THOMSON TR-069, Руководство по настройке

Страница: 107 / 110

E-DOC-CTC-20071119-0003 v1.0
101
7| Zero-Provisioning
7 Zero-Provisioning
Introduction
The zero-provisioning use case considers the auto-configuration of the CPE without any user interaction.
It is based on two assumptions:
Pre-provisioned connectivity
Subscriber-gateway relation identification
Pre-provisioned connectivity
It is assumed that the CPE is pre-provisioned with connectivity to an ACS.
This pre-provisioning includes following aspects:
WAN connection model : for example:
Separate management PVC (IPoA, EoA) with basic IP connectivity to the ACS. In this case, CPE-to-
ACS authentication is not needed.
PPP connection with walled garden common login, e.g. a single username/password that grants
access to only the ACS.
PPP connection with e.g. CPE serial number as username.
ACS :
ACS URL: the host part of the ACS URL is resolved into the ACS IP address.
ACS authentication: user name/password only if needed. The ACS could accept first time
unauthorized access or e.g. CPE serial number as user name/password.
TLS certificates :
ACS-to-CPE authentication: a CA certificate (e.g. a server provider certificate) must be pre-
provisioned on the CPE.
CPE-to-ACS authentication: each CPE certificate is signed by e.g. a service provider CA or the ACS
trusts the CPE CA.
Subscriber-CPE relation identification
Learning the subscriber-CPE relation is mainly the task of the ACS. Two cases are possible:
The relation is pre-configured : the relation between the CPE, subscriber and subscribed-to-services is
pre-configured (e.g. in a shop when buying the CPE).
The ACS learns the relation dynamically : based on the IP address of the CPE, the ACS learns from the
BRAS which DSL line-ID it was assigned to. Using the line-ID, the ACS can query the AAA database to
learn the subscriber credentials (PPP user name/password) and the subscribed-to-services (needed for
knowing which services to auto-provision).
Pre-provisioning can be achieved via Thomson Gateway ISP defaults (ISP.def) . This is a set of
defaults that is preserved even when the end-user or the ACS triggers a reset-to-factory-defaults.
After this action, the zero-provisioning use case is started again.