5.3B Generic test procedures for UE MCVideo operation

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

5.3B.1 MCVideo CO session establishment/modification without provisional responses other than 100 Trying

5.3B.1.1 Initial conditions

As specified in the test case which calls the procedure in its entirety or refers to parts of it.

5.3B.1.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.1.3 Procedure

Table 5.3B.1.3-1: MCVideo CO session establishment/modification without provisional responses other than 100 Trying

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Step 1a1 describes behaviour that depends on the E-UTRA RRC state at the time the present procedure is called.

1a1

IF in RRC_IDLE state, the E-UTRA/EPC actions which are related to the MCVideo call establishment described in clause 5.4.3 ‘Generic Test Procedure for MCX CO communication in E-UTRA’ take place.

2

Check: Does the UE (MCVideo Client) send a SIP INVITE requesting the establishment/modification of an MCVideo call?

–>

SIP INVITE

P

3

The SS sends SIP 100 Trying

<–

SIP 100 (Trying)

4

The SS (MCVideo server) responds with a SIP 200 (OK)

<–

SIP 200 (OK)

5

Check: Does the UE (MCVideo Client) send a SIP ACK to acknowledge the session establishment/modification?

–>

SIP ACK

P

EXCEPTION: Steps 6a1-6a2 describe behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the UE requests implicit floor control in step 2 (i.e. the "mc_implicit_request" fmtp attribute included in the SDP offer and the SS responded with the "mc_implicit_request" fmtp attribute included and the “mc_granted” fmtp attribute not present in the SDP answer (NOTE1)

6a1

The SS (MCVideo server) sends a Floor Granted message.

<–

Transmission Granted

6a2

Check: Does the UE (MCVideo Client) send a Transmission Control Ack message acknowledging the Transmission Granted message from the SS (MCVideo Server)?

–>

Transmission Control Ack

P

NOTE1: Possibilities in SDP-offer/answer depend on the test case requirements

a. UE sends SDP offer without implicit floor request

b. UE sends SDP offer with implicit floor request

i. SDP answer from SS contains “mc_implicit_request” and “mc_granted” (Floor is implicitly granted)

ii. SDP answer from SS contains “mc_implicit request” and but no “mc_granted” (Floor needs to be explicitly granted ar step 6a1)

iii. SDP answer from SS contains no “mc_implicit_request”and no “mc_granted” (the UE needs to explicitly request the floor)

5.3B.1.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure with the following clarifications:

Table 5.3B.1.4-1: SIP INVITE (step 2, Table 5.3B.1.3-1)

Derivation Path: Table 5.5.2.5.1-1 condition MCVIDEO

Table 5.3B.1.4-2: SIP 200 (OK) (step 4, Table 5.3B.1.3-1)

Derivation Path: Table 5.5.2.17.1.2-1 condition INVITE-RSP and MCVIDEO

Table 5.3B.1.4-3: Transmission Granted (step 6a1, Table 5.3B.1.3-1)

Derivation Path: Table 5.5.11.2.1-1, condition ACK

5.3B.2 MCVideo Transmission request – Transmission Granted

5.3B.2.1 Initial conditions

As specified in the test case which calls the procedure in its entirety or refers to parts of it.

5.3B.2.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.2.3 Procedure

Table 5.3B.2.3-1: MCVideo Transmission Request – Transmission Granted

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a Transmission Request message?

–>

Transmission Request

P

2

The SS (MCVideo Server) sends a Transmission Granted message with an acknowledgement required.

<–

Transmission Granted

3

Check: Does the UE (MCVideo Client) send a Transmission Control Ack message in response to the Transmission Granted message?

–>

Transmission Control Ack

P

4

Check: Does the UE (MCVideo Client) provide transmission granted notification to the MCVideo User? (NOTE 1)

P

NOTE 1: This expected to be done via a suitable implementation dependent MMI.

5.3B.2.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

Table 5.3B.2.4-1: Transmission Granted (step 2, Table 5.3B.2.3-1)

Derivation Path: Table 5.5.11.2.1-1 condition ACK

5.3B.3 MCVideo Media Transmission Notification and Request CT

5.3B.3.1 Initial conditions

As specified in the test case which calls the procedure in its entirety or refers to parts of it.

5.3B.3.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.3.3 Procedure

Table 5.3B.3.3-1: MCVideo Media Transmission Notification and Request CT

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS (MCVideo Server) sends a Media Transmission Notification message to the UE (MCVideo Client)

<-

Media Transmission Notification

2

Check: Does the UE (MCVideo Client) provide media transmission notification to the MCVideo User?

(NOTE 1)

P

3

Make the MCVideo User request permission to receive media.

(NOTE 1)

4

Check: Does the UE (MCVideo Client) send a Receive Media Request message to the SS (MCVideo Server)?

–>

Receive Media Request

P

5

The SS (MCVideo Server) sends a Receive Media Response message to the UE (MCVideo Client).

<-

Receive Media Response

EXCEPTION: Step 6a1 describes behaviour that depends on the requirements of test case calling the present procedure.

6a1

IF the test case specifies the Receive Media Response to request a Transmission Control Ack THEN Check: Does the UE (MCVideo Client) acknowledges receipt of Receive Media Response?

–>

Transmission Control Ack

P

NOTE 1: This expected to be done via a suitable implementation dependent MMI.

5.3B.3.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

None

5.3B.4 MCVideo Transmission Request – Queue Position Info

5.3B.4.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.4.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.4.3 Procedure

Table 5.3B.4.3-1: MCVideo Transmission Request – Queue Position Info

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a Transmission Request message?

–>

Transmission Request

P

2

The SS (MCVidao Server) sends a Queue Position Info message indicating that the Transmission Request was queued message with no acknowledgement required.

<–

Queue Position Info

5.3B.4.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

none.

5.3B.5 MCVideo Queue Position Request

5.3B.5.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.5.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.5.3 Procedure

Table 5.3B.5.3-1: MCVideo Queue Position Request

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a Queue Position Request message?

–>

Queue Position Request

P

2

The SS (MCVideo Server) responds with a Queue Position Info message with no acknowledgement required.

<–

Queue Position Info

EXCEPTION: Step 3a1 describes behaviour that depends on the requirements of test case calling the present procedure.

3a1

IF the test case specifies the Queue Position Info to request a Transmission Control Ack THEN Check: Does the UE (MCVideo Client) acknowledges receipt of Queue Position Info?

–>

Transmission Control Ack

P

5.3B.5.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

none

5.3B.6 MCVideo Transmission Request – Transmission Rejected

5.3B.6.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.6.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.6.3 Procedure

Table 5.3B.6.3-1: MCVideo Transmission Request – Transmission Rejected

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a Transmission Request message?

–>

Transmission Request

P

2

The SS (MCVideo Server) sends a Transmission Rejected message with no acknowledgement required

<–

Transmission Rejected

3

Check: Does the UE (MCVideo Client) provide Transmission deny notification to the MCVideo User? (NOTE 1)

P

NOTE 1: This expected to be done via a suitable implementation dependent MMI.

5.3B.6.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

none

5.3B.7 MCVideo Transmission End Request CO

5.3B.7.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.7.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.7.3 Procedure

Table 5.3B.7.3-1: MCVideo transmission End Request CO

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a Transmission End Request message indicating that it wants to terminate a MCVideo On-Demand Pre-Arranged Emergency Group Call, with implicit Transmission Control?

–>

Transmission End Request

P

2

The SS (MCVideo Server) responds with a Transmission End Response message verifying that the UE (MCVideo Client) is able to end an MCVideo On-Demand Pre-Arranged Emergency Group Call, with implicit Transmission Control.

<–

Transmission End Response

3

Check: Does the UE (MCVideo Client) send a Transmission Control Ack message?

–>

Transmission Control Ack

P

4

The SS (MCVideo Server) sends a Transmission Idle message. Do I need this message? No difference whether ending an emergency call or normal call?

<–

Transmission Idle

NOTE 1: This expected to be done via a suitable implementation dependent MMI.

5.3B.7.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

Table 5.3B.7.4-1: Transmission End Response (Step 2, Table 5.3B.7.3-1)

Derivation Path: Table 5.5.11.3.2-1, condition ACK

5.3B.8 MCVideo Reception End Request CO

5.3B.8.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.8.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.8.3 Procedure

Table 5.3B.8.3-1: MCVideo Media Reception End Request CO

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a Media Reception End Request to indicate it wants to stop RTP packet media?

–>

Media Reception End Request

P

2

The SS (MCVideo Server) sends a Receive Media Reception End Response message to the UE (MCVideo Client).

<–

Media Reception End Response

3

The SS (MCVideo Server) sends a Transmission Idle message.

<–

Transmission Idle

5.3B.8.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

none

5.3B.9 MCVideo Transmission End Request CT

5.3B.9.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.9.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.9.3 Procedure

Table 5.3B.9.3-1: MCVideo Transmission End Request CT

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS (MCVideo Server) sends the Transmission end request.

<–

Transmission End Request

2

Void

2A

Check: Does the UE (MCVideo Client) respond to the Transmission end request?

–>

Transmission End Response

P

3

Void

3A

Check Does the UE (MCVideo Client) inform the MCVideo User that the permission to send RTP media is being revoked?

(NOTE 1)

P

4

The SS (MCVideo Server) sends a Transmission Idle message.

<–

Transmission Idle

NOTE 1: This expected to be done via a suitable implementation dependent MMI.

5.3B.9.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

None

5.3B.10 MCVideo Media Reception End Request CT

5.3B.10.1 Initial conditions

As specified in the test case which calls the procedure.

5.3B.10.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.10.3 Procedure

Table 5.3B.10.3-1: MCVideo Media Reception End Request CT

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS (MCVideo Server) sends the Transmission end request.

<–

Media Reception End Request

2

Void

2A

Check: Does the UE (MCVideo Client) respond to the Transmission end request?

–>

Media Reception End Response

P

3

Void

3A

Check: Does the UE (MCVideo Client) inform the MCVideo User that the permission to send RTP media is being revoked?

(NOTE 1)

P

4

The SS (MCVideo Server) sends a Transmission Idle message.

<–

Transmission Idle

NOTE 1: This expected to be done via a suitable implementation dependent MMI.

5.3B.10.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

None

5.3B.11 MCVideo CO session modification

5.3B.11.1 Initial conditions

As specified in the test case which calls the procedure in its entirety or refers to parts of it.

5.3B.11.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used.

5.3B.113 Procedure

Table 5.3B.11.3-1: MCVideo CO session modification

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE (MCVideo Client) send a SIP INVITE requesting the modification of an MCVideo call?

–>

SIP re-INVITE

P

2

The SS sends SIP 100 Trying

<–

SIP 100 (Trying)

3

The SS (MCVideo server) responds with a SIP 200 (OK)

<–

SIP 200 (OK)

4

Check: Does the UE (MCVideo Client) send a SIP ACK to acknowledge the session modification?

–>

SIP ACK

P

EXCEPTION: Steps 5a1-5a2 describe behaviour that depends on whether the UE has implicitly requested a grant at step 1 which has not implicitly been granted at step 3 (NOTE 1)

5a1

IF the media description for media control in the 200 OK contains fmtp parameter mc_implicit_request but no fmtp parameter mc_granted THEN the SS (MCVideo Server) sends a Transmission Granted message with an acknowledgement required.

<–

Transmission Granted

5a2

Check: Does the UE (MCVideo Client) send a Transmission Control Ack message in response to the Transmission Granted message?

–>

Transmission Control Ack

P

NOTE 1: An implicit transmit media request may be requested in case of upgrade to an emergency or imminent peril MCVideo group call but not in case of a downgrade or any other re-INVITE

5.3B.11.4 Specific message contents

All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications:

Table 5.3B.11.4-1: SIP 200 (OK) (step 3, Table 5.3B.11.3-1)

Derivation Path: Table 5.5.2.17.1.2-1 with condition INVITE-RSP

Table 5.3B.11.4-2: Transmission Granted (step 5a1, Table 5.3B.11.3-1)

Derivation Path: Table 5.5.11.2.1-1 condition ACK