7 Coding

24.5483GPPNetwork Resource Management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS

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

7.1 General

This clause specifies the coding to enable an SNRM-C and an SNRM-S to communicate.

7.2 Application unique ID

The AUID shall be set to the VAL service ID as specified in specific VAL service specification.

7.3 Structure

The network resource management document shall conform to the XML schema described in clause 7.4.

7.3.1 VALInfo document

The <seal-request-uri> element shall be the root element of the VALInfo document.

The <seal-request-uri> element shall include one of the followings:

a) a <VAL-user-id> element may include a <VAL-client-id> element; or

b) a <VAL-group-id> element.

7.3.2 UnicastInfo document

The <unicast-info> element shall be the root element of the UnicastInfo document.

The <unicast-info> element shall include one of the followings:

a) a <request> element;r

b) a <request-result> element;

c) a <modification> element;

d) a <modification-result> element;

e) an <adaptation> element; or

f) an <adaptation-result> element.

The <request> element shall include the followings:

a) a <requester-identity> element;

b) an <identity> element; and

c) an optional < requirement-info> element.

The <modification> element shall include the followings:

a) a <requester-identity> element;

b) an <identity> element; and

c) a <requirement-info> element.

The <adaptation> element shall include the followings:

a) a <requester-identity> element;

b) an <identity> element which shall include one of the following elements:

1) a <VAL-ue-id-list> element which shall include:

i) one or more <VAL-ue-id> elements; and

2) a <VAL-group-id> element; and

c) a <requirement> element.

7.3.3 MBMSInfo document

The <mbms-info> element shall be the root element of the MBMSInfo document.

The <mbms-info> element shall include one of the followings:

a) one or more <announcement> elements;

b) an <mbms-listening-status-report> element;

c) a <request> element;

d) an <mbms-bearers> element;

e) a <user-plane-delivery-mode> element;

f) an <mbms-suspension-reporting-instruction> element; or

g) an <mbms-suspension-report> element.

The <announcement> element shall include:

a) a <TMGI> element;

b) an optional <alternative-TMGI> element;

c) an optional <QCI> element;

d) an <mbms-service-areas> element which shall include:

1) one or more <mbms-sa-id> elements;

e) a <frequency> element;

f) an <seal-mbms-sdp> element;

g) an optional <monitoring-state> element;

h) an optional <announcement-acknowlegement> element;

i) an optional <unicast-status> element; and

j) an optional <seal-mbms-rohc> element.

The <mbms-listening-status-report> element shall include:

a) an <identity> element;

b) a <TMGI> element;

c) an <mbms-listening-status> element;

d) an optional <mbms-reception-quality-level> elment; and

e) an optional <unicast-listening-status> element.

The <request> element shall include:

a) a <requester-indentity> element;

b) a <VAL-group-id> element;

c) a <service-anouncement-mode> element;

d) a <QoS> element;

e) an optional <broadcast area> element; and

f) an <endpoint-info> element.

The <mbms-bearers> element shall include:

a) a <result> element;

b) an optional <TMGI> element;

c) a <user-plane-address> element; and

d) an optional <service-description> element.

The <user-plane-delivery-mode> element shall include:

a) a <delivery-mode> element;

b) an <MBMS-media-stream-id> element; and

c) a <unicast-media-stream-id> element;

The <mbms-suspension-reporting-instruction> element shall include either the first two followings or the third following:

a) an <identity> element;

b) a <suspension-reporting> element; or

c) a <suspension-reporting-client-subset> element which shall include:

1) one or more <NRM-client-id> elements.

The <mbms-suspension-report> element shall include:

a) an <mbms-suspension-status> element;

b) an <number-of-reported-bearers> element;

c) one or more <suspended-TMGI> element; and

d) an optional <other-TMGI> element.

7.3.4 NetworkQoSManagementInfo document

The <network-QoS-management-info> element shall be the root element of the NetworkQoSManagementInfo document.

The <NetworkQoSManagement-info> element shall include one of the followings:

a) a <QoS-management-initiation-request> element;

b) a <QoS-management-initiation-responset> element;

c) a <QoS-management-provision-request> element; and

d) a <QoS-management-provision-response> element;

The <QoS-management-initiation-request> element:

a) shall include a <VAL-ue-id> element;

b) shall include a <VAL-ue-list> element;

1) shall include one or more <VAL-ue-id> elements;

c) may include <VAL-service-id> element which:

d) may include <end-to-end-QoS-requirements> element;

e) may include <service-area> element; and

f) may include <validity-period> element.

The <QoS-management-initiation-response> element:

a) shall include a <result> element; and

b) may include a <QoS-configuration> element.

The <QoS-management-provision-request> element:

a) shall include a <VAL-ue-id> element; and

b) may include a <QoS-downgrade-report> element;

The <QoS-management-provision-response> element:

a) shall include a <server-id> element; and

b) shall include a <requested-QoS-parameters> element;

7.4 XML schema

7.4.1 General

This clause defines the XML schemas for application/vnd.3gpp.seal-info+xml, application/vnd.3gpp.seal-unicast-info+xml and application/vnd.3gpp.seal-mbms-usage-info+xml.

7.4.2 XML schema for application/vnd.3gpp.seal-info+xml

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

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

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

xmlns:sealinfo="urn:3gpp:ns:sealInfo:1.0"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">

<!– root XML element –>

<xs:element name="seal-request-uri" type="sealinfo:sealinfo-Type" id="info"/>

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

<xs:sequence>

<xs:element name="VAL-user-id" type="sealinfo:contentType" minOccurs="0"/>

<xs:element name="VAL-group-id" type="xs:string" minOccurs="0"/>

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="contentType">

<xs:choice>

<xs:element name="sealURI" type="xs:anyURI"/>

<xs:element name="sealString" type="xs:string"/>

<xs:element name="sealBoolean" type="xs:boolean"/>

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

</xs:choice>

<xs:attribute name="type" type="sealinfo:protectionType"/>

</xs:complexType>

</xs:schema>

7.4.3 XML schema for application/vnd.3gpp.seal-unicast-info+xml

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

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

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

xmlns:sealunicast="urn:3gpp:ns:sealUnicastInfo:1.0"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">

<!– the root element –>

<xs:element name="seal-unicast-info" id="unicast">

<xs:complexType>

<xs:choice>

<xs:element name="request" type="sealunicast:requestType"/>

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

<xs:element name="modification" type="sealunicast:modificationType"/>

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

<xs:element name="adaptation" type="sealunicast:adaptationType"/>

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

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

</xs:choice>

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

</xs:complexType>

</xs:element>

<xs:complexType name="requestType">

<xs:sequence>

<xs:element name="requesterID" type="xs:string" use="required"/>

<xs:element name="ID" type="xs:string" use="required"/>

<xs:element name="requirement-info" type="xs:string" use="optional"/>

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

</xs:sequence>

</xs:complexType>

<xs:complexType name="modificationType">

<xs:sequence>

<xs:element name="requesterID" type="xs:string" use="required"/>

<xs:element name="ID" type="xs:string" use="required"/>

<xs:element name="requirement-info" type="xs:string" use="required"/>

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

</xs:sequence>

</xs:complexType>

<xs:complexType name="adaptationType">

<xs:sequence>

<xs:element name="requesterID" type="xs:string" use="required"/>

<xs:element name="ID" type="xs:string" use="required"/>

<xs:element name="requirement-info" type="xs:string" use="required"/>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

7.4.4 XML schema for application/vnd.3gpp.seal-mbms-usage-info+xml

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

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

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

xmlns:sealmbms="urn:3gpp:ns:sealMbmsInfo:1.0"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">

<!– the root element –>

<xs:element name="seal-mbms-usage-info" type="sealmbms:seal-mbms-usage-info-Type" id="mbms"/>

<xs:complexType name="seal-mbms-usage-info-Type">

<xs:sequence>

<xs:element name="mbms-listening-status-report" type="sealmbms:mbms-listening-status-reportType"
minOccurs="0"/>

<xs:element name="mbms-suspension-report" type="sealmbms:mbms-suspension-reportType"
minOccurs="0"/>

<xs:element name="announcement" type="sealmbms:announcementTypeParams" minOccurs="0"/>

<xs:element name="user-plane-delivery-mode" type="sealmbms:user-plane-delivery-modeType" minOccurs="0"/>

<xs:element name="mbms-suspension-reporting-instruction" type="sealmbms:mbms-suspension-reporting-instructionType" minOccurs="0"/>

<xs:element name="request" type="sealmbms:requestType" minOccurs="0"/>

<xs:element name="version" type="xs:integer"/>

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="mbms-listening-status-reportType">

<xs:sequence>

<xs:element name="ID" type="xs:string"/>

<xs:element name="TMGI" type="xs:hexBinary" maxOccurs="unbounded"/>

<xs:element name="mbms-listening-status" type="xs:string"/>

<xs:element name="mbms-reception-quality-level" type="xs:integer"/>

<xs:element name="unicast-listening-status" type="xs:string"/>

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="mbms-suspension-reportType">

<xs:sequence>

<xs:element name="mbms-suspension-status" type="xs:string" minOccurs="0" maxOccurs="1"/>

<xs:element name="number-of-reported-bearers" type="xs:integer" minOccurs="0" maxOccurs="1"/>

<xs:element name="suspended-TMGI" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="other-TMGI" type="xs:hexBinary" minOccurs="0" maxOccurs="unbounded"/>

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="announcementTypeParams">

<xs:sequence>

<xs:element name="TMGI" type="xs:hexBinary" minOccurs="1"/>

<xs:element name="alternative-TMGI" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="QCI" type="xs:integer" minOccurs="0"/>

<xs:element name="frequency" type="xs:unsignedLong" minOccurs="0"/>

<xs:element name="mbms-service-areas" type="sealmbms:mbms-service-areasType" minOccurs="0"/>

<xs:element name="seal-mbms-sdp" type="xs:string"/>

<xs:element name="monitoring-state" type="xs:string" minOccurs="0"/>

<xs:element name="announcement-acknowlegement" minOccurs="0"/>

<xs:element name="unicast-status" type="xs:string" minOccurs="0"/>

<xs:element name="seal-mbms-rohc" 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="mbms-service-areasType">

<xs:sequence>

<xs:element name="mbms-service-area-id" type="xs:hexBinary"
minOccurs="1" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute/>

</xs:complexType>

<xs:complexType name="user-plane-delivery-modeType">

<xs:sequence>

<xs:element name="delivery-mode" type="xs:string" minOccurs="1"/>

<xs:element name="MBMS-media-stream-id" type="xs:string" minOccurs="1"/>

<xs:element name="unicast-media-stream-id" type="xs:string" 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="mbms-suspension-reporting-instructionType">

<xs:sequence>

<xs:element name="suspension-reporting" type="xs:string" minOccurs="1"/>

<xs:element name="suspension-reporting-client-subset" type="sealmbms:suspension-reporting-client-subsetType" minOccurs="1"/>

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="suspension-reporting-client-subsetType">

<xs:sequence>

<xs:element name="NRM-client-id" type="xs:string" minOccurs="1" maxOccurs="unbounded"/>

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

</xs:sequence>

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

</xs:complexType>

</xs:schema>

7.4.5 XML schema for application/vnd.3gpp.seal-network-QoS-management-info+xml

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

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

targetNamespace="urn:3gpp:ns:seal NetworkQoSManagementInfo:1.0"

xmlns:sealunicast="urn:3gpp:ns:seal NetworkQoSManagementInfo:1.0"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">

<!– the root element –>

<xs:element name="seal-network-QoS-management-info" id="NetworkQoSManagement">

<xs:complexType>

<xs:choice>

<xs:element name="QoS-management-initiation-request" type="sealNetworkQoSManagement:QoS-management-initiation-requestType"/>

<xs:element name="QoS-management-initiation-response" type="sealNetworkQoSManagement:QoS-management-initiation-responseType"/>

<xs:element name="QoS-management-provision-request" type="sealNetworkQoSManagement:QoS-management-provision-requestType"/>

<xs:element name="QoS-management-provision-response" type="sealNetworkQoSManagement:QoS-management-provision-responseType"/>

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

</xs:choice>

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

</xs:complexType>

</xs:element>

<xs:complexType name="QoS-management-initiation-requestType">

<xs:sequence>

<xs:element name="VAL-ue-id" type="xs:string" use="required"/>

<xs:element name="VAL-ue-list" type="xs:string" use="required"/>

<xs:element name="VAL-service-id" type="xs:string" use="optional"/>

<xs:element name="end-to-end-QoS-requirements" type="xs:string" use="optional"/>

<xs:element name="service-area" type="xs:string" use="optional"/>

<xs:element name="validity-period" type="xs:string" use="optional"/>

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

</xs:sequence>

</xs:complexType>

<xs:complexType name="QoS-management-initiation-responseType">

<xs:sequence>

<xs:element name="result" type="xs:string" use="required"/>

<xs:element name="QoS-configuration" type="xs:string" use="optional"/>

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

</xs:sequence>

</xs:complexType>

<xs:complexType name="QoS-management-provision-requestType">

<xs:sequence>

<xs:element name="VAL-ue-id" type="xs:string" use="required"/>

<xs:element name="QoS-downgrade-report" type="xs:string" use="optional"/>

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

</xs:sequence>

</xs:complexType>

<xs:complexType name="QoS-management-provision-responseType">

<xs:sequence>

<xs:element name="server-id" type="xs:string" use="required"/>

<xs:element name="requested-QoS-parameters" type="xs:string" use="required"/>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

7.5 Data semantics

7.5.1 VALInfo document

The <seal-request-uri> element is the root element of the XML document. The < seal-request-uri> element contains contains one of following sub-elements:

a) <VAL-user-id>, an element contains the identity of the VAL user. This element contains an optional <VAL-client-id> attribute that contains the identity of the VAL client; or

b) <VAL-group-id>, an element contains the group identity of a set of VAL users or VAL clients according to the VAL service.

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

7.5.2 UnicastInfo document

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

The <unicast-info> element is the root element of the XML document. The <unicast-info> element contains a <request> or <request-result> element.

<request> is an optional element used to include the unicast resource management requested information. The <request> element contains the following sub-elements:

a) <requester-identity>, an element contains the identity of the VAL server performing the request;

b) <identity>, an element contains the identity of the VAL user or VAL UE; and

c) <requirement-info>, an optional element contains the requested unicast resource information.

<request-result> contains a string set to either "success" or "failure" used to indicate success or failure of the resource request operation ".

<modification> contains the following sub-elements:

a) <requester-identity>, an element contains the identity of the VAL server performing the request;

b) <identity>, an element contains the identity of the VAL user or VAL UE; and

c) <requirement-info>, an element contains the modified unicast resource information.

<modification-result> contains a string set to either "success" or "failure" used to indicate success or failure of the resource modification request operation.

<adaptation> contains the following sub-elements:

a) <requester-identity>, an element contains the identity of the VAL server performing the request;

b) <identity>, an element contains one of the following elements:

1) <VAL-ue-id-list>, an element contains one or more <VAL-ue-id> elements. Each <VAL-ue-id> element contains the identity of the VAL UE for whom the network resource adaptation occurs; and

2) <VAL-group-id>, an element contains the identity of the VAL group for whom the network resource adaptation occurs; and

c) <requirement>, an element contains VAL service QoS requirements as applied for the corresponding VAL UEs or group of UEs.

<adaptation-result> contains a string set to either "success" or "failure" used to indicate success or failure of the network resource adaptation with the underlying network.

7.5.3 MBMSInfo document

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

The <mbms-info> element is the root element of the XML document. The <mbms-info> element contains one or more <announcement> subelements, the <mbms-listening-status-report> subelement, the <request> subelement, the <mbms-bearers> subelement, the <user-plane-delivery-mode> subelement, the <mbms-suspension-reporting-instruction> subelement and the <mbms-suspension-report> subelement.

<announcement> element contains the following sub-elements:

a) <TMGI>, an element contains the TMGI. The <TMGI> element is coded as described in 3GPP TS 24.008 [5] clause 10.5.6.13 excluding the Temporary mobile group identity IEI and the Length of temporary mobile group identity contents (octet 1 and octet 2 in 3GPP TS 24.008 [5] clause 10.5.6.13);

b) <alternative-TMGI>, an optional element contains a list of additional alternative TMGI used in roaming scenarios;

c) <QCI>, an optional element contains the QCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5. QCI values are defined in 3GPP TS 23.203 [4];

d) <mbms-service-areas>, an element contains a list of MBMS service area IDs for the applicable MBMS broadcast area as specified in 3GPP TS 23.003 [3] for service area identifier (SAI), and with the encoding as specified in 3GPP TS 29.061 [11] for the MBMS-Service-Area AVP;

e) <frequency>, an optional element contains identification of frequency in case of multi carrier support. The <frequency> element is coded as specified in 3GPP TS 29.468 [13];

f) <seal-mbms-sdp>, an element contains SDP with media and application control information applicable to groups that can use this bearer;

g) <monitoring-state>, an optional element contains a string used to control if the client is actively monitoring the MBMS bearer quality or not:

– The value "monitor" indicates that the SNRM-C shall monitor the MBMS bearer quality; and

– The value "not-monitor" indicates that the SNRM-C shall not monitor the MBMS bearer quality;

h) <announcement-acknowlegement>, presence of the <announcement-acknowlegement> element indicates the NRM server requires an acknowledgement of the MBMS bearer announcement;

i) <unicast-status>, presence of the <unicast-status> element indicates the listening status of the unicast bearer is requested; and

j) <seal-mbms-rohc>, presence of the <seal-mbms-rohc> element indicates that the flows delivered by the announced MBMS bearer are header compressed with ROHC as specified in IETF RFC 5795 [20] and IETF RFC 3095 [16].

<mbms-listening-status-report> element contains the following sub-elements:

a) <identity>, an element contains the identity of the VAL user or VAL UE who wants to report the MBMS listening status;

b) <TMGI>, an element contains the TMGI. The <TMGI> element is coded as described in 3GPP TS 24.008 [5] clause 10.5.6.13 excluding the Temporary mobile group identity IEI and the Length of temporary mobile group identity contents (octet 1 and octet 2 in 3GPP TS 24.008 [5] clause 10.5.6.13);

c) <mbms-listening-status>, an element contains a string "listening" or "not-listening" used to indicate the MBMS listening status per TMGI;

d) <mbms-reception-quality-level>, an optional element contains an integer used to indicate the reception quality level per TMGI; and

e) <unicast-listening-status>, an optional element contains a string "listening" or "not-listening" used to indicate the unicast listening status.

<request> is an element used to include the multicast resource management requested information. The <request> element contains the following sub-elements:

a) <requester-indentity>, an element contains the identity of the VAL server performing the request;

b) <VAL-group-id>, an element contains the identity of the VAL group that the MBMS bearer is requested for;

c) <service-anouncement-mode>, an element contains a string used to indicate whether the request is sent by NRM server or by the VAL server:

– The value "NRM-S" indicates the request is sent by NRM server;

– The value "VAL-server" indicates the request is sent by the VAL server;

d) <QoS>, an element contains the requested QoS information for the bearer;

e) <broadcast-area>, an optional element specifying the serving MBMS service area id where the MBMS bearer is requested for; and

f) <endpoint-info>, an element contains the information of the endpoint of the VAL server to which the user plane notifications have to be sent.

<mbms-bearers> element contains the following sub-elements:

a) <result>, an element contains a string either "success" or "failure" indicating success or failure of the MBMS bearers request operation;

b) <TMGI>, an optional element contains the TMGI. The <TMGI> element is coded as described in 3GPP TS 24.008 [5] clause 10.5.6.13 excluding the Temporary Mobile Group Identity IEI and Length of Temporary Mobile Group Identity contents (octet 1 and octet 2 in 3GPP TS 24.008 [5] clause 10.5.6.13);

c) <user-plane-address>, an element contains the BM-SC user plane IP address and port; and

d) <service-description>, an optional element contains the MBMS bearer related configuration information as defined in 3GPP TS 26.346 [10];

<user-plane-delivery-mode> element contains the following sub-elements:

a) <delivery-mode>, an element contains a string used to indicate whether to deliver the user data to the UE(s) via unicast mode or multicast mode:

– The value "unicast" indicates to deliver the user data to the UE(s) via unicast mode;

– The value "multicast" indicates to deliver the user data to the UE(s) via mulicast mode;

b) <MBMS-media-stream-id>, an element set to the MBMS media stream ID indicating the MBMS media stream to be used to deliver the media currently over unicast, or the MBMS media stream currently being used; and

c) one or more <unicast-media-stream-id> element(s), each element set to the unicast media stream ID indicating the unicast media stream to be used to deliver the media currently over multicast, or the unicast to be stopped and switched to multicast.

<mbms-suspension-reporting-instruction> contains the following sub-elements:

a) <identity>, an element contains the identity of the VAL user or VAL UE that reports MBMS suspension in case of a unicast bearer is used for MBMS suspension reporting;

b) <suspension-reporting>, an element contains a string used to enable or disable the suspension reporting for the SNRM-C in case of a unicast bearer is used for MBMS suspension reporting:

– The value "enable" indicates to enable the suspension reporting;

– The value "disable" indicates to disable the suspension reporting; and

c) <suspension-reporting-client-subset>, an element contains one or more <NRM-client-id> child elements set to the identities of the NRM clients that shall report MBMS suspension in case of a multicast bearer is used for MBMS suspension reporting;

<mbms-suspension-report> element contains the following sub-elements:

a) <mbms-suspension-status>, an element contains a string used to indicate the MBMS bearers intended suspension status:

– The value "suspending" indicates that the RAN has decided to suspend the referenced MBMS bearer(s) at the beginning of the next MCCH modification period;

– The value "not-suspending" indicates that the RAN has decided to revoke its decision to suspend the referenced MBMS bearer(s) before the beginning of the next MCCH modification period;

b) <number-of-reported-bearers>, an element contains a hex binary number denoting the total number of occurrences of the <suspended-TMGI> and <other-TMGI> elements reported as part of the MBMS bearer suspension status;

c) <suspended-TMGI>, an element contains a TMGI that is being reported as about to be suspended or as no longer about to be suspended; and

d) <other-TMGI>, an element contains a TMGI that is not being reported as about to be suspended or as no longer about to be suspended, but which shares the same MCH with MBMS bearers reported in the <suspended-TMGI> elements;

a) shall include a <VAL-ue-id> element; and

b) may include a <QoS-downgrade-report> element;

The <QoS-management-provision-response> element:

a) shall include a <server-id> element; and

b) shall include a <requested-QoS-parameters> element;

7.5.4 NetworkQoSManagementInfo document

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

The <network-QoS-management-info> element is the root element of the XML document. The <network-QoS-management-info> element contains a <QoS-management-initiation-request> element, a <QoS-management-initiation-response> element, a <QoS-management-provision-request> element or a <QoS-management-provision-response> element.

A <QoS-management-initiation-request> element is used to request for initiation of the network assisted QoS management. The <QoS-management-initiation-request> element:

a) shall include a <VAL-ue-id> element which contains the identity of IP address of the VAL UE performing the request;

b) shall include a <VAL-ue-list> element which contains one or more <VAL-ue-id> child elements, each contains the identity of the VAL UE;

c) may include a <VAL-service-id> element which contains the VAL service identity of the VAL application;

d) may include a <end-to-end-QoS-requirements> element which contains the QoS requirements for latency, throughput, reliability and jitter for the VAL application for the end-to-end session;

e) may include a <service-area> element which contains the geographical area or topological area where an end-to-end QoS management request applies; and

f) may include a <validity-period> element which contains the period of time during which an end-to-end requirement is valid.

A <QoS-management-initiation-response> element is used to get the response for initiation of the network assisted QoS management. The <QoS-management-initiation-response> element:

a) shall include a <result> element which contains the outcome of the end-to-end QoS management response which indicates either a success or a failure; and

b) may include a <QoS-configuration> element which contains QoS downgrade reported by the SNRM-C or for QoS change requested by SNRM-S.

A <QoS-management-provision-request> element is used to request for provisioning of the network assisted QoS management. The <QoS-management-initiation-request> element:

a) shall include a <VAL-ue-id> element which contains the identity of the SNRM-C acting as the VAL UE and performing the request; and

b) may include <QoS-downgrade-report> element which contains the report indicating a QoS downgrade of the end-to-end QoS parameters (latency, throughput, reliability and jitter) which may be reported based on QoS configuration parameter from the end-to-end QoS management response.

A <QoS-management-provision-response> element is used to get the response for provisioning of the network assisted QoS management. The <QoS-management-initiation-request> element:

a) shall include a <server- id> element which contains the identity of the VAL server; and

b) shall include a <requested-QoS-parameters> element which contains change request for the end-to-end QoS management, imposed by the VAL server on one or more VAL UEs, engaged in a network-assisted communication.

7.6 MIME types

The MIME type for the VALInfo document shall be "application/vnd.3gpp.seal-info+xml MIME body".

The MIME type for the UnicastInfo document shall be "application/vnd.3gpp.seal-unicast-info+xml MIME body".

The MIME type for the MBMSInfo document shall be "application/vnd.3gpp.seal-mbms-usage-info+xml MIME body".

The MIME type for the NetworkQoSManagementInfo document shall be "application/vnd.3gpp.seal-network-QoS-managment-info+xml MIME body".

7.7 IANA registration template

7.7.1 IANA registration template for VALInfo

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

application/vnd.3gpp.seal-info+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 or in HTTP, so the security considerations from IETF RFC 3261 apply while exchanging information in SIP and the security considerations from IETF RFC 7231 apply while exchanging information in HTTP.

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.548 "Network Resource Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification" version 16.0.0, available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media type:

Applications supporting the SEAL network resource management 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>

7.7.2 IANA registration template for UnicastInfo

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

application/vnd.3gpp.seal-unicast-info+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:

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 employ compression.

Interoperability considerations:

Published specification:

3GPP TS 24.548 "Network Resource Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification" version 16.0.0, available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media type:

Applications supporting the SEAL network resource management 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>

7.7.3 IANA registration template for MBMSInfo

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

application/vnd.3gpp.seal-mbms-usage-info+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:

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 employ compression.

Interoperability considerations:

Published specification:

3GPP TS 24.548 "Network Resource Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification" version 16.0.0, available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media type:

Applications supporting the SEAL network resource management 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>

7.7.U IANA registration template for NetworkQoSManagementInfo

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

application/vnd.3gpp.seal-network-QoS-managment-info +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:

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 employ compression.

Interoperability considerations:

Published specification:

3GPP TS 24.548 "Network Resource Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification" version 16.3.0, available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media type:

Applications supporting the SEAL network resource management 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>

Annex A (normative):
CoAP resource representation and encoding