Transcript Multiservice provision in wireless mobile environments

Multiservice Provision in
Wireless Mobile Environments
MSc Nataliya German (COMAS Graduate School)
MSc Dmytro Zhovtobryukh (InBCT Project)
[email protected], [email protected]
University of Jyväskylä
Department of Mathematical Information Techonology
Multiservice Provision in
Wireless Mobile Environments
Different Kinds of
Mobile Services
Mobile Users




Different Demands
Different Abilities
Different Devices
…
Different Wired
Network Services
Allowed for
Mobile Users
Multiservice
Management
System
Communication
Network





Huge Amount of Content
Heterogeneity
Distributed Architecture
Concurrency
…
Future situation:
• Many types of services
• Huge amount of content
• High level of activity
• Concurrency between services
• Different users (preferences, devices, communication lines, allowed
services, etc.)
Multiservice Provisioning
System Architecture
Multiservice Provisioning System
GW
Control Service Network
SR
Internet
SR
SCP
SR
SCP
SR – Service Repository
LSR – Local Service
Repository
SCP – Service Control Point
RNC – Radio Network
Controller
GW – Gateway
LSR
SCP
RNC
LSR
RNC
GSM
SR
SCP
LSR
RNC
WLAN
GPRS
Design Goals









Flexibility
Extensibility
Re-configurability
Scalability
Service Mobility
User Mobility
Heterogeneous Data (Services) Integration
Adaptive Communication
Deregulated Access
Design Perspectives

Transaction management perspective:
the designed architecture must provide the base for
construction/implementation of efficient transaction processing
scheme that can solve existing transaction management problems;

Communication network perspective:
the designed architecture must support the mechanisms for dealing
with different communication network types specifics (user
mobility, frequent disconnections, network domain infrastructure,
etc.);

Service management perspective:
the designed architecture must enable possible differentiation of
services to be provided with respect to concrete user preferences.
Concrete Tasks

Existing Architectures Overview

Classification of Services for Mobile Users

Classification of Mobile Users

Difference between Communication Networks

User-Service Data Flows Analysis
Concrete Tasks

Bottlenecks in Wireless Networks

Conflicts and Concurrency

System Architecture Design

Data Organization Design

Requirements to Services to be Provided

Analysis of Approaches and Techniques for
Development
Relevant Research Areas and
Topics of Study

Mobile Service Management




















Ontologies
Intelligent Agents
DTD – Document Type
Definition (XML-encoded service
definition)
Mark-Up Languages (XML, RDF,
RDFS, DAML-S, OIL)
Intelligent Information
Integration
Multidatabase Systems

Mobile Internet
Mobile Intelligent Networks
E-commerce Systems
(+Mobile)
Metadata, Semantic Web

Next Generation Networks


Mobile Internet Protocols
Middleware
Service Architectures
Service Categories
Service Filtering Mechanisms
Personalization
Billing and Accounting
Security
Business Models

Heterogeneous Data
Integration
Distributed Database
Management
On-Line Analytical Processing
Data Warehousing
Mobile Transaction
Management
Existing Architectures Overview
Next Generation Networks(NGN)
NGN is mobile intelligent network
concept deriving intelligence from
the following properties:
Open Service Architecture
 Softswitches and Distributed Network
Intelligence
 IN/IP Convergence
 NGN Signaling
 Intelligent OSS/BSS Systems

Next Generation Networks(NGN)
Intelligent Transport and Routing
 Embedded Software and Smart Cards
 Intelligent Agent Technology
 Smart Antenna Systems
 Advanced and Value-added Services
 Personalization
 Ad-Hoc Networking

Service Management
Architectures Analysis

Intelligent Network Architecture (Lucent
Technologies)


Converged Service Model (Pelago Networks)


low-cost switching (softswitches, converged service
nodes)
Parlay


centralized service management system
open and technology-independent that allows hosting
applications outside specific networks
Virtual Home Environment

provides personalized service portability across
network boundaries and between terminals
Service Management
Architectures Analysis

Intelligent Service Architecture (IBM)


An Open Service Architecture for Adaptive
Personal Mobile Communication (Ericsson)


network nodes are designed to be as self-configuring,
self-managing, self-diagnosing as possible
intelligent agent-based system implementing shared
service knowledge
Integrated Generic Architecture for Flexible
Service Provision to Mobile Users (University of
Athens, Greece)

3G-core network based re-configurable architecture
Service Architecture Evolution
Trends







OSA convergence (public interfaces)
Service portability
Terminal and location independence
Distributed service execution
End-to-end service negotiation
Shared service knowledge introduction
Service export/import to/from other
networks/Internet
2G (GSM) Service Architecture







Mobile device authentication: HLR
location report
Circuit switching of radio channels
SMS is limited packet data service
Services are mutually exclusive
Internet access via WAP GW only
Restricted WML support
No asynchronous applications
2.5G (GPRS, EDGE)






Mobile device authentication: Gateway
GPRS Support Node (GGSN)
IP addressing of mobiles by GGSN
Traffic differentiation
Support for CS GSM and PS GPRS
Data transfer reliability and radio
efficiency
Operator’s multimedia services
2.5G: JAIN SIP




Session Initiation Protocol (SIP) belongs
to JAIN API family
SIP server is used to setup multimedia
communication between end-points
Parlay-API can be added to SIP server
to execute servlets on a web server
Scripted mobile code can be sent for
execution to application client
2.5G: Parlay






Parlay API is based on CORBA interfaces
Allows hosting applications outside
specific networks while accessing
network resources
Relies upon operator-installed gateways
Open and techology-independent
Requires synchronization between
application client and server
Services can move only within Parlay
domains
2.5G: Parlay Architecture
HTTP
HLR
NEs
Mobile
Network
SCP
Web
Browser
Network Security
Boundary
Service Provider
Domain
NEs
PSTN
Corba Interfaces
Parlay App
ParlayGW
ParlayGW
Web
Server
Application
Server
IP Network
ParlayGW
IIOP
PARLAY logic
layer
Internet
CORBA
Naming
Service
SIP API
SIP
Server
Parlay
APIs
NEs
servlet
SIP mediated
(multimedia) session
Media
Server
Client
Mobile Device
Network
3G Phase 1 (UMTS)




Mobile device authentication: combined
Support GPRS Support Node (SGSN)
and GGSN
IP addressing by combined SGSN/GGSN
Real-time and isochronous multimedia
over wireless end-to-end connectivity
Services are platform-unique and
cannot be exported/imported to/from
Internet
3G Phase 1:VHE

Virtual Home Environment(VHE) provides




service portability accross network
boundaries
UI personalization
location-independent access to services
For UMTS VHE consists of



GSM services
Roaming principles
Service capabilities
Virtual Home Environment
Architecture
GSM Services
Teleservices
Supplementary
Services
System Features
(Location Update,
Authentication, etc.)
Service Capability based Services
Bearer
Services
(CS, PS)
Service
Capability
Features
Standardized Interfaces

Service Features
    
GSM UMTS CAMEL MExE SAT
Bearers
Mechanisms
Service Capabilities
3G Phase 2



Mobile device authentication and IP
addressing: integrated SGSN and GGSN
(IGSN) sends information to AAA-server
and HLR
Services are negotiated end-to-end,
also outside the service network
Necessity of dynamic restoring service
shared knowledge inside mobile device
4G





Public locations provide broadband
Internet access and are equipped with
WLAN extensions
High bandwidth (up to 11 Mbps)
High scalability due to mobility
mechanisms (Mobile-IP, IPv6)
No traditional subscription for Internet
access (e.g.E-Cash)
Third party services without intervention
of network operator
Internet Service Architectures

Universal Plug & Play (UPnP) and JINI




enable devices use each other’s services dynamically
JINI uses a server; UPnP relies upon a control point,
co-located with the resource
Registration of profiles and resources, and event
services
Tuple Spaces


Devices and resources share common application
knowledge
Special tuple-server, and hence scaling problem
Converged Service Node Deployment
Model (Pelago Networks)
Service
Service
Billing
Element
Management Prisioning Mediation Management
System
Environment
System
System
Service Creation
Environment
Operational Support
System
IP Network
(Internet)
Web-based
Subscriber GUI
Converged
Service Node
Packet Network
(ATM/IP)
NGN/Packet
Soft
switch
Media
Gateway
SSP
MSC
PSTN
Mobile
Intelligent Network Architecture
(Lucent Technologies)
Signalling
System 7
SCP
Signal
Transfer
Point
Lucent Technologies
Switches
SCE
Data Link
Signalling
Link
SMS
*
SN
Voice and
Data Link
Lucent Technologies
Mobile Switching
Centers
Other Wireline and
Wireless Switches
TCP/IP Interface to
Provisioning OSS
and Customer Care
TCP/IP to Data
Network
(e.g. Internet)
Lucent Technologies Advanced
Network Services
SCP Service Control Point
SN* Service Node or compact Service
Node/Intelligent Peripheral
SMS Service Management System
SCE Service Creation Environment
Intelligent Service Architecture
(IBM)
COMPOSITION
CREATOR
PROVIDER
STUDIO
Service Creation
Environment
NEW SERVICE
SUBSCRIPTION
SUBSCRIBER
DEPLOYMENT
MONITORING
Service Management
Environment
MESSAGING
NOTIFICATION
OPERATOR
MOBILE
USER
PACKAGING
CORE
SERVICES
PSTN
SERVICE
AGENTS
IP
Service Execution
Distributed Environment
An Open Service Architecture for Adaptive
Personal Mobile Communication (Ericsson)
Integrated Generic Architecture for Flexible Service
Provision to Mobile Users (University of Athens, Greece)
Reconfiguration Control/Service Provision Manager
Registration
Deployment
Services
Service Discovery
User Access Session
Service Deployment
User Profiling
Service Data
Manager
Reconfiguration
Manager
Technology independent interfaces
OSA, Parlay, JAIN, APIs
Reconfiguration
API extensions for reconfigurability
(Charging, QoS, policy)
Control and Service Provision Manager
Network infrastucture
MS
UTRAN
GERAN
Laptop
WLAN
VASP
VASP
3G Core
Network
IP Network
VASP
VASP
Mobile Network Services
Service Classification

Three main types of service
classification can be considered:



Execution Site based classification
Equipment based classification
Functional classification
Execution Site Based Classification

Refers to classifying the services according
to the site in the network where the services
are executed



Server based services – executed on server
side
User terminal based services – executed
locally on user terminals
Network based services – performed by
network functionality
Equipment Based Classification

Refers to classifying the services into
groups according to network standard or
applied equipment capabilities


Network specific services – services specific
for certain network standard or for certain
network hardware
User terminal specific services – services
specific for certain terminal capabilities
Functional Classification

Refers to classifying the services according
to useful function performed by them



Communication services – services which
enable communication between two or more
network users
Content Delivery services – services which
enable information delivery to users in
appropriate form
Remote Management services – services
which enable a user to remotely accomplish
certain activities through the network
Existent and possible mobile
services

Voice Telephony
Data Services
Multimedia Services
Remote Diagnostics
Unified Messaging
Information Brokering
Electronic Commerce

Call Center Services

Mobile Advertising







Interactive Gaming

Distributed Virtual Reality

Home Manager
Location-based billing,
information, emergency, and
tracking services

Value-added applications
enhancement: mobile gaming,
mobile chat/messaging, and
friend finder services

Business Models

Provide flexible and well defined
foundation for design and management
of complicated corporate service
architectures. They define:



Business entities and roles
Reference points for business relationships
Service provision procedures and
frameworks
Business Models in E-Commerce

B2B – Business to business

B2C – Business to consumer

C2B – Consumer to business

A2A – Application to Application

C2C – Consumer to Consumer

M2M – Market to market
Business Models in E-Commerce





Peer-to-peer (machine to machine, with or
without human guidance)
B2B2C – Business to Business to Consumer
Direct Commerce – Vendor Managed
Inventory shipped directly from warehouses
Collaborative Commerce – Multiple partners
working to supply a seamless experience
Transparent Commerce – a persona with data
wake that predictably engages commerce
Thank you for attention!
EUROOPAN UNIONI