Mobile S Service Archi hite tecture ture in in Futur Future M - - PowerPoint PPT Presentation

▶
mobile s service archi hite tecture ture in in futur
SMART_READER_LITE
LIVE PREVIEW

Mobile S Service Archi hite tecture ture in in Futur Future M - - PowerPoint PPT Presentation

Mar 21, 2024 241 likes •501 views

1 Mobile S Service Archi hite tecture ture in in Futur Future M Mobi obile Env Environm ronments Nor Shahniza Kamal Bashah 11th F e b rua ry 2013 2 Outline Motivation Related works Research methodology

slide-1
SLIDE 1

1

Mobile S Service Archi hite tecture ture in in Futur Future M Mobi

  • bile Env

Environm ronments

Nor Shahniza Kamal Bashah

11th F e b rua ry 2013

slide-2
SLIDE 2

2

Outline

  • Motivation
  • Related works
  • Research methodology
  • Contribution of the thesis
  • Conclusion

nor shahniza kamal bashah

slide-3
SLIDE 3

3

nor shahniza kamal bashah

Motivation

Today’s user access to mobile services Motivation

slide-4
SLIDE 4

4

nor shahniza kamal bashah

Seamless handover between access technologies Seamless call transfer between two telephony services Access to service information Service discovery for

  • pen environments

Unifying mobile service architecture IEEE 802.21 MIH Mobicome project Covered in this thesis work

Motivation

Motivation

slide-5
SLIDE 5

5

nor shahniza kamal bashah

Objectives

OBJECTIVES FACTORS CHALLENGES

Service transfer

No access to inform ation about the services Service discovery for future m obile services Service continuity in a m ultiple netw ork system environm ent

Open heterogeneous netw ork environm ent

Architecture

  • f future

m obile services Multiple com peting services by different service providers on different access netw orks Anyone can be a service provider

Access to service inform ation Service discovery for

  • pen

environm ents

Provide service information in the existing IEEE 802.21 MIH Services Similar services with different names in different languages Different services with similar names Partially similar services Enhance the availability of services Ensure service continuity

capable to because

  • f

To unify all the disparate but equivalent services Unifying m obile service architecture

because

  • f

because

  • f

Service can be anything w ith any nam e

because

  • f

No restriction regarding the name length Anybody can introduce anything as a service anytime

achieved by method achieved by method achieved by method capable to capable to

Motivation

slide-6
SLIDE 6

6

nor shahniza kamal bashah

Mobile service can be realised by a multitude of assemblage variants MOBI LI TY MANAGEMENT AND HANDOVER FUTURE MOBI LE SERVI CE ARCHI TECTURES

SERVI CE CONTI NUI TY

3 GPP VOI CE CALL CONTI NUI TY ( VCC) AND GSM VoLTE Seamless switching between circuit switched voice and IMS voice

Support handover between the networks No t service handover

I EEE 8 02.21 MI H SERVI CES

Related works (1)

TI SPAN MOBI LE SERVI CES

Pre-defined Ad-hoc Notion of service equivalence Not continuity

  • f services

Service continuity over non- standardised services

Service continuity as a component of mobility

Handover is not a sufficient condition for service continuity XML RDF

Technologies for service continuity

OWL Use to describe service and realising service continuity

Related works

Continuous connectivity between networks 3GPP WLAN Interworking SIP IP Multimedia Subsystem

What is not covered in the work

slide-7
SLIDE 7

7

nor shahniza kamal bashah

CURRENT SERVI CE DI SCOVERY SYSTEMS

SERVI CE DI SCOVERY

I NTEGRATED SEMANTI C SERVI CE DI SCOVERY Use semantic to improve the Service Discovery OTHER SEMANTI C SERVI CE DI SCOVERY SYSTEMS

Jini UPnP

Service discovery which is capable of finding services having arbitary nam es in any form at given by any service provider

ERGOT OWL-S

Enhance discovery mechanism

  • Deliver and find the right

service for the user in an acceptable time

UbiSearch Salutation Web services CSDS MEMORY Layered architecture Two-stages method

Related works (2)

Related works

Rigid convention and format for service names and types Rely on exact string matching to discover services

  • Open service nam e and

type format

  • Open service nam e and

type convention

  • Open administration
  • Efficient and sound

What is not covered in the work

slide-8
SLIDE 8

8

nor shahniza kamal bashah

Research methodology

Problem Identification Solution Design Evaluation Guideline 2 Problem relevance Guideline: 1 - Design as an artifact 5 - Research rigor 6 - Design as a search process Guideline: 3 - Design evaluation 4 - Research contributions 7 – Communication of research

  • Identify limitations of the existing service

continuity

  • Study and evaluate existing service naming

and service discovery schemes

Research Questions

  • Identify requirements of future

mobile services

  • Propose requirements and

design of future service naming and service discovery scheme

  • Propose extensions to the IEEE

802.21 MIH Services

Conceptual model

  • Implementation of future service

discovery system

  • Case studies
  • Lab experiments

Performance testing

Research methodology

The design-science research process guidelines

slide-9
SLIDE 9

9

nor shahniza kamal bashah

Contribution of the thesis

The specification of the architecture & fram ew ork enabling the unification of mobile services The proposed extension

  • f the current IEEE

802.21 MIH Services for service continuity The specification of an

  • pen & sound service

discovery system

Research Contributions Contribution of the thesis

slide-10
SLIDE 10

10

nor shahniza kamal bashah

Future mobile service architecture and framework

User User’s Device Network system ServiceA Client ServiceA Server

“A service is a mechanism enabling the end-user’s access to one or more capabilities” OASIS Reference Model for SOA

Research contribution – FMSA & Framework

slide-11
SLIDE 11

11

nor shahniza kamal bashah

Offering personalised service Handling of equivalent services Providing location-based services Requirem ents

  • n future

m obile services

Future mobile service architecture and framework

Research contribution – FMSA & Framework

slide-12
SLIDE 12

12

Services in a m obile environm ents A Service Continuity architecture

nor shahniza kamal bashah

A mobile service architecture enhancing availability and supporting continuity

User User’s Device Network system MOBILITY ServiceB Client ServiceB Server ServiceA Server ServiceA Client User User’s Device Network system ServiceA Client ServiceA Server ServiceB Client ServiceB Server Generic Service Service Discovery Agent Service Infobase Service Adm. Continuity Agent Profile Agent Continuity Server

Research contribution – FMSA & Framework

slide-13
SLIDE 13

13

nor shahniza kamal bashah

User A Service Manager Generic Telephony Service GSM voice client chIPhone client Service Infobase Service Discovery Agent Continuity Agent Continuity Server User B Only GSM network available GSM & WLAN available 1. Create Generic Telephony service

  • 2. Dial number
  • 2. Invoke GSM voice client and call establish
  • 3. Forward call request
  • 4. Establish media stream
  • 5. Notify that user A moves to WLAN network offering telephony service
  • 6. Request list of available services
  • 7. Request available equivalent services
  • 8. Perform service discovery

and matchmaking

  • 8. Return equivalent service
  • 9. List of available equivalent services
  • 10. Start service transfer
  • 11. Fork current session
  • 11. Create new call
  • 12. Terminate the call

Research contribution – FMSA & Framework

slide-14
SLIDE 14

14

nor shahniza kamal bashah

Implementation and verification of service continuity

LI NUX KERNEL LBRARI ES ANDROI D RUNTI ME APPLI CATI ON FRAMEWORK APPLI CATI ONS Home Contacts Phone Browser Continuity Agent Profile Agent Service Disc Agent Generic Phone Service Adm. chIPhone ANDROI D RUNTI ME APPLI CATI ON FRAMEWORK Phone Service Adm.

A Service Continuity implementation on Android

Research contribution – FMSA & Framework

slide-15
SLIDE 15

15

nor shahniza kamal bashah

Realisation of service continuity by extending the IEEE 802.21

GSM/GPRS/ EDGE/UMTS WLAN/ Bluetooth Mobile Core Network PSTN Internet MIH PoS Information Server GSM

telephony

HANDOVER GSM/GPRS/ EDGE/UMTS WLAN Mobile Core Network PSTN Internet MIH PoS Information Server GSM

telephony

HANDOVER IP Core Network SIP Server IP

telephony

Handover process with IEEE 802.21 Information Service Handover between GSM telephony and IP telephony

Research contribution – Svs. continuity

slide-16
SLIDE 16

16

I EEE 8 0 2 .2 1 MI H Services

  • IEEE standard published in 2008
  • Ensure seamless connectivity and facilitate handover

between heterogeneous networks

nor shahniza kamal bashah

IEEE 802.21 helps with Handover Initiation, Network Selection and Interface Activation during Vertical Handovers Allows the mobile terminal to detect the communication channels & services that are available in the vicinity

Seamless connectivity

Enables co-operative handover decision making between Clients & Network

Facilitate handover

Research contribution – Svs. continuity

slide-17
SLIDE 17

17

nor shahniza kamal bashah

Proposed extensions to the MIH handover procedure

The propose parameter QueryServiceList is the list of services that the Mobile Node is requesting. It has a type LIST(SERVICE) which contains 0 or more services.

MIH_MN_HO_CANDIDATE_QUERY.REQUEST ( DESTINATIONIDENTIFIER, CURRENTLINKIDENTIFIER, CANDIDATELINKLIST, QUERYRESOURCELIST, IPCONFIGURATIONMETHODS, DHCPSERVERADDRESS, FAADDRESS, ACCESSROUTERADDRESS, QUERYSERVICELIST,

Research contribution – Svs. continuity additional parameter

slide-18
SLIDE 18

18

nor shahniza kamal bashah

Data type name Derived from Definition SERVICE SEQUENCE( SERVICE_NAME, SERVICE_TYPE, SERVICE_PARENT_TYPE, SERVICE_EQUIVALENCE_CLASS, SERVICE_KEWORDS, SERVICE_DESCRIPTION ) A type to represent a list of service in the access network. SERVICE_NAME OCTET_STRING A type to represent a service name. A non-NULL terminated string whose length shall not exceed 253 octets. SERVICE_TYPE OCTET_STRING A type to represent in which category the service belongs to. A non- NULL terminated string whose length shall not exceed 253 octets. SERVICE_PARENT_TYPE OCTET_STRING A type to represent ParentType of a service. A non-NULL terminated string whose length shall not exceed 253 octets. SERVICE_EQUIVALENCE_CLASS OCTET_STRING A type to represent equivalence services (any EquivalenceClass of the service defined by the Service Provider; it can also be service with the same ParentType). The value is a non-NULL terminated string whose length shall not exceed 253 octets. SERVICE_KEYWORDS OCTET_STRING A type to represent keywords of a service. The value is a non-NULL terminated string whose length shall not exceed 253 octets. SERVICE_DESCRIPTION OCTET_STRING A type to represent the description of a service. A non-NULL terminated string whose length shall not exceed 253 octets.

Definition of data type SERVICE

Research contribution – Svs. continuity

slide-19
SLIDE 19

19

IEEE802.11, Operator_1, PoAk (PoA Information) IE_POA_LINK_ADDR IE_POA_LOCATION IE_POA_CHANNEL_RANGE IE_POA_SYSTEM_INFO IE_POA_SUBNET_INFO IE_POA_IP_ADDR IEEE802.11, Operator_1, PoA2 (PoA Information) IE_POA_LINK_ADDR IE_POA_LOCATION IE_POA_CHANNEL_RANGE IE_POA_SYSTEM_INFO IE_POA_SUBNET_INFO IE_POA_IP_ADDR nor shahniza kamal bashah IE_NETWORK_TYPE=UMTS IE_OPERATOR_ID=Operator_1 IE_SERVICE_PROVIDER_ID=SP_A IE_COUNTRY_CODE=US

  • (Access Network Specific Information)

IE_NETWORK_ID= IE_NETWORK_AUX_ID= IE_ROAMING_PARTNERS= IE_COST= IE_NETWORK_QOS= IE_NETWORK_DATA_RATE= IE_NET_REGULAT_DOMAIN= IE_NETWORK_TYPE=IEEE802.11 IE_OPERATOR_ID=Operator_3 IE_SERVICE_PROVIDER_ID=SP_A IE_COUNTRY_CODE=US

  • (Access Network Specific Information)

IE_NETWORK_ID= IE_NETWORK_AUX_ID= IE_ROAMING_PARTNERS= IE_COST= IE_NETWORK_QOS= IE_NETWORK_DATA_RATE= IE_NET_REGULAT_DOMAIN=111 IE_NETWORK_TYPE=IEEE802.16 IE_OPERATOR_ID=Operator_2 IE_SERVICE_PROVIDER_ID=SP_A IE_COUNTRY_CODE=US

  • (Access Network Specific Information)

IE_NETWORK_ID= IE_NETWORK_AUX_ID= IE_ROAMING_PARTNERS= IE_COST= IE_NETWORK_QOS= IE_NETWORK_DATA_RATE= IE_NET_REGULAT_DOMAIN=1 IE_NETWORK_TYPE=IEEE802.11 IE_OPERATOR_ID=Operator_1 IE_SERVICE_PROVIDER_ID=SP_A IE_COUNTRY_CODE=US

  • (Access Network Specific Information)

IE_NETWORK_ID= IE_NETWORK_AUX_ID= IE_ROAMING_PARTNERS= IE_COST= IE_NETWORK_QOS= IE_NETWORK_DATA_RATE= IE_NET_REGULAT_DOMAIN= IEEE802.11, Operator_1, PoA1 (PoA Information) IE_POA_LINK_ADDR IE_POA_LOCATION IE_POA_CHANNEL_RANGE IE_POA_SYSTEM_INFO IE_POA_SUBNET_INFO IE_POA_IP_ADDR IEEE802.11, Operator_1, PoAn (PoA Information) IE_POA_LINK_ADDR IE_POA_LOCATION IE_POA_CHANNEL_RANGE IE_POA_SYSTEM_INFO IE_POA_SUBNET_INFO IE_POA_IP_ADDR IEEE802.11, Operator_2, PoA2 (PoA Information) IE_POA_LINK_ADDR IE_POA_LOCATION IE_POA_CHANNEL_RANGE IE_POA_SYSTEM_INFO IE_POA_SUBNET_INFO IE_POA_IP_ADDR IEEE802.11, Operator_2, PoA1 (PoA Information) IE_POA_LINK_ADDR IE_POA_LOCATION IE_POA_CHANNEL_RANGE IE_POA_SYSTEM_INFO IE_POA_SUBNET_INFO IE_POA_IP_ADDR IE_NET_SERVICES IE_POA_SERVICES

Information elements with service information

PROPOSED EXTENSION TO THE MIIS

Research contribution – Svs. continuity

slide-20
SLIDE 20

20

nor shahniza kamal bashah

Service discovery

Design of service discovery and service matching Requirements on the future service discovery

Service naming

Service discovery

Service naming policy Service naming for future mobile services

Implementation and validation of the proposed service discovery Implementation of Service Discovery

EquivalenceClass ParentType Keyword

Research contribution – Service discovery

slide-21
SLIDE 21

21

nor shahniza kamal bashah

TEKSI CAB TAXI

[taxi] = {x Є S| X ~ taxi} S: set of services Service naming Service may have different names in different languages [taxi] = {taxi, teksi, taksiliito, cab, …}

Research contribution – Service discovery

How to disc ove r the se rvic e s?

slide-22
SLIDE 22

22

nor shahniza kamal bashah

Service discovery Service continuity

Achievem ents & results

Extend information database with service information Include service information in the information exchange between the mobile client and the MIH Mobile service architecture Enhance availability of services Ensure service continuity Similar services with different names in different languages Different services with similar names Partially similar services No restriction regarding the name length Anybody can introduce anything as a service anytime

Conclusion

Conclusion

slide-23
SLIDE 23

23

nor shahniza kamal bashah

Conclusion

Conclusion

Service continuity Service continuity

Future w orks

To develop a prototype which incorporates more semantic matching with more level of parents & larger equivalent set Tests should be carried out on sitations with large no. of services & large sets of equivalent service Service information & extension of handover procedure should be implemented & integrated in an IEEE 802.21 MIH implementation Testing & evaluation should be carried

  • ut in the real mobile environment &
  • n various situations

To introduce other criteria for selection & change of services To emulate a distributed environment

slide-24
SLIDE 24

24

T hank You

nor shahniza kamal bashah