Tech-invite3GPP-SpecsFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

full Table of Contents for  TS 24.229  Word version:   16.3.0

 

Top   Up   Prev   Next
1…   4.5…   5…   5.1.2…   5.2…   5.2.7…   5.4…   5.5…   5.7…   5.8…   5.11…   6…   7…   7.2A…   7.3…   7.9A…   8…   A…   B…   C…   E…   F…   H…   I…   K…   L…   M…   N…   O…   Q…   R…   S…   T…   U…   V…   W…

 

 

5.4  Procedures at the S-CSCF
5.4.0  General [R8]
5.4.1  Registration and authenticationWord-p. 227
5.4.1.1  Introduction
5.4.1.2  Initial registration and user-initiated reregistrationWord-p. 229
5.4.1.2.1  Unprotected REGISTER
5.4.1.2.1A  Challenge with IMS AKA as security mechanism [R8]Word-p. 231
5.4.1.2.1B  Challenge with SIP digest as security mechanism [R8]
5.4.1.2.1C  Challenge with SIP digest with TLS as security mechanism [R8]Word-p. 232
5.4.1.2.1D  Initial registration and user-initiated reregistration for NASS-IMS bundled authentication [R8]Up
5.4.1.2.1E  Initial registration and user-initiated reregistration for GPRS-IMS-Bundled authentication [R8]Word-p. 233
5.4.1.2.2  Protected REGISTER with IMS AKA as a security mechanismWord-p. 235
5.4.1.2.2A  Protected REGISTER with SIP digest as a security mechanism [R8]Word-p. 238
5.4.1.2.2B  Protected REGISTER with SIP digest with TLS as a security mechanism [R8]Word-p. 241
5.4.1.2.2C  NASS-IMS bundled authentication as a security mechanism [R8]
5.4.1.2.2D  GPRS-IMS-Bundled authentication as a security mechanism [R8]
5.4.1.2.2E  Protected REGISTER - Authentication already performed [R8]Word-p. 242
5.4.1.2.2F  Successful registration [R8]Word-p. 243
5.4.1.2.3  Abnormal cases - generalWord-p. 245
5.4.1.2.3A  Abnormal cases - IMS AKA as security mechanism [R8]Word-p. 246
5.4.1.2.3B  Abnormal cases - SIP digest as security mechanism [R8]Word-p. 247
5.4.1.2.3C  Abnormal cases - SIP digest with TLS as security mechanism [R8]Word-p. 248
5.4.1.2.3D  Abnormal cases - NASS-IMS bundled authentication as security mechanism [R8]
5.4.1.2.3E  Abnormal cases - GPRS-IMS-Bundled authentication as security mechanism [R8]
5.4.1.3  Authentication and reauthentication
5.4.1.4  User-initiated deregistration
5.4.1.5  Network-initiated deregistration
5.4.1.6  Network-initiated reauthenticationWord-p. 252
5.4.1.7  Notification of Application Servers about registration statusWord-p. 253
5.4.1.7A  Including contents in the body of the third-party REGISTER request [R8]Word-p. 255
5.4.1.8  Service profile updates [R7]
5.4.2  Subscription and notificationWord-p. 256
5.4.3  General treatment for all dialogs and standalone transactions excluding requests terminated by the S-CSCFWord-p. 263
5.4.4  Call initiation
5.4.5  Call releaseWord-p. 290
5.4.6  Call-related requestsWord-p. 293
5.4.7Void
5.4.7A  GRUU management [R7]
5.4.8  Emergency service [R7]Word-p. 296

Up   Top   ToC