Architectural Considerations for Personal Mobility In the Wireless Internet

Abstract

Personal Mobility, and the need for it, is considered to be the main driving force behind the spreading of the Wireless Internet. Moreover wireless devices and applications are being developed based on a basic assumption that users need to get access to services regardless of their location and used equipment. Wireless Services, on the other hand, are very dynamic and have a vibrant configuration and settings. In order for this to be utilizable a new network architecture is required. In our department we are developing Telecommunication Architecture for Plug-And-play Systems (TAPAS) to be a generic platform and application development environment based on plug-andplay technology, which uses the Web as means for service definition, update and discovery. TAPAS is intended to satisfy three basic classes of properties: Flexible and adaptable, Robust and survivable, and QoS aware. Personal mobility falls into the first class. Aspects of user, application and session mobility are dealt with using different mobility management schemes. The paper discusses trends in the Wireless Internet concerning devices, applications and services, and presents the approach used within TAPAS. Personal mobility in this context is based on the user, terminal and session mobility.

An XML-Based Framework for Dynamic Service Management

“…The framework has been developed and implemented as part of the TAPAS architecture, see [6,7,8] and the URL: http://tapas.item.ntnu.no/. The implementation of the framework is built around the support functionality of the TAPAS core platform.…”

Mobility Support Framework in Adaptable Service Architecture

“…Director maintains UserSession related information in UserSessionBase. [4] dealt with this type of mobility in detail, however certain enhancements to the approach have emerged, which with a general description are provided in the following subsections.…”

“…Some of the mobility features have been implemented, while others undergo redefinition and partial implementation. Personal mobility has been implemented and demonstrated in both fixed and wireless environments [4,6]. To test the applicability of the mobility functionality support two applications have been developed: Chat and File Transfer applications.…”

“…So far in this project, a wide range of topics have been dealt with, and many objectives been achieved. Four main architectures have been developedDthe basic architecture, mobility handling architecture, dynamic configuration architecture, and the adaptive service configuration architectureD for detailed information see [1,2,3,4,5,6] and the URL: http://www .item.ntnu.no/ -plugandplay. •rl TAPAS basic architecture, illustrated in Figure 1, is based on generic Actors (software components) in the Nodes of the network that can download Manuscripts defining Roles tobe played each represent different functionality.…”