THOMSON TR-069 Configuration Manual
  1. Manuals
  2. Brands
  3. THOMSON Manuals
  4. Gateway
  5. TR-069
  6. Configuration manual

THOMSON TR-069 Configuration Manual

R7.4 and higher
Hide thumbs
Table of Contents

Advertisement

Quick Links

Thomson Gateway
TR-069 Configuration Guide
R7.4 and higher

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TR-069 and is the answer not in the manual?

Questions and answers

Related Manuals for THOMSON TR-069

Summary of Contents for THOMSON TR-069

  • Page 1 Thomson Gateway TR-069 Configuration Guide R7.4 and higher...

  • Page 3: Thomson Gateway

    Thomson Gateway TR-069 Configuration Guide R7.4 and higher...
  • Page 4 Distribution and copying of this document, use and communication of its contents is not permitted without written authorization from Thomson. The content of this document is furnished for informational use only, may be subject to change without notice, and should not be construed as a commitment by Thomson. Thomson assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.

  • Page 5: Table Of Contents

    About this TR-069 Configuration Guide ........1 1 Introduction.................. 3 References and Related Documents ............... 4 CWMP Transaction Sessions ................6 IGD Data model on the Thomson Gateway ........... 10 2 Configuring CWMP on the Thomson Gateway ...... 13 Configuring TLS .................... 14 2.1.1 TLS Client ..............................
  • Page 6 Contents Retrieval of the Device Log ................56 Event Subscription ..................57 5 WAN Connections ..............59 WAN Connection Device ................61 WAN PPP or IP Connection ................62 Connection Information ................65 Forwarding Entries ..................66 6 Service Provisioning..............69 VoIP.......................

  • Page 7: About This Tr-069 Configuration Guide

    Terminology Generally, the Thomson Gateway123 will be referred to as Wireless USB Adaptor in this TR-069 Configuration Guide. Typographical Conventions Following typographical convention is used throughout this manual: Sample text indicates a hyperlink to a Web site.
  • Page 8 This TR-069 Configuration Guide provides technical information on TR-069 and how this relates to the various Thomson Gateway products. In the first chapter, a brief introduction to the TR-069 CWMP protocol and the TR-098 IGD data model is presented. The following chapter gives detailed information on the configuration of CWMP on the Thomson Gateway using CLI commands.

  • Page 9: Introduction

    Introduction Introduction Introduction This chapter provides a short introduction to the TR-069 CWMP protocol and the TR-098 IGD data model. Overview This chapter is structured as follows: Topic Page “1.1 References and Related Documents” “1.2 CWMP Transaction Sessions” “1.3 IGD Data model on the Thomson Gateway”...

  • Page 10: References And Related Documents

    CWMP. For more information on the IGD data model, see: Technical Report “TR-098 - Internet Gateway Device Version 1.1 Data Model for TR-069”, DSL Forum, September 2005. Technical Report “TR-098 Amendment 1 - Internet Gateway Device data model for TR-069”, DSL Forum, November 2006.
  • Page 11 “Interoperability test plan for TR-069 plugfests”, June 2006: this document defines TR-069 tests and their expected outcome. These tests are used during the TR-069 plugfests as tests to perform. The DSL Forum regularly organizes TR-069 plugfest test events where all participating CPE devices can test against all participating ACS servers.

  • Page 12: Cwmp Transaction Sessions

    Introduction CWMP Transaction Sessions What is a transaction session? TR-069 defines a transaction session as a sequence of Remote Procedure Calls (RPCs), both requests and responses. A transaction session is completed when both parties (CPE and ACS) have no messages left to send.
  • Page 13 The ACS activates the required services on the CPE, according to the “activation policies”. For example, the ACS configures the voice service and wireless service. Forced reboot The Reboot RPC causes the CPE to reboot. This forced reboot might be desired to restart the Thomson Gateway clearing all state. E-DOC-CTC-20071119-0003 v1.0...
  • Page 14 Introduction When the CPE receives a Reboot RPC from the ACS, following steps are executed: The ongoing transaction session is finalized. This means that all outstanding requests are sent and all responses are received. After finalization, the ongoing transaction session is closed. The CommandKey argument of the Reboot message must be remembered across the reboot via either: Writing it to the memory prozone.
  • Page 15 Introduction File transfer is initiated: a HTTP GET message is sent by the CPE to the file server. File transfer is completed (or an error occurred). A new transaction session to send the TransferComplete RPC is established after loading the downloaded configuration file or firmware image.

  • Page 16: Igd Data Model On The Thomson Gateway

    Introduction IGD Data model on the Thomson Gateway Data model overview Following illustration shows the IGD data model on the Thomson Gateway with (multiple instance) devices and services: InternetGatewayDevice WANDevice DeviceInfo Service WANConnectionDevice WANCommonInterfaceConfig Service ManagementServer Service WAN*LinkConfig WAN**Connection Service...
  • Page 17 This OUI or domain name must be assigned to the organization that defined the parameter, which is not necessarily the same as the vendor of the CPE or ACS. For vendor specific parameters of the Thomson Gateway, i.e. Thomson Gateway proprietary parameters, <VENDOR>...
  • Page 18 Introduction E-DOC-CTC-20071119-0003 v1.0...

  • Page 19: Configuring Cwmp On The Thomson Gateway

    Configuring CWMP on the Thomson Gateway Introduction This chapter describes in detail the configuration of CWMP on the Thomson Gateway using CLI commands. This includes the configuration of the TLS/SSL client and certificates, the CWMP service manager and daemon, and the state checks to detect service activity.

  • Page 20: Configuring Tls

    Configuring CWMP on the Thomson Gateway Configuring TLS Introduction The use of TLS/SSL is optional. Whether or not to use TLS/SSL is derived form the ACS URL scheme or file URL scheme: If the URL scheme starts with https://, TLS/SSL is used.

  • Page 21: Tls Client

    State: this parameter indicates the state of the TLS client. By default, the TLS client is enabled. Auth-serv: if this parameter is enabled, the TLS client (Thomson Gateway) requests authentication of the TLS server (ACS). By default, this parameter is enabled.

  • Page 22: Tls Certificates

    This certificate can only be altered through file upload (using FTP or TR-069). If no certificate is found when the Thomson Gateway is booting, it generates its own certificate and private/public key pair. The Thomson Gateway signs the certificate using its own private key.
  • Page 23 Expand: if this parameter is enabled, more information is displayed. A base64 dump of each displayed certificate is shown. =>:tls acs-client cert list expand=enabled Pre-provisioning ACS certificates The Thomson Gateway can receive the pre-provisioned certificates for server authentication as follows: File upload: through file upload (using FTP or TR-069). Proceed as follows when using FTP: Set up an FTP session from your PC to the Thomson Gateway.

  • Page 24: Configuring Cwmp

    Configuring CWMP on the Thomson Gateway Configuring CWMP Introduction The implementation of CWMP on the Thomson Gateway is split up in two parts: CWMP service manager: use the service manager to: Enable or disable the CWMP client. Assign a specific QoS label and route label to traffic originated by the CWMP client.

  • Page 25: Cwmp Service Manager

    State: by default, the CWMP client service is disabled. To enable the service, execute following command: =>:service system modify name=CWMP-C state=enabled Qoslabel: the Thomson Gateway supports application-based QoS label assignment. If the value of this none attribute differs from , all CWMP client originated data automatically has a QoS label assigned. This QoS label determines the internal QoS class of the data.
  • Page 26 Configuring CWMP on the Thomson Gateway CWMP connection request server To display the default attribute values of the CWMP connection request server service, execute following command: =>:service system list name=CWMP-S expand=enabled Idx Name Protocol SrcPort DstPort Group --------------------------------------------------------------------------------- 1 CWMP-S 51005 Description....

  • Page 27: Cwmp Daemon As Seen From The Acs

    Full: to enable both read and write RPC methods, the operational mode must be set to full. This is the default mode. As more operators are performing TR-069 tests and become ready to deploy it, there is less use and request for a read-only mode.
  • Page 28 ConnectionRequest: if this parameter is enabled, the CWMP client establishes a connection to the ACS when it successfully receives a Connection Request notification. These Connection Request notifications also use HTTP. However, in this case, the ACS acts as the HTTP client and the Thomson Gateway acts as the HTTP server.
  • Page 29 Qos-class: this parameter specifies the internal QoS class of Thomson Gateway originated CWMP data. The Thomson Gateway uses 16 internal QoS classes, numbered from 0 (low priority) through 15 (high priority). With QoS enabled, this makes sure that upstream CWMP data is mapped into the desired QoS queue, allowing prioritization or guaranteeing a minimum bandwidth.

  • Page 30: Cwmp Daemon Towards The Acs

    Url: this parameter specifies the HTTP URL of the ACS. Username: this parameter defines the username for authentication of the Thomson Gateway at the ACS. The ACS default username is <OUI> - <serial number>. This can be achieved using CLI environment variable concatenation.

  • Page 31: Notification Rules

    Configuring CWMP on the Thomson Gateway 2.2.4 Notification Rules Introduction The ParameterList argument of an Inform message contains a list of informational parameters and their values. The list includes: Required parameters: these parameters must be sent in each Inform message.

  • Page 32: Runtime Variables

    Configuring CWMP on the Thomson Gateway 2.2.5 Runtime Variables Listing runtime variables The values of the runtime variables cannot be changed and can only be listed. To list the CWMP runtime variables, execute following command: =>:cwmp runtimevar Software Version : 7.4.2.2...
  • Page 33 Configuring CWMP on the Thomson Gateway At each point in time, InternetGatewayDevice.ManagementServer.ParameterKey has the value of the ParameterKey argument of the most recent applied RPC. The ACS can check the ParameterKey value to identify parameter updates, object creations or object removals.

  • Page 34: Configuring State Checks

    Configuring CWMP on the Thomson Gateway Configuring State Checks Introduction If the state check module is enabled, the module periodically performs a number of parameter checks. Each parameter check results in a “Check” boolean set to 1 or 0. The parameter checks are grouped in different groups. First, the check results within a single group are combined (ANDed or ORed) in a “Group”...
  • Page 35 Configuring CWMP on the Thomson Gateway Deleting a group :statecheck groupdelete To delete a group, execute the command and specify following parameter: Name: the name of the group to be deleted. For example, delete a group as follows: =>:statecheck groupdelete name=DSLActivity...
  • Page 36 Configuring CWMP on the Thomson Gateway E-DOC-CTC-20071119-0003 v1.0...

  • Page 37: Firmware Upgrade And Configuration Update

    Firmware Upgrade and Configuration Update Firmware Upgrade and Configuration Update Introduction For the use cases described in this chapter, we make following assumptions: The CPE has IP connectivity to the ACS. The CPE is preconfigured with: ACS IP address:port ACS username and password ConnectionRequest username and password All passwords are stored encrypted in the persistent configuration file.

  • Page 38: Firmware Upgrade

    Firmware Upgrade and Configuration Update Firmware Upgrade Overview This section is structured as follows: Topic Page “3.1.1 General Firmware Upgrade Mechanism” “3.1.2 Single Memory Bank Firmware Upgrade” “3.1.3 Dual Memory Bank Firmware Upgrade” “3.1.4 Firmware Upgrade with Reduced Memory Mode” E-DOC-CTC-20071119-0003 v1.0...

  • Page 39: General Firmware Upgrade Mechanism

    CPE: the actions taken by the CPE itself depend on the firmware upgrade mechanism, which is defined by TR-069. This is indicated by the “CPE firmware upgrade process” in following illustration. The different firmware upgrade mechanisms are described in different subsections.

  • Page 40: Message Flow

    Firmware Upgrade and Configuration Update Message flow The message flow between the CPE and ACS is identical for all firmware upgrade mechanisms. Following illustration shows the message flow for the “Firmware Upgrade” use case (we assume that the MaxEnvelopes argument of the first Inform RPC has value 1): File Server 1) Schedule firmware upgrade 2) HTTP GET to...

  • Page 41: Single Memory Bank Firmware Upgrade

    3.1.2 Single Memory Bank Firmware Upgrade Introduction All Thomson Gateway residential RTEMS devices have a single memory bank (Flash). Description First, the CPE receives a Download RPC from the ACS. If the FileType argument is set to “1 Firmware Upgrade Image”, a firmware upgrade is started.
  • Page 42 Flash. When, for example at power up, the Thomson Gateway detects the absence of a valid firmware image, the Thomson Gateway sets e.g. the “Flashing Failed” prozone bit and reboots in Bootloader mode. This mode is also indicated by the LEDs.

  • Page 43: Dual Memory Bank Firmware Upgrade

    3.1.3 Dual Memory Bank Firmware Upgrade Introduction Some Thomson Gateway business RTEMS devices have a dual memory bank (Flash). Description First, the CPE receives a Download RPC from the ACS. If the FileType argument is set to “1 Firmware Upgrade Image”, a firmware upgrade is started.
  • Page 44 Whenever something goes wrong while downloading or flashing a new firmware image, there is always a valid firmware image present in Flash. When the Thomson Gateway detects that the downloaded file is invalid or when there is a problem loading the file, the file system automatically remounts the partitions to load the old firmware image.

  • Page 45: Firmware Upgrade With Reduced Memory Mode

    The new firmware image is downloaded and written to SDRAM. The Thomson Gateway reboots (setting a flag in prozone). The Bootloader detects that the new firmware image is still in SDRAM and writes the new firmware image to Flash. Prior to this, the Bootloader checks whether the new firmware image is valid.
  • Page 46 Robustness: this upgrade mechanism is not robust. Unplugging the CPE during the flash process makes it only recoverable with a rescue CDROM. Service interruption: step 1, when the Thomson Gateway reboots in “reduced memory mode”, is the service interrupting step. Up till that point, all services are running and active. E-DOC-CTC-20071119-0003 v1.0...

  • Page 47: Configuration Update

    Firmware Upgrade and Configuration Update Configuration Update Overview This section is structured as follows: Topic Page “3.2.1 Configuration Update Mechanism” “3.2.2 STS Files” “3.2.3 Embedded STS (eSTS) Files” E-DOC-CTC-20071119-0003 v1.0...

  • Page 48: Configuration Update Mechanism

    Firmware Upgrade and Configuration Update 3.2.1 Configuration Update Mechanism Why configuration update? A configuration update focuses on management of the home network. It is used to configure the CPE services and (typically router) features that apply to the home network functionality. File types For a configuration update, one of the following file types can be used: Configuration file (user.ini)
  • Page 49 Firmware Upgrade and Configuration Update Message flow The message flow between the CPE and ACS is identical for configuration files and script files. Following illustration shows the message flow for the “Configuration Update” use case (we assume that the MaxEnvelopes argument of the first Inform RPC has value 2): File Server 1) Schedule configuration update 2) Inform (Event Periodic)

  • Page 50: Sts Files

    IGD data model. STS file format An STS file is a text file containing CLI commands that can be executed on the Thomson Gateway. The main differences between a configuration file and an STS file are listed in following table: Configuration file (user.ini)
  • Page 51 Locally testing STS files Before starting a TR-069 configuration update with an STS file, you may test the STS file locally in order to make sure all commands are properly formatted and run without problems.

  • Page 52: Embedded Sts (Ests) Files

    STS file download requires a longer time and is more vulnerable to failures. How to embed STS files? The process of embedding an STS file in a software build is executed by Thomson during customization, prior to delivery. The use of eSTS files is customizable using the...

  • Page 53: Monitoring And Diagnostics

    In this chapter, we describe several use cases that can be used by the help desk to obtain information on the home network and its network connections. As CWMP is a protocol on top of IP, the use cases assume IP connectivity between the Thomson Gateway and the ACS.

  • Page 54: View On Home Network

    Monitoring and Diagnostics View on Home Network Introduction The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.LANDevice.1.Hosts.”. This hosts table provides a list of all devices that are connected via the local network. For each device, the list...
  • Page 55 Monitoring and Diagnostics Name Value InternetGatewayDevice.LANDevice.1.Hosts.Host.1.MACAddress 00:0f:1f:83:d7:5b InternetGatewayDevice.LANDevice.1.Hosts.Host.1.HostName thomson-2cfa009 InternetGatewayDevice.LANDevice.1.Hosts.Host.1.InterfaceType thomson-2cfa009 InternetGatewayDevice.LANDevice.1.Hosts.Host.1.Active E-DOC-CTC-20071119-0003 v1.0...

  • Page 56: Diagnostics

    DLS statistics The object “InternetGatewayDevice.WANDevice.1.WANDSLInterfaceConfig.“ is relevant to the DSL statistics. This object on the Thomson Gateway contains following vendor specific parameters: X_000E50_NumberOfResets: number of CPE resets. Stats.Showtime.X_000E50_LossOfSignal: number of times that a loss of signal occurred since the most recent DSL showtime.
  • Page 57 WLAN statistics The object “InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.“ is relevant to the WLAN statistics. This object on the Thomson Gateway contains following vendor specific parameters: X_000E50_ChannelMode: this parameter can be used to request automatic selection of the channel. The parameter has one of the following values:...
  • Page 58 Monitoring and Diagnostics Name Value InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.MaxBitRate Auto InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.Channel InternetGatewayDevice.LANDevice.1.WLANConfiguration.1. Auto X_000E50_ChannelMode InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID SpeedTouchEF5A50 InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.BeaconType None Gateway LAN side IP addresses and DHCP pool configuration The object “InternetGatewayDevice.LANDevice.1.LANHostConfigManagement.“ is relevant to the LAN side configuration information. This object contains no vendor specific parameters. To retrieve the gateway LAN side IP addresses and the DHCP pool configuration, the GetParameterValues (message 1 in preceding illustration) contains following ParameterNames argument:...
  • Page 59 Monitoring and Diagnostics TCP and UDP statistics The object “InternetGatewayDevice.X_000E50_Connection.“ is a proprietary data model. This object can be used to obtain statistics on current TCP and UDP connections. To obtain these statistics, the GetParameterValues RPC (message 1 in preceding illustration) contains following ParameterNames argument: Entry Value...

  • Page 60: Ip Ping Diagnostics Test

    The IGD data model contains the object “InternetGatewayDevice.IPPingDiagnostics.”. This object provides access to an IP ping diagnostics test. Using TR-069, the ACS can initiate the test on the CPE. Afterwards, the CPE reports the completion of the test to the ACS. This allows the ACS to ask for the results of the test.
  • Page 61 Monitoring and Diagnostics Name Value InternetGatewayDevice.IPPingDiagnostics.DSCP InternetGatewayDevice.IPPingDiagnostics.DiagnosticsState Requested Obtaining the test results: to retrieve the results of the test, the GetParameterValues RPC (message 9 in preceding illustration) contains following ParameterNames argument: Entry Value InternetGatewayDevice.IPPingDiagnostics. For example, the GetParameterValuesResponse (message 10 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value...

  • Page 62: Retrieval Of The Device Log

    Monitoring and Diagnostics Retrieval of the Device Log Introduction The IGD data model contains the DeviceLog parameter, which is located within the object “InternetGatewayDevice.DeviceInfo.”. When the ACS asks for the device log of the CPE, it receives the “upper” 32 Kbyte of the syslog message buffer contents. Message flow Following illustration shows a possible message flow for the retrieval of the device log: Transaction session...

  • Page 63: Event Subscription

    Monitoring and Diagnostics Event Subscription Introduction The ACS can subscribe to particular parameter change events. When the value of such a parameter changes, the CPE must notify the change to the ACS. Two types of event subscription exist: Passive change notification: whenever the parameter value changes, the CPE must include the new value in the ParameterList argument of the Inform message that is sent the next time a session is established to the ACS.
  • Page 64 Monitoring and Diagnostics Message flow: passive notification Following illustration shows a possible message flow in case of passive notification: Transaction session 1) GetParameterAttributes 2) GetParameterAttributesResponse 3) Verify event subscriptions, decide to reconfigure 4) SetParameterAttributes 5) SetParameterAttributesResponse 6) 200 OK (Empty) 7) Close connection 8) Parameter change event 9) Inform (Event 2 Periodic,...

  • Page 65: Wan Connections

    WAN Connections WAN Connections Introduction The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.WANDevice.1.WANConnectionDevice.”. This object can be used to create a: PPPoE connection PPPoA connection IP connection with static IP address IP connection with DHCP IPoA connection The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.Layer3Forwarding.Forwarding.”.
  • Page 66 WAN Connections Overview Following steps must be performed to create a WAN connection: Create and configure a WAN connection device. See “5.1 WAN Connection Device” on page Create and configure a WAN PPP or IP connection. See “5.2 WAN PPP or IP Connection” on page Obtain connection information.

  • Page 67: Wan Connection Device

    WAN Connections WAN Connection Device WAN connection device A WAN connection device can be created and configured as follows: Creating a WAN connection device: the AddObject RPC (message 1 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.WANDevice.1.WANConnectionDevice.”. AddObjectResponse (message 3 in preceding illustration) contains for the InstanceNumber argument for example value “2“.

  • Page 68: Wan Ppp Or Ip Connection

    WAN Connections WAN PPP or IP Connection Introduction Before, configuring your WAN PPP or IP connection, make sure that you created and configured a WAN connection device. For more information, see “5.1 WAN Connection Device” on page WAN PPPoE connection A WAN PPPoE connection can be created and configured as follows: Creating a PPPoE connection: the...
  • Page 69 WAN Connections Configuring the PPPoA connection: the SetParameterValues RPC (message 10 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2. WANPPPConnection.1.NATEnabled InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2. <username> WANPPPConnection.1.Username InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2. <password> WANPPPConnection.1.Password InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2. Internet WANPPPConnection.1.Name InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2. WANPPPConnection.1.Enable The parameter Name is mandatory. This means that the parameter must be set before the WANPPPConnection object is internally created.
  • Page 70 WAN Connections WAN IP connection with DHCP A WAN IP connection with DHCP can be created and configured as follows: Creating an IP connection: the AddObject RPC (message 7 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANIPConnection.”. AddObjectResponse (message 9 in preceding illustration) contains for the InstanceNumber argument for example value “1“.

  • Page 71: Connection Information

    WAN Connections Connection Information PPP connection To obtain information on the connection status, the assigned external IP address and forwarding entries, the GetParameterValues RPC (message 13 in preceding illustration) contains following ParameterNames arguments: Entry Value InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1 InternetGatewayDevice.Layer3Forwarding.Forwarding IP connection To obtain information on the connection status, the assigned external IP address and the forwarding entries, GetParameterValues RPC (message 13 in preceding illustration) contains following ParameterNames arguments:...

  • Page 72: Forwarding Entries

    WAN Connections Forwarding Entries PPP connection For example, following parameter values can be used: Creating an entry: to add a forwarding entry, the AddObject RPC (message 15 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.Layer3Forwarding.Forwarding.”. AddObjectResponse (message 17 in preceding illustration) contains for the InstanceNumber argument for example value “3“.
  • Page 73 WAN Connections Name Value InternetGatewayDevice.Layer3Forwarding.Forwarding.3.Interface IGD.WANDevice.1. WANConnectionDevice.2. WANIPConnection.1 InternetGatewayDevice.Layer3Forwarding.Forwarding.3.Forwarding Metric InternetGatewayDevice.Layer3Forwarding.Forwarding.3.GatewayIPAd <ipaddress_Interface> dress The parameters DestIPAddress, Interface and GatewayIPAddress are mandatory. This means that these parameters must be set before the Forwarding object is internally created. E-DOC-CTC-20071119-0003 v1.0...
  • Page 74 WAN Connections E-DOC-CTC-20071119-0003 v1.0...

  • Page 75: Service Provisioning

    Service activation based on the data model can be part of the zero-provisioning use case or can be used at any point in time. For example, the user has a VoIP-capable Thomson Gateway but only after an amount of time decides to subscribe to the VoIP service.

  • Page 76: Voip

    Enable or disable the VoIP service Configure the VoIP settings Troubleshoot the VoIP service The VoiceService data model of the Thomson Gateway provides support for the SIP, MGCP and H.323 signalling protocols. For more information on the VoiceService data model, see TR-104 “Provisioning parameters for VoIP CPE”, September 2005.
  • Page 77 Service Provisioning Message flow Following illustration shows a possible message flow for voice service provisioning: Transaction session 1) GetParameterValues Obtain current Configuration 2) GetParameterValuesResponse 3) SetParameterValues 4) Apply changes Configure the VoiceProfile 5) SetParameterValuesResponse 6) SetParameterValues 7) Apply changes Configure the SIP signalling protocol 8) SetParameterValuesResponse 9) AddObject 10) Apply changes...
  • Page 78 Service Provisioning Configuring the signalling protocol: if necessary, modify the value of one or more parameters. The SetParameterValues RPC (message 6 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP.ProxyServer <ip_address > InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP.ProxyServerPort <port> InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP.RegistrarServer <ip_address >...

  • Page 79: Wlan

    For example, remote management can configure or reset the SSID to a “default value” and configure the security settings. The end-user does not need to manually configure the Thomson Gateway. Given a broadcasted SSID and preconfigured security settings, the end-user must only configure the WEP or WPA key on its PC.
  • Page 80 Service Provisioning Example: parameter values For example, following parameter values can be used: Configuration in case of no security: the SetParameterValues RPC (message 1 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.Channel <channel_id> InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.BeaconType None InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID <SSID>...
  • Page 81 Service Provisioning Configuration in case of WPA and WPA2: the SetParameterValues RPC (message 1 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.PreSharedKey.1. abcdefgh KeyPassphrase InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.Channel <channel_id> InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.BeaconType WPAand11i InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID <SSID> InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.Enable E-DOC-CTC-20071119-0003 v1.0...

  • Page 82: Time

    Configure the NTP server IP addresses. Enable the NTP service. Vendor specific parameters The Time data model on the Thomson Gateway contains following vendor specific parameters: X_000E50_WeekDay: the day of the week (Monday, Tuesday,...). X_000E50_Enable: used to enable or disable the NTP service.

  • Page 83: Dhcp Conditional Serving

    Service Provisioning DHCP Conditional Serving DHCPConditionalServingPool data model The IGD data model contains the object “InternetGatewayDevice.LANDevice.1.LANHostConfigManagement.DHCPConditionalServingPool.”. This object supports conditional serving, which allows to: Serve specific devices from a specific pool. Define DHCP options served to those specific devices. Vendor specific parameters There are no vendor specific parameters.
  • Page 84 Service Provisioning Configuring the serving pool: the SetParameterValues RPC (message 4 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.LANDevice.1.LANHostConfigManagement 00:0f:1f:83:d7:5b .DHCPConditionalServingPool.1.Chaddr InternetGatewayDevice.LANDevice.1.LANHostConfigManagement 192.168.1.70 .DHCPConditionalServingPool.1.MinAddress InternetGatewayDevice.LANDevice.1.LANHostConfigManagement 192.168.1.80 .DHCPConditionalServingPool.1.MaxAddress InternetGatewayDevice.LANDevice.1.LANHostConfigManagement 255.255.255.0 .DHCPConditionalServingPool.1.SubnetMask InternetGatewayDevice.LANDevice.1.LANHostConfigManagement 192.168.1.254 .DHCPConditionalServingPool.1.IPRouters InternetGatewayDevice.LANDevice.1.LANHostConfigManagement 86400 .DHCPConditionalServingPool.1.DHCPLeaseTime Creating a DHCP...

  • Page 85: Queue Management

    Service Provisioning Queue Management QueueManagement data model The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.QueueManagement.” for the support of QoS provisioning. This object contains the following multi-instance objects: Classification.[i] Queue.[i] Policer.[i]: only supported on a number of products Vendor specific parameters There are no vendor specific parameters.
  • Page 86 Service Provisioning Name Value InternetGatewayDevice.QueueManagement.Queue.6.DropAlgorithm BLUE InternetGatewayDevice.QueueManagement.Queue.6.SchedulerAlgorith InternetGatewayDevice.QueueManagement.Queue.6.QueueEnable Creating a classification table entry: the AddObject RPC (message 4 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.QueueManagement.Classification.”. AddObjectResponse (message 6 in preceding illustration) contains for the InstanceNumber argument for example value “24”. Configuring the classification table entry: the SetParameterValues RPC...

  • Page 87: Stateful Inspection Firewall

    Service Provisioning Stateful Inspection Firewall Firewall data model The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.X_000E50_Firewall.”. This data model can be used to: Create and configure new security levels, e.g. to create an expert firewall service with 10 levels instead of the default 3 levels.
  • Page 88 Service Provisioning Name Type Actions SourceIP Parameter Read/Write SourceIPMask Parameter Read/Write SourceIPExclude Parameter Read/Write DestinationIP Parameter Read/Write DestinationIPMask Parameter Read/Write DestinationIP- Parameter Read/Write Exclude SourceInterface Parameter Read/Write SourceInterface- Parameter Read/Write Exclude Destination- Parameter Read/Write Interface Destination- Parameter Read/Write InterfaceExclude Protocol Parameter Read/Write ProtocolExclude...
  • Page 89 Service Provisioning Message flow Following illustration shows a possible message flow for the firewall configuration: Transaction session 1) AddObject 2) Apply changes Create a Security Level 3) AddObjectResponse 4) SetParameterValues 5) Apply changes Configure the Security Level 6) SetParameterValuesResponse 7) GetParameterValues Obain the corresponding Firewall Chain 8) GetParameterValuesResponse 9) AddObject...
  • Page 90 Service Provisioning Finding the new chain: the Thomson Gateway automatically creates a new chain that is used by the new security level. The GetParameterValues RPC (message 7 in preceding illustration) contains following ParameterNames argument: Entry Value InternetGatewayDevice.X_000E50_Firewall.Level.7.Chain GetParameterValuesResponse (message 8 in preceding illustration) contains for example value “InternetGatewayDevice.X_000E50_Firewall.Chain.20”.

  • Page 91: Access Rights

    Service Provisioning Access Rights AccessRights data model The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.X_000E50_AccessRights.”. This object can be used for user management. The Thomson Gateway supports following proprietary AccessRights data model: Name Type Actions InternetGatewayDevice.X_000E50_AccessRights.
  • Page 92 Service Provisioning Example: parameter values For example, following parameter values can be used: Creating a user: the AddObject RPC (message 1 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.X_000E50_AccessRights.User.”. AddObjectResponse (message 3 in preceding illustration) contains for the InstanceNumber argument for example value “3“.

  • Page 93: Nat Application List

    Service Provisioning NAT Application List NATApplicationList data model The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.Services.X_000E50_NATApplicationList.”. This object can be used to: Update the list of NAT applications. Each NAT application is defined by: A user-friendly name.
  • Page 94 Service Provisioning Message flow Following illustration shows a possible message flow for the configuration of the NAT application list: Transaction session 1) AddObject 2) Apply changes Create an Application 3) AddObjectResponse 4) SetParameterValues 5) Apply changes Configure the Application 6) SetParameterValuesResponse 7) AddObject 8) Apply changes Create a Rule (Port Mapping)
  • Page 95 Service Provisioning Configuring a rule: the SetParameterValues RPC (message 10 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.Services.X_000E50_NATApplicationList. <ExternalPort> Application.130.Rule.1.ExternalPort InternetGatewayDevice.Services.X_000E50_NATApplicationList. <ExternalPortRangeEnd> Application.130.Rule.1.ExternalPortRangeEnd InternetGatewayDevice.Services.X_000E50_NATApplicationList. <InternalPort> Application.130.Rule.1.InternalPort InternetGatewayDevice.Services.X_000E50_NATApplicationList. TCP or UDP Application.130.Rule.1.Protocol The parameters ExternalPort and ExternalPortRangeEnd are mandatory. This means that the parameter must be set before the Rule object is internally created.

  • Page 96: Dynamic Dns

    The IGD data model contains the object “InternetGatewayDevice.Services.X_000E50_DynamicDNS.”. This object supports Dynamic DNS, which allows the domain name data held in a name server to be updated in real time. The Thomson Gateway supports following proprietary DynamicDNS data model: Name...
  • Page 97 Service Provisioning Message flow Following illustration shows a possible message flow for configuration of the GnuDIP service: Transaction session 1) SetParameterValues 2) Apply changes Configure the Service 3) SetParameterValuesResponse 4) AddObject 5) Apply changes Create a Client 6) AddObjectResponse 7) SetParameterValues 8) Apply changes Configure the Client 9) SetParameterValuesResponse...
  • Page 98 Service Provisioning Configuring the client: the SetParameterValues RPC (message 7 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.Services.X_000E50_DynamicDNS.Client.1. <username> Username InternetGatewayDevice.Services.X_000E50_DynamicDNS.Client.1. <password> Password InternetGatewayDevice.Services.X_000E50_DynamicDNS.Client.1. InternetGatewayDevice. Interface WANDevice.1. WANConnectionDevice.1. WANPPPConnection.1 InternetGatewayDevice.Services.X_000E50_DynamicDNS.Client.1. InternetGatewayDevice. Service Services. X_000E50_DynamicDNS. Service.6 Creating a host: the...

  • Page 99: Remote Access (Remote Assistance)

    6.10 Remote Access (Remote Assistance) RemoteAccess data model The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.Services.X_000E50_RemoteAccess.”. This object can be used to enable remote access to the Thomson Gateway. The Thomson Gateway supports following proprietary RemoteAccess data model:...
  • Page 100 Service Provisioning Example: parameter values: For example, following parameter values can be used: Configuring temporary remote access: the SetParameterValues RPC (message 1 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.Services.X_000E50_RemoteAccess.Mode Temporary InternetGatewayDevice.Services.X_000E50_RemoteAccess.Timeo 20 (minutes) InternetGatewayDevice.Services.X_000E50_RemoteAccess.IPIntf InternetGatewayDevice.

  • Page 101: 6.11 Parental Control

    Service Provisioning 6.11 Parental Control ParentalControl data model The IGD data model on the Thomson Gateway contains the object “InternetGatewayDevice.Services.X_000E50_ParentalControl.”. This object can be used for web site (URL) filtering. The Thomson Gateway supports following proprietary ParentalControl data model: Name...
  • Page 102 Service Provisioning Example: parameter values For example, following parameter values can be used: Creating a rule: the AddObject RPC (message 1 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.Services.X_000E50_ParentalControl.URLFilter.Rule.”. AddObjectResponse (message 3 in preceding illustration) contains for the InstanceNumber argument for example value “1”.

  • Page 103: Vlan Provisioning (Layer2Bridging)

    Configure port VLAN membership Configure default port VID Configure egress VLAN tagging Vendor specific parameters The Layer2Bridging data model on the Thomson Gateway contains no vendor specific parameters. Message flow Following illustration shows a possible message flow for VLAN provisioning: Transaction session...
  • Page 104 Service Provisioning Example: parameter values For example, following parameter values can be used: Creating a VLAN: the AddObject RPC (message 1 in preceding illustration) contains for the ObjectName argument the value “InternetGatewayDevice.Layer2Bridging.Bridge.”. AddObjectResponse (message 3 in preceding illustration) contains for the InstanceNumber argument for example value “3”.
  • Page 105 Service Provisioning Configuring egress VLAN tagging: the SetParameterValues RPC (message 21 in preceding illustration) contains following name-value pairs in its ParameterList argument: Name Value InternetGatewayDevice.Layer2Bridging.Marking.1.MarkingBridge- 2 (= BridgeKey) Reference InternetGatewayDevice.Layer2Bridging.Marking.1.MarkingInterfac 10001 (= AvailableInterfaceKey) InternetGatewayDevice.Layer2Bridging.Marking.1.VLANIDUntag The parameters MarkingBridgeReference and MarkingInterface are mandatory. This means that the parameters must be set before the Marking object is internally created.
  • Page 106 Service Provisioning E-DOC-CTC-20071119-0003 v1.0...

  • Page 107: Zero-Provisioning

    CPE. CPE-to-ACS authentication: each CPE certificate is signed by e.g. a service provider CA or the ACS trusts the CPE CA. 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.
  • Page 108 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 the most recent firmware version.
  • Page 110 THOMSON Telecom Belgium Prins Boudewijnlaan 47 2650 Edegem www.thomson-broadband.com © Thomson 2008. All rights reserved. E-DOC-CTC-20071119-0003 v1.0.

Table of Contents

Save PDF