Δρ. Νάνσυ Αλωνιστιώτη nancy@di.uoa.gr

1. Επιχειρηματικά μοντέλα σε δυναμικά αναπροσαρμοζόμενα δίκτυα και υπηρεσίες(Reconfigurability / adaptability) Δρ. Νάνσυ Αλωνιστιώτη nancy@di.uoa.gr

2. Outline • Εισαγωγή σε βασικά επιχειρηματικά μοντέλα • Απαιτήσεις για ευέλικτη παροχή υπηρεσιών στις κινητές επικοινωνίες 4ης γενιάς • Reconfigurabillity/Adaptability – Γιατί; • Road-map • Διαδικασίες Τυποποίησης για «ανοιχτή» πρόσβαση σε υπηρεσίες • OSA, OSGi, MEXE

3. UMTSκαι παροχή προηγμένων υπηρεσιών

4. Βασικό Επιχειρηματικό Μοντέλο στις Κινητές Επικοινωνίεςσήμερα Service/Application Provider Retailer (R) Mobile network operator Access Provider User User Network Access Provider (AP) (U) (U) (NAP) • Η παροχή υπηρεσιών στις κινητές επικοινωνίες 2ης γενιάς βασίζεται κυρίως σε υπηρεσίες φωνής • Υποστήριξη «κλειστών» επιχειρηματικών μοντέλων • Περιορισμένη διαφοροποίηση των παρόχων • Παροχή περιορισμένου συνόλου υπηρεσιών • Προβλήματα στην ενσωμάτωση νέων επιτευγμάτων στο χώρο της παροχής υπηρεσιών

5. Βασικό Επιχειρηματικό Μοντέλο στο Ιντερνετ Network operator Service/Application Provider Access Provider User User Retailer Internet Provider (AP) (U) (U) (R) • Αρκετή ευελιξία στην εισαγωγή και παροχή νέων υπηρεσιών και περιεχομένου • Δυναμική ανακάλυψη και εγγραφή σε υπηρεσίες

6. Σύστημα επικοινωνιών 4ης γενιάς HAPS Satellite Wireline or Wireless Networks (Internet) GSM Bluetooth WLAN UMTS Content ADSL Services OFDM Unspecified TDMA FDD WCDMA TD-CDMA OFDM TDD Direct Sequence Frequency Hopping Very wide area Wide area Metropolitan area Local area Personal area

7. Απαιτήσεις για ευέλικτη παροχή υπηρεσιών στις κινητές επικοινωνίες 4ης γενιάς • Υποστήριξη ευέλικτων επιχειρηματικών μοντέλων • Σύγκλιση των κόσμων του Ιντερνετ και των Κινητών επικοινωνιών • Απρόσκοπτη πρόσβαση (μέσω οποιουδήποτε συστήματος) σε υπηρεσίες (multimedia, content rich, downloadable services) • Δυναμική ανακάλυψη και χρήση υπηρεσιών από τους χρήστες • Ευέλικτα μοντέλα χρέωσης • Ασφάλεια και προστασία του χρήστη καιτων IPR του παρόχου της υπηρεσίας • Υποστήριξη ποιότητας υπηρεσίας

8. Βασική σύγκλιση επιχειρηματικών μοντέλων Service/Application Provider Retailer (R) User User (U) (U) Mobile network operator Access Provider Network Access Provider (AP)

9. Ανοιχτή πρόσβαση και παροχή υπηρεσιών στις κινητές επικοινωνίες - Σχέση με νέα επιχειρηματικά μοντέλα • 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. Combining Telecom & Datacom The developer community is out there

10. Complexity for profile interpretation, policy enforcement, protocol download etc. Various user profiles Reconfigurability/adaptability management, Ubiquitous Service provision Network Various access and network capabilities Various terminal profiles Reconfigurabillity/Adaptability – Γιατί; Various service/application profiles SP Service SP Service/application Provider Various service/application providers

11. Απαιτήσεις για την εισαγωγή δυναμικά αναπροσαρμοζόμενων δικτύων και υπηρεσιών • Support for flexible business models with novel dynamic services • Convergence towards an IP-based core network and ubiquitous, seamless access • Dynamic service registration, deployment and update by Service Providers (SPs) • Dynamic user registration • Support for QoS, flexible security schemes • Support for flexible charging/accounting models • Advanced profile management (user/service/network/terminal/charging/security) • Context aware and adaptable service deployment • Advanced Service discovery - based on various parameters, e.g.: • Terminal capabilities • User profile • Service profile • Location etc. ADAPTABILITY Dynamic reconfiguration/adaptation based on: profiles, service provision requirements MT/access/network capabilities policy provision (charging, QoS etc.) context information (e.g., terminal, network, user preferences and status RECONFIGURABILITY

12. Τι είναι η δυναμική αναπροσαρμογή • Η δυναμική… • δημιουργία στιγμιοτύπων, • παραμετροποίησηκαι • διασύνδεση • λειτουργικών οντοτήτων (π.χ. protocol instances) στα επίπεδα • χρήστη, • ελέγχουκαι • διαχείρισης, • ενός συστήματος επικοινωνιώνμε τρόπο • διαχειρίσιμο, • ακέραιο και • διαφανή

13. Δυναμική αναδιαμόρφωση και προσαρμογή δικτύων και υπηρεσιών Application/Service Downloadable parts/versions Application/Service registration, adaptation negotiation Open APIs APIs N + 1 Local Reconf Management Protocol Repositories N Communication Standard N - 1 N + 1 Reconfiguration/Adaptation Management Plane Local Reconf Management Context repository N N - 1 N + 1 Local Reconf Management Reconfigurability Classmark N N - 1 Protocol layers

14. Static Spectrum Allocation Limited SpectrumSharing Dynamic and Flexible Spectrum Allocation Regulation 2005 2010 2000 Adaptable, ubiquitous service provision Flexible, reconfigurable service provision Services Limited, static Road-map Terminal, networks, services and regulation evolutions Medium Term Long Term Terminals 1-Mode(Multiband) 2G/3G DualMode Fully Software Definable Composite Multimode Circuit Switched PacketSwitched Convergent, reconfigurable Networks Self Organising

15. Ερευνα-Τυποποίησηστη περιοχή του Reconfigurability και ευέλικτης παροχής υπηρεσιών • IST FP5 projects: • TRUST • SCOUT • CAST • MOBIVAS • IST FP6: • E2R • Standardisation: • SDR Forum • 3GPP, OSA/Parlay, MEXE • W3C • ETSI • IETF • OSGi • κλπ

16. Services toolkits in 3G networks

17. Διαδικασίες Τυποποίησης για «ανοιχτή» πρόσβαση σε υπηρεσίες ·Parlay. Parlay is an object-oriented API, developed by the homonymous industry forum, that provides independent software developers access to a selected range of network capabilities, abstracted by the so-called Service Capability Features (SCFs). Currently specified SCFs (in Parlay version 4.0) include interfaces for call control, retrieval of user location and status, terminal capabilities and user presence and availability information, content-based charging, policy-based management and others. Security issues regarding access to these SCFs (e.g., authentication, authorization and access control) are controlled in a unified way by an entity called the Parlay Framework, which acts as the first contact point for Parlay clients. Parlay interfaces are independent of particular hardware platforms, operating systems, programming languages as well as of network technology. ·OSA. OSA (Open Service Access) is a 3GPP specification that provides an API for the particular case of 3G mobile networks. OSA was from its origins largely based on Parlay. Since late 2001 both specifications are fully aligned and the future versions of both interfaces are jointly developed by 3GPP and the Parlay group. ·JAIN.JAIN (Java APIs for Integrated Networks) is a set of Java APIs that aim to enable the rapid development of next generation telecommunications services on top of the Java platform. The JAIN family of specifications is divided into Protocol APIs¸ which define interfaces to wireline, wireless and IP signalling protocols (e.g., TCAP, ISUP, MAP, SIP) and Application APIs that specify APIs required for creating end-user services. A Java version of the Parlay APIs, called JAIN Service Provider API (SPA) [10] has been included in the latter category, together with other APIs that such as the definitions of a server-side service execution environment, called JSLEE (JAIN Service Logic Execution Environment) as well as of a service creation environment (SCE).

18. Parlay/OSA API: Σχέση με νέα επιχειρηματικά μοντέλα connectivity User Operator Some want to address users directly Some prefer to do it via the Network Operator services connectivity New Player connectivity+ services User Operator connectivity But they have something in common: New Player They compete in the services market... A change in business models has introduced new players in the telecom business and they have no network!

19. Parlay/OSA API: Σχέση με νέα επιχειρηματικά μοντέλα 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, ... Parlay/OSA Τechnical enabler:

20. OSA

21. Parlay/OSA Framework 1 4 3 - control of access to the network - integrity management - discovery of network functionality Client Application 2 2 Registered Services EnterpriseOperator Framework Call Control Mobility etc - Application subscription to services - SCF registration - support of multi-domain

22. OSA - SCS

23. UMTS Service Architecture

24. Mapping of SCFs to Release 2000 Network Architecture

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

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

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

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

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

30. Location service

31. Location service: interaction flow during traffic • The terminal interacts via WAP with application, selects ATM location option • The application invokes ‘userLocationRequest’ method, gets response • The application produces suitable map, provides this to terminal

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

33. Unified messaging application: interaction flow • 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

34. Open Services Gateway initiative

35. OSGi mission With OSGi, high-value services may be dynamically loaded over a wide-area network, and accessed through a Services Gateway in a home, office, vehicle, or mobile device. Applications enabled by OSGi include: Services in the Car: Services in the Home: • Information/Entertainment • Communication • Energy Management and Metering Appliance • Diagnostics and Servicing • Safety and Security monitoring • Telemedicine and healthcare monitoring • Vehicle diagnostics • Emergency assistance • Mobile commerce • Navigation • Location-based services • Information/entertainment

36. MEXE - 3G mobile multimedia • mobile phones fully internet integrated • – internet and multimedia services, on the move • – by 2009 more people will be interacting with the WWW via wireless devices than traditional computers (!?) • • operator and third party multimedia services • • generally no services standardised, but enabled using 3GPP services toolkits (e.g. services toolkits (e.g. MExE MExE, CAMEL, USAT, OSA) and IP/IT toolkits) • • new personalised multimedia services rapidly developed to differentiate from competitors

37. MExE Overview • standardised execution environments in a mobile phone • WAP • PersonalJava • CLDC/MIDP Java (Connected Limited Device Configuration, Mobile Information Device Profile ) • Applicable to 3G, non-3G, cordless and fixed environments • IT/IP multimedia services running on mobile phones • write once, execute on many mobile phones • transfer of multimedia services • up/downloading, network/3rd party, MExE-to-MExE services • standardised negotiation of capabilities with servers • i.e. device type, screen size, memory, bearers etc.

38. MExE Service Scenarios

39. MExE Architecture

40. Example MExE Device

41. Example MExE services

42. Example MExE services

43. Example MExE Services

44. Example MExE Services

45. Example MExE Services

46. Example MExE Services s

47. MExE Functionality

48. MExE Functionality

49. MExE Functionality

50. MExE Functionality