hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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 ETSI TS 188 002-3 V2.0.0 (2008-03) 12 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.
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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.
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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 ETSI TS 188 002-3 V2.0.0 (2008-03) 13 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
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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 ETSI TS 188 002-3 V2.0.0 (2008-03) 14 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.
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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.
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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.
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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 ETSI TS 188 002-3 V2.0.0 (2008-03) 15 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
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
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 ETSI TS 188 002-3 V2.0.0 (2008-03) 16 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 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 SuMSubscriberProfile IOC, SuMService IOCs, SuMSubscribedServiceGroup IOC, SuMSubscribedService IOCs SuM Info Model related Outputs None identified Operation SCA-MSS 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 SuMSubscriberProfile IOC, SuMSubscribedServiceGroup IOC, SuMSubscribedService IOC SuM Info Model related Outputs SuMSubscribedServiceGroup IOC, SuMSubscribed Service IOCs
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
6.3 Manage User(SCA-MU)
|
The SCA-MU NOSI is dealing with the following part of the SuM Info model: • SuMSubscriberProfile IOC. • SuMUser IOC. Operation SCA-MU Create User Description Create User with user general characteristics NOTE: This operation does not assign any service to the user. In practice, a user is at least associated to one service that will be achieved through the SCA MUS NOSI. Pre-conditions Subscriber exists Post-conditions The user has been created SuM Info Model related Inputs SuMSubscriber IOC, SuMUser IOC SuM Info Model related Outputs SuMUser IOC Operation SCA-MU Delete User Description Delete a user NOTE: This operation should also suppress all SuM Service profiles attached to the user. Pre-conditions Subscriber exists Post-conditions The user and its associated User Service profiles have been deleted SuM Info Model related Inputs SuMUser IOC SuM Info Model related Outputs None identified Operation SCA-MU Update User Description Update the profile of a user Pre-conditions Subscriber and User exist Post-conditions User updated SuM Info Model related Inputs SuMUser IOC SuM Info Model related Outputs None identified ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 17 Operation SCA-MU Read User Description Read the profile of a user Pre-conditions Subscriber and User exist Post-conditions No modification SuM Info Model related Inputs SuMUser IOC SuM Info Model related Outputs SuMUser IOC
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
6.4 Manage User Services(SCA-MUS)
|
The SCA-MU NOSI is dealing with the following part of the SuM Info model: • SuMUser IOC. • SuMSubscribedService IOCs. • SuMServiceProfile IOCs (IMSServiceProfile IOC, ApplicationServiceProfile IOC, NgnNetworkAccessProfile IOC). NOTE 1: The subclasses of the SuMSubscribedService and SuMServiceProfile 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. Operation SCA-MUS Create User Services Description Assign subscribed services to the user Pre-conditions Subscriber, subscription with subscribed services, user exist Post-conditions The user with its service profiles for subscribed services has been provisioned The execution of this operation will create related instances of SuMServiceProfile IOC subclasses according to the SuMSubscribedService instances SuM Info Model related Inputs SuMUser IOC, SuMSubscribedService IOCs, NgnSuMCredentials IOC SuM Info Model related Outputs None identified NOTE 2: The handling of credentials through this NOSI is for further study. Operation SCA-MUS Delete User Services Description Delete services assigned to a user Pre-conditions Subscriber, user and User Service profiles exist Post-conditions The concerned user services have been deleted The execution of this operation will delete related instances of SuMServiceProfile IOCs SuM Info Model related Inputs SuMUserIOC, SuMServiceProfile IOCs SuM Info Model related Outputs None identified Operation SCA-MUS Update User Services Description Update user services Pre-conditions Subscriber, user and User Service profiles exist Post-conditions The services assigned to the user have been modified The execution of this operation will update related instances of SuMServiceProfile IOCs in the respect of subscribed services SuM Info Model related Inputs SuMUser IOC, SuMSubscribedService IOCs, SuMServiceProfile IOCs SuM Info Model related Outputs None identified Operation SCA-MUS Read UserServices Description Read user services Pre-conditions Subscriber, user and User Service profiles exist Post-conditions No modification SuM Info Model related Inputs SuMUser IOC, SuMServiceProfile IOCs SuM Info Model related Outputs SuMServiceProfile IOCs ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 18
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
7 SuM Resource Provisioning NOSI
|
This clause contains the description of the SuM Resource Provisioning NOSIs identified in clause 5.1.
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
7.1 Subscription Services (RP-SS)
|
The RP-SS NOSI is dealing with the following part of the SuM Info model: • SuMUser IOC. • SuMServiceProfile IOCs (IMSServiceProfile, ApplicationServiceProfile), User ServiceInstance IOCs, NgnSuMCredentials IOC, IMSPublicIdentification IOCs. NOTE: The IOCs here listed are all associated to the user and to the services of a subscription that are assigned to the user. It is not here considered there may be other data associated to the subscription, but not to the user. Operation RP-SS Configure Subscription Services Description Configure subscription and user information related to IMS, and Applications, (it does not concern NGN network Access) Pre-conditions Subscriber, subscription with subscribed services, user exist Post-conditions The user with its service profiles has been configured SuM Info Model related Inputs SuMUserIOC, SumServiceProfile IOCs (IMSServiceprofile IOC, ApplicationServiceProfile IOC), UserServiceInstance IOC, NgnSuMCredentials IOC, IMSPublicIdentification IOCs SuM Info Model related Outputs None identified Operation RP-SS Remove Subscription Services Description Remove subscription and user information related to IMS service and Application services Pre-conditions Subscriber, user and User Service profiles exist Post-conditions The user services profiles have been deleted SuM Info Model related Inputs SuMUser IOC, SumServiceProfile IOCs (IMSServiceProfile IOC, ApplicationServiceProfile IOC), UserServiceInstance IOCs, NgnSuMCredentials IOC, IMSPublicIdentification IOC SuM Info Model related Outputs None identified Operation RP-SS Update Subscription Services Description Update subscription and user information related to IMS services and Application services Pre-conditions Subscriber, user and user service profiles exist Post-conditions The user services profiles have been updated SuM Info Model related Inputs SuMUser IOC, SumServiceProfile IOCs (IMSServiceprofile IOC, ApplicationServiceProfile IOC), NgnSuMCredentials IOCs, IMSPublicIdentification IOCs SuM Info Model related Outputs None identified Operation RP-SS Read Subscription Services Description Read subscription and user information related to IMS services and Application services Pre-conditions Subscriber, user and user service profiles exist Post-conditions No modification SuM Info Model related Inputs SuMUserIOC, SumServiceProfile IOCs (IMSServiceProfile IOC, ApplicationServiceProfile IOC), UserServiceInstance IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOC SuM Info Model related Outputs SumServiceProfile IOC (IMS ServiceProfile IOC, ApplicationServiceProfile IOC), User ServiceInstance IOC, NgnSuMCredentials IOC, IMSPublicIdentification IOC ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 19
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
7.2 User Preferences (RP-UP)
|
The RP-UP NOSI is dealing with the following part of the SuM Info model: • UserServiceInstance IOCs, IMSServiceProfile IOC, ApplicationServiceProfiles IOC. Operation RP-UP Configure preferences for user Description Configure user preferences in IMS services and Application services Pre-conditions Subscriber, subscription with subscribed services, user, user service profiles exist Post-conditions The preferences for the user have been configured SuM Info Model related Inputs SuMUser IOC, UserServiceInstance IOCs and possibly SumServiceProfile IOC (IMSServiceProfile IOC, ApplicationServiceProfile IOC) SuM Info Model related Outputs None identified Operation RP-UP Remove preferences for user Description Remove user preferences in IMS services and Application services Pre-conditions Subscriber, subscription with subscribed services, user, user service profiles exist Post-conditions The preferences for the user have been removed SuM Info Model related Inputs SuMuser IOC, UserServiceInstance IOCs and possibly SumServiceProfileIOC (IMSServiceProfileIOC, ApplicationServiceProfile IOC) SuM Info Model related Outputs None identified Operation RP-UP Update preferences for user Description Update user preferences in IMS services and Application services Pre-conditions Subscriber, subscription with subscribed services, user, user service profiles exist Post-conditions The user preferences have been updated SuM Info Model related Inputs SuMuserIOC, UserServiceInstance IOCs and possibly SumServiceProfile IOC (IMSServiceProfile IOC, ApplicationServiceProfile IOC) SuM Info Model related Outputs None identified Operation RP-UP Read preferences for user Description Read user preferences in IMS services and Application services Pre-conditions Subscriber, subscription with subscribed services, user, user service profiles exist Post-conditions No modification SuM Info Model related Inputs SuMUser IOC, UserServiceInstance IOC and possibly SumServiceProfile IOC (IMSServiceProfile IOC, ApplicationServiceProfile IOC) SuM Info Model related Outputs UserServiceInstance IOCs and possibly SumServiceProfile IOC (IMSServiceProfile IOC, ApplicationServiceProfile IOC)
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
7.3 Subscription Network Access (RP- SNA)
|
The RP-SNA NOSI is dealing with the following part of the SuM Info model: • NgnSubscribedNetworkAccess IOC, NgnPhysical Access IOC, NgnLocation IOC, NgnLogicalAccess. • NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfile IOC. Operation RP-SNA Configure Network Access for user/subscription Description Configure subscription and user information of a TISPAN Network Access (NASS) Pre-conditions Subscriber, subscription with a Network Access subscribed service exists Post-conditions The subscription and user information of a TISPAN Network Access (NASS) has been configured SuM Info Model related Inputs NgnSubscribedNetworkAccess IOC, NgnPhysical Access IOC, NgnLogicalAccess SuMUser IOC (NASSUser), NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfile IOC SuM Info Model related Outputs None identified ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 20 Operation RP- SNA Remove Network Access for user/subscription Description Remove subscription and user information of a TISPAN Network Access (NASS) Pre-conditions The concerned TISPAN Network Access (NASS) and its configuration exists Post-conditions The subscription and user information of a TISPAN Network Access (NASS) has been removed SuM Info Model related Inputs NgnSubscribedNetworkAccess IOC, NgnPhysical Access IOC, NgnLogicalAccess SuMUser IOC (NASSUser), NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfile IOC SuM Info Model related Outputs None identified Operation RP- SNA Update Network Access for user/subscription Description Update subscription and user information of a TISPAN Network Access (NASS) Pre-conditions The concerned TISPAN Network Access (NASS) and its configuration exists Post-conditions The subscription and user information of a TISPAN Network Access (NASS) has been updated SuM Info Model related Inputs NgnSubscribedNetworkAccess IOC, NgnPhysical Access IOC, NgnLogicalAccess SuMUser IOC (NASSUser), NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfile IOC SuM Info Model related Outputs None identified Operation RP- SNA Read Network Access for user/subscription Description Read subscription information and user of a TISPAN Network Access (NASS) Pre-conditions The concerned TISPAN Network Access (NASS) and its configuration exists Post-conditions No modification SuM Info Model related Inputs NgnSubscribedNetworkAccess IOC, NgnPhysical Access IOC, NgnLogicalAccess IOC SuMUser IOC (NASSUser), NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfile IOC SuM Info Model related Outputs NgnSubscribedNetworkAccess IOC, NgnPhysical Access IOC, NgnLogicalAccess NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfile IOC
|
102966fe8d7c74cf46752c05d8b3d701
|
188 002-3
|
8 SuM NGN Functional entities NOSIs
|
This clause contains the description of the SuM NGN Functional entities NOSIs identified in clause 5.1. The NGN FE-MD NOSIs are dealing with the following part of the SuM Info model: • For UPSF: IMSUserProfile IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOCs, IFC IOCs, IRSET IOCs and relevant Ids. • ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on the UPSF). • For AS: ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on AS). • For PDBF: NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfileIOC. • For CLF: NgnPhysicalAccess IOC, NgnLocationIOC, NGNLogicalAccess IOC. NOTE: The NGN FE NOSIs support the same type of operations with the different NGN FEs (UPSF, PDBF, CLF, AS), but the transferred data are different from a NGN FE to another. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 21 Operation NGN FE-MD Create Data Description Create Data in a NGN FE (UPSF, AS, PDBF, CLF) Pre-conditions The concerned data do not exist in the concerned NGN FE Post-conditions The concerned data have been created in the concerned NGN FE SuM Info Model related Inputs For UPSF: IMSServiceProfile IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOCs, IFC IOCs, IRSET IOCs ApplicationServiceProfiles IOC, UserServiceInstance IOC (when stored on the UPSF) For AS: ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on AS) For PDBF: NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfileIOC For CLF: NgnPhysicalAccess IOC, NGNLogicalAccess IOC SuM Info Model related Outputs None identified Operation NGN FE-MD Delete Data Description Delete Data in a NGN FE (UPSF, AS, PDBF, CLF) Pre-conditions The concerned data exists in the concerned NGN FE Post-conditions The concerned data have been deleted in the concerned NGN FE SuM Info Model related Inputs For UPSF: IMSServiceProfile IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOCs, IFC IOCs, IRSET IOCs, ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on the UPSF) For AS: ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on AS) For PDBF: NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfileIOC For CLF: NgnPhysicalAccess IOC, NgnLocationIOC, NGNLogicalAccess IOC SuM Info Model related Outputs None identified Operation NGN FE-MD Update Data Description Update Data in a NGN FE (UPSF, AS, PDBF, CLF) Pre-conditions The concerned data exists in the concerned NGN FE Post-conditions The concerned data have been updated in the concerned NGN FE SuM Info Model related Inputs For UPSF: IMSServiceProfile IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOCs, IFC IOCs, IRSET IOCs, and relevant Ids ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on the UPSF) For AS: ApplicationServiceProfile IOCs, UserService-Instance IOC (when stored on AS) For PDBF: NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfileIOC For CLF: NgnPhysicalAccess IOC, NgnLocationIOC, NGNLogicalAccess IOC SuM Info Model related Outputs None identified Operation NGN FE-MD Read Data Description Read Data in a NGN FE (UPSF, AS, PDBF, CLF) Pre-conditions The concerned data exists in the concerned NGN FE Post-conditions No modification SuM Info Model related Inputs For UPSF: IMSServiceProfile IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOCs, IFC IOCs, IRSET IOCs ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on the UPSF) For AS: ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on AS) For PDBF: NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfileIOC For CLF: NgnPhysicalAccess IOC, NGNLogicalAccess IOC SuM Info Model related Outputs For UPSF: IMSServiceProfile IOCs, NgnSuMCredentials IOCs, IMSPublicIdentification IOCs, IFC IOCs, IRSET IOCs ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on the UPSF) For AS: ApplicationServiceProfile IOCs, UserServiceInstance IOC (when stored on AS) For PDBF: NgnNetworkAccessProfile IOC, NgnNetworkAccessSubProfileIOC For CLF: NgnPhysicalAccess IOC, NGNLogicalAccess IOC ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 22 Annex A (informative): Relation with 3GPP Generic User Profile (GUP) A.1 3GPP GUP Overview The objective of 3GPP Generic User Profile (GUP) [4], [5], [6], [7] is to provide means to enable harmonized usage of the user-related information originating from different entities, and allow extensibility to cater for future developments. The 3GPP Generic User Profile: • Is a Collection of User-related data. • Can be stored in the home network environment and/or Value Added Service Provider equipment. • Can be accessed by different stakeholders and managed either by one (centralized) or by different stakeholders (de-centralized) such as the user, subscriber, value added service provider and network operator by a standardized access mechanism. • Allows intra-network usage (i.e. data exchange between applications within a mobile operator's network) and inter-network usage (between mobile operator's network and value added service providers). • May be also be used by different applications in a standardized way. The 3GPP Generic User Profile consists in the following technical aspects: • Architecture + Information Model. • Data Description. • Interface with mechanisms to handle the data. A.1.1 Architecture The GUP Architecture as depicted in the figure consists of: • GUP Server: functional entity providing a single point of access to the Generic User Profile data of a particular subscriber. The GUP Server may be located in the home operator network of the targeted subscriber. The GUP Server includes the following functionalities: - Single point of access for reading and managing generic user profile data of a particular subscriber. - Location of Profile Components. - Authentication of profile requests. - Authorization of profile requests. - Synchronization of Profile Components. • Repository Access Function (RAF): realizes the harmonized access interface. It hides the implementation details of the data repositories from the GUP infrastructure. • GUP Data Repositories: Each GUP Data Repository stores the primary master copy of one or several profile components. The RAF provides for the standardized access to the GUP Data Repository. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 23 • Rg and Rp reference points: The Rg reference points may allow applications to create, read, modify and delete any user profile data using the harmonized access interface. The Rp reference point may allow the GUP Server or applications, excluding external applications (e.g. located in a third party application or in the UE), to create, read, modify and delete user profile data using the harmonized access interface. Rp is an intra- operator reference point. • Applications: The applications that may apply GUP reference points Rg and Rp may be targeted for different purposes e.g. for value added services or subscription management. Both operator's own applications and third party applications are covered. Application in UE Application in HPLMN (e.g. SMSC, etc.) Application in 3rd party SP HPLMN Nodes (e.g. HSS/HLR/ VLR, PPR, etc.) Application Servers (e.g. IMS AppServer, etc.) RAF RAF RAF Management Servers (e.g. CRM, etc.) GUP Server Rp Rg Dash line --- communication can take place directly between Application in HPLMN and GUP Data Repositories Rp Figure A.1: An example of mapping the GUP reference architecture to current infrastructure environment A.1.2 Information Model A Generic User Profile consists of a number of independent GUP Components. However, a GUP Component may contain (i.e. reference) other GUP components e.g. to enable reuse of data. The GUP Component has a unique identity within the Generic User Profile. In addition to the component type the component identity contains either a subscriber identity or more generic identification depending on which kind of component is in question. A GUP Component can be retrieved through one RAF, and it may consist of a number of GUP Components, Data Element Groups and/or Data Elements. The UML Class Diagram below illustrates the basic concepts of the GUP Information Model. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 24 1 0..* 1 0..* 0..* 1 1 1..* 1 0.. * * 1 Generic User Profile Identity Data Element GUP Component Data Element group Group type Composite Datatype Figure A.2: Example of the structure of GUP information A.1.3 Interfaces Communication between GUP entities is performed via the exchange of messages expressed as XML documents. XML documents should include the XML declaration with the version and encoding attributes. The XML documents may be well-formed and valid. The W3C XML Schema is used in GUP to define the structure of valid XML documents. The implementation of the Rp and Rg interfaces follows the Liberty Alliance Data Service Template specification [Liberty Alliance]. The GUP interfaces and procedures are SOAP protocol based. Each interface is defined in terms of the messages sent and received. The payload of each message is XML, defined using an XML schema language. The framework, procedures, SOAP binding and security solutions of GUP are based on the Liberty Alliance Project work. The definition of the interfaces can be divided into the following sections: • Definition of the operations (WSDL/XML). • Common functions like security, authentication and authorization (WSDL/XML). • Repository Access Function specific data contents for the operations (XML Schema). A.1.4 Data Description Method The Data Description Method can be viewed as a set of templates for constructing the data description. The templates (sets of rules) enable the standardization of the data description such that it and the described data can be shared (used) by many applications. The data descriptions are abstract in the sense that the data are described independently of data formats specific to data storage, transport protocols or application technologies. Abstraction of data descriptions simplifies the mapping between different data formats, and facilitates future extensions. The common use of the Data Description Method will avoid incompatibilities and inconsistencies between different Profile Components. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 25 A.2 3GPP GUP and TISPAN SuM Functional Architecture This clause analyses the possible reuse of 3GPP GUP Standards for TISPAN SuM Functional Architecture when considering: • The commonalities regarding requirements for GUP or TISPAN SuM Functional Architecture (Stage 1). • The commonalities regarding the architecture for GUP or for SuM (Stage 2). • The commonalities regarding the solutions sets (Stage 3). A.2.1 Commonalities regarding requirements Without going into a detailed analysis of GUP requirements as defined in TS 122 240 [4], this clause indicates many points where GUP objectives and requirements map to those of TISPAN SUM. TS 122 240 [4], clause 4.1, in its introduction mentions: • The objective of specifying the 3GPP Generic User Profile is to provide a means to enable harmonized usage of the user-related information originating from different entities. ….. • The 3GPP Generic User Profile is the collection of User-related data which affects the way in which an individual user experiences services where a community of entities share this data. The 3GPP Generic User Profile can be stored in the home network environment and/or Value Added Service Provider equipment. • The 3GPP Generic User Profile will be accessed by different stakeholders and managed either by one (centralized) or by different stakeholders (de-centralized) such as the user, subscriber, value added service provider and network operator by a standardized access mechanism. (….) • The 3GPP Generic User Profile may be also be used by different applications in a standardized way. • The 3GPP Generic User Profile will help to create and manage the user data in each entity and on the other hand to make it easier to find all user related data as a whole in the home network environment. These GUP objectives maps with TISPAN SUM ones as they focus on user related data that are distributed on different entities. They are accessed by different stakeholders (user, subscriber, service provider) that have also been identified as such in the SuM requirements. It also addresses the user data related to applications that constitute an important part of SuM. Its design allows the creation and the management of user data distributed over different entities. General way to access user data It should be noted that GUP can be used in other areas than Subscription Management, as it allows access to user data stored in an entity by other entities (e.g. when different applications cooperate, they may access to user data stored or managed by another one, also when a third party application need to access user data stored in the operator network, with relevant access rights). GUP is a general way to access and manage user data. In a GUP environment, Subscription Management is one process among others that have to access user data. It seems important to avoid to develop two interfaces to access user data, one dedicated to Subscription Management, one used for other applications. Support of Applications in particular with non standardized services TS 122 240 [4], clause 4.1.2, explicitly mentions that: • Subscription Management benefits from a standardized way to access subscription data of a user. • (….) new services in 3GPP are not standardized. Therefore content and format of subscription data as well as the places (repositories) where subscription data are stored may be different for different new services. GUP specifies the description of - and access of data in a standardized way. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 26 It should be noted that GUP addresses non standardized services, by defining a minimum set of rules allowing to describe and access data in a standardized way. It allows to introduce new applications with their specific user data in a flexible way without impacting other entities. It corresponds to a SuM objective to support provisioning of NGN Services including those, non standardized, offered by Application Servers. Synchronization of data TS 122 240 [4], clauses 4.4 and 6.5, identifies the need to keep synchronized GUP data components stored in different repositories, that SuM functional Architecture has also to address. Stakeholder requirements TS 122 240 [4], clause 5, describes requirements regarding stakeholders quite close to the TISPAN SuM ones: • The subscriber may hold subscriptions for one user (..;) or several users (…) • The subscriber may be able to customize her subscribed services and interrogate customization settings, subject to limitations by the Home operator and/or value added service provider.(…) • The user may be able to customize the services, that have been subscribed to her by the subscriber and interrogate customization settings, subject to limitations by the Home operator and/or value added service provider and/or subscriber. General Service Requirements TS 122 240 [4], clause 6.3, mentions: It may be possible for an application to retrieve the whole user profile or selected parts of it in one transaction. A.2.2 Commonalities regarding Architecture (Stage 2) Reference points Rp and Rg The reference Architecture of TS 123 240 [5] describes two reference points Rp and Rg that fit with the reference points (NOSIs) identified in the SUM Functional Architecture: • 3GPP GUP Rp corresponds to the NGN FE NOSI. Both are used to access and manage the user data stored on NGN FE. • 3GPP GUP Rg corresponds to the RP NOSIs, that hide the network topology, offer a single point of access and allow synchronization of profile components. Repository Access Function (RAF) The RAF function realizes the harmonized Rp access interface. It hides the implementation details of the data repositories from the GUP infrastructure real. It correspond to the fact that in SuM Functional Architecture, NGN FEs should expose NOSIs with the same characteristics to access the data, regarding the operations and the way to structure the data, the difference being in the data themselves that are specific to each type of NGN FE. Structure of data The SuM Functional Architecture should support a large variety of user profiles, dependent of the NGN services offered, in particular from applications servers. There is the need to structure the user data by grouping them in independent components. The word "independent" is important, as when adding a new application with its own user profiles, it should not impact the user data of other applications and avoid incompatibilities. TS 123 240 [5], clause 5 defines an info model, and TR 123 941 [6], a Data Description Method that describes a way to structure the data in GUP components to answer the same type of requirement as for SuM. The GUP component concept allow the independence of applications and their user profiles and offer the way to process these components individually. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 27 Operations The operations that TS 123 240 [5] describes for Rp and Rg interfaces (Create, Delete, Modify, Query, Subscribe, Notify) corresponds to the operations defined respectively for NGN FE NOSIS and RP NOSIs. Able to contain several data components, they allow data synchronization within one data repository or several. A.2.3 Commonalities regarding Solution Sets (Stage 3) The TISPAN SuM functional architecture does not address stage 3 specifications, it is nevertheless worthwhile to note a certain number of Stage 3 GUP characteristics that are of interest for SuM. 3GPP GUP stage 3 relies on: • Web services described by wsdl files. • Data structure described through XML data scheme (xsd) files. • Liberty Alliance standards in particular for the definition of operations. • use of different name spaces guaranteeing independence of the user profiles. • use of a subset of Xpath language to retrieve the components. The use of Web Services is conform to the TISPAN OSS Architecture for NGN Management [1]. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 28 Annex B (informative): Relation with 3GPP Integration Reference Points (IRPs) B.1 3GPP IRP Introduction and overview References: TS 132 101 [11] and 132 150 [12]. IRP (Integration Reference Point): an architectural concept that is described by a set of specifications for definition of a certain aspect of a management interface, comprising a Requirements specification, an IRP Information Service specification, and one or more IRP Solution Set specifications. For the purpose of management interface development 3GPP has developed an interface concept known as Integration Reference Point (IRP) to promote the wider adoption of standardized management interfaces in telecommunication networks. The IRP concept and associated methodology employs protocol and technology neutral modelling methods as well as protocol specific solution sets to achieve its goals. B.1.1 General The three cornerstones of the IRP concept are: • Top-down, process-driven modelling approach: The purpose of each IRP is automation of one specific task, related to TMF TOM. This allows taking a "one step at a time" approach with a focus on the most important tasks. • Technology-independent modelling: To create from the requirements an interface technology independent model. This is specified in the IRP Information Service. • Standards-based technology-dependent modelling: To create one or more interface technology dependent models from the technology independent model. This is specified in the IRP Solution Set(s). IRP Information Service AlarmIRPNotification notify() <<Interface>> System use AlarmIRPOperations acknowledgeAlarms() unacknowledgeAlarms() getAlarmList() selectAlarmIRPVersion() getA larmCount() <<Interface>> implement Actor use implement IRP INFORMATION SERVICE AlarmIRPNotification notify() <<Interface>> System use AlarmIRPOperations acknowledgeAlarms() unacknowledgeAlarms() getAlarmList() selectAlarmIRPVersion() getA larmCount() <<Interface>> implement Actor use implement IRP REQUIREMENTS IRP SOLUTION SETS SNMP SNMP JAVA XML CMIP CMIP CORBA CORBA + Figure B.1: IRP components (with example Solution Sets; for definition of valid 3GPP Solution Sets, see annex C in TS 188 001 [1]) ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 29 B.1.2 IRP Specifications Approach As highlighted in the previous clause, IRP specifications are specified using a 3-level approach: Requirements, IS-level and SS-level. Furthermore, there are three categories of IRP specifications (see formal and more detailed definitions in clause 3.1): • Interface IRPs. • NRM IRPs. • Data Definition IRPs. Each category is partitioned into Requirements, IS-level and SS-level specifications. Solution Set Definitions (other/future e.g. JAVA , SNMP) Requirements / Use Cases Solution Set Definitions (CORBA, SOAP, XML, CMIP) Relative stable over long period of time Changes with new/better Technologies Changes only with respect to addition and extensions Interface IRP’s • Notification IRP • Alarm IRP • BulkCM IRP • KernelCM IRP • BasicCM IRP • etc NRM IRP’s • Generic NRM • CoreNW NRM • UMTS NRM’s • CDMA NRM’s • Inventory NRM • etc Data Definition IRP’s •State Mgmt IRP • etc Information Service Definitions (UML) Figure B.2: The IRP 3-Level Specifications Approach combined with the three IRP categories Level 1: The "Requirements-level" intends to provide conceptual and use cases definitions for a specific management interface aspect as well as defining subsequent requirements for this IRP. Level 2: The "IS-level" provides the technology independent specification of an IRP. Level 3: The "SS-level" finally provides the mapping of IS definitions into one or more technology-specific Solution Sets. This concept provides support for multiple interface technologies as applicable on a vendor and/or network type basis and also enables accommodation of future interface technologies - without the need to redefine requirements and IS-level definitions. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 30 B.2 Architecture The 3GPP IRPs were originally developed to support the management interfaces Itf-N and Itf-P2P in the following reference architecture: Organization A Enterprise Systems NE NE NE NE EM NE EM 5 4 5 6 DM Organization B DM DM 2 2 2 4a 4a 2 1 1 1 1 5a EM EM EM 3 3 Itf-N Operations Systems Itf-P2P 2 NM NM Figure B.3: 3GPP management reference model However, due to a more generalized definition of the IRP, as seen in the first paragraph of clause B.1, the IRP concept and interface specifications are today applicable to any management interface or reference point, e.g. management interfaces/NOSIs defined by TISPAN, both the SCA layer, the RP layer as well as the NGN FE layer. As can be seen in figure B.1, those layers also have many similarities with the various scenarios for 3GPP management interface 2. B.3 IRP SOAP Solution Sets The 3GPP IRP specifications of the table below are supported by SOAP Solution Sets which were created in particular for SuM in 3GPP. These IRPs are described here as candidates for reuse by TISPAN within SuM NOSIs, not excluding the possible relevance of other 3GPP IRPs. The Requirements, Information Service (IS) and SOAP Solution Sets of the Interface IRPs for 3GPP SuM are the listed below. The Requirements, Information Service (IS) and XML file format/schema definitions of the NRM IRPs for 3GPP SuM are also listed below. 3GPP identifies system contexts of the Interface IRP in terms of its implementation, called IRPAgent, and the user of the IRPAgent, called IRPManager. These terms are used in the subsequent clauses. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 31 IRP short name Part Number, Title Requirements TS 132 311: Generic Integration Reference Point (IRP) management: Requirements [13] IS TS 132 312: Generic Integration Reference Point (IRP) management: Information Service (IS) [14] Generic IRP SOAP TS 132 317: Generic Integration Reference Point (IRP) management; SOAP solution set [15] Requirements TS 132 301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements [16] IS TS 132 302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS) [17] Notification IRP SOAP TS 132 307: Configuration Management (CM); Notification Integration Reference Point (IRP): SOAP solution set [18] Requirements TS 132 661: Configuration Management (CM); Kernel CM Requirements [19] IS TS 132 662: Configuration Management (CM); Kernel CM Information Service (IS) [20] XML TS 132 665: Configuration Management (CM); Kernel CM Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions [21] Kernel CM IRP SOAP TS 132 667: Configuration Management (CM); Kernel CM Integration Reference Point (IRP): SOAP solution set [22] Requirements TS 132 601: Configuration Management (CM); Basic CM Integration Reference Point (IRP): Requirements [23] IS TS 132 602: Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS) [24] Basic CM IRP SOAP TS 132 607: Configuration Management (CM); Basic CM Integration Reference Point (IRP): SOAP solution set [25] Requirements TS 132 621: Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements [26] IS TS 132 622: Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) [27] Generic NRM IRP XML TS 132 625: Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition [28] Requirements TS 132 171: Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements [8] IS 3GPP TS 32.172: Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) [9] SuM NRM IRP XML TS 132 175: Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition [10] B.4 Overview of IRPs related to SOAP SSs B.4.1 Generic IRP The Generic IRP (ETSI TS 132 31x) defines some generic data and operations used by all Interface IRPs. Therefore, this IRP is necessary to reuse when reusing Interface IRPs. B.4.2 Notification IRP The Notification IRP (ETSI TS 132 30x) provides basic definitions and operations to send notifications. The basic idea is that an IRPManager subscribes to notifications of events sent by an IRPAgent, where the trigger condition for sending the notification is specified during establishment of the subscription. The operations to manage establishment and modification of a subscription to notifications includes: • subscribe, unsubscribe: To subscribe and unsubscribe to notifications. • other operations to manage the subscription, such as changing the trigger condition, inquiring status, and suspend/resume. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 32 B.4.3 Kernel CM IRP The Kernel CM (Configuration Management) IRP (ETSI TS 132 66x) defines operations and notifications for Configuration Management. The following operation is specified: • getNRMIRPVersion: Used by an IRPManager to obtain the version(s) of the NRM IRP supported by the IRPAgent. The notifications are the following: • notifyObjectCreation, notifyObjectDeletion: To notify creation and deletion of objects. • notifyAttributeValueChange: To notify change of attribute value(s). • notifyCMSynchronizationRecommended: To notify a recommendation of synchronizing of data. • notifyStateChange: To notify a state or status change of an object. B.4.4 Basic CM IRP The Basic CM IRP (ETSI TS 132 60x) defines operations on Managed Object instances of a MIB (i.e. object instances of IOCs) defined by an NRM IRP. The information of the Managed Object instances and the attributes are transferred as part of the operations. The operations are the following: • getMoAttributes: To read attribute values of Managed Object instances. Scope/filter criteria may be specified, and this allows for a large variety of possibilities in selecting objects and attributes subject to read. • getContainment: To retrieve (name-)containment relations in the MIB. • cancelOperation: To cancel an ongoing Basic CM operation. • createMO: To create a Managed Object instance. In this operation it is also possible to specify attribute values. • deleteMO: To delete one or more Managed Object instances. • setMOAttributes: To set attributes of Managed Object instances. Attributes of one or several Managed Objects may be modified - based on the containment hierarchy and scope/filter criteria. B.4.5 Generic NRM IRP The Generic NRM IRP (ETSI TS 132 62x) specifies Information Object Classes (IOCs), attributes, relationships, etc., used by both Interface IRPs and other NRM IRPs. B.4.6 SuM NRM IRP The SuM NRM IRP IS (3GPP TS 32.172 [9]) is used as basis for the TISPAN SuM Information Model (TS 188 002-2 [3]). The XML file format definition is extendable to cover also the TISPAN specific parts of the model. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 33 B.5 3GPP IRPs and TISPAN SuM Functional Architecture This clause analyses the possible reuse of 3GPP IRPs for TISPAN SuM Functional Architecture when considering: • the commonalities regarding requirements for IRPs and TISPAN SuM Functional Architecture (Stage 1); • the commonalities regarding the architecture and information models for IRPs and for SuM (Stage 2); • the commonalities regarding the solution sets (Stage 3). B.5.1 Commonalities regarding requirements (Stage 1) B.5.1.1 General • The 3GPPs IRPs were developed to support (any) management interfaces, with CMISE/CRUD-like operations accessing/manipulating data defined in object-oriented information models. • Interface IRPs and NRM IRPs can be accessed by any entity acting as an IRPManager, which also includes a TISPAN NOSI consumer (in case the NOSI is defined to access an IRP interface). B.5.1.2 IRP support of SuM FA requirements in TS 188 002-1 The following table gives a high-level overview of the SuM requirements on Functional Architecture in TS 188 002-1 [2], clause 6.3, and whether a reuse of the 3GPP SuM NRM IRP (ETSI TS 132 17x) and corresponding SOAP SSs for Interface IRPs support each requirement or not. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 34 Requirement IRP support Comment R1) The SuM functional architecture may hide the complexity of the different functional entities to be configured including the CPE and the AS. Yes The SuM NRM IRP and extensions in the TISPAN SuM IM only model the IOCs and attributes etc., necessary for management. R2) The SuM functional architecture may allow management of necessary/optional data, operations and notifications related to Subscription Management. Yes Supported by 3GPP SuM NRM IRP (ETSI TS 132 17x) with TISPAN extensions, and corresponding SOAP SSs for Interface IRPs. R3) The SuM functional architecture may be easily extensible for the support of new operations, data, and notifications. Yes Supported by TISPAN extensions to the reused 3GPP IRPs. R4) The SuM functional architecture may define the NGN OSS Service Interfaces for the realization of the following processes: - SM&O Service Configuration and Activation process. - RM&O Resource Provisioning process. Yes Supported if the TISPAN NOSIs access relevant objects and data in the TISPAN SuM IM based on the 3GPP SuM NRM and related SOAP SSs. R5) The NOSIs related to Service Configuration & Activation may be network technology agnostic without any knowledge of the NGN functional entities that are involved. Yes The TISPAN SuM IM and 3GPP SuM NRM are network technology agnostic. R6) The NOSIs related to Resource Provisioning are responsible of NGN functional entities (including CPE and AS) management and may hide the complexity of the different NGN functional entities to the NOSIs related to Service Configuration and Activation. Yes See comment to R1 above. R7) The NOSIs related to Service Configuration and Activation may manage the configuration of new subscription, and support of the reconfiguration of installed subscription (either due to customer demand or problem resolution). Yes Supported by normal management operations (Create/Delete instance, Set attributes etc.) to/by the NOSIs accessing TISPAN SuM IM (based on 3GPP SuM NRM) or a more high-level operation. Such operations may be ordered directly by the NOSI consumer or generated by the NGN OSS Service itself as a result of a more high-level operation request. R8) the SuM Functional Architecture may comply with the eTOM Operation regarding Fulfilment as described in clause 4.2 with the following processes. To be verified This is most likely also supported by 3GPP IRP reuse, or at least not hindered by IRP reuse. There is ongoing work in 3GPP SA5 to update the high-level requirements in TS 132 101 [11] and corresponding IRP specifications as necessary to be in line with eTOM. R9) The SuM functional architecture should consider reuse as much as possible of 3GPP existing standards. Yes B.5.2 Commonalities regarding the architecture and information models (Stage 2) B.5.2.1 General • Interface IRPs are separated from, and independent of, the information model managed over the interface and thus can be used to manage any object-oriented information model. • The Generic NRM (TS 132 622 [27]) and SuM NRM (3GPP TS 32.172 [9]) are already being reused for the core part of the TISPAN SuM IM. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 35 B.5.2.2 Reference points As mentioned in clause B.2, due to the general definition of the IRP, the IRP concept and interface specifications are today applicable to any management interface or reference point, e.g. management interfaces defined by TISPAN (note: the TISPAN OSS architecture does NOT define any reference points). Thus, this supports the "loose coupling" between entities which is required for service management interfaces. The following diagram depicts various alternative scenarios with IRPManagers and an NGN OSS Service accessing various NOSIs, the latter acting as IRPAgents. Common Communication Vehicle NOSI exposed for the management of data stored in NGN FE RP NOSI SCA NOSI NGN OSS Basic Framework Services NOSIs FE Service FE Service FE Service RP Service RP Service RP Service SCA Service SCA Service SCA Service NGN OSS Basic Framework Services NOSI consumer/ IRPManager NOSI consumer/ IRPManager NOSI Consumer/ IRPManager A NOSI acting as IRPAgent A A A A Figure B.4: NOSI scenarios with IRPManagers/Agents B.5.2.3 Structure of data The IRP concept, and in particular the separation of Interface IRPs from NRM IRPs, allows any structure of data (and the relationships between data) to be managed. The implementation of the IOCs in the various NRM IRPs may be distributed arbitrarily throughout the network. B.5.2.4 Operations The operations that are defined by the various 3GPP Interface IRP specifications listed in B.3 above (Create, Delete, GetMoAttributes, SetMoAttributes, Subscribe, NotifyXyz) correspond to the operations defined respectively for all NOSIs (SCA, RP, NGN FE NOSIs). ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 36 B.5.3 Commonalities regarding Solution Sets (Stage 3) The TISPAN SuM functional architecture does not address stage 3 specifications, it is nevertheless worthwhile to note a certain number of 3GPP IRP SS characteristics that are of interest for SuM. 3GPP IRP SOAP Solution Sets for SuM comprise: • The SS provides a clear mapping of the Stage 2 (ISs for Interface IRP and NRM IRP) to Stage 3 (SS) specifications, which is in line with the TISPAN WG8 specification guidelines. And since there are many commonalities on the Stage 2 level, this also provides for many commonalities on the Stage 3 level. • Web services described by wsdl files (the use of Web Services is compliant to the TISPAN OSS Architecture for NGN Management [1]). • Data structures described through XML data scheme (xsd) files of NRM IRPs. • 3GPP uses name spaces for object instances as well as XSD schema that are perfectly reusable by TISPAN, thus guaranteeing globally unique identification of all IOC instances and XSD schema. • The SOAP Solution Sets support the XPath filter language (see W3C XPath 1.0 specification [29]). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex. ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 37 Annex C (informative): Bibliography ETSI TS 132 140: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscription Management (SuM) requirements (3GPP TS 32.140)". ETSI TS 132 141: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscription Management (SuM) architecture (3GPP TS 32.141)". ETSI ETSI TS 188 002-3 V2.0.0 (2008-03) 38 History Document history V2.0.0 March 2008 Publication
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
1 Scope
|
The purpose of the present document is the definition of the SuM Information model which is paramount for the NGN service delivery within TISPAN NGN. The present document contains the specification of an information model covering all the mandatory/optional information related to subscription management that shall be provisioned on the NGN Network. The information model described in the present document is developed according to the specifications of TISPAN R1. The purposes of the document are: • To capture the Subscription Management Information Model needs as expressed in [1]. • To satisfy the needs of the NGN OSS Service Interfaces (NOSI) defined in the Subscription Management Functional Architecture and to support their implementation in Solution Set interfaces.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-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.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
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 002-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Subscription Management; Part 1: Requirements". [2] ETSI ES 282 001: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [3] ETSI ES 282 007: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS) Functional Architecture". ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 7 [4] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [5] ETSI ES 283 034: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the diameter protocol". [6] ETSI TS 123 008: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Organization of subscriber data (3GPP TS 23.008 Release 7)". [7] 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)". [8] 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 Release 7)". [9] ETSI TS 132 300: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Configuration Management (CM); Name convention for Managed Objects (3GPP TS 32.300 Release 7)".
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
2.2 Informative references
|
[10] ETSI TS 123 218: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia (IM) session handling; IM call model; Stage 2 (3GPP TS 23.218 Release 7)". [11] ETSI TS 129 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents (3GPP TS 29.228 Release 7)". [12] ETSI TS 129 328: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents (3GPP TS 29.328 Release 7)". [13] ETSI TS 129 240: "Universal Mobile Telecommunications System (UMTS); 3GPP Generic User Profile (GUP); Stage 3; Network (3GPP TS 29.240 Release 7)".
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
3 Definitions and abbreviations
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 188 002-1 [1] and the following apply: IMS Service Profile: collection of service and user related data as defined in TS 129 228 NASS User ID: identity of the attached user at the network access NOTE Correspond to the Subscriber ID used in NASS specification [4]. Sub-Profile: set of user network profile information NOTE Each user network profile may be divided into sub-profiles. Subscribed Network Access: collection of data related to a network access subscribed by the subscriber Subscribed NGN Service: collection of data related to a NGN service subscribed by the subscriber ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 8 Subscriber: entity (associated with one or more users) that is engaged in a Subscription with a service provider NOTE The subscriber is allowed to subscribe and unsubscribe services, to register a user or a list of users authorized to use these services, and also to set the limits relative to the use that associated users make of these services. Subscription: commercial relationship between the subscriber and the service provider User: entity that consumes the services subscribed by the subscriber User NGN Network Access Profile: user profile in a specific network access User NGN Service Profile: collection of service and user related data
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AMF Access Management Function AS Application Server CLF Connectivity session Location and repository Function CNGCF CNG Configuration Function CNG Customer Network Gateway GPRS General Packet Radio Service IMS IP Multimedia Subsystem IOC Information Object Class NACF Network Access Configuration Function NASS Network Attachment SubSystem NGN Next Generation Network P-CSCF Proxy Call Session Control Function PDBF Profile Data Base Function S-CSCF Serving Call Session Control Function SuM Subscription Management TBD To Be Defined in next release UAAF User Access Authorization Function UE User Equipment UPSF User Profile Server Function
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4 High Level Model
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.1 Overview
|
In this clause, a general contextualization of Subscription Management within TISPAN is given. This clause is organized with an initial textual description, followed by a general diagram which aims to depict the "SuM High Level Model". The goal of SuM within the current TISPAN release is to provision the NGN functional entities with all information related to a specific subscriber in order to allow its users to use their services. The objective of the high level model is the identification of candidate entity groupings that need to be modelled, possible relations between those groupings and the associated candidate attributes. The High Level Model does not specify any information model, but is used as the basis for the design of the SuM Information Model. A Subscriber is an entity that is engaged in a subscription with a Service Provider. One or more Users can be associated to a subscriber, who is allowed to subscribe and unsubscribe services, to register a user or a list of users authorized to use these services, and also to set the limits relative to the use that associated users make of these services. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 9 An NGN Subscriber subscribes to NGN Services (e.g. VoIP, VoD, etc) and directly or indirectly to a set of Network Accesses (xDSL, etc.) This subscription covers two different aspects: • Subscription to the NGN Services. • Subscription to Network Accesses. A relationship between NGN services and network accesses is established, in that it is possible to "enjoy" specific NGN services over specific network accesses. The NGN Subscriber is engaged in a Subscription with a Service Provider. The NGN Subscriber may also be engaged in a subscription with a Network Access Provider. The entity which uses the NGN subscribed services/accesses is the User. The subscriber is responsible of the assignment of services/accesses and rights to its users. Each user may be associated to multiple subscribers, and one subscriber may be associated to multiple users. All the parameters related to the services and/or network accesses subscribed by the subscriber are included in a profile related to the subscriber. All the parameters related to the services and network accesses assigned to the user are stored in a profile related to the user. There is a relation between services assigned to the user and which network accesses on which these services can be used by the user. In order to use the NGN services, the user must proceed as follows: 1) Authenticate at Transport Layer: This transport layer may be the one provided by the Service Provider or may be another network access (in case of nomadism or roaming). In order to use the transport layer, the user must provide credentials in order to allow the authentication and authorization procedures with the NASS (network attachment subsystem). Network attachment through NASS is based on implicit or explicit user identity and authentication credentials stored in the NASS (see ES 282 004 [4]). On one network access, the user may use same credentials independently of the services he wants to launch. 2) Authenticate at Service Layer: allow the service provider to identify and authenticate the user at a service level. Within this phase, the user is authenticated by the service provider thanks to authentication procedures and to the credentials provided by the user. 3) Authenticate at Application Layer (Optional): this optional step enables the application provider to identify and authenticate the user for enabling his access to specific applications. Within this phase, the user is authenticated by the applications provider thanks to authentication procedures and to the credentials provided by the user. 4) Usage of the Service/Application: Once the user is authenticated and authorized at service/application level, he can use all the services/applications assigned to him by its subscriber. The relationship between the users, its access credentials and service/application credentials is the following: 1) For each network access and for each user, credentials are associated. 2) For each user, multiple service/applications credentials are associated. According to this description, a general contextualization of the TISPAN Subscription Management can be derived in a "high level model", depicted by the following diagram. For readability purposes, the following legend is proposed. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 10 0..* candidate management entity candidate relationship amongst entities cardinality of a relationship entity out of scope of current specification . text . text candidate management entity with associated attributes 0..* candidate management entity candidate relationship amongst entities cardinality of a relationship entity out of scope of current specification . text . text candidate management entity with associated attributes Subscriber User • User Identity Subscription • Subscription Identitfier User Service Instance • NGN Service Identifier • Service state • Service options • Service data Sub Profile • Sub Profile ID • Set of Logical Access ID • Network Access authentication data • Set of QoS profile info • Initial gate settings • Privacy indicator Physical Access • Physical Access ID Logical Access • Logical Access ID • RACS Point of Contact Location • Location Information Credentials • Private User Identity • Authentication Data • Authentication Schema User NGN Service Profile • User NGN Service Profile Identifier • Reference location • Registration Status • Bandwidth capacity per service • Subscribed Quality of Service User NGN Network Access Profile • NASS User ID • UAAF ID Subscribed NGN Service • NGN Service Identifier Subscribed Network Access • Network Access Identifier • Network Access Type 0..* 0..* 1..1 1..* 1..1 1..* 1..1 1..* 1..1 0..* 1..1 0..* 1..1 0..* 0..* 1..* 1..1 1..* 1..1 1..* 1..1 1..* 1..* 1..1 1..1 1..1 Figure1: TISPAN SuM High Level Model As depicted in the precedent figure, a user may have one or several User NGN Service Profiles, which are a collection of a service and user related data. A User NGN Service Profile can be either an IMS Service profile or of any other type of Service Profile. Other type of Service Profile can cover Services offered by Applications Servers and Services offered by other TISPAN NGN Subsystems such as IPTV Subsystem. The candidate management entity "User NGN Service Profile" contains the attributes that are common for any type of Service Profiles. For any type of service profile including IMS Service Profile, the associated candidate management entity inherits from the User NGN Service Profile candidate management entity as shown in figure 2. For the IMS Service Profile candidate management entity, the associated attributes are depicted in the figure 2. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 11 IMS Service Profile • Public User Identities • Registration Status • Initial Filter Criteria • Application Server Information • Service Indication • Barring Indication • List of Authorized visited Network Identifier • Services related to unregistered state • Implicitly registered public user identity sets • Shared IFC Set Identifier • Default Public User Identity Indicator • Subscribed Media Profile Identifier • Network handling User NGN Service Profile • NGN Service Profile Identifier • Reference location • Bandwidth capacity per service • Subscribed Quality of Service Other type of Service Profile • Attribute 1 • Attribute 2 • …………… • …………….. Figure 2: User NGN Service Profile Inheritance
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.2 Subscriber
|
The subscriber concept used in the present document is the same as the one defined in [2]. This concept which is defined for both fixed and mobile network accesses is not handled (stored or modified) in the TISPAN NGN network nodes. The subscriber is not in the scope of the present document, and is mentioned for clearness and consistency purposes of the model.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.3 User
|
A user is described by its characteristics/attributes, possibly including various identifiers. A user must be immutable and, therefore, independent of any information that may change during the lifecycle of the user. In particular, it must not depend on any service, any device, network access, credential, etc. A user may be associated with zero or more devices, network accesses, credentials, contracts, etc. In addition, the change of/in devices, network accesses, credentials, contracts, etc. must not lead to a change of identities. A user is defined to be long lasting. Life cycle of a user identity is independent of several aspects: • A user is not strictly bound to a particular contract subscription. • A user is independent from any device. • A user is independent from any network access. A user is identified by a unique user identity described in the table below. Attribute Definition User Identity The User identity is the unique identifier of a user. The user identity is used only to refer to the user. It shall not be used for other purposes (it shall not identify access resources, accounts, credentials…). The user identity shall not be seen by the user. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 12
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.4 Subscription
|
The subscription describes the commercial relationship between the subscriber and the service provider. It identifies a subscriber to one or more services. The subscription is identified by a unique subscription identifier. The Subscription identifier is assigned by the information system and has no semantics with regard to the service execution. The subscription identifier remains unchanged all along the service subscription. Attribute Definition Subscription Identifier The Subscription identifier is assigned by the information system and has no semantics with regard to the service execution. The subscription identifier remains unchanged all along the service subscription.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.5 Subscribed NGN Service
|
The subscribed NGN Service describes a NGN service subscribed by the subscriber. The subscribed NGN Service is identified by a unique NGN Service Identifier which is assigned by the service provider. Attribute Definition NGN Service Identifier The NGN Service Identifier is assigned by the service provider and has no semantics with regard to the service execution.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.6 Subscribed Network Access
|
The subscribed Network Access describes a network access subscribed by the subscriber (e.g. xDSL, WLAN..). The subscribed network access attributes are the following: Attribute Definition Network Access Identifier The Network Access Identifier is assigned by the service provider. Network Access Type Assigned by the Service provider and identifies the type of the network access (xDSL, GPRS, etc.).
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.7 Physical Access
|
The physical access describes a physical access over which a user equipment can attach to the network access. The physical access is identified by a physical access ID which is assigned by the service provider. Attribute Definition Default nass user id This identity corresponds to the default NASS User ID is used to query the UAAF in case no NASS User ID is received from the UAAF. Physical Access ID Assigned by the service provider and identify the physical access to which the user equipment is connected. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 13
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.8 Logical Access
|
The logical access describes the logical access used by the attached user. Attribute Definition Logical Access ID The identity of the logical access used by the attached user equipment. In the xDSL case, the Logical Access ID may explicitly contain the identity of the port, VP and/or VC carrying the traffic. RACS point of Contact The address of the RACS element where the Network Access Profile should be pushed.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.9 Location
|
The location is information related to the location of the default NASS User and may take various forms (e.g. network location, geographical coordinates, post mail address, etc.). Attribute Definition Location Information Information about the location of a user.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.10 Credential
|
A credential is a physical or data element that is used by user to establish a claimed identity. Typical credentials include user names/passwords, SIM cards or smart cards, network access numbers, biometrics, etc. The credential attributes are described in the following table. Attribute Definition Private User Identity Assigned by the service provider and used, for example, for registration, authorization and administration purposes. This identity shall take the form of a Network Access Identifier (NAI). Authentication Schema Used during the registration phase and identify the used authentication method (AKA, HTTP DIGEST, NASS-BUNDLED, or other). Authentication Data Used during registration and consist in: - A quintuplet vector when AKA authentication is used. - A secret when HTTP DIGEST authentication is used. - A Location ID when NASS-BUNDLED authentication is used.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.11 User NGN Network Access Profile
|
The User NGN Network Access Profile is a collection of parameters describing a specific profile of a user for network access. A User NGN Network Access Profile is possibly linked to multiple sub profiles. Attribute Definition NASS User ID Represent the identity of the user attached on the network access. UAAF ID Represent the identity or address of the UAAF or the proxy UAAF that need to be queried in case no NASS User ID is received from the UAAF. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 14
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.12 Sub Profile
|
The Sub Profile contains user authentication data (list of supported authentication methods, key materials etc.) and information related to the required network access configuration. A sub profile is associated to only NASS User ID. The Sub Profile attributes are described in the following table. Attribute Definition Sub Profile ID Identifier of the Sub Profile. Set of Logical Access ID List of the logical access ID associated to the sub profile. Network Access Authentication Data Network access credentials associated to a NASS User. Set of QoS Profile Info A list of QoS profile information. Each QoS profile information consist on the following attributes: - Transport Service Class. - Media Type. - UL Subscribed Bandwidth. - DL Subscribed Bandwidth. - Maximum Priority. - Requestor Name. Initial Gate Settings Consist on the following attributes: - List of Allowed destinations. - UL Subscribed Bandwidth. - DL Subscribed Bandwidth. Privacy Indicator Indicates whether location information can be exported to services and applications. It provides an indication whether applications can access location information, depending on their security level.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.13 User Service Instance
|
A user service instance is a commercial service provided (offer) to a customer by a service provider. It is personalized if it is configured by the user. A service from the products and service catalogue is associated with one or more user services instances.. The service is identified by the attributes detailed in the following table. Attribute Definition NGN Service Identifier The NGN Service Identifier uniquely identifies a service that needs session control on the S-CSCF. For each service executed on a third party AS, there must also be a unique NGN Service Identifier (typical implementation will be to indicate that a user identity has subscribed to the Presence service). Service State The Service State must indicate whether the service is active. Service Options The Service Options are used to indicate specific service options relative to a service. Service Data The Service Data represents the specific data associated with a service.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.14 User NGN Service Profile
|
A User NGN Service Profile is a collection of service and user related data. A User NGN Service Profile is possibly linked to a list of NGN Services depending on the service subscription. This list may change in the following cases: • The associated subscription account has requested new services or resigned services. • The service operator has decided to add new services (e.g. for marketing reasons). • The service operator has decided to restrict some services for any reason. A User NGN Service Profile can contain either an IMS Service Profile or another type of Service Profile. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 15 The User NGN Service Profile is identified by the attributes detailed in the following table. Attribute Definition User NGN Service profile identifier The NGN service profile Identifier is used to identify a service profile independently from a public user identity or other attribute. Reference location The reference location is a set of parameters describing the nominal network access for which the user subscribes to his service. Bandwidth Capacity per service xDSL access: the bandwidth capacity per service characterizes the maximum bandwidth associated with a service subscription or service instance. It is a fraction (or all) of the Subscribed network access bandwidth. Ex: 512 K, 1 024 K. Subscribed quality of service xDSL access: the subscribed quality of service characterizes the quality of service subscribed for a xDSL access.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
4.15 IMS Service Profile
|
An IMS Service Profile is a collection of service and user related data as defined in TS 129 228 [11]. The IMS Service Profile is identified by the attributes detailed in the following table. Attribute Definition Public user identities The Public User Identities are used by any user for requesting communications to other users. For example, this might be included on a business card. It represents one or more Reachability addresses (i.e. tel URI or SIP URI) that can be used by a person in order to reach the user-identity. Initial filter criteria Initial filter criteria provide a simple service logic comprising of user/operator preferences that are of static nature. Initial filter criteria contain information allowing the S-CSCF to determine the need to forward SIP requests to an Application Server. Application server information The Application server information contains individualized information concerning one particular application server entry. It is defined in TS 123 218 [10]. Service Indication The service indication identifies exactly one set of service related transparent data which is stored in an HSS in an operator network. It is defined in TS 129 328 [12]. Barring indication The Barring Indication parameter specified in TS 123 008 [6] indicates that the identity is barred from any IMS communication. A Public User Identity that is barred is allowed to register with the IMS. The Barring Indication applies for both fixed and mobile network. In the case of fixed network, it indicates whether a private user identity is authorized to register in Nomadism cases. List of authorized visited network identifiers The list of authorized visited network identifiers specified in TS 123 008 [6] indicates which visited network identifiers are allowed for nomadism/roaming. Services related to Unregistered State The Services related to Unregistered State specified in TS 123 008 [6] is a parameter indicates whether the identity has services related to unregistered state or not. For a Public Service Identity the parameter shall always be set to value indicating that the identity has services related to unregistered state. Implicitly registered public user identity sets The Implicitly Registered Public User Identity Set specified in TS 123 008 [6] contains one or several instances of Public User Identity of an IMS subscriber. Several Implicitly Registered Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Implicitly Registered Public User Identity Set. Default public user identity indicator The Default Public User Identity indicator marks the Public User Identity to be used as default Public User Identity in each Implicitly Registered Public User Identity Set, and is defined in TS 129 228 [11]. There shall be one Default Public User Identity per Implicitly Registered Public User Identity Set. Registration status Indicates whether the user is registered, non registered, or unregistered. Subscribed media profile identifier The Subscribe Media Profile identifier is read by the S-CSCF to indicate a list of authorized Codecs. Network handling The network handling attribute contains the data related to the handling of SIP messages: - S-CSCF name: identifies the S-CSCF assigned to the user (SIP URL). - Diameter Client address of S-CSCF: Identifies the S-CSCF assigned to the user (Diameter identity). - Diameter Server address of HSS: Identifies the HSS assigned to the user (Diameter identity). - Server capabilities: contains information to assist the I-CSCF in the selection of a S-CSCF for an IMS subscriber. The server capabilities are defined in TS 129 228 [11]. Shared iFC Set Identifier Shared iFC Set Identifier identifies sets of Initial Filter Criteria that may be shared by more than one IMS subscriber or PSI user. The translation from a Shared iFC Set Identifier to the set of initial Filter Criteria is performed in the S-CSCF based on operator configuration. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 16
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5 Information Object Classes
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.1 Imported information entities and local labels
|
This clause identifies a list of information entities (e.g. information object class, information relationship, information attribute) that have been defined in other specifications and that are imported in the present document. Label Reference Local Label 3GPP TS 32.172 [7], Information Object Class, SuMSubscriberProfile SuMSubscriberProfile 3GPP TS 32.172 [7], Information Object Class, SuMService SuMService 3GPP TS 32.172 [7], Information Object Class, SuMSubscribedService SuMSubscribedService 3GPP TS 32.172 [7], Information Object Class, SuMServiceProfile SuMServiceProfile 3GPP TS 32.172 [7], Information Object Class, SuMCredentials SuMCredentials 3GPP TS 32.172 [7], Information Object Class, IMSServiceProfile IMSServiceProfile NOTE: The TISPAN SuM information model extends the 3GPP SuM NRM IS [7]. The imported IOCs are limited to the IOCs that the TISPAN specific definitions extend in terms of inheritance or name- containment. Other 3GPP TS 32.172 Information Object Classes are used in the present document and are not contained within the table since no extensions are done on them within the present document.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.2 Class diagram
|
The TISPAN Subscription Management Information Model is based on the 3GPP SUM NRM IS [7] as described in annex A.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.2.1 Attributes and relationships
|
This clause depicts the set of IOCs that encapsulate information relevant for the present document. This clause provides the overview of all information object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these Information Object Classes (IOCs). CommonServiceProfile <<InformationObjectClass>> SuM ServiceProfile <<InformationObjectClass>> 0.. 1 1 1 <<names>> Figure 3a: SuMService Profile Containment/Naming and Association Diagram 1 UserServiceInstance <<InformationObjectClass>> IMSServiceProfile <<InformationObjectClass>> 0..n 1 1 <<names>> Figure 3b: IMSService Profile Containment/Naming and Association Diagram 2 ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 17 UserServiceInstance <<InformationObjectClass>> ApplicationServiceProfile <<InformationObjectClass>> 0..n 1 <<names>> Figure 3c: ApplicationServiceProfile Containment/Naming and Association Diagram 3 relatedSuMSubscribedService SuMSubscribedServiceGroup <<InformationObjectClass>> SuMSubscriberProfile <<InformationObjectClass>> 0..n 1 1 <<names>> SuMSubscribedService <<InformationObjectClass>> +theSuMSubscribedService 0..n Figure 3d: SUMSubscriberProfile Containment/Naming and Association Diagram 4 NgnIMSServiceProfile <<InformationObjectClass>> +theApplicationSerrviceProfile 0..n ApplicationServiceProfile <<InformationObjectClass>> relatedApplicationServiceProfile Figure 3e: NgnIMSServiceProfile Containment/Naming and Association Diagram 5 ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 18 NgnPhysicalAccess <<InformationObjectClass>> NgnSubscribedNetworkAccess <<InformationObjectClass>> 0..n 1 0..n 1 <<names>> NgnLogicalAccess <<InformationObjectClass>> 0..n 1 0..n 1 <<names>> NgnNetworkAccessSubProfile <<InformationObjectClass>> 0..n +theLogicalAccess 0..n relatedLogicalAccess NgnNetworkAccessProfile <<InformationObjectClass>> 0..n 1 0..n 1 <<names>> Figure 3f: TISPAN SUM IM Containment/Naming and Association Diagram 6
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.2.2 Inheritance
|
Figures 4a, 4b, 4c and 4d represent the inheritance hierarchy of all information object classes defined in the present document. These figures do not need to contain the complete inheritance hierarchy but shall at least contain the parent information object classes of all information object classes defined in the present document. By default, an information object class inherits from the information object class "top". This shall be a UML compliant class diagram. SuMSubscribedService <<InformationObjectClass>> SubscribedApplicationService <<InformationObjectClass>> NgnSubscribedNetworkAccess <<InformationObjectClass>> ApplicationService <<InformationObjectClass>> SuMService <<InformationObjectClass>> NgnNetworkAccess <<InformationObjectClass>> ApplicationServiceProfile <<InformationObjectClass>> SuMServiceProfile <<InformationObjectClass>> NgnNetworkAccessProfile <<InformationObjectClass>> Figure 4a: TISPAN SUM IM Inheritance Hierarchy 1 ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 19 NgnLogicalAccess Top <<InformationObjectClass>> NgnNetworkAccessSubProfile <<InformationObjectClass>> <<InformationObjectClass> > NgnPhysicalAccess <<InformationObjectClass> > UserServiceInstance <<InformationObjectClass>> NgnLogicalAccess CommonServiceProfile <<InformationObjectClass>> SuMSubscribedServiceGroup <<InformationObjectClass> > Figure 4b: TISPAN SUM IM Inheritance Hierarchy 2 IMSServiceProfile <<InformationObjectClass>> NgnIMSServiceProfile <<InformationObjectClass>> Figure 4c: TISPAN SUM IM Inheritance Hierarchy 3 SuMCredentials <<InformationObjectClass>> NgnSuMCredentials <<InformationObjectClass>> Figure 4d: TISPAN SUM IM Inheritance Hierarchy 4
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3 Information object class definitions
|
The definition of all the 3GPP Information object classes used in the present document is defined in [7]. NOTE: The following issues are subject for further study: Lack of a Description or Indication of Supplementary Services associated to an IMS or NGN Service for specific subscriber and subscription. For example: Call Forwarding Service, CRBT, etc. Lack of Description or Indication of Authorized Network Access on which specific services subscribed by a subscriber can be used. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 20
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.1 ApplicationService
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.1.1 Definition
|
This IOC is an abstract class provided for subclassing only. In this management context: a) This class represents a service provided by an application server. b) This class contains the valid parameters that define the Application server service from subscription point of view.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.1.2 Attributes
|
None.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.2 ApplicationServiceProfile
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.2.1 Definition
|
This is an abstract IOC provided for sub-classing only. This class represents all the parameters related to specific service provided in an application server.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.2.2 Attributes
|
None
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.3 CommonServiceProfile
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.3.1 Definition
|
This class represents a collection of common service and user related data.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.3.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier commonServiceProfileId TBD TBD TBD referenceLocation TBD TBD TBD bandwidthPerService TBD TBD TBD subscribedQoS TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.4 NgnNetworkAccess
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.4.1 Definition
|
In this management context: a) This class represents a NGN network access provided by a service provider. b) This class contains the valid parameters that define the NGN network access from subscription point of view.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.4.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier ngnNetworkAccessId TBD TBD TBD ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 21
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.5 NgnSubscribedNetworkAccess
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.5.1 Definition
|
In this management context, this class represents subscription to a NGN network access.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.5.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier ngnSubscribedNetworkAccessId TBD TBD TBD ngnNetworkAccessType TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.6 NgnIMSServiceProfile
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.6.1 Definition
|
In this management context: a) This class represents an IMS Service Profile. b) This class inherits from IMSServiceProfile IOC defined in [7].
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.6.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier listofSharedIFCSetIdentifiers TBD TBD TBD theApplicationServiceProfile TBD TBD TBD NOTE 1: The Current Initial Filter Criteria attribute defined in 3GPP IMSServiceProfile IOC does not fulfil the IMS Service Profile requirements since an IMS Service Profile may contain multiple Initial Filter Criteria. NOTE 2: The Implicit Registration Public Identity Set attribute is not represented in the present document, because currently it is present in neither 3GPP IMSPublicIdentification IOC nor 3GPP IMSServiceProfile IOC. NOTE 3: The Attribute "Services related to unregistered state" which is associated to each IMS Public User Identity is currently present in neither 3GPP IMSPublicIdentification IOC nor 3GPP IMSServiceProfile IOC. NOTE 4: The attributes contained in the IMSServiceProfile IOC and that are related to GAA (3GPP Generic Authentication Architecture) are not IMS Specific.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.7 NgnNetworkAccessProfile
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.7.1 Definition
|
This class represents a collection of network access and user related data. A NgnNetworkAccessProfile is possibly linked to a list of NgnNetworkAccessSubProfile depending on the subscribed NGN Network Access.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.7.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier ngnNetworkAccessProfileId nassUserId TBD TBD TBD uaafId TBD TBD TBD ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 22
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.8 NgnNetworkAccessSubProfile
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.8.1 Definition
|
The IOC contains the parameters related to a ngn network access sub profile which contains user authentication data (list of supported authentication methods, key materials etc.) and information related to the required network access configuration.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.8.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier ngnNetworkAccessSubProfileId TBD TBD TBD theLogicalAccess TBD TBD TBD networkAccessAuthenticationData TBD TBD TBD setofQoSProfileInfo TBD TBD TBD initialGateSettings TBD TBD TBD privacyIndicator TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.9 NgnPhysicalAccess
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.9.1 Definition
|
This class contains parameters identifying one Physical Access associated to a subscribed Ngn Network Access.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.9.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier ngnPhysicalAccessId TBD TBD TBD physicalAccessId TBD TBD TBD defaultNassUserId TBD TBD TBD ngnLocationInformation TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.10 NgnLogicalAccess
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.10.1 Definition
|
This class contains parameters identifying one Logical Access associated to a subscribed Ngn Network Access.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.10.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier ngnLogicalAccessId TBD TBD TBD logicalAccessId TBD TBD TBD racsPointofContact TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.11 NgnSuMCredentials
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.11.1 Definition
|
In this management context: a) This class represents a User's credentials. b) This class contains the valid parameters that define the credentials from subscription point of view. c) This class inherits from the SuMCredentials IOC defined in [7]. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 23
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.11.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier authenticationData TBD TBD TBD authenticationSchema TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.12 SubscribedApplicationService
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.12.1 Definition
|
This IOC is an abstract class provided for subclassing only. In this management context, this class represents subscription to a service provided by an application server or other TISPAN NGN Subsystem such IPTV subsystem.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.12.2 Attributes
|
None.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.13 SuMSubscribedServiceGroup
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.13.1 Definition
|
In this management context: a) This class represents a set of subscribed services by a subscriber. b) A subscriber can have multiple sets of subscribed service groups.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.13.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier suMSubscribedServiceGroupId TBD TBD TBD theSuMSubscribedService TBD TBD TBD
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.14 UserServiceInstance
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.14.1 Definition
|
This class represents all the parameters related to specific service and that can be configured or personalized by the user. One or multiple UserServiceInstance may be contained by one IMSServiceProfile IOC or by one ApplicationServiceProfile IOC.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.3.14.2 Attributes
|
Attribute name Support Qualifier Read Qualifier Write Qualifier userServiceInstanceId TBD TBD TBD serviceState TBD TBD TBD serviceOptions TBD TBD TBD serviceData TBD TBD TBD ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 24
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4 Information relationship definitions
|
Each information relationship is defined using the following structure.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.1 relatedLogicalAccess
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.1.1 Definition
|
This represents the relationship between NgnNetworkAccessSubProfile and NgnLogicalAccess.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.1.2 Roles
|
Name Definition theLogicalAccess Represents the logical access IOCs applicable for the user in this network access sub-profile.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.2 relatedApplicationServiceProfile
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.2.1 Definition
|
This represents the relationship between NgnIMSServiceProfile IOC and ApplicationServiceProfile IOC.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.2.2 Roles
|
Name Definition theApplicationServiceProfile Represents the Application Service Profile IOCs associated that may be associated to an IMS Service Profile.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.3 relatedSuMSubscribedService
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.3.1 Definition
|
This represents the relationship between SubscribedServiceGroup IOC and SuMSubscribedService IOC.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.4.3.2 Roles
|
Name Definition theSuMSubscribedService Represents the SuMSubscribedService IOCs associated to a SuMSubscribedServiceGroup.
|
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.5 Information attribute definitions
| |
9014ba8dbedbe826dd149c7c9bc99edf
|
188 002-2
|
5.5.1 Definition and legal values
|
The following table defines the attributes that are present in several IOCs of the present document. The attributes related to 3GPP IOCs are defined in [7]. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 25 Attribute Name Definition Legal Values (see note) ngnNetworkAccessId Identifier of a network access assigned by the service provider. ngnNetworkAccessType Identifies the type of the network access (xDSL, GPRS, etc.). referenceLocation A set of parameters describing the nominal network access for which the user subscribes to his service. bandwidthPerservice characterizes the maximum bandwidth associated with a service profile. It is a fraction (or all) of the Subscribed network access bandwidth. subscribedQoS Identify the quality of service subscribed for specific access. userServiceInstanceId Identifier of the UserServiceInstance IOC. serviceState Identifies if the service is active or not. serviceOptions Identifies options relative to a specific service. serviceData The Service Data represents the specific data associated with a service. nassUserId Represent the identity of the user attached on the network access. uaafId Identify the UAAF or the proxy UAAF that need to be queried in case no NASS User ID is received from the UAAF. ngnNetworkAccessSubProfileId Identifier of the NgnNetworkAccessSubProfile IOC. networkAccessAuthenticationData Authentication data for network access. setofQoSProfileInfo A list of QoS profile information. initialGateSettings Consist in the list of allowed destinations with their associated uplink and downlink bandwidth. privacyIndicator Indicates whether location information can be exported to services and applications. ngnPhysicalAccessId Identifier of the NgnPhysicalAccess IOC. physicalAccessId Identify the physical access to which the user equipment is connected. defaultNassUserId NASS User ID is used to query the UAAF in case no NASS User ID is received from the UAAF. ngnLocationInformation Information related to the location of the default NASS User and may take various forms (e.g. network location, geographical coordinates, post mail address, etc.). ngnLogicalAccessId Identifier of the NgnLogicalAccess IOC. logicalAccessId Identify the logical access used by the attached user equipment (for example, in xDSL case, the Logical Access ID may explicitly contain the identity of the port, VP and/or VC carrying the traffic. racsPointOfContact Identifier of the RACS element where the Network Access Profile should be pushed. authenticationData Used during registration and consist in A quintuplet vector when AKA authentication is used. A secret when HTTP DIGEST authentication is used. A Location Information when NASS-BUNDLED authentication is used. authenticationSchema Identify the used authentication method used during the user registration phase (for example: AKA, HTTP DIGEST, NASS-BUNDLED, or other). ListofSharedIFCSetIdentifiers List of identifiers of SharedIFCSets. ListofUserServiceInstanceID List of UserServiceInstance IOCs. NOTE: Legal Values will be defined the next release. NOTE 1: The 3GPP IOCs identifiers are based on the name convention described in TS 132 300 [9]. NOTE 2: The TISPAN IOCs identifiers have not yet been defined. This issue is to be discussed with 3GPP SA5. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 26 Annex A (normative): Portion of 3GPP SuM NRM IS utilized in TISPAN SuM IM The following diagrams represent an extract from the 3GPP SUM NRM IS which is relevant for the TISPAN SUM Information Model. ManagedElement (from 32.622) <<InformationObjectClass>> ServiceProviderFunction <<InformationObjectClass>> SuMService <<InformationObjectClass>> SuMSubscribedService <<InformationObjectClass>> 0..1 1 0..1 1 <<names>> 1 0..n 1 0..n <<names>> 1 0..n +offer 1 +contract 0..n agreement SuMServiceProfile <<InformationObjectClass>> 1 0..n +specification 1 +service 0..n description SubscriptionFunction <<InformationObjectClass>> 0..1 1 0..1 1 <<names>> SuMSubscriberProfile <<InformationObjectClass>> 1 0..n 1 0..n <<names>> 0..n 1 0..n 1 <<names>> SuMUser <<InformationObjectClass>> 0..n 1 0..n 1 <<names>> 0..n 1 0..n 1 <<names>> 0..n +theSubscriber 0..n userSubscriberRelation +theUser Figure A.1: 3GPP SuM NRM Containment/Naming and Association diagram1 NOTE 1: The current model in [7] has the SuM IOCs contained by the ManagedElement IOC. This usage of the ManagedElement IOC presents issues in the context of TISPAN SuM related to the fact that this entity has in the definition the following text: "This IOC represents telecommunication equipment or TMN entities within the telecommunications network that performs Managed Element (ME) functions, i.e. provides support and/or service to the subscriber" [8]. The question is if ManagedElement has a too strong correspondence with traditional Network Equipment and its management by Network or Element Management systems to be used for the TISPAN SuM (NOSI) interfaces - for example where applications are being executed in virtualised computing and storage domains. TISPAN SuM needs to address the containment of these SuM information classes in Operations Support Systems including Service Management Systems, Value Added Service Provider and Application Servers. One proposed solution of this issue is described in annex B. NOTE 2: The following issue is for further study within subsequent TISPAN releases. Should the TISPAN SuM model be constrained to use the strong composition relationship with its implied cascade delete semantics, or should it use an alternative such as the more relaxed aggregation relationship? ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 27 SuMUser <<InformationObjectClass>> IMSServiceProfile <<InformationObjectClass>> IMSPublicIdentification <<InformationObjectClass>> 0..n 1 0..n 1 <<names>> SuMCredentials <<InformationObjectClass>> 0..n 1 0..n 1 <<names>> 0..n +theServiceProfile 0..n relatedIMSServiceProfile 0..n +thePublicId 0..n relatedIMSPublicId Figure A.2: 3GPP SuM NRM Containment/Naming and Association diagram 2 ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 28 Annex B (informative): Description of ManagedElement IOC Issue The TISPAN SuM Information Model needs to be used in domains such as Service Management, Application Servers and by Value Added Service Providers. The use in TISPAN SUM of ManagedElement as the root under which all SuM Information Classes is an issue since: • It carries physical semantics which may seem inappropriate for Service Management where integration with the TMF SID Model is important. Specifically the attributes of ManagedElement, such as VendorName and LocationName, further reinforce this physical viewpoint e.g. locationName - The physical location of this entity (e.g. an address). • The containment tree in Application Server need to support industry virtualised computing and Storage models. • A potential realization of a TISPAN SuM IM could be by the use of 3GPP GUP for which containment in a GUP Server function is needed. One possible way of addressing this issue is described below. There may be other alternative solutions as well. This proposal is to replace ManagedElement by an Abstract Class "Management Entity" from which ManagedElement inherits as shown below. Figure B.1: Revised harmonized TISPAN SUM IM/3GPP SUM NRM IS containment model ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 29 The meaning of abstract is that it can not be directly instantiated. It requires sub-classing as one or more concrete classes by either the existing ManagedElement in the 3GPP domains, or by any other suitable containment classes such as ManagedServiceEntity as illustrated above. The advantages of the approach shown above are: • The use of an abstract container class allows extensibility of the containment hierarchy to meet the actual requirements of specific TISPAN NOSI Groups. • TeleManagement Forum (TMF) SID classes and linkage to the TMF eTOM could be more readily incorporated which is expected to be significant for implementation of SuM in Service Management Systems and the liaisons that are being progressed with the TMF. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 30 Annex C (informative): SuM Information Reference Table The following table depicts all the information used within the present document, and its corresponding definition and location in 3GPP and TISPAN specifications. Information Reference (TISPAN and/or 3GPP) NGN Functional entity Location Authentication Data TS 123 008 [6] and ES 282 007 [3] Private User Identity TS 123 008 [6], clause 3.1.1 UPSF Authentication Schema TS 123 008 [6] and ES 282 007 [3] Physical Access ID ES 282 004 [4], clause 5.2.3.1 NACF, PDBF, CLF Logical Access ID ES 282 004 [4], clause 5.2.3.1 NACF, PDBF, CLF RACS Point of Contact ES 282 004 [4] Location Information Network Access Type ES 282 004 [4], clause 5.2.3.1 CLF NASS User ID ES 282 004 [4] UAAF ID ES 282 004 [4] Sub Profile ID ES 282 004 [4] PDBF Initial Gate Settings ES 283 034 [5] PDBF QoS Profile Info ES 283 034 [5] PDBF Privacy Indicator ES 283 034 [5] PDBF Network Access Authentication Data ES 282 004 [4], clause 4.4 NACF, PDBF NGN Service Identifier AS, UPSF optional Service State AS, UPSF optional Service Options Part of ServiceInfo defined in TS 129 228 [11] and TS 129 240 [13] AS, UPSF optional Service Data Part of ServiceInfo defined in TS 129 228 [11] and TS 129 240 [13] AS, UPSF optional NGN Service Profile Identifier Identifier of the NGN Service Profile AS Public User Identity TS 123 008 [6], clause 3.1.2 UPSF, AS Initial Filter Criteria TS 123 008 [6], clause 3.5.2 UPSF Application Server Information TS 123 008 [6], clause 3.5.3 UPSF Service Indication TS 123 008 [6], clause 3.5.4 UPSF, one or more AS Barring Indication TS 123 008 [6], clause 3.1.3 UPSF List of authorized visited network identifiers TS 123 008 [6], clause 3.1.4 UPSF, PDBF, NACF Services related to unregistered state TS 123 008 [6], clause 3.1.5 UPSF Implicitly registered public user identity sets TS 123 008 [6], clause 3.1.6 UPSF Default public user identity indicator TS 123 008 [6], clause 3.1.7 UPSF Reference location CLF, UPSF Registration status TS 123 008 [6], clause 3.2.1 UPSF Subscribed media profile identifier TS 123 008 [6], clause 3.6.1 UPSF Network Handling TS 123 008 [6], clauses 3.2.2, 3.2.3, 3.2.4 and 3.4.1 S-CSCF Name: UPSF; AS Name: UPSF; Diameter client: UPSF; Diameter Server: S-CSCF; Server Capabilities: UPSF Bandwidth capacity per service Subscribed quality of service Shared IFC Set Identitfier TS 123 008 [6], clause 3.5.5 UPSF ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 31 Annex D (informative): Mapping High Level Model to Information Model The following table gives a mapping of the candidate management entities identified in the High Level Model (clause 4) and associated IOCs in the SUM IM. High Level Candidate Management Entity Corresponding IOC in the SUM IM Subscriber SuMSubscriberProfile Subscription SuMSubscribedServiceGroup User SuMUser Subscribed NGN Services For IMS Service: IMSSubscribedService IOC For Application Server Service: SubscribedApplicationService IOC For other services: Inherit from SuMSubscribedService IOC Subscribed Network Access NGNSubscribedNetworkAccess IOC Logical Access NgnLogicalAccess IOC Physical Access NgnPhysicalAccess Location Attribute in the NgnPhysicalAccess IOC User NGN Network Access Profile NgnNetworkAccessProfile Sub Profile NgnNetworkAccessSubProfile User NGN Service Profile For IMS Service Profile: IMSServiceProfile IOC For AS Service Profile: ApplicationServiceProfile IOC For other service profile, Inherit from SuMServiceProfile IOC User Service Instance UserServiceInstance IOC Credentials SuMCredentials IOC IMS Service Profile IMSServiceProfile IOC ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 32 Annex E (informative): NASS Information This annex describes the data that need to be provisionned within the Network Attachment Subsystem (NASS) in order to allow registration of users at access level. E.1 NASS Overview The Network Attachment Subsystem (NASS) provides registration at access level and initialization of User Equipment (UE) for accessing to the TISPAN NGN services. The NASS provides network level identification and authentication, manages the IP address space of the Access Network and authenticates access sessions. The NASS also announces the contact point of the TISPAN NGN Service/Applications Subsystems to the UE. Network attachment through NASS is based on implicit or explicit user identity and authentication credentials stored in the NASS. The Network Attachment Subsystem provides the following functionalities: • Dynamic provision of IP address and other user equipment configuration parameters (e.g. using DHCP). • User authentication, prior or during the IP address allocation procedure. • Authorization of network access, based on user profile. • Access network configuration, based on user profile. • Location management. As depicted in the following figure, the Network Attachment Subsystem (NASS) comprises the following functional entities: • Network Access Configuration Function (NACF). • Access Management Function (AMF). • Connectivity Session Location and Repository Function (CLF). • User Access Authorization Function (UAAF). • Profile Data Base Function (PDBF). • CNG Configuration Function (CNGCF). a4 Service control subsystems and applications TE CNG a3 a1 a2 e1 e2 e4 e3 Resource and Admission Control Subsystem CLF NACF CPECF AMF PDBF UAAF ARF e1 e2 e5 CNGCF UE NASS Figure E.1: NASS Functional Architecture ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 33 E.2 NACF Data The NACF is responsible for the IP address allocation to the UE. It may also distribute other network configuration parameters such as address of DNS server(s), address of signalling proxies for specific protocols (e.g. address of the P-CSCF when accessing to the IMS). The data contained within the NACF are outscope of TISPAN Subscription Management, since they are not user or subscription specific but network configuration specific. E.3 CNCGF Data The CNCGF is used during initialization and update of the CNG. The CNCGF Provides to the CNG with additional configuration information (e.g. configuration of a firewall internally in the CNG, QoS marking of IP packets, etc). This data differs from the network configuration data provided by the NACF. The data contained within the CNCGF are out scope of the current release of TISPAN Subscription Management as stated in TS 188 002-1 [1]. E.4 UAAF/PDBF Data The User Access Authorization Function (UAAF) performs user authentication, as well as authorization checking, based on user profiles, for network access. For each user, the UAAF retrieves authentication data and access authorization information from the user network profile information contained in the PDBF. The Profile Database Function (PDBF) is the functional entity that contains user authentication data (e.g. user identity, list of supported authentication methods, authentication keys…) and information related to the required network access configuration: these data are called "user network profile". This profile may be sub-divided into sub-profiles as shown in figure E.2. Each sub profile is associated to one or more Logical Access ID. Support of the Logical Access ID is optional. NASS User ID Sub-Profile #ID 1 Authentication Data Privacy Indicators QoS Profile Information (*) Initial Gate Settings Sub-Profile #ID n Authentication Data Privacy Indicators QoS Profile Information (*) Initial Gate Settings … (*) Each sub-profile may contain more than one set of QoS Profile Information Figure E.2: PDBF Data ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 34 E.5 CLF Data The Connectivity Session Location and Repository Function (CLF) registers the association between the IP address allocated to the UE and related network location information provided by the NACF, i.e.: Logical Access ID, Physical Access ID, Address Realm, etc. The CLF registers the association between network location information received from the NACF and geographical location information. The CLF may also store the identity of the user/UE to which the IP address has been allocated (information received from the UAAF), as well as the user network QoS profile and user preferences regarding the privacy of location information. In case the CLF does not store the identity/profile of the user/UE, the CLF shall be able to retrieve this information from the UAAF. The CLF holds a number of records representing active sessions. These records contain information received from the NACF and the UAAF, and additional statically configured data. As defined in ES 282 004 [4] (clause 5.2.3.1), the CLF shall be able to carry out the following operations: • Derive the NASS User ID and location information from the physical access ID. • Derive the RACS point of contact and Access Network type from the logical access ID. To allow the CLF to perform the above operations, the CLF shall be provisionned with the information described in the following figure. Physical Access ID • Default NASS User ID • Location Information 1..1 1..1 1..n 1..1 Logical Access ID • RACS Point of Contact • Access Network Type 1..1 1..1 Figure E.3 In addition to the precedent operation, the CLF shall be able to retrieve (request) the user network profile from the UAAF (see ES 282 004 [4], clause 5.3.4.2). To allow the CLF to perform these requests, the CLF shall be provisioned with the information described in the following figure. NASS User ID UAAF ID 1..1 1..n Figure E.4 ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 35 E.6 AMF Data The Access Management Function (AMF) translates network access requests issued by the UE. It forwards the requests for allocation of an IP address and possibly additional network configuration parameters to/from the NACF; AMF forwards requests to the User Access Authorization Function (UAAF) to authenticate the user, authorize or deny the network access, and retrieve user-specific access configuration parameters. The data contained within the AMF is out scope of the TISPA Subscription Management. ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 36 Annex F (informative): SuM Scenarios This annex provides some examples of scenarios supported by SuM. F.1 Scenario 1 A company, or its nominated representative, as subscriber, with several subscriptions (e.g. one for sales dept, one for manufacturing, one for senior management). Each subscription having a set of services and/or network access each with a number of users. The Subscriber can allocate a person, or system, to be a User of one or more Subscriptions. Each user being able to customize services. EXAMPLES: A senior manager, with the same User identifier, can access also the services of the 3 subscriptions. A member of the manufacturing department, who is only allocated to one subscription, can only access the services of that subscription. Note that the Subscription is only way for gathering services into a package (for example: Subscription A = VoIP + VOD, Subscription B = VoIP + IPTV + VOD + Mobile, etc). ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 37 Annex G (informative): Bibliography ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905 (Release 7)". ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 8)". ETSI ETSI TS 188 002-2 V2.0.0 (2008-03) 38 History Document history V2.0.0 March 2008 Publication
|
b6c9efb8f3afc1d10658973a2ac7c420
|
188 002-1
|
1 Scope
|
The purpose of the present document is the definition of the necessary requirements for the Subscription Management (SuM) which is paramount for the NGN service delivery within TISPAN NGN. The present document contains the specification of the requirements for the following: • An end-to-end information model to cover all the mandatory/optional information related to Subscription Management (SuM) that shall be provisioned on the NGN Network. • A Subscription Management (SuM) functional architecture which hides the complexity of the different functional entities to be configured including the CPE and the AS. The present document is the first release of the TISPAN Subscription Management (SuM) requirements. Only Service Configuration and Activation aspects are addressed within this first release. For the current release, configuration and customization of services by users and user's rights management, roles management are out of scope. The requirements described in the present document including the defined information model are done according to the specifications of TISPAN R1. The present document will evolve according to new specifications in TISPAN R2.
|
b6c9efb8f3afc1d10658973a2ac7c420
|
188 002-1
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. [1] Void. [2] ETSI TS 123 008: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Organization of subscriber data (3GPP TS 23.008 version 7.6.0 Release 7)". [3] Void. [4] ETSI TS 132 140: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscription Management (SuM) requirements (3GPP TS 32.140 version 7.0.0 Release 7)". [5] GB921: Enhanced Telecom Operations Map (eTOM), The Business Process Framework, Release 5.0. [6] GB921D: Enhanced Telecom Operations Map (eTOM), The Business Process Framework, Addendum D: Process Decompositions and Descriptions. Release 5.0. [7] ETSI TS 188 001: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); NGN management; OSS Architecture Release 1". [8] Void. ETSI ETSI TS 188 002-1 V2.0.0 (2007-08) 6 [9] Void. [10] ETSI TS 188 006-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Management Information Model (MIM); Part 2: Information service". [11] ETSI TS 129 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents (3GPP TS 29.228 version 7.6.0 Release 7)". [12] ETSI TS 132 172: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) (3GPP TS 32.172 version 7.0.0 Release 7)".
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.