5.5.12 MSRP Messages for MCData

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

5.5.12.1 MSRP SEND

5.5.12.1.1 MSRP SEND from the UE

Table 5.5.12.1-1: MSRP SEND from the UE

Derivation Path: RFC 4975 [120] clause 9

Information Element

Value/remark

Comment

Reference

Condition

Transaction Identifier

value

any allowed value

To-Path

value

MSRP URI as provided by the SS in its SDP message sent to the UE during call establishment

From-Path

value

MSRP URI as provided by the UE during call establishment

Message-ID

value

any allowed value

In case of chunking the same Message-ID shall be used for all chunks of the message

Byte-Range

range-start

1 for the first chunk of a message, length of all previous chunks for a second or later chunk of the message

1

EMPTY_SEND_REQ

range-end

any allowed value

0

EMPTY_SEND_REQ

total length

any allowed value

may be a specific length or "*"

0

EMPTY_SEND_REQ

Content-Type

as specified by the test case

TS 24.582 [89], clause 6.4

not present

EMPTY_SEND_REQ

data

as specified by the test case

not present

EMPTY_SEND_REQ

End-line

transact-id

same value as used in Transaction Identifier field

continuation-flag

"+" in case of chunking when further chunks will follow;

"$" in case of the message’s last chunk or if the MSRP SEND request contains the entire message

"$"

EMPTY_SEND_REQ

Condition

Explanation

EMPTY_SEND_REQ

Empty SEND request to bind the TCP connection to an MSRP session

For further conditions see table 5.5.1-1

Table 5.5.12.1-2: Void

Table 5.5.12.1-3: Void

Table 5.5.12.1-4: Void

5.5.12.1.2 MSRP SEND from the SS

Table 5.5.12.1.2-1: MSRP SEND from the SS

Derivation Path: RFC 4975 [120] clause 9

Information Element

Value/remark

Comment

Reference

Condition

Transaction Identifier

value

value assigned by the SS

The SS shall use a different value for each SEND request sent to the UE during a test case

To-Path

value

MSRP URI as provided by the UE in its SDP message sent to the SS during call establishment

From-Path

value

MSRP URI as provided by the SS in its SDP message sent to the UE during call establishment

Message-ID

value

value assigned by the SS

The SS shall use a different value for each message sent to the UE during a test case (NOTE 1)

Byte-Range

range-start

1

range-end

length of the message in bytes

NOTE 1

0

EMPTY_SEND_REQ

total length

length of the message in bytes

NOTE 1

0

EMPTY_SEND_REQ

Content-Type

as specified by the test case

TS 24.582 [89], clause 6.4

not present

EMPTY_SEND_REQ

data

as specified by the test case

not present

EMPTY_SEND_REQ

End-line

transact-id

same value as used in Transaction Identifier field

continuation-flag

"$"

NOTE 1

NOTE 1: It is assumed that in general there is no chunking in DL for MCData test cases.

Condition

Explanation

EMPTY_SEND_REQ

Empty SEND request to bind the TCP connection to an MSRP session

For further conditions see table 5.5.1-1

Table 5.5.12.1.2-2: Void

5.5.12.2 MSRP 200 (OK)

5.5.12.2.1 MSRP 200 (OK) from the UE

Table 5.5.12.2.1-1: MSRP 200 (OK) from the UE

Derivation Path: RFC 4975 [120] clause 9

Information Element

Value/remark

Comment

Reference

Condition

Transaction Identifier

value

same value as received in the MSRP SEND request

To-Path

value

Same value as received in the From-Path of the MSRP SEND request

According to Table 5.5.12.1.2-1 the SS sends only one URI in its SEND requests

RFC 4975 clause 7.2

From-Path

value

MSRP URI of the UE (as provided by the UE in its SDP message sent to the SS during call establishment)

RFC 4975 clause 7.2

End-line

transact-id

same value as used in Transaction Identifier field

continuation-flag

"$"

5.5.12.2.2 MSRP 200 (OK) from the SS

Table 5.5.12.2.2-1: MSRP 200 (OK) from the SS

Derivation Path: RFC 4975 [120] clause 9

Information Element

Value/remark

Comment

Reference

Condition

Transaction Identifier

value

same value as received in the MSRP SEND message

To-Path

value

same value as received in the From-Path of the MSRP SEND request

According to Table 5.5.12.1.1-1 it is assumed that the UE sends only one URI in its SEND requests

RFC 4975 clause 7.2

From-Path

value

MSRP URI of the SS (as provided by the SS in its SDP message sent to the UE during call establishment)

RFC 4975 clause 7.2

End-line

transact-id

same value as used in Transaction Identifier field

continuation-flag

"$"