Академический Документы
Профессиональный Документы
Культура Документы
Source:
Airvana Femtocell White Paper (October 2007)
GSMA document FCG.03 3G Femto Solution Implementation Guidelines 1.0 (03
July 2008)
Pendahuluan
Telah muncul kelas baru dari base station mini yang disebut Femtocell (atau terkadang
dipisah menjadi dua kata Femto cell, sama seperti Handover dan Hand off).Femtocell
menawaarkan indoor wireless coverage kepada mobile phone untuk menggunakan
koneksi internet broadband. Istilah femtocell digunakan secara luas di dunia industri,
yang juga bisa diartikan in-house base station. Kebanyakan femtocell menunjukkan
(berfungsi) sebagai 3% in house base station yang mengimplementasikan teknologi
UMTS dan HSPA. Tetapi femtocell juga memungkinkan untuk menjembatani 2G,
CDMA 2000, dan WiMAX ke dalam gedung/rumah. Femtocell juga menunjukkan multi
teknologi in house home Gateway (atau CPE, Customer Premises Equipment) termasuk
DSL, WiFi atau 3G.
Sampai sekarang pangsa pasar femtocell masih secara besar dipengaruhi dan di mainkan
oleh komunitas vendor. Masih ada kemungkinan untuk mendapat arsitektur Femtocell 3G
di dalam spesifikasi 3GPP release 8, untuk mendukung persyaratan MNO (Mobile
Network Operator) untuk standarisasi.
GSMA supports the requirements put forward in 3GPP TS 22.011. In addition, from the
operator
perspective, the femto architecture shall fulfil the following requirements:
R1. Femto solution shall connect to mobile core network with the standard 3GPP interfaces,
Iucs and Iups.
R2. To maximize the ADSL broadband upstream bandwidth usage efficiencies, femtocell
upstreams VPN bandwidth shall not exceed 200 kbps for a combined 4 simultaneous
voice calls, including signalling traffic and overhead.
R3. The uplink and downlink data traffic shall be optimised regarding overhead. Here
different traffic scenarios like keep alive signals or streaming should be considered.
R4. The Voice quality shall not be lower than for 3G calls (e.g. latency, jitter KPI have to be
considered).
R5. The number of interfaces towards the legacy network elements shall be limited (e.g. to
limit the IOTs). This shall be considered also for the evolution towards IMS.
R6. There shall be no need for extra IMS or SIP application servers for the Femtocells only.
R7. The FAP shall not connect directly to critical mobile network equipments (such as HLR,
MSC)
To limit impacts on network if attacks are from the FAP
To limit dimensioning impacts on mobile network equipments
To limit configuration needed in mobile network
R8. Femto solution shall be compatible with all services implemented in the macro mobile
network like e.g.
Compatible with IN solutions (for prepaid or value added services...)
At least same charging possibilities as for the macro network, in addition to
having possibility for specific charging policy for femto services
Legal interception
Emergency calls, including position information
Supplementary voice services
Video services
R9. No macro network re-configuration shall be necessary each time a new FAP is installed.
The FAP together with the FGW shall be responsible to limit the impact on the macro
network. The Cell ID and location areas shall be handled in an optimised way.
R10. To limit the amount of location updates towards the HLR the FGW shall support IuFlex
R11. Interface between FAP and mobile operator equipment (including O&M) shall evolve
towards a standardised interface
To allow introduction of new FAP without having to change the femto
system
The FAP shall be software update capable via e.g. TR069 based methods.
R12. Interface between FAP and mobile network shall be secured based on 3GPP standards.
For more details, refer to FF WG3 and 3GPP SA3 security requirements
documents and the GSMA white paper Security Issues in Femtocell
Deployment.
R13. FAP shall support local traffic offload controlled by mobile operator to fulfil operator
and
regulatory requirements
The local traffic offload shall be based on 3GPP standards as yet to be
defined.
R14. Direct Tunnel capabilities shall be supported to optimise the traffic load on an SGSN.
As
this is based on available standards this shall be available from the beginning.
R15. Evolution/scalability, the femto solution shall be able to evolve to adapt to a possible
boost
of data traffic in a cost effective way.
R16. Femto solution shall provide industry standardized QoS treatment for different type of
traffic across the broadband pipe to the extent possible.
R17. Femto management system shall utilize industry standardized protocol. For further
information look into the GSMA white paper Management of Femtocells.
R18. Femtocells shall support closed user groups as well as open access.
Arsitektur Femtocell
3GPP uses the term Home NodeB (HNB) for 3G femtocells, whereas the term Home
eNodeB
is used for the LTE (3GPP Long Term Evolution) femtocells.
In the Release 8 specification work, two items are work in process:
a Technical Report (TR) on Home NodeB/ Home eNodeB, reported in 3GPP TR 25.820
a TR of self-organising networks (SON) related O&M Interfaces for Home NodeB,
reported in 3GPP TR 32.821
Auto configuration
The femto gateway (FGW) would typically contain functions like
3GPP RANAP
Network timing delivery and synchronisation
Femtocell authentication and authorisation
AP Topology hiding
Network topology hiding
IP Security functions
Femtocell traffic aggregation and routing
Auto configuration
2.
3.
4.
5.