3G Network Convergence - Stanford Universityweb.stanford.edu/class/msande237/viewgraphs/Chia.pdf3G...
Transcript of 3G Network Convergence - Stanford Universityweb.stanford.edu/class/msande237/viewgraphs/Chia.pdf3G...
3G Network ConvergenceThe Road to a unified mobile network
Dr. Stanley ChiaDirector, Strategic Technologies, Group R&D-US
2
Contents
The OHG Harmonisation Effort and the Global 3G System Proposal MWIF Continued to Drive Network ConvergenceThe Toronto All-IP Harmonization MeetingPutting Words into Actions
3
Regional3G Technology
Selection
IMT2000Submissions /OHG Formed
Strong Growth in Mobile Industry
1997 20021998 20001999 2001
4
CDMA-2000CDMA-2000
WCDMAWCDMA
WCDMAWCDMAEDGEEDGETD-
SCDMATD-
SCDMA WCDMAWCDMACDMA-2000CDMA-2000
WCDMAWCDMA
Ten IMT-2000 Terrestrial 3G System Proposals …
EuropeUSAJapan
KoreaChina
DECTDECT
WIMSWIMS
5
FragmentedStandards
Unnecessary costs to industryUncertainty by application developersComplexity to consumers
Two to Three Major StandardsSame problem as fragmentationMaximum industry growth not realisedContinuation of “Standards Wars”
Unification ofStandards
Eliminates unnecessary industry costsStimulates value-added servicesMeets the needs of customers
Unified standards are good for consumers, operators & manufacturers
… Giving Rise to Multiple 3G Scenarios
6
A Common Chip RateUniform Pilot Structures
Asynchronous & Synchronous
WCDMACDMA2000
Two Uncompromisable Factions …
Synchronous
Common Pilot withCode Division Multiplexing
Chip Rate: 3.6864 Mcps
Asynchronous
Dedicated Pilot withTime Division Multiplexing
Chip Rate: 4.096 Mcps
IMT-2000
7
FDDDS
FDDMC TDD
EvolvedGSM MAP
EvolvedANSI-41
Networkto NetworkInterface
Radio Access“Family of 3GCDMA Modes”
Core Network“Family of 3G
Systems”
Core Network“3G Inter-Family
Roaming”
… Unwillingly Agreed to a Global Harmonization Framework …
MC = MulticarrierDS = Direct SpreadNNI = Network Node InterfaceF/TDD = Frequency/Time Division Duplex
Flexible connection between Modes andCore Networks based on operator needs
8
… Which Led to the Historical OHG Agreement
tbdSynchronousas CDMA2000
Asynchronous/Synchronous
IMT-2000
TDD
tbd
tbd
3.84 Mcps
FDDMulti-carrier
CDM
CDM
3.6864 Mcps
FDDDirect Spread
TDM
CDM
3.84 Mcps
Synchronization
Dedicated Pilot
Common Pilot
Chip Rate
FDD = Frequency Division DuplexTDD = Time Division DuplexCDM = Code Division MultiplexingTDM = Time Division Multiplexing
9
Regional3G Technology
Selection
IMT2000Submissions /OHG Formed
OHGAgreement
Strong Growth in Mobile Industry
1997 20021998 20001999 2001
10
ANSI-41based
Core Network
GSM-MAPbased
Core Network
MC-Mode AccessNetwork
MC-Mode AccessNetwork
DS-ModeAccessNetwork
DS-ModeAccessNetwork
To ANSI-41CN via CDMA2000 stack
To GSM-MAP CN via WCDMA stack
To ANSI-41 CN via CDMA2000 L3 & WCDMA stack
To GSM-MAP CN via WCDMA L3 & CDMA2000 stack
But The Core Network Remained More Problematic …
Network to Network Interface
11
L3 (WCDMA)
L3(CDMA2000)
Hooks
Hooks
Hooks
Extension
Extension
Extension
L3 (WCDMA)
GSM MAP
L3 RRC (WCDMA)
L2 (WCDMA)
L1 (WCDMA)
ANSI-41
L3 (WCDMA)
L3(WCDMA)
Hooks
Hooks
Hooks
Extension
Extension
Extension
L3 (CDMA2000)
ANSI-41
L3 RRC (cdma2000)
L2 (cdma2000)
L1 (cdma2000)
GSM MAP
Additional functionalitieswhich needed to be specified to meet
requirements when hooks are in place
Functionalities specifiedin the initial release of
the standards for futureextensions without major
protocol change
… And the Answer is to Use Hooks and Extensions
12
2G to 3GInteroperation
Direct-SpreadMode
CommonPilot
Multi-carrierMode
TDDMode
Chip rate = 3.84 McpsAsynchronousCDM Common PilotTDM Dedicate Pilot
Chip rate = 3.6864 McpsSynchronousCDM Common PilotCDM Dedicated Pilot
Chip rate = 3.84 / 1.36 Mcps
Other parameters tbd
Hooks and extensionto be defined to ensure
handoff / roaming
The “Global 3G System” Ideal … Had No Real Industry Interests
WCDMA, EDGEcdmaOne
cdmaOneCDMA2000 1X
GSM MAP /ANSI-41
13
Regional3G Technology
Selection
IMT2000Submissions /OHG Formed
MWIFFormed
OHGAgreement
Strong Growth in Mobile Industry
Peak of the Internet Boom
1997 20021998 20001999 2001
14
MWIF Was Formed in 2002 to Drive the Vision of Convergence
• A Mobile Internet Environment With:– Interoperability of services and applications with all radio and other media access
technologiesIncludes legacy wireless and wire line networksCommon radio access protocol
– Standard open interfaces among core network componentsPlug and play installation and configuration
– True customer mobility across all networks– Common service and applications development environment
• Single IP based “backhaul” network• Shared equipment between the Internet and Telecommunications communities• Seamless integration of mobile telephony and Internet services and content
15
Regional3G Technology
Selection
IMT2000Submissions /OHG Formed
MWIFFormed
OHGTorontoMeeting
OHGAgreement
EconomySlow Down
Strong Growth in Mobile Industry
Peak of the Internet Boom
3G LicenseAuctions in
Europe
1997 20021998 20001999 2001
16
Another Attempt … The OHG / MWIF Toronto Meeting
An IP Core Network Harmonization Workshop was held on April 3-4, 2002 in Toronto, Canada.The following conclusions and recommendations were reached:
– The harmonization of 3GPP/3GPP2 IP Multimedia Core Networks is aworthwhile and achievable goal.
– This should be pursued urgently by both PP groups.
– Focus the harmonization efforts to areas where synergies already exist with priority given to the harmonization of:
OSA / PARLAY based service APIs.
IP Multimedia Subsystem (IMS).
– Adopt a single IMS reference model with consistent terminology.
– Ensure interoperability between all IMS mobiles.
– Ensure application level intersystem IMS roaming
17
… And There Is A Glimpse of Hope
The Meeting agreed that 3GPP and 3GPP2 should:– avoid duplication of work– align the IMS and service aspects of their respective Reference Models– collaborate closely on any requirements to be input into IETF related to SIP
extensions and other issues– establish formal and informal mechanisms (e.g., joint e–mail exploder) to
promote harmonization activities– consider routes to joint requirements analysis and joint specification
development– work together on a common evolution strategy taking into account the vision
work in other groups including ITU and IP2 Ad Hoc
It was also agreed that:– the existing schedules (e.g., 3GPP Release 5) should not be negatively
impacted.– common mobility management is an item for future consideration.– 3GPP2 should utilize 3GPP Release 5 IMS and Parlay 3.1 as the base for
their on-going development activities.
18
To Put Words into Actions …
Vodafone Group and Verizon Wireless have jointly issued an invitation to their strategic suppliers to collaborate on identifying a common core architecture:
- An architecture towards which each company can evolve its core network.
- The target networks is to be based on a common standard.
Such a common core network would support:
- Service transparency.
- Application portability.
- Roaming between Vodafone and Verizon Wireless networks.
19
… With A Number of Key Objectives
Enable interoperability between CDMA2000 and GSM / WCDMA networks and other wireless technologies.
Achieve end-user service and quality of service transparency between CDMA2000 and GSM / WCDMA operators.
Share common service applications and service creation capabilities.
Enable the deployment of All-IP-based network for voice, data and multimedia services.
Adapt a common set of 3GPP / 3GPP2 standards.
Assure a coordinated evolution plan from the existing circuit switched and packet data networks to “All-IP” based networks.
Drive standards organization to converge to a single common core network standard.
20
An All-IP Common Core Concept …
A common core network is considered essential to ensure service transparency between CDMA2000 and GSM/WCDMA operators in the long term
“Common” core network
CDMA2000Radio Interface
CDMA2000 Terminal - or -
Multimode Terminal Interface 1
CDMA2000RAN
Interface 2
UMTSRAN
UMTSRadio Interface
UMTS Terminal- or -
Multimode Terminal
WLAN
802.11b / aRadio Interface
WLAN Terminal- or -
Multimode Terminal
Interface 3
21
… Some Basic Requirements for the Solution
The solution should meet, at least, the following requirements:
- Transparent and seamless support of current and evolving services and applications when roaming from one market to another
- Seamless support of SIP based call model and service management
- Provision to support legacy infrastructure in the respective networks
- A common service creation platform
- Evolution path to the target IP based architecture
- Compatible with existing and future mobiles as well as wireless LAN based radio interfaces
- Full quality-of-service support for real-time and non-real-time services
IP
22
A Potential Evolution Roadmap
The evolution to a common core network may need to go through two key stages: - G95 type interoperability and interworking function initially to achieve near
term service transparency. - Migration to an “All-IP” platform by the adoption of compatible IP-based core
network with capability of supporting multiple radio interfaces.
Interworking function
IP-based multimedia domain /
subsystem
Single core with multiple
radio interfaces
Gateway A single standard
Multiple core and multiple
radio interfaces
Near term Long term
23
Key Steps to a Common Core Network
Verizon Wireless and Vodafone to
agree on common core requirements
Submit requirements to
key infrastructure suppliers to derive
solutions
Work with suppliers to come up with a single
solution
Drive the common core solution through the
standards bodies
One core network
Ubiquity
Transparent services