5.5.12 MSRP Messages for MCData

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

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

5.5.12.1 MSRP SEND

5.5.12.1.1 MSRP SEND from the UE

– MSRP SEND from the UE with No Chunking Used

Table 5.5.12.1-1: MSRP SEND from the UE

Derivation Path: RFC 4975 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	any allowed value
To-Path
value	px_MSRP_URI_SS_ID
From-Path
value	px_MSRP_URI_A_ID
Message-ID
value	any allowed value	If chunking is done: The message ID corresponds to the whole message, so the receiver can also use it to reassemble the message and tell which chunks belong with which message.
Byte-Range		The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message
range-start	any allowed value
range-end	any allowed value
total length	any allowed value
Content-Type			TS 24.582 [89], clause 6.4
media-type	"multipart/mixed"
MIME body part		SDS SIGNALLING PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-signalling"
MIME-part-body	As described in Table 5.5.3.8.1-1
MIME body part		SDS DATA PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-payload"
MIME-part-body	As described in Table 5.5.3.9-1
End-line	"——-"<Transaction Identifier value>"$"	an end-line of seven hyphens, the transaction identifier, and a "$" to indicate that this request contains the end of a complete message

– Empty MSRP SEND from the UE for Binding

Table 5.5.12.1-2: Empty MSRP SEND from the UE for Binding

Derivation Path: RFC 4975 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	any allowed value
To-Path
value	px_MSRP_URI_SS_ID
From-Path
value	px_MSRP_URI_A_ID
Message-ID
value	any allowed value
Byte-Range		The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message
range-start	"1-"
range-end	"0/"
total length	"0"
Content-Type	not present
End-line	"——-"<Transaction Identifier value>"$"

– MSRP SEND from the UE with Chunking Used

Table 5.5.12.1-3: MSRP SEND from the UE with Chunking Used

Derivation Path: RFC 4975 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	any allowed value
To-Path
value	px_MSRP_URI_SS_ID
From-Path
value	px_MSRP_URI_A_ID
Message-ID
value	any allowed value	If chunking is done: The message ID corresponds to the whole message, so the receiver can also use it to reassemble the message and tell which chunks belong with which message.
Byte-Range		The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message. Example: Byte-Range for Chunk 1 of 2: 1-2/8 Byte-Range for Chunk 2 of 2: 5-8/8
range-start	<any allowed value>"-"
range-end	<any allowed value>"/"	The range-end field SHOULD indicate the position of the last byte in the body, if known. It MUST take the value of "*" if the position is unknown, or if the request needs to be interruptible.
total length	the total length
Content-Type			TS 24.582 [89], clause 6.4
media-type	"multipart/mixed"
MIME body part		SDS SIGNALLING PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-signalling"
MIME-part-body	As described in Table 5.5.3.8.1-1
MIME body part		SDS DATA PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-payload"
MIME-part-body	As described in Table 5.5.3.9-1
End-line	"——-"<Transaction Identifier value>"+"	an end-line of seven hyphens, the transaction identifier, and a "+" to indicate that this request is not the end of a complete message

– MSRP SEND from the UE with Chunking Used – Last Chunk

Table 5.5.12.1-4: MSRP SEND from the UE with Chunking Used – Last Chunk

Derivation Path: RFC 4975 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	any allowed value
To-Path
value	px_MSRP_URI_SS_ID
From-Path
value	px_MSRP_URI_A_ID
Message-ID
value	any allowed value	If chunking is done: The message ID corresponds to the whole message, so the receiver can also use it to reassemble the message and tell which chunks belong with which message.
Byte-Range		The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message. Example: Byte-Range for Chunk 1 of 2: 1-2/8 Byte-Range for Chunk 2 of 2: 5-8/8
range-start	<any allowed value>"-"
range-end	<the total length>"/"	The range-end field for the last chunk of a message should be equal to the total length of the message.
total length	the total length	The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message. Example: Byte-Range for Chunk 1 of 2: 1-2/8 Byte-Range for Chunk 2 of 2: 5-8/8
Content-Type			TS 24.582 [89], clause 6.4
media-type	"multipart/mixed"
MIME body part		SDS SIGNALLING PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-signalling"
MIME-part-body	As described in Table 5.5.3.8.1-1
MIME body part		SDS DATA PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-payload"
MIME-part-body	As described in Table 5.5.3.9-1
End-line	"——-"<Transaction Identifier value>"$"	an end-line of seven hyphens, the transaction identifier, and a "$" to indicate that this request contains the last chunk of a complete message

5.5.12.1.2 MSRP SEND from the SS

– MSRP SEND from the SS

Table 5.5.12.1.2-1: MSRP SEND from the SS

Derivation Path: RFC 4975 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	"a786hjs2"
To-Path
value	px_MSRP_URI_A_ID
From-Path
value	px_MSRP_URI_SS_ID
Message-ID
value	"87652491"
Byte-Range		The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message
range-start	1
range-end	the length of the message in bytes
total length	the length of the message in bytes
Content-Type			TS 24.582 [89], clause 6.4
media-type	"multipart/mixed"
MIME body part		SDS SIGNALLING PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-signalling"
MIME-part-body	As described in Table 5.5.3.8.2-1
MIME body part		SDS DATA PAYLOAD
MIME-Content-Type	"application/vnd.3gpp.mcdata-payload"
MIME-part-body	As described in Table 5.5.3.9-2
End-line	"——-a786hjs2$"	an end-line of seven hyphens, the transaction identifier, and a "$" to indicate that this request contains the end of a complete message

– Empty MSRP SEND from the SS for Binding

Table 5.5.12.1.2-2: Empty MSRP SEND from the SS for Binding

Derivation Path: RFC 4975 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	"a786hjs2"
To-Path
value	px_MSRP_URI_A_ID
From-Path
value	px_MSRP_URI_SS_ID
Message-ID
value	"87652491"
Byte-Range		The Byte-Range header field value contains a starting value (range-start) followed by a "-", an ending value (range-end) followed by a "/", and finally the total length. The first octet in the message has a position of one, rather than a zero. The Byte-Range header field identifies the portion of the message carried in this chunk and the total size of the message
range-start	1
range-end	0
total length	0
Content-Type	not present
End-line	"——-a786hjs2$"

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 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	same value as received in the MSRP SEND message
To-Path
value	px_MSRP_URI_SS_ID
From-Path
value	px_MSRP_URI_A_ID
End-line	"——-"<Transaction Identifier value>"$"	an end-line of seven hyphens, the transaction identifier, and a "$" to indicate that this request contains the end of a complete message

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 [X]
Information Element	Value/remark	Comment	Reference	Condition
Transaction Identifier
value	same value as received in the MSRP SEND message
To-Path
value	px_MSRP_URI_A_ID
From-Path
value	px_MSRP_URI_SS_ID
End-line	"——-"<Transaction Identifier value>"$"	an end-line of seven hyphens, the transaction identifier, and a "$" to indicate that this request contains the end of a complete message