Ericsson’s way towards IP based Mobile & Multiservice Networks 3G Chaker SLIMI, Ericsson Tunisia “IP Applications and Digital Divide”, 17-19 June 2003 Together, let’s make it happen

AGENDA Introduction All-IP: Concept and challenges ATM versus IP Connectivity Multi-service aspects IP in today’s GSM/GPRS networks The different stages of IP in 3GPP networks Some Selected topics (QoS, IPv6, Signalling over IP )

Drivers for IP in Mobile Networks New Services and applications to generate new revenues IP based Mobile Multimedia services Common connectivity network to reduce cost multi-service backbone networks, based on one single network layer technology

IP for two purposes in mobile networks IP applications IPv4/6 Tunnel SDH PDH ATM IP connectivity Physical 3

Layered Architecture Application layer IP and telephony applications Call and session control Mobility management Switching and routing Data operations Application layer Control layer Connectivity layer 9

IP in all Core Network connectivity nodes Applications Mail server Video server Control HSS CSCF MSC server MGCF Telephony Network MGW MGW IP connectivity SGSN GGSN Internet/Intranet 11

Mobile Multimedia Services Evolution Use Case Mode Interactive Streaming Consumption WAP WAP-NG Messaging MMS SMS EMS e-mail Instant Messaging Communication Conversational IP-Based Conversational Multimedia (IMS) CS Conversational Multimedia (3G-324M) CS telephony Time

All-IP Definition All IP means that the mobile network architecture is IP enabled and that all traffic is transported across the whole network via an IP connectivity network. Primary Site Sec. Site Access Site R I Peering Networks Mgmt PSTN Cell Hub Site RNC

Efficiency over the air All-IP Challenges Telecom carrier class resilience availability high capacity redundancy End-to-End QoS Traffic separation Network Management Roaming Addressing: IPv6 and IPv4 Efficiency over the air

ATM Versus IP Connectivity

ATM versus IP Connectivity Future connectivity is IP ATM characteristics Offers short term advantages over IP Less effort put into future development Provides migration path to IP via MPLS Direct route to IP, or via ATM, depends on current network and time for deployment 15

Multi-service Aspects

Multi-service IP backbone Traffic from other access networks Gb Frame Relay 3G Voice over ATM 2G Voice over TDM Various types of traffic, with different security and QoS requirements, carried over one common IP/MPLS backbone Mobile Network traffic examples O&M traffic over X.25 Charging data over xx SS7 over TDM

All-IP for Mobile & Multi-access Networks Appl. Content Portals Service Mgm Service Enablers Service NW Infrastr. IP Multimedia Servers ISDN Servers -MSC server -GMSC server - TX/LE server -CSCF server -SIP/CATV server Support Servers Access Control Servers -Network mgm -Billing/Accounting -Customer care -RN servers PSTN ISP PLMN Etc Corporate BG Secure QoS/VPN/IPv6 enabled multiservices IP network GGSN MG SG MG MG WLAN hot spot LE ADSL GERAN Cable NW UTRAN 1

IP in today’s GSM/GPRS Networks

GRPS the first step to IP HLR MSC/VLR SMS GW-MSC Gr A Gs Gd SS - 7 BTS A’’ BSC SGSN GGSN PCU Corporate Gb Gn Gi BTS Multi-service IP network Gb Gn Gi BTS A’’ BSC GGSN ISP PCU Gp SGSN Other PLMNs BTS

GPRS Roaming HPLMN VPLMN BSS/RNC SGSN GGSN Host1 BSS/RNC SGSN BG HLR GRX Host1 VPLMN BG BSS/RNC SGSN

GSM over IP, example IP-BB TSC server TSC server MGW MGW BSS MSC/VLR BICC IP-BB ISUP H.248 A-if MGW MGW BSS MSC/VLR MSC/VLR BSS

The different stages of IP in 3GPP networks

3GPP Releases Time Schedule Versions of 3GPP Release 4 3GPP Release 1999 Versions of 3GPP Release 1999 The 3G/UMTS technical specification work, which was carried out in the organizational partners before, was during the beginning of 1999 transferred to 3GPP. Thus, all the 3G/UMTS technical specification work is now done in 3GPP instead of in the regional/national standardization bodies. The 3GPP Release 1999 was approved at the 3GPP TSGs # 6 in December 1999. The 3GPP Release 4 was approved at the 3GPP TSGs #11 meetings in March 2001. The plan is to approve 3GPP Release 5 in March 2002. The tentative plan is to have the 3GPP Release 6 ready in June 2003. 1999 2000 2001 2002 2003

3GPP R3 (R’99)

3GPP Release 1999 Architecture Overview Core Network GSM based evolution to UMTS - circuit switched evolution -packet switched (GPRS) evolution Evolved PLMN PSTN ISDN Internet IP GSM BTS GSM BSS Abis Gb A Um New Node B RNC Radio Network Controller Iub Iu UTRAN - UMTS Terrestrial Radio Access Network Iur Uu The UMTS terrestrial Radio Access Network is new functionality in 3GPP release 1999 and has the following interfaces: - Uu - radio interface. - Iub - between node B and the Radio Node Controller. - Iu - between the Radio Node Controller and the core network. - Iur - between the Radio Node Controllers. The GSM based core network has been evolved towards 3G/UMTS.

Core Network Architecture - CS domain HLR AuC MSC Server GMSC Server PSTN ISDN PLMN RNC MGw STM/TDM Based Transit Network MGw ATM Backbone SDH Network

Core Network Architecture - PS domain HLR AuC SGSN GGSN RNC IP network STM/TDM Based Transit Network ATM Backbone IP Backbone

3GPP R4

3GPP Release 4 Approved 13-22 March 2001 Call and bearer separation for the Circuit Switched domain (MSC Server - Media Gate Way) IP transport of core network protocols (CAP, MAP, BSSAP+) Transparent end-to-end packet switched streaming service (PSS) Header compression New Multimedia Messaging Service (MMS) Picture, sound, video etc. attachments Non real time ... 3GPP Release 4 was approved at the 3GPP Technical Specification Group meetings No 11, 13-22 March 2001. The complete set of specifications in 3GPP Release 4 is described in 3GPP Technical Specification 21.102. Example. Transparent end-to-end packet switched streaming service. The streaming platform supports a multitude of different applications including streaming of news at very low bitrates using still images and speech, music listening at various bitrates and qualities, video clips and watching live sports events. Codecs for speech (AMR), audio (MPEG-4), video (H.263), still images (JPEG together with JFIF), bitmap graphics (GIF), and text (XHTML) are specified. - 3GPP TS 26.233 Transparent end-to-end packet switched streaming service (PSS), General description. - 3GPP TS 26.234 Transparent end-to-end packet switched streaming services (PSS), Protocols and codecs.

Core Network Architecture - CS domain HLR AuC GMSC Server MSC Server STM/TDM Based Transit Network ATM Backbone PSTN ISDN PLMN MGw RNC MGw IP Backbone SDH Network

Core Network Architecture - PS domain HLR AuC SGSN GGSN RNC IP network STM/TDM Based Transit Network ATM Backbone IP Backbone

IP Backbone Interconnecting PSTN Mgm Primary Site Sec. Site Corporate Networks RNC RNC PSTN AXI AXI Sec. Site AXI Access Site (1) AXI AXI AXI AXI MGW AXI IP backbone core RNC AXI RNC IP backbone edge ATM Peering IP Networks ATM

CS Domain - User Plane Iu Nc Mc UTRAN PSTN MSC Server SGW MGW TSC Nb AAL2 AMR ATM PHY PCM RTP UDP IP LL

3GPP R5

3GPP Release 5 Planned content Addition of an IP Multimedia Subsystem (IMS) Session Initiation Protocol (SIP) control Combinational Services IP Version 6 IP transport in UTRAN (including Iu over IP) Home Subscriber System (HSS) Push services CAMEL Phase 4 ... The work is ongoing on the 3GPP Release 5 and the approval date is scheduled for March 2002.

All-IP - Interconnecting sites over the IP-backbone Mgm Primary Site Sec. Site Peering Networks PSTN AXI AXI Sec. Site AXI Access Site (1) AXI AXI AXI AXI RXI RNC Cell Hub Site RNC R R R R R RXI R R R R

IP Multimedia System (IMS) 3GPP R5 standard Reachability Presence Instant messaging Application/content sharing Whiteboard Data transfer

IP Multimedia Subsystem Service Network HSS IP Multimedia Subsystem CS Domain PS Domain GERAN UTRAN

HSS GERAN UTRAN OSA-SCS IMS-SSF SIP-AS MRFC MRFP S-CSCF P-CSCF I-CSCF GMSC Server I-CSCF MG SLF MGCF BGCF MSC Server MG SGSN GGSN MG BSC BS RNC BS GERAN UTRAN BS BS

Major IMS architectural principles Employs IETF protocols where possible IMS is IPv6 only (not IPv4 and IPv6) Network based subscriber services are provided by the home network “Non subscriber specific” services can be provided by the roamed to network and the home network.

3GPP R6

3GPP Release 6 Tentative IMS enhancements Conversational services (i.e. real time services) and interworking with PSTN and ISDN Multimedia Broadcast/Multicast Service (MBMS) UMTS/GPRS - WLAN Interworking … A number of Work Items have been initiated with scheduled ready date in the time frame of 3GPP Release 6, which is June 2003.

QoS Signaling over IP IPv6 Some selected topics QoS Signaling over IP IPv6

QoS

UMTS QoS Classes Conversational Class Streaming Class Delay sensitivity Interactive Class voice streaming video The main distinguishing factor between these QoS classes is how delay sensitive the traffic is. Conversational and Streaming classes are mainly intended to be used to carry real-time traffic flows. The main divider between them is how delay sensitive the traffic is. Conversational real-time services, like video telephony, are the most delay sensitive applications and those data streams should be carried in Conversational class. Interactive class and Background are mainly meant to be used by traditional Internet applications like WWW, Email, Telnet, FTP and News. Due to looser delay requirements, compare to conversational and streaming classes, both provide better error rate by means of channel coding and retransmission. The main difference between Interactive and Background class is that Interactive class is mainly used by interactive applications, e.g. interactive Email or interactive Web browsing, while Background class is meant for background traffic, e.g. background download of Emails or background file downloading. Responsiveness of the interactive applications is ensured by separating interactive and background applications. Traffic in the Interactive class has higher priority in scheduling than Background class traffic, so background applications use transmission resources only when interactive applications do not need them. This is very important in wireless environment where the bandwidth is low compared to fixed networks. Background Class Web browsing E-mail download QoS classes

3GPP Quality of Service Architecture UMTS TE MT UTRAN CN Iu CN TE EDGE Gateway NODE End-to-End Service TE/MT Local UMTS Bearer Service UMTS Bearer Service External Bearer Bearer Service conversational, streaming, interactive, background Service Radio Access Bearer Service CN Bearer conversational, streaming, interactive, background Service operator choice Radio Bearer Iu Bearer Backbone Service Service Bearer Service IP or ATM QoS IP or ATM QoS UTRA Physical FDD/TDD Bearer Service Service

Examples of UMTS services with mapping to RAB’s SMS Speech, AMR Emergency call Video H.324M Modem, V.90 Point-to-point TCP/IP Point-to- multi-point TCP/IP UMTS Services UTRAN Services Signalling Connection RAB RAB RAB RAB 12.2 kbps 64 kbps 57.6 kbps 384 kbps RAB Attributes Radio Access Bearer Classes Conversational Streaming Interactive Background

Streaming, Interactive, Background QoS in Packet Switched Domain (3GPP R4) UMTS Bearer QoS Core Network UE UTRAN SGSN GGSN TFT TFT Streaming, Interactive, Background External Network DiffServ DiffServ DiffServ Streaming, Interactive/Background LER LSR MPLS CoS ATM IP ATM/AAL5 IP IP RAB QoS physical link Diffserv QoS

Example of Mapping: UMTS Service Classes to DiffServ (PS domain) PS services make direct use of the four UMTS classes for traffic differentiation. Real time traffic Non real time traffic Conversational Streaming Interactive Background DiffServ classes EF AF3 AF2 BE

Signaling Over IP

Drivers for Signaling over IP GSM operators with high signaling traffic (SMS tornado) Offloading existing STP network investment in TDM/STPs WCDMA split architecture increases signaling initial 3GPP provides Signaling over ATM/AAL5 3GPP R’4 introduces Signaling over IP To continue well-proven SS7 applications in an IP world Multi-service IP network CAPEX/OPEX reductions

Signaling Example (R4) MSC HLR server MGW RNC SGSN IP sigtran sigtran GCP/IP RANAP/IP IP sigtran MGW MAP/IP RANAP/ATM RNC sigtran SGSN RANAP/ATM

IPv6

Designed for efficient implementation in silicon Hierarchical addressing Auto configuration Increased address space Extended multicast/ any-cast support Multihoming Built-in Mobile IP Flow identification Built-in security IPv6 Also mention ‘renumbering’ Designed for efficient implementation in silicon Defined transition mechanisms/tools

IPv6 User IPv6 Application Server GGSN Terminal UTRAN Core Transport IPv6/IPv4 User and transport planes are completely independent, i.e. the transport plane can run on a different IP version than the user plane which allows for a controlled IPv6 introduction UTRAN and Core Network transport can also run on different IP versions

3GPP UMTS Network & protocol stack External PLMN IPv6 Network Gp Iub RBS RNC GGSN Gn UE UTRAN UMTS/GPRS Backbone SGSN IPv4 Network Appl Appl TCP/UDP TCP/UDP IP IP IP Relay Relay PDCP PDCP GTP-U GTP-U GTP-U GTP-U L2 L2 RLC RLC UDP UDP UDP UDP MAC MAC IP IP IP IP L1 L1 L2/L1 L2/L1 L2/L1 L2/L1 L1 L1 UE UTRAN SGSN GGSN Host Uu Iu-PS Gn/Gp Gi User level IP Transport level IP

Transition Initial deployment of IPv6 will need interworking with existing IPv4 (public & private) networks IPv6 on the user (application) layer first NAT-PT & ALG combination for IPv6-IPv4 translation Dual stack terminals & nodes GGSN Gi interface IPv6 enabled Initially IPv6 islands connected via IPv4 networks Configured and 6to4 tunnels support

Translation mechanism NA(P)T - PT & ALG IPv6 on User level IMS Network IPv4 Network GGSN IPv6 Packet IPv6 Packet IPv4 Packet IPv4 Terminal IPv6 Terminal NA(P)T - PT & ALG In this scenario a NA(P)T-PT functionality is recommended to allow IPv6 terminals to communicate with IPv4 hosts. The use of NA(P)T-PT allows operators to multiplex a number of connections onto the same IPv4 address. The NAT-PT functionality can be located on the edge of the operator’s IPv6 network. In this scenario, NA(P)T-PT is transparent to the end terminals. Hence, no extra requirements are placed on the terminals.

Destination 6to4 router recognises, removes IPv4 prefix IPv6 to IPv4 Tunneling Configured tunnels 6-to-4 tunnels IPv6 on User level IPv4 Network IPv6 Network GGSN IPv6 Packet IPv6 Packet In this scenario a NA(P)T-PT functionality is recommended to allow IPv6 terminals to communicate with IPv4 hosts. The use of NA(P)T-PT allows operators to multiplex a number of connections onto the same IPv4 address. The NAT-PT functionality can be located on the edge of the operator’s IPv6 network. In this scenario, NA(P)T-PT is transparent to the end terminals. Hence, no extra requirements are placed on the terminals. IPv6 Terminal IPv6 Terminal Destination 6to4 router recognises, removes IPv4 prefix 6to4 border router Applies Prefix

Summary IP in Mobile Systems is already reality and increasing in importance and role All-IP is a question of CAPEX/OPEX Many new challenges, such as VPNs, IPv6, QoS… End-user applications are the drivers for IP

Thank you È Mobile : +216 98 244 816 Chaker SLIMI Technical Solutions Engineer Multiservice Networks,Mobile Internet È Mobile : +216 98 244 816 * E-mail : Chaker.Slimi@btn.ericsson.se ( Tel : +216 71 962 400