D.6 XML schema for regroup using preconfigured group

24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS

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

D.6.1 General

This clause defines the XML schema and MIME type for regroup using preconfigured group.

D.6.2 XML schema

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

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

targetNamespace="urn:3gpp:ns:preconfiguredRegroup:1.0"

xmlns:mcdatargrp="urn:3gpp:ns:preconfiguredRegroup:1.0"

attributeFormDefault="unqualified" elementFormDefault="qualified">

<!– root XML element –>

<xs:element name="mcdataregroup" type="mcdatargrp:mcdataregroup-Type" id="info"/>

<xs:complexType name="mcdataregroup-Type">

<xs:sequence>

<xs:element name="mcdataregroup-Params" type="mcdatargrp:mcdataregroup-ParamsType" minOccurs="0"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="mcdataregroup-ParamsType">

<xs:sequence>

<xs:element name="preconfig-group-id" type="mcdatargrp:preconfig-group-Type"/>

<xs:element name="mcdata-regroup-uri" type="mcdatargrp:mcdata-regroup-uri-Type"/>

<xs:element name="groups-for-regroup" type="mcdatargrp:groups-for-regroup-Type" minOccurs="0"/>

<xs:element name="users-for-regroup" type="mcdatargrp:users-for-regroup-Type" minOccurs="0"/>

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

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

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="preconfig-group-Type">

<xs:sequence>

<xs:element type="xs:anyURI" name="preconfigured-group" minOccurs="0"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="mcdata-regroup-uri-Type">

<xs:sequence>

<xs:element type="xs:anyURI" name="mcdata-regroup-uri"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="groups-for-regroup-Type">

<xs:sequence>

<xs:element type="xs:anyURI" name="group" maxOccurs="unbounded"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="users-for-regroup-Type">

<xs:sequence>

<xs:element type="xs:anyURI" name="user" maxOccurs="unbounded"/>

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

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

</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:schema>

D.6.3 Semantic

The <preconfigured-group> element shall contain a URI identifying the preconfigured MCData group.

The <mcdata-regroup-uri> element shall contain a URI containing the temporary group identity identifying the regroup.

The < groups-for-regroup> element shall contain one or more <group> elements that shall each contain a URI of a group that is to be a constituent group of the regroup.

The <users-for-regroup> element shall contain one or more <user> elements that shall each contain an MCData ID of a user that is to be affiliated to the regroup.

The XML document shall have either one <groups-for-regroup> element or one <users-for-regroup> element, but not both.

If the <regroup-action> element contains the string "create" then:

1) if a <groups-for-regroup> element exists in the received XML, then:

a) if the recipient is the controlling MCData function for the MCData group identified in the <preconfigured-group> element the recipient shall follow the procedures to create a group regroup with identity equal to the value contained in the <mcdata-regroup-uri> element based on the configuration of the preconfigured MCData group identified in the <preconfigured-group> element;

b) if the recipient is a non-controlling MCData function, the recipient shall follow the procedures to affiliate users belonging to any constituent groups of the group regroup with identity equal to the value contained in the <mcdata-regroup-uri> element based on the configuration of the preconfigured MCData group identified in the <preconfigured-group> element; and

c) if the recipient is the terminating participating MCData function for one or more MCData users affiliated to a constituent group of the group regroup, the recipient shall follow the procedures to notify each MCData user in the list of users in the <users-for-regroup> element that it serves of the group regroup and affiliate those users to the group regroup; and

2) if a <users-for-regroup> element exists in the received XML, then:

a) if the recipient is the controlling MCData function for the MCData group identified in the <preconfigured-group> element, the recipient shall follow the procedures to create a user regroup with identity equal to the value contained in the <mcdata-regroup-uri> element based on the configuration of the preconfigured MCData group identified in the <preconfigured-group> element; and

b) if the recipient is the terminating participating MCData function for one or more MCData users identified in the <users-for-regroup> element, the recipient shall follow the procedures to notify each MCData user in the list of users in the <users-for-regroup> element that it serves of the user regroup and affiliate those users to the user regroup.

If the <regroup-action> element contains the string "remove" then:

1) the recipient shall follow the procedures to remove the regroup identified in the <mcdata-regroup-uri> element.

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

D.6.4 IANA registration template

Editor’s Note: [enh2MCPTT-CT, CR 0529] MCC is requested to submit the IANA registration for this media type.

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

vnd.3gpp.mcdata-regroup+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.282 "Mission Critical Data (MCData) signalling control" version 16.4.1, 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>