SCF Release 3/4 Achievements and Implications

13/04/2023 © Small Cell Forum Ltd 2013

Release 3+4 Highlights

Release Steering Group13th June 2014

Release 4: Urban

All downloadable from www.scf.io

Urban Small Cells Release Overview

[103]

Backhaul

Regulatory Radio

Deployment

Services

Network Architecture

Inter-operability

Market

SON Use cases [077]

Market status [050]

NET Architectures for Urban [088]

Integrated Small cell Wi-Fi [089]

Synchronisation [075]Backhaul Issues for Urban

Small Cells [095]

Backhaul Requirements & Solutions [049]

Urban Deployment Issues [096]

Urban Market Drivers & Challenges [086]

Business case for urban small cells and their

backhaul [087]

Small Cells - The Big Idea [030]

Regulatory Aspects of small cells [076]

Urban case studies [098]

X2 Interoperability in Multivendor HetNets [059]

Small Cell Security [099]

Services for Urban Small Cells [090]

Services API Programmer’s Guide [091]

Location Based API requirements [092]

Content Management Services [093]

LTE Small Cell-API [082]

Small Cell Plugfests [085]

http://www.scf.io/document/103























• Work Programme to step through X2 SON features, analyse for interoperability, and make recommendations for use or modification to enable interoperability where possible.

• Compare and Contrast with NGMN whitepaper “Recommended Practices for Multi-vendor SON Deployment”, NGMN, January 2014

• Both papers discuss MLB and MRO, and broadly agree• Concluded that MLB is not interoperable as-is and we’ve made some

recommendations as to how it could be used in an interoperable way• MRO is (on the face of it) is much more interoperable

• SCF paper goes on to discuss ICIC and eICIC, concluding that • ICIC is good for mesh-type single layer networks, but not for HetNets as is• eICIC is largely interoperable, with some corner cases requiring further treatment

• “The topic of X2 interoperability as an engine of HetNet growth remains very important, and the firmest conclusion we can reach at this point is that the story is not complete.”

• “Further maintenance updates of this document will capture improved recommendations and best practice as it validates those recommendations into guidelines.”

SON/X2 Interoperability (SCF059)


Plugfests and IOP

Plugfests summary

28 March 2012 © Small Cell Forum Ltd 2012

Topics Participants Test cases

Venue

1st 3G plugfestIPSec, Iuh interface

22 26 March 2010,Sophia Antipolis,France

2nd 3G plugfestHMS (TR-069) interface

14 35 January 2011,Sophia Antipolis,France

3rd 3G plugfestMobility scenarios 12 42 June 2011,

Lannion,France

1st LTE plugfestS1, X2, Mobility scenarios,VoLTE

20 28 June 2013,Kranj,Slovenia

• Topics: • Regression tests• Security,• S1 interface,• X2 interface (Mobility scenarios,• HeMS (TR-069) interface,• VoLTE• CSFB (including E911)• CMAS• SON• PCI,• ANR,• MRO

• Participants: 25• Test cases: 94

2nd LTE plugfest

© Small Cell Forum Ltd 2012

Venue:23rd June – 2nd JulyParis, France

For further information, join IOP WG maillist.


Urban Small Cell Network Architectures

• Supporting incremental increase in small cell mobility

• Residential: autonomous units, idle mode mobility macro-to-small cell and vice versa, connected mode small cell-to-macro, low power

• Enterprise: Residential baseline plus small cell-to-small cell (idle and connected), higher power but limited interactions due to BPL

• Urban: no BPL & higher power hence increased interactions, Macro-to-small cell mobility (connected and idle mode)

Urban Network ArchitecturesSCF088


SCF088: Idle and Connected Mode Mobility Handling


Urban Small Cell Services Integration


Small Cell Network Architecture Supporting SC Services


Supporting Services APIs

SCF093: Small Cell Storage API SCF092: Review of Precise Location APIs• Identifying common PIL use cases and

requirements from the forum’s membership base.

• Surveying existing location APIs that can be mapped in part or whole to a subset of the use cases and requirements.

• Provide a gap analysis comparing needs and APIs to identify possible changes required to existing APIs or potentially new APIs.

• Recommend a set of actions to remove the gaps, and attain a complete set of APIs able to meet the PIL needs of the industry.

SCF Release 3/4 Achievements and Implications

Technology

Transcript of SCF Release 3/4 Achievements and Implications