6.1.3 Subscription to Conference Event Package

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

6.1.3.1 On-network / Conference Event Package / Subscription to Conference Event Package / Termination of subscription

6.1.3.1.1 Test Purpose (TP)

1)

with { UE (MCVideo Client) registered and authorised for MCVideo Service }

ensure that {

when { the MCVideo User requests the establishment of an MCVideo On-demand Pre-arranged Group Call }

then { UE (MCVideo Client) requests On-demand Pre-arranged Group Call by sending a SIP INVITE message, and, after indication from the MCVideo Server that the call was established and receiving a Transmission Granted message, notifies the user }

}

(2)

with { UE (MCVideo Client) having an ongoing On-demand Pre-arranged Group Call with Automatic Commencement Mode }

ensure that {

when { MCVideo User requests to subscribe to the conference event package for the ongoing group call }

then { UE (MCVideo Client) sends a SIP SUBSCRIBE message with the Expires header field set to 4294967295 and responds to a SIP NOTIFY message with a SIP 200 (OK) message }

}

(3)

with { UE (MCVideo Client) having subscribed to the conference event package for the ongoing group call }

ensure that {

when { MCVideo User requests to terminate the subscription }

then { UE (MCVideo Client) sends a SIP SUBSCRIBE message with the Expires header field set to 0 }

}

(4)

with { UE (MCVideo Client) having an ongoing On-demand Pre-arranged Group Call

when { the MCVideo User) requests to end the On-demand Pre-arranged Group Call }

then { UE (MCVideo Client) sends a SIP BYE message and leaves the call }

}

6.1.3.1.2 Conformance Requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.281 clause 9.2.1.2.1.1, 9.2.3.2, 9.2.1.2.3.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.281, clause 9.2.1.2.1.1]

Upon receiving a request from an MCVideo user to establish an MCVideo prearranged group session the MCVideo client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [11], with the clarifications given below.

The MCVideo client:

1) if the MCVideo user has requested the origination of an MCVideo emergency group call or is originating an MCVideo prearranged group call and the MCVideo emergency state is already set, the MCVideo client shall comply with the procedures in clause 6.2.8.1.1;

2) if the MCVideo user has requested the origination of an MCVideo imminent peril group call, the MCVideo client shall comply with the procedures in clause 6.2.8.1.9;

3) if the MCVideo user has requested the origination of a broadcast group call, the MCVideo client shall comply with the procedures in clause 6.2.8.2;

4) shall include the g.3gpp.mcvideo media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [22];

5) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20];

6) 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 [14] in the SIP INVITE request;

7) 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 [20];

8) should include the "timer" option tag in the Supported header field;

9) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";

10) shall set the Request-URI of the SIP INVITE request to the public service identity identifying the participating MCVideo function serving the MCVideo user;

NOTE 1: The MCVideo client is configured with public service identity identifying the participating MCVideo function serving the MCVideo user.

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

12) if the MCVideo emergency state is already set or the MCVideo client emergency group state for this group is set to "MVEG 2: in-progress", the MCVideo client shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2;

13) if the MCVideo client imminent peril group state for this group is set to "MVIG 2: in-progress" or "MVIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12;

14) shall contain in an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with:

a) the <session-type> element set to a value of "prearranged";

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

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

NOTE 2: The MCVideo client does not include the MCVideo ID of the originating MCVideo user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCVideo function.

d) if the group identity can be determined to be a TGI and if the MCVideo client can associate the TGI with a MCVideo group ID, the <associated-group-id> element set to the MCVideo group ID;

NOTE 3: The text "can associate the TGI with a MCVideo group ID" means that the MCVideo client is able to determine that there is a constituent group of the temporary group that it is a member of.

NOTE 4: The MCVideo client is informed about temporary groups and regouping of MCVideo groups that the user is a member of as specified in 3GPP TS 24.481 [24].

NOTE 5: If the MCVideo user selected a TGI where there are several MCVideo groups where the MCVideo user is a member, the MCVideo client selects one of those MCVideo groups.

15) shall include an SDP offer according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.1;

16) if an implicit transmission request is required, shall indicate this as specified in clause 6.4; and

17) shall send the SIP INVITE request towards the MCVideo server according to 3GPP TS 24.229 [11].

On receiving a SIP 2xx response to the SIP INVITE request, the MCVideo client:

1) shall interact with the user plane as specified in 3GPP TS 24.581 [5] ;

2) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted" or the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril-call-requested" or "MVIGC 3: imminent-peril-call-granted", the MCVideo client shall perform the actions specified in clause 6.2.8.1.4; and

3) may subscribe to the conference event package as specified in clause 9.1.3.1.

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

1) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted"; or

2) if the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril-call-requested" or "MVIGC 3: imminent-peril-call-granted";

the MCVideo client shall perform the actions specified in clause 6.2.8.1.5.

On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in clause 6.2.8.1.13.

[TS 24.281, clause 9.2.3.2]

A MCVideo client may subscribe to the conference state event package when a group call is ongoing and the ongoing group call is not initiated as a broadcast group call by sending a SIP SUBSCRIBE request to obtain information of the status of a group session.

When subscribing to the conference state event package, the MCVideo client:

1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [16], IETF RFC 4575 [57] and 3GPP TS 24.229 [11];

2) shall set the Request-URI of the SIP SUBSCRIBE request to the MCVideo session identity of the group session;

3) 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 [14];

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

5) if the MCVideo client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [16], to 4294967295;

NOTE 1: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [15].

6) if the MCVideo client wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [16], to zero;

7) shall include an Accept header field containing the application/conference-info+xml"MIME type;

8) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideo-request-uri> element set to the MCVideo group ID of the group session; and

9) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [11].

The responses to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [16], IETF RFC 4575 [57] and TS 24.229 [11].

Upon receiving a SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request the MCVideo client:

1) shall handle the request according to IETF RFC 6665 [16] and IETF RFC 4575 [57]; and

2) may display the current state information to the MCVideo client based on the information in the SIP NOTIFY request body.

When needed the MCVideo client shall terminate the subscription and indicate it terminated according to IETF RFC 6665 [16].

NOTE 2: The contents of the received SIP NOTIFY request body is specified in clause 6.3.3.4.

[TS 24.281, clause 9.2.1.2.3.1]

When an MCVideo client wants to leave the MCVideo session that has been established using on-demand session, the MCVideo client shall follow the procedures as specified in clause 6.2.4.1.

6.1.3.1.3 Test description

6.1.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.1.3.1.3.2 Test procedure sequence

Table 6.1.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 MCVideo On-demand Pre-arranged Group Call using, Automatic Commencement Mode, with request for implicit Transmission Control.

(NOTE 1)

2

Check: Does the UE (MCVideo Client) correctly perform test procedure ‘MCVideo CO session establishment/modification without provisional responses other than 100 Trying’ as described in TS 36.579-1 [2] Table 5.3B.1.3-1 to establish an MCVideo On-demand Pre-arranged Group Call, Automatic Commencement Mode, with implicit Transmission Control?

1

3

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

(NOTE 1)

1

P

4

Make the MCVideo User request to subscribe to the conference event package for the ongoing group call to receive the current status and later notification.

(NOTE 1)

5-8

Check: Does the UE (MCVideo Client) correctly perform steps 2 to 5 of the test procedure MCX Subscription and Notification as described in TS 36.579-1 [2] Table 5.3.29.3-1 to subscribe to the conference event package for the ongoing group call to receive the current status and later notification?

2

9

The SS (MCVideo Server) sends conference event package notification update via a SIP NOTIFY message.

<–

SIP NOTIFY

10

Check: Does the UE (MCVideo Client) send a SIP 200 (OK) in response to the SIP NOTIFY message?

–>

SIP 200 (OK)

2

P

11

Make the MCVideo User request to terminate the subscription to the conference event package.

(NOTE 1)

12

Check: Does the UE (MCVideo Client) send a SIP SUBSCRIBE message with the Expires header field set to 0?

–>

SIP SUBSCRIBE

3

P

13

The SS (MCVideo Server) responds with a SIP 200 (OK) message.

<–

SIP 200 (OK)

14

Make the MCVideo User end the on-demand group call. (NOTE 1)

15

Check: Does the UE (MCVideo Client) perform Generic Test Procedure for MCX CO call release as described in TS 36.579-1 [2] Table 5.3.10.3-1 to end the on-demand group call?

4

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

6.1.3.1.3.3 Specific message contents

Table 6.1.3.1.3.3-1: SIP INVITE (Step 2, Table 6.1.3.1.3.2-1; Step 2, TS 36.579-1 [2] Table 5.3B.1.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.5.1-1

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

SDP message

MIME-part-headers

Content-Type

"application/sdp"

MIME-part-body

SDP Message as described in Table 6.1.3.1.3.3-2

MIME body part

MCVideo Info

MIME-part-headers

Content-Type

"application/vnd.3gpp.mcvideo-info+xml"

MIME-part-body

MCVideo-Info as described in Table 6.1.3.1.3.3-3

Table 6.1.3.1.3.3-2: SDP in SIP INVITE (Table 6.1.3.1.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.1-2, conditions FIRST_SDP_FROM_UE, INITIAL_SDP_OFFER, IMPLICIT_GRANT_REQUESTED

Table 6.1.3.1.3.3-3: MCVideo-Info in SIP INVITE (Table 6.1.3.1.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-2, conditions GROUP-CALL, INVITE_REFER

Table 6.1.3.1.3.3-4: SIP 200 (OK) (Step 2, Table 6.1.3.1.3.2-1; Step 4, TS 36.579-1 [2] Table 5.3B.1.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.17.1.2-1, condition INVITE-RSP

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

SDP message

MIME-part-header

MIME-part-body

SDP as described in Table 6.1.3.1.3.3-5

Table 6.1.3.1.3.3-5: SDP in SIP 200 (OK) (Table 6.1.3.1.3.3-4)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.2-2, conditions FIRST_SDP_FROM_SS, SDP_ANSWER, IMPLICIT_GRANT_REQUESTED

Table 6.1.3.1.3.3-6: SIP SUBSCRIBE (Step 5, Table 6.1.3.1.3.2-1; Step 2, TS 36.579-1 [2] Table 5.3.29.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.14-1

Information Element

Value/remark

Comment

Reference

Condition

Request-Line

Request-URI

The MCVideo session identity of the group session

The public service identity identifying the originating participating MCVideo function serving the MCVideo user

TS 24.281 [26] clause 9.2.3.2

Accept-Contact

ac-value

feature-param

"+g.3gpp.icsi-ref=urn:urn-7:3gpp-service.ims.icsi.mcptt"

TS 24.281 [26] clause 9.2.3.2

req-param

"require"

TS 24.281 [26] clause 9.2.3.2

explicit-param

"explicit"

TS 24.281 [26] clause 9.2.3.2

Expires

value

"4294967295"

TS 24.281 [26] clause 9.2.3.2

Accept

media-range

"application/pidf+xml"

not present

media-range

"application/conference-info+xml "

TS 24.281 [26] clause 9.2.3.2

Message-body

MIME body part

MCVideo Info

MIME-part-body

MCVideo-Info as described in Table 6.1.3.1.3.3-7

Table 6.1.3.1.3.3-7: MCVideo-Info in SIP SUBSCRIBE (Table 6.1.3.1.3.3-6)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-1

Information Element

Value/remark

Comment

Reference

Condition

mcpttinfo

mcptt-Params

mcptt-request-uri

Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCVideo_Group_A_ID

The URI of the group

TS 24.281 [26] clause 9.2.3.2

NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-2A

Table 6.1.3.1.3.3-8: SIP 200 (OK) (Steps 6, 12, Table 6.1.3.1.3.3-1; Step 3, TS 36.579-1 [2] Table 5.3.29.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.17.1.2-1 condition SUBSCRIBE-RSP

Table 6.1.3.1.3.3-9: SIP NOTIFY (step 7, Table 6.1.3.1.3.2-1; Step 4, TS 36.579-1 [2] Table 5.3.29.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1

Information Element

Value/remark

Comment

Reference

Condition

P-Asserted-Identity

addr-spec

user-info and host

tsc_MCVideo_PublicServiceId_A

TS 24.281 [26] clause 6.3.3.4

Event

event-type

"conference"

TS 24.281 [26] clause 6.3.3.4

Expires

value

"3600"

3600 seconds

TS 24.281 [26] clause 6.3.3.4

P-Preferred-Service

Service-ID

"urn:urn-7:3gpp-service.ims.icsi.mcptt"

TS 24.281 [26] clause 6.3.3.4

Message-body

MIME body part

MCVideo Info

MIME-part-body

MCVideo-Info as described in Table 6.1.3.1.3.3-10

MIME body part

Conference-Info

MIME-part-body

Conference-Info as described in Table 6.1.3.1.3.3-11

Table 6.1.3.1.3.3-10: MCVideo-Info in SIP NOTIFY (Table 6.1.3.1.3.3-9)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.2-2, condition GROUP-CALL

Information Element

Value/remark

Comment

Reference

Condition

mcpttinfo

mcptt-Params

mcptt-calling-user-id

not present

Table 6.1.3.1.3.3-11: Conference-Info in SIP NOTIFY (Table 6.1.3.1.3.3-9)

Derivation Path: TS 24.281 [26] clause 6.3.3.4

Information Element

Value/remark

Comment

Reference

Condition

conference-info

entity

Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCVideo_Group_A_ID

The URI of the group

user

entity

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCVideo_ID_User_A

endpoint

entity

status

"connected"

user

entity

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCVideo_ID_User_B

endpoint

entity

status

"connected"

user

entity

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCVideo_ID_User_C

endpoint

entity

status

"connected"

NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.2-2A

Table 6.1.3.1.3.3-12: SIP NOTIFY (step 9, Table 6.1.3.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1

Information Element

Value/remark

Comment

Reference

Condition

P-Asserted-Identity

addr-spec

user-info and host

tsc_MCVideo_PublicServiceId_A

TS 24.281 [26] clause 6.3.3.4

Event

event-type

"conference"

TS 24.281 [26] clause 6.3.3.4

Expires

value

"3600"

3600 seconds

TS 24.281 [26] clause 6.3.3.4

P-Preferred-Service

Service-ID

"urn:urn-7:3gpp-service.ims.icsi.mcptt"

TS 24.281 [26] clause 6.3.3.4

Message-body

MIME body part

MCVideo Info

MIME-part-body

MCVideo-Info as described in Table 6.1.3.1.3.3-10

MIME body part

Conference-Info

MIME-part-body

Conference-Info as described in Table 6.1.3.1.3.3-13

Table 6.1.3.1.3.3-13: Conference-Info in SIP NOTIFY (Table 6.1.3.1.3.3-12)

Derivation Path: TS 24.281 [26] clause 6.3.3.4

Information Element

Value/remark

Comment

Reference

Condition

conference-info

entity

Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCVideo_Group_A_ID

The URI of the group

user

entity

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCVideo_ID_User_A

endpoint

entity

status

"connected"

user

entity

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCVideo_ID_User_B

endpoint

entity

status

"connected"

user

entity

Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCVideo_ID_User_C

endpoint

entity

status

"disconnected"

NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.2-2A

Table 6.1.3.1.3.3-14: SIP SUBSCRIBE (step 12, Table 6.1.3.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.14-1

Information Element

Value/remark

Comment

Reference

Condition

Request-Line

Request-URI

The MCVideo session identity of the group session

The public service identity identifying the originating participating MCVideo function serving the MCVideo user

TS 24.379 [9] clause 10.1.3.2

Accept-Contact

ac-value

feature-param

"+g.3gpp.icsi-ref=urn:urn-7:3gpp-service.ims.icsi.mcptt"

TS 24.379 [9] clause 10.1.3.2

req-param

"require"

TS 24.379 [9] clause 10.1.3.2

explicit-param

"explicit"

TS 24.379 [9] clause 10.1.3.2

Expires

value

"0"

TS 24.379 [9] clause 10.1.3.2

Accept

media-range

"application/pidf+xml"

not present

media-range

"application/conference-info+xml "

TS 24.379 [9] clause 10.1.3.2

Message-body

MIME body part

MCVideo Info

MIME-part-body

MCVideo-Info as described in Table 6.1.3.1.3.3-7

Table 6.1.3.1.3.3-15: SIP BYE (step 15, Table 6.1.3.1.3.2-1; Step 1, TS 36.579-1 [2] Table 5.3.10.3-1)

Derivation Path: TS 36.579-1, Table 5.5.2.2.1-1, condition MO_CALL