© Intellitel Communications Ltd Intelligent Networks

Introduction to Pasi Kemppainen Agenda • Introduction to Intelligent Networks ­ Objectives ­ History ­ Standardisation ­ Network components ­ Services ­ Markets and players ­ Future • Introduction to mobile intelligent networks ­ GSM networking and standardisation principles ­ CAMEL ­ UMTS/3G

© IntellitelCommunications Ltd 2 IN Business Objectives • IN business objectives ­ additional revenues • more traffic •new services • new customers ­ cost-efficiency • lower level of investments • lower service introduction costs • decrease operational costs • multivendor systems and networks

© IntellitelCommunications Ltd 3 IN Business Objectives ­ better customer service • rapid service introduction • differentiated services • centralized service/subscriber management • management over multiple networks

Customer care Reliability Ease of use

Connectivity Reasonable costs Customer Security Tailorised billing

Features Personalisation Ease of subscription

© IntellitelCommunications Ltd 4 History - non-IN

“intelligence”

Feature Centralised Node databases, Support for CC and Mgmt 800 -services Electro- SPCs mechanical Relay switches non-IN

© IntellitelCommunications Ltd 1960 1970 1980 1985 1990 1995 5 Time History - pre-IN • SPC (Stored Program Control) exchanges in 1960s ­ Computer technology and telephone network merged ­ Routing intelligence in switches ­ Offered services call waiting and traditional PBX (AT&T) • Mid-1970s support for management and maintenance ­ Databases located at network control points ­ Value added services practical and economical to offer • 1984 deregulation of the markets in the USA ­ AT&T’s regional telephone business split into baby bells

© IntellitelCommunications Ltd 6 History - pre-IN • Centralised databases in 1980s (AT&T) ­ First calling card and 800-services ­ AT&T Software Defined Network (“pre-VPN”) ­ Term ‘Intelligent Network’, Bellcore 1984 • term more for marketing purposes than for technology ­ ‘Feature Node’ concept 1985 (Ameritech) objectives • total separation of services and switching • vendor independence • new services quickly and economically • services offered by third party

© IntellitelCommunications Ltd 7 History - AIN

“intelligence”

AIN AIN Rel 0.2 Rel .0.1 AIN IN/2 Rel 0.0

IN/1+ IN/1

Feature Bellcore Centralised Node IN databases, Support for CC and Mgmt 800 -services Electro- SPCs mechanical Relay switches non-IN

© IntellitelCommunications Ltd 1960 1970 1980 1985 1990 1995 8 Time History - IN/1 • IN/1, Bellcore 1986 ­ Terminology (SCP, SSP) ­ Centralised architecture • SCP only a simple “number translator” • in service provision both SSP and SCP had to be updated (i.e., proprietary SSP-SCP protocols) • SS#7 signalling ­ Framework only for three new services • freephone • credit card billing • private numbering plan ­ Dropped by the regional operating companies • new regulations did not allow provision of services in national scale

© IntellitelCommunications Ltd 9 History - IN/2 • IN/2, Bellcore 1987 ­ Generalization of the IN/1 approach • no service-specific specifications ­ No switch dependency ­ Rapid deployment of new services with standardized service logic intepreter ­ IP concept was introduced ­ Functional components (FC) • network capabilities availalable to services • FC’s were called by SCP and executed by SSP ­ Project timescales discovered unrealistic

© IntellitelCommunications Ltd 10 History - IN/1+ • IN/1+, Bellcore 1991 ­ Interim, downsized solution to IN/2 ­ Timescales unrealistic, too ­ Both IN/2 and IN/1+ were rejected by telcos

© IntellitelCommunications Ltd 11 History - AIN • AIN (Advanced IN), Bellcore 1989 ­ Influenced by IN/2 ­ Phased standardization •AIN Release 0.1 - 1991 •AIN Release 0.2 -1993 •AIN Release 1.0 - 1995 ­ Multivendor Interaction Forum (MVI) • in co-operation with other organisations and companies • solid industry standard • better interoperability with different systems • objective to achieve applicable specifications • introduced SLEE, SCE and IN call modelling

© IntellitelCommunications Ltd 12 History - AIN ­ Reported AIN Release situation •AINrel0.1, IN/1-based implementations ‘94 • AIN rel 0.2, technical specifications for AIN ‘95-’96 •AINrel. 1.0 not anymore the target AIN-architecture (ANSI/TIA work) ­ Bellcore has withdrawn support for the AIN specifications • US operators’ own long-term plans were not aligned with AIN • US operators are now adapting ITU-T CS because of the ongoing global liberalisation of telecommunications markets ­ ANSI/TIA-consortium is working to consolidate the CS and AIN specifications • the mobile specification work is aligned with the standardization process • ITU-T supports mobile IN (GSM) through CS2 and CS3 (CAMEL) and ANSI supports IS-41 through WIN (Wireless IN)

© IntellitelCommunications Ltd 13 History - Global IN

“intelligence” Global CS2 IN CS1 AIN CS Rel 1.0

AIN AIN Rel 0.2 Rel .0.1 AIN IN/2 Rel 0.0

IN/1+ IN/1

Feature Bellcore Centralised Node IN databases, Support for CC and Mgmt 800 -services Electro- SPCs mechanical Relay switches non-IN

© IntellitelCommunications Ltd 1960 1970 1980 1985 1990 1995 14 Time History - CS • CS (Capability Sets), ITU-T 1989 ­ Framework equivalent to AIN ­ Define basic IN-services (e.g. freephone, premium rate and UPT) and service features ­ Introduced IN conceptual model (INCM) • 4-plane framework of IN structured telecommunications network ­ Service independent building blocks, SIBs • basic IN-service functional entities (e.g. digit collect and analyse, time and date functions) • ideal service creation by grouping SIBs

© IntellitelCommunications Ltd 15 History - CS ­ Development in downwards compatible phases •CS1, published 1992 (ETSI specified downsized CORE CS1 specification 1994) • CS2, design started 1992, first stable specifications out 6/96 (approved 1998) • CS3, design focus on internet, mobility, multimedia and broadband networks (approved 2000) • CS4 work started to consolidate the IETF and ITU-T/ETSI standards

CS3 CS2 AIN CS CS1

© IntellitelCommunications Ltd 16 History - CS1 • CS1 includes e.g. ­ IN Conseptual Model (INCM) • Service Plane (Services, Service Features) • Global Functional Plane (SIBs) • Distributed Functional Plane (Functional Entities) • Physical Plane (Physical Entities, protocols) ­ INAP interfaces for SSP - SCP - IP ­ Basic Call Model (BCM)

© IntellitelCommunications Ltd 17 Present - CS2 • CS2 includes e.g. ­ All CS1 functionality (+INAP for SCP - SDP) ­ Internetworking e.g. • TMN (service and subscriber data management) • TCP/IP (WWW, intranets) ­ Advanced SRF (scripts) ­ Feature interaction discovery methodologies ­ Basic Non-Call Related Call Model (BNCM) ­ New functional entities e.g. • Call Unrelated Switching Function • Service Control User Access Function

© IntellitelCommunications Ltd 18 Future - Towards 3G/UMTS

“intelligence”

GSM 2+ CAMEL, CS2, CS3 GSM

GSM 2+ GPRS, CS3 Internet / WWW 3G/3G/ Fixed: ATM, FR, xDSL, cable, (D)WDM UMTSUMTS Mobile: HSCSD, EDGE, WCDMA CSx WB/BB

AIN

Pre-IN

© IntellitelCommunications Ltd 1970 1980 1990 2000 2005 2010 19 Time Evolution of Telecommunications

TNI-RM “telecommunications network and services WLAN intelligence” 3G/UMTS

CS3 CS2

v2+ GSM v2 GSM v1

TMN

IN CS1 NMT ATM Corporate IETF Packet data Networks ISDN OMG OMA networks, SS 7 TCP/IP ODP/TINA Analogous Modem SS 6 telephony services World Wide Web services

© IntellitelCommunications Ltd 20 1950 1960 1970 1980 1990 2000 time IN

SMS SCE

SMF SDP SCEF SCP SDF

SCF SN SS#7 network AD SDF SSF SDF SCF CCF SRF STP

SCF

IP SSP SSCP SRF CCF CCAF SRF CCF CCAF SCF Signalling NAP SSF SDF Optional FE Transfer CCAF SSF Point (STP) Signalling Transport CCF Management

© IntellitelCommunications Ltd 21 IN Architecture - Example

Operations Management Center SMAF SMF SCEF

SCP SDF SCF IP

SRF

Local Exchange SSP + SSP SSF SSF Local Exchange CCAF CCF CCF CCF CCAF

Service management Service control Call and Resource control Bearer control (below)

© IntellitelCommunications Ltd 22 IN Terminology

Functional Entity Definition Related products Call Control Agent Provides the means to connect the subscriber terminal Network Access Point (NAP), Function (CCAF) (i.e., phone) to switch (SSP). Controls the establishment Service Switching Point (SSP) and releases of calls on behalf subscriber's terminal. Call Control Function Provides the means for establishing and controlling bearer Service Switching Point (SSP) (CCF) services on behalf network users; the CCF refers to call and connection handling in classical sense Service Switching Provides the means to recognise calls requiring IN service Service Switching Point (SSP) Function (SSF) processing, and to interact with call processing and service logic on behalf of these calls Service Control Function Provides the logical control applied to a call requiring IN Service Control Point (SCP), (SCF) service and handles service related processing activities, adjuct (AD), Service Node (SN) e.g. analysis translattion, screenig, routing; in other words the SCF contains the IN service logic Service Data Function Handles the access to service-related and network data Service Control Point (SCP), (SDF) and provides a logical view of the data to the SCF adjuct (AD), Service Node (SN) Specialised Resource Provides end-user interaction with the IN-structured Service Node (SN), Intelligent Function (SRF) network through control over resources such as DTMF Peripheral (IP) receivers, voice, recognation capabilities, protocol conversion, announcements etc. Service Management Provides service provisioning deployment and Service Management System Function (SMF) management control; the SMF allows access to all IN (SMS) functional entities for the transfer of information related to service logic and service data Service Creation provides the capability for the creation, verification and Service Creation Environment Environment Function testing of new IN services (SCE) (SCEF)

© IntellitelCommunications Ltd 23 IN Architecture • Service Switching Point, SSP ­ PSTN exchange modified to recognise and trigger IN-services ­ Can have dialogues with different SCPs • trigger points define the required IN services in calls • interconnections via Signalling Transfer Points (or not) ­ Dialogues with SCP’s based on SS7 signalling - no actual payload (e.g. voice) is transmitted in SS7 ­ SSP+”SCF”+”SDF” = SSCP, Service Switching and Control Point

© IntellitelCommunications Ltd 24 IN Architecture • Service Control Point, SCP ­ Service logic implemented in Service Logic Program (SLP) ­ Services (SLPs) are run in Service Logic Execution Environment (SLEE) e.g. OS, runtime modules, management procedures etc ­ Service data can be located in Service Data Point i.e. (relational) database • usually integrated to SCP • commercial product (Oracle,Sybase) or proprietary (in-memory/real-time) database ­ Service interfaces to SSP/IP abstracted with TCAP or INAP (OSI ) ­ High system availability with doubled and/or mated pair systems

© IntellitelCommunications Ltd 25 IN Architecture •Adjuct, AD ­ Functionally equivalent to SCP, but has • direct communications link to SSP (X.25, IP, Frame Relay) • supports one-to-one relationship with SSP • usually small geographical coverage

© IntellitelCommunications Ltd 26 IN Architecture • Intelligent Peripheral, IP ­ Usually integrated with SSP or SN • interface to SSP/SN incl. both signaling and data • TUP/ISUP call control signaling, service control usually proprietary ­ Service logic in SSP/SN/SCP • interface to SCP only signaling i.e. TCAP/INAP ­ Manages resources such as • announcements • speech recognitions • digit collection • protocol conversions

© IntellitelCommunications Ltd 27 IN Architecture • Service Node, SN ­ Complete set of resources and services for advanced IN services • can have the functionality of SSP, SCP and IP • usually used for advanced voice-processing functionality e.g. voice messaging

© IntellitelCommunications Ltd 28 IN Architecture • Service Management System, SMS ­ Supports both centralised subscriber and service data management • ensure data consistency in distributed SCPs’ databases (SDPs) • service subscriber to an 800-service can configure call routing • operator can load new services to the SCPs • operator can gather statistics and billing data to the OSS (Operations Support System) ­ Usually closely coupled with the SCP • no standard SMS-SCP interface protocols exist in CS1 • CS2 specifies TMN as the management framework

© IntellitelCommunications Ltd 29 IN Architecture • Service Creation Environment, SCE ­ Framework for defining, developing and testing SLPs e.g. • graphical SIB-based ‘drag and drop’ • graphical SDL-based • high level, 4GL language based • low level C-language based with special resources e.g. libraries and runtimes • proprietary graphic and/or text based ­ Services are loaded via SMS to SCPs

© IntellitelCommunications Ltd 30 IN Services • Services are the core of IN ­ Rapid service creation and deployment ­ Time to market the competitive advantage ­ Different services for different needs • Ideally service environments facilitate ­ the profiling of existing services as well as the provision of customised service requirements ­ third party service provision ­ service creation/customisation by the subscribers

© IntellitelCommunications Ltd 31 IN Services • Service categories ­ Mass market services • well-defined set of ‘basic’ service features • no customer differentiation • e.g. 800, premium rate, VPN, mobile services ­ Profiled services • same service features as in mass market services • user data can be easily and rapidly modified by the service subscriber or the users • 800 service with dynamic routing, premium rate with information selection, UPT

© IntellitelCommunications Ltd 32 IN Services ­ Custom services • tailored services for specific subscriber and end-user needs • service creation by subcribers • personal assistants, VPN and mobility in Intranet, voice and media integration (VoIP)

Custom services

Service Complexity / Profiled services Value to customers Mass market services

1980 1990 2000

© IntellitelCommunications Ltd 33 IN Services • Mass market services ­ 800-service i.e. freephone • the oldest and most widely used IN-service • the most profitable • in phone calls the subscriber is charged, not users • based on pure number translation with or without intelligent routing e.g. ­ call distribution ­ call queueing ­ time and date dependencies • very widely used in USA, in Europe slow uptake

© IntellitelCommunications Ltd 34 IN Services ­ Premium rate • 700-service (also 600-service in Finland) • user is charged for the use of services • typically provision of information, direct selling, chat lines and televoting ­ Virtual Private Network, VPN • defined as a logical closed user group, implemented over public switched telecommunications facilities • provision of private numbering plan • call charging on the basis of duration of usage • usage for switched voice, switched data or both • single interface for all domestic and international needs e.g. Sonera’s 02040 xxxx -numbering plan

© IntellitelCommunications Ltd 35 IN Services ­ Mobile/wireless services • basically all IN services are also available for mobile users • in addition mobility brings new opportunities for service offerings ­ mobile services ­ location sensitive billing and services ­ universal voice mail • mobile IN services enabled by GSM CAMEL standard

© IntellitelCommunications Ltd 36 IN Services • Profiled services ­ Dynamic 800 call routing • control of the service data in call routing via switching environment • subcriber can have own SMS to gather information of the service usage ­ Bank account query • DTMF coded user ID and password ­ Personal Communications Service (PCS) • users have unique PINs (Personal identification Number) • network access terminal independency

© IntellitelCommunications Ltd 37 IN Services • Custom services ­ Differentiated IN/ services for subscriber basis • not possible with traditional IN technologies ­ IN-GSM-IP (WWW) integration ­ CAMEL services

© IntellitelCommunications Ltd 38 Telecommunications Markets

Deregulation and liberalization process

Differentation

Deregulation Competition Cost-efficiency

Liberalization Time-to-market

Towards differentiated value-added services and cost-efficient technologies and business processes also in telecommunications business

© IntellitelCommunications Ltd 39 Telecommunications Markets • For the telecom infrastructure, there has been introduced at least three different, yet complementing, service platform emphasises: ­ telecommunications, IN and GSM in particular, enhanced value added services platforms (the market differentation emphasis) e.g. •HP • Ericsson • Lucent •Siemens •Nokia • Alcatel (incl. DSC Communications) •Nortel • Others: Compaq, Tecnomen, Logica

© IntellitelCommunications Ltd 40 Telecommunications Markets ­ telecommunications and Internet-based telephony interworking and integration platforms (the unified messaging and overlay switching emphasis) • IVR-system vendors: Homisco/VoiceNet, Intervoice, … • tradional CTI-vendors: Genesys, …, and PBX-vendors • service node vendors: Teligent, Votek, IBM, … • enhanced service platform (ESP) vendors: Vicorp, Aethos, … • voice-over-IP vendors: Vocaltec, Elemedia, Databeam, ... AND Microsoft ­ telecommunications and Internet service infrastructure consolidation platforms (the service convergence emphasis) • Intellitel Communications • ObjectSwitch, Corp. • Omnisoft, Inc.

© IntellitelCommunications Ltd 41 Telecommunications Markets

Telecommunications market life cycle

sales market segmentation : price competition differentation low profits market competition :

International overcapacity falling prices calls LAN standardization : IN niche markets advertizing GSM Internet-access lower profits high prices WAN Domestic high profits calls Security SMS SDH proprietary technologies : WLAN

creaming prices xDSL VoIP highest profits (D)WDM EDI GPRS WLL VOD 3G WAP

© IntellitelCommunications Ltd Introductory Growth Maturity Decline 42 IN Business Objectives • IN business objectives ­ additional revenues • more traffic •new services • new customers ­ cost-efficiency • lower level of investments • lower service introduction costs • decrease operational costs • multivendor systems and networks

© IntellitelCommunications Ltd 43 IN Business Objectives ­ better customer service • rapid service introduction • differentiated services • centralized service/subscriber management • management over multiple networks

Customer care Reliability Ease of use

Connectivity Reasonable costs Customer Security Tailorised billing

Features Personalisation Ease of subscrition

© IntellitelCommunications Ltd 44 IN Markets ­ The vast majority of capital will be spent on SSF/CCF functionality and SCP-related products • competition rises cost-efficiency • expect strategic partnerships and alliances ­ Personal mobility (PCS) became the killer application ­ IP/web-integration in mobile services is inevitable (WAP, GPRS) ­ Will CAMEL take place? ­ Liberation of Telco industry in Europe has fierced the competition ­ Expect consolidation of telecommunications operators and service providers to continue

© IntellitelCommunications Ltd 45 IN vs. Internet

Axiom Intelligent Internet Networks Switching Circuit Packet Signalling SS7 TCP/IP Payload Trunk TCP/IP Congestion control Good Poor Standards De-jure De-facto Service logic Centralized Distributed Management Centralized Distributed Network API INAP, MAP, CAP Various: HTTP, SMTP ... Security Safe Not so safe Billing Centralized Distributed Business Oligopoly Free competition Technology Expensive, Cost-efficient, standard tools proprietary Open for 3rd party No Yes Terminals Phones, PDAs Computers Speech Yes “Yes” (VoIP) Broadband ATM, WDM ATM, GbitEth, WDM Mobility GSM, 3G/UMTS No. (IP v6 (?), mobile IP (?)) Killer application PCS, GPRS WWW, e-commerce

© IntellitelCommunications Ltd 46 Intelligents Networks - Summary • Intelligent Network, IN objectives ­ Open standards, vendor independence ­ Rapid service creation and deployment ­ Centralised subscriber and service data management ­ Differentiated services to customers Rapid adaptation to market needs and competition Competitive advantage

© IntellitelCommunications Ltd 47 Mobile Networking Evolution • Intelligent Networks (IN) ­ emphasis on service creation and deployment in telecommunications networks e.g. • number translation services (800/700, VPN, …) • televoting • pre-paid services ­ IN objectives • rapid service creation and time to market • multivendor solutions • cost-efficiency ­ standardised networking interfaces and functionality (Bellcore AIN, ITU-T CS{1,2,3}) ­ service and subscriber information (‘network intelligence’) is stored in databases

© IntellitelCommunications Ltd 48 Mobile Networking Evolution • Intelligent Network architecture

SME SCE SMS PSTN

Alueverkko Kaukoverkko

SCP SDPEIR IP

LE

SSP

SSP Muiden Kansainvälinen maiden KV- keskukset LE SSP

Alueverkko

muut PLMN:t, esim. PCS- tai SSP toisen operaattorin LE SSP samanlainen GSM- verkko

© IntellitelCommunications Ltd 49 Mobile Networking Evolution • GSM networks ­ first second generation (2G) global digital mobile networking standard • first generation (1G) mobile networks based on analog systems (NMT, AMPS) ­ emphasis on • wide networking coverage (national level, international roaming) • new value added services (short messages, voice mails, …) • interoperability with other networks (PSTN, IN, other GSM networks) ­ networking intelligence based on databases (registers) • IN functionality already exists in GSM networks • it is obvious that mobile networking evolution will align with IN evolution • objective is to utilise the exisiting IN standardisation and merge fixed and mobile networking standardisation

© IntellitelCommunications Ltd 50 Mobile Networking Evolution • GSM network architecture

OSS OMC PLMN

liitetty kaikkiin BSC:ihin liitetty kaikkiin NSS:n elementteihin BSS NSS

AuC EIR HLR

BTS SC MS BSC VLR MSC muut verkot: SMS-GMSC esimerkiksi PSTN, ISDN, BTS tai SMS-IWGMSC PSPDN tai MS CSPDN BSS

muut PLMN:t, esim. PCS- tai GMSC toisen operaattorin BTS BSC samanlainen GSM- verkko MS

© IntellitelCommunications Ltd 51 Mobile Networking Evolution • GSM and IN integration: CAMEL ­ GSM Phase 2+-defines CAMEL standard (Customised Applications for Mobile network Enhanced Logic) for IN service provisioning • defines standard interfaces inbetween IN and GSM components • offers global roaming for value added services • enables new service operators to offer services globally ­ CAMEL enables the use of home operator or service operator services • services will roam even in national networks • service billing can be managed in the home operator network (not desired by the visited operators due to the lost revenues)

© IntellitelCommunications Ltd 52 CAMEL • CAMEL standardisation ­ CAMEL Phase 1 objective was rapid time to market •short numbering • call barring • extended call transfer (time and place independence) ­ CAMEL Phase 2 extends the phase 1 and is backward compatible • prepaid with advice of charging •private numbering • flexible charging • service numbers (e.g. 800 and 700 services) ­ CAMEL Phase 3 features e.g. • MO SMS triggering • SRF based IN services • GPRS prepaid services • fraud control

© IntellitelCommunications Ltd 53 Mobile Networking Evolution

OSS OMC PLMN

liitetty kaikkiin BSC:ihin liitetty kaikkiin NSS:n elementteihin BSS NSS

AuC EIR HLR

BTS SC MS BSC VLR VMSC muut verkot: SMS-GMSC esimerkiksi PSTN, ISDN, BTS tai SMS-IWGMSC PSPDN tai MS CSPDN BSS

muut PLMN:t, esim. PCS- tai GMSC toisen operaattorin BTS BSC samanlainen GSM- verkko MS

Koti-GSM-verkko Kaukoverkko

SCP

HLR CSE SSP SDP

IP

© IntellitelCommunications Ltd 54 Mobile Networking Evolution • UMTS (Universal Mobile Telecommunications Service) and 3G networks will be evolutionary from 2G/2.5G networks ­ UMTS radio networks will be hierarchical (revolution, not evolution) and based on WCDMA (Wideband Code Division Multiple Access). Theoretical bandwidths • ~2 Mbit/s picocells • ~340 kbit/s microcells • ~64 kbit/s macrocells •~14,4 kbit/s elsewhere ­ UMTS core networking infrastructure will be based on IN/GSM SS7 signalling network foundation (evolution, not revolution) • wideband IP connectivity by GPRS, service roaming by CAMEL

© IntellitelCommunications Ltd 55 Mobile Networking Evolution

• UMTS network OSS OMC liitetty kaikkiin NSS:n elementteihin PLMN architecture NSS

Makrosolu Kannettava Mikrosolu CSE SCPEIR HLR tietokone

SC mSCP

W-BTS VLR (ATM) MS MSC muut verkot: RNC SMS-GMSC esimerkiksi tai PSTN, ISDN, SMS-IWGMSC PSPDN tai CSPDN W-BTS MS muut PLMN:t, (ATM) esim. PCS- tai GMSC toisen operaattorin samanlainen UMTS-verkko

GPRS- Pikosolu infrastruktuuri pakettidata- RNC SGSN VLRGR verkko: esimerkiksi mSCP X.25 tai W-BTS IP-pohjainen GPRS- Internet runkoverkko MS Gi GGSN Gn Gn yhteys muihin GPRS-verkkoihin, esimerkiksi

© IntellitelCommunications Ltd GGSN 56 Gi Internetin avulla Mobile Networking Evolution • UMTS services ­ traditional GSM services, in addition • sophisticated radio network services ­ in theory 2Mbit/s -14,4 kbit/s (in real life 300 kbit/s - 9,6 kbit/s) • wideband multimedia services ­ mp3 and mpeg4 based streaming services? ­ WWW- and Java based user interfaces? ­ wireless PDA/HPC appliances? ­ wireless multi-conferencing services? • virtual and private corporate mobile networks • global network connectivity? • GPS (Global Positioning System) connectivity?

© IntellitelCommunications Ltd 57 Mobile Convergence • Summary ­ IN architecture will be in the core of mobile intelligent networks • emphasis on networking functionality and registers (databases) • other future core networking functionality ­ ubiquitous IP connectivity (GPRS) ­ global service roaming (CAMEL) ­ provisioning of interactive services (WAP, WWW) ­ new charging modes ­ UMTS will unify IN and GSM architectures, wideband radio networking and IP networks into universal communications networks

© IntellitelCommunications Ltd 58 Mobile Convergence • Summary, cont. ­ Wireless LAN (WLAN) networks will bring faster, cheaper and more reliable IP connectivity • however, the speech quality, coverage and roaming will not be comparable to GSM/UMTS networks ­ ”4G networking” is about utilising and managing the best possible mobile/wireless connectivity seamlessly for the user e.g. • 2G/3G roaming •3G/WLAN roaming • network independent number portability ­ the weakest link might be the appliances’ support for multiple simultaneous network connections

© IntellitelCommunications Ltd 59 Mobile Convergence Reality Check • UMTS is not the ultimate solution for all mobility and wireless services needs ­ WLAN networks will bring faster, cheaper and more reliable IP connectivity • however, the speech quality, coverage and roaming will not be comparable to the combined GSM/UMTS networks • More important than UMTS itself, will be the seamless integration of different networking accesses and services ­ GPRS and WLAN roaming between operators and service providers ­ CAMEL for national and global CS (voice+data) services roaming ­ Mobile Number Portability for operator independent numbering • Appliances will be the critical success factor ­ Multinetwork mode appliances for GPRS (wap) and WLAN (web)

© IntellitelCommunications Ltd 60 © Intellitel Communications Ltd www.intellitel.com