|
LOMS: Local Mobile Services |
 Home
 Mail
 Internal
|
Project Summary
Given the ubiquity of IT and the commoditisation of telecoms, end-user expectations of easy access to ad-hoc services in varying circumstances and locations have gradually increased. Moreover, third parties like small companies, independent professionals and other individuals desire to participate in the e-trend by offering their own services. The ability to create service value has become the distinctive market driver for all players. Apart from mastering the current and future wireless network technologies used in enterprises or at public places, many hurdles face newcomers aiming to introduce innovative and widely available services to the general public or to targeted customer segments.
LOMS value chain modelIn order to solve the above described market dilemma of populating an ecosystem of local services, LOMS has defined an extended roles model (see Figure 1), introducing a number of intermediate value chain roles for actors in the service creation process:
 Figure 1: LOMS Roles Model
Encapsulating enabling services through LOMS service templatesAs an architectural foundation, LOMS has introduced LOMS service templates as the main service creation mechanism in its framework. The LOMS service templates encapsulate a variable, transformable orchestration flow between underlying components, e.g., expressed in transformable WS-BPEL language, as chosen in most of the LOMS demo example services. The templates can even contain other transformable functions as well as user interface definitions.Typically also, LOMS service templates hide the complexities of template-controlled enabling services in the underlying network. Some effectively demonstrated enabling services are:
The process: create - deploy - useThe process starts by Service Operators creating LOMS service templates, either manually or through the LOMS Creation Tools (version 1.0 shown in Figure 2). This includes the identification of variable parts of service code, descriptions on how it should be automatically deployed and provisioned, as well as descriptions of which parameters a Service Provider is able to provide when creating an actual service from the template.
 Figure 2: LOMS Creation Tools
In a next phase, Service Providers select the template of their choice - addressing their application domain - and instantiate it into a real, live service. They do this by simply answering questions, either through a webpage included in the template or via questionnaires in the richer LOMS Service Creation Environment (examples shown in Figure 3) and deploying their configured service by a single button push.
 Figure 3: LOMS Service Creation Environment
From then on, the Service Provider can manage content, charging rules, etc. depending on what the template provides, and ultimately also undeploy his service (see example management pages in Figure 4).
 Figure 4: Example Service Management Pages
In the meantime, also Mobile Users can use the launched services through the variety of devices as foreseen in the templates, which thus also allow for consistent, truly converged and device-independent services. Some samples of end-user services created with LOMS technology are shown in Figure 5.
 Figure 5: Example LOMS End User Services
Benefits to all stakeholders and exploitation perspectivesLOMS has made it possible to easily combine service creativity with rich, powerful features of a well-controlled service environment, thus offering clear value to all roles in the LOMS value chain model. A wide range of large to especially small Service Providers can benefit from the LOMS framework methodology, ultimately even allowing end-users themselves to offer their own services and content. The concept has opened a broad set of opportunities in concrete solutions of LOMS partners and their customers.
Project Structure Figure 6: LOMS Work Package Structure
The work within the LOMS project is split into seven Work Packages (see Figure 6):
|
News
|
Supported by
