7 Coding

24.5443GPPGroup Management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS

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

7.1 General

7.2 Application unique ID

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

7.3 Data structure

The <list-service> element:

a) shall include an "uri" attribute representing the VAL group identity;

b) may include a <display-name> element containing a human readable name of the VAL group;

c) shall include a <common> element. The <common> element:

1) may include a <seal-subject> element indicating group description;

2) shall include a <category> element indicating category of the group; and

3) shall include one or more <val-service-id> element(s) indicating list of services supported by the group; and

4) may include one or more <geo-id> element(s) indicating list of geographical areas to be addressed by the group.

d) may include a <administrators> element containing list of group members who are administrator for the group;

e) may include a <explicit-members-list> element containing list of users who explicitly needs to register to join the group;

f) may include a <list> element containing list of members who are implicitly registered to join the group; and

g) shall include a <val-specific-config> element. The <val-specific-config> element:

1) may include a <group-priority> element; and

2) may include an<external-group-id> element.

7.4 XML Schema

7.4.1 General

The Group Document shall be composed according to the XML schema described in [7] and extended with extensions from the XML Schemas defined in [8] and [9], and extended with extensions from the XML schema defined in clause 7.4.2.

7.4.2 XML schema for SEAL group document specific extension

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

<xs:schema

xmlns="urn:3gpp:ns:seal:GroupInfo:1.0"

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

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

xmlns:ls="urn:oma:xml:poc:list-service"

xmlns:sealgi="urn:3gpp:ns:seal:GroupInfo:1.0"

elementFormDefault="qualified"

attributeFormDefault="unqualified">

<xs:import namespace="urn:oma:xml:xdm:extensions"/>

<xs:import namespace="urn:ietf:params:xml:ns:resource-lists"/>

<!– SEAL specific "list-service" child elements –>

<xs:element name="common" type="sealgi:common-type"/>

<xs:element name="administrators" type="ls:list-type" minOccurs="0"/>

<xs:element name="explicit-member-list" type="ls:list-type" minOccurs="0"/>

<xs:element name="val-specific-config" type="sealgi:valSpecificConfigType"/>

<xs:complexType name="common-type">

<xs:sequence>

<xs:element name="seal-subject" type="sealgi:subjectType" minOccurs="0"/>

<xs:element name="category" type="sealgi:groupCategoryType"/>

<xs:element name="val-service-id" type="sealgi:serviceNameType" minOccurs="0" maxOccurs=="unbounded"/>

<xs:element name="geo-id" type="xs:string" minOccurs="0" maxOccurs=="unbounded"/>

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="valSpecificConfigType">

<xs:sequence>

<xs:element name="group-priority" type="sealgi:priorityType" minOccurs="0"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:simpleType name="subjectType">

<xs:restriction base="xs:string">

<xs:minLength value="0"/>

<xs:maxLength value="255"/>

</xs:restriction>

</xs:simpleType>

<xs:simpleType name="groupCategoryType">

<xs:restriction base="xs:string">

<xs:enumeration value="normal"/>

<xs:enumeration value="location-based"/>

<xs:enumeration value="regroup"/>

</xs:restriction>

</xs:simpleType>

<xs:simpleType name="priorityType">

<xs:restriction base="xs:unsignedShort">

<xs:minInclusive value="0"/>

<xs:maxInclusive value="255"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="serviceNameType">

<xs:sequence>

<xs:element name="serviceType" minOccurs="0" maxOccurs="unbounded" type="Services"/>

</xs:sequence>

<xs:unique name="uniqueserviceType">

<xs:selector xpath="serviceType"/>

<xs:field xpath="."/>

</xs:unique>

</xs:complexType>

<xs:simpleType name="Services">

<xs:restriction base="xs:string">

<xs:enumeration value="V2X"/>

<xs:enumeration value="Others"/>

</xs:restriction>

</xs:simpleType>

</xs:schema>

7.5 Semantics

The <display-name> element of <list-service> element contains a human readable name of the VAL group.

The value of the "uri" attribute in the <list-service> element shall represent a VAL group identity.

The <administrators> element of a <list-service> element shall contain the group members who are administrator of the group and have special authorities as defined by VAL service to manage the group. The administrator user do not require explicit registration to join the group.

The <explicit-member-list> element of a <list-service> element shall contain the group members who are not administrator of the group and require explicit registration to join the group.

The <list> element of a <list-service> element shall contain the group members who are not administrator of the group and also do not require explicit registration to join the group.

The <seal-subject> child element of a <common> element of a <list-service> element shall indicate the title or description for the Group. The length of the value of the <seal-subject> element should not exceed 255 characters.

The <category> child element of a <common> element of a <list-service> element shall indicate the category of the group. The possible values for this element are "normal", "location-based" and "regroup".

The <val-service-id> child element of a <common> element of a <list-service> element shall indicate the service supported by the group.

The <geo-id> child element of a <common> element of a <list-service> element shall indicate geographical area addressed by the group.

The <group-priority> child element of a <val-specific-config> element of a <list-service> element contains a positive number which provides VAL group priority among different VAL groups within VAL service. More than one VAL group can have same priority.

The <external-group-id> child element of a <val-specific-config> element of a <list-service> element identifies the member UEs of the VAL group at the 3GPP core network

The VAL service may further extend the <val-specific-config> element of a <list-service> element to include VAL service specific configuration.

7.6 MIME type

The MIME type for VAL user profile configuration shall be set to "vnd.3gpp.seal-group-doc+xml".

7.7 IANA registration template

Your Name:

Your Email Address:

Media Type Name:

Application

Subtype name:

vnd.3gpp.seal-group-doc+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 2616 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.544 "Group Management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.

Applications Usage:

Applications supporting the SEAL group management procedures 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):
Parameters for different operations