5.5.11 Default MCVideo Transmission Control Messages and other Information Elements
36.579-13GPPMission Critical (MC) services over LTEPart 1: Common test environmentRelease 15TS
Considerations in regard to describing specific values:
– SSRC
– Synchronization SouRCe (SSRC) values are used in most of the messages specified in clause 5.5.6. The SSRC value is randomly chosen by the participant in, and globally unique within, an RTP session as specified in IETF RFC 3550 [76]. Because the value chosen by the UE (MCVideo client) cannot be controlled, specifying a "hard coded" value to be used by the SS (MCVideo Server) or the SS-UE (MCVideo Client) is prone to triggering a collision by choosing a value which may be the same as the one chosen by the UE. How to resolve SSRC collisions is described in IETF RFC 3550 [76] however, resolving them as part of the MCVideo test case definitions e.g. in TS 36.579-6 [84] is not foreseen and is left to the test implementation.
– For the purposes of default and specific messages definition throughout the present specification, as well as, throughout the rest of the MCPTT conformance test specifications e.g. the TS 36.579-6 [84] no explicit SSRC values are defined and instead the following notation is used to clarify the messages origin/destination:
– When there is no danger for misunderstanding the notation ‘The SSRC of the message sender’ and the ‘The SSRC of the intended recipient of the message’ are used whereas the "sender" and the "recipient" are to be understood in the context of the test i.e. the test entities being involved to exchange messages.
5.5.11.1 Transmission Control Specific Messages Sent by the Transmission Participant
5.5.11.1.1 Transmission Request
Table: 5.5.11.1.1-1 Transmission Request
|
Derivation Path: TS 24.581 [88] Table 9.2.4-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00000” |
Transmission control messages sent by the transmission control participant to the transmission control server |
TC 24.581 [88] clause 9.2.7 and Table 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant sending the Transmission Request message. The participant has permission to send media. |
IETF RFC 3550 [3]. |
|
|
Transmission Priority |
TC 24.581 [88] clause 9.2.3.2 |
|||
|
Transmission Priority Field ID |
“00000000” |
8-bit binary value |
||
|
Transmission Priority Length |
“00000010” |
A binary value that has the value ‘2’ Indicates the total length in octets of the <Transmission priority> value item and the spare bits. |
||
|
Transmission Priority Value |
Any allowed value |
Consists of 8 bit parameter giving the transmission priority (‘0’ to ‘255’) where ‘0’ is the lowest priority and ‘255’ is the highest priority. If the Transmission Priority field is not included in the message the default priority is used as the Transmission Priority value. The value of the default priority is ‘0’. The default priority is sometimes referred to as normal priority. |
||
|
Spare bits |
"00000000" |
An 8-bit binary value set to zero. |
||
|
User ID |
Not Present |
ON-NETWORK |
||
|
User ID |
The User ID field is used in off-network only. The User ID field carries the MCVideo ID of the transmission participant sending the Transmission Release message. |
TC 24.581 [88] clause 9.3.2.8 |
OFF-NETWORK |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Transmission Indicator |
TC 24.581 [88] clause 9.2.3.11 |
|||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.11 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.11 |
|
5.5.11.1.2 Transmission Release
Table: 5.5.11.1.2-1 Transmission Release
|
Derivation Path: TS 24.581 [88] Table 9.2.7-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00010” |
Transmission control messages sent by the transmission control participant to the transmission control server |
TC 24.581 [88] clause 9.2.7 and Table 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant with permission to send media. |
IETF RFC 3550 [3]. |
|
|
User ID |
Not Present |
ON-NETWORK |
||
|
User ID |
The User ID field is used in off-network only. The User ID field carries the MCVideo ID of the transmission participant sending the Transmission Release message. |
TC 24.581 [88] clause 9.3.2.8 |
OFF-NETWORK |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Transmission Indicator |
||||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.11 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.11 |
|
5.5.11.1.3 Queue Position Request
Table: 5.5.11.1.3-1 Queue Position Request
|
Derivation Path: TS 24.581 [88] Table 9.2.11-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00011” |
Server client |
TS 24.581 [88] 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant requesting information about its position in the transmission request queue. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
User ID |
Not Present |
ON-NETWORK |
||
|
User ID |
TS 24.581 [88] 9.2.3.8 |
OFF-NETWORK |
||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Track Info |
Not present |
The MCVideo call does not involve a non-controlling MCVideo function |
TS 24.581 [88] 9.2.3.13 |
|
5.5.11.1.4 Receive Media Request
Table: 5.5.11.1.4-1 Receive Media Request
|
Derivation Path: TS 24.581 [88] Table 9.2.14-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00100” |
Server client |
TS 24.581 [88] 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant requesting the reception of the media from another user. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
User ID |
The User ID field is used to carry the identity of the user who is requesting the reception of the media Note: If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
|||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value |
value is a binary value and includes the value indicating the length in octets of the <User ID> value item except padding. |
TS 24.581 [88] 9.2.3.8 |
|
|
User ID |
px_MCVideo_ID_User_A |
TS 24.581 [88] Table 9.2.3.8-2 |
||
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
||
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.11 |
||
|
Transmission Indicator field ID |
“00001101” |
An 8-bit binary value set according to TS 24.581 [88] 9.2.3.1-1. |
TS 24.581 [88] Table 9.2.3.1-1-1 |
|
|
Transmission Indicator Length |
“00000010” |
An 8-bit binary value (2 in binary) |
TS 24.581 [88] Table 9.2.3.1-1-1 |
|
|
Transmission Indicator |
"1000000000000000" |
A 16 bit bit-map |
TS 24.581 [88] Table 9.2.3.11-2 |
|
|
Reception Priority |
Describes the level of reception priority requested in a Reception Request message or granted in a Reception Granted message. The max reception priority that can be requested in a Reception Request message is negotiated between the transmission control participant and the transmission control server |
|||
|
Reception Priority field ID |
"00010011" |
Uniquely identifies the instance of the Reception Priority Field |
||
|
Reception Priority length |
“00000010” |
Indicates the total length in octets of the < Reception Priority> value item and the spare bits. |
TS 24.581 [88] 9.2.3.19 |
|
|
Reception Priority value |
Any allowed value |
The reception priority (‘0’ to ‘255’) where ‘0’ is the lowest reception priority and ‘255’ is the highest reception priority. If the Reception Priority field is not included in the message the default reception priority is used as the Reception Priority value. The value of the default reception priority is ‘0’. The default reception priority is sometimes referred to as normal reception priority. |
TS 24.581 [88] 9.2.3.19 |
|
|
Track Info |
Not present |
The MCVideo call does not involve a non-controlling MCVideo function |
TS 24.581 [88] 9.2.3.13 |
|
5.5.11.1.5 Transmission Cancel Request
Table: 5.5.11.1.5-1 Transmission Cancel Request
|
Derivation Path: TS 24.581 [88] Table 9.2.17-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00101” |
Server client |
TS 24.581 [88] 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
User ID |
TS 24.581 [88] 9.2.3.8 |
|||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
||
5.5.11.1.6 Remote Transmission Request
Table: 5.5.11.1.6-1 Remote Transmission Request
|
Derivation Path: TS 24.581 [88] Table 9.2.22-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00111” |
Transmission control messages sent by the transmission control participant to the transmission control server |
TC 24.581 [88] clause 9.2.7 and Table 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant requesting the reception of the media from another user. |
IETF RFC 3550 [3]. |
|
|
Remote ID |
Carries the identity of the user whose media transmission is requested. |
TC 24.581 [88] clause 9.3.2.8 |
||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_B |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
User ID |
TC 24.581 [88] clause 9.3.2.8 |
|||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
||
5.5.11.1.7 Remote Transmission Cancel Request
Table: 5.5.11.1.7-1 Remote Transmission Cancel Request
|
Derivation Path: TS 24.581 [88] Table 9.2.24-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01000” |
Transmission control messages sent by the transmission control participant to the transmission control server |
TC 24.581 [88] clause 9.2.7 and Table 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender. |
The SSRC field carries the SSRC of the transmission participant requesting the reception of the media from another user. |
IETF RFC 3550 [3]. |
|
|
User ID |
The User ID field is used in off-network only. The User ID field carries the identity of the user whose media transmission is requested for cancellation. |
TC 24.581 [88] clause 9.3.2.8 |
||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
||
5.5.11.2 Transmission Control Specific Messages Sent by the Transmission Control Server
5.5.11.2.1 Transmission Granted
Table: 5.5.11.2.1-1 Transmission Granted
|
Derivation Path: TS 24.581 [88] Table 9.2.5-1 |
|||||
|---|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
|
Subtype |
“00000” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
||
|
SSRC |
The SSRC of the message sender |
The SSRC of the Transmission Control server for on-network and transmission arbitrator for off-network. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
|||
|
name |
MCV1 |
Transmission Control messages sent by the transmission control server and transmission control participant |
|||
|
Duration |
|||||
|
Duration field ID |
"00000001" |
||||
|
Duration length |
"10" |
value is a binary value and has the value ‘2’ indicating the total length in octets of the <Duration> value item |
|||
|
Duration |
"00000000 10000000" |
128 sec (an arbitrary value) |
|||
|
SSRC of granted transmission participant |
The SSRC of the intended recipient of the message |
Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
|||
|
Transmission priority |
Not present |
If the Transmission Priority field is not included in the message the default priority (=’0′) is used as the Floor Priority value |
|||
|
User ID |
Not present |
ON-NETWORK |
|||
|
User ID |
OFF-NETWORK |
||||
|
User ID field ID |
"00000110" |
||||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
||||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
|||
|
Queue Size |
Not present |
ON-NETWORK |
|||
|
Queue Size |
"0" |
the number of queued MCVideo clients in the MCVideo call |
OFF-NETWORK |
||
|
SSRC of queued floor participant |
Not present |
||||
|
Queued User ID |
Not present |
||||
|
Queue Info |
Not present |
||||
|
Transmission Indicator |
|||||
|
Transmission Indicator field ID |
“00001101” |
An 8-bit binary value set according to TS 24.581 [88] 9.2.3.1-1. |
TS 24.581 [88] Table 9.2.3.1-1-1 |
||
|
Transmission Indicator Length |
“00000010” |
An 8-bit binary value (2 in binary) |
TS 24.581 [88] Table 9.2.3.1-1-1 |
||
|
Transmission Indicator |
"1000000000000000" |
A 16 bit bit-map |
TS 24.581 [88] Table 9.2.3.11-2 |
||
5.5.11.2.2 Transmission Rejected
Table: 5.5.11.2.2-1 Transmission Rejected
|
Derivation Path: TS 24.581 [88] Table 9.2.6-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00001” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
Reject Cause |
Includes the reason for the rejecting the transmission request and can be followed by a text-string explaining why the transmission request was rejected. Therefore the length of the packet will vary depending on the size of the application dependent field. |
TS 24.581 [88] 9.2.3.4 |
||
|
Reject Cause field ID |
"00000010" |
TS 24.581 [88] Table 9.2.3.1-1 |
||
|
Reject Cause length |
The <Reject Cause length> value is a binary value and indicates the total length in octets of the <Reject Cause > value and the <Reject Phrase> value items excluding any padding octets. If the length field is set to ‘2’, there is no <Reject Phrase> value in the Reject Cause field. If the length of the <Reject Cause> value is not (2 + multiple of 4) bytes, the Reject Cause field is padded to (2 + multiple of 4) bytes. The value of the padding bytes is set to zero. The padding bytes are ignored by the receiver. |
|||
|
Reject Cause |
"255" |
Cause #1 – Transmission limit reached The <Reject cause> value set to ‘1’ indicates that the number of transmitters have reached maximum. Cause #2 – Internal transmission control server error The <Reject cause> value set to ‘2’ indicates that the transmission control server cannot grant the transmission request due to an internal error. Cause #3 – Only one participant The <Reject cause> value set to ‘3’ indicates that the transmission control server cannot grant the transmission request, because the requesting party is the only participant in the MCVideo session. Cause #4 – Retry-after timer has not expired The <Reject cause> value set to ‘4’ indicates that the transmission control server cannot grant the transmission request, because timer T9 (Retry-after) has not expired after permission to send media has been revoked. Cause #5 – Receive only The <Reject cause> value set to ‘5’ indicates that the transmission control server cannot grant the transmission request, because the requesting party only has receive privilege. Cause #6 – No resources available The <Reject cause> value set to ‘6’ indicates that the transmission control server cannot grant the transmission request due to congestion. Cause #255 – Other reason The <Reject cause> value set to ‘255’ indicates that the transmission control server does not grant the transmission request due to the transmission control server local policy. |
TS 24.581 [88] 9.2.6.2 |
|
|
Reject Cause Phrase |
"Other reason" |
A text string encoded the text string in the SDES item CNAME. |
IETF RFC 3550 [3] |
|
|
User ID |
Not present |
ON-NETWORK |
||
|
User ID |
The User ID field is used in off-network only. The User ID carries the MCVideo ID of the requesting transmission participant to which the Transmission Rejected message is sent. |
TS 24.581 [88] 9.2.3.8 |
OFF-NETWORK |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.11 |
||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
|
5.5.11.2.3 Transmission Arbitration Taken
Table: 5.5.11.2.3-1 Transmission Arbitration Taken
|
Derivation Path: TS 24.581 [88] Table 9.2.8-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00010” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
Granted Party’s Identity |
Identifies the MCVideo user that is granted to send media. |
TS 24.581 [88] 9.2.3.6 |
||
|
Granted Party’s Identity Field ID |
"00000100" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Granted Party’s Identity length |
value is a binary value and includes the value indicating the length in octets of the <User ID> value item except padding |
TS 24.581 [88] 9.2.3.8 |
||
|
Granted Party’s Identity |
px_MCVideo_ID_User_A |
If the length of the <Granted Party’s> value is not (2 + multiple of 4) bytes, the Granted Party’s Identity field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is set to zero. The padding bytes are ignored by the receiver. |
TS 24.581 [88] 9.2.3.8 |
|
|
Permission to Request the Transmission |
Indicates whether receiving parties are allowed to request the transmission. |
TS 24.581 [88] 9.2.3.8 |
||
|
Permission to Request the Transmission Field ID |
"00000101" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Permission to Request the Transmission length |
"10" |
The <Permission to Request the Transmission length> value is a binary value and has the value ‘2’ indicating the total length in octets of the <Duration> value item. |
TS 24.581 [88] 9.2.3.7 |
|
|
Permission to Request the Transmission |
"1" |
Coded as follows: 0 The receiver is not permitted to request transmission. 1 The receiver is permitted to request transmission |
TS 24.581 [88] 9.2.3.7 |
|
|
User ID |
Not Present |
ON-NETWORK |
||
|
User ID |
The User ID field is used in off-network only. The User ID carries the MCVideo ID of the transmission participant sending the Transmission Arbitration Taken message. |
TS 24.581 [88] 9.2.3.8 |
OFF-NETWORK |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Message Sequence Number |
Used to bind a number of Transmission Arbitration Taken or bind a number of Transmission Idle messages together |
TS 24.581 [88] 9.2.3.9 |
||
|
Message Sequence Number field ID |
"00001000" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Message Sequence Number length |
"10" |
Has the value ‘2’ indicating the total length in octets of the <Message Sequence Number> value item. |
||
|
Message Sequence Number |
"1" |
The <Message Sequence Number> value can be between ‘0’ and ‘65535’. When the ‘65535’ value is reached, the <Message Sequence Number> value starts from ‘0’ again. |
||
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
|
|
SSRC of Granted Transmission Participant |
The SSRC of the intended recipient of the message |
IETF RFC 3550 [3] |
||
5.5.11.2.4 Transmission Arbitration Release
Table: 5.5.11.2.4-1 Transmission Arbitration Release
|
Derivation Path: TS 24.581 [88] Table 9.2.9-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00010” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
Granted Party’s Identity |
Identifies the MCVideo user that is granted to send media. |
TS 24.581 [88] 9.2.3.6 |
||
|
Granted Party’s Identity Field ID |
"00000100" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Granted Party’s Identity length |
value is a binary value and includes the value indicating the length in octets of the <User ID> value item except padding |
TS 24.581 [88] 9.2.3.8 |
||
|
Granted Party’s Identity |
px_MCVideo_ID_User_A |
If the length of the <Granted Party’s> value is not (2 + multiple of 4) bytes, the Granted Party’s Identity field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is set to zero. The padding bytes are ignored by the receiver. |
TS 24.581 [88] 9.2.3.8 |
|
|
Permission to Request the Transmission |
Indicates whether receiving parties are allowed to request the transmission. |
TS 24.581 [88] 9.2.3.8 |
||
|
Permission to Request the Transmission Field ID |
"00000101" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Permission to Request the Transmission length |
"10" |
The <Permission to Request the Transmission length> value is a binary value and has the value ‘2’ indicating the total length in octets of the <Duration> value item. |
TS 24.581 [88] 9.2.3.7 |
|
|
Permission to Request the Transmission |
"1" |
Coded as follows: 0 The receiver is not permitted to request transmission. 1 The receiver is permitted to request transmission |
TS 24.581 [88] 9.2.3.7 |
|
|
User ID |
Not Present |
ON-NETWORK |
||
|
User ID |
The User ID field is used in off-network only. The User ID carries the MCVideo ID of the transmission participant sending the Transmission Arbitration Release message. |
TS 24.581 [88] 9.2.3.8 |
OFF-NETWORK |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Message Sequence Number |
Used to bind a number of Transmission Arbitration Taken or bind a number of Transmission Idle messages together |
TS 24.581 [88] 9.2.3.9 |
||
|
Message Sequence Number field ID |
"00001000" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Message Sequence Number length |
"10" |
Has the value ‘2’ indicating the total length in octets of the <Message Sequence Number> value item. |
||
|
Message Sequence Number |
"1" |
The <Message Sequence Number> value can be between ‘0’ and ‘65535’. When the ‘65535’ value is reached, the <Message Sequence Number> value starts from ‘0’ again. |
||
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
|
|
SSRC of Granted Transmission Participant |
The SSRC of the intended recipient of the message |
IETF RFC 3550 [3] |
||
5.5.11.2.5 Transmission Revoked
Table: 5.5.11.2.5-1 Transmission Revoked
|
Derivation Path: TS 24.581 [88] Table 9.2.10-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00100” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
Reject Cause |
Message includes <Reject Cause> cause value in the Reject Cause field explaining why the transmission control server wants the transmission participant to stop sending media and can be followed by additional information. Therefore the length of the packet can vary depending on the value of the rejection cause. |
TS 24.581 [88] 9.2.3.4 |
||
|
Reject Cause field ID |
"00000010" |
TS 24.581 [88] Table 9.2.3.1-1 |
||
|
Reject Cause length |
The <Reject Cause length> value is a binary value and indicates the total length in octets of the <Reject Cause > value and the <Reject Phrase> value items excluding any padding octets. If the length field is set to ‘2’, there is no <Reject Phrase> value in the Reject Cause field. If the length of the <Reject Cause> value is not (2 + multiple of 4) bytes, the Reject Cause field is padded to (2 + multiple of 4) bytes. The value of the padding bytes is set to zero. The padding bytes are ignored by the receiver. |
|||
|
Reject Cause Value |
"7" |
Cause #1 – Only one MCVideo client The <Reject Cause> value set to ‘1’ indicates that the MCVideo client is the only MCVideo client in the MCVideo session or the only participant connected to a transmission control server. No additional information included. Cause#2 – Media burst too long The <Reject Cause> value set to ‘2’ indicates that the MCVideo User has transmitted too long (e.g., the stop-transmission timer has expired). No additional information included. Cause#3 – No permission to send a Media Burst The <Reject Cause> value set to ‘3’ indicates that the MCVideo client does not have permission to send media. No additional information is included. Cause#4 – Media Burst pre-empted The <Reject Cause> value set to ‘4’ indicates that the MCVideo client ‘s permission to send a media is being pre-empted. No additional information is included. Cause#5 – Terminate the RTP stream The <Reject Cause> value set to ‘5’ indicates that the MCVideo client’s permission to send a media is being revoked. No additional information is included. Cause#6 – No resources available The <Reject Cause> value set to ‘6’ indicates that the transmission control server can no longer grant MCVideo client to send media due to congestion. No additional information is included. Cause#7 – Queue the transmission The <Reject Cause> value set to ‘7’ indicates that the MCVideo client’s permission to send a media is being queued. No additional information is included. Cause #8 – No receiving participant The <Reject cause> value set to ‘8’ indicates that the MCVideo client’s permission to send a media is being revoked because there is no participant to receive the stream. Cause#255 – Other reason The <Reject Cause> value set to ‘255’ indicates that the transmission control server can no longer grant MCVideo client to send media due to the transmission control server local policy. No additional information is included. |
TS 24.581 [88] 9.2.10.2 |
|
|
Reject Cause Phrase |
"Queue the transmission" |
A text string encoded the text string in the SDES item CNAME. |
TS 24.581 [88] 9.2.10.2 |
|
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.11 |
||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
|
5.5.11.2.6 Queue Position Info
Table: 5.5.11.2.6-1 Queue Position Info
|
Derivation Path: TS 24.581 [88] Table 9.2.12-1 |
|||||||||
|---|---|---|---|---|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|||||
|
Subtype |
“00101” |
Server client |
TS 24.581 [88] 9.2.2.1-1 |
||||||
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
||||||
|
User ID |
Not present |
ON-NETWORK |
|||||||
|
User ID |
The User ID field is used in off-network only. The User ID field carries the MCVideo user ID of the transmission participant sending the Queue Position Info message. |
TS 24.581 [88] 9.2.3.8 |
OFF-NETWORK |
||||||
|
User ID field ID |
"00000110" |
||||||||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
||||||||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
|||||||
|
SSRC of Queued Transmission Participant |
Not present |
ON-NETWORK |
|||||||
|
SSRC of Queued Transmission Participant |
The SSRC of the queued transmission participant |
Applicable only in off-network and shall carry the SSRC of the queued transmission participant. |
IETF RFC 3550 [3]. |
OFF-NETWORK |
|||||
|
Queued User ID |
Not present |
ON-NETWORK |
|||||||
|
Queued User ID |
px_MCVIDEO_ID_User_B |
Used in off-network only. The Queued User ID field carries the MCVideo ID of the queued transmission control participant. |
TS 24.581 [88] 9.2.3.8 |
OFF-NETWORK |
|||||
|
Queue Info |
Defines the queue position and granted transmission control priority in the queue. |
TS 24.581 [88] 9.2.3.5 |
|||||||
|
Queue Info field ID |
"00000011" |
TS 24.581 [88] 9.2.3.1 |
|||||||
|
Queue Info length |
"10" |
value is a binary value and has the value ‘2’ |
|||||||
|
Queue Position Info |
"0000001" |
value is a binary value. The <Queue Position Info> value has the value ‘254’ if the MCVideo client is not queued. The <Queue Position Info> value has the max value (‘255’) if the MCVideo client is queued but the MCVideo server is unable to determine the queue position or if MCVideo server policy is not to release information of the queue position to the MCVideo client. |
|||||||
|
Queue Priority Level |
"00000000" |
value consists of 8 bit parameter giving the transmission priority (‘0’ to ‘255’) where ‘0’ is the lowest priority and ‘255’ is the highest priority. If the Transmission Priority field is not included in the message the default priority is used as the Transmission Priority value. The value of the default priority is ‘0’. The default priority is sometimes referred to as normal priority. |
TS 24.581 [88] 9.2.3.2 |
||||||
|
Track Info |
Not present |
The MCVideo call does not involve a non-controlling MCVideo function |
TS 24.581 [88] 9.2.3.13 |
||||||
|
Transmission Control Indicator |
TS 24.581 [88] 9.2.3.11 |
||||||||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
|||||||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
|||||||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
||||||
5.5.11.2.7 Media Transmission Notification
Table: 5.5.11.2.7-1 Media Transmission Notification
|
Derivation Path: TS 24.581 [88] Table 9.2.13-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00110” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
User ID |
The User ID field is used in off-network only. The User ID carries the MCVideo ID of the requesting transmission participant to which the Transmission Rejected message is sent. |
TS 24.581 [88] 9.2.3.8 |
||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Permission to Request the Transmission |
Indicates whether receiving parties are allowed to request the transmission. |
TS 24.581 [88] 9.2.3.8 |
||
|
Permission to Request the Transmission Field ID |
"00000101" |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Permission to Request the Transmission length |
"10" |
The <Permission to Request the Transmission length> value is a binary value and has the value ‘2’ indicating the total length in octets of the <Duration> value item. |
TS 24.581 [88] 9.2.3.7 |
|
|
Permission to Request the Transmission |
"1" |
Coded as follows: 0 The receiver is not permitted to request transmission. 1 The receiver is permitted to request transmission |
TS 24.581 [88] 9.2.3.7 |
|
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.1.1 |
||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
|
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3 |
|
|
Track Info |
Not present |
The MCVideo call does not involve a non-controlling MCVideo function |
TS 24.581 [88] 9.2.3.13 |
|
5.5.11.2.8 Receive Media Response
Table: 5.5.11.2.8-1 Receive Media Response
|
Derivation Path: TS 24.581 [88] Table 9.2.15-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00111” |
Server client |
TS 24.581 [88] 9.2.2.1-1 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant requesting the reception of the media from another user. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
Result |
Indicates whether media reception is possible as per the request |
|||
|
Result field ID |
"00001111" |
TS 24.581 [88] Table 9.2.3.1-1 |
||
|
Result length |
"2" |
value is a binary value and has the value ‘2’ indicating the total length in octets of the <Result> value item and the spare bits |
TS 24.581 [88] 9.2.3.17 |
|
|
Result |
"1" |
0 – The receiver is not permitted (rejected) to receive the media transmission. 1 – The receiver is permitted (granted) to receive the media transmission. |
TS 24.581 [88] 9.2.3.17 |
|
|
Reject Cause |
Not present |
Includes the reason for the rejecting the media receive request and can be followed by a text-string explaining why the media receive request was rejected. Therefore the length of the packet will vary depending on the size of the application dependent field |
||
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.11 |
||
|
Transmission Indicator field ID |
“00001101” |
An 8-bit binary value set according to TS 24.581 [88] 9.2.3.1-1. |
TS 24.581 [88] Table 9.2.3.1-1-1 Transmission Indicator Length |
|
|
Transmission Indicator Length |
“00000010” |
An 8-bit binary value (2 in binary) |
TS 24.581 [88] Table 9.2.3.1-1-1 |
|
|
Transmission Indicator |
"1000000000000000" |
A 16 bit bit-map |
TS 24.581 [88] Table 9.2.3.11-2 |
|
5.5.11.2.9 Media Reception Notification
Table: 5.5.11.2.9-1 Media Reception Notification
|
Derivation Path: TS 24.581 [88] Table 9.2.16-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01000” |
Server client |
TS 24.581 [88] 9.2.2.1-2 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
User ID |
The User ID field carries the MCVideo ID of the user transmitting the media. Note: If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
TS 24.581 [88] 9.2.3.8 |
||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3 |
|
5.5.11.2.10 Transmission Cancel Response
Table 5.5.11.2.10-1 Transmission Cancel Response
|
Derivation Path: TS 24.581 [88] Table 9.2.18-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01001” |
Server client |
TS 24.581 [88] 9.2.2.1-2 and clause 9.2.18 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.2.11 Transmission Cancel Request Notify
Table: 5.5.11.2.11-1 Transmission Cancel Request Notify
|
Derivation Path: TS 24.581 [88] Table 9.2.19-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01010” |
Server client |
TS 24.581 [88] 9.2.2.1-2 and clause 9.2.19 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC of the Transmission Control server for on-network and transmission arbitrator for off-network. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.2.12 Remote Transmission Response
Table: 5.5.11.2.12-1 Remote Transmission Response
|
Derivation Path: TS 24.581 [88] Table 9.2.23-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01011” |
Server client |
TS 24.581 [88] 9.2.2.1-2 and clause 9.2.20 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.2.13 Remote Transmission Cancel Response
Table: 5.5.11.2.13-1 Remote Transmission Cancel Response
|
Derivation Path: TS 24.581 [88] Table 9.2.25-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01100” |
Server client |
TS 24.581 [88] 9.2.2.1-2 and clause 9.2.20 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant requesting the reception of the media from another user. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.2.14 Media Reception Override Notification
Table: 5.5.11.2.14-1 Media Reception Override Notification
|
Derivation Path: TS 24.581 [88] Table 9.2.28-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01101” |
Server client |
TS 24.581 [88] 9.2.2.1-2 and clause 9.2.20 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission participant requesting the reception of the media from another user. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
User ID |
16-bit binary value |
Carries the identity of the user who is requesting the reception of the media. |
TS 24.581 [88] 9.2.3.8 |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Overriding ID |
16-bit binary value |
Carries the identity of the user of the overriding media. |
TS 24.581 [88] 9.2.3.8 |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_B |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identifies the communication of overriding media within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
|
Overridden ID |
16-bit binary value |
Carries the identity of the user of the overridden media. |
TS 24.581 [88] 9.2.3.8 |
|
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identifies the communication of overriding media within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.2.15 Transmission End Notify
Table: 5.5.11.2.15-1 Transmission End Notify
|
Derivation Path: TS 24.581 [88] Table 9.2.29-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01110” |
Server client |
TS 24.581 [88] 9.2.2.1-2 and clause 9.2.20 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
User ID |
Carries the identity of the user whose media transmission has been released |
TS 24.581 [88] 9.2.3.8 |
||
|
User ID field ID |
"00000110" |
|||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
|||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
||
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.2.16 Transmission Idle
Table: 5.5.11.2.16-1 Transmission Idle
|
Derivation Path: TS 24.581 [88] Table 9.2.30-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“01111” |
TS 24.581 [88] 9.2.2.1-2 |
||
|
SSRC |
The SSRC of the message sender |
The SSRC of the Transmission Control server for on-network and transmission arbitrator for off-network. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
name |
“MCV1” |
Transmission Control messages sent by the Transmission Control Server and the Transmission Control Participant. |
||
|
Message Sequence Number |
||||
|
Message Sequence Number field ID |
"00001000" |
|||
|
Message Sequence Number length |
"10" |
value is a binary value and has the value ‘2’ indicating the total length in octets of the <Message Sequence Number> value item. |
||
|
Message Sequence Number |
"1" |
value is a binary value. The <Message Sequence Number> value can be between ‘0’ and ‘65535’. When the ‘65535’ value is reached, the <Message Sequence Number> value starts from ‘0’ again |
||
|
Transmission Indicator |
||||
|
Transmission Indicator field ID |
"00001101" |
TC 24.581 [88] clause 9.2.3.1.1 |
||
|
Transmission Indicator Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Transmission Indicator |
"1000000000000000" |
Contains additional information about a received transmission control message. It is a 16 bit bit-map named as shown in Table 9.2.3.11.2 (a thru P). When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications. |
TC 24.581 [88] clause 9.2.3.1.1 |
|
5.5.11.3 Transmission control specific messages sent by both the transmission control server and transmission control participant
5.5.11.3.1 Transmission End Request
Table: 5.5.11.3.1-1 Transmission End Request
|
Derivation Path: TS 24.581 [88] Table 9.2.20-1 |
|||||
|---|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
|
Subtype |
“00000” |
TS 24.581 [88] 9.2.2.1-2 |
|||
|
SSRC |
The SSRC of the message sender |
The SSRC of the Transmission Control server for on-network and transmission arbitrator for off-network. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
|||
|
User ID |
The User ID field is used to carry the identity of the user whose media transmission is requested to be terminated. |
||||
|
User ID field ID |
"00000110" |
||||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
||||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
|||
|
Media ID |
Not Present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
|||
5.5.11.3.2 Transmission End Response
Table: 5.5.11.3.2-1 Transmission End Response
|
Derivation Path: TS 24.581 [88] Table 9.2.21-1 |
|||||
|---|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
|
Subtype |
“00001” |
TS 24.581 [88] 9.2.2.1-2 |
|||
|
SSRC |
The SSRC of the message sender |
The SSRC of the Transmission Control server for on-network and transmission arbitrator for off-network. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
|||
|
User ID |
The User ID field is used to carry the identity of the user whose media transmission is requested to be terminated. |
||||
|
User ID field ID |
"00000110" |
||||
|
User ID length |
a binary value that includes the value indicating the length in octets of the <User ID> value item except padding. |
||||
|
User ID |
px_MCVideo_ID_User_A |
If the length of the <User ID> value is not (2 + multiple of 4) bytes User ID field shall be padded to (2 + multiple of 4) bytes. The value of the padding bytes is to zero. The padding bytes are ignored by the receiver. |
|||
|
Media ID |
Not Present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
|||
5.5.11.3.3 Media Reception End Request
Table: 5.5.11.3.3-1 Media Reception End Request
|
Derivation Path: TS 24.581 [88] Table 9.2.26-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00010” |
Server client |
TS 24.581 [88] 9.2.2.1-3 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server or the transmission control participant requesting the end of reception of the media from another user. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
|
Transmission Indicator |
The Transmission Indicator contains additional information about a received transmission control message. The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value ‘2’. The <Transmission Indicator> value is a 16 bit bit-map. When set to 1 these meanings apply: A = Normal call B = Broadcast group C = System call D = Emergency call E = Imminent peril call |
TS 24.581 [88] 9.2.3.11 |
||
|
Transmission Indicator field ID |
“00001101” |
An 8-bit binary value set according to TS 24.581 [88] 9.2.3.1-1. |
TS 24.581 [88] Table 9.2.3.1-1-1 |
|
|
Transmission Indicator Length |
“00000010” |
An 8-bit binary value (2 in binary) |
TS 24.581 [88] Table 9.2.3.1-1-1 |
|
|
Transmission Indicator |
Any allowed value |
A 16 bit bit-map |
TS 24.581 [88] Table 9.2.3.11-2 |
|
5.5.11.3.4 Media Reception End Response
Table: 5.5.11.3.4-1 Media Reception End Response
|
Derivation Path: TS 24.581 [88] Table 9.2.27-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00011” |
Server client |
TS 24.581 [88] 9.2.2.1-3 |
|
|
SSRC |
The SSRC of the message sender |
The SSRC field carries the SSRC of the transmission control server or the transmission control participant requesting the end of reception of the media from another user. |
RFC 3550 [3], Appendix 6 shows how to generate a random 32-bit identifier |
|
|
SSRC of transmitter |
The SSRC of the user transmitting the media |
The SSRC of transmitter field carries the SSRC of the user transmitting the media |
||
|
Media ID |
Not present |
The Media ID field is present only if media multiplexing is used. The Media ID field identified a media flow within a media multiplex. |
TS 24.581 [88] 9.2.3.x |
|
5.5.11.3.5 Transmission Control Ack
Table: 5.5.11.3.5-1: Transmission Control Ack
|
Derivation Path: TS 24.581 [88] Table 9.2.31-1 |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Subtype |
“00100” |
|||
|
SSRC |
The SSRC of the message sender |
The SSRC of the Transmission Control server for on-network and transmission arbitrator for off-network. Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [76]. |
||
|
Source |
TS 24.581 [88] 9.2.3.12 |
|||
|
Source field ID |
"00001010" |
|||
|
Source length |
"10" |
value is a binary value and has the value 2 indicating the total length in octets of the <Source> value item |
||
|
Source |
"2" |
The <Source> value is a 16 bit binary value where: ‘0’ the transmission participant is the source ‘1’ the participating MCVideo function is the source ‘2’ the controlling MCVideo function is the source ‘3’ the non-controlling MCVideo function is the source All other values are reserved for future use |
||
|
Message name |
TS 24.581 [88] 9.2.3.18 |
|||
|
Message Name field ID |
"00010000" |
|||
|
Message Name Length |
"110" |
value is a binary value and has the value ‘6’. |
||
|
Message Name |
the message name of the received message |
value is as coded as an ascii name field |
||
|
Message type |
TS 24.581 [88] 9.2.3.10 |
|||
|
Message Type field ID |
"00001100" |
|||
|
Message Type Length |
"10" |
value is a binary value and has the value ‘2’ |
||
|
Message Type |
"000"<the subtype of the received message> |
value is an 8 bit binary value containing the binary value consisting of the 5 bit message subtype as coded in table 9.2.2.1-1, table 9.2.2.1-2 and table 9.2.2.1-3 (including the first bit (used by some transmission control messages to indicate that a Transmission control Ack message is requested) of the five bit subtype) preceded by "000". |
||