Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.582  Word version:  17.5.0

Top   Top   None   None   Next
0…   4…   8…   14…

 

0  Introductionp. 8

The present document has been produced as an aspect of work to realise the stage 3 protocols to implement the stage 2 functionality for Interworking between Mission Critical systems and Land Mobile Radio systems as described in TS 23.283. Early stage 3 study work is documented in TR 24.883 which covers both MCPTT and MCData interworking.
The document structure describes functionality modelled on TS 24.282 because the behaviour of an Interworking Function (IWF) for LMR MCData interworking is modelled on that of an MCData server, and the clause numbering is also based on that used in on TS 24.282 in order to aid comparison between the two specifications and identification of any behavioural changes.
The reference numbering is based on that used in TR 24.883 and so may not be sequential.
Up

1  Scopep. 9

The present document specifies the protocols needed to support a Mission Critical Data (MCData) system interworking with a Land Mobile Radio (LMR) system based on the IWF-2 interface between an MCData server and an Interworking Function (IWF) as described in TS 23.283.

2  Referencesp. 9

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".
[4]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[5]
TS 23.379: "Functional architecture and information flows to support mission critical communication services; Stage 2".
[6]
RFC 3841  (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[7]
RFC 4028  (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[9]
RFC 6050  (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[16]
RFC 3711:  "The Secure Real-time Protocol (SRTP)".
[19]
RFC 6135  (February 2011): "An Alternative Connection Model for the Message Session Relay Protocol (MSRP) ".
[20]
RFC 5366  (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[24]
RFC 3261  (June 2002): "SIP: Session Initiation Protocol".
[26]
RFC 6665  (July 2012): "SIP-Specific Event Notification".
[31]
TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
[33]
RFC 3428  (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[37]
RFC 3903  (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication".
[45]
TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
[46]
RFC 3986:  "Uniform Resource Identifier (URI): Generic Syntax".
[47]
RFC 4567  (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[49]
TS 24.482: "Mission Critical Services (MCS) identity management Protocol specification.
[50]
TS 24.484: "Mission Critical Services (MCS) configuration management Protocol specification".
[51]
RFC 3856  (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[67]
RFC 4122  (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[78]
TS 33.180: "Security of the mission critical service".
[80]
TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
[81]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; protocol specification;".
[82]
TS 24.282: " Mission Critical Data (MCData) signalling control; Protocol specification;"
[85]
TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification".
[86]
RFC 1738  (December 1994): "Uniform Resource Locators (URL)".
[87]
TS 29.379: "Mission Critical Push To Talk (MCPTT) call control interworking with LMR systems; Protocol specification".
[89]
RFC 4826  (May 2007): "Extensible Markup Language (XML) Formats for Representing Resource Lists".
[90]
TR 24.883: "Mission Critical Systems Connection to LMR".
[91]
RFC 4975  (September 2007): "The Message Session Relay Protocol (MSRP)".
[92]
RFC 6714  (August 2012): "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)".
[93]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
Up

3  Definitions of terms, symbols and abbreviationsp. 10

3.1  Termsp. 10

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.
For the purposes of the present document, the following terms and definitions given in TS 23.379 apply:
Group call
MCPTT call
Mission critical push to talk
Private call
SIP core
For the purposes of the present document, the following terms and definitions given in TS 23.283 apply:
Interworking Function (IWF)
For the purposes of the present document, the following terms and definitions given in TS 29.379 apply:
IWF performing the controlling role
IWF performing the non-controlling
IWF performing the participating role
For the purposes of the present document, the following terms and definitions given in TS 33.180 apply:
Group Master Key (GMK)
Group Master Key Identifier (GMK-ID)
Private Call Key (PCK)
Private Call Key Identifier (PCK-ID)
Signalling Protection Key (SPK)
Signalling Protection Key Identifier (SPK-ID)
For the purposes of the present document, the following terms and definitions given in IETF RFC 3711 [16] apply:
SRTP master key (SRTP-MK)
SRTP master key identifier (SRTP-MKI)
SRTP master salt (SRTP-MS)
Up

3.2  Abbreviationsp. 11

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.
GMK
Group Management Key
GMK-ID
Group Master Key Identifier
GMS
Group Management Server
GUK-ID
Group User Key Identifier
IP
Internet Protocol
MCData
Mission Critical Data
PCK
Private Call Key
PCK-ID
Private Call Key Identifier
RFC
Request For Comment
RTCP
RTP Control Protocol
RTP
Real-time Transport Protocol
SPK
Signalling Protection Key
SPK-ID
Signalling Protection Key Identifier
SRTCP
Secure RTCP
SRTP
Secure RTP
SRTP-MK
SRTP master key
SRTP-MKI
SRTP master key identifier
SRTP-MS
SRTP master salt
SSRC
Synchronization SouRCe
UE
User Equipment
Up

Up   Top   ToC