Femto Group support

Feature Requirements Specification

Feature # 80569
Version 0.02

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 # 80569 Page 1

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

Feature # 80569 Page 2

Femto Group support Version 0.02

TABLE OF CONTENTS

1 GENERAL FEATURE INFORMATION................................................................................................... 3

1.1 FRS TITLE: FEMTO GROUP SUPPORT................................................................................................. 3
1.2 FEATURE # 80569........................................................................................................................ 3
1.3 NETWORK ELEMENT..................................................................................................................... 3
1.4 FEATURE ORDER TYPE................................................................................................................. 3
1.5 INTERNAL/EXTERNAL FEATURE....................................................................................................... 3
1.6 PLM FRS OWNER....................................................................................................................... 3
1.7 FRS CONTRIBUTORS.................................................................................................................... 3
1.8 FRS APPROVERS......................................................................................................................... 3
1.9 REVISION HISTORY....................................................................................................................... 3
1.10 REQUESTED RELEASES.............................................................................................................. 4
2 FEATURE INFORMATION.................................................................................................................... 4
2.1 FEATURE OVERVIEW..................................................................................................................... 4
2.2 FEATURE DESCRIPTION................................................................................................................. 4
2.3 FEATURE VALUE AND BENEFITS...................................................................................................... 5
2.4 MARKET INFORMATION.................................................................................................................. 6
2.4.1 Applicable Market.................................................................................................................... 6
2.4.2 Technology.............................................................................................................................. 6
3 DEVELOPMENT REQUIREMENTS...................................................................................................... 6
3.1 DEVELOPMENT REQUIREMENTS...................................................................................................... 6
3.2 PERFORMANCE / CAPACITY / RELIABILITY REQUIREMENTS...................................................................6
3.3 OPERATION, ADMINISTRATION AND MANAGEMENT..............................................................................7
3.3.1 Counter Requirements............................................................................................................. 7
3.3.2 Fault Management and Alarm Requirements............................................................................7
3.3.3 Configuration Management and Parameter Requirements........................................................7
3.3.4 Billing Requirements................................................................................................................ 7
3.3.5 Serviceability Requirements..................................................................................................... 7
3.3.6 Specific Documentation Requirements.....................................................................................7
3.3.7 Software Optional Control........................................................................................................ 7
4 RESTRICTIONS, LIMITATIONS AND CLARIFICATIONS......................................................................8
4.1 KNOWN FEATURE RESTRICTIONS, LIMITATIONS AND CLARIFICATIONS....................................................8
5 DEPENDENCIES.................................................................................................................................. 8
5.1 KNOWN FEATURE DEPENDENCIES................................................................................................... 8
5.2 HARDWARE DEPENDENCIES........................................................................................................... 8
5.3 SOFTWARE DEPENDENCIES............................................................................................................ 8
5.4 INTERWORKING TO EXTERNAL NODES/INTERFACES............................................................................8
5.5 DEVICE DEPENDENCIES................................................................................................................. 8
5.6 ENGINEERING IMPACTS.................................................................................................................. 8
6 STANDARDS........................................................................................................................................ 9
6.1 APPLICABLE STANDARDS............................................................................................................... 9
7 OTHER RELATED DOCUMENTATION................................................................................................. 9
7.1 OTHER DOCUMENTATION............................................................................................................... 9
8 ACRONYMS AND DEFINITIONS.......................................................................................................... 9

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

Feature # 80569 Page 3

Femto Group support Version 0.02

1 GENERAL FEATURE INFORMATION

1.1 FRS Title: Femto Group support

1.2 Feature # 80569

1.3 Network Element

BSR Femto, BSR Gateway, FMS

1.4 Feature Order Type

Optional

1.5 Internal/External Feature

External

1.6 PLM FRS Owner

Philippe Cassuto

1.7 FRS Contributors

Functional Prime Name

PLM Philippe Cassuto, Pascal Hamelin
SAE
Design
Product Test
Service Introduction

1.8 FRS Approvers

Approval Prime Name

PLM
Design
Product Test

1.9 Revision History

Version Date Author/Role Changes made

0.01 02/07/2008 Ph. Cassuto / PLM Initial version
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

Feature # 80569 Page 4

Femto Group support Version 0.02

0.02 10/07/2008 Ph. Cassuto /PLM Updated after 1st review

1.10 Requested Releases

Feature Patch/Prop/S
Release Comments
# ource
80569 BCR 2.2

2 FEATURE INFORMATION

2.1 Feature Overview

This feature introduces the support for Femto groups which may be used for instance in small or
medium enterprises, or in public areas (airports, ..).

2.2 Feature Description

Femto Group definition

A Femto group targets various customers’ needs, mainly to cover some private or public areas
(small/medium enterprise, airports, etc…) where the individual Femto is not sufficient in terms of
capacity or coverage.

The coverage can be provided by a group of Femtocells, located close together, instead of only
one Femtocell. Additionally, non co-located Femtocells may also be part of a group (eg. for a
company having multiple offices or stores).

A Femto group can include up to 50 Femtos. A Femto could either be a part of a Femto Group
(only one Femto group, the Femto can not be part of two groups) or be an individual Femto (not
belonging to any group).

All Femtos belonging to the same group should belong to the same Femto Cluster.

All Femtocells belonging to the same group should have a common Access Control (Open/Closed
access, and ACL if any) and the same billing definition.

In addition, to avoid useless Location/Routing Area Updates, all co-located Femtos belonging to a
group should have a common Mobility LAC/RAC definition.

The co-location notion should rely on preconfigured information through OAM (static) or not rely
on OAM pre configured information but on information coming from information coming from the
network listening function (dynamic).

Access Control Management

All Femtos belonging to the same group should have the same Open / Closed access definition.

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

Feature # 80569 Page 5

Femto Group support Version 0.02

In case of Closed Access, all Femtos belonging to the same group should have a commun
ACLlist. An authorized femto user should be able to update the ACLlists for the group of Femtos
without having to change the ACL lists individually for each of the Femtos. There could be multiple
authorized users that can change and update the ACL.

This common management of the Access Control Lists should be applicable for both owners and
guests.

The number of users (owners (employees…) or guests) who should be able to access the Femto
group is logically higher than the number of users in case of a residential Femto; therefore the
ACLlists, previously, in BCR2.1 limited to 32 IMSI, should be extended to support up to 256 IMSI.

Billing

All the Femtos belonging of the same group should have a common billing definition. In the
previous BCR2.1 release the Femto can differentiate between the different categories of users
(owner, visitors) using the LAC1/LAC2/SAC1/SAC2 attributes. Optionally, in release BCR2.2,
these LACx/SACx can be dynamically read from the macro cell, or can be defined as in BCR2.1

In the BCR2.2, the Femtos belonging to the same Femto Group should share the same definition
of these LACx/SACx parameters. An FMS user should be able to update these parameters for the
group of Femtos without having to change them individually for each of the Femtos.

Emergency

All the Femtos belonging of the same group should individually define the emergency calls
attributes (ie SAC3/LAC3). Allocation should be done as it was a standalone femtocell.

Mobility management

The LAC/RAC parameters should be common to all co-located Femtos, that belong to the same
group. This shall be enforced in order to avoid useless Location/Routing Area Updates while
moving inside the group. For instance, Tthe network listening function should could be used to
sniff the Location Area Code parameters for neighbour cells belonging to the same group.

The operator has the possibility to set manually these parameters or he can use the auto-
configuration functionalities provided by FMS (Geographical location based algorithm or Random
assignation).

For mobility purposes, each Femto which belongs to a group should know all the other Femtos
that belong to the same group (identified by their PSC/cell id). This shall be provided by the FMS.

Cell reselection and Handover within/from/to a Femto group is described in FRSs 77028 and
75494.

2.3 Feature Value and Benefits

Ability to use multiple Femtos to cover a larger area and higher capacity than an individual Femto,
while allowing simple configuration and management.

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

Feature # 80569 Page 6

 Femto Group support Version 0.02

2.4 Market Information

2.4.1 Applicable Market

Global

2.4.2 Technology

UMTS

3 DEVELOPMENT REQUIREMENTS

3.1 Development Requirements

Require-
General Requirements
ment #
R1 It shall be possible to define Femto Groups from FMS
A Femto Group could contain as many as 50 Femtos. They shall all be part of the same Femto
R2
cluster
R3 A Femto BSR can belong to only one Femto Group (or none)
All Femtos belonging to a group shall have the following parameters in common
 Frequency used
 Access Control
o Open or Closed access
o Access Control List in case of Closed Access
 Billing definition :
o if Home Tariff feature is used, the areaSelectNormalFlag should be common to all
Femtos within the group. This is not true for areaSelectEmergencyFlag, which
shall be set individually as in the non-group case.
R4
o If Dynamic SAC/LAC is used (FRS 78695), all Femtos of the same Group shall be
configured in the same way (although it could happen that not all the macro LACs
or SACs are the same).
 For co-located BSRs only:
o the same mobility LAC/RAC definition.
o The 3G listening function shall could be used to set/override the LAC/SAC sniffed
from an existing BSR part of the same group
o Alternatively, this could be defined from the FMS

For Mobility purposes (see FRSs 77028, 75494), each Femto part of a Group should be aware of all
1.
the other Femtos in the same group. At least the PSC (for cell reselection and Handover) and Cell
xx
id (for Handover) should be known.
R5 For Femtos part of a group, the ACLlist should be extended to support up to 256 IMSIs.
R6

3.2 Performance / Capacity / Reliability Requirements

Require-
Performance / Capacity / Reliability Requirements
ment #

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

Feature # 80569 Page 7

 Femto Group support Version 0.02

The support of Femto groups shall not negatively impact the capacity / performance of the BSG or
R7 other nodes. In particular, scanning the ACL in the BSG shall be optimized due to the extension to
256 IMSIs (eg. scanning the common ACL list only once for the Femto Group).

3.3 Operation, Administration and Management

3.3.1 Counter Requirements

Require-
Counter Requirements
ment #
R8 Not applicable
3.3.2 Fault Management and Alarm Requirements

Require-
Fault Management and Alarm Requirements
ment #
R9 Not applicable
3.3.3 Configuration Management and Parameter Requirements

Require-
Configuration Management and Parameter Requirements
ment #
It shall be possible to activate or deactivate this feature through FMS configuration. Please refer to
R10
FRS 75497.

3.3.4 Billing Requirements

Require-
Billing Requirements
ment #
R11 All the Femtos belonging to a group shall have common billing definition.
3.3.5 Serviceability Requirements

Require-
Serviceability Requirements
ment #
R12 None
3.3.6 Specific Documentation Requirements

Require-
Specific Documentation Requirements
ment #
R13 None
3.3.7 Software Optional Control

Require- State or New or SOC Code

SOC Title
ment # Usage Existing (if available)
R14

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

Feature # 80569 Page 8

Femto Group support Version 0.02

4 RESTRICTIONS, LIMITATIONS and CLARIFICATIONS

4.1 Known Feature Restrictions, Limitations and Clarifications

# Description of Restriction/Limitation/Clarification
1

5 DEPENDENCIES

5.1 Known Feature Dependencies

Optional or
# Feature # Feature Title
Required
1 Mandatory 75497 Management for a group of Femto cells
2

5.2 Hardware Dependencies

# Hardware Dependencies
1 None

5.3 Software Dependencies

# Software Dependencies
1 None

5.4 Interworking to External Nodes/Interfaces

# Interworking Dependencies
1 None

5.5 Device Dependencies

# Device Dependencies
1 None

5.6 Engineering Impacts

# Engineering Impacts
1 None

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

Feature # 80569 Page 9

Femto Group support Version 0.02

6 STANDARDS

6.1 Applicable Standards

# Standard Version Specification Description

1
2

7 OTHER RELATED DOCUMENTATION

7.1 Other Documentation

none

8 ACRONYMS AND DEFINITIONS

Acronym Definition
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
GGSN Gateway GPRS Supporting Node
GPRS General Packet Radio System
GSM Global System for Mobile Telecommunications
HLR Home Location Register
IMSI International Mobile Subscriber Identity
MAP Mobile Application Part
MSC Mobile Switching Center
PDP Packet Data Protocol
PLMN Public Land Mobile Network
SCP Service Control Point
SGSN Serving GPRS Support Node
SIG SS7/IP Gateway
UMTS Universal Mobile Telephone System
UTRAN Universal Terrestrial Radio Access Network

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

Feature # 80569 Page 10