Cisco Universal Small Cell
USC6732 UMTS-Only Mode
Feature Description
21 September 2015
Document Version: 0.3
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Ref: USC-44-20-093
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO
CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE
BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE
INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS
REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR
CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of
California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved.
Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE
SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL
WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING,
USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR
INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA
ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual
addresses and phone numbers. Any examples, command display output, network topology diagrams, and other
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone
numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version
should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco
website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other
countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks
mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
© 2015 Cisco Systems, Inc. All rights reserved.
USC6732 UMTS-Only Mode▄
USC-44-20-093
ii
USC6732 UMTS-Only Mode
Feature Tracking ID(s): FEAT-1274
USC Operation Mode(s): RANGW (Iuh)
1. Definitions and Abbreviations
For the purposes of the present document, the following abbreviations apply:
DHCP
GE
HMS
HeNB
HNB
LAN
LLDP
MAC
OAMP
OUI
PoE
PS
SN
USC
Dynamic Host Configuration Protocol
Gigabit Ethernet
Home NodeB Management System
Home eNodeB
Home NodeB
Local Area Network
Link Layer Discovery Protocol
Media Access Control
Operations, Administration, Maintenance, and Provisioning.
Organizationally Unique Identifier
Power over Ethernet
Packet Switched
Serial Number
Universal Small Cell
2. References
[1] EDCS-1480453 “Cisco Universal Small Cell Quick Reference Guide, 3G Only LTE
Dark Mode Configuration Setup”
[2] “Cisco RAN Management System Administration Guide, Release 5.1”,
http://www.cisco.com/c/en/us/td/docs/wireless/access_point/small_cell/rms/r51/admin
_guide/b_rms_admin_guide_51.html
USC6732 UMTS-Only Mode
3
USC-44-20-093
3. Functional Description
This document describes how the USC6732 supports UMTS-only operation, covering aspects
relating to running the UMTS software on the master module whilst the slave module does not
support any service.
3.1
Licensing
This feature is not licensed.
3.2
Principles
The USC6732 is a device that internally contains two modules each capable of supporting the
functions of an HNB or an HeNB. This document describes the operation of the USC6732 when it
is deployed as a UMTS-only device running R3.8 USC software on the master module.
USC6732
Module #1
HNB
GE
UMTS Cell
Module #2
Not Active
Figure 1: USC 6732 supporting UMTS-only mode of operation.
The general principle of this mode of operation is that the USC6732 operates as if it is a standalone HNB. However the inactive module will run a special software image to manage the platform
and enable a future upgrade of this module to run LTE software. The description of these
additional considerations of UMTS-only mode are the topic of this document.
The key characteristics of the inactive module are that it:
•
•
•
Requires an IP address (obtained through DHCP)
Is not managed by the RMS
Does not create an IPsec tunnel to the operator’s network
TM
The device is placed into UMTS-only mode of operation by the Cloudbase configuration for the
unit. Cloudbase will install two software images on the unit (UMTSHNB software and the one for
the inactive unit). Changing from this to UMTS+LTE mode of operation is performed through
factory recovery.
The USC6732 has a single Ethernet port for backhaul and PoE+ power. However, the device will
appear as two Ethernet MAC and IP end-points to the LAN. PoE+ negotiation is handled by the
USC software running on the master module.
The timing control of the unit is provided by the USC software offering the range of R3.8 timing
references.
USC6732 UMTS-Only Mode ▄
USC-44-20-093
4
3.3
Identities
When the USC6732 is manufactured each module is assigned a number of different identities.
DeviceID
The unique identity for each module. In the format:
<OUI>-<Serial Number>.cisco.com
MAC address
Uniquely identifies the module’s Ethernet interface. Note each
module has its own Ethernet termination.
The <OUI> value for this product is: 001B67.
In addition to these identities a common “Chassis Serial Number” (ChassisSN) is assigned to each
module that identifies the unique multimode device. Thus, both modules in the multimode device
share a common “Chassis Serial Number”. This is used when operating in the UMTS+LTE mode
of operation to allow the management interface to identify which HNB and HeNB instances belong
to the same physical multimode device.
On activation of a module Cloudbase will install the appropriate UMTS device certificates for the
HNB module.
USC6732
Module #1
HNB
• UMTS DeviceID
• HNB MAC
• ChassisSN
UMTS
device
certificates
GE
Module #2
• Inactive Module DeviceID
• Inactive Module MAC
• ChassisSN
Figure 2: Key identities in multimode device.
These identities are reflected in the following HNB database parameters:
Parameter
Description
DeviceInfo.ManufacturerOUI
DeviceInfo.SerialNumber
DeviceInfo.
X_UBIQUISYS_COM_ChassisSN
WANEthernetInterfaceConfig.
MACAddress
HNB DeviceID
Multimode device common chassis serial number
HNB module’s Ethernet MAC address
Table 1: Database parameters for device identities.
3.4
Activation
Prior to activating the access point the unit must be associated with a 3G-only network profile in
Cloudbase. The configuration of Cloudbase for this mode of operation is described in [1].
USC6732 UMTS-Only Mode
5
USC-44-20-093
When the access point is powered up for the first time both modules will contact Cloudbase in
parallel to obtain their initial configuration
1a.
Master module performs DHCP transaction to obtain an IP address.
1b.
Slave module performs DHCP transaction to obtain an IP address.
2a.
Master module contacts Cloudbase to download the inactive mode software image and
configuration.
2b.
Slave module contacts Cloudbase to download a UMTS software image and
configuration.
3.
Both master and slave modules reboot.
4a.
Master module performs DHCP transaction to obtain an IP address.
4b.
Slave module performs DHCP transaction to obtain an IP address.
5a.
Master module polls the public NTP server configured by Cloudbase to obtain the time.
5b.
Slave module polls the public NTP server configured by Cloudbase to obtain the time.
6.
The master module contacts the initial HMS to obtain its UMTS database configuration
(and potentially commanded to obtain a software update).
7.
The master module follows the remained of the UMTS activation procedure to then come
into service.
3.5
Factory Recovery
The USC6732 supports the factory recovery procedure that initialises the device to a default
configuration downloaded from Cloudbase. This factory recovery always installs a default
configuration for both modules inside the device.
The unit may initiate the factory recovery procedure when:
•
•
The external switch on the device is held down for a long period
The RMS instructs the HNB to start factory recovery by setting the following HNB
database parameter:
InternetGatewayDevice.Services.FAPService.1. X_UB IQUISYS_COM_Diagnostics.
FactoryRecovery
This will result in both modules of the USC6732 executing the factory recovery procedure in
parallel.
Note: the local network the USC6732 is connected to must provide an IP address to both modules
on the device, and provide connectivity for both of these to the Cloudbase servers.
3.6
Software Upgrade
3.6.1 Upgrading the UM TS Software Load
The software load for the UMTS module on the USC6732 can be upgraded separately from the
software image running on the inactive module. This is performed using the standard R3.8
software upgrade procedure as described in the RMS configuration guide [2].
3.6.2 Upgrading to UM TS+LTE M ode
The USC6732 can be software upgraded from UMTS-only mode to UMTS+LTE mode using the
factory recovery procedure. This procedure requires the following steps:
1.
Configure the unit in Cloudbase with a UMTS+LTE configuration and software image.
USC6732 UMTS-Only Mode ▄
USC-44-20-093
6
2.
3.
Create an LTE configuration for the cell in the RMS.
Trigger the USC6732 to perform a factory recovery procedure to download this new multimode
configuration from Cloudbase.
Once the unit has been factory recovered it will start up running both HNB and HeNB software and
perform UMTS and LTE initialisation in parallel.
The detailed steps for configuring a multimode UMTS+LTE access point is described in the RMS
configuration guide [2].
3.6.3 Upgrading Software on Both M odules
In most instances, Cisco expects only the 3G software will need to be upgraded and the software
image running on the inactive module will remain the same. However, in some circumstances, for
example the introduction of a new feature, it might be necessary to update the software on both
the active and in-active module. If this should arise, the upgrade can only be performed using the
factory recovery procedure and would be stated as such in the release notes.
3.7
Inactive M odule Operation
3.7.1 Overview
The inactive module runs a software image that allows this module to operate in a disabled state.
This software image is installed using Cloudbase. RMS based upgrade of this software image is
not supported.
In the inactive state this module does not offer service or requires the operator to manage it. In
particular:
•
•
•
•
•
•
The module does not connect to the RMS for TR-069 management. Thus no RMS
configuration is required for this module
The module does not create an IPsec tunnel to the SeGW
No NTP polls to an Operator NTP server occur, only to the public NTP server configured
through Cloudbase
The module does not raise any alarms
The module does not upload any PM counter files
The LED for the inactive module is not used
However, the inactive module does implement a number of basic functions to ensure it can support
factory recovery. These require the module to have a presence on the local LAN it is deployed on:
•
•
•
The module requires an IP address to be assigned to it.
The module uses DHCP to obtain this IP address.
The module performs periodic NTP polls to the public NTP server defined by Cloudbase.
3.7.2 Backhaul Aspects
The USC6732 provides a single Gigabit Ethernet port for connecting the device to the customer’s
LAN. However the internal architecture of the USC6732 has the Ethernet terminating on internal
Ethernet ports for each module connected to the external Ethernet port via an internal Ethernet
switch. For the backhaul interconnection this has the following implications:
•
There are two Ethernet MAC addresses assigned to the USC6732, one for each internal
module
•
•
Each module requires its own IP address obtained through DHCP
PoE+ operation is managed by the master module which supports the LLDP protocol
USC6732 UMTS-Only Mode
7
USC-44-20-093
USC6732
HNB DHCP
Transaction
PoE+
LLDP
PoE+
Ethernet
Switch
DHCP
Server
MAC #1
IP #1
Module #1 (HNB)
GE
Inactive Module
DHCP Transaction
Module #2 (Inactive)
MAC #2
IP #2
Figure 3: Usage of the backhaul interface in UMTS-only mode of operation.
3.7.3 DHCP
Each module requires its own IP address for operation. These are obtained through DHCP
transactions. The HNB will obtain its DHCP address through one DHCP transaction whilst in
parallel the inactive module will obtain its IP address through a parallel DHCP transaction.
The following tables list the key options that identify the USC6732 operation for the UMTS and
Inactive module during normal initialisation and factory recovery initialisation.
Option
43
60
61
125
125
125
Sub Opt.
1
2
3
4
5
6
7
8
9
10
1
2
Value
VLANID
Conversational IEEE802.1p value
StreamingPS IEEE802.1p value
InteractivePS_Priority1 IEEE802.1p value
InteractivePS_Priority2 IEEE802.1p value
InteractivePS_Priority3 IEEE802.1p value
Back groundPS IEEE802.1p value
Signalling IEEE802.1p value
OAMP IEEE802.1p value
IP Timing IEEE802.1p value
“Cisco Small Cell”
UMTS module MAC address
3561
001B67
Serial number of UMTS module
Comment
Refer VLAN feature
Refer IEEE8022.1P
QoS feature
“Broadband Forum”
Refer section 0
Table 2: UMTS module: Normal initialisation DHCP options
Option
60
61
Sub Opt.
Value
“Cisco Small Cell”
UMTS module MAC address
Comment
Table 3: UMTS module: Factory Recovery DHCP options
USC6732 UMTS-Only Mode ▄
USC-44-20-093
8
Option
60
61
125
125
125
Sub Opt.
1
2
Value
“Cisco Small Cell”
Inactive module MAC address
3561
001B67
Serial number of Inactive module
Comment
“Broadband Forum”
Refer section 0
Table 4: Inactive module: Normal initialisation DHCP options
Option
60
61
Sub Opt.
Value
“Cisco Small Cell”
Inactive module MAC address
Comment
Table 5: Inactive module: Factory Recovery DHCP options
3.7.4 PoE+ & LLDP
The USC6732 is powered via its Ethernet port using PoE+.
The USC6732 supports LLDP to identify itself to Ethernet equipment and to support PoE+ power
negotiation. The LLDP protocol is handled only for the master module, i.e. the UMTS module,
which identifies the whole USC6732 device. Refer to the PoE+ feature documentation for details.
4. Related Database Parameters
No database parameters are used to manage this feature.
5. Performance Counters and KPI
No new Performance Counters will be generated as a result of the implementation of this feature.
6. Alarm
No new alarms are introduced as a result of the implementation of this feature.
7. LED
The UMTS LED indicates the state of the HNB operation as defined in the R3.8 LED
documentation.
The LTE LED will not be active in this mode.
USC6732 UMTS-Only Mode
9
USC-44-20-093
8. Revision History
Date
Version
Author
Comment
10/09/2015
16/09/2015
0.1
0.2
Paul McDonald
Paul McDonald
21/09/2015
0.3
Simon Hughes
Initial draft
Added section 3.6.3 based on Stuart
Hazell’s comments.
Edit for R3.8 EFT
USC6732 UMTS-Only Mode ▄
USC-44-20-093
10