6 High-level requirements

32.1403GPPRelease 17Subscription Management (SuM) requirementsTelecommunication managementTS

6.1 General

Figure 5: SuM Entities – Relations

Figure 7 shows the relationships between users, subscribers, subscriptions and services.

According to the way in which Operators do business:

– Each Operator has many subscribers;

– Each subscriber can have several users; and

– Users can request a service. The request will be granted if for the user, a contract for the requested service has been signed between the service provider and a subscriber.

6.1.1 Pre-requisites for service

These assertions address some of the operator’s concerns, prior to granting a service request to a user:

1. find a subscriber entity that can match with the user;

2. identify and verify the subscriber’s subscription profile; and

3. ensure the request for service is consistent with the subscription profile.

6.2 Feature requirements

SuM shall provide:

1. The management of the subscription profile information in the home PLMN.

2. It shall be possible to replicate and distribute the subscription profile components.

– Support for subscription profile information across administrative, network and systems domains (e.g. VLR in visited networks).

3. The control and modification of subscription profile information consistent with the customer care needs including self help, self diagnosis and fault diagnosis.

– SuM shall provide a process to support subscribers wishing to check their Subscription Configuration (e.g. support self care).

6.2.1 Requirements on HSS/HLR

The master database where subscription profile components are stored is in the HSS/HLR, which is used by the network for distribution and replication of this data in other subsystems such as the PS, CS and IM domains, CAMEL, etc.

1. SuM shall allow for the creating, reading, updating and deleting of subscription profile data in the HSS/HLR.

2. SuM shall support the data described in 3GPP TS 23.008 [7].

6.2.1.1 PS domain

1. SuM shall manage subscription profile components within the HSS for the PS Domain.

6.2.1.2 CS domain

1. SuM shall manage subscription profile components within the HSS for the CS Domain.

6.2.1.3 IM CN Sub-system (IMS)

1. SuM shall manage subscription profile components within the HSS for the IMS defined in reference 3GPP TS 23.228 [8].

6.2.1.4 Authentication Center (AuC)

1. SuM shall be able to manage subscription profile components in the HSS for the Authentication Center.

6.2.1.5 Equipment Identity Register (EIR)

1. SuM shall be able to manage relevant subscription profile components in the HSS for the EIR

2. SuM shall support Subscription Data defined in reference 3GPP TS 22.041 [13], 3GPP TS 23.015 [14].

6.3 Security

1. Specific local, national, and regional security regulations shall be complied with.

2. SuM data shall be safeguarded against unapproved disclosure or usage.

3. SuM data shall be provided in a secure and reliable manner that ensures the information is neither lost nor corrupted.

4. Access to SuM data shall only be permitted in an authorised and secure manner

5. Secure mechanisms shall be available for the transfer of SuM data to, from or between authorised entities.
The secure mechanisms to be applied shall be appropriate to the level of confidentiality of the data, the endpoints of the transfer and the routes that are available for the transfer of the data.

6. Audit records should be maintained for all SuM transactions to facilitate resolution of security violations.

Annex A (informative):
Business model