Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.282  Word version:  17.1.0

Top   Top   None   None   Next
1…   4…   6…   7…   8…   9…   10…   11…   12…   13…   14…   15…   16…   17…   18…   19…   20…   21…   22…   23…   A…

 

1  ScopeWord‑p. 20

The present document specifies the signalling control protocols needed to support Mission Critical Data (MCData) communications as specified by TS 23.282. The present document specifies both on-network and off-network protocols.
The present document utilises the common functional architecture to support mission critical services as specified in TS 23.280, in support of MCData communications.
The MCData 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 MCData client functionality, and to application servers supporting the MCData server functionality.
Up

2  References

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.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2";
[3]
TS 23.280: " Common functional architecture to support mission critical services; Stage 2";
[4]
RFC 3261  (June 2002): "SIP: Session Initiation Protocol".
[5]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[6]
RFC 3428  (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[7]
RFC 6050  (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[8]
RFC 3841  (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[9]
RFC 4826  (May 2007): "Extensible Markup Language (XML) Formats for Representing Resource Lists".
[10]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification".
[11]
TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
[12]
TS 24.484: "Mission Critical Services (MCS) configuration management Protocol specification".
[13]
RFC 4483  (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages.
[14]
RFC 4122  (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[15]
TS 24.582: "Mission Critical Data (MCData) media plane control Protocol specification";
[16]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[17]
RFC 4975  (September 2007): "The Message Session Relay Protocol (MSRP)".
[18]
RFC 5366  (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[19]
RFC 6135  (February 2011): "An Alternative Connection Model for the Message Session Relay Protocol (MSRP) ".
[20]
RFC 6714  (August 2012): "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)".
[21]
RFC 6086  (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[22]
RFC 7230:  "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
[23]
RFC 7231:  "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
[24]
TS 24.482: "Mission Critical Services (MCS) identity management Protocol specification.
[25]
TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[26]
TS 33.180: "Security of the Mission Critical Service".
[27]
Void
[28]
W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-core1/.
[29]
W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-core/.
[30]
RFC 4648  (October 2006): "The Base16, Base32, and Base64 Data Encodings".
[31]
TS 23.003: "Numbering, addressing and identification".
[32]
RFC 2045  (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[33]
RFC 2392  (August 1998): "Content-ID and Message-ID Uniform Resource Locators".
[34]
RFC 3903  (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication".
[35]
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".
[36]
RFC 6665  (July 2012): "SIP-Specific Event Notification".
[37]
TS 29.283: "Diameter Data Management Applications".
[38]
RFC 4028  (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[39]
RFC 3856  (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[40]
RFC 3863  (August 2004): "Presence Information Data Format (PIDF)".
[41]
RFC 4661  (September 2006): "An Extensible Markup Language (XML)-Based Format for Event Notification Filtering".
[42]
TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
[43]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[44]
RFC 5627  (October 2009): "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)".
[45]
RFC 4567  (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[46]
RFC 3986  (January 2005): "Uniform Resource Identifier (URI): Generic Syntax".
[47]
TS 23.032: "Universal Geographical Area Description (GAD)".
[48]
TS 29.582: "Mission Critical Data (MCData) signalling control interworking with LMR systems; Protocol specification".
[49]
TS 29.214: "Policy and Charging Control over Rx reference point".
[50]
RFC 5245  (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer Answer Protocols".
[51]
RFC 3515  (April 2003): "The Session Initiation Protocol (SIP) Refer Method".
[52]
RFC 7647  (September 2015): "Clarifications for the use of REFER with RFC6665".
[53]
RFC 4488  (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[54]
RFC 4538  (June 2006): "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[55]
RFC 6509  (February 2012): "MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY)".
[56]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[57]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[58]  Void.
[59]
RFC 5761  (April 2010): "Multiplexing RTP Data and Control Packets on a Single Port".
[60]
RFC 5795  (March 2010): "The RObust Header Compression (ROHC) Framework".
[61]
RFC 3095  (July 2001): "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".
[62]
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[63]
TS 23.203: "Policy and charging control architecture".
[64]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[65]
TS 29.199-09: "Open Service Access (OSA); Parlay X web services; Part 9: Terminal location".
[66]
OMA-TS-REST_NetAPI_NMS-V1_0-20190528-C: "RESTful Network API for Network Message Storage".
[67]
RFC 8101  (March 2017): "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk Service".
[68]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[69]
RFC 5547:  "A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer".
[70]
RFC 1738:  "Uniform Resource Locators (URL)".
[71]
RFC 4566  (July 2006): "SDP: Session Description Protocol".
[72]
RFC 5888  (June 2010): "The Session Description Protocol (SDP) Grouping Framework".
[73]
ISO 8601 (2019): "Date and Time - Representations for Information Exchange".
Up

3  Definitions, symbols and abbreviationsWord‑p. 23

3.1  Definitions

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 MCData user is affiliated to an MCData group:
The MCData user has expressed interest in an MCData group it is a member of, and both the MCData server serving the MCData user and the MCData server owning the MCData group have authorized the MCData user's interest in the MCData group communication.
An MCData user is affiliated to an MCData group at an MCData client:
The MCData user is affiliated to the MCData group, the MCData client has a registered IP address for an IMPU related to the MCData ID, and the MCData server serving the MCData user has authorised the MCData user's interest in the MCData group at the MCData client.
Affiliation status:
Applies for an MCData user to an MCData group and has one of the following states:
  1. the "not-affiliated" state indicating that the MCData user is not interested in the MCData group and the MCData user is not affiliated to the MCData group;
  2. the "affiliating" state indicating that the MCData user is interested in the MCData group but the MCData user is not affiliated to the MCData group yet;
  3. the "affiliated" state indicating that the MCData user is affiliated to the MCData group and there was no indication that MCData user is no longer interested in the MCData group; and
  4. the "deaffiliating" state indicating that the MCData user is no longer interested in the MCData group but the MCData user is still affiliated to the MCData group.
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 MCData server at the time of the regroup creation, see clause 23.
Group identity:
An MCData group identity or a temporary MCData group identity.
MCData client ID:
is a globally unique identification of a specific MCData client instance. MCData client ID is a UUID URN as specified in IETF RFC 4122 [14].
MCData emergency alert:
A notification from the MCData client to the MCData service that the MCData user has an emergency condition.
MCData emergency alert state:
MCData client internal perspective of the state of an MCData emergency alert.
MCData emergency group state:
MCData client internal perspective of the in-progress emergency state of an MCData group maintained by the controlling MCData function.
MCData emergency group communication:
An urgent MCData group communication that highlights a situation of potential death or serious injury.
MCData emergency group communication state:
MCData client internal perspective of the state of an MCData emergency group communication.
Functional alias status:
Applies for the status of a functional alias for an MCData user and has one of the following states:
  1. the "not-activated" state indicating that the MCData user has not activated the functional alias;
  2. the "activating" state indicating that the MCData user is interested in using the functional alias but the functional alias is not yet activated for the MCData user;
  3. the "activated" state indicating that the MCData user has activated the functional alias; and
  4. the "deactivating" state indicating that the MCData user is no longer interested in using the functional alias but the functional alias is still activated for the MCData user.
For the purpose of the present document, the following terms and definitions given in TS 33.180 apply:
Client Server Key (CSK)
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
Up

3.2  AbbreviationsWord‑p. 24

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
IMPU
P Multimedia Public User identity
MBMS
Multimedia Broadcast and Multicast Service
MC
Mission Critical
MCS
Mission Critical Service
MCData
Mission Critical Data
MCData group ID
MCData group Identity
MDEA
MCData Emergency Alert
MDEG
MCData Emergency Group
MDEGC
MCData Emergency Group Communication
MDES
MCData Emergency State
MIME
Multipurpose Internet Mail Extensions
MONP
MC service Off-Network Protocol
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
URI
Uniform Resource Identifier
URN
Uniform Resource Name
UUID
Universally Unique IDentifier
XPK
XML Protection Key
Up

Up   Top   ToC