Release 3+4 Highlights
Release Steering Group
13th June 2014
17/06/2014 © Small Cell Forum Ltd 2013
Release 4: Urban
All downloadable from www.scf.io
Urban Small Cells
Release Overview
[103]
Backhaul
Regulatory Radio
Deplo...
• Work Programme to step through X2 SON features, analyse for interoperability,
and make recommendations for use or modifi...
Plugfests and IOP
17/06/2014 © Small Cell Forum Ltd 2013
Plugfests summary
28 March 2012 © Small Cell Forum Ltd 2012
Topics Participants
Test
cases
Venue
1st 3G plugfest
IPSec,
Iu...
• Topics:
• Regression tests
• Security,
• S1 interface,
• X2 interface (Mobility scenarios,
• HeMS (TR-069) interface,
• ...
Urban Small Cell Network
Architectures
17/06/2014 © Small Cell Forum Ltd 2013
• Supporting incremental
increase in small cell mobility
• Residential: autonomous units,
idle mode mobility macro-to-
sma...
SCF088: Idle and Connected Mode
Mobility Handling
17/06/2014 © Small Cell Forum Ltd 2013
Urban Small Cell Services
Integration
17/06/2014 © Small Cell Forum Ltd 2013
Small Cell Network Architecture
Supporting SC Services
17/06/2014 © Small Cell Forum Ltd 2013
Supporting Services APIs
17/06/2014 © Small Cell Forum Ltd 2013
SCF093: Small Cell Storage API SCF092: Review of Precise
L...
Upcoming SlideShare
Loading in …5
×

SCF Release 3/4 Achievements and Implications

367 views
267 views

Published on

At a recent workshop, we reviewed the achievements and implications of the latest Release documents from Small Cell Forum

Published in: Technology, Health & Medicine
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
367
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SCF Release 3/4 Achievements and Implications

  1. 1. Release 3+4 Highlights Release Steering Group 13th June 2014 17/06/2014 © Small Cell Forum Ltd 2013
  2. 2. 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]
  3. 3. • 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) 17/06/2014 © Small Cell Forum Ltd 2014
  4. 4. Plugfests and IOP 17/06/2014 © Small Cell Forum Ltd 2013
  5. 5. Plugfests summary 28 March 2012 © Small Cell Forum Ltd 2012 Topics Participants Test cases Venue 1st 3G plugfest IPSec, Iuh interface 22 26 March 2010, Sophia Antipolis, France 2nd 3G plugfest HMS (TR-069) interface 14 35 January 2011, Sophia Antipolis, France 3rd 3G plugfest Mobility scenarios 12 42 June 2011, Lannion, France 1st LTE plugfest S1, X2, Mobility scenarios, VoLTE 20 28 June 2013, Kranj, Slovenia
  6. 6. • 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 July Paris, France For further information, join IOP WG maillist.
  7. 7. Urban Small Cell Network Architectures 17/06/2014 © Small Cell Forum Ltd 2013
  8. 8. • 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 Architectures SCF088
  9. 9. SCF088: Idle and Connected Mode Mobility Handling 17/06/2014 © Small Cell Forum Ltd 2013
  10. 10. Urban Small Cell Services Integration 17/06/2014 © Small Cell Forum Ltd 2013
  11. 11. Small Cell Network Architecture Supporting SC Services 17/06/2014 © Small Cell Forum Ltd 2013
  12. 12. Supporting Services APIs 17/06/2014 © Small Cell Forum Ltd 2013 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.

×