Subscription Management for TISPAN NGN Network Entities

1. WG8 presentation of current Subscription Management ActivitiesTISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15th 2007. Source: Idir FODIL, Rapporteur France Telecom Group (idir.fodil@orange-ftgroup.com)

2. P-CSCF AS PDBF Subscription Management Selling (CRM) End to End Info Model Service Configuration & Activation (SM&O) Subscriber Resource Provisioning Distribute, Retrieve, …. Data Across Nodes Manage Relations (IMS Functions  Nodes)

3. TISPAN Subscription Management • Objectives: • Allows service providers to provision their TISPAN NGN network entities with the data necessary for delivering services for a specific subscriber. • allows subscribers to configure their services when they have these capabilities. • Consist in the specification of: • An end-to-end information model to cover all the mandatory/optional information related to subscription management that shall be provisioned on the NGN Network. • A subscription management functional architecture which hides the complexity of the different functional entities to be configured including the CPE and the AS.

4. Overview • Allows service providers to leverage their network resources to: • Validate (register, authenticate, and authorize.) a request for service from a user; • Collect, store, update, and distribute the Service Profile information for the user; • Select the trusted network resources to manage access, distribution, and control of the profile data information for the user; and • Direct the network resources to promptly deliver the service requested to the user according to said profile information. • fulfils the following essential TISPAN NGN requirements: • "User equipment Diversity" allows the users to access their TISPAN NGN services by a variety of UEs. • "Service Diversity" allows the users to access TISPAN NGN services provided by service providers or third party application server providers. • "Access Diversity" allows the users to access their TISPAN NGN services over a wide variety of network access such as xDSL, WLAN, GPRS, etc. • "Noamdism": allows the users to access their TISPAN NGN services in multiple nomadism scenarios.

5. Standards in Progress • 3 Work Items • 08015-1: Subscription Management Requirements (TS 188 002-1) • 08015-2: Subscription Management Information Model (TS 188 002-2) • 08015-3: Subscription Management Functional Architecture (TS 188 002-3) • Currently • Requirements: draft v0.0.10 : 12tTD350r1 • Approved standard • Information Model : draft v0.0.5 • Functional Architecture: table of contents.

6. SUM from ETOM Business Processes View

7. Service Provider Service Delivery Customer Care Subscription Management Other Applications CPE UPSF NASS AS NGN Functional Entities SUM Functional View Subscriber Subscribe Configure Give rights Assign Services Users Use Services Customize Services

8. SuM Requirements • Some Definitions • Offered Services, Subscribed Services, User Assigned Services, User Activated & Customized Services" • Value Chain Model • Definition of a high level use case • Definition of detailed use cases • Help in the design of the information model and the specification of the provisioning interfaces. • It was agreed to describe use cases using 3GPP TR 32.803: Process Guide: Use Cases in Unified Modelling Language (UML). • High Level Requirements • Requirements on Information Model • Re use of 3GPP SUM NRM if possible. • Requirements on Functional Architecture • Re use of 3GPP IRP and 3GPP GUP if necessary • Requirements on NGN entities • Security Requirements • Annex • Example Scenarios of TISPAN SuM

9. SuM Information Model • Current version: draft v0.0.5 • High Level Model • Identification of candidate entity groupings that need to be modelled, possible relations between those groupings and the associated candidate attributes. • Does not specify any information model, but is used as the basis for the design of the SuM Information Model. • The attributes are the one defined within TISPAN & 3GPP (Services, Architecture & protocols) + other attributes if needed • Information Object Classes • Based on 3GPP TS 32.151 Template. • Annex A: SuM Information Reference Table • Information used within this specification, and its corresponding definition and location in 3GPP and TISPAN specifications. • Annex B: Summary of SuM Information • Give the sub clause within this document where SuM Information are used.

10. Engaged in Subscription with a Service Provider Subscriber Commercial Relationship Consume Services Subscription User Credentials Network Access Network Access Profile NGN Service NGN Service Profile SuM High Level Model: Simplified View

11. Current SuM High Level IM

12. Subscriber/Subscription/User Management • Network Technology agnostic • Allocation and Configuration of Network Resources • Hides NGN Functional entities • Add/modify/remove related SuM Data NOSI Consumer NOSI Interface SuM Functional Architecture Objective: Design NGN OSS Service Interfaces (NOSI) Order Handling Service Configuration & Activation (SCA) TISPAN SUM NOSI Focus Resource Provisioning (RP) NGN Function Entities

13. TISPAN WG8 / 3GPP SA5 Subscription Managment Harmonization

14. TISPAN WG8 / 3GPP SA5 Harmonization • SuM Requirements • Definitions • Define common requirements for Fixed/Mobile Convergence ? • Use Cases ? • SuM Information Model • Needed in order to reuse the 3GPP SUM IRP • Start Harmonization from the High Level Model and not from the object classes. • SuM Functional Architecture • Study the NGN OSS Service Interface reuse of 3GPP IRP ? • At which level SUM IRP can be used according to eTOM ? • The use of 3GPP Generic User Profile ? • Need to take in account the 3GPP/TISPAN collaboration work • General Question : • What is 3GPP SA5 objectives and plan for Subscription Management in Next Releases ?

15. 3GPP SuM NRM Containment IOC Managed Element 1 1 <<names>> <<names>> 0..1 0..1 IOC Subscription Function IOC Service Provider Function 1 1 <<names>> <<names>> 0..n 0..n <<names>> +offer +contract IOC SuMService IOC SuMSubscriberProfile IOC SuMSubscribedService 1 0..n agreement 0..n 1 +specification 1 1 <<names>> description +service 0..n 0..n <<names>> IOC SuMSubscriptionProfile IOC SuMServiceProfile 1 0..n

16. Subscriber Profile 1 One Subscription = One User One User  1 IMPI + 1 IMPU 0..n Subscription Profile 1 1 0..n 0..n Subscribed Service Service Profile 0..n 1 More attributes are needed Credentials? Network Accesses ? Simplified view of 3GPP SUM NRM TISPAN High Level Model

17. Proposal for 3GPP SuM NRM IS Reuse in TISPAN • In order to reuse the 3GPP SUM within TISPAN, we propose to proceed as follows • Review the 3GPP SUM NRM according to the TISPAN High level model • Introduce the concept of User • Introduce the network access • Some 3GPP SUM NRM IOC can be reused as they are with some modifications • SuMSubscriberProfile • SuMServiceProfile • SuMSubscribedService

18. TISPAN WG8 / 3GPP SA5 Harmonization • SuM Requirements • Definitions • Define common requirements for Fixed/Mobile Convergence ? • Use Cases ? • SuM Information Model • Needed in order to reuse the 3GPP SUM IRP • Start Harmonization from the High Level Model and not from the object classes. • SuM Functional Architecture • Study the NGN OSS Service Interface reuse of 3GPP IRP ? • At which level SUM IRP can be used according to eTOM ? • The use of 3GPP Generic User Profile ?

19. TISPAN SuM Functional Architecture vs 3GPP • Which part of the eTOM business process are realized by 3GPP SUM IRP ? • Service Configuration & Activation ? • Resource Provisioning ? • How 3GPP SUM IRP and 3GPP GUP are related to each other ? • Can we move current 3GPP SUM IRP toward SOA principles? • May be using Web Services ? • Is there any roadmap ?

20. SuMSubscriptionProfile Additional Slide3GPP SuMSubscriptionProfile IOC • This class represents user’s subscription profile of the services contracted by a subscriber. • This class contains Service Profiles for the services contracted by a subscriber and assigned to a user. One User is limited to a single: IMPI, IMPU