A Mobile Service

Architecture for Improving

Availability and Continuity

Author: Nor Shahniza Kamal Bashah

Ivar Jørstad

Do van Thuan

Tore Jønvik

Do van Thanh

Presenter: SOK, Phearin

MBC Laboratory

Konkuk University

Content

Introduction

Motivation

Related Works

Enhancing Availability and Providing Continuity

Implementation

Conclusion

Introduction

Introduction

In modern mobile environment, services

offered by various network systems are usually

NOT standardized.

Example: GSM voice service vs. IP Telephony

A new mobile service architecture - enables

the discovery and consumption of equivalent

services.

Motivation

Handling of equivalent

services

A service can be implemented using different

architectures and technologies. Example:

Data service -> 3G or WiFi

Voice Service -> GSM or IP Telephony (chIPhone)

Availability, ease of use, seamless

performance, security, price… motivate the use

of detection and swapping to the use of pop-

up service

When travelling, the mobile user will want to

have access to the same service. Example:

Taxi service in Trondheim, London, China, Cambodia

=> there should be a taxi service switch

To user, it is valuable to seamlessly access

the right service based on location.

Providing location-based

services

User preferences and personal data should

be remembered and dynamically re-applied

to every equivalent service at one place.

Offering personalized service

Related Works

Service continuity works at

NTNU

Several works on service continuity have been

proposed.

“Seamless service continuity is the …, where service

abruptness is bounded by the time it takes the user to move

between the two locations.”

“Non-seamless service continuity is the …, but where

additional disruption is introduced due to a required

reorganization of the service composition.”

No real implementation or usage has been achieved.

Service continuity is the ability for a user to maintain an

ongoing service during mobility.

The definition may imply continuity across different

devices, but it is not clearly stated.

TISPAN (Telecoms & Internet

Converged Services & Protocols for

Advanced Networks)

All works focus on seamless switching

between circuit switched voice and IMS

voice, well defined by mobile operators.

The proposed work extends service continuity

over non-standardized services.

3GPP Voice Call Continuity (VCC) and

GSMA VoLTE

802.21 Media Independent Handover (MIH)

services support detection of mobile

communication channels of a mobile terminal in

the vicinity.

Same service is implemented across all

heterogeneous networks

The paper work supports service continuity offered by

different types of networks implementation and using

different components.

IEEE Media Independent

Handover (MIH)

Enhancing Availability and

Providing Continuity

Clarification of the Service

Concept

The paper is adopted from [9]: “A service is a

mechanism enabling the end-user’s access to

one or more capabilities”

Clarification of the Service

Concept

A server on the network - hardware and

software - distributed over multiple network

elements

A client:

Generic client, eg. the Web browser, capable to

collaborate with any service server

Specific/dedicated client collaborate only with

some specific service servers

The paper focus on dedicated clients and the

way to provide service continuity on these clients

A Service Continuity

Architecture

There is NO mechanism for switching the two

different services seamlessly and smoothly.

A Service Continuity

Architecture User’s Device

Generic Service: receives commands from the

user and to generate output, and invokes the right

service according to the availability.

Continuity Agent: performs the necessary

initialization and configuration for the replacing

service to continue from the point of the previous

service stop - capable of downloading, installing

and initiating the new service.

A Service Continuity

Architecture

Service Discovery Agent: performs the dynamic

discovery of available services.

Profile Agent: stores and administers the user

profile, provides an interface allowing the

Continuity Agent to fetch the necessary data for

service configuration and changes done by the

user when using the services.

A Service Continuity

Architecture Network System

Continuity Server: carry out seamless transfer of

synchronous services like telephony.

Service Infobase: a service registry containing

information of all services available and equivalent

at a location, providing open interface for service

registration and matchmaking

Also provides Event service for notifications reception of

the subscribed Service Discovery Agent.

Sequence Processes of

a Service Continuity

Architecture

Implementation

Implementation

Continuity Server is realized by the Voice

server inherited from the EUREKA Mobicome

project [11]

Service Infobase has been successfully

implemented in [12]

Switch between the native

Phone application and

chIPhone, a SIP client.

communicate with the

native Contacts to

provide proper

configuration and

contacts for Phone and

chIPhone

Conclusion

Conclusion

The proposed service architecture dynamically

discovers and switches equivalent services by

ensuring the reusability of the user’s preference

and data, and controlling by the user.

In addition to the service availability, handover

criteria such as QoS, security, price, etc will be

considered to be further work.

Thank You