Objectives
Partners
Papers
Private
Wise Home page

 

 

 

API Application Program Interface ASP Application Service Provider BM Business Model CORBA Common Object Request Broker Architecture CSV Comma-separated Values COTS commercial off-the-shelf DOM Document Object Model DNS Domain Name Service (or System) EJB Enterprise Java Bean FTP File Transfer Protocol FTPD File Transfer Protocol Daemon GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GUI Graphical User Interface HTML HyperText Markup Language HTTP HyperText Transport Protocol IMSI International Mobile Subscriber Identity IPDR Internet Protocol Detail Record JDBC Java Database Connectivity J2EE Java 2 Enterprise Edition J2ME Java 2 Micro Edition JMS Java Messaging Service JMX Java Management Extension JNDI Java Naming and Directory Interface JVM Java Virtual Machine LDAP Lightweight Directory Access Protocol OTA Over-the-Air PP Position Paradigm RMI Remote Method Invocation SNMP Simple Network Management Protocol SNMP MIB SNMP Management Information Base SP Service Provider SMS Short Message Service VoD Video-on-Demand VP Viewpoint WAP Wireless Application Protocol WISA WISE Architecture WISE Wireless Internet Service Engineering WSMC WISE Service Management Component XML Extensible Markup Language XSLT eXtensible Stylesheet Language Transformation BLOB Binary Large OBject JDBC Java Database Connectivity ODBC Open Database Connectivity PDA Personal Digital Assistant SmartFlow Solid proprietary data synchronization mechanism Statement An SQL command to write or read data from a relational database. SQL Structured Query Language Transaction A set of database operations, all of which succeed together or fail together. API Application Programming Interface ATM Asynchronous Transfer Mode BSS Business Support Systems BTS Base Transceiver Station C/S Client Server CORBA Common Object Request Broker Architecture COTS Commercial Off-The-Shelf CRM Customer Relationship Management DNS Domain Name Server EMS Enterprise Messaging Server FTP File Transfer Protocol GGSN Gateway GPRS Support Node GIS Geographic Information Systems GPS Global Positioning System GUI Graphic User Interface HTML HyperText Markup Language HTTP HyperText Transfer Protocol HUS Heterogeneous User Interface Service DSOM Distributed System Object Model IM/P Instant Messaging and Presence service ITF Interface J2EE Java 2 Enterprise Edition J2ME Java 2 Micro Edition MMS Multi Media Messaging MOTS Modified Off-The-Shelf MP3 MPEG1 Layer 3 MPEG Moving Picture Experts Group MVC Model-View-Controller architectural pattern NFR Non-functional Requirements OCM Original Component Manufacturer ODBC Open DataBase Connectivity OLE Object Linking and Embedding OS Operating System OSE Open System Environment OSI Open Systems Interconnection Model OSS Operating Support Systems P2P Peer-to-Peer PAC Presentation-Abstraction-Control PAs Presence Agents PC Personal Computer PDA Personal Digital Assistant PING Packet INternet Groper QoS Quality of Service RPC Remote Procedure Call RTP Rapid Transport Protocol RTSP Real-Time Streaming Protocol SIP Session Initiation Protocol SLA Service Level Agreement SMC Service Management Component SMS Short Message Service SQL Structured Query Language TCP/IP Transmission Control Protocol/ Internet Protocol TOM Telecom Operations Management UDP User Datagram Protocol UE Universal Explorer UIML User Interface Markup Language WAP Wireless Application Protocol. WISA Wireless Internet Service Architecture VM Virtual Machine / memory VP Viewpoint WWW World Wide Web VXML Voice eXtensible Markup Language XML eXtensible Markup Language This document is a part of the deliverable D4 produced in the task 2.1 of the Wise project. Deliverable D4 includes four parts: Part A: Architectural guidelines, Part B: the WISA (Wireless Internet Service Architecture) architectural knowledge base and its reference architecture (WISA/RA), Part C: Analysis of the pilot architectures, and Part D: Handbook of reusable architectural assets.This document presents a set of guidelines for describing the architecture of software systems in an abstract way, and for detailing their design in a more concrete way (for their implementation). This document presents a conceptual and a concrete view for the architecture of the WISE Data Management Component. WISE Data Management Component provides data management service for the WISE generic architecture. It also offers support for multi-point synchronization and transaction based data transfer facilities between two or more database nodes. The primary use of the WISE Data Management Component is providing a Content Delivery service for the WISE pilots. In practice this means that both in the server-side and in the client-side locates a local data storage and these storages are connected with each other wirelessly. The Data Management Component offers a controlled way to transfer content objects between these two storages. While the transfer is transaction based it can be restarted from any point of the transfer in error situations. Transaction base also allows a variation of pricing mechanisms for the content to be transferred: pay per view, reduced price against watching commercials, cheap hours for loading, etc. The Data Management Component is connected to other applications through ODBC or JDBC programming interfaces and it has SQL API for giving direct commands to the database. The database technology used as a platform for the component has been improved to wireless conditions based on feedback obtained in WISE pilot projects. The improvements to the product architecture are described in this document. Main enhancements are push type synchronization, improved performance in blob synchronization and improved management tools. This document addresses the requirements of WISE Service Management Component (WSMC) which applies to the first iteration of the WISE Project (see [3] for a description of WISA where the WSMC is introduced). In the first iteration we identify, starting from Pilots requirements, a set of 3 functional areas that provide a consistent set of features to enable Pilots to participate to the following scenario: · users have contracts with a service provider and they are provided with a single userId/password pair to be authenticated by the different systems in the architecture · users are enabled to manage (subscribe/unsubscribe) by themselves a set of services from a portfolio of available services · users are charged for having subscribed a service and for using a service according to a stated billing strategy · users are enabled to download client side code to have access to the offered service In the second iteration users have the enhanced possibility to regularly store in their profile informations about their location. Those informations are provided by clients by regularly sending data (possibly retrieved with a GPS) to the service component. The added scenario in this case is: · after subscription users are enabled to download a client for regularly sending positioning informations to the server · users have a GPS/positioning system and regularly provide (using the above-mentioned application) timing and positioning informations to the service Another enhancement concerns a new notification capability: it is now possible to send notifications to users with an event-driven approach. Both the application service and the Service Administrator are in charge for enabling/disabling notifications. The identified functional areas for Service Management Services which applies to the first iteration, described in this section, are: · User Management: Authentication & Authorization and User Profile Management · Provisioning: Self-Subscription and Client Code Download · Billing: Accounting and Mediation/Rating Enhancements specific to second iteration refer to: · Monitoring: Notification and Positioning