Content for TS 32.140 Word version: 17.0.0
4 General description
5 SuM assumptions and methods
6 High-level requirements
A Business model
B Example use case
$ Change History
4 General description p. 10
4.1 Subscription Management (SuM) concept p. 10
4.2 Partnership with Enhanced Telecom Operations Map (eTOM) p. 11
4.3 SuM operations viewpoint p. 11
4.4 Management of subscription profiles p. 14
4.4.1 Requirements for subscription profile component management p. 14
4.4.2 Requirements for network and terminal provisioning p. 15
4.4.3 Profile management evolution p. 16
4.5 SuM: relationship to Network Entities and other subsystems p. 17
4.5.1 General p. 17
4.5.2 Void
5 SuM assumptions and methods p. 19
5.1 Business model assumptions p. 19
5.2 Network and control assumptions p. 19
5.3 Use case method p. 19
6 High-level requirements p. 20
6.1 General p. 20
6.2 Feature requirements p. 21
6.3 Security p. 22
A Business model p. 23
A.1 Processes p. 23
A.2 Assumptions concerning actors and roles p. 24
A.3 SuM scope from actor/role model p. 25
A.4 Business model requirements p. 25
B Example use case p. 26
B.1 Create a subscription for a new subscriber p. 27
B.2 Modify subscription for an existing subscriber p. 28
B.3 Delete subscription from an existing subscriber p. 29
B.4 Get subscription details of an existing subscriber p. 30
B.5 Create a subscription profile for a new user p. 30
B.6 Modify a subscription for an existing user p. 31
B.7 Delete a subscription from an existing user p. 32
B.8 Get subscription details of an existing user p. 32
B.9 Add service p. 33
B.10 Modify service p. 34
B.11 Delete service p. 35
B.12 Get service details p. 36
B.13 Create and activate prepaid subscription for a new subscriber p. 37
B.14 Delete prepaid subscription p. 38
$ Change History p. 39
