2 References
24.4843GPPMission Critical Services (MCS) configuration managementProtocol specificationRelease 18TS
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.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] OMA OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification".
[3] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT) over LTE; Stage 1".
[4] 3GPP TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
[5] 3GPP TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
[6] 3GPP TS 24.482: "Mission Critical Services (MCS) identity management Protocol specification".
[7] 3GPP TS 29.283: "Diameter Data Management Applications".
[8] 3GPP TS 23.379: "Functional architecture and information flows to support mission critical push to talk (MCPTT); Stage 2".
[8A] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[9] 3GPP TS 24.379: "Mission Critical Push to Talk (MCPTT) call control Protocol specification".
[10] 3GPP TS 24.380: "Mission Critical Push to Talk (MCPTT) media plane control Protocol specification".
[11] IETF RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[12] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)".
[13] IETF RFC 4745: "Common Policy: A Document Format for Expressing Privacy Preferences".
[14] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".
[15] Void.
[16] 3GPP TS 23.003: "Numbering, addressing and identification".
[17] OMA OMA-TS-XDM_Group-V1_1-20120403-A: "Group XDM Specification".
[18] 3GPP TS 23.303: "Proximity-based Services (ProSe); Stage 2".
[19] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".
[20] IETF RFC 8101 "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service".
[21] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[22] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[23] IETF RFC 6050: "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[24] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2";
[25] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control Protocol specification".
[26] 3GPP TS 24.582: "Mission Critical Data (MCData) media plane control Protocol specification".
[27] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[28] 3GPP TS 24.281: "Mission Critical Video (MCVideo) signalling control Protocol specification".
[29] 3GPP TS 24.581: "Mission Critical Video (MCVideo) media plane control Protocol specification".
[30] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe) Stage 1".
[31] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[32] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[33] IETF RFC 3748: "Extensible Authentication Protocol (EAP)".
[34] 3GPP TS 24.526: "UE policies for 5G System (5GS); Stage 3".