…

2
(NOTE 3)

GBR

4

150 ms
(NOTE 1, NOTE 11)

10^-3

Conversational Video (Live Streaming)

…

67
(NOTE 3, NOTE 12)

1.5

100 ms
(NOTE 1,
NOTE 10)

10^-3

Mission Critical Video user plane

…

69
(NOTE 3, NOTE 9, NOTE 12)

0.5

60 ms
(NOTE 7, NOTE 8)

10^-6

Mission Critical delay sensitive signalling (e.g., MC-PTT signalling)

…

…

NOTE 3: This QCI is typically associated with an operator controlled service, i.e., a service where the SDF aggregate’s uplink / downlink packet filters are known at the point in time when the SDF aggregate is authorized. In case of E-UTRAN this is the point in time when a corresponding dedicated EPS bearer is established / modified.

…

NOTE 9: It is expected that QCI-65 and QCI-69 are used together to provide Mission Critical Push to Talk service (e.g., QCI-5 is not used for signalling for the bearer that utilizes QCI-65 as user plane bearer). It is expected that the amount of traffic per UE will be similar or less compared to the IMS signalling.

…

NOTE 12: This QCI value can only be assigned upon request from the network side. The UE and any application running on the UE is not allowed to request this QCI value.

…

Service n°3:

MCS Group configuration data

No

Service n°6:

MCData UE configuration data

No

Service n°7:

MCData user profile data

No

Service n°8:

MCData service configuration data

No

Service n°9:

MCVideo UE configuration data

No

Service n°10:

MCVideo user profile data

No

Service n°11:

MCVideo service configuration data

No

MCS Group configuration data

’82’

Not present.

MCData UE configuration data

’85’

Not present.

MCData user profile data

’86’

Not present.

MCData service configuration data

’87’

Not present.

MCVideo UE configuration data

’88’

Not present.

MCVideo user profile data

’89’

Not present.

MCVideo service configuration data

‘8A’

Not present.

ADD_IMS

true if PDN CONNECTIVITY REQUEST is for IMS

ADD_MCX

true if PDN CONNECTIVITY REQUEST is for MCX

U – S

Message

1

Switch the UE on.

–

–

–

–

2-3

Steps 2-3 as specified in TS 36.508 [18], subclause 4.5.2 ‘UE Registration (State 2)’ take place.

–

–

–

–

4

The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST.

NOTE: Verdict shall be assigned here only if the PDN CONNECTIVITY REQUEST contained APN for MCVideo services.

–>

RRC: RRCConnectionSetupComplete

NAS: ATTACH REQUEST

NAS: PDN CONNECTIVITY REQUEST

1

P

5-15

Steps 5-15 as specified in TS 36.508 [18], subclause 4.5.2 ‘UE Registration (State 2) take place.

–

–

–

–

–

EXCEPTION: In parallel to the event described in step 16 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane as defined in TS 36.508 [6] clause 4.5A.1 takes place.

–

–

–

–

–

EXCEPTION: IF the UE is configured to register for MCX as first PDN during initial registration, THEN in parallel to the event described in step 16 below the events described in table 13.1.23.3.2-3 take place.

–

–

1

P

–

EXCEPTION: IF the UE is configured to register for IMS as first PDN during initial registration, THEN in parallel to the event described in steps 16 below the generic procedure for IMS signalling in the U-plane specified in TS 36.508 clause 4.5A.3 takes place if requested by the UE

–

–

–

–

16

This message includes the ATTACH COMPLETE message. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE.

IF the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT confirmed the establishment of a default bearer for MCVideo services THEN set mcvideo_bearer_established=TRUE.

NOTE: Verdict shall be assigned here only if the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT was for a default bearer for MCVideo services.

–>

RRC: ULInformationTransfer

NAS: ATTACH COMPLETE

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

1

P

–

EXCEPTION: Depending on the UE capability step 17a1-17b1 may be performed 1 or 2 times. IF it is performed 2 times THEN they can happen in parallel to one another.

(NOTE 1)

–

–

–

–

17a1

Start Wait_timer=10 sec

–

–

–

–

17a2

The generic procedure for UE establishing additional PDN connectivity as specified in Table 13.1.23.3.2-2 takes place.

(NOTE 2)

Stop Wait_timer if running upon receipt of the first message.

Re-start Wait_timer at the completion of the procedure.

–

–

–

–

17b1

Wait_timer expires.

–

–

–

–

18

The SS transmits an RRCConnectionRelease message.

<–

RRC: RRCConnectionRelease

–

EXCEPTION: IF the UE is not configured to register for MCX automatically during initial registration, and consequently no PDN for MCX services was established during the registration THEN steps 19 to 27 take place.

–

–

–

–

19

Make the UE user start the MCVideo application.

(NOTE 3)

–

–

–

–

20

The UE transmits an RRCConnectionRequest message.

–>

RRC: RRCConnectionRequest

–

–

21

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

–

–

22

The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.

–>

RRC: RRCConnectionSetupComplete

NAS: SERVICE REQUEST

–

–

23

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

–

–

24

The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

–>

RRC: SecurityModeComplete

–

–

–

EXCEPTION: In parallel to the events described in steps 25-26, the generic procedure for UE establishing additional PDN connectivity as specified in Table 13.1.23.3.2-2 takes place.

(NOTE 2)

–

–

–

–

25

The SS configures a new data radio bearer, associated with the default EPS bearer context.

The RRCConnectionReconfiguration message is using condition SRB2-DRB(N, 0) with N being the number of PDN connectivities established during initial registration (steps 0-17).

The DRBs associated with the respective default EPS bearer context obtained during the attach procedure are established

<–

RRC: RRCConnectionReconfiguration

–

–

26

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new radio bearer, associated with the default EPS bearer context.

–>

RRC: RRCConnectionReconfigurationComplete

–

–

27

The SS transmits an RRCConnectionRelease message.

<–

RRC: RRCConnectionRelease

–

–

28

Is mcvideo_bearer_established=TRUE?

NOTE: If at this point of the message flow, there have not been a default bearer establish for MCVideo services (QCI=69) THEN a verdict FAIL shall be assigned and the test case terminated

–

–

1

P

29

Make the UE attempt an MCVideo private call, on-demand Automatic Commencement Mode.

(NOTE 3)

–

–

–

–

30

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘ mo-Data ‘.

–>

RRCConnectionRequest

–

–

31

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

–

–

32

The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.

–>

RRC: RRCConnectionSetupComplete

NAS: SERVICE REQUEST

–

–

33

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

–

–

34

The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

–>

RRC: SecurityModeComplete

–

–

35

The SS configures a new data radio bearer, associated with the default EPS bearer context.

The RRCConnectionReconfiguration message is using condition SRBn-DRB(1, 0) as specified in TS 36.508 [6] clause 4.8.2.2.1. The DRBn associated with default EPS bearer context for the PDN established for the MCVideo services and obtained during the registration is established.

<–

RRC: RRCConnectionReconfiguration

–

–

–

EXCEPTION: In parallel to the events described in step 36 below, the events described in table 13.1.23.3.2-4, steps 1-4 take place.

–

–

–

–

36

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer context.

–>

RRC: RRCConnectionReconfigurationComplete

–

–

–

EXCEPTION: Steps 37a1 to 37b1 describe behaviour that depends on pc_Use_QCI_67 parameter "true" or "false".

The “lower case letter” identifies a step sequence that takes place when one or the other is the case.

–

–

–

–

37a1

IF pc_Use_QCI_67, THEN the SS configures a new RLC-UM data radio bearer, associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #10 (QCI 67) according to 36.508 [24], table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

NOTE 1: The same MCVideo PDN address is applicable because the linked EPS bearer ID refers to the default EBC.

NOTE 2: The network initiates the creation of a dedicated bearer to transport the video media, see TS 36.579-1 [59], subclause 5.4.1A.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

–

37b1

ELSE IF NOT pc_Use_QCI_67, THEN the SS configures a new RLC-UM data radio bearer, associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #3 (QCI 2) according to 36.508 [24], table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

NOTE 1: The same MCVideo PDN address is applicable because the linked EPS bearer ID refers to the default EBC.

NOTE 2: The network initiates the creation of a dedicated bearer to transport the video media, see TS 36.579-1 [59], subclause 5.4.1A.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

–

38

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for MCVideo services.

–>

RRC: RRCConnectionReconfigurationComplete

2

P

39

Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message?

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

2

P

40

Make the UE (MCVideo User) request termination of the MCVideo private call.

(NOTE 3)

–

–

–

–

41

Steps 5-6 described in table 13.1.23.3.2-4 take place.

–

–

–

–

42

The SS transmits an RRCConnectionRelease message.

<–

RRC: RRCConnectionRelease

–

–

NOTE 1: The assumptions for the PDN support of a MCVideo capable UE, including the default EPS bearer context QCI requirements in regard to the different PDN are described in TS 36.579-1 [59], subclause 5.4.1A.

NOTE 2: SRB numbering shall take into account the SRBs already established.

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

U – S

Message

1

The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN.

NOTE: Verdict shall be assigned here only if the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT was for a default bearer for MCVideo services.

–>

RRC: ULInformationTransfer

NAS: PDN CONNECTIVITY REQUEST

1

P

2

The SS configures a new data radio bearer, associated with the additional default EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

–

3

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of additional default bearer.

–>

RRC: RRCConnectionReconfigurationComplete

–

–

–

EXCEPTION: In parallel to the event described in step 4 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 clause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

–

–

–

EXCEPTION: IF ADD_IMS THEN in parallel to the event described in step 4 below the generic procedure for IMS signalling in the U-plane specified in TS 36.508 clause 4.5A.3 takes place if requested by the UE.

–

–

–

–

–

EXCEPTION: IF ADD_MCX THEN in parallel to the event described in step 4 below the SIP registration for MCVideo as specified in table 13.1.23.3.2-3 takes place.

–

–

–

–

4

The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message.

IF the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT confirmed the establishment of a default bearer for MCVideo services THEN set mcvideo_bearer_established=TRUE.

NOTE: Verdict shall be assigned here only if the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT was for a default bearer for MCVideo services.

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

1

P

U – S

Message

–

EXCEPTION: In parallel to the event described in steps 1 to 4 below the MCVideo user authentication as specified in TS 36.579-1 [59], table 5.3.2.3-1 takes place.

–

–

–

–

1

The UE sends initial registration for IMS services.

–>

SIP REGISTER

–

–

2

The SS responds with a valid AKAv1-MD5 authentication challenge and security mechanisms supported by the network.

<–

SIP 401 Unauthorized

–

–

3

The UE completes the security negotiation procedures, sets up a temporary set of SAs and uses those for sending another REGISTER with AKAv1-MD5 credentials.

–>

SIP REGISTER

–

–

4

The SS responds with 200 OK.

<–

SIP 200 OK

–

–

U – S

Message

1

The UE sends an initial SIP INVITE request requesting the establishment of an MCVideo call.

–>

SIP INVITE

–

–

2

The SS sends SIP 100(Trying).

<–

SIP 100 (Trying)

–

–

3

The SS sends SIP 200 (OK).

<–

SIP 200 (OK)

–

–

4

The UE sends a SIP ACK in response to the SIP 200 (OK)

–>

SIP ACK

–

–

5

The UE sends a SIP BYE request.

–>

SIP BYE

–

–

6

The SS sends SIP 200 (OK).

<–

SIP 200 (OK)

–

–

Information Element

Value/remark

Comment

Condition

Access point name

px_MCX_APN (TS 36.579-5 [63])

The APN used for connecting for MCVideo services

ADD_MCX

Not present or any allowed value

This is the case for Internet, IMS or default APN.

It is assumed that the UE is NOT configured to expect MCVideo as default APN.

Information Element

Value/remark

Comment

Condition

EPS bearer identity

‘0101’B

arbitrary value used for PDN connectivity being maintained during the test case

ADD_IMS

‘0110’B

ADD_MCX

‘1100’B

EPS QoS

See Reference default EPS bearer context #3 (QCI=69) in TS 36.508 [6], table 6.6.1-1

ADD:MCX

Negotiated QoS

See Reference default EPS bearer context #3 (QCI=69) in TS 36.508 [6], table 6.6.1-1

ADD:MCX

Radio priority

See Reference default EPS bearer context #3 (QCI=69) in TS 36.508 [6], table 6.6.1-1

ADD:MCX

Protocol configuration options

FFS

NOTE 1: Content of the message does not provide full details for the cases of IMS and Internet – the relevant conditions should apply depending on the type requested e.g. condition IMS_PDN_ConnEstab for PDN1_IMS and NOT IMS_PDN_ConnEstab, etc.

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Procedure transaction identity

0

"No procedure transaction identity assigned"

Linked EPS bearer identity

5

SS re-uses the EPS bearer identity of the default EPS bearer context.

EPS QoS

According to reference dedicated EPS bearer context #10, TS 36.508 [6], table 6.6.2-1

QCI 67

TFT

According to reference dedicated EPS bearer context #10, TS 36.508 [6], table 6.6.2-1

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Procedure transaction identity

0

"No procedure transaction identity assigned"

Linked EPS bearer identity

5

SS re-uses the EPS bearer identity of the default EPS bearer context.

EPS QoS

According to Reference dedicated EPS bearer context in Table 13.1.23.3.3-5

Reference dedicated EPS bearer context #3 (QCI 2)

TFT

According to Reference dedicated EPS bearer context Table 13.1.23.3.3-5

Reference dedicated EPS bearer context #3 (QCI 2)

Parameters

Reference dedicated EPS bearer context #3

Comment

Condition

Linked EPS bearer identity

Reference default EPS bearer #3

Packet filters

4, 5, 10

Packet filter #4 for audio stream, packet filter #5 for video stream, packet filter #10 for transmission control messages.

Traffic Class

–

Delivery Order

–

Delivery of erroneous SDU

–

Maximum SDU size

–

Maximum bit rate for uplink

–

Maximum bit rate for downlink

–

Residual BER

–

SDU error ratio

–

Transfer delay

–

Traffic Handling priority

–

Guaranteed bit rate for uplink

–

Guaranteed bit rate for downlink

–

Signalling Indication

–

Source Statistics Descriptor

–

Maximum bit rate for downlink (extended)

–

Guaranteed bit rate for downlink (extended)

–

Maximum bit rate for uplink (extended)

–

Guaranteed bit rate for uplink (extended)

–

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

Procedure transaction identity

0

"No procedure transaction identity assigned"

Information Element

Value/remark

Comment

Reference

Condition

mcvideo-UE-configuration

common

MCVideo-Group-Call

Not present

on-network

Not present

Information Element

Value/remark

Comment

Reference

Condition

mcptt-user-profile

OnNetwork

MCVideoGroupInfo

Not present

MaxAffiliationsN2

Not present

OffNetwork

Not present

cp:ruleset

cp:rule

cp:id attribute

"rule1"

cp:actions

allow-create-group-broadcast- group

"false"

allow-create-user-broadcast-group

"false"

allow-request-affiliated-groups

"false"

allow-request-to-affiliate-other-users

"false"

allow-recommend-to-affiliate-other-users

"false"

allow-regroup

"false"

allow-presence-status

"false"

allow-request-presence

"false"

allow-override-group-call

"false"

allow-emergency-group-call

"false"

allow-cancel-group-emergency

"false"

allow-imminent-peril-call

"false"

allow-cancel-imminent-peril

"false"

allow-off-network-group-call-change-to-emergency

"false"

Information Element

Value/remark

Comment

Reference

Condition

service configuration

common

broadcast-group

Not present

on-network

signalling-protection

Not present

off-network

Not present

Information Element

Value/remark

Comment

Reference

Condition

Require

Not present

option-tag

Not present

Proxy-Require

Not present

option-tag

Not present