Multi-Standard Iuh integration

Feature Requirements Specification

Feature # 171268
Version 1.0

Copyright 2007 Alcatel-Lucent, All Rights Reserved

Printed in France

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write protected”; it
may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the
master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled
copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent.
Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein
confidential, shall disclose the information only to its employees with a need to know, and shall protect the information
from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the
holder is granted no rights to use the information contained herein. If you have received this document in error,
please notify the sender and destroy it immediately.

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 1

 Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 2

 Multi-Standard Iuh integration Version 1.0

1 TABLE OF CONTENTS
2
3 1 GENERAL FEATURE INFORMATION .............................................................................................................5
4 1.1 FRS TITLE: MULTI-STANDARD IUH INTEGRATION.............................................................................................5
5 1.2 FEATURE # 171268 ........................................................................................................................................5
6 1.3 NETWORK ELEMENT .......................................................................................................................................5
7 1.4 FEATURE ORDER TYPE ...................................................................................................................................5
8 1.5 INTERNAL/EXTERNAL FEATURE .......................................................................................................................5
9 1.6 PLM FRS OWNER..........................................................................................................................................5
10 1.7 FRS CONTRIBUTORS ......................................................................................................................................5
11 1.8 FRS APPROVERS ...........................................................................................................................................5
12 1.9 REVISION HISTORY .........................................................................................................................................5
13 1.10 REQUESTED RELEASES ..................................................................................................................................6
14 2 FEATURE INFORMATION .................................................................................................................................6
15 2.1 FEATURE OVERVIEW .......................................................................................................................................6
16 2.2 FEATURE DESCRIPTION...................................................................................................................................6
17 2.3 FEATURE VALUE AND BENEFITS ......................................................................................................................9
18 2.4 MARKET INFORMATION................................................................................................................................. 10
19 2.4.1 Applicable Market .............................................................................................................................. 10
20 2.4.2 Technology......................................................................................................................................... 10
21 3 DEVELOPMENT REQUIREMENTS ............................................................................................................... 10
22 3.1 DEVELOPMENT REQUIREMENTS ................................................................................................................... 10
23 3.2 PERFORMANCE / CAPACITY / RELIABILITY REQUIREMENTS ........................................................................... 11
24 3.3 OPERATION, ADMINISTRATION AND MANAGEMENT ....................................................................................... 11
25 3.3.1 Counter Requirements ...................................................................................................................... 11
26 3.3.2 Fault Management and Alarm Requirements .................................................................................. 11
27 3.3.3 Configuration Management and Parameter Requirements ............................................................ 11
28 3.3.4 Billing Requirements .......................................................................................................................... 11
29 3.3.5 Serviceability Requirements.............................................................................................................. 11
30 3.3.6 Specific Documentation Requirements ............................................................................................ 11
31 3.3.7 Software Optional Control ................................................................................................................. 12
32 4 RESTRICTIONS, LIMITATIONS AND CLARIFICATIONS ........................................................................... 12
33 4.1 KNOWN FEATURE RESTRICTIONS, LIMITATIONS AND CLARIFICATIONS .......................................................... 12
34 5 DEPENDENCIES .............................................................................................................................................. 12
35 5.1 KNOWN FEATURE DEPENDENCIES ............................................................................................................... 12
36 5.2 HARDWARE DEPENDENCIES......................................................................................................................... 12
37 5.3 SOFTWARE DEPENDENCIES ......................................................................................................................... 12
38 5.4 INTERWORKING TO EXTERNAL NODES/INTERFACES ..................................................................................... 12
39 5.5 DEVICE DEPENDENCIES ............................................................................................................................... 12
40 5.6 ENGINEERING IMPACTS ................................................................................................................................ 13
41 6 STANDARDS .................................................................................................................................................... 13
42 6.1 APPLICABLE STANDARDS ............................................................................................................................. 13
43 7 OTHER RELATED DOCUMENTATION......................................................................................................... 13
44 7.1 OTHER DOCUMENTATION............................................................................................................................. 13
45 8 ACRONYMS AND DEFINITIONS ................................................................................................................... 13

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 3

 Multi-Standard Iuh integration Version 1.0

46
47

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 4

 Multi-Standard Iuh integration Version 1.0

48 1 GENERAL FEATURE INFORMATION

49 1.1 FRS Title: Multi-Standard Iuh integration

50 1.2 Feature # 171268

51 1.3 Network Element

52 Small Cell AP, Small Cell GW, Small Cell Management System

53 1.4 Feature Order Type

54 Basic

55 1.5 Internal/External Feature

56 Internal

57 1.6 PLM FRS Owner

58 Philippe Cassuto

59 1.7 FRS Contributors

Functional Prime Name

PLM Philippe Cassuto, Fatima Elomami
SAE Mark Skeates
Design
Product Test
Service Introduction

60

61 1.8 FRS Approvers

Approval Prime Name

PLM Pascal Hamelin
Design Eddie Chow
Product Test

62

63 1.9 Revision History

Version Date Author/Role Changes made

0.01 18/01/2013 Ph. Cassuto / PLM Creation of FRS

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 5

 Multi-Standard Iuh integration Version 1.0

0.2 08/02/2013 Ph. Cassuto / PLM Updated after review

1.0 19/02/2013 Ph. Cassuto / PLM Baseline version after check
64

65 1.10 Requested Releases

Feature Patch/Prop/S
Release Comments
# ource
171268 BCR 4.3 BCR4.3 for phase 1 containing 3G only solution
66

67 2 FEATURE INFORMATION

68 2.1 Feature Overview

69 This feature enables the support on the SCGW of a 3rd party CPE using Iuh interface based on
70 3GPP R10 specifications.

71 2.2 Feature Description

72 AT&T requests that for Indoor Small Cells, a Multi-Standard product is provided which supports a
73 Multi-Vendor implementation. The Indoor Multi-Standard product should support multiple
74 technologies: 3G, LTE and WiFi.

75 To support Multi-Vendor implementation, ALU is requested to act as the integrator for the Indoor
76 Small Cells from either vendor. This means ALU has to provide the network integration as per the
77 customer’s requirements. This is divided into Core Network integration and IT System integration.

78 Some elements come from the customer’s existing solutions, so not all elements are necessarily
79 provided in the end-to-end solution architecture. In particular, the SeGW is from Cisco, the NTP
80 server is either from Meinberg or Symmetricon and the Load Balancers are from F5. AT&T also
81 use firewalls from Juniper.

82 To support this request the following elements are required to meet the architecture:

83  9763 Multi-Standard Metrocell Indoor

84  9766 Multi-Standard Small Cell Gateway

85  9772 WiFi Service Controller

86  7750 Service Router Wireless LAN Gateway

87  8950 AAA

88  9753 Wireless Management System Evolution

89  9952 Wireless Provisioning System

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 6

 Multi-Standard Iuh integration Version 1.0

90  9958 Network Performance Optimiser

91  9959 Wireless Trace Analyser

92  Motive Home Device Manager

93  Motive Service Management Platform

94  Relevance Service Enablement Platform

95

96
97  Figure 1. Core Network Integration with 3G, LTE and WiFi

98 In this figure, the Small Cell is an integrated 3G + LTE + WiFi product. The Core Network
99 Integration is shown using the Multi-Standard Small Cell Gateway and assumes use of the 7750
100 Service Router as the WLAN Gateway.

101 For 3rd Party integration, the Small Cells connect using Iuh/S1 with WiFi connectivity optionally
102 bypassing the Security Gateway. For interconnection between Small Cells, use of Iurh/X2 is
103 assumed.

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 7

 Multi-Standard Iuh integration Version 1.0

104 

105  Figure 2. IT System Integration for 3G and LTE

106
107 In this figure, there is no WiFi management integration shown (as this is assumed to be part of the
108 existing AT&T management solution). Each Element Management System is assumed to be 3G
109 and LTE capable.

110 For 3rd Party Integration, the Small Cells connect over TR-069 to the Motive Femtocell Device
111 Management System (FDMS) using the TR-196 standard data model. Integration with Motive
112 Service Management Platform (SMP) is required for 2 reasons:

113  Location "Feature Description" is a full description of the technical requirements for the
114 feature. This includes a problem description followed by a suggested means of solving the
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 8

 Multi-Standard Iuh integration Version 1.0

115 problem. It is best to provide as much detail as possible. Verification is done by using the
116 ADS geo-location database implemented on SMP which also provides some location
117 specific provisioning

118  Metrocell Management Console interface for Pre-Provisioning actions

119 Integration with Relevance Service Enablement Platform (SEP) is required to provide a single Fault
120 Management interface towards the AT&T IT System using a CORBA North Bound Interface (NBI).
121 Additionally an FTP interface is provided towards the AT&T IT System for collection of
122 Performance Management files from the OpenSSH File Server. Lastly an Inventory Management
123 report is generated on the Home Device Manager (HDM) for Inventory Management import into
124 the AT&T IT System.

125

126
127  Figure 3. Proposed Solution Phasing

128 In this proposal, a 3G only solution is proposed based on existing BCR4.x functionality supported.
129 The first step is to introduce Iuh+. In phase 1, the FDMS is also introduced with Location
130 Verification support from SMP/ADS and NBI Integration for FM , PM and IM. The SCMS is
131 required to support provisioning of 3rd Party Small Cells onto the SCGW at this time. Phase 2 adds
132 the LTE parts and the completion of the SMP Metrocell Management Console work. This last
133 phase includes WiFi also.

134

135 2.3 Feature Value and Benefits

136 The added value to the customer is to support multiple technologies in the same product and to
137 support a multi-vendor environment, thus allowing competition between vendors.
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 9

 Multi-Standard Iuh integration Version 1.0

138 2.4 Market Information

139 2.4.1 Applicable Market

140 AT&T

141 2.4.2 Technology

142 Small Cell

143 3 DEVELOPMENT REQUIREMENTS

144 3.1 Development Requirements

Require-
General Requirements
ment #
The existing functionalities supported by the SC-GW on the Iuh interface (currently based on 3GPP
Release 8) shall comply with 3GPP R10 specifications.

Please refer to the following specifications:

 3GPP TS 25.467 : UTRAN architecture for 3G Home Node B (HNB); Stage 2
 3GPP TS 25.468 : UTRAN Iuh Interface RANAP User Adaption (RUA) signalling
R1
specifications
 3GPP TS 25.469 : UTRAN Iuh interface Home Node B (HNB) Application Part (HNBAP)
signalling specifications.

Note : This is to support 3rd party CPE onto ALU SC-GW based on R10 Iuh

In addition, the following functionalities shall be supported on the SC-GW and comply with Iuh
Release 10 specifications :
 PS and CS+PS outgoing handover
 Macro to Small Cell Hand in
 Small Cell to Small Cell Handover using direct Iurh interface (3GPP TS 25.471)
 CMAS
 RTP Mux in UL (3GPP TS 25.444)
R2  Open and Hybrid Access Support

Notes :
 CSG support is not required within this feature, so UEs shall be handled as non-CSG
capable UEs
 Only Non-ALU HNB to Non-ALU HNB Iurh Handover is required

The following shall be supported :

 Provisioning of 3rd Party Small Cells through HNBGW.
 HTTP CR Proxy Support for 3rd Party Small Cells.
R3
Note : The SC-GW provides a Generic NAT proxy which can be configured for an HTTP based
protocol like TR-069. In this case the Connection Request must be sent inside the tunnel, as for ALU
SC – part of the AT&T startup feature. The SC-GW is required to proxy 3rd Party SC in the same
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 10

 Multi-Standard Iuh integration Version 1.0

way.
145
146
147 3.2 Performance / Capacity / Reliability Requirements

Require-
Performance / Capacity / Reliability Requirements
ment #
R4 None
148
149 3.3 Operation, Administration and Management

150 3.3.1 Counter Requirements

Require-
Counter Requirements
ment #
R5 None
151 3.3.2 Fault Management and Alarm Requirements

Require-
Fault Management and Alarm Requirements
ment #
R6 None
152 3.3.3 Configuration Management and Parameter Requirements

153

Require-
Configuration Management and Parameter Requirements
ment #
New parameters may be needed for features which were not previously supported over Iuh (listed
R7
in R2)
154

155 3.3.4 Billing Requirements

Require-
Billing Requirements
ment #
R8 None
156 3.3.5 Serviceability Requirements

Require-
Serviceability Requirements
ment #
R9 None
157 3.3.6 Specific Documentation Requirements

Require-
Specific Documentation Requirements
ment #
R10 None

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 11

 Multi-Standard Iuh integration Version 1.0

158 3.3.7 Software Optional Control

Require- State or New or SOC Code

SOC Title
ment # Usage Existing (if available)
R11
159

160 4 RESTRICTIONS, LIMITATIONS and CLARIFICATIONS

161 4.1 Known Feature Restrictions, Limitations and Clarifications

# Description of Restriction/Limitation/Clarification
It is not required to support both Iu’ and Iuh simultaneously on the SC-GW, ie the SC-GW shall
1
operate either in Iuh or Iu’ mode.
2

162 5 DEPENDENCIES

163 5.1 Known Feature Dependencies

Optional or
# Feature # Feature Title
Required
1

164 5.2 Hardware Dependencies

# Hardware Dependencies
1

165 5.3 Software Dependencies

# Software Dependencies
1 None

166 5.4 Interworking to External Nodes/Interfaces

# Interworking Dependencies
1 ALU HNB GW interworking with non-ALU HNB will require IOT
2

167 5.5 Device Dependencies

# Device Dependencies
1 None, CSG UEs will be handled as non-CSG UEs during Incoming mobility

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 12

 Multi-Standard Iuh integration Version 1.0

168 5.6 Engineering Impacts

# Engineering Impacts
1 None

169 6 STANDARDS

170 6.1 Applicable Standards

# Standard Version Specification Description

1 3GPP TS 25.467 Rel 10 UTRAN architecture for 3G Home Node B (HNB); Stage 2
2 3GPP TS 25.468 Rel 10 UTRAN Iuh Interface RANAP User Adaption (RUA) signalling
3GPP TS 25.469 Rel 10 UTRAN Iuh interface Home Node B (HNB) Application Part
3
(HNBAP) signalling
4 3GPP TS 25.444 Rel 10 Iuh data transport
3GPP TS 25.471 Rel 10 UTRAN Iurh interface - Radio Network Subsystem Application
5
Part (RNSAP) - User Adaption (RNA) signalling

171 7 OTHER RELATED DOCUMENTATION

172 7.1 Other Documentation

173 none

174 8 ACRONYMS AND DEFINITIONS

Acronym Definition
ADS Auxiliary Data Store
AP Access Point
ASN.1 Abstract Syntax Notation One
BCR Base Station Cluster Release
BSR Base Station Router
CAMEL Customized Application for Mobile Network Enhanced Logic
CDR Customer Data Record
CGF Charging Gateway Function
CPE Customer Premises Equipment
FDMS Femtocell Device Management System (FDMS)
FM Fault Management
GGSN Gateway GPRS Supporting Node
GPRS General Packet Radio System
GSM Global System for Mobile Telecommunications
GW Gateway
HDM Home Device Manager
HLR Home Location Register
HNB Home NodeB
IM Inventory Management
IMSI International Mobile Subscriber Identity
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 13

 Multi-Standard Iuh integration Version 1.0

MAP Mobile Application Part

MSC Mobile Switching Center
NBI Northbound Interface
NTP Network Time Protocol
PDP Packet Data Protocol
PLMN Public Land Mobile Network
PM Performance Management
RUA RANAP User Adaptation
SCGW Small Cell Gateway
SCMS Small Cell Management System
SCP Service Control Point
SeGW Security Gateway
SEP Service Enablement Platform
SGSN Serving GPRS Support Node
SIG SS7/IP Gateway
SMP Service Management Platform
UMTS Universal Mobile Telecommunications System
UTRAN Universal Terrestrial Radio Access Network
175

176

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 171268 Page 14