Content for TS 24.281 Word version: 18.1.0
1 Scope
2 References
3 Definitions, symbols and abbreviations
3.1 Definitions
3.2 Symbols
3.3 Abbreviations
...
...
1 Scope p. 24
The present document specifies the signalling control needed to support Mission Critical Video (MCVideo) service.
The MCVideo service and its associated media plane control protocols 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 MCVideo client, and MCVideo server.
2 References p. 24
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]
RFC 4566 (July 2006): "Session Description Protocol".
[3]
RFC 3605 (October 2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)".
[4]
TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
[5]
TS 24.581: "Mission Critical Video (MCVideo) media plane control Protocol specification".
[6]
RFC 4567 (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[7]
RFC 3264 (June 2002): "An Offer/Answer Model with the Session Description Protocol (SDP)".
[8]
TS 33.180: "Security of the mission critical service".
[9]
TS 29.199-09: "Open Service Access (OSA); Parlay X Web Services; Part 9: Terminal location".
[10]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[11]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[12]
RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication".
[13]
RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[14]
RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[15]
RFC 3261 (June 2002): "SIP: Session Initiation Protocol".
[16]
RFC 6665 (July 2012): "SIP-Specific Event Notification".
[17]
RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[18]
RFC 3863 (August 2004): "Presence Information Data Format (PIDF)".
[19]
RFC 4661 (September 2006): "An Extensible Markup Language (XML)-Based Format for Event Notification Filtering".
[20]
RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[21]
RFC 6086 (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[22]
RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[23]
RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[24]
TS 24.481: "Mission Critical Services (MCS) group management; Protocol specification".
[25]
TS 24.484: "Mission Critical Services (MCS) configuration management; Protocol specification".
[26]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[27]
RFC 5373 (November 2008): "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[28]
RFC 5318 (December 2008): "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
[29]
RFC 4483 (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".
[30]
RFC 4964 (September 2007): "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular".
[31]
RFC 4488 (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[32]
RFC 4538 (June 2006): " Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[33]
RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[34] Void.
[35]
RFC 5626 (October 2009): "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)".
[36]
TS 22.281: "Mission Critical Video over LTE".
[37]
RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[38]
RFC 8101 (March 2017): "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk Service".
[39]
TS 23.032: "Universal Geographical Area Description (GAD)".
[40]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification".
[41]
RFC 5627 (October 2009): "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)".
[42] Void.
[43] Void.
[44]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[45]
W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-core1/ .
[46]
RFC 4648 (October 2006): "The Base16, Base32, and Base64 Data Encodings".
[47]
TS 23.003: "Numbering, addressing and identification".
[48]
RFC 2045 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[49]
RFC 2392 (August 1998): "Content-ID and Message-ID Uniform Resource Locators".
[50]
W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-core/
[51] Void.
[52]
TS 24.482: "Mission Critical Services (MCS) identity management Protocol specification".
[53]
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".
[54]
TS 29.283: "Diameter Data Management Applications".
[55]
RFC 6509 (February 2012): "MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY)".
[56] Void.
[57]
RFC 4575 (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".
[58]
RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[59]
TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects".
[60]
TS 24.237: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity".
[61]
TS 26.281: "Mission Critical Video (MCVideo); Codecs and media handling".
[62]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)".
[63]
RFC 6809 (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[64]
RFC 3515 (April 2003): "The Session Initiation Protocol (SIP) Refer Method".
[65]
RFC 7647 (September 2015): "Clarifications for the Use of REFER with RFC 6665".
[66]
RFC 7462 (March 2015): "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)".
[67]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[68]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[69]
TS 23.203: "Policy and charging control architecture".
[70]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[71]
RFC 5368 (October 2008): "Referring to Multiple Resources in the Session Initiation Protocol (SIP)".
[72]
RFC 5761 (April 2010): "Multiplexing RTP Data and Control Packets on a Single Port".
[73]
TS 24.216: "Communication continuity managed object".
[74]
TS 23.280: "Technical Specification Group Services and System Aspects; Common functional architecture to support mission critical services; Stage 2".
[75]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[76]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[77]
TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[78]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push to Talk (MCPTT); Stage 2".
[79]
TS 24.380: "Mission Critical Push to Talk (MCPTT) media plane control; Protocol Specification".
[80]
RFC 3550 (July 2003): "RTP: A Transport Protocol for Real-Time Applications".
[81]
RFC 7614 (August 2015): "Explicit Subscriptions for the REFER method".
[82]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[83]
RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
3 Definitions, symbols and abbreviations p. 27
3.1 Definitions p. 27
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 MCVideo user is affiliated to an MCVideo group:
The MCVideo user is listed as a member of the MCVideo group in the MCVideo group document, the MCVideo server owning the MCVideo group has authorised the MCVideo user's interest in the MCVideo group and the MCVideo server serving the MCVideo user has authorised the MCVideo user's interest in the MCVideo group.
An MCVideo user is affiliated to an MCVideo group at an MCVideo client:
The MCVideo user is affiliated to the MCVideo group, the MCVideo client has a registered IP address for an IMPU related to the MCVideo ID, and the MCVideo server serving the MCVideo user has authorised the MCVideo user's interest in the MCVideo group at the MCVideo client.
Affiliation status:
Applies for an MCVideo user to an MCVideo group and has one of the following states:
- the "not-affiliated" state indicating that the MCVideo user is not interested in the MCVideo group and the MCVideo user is not affiliated to the MCVideo group;
- the "affiliating" state indicating that the MCVideo user is interested in the MCVideo group but the MCVideo user is not affiliated to the MCVideo group yet;
- the "affiliated" state indicating that the MCVideo user is affiliated to the MCVideo group and there was no indication that MCVideo user is no longer interested in the MCVideo group; and
- the "deaffiliating" state indicating that the MCVideo user is no longer interested in the MCVideo group but the MCVideo user is still affiliated to the MCVideo group.
a call type allowing an authorized MCVideo user to cause an MCVideo client to initiate a communication which results in no indication on the MCVideo UE that it is transmitting. Ambient viewing can be initiated by an authorized MCVideo user who wants to be viewed to by another authorized MCVideo user or can be initiated by an authorized MCVideo user who wants to view to another MCVideo user.
Ambient viewing client role:
the role of an MCVideo client in an ambient viewing call, which can be that of:
- the "viewing MCVideo user"; or
- the "viewed-to MCVideo user".
the type of an ambient viewing call from the perspective of the relationship of the initiator of the call to the user being viewed to. The two types of ambient viewing call are:
- "remote-init", indicating that the viewing MCVideo user initiated the call; and
- "local-init", indicating that the viewed-to MCVideo user initiated the call.
Applies for the status of a functional alias for an MCVideo user and has one of the following states:
- the "not-activated" state indicating that the MCVideo user has not activated the functional alias;
- the "activating" state indicating that the MCVideo user is interested in using the functional alias but the functional alias is not yet activated for the MCVideo user;
- the "activated" state indicating that the MCVideo user has activated the functional alias;
- the "deactivating" state indicating that the MCVideo user is no longer interested in using the functional alias but the functional alias is still activated for the MCVideo user; and
- the "take-over-possible" state indicating that the MCVideo user is interested in using the functional alias but the functional alias is already activated and used by another MCVideo user.
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 MCVideo server at the time of the regroup creation, see clause 21.
Group identity:
An MCVideo group identity or a temporary MCVideo group identity.
For the purpose of the present document, the following terms and definitions given in TS 24.581 apply:
MBMS bearer
MBMS subchannel
MCVideo client ID:
is a globally unique identification of a specific MCVideo client instance. MCVideo client ID is a UUID URN as specified in RFC 4122.
MCVideo emergency alert state:
MCVideo client internal perspective of the state of an MCVideo emergency alert.
MCVideo emergency group state:
MCVideo client internal perspective of the in-progress emergency state of an MCVideo group maintained by the controlling MCVideo function.
MCVideo emergency group call state:
MCVideo client internal perspective of the state of an MCVideo emergency group call.
MCVideo emergency private call:
MCVideo emergency call between two MCVideo users that is initiated as a private call or a first-to-answer call with emergency indication, or without emergency indication when the MCVideo emergency state is already set,
MCVideo emergency private call state:
MCVideo client internal perspective of the state of an MCVideo emergency private call.
MCVideo emergency private priority state:
MCVideo client internal perspective of the in-progress emergency private call state of the two participants of an MCVideo emergency private call maintained by the controlling MCVideo function.
MCVideo imminent peril group call state:
MCVideo client internal perspective of the state of an MCVideo imminent peril group call.
MCVideo imminent peril group state:
MCVideo client internal perspective of the state of an MCVideo imminent peril group.
MCVideo private call:
MCVideo call between two MCVideo users that is initiated as a private call or a first-to-answer call.
MCVideo private emergency alert state:
MCVideo client internal perspective of the state of an MCVideo private emergency alert targeted to an MCVideo user.
MCVideo video media:
streaming video and audio media used in mission critical video systems as defined by TS 22.179 and TS 23.281.
Media-transmission control entity:
A media control resource shared by participants in an MCVideo session, controlled by a state machine to ensure that participants can access the media resource at the same time.
N2:
The maximum number of simultaneous affiliations to MCVideo groups that the MCVideo client may have. The value of N2 is specified in the <MaxAffiliationsN2> element of the <Common> element of the MCVideo user profile and corresponds to the parameter Nc2 specified in TS 22.280.
Private call:
A call initiated by one user towards one other user with the intention to establish an MCVideo private call or MCVideo emergency private call.
Remote change of an MCVideo user's selected group:
A mechanism allowing an authorised user to remotely change the selected group of another MCVideo user.
Temporary MCVideo group identity:
A group identity representing a temporary grouping of MCVideo group identities formed by the group regrouping operation as specified in TS 24.481.
Trusted mutual aid:
A business relationship whereby the Partner MCVideo system is willing to share the details of the members of an MCVideo group that it owns with the Primary MCVideo system.
Untrusted mutual aid:
A business relationship whereby the Partner MCVideo system is not willing to share the details of the members of an MCVideo group that it owns with the Primary MCVideo 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 MCVideo server implementation.
Viewing MCVideo user:
the MCVideo user in an ambient viewing call receiving the media transmission from the viewed-to MCVideo user;
Viewed-to MCVideo user:
the MCVideo user in an ambient viewing call who is being viewed to, may or may not be aware of being viewed to depending on ambient viewing type of the call.
For the purposes of the present document, the following terms and definitions given in TS 22.179 apply:
In-progress emergency
MCVideo emergency alert
MCVideo emergency group call
MCVideo emergency state
Partner MCVideo system
Primary MCVideo system
For the purpose of the present document, the following terms and definitions given in TS 23.281 apply:
Pre-selected MCVideo user profile
Selected MCVideo 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)
Functional alias status:
Applies for the status of a functional alias for an MCVideo user and has one of the following states:
- the "not-activated" state indicating that the MCVideo user has not activated the functional alias;
- the "activating" state indicating that the MCVideo user is interested in using the functional alias but the functional alias is not yet activated for the MCVideo user;
- the "activated" state indicating that the MCVideo user has activated the functional alias; and
- the "deactivating" state indicating that the MCVideo user is no longer interested in using the functional alias but the functional alias is still activated for the MCVideo user.
Functional alias
3.2 Symbols p. 30
3.3 Abbreviations p. 30
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.
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
MBSFN
Multimedia Broadcast multicast service Single Frequency Network
MC
Mission Critical
MCS
Mission Critical Service
MCVideo
Mission Critical Video
MCVideo group ID
MCVideo group Identity
MVEA
MCVideo Emergency Alert
MVEG
MCVideo Emergency Group
MVEGC
MCVideo Emergency Group Call
MVEPC
MCVideo Emergency Private Call
MVEPP
MCVideo Emergency Private Priority
MVES
MCVideo Emergency State
MIME
Multipurpose Internet Mail Extensions
MVIG
MCVideo Imminent peril Group
MVIGC
MCVideo Imminent peril Group Call
MONP
MC service Off-Network Protocol
MVPEA
MCVideo Private Emergency Alert
NAT
Network Address Translation
PCC
Policy and Charging Control
PCCB
Private Call Call-Back
PLMN
Public Land Mobile Network
QCI
QoS Class Identifier
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 MCVideo Group Identity
TMGI
Temporary Mobile Group Identity
UE
User Equipment
URI
Uniform Resource Identifier
XPK
XML Protection Key
