5.5.3 Default SDP message and other information elements

36.579-13GPPMission Critical (MC) services over LTEPart 1: Common test environmentRelease 15TS

5.5.3.1 SDP Message

5.5.3.1.0 Common conditions for SDP Message

The following conditions apply throughout clause 5.5.3.1:

Table 5.5.3.1.0-1: Conditions

Condition

Explanation

INITIAL_SDP_OFFER

SDP message is an initial offer

SDP_OFFER

SDP message is an offer;

INITIAL_SDP_OFFER implies SDP_OFFER, i.e. when a test case or test procedure specifies INITIAL_SDP_OFFER then SDP_OFFER shall be applied too, even when not explicitly specified.

SDP_ANSWER

SDP message is an Answer

FIRST_SDP_FROM_UE

First SDP message sent by the UE within the session;

FIRST_SDP_FROM_UE shall be applied implicitly for an SDP message sent by the UE when the SDP message is the first SDP message sent by the UE for a session.

⇒ In general FIRST_SDP_FROM_UE does not need to be specified for a specific message content.

FIRST_SDP_FROM_SS

First SDP message sent by the SS within the session;

FIRST_SDP_FROM_SS shall be applied implicitly for an SDP message sent by the SS when the SDP message is the first SDP message sent by the UE for a session.

⇒ In general FIRST_SDP_FROM_SS does not need to be specified for a specific message content; nevertheless FIRST_SDP_FROM_SS may be specified for a specific message content when the SDP message is for a new session (e.g. when a new dialog replaces a pre-established session)

IMPLICIT_GRANT_REQUESTED

An implicit grant is requested by the user

IMPLICIT_FLOOR_GRANTED

An implicit grant shall be granted by the SS

PRE_ESTABLISHED_SESSION

SDP message during establishment or modification of a pre-established session
NOTE: The condition shall be applied for all SDP messages of preestablished session test cases and it is not explicitly mentioned in specific message content for these test cases

WITHOUT_FLOORCONTROL

SDP message for MCPTT call without floor control:
In general when this condition is applied for an on-demand call the SDP message does not contain a media description for media plane control at all, whereas for call establishment using pre-established session the SDP message still contains a media description for media plane control but without any floor control related fmtp attributes (see TS 24.380 [10] clauses 14.2.6 and 14.3.7).

WITHOUT_TRANSMISSIONCONTROL

SDP message for MCVideo call without transmission control

Editor’s note:

In contrast to MCPTT there is no "mc_no_floor_ctrl" (or similar) fmtp parameter for MCVideo yet.

WITHOUT_SECURITY

In case of private call: SDP message shall not contain any "a=key-mgmt" attribute for end-to-end security

WITH_SECURITY

End-to-end security to be applied independent from other conditions like PRIVATE-CALL, SDP_OFFER (e.g. for first-to-answer call)

SDS_SESSION

SDP message for establishment of an SDS session according to TS 24.282 [87] clause 9.2.4.

5.5.3.1.1 SDP Message from the UE

– MCPTT

Table 5.5.3.1.1-1: SDP Message from the UE for MCPTT

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

Same o=line as in the previous SDP message sent by the UE except that sess-version is

incremented by one

o= line

Origin

o= line

FIRST_SDP_FROM_UE

username

any allowed value

sess-id

any allowed value

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session

sess-version

any allowed value

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

unicast-address

IP address of the UE

IP address assigned at initial registration

Session Name

at least one UTF-8-encoded character, or if no name is given, a single empty space

s= line

Connection Data

not required if included in all media

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

connection-address

IP address of the UE

Bandwidth

b= line

"AS"

any allowed value

TS 26.114 [64] Table K.6

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Session attribute

present only if there is no key-mgmt media attribute in the media description for audio

a= line

attribute = key-mgmt

(NOTE 2)

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A

RFC 4567 [44]

Session attribute

optional (NOTE 3)

a=line

attribute=”ice-lite”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

ice-lite

Media description[1]

Media description for audio

media description

m= line

media = audio

RFC 4867 [59]

media

"audio"

port

any allowed value

The transport port to which the media stream is sent

proto

"RTP/SAVP"

fmt

any allowed value(s)

Indicating RTP payload type numbers

media title

"speech"

i= line

Connection Data

present if session description does not contain a c=line; optional otherwise

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

Bandwidth

b= line

"AS"

any allowed value

TS 26.114 [64] Table K.6

"RS"

any allowed value if present

RFC 3556 [113]

"RR"

any allowed value if present

RFC 3556 [113]

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

same value as format parameter of the "fmtp" attribute

encoding name

"AMR-WB"

clock rate

16000

RFC 4867 [59] clause 8.3

encoding parameter

"1" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

a value given in fmt in the audio media description

format specific parameters

Parameters of WB-AMR codec

NOTE: In addition to the parameters below the UE may provide further parameters

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

RFC 4867 [59] clause 8.2

max-red

"0"

No redundancy will be used

RFC 4867 [59] clause 8.2

media attribute

a= line

attribute =ptime

ptime

any allowed value

packet time

media attribute

a= line

attribute =maxptime

maxptime

any allowed value

maximum packet time

media attribute

optional

a= line

attribute =sendrecv

Indicates send and receive mode being activated

sendrecv

Parameter has no value

media attribute

one or several attribute lines if present

a=line

attribute=ssrc

RFC 5576 [116]

ssrc

ssrc-id

any allowed value but all the same if there is more than one ssrc attribute for audio

attribute

any source attribute according to RFC 5576 [116]
(NOTE 1)

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTP

foundation

any value

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in speech media’s c= line or in the session’s c= line if the speech media does not have a c= line

default candidate

port

same port number as in the m= line for speech

cand-type

"host"

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTCP

foundation

any value

component-id

2

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in speech media’s c= line or in the session’s c= line if the speech media does not have a c= line

default candidate

port

same port number as in the m= line for speech incremented by 1

cand-type

"host"

media attribute

present only if there is no key-mgmt attribute at session level

a= line

attribute = key-mgmt

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A

RFC 4567 [44]

Media description[2]

Media description for media control

NOT WITHOUT_FLOORCONTROL OR PRE_ESTABLISHED_SESSION

media description

m= line

media = application

SDP media-level section for a media-control entity

(NOTE 2)

media

"application"

port

any allowed value

The port for the media-control entity

proto

"udp"

fmt

"MCPTT"

Connection Data

present if session description does not contain a c=line; optional otherwise

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

media attribute

a= line

attribute = fmtp

fmtp

format

"MCPTT"

format specific parameters

SDP_OFFER AND NOT WITHOUT_FLOORCONTROL

mc_queueing

not present

TS 24.380 [10] cl. 12.1.2.3

present

Parameter has no value

pc_MCPTT_FloorRequestQueueing

mc_priority

any allowed value

Any integer value in the range of 1..255

TS 24.380 [10] cl. 12.1.2.3

mc_granted

not present

present

Parameter has no value

TS 24.380 [10] cl. 12.1.2.3

INITIAL_SDP_OFFER

mc_implicit_request

not present

present

Parameter has no value

TS 24.380 [10] cl. 12.1.2.3

IMPLICIT_GRANT_REQUESTED

mc_ssrc

any value if present

TS 24.380 [10] cl. 12.1.2.3

mc_no_floor_ctrl

not present

TS 24.380 [10]
cl. 12.1.2.3

format specific parameters

SDP_ANSWER AND NOT WITHOUT_FLOORCONTROL

mc_queueing

not present

TS 24.380 [10] cl. 12.1.2.3

present

Parameter has no value

pc_MCPTT_FloorRequestQueueing

mc_priority

same value as in the offer

TS 24.380 [10] cl. 12.1.2.3

mc_granted

not present

TS 24.380 [10] cl. 12.1.2.3

mc_implicit_request

not present

TS 24.380 [10] cl. 12.1.2.3

mc_ssrc

not present

TS 24.380 [10] cl. 12.1.2.3

format specific parameters

WITHOUT_FLOORCONTROL

mc_queueing

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_priority

not present

TS 24.380 [10]
cl. 12.1.2.3 and cl. 14.3.3

mc_granted

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_implicit_request

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_ssrc

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_no_floor_ctrl

present

Parameter has no value

TS 24.380 [10]
cl. 12.1.2.3

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for Media Control messages

foundation

any value

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in application media’s c= line or in the session’s c= line if the application media does not have a c= line

default candidate

port

same port number as in the m= line for application

cand-type

"host"

NOTE 1: If "ssrc" media attributes are included, then at least one "ssrc=" line shall contain a "cname" source attribute according to RFC 5576 [116] clause 6.1.

NOTE 2: Even though there is no clarity in core specs it is assumed that a key-mgmt attribute at session level does not affect the media control security, i.e. the key-mgmt attribute is not applicable for the "application" media description for which still the CSK is used as security key. This is in contrast to RFC 4566 [27] clause 5 saying "In general, session-level values are the default for all media unless overridden by an equivalent media-level value."

NOTE 3: If the UE is configured as lite implementation according to RFC 5245 [115], it shall include "a=ice-lite" session-level attribute; nevertheless this is not a test requirement unless specified otherwise in a test case.

– MCVideo

Table 5.5.3.1.1-2: SDP Message from the UE for MCVideo

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

Same o=line as in the previous SDP message sent by the UE except that sess-version is

incremented by one

o= line

Origin

o= line

FIRST_SDP_FROM_UE

username

any allowed value

sess-id

any allowed value

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

any allowed value

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

unicast-address

IP address of the UE

IP address assigned at initial registration

Session Name

at least one UTF-8-encoded character, or if no name is given, a single empty space

s= line

Connection Data

not required if included in all media

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

connection-address

IP address of the UE

Bandwidth

b= line

"AS"

any allowed value

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Session attribute

present only if there is no key-mgmt media attribute in the media descriptions for audio and video

a= line

attribute = key-mgmt

(NOTE 2)

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A

RFC 4567 [44]

Session attribute

optional (NOTE 3)

a=line

attribute=”ice-lite”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

ice-lite

Media description[1]

Media description for audio

media description

m= line

media = audio

RFC 4867 [59]

media

"audio"

port

any allowed value

The transport port to which the media stream is sent

proto

"RTP/SAVP"

fmt

any allowed value(s)

Indicating RTP payload type numbers

media title

"audio component of MCVideo"

i= line

Connection Data

present if session description does not contain a c=line; optional otherwise

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

Bandwidth

b= line

"AS"

any allowed value

"RS"

any allowed value if present

RFC 3556 [113]

"RR"

any allowed value if present

RFC 3556 [113]

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

same value as format parameter of the "fmtp" attribute

encoding name

"AMR-WB"

clock rate

16000

RFC 4867 [59] clause 8.3

encoding parameter

"1" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

a value given in fmt in the audio media description

format specific parameters

Parameters of WB-AMR codec

NOTE: In addition to the parameters below the UE may provide further parameters

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

RFC 4867 [59] clause 8.2

max-red

"0"

No redundancy will be used

RFC 4867 [59] clause 8.2

media attribute

a= line

attribute =ptime

ptime

any allowed value

packet time

media attribute

a= line

attribute =maxptime

maxptime

any allowed value

maximum packet time

media attribute

optional

a= line

attribute =sendrecv

Indicates send and receive mode being activated

sendrecv

Parameter has no value

media attribute

one or several attribute lines if present

a=line

attribute=ssrc

RFC 5576 [116]

ssrc

ssrc-id

any allowed value but all the same if there is more than one ssrc attribute for audio

attribute

any source attribute according to RFC 5576 [116]
(NOTE 1)

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTP

foundation

any value

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in audio media’s c= line or in the session’s c= line if the audio media does not have a c= line

default candidate

port

same port number as in the m= line for audio

cand-type

"host"

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTCP

foundation

any value

component-id

2

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in audio media’s c= line or in the session’s c= line if the audio media does not have a c= line

default candidate

port

same port number as in the m= line for audio incremented by 1

cand-type

"host"

media attribute

present only if there is no key-mgmt attribute at session level

a= line

attribute = key-mgmt

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.281 [86] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A (NOTE 4)

Use condition MCVIDEO

RFC 4567 [44]

Media description[2]

Media description for video

media description

m= line

media = video

SDP media-level section for a media-transmission control entity

media

"video"

port

any allowed value

The port for the media-transmission control entity

proto

"RTP/SAVPF" or "RTP/SAVP"

fmt

any allowed value(s)

media title

"video component of MCVideo"

i= line

Connection Data

present if session description does not contain a c=line; optional otherwise

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

Bandwidth

b= line

"AS"

any allowed value

"RS"

any allowed value if present

RFC 3556 [113]

"RR"

any allowed value if present

RFC 3556 [113]

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

same value as format parameter of the "fmtp" attribute

encoding name

"H264"

clock rate

90000

RFC 4867 [59] clause 8.3

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

a value given in fmt in the audio media description

format specific parameters

Parameters of H264 codec

NOTE: In addition to the parameters below the UE may provide further parameters

RFC 6184 [129]

profile-level-id

any allowed value

packetization-mode

0

SDP_ANSWER

media attribute

present if proto="RTP/AVP" in the m=line

a= line

attribute = tcap

RFC 5939 [128]

TS 26.114 [64] clause 6.2.1a.2

SDP_OFFER

tcap

trpr-cap-num

1

proto-list

RTP/AVPF

media attribute

present if proto="RTP/AVP" in the m=line

a= line

attribute = pcfg

RFC 5939 [128]

TS 26.114 [64] clause 6.2.1a.2

SDP_OFFER

pcfg

config-number

1

pot-cfg-list

t=1

media attribute

one or several attribute lines if present

a=line

attribute=ssrc

RFC 5576 [116]

ssrc

ssrc-id

any allowed value but all the same if there is more than one ssrc attribute for audio

attribute

any source attribute according to RFC 5576 [116]
(NOTE 1)

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTP

foundation

any value

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in video media’s c= line or in the session’s c= line if the video media does not have a c= line

default candidate

port

same port number as in the m= line for video

cand-type

"host"

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTCP

foundation

any value

component-id

2

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in video media’s c= line or in the session’s c= line if the video media does not have a c= line

default candidate

port

same port number as in the m= line for video incremented by 1

cand-type

"host"

media attribute

present only if there is no key-mgmt attribute at session level

a= line

attribute = key-mgmt

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.281 [86] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A (NOTE 4)

Use condition MCVIDEO

RFC 4567 [44]

Media description[3]

Media description for media control

NOT WITHOUT_TRANSMISSIONCONTROL OR PRE_ESTABLISHED_SESSION

media description

m= line

media = application

SDP media-level section for a media-control entity

(NOTE 2)

media

"application"

3GPP TS 24.581 [88] clause 12

port

any allowed value

The port for the media-control entity

proto

"udp"

fmt

"MCVideo"

Connection Data

present if session description does not contain a c=line; optional otherwise

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

media attribute

a= line

attribute = fmtp

fmtp

3GPP TS 24.581 [88] clause 12, clause 14

format

"MCVideo"

format specific parameters

SDP_OFFER AND NOT WITHOUT_TRANSMISSIONCONTROL

mc_queueing

not present

3GPP TS 24.581 [88] clause 12, clause 14

present

Parameter has no value.

pc_MCVideo_TransmissionRequestQueueing

mc_priority

any allowed value if present

Any integer value in the range of 1..255

Shall be present when priority other than the default priority is required

3GPP TS 24.581 [88] clause 12, clause 14

mc_reception_priority

any allowed value if present

Any integer value in the range of 0…255

Shall be present when priority other than the default reception priority is required

3GPP TS 24.581 [88] clause 12, clause 14

mc_granted

not present

present

Parameter has no value

3GPP TS 24.581 [88] clause 12, clause 14

INITIAL_SDP_OFFER

mc_implicit_request

not present

present

Parameter has no value

3GPP TS 24.581 [88] clause 12, clause 14

IMPLICIT_GRANT_REQUESTED

format specific parameters

SDP_ANSWER AND NOT WITHOUT_TRANSMISSIONCONTROL

mc_queueing

not present

3GPP TS 24.581 [88] clause 12, clause 14

present

Parameter has no value

pc_MCVideo_TransmissionRequestQueueing

mc_priority

same value as in the SDP offer if present, not present otherwise

3GPP TS 24.581 [88] clause 12, clause 14

mc_reception_priority

same value as in the SDP offer if present, not present otherwise

3GPP TS 24.581 [88] clause 12, clause 14

mc_granted

not present

3GPP TS 24.581 [88] clause 12, clause 14

mc_implicit_request

not present

3GPP TS 24.581 [88] clause 12, clause 14

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for Transmission Control Messages

foundation

any value

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

any value

connection-address

same IP address as in application media’s c= line or in the session’s c= line if the application media does not have a c= line

default candidate

port

same port number as in the m= line for application

cand-type

"host"

NOTE 1: If "ssrc" media attributes are included, then at least one "ssrc=" line shall contain a "cname" source attribute according to RFC 5576 [116] clause 6.1.

NOTE 2: Even though there is no clarity in core specs it is assumed that a key-mgmt attribute at session level does not affect the media control security, i.e. the key-mgmt attribute is not applicable for the "application" media description for which still the CSK is used as security key. This is in contrast to RFC 4566 [27] clause 5 saying "In general, session-level values are the default for all media unless overridden by an equivalent media-level value."

NOTE 3: If the UE is configured as lite implementation according to RFC 5245 [115], it shall include "a=ice-lite" session-level attribute; nevertheless this is not a test requirement unless specified otherwise in a test case.

NOTE 4: If present the a=key-mgmt attributes for audio and video carry the same keys.

– MCData

Table 5.5.3.1.1-3: SDP Message from the UE for MCData

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

Same o=line as in the previous SDP message sent by the UE except that sess-version is incremented by one

o= line

Origin

o= line

FIRST_SDP_FROM_UE

username

any allowed value

sess-id

any allowed value

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

any allowed value

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

unicast-address

IP address of the UE

IP address assigned at initial registration

Session Name

at least one UTF-8-encoded character, or if no name is given, a single empty space

s= line

Connection Data

not required if included in all media

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Session attribute

present only if there is no key-mgmt media attribute in the media description for audio

a= line

attribute = key-mgmt

SDP_OFFER AND MCD_1to1

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A

RFC 4567 [44]

Media description[1]

Media description for data

media description

m= line

media = message

RFC 4867 [59]

TS 24.282 [31]

media

"message"

port

any allowed value

The transport port to which the media stream is sent

proto

"TCP/MSRP"

fmt

“*”

Connection Data

present if session description does not contain a c=line; optional otherwise

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

connection-address

IP address of the UE

media attribute

a= line

attribute = sendonly

SDP_OFFER AND NOT SDS_SESSION

sendonly

No parameters associated with this line

media attribute

a= line

attribute = recvonly

SDP_ANSWER AND NOT SDS_SESSION

recvonly

No parameters associated with this line

media attribute

a= line

attribute = sendrecv

SDS_SESSION

sendrecv

No parameters associated with this line

media attribute

a= line

attribute = path

path

MSRP URI according to RFC 4975 [120] clause 6 and 9

attribute containing its own MSRP URI.

An example:

msrp://mcdata.example.com:7654/abcde1; tcp

TS 24.282 [31]

scheme

"msrp"

authority

RFC 3986 [123] clause 3.2

userinfo

any value if present

host

any allowed value

domain name or IP address of the UE

port

same value as in the media line if present

port at which the UE may be connected to for MSRP;

mandatory when hostname is an IP address

session id

any allowed value if present

transport

"tcp"

mandatory for MSRP according to RFC 4975 [120] clause 6

URI-parameter

not present

media attribute

a= line

attribute = accept-types

RFC 4975 [120]

accept-types

format-entry[1]

"application/vnd.3gpp.mcdata-signalling"

format-entry[2]

"application/vnd.3gpp.mcdata-payload"

MCDATA_SDS

media attribute

a= line

attribute = setup

RFC 4145 [119]

setup

“actpass”

SDP_OFFER

"active" or "passive"

SDP_ANSWER

media attribute

a= line

attribute = file-transfer-id

RFC 5547 [124]

MCDATA_FD

file-transfer-id

any allowed value

RFC 5547 [124] clause 8.2.1

SDP_OFFER

same value as in the sdp offer

RFC 5547 [124] clause 8.2.2

SDP_ANSWER

media attribute

a= line

attribute = file-selector

RFC 5547 [124]

MCDATA_FD

file-selector

SDP_OFFER

selector[1]

filename

any allowed value

e.g. "TestFile.txt"

filesize

size of the file to be transferred

filetype

any allowed value

e.g. "text/plain"

hash

algorithm

"sha-1"

value

hash value of the file to be transferred

file-selector

same value as in the sdp offer

SDP_ANSWER

media attribute

a= line

attribute = file-date

RFC 5547 [124]

MCDATA_FD AND SDP_OFFER

file-date

date-param

at least one entry with an allowed value

media attribute

present only if there is no key-mgmt attribute at session level

a= line

attribute = key-mgmt

SDP_OFFER AND MCD_1to1

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A

Use condition MCDATA

RFC 4567 [44]

5.5.3.1.2 SDP Message from the SS

– MCPTT

Table 5.5.3.1.2-1: SDP Message from the SS for MCPTT

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

Same o=line as in the previous SDP message sent by the SS except that sess-version is incremented by one

o= line

Origin

o= line

FIRST_SDP_FROM_SS

username

"-"

"-" indicating the concept of user IDs not being supported

sess-id

"11111111"

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

"11111111"

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

This depends on the unicast address of the UE

unicast-address

IP address of the SS

Session Name

" "

s= line

single empty space indicating no session name

Bandwidth

b= line

"AS"

38

TS 26.114 [64] Table K.6

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Session attribute

a=line

attribute=”ice-lite”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

ice-lite

Media description[1]

Media description for audio

media description

m= line

media = audio

RFC 4867 [59]

media

"audio"

port

port number assigned by the SS (even integer)

The transport port to which the media stream is sent

RFC 6335 [63] clause 6

proto

"RTP/SAVP"

fmt

"99"

RTP/SAVP payload type for AMR-WB is dynamic

INITIAL_SDP_OFFER

value for AMR-WB as used in initial offer

media title

"speech"

i= line

Connection Data

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address"

This depends on the connection address

connection-address

IP address of the SS

Bandwidth

b= line

"AS"

38

TS 26.114 [64] Table K.6

"RS"

0

RFC 3556 [113]

"RR"

2000

RFC 3556 [113]

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"99"

INITIAL_SDP_OFFER

value for AMR-WB as used in initial offer

encoding name

"AMR-WB"

clock rate

16000

RFC 4867 [59] clause 8.3

encoding parameter

"1"

Channel number

media attribute

a= line

attribute = fmtp

fmtp

format

"99"

INITIAL_SDP_OFFER

value for AMR-WB as used in initial offer

format specific parameters

Parameters of WB-AMR codec

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

RFC 4867 [59] clause 8.2

max-red

"0"

No redundancy will be used

RFC 4867 [59] clause 8.2

media attribute

a= line

attribute =ptime

ptime

"20"

packet time

media attribute

a= line

attribute =maxptime

maxptime

"240"

maximum packet time

media attribute

a= line

attribute = key-mgmt

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

RFC 4567 [44]

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTP

foundation

1234

arbitrarily selected

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706431

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for speech)

default candidate

port

same port number as in the m= line for speech

cand-type

"host"

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTCP

foundation

1234

same as for RTP

component-id

2

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706430

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for speech)

default candidate

port

same port number as in the m= line for speech incremented by 1

cand-type

"host"

Media description[2]

Media description for media control

NOT WITHOUT_FLOORCONTROL OR PRE_ESTABLISHED_SESSION

media description

m= line

media = application

SDP media-level section for a media control entity

media

"application"

port

port number assigned by the SS being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)"

The port for the media control entity

proto

"udp"

fmt

"MCPTT"

Connection Data

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

This depends on the connection address

connection-address

IP address of the SS

media attribute

a= line

attribute = fmtp

fmtp

format

"MCPTT"

format specific parameters

SDP_OFFER AND NOT WITHOUT_FLOORCONTROL

mc_queueing

Present

Parameter has no value

TS 24.380 [10]
cl. 12.1.2.3

mc_priority

"3"

"3" is the value of the <user-priority> element for user A in the MCPTT Group Configuration (Table 5.5.7.1-1)

TS 24.380 [10]
cl. 12.1.2.3 and cl. 14.3.3

mc_granted

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_implicit_request

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_ssrc

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_no_floor_ctrl

not present

TS 24.380 [10]
cl. 12.1.2.3

format specific parameters

SDP_ANSWER AND NOT WITHOUT_FLOORCONTROL

mc_queueing

present if included in the offer

Parameter has no value

TS 24.380 [10]
cl. 12.1.2.3

mc_priority

if a value is provided in the offer: "3" or the value provided in the offer, whichever is the lower value;

otherwise not present

"3" is the value of the <user-priority> element for user A in the MCPTT Group Configuration (Table 5.5.7.1-1)

NOTE: <num-levels-priority-hierarchy> has a value of 10 for on-network i.e. it is greater than 3

TS 24.380 [10]
cl. 12.1.2.3 and cl. 14.3.3

mc_granted

not present

TS 24.380 [10]
cl. 12.1.2.3

present

Parameter has no value

TS 24.380 [10]
cl. 12.1.2.3

IMPLICIT_FLOOR_GRANTED

mc_implicit_request

not present

TS 24.380 [10]
cl. 12.1.2.3

present

Parameter has no value

TS 24.380 [10]
cl. 12.1.2.3

IMPLICIT_GRANT_REQUESTED

mc_ssrc

not present

TS 24.380 [10]
cl. 12.1.2.3

same value as in the offer if provided in the offer and there is no collision with the value used by the SS;

otherwise value assigned by the SS

TS 24.380 [10]
cl. 12.1.2.3

IMPLICIT_GRANT_REQUESTED

mc_no_floor_ctrl

not present

TS 24.380 [10]
cl. 12.1.2.3

format specific parameters

WITHOUT_FLOORCONTROL

mc_queueing

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_priority

not present

TS 24.380 [10]
cl. 12.1.2.3 and cl. 14.3.3

mc_granted

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_implicit_request

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_ssrc

not present

TS 24.380 [10]
cl. 12.1.2.3

mc_no_floor_ctrl

present

Parameter has no value

TS 24.380 [10]
cl. 12.1.2.3

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for Media Control messages

foundation

4321

arbitrarily selected; different than for RTP/RTCP

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706431

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for media control)

default candidate

port

same port number as in the m= line for application

cand-type

"host"

– MCVideo

Table 5.5.3.1.2-2: SDP Message from the SS for MCVideo

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

Same o=line as in the previous SDP message sent by the SS except that sess-version is incremented by one

o= line

Origin

o= line

FIRST_SDP_FROM_SS

username

"-"

"-" indicating the concept of user IDs not being supported

sess-id

"11111111"

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

"11111111"

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

This depends on the unicast address of the UE

unicast-address

IP address of the SS

Session Name

" "

s= line

single empty space indicating no session name

Bandwidth

b= line

"AS"

352

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Session attribute

a=line

attribute=”ice-lite”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

ice-lite

Media description[1]

Media description for audio

media description

m= line

media = audio

RFC 4867 [59]

media

"audio"

port

port number assigned by the SS (even integer)

The transport port to which the media stream is sent

RFC 6335 [63] clause 6

proto

"RTP/SAVP"

fmt

"99"

RTP/SAVP payload type for AMR-WB is dynamic

INITIAL_SDP_OFFER

value for AMR-WB as used in initial offer

media title

"audio component of MCVideo"

i= line

Connection Data

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

This depends on the connection address

connection-address

IP address of the SS

Bandwidth

b= line

"AS"

37

"RS"

0

RFC 3556 [113]

"RR"

2000

RFC 3556 [113]

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"99"

INITIAL_SDP_OFFER

value for AMR-WB as used in initial offer

encoding name

"AMR-WB"

clock rate

16000

RFC 4867 [59] clause 8.3

encoding parameter

"1"

Channel number

media attribute

a= line

attribute = fmtp

fmtp

format

"99"

INITIAL_SDP_OFFER

value for AMR-WB as used in initial offer

format specific parameters

Parameters of WB-AMR codec

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

RFC 4867 [59] clause 8.2

max-red

"0"

No redundancy will be used

RFC 4867 [59] clause 8.2

media attribute

a= line

attribute =ptime

ptime

"20"

packet time

media attribute

a= line

attribute =maxptime

maxptime

"240"

maximum packet time

media attribute

a= line

attribute = key-mgmt

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.281 [86] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

Use condition MCVIDEO

RFC 4567 [44]

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTP

foundation

1234

arbitrarily selected

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706431

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for audio)

default candidate

port

same port number as in the m= line for audio

cand-type

"host"

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTCP

foundation

1234

same as for RTP

component-id

2

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706430

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for audio)

default candidate

port

same port number as in the m= line for audio incremented by 1

cand-type

"host"

Media description[2]

Media description for video

media description

m= line

media = video

SDP media-level section for a media-transmission control entity

media

"video"

port

port number of the audio stream incremented by 2 (resulting in even integer)

The port for the media-transmission control entity

proto

"RTP/SAVPF"

fmt

"100"

INITIAL_SDP_OFFER

value for H264 as used in initial offer

media title

"video component of MCVideo"

i= line

Connection Data

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

connection-address

IP address of the SS

Bandwidth

b= line

"AS"

315

"RS"

0

RFC 3556 [113]

"RR"

2500

RFC 3556 [113]

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"100"

INITIAL_SDP_OFFER

value for H264 as used in initial offer

encoding name

"H264"

clock rate

90000

RFC 6184 [129]

media attribute

a= line

attribute = fmtp

fmtp

format

"100"

INITIAL_SDP_OFFER

value for H264 as used in initial offer

format specific parameters

Parameters the H264 codec

RFC 6184 [129]

SDP_OFFER

packetization-mode

"0"

profile-level-id

"42e00c"

sprop-parameter-sets

"J0LgDJWgUH6Af1A=,KM46gA=="

format specific parameters

same parameters and values as sent by the UE in the corresponding SDP offer

Parameters the H264 codec

SDP_ANSWER

media attribute

a= line

attribute = rtcp-fb

RFC 4585 [130]

SDP_OFFER

rtcp-fb

rtcp-fb-pt

"*"

rtcp-fb-val

"trr-int 5000"

media attribute

a= line

attribute = rtcp-fb

RFC 4585 [130]

SDP_OFFER

rtcp-fb

rtcp-fb-pt

"*"

rtcp-fb-val

"nack"

media attribute

a= line

attribute = rtcp-fb

RFC 4585 [130]

SDP_OFFER

rtcp-fb

rtcp-fb-pt

"*"

rtcp-fb-val

"nack pli"

media attribute

a= line

attribute = rtcp-fb

RFC 4585 [130]

SDP_OFFER

rtcp-fb

rtcp-fb-pt

"*"

rtcp-fb-val

"ccm fir"

media attribute

a= line

attribute = rtcp-fb

RFC 4585 [130]

SDP_OFFER

rtcp-fb

rtcp-fb-pt

"*"

rtcp-fb-val

"ccm tmmbr"

media attribute

present if there have been a=tcap and a=pcfg attributes in the corresponding SDP offer

a= line

attribute = acfg

RFC 5939 [128]

TS 26.114 [64] clause 6.2.1a.3

SDP_ANSWER

acfg

config-number

1

sel-cfg-list

"t=1"

media attribute

a= line

attribute = key-mgmt

WITH_SECURITY OR (PRIVATE-CALL AND SDP_OFFER AND NOT WITHOUT_SECURITY)

key-mgmt

TS 24.281 [86] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

Use condition MCVIDEO

RFC 4567 [44]

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTP

foundation

2345

arbitrarily selected; different than audio

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706431

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for video)

default candidate

port

same port number as in the m= line for video

cand-type

"host"

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for RTCP

foundation

22345

same as for RTP

component-id

2

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706430

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for video)

default candidate

port

same port number as in the m= line for video incremented by 1

Media description[3]

Media description for media control

NOT WITHOUT_TRANSMISSIONCONTROL OR PRE_ESTABLISHED_SESSION

media description

m= line

media = application

SDP media-level section for a media control entity

media

"application"

port

port number assigned by the SS being different than the port number of the audio and video channels (RTP) and their associated control channels (RTCP)"

The port for the media control entity

proto

"udp"

fmt

"MCVideo"

Connection Data

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

This depends on the connection address

connection-address

IP address of the SS

media attribute

a= line

attribute = fmtp

fmtp

format

"MCVideo"

format specific parameters

SDP_OFFER AND NOT WITHOUT_TRANSMISSIONCONTROL

mc_queueing

Present

Parameter has no value

3GPP TS 24.581 [88] clause 12, clause 14

mc_priority

"5"

Any integer value in the range of 1..255

3GPP TS 24.581 [88] clause 12, clause 14

mc_granted

not present

3GPP TS 24.581 [88] clause 12, clause 14

mc_implicit_request

not present

3GPP TS 24.581 [88] clause 12, clause 14

mc_reception_priority

not present

3GPP TS 24.581 [88] clause 12, clause 14

format specific parameters

SDP_ANSWER AND NOT WITHOUT_TRANSMISSIONCONTROL

mc_queueing

present if included in the offer

Parameter has no value

3GPP TS 24.581 [88] clause 12, clause 14

mc_priority

if a value is provided in the offer: "3" or the value provided in the offer, whichever is the lower value;

otherwise not present

"3" is the value of the <user-priority> element for user A in the MCVideo Group Configuration (Table 5.5.7.2-1)

3GPP TS 24.581 [88] clause 12, clause 14

mc_granted

not present

present

Parameter has no value

3GPP TS 24.581 [88] clause 12, clause 14

IMPLICIT_FLOOR_GRANTED

mc_implicit_request

not present

present

Parameter has no value

3GPP TS 24.581 [88] clause 12, clause 14

IMPLICIT_GRANT_REQUESTED

mc_reception_priority

same value as in the SDP offer if present, not present otherwise

3GPP TS 24.581 [88] clause 12, clause 14

media attribute

a=line

attribute=”candidate”

RFC 5245 [115]

PRE_ESTABLISHED_SESSION

candidate

candidate for Media Control messages

foundation

4321

arbitrarily selected; different than for RTP/RTCP (audio, video)

component-id

1

according to RFC 5245 [115] clause 4.1.1.1

transport

"UDP"

priority

2130706431

RFC 5245 [115] clause 4.2:

224 * 126 +
28 * 65535 +
256 – component id

connection-address

IP address of the SS (same IP address as in the c=line for media control)

default candidate

port

same port number as in the m= line for application

cand-type

"host"

– MCData

Table 5.5.3.1.2-3: SDP Message from the SS for MCData

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

Same o=line as in the previous SDP message sent by the SS except that sess-version is

incremented by one

o= line

Origin

o= line

FIRST_SDP_FROM_SS

username

"-"

"-" indicating the concept of user IDs not being supported

sess-id

"11111111"

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

"11111111"

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

unicast-address

IP address of the SS

Session Name

" "

s= line

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Media description[1]

Media description for data

media description

m= line

media = message

RFC 4867 [59]

TS 24.282 [31]

media

"message"

port

port number assigned by the SS

The transport port to which the media stream is sent

proto

"TCP/MSRP"

fmt

“*”

Connection Data

c= line

nettype

"IN"

Addrtype

"IP4" or "IP6" depending on IP address

connection-address

IP address of the SS

media attribute

a= line

attribute = sendonly

SDP_OFFER AND NOT SDS_SESSION

sendonly

No parameters associated with this line

media attribute

a= line

attribute = recvonly

SDP_ANSWER AND NOT SDS_SESSION

recvonly

No parameters associated with this line

media attribute

a= line

attribute = sendrecv

SDS_SESSION

sendrecv

No parameters associated with this line

media attribute

a= line

attribute = path

path

MSRP URI according to RFC 4975 [120] clause 6 and 9

TS 24.282 [31]

scheme

"msrp"

authority

RFC 3986 [123] clause 3.2

userinfo

not present

host

IP address of the SS

port

same value as in the media line

session id

assigned by the SS

transport

"tcp"

URI-parameter

not present

media attribute

a= line

attribute = accept-types

RFC 4975 [120]

accept-types

format-entry[1]

"application/vnd.3gpp.mcdata-signalling"

format-entry[2]

"application/vnd.3gpp.mcdata-payload"

MCDATA_SDS

media attribute

a= line

attribute = setup

RFC 4145 [119]

setup

“actpass”

SDP_OFFER

"passive"

SDP_ANSWER

media attribute

a= line

attribute = file-transfer-id

RFC 5547 [124]

MCDATA_FD

file-transfer-id

value assigned by the SS

randomly chosen globally unique identification (RFC 5547 [124])

SDP_OFFER

same value as in the sdp offer

SDP_ANSWER

media attribute

a= line

attribute = file-selector

RFC 5547 [124]

MCDATA_FD

file-selector

SDP_OFFER

selector[1]

filename

name of the file to be transferred

e.g. "TestFile.txt"

filesize

size of the file to be transferred

filetype

type of the file to be transferred

e.g. "text/plain"

hash

algorithm

"sha-1"

value

hash value of the file to be transferred

file-selector

same value as in the sdp offer

SDP_ANSWER

media attribute

a= line

attribute = file-date

RFC 5547 [124]

MCDATA_FD AND SDP_OFFER

file-date

date-param[1]

type

"creation"

date-time

date and time when the file has been created

e.g. "Mon, 20 Dec 2021 15:01:31 +0100"

RFC 5322 [109]

media attribute

a= line

attribute = key-mgmt

SDP_OFFER AND MCD_1to1

key-mgmt

TS 24.379 [9] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

Use condition MCDATA

RFC 4567 [44]

5.5.3.1.3 SDP Message from the UE Off-network

– MCPTT

Table 5.5.3.1.3-1: SDP Message from the UE – Off-network for MCPTT

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

o= line

username

"-"

sess-id

any allowed value

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

any allowed value

nettype

"IN"

addrtype

"IP4"

"IP4" or "IP6"

unicast-address

px_MCPTT_IP_ConnectionAddressAll

Session Name

"-"

s= line

Connection Data

c= line

nettype

"IN"

addrtype

"IP4"

"IP4" or "IP6"

connection-address

px_MCPTT_IP_ConnectionAddressAll

Set to the multicast IP address of the MCPTT group

Bandwidth

b= line

bwtype

"AS:"

bwtype:bandwidth

bandwidth

any allowed value

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Media descriptions

media description

m= line

media = audio

media

"audio"

port

any allowed value

Set to a port number for MCPTT speech of the MCPTT group

proto

"RTP/AVP"

fmt

any allowed value(s)

Indicating RTP payload type numbers

media title

"speech"

i= line

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"99"

encoding name

"AMR-WB"

clock rate

16000

encoding parameter

"1" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

the value given in fmt in the audio media description

format specific parameters

Parameters of WB-AMR codec

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

max-red

"0"

No redundancy will be used

media attribute

a= line

attribute =ptime

ptime

any allowed value

packet time

media attribute

a= line

attribute =maxptime

maxptime

any allowed value

maximum packet time

media description

m= line

media = application

media

"application"

port

any allowed value

Set to a port number for media-floor control entity of the MCPTT group

proto

"udp"

fmt

"MCPTT"

media attribute

a= line

attribute = fmtp

fmtp

format

"MCPTT"

format specific parameters

mc_queueing

optional

Parameter has no value

mc_priority

not present

or

any allowed value

Any integer value in the range of 1..255

mc_granted

present

Parameter has no value

mc_implicit_request

present

Parameter has no value

media attribute

a= line

attribute = key-mgmt

key-mgmt

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

– MCVideo

Table 5.5.3.1.3-2: SDP Message from the UE – Off-network for MCVideo

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

o= line

username

"-"

sess-id

any allowed value

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

any allowed value

nettype

"IN"

addrtype

"IP4"

"IP4" or "IP6"

unicast-address

px_MCVideo_IP_ConnectionAddressAll

Session Name

"-"

s= line

Connection Data

c= line

nettype

"IN"

addrtype

"IP4"

"IP4" or "IP6"

connection-address

px_MCVideo_IP_ConnectionAddressAll

Set to the multicast IP address of the MCVideo group

Bandwidth

b= line

bwtype

"AS:"

bwtype:bandwidth

bandwidth

any allowed value

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Media descriptions

media description

m= line

media = audio

media

"audio"

port

any allowed value

Set to a port number for MCVideo speech of the MCVideo group

proto

"RTP/AVP"

fmt

any allowed value(s)

Indicating RTP payload type numbers

media title

"speech"

i= line

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"99"

encoding name

"AMR-WB"

clock rate

16000

encoding parameter

"1" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

the value given in fmt in the audio media description

format specific parameters

Parameters of WB-AMR codec

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

max-red

"0"

No redundancy will be used

media attribute

a= line

attribute =ptime

ptime

any allowed value

packet time

media attribute

a= line

attribute =maxptime

maxptime

any allowed value

maximum packet time

media description

m= line

media = video

SDP media-level section for a media-transmission control entity

media

"video"

port

any allowed value

The port for the media-transmission control entity

proto

"udp"

User Datagram Protocol. With UDP, computer applications can send messages to other hosts on an Internet Protocol (IP) network. Time-sensitive applications often use UDP because dropping packets is preferable to waiting for packets delayed due to retransmission, which may not be an option in a real-time system.

fmt

"MCVideo"

Connection Data

c= line

Included if the media plane control channel uses a different IP address than other media described in the SDP

nettype

"IN"

addrtype

"IP4"

connection-address

px_MCVideo_IP_ConnectionAddressApp

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

""

encoding name

"H.264"

clock rate

RFC 4867 [59] clause 8.3

encoding parameter

"" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

3GPP TS 24.581 [88] clause 12, clause 14

format

"MCVideo"

format specific parameters

mc_queueing

optional

Parameter has no value.

Shall include the "mc_queueing" fmtp attribute in SDP offers when queueing of Transmission request is supported.

3GPP TS 24.581 [88] clause 12, clause 14

mc_priority

not present

or

any allowed value

Any integer value in the range of 1..255

Shall include the "mc_priority" fmtp attribute when a transmission priority different than the default priority is required.

3GPP TS 24.581 [88] clause 12, clause 14

mc_reception_priority

not present

or

any allowed value

Any integer value in the range of 0…255

Shall include the "mc_reception_priority" fmtp attribute when a reception priority different than the default reception priority is required.

3GPP TS 24.581 [88] clause 12, clause 14

mc_granted

present

Parameter has no value

Shall include the "mc_granted" fmtp attribute in the SDP offer of an initial SIP INVITE request when it is acceptable for the MCVideo client to receive a granted indication in the SIP 200 (OK) response to an initial INVITE request.

3GPP TS 24.581 [88] clause 12, clause 14

mc_implicit_request

present

Parameter has no value

Shall include the "mc_implicit_request" fmtp attribute when a SIP request shall be interpreted as an implicit Transmission request. If not explicitly stated in procedures in the present document or in procedures in 3GPP TS 24.281 [2] that the "mc_implicit_request" fmtp attribute shall be included, the decision to include the "mc_implicit_request" fmtp attribute or not, is an implementation option.

3GPP TS 24.581 [88] clause 12, clause 14

media attribute

a= line

attribute = key-mgmt

PRIVATE-CALL

key-mgmt

Key Management attribute field in the media and session level.

TS 24.281 [86] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 6.1.1.1.3.3-3

MIKEY carries the security parameters needed for

setting up the security protocol. It is a protocol designed for government and relevant enterprises to enable secure, cross-platform multimedia communications.

RFC 4567 [44]

media description

m= line

media = application

media

"application"

port

any allowed value

Set to a port number for media-floor control entity of the MCVideo group

proto

"udp"

fmt

"MCVideo"

media attribute

a= line

attribute = fmtp

fmtp

format

"MCVideo"

format specific parameters

mc_queueing

optional

Parameter has no value

mc_priority

not present

or

any allowed value

Any integer value in the range of 1..255

mc_granted

present

Parameter has no value

mc_implicit_request

present

Parameter has no value

media attribute

a= line

attribute = key-mgmt

key-mgmt

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2A

– MCData

Table 5.5.3.1.3-3: SDP Message from the UE – Off-network for MCData

FFS

5.5.3.1.4 SDP Message from the SS Off-network

– MCPTT

Table 5.5.3.1.4-1: SDP Message from the SS – Off-network for MCPTT

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

o= line

username

"-"

sess-id

"12345678"

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

"12345678"

nettype

"IN"

addrtype

"IP4"

unicast-address

px_MCPTT_IP_ConnectionAddressAll

Session Name

"-"

s= line

Connection Data

c= line

nettype

"IN"

addrtype

"IP4"

"IP4" or "IP6"

connection-address

px_MCPTT_IP_ConnectionAddressAll

Set to the multicast IP address of the MCPTT group

Bandwidth

b= line

bwtype

"AS:"

bwtype:bandwidth

bandwidth

any allowed value

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Media descriptions

media description

m= line

media = audio

media

"audio"

port

"49152"

Set to a port number for MCPTT speech of the MCPTT group

proto

"RTP/AVP"

fmt

"99"

Indicating RTP payload type numbers

media title

"speech"

i= line

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"99"

encoding name

"AMR-WB"

clock rate

16000

encoding parameter

"1" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

"99"

format specific parameters

Parameters of WB-AMR codec

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

max-red

"0"

No redundancy will be used

media attribute

a= line

attribute =ptime

ptime

"20"

packet time

media attribute

a= line

attribute =maxptime

maxptime

"240"

maximum packet time

media description

m= line

media = application

media

"application"

port

"49153"

Set to a port number for media-floor control entity of the MCPTT group

proto

"udp"

fmt

"MCPTT"

media attribute

a= line

attribute = fmtp

fmtp

format

"MCPTT"

format specific parameters

mc_queueing

Present

Parameter has no value

mc_priority

"5"

Any integer value in the range of 1..255

mc_granted

Present

Parameter has no value

mc_implicit_request

Present

Parameter has no value

media attribute

a= line

attribute = key-mgmt

key-mgmt

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

– MCVideo

Table 5.5.3.1.4-2: SDP Message from the SS – Off-network for MCVideo

Derivation Path: RFC 4566 [27]

Information Element

Value/remark

Comment

Reference

Condition

Session description:

Protocol Version

"0"

v= line

Origin

o= line

username

"-"

sess-id

"12345678"

A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session.

sess-version

"12345678"

nettype

"IN"

addrtype

"IP4"

unicast-address

px_MCVideo_IP_ConnectionAddressAll

Session Name

"-"

s= line

Connection Data

c= line

nettype

"IN"

addrtype

"IP4"

"IP4" or "IP6"

connection-address

px_MCVideo_IP_ConnectionAddressAll

Set to the multicast IP address of the MCVideo group

Bandwidth

b= line

bwtype

"AS:"

bwtype:bandwidth

bandwidth

any allowed value

Time description

Timing

t= line

start-time

"0"

stop-time

"0"

Media descriptions

media description

m= line

media = audio

media

"audio"

port

"49152"

Set to a port number for MCVideo speech of the MCVideo group

proto

"RTP/AVP"

fmt

"99"

Indicating RTP payload type numbers

media title

"speech"

i= line

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

"99"

encoding name

"AMR-WB"

clock rate

16000

encoding parameter

"1" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

"fmtp"

format

"99"

format specific parameters

Parameters of WB-AMR codec

mode-change-capability

"2"

To be able to interoperate fully with gateways to circuit switched networks

max-red

"0"

No redundancy will be used

media attribute

a= line

attribute =ptime

ptime

"20"

packet time

media attribute

a= line

attribute =maxptime

maxptime

"240"

maximum packet time

media description

m= line

media = video

SDP media-level section for a media-transmission control entity

media

"video"

port

any allowed value

The port for the media-transmission control entity

proto

"udp"

User Datagram Protocol. With UDP, computer applications can send messages to other hosts on an Internet Protocol (IP) network. Time-sensitive applications often use UDP because dropping packets is preferable to waiting for packets delayed due to retransmission, which may not be an option in a real-time system.

fmt

"MCVideo"

Connection Data

c= line

Included if the media plane control channel uses a different IP address than other media described in the SDP

nettype

"IN"

addrtype

"IP4"

connection-address

px_MCVideo_IP_ConnectionAddressApp

media attribute

a= line

attribute = rtpmap

rtpmap

"rtpmap"

payload type

""

encoding name

"H.264"

clock rate

RFC 4867 [59] clause 8.3

encoding parameter

"" if present

Channel number

media attribute

a= line

attribute = fmtp

fmtp

3GPP TS 24.581 [88] clause 12, clause 14

format

"MCVideo"

format specific parameters

mc_queueing

optional

Parameter has no value.

Shall include the "mc_queueing" fmtp attribute in SDP offers when queueing of Transmission request is supported.

3GPP TS 24.581 [88] clause 12, clause 14

mc_priority

not present

or

any allowed value

Any integer value in the range of 1..255

Shall include the "mc_priority" fmtp attribute when a transmission priority different than the default priority is required.

3GPP TS 24.581 [88] clause 12, clause 14

mc_reception_priority

not present

or

any allowed value

Any integer value in the range of 0…255

Shall include the "mc_reception_priority" fmtp attribute when a reception priority different than the default reception priority is required.

3GPP TS 24.581 [88] clause 12, clause 14

mc_granted

present

Parameter has no value

Shall include the "mc_granted" fmtp attribute in the SDP offer of an initial SIP INVITE request when it is acceptable for the MCVideo client to receive a granted indication in the SIP 200 (OK) response to an initial INVITE request.

3GPP TS 24.581 [88] clause 12, clause 14

mc_implicit_request

present

Parameter has no value

Shall include the "mc_implicit_request" fmtp attribute when a SIP request shall be interpreted as an implicit Transmission request. If not explicitly stated in procedures in the present document or in procedures in 3GPP TS 24.281 [2] that the "mc_implicit_request" fmtp attribute shall be included, the decision to include the "mc_implicit_request" fmtp attribute or not, is an implementation option.

3GPP TS 24.581 [88] clause 12, clause 14

media attribute

a= line

attribute = key-mgmt

PRIVATE-CALL

key-mgmt

Key Management attribute field in the media and session level.

TS 24.281 [86] clause 6.2.1

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 6.1.1.1.3.3-3

MIKEY carries the security parameters needed for

setting up the security protocol. It is a protocol designed for government and relevant enterprises to enable secure, cross-platform multimedia communications.

RFC 4567 [44]

media description

m= line

media = application

media

"application"

port

"49153"

Set to a port number for media-floor control entity of the MCVideo group

proto

"udp"

fmt

"MCVideo"

media attribute

a= line

attribute = fmtp

fmtp

format

"MCVideo"

format specific parameters

mc_queueing

Present

Parameter has no value

mc_priority

"5"

Any integer value in the range of 1..255

mc_granted

Present

Parameter has no value

mc_implicit_request

Present

Parameter has no value

media attribute

a= line

attribute = key-mgmt

key-mgmt

mikey

MIKEY-SAKKE I_MESSAGE as specified in Table 5.5.9.1-2

– MCData

Table 5.5.3.1.4-3: SDP Message from the SS – Off-network for MCData

FFS

5.5.3.2 MCS Info Lists

5.5.3.2.1 MCS Info Lists from the UE
– MCPTT

Table 5.5.3.2.1-1: MCPTT-Info from the UE

Derivation Path: TS 24.379 [9] clause F.1.2

Information Element

Value/remark

Comment

Reference

Condition

mcpttinfo

mcptt-Params

mcptt-access-token

not present

Encrypted (NOTE 2) <mcptt-access-token> with mcpttString set to access token as assigned to the UE in the Token Response

The access token is opaque to the MCPTT client

TS 33.180 [94], clause B.4

RFC 6749 [77]

CONFIG, GROUPCONFIG

session-type

not present

"prearranged"

GROUP-CALL AND INVITE_REFER

"private"

PRIVATE-CALL AND INVITE_REFER

“chat”

CHAT-GROUP-CALL AND INVITE_REFER

"first-to-answer"

FIRST-TO-ANSWER AND INVITE_REFER

mcptt-request-uri

not present

Encrypted (NOTE 2) <mcptt-request-uri> with mcpttURI set to px_MCPTT_Group_A_ID

The URI of the group

(GROUP-CALL OR CHAT-GROUP-CALL) AND INVITE_REFER

not present or encrypted (NOTE 2) <mcptt-request-uri> with mcpttURI set to px_MCPTT_User_B_ID

The URI of the invited MCPTT Client

PRIVATE-CALL AND INVITE_REFER

encrypted (NOTE 2) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A

POC-SETTINGS-EVENT

mcptt-calling-user-id

not present or encrypted (NOTE 2) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A

not present

CONFIG, GROUPCONFIG, POC-SETTINGS-EVENT

mcptt-called-party-id

not present

not present or encrypted (NOTE 2) <mcptt-called-party-id> with mcpttURI set to px_MCPTT_ID_User_A

INVITE-RSP

mcptt-calling-group-id

not present

required

not present

emergency-ind

not present or encrypted (NOTE 2) <emergency-ind> with mcpttBoolean set to "false"

Encrypted (NOTE 2) <emergency-ind> with mcpttBoolean set to "true"

EMERGENCY-CALL AND INVITE_REFER

alert-ind

not present or encrypted (NOTE 2) <alert-ind> with mcpttBoolean set to "false"

Encrypted (NOTE 2) <alert-ind> with mcpttBoolean set to pc_MCX_EmergencyIndWithAlertInd

EMERGENCY-CALL AND INVITE_REFER

imminentperil-ind

not present or encrypted (NOTE 2) <imminentperil-ind> with mcpttBoolean set to "false"

Encrypted (NOTE 2) < imminentperil -ind> with mcpttBoolean set to "true"

IMMPERIL-CALL AND INVITE_REFER

broadcast-ind

not present or “false”

mc-org

not present

floor-state

not present

associated-group-id

not present

px_MCPTT_Group_A_ID if mcptt-request-uri contains a temporary group identity; otherwise, not present

if the <mcptt-request-uri> element contains a group identity then this element can include an MCPTT group ID associated with the group identity in the <mcptt-request-uri> element. E.g. if the <mcptt-request-uri> element contains a temporary group identity (TGI), then the <associated-group-id> element can contain the constituent MCPTT group ID

TS 24.379 [9] clause F.1.3

GROUP-CALL

originated-by

not present

MKFC-GKTPs

not present

mcptt-client-id

not present

encrypted (NOTE 2) <mcptt-client-id> with mcpttString set to valid UUID URN (NOTE 1)

The UUID URN of the MCPTT Client

RFC 4122 [106]

TS 24.379 [9] clause 4.10

(GROUP-CALL OR CHAT-GROUP-CALL OR EMERGENCY-CALL OR IMMPERIL-CALL) AND INVITE_REFER

not present or encrypted (NOTE 2) <mcptt-client-id> with mcpttString set to valid UUID URN (NOTE 1)

(PRIVATE-CALL OR FIRST-TO-ANSWER) AND INVITE_REFER

not present or encrypted (NOTE 2) <mcptt-client-id> with mcpttString set to valid UUID URN (NOTE 1)

in general mcptt-client-id is not mandatory (e.g. for SIP SUBSCRIBE)

RFC 4122 [106]

TS 24.379 [9] clause 4.10

CONFIG, GROUPCONFIG

encrypted (NOTE 2) <mcptt-client-id> with mcpttString set to valid UUID URN (NOTE 1)

mcptt-client-id is mandatory in the SIP REGISTER or SIP PUBLISH for service authorisation according to TS 24.379 [9] clauses 7.2.1 and 7.2.2

RFC 4122 [106]

TS 24.379 [9] clause 4.10

CONFIG AND REGISTER_PUBLISH

encrypted (NOTE 2) <mcptt-client-id> with mcpttString set to valid UUID URN (NOTE 1)

mcptt-client-id is mandatory in SIP PUBLISH for MCPTT service settings only, according to TS 24.379 [9] clause 7.2.3

RFC 4122 [106]

TS 24.379 [9] clause 4.10

POC-SETTINGS-EVENT

alert-ind-rcvd

not present

anyExt

not present or any allowed value

TS 24.379 [9], clause F.1.3

NOTE 1: The SS shall check the mcptt-client-id
– at the first time being sent by the UE to be a valid UUID URN with a format like
"urn:uuid:XXXXXXXX-YYYY-ZZZZ-yyyy-zzzzzzzzzzzz" according to RFC 4122 [106]
– to be all the same UUID URN in subsequent messages.

NOTE 2: Encrypted element as described in Table 5.5.3.2.1-1A

Condition

Explanation

REGISTER_PUBLISH

MCPTT-Info in SIP REGISTER or SIP PUBLISH request for service authorisation

INVITE_REFER

MCPTT-Info in SIP INVITE or SIP REFER request for call establishment

INVITE-RSP

MCPTT-Info in SIP response to a SIP INVITE

NOTE: INVITE-RSP is inherited from the SIP response, i.e. it shall be considered as true whenever set for the SIP response

For further conditions see table 5.5.1-1

Table 5.5.3.2.1-1A: Encrypted MCPTT info parameter sent by the UE

Derivation Path: TS 24.379 [9] clauses F.1.2, F.1.3

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the mcptt parameter

– MCVideo

Table 5.5.3.2.1-2: MCVideo-Info from the UE

Derivation Path: TS 24.281 [86] Clause F.1.2

Information Element

Value/remark

Comment

Reference

Condition

mcvideoinfo

mcvideo-Params

mcvideo-access-token

not present

Encrypted (NOTE 2) <mcvideo-access-token> with mcvideoString set to access token as assigned to the UE in the Token Response

The access token is opaque to the MCVideo client

TS 33.180 [94], clause B.4

RFC 6749 [77]

CONFIG

GROUPCONFIG

session-type

not present

"prearranged"

GROUP-CALL AND INVITE_REFER

"private"

PRIVATE-CALL AND INVITE_REFER

“chat”

CHAT-GROUP-CALL AND INVITE_REFER

mcvideo-request-uri

not present

Encrypted (NOTE 2) <mcvideo-request-uri> with mcvideoURI set to px_MCVideo_Group_A_ID

The URI of the group

(GROUP-CALL OR CHAT-GROUP-CALL) AND INVITE_REFER

not present or Encrypted (NOTE 2) <mcvideo-request-uri> with mcvideoURI set to px_MCVideo_User_B_ID

The URI of the invited MCVideo Client

PRIVATE-CALL AND INVITE_REFER

Encrypted (NOTE 2) <mcvideo-request-uri> with mcvideoURI set to px_MCVideo_User_A_ID

POC-SETTINGS-EVENT

mcvideo-calling-user-id

not present or Encrypted (NOTE 2) <mcvideo-request-uri> with mcvideoURI set to px_MCVideo_ID_User_A

not present

CONFIG,

GROUPCONFIG, POC-SETTINGS-EVENT

mcvideo-called-party-id

not present

not present or Encrypted (NOTE 2) <mcvideo-request-uri> with mcvideoURI set to px_MCVideo_ID_User_A

INVITE-RSP

mcvideo-calling-group-id

not present

required

not present

emergency-ind

not present or encrypted (NOTE 2) <emergency-ind> with mcvideoBoolean set to "false"

encrypted (NOTE 2) <emergency-ind> with mcvideoBoolean set to true

EMERGENCY-CALL AND INVITE-REFER

alert-ind

not present or encrypted (NOTE 2) <alert-ind> with mcvideoBoolean set to "false"

encrypted (NOTE 2) <alert-ind> with mcvideoBoolean set to pc_MCX_EmergencyIndWithAlertInd

EMERGENCY-CALL AND INVITE_REFER

imminentperil-ind

not present or encrypted (NOTE 2) <imminentperil-ind> with mcvideoBoolean set to "false"

encrypted (NOTE 2) <imminentperil-ind> with mcvideoBoolean set to true

IMMPERIL-CALL AND INVITE-REFER

broadcast-ind

not present or “false”

mc-org

not present

associated-group-id

not present

px_MCVideo_Group_A_ID if mcvideo-request-uri contains a temporary group identity; otherwise, not present

if the <mcvideo-request-uri> element contains a group identity then this element can include an MCVideo group ID associated with the group identity in the <mcvideo-request-uri> element. E.g. if the <mcvideo-request-uri> element contains a temporary group identity (TGI), then the <associated-group-id> element can contain the constituent MCVideo group ID

TS 24.281 [86] clause F.1.3

GROUP-CALL

originated-by

not present

MKFC-GKTPs

not present

mcvideo-client-id

not present

encrypted (NOTE 2) < mcvideo-client-id> with mcvideoString set to valid UUID URN (NOTE 1)

The UUID URN of the MCVIDEO Client

RFC 4122 [106]

TS 24.281 [86] clause 4.9

(GROUP-CALL OR CHAT-GROUP-CALL OR

EMERGENCY-CALL OR

IMMPERIL-CALL)

AND INVITE_REFER

not present or encrypted (NOTE 2) < mcvideo-client-id> with mcvideoString set to valid UUID URN (NOTE 1)

PRIVATE-CALL AND INVITE_REFER

not present or encrypted (NOTE 2) < mcvideo-client-id> with mcvideoString set to valid UUID URN (NOTE 1)

in general mcvideo-client-id is not mandatory (e.g. for SIP SUBSCRIBE)

RFC 4122 [106]

TS 24.281 [86] clause 4.9

CONFIG, GROUPCONFIG

encrypted (NOTE 2) < mcvideo-client-id> with mcvideoString set to valid UUID URN (NOTE 1)

mcvideo-client-id is mandatory in the SIP REGISTER or SIP PUBLISH for service authorisation according to TS 24.281 [86] clauses 7.2.1 and 7.2.2

RFC 4122 [106]

TS 24.281 [86] clause 4.9

CONFIG AND REGISTER_PUBLISH

encrypted (NOTE 2) < mcvideo-client-id> with mcvideoString set to valid UUID URN (NOTE 1)

mcvideo-client-id is mandatory in SIP PUBLISH for MCVideo service settings only, according to TS 24.281 [86] clause 7.2.3

RFC 4122 [106]

TS 24.281 [86] clause 4.9

POC-SETTINGS-EVENT

alert-ind-rcvd

not present

anyExt

not present or any allowed value

TS 24.281 [86] clause F.1.3

NOTE 1: The SS shall check the mcvideo-client-id
– at the first time being sent by the UE to be a valid UUID URN with a format like
"urn:uuid:XXXXXXXX-YYYY-ZZZZ-yyyy-zzzzzzzzzzzz" according to RFC 4122 [106]
– to be all the same UUID URN in subsequent messages.

NOTE 2: Encrypted element as described in Table 5.5.3.2.1-2A

Condition

Explanation

REGISTER_PUBLISH

MCVideo-Info in SIP REGISTER or SIP PUBLISH request for service authorisation

INVITE_REFER

MCVideo-Info in SIP INVITE or SIP REFER request for call establishment

INVITE-RSP

MCVideo-Info in SIP response to a SIP INVITE

For further conditions see table 5.5.1-1

Table 5.5.3.2.1-2A: Encrypted MCVideo info parameter sent by the UE

Derivation Path: TS 24.281 [86] clauses F.1.2, F.1.3

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the mcvideo parameter

– MCData

Table 5.5.3.2.1-3: MCData-Info from the UE

Derivation Path: TS 24.282 [87], Clause D.1

Information Element

Value/remark

Comment

Reference

Condition

mcdata-info

mcdata-Params

mcdata-access-token

not present

Encrypted (NOTE 2) <mcdata-access-token> with mcdataString set to access token as assigned to the UE in the Token Response

The access token is opaque to the MCData client

TS 33.180 [94], clause B.4

RFC 6749 [77]

CONFIG

GROUPCONFIG

request-type

not present

"one-to-one-sds"

MCD_1to1

“group-sds”

MCD_grp

mcdata-request-uri

not present

Encrypted (NOTE 1) <mcdata-request-uri> with mcdataURI set to px_MCData_Group_A_ID

MCD_grp

Encrypted (NOTE 1) <mcdata-request-uri> with mcdataURI set to px_MCData_Group_A_ID

POC-SETTINGS-EVENT

mcdata-calling-user-id

not present

mcdata-called-party-id

not present

mcdata-calling-group-id

not present

alert-ind

not present

originated-by

not present

mcdata-client-id

not present

Encrypted (NOTE 1) <mcdata-client-id> with mcdataString set to valid UUID URN (NOTE 1)

MCD_grp

Encrypted (NOTE 1) <mcdata-client-id> with mcdataString set to valid UUID URN (NOTE 1)

CONFIG AND PUBLISH

not present or encrypted (NOTE 1) <mcdata-client-id> with mcdataString set to valid UUID URN (NOTE 1)

in general mcdata-client-id is not mandatory (e.g. for SIP SUBSCRIBE)

(CONFIG OR GROUPCONFIG) AND NOT REGISTER (NOTE 3)

Encrypted (NOTE 1) <mcdata-client-id> with mcdataString set to valid UUID URN (NOTE 1)

mcdata-client-id is mandatory in SIP PUBLISH for MCData service settings only, according to TS 24.282 [87] clause 7.2.3

RFC 4122 [106]

POC-SETTINGS-EVENT

mcdata-controller-psi

not present

NOTE 1: The SS shall check the mcvideo-client-id
– at the first time being sent by the UE to be a valid UUID URN with a format like
"urn:uuid:XXXXXXXX-YYYY-ZZZZ-yyyy-zzzzzzzzzzzz" according to RFC 4122 [106]
– to be all the same UUID URN in subsequent messages.

NOTE 2: Encrypted element as described in Table 5.5.3.2.1-3A

NOTE 3: In contrast to MCPTT and MCVideo for MCData TS 24.282 [87] clause 7.2.1 does not specify the client-id to be included in the REGISTER request.

Condition

Explanation

MCD_1to1

A one-to-one MCData call

MCD_grp

A goup MCData call

REGISTER

MCData-Info in SIP REGISTER request for service authorisation

PUBLISH

MCData-Info in SIP PUBLISH request for service authorisation

For further conditions see table 5.5.1-1

Table 5.5.3.2.1-3A: Encrypted MCData info parameter sent by the UE

Derivation Path: TS 24.282 [87] clauses D.1.2, D.1.3

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the mcdata parameter

5.5.3.2.2 MCS Info Lists from the SS
– MCPTT

Table 5.5.3.2.2-1: MCPTT-Info from the SS

Derivation Path: TS 24.379 [9] clause F.1.2

Information Element

Value/remark

Comment

Reference

Condition

mcpttinfo

mcptt-Params

mcptt-access-token

not present

session-type

not present

"prearranged"

GROUP-CALL

"private"

PRIVATE-CALL

“chat”

CHAT-GROUP-CALL

"first-to-answer"

FIRST-TO-ANSWER

mcptt-request-uri

Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A

The URI of the called user

mcptt-calling-user-id

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B

The URI of the calling user

mcptt-called-party-id

not present

mcptt-calling-group-id

not present

Encrypted (NOTE 1) <mcptt-calling-group-id> with mcpttURI set to px_MCPTT_Group_A_ID

The URI of the group

GROUP-CALL OR CHAT-GROUP-CALL

required

not present

emergency-ind

not present

Encrypted (NOTE 1) <emergency-ind> with mcpttBoolean set to "true"

EMERGENCY-CALL

alert-ind

not present

Encrypted (NOTE 1) <alert-ind> with mcpttBoolean set to "false"

EMERGENCY-CALL

imminentperil-ind

not present

Encrypted (NOTE 1) <imminentperil-ind> with mcpttBoolean set to "true"

IMMPERIL-CALL

broadcast-ind

not present

mc-org

not present

floor-state

not present

associated-group-id

not present

originated-by

not present

MKFC-GKTPs

not present

mcptt-client-id

not present

alert-ind-rcvd

not present

anyExt

not present

TS 24.379 [9], clause F.1.3

NOTE 1: Encrypted element as described in Table 5.5.3.2.2-1A

Table 5.5.3.2.2-1A: Encrypted MCPTT info parameter sent by the SS

Derivation Path: TS 24.379 [9] clauses F.1.2, F.1.3

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-2 containing encrypted element content of the mcptt parameter

– MCVideo

Table 5.5.3.2.2-2: MCVideo-Info from the SS

Derivation Path: TS 24.281 [86] Clause F.1.2

Information Element

Value/remark

Comment

Reference

Condition

mcvideoinfo

mcvideo-Params

mcvideo-access-token

not present

session-type

not present

"prearranged"

GROUP-CALL

"private"

PRIVATE-CALL

"chat"

CHAT-GROUP-CALL

mcvideo-request-uri

Encrypted (NOTE 1) <mcvideo-request-uri> with mcvideoURI set to px_MCVideo_ID_User_A

The URI of the called user

mcvideo-calling-user-id

Encrypted (NOTE 1) <mcvideo-calling-user-id> with mcvideoURI set to px_MCVideo_ID_User_B

The URI of the calling user

mcvideo-called-party-id

not present

mcvideo-calling-group-id

not present

Encrypted (NOTE 1) <mcvideo-calling-group-id> with mcvideoURI set to px_MCVideo_Group_A_ID

The URI of the group

GROUP-CALLOR CHAT-GROUP-CALL

required

not present

emergency-ind

Encrypted (NOTE 1) <emergency-ind> with mcvideoBoolean set to "false"

Encrypted (NOTE 1) <emergency-ind> with mcvideoBoolean set to "true"

EMERGENCY-CALL

alert-ind

not present

Encrypted (NOTE 1) <alert-ind> with mcvideoBoolean set to "false"

EMERGENCY-CALL

imminentperil-ind

not present

Encrypted (NOTE 1) <imminentperil-ind> with mcvideoBoolean set to "true"

IMMPERIL-CALL

broadcast-ind

not present

mc-org"

not present

associated-group-id

not present

originated-by

not present

MKFC-GKTPs

not present

mcvideo-client-id

not present

alert-ind-rcvd

not present

anyExt

not present

TS 24.281 [86] clause F.1.3

NOTE 1: Encrypted element as described in Table 5.5.3.2.2-2A

Table 5.5.3.2.2-2A: Encrypted MCVideo info parameter sent by the SS

Derivation Path: TS 24.281 [86] clauses F.1.2, F.1.3

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-2 containing encrypted element content of the mcvideo parameter

– MCData

Table 5.5.3.2.2-3: MCData-Info from the SS

Derivation Path: TS 24.282 [87], Clause D.1

Information Element

Value/remark

Comment

Reference

Condition

mcdata-info

mcdata-Params

mcdata-access-token

not present

request-type

not present

"one-to-one-sds"

MCD_1to1

“group-sds”

MCD_grp

mcdata-request-uri

Encrypted (NOTE 1) <mcdata-request-uri> with mcdataURI set to px_MCData_ID_User_A

mcdata-calling-user-id

Encrypted (NOTE 1) <mcdata-calling-user-id> with mcdataURI set to px_MCData_ID_User_B

mcdata-called-party-id

not present

mcdata-calling-group-id

not present

Encrypted (NOTE 1) <mcdata-calling-group-id> with mcdataURI set to px_MCData_Group_A_ID

MCD_grp

alert-ind

not present

originated-by

not present

mcdata-client-id

not present

Encrypted (NOTE 1) <mcdata-client-id> with mcdataString set to px_MCX_Client_B_ID

MCD_grp

mcdata-controller-psi

not present

NOTE 1: Encrypted element as described in Table 5.5.3.2.2-3A

Condition

Explanation

MCD_1to1

A one-to-one MCData call

MCD_grp

A group MCData call

For further conditions see table 5.5.1-1

Table 5.5.3.2.2-3A: Encrypted MCData info parameter sent by the SS

Derivation Path: TS 24.282 [87] clauses D.1.2, D.1.3

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.232 containing encrypted element content of the mcdata parameter

5.5.3.3 Resource-lists

5.5.3.3.1 Resource-lists from the UE
– MCPTT

Table 5.5.3.3.1-1: Resource-lists from the UE for MCPTT

Derivation Path: RFC 5366 [35] / RFC 4826 [83]

Information Element

Value/remark

Comment

Reference

Condition

resource-lists

encrypted (NOTE 4)

list[1]

encrypted (NOTE 4)

name attribute

Not present

display-name

Not present

entry[1]

NOTE 4,5

uri attribute

px_MCPTT_ID_User_B

The MCPTT ID of the invited user

px_MCPTT_ID_User_B

the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request

MSG_RSP

SIP-URI with px_MCPTT_Group_A_ID (NOTE 8) extended with SIP URI header fields as specified for the SIP REFER message

SIP-URI:
prearranged MCPTT group identit or
chat group identity extended with header fields

PRE-ESTABLISH AND (GROUP-CALL OR CHAT-GROUP-CALL)

SIP-URI with px_MCPTT_ID_User_B (NOTE 8) extended with SIP URI header fields as specified for the SIP REFER message

SIP-URI:
MCPTT ID of the called user extended with header fields

PRE-ESTABLISH AND (PRIVATE-CALL OR FIRST-TO-ANSWER)

display-name

not present

entry[2]

NOTE 4,5

FIRST-TO-ANSWER

uri attribute

px_MCPTT_ID_User_C

display-name

not present

entry[2]

NOTE 4,5

PRE-ESTABLISH AND FIRST-TO-ANSWER

uri attribute

SIP-URI with px_MCPTT_ID_User_C (NOTE 8) extended with SIP URI header fields as specified for the SIP REFER message

SIP-URI:
MCPTT ID of the called user extended with header fields

display-name

not present

resource-lists

encrypted (NOTE 4)

TS 24.481 [11]

TS 24.484 [14]

CONFIG OR GROUPCONFIG

list[1]

encrypted (NOTE 4)

name attribute

not present

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.484 [14]

CONFIG

uri attribute

AUID1 & “/users/” & XUID & “/” & MCSUEID & “/”

UE Configuration document
(NOTE 1a, 2, 3)

“AUID1 & “/users/” & XUID & “/”

Editor’s note: It is not clear in the core specs whether both options are allowed or only one of both; if the UE is allowed not to include the MCSUEID, it is not clear where the MC server gets it from

display-name

Not present

entry[2]

NOTE 4, 5

TS 24.484 [14]

CONFIG

uri attribute

AUID2 & “/users/” & XUID & “/”

UE User Profile document

(NOTE 1b, 2)

display-name

Not present

entry[3]

NOTE 4, 5

TS 24.484 [14]

CONFIG

uri attribute

AUID3 & “/global/service-config.xml”

UE Service Configuration document

(NOTE 1c)

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.484 [14]

GROUPCONFIG

uri attribute

“org.openmobilealliance.groups/global/byGroupID/” & px_MCPTT_Group_A_ID

UE Group Configuration document

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.484 [14]

GROUPCONFIG_B

uri attribute

“org.openmobilealliance.groups/global/byGroupID/” & px_MCPTT_Group_B_ID

UE Group Configuration document

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.484 [14]

GROUPCONFIG_C

uri attribute

“org.openmobilealliance.groups/global/byGroupID/” & px_MCPTT_Group_C_ID

UE Group Configuration document

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.484 [14]

GROUPCONFIG_T

uri attribute

“org.openmobilealliance.groups/global/byGroupID/” & px_MCPTT_Group_T_ID

UE Group Configuration document

display-name

Not present

entry[2]

optional,
NOTE 4, 5

TS 24.481 [11]

GROUPCONFIG

uri attribute

Doc-Sel & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[2]

optional,
NOTE 4, 5

TS 24.481 [11]

GROUPCONFIG_B

uri attribute

Doc-Sel_B & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[2]

optional,
NOTE 4, 5

TS 24.481 [11]

GROUPCONFIG_C

uri attribute

Doc-Sel_C & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[2]

optional,
NOTE 4, 5

TS 24.481 [11]

GROUPCONFIG_T

uri attribute

Doc-Sel_T & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.481 [11]

GROUPKEY

uri attribute

Doc-Sel & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.481 [11]

GROUPKEY_B

uri attribute

Doc-Sel_B & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.481 [11]

GROUPKEY_C

uri attribute

Doc-Sel_C & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[2]

optional,
NOTE 4, 5

TS 24.481 [11]

GROUPCONFIG_T

uri attribute

Doc-Sel_T & “~~” & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

NOTE 1a: AUID1 = “org.3gpp.mcptt.ue-config”

NOTE 1b: AUID2 = “org.3gpp.mcptt.user-profile”

NOTE 1c: AUID3 = “org.3gpp.mcptt.service-config”

NOTE 2: XUID = “sip:” & px_MCPTT_ID_User_A

NOTE 3: MCSUEID = Instance id of the UE (derived from the IMEI according to 23.003 [69] clause 13.8)

NOTE 4: XML encryption may be done by
– element content encryption of the root element <resource-lists> as described in Table 5.5.13.2-1
– element content encryption of (each) <list> element as described in Table 5.5.13.2-1
– attribute URI encryption of the entry’s uri attribute as described in Table 5.5.13.3-1

NOTE 5: When a resource-lists document contains more than one entry, the entries may be in any order

NOTE 6: Doc-Sel = “org.3gpp.MCPTT-GKTP/global/byGroupID/" & px_MCPTT_Group_A_ID & “/”
Doc-Sel_B=“org.3gpp.MCPTT-GKTP/global/byGroupID/” & px_MCPTT_Group_B_ID & “/”
Doc-Sel_C=“org.3gpp.MCPTT-GKTP/global/byGroupID/” & px_MCPTT_Group_C_ID & “/”
Doc-Sel_T=“org.3gpp.MCPTT-GKTP/global/byGroupID/” & px_MCPTT_Group_T_ID & “/”

NOTE 7: Node-Sel = "/group/list-service/mgktp:GKTPs?xmlns(mgktp=urn:3gpp:ns:mcpttGKTP:1.0)”

NOTE 8: TS 23.179 [8] specifies MCPTT ID and MCPTT group ID (clause 8.1.3.1) to be a URIs but does not mandate them to be a SIP URIs; nevertheless according to TS 24.379 [9] (clauses 10.1.1.2.2.1, 10.1.2.2.2.1) the URI in the uri attribute of the resource-lists’ <entry> element needs to be a SIP URI.

Condition

Explanation

PRE-ESTABLISH

Call using a pre-established session

MSG_RSP

resource lists IE in SIP MESSAGE in response to a received SIP MESSAGE message

GROUPCONFIG_B

Message content within subscription to GROUP_B documents

GROUPCONFIG_C

Message content within subscription to GROUP_C documents

GROUPCONFIG_T

Message content within subscription to temporary GROUP_T documents

GROUPKEY_B

Message content within subscription to GROUP_B key material retrieval

GROUPKEY_C

Message content within subscription to GROUP_C key material retrieval

GROUPKEY_T

Message content within subscription to temporary GROUP_T key material retrieval

For further conditions see table 5.5.1-1

– MCVideo

Table 5.5.3.3.1-2: Resource-lists from the UE for MCVideo

Derivation Path: RFC 5366 [35] / RFC 4826 [83]

Information Element

Value/remark

Comment

Reference

Condition

resource-lists

encrypted (NOTE 4)

PRIVATE-CALL

GROUP-CALL

EMERGENCY-CALL

IMMPERIL-CALL

list[1]

encrypted (NOTE 4)

name attribute

Not present

display-name

Not present

entry[1]

NOTE 4, 5

uri attribute

px_MCVideo_ID_User_B

The MCVideo ID of the invited user

display-name

Not present

resource-lists

encrypted (NOTE 4)

TS 24.481 [11]

TS 24.484 [14]

CONFIG OR GROUPCONFIG

list[1]

encrypted (NOTE 4)

name attribute

Not present

CONFIG

display-name

Not present

entry[1]

NOTE 4, 5

TS 24.484 [14]

CONFIG

uri attribute

AUID1 & "/users/" & XUID & "/" & MCSUEID & "/"

UE Configuration document
(NOTE 1a, 2, 3)

"AUID1 & "/users/" & XUID & "/"

Editor’s note: It is not clear in the core specs whether both options are allowed or only one of both; if the UE is allowed not to include the MCSUEID, it is not clear where the MC server gets it from

display-name

Not present

entry[2]

NOTE 5

TS 24.484 [14]

CONFIG

uri attribute

AUID2 & "/users/" & XUID & "/"

UE User Profile document

(NOTE 1b, 2)

display-name

Not present

entry[3]

NOTE 5

TS 24.484 [14]

CONFIG

uri attribute

AUID3 & "/global/service-config.xml"

UE Service Configuration document

(NOTE 1c)

display-name

Not present

entry[1]

NOTE 5

TS 24.481 [11]

GROUPCONFIG

uri attribute

"org.openmobilealliance.groups/global/byGroupID/" & px_MCVideo_Group_A_ID

UE Group Configuration document

display-name

Not present

entry[2]

optional
NOTE 5

TS 24.481 [11]

GROUPCONFIG

uri attribute

Doc-Sel & "~~" & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[1]

NOTE 5

TS 24.481 [11]

GROUPKEY

uri attribute

Doc-Sel & "~~" & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

NOTE 1a: AUID1 = "org.3gpp.mcvideo.ue-config"

NOTE 1b: AUID2 = "org.3gpp.mcvideo.user-profile"

NOTE 1c: AUID3 = "org.3gpp.mcvideo.service-config"

NOTE 2: XUID = "sip:" & px_MCVideo_ID_User_A

NOTE 3: MCSUEID = Instance id of the UE (derived from the IMEI according to 23.003 [69] clause 13.8)

NOTE 4: XML encryption may be done by
– element content encryption of the root element <resource-lists> as described in Table 5.5.13.2-1
– element content encryption of (each) <list> element as described in Table 5.5.13.2-1
– attribute URI encryption of the entry’s uri attribute as described in Table 5.5.13.3-1

NOTE 5: When a resource-lists document contains more than one entry, the entries may be in any order

NOTE 6: Doc-Sel = “org.3gpp.MCPTT-GKTP/global/byGroupID/” & px_MCVideo_Group_A_ID & "/"

NOTE 7: Node-Sel = "/group/list-service/mgktp:GKTPs?xmlns(mgktp=urn:3gpp:ns:mcpttGKTP:1.0)”

– MCData

Table 5.5.3.3.1-3: Resource-lists from the UE for MCData

Derivation Path: RFC 5366 [35] / RFC 4826 [83]

Information Element

Value/remark

Comment

Reference

Condition

resource-lists

encrypted (NOTE 4)

list

encrypted (NOTE 4)

name attribute

Not present

display-name

Not present

entry[1]

NOTE 4, 5

uri attribute

px_MCData_ID_User_B

The MCData ID of the target MCData user

display-name

not present

resource-lists

encrypted (NOTE 4)

TS 24.481 [11]

TS 24.484 [14]

CONFIG OR GROUPCONFIG

list[1]

encrypted (NOTE 4)

name attribute

Not present

CONFIG

display-name

Not present

entry[1]

NOTE 4. 5

TS 24.484 [14]

CONFIG

uri attribute

AUID1 & "/users/" & XUID & "/" & MCSUEID & "/"

UE Configuration document
(NOTE 1a, 2, 3)

"AUID1 & "/users/" & XUID & "/"

Editor’s note: It is not clear in the core specs whether both options are allowed or only one of both; if the UE is allowed not to include the MCSUEID, it is not clear where the MC server gets it from

display-name

Not present

entry[2]

NOTE 5

TS 24.484 [14]

CONFIG

uri attribute

AUID2 & "/users/" & XUID & "/"

UE User Profile document

(NOTE 1b, 2)

display-name

Not present

entry[3]

NOTE 5

TS 24.484 [14]

CONFIG

uri attribute

AUID3 & "/global/service-config.xml"

UE Service Configuration document

(NOTE 1c)

display-name

Not present

entry[1]

NOTE 5

TS 24.481 [11]

GROUPCONFIG

uri attribute

"org.openmobilealliance.groups/global/byGroupID/" & px_MCData_Group_A_ID

UE Group Configuration document

display-name

Not present

entry[2]

optional
NOTE 5

TS 24.481 [11]

GROUPCONFIG

uri attribute

Doc-Sel & "~~" & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

entry[1]

NOTE 5

TS 24.481 [11]

GROUPKEY

uri attribute

Doc-Sel & "~~" & Node-Sel

MCPTT-GKTP document (NOTE 6, 7)

display-name

Not present

NOTE 1a: AUID1 = "org.3gpp.mcdata.ue-config"

NOTE 1b: AUID2 = "org.3gpp.mcdata.user-profile"

NOTE 1c: AUID3 = "org.3gpp.mcdata.service-config"

NOTE 2: XUID = "sip:" & px_MCData_ID_User_A

NOTE 3: MCSUEID = Instance id of the UE (derived from the IMEI according to 23.003 [69] clause 13.8)

NOTE 4: XML encryption may be done by
– element content encryption of the root element <resource-lists> as described in Table 5.5.13.2-1
– element content encryption of (each) <list> element as described in Table 5.5.13.2-1
– attribute URI encryption of the entry’s uri attribute as described in Table 5.5.13.3-1

NOTE 5: When a resource-lists document contains more than one entry, the entries may be in any order

NOTE 6: Doc-Sel = “org.3gpp.MCPTT-GKTP/global/byGroupID/” & px_MCData_Group_A_ID & "/"

NOTE 7: Node-Sel = "/group/list-service/mgktp:GKTPs?xmlns(mgktp=urn:3gpp:ns:mcpttGKTP:1.0)”

5.5.3.3.2 Resource-lists from the SS
– MCPTT

Table 5.5.3.3.2-1: Resource-lists from the SS for MCPTT

Derivation Path: RFC 5366 [35] / RFC 4826 [83]

Information Element

Value/remark

Comment

Reference

Condition

resource-lists

Editor’s note: XML element content encryption to be added

name attribute

Not present

display-name

Not present

list

entry[1]

uri attribute

px_MCPTT_ID_User_A

The MCPTT ID of the invited user

display-name

Not present

– MCVideo

Table 5.5.3.3.2-2: Resource-lists from the SS for MCVideo

Derivation Path: RFC 5366 [35] / RFC 4826 [83]

Information Element

Value/remark

Comment

Reference

Condition

resource-lists

Editor’s note: XML element content encryption to be added

list

entry[1]

uri attribute

px_MCVideo_ID_User_A

The MCVideo ID of the invited user

display name

not present

– MCData

Table 5.5.3.3.2-3: Resource-lists from the SS for MCData

Derivation Path: RFC 5366 [35] / RFC 4826 [83]

Information Element

Value/remark

Comment

Reference

Condition

resource-lists

Editor’s note: XML element content encryption to be added

list

entry[1]

uri attribute

px_MCData_ID_User_A

The MCData ID of the invited user

display name

not present

5.5.3.4 Location-info

5.5.3.4.1 Location-info (Report from the UE)
– MCPTT

Table 5.5.3.4.1-1: Location-info (Report from the UE) for MCPTT

Derivation Path: TS 24.379 [9] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

ReportID attribute

not present

Attribute is used to return the value in the <RequestId> attribute in the <Request> element. Only present in response to a Location-Info Request.

ReportType attribute

"Emergency"

Required

The <ReportType> attribute has two values "Emergency" and "NonEmergency" used to inform whether the client is sending the report in an emergency situation or not.

TriggerID

not present

An element which can occur multiple times. Contains the value of the <TriggerId> attribute associated with a trigger that has fired. Only present if a trigger is the cause of the Location-info Report.

CurrentLocation

A mandatory element that contains the location information

CurrentServingEcgi

Encrypted (NOTE 2) <CurrentServingEcgi> with any content if present

This is optional depending on the configuration sent by the SS

NeighbouringEcgi

Encrypted (NOTE 2) <NeighbouringEcgi> with any content if present

This is optional depending on the configuration sent by the SS

MbmsSaId

Encrypted (NOTE 2) <MbmsSaId> with any content if present

This is optional depending on the configuration sent by the SS

MbsfnArea

Encrypted (NOTE 2) <MbsfnArea> with any content if present

This is optional depending on the configuration sent by the SS

CurrentCoordinate

if present

This is optional depending on the configuration sent by the SS

longitude

Encrypted (NOTE 1) <longitude> with any content

latitude

Encrypted (NOTE 1) <latitude> with any content

NOTE 1: Encrypted sub-element of <CurrentCoordinate> as described in Table 5.5.3.4.1-1A

NOTE 2: Encrypted sub-element of <CurrentLocation> element as described in Table 5.5.3.4.1-1B

Table 5.5.3.4.1-1A: Encrypted sub-element of <CurrentCoordinate> sent by the UE

Derivation Path: TS 24.379 [9] clause F.3.2 (tCoordinateType )

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the sub-element of <CurrentCoordinate>

Table 5.5.3.4.1-1B: Encrypted sub-element of <CurrentLocation> sent by the UE

Derivation Path: TS 24.379 [9] clause F.3.2 (tCurrentLocationType)

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the sub-element of <CurrentLocation>

– MCVideo

Table 5.5.3.4.1-2: Location-info (Report from the UE) for MCVideo

Derivation Path: TS 24.281 [86] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

ReportID

not present

Attribute is used to return the value in the <RequestId> attribute in the <Request> element. Only present in response to a Location-Info Request.

ReportType

"Emergency"

Required

The <ReportType> attribute has two values "Emergency" and "NonEmergency" used to inform whether the client is sending the report in an emergency situation or not.

TriggerID

not present

An element which can occur multiple times. Contains the value of the <TriggerId> attribute associated with a trigger that has fired. Only present if a trigger is the cause of the Location-info Report.

CurrentLocation

A mandatory element that contains the location information

CurrentServingEcgi

Encrypted (NOTE 2) <CurrentServingEcgi> with any content if present

This is optional depending on the configuration sent by the SS

NeighbouringEcgi

Encrypted (NOTE 2) <NeighbouringEcgi> with any content if present

This is optional depending on the configuration sent by the SS

MbmsSaId

Encrypted (NOTE 2) <MbmsSaId> with any content if present

This is optional depending on the configuration sent by the SS

MbsfnArea

Encrypted (NOTE 2) <MbsfnArea> with any content if present

This is optional depending on the configuration sent by the SS

CurrentCoordinate

if present

This is optional depending on the configuration sent by the SS

longitude

Encrypted (NOTE 1) <longitude> with any content

latitude

Encrypted (NOTE 1) <latitude> with any content

NOTE 1: Encrypted sub-element of <CurrentCoordinate> as described in Table 5.5.3.4.1-2A

NOTE 2: Encrypted sub-element of <CurrentLocation> element as described in Table 5.5.3.4.1-2B

Table 5.5.3.4.1-2A: Encrypted sub-element of <CurrentCoordinate> sent by the UE

Derivation Path: TS 24.281 [86] clause F.3.2 (tCoordinateType)

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the sub-element of <CurrentCoordinate>

Table 5.5.3.4.1-2B: Encrypted sub-element of <CurrentLocation> sent by the UE

Derivation Path: TS 24.281 [86] clause F.3.2 (tCurrentLocationType)

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the sub-element of <CurrentLocation>

– MCData

Table 5.5.3.4.1-3: Location-info (Report from the UE) for MCData

Derivation Path: TS 24.282 [87] clause D.4

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

ReportID

not present

Attribute is used to return the value in the <RequestId> attribute in the <Request> element. Only present in response to a Location-Info Request.

ReportType

"Emergency"

Required

The <ReportType> attribute has two values "Emergency" and "NonEmergency" used to inform whether the client is sending the report in an emergency situation or not.

TriggerID

not present

An element which can occur multiple times. Contains the value of the <TriggerId> attribute associated with a trigger that has fired. Only present if a trigger is the cause of the Location-info Report.

CurrentLocation

A mandatory element that contains the location information

CurrentServingEcgi

Encrypted (NOTE 2) <CurrentServingEcgi> with any content if present

This is optional depending on the configuration sent by the SS

NeighbouringEcgi

Encrypted (NOTE 2) <NeighbouringEcgi> with any content if present

This is optional depending on the configuration sent by the SS

MbmsSaId

Encrypted (NOTE 2) <MbmsSaId> with any content if present

This is optional depending on the configuration sent by the SS

MbsfnArea

Encrypted (NOTE 2) <MbsfnArea> with any content if present

This is optional depending on the configuration sent by the SS

CurrentCoordinate

if present

This is optional depending on the configuration sent by the SS

longitude

Encrypted (NOTE 1) <longitude> with any content

latitude

Encrypted (NOTE 1) <latitude> with any content

NOTE 1: Encrypted sub-element of <CurrentCoordinate> as described in Table 5.5.3.4.1-2A

NOTE 2: Encrypted sub-element of <CurrentLocation> element as described in Table 5.5.3.4.1-2B

Table 5.5.3.4.1-3A: Encrypted sub-element of <CurrentCoordinate> sent by the UE

Derivation Path: TS 24.282 [87] clause d.4.2 (tCoordinateType)

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the sub-element of <CurrentCoordinate>

Table 5.5.3.4.1-3B: Encrypted sub-element of <CurrentLocation> sent by the UE

Derivation Path: TS 24.282 [87] clause D.4.2 (tCurrentLocationType)

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-1 containing encrypted element content of the sub-element of <CurrentLocation>

5.5.3.4.2 Location-info (Configuration sent by the SS)
– MCPTT

Table 5.5.3.4.2-1: Location-info (Configuration sent by the SS) for MCPTT

Derivation Path: TS 24.379 [9] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

ConfigScope

"Full"

The MCPTT Client shall replace any previous configuration.

NonEmergencyLocationInformation

ServingEcgi

present

An optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported

NeighbouringEcgi

present

An optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported

MbmsSaId

present

An optional element specifying that the serving MBMS Service Area Id needs to be reported;

MbsfnArea

present

An optional element specifying that the MBSFN area Id needs to be reported;

GeographicalCoordinate

present

An optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [65] needs to be reported

minimumIntervalLength

"10"

A mandatory element specifying the minimum time the MCPTT client needs to wait between sending location reports. The value is given in seconds

EmergencyLocationInformation"

ServingEcgi

present

An optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported

NeighbouringEcgi

present

An optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported

MbmsSaId

present

An optional element specifying that the serving MBMS Service Area Id needs to be reported;

MbsfnArea

present

An optional element specifying that the MBSFN area Id needs to be reported;

GeographicalCoordinate

present

An optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [65] needs to be reported

minimumIntervalLength

"5"

A mandatory element specifying the minimum time the MCPTT client needs to wait between sending location reports. The value is given in seconds

TriggeringCriteria

CellChange

not present

TrackingAreaChange

not present

PlmnChange

not present

MbmsSaChange

not present

MbsfnAreaChange

not present

PeriodicReport

not present

TravelledDistance

not present

McpttSignallingEvent

not present

GeographicalAreaChange

AnyAreaChange

not present

EnterSpecificAreaType

not present

ExitSpecificAreaType

not present

anyExt

mandatory for Rel-15 and above

EmergencyTriggeringCriteria

CellChange

not present

TrackingAreaChange

not present

PlmnChange

not present

MbmsSaChange

not present

MbsfnAreaChange

not present

PeriodicReport

not present

TravelledDistance

not present

McpttSignallingEvent

not present

GeographicalAreaChange

AnyAreaChange

not present

EnterSpecificAreaType

not present

ExitSpecificAreaType

not present

– MCVideo

Table 5.5.3.4.2-2: Location-info (Configuration sent by the SS) for MCVideo

Derivation Path: TS 24.281 [86] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

ConfigScope

"Full"

The MCVideo Client shall replace any previous configuration.

NonEmergencyLocationInformation

ServingEcgi

present

An optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported

NeighbouringEcgi

present

An optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported

MbmsSaId

present

An optional element specifying that the serving MBMS Service Area Id needs to be reported;

MbsfnArea

present

An optional element specifying that the MBSFN area Id needs to be reported;

GeographicalCoordinate

present

An optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [65] needs to be reported

minimumIntervalLength

"10"

A mandatory element specifying the minimum time the MCVIdeo client needs to wait between sending location reports. The value is given in seconds

EmergencyLocationInformation"

ServingEcgi

present

An optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported

NeighbouringEcgi

present

An optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported

MbmsSaId

present

An optional element specifying that the serving MBMS Service Area Id needs to be reported;

MbsfnArea

present

An optional element specifying that the MBSFN area Id needs to be reported;

GeographicalCoordinate

present

An optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [65] needs to be reported

minimumIntervalLength

"5"

A mandatory element specifying the minimum time the MCVideo client needs to wait between sending location reports. The value is given in seconds

TriggeringCriteria

CellChange

not present

TrackingAreaChange

not present

PlmnChange

not present

MbmsSaChange

not present

MbsfnAreaChange

not present

PeriodicReport

not present

TravelledDistance

not present

McvideoSignallingEvent

not present

GeographicalAreaChange

AnyAreaChange

not present

EnterSpecificAreaType

not present

ExitSpecificAreaType

not present

– MCData

Table 5.5.3.4.2-2: Location-info (Configuration sent by the SS) for MCData

Derivation Path: TS 24.281 [86] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

ConfigScope

"Full"

The MCData Client shall replace any previous configuration.

NonEmergencyLocationInformation

ServingEcgi

present

An optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported

NeighbouringEcgi

present

An optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported

MbmsSaId

present

An optional element specifying that the serving MBMS Service Area Id needs to be reported;

MbsfnArea

present

An optional element specifying that the MBSFN area Id needs to be reported;

GeographicalCoordinate

present

An optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [65] needs to be reported

minimumIntervalLength

"10"

A mandatory element specifying the minimum time the MCData client needs to wait between sending location reports. The value is given in seconds

EmergencyLocationInformation"

ServingEcgi

present

An optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported

NeighbouringEcgi

present

An optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported

MbmsSaId

present

An optional element specifying that the serving MBMS Service Area Id needs to be reported;

MbsfnArea

present

An optional element specifying that the MBSFN area Id needs to be reported;

GeographicalCoordinate

present

An optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [65] needs to be reported

minimumIntervalLength

"5"

A mandatory element specifying the minimum time the MCData client needs to wait between sending location reports. The value is given in seconds

TriggeringCriteria

CellChange

not present

TrackingAreaChange

not present

PlmnChange

not present

MbmsSaChange

not present

MbsfnAreaChange

not present

PeriodicReport

not present

TravelledDistance

not present

McdataSignallingEvent

not present

GeographicalAreaChange

AnyAreaChange

not present

EnterSpecificAreaType

not present

ExitSpecificAreaType

not present

5.5.3.4.3 Location-info (Request sent by the SS)
– MCPTT

Table 5.5.3.4.3-1: Location-info (Request sent by the SS) for MCPTT

Derivation Path: TS 24.379 [9] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Request

RequestID

"1"

The RequestID that the MCPTT Client will reference in the Report

– MCVideo

Table 5.5.3.4.3-2: Location-info (Request sent by the SS) for MCVideo

Derivation Path: TS 24.281 [96] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Request

RequestID

"1"

The RequestID that the MCVideo Client will reference in the Report

5.5.3.4.4 Location-info (Report from the SS)

– MCPTT

Table 5.5.3.4.4-1: Location-info (Report from the SS) for MCPTT

Derivation Path: TS 24.379 [9] clause F.3

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

ReportID attribute

not present

ReportType attribute

"Emergency"

TriggerID

not present

CurrentLocation

CurrentServingEcgi

not present

NeighbouringEcgi

not present

MbmsSaId

not present

MbsfnArea

not present

CurrentCoordinate

longitude

Encrypted (NOTE 1) <longitude> with content as specified by the test case

latitude

Encrypted (NOTE 1) <longitude> with content as specified by the test case

NOTE 1: Encrypted tCoordinateType element as described in Table 5.5.3.4.4-1A

Table 5.5.3.4.4-1A: Encrypted sub-element of <CurrentCoordinate> sent by the SS

Derivation Path: TS 24.379 [9] clause F.3.2 (tCoordinateType )

Information Element

Value/remark

Comment

Reference

Condition

type attribute

"Encrypted"

EncryptedData

EncryptedData as described in Table 5.5.13.2-2 containing encrypted element content of the sub-element of <CurrentCoordinate>

5.5.3.5 PIDF

5.5.3.5.1 PIDF from the UE
– MCPTT

Table 5.5.3.5.1-1: PIDF for MCPTT from the UE

Derivation Path: RFC 3863 [114]

Information Element

Value/remark

Comment

Reference

Condition

presence

RFC 3863 [114]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_User_A

tuple

id attribute

Encrypted URI (NOTE 1) with value set to the mcptt-client-id as provided by the UE at registration

status

affiliation

MCPTT extension

TS 24.379 [9] clause 9.3.1

AFFILIATION

group

Encrypted URI (NOTE 1) with value set to px_MCPTT_Group_A_ID

client

not present

status

not present

expires

not present

functionalAlias

MCPTT extension

TS 24.379 [9] Table 9A.3.1.2-1

FUNCTIONAL_ALIAS_STATUS_CHANGE

functionalAliasID attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_FA_A

user attribute

not present

status attribute

not present

expires attribute

not present

contact

not present

note

not present

timestamp

not present

note

not present

p-id

any allowed value if present

TS 24.379 [9] clause 9.3.1

AFFILIATION

p-id-fa

Any allowed value

a globally unique value set to an identifier of a SIP PUBLISH request

TS 24.379 [9] clause 9A.2.1.2

FUNCTIONAL_ALIAS_STATUS_CHANGE

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1

Condition

Explanation

FUNCTIONAL_ALIAS_STATUS_CHANGE

PIDF sent by the UE in request for functional alias status change

For further conditions see table 5.5.1-1

– MCVideo

Table 5.5.3.5.1-2: PIDF for MCVideo from the UE

Derivation Path: RFC 3863 [114]

Information Element

Value/remark

Comment

Reference

Condition

presence

RFC 3863 [114]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCVideo_ID_User_A

tuple

id attribute

Encrypted URI (NOTE 1) with value set to the mcptt-client-id as provided by the UE at registration

status

affiliation

TS 24.281 [86] clause 8.3.1

AFFILIATION

group

Encrypted URI (NOTE 1) with value set to px_MCVideo_Group_A_ID

client

not present

status

not present

expires

not present

p-id

any allowed value if present

AFFILIATION

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1

– MCData

Table 5.5.3.5.1-3: PIDF for MCData from the UE

Derivation Path: RFC 3863 [114]

Information Element

Value/remark

Comment

Reference

Condition

presence

RFC 3863 [114]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCData_ID_User_A

tuple

id attribute

Encrypted URI (NOTE 1) with value set to the mcptt-client-id as provided by the UE at registration

status

affiliation

TS 24.282 [87] clause 8.4.1

AFFILIATION

group

Encrypted URI (NOTE 1) with value set to px_MCDATA_Group_A_ID

client

not present

status

not present

expires

not present

p-id

any allowed value or same value as sent in SIP PUBLISH

set to an identifier of a SIP PUBLISH request

AFFILIATION

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1

5.5.3.5.2 PIDF from the SS
– MCPTT

Table 5.5.3.5.2-1: PIDF for MCPTT from the SS

Derivation Path: RFC 3863 [114]

Information Element

Value/remark

Comment

Reference

Condition

presence

RFC 3863 [114]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_User_A

tuple

id attribute

Encrypted URI (NOTE 1) with value set to the mcptt-client-id as provided by the UE at registration

status

affiliation

MCPTT extension

TS 24.379 [9] clause 9.3.1

AFFILIATION

group

Encrypted URI (NOTE 1) with value set to px_MCPTT_Group_A_ID

client

not present

status

"affiliating"

expires

not present

functionalAlias

MCPTT extension

TS 24.379 [9] Table 9A.3.1.2-1

FUNCTIONAL_ALIAS_ACTIVATED

functionalAliasID attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_FA_A

user attribute

not present

status attribute

"activated"

expires attribute

not present

contact

not present

note

not present

timestamp

not present

note

not present

p-id

not present

AFFILIATION

p-id-fa

same value as received in the SIP PUBLISH message

TS 24.379 [9] clause 9A.2.2.2.5

NOTIFY_FOR_PUBLISH

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1

Condition

Explanation

FUNCTIONAL_ALIAS_ACTIVATED

PIDF sent by the SS in notification for functional alias getting activated

NOTIFY_FOR_PUBLISH

PIDF sent by the SS in notification associated with a previous SIP PUBLISH message sent by the UE

For further conditions see table 5.5.1-1

– MCVideo

Table 5.5.3.5.2-2: PIDF for MCVideo from the SS

Derivation Path: RFC 3863 [114]

Information Element

Value/remark

Comment

Reference

Condition

presence

RFC 3863 [114]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCVideo_ID_User_A

tuple

id attribute

Encrypted URI (NOTE 1) with value set to the mcptt-client-id as provided by the UE at registration

status

affiliation

TS 24.281 [86] clause 8.3.1

AFFILIATION

group

Encrypted URI (NOTE 1) with value set to px_MCVideo_Group_A_ID

client

not present

status

“affiliating”

expires

not present

p-id

not present

AFFILIATION

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1

– MCData

Table 5.5.3.5.2-3: PIDF for MCData from the SS

Derivation Path: RFC 3863 [114]

Information Element

Value/remark

Comment

Reference

Condition

presence

RFC 3863 [114]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCDATA_ID_User_A

tuple

id attribute

Encrypted URI (NOTE 1) with value set to the mcptt-client-id as provided by the UE at registration

status

affiliation

TS 24.282 [87] clause 8.4.1

AFFILIATION

group

px_MCDATA_Group_A_ID

client

not present

status

“affiliating”

expires

not present

p-id

not present

AFFILIATION

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1

5.5.3.6 SIMPLE-FILTER

Table 5.5.3.6-1: SIMPLE-FILTER

Derivation Path: RFC 4661 [48] clause 7

Information Element

Value/remark

Comment

Reference

Condition

filter-set

ns-bindings

TS 24.379 [9] clause 9.3.2.2 requires two separate ns-binding elements

ns-binding urn [1]

prefix

"pidf"

urn

"urn:ietf:params:xml:ns:pidf"

ns-binding urn [2]

MCPTT

prefix

"mcpttPI10"

urn

"urn:3gpp:ns:mcpttPresInfo:1.0"

ns-binding urn [2]

MCVIDEO

prefix

"mcvideoPI10"

urn

"urn:3gpp:ns:mcvideoPresInfo:1.0"

ns-binding urn [2]

MCDATA

prefix

"mcdataPI10"

urn

"urn:3gpp:ns:mcdataPresInfo:1.0"

filter[1]

id attribute

Any value

The value of the ‘id’ attribute has to be unique within the <filter-set> element

uri attribute

Not present

According to TS 24.379 [9] clause 9.3.2.2

domain attribute

Not present

According to TS 24.379 [9] clause 9.3.2.2

remove attribute

false if present

‘false’ per default

enabled attribute

true if present

‘true’ per default

what

RFC 4661 [48]

PER-CLIENT

include[1]

type

xpath if present

"xpath" per default

base

"//presence/tuple[@id=" & client id (NOTE 1) & "]"
Editor’s Note:

FFS whether and how this element should be encrypted

contains the value, according to IETF RFC 4661 [48], set to concatenation of the ‘//presence/tuple[@id="’ string, the MCX client ID, and the ‘"]’ string

what

RFC 4661 [48]

PER-GROUP

include[1]

type

xpath if present

"xpath" per default

base

"//pidf:presence/pidf:additionalData/@pidf:groupCallOngoing"

TS 24.379 [9] clause 9.3.2.2

trigger

Not present

NOTE 1: UUID URN as provided by the client at initial registration

Condition

Explanation

PER-CLIENT

Per-client restrictions of presence event package notification information according to TS 24.379 [9] clause 9.3.2.2

PER-GROUP

Per-group restrictions of presence event package notification information according to TS 24.379 [9] clause 9.3.2.2

Table 5.5.3.6-2: Void

Table 5.5.3.6-3: Void

5.5.3.7 AFFILIATION-COMMAND

– MCPTT

Table 5.5.3.7-1: MCPTT-AFFILIATION-COMMAND for MCPTT

Derivation Path: TS 24.379 [9] clause F.4

Information Element

Value/remark

Comment

Reference

Condition

command-list

affiliate

group[1]

px_MCPTT_Group_A_ID

MCPTT group name

de-affiliate

not present

– MCVideo

Table 5.5.3.7-2: MCVideo-AFFILIATION-COMMAND for MCVideo

Derivation Path: TS 24.281 [86] clause F.4

Information Element

Value/remark

Comment

Reference

Condition

command-list

affiliate

group[1]

px_MCVideo_Group_A_ID

MCVideo group name

de-affiliate

not present

– MCData

Table 5.5.3.7-3: MCData-AFFILIATION-COMMAND for MCData

Derivation Path: TS 24.282 [87] clause D.3

Information Element

Value/remark

Comment

Reference

Condition

command-list

affiliate

group[1]

px_MCData_Group_A_ID

MCData group name

de-affiliate

not present

5.5.3.8 MCData Data signalling messages

The MCData Data signalling messages specified in this clause are protected according to TS 33.180 clause 8.5.4, i.e. a MCData Data signalling message is contained in the protected payload of a MCData Protected Payload Message according to clause 5.5.3.10 with condition PROTECTED_MESSAGE and CSK.

The following conditions apply throughout clause 5.5.3.8:

Table 5.5.3.8-1: Conditions

Condition

Explanation

DELIVERED

Disposition request/notification type DELIVERED

READ

Disposition request/notification type READ

DELIVERED_READ

Disposition request/notification type DELIVERED AND READ

FD_ACCEPTED

Disposition notification type FILE DOWNLOAD REQUEST ACCEPTED

FD_REJECTED

Disposition notification type FILE DOWNLOAD REQUEST REJECTED

FD_COMPLETED

Disposition notification type FILE DOWNLOAD COMPLETED

FD_DEFERRED

Disposition notification type FILE DOWNLOAD DEFERRED

FD_HTTP

FD Message for FD using using HTTP

FD_MSRP

FD Message for FD using media plane

5.5.3.8.1 SDS SIGNALLING PAYLOAD message from the UE

Table 5.5.3.8.1-1: SDS SIGNALLING PAYLOAD message from the UE

Derivation Path: TS 24.282 [87] clause 15.1.2

Information Element

Value/remark

Comment

Reference

Condition

SDS signalling payload message identity

‘00000001’B

SDS SIGNALLING PAYLOAD

TS 24.282 [87] clause 15.2.2

Date and time

Any allowed value

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Any allowed value

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Any allowed value

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

InReplyTo message ID

Not present

TS 24.282 [87] clause 15.2.11

Application ID

Not present

TS 24.282 [87] clause 15.2.7

SDS disposition request type

‘0001’B

TS 24.282 [87] clause 15.2.3

DELIVERED

‘0010’B

READ

‘0011’B

DELIVERED_READ

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

User location

Any allowed value if present

TS 24.282 [87] clause 15.2.25

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

5.5.3.8.2 SDS SIGNALLING PAYLOAD message from the SS

Table 5.5.3.8.2-1: SDS SIGNALLING PAYLOAD message from the SS

Derivation Path: TS 24.282 [87] clause 15.1.2

Information Element

Value/remark

Comment

Reference

Condition

SDS signalling payload message identity

‘00000001’B

SDS SIGNALLING PAYLOAD

TS 24.282 [87] clause 15.2.2

Date and time

The current date and time

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

‘01010101010101010101010101010101’O

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

‘01010101010101010101010101010101’O

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

InReplyTo message ID

Not present

TS 24.282 [87] clause 15.2.11

Application ID

Not present

TS 24.282 [87] clause 15.2.7

SDS disposition request type

‘0001’B

TS 24.282 [87] clause 15.2.3

DELIVERED

‘0010’B

READ

‘0011’B

DELIVERED_READ

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

User location

Not present

TS 24.282 [87] clause 15.2.25

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

5.5.3.8.3 SDS NOTIFICATION message from the UE

Table 5.5.3.8.3-1: SDS NOTIFICATION message from the UE

Derivation Path: TS 24.282 [87] clause 15.1.5

Information Element

Value/remark

Comment

Reference

Condition

SDS notification message identity

‘00000101’B

SDS NOTIFICATION

TS 24.282 [87] clause 15.2.2

SDS disposition notification type

‘00000010’B

TS 24.282 [87] clause 15.2.5

DELIVERED

‘00000011’B

READ

‘00000100’B

DELIVERED_READ

Date and time

Any allowed value

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Same value as in the corresponding SDS SIGNALLING PAYLOAD sent to the UE

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Same value as in the corresponding SDS SIGNALLING PAYLOAD sent to the UE

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Application ID

Not present

TS 24.282 [87] clause 15.2.7

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

5.5.3.8.4 SDS NOTIFICATION message from the SS

Table 5.5.3.8.4-1: SDS NOTIFICATION message from the SS

Derivation Path: TS 24.282 [87] clause 15.1.5

Information Element

Value/remark

Comment

Reference

Condition

SDS notification message identity

‘00000101’B

SDS NOTIFICATION

TS 24.282 [87] clause 15.2.2

SDS disposition notification type

‘00000010’B

TS 24.282 [87] clause 15.2.5

DELIVERED

‘00000011’B

READ

‘00000100’B

DELIVERED_READ

Date and time

The current date and time

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Same value as in the corresponding SDS SIGNALLING PAYLOAD received from the UE

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Same value as in the corresponding SDS SIGNALLING PAYLOAD received from the UE

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Application ID

Not present

TS 24.282 [87] clause 15.2.7

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

5.5.3.8.5 FD SIGNALLING PAYLOAD message from the UE

Table 5.5.3.8.5-1: FD SIGNALLING PAYLOAD message from the UE

Derivation Path: TS 24.282 [87] clause 15.1.2

Information Element

Value/remark

Comment

Reference

Condition

FD signalling payload message identity

‘00000010’B

FD SIGNALLING PAYLOAD

TS 24.282 [87] clause 15.2.2

Date and time

Any allowed value

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Any allowed value

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Any allowed value

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

InReplyTo message ID

Not present

TS 24.282 [87] clause 15.2.11

Application ID

Not present

TS 24.282 [87] clause 15.2.7

FD disposition request type

“0001”

FILE DOWNLOAD COMPLETED UPDATE

TS 24.282 [87] clause 15.2.4

Mandatory download

Not present

Not present indicates a Non-Mandatory download

TS 24.282 [87] clause 15.2.16

‘0001’B

MANDATORY DOWNLOAD

FD_MSRP

Payload

TS 24.282 [87] clause 15.2.13

FD_HTTP

Length of Payload contents

Length of the payload contents

Payload content type

“00000100”

FILEURL

Payload contents

same URL as assigned by the SS in the HTTP 201 (Created) response to the HTTP POST request

Metadata

if present

Metadata is optional

TS 24.282 [87] clause 15.2.17

FD_HTTP

file-selector

Any allowed value

file-date

Any allowed value

file-availability

Any allowed value

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

5.5.3.8.6 FD SIGNALLING PAYLOAD message from the SS

Table 5.5.3.8.6-1: FD SIGNALLING PAYLOAD message from the SS

Derivation Path: TS 24.282 [87] clause 15.1.2

Information Element

Value/remark

Comment

Reference

Condition

FD signalling payload message identity

‘00000010’B

FD SIGNALLING PAYLOAD

TS 24.282 [87] clause 15.2.2

Date and time

The current date and time

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

‘01010101010101010101010101010101’O

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

‘01010101010101010101010101010101’O

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

InReplyTo message ID

Not present

TS 24.282 [87] clause 15.2.11

Application ID

Not present

TS 24.282 [87] clause 15.2.7

FD disposition request type

‘0001’B

FILE DOWNLOAD COMPLETED UPDATE

TS 24.282 [87] clause 15.2.4

Mandatory download

Not present

Not present indicates a Non-Mandatory download

TS 24.282 [87] clause 15.2.16

‘0001’B

MANDATORY DOWNLOAD

FD_MSRP

Length of Payload contents

Length of the payload contents

Payload content type

“00000100”

FILEURL

Payload contents

tsc_MCData_MSF_URI & "/" & sub-path

URL identifying the location of the stored file;

sub-path is arbitrarily selected by the SS and shall be different for every file upload of a test case

Metadata

NOTE 1

TS 24.282 [87] clause 15.2.17

FD_HTTP

file-selector

RFC 5547 [124]

filename

name of the file

e.g. "TestFile.txt"

filesize

size of the file

type

type of the file

e.g. "text/plain"

hash

algorithm

"sha-1"

value

hash value of the file

file-date

RFC 5547 [124]

date-param[1]

type

"creation"

date-time

date and time when the file has been created

e.g. "Mon, 20 Dec 2021 15:01:31 +0100"

RFC 5322 [109]

file-availability

Date and time until which the file is available

e.g. "Fri, 30 Dec 2050 23:59:59 +0100"

TS 24.282 [87] table 15.2.17-1

file-description

"Test file"

TS 24.282 [87] table 15.2.17-1

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

NOTE 1: file-selector, file-date, file-availability and file-description are concatenated using CRLF (carriage-return/line-feed) as separator

5.5.3.8.7 FD NOTIFICATION message from the UE

Table 5.5.3.8.7-1: FD NOTIFICATION message from the UE

Derivation Path: TS 24.282 [87] clause 15.1.6

Information Element

Value/remark

Comment

Reference

Condition

FD notification message identity

‘00000110’B

FD NOTIFICATION

TS 24.282 [87] clause 15.2.2

FD disposition notification type

‘00000001’B

TS 24.282 [87] clause 15.2.6

FD_ACCEPTED

‘00000010’B

FD_REJECTED

‘00000011’B

FD_COMPLETED

‘00000100’B

FD_DEFERRED

Date and time

Any allowed value

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Same value as in the corresponding FD SIGNALLING PAYLOAD sent to the UE

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Same value as in the corresponding FD SIGNALLING PAYLOAD sent to the UE

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Application ID

Not present

TS 24.282 [87] clause 15.2.7

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

5.5.3.8.8 FD NOTIFICATION message from the SS

Table 5.5.3.8.8-1: FD NOTIFICATION message from the SS

Derivation Path: TS 24.282 [87] clause 15.1.6

Information Element

Value/remark

Comment

Reference

Condition

FD notification message identity

‘00000110’B

FD NOTIFICATION

TS 24.282 [87] clause 15.2.2

FD disposition notification type

‘00000001’B

TS 24.282 [87] clause 15.2.6

FD_ACCEPTED

‘00000010’B

FD_REJECTED

‘00000011’B

FD_COMPLETED

‘00000100’B

FD_DEFERRED

Date and time

The current date and time

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Same value as in the corresponding FD SIGNALLING PAYLOAD received from the UE

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Same value as in the corresponding FD SIGNALLING PAYLOAD received from the UE

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Application ID

Not present

TS 24.282 [87] clause 15.2.7

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Sender MCData user ID

Not present

TS 24.282 [87] clause 15.2.15

5.5.3.8.9 SDS OFF-NETWORK MESSAGE message from the UE

Table 5.5.3.8.9-1: SDS OFF-NETWORK MESSAGE message from the UE

Derivation Path: TS 24.282 [87] table 15.1.7.1-1

Information Element

Value/remark

Comment

Reference

Condition

Date and time

Any allowed value

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Conversation ID

Any allowed value

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Any allowed value

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Sender MCData user ID

px_MCData_ID_User_A

InReplyTo message ID

Not present

TS 24.282 [87] clause 15.2.11

Application ID

Not present

TS 24.282 [87] clause 15.2.7

SDS disposition request type

‘0001’B

TS 24.282 [87] clause 15.2.3

DELIVERED

‘0010’B

READ

‘0011’B

DELIVERED_READ

Security parameters

MCData Protected Payload Message as described in Table 5.5.3.10-1 with condition PROTECTED_PAYLOAD containing the Payload as described in Table 5.5.3.8.9-2

MCData Protected Payload Message

TS 33.180 [94]

MCD_1to1

MCData group ID

px_MCData_Group_A_ID

TS 24.282 [87] clause 15.2.14

MCD_grp

Recipient MCData user ID

px_MCData_ID_User_B

MCD_1to1

Payload

Payload as described in Table 5.5.3.8.9-3

TS 24.282 [87] clause 15.2.13

MCD_grp

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Condition

Explanation

MCD_1to1

A one-to-one MCData call

MCD_grp

A group MCData call

For further conditions see table 5.5.3.8-1

Table 5.5.3.8.9-2: Payload contained in the Security parameters

Derivation Path: TS 24.282 [87] clause 15.2.13

Field

Value/remark

Comment

Reference

Condition

Payload IEI

’78’O

TS 24.282 [87] clause 15.1.4

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

any allowed value

The data payload

Example: “abcdEFGH”

Table 5.5.3.8.9-3: DATA PAYLOAD message for group communication from the UE

Derivation Path: TS 24.282 [87] clause 15.1.4

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Payload

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

any allowed value

The data payload

Example: “abcdEFGH”

5.5.3.8.10 SDS OFF-NETWORK MESSAGE message from the SS

Table 5.5.3.8.10-1: SDS OFF-NETWORK MESSAGE message from the SS

Derivation Path: TS 24.282 [87] table 15.1.7.1-1

Information Element

Value/remark

Comment

Reference

Condition

Date and time

The current date and time

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Conversation ID

‘01010101010101010101010101010101’O

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

‘01010101010101010101010101010101’O

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Sender MCData user ID

px_MCData_ID_User_B

InReplyTo message ID

Not present

TS 24.282 [87] clause 15.2.11

Application ID

Not present

TS 24.282 [87] clause 15.2.7

SDS disposition request type

‘0001’B

TS 24.282 [87] clause 15.2.3

DELIVERED

‘0010’B

READ

‘0011’B

DELIVERED_READ

Security parameters

MCData Protected Payload Message as described in Table 5.5.3.10-2 with condition PROTECTED_PAYLOAD containing the Payload as described in Table 5.5.3.8.10-2

MCData Protected Payload Message

TS 33.180 [94]

MCD_1to1

MCData group ID

px_MCData_Group_A_ID

TS 24.282 [87] clause 15.2.14

MCD_grp

Recipient MCData user ID

px_MCData_ID_User_A

MCD_1to1

Payload

Payload as described in Table 5.5.3.8.10-3

TS 24.282 [87] clause 15.2.13

MCD_grp

Extended application ID

Not present

TS 24.282 [87] clause 15.2.24

Condition

Explanation

MCD_1to1

A one-to-one MCData call

MCD_grp

A group MCData call

For further conditions see table 5.5.3.8-1

Table 5.5.3.8.10-2: Payload contained in the Security parameters and Payload

Derivation Path: TS 24.282 [87] clause 15.2.13

Field

Value/remark

Comment

Reference

Condition

Payload IEI

’78’O

TS 24.282 [87] clause 15.1.4

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

"Test"

The data payload

Table 5.5.3.8.10-3: DATA PAYLOAD message for group communication from the SS

Derivation Path: TS 24.282 [87] clause 15.1.4

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Payload

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

"Test"

The data payload

5.5.3.8.11 SDS OFF-NETWORK NOTIFICATION message from the UE

Table 5.5.3.8.11-1: SDS OFF-NETWORK message from the UE

Derivation Path: TS 24.282 [87] table 15.1.8.4-1

Information Element

Value/remark

Comment

Reference

Condition

SDS disposition notification type

‘00000010’B

TS 24.282 [87] clause 15.2.5

DELIVERED

‘00000011’B

READ

‘00000100’B

DELIVERED_READ

Date and time

Any allowed value

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Same value as in the corresponding SDS OFF-NETWORK MESSAGE sent to the UE

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Same value as in the corresponding SDS OFF-NETWORK MESSAGE sent to the UE

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Sender MCData user ID

px_MCData_ID_User_A

Application ID

Not present

Extended application ID

Not present

5.5.3.8.12 SDS OFF-NETWORK NOTIFICATION message from the SS

Table 5.5.3.8.12-1: SDS OFF-NETWORK message from the SS

Derivation Path: TS 24.282 [87] table 15.1.8.4-1

Information Element

Value/remark

Comment

Reference

Condition

SDS disposition notification type

‘00000010’B

TS 24.282 [87] clause 15.2.5

DELIVERED

‘00000011’B

READ

‘00000100’B

DELIVERED_READ

Date and time

The current date and time

The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

TS 24.282 [87] clause 15.2.8

Conversation ID

Same value as in the corresponding SDS OFF-NETWORK MESSAGE received from the UE

The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier.

TS 24.282 [87] clause 15.2.9

Message ID

Same value as in the corresponding SDS OFF-NETWORK MESSAGE received from the UE

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier

TS 24.282 [87] clause 15.2.10

Sender MCData user ID

px_MCData_ID_User_B

Application ID

Not present

Extended application ID

Not present

5.5.3.9 MCData Data Payload

5.5.3.9.1 MCData Data Payload for group communication

The MCData Data Payload messages for group communication specified in this clause are protected according to TS 33.180 clause 8.5.4, i.e. a MCData Data Payload message is contained in the protected payload of a MCData Protected Payload Message according to clause 5.5.3.10 with condition PROTECTED_MESSAGE and GMK.

Table 5.5.3.9.1-1: DATA PAYLOAD message for group communication from the UE

Derivation Path: TS 24.282 [87] clause 15.1.4

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Payload

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

any allowed value

The data payload

Example: “abcdEFGH”

Table 5.5.3.9.1-2: DATA PAYLOAD message for group communication from the SS

Derivation Path: TS 24.282 [87] clause 15.1.4

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Payload

TS 24.282 [87] clause 15.2.13

MCD_grp

Payload IEI

’78’O

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

"Test"

The data payload

5.5.3.9.2 MCData Data Payload for one-to-one communication

Table 5.5.3.9.2-1: DATA PAYLOAD message for one-to-one communication from the UE

Derivation Path: TS 24.282 [87] clause 15.1.4

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Security parameters and Payload

MCData Protected Payload Message as described in Table 5.5.3.10-1 with condition PROTECTED_PAYLOAD containing the Payload as described in Table 5.5.3.9.2-1A

MCData Protected Payload Message

TS 33.180 [94]

Table 5.5.3.9.2-1A: Payload contained in the Security parameters and Payload

Derivation Path: TS 24.282 [87] clause 15.2.13

Field

Value/remark

Comment

Reference

Condition

Payload IEI

’78’O

TS 24.282 [87] clause 15.1.4

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

any allowed value

The data payload

Example: “abcdEFGH”

Table 5.5.3.9.2-2: DATA PAYLOAD message for one-to-one communication from the SS

Derivation Path: TS 24.282 [87] clause 15.1.4

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Security parameters and Payload

MCData Protected Payload Message as described in Table 5.5.3.10-2 with condition PROTECTED_PAYLOAD containing the Payload as described in Table 5.5.3.9.2-2A

MCData Protected Payload Message

TS 33.180 [94]

Table 5.5.3.9.2-2A: Payload contained in the Security parameters and Payload

Derivation Path: TS 24.282 [87] clause 15.2.13

Field

Value/remark

Comment

Reference

Condition

Payload IEI

’78’O

TS 24.282 [87] clause 15.1.4

Length of Payload

length of the content

Payload content type

‘00000001’B

TEXT

Payload data

"Test"

The data payload

5.5.3.10 MCData Protected Payload Message

Table 5.5.3.10-1: MCData Protected Payload Message from the UE

Derivation Path: TS 33.180 [94] clause 8.5.4

Information Element

Value/remark

Comment

Reference

Condition

Message Type

Same message type as in the MCData message contained as Payload but with bit 7 set to ‘1’B

PROTECTED_MESSAGE

’01??????’B

NOTE: TS 33.180 [94] does not specify any message type

PROTECTED_FILE

‘01111010B

‘7A’O; IEI

TS 24.282 [87] clause 15.1.4

PROTECTED_PAYLOAD

Date and Time

Any allowed value

Date and Time of creation of protected payload message

Payload ID

Any allowed value

The identifier for the payload.

Payload sequence number

Any allowed value

The sequence number of the protected payload.

Payload Algorithm

’01’O

DP_AES_128_GCM

Signalling algorithm

not present

IV

Any allowed value

Initialisation vector (or nonce) for message.

Length depends on the algorithm and key used.

128 bits or 256 bits depending on the algorithm.

DPPK-ID

PCK-ID

PROTECTED_PAYLOAD, PCK

GMK-ID

GMK

CSK-ID

CSK

Payload

Protected Payload (Ciphertext)

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Value as used in MCData messages in TS 24.282 [87]

Length of Payload contents

length of the content

Payload content type

’02’O

BINARY

Payload contents

Encrypted MCData message (NOTE 1)

PROTECTED_MESSAGE

Encrypted file or portion of file

PROTECTED_FILE

Encrypted Payload(s) of the unprotected DATA PAYLOAD message (NOTE 2)

PROTECTED_PAYLOAD

NOTE 1: The whole message is encrypted (including its message type)

NOTE 2: The whole payload(s) are encrypted (including their IEI and length); in general there is only one payload

Condition

Explanation

PROTECTED_MESSAGE

The MCData Protected Payload message contains a whole encrypted MCData message

PROTECTED_FILE

The MCData Protected Payload message contains encrypted binary data representing a file or portion of a file

PROTECTED_PAYLOAD

The MCData Protected Payload message contains the Payload IE(S) of the MCData DATA PAYLOAD message

PCK

Encryption uses PCK

GMK

Encryption uses GMK

CSK

Encryption uses CSK

Table 5.5.3.10-2: MCData Protected Payload Message from the SS

Derivation Path: TS 33.180 [94] clause 8.5.4

Information Element

Value/remark

Comment

Reference

Condition

Message Type

Same message type as in the MCData message contained as Payload but with bit 7 set to ‘1’B

PROTECTED_MESSAGE

‘01000011’B

’43’O; same as for protected DATA PAYLOAD

PROTECTED_FILE

‘01111010B

‘7A’O; IEI

TS 24.282 [87] clause 15.1.4

PROTECTED_PAYLOAD

Date and Time

The current date and time

Date and Time of creation of protected payload message

Payload ID

“1”

The identifier for the payload.

Payload sequence number

“1”

The sequence number of the protected payload.

Payload Algorithm

’01’O

DP_AES_128_GCM

Signalling algorithm

not present

IV

‘DCB9085150B3CF21E2F7DF5B542C25C2’O

Initialisation vector (or nonce) for message.

Length depends on the algorithm and key used.

128 bits or 256 bits depending on the algorithm.

DPPK-ID

PCK-ID

PROTECTED_PAYLOAD, PCK

GMK-ID

GMK

CSK-ID

CSK

Payload

Protected Payload (Ciphertext)

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Value as used in MCData messages in TS 24.282 [87]

Length of Payload contents

length of the content

Payload content type

’02’O

BINARY

Payload contents

Encrypted MCData message (NOTE 1)

PROTECTED_MESSAGE

Encrypted field or portion of file

PROTECTED_FILE

Encrypted Payload(s) of the unprotected DATA PAYLOAD message (NOTE 2)

PROTECTED_PAYLOAD

NOTE 1: The whole message is encrypted (including its message type)

NOTE 2: The whole payload(s) are encrypted (including their IEI and length); in general there is only one payload

Condition

Explanation

PROTECTED_MESSAGE

The MCData Protected Payload message contains a whole encrypted MCData message

PROTECTED_FILE

The MCData Protected Payload message contains encrypted binary data representing a file or portion of a file

PROTECTED_PAYLOAD

The MCData Protected Payload message contains the Payload IE(S) of the MCData DATA PAYLOAD message

PCK

Encryption uses PCK

GMK

Encryption uses GMK

CSK

Encryption uses CSK

5.5.3.11 PoC Settings

5.5.3.11.1 PoC Settings from the UE

Table 5.5.3.11.1-1: PoC Settings from the UE

Derivation Path: RFC 4354 [103]

Information Element

Value/remark

Comment

Reference

Condition

poc-settings

entity [1]

id attribute

any value

unique identifier of the EPA (Event Publication Agent)

Editor’s note: to be clarified whether there are requirements for the id

RFC 4354 [103]

am-settings

RFC 4354 [103]

answer-mode

"automatic" or "manual"

"manual"

MANUAL

"automatic"

AUTOMATIC

selected-user-profile-index

TS 24.379 [9] clause 7.4.1

user-profile-index

same value the user-profile-index in the user profile in Table 5.5.8.3-1

Condition

Explanation

MANUAL

Manual answer mode

AUTOMATIC

Automatic answer mode

5.5.3.11.2 PoC Settings from the SS

Table 5.5.3.11.2-1: PoC Settings from the SS

Derivation Path: RFC 4354 [103]

Information Element

Value/remark

Comment

Reference

Condition

poc-settings

entity [1]

id-attribute

"PoC-Settings-1"

unique identifier of the EPA (Event Publication Agent)

Editor’s note: to be clarified whether there are requirements for the id

RFC 4354 [103]

isb-settings

incoming-session-barring

"false"

am-settings

RFC 4354 [103]

answer-mode

"manual"

MANUAL

"automatic"

AUTOMATIC

ipab-settings

incoming-personal-alert-barring

"false"

sss-settings

simultaneous-sessions-support

"true"

selected-user-profile-index

TS 24.379 [9] clause 7.4.1

user-profile-index

same value the user-profile-index in the user profile in Table 5.5.8.3-1

Condition

Explanation

MANUAL

Manual answer mode

AUTOMATIC

Automatic answer mode

5.5.3.12 Xcap-diff documents

Table 5.5.3.12-1: xcap-diff document for MCX configuration

Derivation Path: RFC 5874 [107] clause 4

Information Element

Value/remark

Comment

Reference

Condition

xcap-diff

encrypted (NOTE 5)

xcap-root attribute

tsc_MCX_CMSXCAPRootURI

same URI as <CMS-XCAP-root-URI> element of the initial UE configuration

document[1]

sel attribute

AUID1 & "/users/" & XUID & "/" & MCSUEID & "/" & UE-Config "

NOTE 1a, 2, 2A, 3

new-etag

arbitrary value

previous-etag

same as new-etag

document[2]

sel attribute

AUID2 & "/users/" & XUID & "/" & User-Profile

NOTE 1b, 2, 2B

new-etag

arbitrary value (different than for document[1])

previous-etag

same as new-etag

document[3]

sel attribute

AUID3 & "/global/service-config.xml"

NOTE 1c

new-etag

arbitrary value (different than for document[1] and [2])

previous-etag

same as new-etag

NOTE 1a: AUID1 = "org.3gpp.mcptt.ue-config" for Condition MCPTT
AUID1 = "org.3gpp.mcvideo.ue-config" for Condition MCVideo
AUID1 = "org.3gpp.mcdata.ue-config" for Condition MCData

NOTE 1b: AUID2 = "org.3gpp.mcptt.user-profile" for Condition MCPTT
AUID2 = "org.3gpp.mcvideo.user-profile" for Condition MCVideo
AUID2 = "org.3gpp.mcdata.user-profile" for Condition MCData

NOTE 1c: AUID3 = "org.3gpp.mcptt.service-config" for Condition MCPTT
AUID3 = "org.3gpp.mcvideo.service-config" for Condition MCVideo
AUID3 = "org.3gpp.mcdata.service-config" for Condition MCData

NOTE 2: XUID = "sip:" & px_MCPTT_ID_User_A for Condition MCPTT
XUID = "sip:" & px_MCVideo_ID_User_A for Condition MCVideo
XUID = "sip:" & px_MCData_ID_User_A for Condition MCData

NOTE 2A: UE-Config = "mcptt-ue-configuration.xml" for Condition MCPTT
UE-Config = "mcvideo-ue-configuration.xml" for Condition MCVideo
UE-Config = "mcdata-ue-configuration.xml" for Condition MCData

NOTE 2B: User-Profile = "mcptt-user-profile-" & profile-index & ".xml" for Condition MCPTT (NOTE 4)
User-Profile = "mcvideo-user-profile-" & profile-index & ".xml" for Condition MCVideo (NOTE 4)
User-Profile = "mcdata-user-profile-" & profile-index & ".xml" for Condition MCData (NOTE 4)

NOTE 3: MCSUEID = Instance id of the UE (derived from the IMEI according to 23.003 [69] clause 13.8)

NOTE 4: profile-index is the same as in the user-profile-index attribute of the corresponding document

NOTE 5: The content of the root element <xcap-diff> (not including the xcap-root attribute) is encrypted as described in Table 5.5.13.2-2

Table 5.5.3.12-2: xcap-diff document for MCX group configuration

Derivation Path: RFC 5854 [107] clause 4

Information Element

Value/remark

Comment

Reference

Condition

xcap-diff

encrypted (NOTE 1)

xcap-root

tsc_MCX_GMSXCAPRootURI

same URI as <GMS-XCAP-root-URI> element of the initial UE configuration

document[1]

GROUPCONFIG

sel attribute

"org.openmobilealliance.groups/global/byGroupID/" & Group-ID

NOTE 2

new-etag

arbitrary value for first notification, ‘incremented’ value otherwise (NOTE 4)

NOTE 5

previous-etag

same as new-etag for first notification, same as <new-etag> of previous notification otherwise

NOTE 5

element[1]

GROUPKEY

sel attribute

“org.3gpp.MCPTT-GKTP/global/byGroupID/” & Group-ID & "/~~" & Node-Sel

NOTE 2, 3

GKTPs

group key transport payloads (GKTP) document as described in Table 5.5.3.14-1

NOTE 1: The content of the root element <xcap-diff> (not including the xcap-root attribute) is encrypted as described in Table 5.5.13.2-2

NOTE 2: Group-ID = px_MCPTT_Group_A_ID for Condition MCPTT
Group-ID = px_MCVideo_Group_A_ID for Condition MCVideo
Group-ID = px_MCData_Group_A_ID for Condition MCData

NOTE 3: Node-Sel = “/group/list-service/mgktp:GKTPs?xmlns(mgktp=urn:3gpp:ns:mcpttGKTP:1.0)”

NOTE 4: It is TTCN implementation dependent how the etag is incremented

NOTE 5: Values for <new-etag> and <previous-etag> shall be different for different groups

5.5.3.13 Void

5.5.3.14 MCS group key transport payloads (GKTP) document

Table 5.5.3.14-1: group key transport payloads (GKTP) document

Derivation Path: TS 24.481 [11] clause 7.7

Information Element

Value/remark

Comment

Reference

Condition

GKTPs

GMK-GKTPs

GKTP[1]

MIKEY message as described in Table 5.5.9.1-3

MIKEY message, containing the GMK

TS 33.180 [94]

id attribute

arbitrary value

unique charstring assigned by the SS

5.5.3.15 Conference-info

Table 5.5.3.15-1: Conference-info from the SS

Derivation Path: RFC 4575 [127] clause 6

Information Element

Value/remark

Comment

Reference

Condition

conference-info

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_Group_A_ID

The URI of the group

MCPTT

Encrypted URI (NOTE 1) with value set to px_MCVideo_Group_A_ID

MCVIDEO

state attribute

not present

version attribute

not present

conference-description

not present

host-info

not present

conference-state

not present

users

user [1]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_User_A

MCPTT

Encrypted URI (NOTE 1) with value set to px_MCVideo_ID_User_A

MCVIDEO

state attribute

not present

display-text

not present

associated-aors

not present

roles

not present

languages

not present

cascaded-focus

not present

endpoint

entity attribute

px_MCX_SIP_PublicUserId_A_1

Contact URI of the participant

RFC 4575 [127] clause 5.7

status attribute

not present

display-text

not present

referred

not present

status

connected

joining-method

not present

joining-info

not present

disconnection-method

not present

disconnection-info

not present

media

not present

call-info

not present

user [2]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_User_B

MCPTT

Encrypted URI (NOTE 1) with value set to px_MCVideo_ID_User_B

MCVIDEO

state attribute

not present

display-text

not present

associated-aors

not present

roles

not present

languages

not present

cascaded-focus

not present

endpoint

entity attribute

px_MCX_SIP_PublicUserId_B

Contact URI of the participant

RFC 4575 [127] clause 5.7

status attribute

not present

display-text

not present

referred

not present

status

connected

joining-method

not present

joining-info

not present

disconnection-method

not present

disconnection-info

not present

media

not present

call-info

not present

user [3]

entity attribute

Encrypted URI (NOTE 1) with value set to px_MCPTT_ID_User_C

MCPTT

Encrypted URI (NOTE 1) with value set to px_MCVideo_ID_User_C

MCVIDEO

state attribute

not present

display-text

not present

associated-aors

not present

roles

not present

languages

not present

cascaded-focus

not present

endpoint

entity attribute

px_MCX_SIP_PublicUserId_C

Contact URI of the participant

RFC 4575 [127] clause 5.7

status attribute

not present

display-text

not present

referred

not present

status

connected

joining-method

not present

joining-info

not present

disconnection-method

not present

disconnection-info

not present

media

not present

call-info

not present

sidebars-by-ref

not present

sidebars-by-val

not present

NOTE 1: Encrypted attribute as described in Table 5.5.13.3-1