F.5 XML schema for the floor request

24.3793GPPMission Critical Push To Talk (MCPTT) call controlProtocol specificationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

F.5.1 General

This clause defines XML schema and MIME type for application/vnd.3gpp.mcptt-floor-request+xml.

F.5.2 XML schema

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:3gpp:ns:mcpttFloorRequest:1.0" xmlns:mcpttfloor="urn:3gpp:ns:mcpttFloorRequest:1.0">

<!– the root element –>

<xs:element name="mcptt-floor-request" type="mcpttfloor:mcptt-floor-request-Type" minOccurs="1" maxOccurs="2"/>

<xs:complexType name="mcptt-floor-request-Type">

<xs:sequence>

<xs:element name="floor-type" type="xs:string"/>

<xs:element name="ssrc" type="xs:unsignedLong"/>

<xs:element name="floor-priority" type="xs:unsignedByte"/>

<xs:element name="user-id" type="xs:anyURI"/>

<xs:element name="track-info" type="mcpttfloor:track-info-Type"/>

<xs:element name="floor-indicator" type="xs:unsignedLong"/>

<xs:element name="anyExt" type="mcpttfloor:anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="anyExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="track-info-Type">

<xs:sequence>

<xs:element name="queueing-capability" type="xs:byte"/>

<xs:element name="participant-type" type="xs:string"/>

<xs:element name="floor-participant-reference" type="xs:unsignedLong" minOccurs="1" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="mcpttfloor:anyExtType" minOccurs="0"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

</xs:schema>

F.5.3 Semantic

This clause describes the elements of the floor request XML Schema.

<floor-type> Contains information about which floor the current speaker was using. The value "general is selected when the current speaker has permission to speak in on the general floor as specified in 3GPP TS 24.380 [5] clause 6.3.4. The value "dual" is selected when the current speaker has permission to speak in on the dual floor as specified in 3GPP TS 24.380 [5] clause 6.3.6.

Table F.5.3-1 shows the ABNF of the <floor-type> element.

Table F.5.3-1: ABNF syntax of values of the <floor-type> element

floor-type-value = general-value / dual-value

general-value = %x67.65.6e.65.72.62.6c ; "general"

dual-value = %x64.75.61.6c ; "dual"

<ssrc>: Contains the SSRC of the floor participant. The content of the SSRC field shall be coded as specified in IETF RFC 3550 [10].

<floor-priority>: Contains the level of priority of the floor request. The <floor-priority> element is coded as specified in 3GPP TS 24.380 [5].

<user-id>: Contains the MCPTT ID of the MCPTT user requesting the permission to send media.

<track-info>: Contains the <queueing-capability> element, the <participant-type> element and the <floor-participant-reference>.

<floor-indicator>: Contains additional information. The <floor-indicator> element is coded as specified in 3GPP TS 24.380 [5].

<participant-type>: Contains the participant type assigned to the MCPTT user identified by the <user-id> element. The <participant-type> element is coded as specified in3GPP TS 24.380 [5].

NOTE: The reference to the floor participant is a value only understandable by the floor control server interface in the non-Controlling function of an MCPTT group.

<queueing-capability>: Contains the queueing capability of the MCPTT client. The <queueing-capability> element is coded as specified in 3GPP TS 24.380 [5].

The recipient of the XML ignores any unknown element and any unknown attribute.

F.5.4 IANA registration template

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

vnd.3gpp.mcptt-floor-request+xml

Required parameters:

None

Optional parameters:

"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.

Encoding considerations:

binary.

Security considerations:

Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.

The information transported in this media type does not include active or executable content.

Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.

This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.

This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient’s privacy in any way.

This media type does not employ compression.

Interoperability considerations:

Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.

Published specification:

3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.0.0, available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media type:

Applications supporting the mission critical push to talk as described in the published specification.

Fragment identifier considerations:

The handling in section 5 of IETF RFC 7303 applies.

Restrictions on usage:

None

Provisional registration? (standards tree only):

N/A

Additional information:

1. Deprecated alias names for this type: none

2. Magic number(s): none

3. File extension(s): none

4. Macintosh File Type Code(s): none

5. Object Identifier(s) or OID(s): none

Intended usage:

Common

Person to contact for further information:

– Name: <MCC name>

– Email: <MCC email address>

– Author/Change controller:

i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG

ii) Change controller: <MCC name>/<MCC email address>