SIST ES 203 069 V1.2.1:2014

SLOVENSKI STANDARD
SIST ES 203 069 V1.2.1:2014
01-julij-2014
'RVWRSSULNOMXþNLSUHQRVLQPXOWLSOHNVLUDQMH$770'DOMLQVNRXSUDYOMDQMH
RSUHPHSULQDURþQLNX&3(SUHNãLURNRSDVRYQLKRPUHåLM3URWRNRO]DXSUDYOMDQMH
SURVWUDQHJDRPUHåMDRSUHPHSULQDURþQLNX&:03
Access, Terminals, Transmission and Multiplexing (ATTM) - Remote management of
CPE over broadband networks - CPE WAN Management Protocol (CWMP)
Ta slovenski standard je istoveten z: ES 203 069 Version 1.2.1
ICS:
33.060.40 Kabelski razdelilni sistemi Cabled distribution systems
SIST ES 203 069 V1.2.1:2014 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

The present document may be made available in more than one electronic version or in print. In any case of existing or

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive

Users of the present document should be aware that the document may be subject to revision or change of status.

Information on the current status of this and other ETSI documents is available at

If you find errors in the present document, please send your comment to one of the following services:

DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.

3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

Intellectual Property Rights ................................................................................................................................ 4

Foreword ............................................................................................................................................................. 4

Introduction ........................................................................................................................................................ 4

1 Scope ........................................................................................................................................................ 5

2 References ................................................................................................................................................ 5

2.1 Normative references ......................................................................................................................................... 5

2.2 Informative references ........................................................................................................................................ 5

3 Definitions and abbreviations ................................................................................................................... 6

3.1 Definitions .......................................................................................................................................................... 6

3.2 Abbreviations ..................................................................................................................................................... 6

4 Conventions .............................................................................................................................................. 6

5 Recommendations .................................................................................................................................... 7

6 Remote management of CPE over broadband networks .......................................................................... 8

6.1 Elements of the CPE WAN management protocol ............................................................................................. 8

6.1.1 TR-069: CPE WAN management protocol (CWMP) ................................................................................... 8

6.1.2 Auto-configuration and dynamic service provisioning ................................................................................. 9

6.1.3 Software/firmware image management ........................................................................................................ 9

6.1.4 Status and performance monitoring .............................................................................................................. 9

6.1.5 Diagnostics ................................................................................................................................................... 9

6.1.6 Security ......................................................................................................................................................... 9

6.2 Data models ........................................................................................................................................................ 9

6.2.1 TR-181: Device data model for TR-069 ..................................................................................................... 10

6.2.2 TR-157: Component objects for CWMP .................................................................................................... 10

6.2.3 TR-143: Enabling network throughput performance tests and statistical monitoring ................................. 11

6.2.4 TR-104: DSLHome provisioning parameters for VoIP CPE ...................................................................... 11

6.2.5 TR-135: Data model for a TR-069 enabled set-top box.............................................................................. 11

6.2.6 TR-140: TR-069 data model for storage service enabled devices .............................................................. 11

6.2.7 TR-196: Femto access point service data model ......................................................................................... 12

Annex A (informative): Bibliography ................................................................................................... 13

History .............................................................................................................................................................. 14

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information

pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in

respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee

can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

This ETSI Standard (ES) has been produced by ETSI Technical Committee Access, Terminals, Transmission and

The basis of the present document is the Broadband Forum CPE WAN management protocol (CWMP), commonly

The protocol is intended for communication between a CPE and an Auto-Configuration Server (ACS). The CPE WAN

management protocol defines a mechanism that encompasses secure auto-configuration of a CPE, and also incorporates

TR-069 [1] specifies the generic requirements of the management protocol, and methods that can be applied to any

TR-069 [1] CPE. Other Broadband Forum Technical Reports (TRs) specify the managed objects, or data models, for

The protocol can be used to manage various types of CPE, including stand-alone routers and LAN-side client devices. It

is agnostic to the specific access medium utilized by the service provider, although it does depend on IP-layer

The present document defines a European Standard (ES) for remote management of CPE WAN interfaces over

broadband networks. It provides an overview of a set of normative references to the suite of individual specifications

comprising the Broadband Forum (BBF) CPE WAN Management Protocol (CWMP) and Data models.

References are either specific (identified by date of publication and/or edition number or version number) or

non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the

Referenced documents which are not found to be publicly available in the expected location might be found at

NOTE 1: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

The following referenced documents are necessary for the application of the present document.

[5] Broadband Forum TR-140: "TR-069 Data Model for Storage Service Enabled Devices".

[6] Broadband Forum TR-143: "Enabling Network Throughput Performance Tests and Statistical

The following referenced documents are not necessary for the application of the present document but they assist the

[i.1] ITU-T Recommendation Y.101 (2000): "Global Information Infrastructure terminology: Terms

NOTE: Available at http://www.broadband-forum.org/about/download/trapprovalprocess.pdf.

[i.3] Broadband Forum TR-181 (Issue 1 - February 2010): "Device Data Model TR-069" (superseded

[i.4] Broadband Forum TR-098 (Amendment 2 - September 2008): "Internet Gateway Device Data

For the purposes of the present document, the terms and definitions given in ITU-T Recommendation Y.101 [i.1],

Customer Premises Equipment (CPE): end use system including private network elements connecting the customer

Technical Report (TR): approved technical specification of the Broadband Forum [i.2]

There are no particular notations, styles, presentations, etc., used within the present document.

The present document defines the requirements for the remote management of networked devices by a service provider

in a consumer's home. It provides an overview of and the necessary normative references to a family of technical

specifications (see figure 1). It describes how the various technical specifications in this family are related.

• The protocol allows both CPE and ACS initiated connection establishment, avoiding the need for a persistent

• The functional interactions between the ACS and CPE should be independent of which end initiated the

establishment of the connection. In particular, even where ACS initiated connectivity is not supported, all ACS

initiated transactions should be able to take place over a connection initiated by the CPE.

• The protocol allows one or more ACSs to serve a population of CPE. Each CPE can only be associated with