Universal Mobile Telecommunication System (UMTS)

Παρουσίαση με θέμα: "Universal Mobile Telecommunication System (UMTS)"— Μεταγράφημα παρουσίασης:

1

2 Universal Mobile Telecommunication System (UMTS)

3 2ΠεριεχόμεναΠεριεχόμενα 1. Εισαγωγή 2. UTRAN 3. Mobility 4. QoS 5. IMS 6. OSA 7. MEXE

4 3 Εισαγωγή στο UMTS

5 4

6 5 Χαρακτηριστικά του UMTS Κοινή παγκόσμια χρήση Υποστήριξη όλων των εφαρμογών Υποστήριξη PS (Packet Switched) & CS (Circuit Switch) Ρυθμοί μετάδοσης μέχρι 2Mbps (κινητικότητα - ταχύτητα) WCDMA (Wideband Code Division Multiple Access) 384 Kbps wide area coverage 2 Mbps local area coverage 10 ms frame length Chip rate = 3.84 Mchips/s FDD (Frequency Division Duplex) Uplink 1920-1980MHz;Downlink 2110-2170MHz Uplink 1850-1910MHz;Downlink 1930-1990MHz TDD (Time Division Duplex)

7 6 Διαδικασίες προτυποποίησης UMTS IMT 2000 (ITU): International Mobile Telecommunications 2000: initial trial systems & 2000MHz 17 διαφορετικές προτάσεις κατατέθηκαν στην ITU το 1998 11 terrestrial & 6 Mobile satellite systems Αξιολόγηση των προτάσεων (τέλος του 1998) Διαπραγματεύσεις για συνένωση τους (6/1999) Προδιαγραφές για την ραδιο-τεχνολογία μετάδοσης (τέλος του 1999) Πιο σημαντικές προτάσεις: UMTS (W-CDMA): μετεξέλιξη του GSM CDMA2000: Ενδιάμεσο πρότυπο για το IS-95 TD-CDMA (Time Division synchronous CDMA): UWC-136/EDGE για την επαύξηση των δυνατοτήτων των D-AMPS και GSM

8 7 3GPP Third Generation Partnership Project ETSI (Ευρώπη), Association of Radio Industries and Business Telecommunication Technology Committee (ARIB/TTC - Ιαπωνία), American National Standards Institute (ANSI - Αμερική), Telecommunication Technology Association (Ν. Κορέα), Chinese Wireless Telecommunication Standard (CWTS). Εκδόσεις: Release 99 (12/1999): Μετεξέλιξη του GSM δικτύου Release 2000: Μετεξελίξεις για το IS-95 και το EDGE; δυνατότητα σύνδεσης με άλλα δίκτυα πρόσβασης (WLAN,BRAN)

9 8 Release 99 UTRAN: UMTS Terrestrial Radio Access Network W-CDMA Ραδιοεπαφή Υποστήριξη Time Division Duplex & Frequency Division Duplex TDD: Micro & Pico κυψέλες καθώς και ασύρματες εφαρμογές FDD: Wide-area coverage (public & macro κυψέλες) MC (Multicarrier) mode: εγκαθίδρυση συμβατότητας ανάμεσα σε UMTS και CDMA 2000

10 9 Λογική αρχιτεκτονική UMTS Circuit Switched domain UMTS Access Network GSM Access Network Packet Switched domain

11 10 UTRAN (TS 25.401) RNC- BSC Node B - BTS Iu, Iub, Iur:ATM transmission principles

12 11 Γενική αρχιτεκτονική πρωτοκόλλων User Plane The radio access bearer service is offered from SAP to SAP by the Access Stratum. Uu and Iu interfaces linked together provide this radio access bearer service.

13 12 Γενική αρχιτεκτονική πρωτοκόλλων Control Plane Note: CM, MM, GMM and SM exemplifies a set of NAS control protocols between UE and CN. There may be different NAS protocol stacks in parallel.

14 13 Serving & Drift RNC RNC: Αυτόνομη διαχείριση των ράδιο πόρων του UTRAN O&M Διεπαφή ATM switching & multiplexing Συνολικός ελεγχος του RNS SRNC: Admission RR Allocation Congestion Control Handover Macro-diversity DRNC: RR Allocation

15 14 Node B Η φυσική μονάδα για μεταδόσεις δεδομένων στη ραδιο-επαφή Ελέγχει μία ή περισσότερες κυψέλες Μπορεί να υποστηρίζει FDD & TDD Αποτελεί σημείο τερματισμού του ΑΤΜ Εκτελεί:  Rate adaptation  Forward Error Correction (FEC)  Quadrature Phase Shift Keying (QPSK)  Μετρήσεις στην ισχύ και την ποιότητα της σύνδεσης (Μεταφορά στοιχείων στο RNC για εκτέλεση handover/macro-diversity)  Power Control  W-CDMA spreading/despreading

16 15 UMTS User Equipment UMTS UE = Mobile Equipment & UMTS SIM - USIM UMTS UE - Node B: FEC Power Control Radio Measurements Modulation - Demodulation W-CDMA Spreading/Despreading UMTS UE - RNC: Radio Resource Control Handover (CS) & Cell Selection (PS) Ciphering/De-ciphering UMTS UE - Core Network: Mobility Management(Location Registration/update, Attach-Detach) Session Management (PDP Context De/Activation) Service Request

17 16 Γενικό Μοντέλο General protocol model for UTRAN Interfaces. The structure is based on the principle that the layers and planes are logically independent of each other.

18 17 Application Protocols

19 18 Radio Access Network Application Part - RANAP TS 25.413 Radio Access Bearer Management (setup, maintenance, release) Management of the Iu connections Transport of non-access stratum info between UE-CN (mobility management signaling, broadcast information) Exchange UE location information between RNC and CN Paging requests from CN to UE Overload and general error situation handling

20 19 Radio Network Sublayer Application Part - RNSAP TS 25.423 Management of Radio Links Paging SRNC relocation Measurements of dedicated resources

21 20 Node B Application Part - NBAP TS 25.433 Management of common channels, radio resources and radio links Configuration management Measurement handling and control Synchronization (TDD) Reporting of Error situations

22 21 Radio Resource Control - RRC TS 25.331 Broadcasting Information Management of connections between UE and UTRAN Management of radio bearers Ciphering Control Power Control Message Integrity protection Paging and notifying

23 22 Transport Network Layer - Layer 3 Iu, Iur: Signaling Connection Protocol Part (SCCP) [Q.711, Q.716] Provides connectionless and connection oriented services Iu-CS, Iur, Iub: ALCAP [Q.2630.1, Q.2150.1, Q.2150.2] Signaling needed to setup bearers to transmit data via the user plane.

24 23 PS domain με UTRAN δίκτυο πρόσβασης User Plane Control Plane L1 L2 IP TCP/UDP GTP-C L2 IP GGSN L1 L2 IP HOST MS RF MAC RLC PDCP IP TCP/UDP APPL RNS RFATM MAC AAL5 RLC SIGNAL SCCP RRCRANAP MS RF MAC RLC RRC GMM/SM SGSN ATML1 AAL5L2 SIGNAL SCCP RANAP IP TCP/UDP GTP-C GMM/SM L1 L2 IP TCP/UDP APPL HOSTRNS RF MAC RLC PDCP ATM AAL5 IP TCP/UDP GTP-U Relay Function SGSN ATM AAL5 IP TCP/UDP GTP-U L1 L2 IP TCP/UDP GTP-U Relay Function GGSN L1 L2 IP TCP/UDP GTP-U IP L2 IP Relay Function

25 24 Στοίβα πρωτοκόλλων με UTRAN δίκτυο πρόσβασης Applicatio n UMTS Link IP TCP UDP IP TCP UDP Other Network IP TCP UDP GPRS Link UMTS Radio LinkGPRS Core Network Link MS RF MAC RLC PDCP RNS RF MAC RLC PDCP ATM AAL5 IP TCP/UDP GTP-U SGSN ATM AAL5 IP TCP/UDP GTP-U L1 L2 IP TCP/UDP GTP-U GGSN L1 L2 IP TCP/UDP GTP-U L2 IP

26 25 Δρομολόγηση και μεταφορά πακέτων: Ενθυλάκωση Ενθυλάκωση  Το τμήμα μεταγωγής πακέτου μεταφέρει PDP Protocol Data Units (PDU) ανάμεσα σε εξωτερικά δίκτυα και ένα MS με διαφανή τρόπο  Όλα τα PDP Protocol Data Units ενθυλακώνονται και αποθυλακώνονται για την περαιτέρω δρομολόγησή τους Δικτυακά στοιχεία ενθυλάκωσης  MS  RNC  SGSN  GGSN Λειτουργίες ενθυλάκωσης  Στο δίκτυο κορμού ανάμεσα σε δύο κόμβους GSN ή ανάμεσα σε ένα SGSN και ένα RNC  Μια ανάμεσα στο MS και το SGSN στην περίπτωση GSM δικτύου πρόσβασης  Μια ανάμεσα στο MS και το RNC στην περίπτωση UMTS δικτύου πρόσβασης

27 26 Δρομολόγηση και μεταφορά πακέτων στο UMTS Ανάμεσα στο MS και το SGSN  Με το πρωτόκολλο PDCP Ανάμεσα στο SGSN και το GGSN  Με το πρωτόκολλο GTP χρησιμοποιώντας UDP/IP  Το GTP tunnel αναγνωρίζεται μοναδικά από ένα Tunnel ID (TEID) και την διεύθυνση του GSN (SGSN or GGSN) User Plane MS RF MAC RLC PDCP IP TCP/UDP APPL L1 L2 IP TCP/UDP APPL HOSTRNS RF MAC RLC PDCP ATM AAL5 IP TCP/UDP GTP-U Relay Function SGSN ATM AAL5 IP TCP/UDP GTP-U L1 L2 IP TCP/UDP GTP-U Relay Function GGSN L1 L2 IP TCP/UDP GTP-U IP L2 IP Relay Function

28 27 Υποστήριξη ποιότητας υπηρεσιών στο UMTS

29 28 Μηχανισμοί υποστήριξης ποιότητας υπηρεσίας Admission Control: Περιέχει πληροφορίες για τους υπάρχοντες και παραχωρηθέντες πόρους του δικτύου, και αποφασίζει αν υπάρχουν αρκετοί πόροι ώστε να υποστηριχθεί μια καινούργια αίτηση. Βασικός έλεγχος για ένα PDP Context στο SGSN, ενώ στα GGSN & UTRAN επιβεβαίωση δυνατότητας υποστήριξης του QoS για το PDP Context. Bearer Service Manager Συντονισμός σηματοδοσίας για την εγκαθίδρυση, μετατροπή και διατήρηση Ενός bearer service. Επικοινωνία με τις οντότητες admission & subscription control. BS-MT: Αιτήσεις για εγκαθίδρυση local bearer service; Μετάφραση UMTS QoS Χαρακτηριστικών σε αυτά του local bearer service. BS-SGSN: Αντίστοιχες λειτουργίες για την εγκαθίδρυση RAB,Iu, CN bearers. Συνεργασία με τις οντότητες στο UTRAN και το GGSN. BS-GGSN: Αντίστοιχες λειτουργίες για την εγκαθίδρυση CN bearers και τη διαλειτουργικότητα με τα εξωτερικά δίκτυα

30 29 Μηχανισμοί υποστήριξης ποιότητας υπηρεσίας Resource Manager: Διαχείριση δικτυακών πόρων βάση των χαρακτηριστικών του bearer. Υποστήριξη QoS με μηχανισμούς scheduling, bandwidth management, power control. Traffic Conditioner: Πιστοποίηση των χαρακτηριστικών μετάδοσης στις προδιαγραφές που έχουν οριστεί. Εκτέλεση traffic shaping & traffic policing. TC-MT: uplink TN-UTRAN & GGSN: downlink Packet Classifier: PC-MT: Εκχώρηση πακέτων από το local BS manager στο κατάλληλο UMTS bearer (DSCP, Transport layer Port number, security parameter index) PC-GGSN: Εκχώρηση πακέτων από εξωτερικό BS manager στο κατάλληλο UMTS bearer.

31 30 Κλάσεις και παράμετροι QoS Ορισμός κλάσεων βάσει: delay, bit rate, bit error rate, traffic handling priority requirements Conversational Class: Fixed resource allocation (like CBR in ATM) Παράδειγμα:Video telephony Streaming Class: Tolerance to a certain amount of delay variation (like VBR in ATM) Παράδειγμα:Video Downloading Interactive Class: Services requiring assured response times (scheduling priority) Παράδειγμα:E-commerce, Web Background Class: Best effort services (lowest priority) Παράδειγμα:file transfer, E-mail

32 31 Κλάσεις και παράμετροι QoS

33 32 PDP Context activation Ενεργοποίηση PDP Context με συγκεκριμένα χαρακτηριστικά QoS: (traffic class, transfer delay, traffic handling priority) Πολλαπλά PDP Context μπορούν να μοιράζονται την ίδια IP διεύθυνση Παροχή φίλτρου από το MS για κάθε PDP Context GGSN: χρήση φίλτρου για την απο-πολύπλεξη εισερχόμενων πακέτων στο σωστό PDP Context Χαρακτηριστικά φίλτρου:IP source, IP Dest, Port number, DSCP Ύπαρξη φίλτρου: MS & GGSN (unidirectional flows)

34 33 PDP Context Activation 1. Ενεργοποίηση εφαρμογής 2. Έλεγχος ύπαρξης PDP Context με παρόμοια χαρακτηριστικά QoS 3. I) Πολύπλεξη πακέτων στο υπάρχον PDP Context II) Εναλλακτικά τροποποίηση υπάρχοντος PDP Context III) Εναλλακτικά ενεργοποίηση “Secondary PDP Context” Secondary PDP Context: Κληρονομεί τα περισσότερα χαρακτηριστικά του “Primary PDP Context”. Εγκαθίδρυση νέου bearer (GTP Tunnel). Default PDP Context: Δεν σχετίζεται με συγκεκριμένη ροή πακέτων, και επιτρέπει τη μεταφορά πακέτων που δεν «ταιριάζουν» σε κάποιο από τα υπάρχοντα PDP Context να φτάσουν στο MS

35 34 Core Network QoS UMTS Packet Core Network = IP Network Δυνατότητες υποστήριξης QoS: 1) Χωρίς κάποια επιπλέον υποστήριξη (το δίκτυο κορμού δεν αποτελεί bottleneck) 2) ΑΤΜ based transport (εμπεριέχει μηχανισμούς υποστήριξης QoS) 3) Differentiated Services (marking points: RNC uplink & GGSN downlink)

36 35 Χρέωση - Ορισμοί

37 36 Χρέωση - Λογική Αρχιτεκτονική CGF: Distributed functionality in SGSN & GGSN or Centralized Network Element

38 37 Αρχές διαδικασιών χρέωσης Σε κάθε PDP Context εκχωρείται ένας μοναδικός προσδιοριστής για τη λειτουργία των διαδικασιών χρέωσης (charging ID) Οι μετρήσεις του όγκου δεδομένων που ανταλλάσσονται γίνονται ξεχωριστά για το uplink και το downlink Οι μηχανισμοί χρέωσης θα παρέχουν τη διάρκεια ενός PDP Context με πληροφορίες όπως ημέρα και ώρα Τα GSNs θα μπορούν να χειρίζονται χαρακτηριστικά χρέωσης που θα προμηθεύονται από τις πληροφορίες συνδρομής που βρίσκονται αποθηκευμένες στην HLR Τα SGSNs θα υποστηρίζουν τη χρέωση υπηρεσιών CAMEL

39 38 Συλλογή πληροφοριών χρέωσης Χρήση πόρων στη ραδιο-επαφή: amount of data uplink, downlink, QoS Διάρκεια χρήσης: Activation - Deactivation of PDP Context Χρήση γενικών πόρων του δικτύου GPRS & διαδικασιών διαχείρισης (π.χ., mobility management) Προορισμός και πηγή: Ο προορισμός καθορίζεται με την ακρίβεια του APN Χρήση εξωτερικών δικτύων: Δεδομένα που ανταλλάσσονται με εξωτερικά δίκτυα Τοποθεσία του κινητού: HPLMN, VPLMN, πληροφορίες τοποθεσίας μεγαλύτερης ακρίβειας (από τις διευθύνσεις SGSN, GGSN) SGSN: Συγκεντρώνει πληροφορίες για τη χρήση των ράδιο-πόρων GGSN: Συγκεντρώνει πληροφορίες για την επικοινωνία με εξωτερικά δίκτυα

40 39 Αρχές συλλογής δεδομένων χρέωσης Κάθε PDP Context δημιουργεί τα δικά του records (S-CDR SGSN, G-CDR GGSN Ένα SGSN μπορεί να στείλει προαιρετικά records σχετικά με τη διαχείριση κινητικότητας (M-CDR) To MS δημιουργεί records για το SMS Η αποστολή των records στο CGF εξαρτάται από διάφορες παραμέτρους (timer expiration, transferred data volume limit, routing area update, intra-inter handover) Η συσχέτιση των records από το SGSN και το GGSN για το ίδιο PDP Context γίνεται από το Charging ID Το RNC είναι υπεύθυνο να μετράει τον αριθμό δεδομένων που δεν στάλθηκαν στο κινητό (λόγω προβλήματος στη μετάδοση ή λόγω εκτέλεσης μεταπομπής)

41 40S-CDRS-CDR

42 41G-CDRG-CDR

43 42 The IP-Multimedia Subsystem (IMS) 19921993199419961997199819992000200120021995 GSMUMTS Rel 99Rel 4 Phase 1Rel 96Rel 97 Rel 98 Rel 5 GPRSUTRA IMS Phase 2

44 43 Basic Architecture (Phases 1 and 2) HOME Circuit domain GSM Radio

45 44 Εισαγωγή του GPRS HOME Circuit domainGSM Radio Packet domain

46 45 Εισαγωγή του UMTS HOME Circuit domainGSM Radio Packet domain UMTS Radio

47 46 Εισαγωγή του IMS HOME Circuit domainGSM Radio Packet domain UMTS Radio IMS

48 47 Στοιχεία του IMS UTRAN Home Serving PS domain IMS S-CSCF I-CSCF GGSN SGSN HSS P-CSCF MRF Other IP/IMS network Home Subscriber Server Call Session Control Function Multimedia Resource Function Supports and controls the multimedia sessions, providing the flexibility to add, modify or delete bearers used by the user’s services

49 48 Details of IMS S-CSCF I-CSCF GGSN SGSN HSS P-CSCF UTRAN MRF Other IP/IMS network Serving-CSCF: Performs the Session Control: handles the SIP requests and forwards them to the S-CSCF /external IP network of other end user. The S-CSCF might be specialized for the provisioning of a (set of) service(s). Proxy-Call Session Control Function: “first contact point” of IMS: located in the visited network, selects the I- CSCF of the Home Network of the user. Performs some local analysis (e.g. number translation, QoS policing,..) Interrogating-CSCF: “main entrance” of the home network: Selects (with the help of HSS) the appropriate S-CSCF. Multimedia Resource Function: Handles multiparty calls and conferences

50 49 Details of IMS S-CSCF I-CSCF GGSN SGSN HSS P-CSCF UTRAN MRF Other IP/IMS network BGCF MGCF R-SGW Legacy, PSTN IM-MGW T-SGW Legacy mobile signalling network Transport Signalling Many interworking functions and entities defined for interconnection with legacy networks (PSTN, GSM, GSM+GPRS, UMTS, etc.)

51 50 Details of IMS S-CSCF I-CSCF GGSN SGSN BGCF MGCF R-SGW HSS Legacy, PSTN IM-MGW T-SGW Mc P-CSCF Mc Cx Mm Legacy mobile signalling network UTRAN Transport Signalling MRF Other IP/IMS network Gi+Go Mw Mg Mw Mi Cx Mh Ms Gi Mk Mj

52 51 Principle of IMS procedures 1. Establishment of Transport Bearers and PDP context S-CSCF I-CSCF GGSN SGSN HSS P-CSCF UTRAN MRF Other IP/IMS network

53 52 Principle of IMS procedures S-CSCF I-CSCF GGSN SGSN HSS P-CSCF UTRAN MRF Other IP/IMS network 2. Discovery by GGSN of P-CSCF and UE request sent to P-CSCF 3. Contact I- CSCF in Home 4. IMS Registration and subsequent interactions between UE and S-CSCF and with external network(s)

54 53 Overview of Protocol Stack S-CSCF I-CSCF GGSN SGSN P-CSCF UTRAN SIP signalling User data

55 54 Overview of Protocol Stack PS domain transportBackbone transport IMS Signalling SIP IPv6 P-CSCFS-CSCF

56 55 Flows already defined  Registration (UE initiated) and de-registration (UE and network initiated)  Establishment of an IMS session in cases (different roaming scenarios plus PSTN or IMS initiated/terminated calls)  Session Release: initiated by UE, by CN (by P- or S-CSCF, by UTRAN – loss of radio- or loss of signaling PDP context), by PSTN  Call hold/resume, codec and media flow negotiations, addition of another media  Session redirection (6 different cases), session transfer (i.e. redirection after establishment)

57 Parlay/OSA: an open API for service development

58 57OutlineOutline 0- Introduction: the Parlay/OSA API: why, where, what? 1- A closer look at Parlay/OSA - Parlay/OSA Framework and Service Capability Features - Parlay/OSA current functionality 2- The Parlay/OSA Framework - Framework functionality - How does it work? 3- Example Parlay/OSA applications

59 58OutlineOutline 4- Parlay/OSA standardisation - Bodies involved in Parlay/OSA standardisation - The Joint API Group 5- The next Parlay/OSA release 6- Summary, contacts

60 59OutlineOutline 0- Introduction: the Parlay/OSA API: why, where, what? 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

61 60 The Parlay/OSA API: Why? (1/2) A change in business models has introduced new players in the telecom business User New Player services connectivity Operator connectivity Some want to address users directly User New Player connectivity + services Operator connectivity Some prefer to do it via the Network Operator But they have something in common: They compete in the services market... and they have no network!

62 61 The Parlay/OSA API: Why? (2/2) This is a win-win situation! - It opens new sources of revenue for incumbent Network Operators - traffic in their networks increases - they may enrich their service offering - It opens the telecom business to newcomers - VNOs, MVNOs, ASPs,... So we only need a technical enabler: Parlay/OSA

63 62 Services/application layer Control layer Service Capability Servers Connectivity layer Core & Radio Networks 2G 2.5G & 3G Core network Service network OSA/Parlay API’s exposing network service capabilities Distribution via middleware Parlay / OSA The Parlay/OSA API: Where? (1/2)

64 63 The Parlay/OSA API: Where? (2/2) SIP AS IM SSF CAMEL App CAP S-CSCF ISC OSA SCS OSA Service OSA HSS ISC Cx MAP Sh The UMTS Example

65 64 The Parlay/OSA API: What? (1/2) Parlay/OSA (Open Service Access) is an API that enables operator and 3rd party applications to make use of network functionality through a set of open, standardised interfaces Parlay/OSA API OSA Gateway Mapping to network specific protocols Network Network complexity hidden from applications App1App2 AppN Applications (independent of underlying network technology) 3GPP ETSI Parlay JAIN

66 65 The Parlay / OSA API: What (2/2) Opening up of network by means of standardized APIs based on open technology. This leads to :  Shorter TTM for applications / services due to abstraction and open technology (developer community orders of magnitude larger than telco developer community)  Applications can also be developed and deployed by 3rd parties (creative, new innovative services).  Applications can be network independent (multi-access / multi-service)  Applications can be combination of – different capabilities – enterprise data with network functionality leading to new innovative services.

67 66OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA - Parlay/OSA Framework and Service Capability Features - Parlay/OSA current functionality 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

68 67 Parlay/OSA Terminology: SCSs and SCFs - The Parlay/OSA Gateway consists of several Service Capability Servers (SCS): functional entities that provide Parlay/OSA interfaces towards applications. SCF SCS Interface Each SCS is seen by applications as one or more Service Capability Features (SCF): abstractions of the functionality offered by the network, accessible via the Parlay/OSA API. Sometimes they are also called services - Each SCS is seen by applications as one or more Service Capability Features (SCF): abstractions of the functionality offered by the network, accessible via the Parlay/OSA API. Sometimes they are also called services - The Parlay/OSA SCFs are specified in terms of interface classes and their methods

69 68 Parlay/OSA = Framework + A Set Of SCFs framework User Location Call control HLR CSE ---- Servers E.g. Location server Billing server Service capability servers interface class OSA API ApplicationApplicationserver Not standardized OSA Internal API One of the Parlay/OSA SCSs is called the Parlay/OSA Framework, and is always present, one per network

70 69OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA - Parlay/OSA Framework and Service Capability Features - Parlay/OSA current functionality 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

71 70 Basic Parlay/OSA SCFs Note 2: Not part of 3GPP OSA Release 4 Note 1: Multimedia and Conference Call Control not part of 3GPP OSA Release 4

72 71OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework - Framework functionality - How does it work? 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

73 72 The Parlay/OSA Framework Registered Services Client Application Framework CallControlMobilityetc 1 3 SCF registration - SCF registration - support of multi-domain control of access to the network - control of access to the network - integrity management - discovery of network functionality 4 Enterprise Operator Application subscription - Application subscription to services 2 2

74 73OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework - Framework functionality - How does it work? 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

75 74 How does the FW work ? Application Framework Service / SCS 1: authentication 2: request Registration interface 3: register factory 4: authentication 5: request Discovery interface 6: discover Service 7: Select Service + sign SLA 8: create Service Manager 9: return Service Manager 10: return Service Manager 11: Use service

76 75OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework - Framework functionality - How does it work? 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

77 76 The user dials in to the application to access information, traffic traffic weather, weather, stocks, stocks, etc etc via voice. Information Application

78 77 The Application registers to the Framework The Framework starts a suitable Call Manager, and passes a reference to the application Information Application : interaction flow before traffic

79 78 User calls service number SCS checks subscription to service Information presented to user via UI SCS Application charges subscriber (either via Charging API, or indirectly via CC API) Information Application : interaction flow during traffic

80 79 This is an example of combination of enterprise data with network capabilities Location Service Bank services Location services Leisure News

81 80 Location Service The idea is that the user is able to find out the nearest ATM machine Directions From To ATM Bank Police Default

82 81 Location service

83 82 The terminal interacts via WAP with application, selects ATM location option The application invokes ‘userLocationRequest’ method, gets response The application produces suitable map (including term.caps from WAP GW), provides this to terminal Location service: interaction flow during traffic

84 83 The application allows user to access all his messages. This is an example of combination of information in different business domains Unified messaging application

85 84 The user sets messaging preferences (private and corporate combined if desired) via Web/WAP (or via voice recognition) Notifications of different messages, plus actions, are handled by the application Unified messaging application: interaction flow

86 85OutlineOutline 0- Introduction 1- A closer look at OSA 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation - Bodies involved in Parlay/OSA standardisation - The Joint API Group 5- The next Parlay/OSA release 6- Summary, contacts

87 86 Bodies Involved In Parlay/OSA Standardisation OSA specification and standardisation is a joint effort by the following bodies: - 3GPP CN5 - ETSI SPAN12 - ITU-T SG11 (only ref. document) - The Parlay Group The objective is to have a single API for the whole developer community

88 87 OSA (Parlay) In 3GPP 3GPP Services Architecture +coordination SecurityCodec Telecom mgmt... SIP CAMEL OSA OSA stage 1: requirements OSA stage 2: architecture Services and System Aspects (SA) Terminals (T) Radio Access Network (RAN/GERAN) Core Network (CN) OSA stage 3: protocols

89 88 - ETSI SPAN (Services and Protocols for Advanced Networks) was re-organized - The group ETSI SPAN12, Application interfaces for service providers and network operators, was created - An activity in ETSI SPAN14, called Service Provider Access Requirements (SPAR), was also created - ETSI SPAN12, aware of the identical scope of the work in 3GPP CN5, agreed to work jointly and make all meetings joint meetings - Today ETSI SPAN12 has an OSA Project, part of the Joint API Group and working also on OSA/Parlay Compliance OSA (Parlay) In ETSI

90 89 OSA/Parlay In ITU-T - ITU-T SG11 has defined a Question 4 called API/Object interface and architecture for signaling, “covering the interface between network control and application layers” - ITU-T has decided to write a reference document for this activity, and delegate the contents to other bodies - This way ITU-T will adopt OSA specifications by ETSI (+3GPP +Parlay) - ITU-T SG11 draft document is called TD 1/11-25

91 90 Parlay (OSA) In The Parlay Group - The Parlay Group (www.parlay.org) started in March 98, and today is an open, multi-vendor forum with around 50 members from the IT and Telecom business - The Parlay Group aims to create open, technology independent APIs which enable developing applications across multiple networks (=OSA!); and to accelerate the adoption of these APIs and promotes their use and standardisation. - Technical work in the Parlay Group is done in Work Groups; the Parlay WGs have joined the 3GPP+ETSI OSA (Parlay) joint group to develop together a single API

92 91OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation - Bodies involved in Parlay/OSA standardisation - The Joint API Group 5- The next Parlay/OSA release 6- Summary, contacts

93 92 Today’s Parlay/OSA Joint Activities - Today 3GPP, ETSI and Parlay have joined forces to specify a single API for the whole developer community - Requirements coming from the three participating bodies are taken into account: - 3GPP requirements from SA1 and SA2 - ETSI requirements from SPAN14 SPAR - Parlay requirements from the Parlay Group - All meetings are joint meetings - The joint work is (UML) based on a common model, http://docbox.etsi.org/tech-org/span/open/span12/UML/ Then each body generates its own document format

94 93 PSTN/ISDN OSA (Open Service Access) UMTS OSA (Open Service Access) API’s for Open Service Access; ONE API for ONE developer community Joint API Group Current Workflow Reference in ITU-T Roadmap JAIN 1.) Requirements introduced by individual bodies 2.) create the API that supports the superset of all requirements. (Joint meetings) 3.) Results are transferred back to individual bodies

95 94 Joint Work Synchronization 20012002 1Q1Q2Q3Q4Q2Q3Q4Q Parlay ETSI 3GPP Release 4 Release 5 2.1 4.04.14.2 1.0 3.03.1 4.3No further changes accepted 4.0 2.0 5.05.15.25.3 1.1 = point of alignment between specifications

96 95 Alignment and backwards compatibility - The current last versions of the three bodies are fully aligned 3GPP Rel4  ETSI Ver1  Parlay 3 - None of them is backwards compatible with any of its previous releases/versions, due to changes based on feedback from implementers - From now on backwards compatibility is a must

97 96 The Parlay/OSA API is contained in two sets of documents: - The API specification in terms of interfaces and their parameters (UML description and IDL specification), sequence diagrams and state models - The Mapping specification of the Parlay/OSA API and network protocols : a possible, informative mapping from the API to various network protocols (i.e. MAP, CAP,..) 3GPP Parlay/OSA Rel4 Document Structure (1/2)

98 97 Parlay/OSA Document Structure (2/2) The specification is in turn contained in the following documents: - 3GPP : TS 29.198 /12 parts (API) + TR 29.998 (Mapping) http://www.3gpp.org/ftp/Specs/2001- 12/Rel4/29_Series - ETSI : ES 201 915 (API) + TR 101 917 (Mapping) http://docbox.etsi.org/tech-org /span/Open/Span12/osa.html - Parlay http://www.parlay.org/specs/index.asp Choose your favorite: all are aligned!

99 98OutlineOutline 0 - Introduction 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts

100 99 Ongoing Work for Parlay/OSA Based on requirements from all the bodies in the joint activity, Parlay/OSA is enhanced with: 03/02: - MM Call Control evolution - Presence Service - Policy Management 07/02: - Retrieval of Network Capabilities - Information Services - User Profile Management - Journalling... plus enhancements in the existing SCFs

101 100OutlineOutline 0- Introduction 1- A closer look at Parlay/OSA 2- The Parlay/OSA Framework 3- Example Parlay/OSA applications 4- Parlay/OSA standardisation 5- The next Parlay/OSA release 6- Summary, contacts