Embed Size (px)
Citation preview
Feb. 21, 2002. HSN2002 2
ContentsIntroduction
IP Transport RAN
Open RAN
IP-based RAN
TelCo’s IP-based RAN Architecture
Technical Study
Conclusion
Feb. 21, 2002. HSN2002 3
IntroductionWhat is IP-based RAN?
Main Benefits of IP TransportRe-use of potentially available IP transport infrastructure (e.g. in corporate environments and/or hot spots)
IP as universal transport technology throughout the whole mobilenetwork will bring benefits:
sharing of infrastructuresimilar network management skills for transport functions
IP TransportOpen Architecture based on
Internet Paradigms
Feb. 21, 2002. HSN2002 4
IntroductionIP-based RAN Concepts
Flexible and independent scaling of different network functions
Adoption of existing or new IETF protocols to enhance the flexibility, robustness and functionality of the RAN
Potential basis for the support of IP-based network applications and services within the RAN
Decisive step towards the long term 3GPP All-IP vision
Feb. 21, 2002. HSN2002 5
IntroductionIP RAN Evolution
RNC
RRM
IubIub
Iu
Point-to-point ATM Concentration
Current
R99/R4
IP Routing IP Transport Point-to-point Node B Link
IP transport RAN
R5/R6?
IP Transport Network
Iub Iub
Node B Re-parenting RNC Distributed RRM
IP RAN
R?
IP Network
Iu
Iub Iub
Aggregation
Node B
RNC: Radio Network Controller RRM: Radio Resource Management
Node B
RNCRRM
Iu
RNCRRM
Iu
CallServer
O&M
RRM
VocoderPool
LocationServer
Node B
Node B
3G 3.5G 4G
All IP Network
Feb. 21, 2002. HSN2002 6
IP Transport in UTRAN: 3GPPIP Transport Requirements
Use already standardized protocols, e.g. IETF protocols for IP related partsRNL shall be independent of the TNL
Impact on the RNL shall be minimized but there could be some minor changes to the RNL, e.g. addressing
Support coexistence of the ATM-based and IP-based transport options:Where a UTRAN node does not support both ATM interfaces (R99 and later releases) and IP interfaces, an TNL interworking function is required
Provide QoS:TNL shall provide appropriate QoS requested by the RNLMechanisms that provide QoS must take into account both UTRAN traffic(control plane, user plane, and O&M) and non-UTRAN traffic
Provide utilization of transport resourcesIub/Iur protocols shall operate efficiently on low speed point to point links
Provide Layer 1/ Layer 2 independenceLayer 1 and Layer 2 shall be capable to fullfill the QoS requirements set by the higher layers
Feb. 21, 2002. HSN2002 7
IP Transport in UTRAN: 3GPPIP Transport Requirements (cont’d)
Provide IP transport flexibility:No preference to routed vs point-to-point networks
Use individual flows addressingSupport identification of UTRAN nodes by one or several IP addressSupport requirements on signaling bearers
Feb. 21, 2002. HSN2002 8
IP Transport in UTRAN: 3GPPUser Plane Proposed Solutions
Composite IP(CIP) SolutionMultiple CIP packets of variable size in one CIP container for an efficient use of the bandwidth of the linksSegmentation/re-assembly mechanism
IPHeader
UDPHeader
CIP Packet Payload CIP Packet Payload CIP Packet Payload
FP PDU Segment FP PDU Segment FP PDU Segment
FP PDU
FP PDU is segmented in 3 packets
CIPPacketHeader
CIPPacketPayload
CIPPacketHeader
CIPPacketPayload
CIPPacketHeader
CIPPacketPayload
Feb. 21, 2002. HSN2002 9
IP Transport in UTRAN: 3GPPUser Plane Proposed Solutions (cont’d)
Lightweight IP Encapsulation(LIPE) SolutionUDP/IP or IP as transport layerEncapsulated payload of a variable number of multimedia data packet(MDP) and multiplexing header(MH)LIPE UDP/IP or IP encapsulation format
IP(20)
MH: Multiplexed Header, MDP: Multiplexed Data Payload
UDP(8)
MH1(1-3) MDP1 MH2
(1-3) MDP2 MH3(1-3) MDP3
IP(20)
TID(1)
MH1(1-3) MDP1 MH2
(1-3) MDP2 MH3(1-3) MDP3
TID: Tunnel Identifier
PPP/HDLC Framing
Feb. 21, 2002. HSN2002 10
IP Transport in UTRAN: 3GPPUser Plane Proposed Solutions (cont’d)
PPP-mux based SolutionMethod to reduce the PPP framing overhead used to transport small packets, e.g. voice frames, over slow linksMultiple PPP encapsulated packets in a single PPP framePPP multiplexed frame options
over ATM/AAL5over L2TP(TCRTP)
PPP-mux frame with multiple subframes
Length1
HDLCHdr(1)
PPPmuxID
(0x59)
PPP Header(2)
PFF LXT
(1-2)
PPP Prot.Field1(0-2)
cUDP1(2) Payload1
Information1
LengthNPFF LXT
(1-2)
PPP Prot.FieldN(0-2)
cUDPN(2) PayloadN
InformationN
CRC(2)
Feb. 21, 2002. HSN2002 11
IP Transport in UTRAN: 3GPPUser Plane Proposed Solutions (cont’d)
MPLS SolutionMethod of forwarding IP packets, while reusing the existing IP routing protocols, e.g. OSPF, BGPAdvantages of routing with MPLS
Coexistence with IP hop-by-hop routingTraffic engineering capabilitiesFlexibility due to label semantics and stackingTransparent and fast routing
IP/MPLSNetwork RNC
Payload Frame
IP
UDP
MPLS
Payload Frame
IP
UDP
Payload Frame
IP
UDP
MPLS
Payload Frame
IP
UDP
Class of Service 1 LSP *:may also be compressed depending on
Class of Service 2 LSP the compression technique used. (see2.6)
Class of Service 3 LSP
Narrow-bandLink
Compress/Decomp.
Node
Node B
Payload Frame
cUDP/IP
MPLS*
Payload Frame
cUDP/IP
MPLS*
Feb. 21, 2002. HSN2002 12
IP Transport in UTRAN: 3GPPQuality of Service
QoS MechanismsAt IP layer, Diffserv, RSVP or over-provisioning considered
UTRAN Hop-by-Hop QoS ApproachQoS differentiation in the IP backboneSome problems
Definition to inform the edge router about the needed quality classesEdge router functionality that the standard design relies onInterworking of PPP-mux with MC-PPP
UTRAN End-to-End QoS ApproachQoS differentiation for the UTRAN traffic flows inside UTRAn NEs
Composit IP, LIPETunneling PPP protocol via L2TP(TCRTP)
PPP-mux
Feb. 21, 2002. HSN2002 13
IP Transport in UTRAN: 3GPPTransport Network Bandwidth Utilization
MultiplexingReducing the impact of the size of the UDP/IP headers in a packetMultiplexing location: application level, transport levelTransport level multiplexing
End-to-end multiplexing transparent to intermediate transport nodesLast Mile multiplexing terminated in Edge routerLast Mile multiplexing + Routed network multiplexing
Resource ManagementFunctions to be considered
Admission controlPolicingReservation of resources
Methods of resource allocationOver-provisioningAllocation of aggregates of flowsAllocation per flowCentralized or distributed admission controlSignaling(e.g. RSVP) for distributed admission control
Feb. 21, 2002. HSN2002 14
IP Transport in UTRAN: 3GPPTransport Network Bandwidth Utilization (cont’d)
Header CompressionStandard compression techniques
Compression with differential coding: re-synchronization problemCompression without differential coding: quick recovery from out of synchronization
IP Header Compression(RFC2507): for PDCP(3GPP TS25.323)Compressing IP/UDP/RTP Headers for Low-Speed Serial Links(RFC2508)
Feb. 21, 2002. HSN2002 15
IP Transport in UTRAN: 3GPPUser Plane Transport Signaling
Solution without Access Link Control Application Protocol(ALCAP)Establishment/maintenance/release of user plane transport bearers with TNL signaling protocolTransport bearer termination points: related RANAP message
Transport layer address IE: IP address to be used for user plane transportIu transport association IE: GTP tunnel endpoint identifier
LIPE Solution
IP Cloud
RNC Point to Point Link RNC/Node B
LIPE Tunnel
RNC RNC/Node B
LIPE Tunnel
RNLTermination
TNLTermination
RNLTermination
TNLTermination
RNL Protocol
TNLSwitching
TNL Protocol(ALCAP)
TNL Protocol(ALCAP)
Feb. 21, 2002. HSN2002 16
IP Transport in UTRAN: 3GPPLayer 1 and Layer 2 Independence
Layer 1 and Layer 2 in QoS and/or in transport resource efficiencyLayer 2 Options
ConsiderationsQoS differentiation (queuing scheme, segmentation and scheduling functionality, ..)Efficiency
L2 not standardizedProvide the most freedom for the operators to build their transport network
L2 standardizedRestrict flexibility for operatorsIn UTRAn NEs, PPP protocol with its extensions PPP-mux, Multi-Link(ML)/Multi-Class(MC)-PPP
Feb. 21, 2002. HSN2002 17
IP Transport in UTRAN: 3GPPRadio Network Signaling Bearer
Iub RNL Signaling BearerIub signaling bearer protocol stack
RNS SignalingSS7 SCCP-User Adaptation Layer(SUA) protocolSUA/SCTP/IP over ATM AAL5(or HDLC-PPP, etc)
NBAP
SCTP
IP
Layer 2
Layer 1
NBAP
SCTP
IP
Layer 2
Layer 1
AdaptationSSCF
SCTP
without Adaptation Layer with Adaptation Layer
Iub Iub
Feb. 21, 2002. HSN2002 18
IP Transport in UTRAN: 3GPPRadio Network Signaling Bearer (cont’d)
RANAP SignalingUse of SCTP to minimize the changes on UTRAN RNL and to reduce the number of different variants of any application signaling protocolRNL signaling bearers on Iu interface: illustration
NBAP
SCTP
IP
Layer 2
Layer 1
Adaptation
Radio NetworkLayer
TransportLayer
Iu
Feb. 21, 2002. HSN2002 19
IP Transport in UTRAN: 3GPPRadio Network Signaling Bearer (cont’d)
SCCP/M3UA versus SUAComparison of SUA with SCCP/M3U: Benefits
With M3UA, the signaling point is required to support different flavours of SCCP if it has to inter-operate with different national systemsOne less protocol layer with elimination of SCCPSUA allows the IP network to route the messagesSUA allows the messages routing using Global Titles without involvement of point codes in IP-IP caseSUA provides much better scalability and flexibility for signaling network implementation in all IP network compared to the SCCP/M3UA optionThe powerful end-to-end addressing and routing capability od SUA can greatly reduce the signaling transfer latencyThe M3UA nodes need to be addressed by point codes at M3UA layer and by IP addresses at IP layerThere are some function redundancies in SCCP/M3UA/SCTP stack modeThe capabilities of SUA make SCCP and M3UA unnecessary and SUA can be considered preferable in terms of efficiency and implementation complexity
Comparison of SUA with SCCP/M3U: DrawbacksSUA doesn’t support MTP-3 user protocols such as ISUP ans BICCInterworking between SUA and SCCP/M3UA is introducedIn use of common principles, M3UA would be similar to MTP3 network
Feb. 21, 2002. HSN2002 20
IP Transport in UTRAN: 3GPPRadio Network Signaling Bearer (cont’d)
SCCP/M3UA versus SUA (cont’d)Comparison of SCCP/M3U with SUA: Advantages
The M3UA takes care of other MTP-3 user than SCCP like ISUP, BICC and H.248No special interworking functions are required for interworking with Rel4Addition of a new protocol will impose additional cost of training, testing, new equipment(protocol analyzer) and signaling gateway functionalityThe introduction od SUA as an alternative to M3UA+SCCP will introduce options in implementations, which will sooner or later lead to increased costThe introduction of SUA as an alternative to M3UA+SCCP will introduce options in the networks, and between networksThe operators can apply similar principles for network planning, network management and network operation as for the MTP networkFor the case of a smooth transition towards an IP network the SCCP+M3UA solution reuses the complex SCCP functionality and to rebuild this functionality can only increase development costs and lead to interworking problemsThe operator can reuse the GT analysis already provided by data builds in SCCP, which is proven to work in existing networks
Feb. 21, 2002. HSN2002 21
IP Transport in UTRAN: 3GPPRadio Network Signaling Bearer (cont’d)
Interworking of SCCP/M3UA and SUAInterconnecting operator networks with SUA
Network
IPSP
IPSP
IPSP
IPSP
Network
Signaling Point 1
Signaling Point 2
Signaling Point N
Signaling Point 1
Signaling Point 2
Signaling Point N
SUARelay
SUARelay
SUARelay
SUARelay
IPSP
IPSP
NetworkNetwork
SCTPassociations
SCTPassociations
SCTPassociations
Feb. 21, 2002. HSN2002 22
IP Transport in UTRAN: 3GPPIP Transport and Routing Architecture
IP Transport Network Architecture: Example
IP Network of Routers
EdgeRouter
EdgeRouter
RNC
RNC
Node B
EdgeRouter
Node B
Node B
Node B
EdgeRouter
Feb. 21, 2002. HSN2002 23
IP Transport in UTRAN: 3GPPBackward Compatibility with R99/Coexistence with ATM Nodes
Interworking Cases
Interworking Unit(IWU) in Transport Network Layer
RNCIP
RNCATM
RNCATM
Node BATM
Node BIP
RNCIP
IWU
IWU IWU
RNL
TNL
RNL
TNL
IWU
ATM IP
ATM based IP based
Feb. 21, 2002. HSN2002 24
IP Transport in UTRAN: 3GPPBackward Compatibility with R99/Coexistence with ATM Nodes
Transport Network Control Plane Interworking
L1
L2
IP
SCTP
Q.2150.3
IP ALCAP
L1
L2
IP
SCTP
Q.2150.3
IP ALCAP
L1
ATM
AAL5
SSCOP
MTP-3b
SSCF
Q.2150.1
L1
ATM
AAL5
SSCOP
Q.2150.1
SSCF
Q.2630.1
IPATM/AAL2
IP-based RNCIWUATM-based RNC
MTP-3b
Feb. 21, 2002. HSN2002 25
IP Transport in UTRAN: 3GPPBackward Compatibility with R99/Coexistence with ATM Nodes
Interworking between External Dual Stack RNC and Rel4/R99 RNC
RNSAP
L1
L2
IP
SCTP
SUA
L1
ATM
AAL5
SSCOP
MTP-3b
SSCF-NNI
SCCP
L1
ATM
AAL5
SSCOP
SCCP
SSCF-NNI
RNSAP
IPATM
R4 RNCSignaling GatewayR99 RNC
MTP-3b
L1
L2
IP
SCTP
SUA
External Dual Stack R4/R99 RNC
Feb. 21, 2002. HSN2002 26
IP Transport in UTRAN: 3GPPSecurity
IPSec ArchitectureProtocol providing authentication and integrity protection in two architectures:
End-to-end security provisioning between hostsGateway to gateway
Host to host securityTransport mode: integrity and authentication cover only transport protocol(above IP) and higher protocolsTunnel mode: IP header is protected
SCTP Security FeaturesIncorporate a cookie exchange mechanism at association establishmentDesigned to prevent unauthorized connections to be set up at transport level
Feb. 21, 2002. HSN2002 27
IP Transport in UTRAN: 3GPPIu-CS/Iu-PS Harmonization
GTP-U for Iu User PlaneIu-PS domain
GTP-U header size: 8 octets, 12 octetsGTP’s header size: 6 octetsGTP-U header whould be defined that is optimized for real-time applications
Iu-CS domainGTP-U for Iu-CS interface over IP transportRTP as alternative to GTP-U
RTP for Iu-CS InterfaceRTP/UDP/IP based Iu-CS user data transportRTP selected
used in the 3GPP circuit-switched core network for Nb interfacehas capability that is needed for real-time services over Iu-CS interfaceIETF protocolBandwidth utilization
Feb. 21, 2002. HSN2002 28
OpenRAN: MWIFArchitectural Characteristics and Conceptual Model
Open Flexible Distributed Scalable Core Network
Routed Cloud Routed Cloud
Radio FrameRouted Cloud
Radio FrameRouted Cloud
Radio Controller
Radio Layer 1
Cell Bearer GW
Access GW
1 2 3
4 5 6
7 8 9
* 0 #
Feb. 21, 2002. HSN2002 29
OpenRAN: MWIFArchitectural Requirements
Support the current 2G and 3G radio technologies Provide at least equivalent functionality to existing RAN architectureTransport bearer and control traffic based on IP technologyUse IETF protocols wherever applicableSupport IPv6 as well as IPv4Consist of separated control and bearer functionSupport distributed control and bearer functionSupport distribution of cell dependent and UE control and bearer functionSupport QoSs such as
multiple transport and radio QoS levels, including in handoff scenariosapplication QoS in the RAN and over the airmultiple levels of static QoS as well as dynamic QoS
Allow optimized use of different wireless access technologiesSupport necessary functions to ensure that the necessary availability and reliability can be achievedSupport deployment within LAN, MAN, WAN environment
Feb. 21, 2002. HSN2002 30
OpenRAN: MWIFArchitectural Requirements (cont’d)
Use IETF-based standard network management protocolsInteroperate with the MWIF core network architectureSupport AAA
to handle multiple radio channel authentiation protocols to be present in the RAN or provided by core network functions
Feb. 21, 2002. HSN2002 31
OpenRAN: MWIFOperator Requirements
Support open interfaces between any network entities in the OpenRANSupport interoperability with legacy(2G/3G CN and AN) networksSupport network deployment in public as well as in enterprise/corporate environmentsProvide network operators the ability to expand specific RAN functional entities independently of other entitiesProvide functions to protect its network resources and traffic from unauthorized control accessProvide Plug and Play
to make easy and reliable equipment installation without specific technical knowledge, reducing the cost for installationto make easy deployment of a distributed network systemto make easy and hot exchange of the network equipment when it is broken or version incremented
Provide the ability to integrate with legacy RAN and core network infrastructure to allow a smooth migration
Feb. 21, 2002. HSN2002 32
OpenRAN: MWIFHandoff Requirements
Provide equivalent handoff mechanisms that equal or exceed current cellular performance, and work for both voice and dataAllow handoff between different radio access technologies on a single RAN for load balancing purposesMeets QoS requirements (e.g. low latency)Minimize transport data loss within the constraints of the mediumSupport inter-RAN handoff by working together with core network mobility management
Feb. 21, 2002. HSN2002 33
OpenRAN: MWIFNetwork Architecture
Flat, distributedarchitecture
User Plane related Entity Control Plane related Entity
A-GW A-GW
MT UE UE MS
BTS
CN = IP Multimedia Subsystem
GSM
RAN = Pure IP Network
Macro Mobility
AP Node B Node B BSC+α
Micro Mobility
WirelessLAN
OAM&P
AccountServer
NRM
IP-addr.Mngr.
Authen.Server
PolicyServer
RRM
NameServer
AuthorServer
ProfileServer
Other service relating servers: MediaGateway, etc.
Flat, distributedarchitecture
Wireless Tech.Indepemdent IF
Access NW IF
Wireless-Wired IF
IFs for C-planeEntities
A-GW : Access GatewayNRM : Network Resource ManagementRRM : Radio Resource Management
DistributedControlSevers
Feb. 21, 2002. HSN2002 34
OpenRAN: MWIFMapping to the UTRAN Architecture
CommonRRM Func
PagingBroadcast
MobileControl
CellController
Cell BearerGateway User Radio
Gateway
UE Geo-location
Radio L1
RNCCRNC/RNC SRNC
Node B
Iups-C
Iups-UIur-UIub-UIub-U
Iur-CIub-C
Iub-C
Iur-C
Iur-C
New reference point in MWIFExisting 3GPP reference point
Bea
rer P
lane
Con
trol
Pla
ne
Feb. 21, 2002. HSN2002 35
OpenRAN: MWIFMapping to 3GPP2 IOSv4.1 RAN(cdma2000 RAN) Architecture
CommonRRM Func Paging
BroadcastMobileControl
CellController
Cell BearerGateway User Radio
Gateway
UE Geo-location
Radio L1
BSCTarget BSC Source BSC
BTS
A11
Iups-UA3_UAbis_traffic
Abis_sig
Abis_sig
A3_s
A7
New reference point in MWIFExisting 3GPP2 reference point
Bea
rer P
lane
Con
trol
Pla
ne
Feb. 21, 2002. HSN2002 36
IP-based RANRequirements
Support of GERAN and UTRAN radio technologies, hooks for possible other radio technologiesOpen multivendor RAN architecture and interfacesOptimized utilization of the radio interface resources
Optimized location of operational and radio functions to maximize performanceCo-ordinated management of multi-radio environments
Optimized utilization of transmission resources especially on the last mileDistributed architecture enabling maximum modularity and scalabilityNeed to be able to add new transport options without affecting the radio network layer, and the ability to adapt the radio network layer without affecting the transportEvolution of the RAN architecture shall re-use current interface standards and interface principles
3GPP UTRAN interface protocolsIETF protocols when applicable
Feb. 21, 2002. HSN2002 37
IP-based RANRequirements (cont’d)
Transport based on IP layer serviceslayer 1 / layer 2 independence, provided that IP layer service level is achievedQuality of Service, mechanisms to support traffic engineering and bandwidth management
IP transport solution based on the UTRAN Rel.4 IP transport, where applicableSupport of location based servicesNetwork security and user access security must be guaranteedInteroperability with legacy(2G/3G) networks and mobile terminalsEvolution path from existing radio systems towards IP-based RAN
Feb. 21, 2002. HSN2002 38
IP-based RANPrinciples of IP-based RAN
Separation of Different Network Functions:User plane functionControl plane functionTransport plane function
Flexible Distributed Architecture which allows for:Flexible deploymentLoad sharingRedundancy concepts
Use of IP Transport
Re-use of IETF Protocolse.g. RAN-internal mobility management based on Mobile IP mechanisms
Feb. 21, 2002. HSN2002 39
IP-based RAN3GPP IP-based Mobile Comm. Networks with Legacy RAN
iRNS (IP UTRAN)
RNS (UTRAN)
Internet
MRF MGCF
MGW
T-SGW
PGW
SGSN
EIR
MSC/VLR
PSTNNetwork
PSTNNetwork
SGSN HSS AuCHLR
CSCF
GGSN
MSC/GMSCserver
SCP
Managed IPCore Network(QoS, COS)
Iu-CS
E
F
D H
Gr Gc D/C
CAP
CAP
Gf
Iu-PS
iIu-PS
Gn
Gi GiGi
iIu-CS(RANAP)
iIu(RTP)
Mc
MrMg
Mm
ISUP/IP
ISUP/IP
Mc
1 2 34 5 6
7 8 9* 0 #
1 2 34 5 6
7 8 9* 0 #
Uu
Uu
Uu
1 2 34 5 67 8 9* 0 #
Uu
Iur
RNC
RNCIub
Node B
Iub
Node B
iIur
iRNC
iRNCiIub
iIub
iNode B
iNode B
RAN CNUE
Feb. 21, 2002. HSN2002 40
Telco’s IP-based RAN ArchitectureNokia’s IP-based RAN Architecture
Control Plane
IPv6 basedMobility Interface
GW
InterfaceGW
User & GW Plane
SignalingControl
Common RadioResource Management
Radio AccessServer
CRRMServer
O&MServer
Multi-StandardBase Stations- GSM/EDGE- TDMA/EDGE- WCDMA- 1XTREME- WLAN IPv6 Core
GbA, Iu-CSIOS(IS-41)
Iu-PS
Feb. 21, 2002. HSN2002 41
Telco’s IP-based RAN ArchitectureSimens’ IP-based RAN Architecture
Core NetworksTransport Plane
User Plane
Control Plane
CN with Rel'99 Iu
Rel'99 RNS
Radio Network ControlPlane Functions
Radio Network ControlInterworking Functions
IP TransportFunctions
Radio NetworkUser Plane Functions
Radio L1Functions
Feb. 21, 2002. HSN2002 42
Telco’s IP-based RAN ArchitectureAlcatel’s IP-based RAN Architecture
IP Network
Cell-scaledControl
Functions
TNL
TNLTNL
Node BNode B
Node B
TNL
UE-scaledControl
FunctionsGateway to CN
Core Network- Gateway to Core Network- Mobility anchor point- Dedicated channels: Ciphering, RLC, MAC-d, DHO- Shared channels: Ciphering, RLC, MAC-d
- Traffic concentration
- Shared channels cell scheduling
UE control
Cell control
Feb. 21, 2002. HSN2002 43
Technical StudyIP Transport RAN Protocol Stack: example 1
ATM
AAL2IP
UDPFP
NBAPAPP
AAL2IP
UDPFP
AAL5IP
SCTP
ATM ATM
NBAP
AAL5IP
SCTP
UP(CS)
AAL2IP
UDPMACRLC
PDCP
RRC
BMC
ATM
AAL5IP
TCP
SABP
AAL5IP
SCTPM3UA
SCCP
AAL5IP
UDPGTP-U
UP(PS) RANAP RNSAPAPP
iIub Iu-CS(CP) Iu-CS(UP) Iu-PS
IP-based Node B IP-based RNC
W-CDMA
Iub-GW
ATM
AAL5SSCOP
SSCF-UNI
ATMATM
AAL5IP
SCTP
NBAP Relay
AAL2
FP
UP Relay
Q.2150.1Q.2630.1
iIubiub iIur
Iur-GW
ATM
AAL5SSCOP
SSCF-UNI
ATM
AAL5IP
SCTPMTP-3b
SCCPM3UASCCP
RNSAP Relay
Q.2150.1Q.2630.1
ATM
AAL5IP
UDPGTP-U
ATM
AAL2
FP
UP Relay
Traffic &Signaling
Traffic
Signaling
iub iuriur
Feb. 21, 2002. HSN2002 44
Technical StudyIP Transport RAN Protocol Stack: example 1a
MGW(CN-CS)
ATM ATM
AAL5IP
UDPGTP-U RTP/RTCP
AAL5IP
UDP
H.248/ MEGACO
UPAPP
Iur-GW
ATMATM ATM ATM
AAL5IP
SCTPM3UASCCP
AAL5IP
UDPGTP-U
AAL2
UP Relay
AAL5SSCOPSSCF-NNIMTP-3b
SCCP
RNSAP Relay
Q.2150.1Q.2630.1
Iub-GW
ATM ATM
AAL5IP
AAL5SSCOP
SSCF-UNI SCTP
NBAP Relay
Q.2150.1Q.2630.1
ATM ATM
AAL2AAL2 IP
UDPFPFP
UP Relay
H.J.Park
ATMATM
iRNC
AAL5IP
TCP
AAL5IP
SCTP
NBAP
AAL2IP
UDPFP
MACRLC
PDCP BMC
RRC
SABP
AAL5IP
UDPGTP-U
UP(CS) UP(PS)
AAL5IP
SCTPM3UA
SCCP
RANAP RNSAPAPP
Uu
(Radio) iIub
iIur
iIu-PS
Iu-BC
iIubIub
IuriIur iIu-CS(UP)
iIu-CS(CP)
TrafficSignaling
Traffic/Signaling
STM-1
E1/STM-1
E1/STM-1 E1/STM-1
STM-1 STM-1
STM-1 STM-1
STM-1
STM-1 STM-1
WCDMA
MACRLC
UE
PDCP BMCPPPIP
IP
SIP/MIP/RTP/RTCP/RSVP
APP
RRC
MM/SM/CC
ATM
AAL5IP
SCTP
iRTS
AAL2IP
UDPFP
WCDMA
NBAPAPP
other iRNC
ATM
AAL5IP
SCTPM3UA
SCCP
RNSAP RANAP
AAL5IP
UDPGTP-U
UPAPP
CBC
ATM
AAL5IP
TCP
SABP
APP
ATM
AAL5
R99 RTS
AAL2
FP
SSCOPSSCF-UNI
Q.2150.1Q.2630.1
NBAPAPP
R99 RNC
ATM
AAL2 AAL5AAL5AAL5IP IP SSCOP
TCP UDPGTP-U
SSCF-NNIMTP-3b
SCCPSABP
Q.2150.1Q.2630.1
RANAP RNSAPUP(CS) UP(PS)APP
iSGSN(CN-PS)
ATM
AAL5AAL5IP
SCTPM3UASCCP
IPUDP
GTP-U
RANAP UPAPP (MM/SM/CC)
ATM
iGGSN(CN-PS)
ATM
AAL5AAL5IP
UDPGTP-U
PPPIP
IP
IP
UP (Routing)
APP
STM-1Gn
Gi
Mc
from/to MultimediaIP Networks
iMSC(CN-CS)
ATM
AAL5IP
UDP
H.248/ MEGACO
AAL5IP
SCTPM3UA
SCCP
RANAPAPP
Feb. 21, 2002. HSN2002 45
Technical StudyIP Transport Mobile Comm. Network Protocol Stack: example 2
(Radio)
iSGSN(CN-PS)
MAP CAP
ATMATM
IPSCTP
AAL5
M3UASCCPTCAP
ATM
IPSCTP
AAL5
M3UASCCPTCAP
APP
IPUDP
AAL5
GTP-C
APP
SCCP
RANAP
IPSCTPM3UA
AAL5
UP
IPUDP
AAL5
GTP-U
iIu-PSGnWINGrGf
APP
ATM
IPSCTP
AAL5
SCCP
EIR
M3UA
TCAP
MAP
Gf
iGGSN(CN-PS)
IPUDP
GTP-C
AAL5
PPPIP
IP
ATM
IPUDP
AAL5
GTP-U
ATM
IP
AAL5
UP (Routing)
APP
ATM
MAP
IPSCTP
AAL5
M3UASCCPTCAP
GiGnGc Gc
HSS(CN)
MAP
ATM
IPSCTP
AAL5
Diameter
CAPAPP(DB)
ATM
IPSCTP
AAL5
M3UASCCPTCAP
ATM
IPSCTP
AAL5
M3UASCCPTCAP
CxGr WIND
CSCF(CN-IM)
ATM
IPSCTP
AAL5
Diameter
ATM
IPTCP
AAL5
SIP mSIP
APP
CxMrGi Mg
MRF(CN-IM)
ATM
RSVPRTP /RTCP
IPUDP
UP
ATM
IPTCP
AAL5AAL5
mSIP
APP
GiMr
MGCF(CN-IM)
ATM
IPTCP
AAL5
SIP
ATM
IPUDP
AAL5
ATM
IPSCTP
AAL5
M3UAH.248/ MEGACO
ISUP
APP
McMg 3
T-SGW(CN-IM)
ATM
IPSCTP
AAL5
M3UA
PCM
TimeSlot
MTP-3MTP-2
ISUP Relay
SS No.73
APP
ATM
IPTCP
AAL5
SABP
CBC
1
PDCP BMC
RRC
MM/SM/CC
PPPIP
IP
SIP/MIP/RTP/RTCP/RSVP
RLCMAC
WCDMA
iUE
Uu
APP
Nc
RTP /RTCP
MGW(CN-IM)
PCM
TimeSlot
ATM
IPUDP
H.248/ MEGACO
AAL5
APP
Nb Mc2
ATM
IPUDP
AAL5
RSVP
UP
GTP-U RTP /RTCP
APP
ATM
IPUDP
H.248/ MEGACO
MGW(CN-CS)
AAL5
NbiIu-CS(UP) Mc
RSVP
ATM
IPUDP
AAL5
UP
iUE iUTRAN
EIR
iSGSN(CN-PS)
MGW(CN-CS) MGW(CN-IM)
iMSC(CN-CS)
MGCF(CN-IM)iGGSN(CN-PS)
CSCF(CN-IM)
MRF(CN-IM)
Uu
D
Cx
Gn
Gf
NbiIu-CS(UP)
iIu-PS
iIu-CS(CP)
Mc
Gi
Mr
Gi
Gi
Multimedia IP NetworksMm
Mg
Gi
Mc
Gr
HSS(CN)
PSTN/Legacy/External
iGMSC(CN-CS) T-SGW(CN-IM)
CBC
1
2
3
App's & Services(inc. SCP)
C
Gc
CAP
CAPMc
ATM
H.J.Park
BMC
iUTRAN
WCDMA ATMATM
PDCP
SCCP
NBAPRTS APP
NBAP
RRC
UP(CS) RANAP RNSAPRNC APP
UP(PS)
RLCMACFP
UDPIP
AAL2IP
TCP
AAL5
SABP
IPUDP
GTP-U
AAL5IP
SCTPM3UA
AAL5IP
UDPFP
AAL2
SCTPIP
AAL5
SCTPIP
AAL5
Uu iIub iIu-PS 1 iIu-CS(UP) iIu-CS(CP)
ATM
IPUDP
H.248/ MEGACO
iMSC(CN-CS)
AAL5
SCCP
RANAP
IPSCTPM3UA
AAL5
ATM
MAP CAPAPP
ATM
IPSCTP
AAL5
M3UASCCPTCAP
ATM
IPSCTP
AAL5
M3UASCCPTCAP
Mc iIu-CS(CP) D WIN
Feb. 21, 2002. HSN2002 46
Technical StudyHandover Scheme in IP Transport RAN: example
Procedures to reduce the inter-RNS handover delayHard handover procedure
GGSNUE SGSN2/ MSC
SGSN1/ MSCTRNCSRNCTNode BSNode B
1. Relocation Required2. Forward Relocation Request
3. Relocation Request
4. GTP tunnel setupbetween RNCs
(UDP Port# / IP Addr)5. Radio Link Setup Request6. Radio Link Setup Response
7. Iub data transport bearer setup(UDP Port# / IP Addr)
8. Handover Command9. Forward Handover Command
10. Forward Handover Command11. Physical CH Reconfiguration(DCCH)12. Detection of UE13. Physical CH Reconfig. Complete(DCCH)
Stop DL transport and buffering, Data forwarding into TRNC
Start DL transport
Control Plane User Plane
TargetRNC
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
Feb. 21, 2002. HSN2002 47
Technical StudyHandover Scheme in IP Transport RAN: example (cont’d)
Procedures to reduce the inter-RNS handover delayHard handover procedure (cont’d)
GGSNUE SGSN2/ MSC
SGSN1/ MSCTRNCSRNCTNode BSNode B
14. SRNC Anchored
15. from Active Mode to Dormant Mode
16. Relocation Detect
18. Relocation Complete
19. Forward Relocation Complete
20. Release Related Links
Hard Handover Complete / UL and DL Transmission(Active Mode)
17. Update PDP Context Request
17. Update PDP Context Response
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Uplink Traffic
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSNN-PDUs
N-PDUs
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSNN-PDUs
N-PDUs
UE
Control Plane User Plane
Feb. 21, 2002. HSN2002 48
Technical StudyHandover Scheme in IP Transport RAN: example (cont’d)
Procedures to reduce the inter-RNS handover delaySoft handover procedure
GGSNUE SGSN2/ MSC
SGSN1/ MSCTRNCSRNCTNode BSNode B
1. Relocation Required2. Forward Relocation Request
3. Relocation Request
4. GTP tunnel setupbetween RNCs
(UDP Port# / IP Addr)
6. Radio Link Setup Request7. Radio Link Setup Response
9. Iub data transport bearer setup(UDP Port# / IP Addr)
10. Handover Command11. Forward Handover Command
12. Forward Handover Command13. DL Synchronization(DCH-FP)
Control Plane
5. New Radio Link Setup Request
8. New Radio Link Setup Response
14. UL Synchronization(DCH-FP)
Start UL datareceiving
Start DL data transmitting
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
UL Sel.
DL Sel.
User Plane
TargetRNC
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
Feb. 21, 2002. HSN2002 49
Technical StudyHandover Scheme in IP Transport RAN: example (cont’d)
Procedures to reduce the inter-RNS handover delaySoft handover procedure (cont’d)
GGSNUE SGSN2/ MSC
SGSN1/ MSCTRNCSRNCTNode BSNode B
15. SRNC Anchored
Dormant Mode
18. Relocation Detect
20. Relocation Complete
21. Forward Relocation Complete
22. Release Related Links
Active Mode
19. Update PDP Context Request
19. Update PDP Context Response
Control Plane User Plane
16. Active Setup Update(DCCH)
17. Active Setup Update(DCCH) Complete
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSN
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Downlink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSNN-PDUs
N-PDUs
UE
TargetRNC
N-PDUsGTP tunnel
SourceRNC
Uplink Traffic
N-PDUs
SGSN1
N-PDUs
SGSN1
GGSNN-PDUs
N-PDUs
UE
Feb. 21, 2002. HSN2002 50
ConclusionThere are many technical problems to be solved for RAN evolution
IP Transport in UTRAN seems to be applied to 3.5G mobile comm. systems in Korea
Open RAN(or Virtual RAN) seems to be an influential solution of 4G mobile comm. systems
Feb. 21, 2002. HSN2002 51
References
3GPP TSG RAN TR 25.933, “IP Transport in UTRAN Work Task Technical Report”, V1.5.0, Dec. 2001.MWIF Technical Report MTR-007, “OpenRAN Architecture in 3rd
Generation Mobile Systems”, V1.0.0, Sep. 4, 2001.MWIF Technical Report MTR-006, “IP in the RAN as a Transport Option in 3rd Generation Mobile Systems”, V2.0.0, June 18, 2001.3GPP TSG RAN W010001, “IP based RAN Architecture”, Feb. 5-6, 2001.3GPP TSG RAN RPW010007, “UTRAN Evolution”, Ericsson, Feb. 2001.3GPP TSG RAN RPW010010. “Status of IP-Transport in UTRAN Work Item”, Alcatel, Feb. 2001.“IP-based UTRAN”, Nortel Networks’ White Paper, 2001.“IP-Radio Access Network”, Nokia’s White Paper, 2000.
