Content for TR 22.818 Word version: 14.0.0
4 Use cases
4.1 Third Party Server Reports Congestion or Failure
4.2 Third Party Server Fails
4.3 Combating a DDOS Attack from a Virus
4.4 Using Phased CATS to Gracefully Restore Service
4.5 Coexistence of ACDC and CATS
4.6 Activation and Control of CATS Using 3GPP Network Subscription Profiles
4.7 Activation and Control of CATS Using Third Party Service Subscription Profiles
4.8 Activation and Control of CATS when a Third Party Server Supports Multiple Applications
4.9 Relationship to Access Class 11-15
4.10 Charging between CATS activation and deactivation
5 Considerations
6 Potential requirements
7 Conclusions and Recommendations
A CATS Conceptual Approaches
B Mapping of potential requirements.
$ Change history
4 Use cases p. 7
4.1 Third Party Server Reports Congestion or Failure p. 7
4.1.1 Description p. 7
4.1.2 Pre-conditions p. 7
4.1.3 Service Flows p. 7
4.1.4 Post-conditions p. 8
4.1.5 Potential Requirements p. 8
4.2 Third Party Server Fails p. 8
4.2.1 Description p. 8
4.2.2 Pre-conditions p. 8
4.2.3 Service Flows p. 8
4.2.4 Post-conditions p. 9
4.2.5 Potential Requirements p. 9
4.3 Combating a DDOS Attack from a Virus p. 9
4.3.1 Description p. 9
4.3.2 Pre-conditions p. 9
4.3.3 Service Flows p. 9
4.3.4 Post-conditions p. 9
4.3.5 Potential Requirements p. 10
4.4 Using Phased CATS to Gracefully Restore Service p. 10
4.4.1 Description p. 10
4.4.2 Pre-conditions p. 10
4.4.3 Service Flows p. 10
4.4.4 Post-conditions p. 10
4.4.5 Potential Requirements p. 10
4.5 Coexistence of ACDC and CATS p. 11
4.5.1 Description p. 11
4.5.2 Pre-conditions p. 11
4.5.3 Service Flows p. 11
4.5.4 Post-conditions p. 11
4.5.5 Potential Requirements p. 12
4.6 Activation and Control of CATS Using 3GPP Network Subscription Profiles p. 12
4.6.1 Description p. 12
4.6.2 Pre-conditions p. 12
4.6.3 Service Flows p. 12
4.6.4 Post-conditions p. 13
4.6.5 Potential Requirements p. 13
4.7 Activation and Control of CATS Using Third Party Service Subscription Profiles p. 13
4.7.1 Description p. 13
4.7.2 Pre-conditions p. 14
4.7.3 Service Flows p. 14
4.7.4 Post-conditions p. 14
4.7.5 Potential Requirements p. 15
4.8 Activation and Control of CATS when a Third Party Server Supports Multiple Applications p. 15
4.8.1 Description p. 15
4.8.2 Pre-conditions p. 15
4.8.3 Service Flows p. 15
4.8.4 Post-conditions p. 16
4.8.5 Potential Requirements p. 16
4.9 Relationship to Access Class 11-15 p. 17
4.9.1 Description p. 17
4.9.2 Pre-conditions p. 17
4.9.3 Service Flows p. 17
4.9.4 Post-conditions p. 17
4.9.5 Potential Requirements p. 17
4.10 Charging between CATS activation and deactivation p. 17
4.10.1 Description p. 17
4.10.2 Pre-conditions p. 17
4.10.3 Service Flows p. 18
4.10.4 Post-conditions p. 18
4.10.5 Potential Requirements p. 18
5 Considerations p. 18
5.1 Considerations on security p. 18
5.2 Considerations on charging p. 18
5.3 Considerations on Network Sharing p. 18
5.4 Considerations on relationship between CATS and existing Access Controls p. 19
6 Potential requirements p. 19
7 Conclusions and Recommendations p. 20
A CATS Conceptual Approaches p. 21
A.1 Introduction p. 21
A.2 CATS Policy Enforcement Options p. 21
A.3 Network-Centred CATS Concept p. 21
A.4 UE-Centred CATS Concept p. 22
A.4.1 Concept Description p. 22
A.4.2 Policy Fetch Options p. 23
A.5 Discussion and Comparison p. 24
B Mapping of potential requirements. p. 25
$ Change history p. 25
