5.4 Generic test procedures for UE operation over E-UTRA/EPC

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

5.4.1 General

The purpose of the procedures specified in the following clauses is to facilitate test description by providing procedure sequences which can be referred from the relevant test cases specified e.g. in 3GPP TS 36.579-2 [2], 3GPP TS 36.579-3 [3], 3GPP TS 36.579-6 [84], 3GPP TS 36.579-7 [85].

The intention is, wherever possible, that E-UTRA/EPC signalling and initial conditions should not be provided in the test descriptions rather should be referred to the procedure steps described in the generic procedures below, whereas, the MCS SIP signalling and initial conditions when relevant for the test purposes shall be explicitly provided in the tests description itself.

Throughout the generic test procedures E-UTRA/EPC behaviour is denoted as "SS" for the System Simulator simulating the NWK side of the communication, and, "UE" for the Implementation Under Test (IUT), whereas the MCPTT/MCVideo/MCData relevant behaviour is denoted as "SS (MCPTT/MCVideo/MCData server)" and "UE (MCPTT/MCVideo/MCData client)"/"UE (MCPTT/MCVideo/MCData user)" respectively. ProSe related SS behaviour when the SS simulates an UE device is denoted e.g. as "SS-UE1".

Depending on the TS 36.579-5[5] test model being used, the E-UTRA/EPC signalling is:

– MCX EUTRA test model: normative.

– MCX IPCAN test model: informative, unless specifically specified otherwise elsewhere.

5.4.1A UE APN/PDN support assumptions

A MCPTT (or in general Mission Critical Services) capable UE, depending on implementation/deployment, may be provided with up to 3 MCPTT related APN: An APN utilised by the MCPTT service including the MCPTT service APN for the SIP-1 reference point, an MC common core services APN for the HTTP-1 reference point and a MC identity management service APN for the CSC-1 reference point (see TS 23.179 [8], clause 5.2.9).

To limit the test specification complexity utilisation of single APN/PDN to be used for all 3 MCPTT services is assumed and only 2 QCIs are used for the bearers established in regard to the PDN:

1. MCPTT (QCI=69 for signalling bearer, QCI=65 for voice)

NOTE 1: It should be noted that the core specs impose a requirement that the QCI value 8 or better shall be used for the EPS bearer that transports HTTP-1 reference point messaging. Using a single APN and having for the EPS bearer QCI=69 will satisfy this.

NOTE 2: Void.

In addition to the MCPTT relevant APN, a MCPTT (or in general Mission Critical Services) capable UE may support 2 additional different APNs for which different PDNs each with its specific QCI:

2. Internet (QCI=9)

3. IMS (VOLTE QCI=5 for signalling bearer, QCI=1 for voice call)

This will result in the need the MCPTT tests to be able to handle a 3 APNs and different PDNs.

NOTE 3: It should be noted that, handling IMS and MCPTT with one APN is theoretically possible but may have undesirable implications e.g. VoLTE signalling could delay MCPTT signalling therefore the assumption is that such implementations will be undesirable and unlikely.

Consequently, for the IMS and MCPTT it should be assumed that the UE will do 2 different registrations, i.e. for each of them there will be a separate IP connection (different IP addresses at the UE and the SS).

Depending on UE configuration PDN connectivities for the up-to three PDNs may be established. There are two major scenarios:

1. The MCX PDN connectivity gets established automatically after switch-on during the initial registration procedure. In addition the UE may establish PDN connectivities to the IMS PDN and/or the internet PDN. The connectivity to these PDNs may be requested in any order. There can be 1, 2 or 3 PDNs.

2. The UE requests PDN connectivities for IMS and/or internet but not for MCPTT. If IMS and internet are requested, it may be in any order. Establishment of the MCX PDN connectivity is triggered after the initial registration in a separate procedure. There can be 2 or 3 PDNs in total.

To serve the above scenarios the following parameters are defined in TS 36.579-5 [5]:

– px_MCX_InitialRegistration_TypeOfPDN1:
First PDN registered during initial registration (either ‘ims’ or ‘internet’ or ‘mcx’)

– px_MCX_InitialRegistration_TypeOfPDN2:
Second PDN registered during initial registration; in addition to ‘ims’ or ‘internet’ or ‘mcx’ it may be ‘none’ to indicate that there is no second PDN connectivity requested by the UE during initial registration.

– px_MCX_InitialRegistration_TypeOfPDN3:
Third PDN registered during initial registration; in addition to ‘ims’ or ‘internet’ or ‘mcx’ it may be ‘none’ to indicate that there is no third PDN connectivity requested by the UE during initial registration.

The type of the parameters is a TTCN-3 enumerated type with values ‘ims’,‘internet’, ‘mcx’ and ‘none’.

In addition there is the parameter px_AccessPointName in TS 36.523-3 [74] which is used as default APN, i.e. for a PDN for which the UE does not provide an APN (NOTE: Any, but only one, of the three PDNs can be the one with default APN).

In regard to the MCPTT the following shall be also taken into account

– If the PDN connection established during the initial attach by the UE is to an APN other than the MCPTT service APN, then prior to user authentication, the UE shall establish another PDN connection to the MCPTT service APN. PDN connection establishment can also be caused by a SIP registration request for MCPTT. The QCI value of 69 shall be used for the EPS bearer that transports SIP-1 reference point messaging. It is used for SIP signalling.

– For the MCPTT service APN, the MCPTT UE does not activate EPS bearers for media streams.

– The network initiates the creation of a dedicated bearer to transport the voice media. The dedicated bearer for Conversational Voice utilises the standardised QCI value of 65. The network, utilising dynamic PCC, creates no more than one dedicated bearer for voice media (the UE is required to support at minimum one UM bearer which is used for MCPTT voice).

Editor’s Note: The requirements in regard to MCVideo and MCData are FFS.

5.4.2 Generic Test Procedure for MCPTT UE registration

5.4.2.1 Initial conditions

System Simulator:

– SS (MCPTT server)

– E-UTRA related parameters are set to the default parameters for the basic single cell environment, as defined in TS 36.508 [6] clause 4.4, unless otherwise specified in the test case. Requirements in regard to the PLMN which the simulated Cell(s) belongs to are specified in the test case using the present procedure.

IUT:

– UE (MCPTT client)

– The UE is MCPTT capable. The MCPTT preconditions required for initiation of MCPTT service authorization for the MCPTT client and the MCPTT service are specified in the test cases.

– The test USIM set as defined in clause 5.5.10 is inserted.

– The UE shall be switched off.

5.4.2.2 Definition of system information messages

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

5.4.2.3 Procedure

Table 5.4.2.3-1: E-UTRA/EPC signalling for UE registration

St

Procedure

Message Sequence

U – S

Message

0

Switch the UE on.

1

Void

2

UE transmits an RRCConnectionRequest message.

–>

RRC: RRCConnectionRequest

3

SS transmits an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

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 1)

–>

RRC: RRCConnectionSetupComplete

NAS: ATTACH REQUEST

NAS: PDN CONNECTIVITY REQUEST

5

The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.

<–

RRC: DLInformationTransfer

NAS: AUTHENTICATION REQUEST

6

The UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication.

–>

RRC: ULInformationTransfer

NAS: AUTHENTICATION RESPONSE

7

The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security.

<–

RRC: DLInformationTransfer

NAS: SECURITY MODE COMMAND

8

The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration.

–>

RRC: ULInformationTransfer

NAS: SECURITY MODE COMPLETE

EXCEPTION: Steps 9a1 to 9a2 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that take place if the UE has ESM information which needs to be transferred.

9a1

IF the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the SS transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<–

RRC: DLInformationTransfer

NAS: ESM INFORMATION REQUEST

9a2

The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.

–>

RRC: ULInformationTransfer

NAS: ESM INFORMATION RESPONSE

10

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

11

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

–>

RRC: SecurityModeComplete

12

The SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure.

<–

RRC: UECapabilityEnquiry

13

The UE transmits a UECapabilityInformation message to transfer UE radio access capability.

–>

RRC: UECapabilityInformation

14

The SS transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to TS 36.508 [6] clause 4.8.2.2.1.1.

This message includes the ATTACH ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT. (NOTE 1)

<–

RRC: RRCConnectionReconfiguration

NAS: ATTACH ACCEPT

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

15

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

–>

RRC: RRCConnectionReconfigurationComplete

EXCEPTION: In parallel to the event described in steps 16 and 16A 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 steps 16 and 16Abelow the events described in table 5.4.2.3-2 take place.

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 and 16A 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.

–>

RRC: ULInformationTransfer

NAS: ATTACH COMPLETE

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

EXCEPTION: Depending on the UE capability step 16A may be performed 0, 1 or 2 times. (NOTE 1)

16A

The E-UTRA/EPC signalling for establishment of an additional PDN connectivity according to table 5.4.2.3-1A takes place

17

The SS transmits an RRCConnectionRelease message.

<–

RRC: RRCConnectionRelease

EXCEPTION: IF the UE is not configured to register for MCX during initial registration, THEN steps 18 to 27 take place.

18

Make the UE user request MCPTT service authorisation/configuration.

NOTE 2

19

The UE transmits an RRCConnectionRequest message.

–>

RRCConnectionRequest

20

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

21

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

22

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

23

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

–>

RRC: SecurityModeComplete

24

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

25

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

–>

RRC: RRCConnectionReconfigurationComplete

26

The E-UTRA/EPC signalling for establishment of an additional PDN connectivity according to table 5.4.2.3-1A takes place

27

The SS transmits an RRCConnectionRelease message.

<–

RRC: RRCConnectionRelease

NOTE 1: The assumptions for the PDN support of a MCPTT capable UE, including the default EPS bearer context QCI requirements in regard to the different PDN are described in 5.4.1A.

NOTE 2: This will start a 5 stage process. The first stage involves MCPTT User Authentication and includes Steps 3a1 through 10 of Table 5.3.2.3-1. The end result of the first stage is the MCPTT Client receives 3 tokens: access token, ID token, and refresh token.

Table 5.4.2.3-1A: E-UTRA/EPC signalling for establishment of an additional PDN connectivity

St

Procedure

Message Sequence

U – S

Message

1

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

–>

RRC: ULInformationTransfer

NAS: PDN CONNECTIVITY REQUEST

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 MCPTT as specified in table 5.4.2.3-2 takes place

4

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

Condition

Explanation

ADD_IMS

true if PDN CONNECTIVITY REQUEST is for IMS

ADD_MCX

true if PDN CONNECTIVITY REQUEST is for MCX

Table 5.4.2.3-2: SIP registration for MCPTT

St

Procedure

Message Sequence

U – S

Message

EXCEPTION: In parallel to the event described in steps 1 to 4 below the MCPTT user authentication as according to table 5.3.2.3-1 take 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

5-6

Void

6A

The generic procedure for MCPTT Service Authorization as specified in table 5.3.2.3-2 takes place

7

The SS (MCPTT server) sends SIP MESSAGE for configuring Location Info reporting.

<–

SIP MESSAGE

8

The UE (MCPTT client) responds with SIP 200 (OK)

–>

SIP 200 (OK)

5.4.2.4 Specific message contents

All specific E-UTRA/EPC signalling message contents shall be referred to TS 36.508 [6] clause 4.6 and 4.7.

The MCPTT relevant SIP message contents, Table 5.4.2.3-2, are specified in the present document clause 5.5.2, except for the following messages.

Table 5.4.2.4-1: SIP MESSAGE (step 7)

Derivation Path: Table 5.5.2.7.2-1 SIP MESSAGE from the SS, condition LOCATION-INFO

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCPTT Info

MIME-part-body

As described in Table 5.4.2.4-1A

Table 5.4.2.4-1A: MCPTT Info in SIP MESSAGE (Table 5.4.2.4-1)

Derivation Path: Table 5.5.3.2.2-1

Information Element

Value/remark

Comment

Reference

Condition

mcpttinfo

mcptt-Params

mcptt-calling-user-id

not present

Table 5.4.2.4-2: SIP 200 (OK) (Step 8, Table 5.4.2.3-2)

Derivation Path: Table 5.5.2.17.1.1-1

Table 5.4.2.4-3: REGISTER (Step 1, Table 5.4.2.3-2)

Derivation Path: Table 5.5.2.13-1 with condition SIP_REGISTER_INITIAL

Table 5.4.2.4-4: SIP 401 (Unauthorized) (Step 2, Table 5.4.2.3-2)

Derivation Path: Table 5.5.2.19.7-1

Table 5.4.2.4-5: REGISTER (Step 3, Table 5.4.2.3-2)

Derivation Path: Table 5.5.2.13-1

Table 5.4.2.4-6: SIP 200 (OK) (Step 4, Table 5.4.2.3-2)

Derivation Path: Table 5.5.2.17.1.2-1

5.4.2A Generic Test Procedure for MCVideo UE registration

The same as the procedure described in 5.4.2 with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo".

5.4.2B Generic Test Procedure for MCData UE registration

The same as the procedure described in 5.4.2 with the following exception(s):

– The term "MCPTT" is replaced with "MCData", and the term "call" with "communication".

5.4.3 Generic Test Procedure for MCPTT CO communication in E-UTRA

5.4.3.1 Initial conditions

System Simulator:

– SS (MCPTT server)

– SS E-UTRA related parameters are set to the default parameters for the basic single cell environment, as defined in TS 36.508 [6] clause 4.4, unless otherwise specified in the test case. Requirements in regard to the PLMN which the simulated Cell(s) belongs to are specified in the test case using the present procedure.

IUT:

– UE (MCPTT client)

– The test USIM set as defined in clause 5.5.10 is inserted.

– The UE has performed the Generic Test Procedure for MCPTT UE registration as specified in clause 5.4.2 and is in E-UTRA Registered, Idle Mode state with the MCPTT Client being active. During the attach a default EPS bearer context #3 (QCI 69) according to table 6.6.1-1, TS 36.508 [6] is established for MCPTT and SIP signalling.

NOTE 1: The assumptions for the PDN support of a MCPTT capable UE, including the default EPS bearer context QCI requirements in regard to the different PDN are described in 5.4.1A.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

5.4.3.2 Definition of system information messages

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

5.4.3.3 Procedure

Table 5.4.3.3-1: E-UTRA/EPC signalling for MCPTT CO communication

St

Procedure

Message Sequence

U – S

Message

1

Make the UE attempt an MCPTT call

2

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

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

5

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

6

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

–>

RRC: SecurityModeComplete

7

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

The RRCConnectionReconfiguration message is using condition SRB2-DRB(1, 0) as specified in TS 36.508 [6] clause 4.8.2.2.1. The DRB associated with default EPS bearer context obtained during the attach procedure is established (see Preamble).

<–

RRC: RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described below, depending on the test case, one of the generic procedures in clause 5.3 for MCPTT CO call establishment, starting with step 2, takes place

8

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

9-12

Void.

13

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 #5 (QCI 65) according to table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

NOTE 1: The same MCPTT 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 voice media see 5.4.1A.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

14

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

–>

RRC: RRCConnectionReconfigurationComplete

15

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

Table 5.4.3.3-2: Void

5.4.3.4 Specific message contents

All specific E-UTRA/EPC signalling message contents shall be referred to TS 36.508 [6] clauses 4.6 and 4.7.

5.4.3A Generic Test Procedure for MCVideo CO communication in E-UTRA

The same as the procedure described in 5.4.3 with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo".

– EPS bearer context #3 (QCI 2) according to TS 36.508 [6], table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

5.4.3B Generic Test Procedure for MCData CO communication in E-UTRA

The same as the procedure described in 5.4.3 with the following exception(s):

– The term "MCPTT" is replaced with "MCData", and the term "call" with "communication".

– EPS bearer context #[9] (QCI 70) according to TS 36.508 [6], table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

5.4.4 Generic Test Procedure for MCPTT CT communication in E-UTRA

5.4.4.1 Initial conditions

System Simulator:

– SS (MCPTT server)

– E-UTRA related parameters are set to the default parameters for the basic single cell environment, as defined in TS 36.508 [6] clause 4.4, unless otherwise specified in the test case. Requirements in regard to the PLMN which the simulated Cell(s) belongs to are specified in the test case using the present procedure.

IUT:

– UE (MCPTT client):

– The test USIM set as defined in clause 5.5.10 is inserted.

– The UE has performed the Generic Test Procedure for MCPTT UE registration as specified in clause 5.4.2 and is in E-UTRA Registered, Idle Mode state with the MCPTT Client being active. During the attach a default EPS bearer context #3 (QCI 69) according to table 6.6.1-1, TS 36.508 [6] is established for MCPTT and SIP signalling.

NOTE 1: The assumptions for the PDN support of a MCPTT capable UE, including the default EPS bearer context QCI requirements in regard to the different PDN are described in 5.4.1A.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

5.4.4.2 Definition of system information messages

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

5.4.4.3 Procedure

Table 5.4.4.3-1: E-UTRA/EPC signalling for MCPTT CT communication

St

Procedure

Message Sequence

U – S

Message

1

SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.

<–

RRC: Paging (PCCH)

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘mt-Access’.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

5

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

6

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

–>

RRC: SecurityModeComplete

7

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

The RRCConnectionReconfiguration message is using condition SRB2-DRB(1, 0) as specified in TS 36.508 [6] clause 4.8.2.2.1. The DRB associated with default EPS bearer context obtained during the attach procedure is established (see Preamble).

<–

RRC: RRCConnectionReconfiguration

8

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: In parallel to the events described below, depending on the test case, one of the generic procedures in clause 5.3 for MCPTT CT call establishment, starting with step 2, takes place

9-12

Void.

13

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 #5 (QCI 65/69) according to table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

NOTE 1: The same MCPTT 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 voice media see 5.4.1A.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

14

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

–>

RRC: RRCConnectionReconfigurationComplete

15

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

16

Void

Table 5.4.4.3-2: Void

5.4.4.4 Specific message contents

All specific E-UTRA/EPC signalling message contents shall be referred to TS 36.508 [6] clause 4.6 and 4.7.

5.4.4A Generic Test Procedure for MCVideo CT communication in E-UTRA

The same as the procedure described in 5.4.4 with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo".

– EPS bearer context #3 (QCI 2) according to TS 36.508 [6], table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

5.4.4B Generic Test Procedure for MCData CT communication in E-UTRA

The same as the procedure described in 5.4.4 with the following exception(s):

– The term "MCPTT" is replaced with "MCData", and the term "call" with "communication".

– EPS bearer context #[9] (QCI 70) according to TS 36.508 [6], table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

5.4.5 Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment

5.4.5.1 Initial conditions

System Simulator:

– SS-UE1 (MCPTT Client).

– For the underlying "transport bearer" over which the SS and the UE will communicate, the SS is behaving as SS-UE1 as defined in TS 36.508 [6], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator configured to simulate a location in the centre of Geographical area #1 and providing timing reference as defined in TS 36.508 [6] Table 4.11.2-2 scenario #1, for the assistance of E-UTRAN off-network testing.

NOTE: For operation in off-network environment, it needs to be ensured that after the UE is powered up it considers the Geographical area #1 as being one of the geographical areas set in the USIM for operation when UE is "not served by E-UTRAN".

IUT:

– UE (MCPTT client):

– The test USIM set as defined in clause 5.5.10 is inserted.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

UE state:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [6].

5.4.5.2 Definition of system information messages

N/a (out of E-UTRA coverage)

5.4.5.3 Procedure

Table 5.4.5.3-1: ProSe direct communication one-to-one out of E-UTRA coverage signalling for MCPTT CO communication-establishment

St

Procedure

Message Sequence

U – S

Message

1

Power up the UE.

2

Wait for 15 sec to allow the UE to establish that it is out of coverage and initiate scanning the frequency pre-set for ProSe communication for any activities.

3

Make the UE initiate one-to-one ProSe direct communication with the remote UE preconfigured (ProSe Layer-2 Group ID).

4

UE sends a DIRECT_COMMUNICATION_REQUEST message, IP Address Config IE set to "address allocation not supported".

–>

DIRECT_COMMUNICATION_REQUEST

5

SS-UE1 sends a DIRECT_SECURITY_MODE_COMMAND message.

<–

DIRECT_SECURITY_MODE_COMMAND

6

UE sends a DIRECT_SECURITY_MODE_COMPLETE message ciphered and integrity protected with the new security context.

–>

DIRECT_SECURITY_MODE_COMPLETE

7

SS-UE1 sends a DIRECT_COMMUNICATION_ACCEPT message.

<–

DIRECT_COMMUNICATION_ACCEPT

8

EXCEPTION: After the communication is established, an IP address configuration procedure is performed depending on what the UE has indicated in the IP Address Config IE (if it is not "address allocation not supported") in the DIRECT_COMMUNICATION_REQUEST message, and, the SS-UE1 itself indicating "address allocation not supported" in the DIRECT_COMMUNICATION_ACCEPT message.

EXCEPTION: Steps 9a1 to 9a2 describe behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that depends on the UE implementation of keepalive procedure.

9a1

UE sends a DIRECT_COMMUNICATION_KEEPALIVE message.

–>

DIRECT_COMMUNICATION_KEEPALIVE

9a2

SS-UE1 sends a DIRECT_COMMUNICATION_KEEPALIVE_ACK message.

<–

DIRECT_COMMUNICATION_KEEPALIVE_ACK

5.4.5.4 Specific message contents

Table 5.4.5.4-1: DIRECT_COMMUNICATION_ACCEPT (step 7 Table 5.4.5.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-6.

Information Element

Value/remark

Comment

Condition

IP Address Config

‘0011’B

address allocation not supported

Link Local IPv6 Address

If the UE indicated ‘address allocation not supported’ in the IP Address Config IE in the DIRECT_COMMUNICATION_REQUEST message then a link-local IPv6 address formed locally

128-bit IPv6 address

Table 5.4.5.4-2: DIRECT_SECURITY_MODE_COMMAND (step 5, Table 5.4.5.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-7.

Information Element

Value/remark

Comment

Condition

UE Security Capabilities

Set to the UE Security Capabilities received in the DIRECT_COMMUNICATION_REQUEST message

Chosen Algorithms

One of the non-null algorithms provided in UE Security Capabilities (i.e. different to EIA0 (null integrity protection algorithm)/EEA0 (null ciphering algorithm))

MSB of KD ID

The MSB of KD ID of the new KD

KD Freshness

Not included

GPI

Not included

User Info {

Type of User Info

IMSI

Odd/even indication

Reflecting the number of digits in the IMSI

Identity digits

A value different to the IMSI of the UE

}

Table 5.4.5.4-3: DIRECT_SECURITY_MODE_COMPLETE (step 6, Table 5.4.5.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-8.

Information Element

Value/remark

Comment

Condition

LSB of KD ID

Not included

Table 5.4.5.4-4: DIRECT_COMMUNICATION_KEEPALIVE (step 9a1, Table 5.4.5.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-9.

Information Element

Value/remark

Comment

Condition

Keepalive Counter

0

Maximum Inactivity Period

Any allowed value

5.4.6 Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment

5.4.6.1 Initial conditions

System Simulator:

– SS-UE1 (MCPTT Client).

– For the underlying "transport bearer" over which the SS and the UE will communicate, the SS is behaving as SS-UE1 as defined in TS 36.508 [6], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator configured to simulate a location in the centre of Geographical area #1 and providing timing reference as defined in TS 36.508 [6] Table 4.11.2-2 scenario #1,for the assistance of E-UTRAN off-network testing.

NOTE: For operation in off-network environment, it needs to be ensured that after the UE is powered up it considers the Geographical area #1 as being one of the geographical areas set in the USIM for operation when UE is "not served by E-UTRAN".

IUT:

– UE (MCPTT client)

– The test USIM set as defined in clause 5.5.10 is inserted.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

UE state:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [6].

5.4.6.2 Definition of system information messages

N/a (out of E-UTRA coverage).

5.4.6.3 Procedure

Table 5.4.6.3-1: ProSe direct communication one-to-one out of E-UTRA coverage signalling for MCPTT CT communication-establishment

St

Procedure

Message Sequence

U – S

Message

1

Power up the UE.

2

Wait for 15 sec to allow the UE to establish that it is out of coverage and initiate scanning the frequency pre-set for ProSe communication for any activities.

3

SS-UE1 sends a DIRECT_COMMUNICATION_REQUEST message, IP Address Config IE set to "address allocation not supported".

<–

DIRECT_COMMUNICATION_REQUEST

4

UE sends a DIRECT_SECURITY_MODE_COMMAND message uncyphered but integrity protected with the new security context.

–>

DIRECT_SECURITY_MODE_COMMAND

5

SS-UE1 sends a DIRECT_SECURITY_MODE_COMPLETE message ciphered and integrity protected with the new security context.

<–

DIRECT_SECURITY_MODE_COMPLETE

6

UE sends a DIRECT_COMMUNICATION_ACCEPT message.

–>

DIRECT_COMMUNICATION_ACCEPT

7

EXCEPTION: After the communication is established, an IP address configuration procedure is performed depending on what the UE has indicated in the IP Address Config IE (if it is not "address allocation not supported") in the DIRECT_COMMUNICATION_REQUEST message, and, the SS-UE1 itself indicating "address allocation not supported" in the DIRECT_COMMUNICATION_ACCEPT message.

8

SS-UE1 sends a DIRECT_COMMUNICATION_KEEPALIVE message with a Keepalive Counter IE that contains the value of the keepalive counter for this link=0, and a Maximum Inactivity Period IE.

<–

DIRECT_COMMUNICATION_KEEPALIVE

9

UE sends a DIRECT_COMMUNICATION_KEEPALIVE_ACK message including the Keepalive Counter IE set to the same value as that received in the DIRECT_COMMUNICATION_KEEPALIVE message.

–>

DIRECT_COMMUNICATION_KEEPALIVE_ACK

5.4.6.4 Specific message contents

Table 5.4.6.4-1: DIRECT_COMMUNICATION_REQUEST (step 3, Table 5.4.6.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-5.

Information Element

Value/remark

Comment

Condition

User Info {

Type of User Info

IMSI

Odd/even indication

Reflecting the number of digits in the IMSI

Identity digits

A value different to the IMSI of the UE

}

IP Address Config

‘0011’B

address allocation not supported

Maximum Inactivity Period

’10 0000 0000’B

512 sec, randomly chosen to allow sufficient time for a TC which uses this procedure to be completed without need to repeat the keepalive procedure

Nonce_1

UE Security Capabilities

01111111 01111111

All but null algorithms supported

MSB of KD-sess ID

the 8 most significant bits of the KD-sess ID

KD ID

Not present

Signature

the ECCSI signature calculated with the User Info and Nonce_1 as specified in 3GPP TS 33.303 [67]

Link Local IPv6 Address

a link-local IPv6 address formed locally

Table 5.4.6.4-2: DIRECT_SECURITY_MODE_COMMAND (step 4 Table 5.4.6.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-7.

Information Element

Value/remark

Comment

Condition

MSB of KD ID

Any allowed value

KD Freshness

Not included

GPI

Not included

Signature

The ECCSI signature calculated with the User Info and Nonce_1 as specified in 3GPP TS 33.303 [67]

Encrypted Payload

The SAKKE payload generated as specified in 3GPP TS 33.303 [67].

Table 5.4.6.4-3: DIRECT_SECURITY_MODE_COMPLETE (step 5, Table 5.4.6.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-8.

Information Element

Value/remark

Comment

Condition

LSB of KD ID

16 least significant bits of KD ID

Table 5.4.6.4-4: DIRECT_COMMUNICATION_KEEPALIVE (step 8, Table 5.4.6.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-9.

Information Element

Value/remark

Comment

Condition

Keepalive Counter

0

Maximum Inactivity Period

’10 0000 0000’B

512 sec, randomly chosen to allow sufficient time for a TC which uses this procedure to be completed without need to repeat the keepalive procedure

5.4.7 Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the SS

5.4.7.1 Initial conditions

System Simulator:

– SS-UE1 (MCPTT Client).

– Same as those defined in the ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.5, or, the ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.6.

IUT:

– UE (MCPTT client)

ProSe related configuration

– Same as those defined in the ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.5, or, the ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.6.

UE state

– The UE has established ProSe direct communication one-to-one out of E-UTRA coverage using the ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.5, or, the ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.6.

5.4.7.2 Definition of system information messages

N/a (out of E-UTRA coverage).

5.4.7.3 Procedure

Table 5.4.7.3-1: ProSe direct communication one-to-one out of E-UTRA coverage signalling for MCPTT communication – release by the SS

St

Procedure

Message Sequence

U – S

Message

1

SS-UE1 sends a DIRECT_COMMUNICATION_RELEASE message with a Release Reason IE indicating ‘Direct Communication to peer UE no longer needed’.

<–

DIRECT_COMMUNICATION_RELEASE

2

UE sends a DIRECT_COMMUNICATION_RELEASE_ACCEPT message.

–>

DIRECT_COMMUNICATION_RELEASE_ACCEPT

5.4.7.4 Specific message contents

Table 5.4.7.4-1: DIRECT_COMMUNICATION_RELEASE (step 1, Table 5.4.7.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-11.

Information Element

Value/remark

Comment

Condition

Release Reason

‘0001’B

Direct communication to the peer UE no longer needed

5.4.8 Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the UE

5.4.8.1 Initial conditions

System Simulator:

– SS-UE1 (MCPTT Client).

– Same as those defined in the ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.5, or, the ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.6.

IUT:

– UE (MCPTT client)

ProSe related configuration

– Same as those defined in the ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.5, or, the ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.6.

UE state

– The UE has established ProSe direct communication one-to-one out of E-UTRA coverage using the ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.5, or, the ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’, as described in clause 5.4.6.

5.4.8.2 Definition of system information messages

N/a (out of E-UTRA coverage).

5.4.8.3 Procedure

Table 5.4.8.3-1: ProSe direct communication one-to-one out of E-UTRA coverage signalling for MCPTT communication – release by the UE

St

Procedure

Message Sequence

U – S

Message

1

UE sends a DIRECT_COMMUNICATION_RELEASE message with a Release Reason IE indicating ‘Direct Communication to peer UE no longer needed’.

–>

DIRECT_COMMUNICATION_RELEASE

2

SS-UE1 sends a DIRECT_COMMUNICATION_RELEASE_ACCEPT message.

<–

DIRECT_COMMUNICATION_RELEASE_ACCEPT

5.4.8.4 Specific message contents

Table 5.4.8.4-1: DIRECT_COMMUNICATION_RELEASE (step 1, Table 5.4.8.3-1)

Derivation path: 36.508 [6], Table 4.7F.3-11.

Information Element

Value/remark

Comment

Condition

Release Reason

‘0001’B

Direct communication to the peer UE no longer needed

5.4.9 Generic Test Procedure for MCPTT communication in E-UTRA / Change of cells

5.4.9.1 Initial conditions

System Simulator:

– SS (MCPTT server)

– SS E-UTRA

– Parameters are set to the default parameters for the basic E-UTRA single mode multi cell network scenarios, as defined in TS 36.508 [6] clause 4.4, unless otherwise specified in the test case.

– 3 cells (Cell 1, Cell 2 and Cell 4, all operating on the same frequency). Cells 1 and 2 are on the same PLMN1, whereas Cell 4 is on a different PLMN2.

NOTE: The procedure only requires at maximum 2 cells to be active at any one instance.

IUT:

– UE (MCPTT client)

– The UE has performed the Generic Test Procedure for MCPTT UE registration as specified in clause 5.4.2 and is in E-UTRA Registered, Idle Mode state on Cell 1 with the MCPTT Client being active. During the attach a default EPS bearer context #3 (QCI 69) according to table 6.6.1-1, TS 36.508 [6] is established for MCPTT and SIP signalling. The UE is allowed to operate on both PLMN1 and PLMN2.

NOTE 1: The assumptions for the PDN support of a MCPTT capable UE, including the default EPS bearer context QCI requirements in regard to the different PDN are described in 5.4.1A.

– The UE has performed the Generic Test Procedure for MCPTT Authorization/Configuration and Key Generation as specified in clause 5.3.2 and thereby the MCPTT client is authorised for and able to use the MCPTT service including making group and private calls on- and off-network, and, the MCPTT user is registered for receiving MCPTT service through the MCPTT Client. The PLMN1 is set as HPLMN and PLMN2 is set as VPLMN in Table 5.5.8.1-1: MCPTT Initial UE Configuration Defaults.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

5.4.9.2 Definition of system information messages

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

5.4.9.3 Procedure

Table 5.4.9.3-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" … "Tn" are to be applied subsequently. The exact instants on which these values shall be applied are described elsewhere in the present clause.

Table 5.4.9.3-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Cell 4

T0

Cell-specific RS EPRE

dBm/15kHz

-79

"Off"

"Off"

T1

Cell-specific RS EPRE

dBm/15kHz

"Off"

-79

"Off"

T2

Cell-specific RS EPRE

dBm/15kHz

"Off"

"Off"

-79

Table 5.4.9.3-2: E-UTRA/EPC signalling for UE changing cells

St

Procedure

Message Sequence

U – S

Message

1

The SS configures:

Cell 1 and Cell 2 parameters according to the row "T1" in table 5.4.9.3-1 in order to simulate needs for cell reselection to Cell2.

2

Wait for 5 sec to allow the UE to adjust to cell changes.

NOTE 1.

3

The SS configures:

Cell 2 and Cell 4 parameters according to the row "T2" in table 5.4.9.3-1 in order to simulate needs for cell reselection to Cell4.

4

The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [6] clause 4.5A.2 take place.

NOTE 2.

NOTE 1: Depending on implementation the UE may start transmitting MCPTT protocol relevant data earlier. What may be transmitted is specified in the TCs.

NOTE 2: The UE may start transmitting MCPTT protocol relevant data as soon as it receives TRACKING AREA UPDATE ACCEPT message. If this happens the SS shall not execute step 7 of the Generic test procedure for ‘Tracking area updating procedure’ and shall continue with the rest of the messages exchange defined in the test case.

5.4.9.4 Specific message contents

None.

5.4.10 Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-many communication out of E-UTRA coverage / Announcing/Discoveree procedure for group member discovery

5.4.10.1 Initial conditions

System Simulator:

– SS-UE1 (MCPTT Client).

– For the underlying "transport bearer" over which the SS and the UE will communicate, the SS is behaving as SS-UE1 as defined in TS 36.508 [6], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator configured to simulate a location in the centre of Geographical area #1 and providing timing reference as defined in TS 36.508 [6] Table 4.11.2-2 scenario #1, for the assistance of E-UTRAN off-network testing.

NOTE: For operation in off-network environment, it needs to be ensured that after the UE is powered up it considers the Geographical area #1 as being one of the geographical areas set in the USIM for operation when UE is "not served by E-UTRAN".

IUT:

– UE (MCPTT client)

– The test USIM set as defined in clause 5.5.10 is inserted.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

UE state:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [6].

5.4.10.2 Definition of system information messages

N/a (out of E-UTRA coverage)

5.4.10.3 Procedure

Table 5.4.10.3-1: ProSe Direct Discovery for public safety use / Announcing/Discoveree procedure for group member discovery for MCPTT off-network CT group calls

St

Procedure

Message Sequence

U – S

Message

1

Power up the UE.

2

Wait for 60 sec to allow the UE to determine that it is in the Geographical area #1 set in the USIM for operation when UE is "not served by E-UTRAN and acquire reference timing.

EXCEPTION: Steps 3a1-3b3b1 describe events which depend on the UE capabilities; the "lower case letter" identifies a step sequence that takes place if the UE is capable or not of Announcing for group member discovery.

3a1

IF pc_ProSeAnnForGroupMemberDiscovery (TS 36.523-2 [75]) THEN Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity2 (TS 36.523-3 [74]) to initiate continuous announcing its availability in a discovery group.

NOTE 1.

3a2

The UE transmits in the next transmission period a PC5_DISCOVERY message for Group Member Discovery Announcement applying DUIK, DUSK, and DUCK with the associated Encrypted Bitmask, along with the UTC-based counter to the PC5_DISCOVERY message.

–>

PC5_DISCOVERY

3b1

ELSE SS sets WaitForMessageCounter=1

EXCEPTION: Steps 3b2-3b3b1 are repeated until the event described in step 3b3a1 takes place OR WaitForMessageCounter=11.

3b2

SS-UE1 transmits in the next transmission period a PC5_DISCOVERY message for Group Member Discovery Solicitation applying DUIK, DUSK, and DUCK with the associated Encrypted Bitmask, along with the UTC-based counter to the PC5_DISCOVERY message.

WaitForMessageCounter=WaitForMessageCounter+1

<–

PC5_DISCOVERY

EXCEPTION: Steps 3b3a1-3b3b1 describe events which depend on the UE behaviour; the "lower case letter" identifies a step sequence that take place if the UE transmit or not in the next transmission period a PC5_DISCOVERY message.

3b3a1

The UE transmits in the next transmission period a PC5_DISCOVERY message for Group Member Discovery Response applying DUIK, DUSK, and DUCK with the associated Encrypted Bitmask, along with the UTC-based counter to the PC5_DISCOVERY message and including the target Discovery Group ID of the discovery group to be discovered in step 3b2.

–>

PC5_DISCOVERY

3b3b1

The WaitForMessageCounter=11.

EXCEPTION: Steps 4 and 5 may be repeated multiple times depending on the MCPTT procedure taking place.

EXCEPTION: Step 4 is repeated until the MCPTT protocol data unit provided by the higher layers is transmitted in full.

NOTE 2.

4

SS-UE1 sends sidelink communication over the PC5 interface in the next transmission period using the timing reference provided by the GNSS simulator (same to be used by the UE).

NOTE 3.

<–

STCH PDCP SDU packet

EXCEPTION: Step 5 is repeated until the MCPTT protocol data unit provided by the higher layers is transmitted in full.

NOTE 4.

5

The UE sends sidelink communication over the PC5 interface in the next transmission period using the timing reference provided by the GNSS simulator (same to be used by the SS-UE1).

NOTE 3.

–>

STCH PDCP SDU packet

NOTE 1: UEs which are capable of Announcing for group member discovery may start announcement automatically.

NOTE 2: The SS-UE1 may need to send more than one MCPTT protocol data unit in sequence with no response expected between them from the UE.

NOTE 3: What MCPTT protocol data units are included in the sidelink communication is defined in the test case using the present generic procedure.

NOTE 4: The UE may need to send more than one MCPTT protocol data unit in sequence with no response expected between them from the SS-UE1.

5.4.10.4 Specific message contents

Table 5.4.10.4-1: PC5_DISCOVERY (step 3a2 Table 5.4.10.3-1)

Derivation path: 36.508 [6], Table 4.7F.1-5A.

Table 5.4.10.4-2: PC5_DISCOVERY (step 3b2 Table 5.4.10.3-1)

Derivation path: 36.508 [6], Table 4.7F.1-5B.

Table 5.4.10.4-3: PC5_DISCOVERY (step 3b3a1 Table 5.4.10.3-1)

Derivation path: 36.508 [6], Table 4.7F.1-5C.

5.4.11 Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-many communication out of E-UTRA coverage / Monitoring/Discoverer procedure for group member discovery / One-to-many communication

5.4.11.1 Initial conditions

System Simulator:

– SS-UE1 (MCPTT Client).

– For the underlying "transport bearer" over which the SS and the UE will communicate, the SS is behaving as SS-UE1 as defined in TS 36.508 [6], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator configured to simulate a location in the centre of Geographical area #1 and providing timing reference as defined in TS 36.508 [6] Table 4.11.2-2 scenario #1, for the assistance of E-UTRAN off-network testing.

NOTE: For operation in off-network environment, it needs to be ensured that after the UE is powered up it considers the Geographical area #1 as being one of the geographical areas set in the USIM for operation when UE is "not served by E-UTRAN".

IUT:

– UE (MCPTT client)

– The test USIM set as defined in clause 5.5.10 is inserted.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

UE state:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [6].

5.4.11.2 Definition of system information messages

N/a (out of E-UTRA coverage)

5.4.11.3 Procedure

Table 5.4.11.3-1: ProSe Direct Discovery for public safety use / Monitoring/Discoverer procedure for group member discovery for MCPTT off-network CO group calls

St

Procedure

Message Sequence

U – S

Message

1

Power up the UE.

2

Wait for 60 sec to allow the UE to determine that it is in the Geographical area #1 set in the USIM for operation when UE is "not served by E-UTRAN and acquire reference timing.

EXCEPTION: Steps 3a1-3b3 describe events which depend on the UE capabilities; the "lower case letter" identifies a step sequence that takes place if the UE is capable or not of Monitoring for group member discovery.

3a1

IF pc_ProSeMonForGtoupMemberDiscovery (TS 36.523-2 [75]) THEN the SS-UE1 starts continuously transmitting in the relevant transmission periods a PC5_DISCOVERY message for Group Member Discovery Announcement applying DUIK, DUSK, and DUCK with the associated Encrypted Bitmask, along with the UTC-based counter to the PC5_DISCOVERY message.

<–

PC5_DISCOVERY

3b1

ELSE Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity2 (TS 36.523-3 [74]) to solicit proximity of other UEs in a discovery group.

NOTE 1.

3b2

The UE transmits in the next transmission period a PC5_DISCOVERY message for Group Member Discovery Solicitation applying DUIK, DUSK, and DUCK with the associated Encrypted Bitmask, along with the UTC-based counter to the PC5_DISCOVERY message.

–>

PC5_DISCOVERY

3b3

SS-UE1 transmits a PC5_DISCOVERY message for Group Member Discovery Response applying DUIK, DUSK, and DUCK with the associated Encrypted Bitmask, along with the UTC-based counter to the PC5_DISCOVERY message and including the target Discovery Group ID of the discovery group to be discovered in step 2b2.

<–

PC5_DISCOVERY

EXCEPTION: Steps 4 and 5 may be repeated multiple times depending on the MCPTT procedure taking place.

EXCEPTION: Step 4 is repeated until the MCPTT protocol data unit provided by the higher layers is transmitted in full.

NOTE 2.

4

The UE sends sidelink communication over the PC5 interface in the next transmission period using the timing reference provided by the GNSS simulator (same to be used by the SS-UE1).

NOTE 3.

–>

STCH PDCP SDU packet

EXCEPTION: Step 5 is repeated until the MCPTT protocol data unit provided by the higher layers is transmitted in full.

NOTE 4.

5

SS-UE1 sends sidelink communication over the PC5 interface in the next transmission period using the timing reference provided by the GNSS simulator (same to be used by the UE).

NOTE 3.

<–

STCH PDCP SDU packet

NOTE 1: UEs which are not capable of Monitoring for group member discovery may start Discoverer procedure automatically.

NOTE 2: The UE may need to send more than one MCPTT protocol data unit in sequence with no response expected between them from the SS-UE1.

NOTE 3: Which MCPTT protocol data units are included in the sidelink communication is defined in the test case using the present generic procedure.

NOTE 4: The SS-UE1 may need to send more than one MCPTT protocol data unit in sequence with no response expected between them from the UE.

5.4.11.4 Specific message contents

Table 5.4.11.4-1: PC5_DISCOVERY (step 3a1 Table 5.4.11.3-1)

Derivation path: 36.508 [6], Table 4.7F.1-5A.

Table 5.4.11.4-2: PC5_DISCOVERY (step 3b2 Table 5.4.11.3-1)

Derivation path: 36.508 [6], Table 4.7F.1-5B.

Table 5.4.11.4-3: PC5_DISCOVERY (step 3b3 Table 5.4.11.3-1)

Derivation path: 36.508 [6], Table 4.7F.1-5C.

5.4.12 Generic Test Procedure for MCPTT communication over MBMS

5.4.12.1 Initial conditions

System Simulator:

– SS (MCPTT server)

– SS E-UTRA

– E-UTRA related parameters are set to the default parameters for the basic single cell environment, as defined in TS 36.508 [6] clause 4.4, unless otherwise specified in the test case.

– MBSFNAreaConfiguration as defined in TS 36.508[6] table 4.6.1-4A is transmitted on MCCH

IUT:

– UE (MCPTT client):

– E-UTRAN UE supporting MBMS services. The UE has performed the Generic Test Procedure for MCPTT UE registration as specified in clause 5.4.2 and is in E-UTRA Registered, Idle Mode state. The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

5.4.12.2 Definition of system information messages

The E-UTRA default system information messages as defined in TS 36.508 [6] are used. System information combination 15 as defined in TS 36.508[6] clause 4.4.3.1 is used in the E-UTRA cell.

5.4.12.3 Procedure

Table 5.4.12.3-1: MCPTT communication over MBMS

St

Procedure

Message Sequence

U – S

Message

1

SS transmits MBSFNAreaConfiguration message

<–

MBSFNAreaConfiguration

2

Wait for a period equal to the MCCH modification period for the UE to receive MBSFNAreaConfiguration message.

EXCEPTION: Step 3 is repeated continuously to carry the relevant MCPTT protocol data units provided by the higher layers.

3

The SS transmits 1 MBMS Packet on the MTCH in the next MCH Scheduling Period.

NOTE: Which MCPTT protocol data units are sent and at which time is defined in the test case using the present generic procedure.

<–

MBMS Packet

5.4.12.4 Specific message contents

None.

5.4.13 Generic Test Procedure for MCPTT radio bearer establishment for use of pre-established session

5.4.13.1 Initial conditions

System Simulator:

– SS (MCPTT server)

– SS E-UTRA related parameters are set to the default parameters for the basic single cell environment, as defined in TS 36.508 [6] clause 4.4, unless otherwise specified in the test case. Requirements in regard to the PLMN which the simulated Cell(s) belongs to are specified in the test case using the present procedure.

IUT:

– UE (MCPTT client)

– The test USIM set as defined in clause 5.5.10 is inserted.

– The UE has performed the Generic Test Procedure for MCPTT UE registration as specified in clause 5.4.2 and is in E-UTRA Registered, Idle Mode state with the MCPTT Client being active. During the attach a default EPS bearer context #3 (QCI 69) according to table 6.6.1-1, TS 36.508 [6] is established for MCPTT and SIP signalling.

NOTE 1: The assumptions for the PDN support of a MCPTT capable UE, including the default EPS bearer context QCI requirements in regard to the different PDN are described in 5.4.1A.

– The UE has performed the Generic Test Procedure for MCPTT pre-established session establishment CO as specified in clause 5.3.3.

– Detailed initial conditions for the UE (MCPTT client) shall be specified in the TC referring to the present procedure.

5.4.13.2 Definition of system information messages

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

5.4.13.3 Procedure

Table 5.4.13.3-1: MCPTT radio bearer establishment for use of pre-established session

St

Procedure

Message Sequence

U – S

Message

1

SS sends a Paging message to the UE

<–

RRC: Paging (PCCH)

2

The UE transmits an RRCConnectionRequest message

–>

RRC: RRCConnectionRequest

3

The SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

5

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

6

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

–>

RRC: SecurityModeComplete

7

The SS configures all DRBs, associated with the default EPS bearers established during the attach procedure and another DRB, associated with the dedicated EPS bearer established during pre-established session establishment.

The RRCConnectionReconfiguration message is using condition SRB2-DRB(n, 1) as specified in TS 36.508 [6] clause 4.8.2.2.1, with n=1..3 depending on the number of PDNs (see clause 5.4.1A).

=> The DRB associated with MCPTT default EPS bearer obtained during the attach procedure and the DRB associated with dedicated EPS bearer obtained during the establishment of the pre-established session get established

<–

RRC: RRCConnectionReconfiguration

EXCEPTION: In parallel to step 8, depending on the test case, the UE may start signalling on the DRBs

8

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of radio bearers.

–>

RRC: RRCConnectionReconfigurationComplete

5.4.13.4 Specific message contents

All specific E-UTRA/EPC signalling message contents shall be referred to TS 36.508 [6] clauses 4.6 and 4.7.