6.3 Emergency Alert

36.579-63GPPMission Critical (MC) services over LTEPart 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specificationRelease 15TS

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

6.3.1 On-network / Emergency alert / Cancel emergency alert / Client Originated (CO)

6.3.1.1 Test Purpose (TP)

(1)

with { UE (MCVideo Client) registered and authorized for MCVideo Service, including authorized to initiate an emergency alert }

ensure that {
when { the MCVideo User requests to send an emergency alert with the location of emergency }

then { UE (MCVideo Client) sends a SIP MESSAGE initiating an emergency alert and reporting location information }

}

(2)

with { UE (MCVideo Client) in the “MVEA 3: emergency-alert-initiated” state}

ensure that {

when { the MCVideo User requests to cancel the emergency alert}

then { UE (MCVideo Client) sends a SIP MESSAGE requesting the cancelation of the emergency alert}

}

6.3.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.281, clauses 11.2.1.1, 11.2.1.2. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core spec they have been copied from. Unless otherwise stated, these are Rel-15 requirements.

[TS 24.281 clause 11.2.1.1]

Upon receiving a request from the MCVideo user to send an MCVideo emergency alert to the indicated MCVideo group and this is an authorised request for an MCVideo emergency alert as determined by clause 6.2.8.1.6, the MCVideo client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [33] with the clarifications given below.

NOTE 1: this SIP MESSAGE request is assumed to be sent out-of-dialog.

The MCVideo client:

1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;

2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];

3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [11];

4) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 with the <mcvideoinfo> element containing the <mcvideo-Params> element with:

a) the <mcvideo-request-uri> element set to the group identity;

b) the <alert-ind> element set to a value of "true"; and

c) the <mcvideo-client-id> element set to the MCVideo client ID of the originating MCVideo client;

5) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in Annex F.3 with a <Report> element included in the <location-info> root element;

6) shall include in the <Report> element the specific location information configured for the MCVideo emergency alert location trigger;

7) shall set the MCVideo emergency state if not already set;

8) shall set the MCVideo emergency alert state to "MVEA 2: emergency-alert-confirm-pending";

9) shall set the Request-URI to the public service identity identifying the participating MCVideo function serving the group identity; and

10) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [11].

On receiving a SIP 2xx response to the SIP MESSAGE request, the MCVideo client shall set the MCVideo emergency alert state to "MVEA 3: emergency-alert-initiated".

On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCVideo client shall set the MCVideo emergency alert state to "MVEA 1: no-alert".

NOTE 2: the MCVideo emergency state is left set in this case as the MCVideo user presumably is in the best position to determine whether or not they are in a life-threatening condition. The assumption is that the MCVideo user can clear the MCVideo emergency state manually if need be.

[TS 24.281 clause 11.2.1.2]

Upon receiving a request from the MCVideo user to send an MCVideo emergency alert cancellation to the indicated MCVideo group and this is an authorised request for an MCVideo emergency alert cancellation as determined by clause 6.2.8.1.6, the MCVideo client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [33] with the clarifications given below.

NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.

The MCVideo client:

3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [11];

4) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 with the <mcvideoinfo> element containing the <mcvideo-Params> element with:

a) the <mcvideo-request-uri> element set to the MCVideo group identity;

b) the <alert-ind> element set to a value of "false"; and

c) if the MCVideo user is cancelling an MCVideo emergency alert originated by another MCVideo user, include the <originated-by> element set to the MCVideo ID of the MCVideo user who originated the MCVideo emergency alert;

5) if the MCVideo user has additionally requested the cancellation of the in-progress emergency state of the MCVideo group and this is an authorised request for an in-progress emergency group state cancellation as determined by clause 6.2.8.1.7, shall include an <emergency-ind> element set to a value of "false" in the <mcvideoinfo> element containing the <mcvideo-Params> element;

6) shall set the Request-URI to the public service identity identifying the participating MCVideo function serving the group identity;

7) if the generated SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, shall set the MCVideo emergency alert state to "MVEA 4: Emergency-alert-cancel-pending"; and

8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [11].

On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <alert-ind-rcvd> element set to true and an <mcvideo-client-id> matching the MCVideo client ID included in the sent SIP MESSAGE request:

1) if the <alert-ind> element is set to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body of the received SIP MESSAGE request and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, shall:

a) set the MCVideo emergency alert state to "MVEA 1: no-alert"; and

b) clear the MCVideo emergency state if not already cleared;

2) if the <alert-ind> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the received SIP MESSAGE request is set to a value of "true" and if the MCVideo emergency alert state is set to "MVEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, shall set the MCVideo emergency alert state to "MVEA 3: emergency-alert-initiated"; and

NOTE 2: It would appear to be an unusual situation for the initiator of an MCVideo emergency alert to not be able to clear their own alert. Nevertheless, an MCVideo user can be configured to be authorised to initiate MCVideo emergency alerts but not have the authority to clear them. Hence, the case is covered here.

3) if an <emergency-ind> element is present in the application/vnd.3gpp.mcvideo-info+xml MIME body of received SIP MESSAGE request and is set to a value of "false":

a) shall set the MCVideo emergency group call state of the group to "MVEGC 1: emergency-gc-capable"; and

b) shall set the MCVideo emergency group state of the group to "MVEG 1: no-emergency".

NOTE 3: The case where an <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes.

On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the sent SIP MESSAGE request:

1) if the received SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <alert-ind> element set to a value of "true", the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body and the MCVideo emergency alert state is set to "MVEA 4: Emergency-alert-cancel-pending", shall set the MCVideo emergency alert state to "MVEA 3: emergency-alert-initiated"; and

NOTE 4: In this case, an <emergency-ind> element would either not be present or would be set to true. In either case, no change in state would result. Hence, this case is not specified above.

2) if the received SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request does not contain an application/vnd.3gpp.mcvideo-info+xml MIME body with an <alert-ind> element, the sent SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body and the MCVideo emergency alert state is set to "MVEA 4: Emergency-alert-cancel-pending", shall set the MCVideo emergency alert state to "MVEA 3: emergency-alert-initiated".

6.3.1.3 Test description

6.3.1.3.1 Pre-test conditions

System Simulator:

– SS (MCVideo server)

– For the underlying "transport bearer" over which the SS and the UE will communicate Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in TS 36.508 [24] clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document).

IUT:

– UE (MCVideo Client)

– The test USIM set as defined in TS 36.579-1 [2], subclause 5.5.10 is inserted.

Preamble:

– The UE has performed the Generic Test Procedure for MCVideo UE registration as specified in TS 36.579-1 [2], subclause 5.4.2A.

– The MCVideo User performs the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2A.

– UE States at the end of the preamble

– The UE is in E-UTRA Registered, Idle Mode state.

– The MCVideo Client Application has been activated and User has registered-in as the MCVideo User with the Server as active user at the Client.

6.3.1.3.2 Test procedure sequence

Table 6.3.1.3.2-1: Main Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Make the MCVideo User request the establishment of an emergency alert. (NOTE 1)	–	–	–	–
2	Check: Does the UE (MCVideo Client) correctly perform test procedure MCX SIP MESSAGE Request – Accept CO as described in TS 36.579-1 [2] Table 5.3.30.3-1 to request an emergency alert providing location information?	–	–	1	–
3	Make the MCVideo User request to send an emergency alert cancellation to the MCVideo group. (NOTE 1)	–	–	–	–
4	Check: Does the UE (MCVideo Client) correctly perform test procedure MCX SIP MESSAGE Request – Accept CO as described in TS 36.579-1 [2] Table 5.3.30.3-1 to cancel the emergency alert?	–	–	2	–
NOTE 1: This is expected to be done via a suitable implementation dependent MMI

6.3.1.3.3 Specific message contents

Table 6.3.1.3.3-1: SIP MESSAGE (step 2, Table 6.3.1.3.2-1; step 2, TS 36.579-1 [2] Table 5.3.30.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.1-1, condition LOCATION_REPORT
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.3.1.3.3-2
MIME body part		Location info
MIME-part-body	Location-info as described in TS 36.579-1 [2], Table 5.5.3.4.1-2

Table 6.3.1.3.3-2: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-2 condition GROUP-CALL, INVITE_REFER
Information Element	Value/remark	Comment	Reference	Condition
mcvideoinfo
mcvideo-Params
alert-ind	"true"	Encryption according to NOTE 2 in TS 36.579-1 [2] Table 5.5.3.2.1-2

Table 6.3.1.3.3-3: SIP MESSAGE (step 2, Table 6.3.1.3.2-1; step 4, TS 36.579-1 [2] Table 5.3.30.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.2-1
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.3.1.3.3-5

Table 6.3.1.3.3-4: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-4)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.2-2 condition GROUP-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcvideoinfo
mcvideo-Params
alert-ind	"true"	Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.2.2-2
mcvideo-client-id	<mcvideo-client-id> with mcvideoString set to valid UUID URN
alert-ind-rcvd	"true"	Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.2.2-2

Table 6.3.1.3.3-5: SIP MESSAGE (step 4, Table 6.3.1.3.2-1; step 2, TS 36.579-1 [2] Table 5.3.30.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.1-1
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.3.1.3.3-6

Table 6.3.1.3.3-6: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-5)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-1 condition GROUP-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcvideoinfo
mcvideo-Params
alert-ind	"false"

Table 6.3.1.3.3-7: SIP MESSAGE (step 4, Table 6.3.1.3.2-1; step 4, TS 36.579-1 [2] Table 5.3.30.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.2-1
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.3.1.3.3-8

Table 6.3.1.3.3-8: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-7)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.2-2 condition GROUP-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcvideoinfo
mcvideo-Params
alert-ind	"false"	Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.2.2-2
mcvideo-client-id	<mcvideo-client-id> with mcvideoString set to valid UUID URN

6.3.2 On-network / Emergency Alert / Emergency alert origination / Emergency alert cancellation / Client Terminated (CT)

6.3.2.1 Test Purpose (TP)

(1)

with { UE (MCVideo Client) registered and authorized for MCVideo Service, including authorized to initiate an emergency alert }

ensure that {
when { UE (MCVideo Client) receives an emergency alert via s SIP MESSAGE message with the <alert-ind> element in the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of either "true" or "false" }

then { UE (MCVideo Client) responds by sending a SIP 200 (OK) message }

}

6.3.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.281, clauses 11.2.1.1, 11.2.1.3. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core spec they have been copied from. Unless otherwise stated, these are Rel-15 requirements.

[TS 24.281 clause 11.2.1.3]

Upon receipt of a "SIP MESSAGE request for emergency notification", the MCVideo client:

1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true", should display to the MCVideo user an indication of the MCVideo emergency alert and associated information, including:

a) the MCVideo group identity contained in <mcvideo-calling-group-id> element application/vnd.3gpp.mcvideo-info+xml MIME body;

b) the originator of the MCVideo emergency alert contained in the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and

c) the mission critical organization of the MCVideo emergency alert originator contained in the <mc-org> element of the application/vnd.3gpp.mcvideo-info+xml MIME body;

NOTE 1: This is the case of the MCVideo client receiving the notification of another MCVideo user’s emergency alert.

2) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "false":

a) should display to the MCVideo user an indication of the MCVideo emergency alert cancellation and associated information, including:

i) the MCVideo group identity contained in the <mcvideo-calling-group-id> element application/vnd.3gpp.mcvideo-info+xml MIME body;

ii) the originator of the MCVideo emergency alert contained in:

A) if present, the <originated-by> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; or

B) the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and

b) if the MCVideo ID contained in the <originated-by> element is the MCVideo ID of the receiving MCVideo user, shall set the MCVideo emergency alert state to "MVEA 1: no-alert"; and

c) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element is set to a value of "false":

i) shall set the MCVideo emergency group state to "MVEG 1: no-emergency"; and

ii) shall set the MCVideo emergency group call state to "MVEGC 1: emergency-gc-capable";

NOTE 2: This is the case of the MCVideo client receiving the notification of the cancellation by a third party of an MCVideo emergency alert. This can be the MCVideo emergency alert of another MCVideo user or the MCVideo emergency alert of the recipient, as determined by the contents of the <originated-by> element. Optionally, notification of the cancellation of the in-progress emergency state of the MCVideo group can be included.

3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true":

a) should display to the MCVideo user an indication of the additional emergency MCVideo user participating in the MCVideo emergency group call including the following if not already displayed as part of step 1):

i) the MCVideo group identity contained in the <mcvideo-calling-group-id> element application/vnd.3gpp.mcvideo-info+xml MIME body; and

ii) the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body;

b) shall set the MCVideo emergency group state to "MVEG 2: in-progress" if not already set to that value;

NOTE 3: This is the case of the MCVideo client receiving notification of an additional MCVideo user in an MCVideo emergency state (i.e., not the MCVideo user that originally triggered the in-progress emergency state of the group) joining the in-progress emergency group call. An emergency alert indication, if included, is handled in step 1).

4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false":

a) should display to the MCVideo user an indication of the cancellation of the in-progress emergency state of the MCVideo group call including the following if not already displayed as part of step 2):

i) the MCVideo group identity contained in the <mcvideo-calling-group-id> element application/vnd.3gpp.mcvideo-info+xml MIME body; and

ii) the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body;

b) shall set the MCVideo emergency group state to "MVEG 1: no-emergency"; and

c) shall set the MCVideo emergency group call state to "MVEGC 1: emergency-gc-capable";

NOTE 4: This is the case of the MCVideo client receiving the notification of the cancellation of the in-progress emergency state of the MCVideo group. In this case, the receiving MCVideo client is affiliated with the MCVideo group but not participating in the session. An emergency alert cancellation, if included, is handled in step 2).

5) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true":

a) should display to the MCVideo user an indication of the MCVideo user participating in the MCVideo imminent peril group call including the following if not already displayed as part of step 1):

i) the MCVideo group identity contained in the <mcvideo-calling-group-id> element application/vnd.3gpp.mcvideo-info+xml MIME body; and

ii) the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and

b) shall set the MCVideo imminent peril group state to "MVIG 2: in-progress" if not already set to that value;

NOTE 5: This is the case of the MCVideo client receiving notification of an additional MCVideo user initiating an imminent peril group call when there is already an in-progress imminent peril state in effect on the group.

6) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "false":

a) should display to the MCVideo user an indication of the cancellation of the in-progress imminent peril state of the MCVideo group including the following if not already displayed as part of step 2):

i) the MCVideo group identity contained in the <mcvideo-calling-group-id> element application/vnd.3gpp.mcvideo-info+xml MIME body; and

ii) the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body;

b) shall set the MCVideo imminent peril group state to "MVIG 1: no-imminent-peril"; and

c) shall set the MCVideo imminent peril group call state to "MVIGC 1: imminent-peril-gc-capable";

NOTE 6: This is the case of the MCVideo client receiving notification of the cancellation of the in-progress imminent peril state of the group.

7) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; and

8) shall send the SIP 200 (OK) response towards the MCVideo server according to rules and procedures of 3GPP TS 24.229 [11].

6.3.2.3 Test description

6.3.2.3.1 Pre-test conditions

System Simulator:

– SS (MCVideo server)

IUT:

– UE (MCVideo Client)

– The test USIM set as defined in TS 36.579-1 [2], subclause 5.5.10 is inserted.

Preamble:

– The UE has performed the Generic Test Procedure for MCVideo UE registration as specified in TS 36.579-1 [2], subclause 5.4.2A.

– The MCVideo User performs the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2A.

– UE States at the end of the preamble

– The UE is in E-UTRA Registered, Idle Mode state.

– The MCVideo Client Application has been activated and User has registered-in as the MCVideo User with the Server as active user at the Client.

6.3.2.3.2 Test procedure sequence

Table 6.3.2.3.2-1: Main Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE (MCVideo Client) correctly perform test procedure MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 to receive an emergency alert?	–	–	1	–
2	Check: Does the UE (MCVideo Client) correctly perform test procedure MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 to receive an emergency alert cancellation?	–	–	1	–

6.3.2.3.3 Specific message contents

Table 6.3.2.3.3-1: SIP MESSAGE (step 1, Table 6.3.2.3.2-1; step 2, TS 36.579-1 [2] Table 5.3.33.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.2-1
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.3.2.3.3-2
MIME body part		Location info
MIME-part-body	Location-info as described in TS 36.579-1 [2], Table 5.5.3.4.1-2

Table 6.3.2.3.3-2: MCVideo-Info in SIP MESSAGE (Table 6.3.2.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.2-2 condition GROUP-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcvideoinfo
mcvideo-Params
alert-ind	"true"	Encryption according to NOTE 2 in TS 36.579-1 [2] Table 5.5.3.2.2-2A

Table 6.3.2.3.3-3: SIP MESSAGE (step 2, Table 6.3.2.3.2-1; step 2, TS 36.579-1 [2] Table 5.3.33.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.2-1
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.3.2.3.3-4

Table 6.3.2.3.3-4: MCVideo-Info in SIP MESSAGE (Table 6.3.2.3.3-3)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.2-2 condition GROUP-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcvideoinfo
mcvideo-Params
alert-ind	"false"	Encryption according to NOTE 2 in TS 36.579-1 [2] Table 5.5.3.2.2-2A