ETSI TS 188 002-3 V2.0.0 (2008-03)

Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network and Service Management;
Subscription Management;
Part 3: Functional Architecture

2 ETSI TS 188 002-3 V2.0.0 (2008-03)

Reference
DTS/TISPAN-08015-3-NGN-R2
Keywords
administration, management, service, subscriber
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 188 002-3 V2.0.0 (2008-03)

Contents
Intellectual Property Rights.5
Foreword.5
Introduction .5
1 Scope.6
2 References.6
2.1 Normative references.7
2.2 Informative references.7
3 Abbreviations.9
4 SuM Functional Architecture .9
4.1 Overview.9
4.2 Service Configuration and Activation .11
4.3 Resource Provisioning.11
4.4 NGN Functional entities.11
5 SuM NOSI.12
5.1 SuM NOSI Identification .12
5.2 SuM NOSI and SUM Information Model .13
5.3 SuM NOSI description .14
6 SuM Service Activation and Configuration NOSIs .14
6.1 Manage Subscription by Service Provider (SCA-MSSP).14
6.2 Manage Subscription by Subscriber (SCA-MSS) .15
6.3 Manage User(SCA-MU).16
6.4 Manage User Services(SCA-MUS).17
7 SuM Resource Provisioning NOSI.18
7.1 Subscription Services (RP-SS).18
7.2 User Preferences (RP-UP).19
7.3 Subscription Network Access (RP- SNA).19
8 SuM NGN Functional entities NOSIs .20
Annex A (informative): Relation with 3GPP Generic User Profile (GUP) .22
A.1 3GPP GUP Overview.22
A.1.1 Architecture.22
A.1.2 Information Model.23
A.1.3 Interfaces.24
A.1.4 Data Description Method .24
A.2 3GPP GUP and TISPAN SuM Functional Architecture .25
A.2.1 Commonalities regarding requirements.25
A.2.2 Commonalities regarding Architecture (Stage 2) .26
A.2.3 Commonalities regarding Solution Sets (Stage 3).27
Annex B (informative): Relation with 3GPP Integration Reference Points (IRPs) .28
B.1 3GPP IRP Introduction and overview .28
B.1.1 General.28
B.1.2 IRP Specifications Approach.29
B.2 Architecture.30
B.3 IRP SOAP Solution Sets .30
B.4 Overview of IRPs related to SOAP SSs.31
B.4.1 Generic IRP.31
ETSI
4 ETSI TS 188 002-3 V2.0.0 (2008-03)

B.4.2 Notification IRP .31
B.4.3 Kernel CM IRP.32
B.4.4 Basic CM IRP.32
B.4.5 Generic NRM IRP.32
B.4.6 SuM NRM IRP.32
B.5 3GPP IRPs and TISPAN SuM Functional Architecture .33
B.5.1 Commonalities regarding requirements (Stage 1) .33
B.5.1.1 General.33
B.5.1.2 IRP support of SuM FA requirements in TS 188 002-1 .33
B.5.2 Commonalities regarding the architecture and information models (Stage 2) .34
B.5.2.1 General.34
B.5.2.2 Reference points.35
B.5.2.3 Structure of data.35
B.5.2.4 Operations.35
B.5.3 Commonalities regarding Solution Sets (Stage 3).36
Annex C (informative): Bibliography.37
History .38

ETSI
5 ETSI TS 188 002-3 V2.0.0 (2008-03)

Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 3 of a multi-part deliverable covering the Network and Service Management; Subscription
Management, as identified below:
Part 1: "Requirements";
Part 2: "Information Model";
Part 3: "Functional Architecture".
Introduction
The focus of the present document is the definition of the Subscription Management (SuM) Functional Architecture that
has the objective to offer service providers and operators means for a simple, flexible and efficient subscription data
repartition in the TISPAN NGN network entities.
ETSI
6 ETSI TS 188 002-3 V2.0.0 (2008-03)

1 Scope
The purpose of the SuM Functional Architecture is the design of the NGN OSS Service Interfaces (NOSIs) needed for
the management of a specific Subscriber, User, Service Profile and User Services within TISPAN NGN. The SuM
Functional Architecture shall deliver the necessary NOSIs for the Resource Provisioning and Service Activation
processes.
The NOSIs related to Service Configuration & Activation shall be network technology agnostic without any knowledge
of the NGN functional entities that are involved. The NOSIs related to Resource Provisioning are responsible of NGN
functional entities (including CPE and AS) management and shall hide the complexity of the different NGN functional
entities to the NOSIs related to Service Configuration & Activation.
The specification of the NOSIs comprises the list of operations they are offering and the associated subscription and
user data that are specified in the SuM Information model. The set of NGN FEs expose one or more NOSIs for the
management of Subscription Management data.
The present document is part of specifications related to subscription management that comprises:
• TS 188 002-1 [2]: SuM Requirements.
• TS 188 002-2 [3]: SuM Information Model.
• TS 188 002-3 (the present document): SuM Functional Architecture.
The present document is developed according to the specifications of TISPAN R1, including the NGN OSS
Architecture specifications described in TS 188 001 [1]. The SuM Functional Architecture meets the requirements of
TS 188 002-1 [2].
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
ETSI
7 ETSI TS 188 002-3 V2.0.0 (2008-03)

2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 188 001: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); NGN management; OSS Architecture Release 1".
[2] ETSI TS 188 002-1: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Subscription Management; Part 1: Requirements".
[3] ETSI TS 188 002-2: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Subscription Management; Part 2: Information Model".
[4] ETSI TS 122 240: "Universal Mobile Telecommunications System (UMTS); Service requirements
for 3GPP Generic User Profile (GUP); Stage 1 (3GPP TS 22.240 Release 6)".
[5] ETSI TS 123 240: "Universal Mobile Telecommunications System (UMTS); 3GPP Generic User
Profile (GUP) requirements; Architecture (Stage 2) (3GPP TS 23.240 Release 6)".
[6] ETSI TR 123 941: "Universal Mobile Telecommunications System (UMTS); 3GPP Generic User
Profile (GUP); Stage 2; Data Description Method (DDM) (3GPP TR 23.941 Release 6)".
[7] ETSI TS 129 240: "Universal Mobile Telecommunications System (UMTS); 3GPP Generic User
Profile (GUP); Stage 3; Network (3GPP TS 29.240 Release 6)".
[8] ETSI TS 132 171: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Subscription
Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP):
Requirements (3GPP TS 32.171)".
[9] 3GPP TS 32.172: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Telecommunication management; Subscription Management (SuM) Network
Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) (Release 8)".
[10] ETSI TS 132 175: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Subscription
Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP):
eXtensible Markup Language (XML) definition (3GPP TS 32.175)".
2.2 Informative references
[11] ETSI TS 132 101: "Universal Mobile Telecommunications System (UMTS); Telecommunication
management; Principles and high level requirements (3GPP TS 32.101)".
[12] ETSI TS 132 150: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Integration Reference
Point (IRP) Concept and definitions (3GPP TS 32.150)".
[13] ETSI TS 132 311: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Generic Integration
Reference Point (IRP) management; Requirements (3GPP TS 32.311)".
[14] ETSI TS 132 312: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Generic Integration
Reference Point (IRP) management; Information Service (IS) (3GPP TS 32.312)".
[15] ETSI TS 132 317: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Generic Integration
Reference Point (IRP) management; SOAP Solution Set (SS) (3GPP TS 32.317)".
ETSI
8 ETSI TS 188 002-3 V2.0.0 (2008-03)

[16] ETSI TS 132 301: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Notification Integration Reference Point (IRP): Requirements
(3GPP TS 32.301)".
[17] ETSI TS 132 302: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)
(3GPP TS 32.302)".
[18] ETSI TS 132 307: "Universal Mobile Telecommunications System (UMTS); Telecommunication
management; Configuration Management (CM); Notification Integration Reference Point (IRP):
Simple Object Access Protocol (SOAP) Solution Set (SS) (3GPP TS 32.307)".
[19] ETSI TS 132 661: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Kernel CM; Requirements (3GPP TS 32.661)".
[20] ETSI TS 132 662: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Kernel CM; Information service (IS) (3GPP TS 32.662)".
[21] ETSI TS 132 665: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Kernel CM Integration Reference Point (IRP): eXtensible Markup Language
(XML) definitions (3GPP TS 32.665)".
[22] ETSI TS 132 667: "Universal Mobile Telecommunications System (UMTS); Telecommunication
management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP):
Simple Object Access Protocol (SOAP) Solution Set (SS) (3GPP TS 32.667)".
[23] ETSI TS 132 601: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Basic CM Integration Reference Point (IRP); Requirements
(3GPP TS 32.601)".
[24] ETSI TS 132 602: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)
(3GPP TS 32.602)".
[25] ETSI TS 132 607: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Basic CM Integration Reference Point (IRP): SOAP Solution Set (SS)
(3GPP TS 32.607)".
[26] ETSI TS 132 621: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Generic network resources Integration Reference Point (IRP); Requirements
(3GPP TS 32.621)".
[27] ETSI TS 132 622: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Generic network resources Integration Reference Point (IRP): Network
Resource Model (NRM) (3GPP TS 32.622)".
[28] ETSI TS 132 625: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Configuration
Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM
eXtensible Markup Language (XML) file format definition (3GPP TS 32.625)".
[29] W3C Recommendation: "XML Path Language (XPath)" Version 1.0, 16 November 1999.
ETSI
9 ETSI TS 188 002-3 V2.0.0 (2008-03)

3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AS Application Server
CLF Connectivity session Location and repository Function
GUP Generic User Profile
IOC Information Object Class
IRP Integration Reference Point
IS Information Service
NASS Network Attachment SubSystem
NGN FE NGN Functional Entity
NOSI NGN OSS Service Interface
OSS Operation Support Systems
PDBF Profile Data Base Function
RAF Repository Access Function
RP Resource Provisioning
SCA Service Configuration & Activation
SOAP Simple Object Access Protocol
SS Solution Set
SuM Subscription Management
TOM Telecommunication Operation Map
UPSF User Profile Server Function
WSDL Web Services Description Language
XML eXtensible Markup Language
4 SuM Functional Architecture
4.1 Overview
Subscription Management is paramount for the NGN service delivery within TISPAN NGN. It aims to define an end-
to-end information model and a functional architecture that allows service providers to provision their NGN functional
entities with all the mandatory/optional information specific to a subscriber and its users. Subscription Management can
be summarized as the framework that offer service providers means for efficient management of all the data related to a
specific subscription. The purposes of specifying a SuM Information Model is to capture all the information needed for
the management of a specific subscription. The purpose of the SuM Functional Architecture is the design of the NGN
OSS Service Interfaces (NOSIs) needed for the management of subscribers and their users, with respect to the
requirements defined in [2], and to the NGN OSS Architecture [1].
Subscription Management aligns with subset of the eTOM fulfilment process, in particular the Customer Relationship
Management process, the Service Management & Operations process, and the Resource management and operation
process. As depicted in figure 1, the current target of the SuM FA is the specification of:
• The NOSIs for the realization of the Service Configuration & Activation (SCA NOSIs).
• The NOSIs for the realization of the Resource Provisioning (RP NOSIs).
• The NOSIs exposed for the management of data stored within NGN FEs (NGN FE NOSIs).
ETSI
10 ETSI TS 188 002-3 V2.0.0 (2008-03)

Order Handling
Service Configuration
& Activation (SCA)
Resource Provisioning (RP)
NGN Function Entities
NOSI Interface
Figure 1: Subscription Management NOSI
Following concepts are introduced:
• SCA Service (SCA): Service which exposes at least one SCA NOSI.
• RP Service (RP): Service which exposes at least one RP NOSI.
• NGN FE Service (NGN FE MA): Service which exposes at least one NGN FE NOSI.
The following figure depicts the Subscription Management Functional Architecture based on the precedent concepts
and TISPAN NGN OSS Architecture.
SCA SCA
SCA
NGN OSS Basic
Service Service
Service
Framework Services
Common Communication Vehicle
RP RP RP
FE FE FE
Service Service Service
Service Service Service
NOSI exposed for the management of data stored in NGN FE
RP NOSI
SCA NOSI
NGN OSS Basic Framework Services NOSIs

Figure 2: Subscription Management NOSIs
ETSI
11 ETSI TS 188 002-3 V2.0.0 (2008-03)

The NGN OSS basic framework services NOSIs are the NOSIs in charge of aspects such as distribution, transparency,
registration, etc., as described in NGN OSS Architecture. The NGN OSS basic framework services NOSIs are out of the
scope of the Subscription Management standards.
4.2 Service Configuration and Activation
For the specification of the SCA NOSIs, it is necessary to list all the required capabilities that need to be supported or
offered by the NOSIs with respect to SuM requirements, eTOM and to the use cases defined in [2]. There is no
assumption on the relations between the required capabilities and the NOSIs that support them.
The SCA NOSIs shall expose the following capabilities:
• Manage Subscription by the service provider: consist in all the CRUD operations needed for the
management of a specific subscription.
• Manage Subscription by the subscriber: consist in all the CRUD operation allowed by the service provider
for its subscribers (example: subscribe to new services, etc.).
• Manage Users: consist in all the CRUD capabilities needed for the management of a user of a specific
subscriber. (example: create new user, assign services to a user, etc.).
• Manage User Services: consist in all the capabilities needed for the customization of services by users
(example: configure a phone number for the call forwarding service, etc.).
In addition to the above capabilities, the SCA NOSI shall expose the subscribe/notify capabilities that allows
notifications when subscription information change (example: when a phone number for the call forwarding service is
configured by a user, the service provider may be informed for legal interception purposes).
The precedent capabilities of the SCA NOSIs represent the fact that theses NOSIs are responsible of the management of
Subscriber, Subscription and Users.
4.3 Resource Provisioning
This clause consists in a description of all the capabilities required for SuM within the Resource Provisioning process
group with respect to the Subscription Management Requirements and to eTOM.
For the specification of the RP NOSIs, it is necessary to list all the required capabilities that need to be supported or
offered by the NOSIs with respect to eTOM and to the use cases defined in [2].
The RP NOSIs shall expose the following capabilities:
• Manage NGN Subscription Management Data: consist in all the CRUD capabilities related to the
management of Subscription Management information (services, network access, credentials, etc.) for
subscription, users, and user services.
The precedent capabilities represent the fact that the RP NOSIs allow the management of the information part of the
Subscriber, Subscription and Users which are the Services, Credentials, Network Access, etc.
4.4 NGN Functional entities
This clause consists in a description of all the capabilities required for SuM within the NGN Functional entities with
respect to the Subscription Management Requirements and to eTOM.
The TISPAN NGN Functional entities concerned by the present SuM NGN FEs NOSI specification are:
• The UPSF.
• The PDBF, NACF and the CLF in the NASS subsystem.
• User data repositories of Application servers offering NGN services.
NOTE: The CPE case is for further study.
ETSI
12 ETSI TS 188 002-3 V2.0.0 (2008-03)

The Operations offered by NGN FE NOSIs allows to create, read, update and delete subscription data stored on any
instance of the concerned NGN FEs.
These operations are not different from a NGN FE to another, so the specifications of these operations are common to
all the NGN FEs. They comprise:
• "Create" operation: it applies to a data that is created on the concerned NGN FE. It indicates the links or
references that this data can have with other data.
• "Read" operation: it allows to retrieve a data stored on a given NGN FE, by using the relevant identifier of this
data.
• "Update" operation: it allows to update a data, its attributes or its links to other data.
• "Delete" operation: it allows to delete a data and its dependent data ("children").
These operations are completed with the following ones:
• "Notify" operations: it allows the NGN FE to notify modifications occurring on data to the Resource
Management.
• "Subscribe/ unsubscribe to notify": it allows the Resource Management to be (/ or not) notified of
modifications occurring on data stored on the NGN FE.
5 SuM NOSI
In this clause, a description of the process used for the identification and specification of the SUM NOSI is given. In
addition, a description of the relationship between the SuM NOSI and the SuM Information model is also given.
A NGN OSS Service Interface (NGN OSS SI) is defined in the NGN OSS Architecture [1], clauses 3 and 6.3. It is a
well defined grouping of related NGN OSS Operations and constant data which are necessary to deliver coherent
business or system functionality. The NGN OSS Service Interface is:
• An aggregation of functionality required for managing some coherent aspect of the NGN network or services.
This functionality is provided through a set of related behaviour/functionality and is made publicly available
for use by consumers of this service interface. An example is an Alarm Reporting service interface that offers
the functionality supporting the NGN OSS Operations "getAlarmList" and "acknowledgeAlarms".
• Comprised of a set of NGN OSS Operations which must be all present.
According to the above definition from [1], a NOSI is a set of operations and constant data, which correspond to an
aggregation of functionality required for managing aspects of NGN network or services.
With respect to this definition, we will first describe the methodology used for the identification of the NOSIs needed
for Subscription Management, and the NOSI themselves with their operations. We will then detail the relationship
between the NOSIs and the Subscription Management Information Model which represent the data part of the NOSI.
5.1 SuM NOSI Identification
In this clause, a description of the process used for the identification and specification of the SUM NOSI is given.
In clause 4, we have identified three sets of NOSI for Subscription Management: SCA, RP and NGN FE NOSIs and the
capabilities they should expose.
The SCA NOSI should expose capabilities for the management of subscriber, subscription and users. The RP NOSI
should expose capabilities for the management of the information part of the Subscriber, subscription and users which
are the Services, Credentials, Network Access, etc.
The NGN FE NOSIs shall expose the capabilities for the basic CRUD operations on the subscription management
information contained in the NGN FE(s).
The following NOSI have been identified.
ETSI
13 ETSI TS 188 002-3 V2.0.0 (2008-03)

SCA NOSI Operations
Manage Subscription by Service Provider (SCA-MSSP)
- Create/ Read/Update/ Delete Subscription
- Subscribe/Notify operations may be defined
Manage Subscription by Subscriber (SCA-MSS) - Read/Update Subscription
- Subscribe/Notify operations may be defined
Manage User(SCA-MU) - Create/Read/Update/Delete User
- Subscribe/Notify operations may be defined
Manage User Services(SCA-MUS) - Create/Read/Update/Delete User Services
- Subscribe/Notify operations may be defined

RP NOSI
Subscription Services (RP-SS) - Configure/Update/Read/Remove subscription and user information
- Subscribe/Notify operations may be defined
User Preferences (RP-UP) - Configure/Update/Read/Remove Preferences for user
- Subscribe/Notify operations may be defined
Subscription Network Access (RP- SNA)
- Configure/Update/Read/Remove Network Access for user/subscription
- Subscribe/Notify operations may be defined

NGN FE Operations
Manage Data (NGN FE-MD)
- Create/ Read/Update/ Delete Data
- Subscribe/Notify operations may be defined

5.2 SuM NOSI and SUM Information Model
In this clause, a description of the relationship between the SuM NOSI and the SuM Information model is also given. A
NOSI is a well defined grouping of related NGN OSS Operations and constant data. In clause 5.1 we have identified a
set of NOSIs with their related operations. The constant data that are part of a NOSI is part of the Subscription
Management Information Model.
A NOSI as defined in NGN OSS Architecture is equivalent to the SOA service interface concept. In the OASIS SOA
reference model which is used as the reference in TISPAN, service interface is defined as the means for interacting with
a service (an SOA service is accessed by means of a service interface, where the interface comprises the specifics of
how to access the underlying capabilities). A service is opaque in that its implementation is typically hidden from the
service consumer except for the information and behaviour models exposed through the service interface and the
information required by service consumers to determine whether a given service is appropriate for their needs.
An SOA service interface includes the specific protocols, commands, and information exchange by which actions are
initiated that result in the real world effects as specified through the service functionality portion of the service
description. The specifics of the interface SHOULD be syntactically represented in a standard referenceable format.
These prescribe what information needs to be provided to the service in order to access its capabilities and interpret
responses. This is often referred to as the service's information model.
The information model of a service is a characterization of the information that may be exchanged with the service.
Only information and data that are potentially exchanged with a service are generally included within that service's
information model. The scope of the information model includes the format of information that is exchanged, the
structural relationship within the exchanged information and also the definition of terms used.
According to the OASIS service interface and its information model definitions, we define the relation between the
SuM NOSI and the SuM information Model as follows: "The Information model of a SuM NOSI should be a part of the
whole SuM Information Model".
For example, if the SuM Information Model define 3 objects (object A, object B, object C), their attributes and relations
between the 3 objects, a specific SuM NOSI may use only 2 objects (Object A and Object C) with all their attributes an
relations between the 2 objects as defined in the SuM Information Model.
In summary, for each SuM NOSI, its associated part of the SuM Information Model should be indicated. For example,
the NOSIs exposed by the SCA may access only to information that represents subscription, user, service profiles and
services which are independent from the network resources.
ETSI
14 ETSI TS 188 002-3 V2.0.0 (2008-03)

The association between the NOSIs and the information model or information part of the information model which is
accessed by a specific NOSI is defined in clauses 6, 7 and 8.
5.3 SuM NOSI description
The following table is used to describe the SuM NOSIs in clauses 6, 7 and 8.
Operation
contains the name of a NOSI operation
Description describes the purpose of a NOSI operation
Pre-conditions defines the conditions to be fulfilled before requesting a NOSI operation
Post-conditions defines the new conditions after the execution of a NOSI operation
SuM Info Model related Inputs as according to clause 5.2, data inputs defined for a NOSI operation are part of the
SuM info model, and are identified through the relevant Information Object Classes
(IOC) of the SuM info model to which they refer or belong
SuM Info Model related Outputs
as according to clause 5.2, data outputs defined for a NOSI operation are part of the
SuM info model, and are identified through the relevant Information Object Classes
(IOC) of the SuM info model to which they refer or belong

NOTE 1: The outputs parameters are those delivered when the request is successful. Exception cases are not
covered in this release.
NOTE 2: Subscribe to notify / notify operations are not described in this release.
6 SuM Service Activation and Configuration NOSIs
This clause contains the description of the SuM Service Configuration & Configuration NOSIs identified in clause 5.1.
NOTE: Since both the TISPAN SCA-NOSI and MTOSI Interfaces from TMF mTOP in the Service Activation
domain specify interfaces between the eTOM's Order Handling process in the CRM layer and the SCA
process in the Service Management layer, a possible further harmonization and alignment
between these standards in the offered functionalities as well as the interfaces and the associated
information model will be investigated.
A mutual further study as to the potential benefits of using MTOSI Service Activation Interface as SCA
NOSIs has been offered and possible advantages from alignment with MTOSI Service Activation
Interfaces will be explored with mTOP's MTOSI SAI team.
6.1 Manage Subscription by Service Provider (SCA-MSSP)
The SCA-MSSP NOSI is dealing with the following part of the SuM Info model:
• SuMSubscriberProfile IOC.
• SuMService IOCs.
• SuMSubscribedServiceGroup IOC.
• SuMSubscribedService IOCs.
NOTE 1: The subclasses of the SuMSubscribedService and SuMService IOCs are involved in the SCA process.
These classes contain also attributes belonging to the Resource Provisioning process, and the implications
of this are for further study.
NOTE 2: An instance of the SumSubscribedServicesGroup IOC may identify a subscription with multiple
subscribed services.
ETSI
15 ETSI TS 188 002-3 V2.0.0 (2008-03)

Operation
SCA-MSSP Create Subscription
Description
Create a subscription with associated subscribed services
Pre-conditions Subscriber exists
Post-conditions The subscription with its set of subscribed services has been created
SuM Info Model related Inputs SuMSubscriberProfile IOC, SuMService IOCs
SuM Info Model related Outputs SuMSubscribedServiceGroup IOC, SuMSubscribedService IOCs

Operation SCA-MSSP Delete Subscription
Description
Delete a subscription with associated subscribed services
NOTE: This operation should also suppress / modify all User Service profiles
concerned by subscribed services that are suppressed.
Pre-conditions Subscriber and subscribed services exists
Post-conditions The subscription with its set of subscribed services has been deleted
SuM Info Model related Inputs SuMSubscribedServiceGroup IOC
SuM Info Model related Outputs None identified

Operation
SCA-MSSP Update Subscription
Description Update a subscription and/or associated subscribed services. It can comprise
addition, deletion and modification of a service
Pre-conditions
Subscriber and subscription exists
Post-conditions
The subscription with its set of subscribed services has been modified
SuM Info Model related Inputs SuMSubscribedServiceGroup IOC, SuMSubscribed Service IOCs
SuM Info Model related Outputs None identified

Operation SCA-MSSP Read Subscription
Description Read a subscription and associated subscribed services
Pre-conditions Subscriber and subscription exists
Post-conditions
No modification
SuM Info Model related Inputs SuMSubscribedServiceGroup IOC, SuMSubscribed Service IOCs
NOTE: According to the input, the read operation may concern the whole set of
subscribed services or only a part.
SuM Info Model related Outputs SuMSubscribedServiceGroup IOC, SuMSubscribed Service IOCs

6.2 Manage Subscription by Subscriber (SCA-MSS)
The SCA-MSS NOSI is dealing with the following part of the SuM Info model:
• SuMSubscriberProfile IOC.
• SuMService IOC.
• SuMSubscribedServiceGroup IOC.
• SuMSubscribedService IOCs.
NOTE 1: The subclasses of the SuMSubscribedService and SuMService IOCs are involved in the SCA process.
These classes contain also attributes belonging to the Resource Provisioning process, and the implications
of this are for further study.
NOTE 2: The SCA-MSS operations are similar to the SCA-MSSP ones but the behaviour would be different
according to what the subscriber is allowed to do.
Operation SCA-MSS Create Subscription
Description Create a subscription with associated subscribed services
Pre-conditions Subscriber exists
Post-conditions
The subscription with its set of Subscribed services has been created
SuM Info Model related Inputs SuMSubscriberProfile IOC, SuMService IOCs
SuM Info Model related Outputs SuMSubscribedServiceGroup IOC, SuMSubscribedService IOCs

ETSI
16 ETSI TS 188 002-3 V2.0.0 (2008-03)

Operation
SCA-MSS Delete Subscription
Description
Delete a subscription with associated subscribed services
Pre-conditions Subscriber and subscribed services exists
Post-conditions The subscription with its set of Subscribed services has been deleted
SuM Info Model related Inputs SuMSubscriberProfile IOC, SuMSubscribedServiceGroup IOC
SuM Info Model related Outputs None identified

Operation SCA-MSS Update Subscription
Description
Update a subscription and/or a
...