Strategisk plan

534 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
534
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Essence here: Applications using Parlay API do not have to be aware of underlying network specifics. Application on parlay developed for the CAP or CS1/CS1+/CS2 circuit switched voice network can also operate towards an SIP-based network. Service architecture suitable for voice and multimedia over IP can already provide open services for circuit switched networks Note that the direct Terminal-Application interaction (e.g. HTTP based) is not included here, but does exist! See also NOTE under ‘start with 2G’
  • Strategisk plan

    1. 1. An Open Service Architecture with Location Aware Calls and Services Lill Kristiansen, Prof. Dr. Scient Dept. of Telematics, NTNU, Norway www.item.ntnu.no /~lillk www.pats.no (lab-information) [email_address]
    2. 2. Outline of the talk <ul><li>Trends in evolution </li></ul><ul><ul><li>Layering, separation and towards ’all-IP’ </li></ul></ul><ul><li>Some mobility definitions </li></ul><ul><ul><li>User mobility, service mobility, terminal mobility,… </li></ul></ul><ul><ul><li>Virtual home environment </li></ul></ul><ul><li>Brief overview of UMTS IMS system (release 5,..) </li></ul><ul><li>Brief overview of Parlay / UMTS OSA </li></ul><ul><ul><li>API for ’value added services’ </li></ul></ul><ul><li>A framework to discuss technical solutions to mobility </li></ul><ul><ul><li>Illustrations of GSM/Camel and IMS/OSA in this framework </li></ul></ul><ul><ul><li>Illustrations of possible ’middleman’ arrangements using OSA, to decrease the ’operator centric view’ </li></ul></ul>
    3. 3. The scope of this talk: <ul><li>We are mostly based on the current and upcoming ETSI/3GPP definitions (GSM, IMS and OSA) </li></ul><ul><li>We look into combinations of ’telephony’ and location based services </li></ul><ul><li>We consider that each operator: </li></ul><ul><ul><li>Has some hardware and software controlled by himself </li></ul></ul><ul><ul><ul><li>Hence has control over the non-functional requirements in this way </li></ul></ul></ul><ul><li>We do not consider ’mobile code’ in general </li></ul><ul><ul><li>But we may foresee upgrades of software from vendor to operator, or from operator’s management system to operator’s switches (call servers and service nodes </li></ul></ul>
    4. 4. Evolution: <ul><li>Several activities going on </li></ul><ul><ul><li>From CS (Circuit switched) to PS (Packet switched) </li></ul></ul><ul><ul><li>From monolitic systems (GSM and PSTN) to layered systems with one common core system with several access technologies </li></ul></ul><ul><li>QoS and realtime aspects </li></ul><ul><ul><li>GSM (2G CS): supports ’voice ’interactive conversation with 1 medium) </li></ul></ul><ul><ul><li>UMTS (3G first releases): </li></ul></ul><ul><ul><li>CS multimedia (H.324M) supports multimedia telephony </li></ul></ul>
    5. 5. System topology <ul><li>Today </li></ul><ul><ul><li>Separate Networks </li></ul></ul><ul><ul><li>Separate Users </li></ul></ul><ul><ul><li>Separate Services </li></ul></ul><ul><li>Tomorrow </li></ul><ul><ul><li>Separate Accesses </li></ul></ul><ul><ul><li>Same Core network </li></ul></ul><ul><ul><li>Same User on different accesses </li></ul></ul><ul><ul><li>Same Services </li></ul></ul>Data/IP Networks PLMN PSTN/ISDN CATV Separate Services Separate users
    6. 6. UMTS from release 5 on: IMS: I P M ultimedia S ubsystem <ul><li>Same Core network </li></ul><ul><li>Same User on different accesses </li></ul><ul><li>Same Services </li></ul><ul><li>I can use WLAN, ADSL, LAN, UTRAN (GPRS) etc. as accesses in ONE system </li></ul><ul><li>I can have several devices and move between them </li></ul>Servers Users Backbone Network Access Access Communication Control Content Content Access Gateways Access Gateways Access
    7. 7. General types of mobility <ul><li>Mobility between several technologies (e.g. with the same handheld device having several (radio) access modes). </li></ul><ul><li>User mobility across different devices. </li></ul><ul><li>Mobility in a network (i.e. inside one technology). </li></ul><ul><ul><li>Terminal mobility in GSM network </li></ul></ul><ul><ul><ul><li>Either inside one operator domain (/one country) </li></ul></ul></ul><ul><ul><ul><li>Or ‘roaming’ (to a foreign contry/operator domain) </li></ul></ul></ul>
    8. 8. General mobility definitions <ul><li>Personal mobility enables users to use services that are personalized with their preferences and identity ubiquitously, independently of both physical location and specific equipment. … ( From TINA-C in the mid-90’ties) </li></ul><ul><li>Service mobility (of a particular service) is defined as the ability for a user to obtain that particular service independently of user and terminal mobility. (Ericsson contribution to ETSI Tiphon 1999) </li></ul><ul><li>Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalized …. (3GPP TS 23.127) </li></ul>
    9. 9. Internet Mobile WAP e.g. email MMoIP(1) e.g. MMS MMoIP(3) IMS/ ’telephony’ MMoIP(4) e.g. P2T 3+G from rel.5 UTRAN ” 4-G” WLAN MMoIP(2) e.g. steaming (and H.324M) Evolution (modified from Kanter) 2G GSM 3G first releases UTRAN 2,5G ERAN
    10. 10. QoS and realtime aspects <ul><li>The CS part: </li></ul><ul><ul><li>GSM (2G CS): supports ’voice telephony’ i.e.: ’interactive conversation with one medium’ </li></ul></ul><ul><ul><li>UMTS (3G first releases CS): (H.324M) supports ’multimedia telephony i.e. ’ ’interactive conversation with multi media’ </li></ul></ul><ul><li>The ’data’ part: </li></ul><ul><ul><li>GSM supports CS-data: not used for ’conversation’ (too much delay) </li></ul></ul><ul><ul><li>GSM/GPRS (2G, 2,5G) supports SMS, and MMS: MMoIP(1): QoS BE: Best Effort (not requiring real time support) </li></ul></ul><ul><ul><li>GPRS with streaming MMoIP(2) </li></ul></ul><ul><li>From realease 5: All-IP common voice/data </li></ul><ul><ul><li>Full QoS enabling MMoIP(3) (VoIP and MMoIP in) IMS: Interactive Conversational Services over IP, using SIP </li></ul></ul><ul><li>Via WLAN: P2T/PoC (Push to Talk /over Cellular) varying QoS (delays and walkie-talkie-like) </li></ul>
    11. 11. UMTS IMS architecture HSS: Home Subscriber Services HLR-like CSCF: ’Call Server’ Call/Session Control Function P-CSCF Proxy- I-CSCF Interrogating- S-CSCF Serving - xGSN GPRS-noder Visited B Home A Visited A A B Home B GGSN SGSN Radio Access Network GGSN SGSN Radio Access Network P-CSCF I-CSCF HSS HSS S-CSCF I-CSCF S-CSCF P-CSCF
    12. 12. UMTS IMS: basic call flow Non-GPRS access Networks (e.g. WLAN) comes in release 6 P-SCSF Visited B Home A Visited A A B Home B GGSN SGSN Radio Access Network P-CSCF I-CSCF HSS HSS S-CSCF I-CSCF S-CSCF WLAN
    13. 13. Virtual Home Environment (3GPP): <ul><li>VHE enables end users to bring with them their personal service environment whilst roaming between networks, and also being independent of terminal used </li></ul><ul><li>PSE Personal Service Environment: </li></ul><ul><ul><li>describes how the user wishes to manage and interact with her communication services. It is a combination of a list of subscribed to services, service preferences and terminal interface preferences. PSE also encompasses the user management of multiple subscriptions, e.g. business and private, multiple terminal types and location preferences. </li></ul></ul><ul><ul><li>The PSE is defined in terms of one or more User Profiles. </li></ul></ul>
    14. 14. 3GPP OSA architecture <ul><li>Allows application to use underlying network resources </li></ul><ul><li>Allows combinations: </li></ul><ul><ul><li>Location capabilities (from GSM/UMTS and WLAN) </li></ul></ul><ul><ul><ul><li>Radionor Cordis Radioeye allows detailed location in WLAN </li></ul></ul></ul><ul><ul><li>SMS/MMS capabilities </li></ul></ul><ul><ul><li>Call Control capabilities </li></ul></ul>
    15. 15. Parlay and UMTS Open Service Access; Migration and Convergence
    16. 16. Today (2000 and 2004) on PC: type in your location into web-page manually Tomorrow: fixed LAN,and WLAN access into same core system Parlay/OSA for data-services
    17. 17. For data services (From Ericsson 2000) Avoid typing, get location automatic e.g. into WAP page (or into SMS content) Today in Oslo, Norway(2004): Call taxi, application fetches your location:nearest taxi comes (combinations: call, location, applic.data!) Further issues: mobility between operators, countries and companies for this taxi service Bank services Location services Leisure News
    18. 18. A Framework to analyse the relations between home and visited in 2G and 3G <ul><li>This figure assumes no mobile code </li></ul><ul><ul><li>i.e. more specifically: </li></ul></ul><ul><ul><ul><li>Each box is: hardware, software run by one operator </li></ul></ul></ul><ul><li>(We may note that mobility in both 2G and planned versions of 3G all assumes no mobile code.) </li></ul>
    19. 19. Framework applied to 2G with OSA <ul><li>NOTE: There is a typo in the paper, this is the right version of Figure 3, showing Camel </li></ul>S) C) MSC +VLR MSC CC CC WAP WAP GW IN/ Camel HLR SCS OSA AS2 S2) HLR
    20. 20. 3G IMS system in this reference model <ul><li>This is previous IMS-slide, now slightly re-arranged </li></ul>
    21. 21. OSA revisited: with several service providers involved This may be the (national) regulator
    22. 22. Advantages with this new solution <ul><li>Less ’operator centric’ </li></ul><ul><ul><li>Does not require the 3rd party service provider to have a business relation with the operator </li></ul></ul><ul><ul><li>The regulator acts as ’neutral middleman’: </li></ul></ul><ul><ul><ul><li>assuring equal access for all service providers </li></ul></ul></ul><ul><ul><ul><li>Single point of contact for the enduser </li></ul></ul></ul><ul><ul><ul><li>Easier for the enduser to enforce a good privacy policy </li></ul></ul></ul>
    23. 23. Network centric =/= operator centric <ul><li>AS3 is a network based solution, but totally independent from the network operator domain </li></ul><ul><li>A personal web-page might also act as a network based solution </li></ul><ul><ul><li>See Jan Egil Kristiansen Our addresses and phones, http:// heima.olivant.fo/~styrheim/kontakt.en.html </li></ul></ul><ul><ul><ul><li>The enduser himself controls the user mobility, and (in non-realtime) informs his contacts about the ’current terminal/SIM card) </li></ul></ul></ul><ul><ul><ul><li>Allows the enduser to buy local GSM-cards, instead of the often more expence network operator centric solution with ’roaming’ That is often very expensive, and subject to little competition </li></ul></ul></ul>
    24. 24. Summing up the reference figure <ul><li>Allows us to discuss different business models between home and visited networks </li></ul><ul><ul><li>Fits in with 2G & Camel &OSA </li></ul></ul><ul><ul><ul><li>Shows some major drawback with Camel </li></ul></ul></ul><ul><ul><ul><li>Due to call server (MSC in visited network) </li></ul></ul></ul><ul><ul><li>Also fits in with 3+G (IMS) & OSA </li></ul></ul><ul><ul><ul><li>Nice to use when discussing the advantages of having S-CSCF in home network vs. (the now gone option of S-SCSF in visited network) </li></ul></ul></ul><ul><ul><ul><li>Useful when discussing the fully mobile case of ’call nearest taxi’ </li></ul></ul></ul><ul><ul><ul><li>Fits in also with private initiatives not described in the 3GPP standards </li></ul></ul></ul><ul><li>Further issues: Mobile code is not covered </li></ul>

    ×