1. Introduction

This document describes a 'Reference Architecture' for deploying communication network applications that capitalize on a design approach in which a consolidated data-store of common subscriber profile data is used, and in which the individual application instances using this common data-store, are data-less and in some cases, even state-less. The SPUG approach to application design will be generically referred to as the "Data-less Application Architecture" (DAA). In this context the term "Application" refers to any functional component delivering either operational control (e.g. HLR, MSC, GGSN, AAA, etc.) or service delivery (e.g. SMS, MMS,

Voicemail, online data services, etc.).

In developing this Reference Architecture, the authors have attempted to focus on producing a solution that is highly pragmatic and based on the collective knowledge and real-world experience of the SPUG membership. At the same time, care has been taken so as not to lose sight of the technical ideal and significant business benefits that such an approach can deliver.

The release of this SPUG Reference Architecture is a "work in progress" proposal that will evolve significantly over the coming months as further review and input is received and welcomed from within the SPUG membership and from external interested parties.

1.1 Purpose

The primary purpose of this document is to provide a pragmatic architectural structure for the design and discussion of DAA based solutions. It offers a set of established DAA requirements, recommendations, and guidelines as input into the architectural design process for all DAA based solutions or sub-components. The intention of the Reference Architecture is to present an "open" technical model that can be used by all members of a DAA project team providing them with a consistent set of architectural and technical best practices.

It is hoped that by making this document available, it will not only encourage the wider consideration of a DAA design approach among network operators and component vendors, but also promote and encourage a greater degree of compatibility across DAA based network applications and their data sets. Ultimately the adoption of a DAA based design approach can lead to:

Improved user experience. By users no longer having to enter the same data more than once, and by offering a wider range of applications which recognizes a common set of subscriber preferences and settings.

• Increased Operator's ARPU. For example, by providing the operator with a greater understanding of the subscriber's behaviours, service access patterns, and lifestyle. Enabling the operator to fully extract the business value from the subscriber data.

• Reduced OPEX. For example, by the efficient use of the data resources available, and by enhancing application and data storage scalability (only scaling as and when needed).

Reduced CAPEX. The consolidation of data means that only one logical platform needs to expand with subscriber based growth. By pooling resources for redundancy and high-availability, it saves on the need to build un-utilized multi-site solutions and all the associated interconnect infrastructure for multiple applications.

Reduced time to market for new services. When new applications or services can connect to a "pre-integrated" data-store, the number of validation checkpoints required is reduced.

• Centralized and homogeneous data management, resulting in increased ARPU and improved OPEX efficiency.

The adoption of DAA based solutions is expanding rapidly as the need to increase ARPU, reduce CAPEX, reduce OPEX, and most importantly capitalization of subscriber data intelligence growth.

With any DAA solution there should be a standardized means (de-facto or formal) of integrating different applications, platforms, and network types. The SPUG Reference Architecture presented in this document is intended to promote interoperability and extensibility among the various applications, services, platforms and frameworks in a manner that remains consistent to the principles of a DAA based approach.

1.2 Objectives

The purpose of this Reference Architecture is supported by the following key objectives:

To identify and describe the most appropriate DAA architectural framework, functional component grouping, and inter-component relationships and to realize the desired properties and advantages of a DAA based solution.

To establish a set of general DAA solution design principles, guidelines, recommendations, and constraints upon which the SPUG DAA concept is based.

To provide material that can be constructively used as the key architectural input in the design process for any operator considering a DAA solution deployment, or by any vendor proposing development of any DAA targeted components.

To define a set of consistent terminology for use in any discussion about DAA solutions or design approaches.

To establish the concept of data-less applications and common data-stores within the communication network industry, and define the application and data-store characteristics that typify the common interests and goals that bring together the SPUG membership.

To identify candidate technologies that have been determined to meet the functional requirements defined within the DAA design approach and, where appropriate, make recommendations on the adoption such technology for DAA solutions.

To maintain the principle that the DAA is a vendor agnostic architecture, representing the current best practices derived from the practical experience of the collective SPUG membership.

To develop the DAA Reference Architecture to be complementary to the work of the many standards bodies and industry forums also working within this technology space.

The term DAA, and other terms for the generalized description of data-less applications which share a common data store, does not currently describe a coherent or necessarily consistent set of technologies, architectures or even visions. The community of DAA focused evangelists, architects, developers, and vendors (all as embodied by the SPUG membership) represents the merging of thought streams and practical experiences to produce a view of what a DAA solution is thought to be.