The use of 5GS to support MC services (i.e., MCPTT defined in TS 23.379, MCVideo defined in TS 23.281, MCData defined in TS 23.282) including common application plane and signalling plane entities is specified in the present document. Each MC service supports several types of communications amongst the users (e.g. group communication, peer to peer communication). There are several general functions and entities (e.g. configuration, identity) which are used by the MC services. The general functional architecture to support MC services utilizes aspects of the IMS architecture specified in TS 23.228. An MC service UE in the 5GS context obtains access to a MC service via 3GPP access (i.e., E-UTRA, 5G NR), wireless non-3GPP access (e.g. WLAN or Satellite) and/or wireline access using the 5GS architecture defined in TS 23.501. Certain MC service functions such as dispatch and administrative functions can be supported using MC service UEs with 3GPP access and non-3GPP wireless/wireline access. External applications usage of MC services can be enabled via 3GPP access and/or non-3GPP access.

The present document specifies the use of the 5G System (5GS) considering common functional architecture, procedures and information flows needed to support mission critical services encompassing the common services core architecture. The corresponding service requirements applied in TS 23.280, TS 22.179, TS 22.280, TS 22.281 and TS 22.282 also apply here. The corresponding MC service specific procedures and information flows are defined in TS 23.379, TS 23.281, and TS 23.282. The present document is applicable primarily to mission critical services using 3GPP access (5G NR and/or E-UTRA) and non-3GPP access (WLAN, Satellite and/or wireline) based on the 5GC architecture defined in TS 23.501, TS 23.247 and TS 23.304. The common functional architecture to support mission critical services can be used for public safety applications and for general commercial applications e.g. utility companies and railways.

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

• References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.