eLTE Device Management Technical White Paper - Huawei · eLTE Device Management Technical White...

eSight V300R001C10

eLTE Device Management Technical White Paper

Issue 01

Date 2013-12-10

HUAWEI TECHNOLOGIES CO., LTD.

Issue 01 (2013-12-10) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://enterprise.huawei.com

http://enterprise.huawei.com/

eSight

eLTE Device Management Technical White Paper About This Document



ii

About This Document

Purpose

Based on the application background of enterprise Long Term Evolution (eLTE) terminal

management on eSight and functions of eLTE terminals, this document analyzes and

introduces the eLTE device management feature by analyzing technologies and typical

application scenarios in details.

Intended Audience

This document is intended for:

Technical support engineers

Maintenance engineers

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.


avoided, may result in minor or moderate injury.


avoided, could result in equipment damage, data loss,

performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to

personal injury.

eSight

eLTE Device Management Technical White Paper About This Document



iii

Symbol Description

Calls attention to important information, best practices

and tips.

NOTE is used to address information not related to

personal injury, equipment damage, and environment

deterioration.

Change History

Changes between document issues are cumulative. The latest document issue contains all the

changes made in earlier issues.

Issue 01 (2013-12-10)

This issue is the first official release.

eSight

eLTE Device Management Technical White Paper Contents



iv

Contents

About This Document .................................................................................................................... ii

1 Executive Summary ...................................................................................................................... 1

2 Introduction.................................................................................................................................... 2

3 Solution ........................................................................................................................................... 4

3.1 Solution Overview ........................................................................................................................................................ 4

3.1.1 Terminal NE Management ......................................................................................................................................... 4

3.1.2 PnP Device Access ..................................................................................................................................................... 5

3.1.3 Configuration File Updating ...................................................................................................................................... 5

3.1.4 Device Firmware Upgrade ......................................................................................................................................... 6

3.1.5 Authentication Parameter Setting .............................................................................................................................. 6

3.1.6 Remote Maintenance and Management ..................................................................................................................... 7

3.2 Key Technologies ......................................................................................................................................................... 7

3.2.1 TR069 Protocol Stack ................................................................................................................................................ 7

3.2.2 PnP Automatic Deployment ..................................................................................................................................... 10

3.3 Function Restriction .................................................................................................................................................... 12

3.3.1 Applicable Devices .................................................................................................................................................. 12

3.4 Typical Applications ................................................................................................................................................... 13

3.4.2 Deployment.............................................................................................................................................................. 13

3.4.3 Upgrade ................................................................................................................................................................... 16

3.4.4 Maintenance ............................................................................................................................................................. 20

3.4.5 Troubleshooting ....................................................................................................................................................... 23

4 Acronyms and Abbreviations ................................................................................................... 26

eSight

eLTE Device Management Technical White Paper Executive Summary



1

1 Executive Summary

The eSight eLTE device management component provides management functions such as

plug and play (PnP) access mode for Huawei eLTE terminals, device firmware upgrade,

device configuration management, and remote device maintenance. With these compelling

functions, eSight manages wired and wireless networks in a unified manner, and helps users

implement automatic deployment of terminals, upgrade firmware, adjust configurations,

monitor faults, and perform routine operation and maintenance (O&M).

eSight

eLTE Device Management Technical White Paper Introduction



2

2 Introduction

As a long term evolution version of 3G protocols, LTE has made remarkable progress in

recent years. Access terminal products play an increasingly important role in network

evolution, and the product forms are diversified. Access terminal products are important parts

of Huawei end to end (E2E) solutions, and are of great significance in improving

completeness of Huawei solutions.

As broadband access terminals that are used in the Passenger Information System (PIS),

terminal access units (TAU) are placed in the head and tail of a train, connect to the ground

and train using the wireless standard TDD-LTE (where TDD refers to time division duplex),

and provide upstream and downstream data transmission for the train, as shown in Figure 2-1.

TAUs provide multiple data playback in the downstream direction, and provide video

surveillance data backhaul in the upstream direction.

Figure 2-1 TAU backhaul network architecture in the PIS

As access terminals on wireless Internet of Things (IoT) dedicated networks, outdoor

customer premises equipment (CPE) connects to sensors through wired Ethernet ports for

collecting data. Generally, CPEs support power over Ethernet (PoE) and transmit data back

through wireless LTE networks.

eSight

eLTE Device Management Technical White Paper Introduction



3

Figure 2-2 CPE backhaul network architecture on an electric dedicated network

eLTE terminals have the following management features:

The number of terminals is large, and terminals scatter over large areas.

Terminals are deployed in various modes on the user side, and the networks are complex.

The openness of network structures brings security problems.

Terminals are of various types, and there is a lack of unified standards.

Terminals are simple, and parameter settings are rarely needed after services are

deployed.

The features bring difficulties to device management.

Based on the preceding features and difficulties, terminals use TR069 as the network

management protocol in addition to supporting near end web network management systems

(NMSs). eSight helps users manage a large number of terminals in a centralized manner, uses

automatic deployment to overcome service deployment difficulties, and reduces operating

costs of users.

eSight

eLTE Device Management Technical White Paper Solution



4

3 Solution

3.1 Solution Overview

eLTE device management functions include PnP access mode for terminals, terminal

firmware upgrade, device configuration management, and remote device maintenance.

3.1.1 Terminal NE Management

eSight provides a unified entry for managing a specified type of terminals, and supports the

following functions:

Basic terminal information

eSight manages connected terminals in lists, and displays basic device information such

as the IP address, firmware version, management status, O&M operations, and O&M

operation results. In addition, users can export terminal lists, delete specified terminals,

and manage subnets to which terminals belong.

eSight displays common terminal parameters in a centralized manner, which can be

refreshed manually. Users can use the IP ping function to check connectivity between

eSight and terminals to learn about the IP link status between them in a timely manner.

Common terminal configuration

Users can use the TR069 data model tree to modify parameters.

Common terminal parameter setting

Users can view and modify common parameters such as wide area network (WAN), local

area network (LAN), wireless local area network (WLAN), route, gateway, and

auto-configuration server (ACS) parameters.

Web user interface (UI) jumping

User can use the web UI jumping function to directly jump to the CPE web UI.

Configuration file export

Users can use this function to export, download, and back up terminal configuration

files.

Configuration file loading

Users can load selected configuration files to terminals to ensure that terminals use

specified configuration files.

Device log

Users can browse log files of the modem, diagnosis, and route types for CPEs, download

log files to the server, and export log files to the local PC.

eSight




5

Alarm management

Users can view current and historical alarms for specified NEs.

Peak rate monitoring

Users can start and stop the peak rate monitoring task, display IP layer traffic statistics in

the upstream and downstream directions, and export details about peak rate monitoring.

3.1.2 PnP Device Access

Automatically grouping CPEs to different subnets

Users can create CPE subnets on eSight. When CPEs initially register with eSight,

eSight automatically adds CPEs to corresponding subnets based on the authorized

terminal list configuration.

Automatically updating configuration files

After CPE subnets are created, users can create a configuration file for each subnet. Then,

eSight automatically updates the corresponding configuration file on a CPE when the

CPE is added to a subnet.

Automatically upgrading version files

Users can upload firmware version files for CPEs. eSight automatically queries the

firmware version of a CPE, and compares it with the version of the firmware version file

uploaded by users. If the versions do not match, eSight automatically upgrades CPE

firmware.

Figure 3-1 PnP device access

3.1.3 Configuration File Updating

eSight allows users to manage CPE parameter settings using configuration files. Users can

perform the following configuration file management functions:

Export configuration files from specified CPEs in online mode.

Load configuration files to specified CPEs.

eSight




6

Figure 3-2 Configuration file management in NE management

In addition to exporting and loading configuration files from and to specified terminals, users

can also use the public configuration file capability provided by eSight. The public

configuration file capability is not limited to a specified terminal type. Main functions include

configuration file management and loading.

Figure 3-3 Batch configuration file management

3.1.4 Device Firmware Upgrade

Users can upgrade the CPE firmware in batches immediately or as scheduled.

3.1.5 Authentication Parameter Setting

User names and passwords for connecting terminals to eSight are preset before delivery. To

enhance security, the system allows users to change user names and passwords for terminals

on the whole network.

eSight




7

3.1.6 Remote Maintenance and Management

eSight allows users to remotely maintain terminals in batches. The eSight server can remotely

ping WAN IP addresses of terminals, reboot terminals, and restore terminals to factory

defaults.

3.2 Key Technologies

3.2.1 TR069 Protocol Stack

With the popularization of IP terminals (especially at home) such as voice over Internet

Protocol (VoIP) and Internet Protocol television (IPTV) terminals, it becomes more and more

difficult to manage and maintain a large number of devices. The costs of network product

carriers are greatly increased. Traditional NMSs based on Simple Network Management

Protocol (SNMP) appear to be inadequate when facing so many terminals, affecting the

development and scale of the broadband access market. TR069 defines a brand new NMS

architecture that consists of the management model, interaction interface, and management

parameter, greatly reducing network product operating costs.

TR069 is a Broadband Forum (formerly known as DSL Forum) technical specification

entitled CPE WAN Management Protocol (CWMP). The document ID of the technical

specification is TR069. Since TR069 was introduced by DSL Forum in May 2004, carriers

have deployed many TR069-based terminals. From the protocol development perspective,

TR069 is still in the process of continuous development.

As the network management center, the ACS is located at the network O&M layer, and is

generally deployed on the carrier side to manage all terminals. O&M personnel use the ACS

to maintain and manage the entire network. Non-handheld terminals function as access

devices and are located on the user side. Generally, terminals are placed in specific enterprise

office environments. Terminals can be located on the same network as the ACS, or located on

a LAN so that they are on a different network from the ACS. Interfaces between the ACS and

CPEs are southbound interfaces, and interfaces between the ACS and management systems

are northbound interfaces. TR069 mainly defines southbound interfaces.

Figure 3-4 TR069-based network management network

The ACS can be integrated into the NMS for a dedicated network, as shown in Figure 3-5.

The NMS manages both network-side devices and terminals.

eSight




8

Figure 3-5 Solution where the NMS and ACS are deployed together

Figure 3-6 shows the original TR069 protocol stack.

Figure 3-6 TR069 protocol stack

The protocol stack is based on Transmission Control Protocol/Internet Protocol (TCP/IP), and

uses a standard Internet transmission security protocol such as Secure Sockets Layer (SSL)

3.0 or Transport Layer Security (TLS) 1.0. Using SSL or TLS is not mandatory. Users must

ensure that certificate-based authentication is performed between CPEs and the ACS. The

ACS and CPEs use Hypertext Transfer Protocol (HTTP) 1.1 to exchange messages. Messages

are encapsulated using Simple Object Access Protocol (SOAP) packages. A SOAP package is

an Extensible Markup Language (XML) document consisting of a SOAP header and a SOAP

body.

eSight




9

Figure 3-7 TR069 packet encapsulation structure

eSight implements the TR069 protocol stack and uses southbound interfaces to interact with

CPEs.

Figure 3-8 TR069 protocol stack structure implemented on eSight

eSight




10

3.2.2 PnP Automatic Deployment

Figure 3-9 shows the PnP automatic deployment process.

Figure 3-9 PnP automatic deployment process

After being powered on, a terminal initiates the PnP process as follows:

The terminal proactively looks for the IP address of the ACS from the domain name server

(DNS), and registers with the ACS after the IP address is obtained. The ACS proactively

delivers the version file and configuration file to the terminal to ensure that the terminal can

enter the O&M status without manual intervention after it is started.

Terminal authorization management allows users to manage a list of authorized terminals on

eSight. eSight identifies a terminal based on the terminal ID contained in the message

reported by the terminal, and checks whether the terminal is in the authorized terminal list

saved on eSight. If yes, eSight allows the terminal to register with and connect to eSight. If no,

eSight rejects the terminal and records a system log. The authorized terminal list management

feature allows users to import a device list, and add, delete, modify, and query items in the

authorized terminal list.

The prerequisites of the PnP process are that an authorized terminal list has been imported to

eSight and users have purchased the corresponding number of licenses. In addition, the PnP

process also verifies that terminals are authorized and the number of licenses is sufficient.

Before using the PnP service, users must clearly specify the mapping between the online

version for the specified terminal type and the version of the terminal that initiates the PnP

process, and upload and store the online firmware version file and configuration file on eSight

eSight




11

in advance. Terminal maintenance personnel release the PnP configuration file and provide

the method of modifying the configuration file, where the policy is the same as that for

manual configuration file updating tasks. If no corresponding firmware version file or

configuration file is available, the PnP process skips corresponding steps.

The PnP process is triggered by the Inform message sent by the terminal. Generally, in the

Inform message sent by a terminal that initiates registration for the first time, the eventcode

value is bootstrap. When considering that the Inform message with eventcode being

bootstrap is properly received by eSight, the terminal reports Inform messages with other

eventcode values. Therefore, provided that DeviceID of the terminal is authorized and

sufficient licenses are available, eSight checks whether the terminal that reports Inform

messages has a record on eSight to determine whether to initiate the PnP process for the

terminal.

The entire PnP process consists of the registration, upgrade, and configuration processes. In

the wireless upgrade scenario where bandwidth is limited, the upgrade and configuration

processes are optional. Users can set PnP parameters to disable the upgrade and configuration

processes in the PnP process. In this way, the PnP process ends when the terminal is registered.

After the PnP process ends, users need to manually upgrade the firmware of the terminal and

update the configuration file.

Figure 3-10 PnP registration process

eSight




12

Figure 3-11 PnP firmware upgrade and configuration file updating process

3.3 Function Restriction

3.3.1 Applicable Devices

Device Version

eA660-160 V100R001C01B207 and later versions

eA660-135 V100R001C01B207 and later versions

eA660-118 V100R001C00 and later versions






eSight




13

3.4 Typical Applications

By supporting management functions such as PnP deployment, device configuration file

management, firmware upgrade management, alarm monitoring, LAN port peak rate

monitoring, common device configuration, ping, rebooting, and restoration to factory defaults,

eSight eLTE device management component helps users comprehensively manage eLTE

devices and builds core competitiveness of eLTE applications.

Figure 3-12 Core competitiveness of eLTE device management

3.4.2 Deployment

During deployment, a lot of CPEs need to be powered on, upgraded to the unified firmware

version, and configured in a unified manner. Manually performing the preceding tasks on

terminals one by one is labor-intensive and time-consuming. eSight provides the PnP

automatic upgrade and configuration functions, and automatically starts the upgrade and

configuration file updating tasks when terminals connect to eSight.

Figure 3-13 Deployment

Subnet planning

eSight




14

A CPE subnet is a logical management object. Users can group CPEs to different subnets for

management based on different service properties and area ranges. Users can configure a

specified configuration file for each subnet to set device parameters.

Figure 3-14 Subnet planning

Authorized list

The authorized list provides a list of authorized devices for eSight to reject unauthorized

devices that attempt to connect to eSight. Before devices connect to eSight, users must create

the authorized list and specify subnets for devices. Users can add a single device to the

authorized list or import multiple devices to the authorized list in batches. Before adding a

single device, users must create subnets. Batch import automatically creates configured

subnets.

Figure 3-15 Authorized list

PnP parameter setting

eSight




15

After the PnP process is enabled and the default PnP configuration file and firmware version

are configured, eSight automatically creates the upgrade and configuration file updating tasks

when a device is powered on. Users can set PnP parameters separately for different types of

devices, and specify configuration files for subnets.

Figure 3-16 PnP parameter setting

Device status monitoring

After a CPE is powered on, information about the CPE such as the basic information, status,

and O&M operations is displayed in the device list. For devices that have connected to eSight,

users can click the management menu or the device ID link to view detailed parameters.

Figure 3-17 Device status monitoring

eSight




16

3.4.3 Upgrade

After devices are put into use, they may go through multiple upgrades. Considering

configuration file updating, it is difficult to manage a large number of firmware versions and

configuration files. In addition, it is labor-intensive and time-consuming to upgrade a large

number of devices. eSight provides the firmware version and configuration file management,

batch upgrade, and batch configuration file updating functions. eSight operates a large

number of devices concurrently, and allows users to configure different firmware versions and

configuration files for devices of different models, saving time and effort.

Configuration file and firmware version management

Before upgrading devices, users must upload configuration files and firmware version files.

Figure 3-18 Configuration file and firmware version management

Firmware version upgrade parameter setting

Users can set the following parameters:

File Server Concurrency Control (for controlling the number of devices that are

upgraded and configured concurrently)

Automatic Re-execute Times (for configuring the number of automatic retry times

when the upgrade or configuration fails)

eSight




17

Upgrade Timeout Time (for configuring the duration after which the upgrade or

configuration times out)

Total Cell Concurrency (for controlling the number of devices that are upgraded and

configured concurrently in a residential area)

Figure 3-19 Firmware version upgrade parameter setting

Firmware version upgrade task creation

1. Enter a task name and click Next. You can set a task to a scheduled task.

2. Select the devices whose firmware needs to be upgraded and click Next. You can select

devices of different models and versions.

3. Specify the target firmware version for devices of different models and versions and

click Create. After a scheduled task is created, the task is automatically executed when

the specified time arrives.

Figure 3-20 Firmware version upgrade task creation

Firmware version upgrade task status monitoring

All firmware version upgrade tasks are displayed in the task list, and task execution status is

updated in real time. Users can click a task to view task details, including execution status of

each device involved in the task, current step, and failure cause. If a device fails to upgrade

the firmware, users can click the retry button to run the task again.

eSight




18

Figure 3-21 Upgrade task monitoring

Configuration file updating task creation

1. Enter a task name and click Next. You can set a task to a scheduled task.

2. Select the devices whose configuration files need to be updated and click Next. You can

select devices of different models and versions.

3. Specify the target configuration file for devices of different models and versions and

click Create. After a scheduled task is created, the task is automatically executed when

the specified time arrives.

Figure 3-22 Configuration file updating task creation

Configuration file updating task status monitoring

All configuration file updating tasks are displayed in the task list, and task execution status is

updated in real time. Users can click a task to view task details, including execution status of

each device involved in the task, current step, and failure cause. If a device fails to update the

configuration file, users can click the retry button to run the task again.

eSight




19

Figure 3-23 Configuration file updating task status monitoring

Historical firmware version upgrade and configuration file updating task monitoring

All tasks that have been deleted are displayed in the historical upgrade and configuration task

list, and can be exported to the local PC. Users can click a task to view task details, including

the execution result for each device and failure cause.

Figure 3-24 Historical task monitoring

eSight




20

3.4.4 Maintenance

During daily maintenance, users need to perform preventive maintenance inspection (PMI) on

devices to discover problems in a timely manner. eSight provides multiple functions for

monitoring the current status of devices, and reports alarms to notify users if any problems are

detected.

License capacity management

The license determines the capability of eSight in CPE management. Basic license

information includes the validity period, resource usage, and function control.

eSight




21

Figure 3-25 License control

Device status

Users can search for specified devices by setting filter conditions. The device list displays the

management status, O&M operations, and O&M operation results for all devices. Users can

manage, modify, delete, and obtain device information and perform the ping operation.

Device alarm

Current alarms for devices are displayed in device details. Users can search for specified

alarms by setting filter conditions, and click an alarm name to view alarm details.

eSight




22

Figure 3-26 Alarm monitoring

Device parameter setting

Using the device tree, users can view details about device firmware and hardware, view

network parameter settings, and add, delete, and modify parameter settings.

Figure 3-27 Device parameter setting

Device LAN port peak rate monitoring

Users can monitor device LAN port upstream and downstream rates in real time, detect link

disconnections, and view bandwidth usage.

eSight




23

Figure 3-28 LAN port peak rate monitoring

3.4.5 Troubleshooting

After devices are put into use, some problems may occur and affect normal use of devices.

eSight provides functions for discovering, locating, and solving problems, facilitating fault

diagnosis and device recovery.

Device information

Users can find devices that malfunction from the device list, for example, a device fails to be

managed, or the firmware of a device fails to be upgraded.

Figure 3-29 Device information

eSight




24

Alarm display and notifications

The alarm list displays alarms reported by all devices. When an alarm is reported, a sound is

played and detailed alarm information is displayed. Users can enable the short message

service (SMS) notification function to learn about problems in a timely manner.

Device log management

Users can obtain modem, diagnosis, and route logs, and click Export to export device logs.

Users can also download log files to the local PC.

Figure 3-30 Device log management

Remote maintenance

eSight allows users to remotely ping and reboot devices and restore devices to factory defaults

in batches.

Figure 3-31 Remote maintenance

Batch modification of device parameters

Users can modify device parameters in batches to solve some device problems.

eSight




25

CPE web UI

Users can click the management menu on the web page, go to the CPE Web UI portal, select

the CPE user name, enter the password, and log in to the CPE web page where users can

manage the CPE remotely.

Figure 3-32 Web UI

eSight

eLTE Device Management Technical White Paper Acronyms and Abbreviations



26

4 Acronyms and Abbreviations

Table 4-1 Acronyms and abbreviations

Acronym or Abbreviation

Full Spelling

ACS auto-configuration server

CPE customer premise equipment

CWMP CPE Wan Management Protocol

DSL digital subscriber line

eLTE enterprise Long Term Evolution

LTE Long Term Evolution

PIS passenger information system

PoE power over Ethernet

TAU terminal access unit

TDD-LTE Time Division Duplex Long Term Evolution

eLTE Device Management Technical White Paper - Huawei · eLTE Device Management Technical White...

Documents

Transcript of eLTE Device Management Technical White Paper - Huawei · eLTE Device Management Technical White...