10.2 User authentication and authorization for MCPTT service

23.3793GPPFunctional architecture and information flows to support Mission Critical Push To Talk (MCPTT)Release 18Stage 2TS

NOTE 1: Flow 10.2-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [19] defines the specific user authentication and authorization architecture required by the MCPTT service in order to realize the MCPTT user authentication and authorization requirements as defined in 3GPP TS 22.179 [2].

A procedure for user authentication is illustrated in figure 10.2-1. The user authentication is performed based on the procedure specified in 3GPP TS 23.280[16].

Figure 10.2-1: MCPTT user authentication and registration, single domain

1. The user authentication is performed as per the general user authentication procedure specified in 3GPP TS 23.280[16].

2. MCPTT client performs the MCPTT service authorization for the user. Step 2 utilizes the results of step 1.

NOTE 2: The MCPTT server may reject a request for service authorization by an MCPTT user if the number of simultaneous service authorizations for that MCPTT user would be exceeded.