Content for TS 29.379 Word version: 17.5.0
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Abbreviations
...
...
1 Scope p. 11
The present document specifies the call control protocols needed to support a Mission Critical Push To Talk (MCPTT) system interworking with a Land Mobile Radio (LMR) system.
The IWF supports the basic group and other features as specified in TS 23.283. The present document describes functionality modelled on TS 24.379.
2 References p. 11
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.379: "Functional architecture and information flows to support mission critical communication services; Stage 2".
[3]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[4]
TS 24.380: "Mission Critical Push To Talk (MCPTT) floor control Protocol specification".
[5]
RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[6]
RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[7]
RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[8]
RFC 4566 (July 2006): "Session Description Protocol".
[9]
RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[10]
RFC 5373 (November 2008): "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[11]
RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[12]
RFC 4488 (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[13]
RFC 4538 (June 2006): "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[14]
RFC 3261 (June 2002): "SIP: Session Initiation Protocol".
[15]
RFC 4575 (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".
[16]
TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
[17]
RFC 4483 (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".
[18]
RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[19]
RFC 4964 (October 2007): "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push-to-talk over Cellular".
[20]
RFC 5318 (December 2008): "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
[21]
RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication".
[22]
RFC 4567 (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[23]
RFC 8101 "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service".
[24]
RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[25]
RFC 6665 (July 2012): "SIP-Specific Event Notification".
[26]
RFC 6086 (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[27]
TS 33.180: "Security of the mission critical service".
[28]
TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
[29]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
[30]
TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification".
[31]
TS 29.380: "Mission Critical Push To Talk (MCPTT) media plane control interworking with LMR systems".
[32]
RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[33]
TS 29.582: "Mission Critical Data (MCData) interworking with LMR systems".
[34]
TS 24.484: "Mission Critical Services (MCS) configuration management Protocol specification".
3 Definitions of terms, symbols and abbreviations p. 12
3.1 Terms p. 12
For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
IWF performing the controlling role:
an IWF role in which the IWF interacts with MCPTT participating functions and MCPTT non-controlling functions across the IWF-1 interface.
IWF performing the non-controlling role:
an IWF role in which the IWF interacts with MCPTT participating functions and MCPTT controlling functions across the IWF-1 interface
IWF performing the participating role:
an IWF role in which the IWF interacts with MCPTT controlling functions and MCPTT non-controlling functions across the IWF-1 interface.
Participant homed in the IWF:
same as "User homed in the IWF".
User homed in the IWF:
A user represented by an MCPTT ID in the IWF with the same domain as the IWF.
For the purposes of the present document, the following terms and definitions given in TS 23.283 apply:
Interworking Function (IWF)
3.2 Abbreviations p. 13
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
IWF
InterWorking Function
KMS
Key Management Service
LMR
Land Mobile Radio
MC
Mission Critical
MCPTT
Mission Critical Push To Talk
URI
Uniform Resource Identifier
