Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.379  Word version:  18.7.0

Top   Top   None   None   Next
1…   4…   6…   6.3…   6.3.3…   6.4…   7…   9…   9A…   10…   10.1.2   10.1.3…   10.2…   10.2.3…   11…   11.1.5…   11.2…   11.2.3   12…   13…   15…   A…   F…   G…   I…   J… 
1 Scope  2 References  3 Definitions, symbols and abbreviations  3.1 Definitions  3.2 Abbreviations 
...

 

1  Scope  p. 30

The present document specifies the session control protocols needed to support Mission Critical Push To Talk (MCPTT). The present document specifies both on-network and off-network protocols.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the MCPTT client functionality, and to application servers supporting the MCPTT server functionality.
Up

2  References  p. 30

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 22.179: "Mission Critical Push To Talk (MCPTT) over LTE; Stage 1".
[3]
TS 23.379: "Functional architecture and information flows to support mission critical communication services; Stage 2".
[4]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[5]
TS 24.380: "Mission Critical Push To Talk (MCPTT) floor control Protocol specification".
[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)".
[8]  Void .
[9]
RFC 6050  (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[10]
RFC 3550  (July 2003): "RTP: A Transport Protocol for Real-Time Applications".
[11]  Void.
[12]
RFC 4566  (July 2006): "Session Description Protocol".
[13]
RFC 3605  (October 2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)".
[14]
RFC 3325  (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks".
[15]
RFC 5626  (October 2009): "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)".
[16]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[17]  Void.
[18]
RFC 5373  (November 2008): "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[19]  Void.
[20]
RFC 5366  (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[21]
RFC 2046  (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
[22]
RFC 4488  (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[23]
RFC 4538  (June 2006): "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[24]
RFC 3261  (June 2002): "SIP: Session Initiation Protocol".
[25]
RFC 3515  (April 2003): "The Session Initiation Protocol (SIP) Refer Method".
[26]
RFC 6665  (July 2012): "SIP-Specific Event Notification".
[27]
RFC 7647  (September 2015): "Clarifications for the use of REFER with RFC 6665".
[28]
TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[29]
RFC 4412  (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[30]
RFC 4575  (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".
[31]
TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
[32]
RFC 4483  (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages.
[33]
RFC 3428  (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[34]
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".
[35]
RFC 7614  (August 2015): "Explicit Subscriptions for the REFER Method".
[36]
RFC 5318  (December 2008): "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
[37]
RFC 3903  (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication".
[38]
RFC 5368  (October 2008): "Referring to Multiple Resources in the Session Initiation Protocol (SIP)".
[39]
RFC 5761  (April 2010): "Multiplexing RTP Data and Control Packets on a Single Port".
[40]
TS 23.003: "Numbering, addressing and identification".
[41]
TS 23.203: "Policy and charging control architecture".
[42]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[43]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[44]
RFC 3264  (June 2002): "An Offer/Answer Model with the Session Description Protocol (SDP)".
[45]
TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
[46]  Void.
[47]
RFC 4567  (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[48]
RFC 8101  (March 2017): "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service".
[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)".
[52]
RFC 3863  (August 2004): "Presence Information Data Format (PIDF)".
[53]
RFC 7519  (May 2015): "JSON Web Token (JWT)".
[54]
TS 23.032: "Universal Geographical Area Description (GAD)".
[55]
RFC 4354  (January 2006): "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service".
[56]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[57]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[58]
TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".
[59]
TS 29.199-09: "Open Service Access (OSA); Parlay X Web Services; Part 9: Terminal location".
[60]
W3C: "XML Encryption Syntax and Processing Version 1.1": https://www.w3.org/TR/xmlenc-core1/.
[61]
W3C: "XML Signature Syntax and Processing (Second Edition)": http://www.w3.org/TR/xmldsig-core/.
[62]
RFC 2392  (August 1998): "Content-ID and Message-ID Uniform Resource Locators".
[63]
RFC 4661  (September 2006): "An Extensible Markup Language (XML)-Based Format for Event Notification Filtering".
[64]
RFC 6086  (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[65]
RFC 3891  (September 2004): "The Session Initiation Protocol (SIP) Replaces Header".
[66]
TS 24.216: "Communication continuity managed object".
[67]
RFC 4122  (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[68]
RFC 2045  (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[69]
TS 26.179: "Mission Critical Push To Talk (MCPTT) Codecs and media handling".
[70]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[71]
RFC 4648  (October 2006): "The Base16, Base32, and Base64 Data Encodings".
[72]
RFC 5627  (October 2009): "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)".
[73]
TS 29.283: "Diameter Data Management Applications".
[74]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[75]
RFC 6509  (February 2012): "MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY)".
[76]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[77]
RFC 7462  (March 2015): "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)".
[78]
TS 33.180: "Security of the mission critical service".
[79]
TS 29.214: "Policy and Charging Control over Rx reference point".
[80]
RFC 5795  (March 2010): "The Robust Header Compression (ROHC) Framework".
[81]
RFC 3095  (July 2001): "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".
[82]
TS 23.280: "Technical Specification Group Services and System Aspects; Common functional architecture to support mission critical services; Stage 2".
[83]
RFC 5288  (August 2008): "AES Galois Counter Mode (GCM) Cipher Suites for TLS".
[84]
TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification".
[85]
TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification".
[86]
RFC 5576  (June 2009): "Source-Specific Media Attributes in the Session Description Protocol (SDP)".
[87]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[88]
TS 29.379: "Mission Critical Push To Talk (MCPTT) call control interworking with Land Mobile Radio (LMR) systems; Stage-3".
[89]
RFC 8445  (July 2018): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal".
[90]
RFC 8839  (January 2021): "Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)".
[91]
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[92]
TS 23.289: "Mission Critical services over 5G System; Stage 2".
[93]
RFC 6809  (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[94]
TS 24.554: " Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3".
[95]
TS 23.501: "System architecture for the 5G System (5GS)".
[96]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[97]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
Up

3  Definitions, symbols and abbreviations  p. 34

3.1  Definitions  p. 34

For the purposes of the present document, the terms and definitions 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.
An MCPTT user is affiliated to an MCPTT group:
The MCPTT user has expressed interest in an MCPTT group it is a member of, and both the MCPTT server serving the MCPTT user and the MCPTT server owning the MCPTT group have authorized the MCPTT user's interest in the MCPTT group communication.
An MCPTT user is affiliated to an MCPTT group at an MCPTT client:
The MCPTT user is affiliated to the MCPTT group, the MCPTT client has a registered IP address for an IMPU related to the MCPTT ID, and the MCPTT server serving the MCPTT user has authorised the MCPTT user's interest in the MCPTT group at the MCPTT client.
Affiliation status:
Applies for an MCPTT user to an MCPTT group and has one of the following states:
  1. the "not-affiliated" state indicating that the MCPTT user is not interested in the MCPTT group and the MCPTT user is not affiliated to the MCPTT group;
  2. the "affiliating" state indicating that the MCPTT user is interested in the MCPTT group but the MCPTT user is not affiliated to the MCPTT group yet;
  3. the "affiliated" state indicating that the MCPTT user is affiliated to the MCPTT group and there was no indication that MCPTT user is no longer interested in the MCPTT group; and
  4. the "deaffiliating" state indicating that the MCPTT user is no longer interested in the MCPTT group but the MCPTT user is still affiliated to the MCPTT group.
Ambient listening call:
a call type allowing an authorized MCPTT user to cause an MCPTT client to initiate a communication which results in no indication on the MCPTT UE that it is transmitting. Ambient listening can be initiated by an authorized MCPTT user who wants to be listened to by another authorized MCPTT user or can be initiated by an authorized MCPTT user who wants to listen to another MCPTT user.
Ambient listening client role:
the role of an MCPTT client in an ambient listening call, which can be that of:
  1. the "listening MCPTT user"; or
  2. the "listened-to MCPTT user".
Ambient listening type:
the type of an ambient listening call from the perspective of the relationship of the initiator of the call to the user being listened to. The two types of ambient listening call are:
  1. "remote-init", indicating that the listening MCPTT user initiated the call; and
  2. "local-init", indicating that the listened-to MCPTT user initiated the call.
First-to-answer call:
A call initiated by one user towards a list of other users with the intention to establish an MCPTT private call or MCPTT emergency private call, with one of the users in the list of users.
Group document:
when the group is not a regroup based on a preconfigured regroup, the term "group document" used within the present document refers to the group document for that group within the GMS as specified in TS 24.481; when the group is a regroup based on a preconfigured group, the term "group document" used within the present document refers to the group document for the preconfigured group as specified in TS 24.481 restricted to the users or groups included in the regroup stored by the MCPTT server at the time of the regroup creation, see clause 16.
Group identity:
An MCPTT group identity or a temporary MCPTT group identity.
In-progress emergency private call state:
the state of two participants when an MCPTT emergency private call is in progress.
In-progress imminent peril group state:
the state of a group when an MCPTT imminent peril group call is in progress.
Listening MCPTT user:
the MCPTT user in an ambient listening call receiving the media transmission from the listened-to MCPTT user;
Listened-to MCPTT user:
the MCPTT user in an ambient listening call who is being listened to, may or may not be aware of being listened to depending on ambient listening type of the call.
MCPTT client ID:
is a globally unique identification of a specific MCPTT client instance. MCPTT client ID is a UUID URN as specified in RFC 4122.
MCPTT emergency alert state:
MCPTT client internal perspective of the state of an MCPTT emergency alert.
MCPTT emergency group state:
MCPTT client internal perspective of the in-progress emergency state of an MCPTT group maintained by the controlling MCPTT function.
MCPTT emergency group call state:
MCPTT client internal perspective of the state of an MCPTT emergency group call.
MCPTT emergency private call:
MCPTT emergency call between two MCPTT users that is initiated as a private call or a first-to-answer call with emergency indication, or without emergency indication when the MCPTT emergency state is already set,
MCPTT emergency private call state:
MCPTT client internal perspective of the state of an MCPTT emergency private call.
MCPTT emergency private priority state:
MCPTT client internal perspective of the in-progress emergency private call state of the two participants of an MCPTT emergency private call maintained by the controlling MCPTT function.
MCPTT imminent peril group call state:
MCPTT client internal perspective of the state of an MCPTT imminent peril group call.
MCPTT imminent peril group state:
MCPTT client internal perspective of the state of an MCPTT imminent peril group.
MCPTT private call:
MCPTT call between two MCPTT users that is initiated as a private call or a first-to-answer call.
MCPTT private emergency alert state:
MCPTT client internal perspective of the state of an MCPTT private emergency alert targeted to an MCPTT user.
MCPTT speech:
Conversational audio media used in mission critical push to talk systems as defined by TS 22.179 and TS 23.379.
Media-floor control entity:
A media control resource shared by participants in an MCPTT session, controlled by a state machine to ensure that only one participant can access the media resource at the same time.
Private call:
A call initiated by one user towards one other user with the intention to establish an MCPTT private call or MCPTT emergency private call.
N2:
The maximum number of simultaneous affiliations to MCPTT groups that the MCPTT user may have. The value of N2 is specified in the <MaxAffiliationsN2> element of the <Common> element of the MCPTT user profile and corresponds to the parameter Nc2 specified in TS 22.280.
Private Call Call-Back:
A mechanism for a requesting MCPTT client to request a targeted MCPTT client to initiate an MCPTT private call with the requesting MCPTT client (at earliest convenience).
Remote change of an MCPTT user's selected group:
A mechanism allowing an authorised user to remotely change the selected group of another MCPTT user.
Temporary MCPTT group identity:
A group identity representing a temporary grouping of MCPTT group identities formed by the group regrouping operation as specified in TS 24.481.
Trusted mutual aid:
A business relationship whereby the Partner MCPTT system is willing to share the details of the members of an MCPTT group that it owns with the Primary MCPTT system.
Untrusted mutual aid:
A business relationship whereby the Partner MCPTT system is not willing to share the details of the members of an MCPTT group that it owns with the Primary MCPTT system.
User Requested Application Priority:
The requested priority as defined in TS 23.280. How the server determines the priority for the requested communication based on requested priority and in combination with other factors is up to MCPTT server implementation.
Functional alias status:
Applies for the status of a functional alias for an MCTT user and has one of the following states:
  1. the "not-activated" state indicating that the MCPTT user has not activated the functional alias;
  2. the "activating" state indicating that the MCPTT user is interested in using the functional alias but the functional alias is not yet activated for the MCPTT user;
  3. the "activated" state indicating that the MCPTT user has activated the functional alias;
  4. the "deactivating" state indicating that the MCPTT user is no longer interested in using the functional alias but the functional alias is still activated for the MCPTT user; and
  5. the "take-over-possible" state indicating that the MCPTT user interested in the functional alias is allowed to take-over the functional alias although the functional alias is already activated and used by another MCPTT user.
For the purposes of the present document, the following terms and definitions given in TS 22.179 apply:
In-progress emergency
MCPTT emergency alert
MCPTT emergency group call
MCPTT emergency state
Partner MCPTT system
Primary MCPTT system
For the purpose of the present document, the following terms and definitions given in TS 24.380 apply:
MBMS subchannel
For the purpose of the present document, the following terms and definitions given in TS 23.379 apply:
Pre-selected MCPTT user profile
Selected MCPTT user profile
For the purpose of the present document, the following terms and definitions given in TS 33.180 apply:
Client Server Key (CSK)
Multicast Floor Control Key (MKFC)
Multicast Signalling Key (MuSiK)
Multicast Signalling Key Identifier (MuSiK-ID)
MBMS subchannel control key (MSCCK)
MBMS subchannel control key identifier (MSCCK-ID)
Private Call Key (PCK)
Signalling Protection Key (SPK)
XML Protection Key (XPK)
For the purpose of the present document, the following terms and definitions given in TS 22.280 apply:
Functional alias
For the purposes of the present document, the following terms related to a MCPTT gateway UE function apply
MCPTT gateway UE:
A functional entity that enables simultaneous access to the MCPTT system for multiple MCPTT clients.
MCPTT gateway client:
A client that enables the authorized binding with one or more MCPTT GW UEs in order to be able to handle MCPTT services.
MCPTT gateway UE server:
A server on an MCTT gateway UE that controls authorized binding with multiple MCPTT gateway clients.
MCPTT gateway UE function:
Functional block as part of the MCPTT server that authorises and manages the association between MCPTT client and MCPTT gateway UE.
Up

3.2  Abbreviations  p. 37

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.
CID
Context ID
CSK
Client-Server Key
ECGI
E-UTRAN Cell Global Identification
IPEG
In-Progress Emergency Group
IPEPC
In-Progress Emergency Private Call
IPIG
In-Progress Imminent peril Group
MBMS
Multimedia Broadcast and Multicast Service
MBS
Multicast/Broadcast Service
MBSFN
Multimedia Broadcast multicast service Single Frequency Network
MCPTT
Mission Critical Push To Talk
MCPTT group ID
MCPTT group Identity
MC
Mission Critical
MCS
Mission Critical Service
MEA
MCPTT Emergency Alert
MEG
MCPTT Emergency Group
MEGC
MCPTT Emergency Group Call
MEPC
MCPTT Emergency Private Call
MEPP
MCPTT Emergency Private Priority
MES
MCPTT Emergency State
MIME
Multipurpose Internet Mail Extensions
MIG
MCPTT Imminent peril Group
MIGC
MCPTT Imminent peril Group Call
MONP
MCPTT Off-Network Protocol
MPEA
MCPTT Private Emergency Alert
NAT
Network Address Translation
PCC
Policy and Charging Control
PCCB
Private Call Call-Back
PLMN
Public Land Mobile Network
PPPP
ProSe Per-Packet Priority
PQI
PC5 5QI
QCI
QoS Class Identifier
ROHC
Robust Header Compression
RTP
Real-time Transport Protocol
SAI
Service Area Identifier
SDP
Session Description Protocol
SIP
Session Initiation Protocol
SPK
Signalling Protection Key
SSRC
Synchronization SouRCe
TGI
Temporary MCPTT Group Identity
TMGI
Temporary Mobile Group Identity
UE
User Equipment
URI
Uniform Resource Identifier
XPK
XML Protection Key
Up

Up   Top   ToC