Understanding MExE and Reconfigurability in Mobile Services

1. MEXE

2. Outline • 2G and 3G Services • What is MExE ? • Example MExE services • MExE functionality • MExE security • MExE secure transfer • MExE timetable and summary

3. 2G mobile services • • core network supplementary services (e.g. call forwarding, call barring, call diversion etc.) • • limited, expensive to develop, difficult to deploy • • all operators with same bland standardised services • • little scope for operators to differentiate • • tariffs are principle differentiators

4. 3G mobile multimedia • mobile phones fully internet integrated • –internet and multimedia services, on the move • – by 2005 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

5. Services toolkits in 3G networks

6. MExE Overview • standardised execution environments in a mobile phone • WAP • PersonalJava • CLDC/MIDP Java • 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.

7. MExE Service Scenarios

8. MExE Architecture

9. Example MExE Device

10. Example MExE services

11. Example MExE services

12. Example MExE Services

13. Example MExE Services

14. Example MExE Services

15. Example MExE Services s

16. MExE Functionality

17. MExE Functionality

18. MExE Functionality

19. MExE Functionality

20. MExE Functionality

21. MExE Summary

22. Reconfigurability

23. Outline • Why Reconfigurabillity? • Reconfigurability Perspective • Road-map • Main challenges for Reconfigurability implementation • Synthesis

24. Various service profiles Complexity for profile interpretation, policy enforcement, protocol download etc. Various user profiles Reconfigurability/adaptability management Ubiquitous Service provision SP Service SP Service Provider Various service providers Network Various access and network capabilities Various terminal profiles Why Reconfigurabillity?

25. Reconfigurability & Adaptability- Key Enablers of systems integration and advanced service provision for 3G/4G Reconfigurability/Adaptability Internet 4G 2G 3G

26. Reconfigurability Perspective Current Status • Service provision in 2G networks has been mainly based on voice services • “Closed” business model support • Limited operator differentiation • Limited set of offered services • Mobile service provision is facing important advancements • “Re-configurability is a concept that embraces advanced new capabilities in service provision and support and extends them to cover more challenging possibilities including the reconfiguration of mobile terminal capabilities, the dynamic adaptation of the communication protocol stacks or even the re-definition of the physical layer of the PLNM”

27. Reconfigurability Perspective Beyond 3G • Support for flexible business models with novel dynamic services • Convergence towards an IP-based core network and ubiquitous, seamless access between 2G, 3G, broadband and broadcast wireless access schemes, augmented by self-organizing network schemes and short range connectivity between intelligent communication appliances • 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.

28. 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

29. Main challenges for Reconfigurability implementation • Flexible service provision: • Reconfigurability management • Policy provision • Profile management • Protocol/software download • Adaptable service deployment • Open APIs • Reconfigurable charging models • Flexible QoS and security schemes

30. Main challenges for Reconfigurability implementation • Radio resource management: • Handover management procedures • Mobility management • Dynamic and flexible spectrum management • User perspective: • User requirements • User interactions with the SDR terminal • User anonymity and profile management • Re-configurable and value added service provision

31. Main challenges for Reconfigurability implementation • System level issues: • Generic architectures for flexible service provision and reconfigurability management • Network reconfiguration mechanisms and applications • Hierarchical and decentralized networkarchitectures • Terminal re-configuration procedures • Interactions betweenterminal and network • Novel signaling mechanisms • Distributed processing • Adaptiveprotocols • SW downloading and impact on traffic

32. Main challenges for Reconfigurability implementation • Enabling technologies: • Adaptable service provision environments • Reconfigurability control middleware • Software download and repository techniques • APIs definition • Applications enabling network recofiguration features • Re-configurable baseband SW architecture • Re-configurable signal processing algorithms • Adaptive air-interfaces • Novel HW-SW co-design methodologies • Resource management

33. Issues for Reconfigurability • Requirements analysis from user/operator/service provider/regulator points of view • Identification of generic architectures and middleware for the support of flexible service provision and reconfiguration management • Identification of protocol adaptability mechanisms • Identification of protocol/software downloading procedures • Identification of supporting network/terminal reconfiguration mechanisms • Research integration on enabling technologies and identification of solutions to all bottlenecks • Identification of technology concepts applicable to reconfigurable environments, e.g., CORBA (Wireless CORBA), JAVA-RMI, JINI, (Mobile) Agents etc.

34. Conformance Provider 1 1 1..n 1..n 1 1 1..n 1..n 1..n 1..n 1..n 1..n 0..n 0..n 0..n 0..n 1..n 1..n 1..n 1..n Implementation Provider Specification Provider Reconfigurability Provider 1 1 0..n 0..n Reconfigurability User Reconfigurability business model • Independent software vendors • Develops implementations for a particular functionality as defined by a specification • Standardisation bodies • Publishes functional specifications • Authoritative bodies • Ascertains conformance of implementations • Reconfigurability providers • Orchestrates the reconfigurability process • Reconfigurability users • End users • Network operators • etc

35. The reconfigurability process • Identification of context • Spatially scope the technological surrounding of the requesting entity by identifying affected elements in the communication and computing infrastructure • Identification of feasible alternative solutions • Capability exchange and negotiation procedure under a specific policy (e.g., maximise system features) • Decision on solution and respective implementation • Take into account generic (e.g. user) preferences alongside with strictly technical considerations (type-checking) • Physical deployment of solution • Reserve necessary resources then download and install solution • Activation of solution

36. SDR Forum – Architecture of CCL/ITRI SDR software framework

37. SDR Forum – Use case diagram of SDR core framework

38. Standardisation activities for open service access ·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).

39. OSA

40. OSA

41. OSA - Application Programming Interface Option 1A Option 1B

42. OSA - Application Programming Interface (2) Option 2 Option 3

43. Open Services Gateway initiative

44. 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

45. UMTS Service Architecture

46. Mapping of SCFs to Release 2000 Network Architecture

47. Requirements for Flexible Service Provision in 3G systems and beyond • Flexible business models • Dynamic service registration, deployment and update by Value Added Service Providers (VASPs) • Dynamic user registration • Advanced Service discovery - based on various parameters, e.g.: • Terminal capabilities • User profile and location • Service profile • Charging, Accounting and Billing (CAB): • Support of flexible charging/accounting models • Provision of single bill to end user for all consumed VASs • Profile interpretation:User, Terminal, Service, Security • Identification of network/terminal capabilities • Support downloadability • Support for QoS • Support for secure service usage

48. Basic Requirements for Reconfigurability in 3G and beyond • Support for flexible business models with novel dynamic services • Dynamic reconfiguration based on profiles (e.g., user, terminal, service), service provision requirements • Dynamic reconfiguration based on MT/access/network capabilities • Dynamic reconfiguration based on policy provision (charging, QoS etc.)

49. Applications enabling reconfigurability management • Applications supporting reconfigurability and flexible service provision: • reconfigurability management/control • adaptability enablers • Applications enhancing network functionality/ capabilities/ interoperability/ management • Applications enhancing/optimising terminal functionality/capabilities • Adaptable Services

50. Business model for flexible service provision through Service Provision and Reconfigurability Middleware Provision of portal reference Business level relationship Portal access control for VAS provision Third Trusted Party/HE-VASP Domain Service Provision and Reconfigurability Platform Provider Value-added Application/ Service/Application User User Retailer Service Provider Provider (U) (U) (R) (SAP) (VASP) Mobile network operator Access Provider Network Access Provider (AP) (NAP)