7 Off-Network Test Scenarios

36.579-73GPPMission Critical (MC) services over LTEPart 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specificationRelease 15TS

7.1 Short Data Service (SDS)

7.1.1 Off-network / Short Data Service (SDS) / Standalone SDS using signalling control plane / One-to-one SDS message / Client Originated (CO)

7.1.1.1 Test Purpose (TP)

(1)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send a standalone one-to-one SDS message with a disposition request type of DELIVERY }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

(2)

with { UE (MCData Client) having sent a SDS OFF-NETWORK MESSAGE message and started timer TFS1 (SDS retransmission) }

ensure that {

when { timer TFS1 (SDS retransmission) expires }

then { UE (MCData Client) retransmits the SDS OFF-NETWORK MESSAGE message and, stops re-transmitting if the counter CFS1 (SDS retransmission) has reached its maximum value and TFS1 (SDS retransmission) has expired }

}

(3)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send a standalone one-to-one SDS message with a disposition request type of READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

(4)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send a standalone one-to-one SDS message with a disposition request type of DELIVERY AND READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

7.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.282 clauses 9.3.2.2, 9.3.2.3. Unless otherwise stated these are Rel-15 requirements.

[TS 24.282, clause 9.3.2.2]

Upon receiving an indication to send an SDS message, the MCData client:

1) if the request to send the SDS message is for a MCData group, shall check if the value of "/<x>/<x>/Common/MCData/AllowedSDS" leaf node, present in the group configuration as specified in 3GPP TS 24.483 [42], is set to "false". It the value is set to "false", shall reject the request to send the SDS message and not continue with the remaining procedures in this clause;

2) if:

a) a one-to-one SDS message is to be sent then, shall store the MCData user ID of the intended recipient as the target MCData user ID; or

b) a group SDS message is to be sent then, shall store the MCData group ID as the target MCData group ID;

3) may set the stored SDS disposition request type as:

a) "DELIVERY", if only delivery disposition is requested;

b) "READ", if only read disposition is requested; or

c) "DELIVERY AND READ", if both delivery and read dispositions are requested;

4) if an existing conversation is indicated then, shall store the conversation identifier of the indicated conversation as SDS conversation ID. Otherwise, shall generate an UUID as described in IETF RFC 4122 [14] and store SDS conversation ID;

5) shall generate an UUID as described in IETF RFC 4122 [14] and store as the SDS message ID;

6) if indicated that the SDS message is in reply to another SDS message then, shall store the message identifier of the indicated message as SDS reply ID;

7) if indicated that the target recipient of the SDS message is an application then, shall store the application ID of the indicated application as the SDS application ID or as the SDS extended application ID;

8) shall store the received payload as the SDS payload;

9) shall store the received payload type as the SDS payload type;

10) shall store the current UTC time as the SDS transmission time;

11) shall generate a SDS OFF-NETWORK MESSAGE message as specified in clause 15.1.7. In the SDS OFF-NETWORK MESSAGE message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID;

b) if:

i) a one-to-one SDS message is to be sent then shall set the Recipient MCData user ID IE to the stored target MCData user ID as specified in clause 15.2.15; or

ii) a group SDS message is to be sent then, shall set the MCData group ID IE to the stored target MCData group ID as specified in clause 15.2.14;

c) may set the SDS disposition request type IE to the stored the SDS disposition request type as specified in clause 15.2.3;

d) shall set the Conversation ID IE to the stored conversation ID as specified in clause 15.2.9;

e) shall set the Message ID IE to the stored SDS message ID as specified in clause 15.2.10;

f) shall set the Date and time IE to the stored SDS transmission time as specified in clause 15.2.8;

g) may include the InReplyTo message ID IE set to the stored SDS reply ID as specified in clause 15.2.11;

h) may include:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE set to the stored SDS extended application ID as specified in clause 15.2.24;

i) if end-to-end security is required for a one-to-one communication and the security context does not exist or if the existing security context has expired, shall include the Security parameters and Payload IE with security parameters as described in 3GPP TS 33.180 [26];

j) if

i) end-to-end security is not required for a one-to-one communication, or

ii) sending the SDS OFF-NETWORK MESSAGE message to a MCData group;

may include the Payload IE as specified in clause 15.2.13 with:

i) the Payload content type to the stored SDS payload type; and

ii) the Payload data set to the stored SDS payload;

12) if:

a) a one-to-one SDS message is to be sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.1; or

b) a group SDS message is to be sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.2;

13) shall initialise the counter CFS1 (SDS retransmission) with the value set to 1; and

14) shall start timer TFS1 (SDS retransmission).

[TS 24.282, clause 9.3.2.3]

Upon expiry of timer TFS1 (SDS retransmission), the MCData client:

1) shall generate a SDS OFF-NETWORK MESSAGE message as specified in clause 15.1.7. In the SDS OFF-NETWORK MESSAGE message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID;

b) if:

i) a one-to-one SDS message is to be sent then, shall set the Recipient MCData user ID IE to the stored target MCData user ID; or

ii) a group SDS message is to be sent then, shall set the MCData group ID IE to the stored target MCData group ID;

c) may set the SDS disposition request type IE to the stored the SDS disposition request type as specified in clause 15.2.3;

d) shall set the Conversation ID IE to the stored conversation ID as specified in clause 15.2.9;

e) shall set the Message ID IE to the stored SDS message ID as specified in clause 15.2.10;

f) shall set the Date and time IE to the stored the SDS transmission time as specified in clause 15.2.8;

g) may include the InReplyTo message ID IE set to the stored SDS reply ID as specified in clause 15.2.11;

h) may include:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE set to the stored SDS extended application ID as specified in clause 15.2.24;

i) if end-to-end security is required for a one-to-one communication and the security context does not exist or if the existing security context has expired, shall include the Security parameters IE with security parameters as described in 3GPP TS 33.180 [26]; and

j) if:

i) end-to-end security is not required for a one-to-one communication, or

ii) sending the SDS OFF-NETWORK MESSAGE message to a MCData group;

may include the Payload IE as specified in clause 15.2.13 with:

i) the Payload content type to the stored SDS payload type; and

ii) the Payload data set to the stored SDS payload;

2) if:

a) a one-to-one SDS message was sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.1; or

b) a group SDS message was sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.2;

3) shall increment the counter CFS1(SDS retransmission) by 1; and

4) shall start timer TFS1 (SDS retransmission) if the associated counter CFS1 (SDS retransmission) has not reached its upper limit.

7.1.1.3 Test description

7.1.1.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCData 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 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

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

– SS-NW (MCData 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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCData Client)

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

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

– CFS1 (SDS retransmission) is set to the default value of 5.

– TFS1 (SDS retransmission) is set to the default value of 40 ms.

Preamble:

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

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.1.1.3.2 Test procedure sequence

Table 7.1.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power up the UE.

–

–

–

–

2

Trigger the UE to reset UTC time and location.

NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

3

Activate the MCData Client Application and register User A as the MCData User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password).

(NOTE 1)

–

–

–

–

4

Make the MCData User request to send a standalone one-to-one SDS message to a single user with an SDS disposition request type of DELIVERY.

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.5 ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 5-7 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

5

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with a disposition request type of DELIVERY?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

1,2

P

6

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

7

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 8-10 are repeated 5 times.

–

–

–

–

8

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of DELIVERED.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

9

Start 40 millisecond timer.

–

–

–

–

10

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

11

Make the MCData User request to send a standalone one-to-one SDS message to a single user with an SDS disposition request type of READ.

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.5 ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 12-14 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

12

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with a disposition request type of READ?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

3,2

P

13

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

14

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 15-17 are repeated 5 times.

–

–

–

–

15

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of READ.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

16

Start 40 millisecond timer.

–

–

–

–

17

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

18

Make the MCData User request to send a standalone one-to-one SDS message to a single user with an SDS disposition request type of DELIVERY AND READ.

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.5 ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 12-14 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

19

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with a disposition request type of DELIVERY AND READ?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

4,2

P

20

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

21

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 15-17 are repeated 5 times.

–

–

–

–

22

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of DELIVERED AND READ.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

23

Start 40 millisecond timer.

–

–

–

–

24

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

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

7.1.1.3.3 Specific message contents

Table 7.1.1.3.3-1: SDS OFF-NETWORK MESSAGE (step 5, Table 7.1.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED, MCD_1to1

Table 7.1.1.3.3-2: SDS OFF-NETWORK NOTIFICATION (step 8, Table 7.1.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED

Table 7.1.1.3.3-3: SDS OFF-NETWORK MESSAGE (step 12, Table 7.1.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition READ, MCD_1to1

Table 7.1.1.3.3-4: SDS OFF-NETWORK NOTIFICATION (step 15, Table 7.1.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition READ

Table 7.1.1.3.3-5: SDS OFF-NETWORK MESSAGE (step 19, Table 7.1.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED_READ, MCD_1to1

Table 7.1.1.3.3-6: SDS OFF-NETWORK NOTIFICATION (step 22, Table 7.1.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED_READ

7.1.2 Off-network / Short Data Service (SDS) / Standalone SDS using signalling control plane / One-to-one SDS message / Client Terminated (CT)

7.1.2.1 Test Purpose (TP)

(1)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an SDS OFF-NETWORK MESSAGE message with a disposition of DELIVERY }

then { UE (MCDATA Client) sends SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission) }

}

(2)

with { UE (MCData Client) having sent a SDS OFF-NETWORK NOTIFICATION message and started timer TFS2 (SDS notification retransmission) }

ensure that {

when { TFS2 (SDS notification retransmission) expires }

then { UE (MCData Client) retransmits the SDS OFF-NETWORK NOTIFICATION message and, stops re-transmitting if the counter CFS2 (SDS notification retransmission) has reached its maximum value and TFS2 (SDS notification retransmission) }

}

(3)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an SDS OFF-NETWORK MESSAGE message with a disposition of READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of READ upon receiving a display indication for the payload to the MCData User and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission) }

}

(4)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an SDS OFF-NETWORK MESSAGE message with a disposition of DELIVERY AND READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED AND READ after the message is rendered to the user if the timer TFS3 (delivery and read) has not expired, or, if the timer TFS3 (delivery and read) expires before the message is rendered to the MCData User, sends first a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED and then sends a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of READ after the payload is rendered to the MCData User, and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission) after each sending of the SDS OFF-NETWORK NOTIFICATION message }

}

7.1.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.282 clauses 9.3.2.4, 9.3.2.5, 9.3.2.6, 12.3.2, 12.3.3, 12.3.4, 12.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.282, clause 9.3.2.4]

Upon receiving an SDS OFF-NETWORK MESSAGE message with a SDS disposition request type IE, the MCData client:

1) shall store the value of Sender MCData user ID IE as the stored notification target MCData user ID;

2) shall store the value of Conversation ID IE as the stored conversation ID;

3) shall store the value of Message ID IE as the stored SDS message ID;

4) shall store the current UTC time as the stored SDS notification time;

5) if present, shall store the value of Application ID IE as the stored SDS application ID;

6) if present, shall store the value of the Extended application ID IE as the stored SDS extended application ID;

7) if present, shall store the value of MCData group ID IE to the stored target MCData group ID; and

8) if the SDS disposition request type IE is set to:

a) "DELIVERY" then, shall send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.2;

b) "READ" then, shall send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.3; or

c) "DELIVERY AND READ" then, shall start timer TFS3 (delivery and read).

NOTE: Duplicate messages (re-transmissions) that are received by the MCData client should not be processed again.

[TS 24.282, clause 9.3.2.5]

Upon receiving a display indication before timer TFS3 (delivery and read) expires, the MCData client:

1) shall generate and send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.4.

[TS 24.282, clause 9.3.2.6]

Upon expiry of timer TFS3 (delivery and read), the MCData client:

1) shall generate and send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.2; and

2) upon receiving a display indication, shall generate and send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.3.

[TS 24.282, clause 12.3.2]

To send an off-network SDS delivery notification, the MCData client:

1) shall store "DELIVERED" as the disposition type;

2) shall generate a SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the stored SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

3) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored notification target MCData user ID as specified in clause 9.3.1.1;

4) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

5) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.3]

Upon receiving a display indication for the payload to the user or processing of the payload by the target application, the MCData client:

1) shall store "READ" as the disposition type;

2) shall store the current UTC time as the stored SDS notification time;

3) shall generate SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Data and time IE as the SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

4) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

5) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

6) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.4]

Upon receiving a display indication for the payload to the user or processing of the payload by the target application, the MCData client:

1) shall store "DELIVERED AND READ" as the disposition type and stop the timer TFS3 (display and read);

2) shall store the current UTC time as the stored SDS notification time;

3) shall generate SDS OFF-NETWORK NOTIFICATION message. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

4) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

5) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

6) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.5]

Upon expiry of timer TFS2 (SDS notification retransmission), the MCData client:

1) shall generate a SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the stored SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

2) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

3) shall increment the counter CFS2 (SDS notification retransmission) by 1; and

4) shall start timer TFS2 (SDS notification retransmission) if the associated counter CFS2 (SDS notification retransmission) has not reached its upper limit.

7.1.2.3 Test description

7.1.2.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCData 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 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

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

– SS-NW (MCData 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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCData Client)

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

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

– CFS2 (SDS notification retransmission)is set to the default value of 5.

– TFS2 (SDS notification retransmission)is set to the default value of 40 ms.

– TFS3 (delivery and read)is set to the default value of 120 ms.

Preamble:

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

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.1.2.3.2 Test procedure sequence

Table 7.1.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power up the UE.

–

–

–

–

2

Trigger the UE to reset UTC time and location.

NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

3

Activate the MCData Client Application and register User A as the MCData User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password).

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

4

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition request type of DELIVERY.

<–

SDS OFF-NETWORK MESSAGE

–

–

–

EXCEPTION: Steps 5-7 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

5

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

1,2

P

6

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

7

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

8

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition request type of READ.

<–

SDS OFF-NETWORK MESSAGE

–

–

–

EXCEPTION: Steps 9-11 are repeated CFS2=5 times (CFS2 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

9

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of READ upon receiving a display indication for the payload to the MCData User?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

3,2

P

10

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

11

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

12

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition request type of DELIVERY AND READ.

NOTE: Timer TFS3 (delivery and read).is started upon receipt of the SDS OFF-NETWORK MESSAGE message that contains a "DELIVERY AND READ" disposition request. TFS3 (delivery and read)=120ms according to the default value defined in TS 24.282 [31] Table F.3.1-1.

<–

SDS OFF-NETWORK MESSAGE

–

–

–

EXCEPTION: Steps 13a1-13b2 describe behaviour that depends on the UE implementation. Steps 13a1-13a6 describe the behaviour of the UE when the timer TFS3 (delivery and read) expires before the contents of the Payload IE are rendered to the MCData User. Steps 13b1-13b3 describe the behaviour of the UE when the contents of the Payload IE are rendered to the MCData User before the timer TFS3 (delivery and read) expires.

–

–

–

–

–

EXCEPTION: Steps 13a1-13a3 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

13a1

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

4,2

P

13a2

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

13a3

TFS2 expires.

–

–

–

–

–

EXCEPTION: Steps 13a4-13a6 are repeated CFS2=5 times (CFS2 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

13a4

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of READ upon receiving a display indication for the payload to the MCData User?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

4,2

P

13a5

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

13a6

TFS2 expires.

–

–

–

–

–

EXCEPTION: Steps 13b1-13b3 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

13b1

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED AND READ?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

4,2

P

13b2

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

13b3

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

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

7.1.2.3.3 Specific message contents

Table 7.1.2.3.3-1: SDS OFF-NETWORK MESSAGE (step 4, Table 7.1.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED, MCD_1to1

Table 7.1.2.3.3-2: SDS OFF-NETWORK NOTIFICATION (steps 5, 13a1, Table 7.1.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED

Table 7.1.2.3.3-3: SDS OFF-NETWORK MESSAGE (step 8, Table 7.1.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition READ, MCD_1to1

Table 7.1.2.3.3-4: SDS OFF-NETWORK NOTIFICATION (steps 9, 13a4, Table 7.1.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition READ

Table 7.1.2.3.3-5: SDS OFF-NETWORK MESSAGE (step 8, Table 7.1.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED_READ, MCD_1to1

Table 7.1.2.3.3-6: SDS OFF-NETWORK NOTIFICATION (step 13b1, Table 7.1.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED_READ

7.1.3 Off-network / Short Data Service (SDS) / Standalone SDS using signalling control plane / Group SDS message / Client Originated (CO)

7.1.3.1 Test Purpose (TP)

(1)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send a standalone group SDS message with a disposition request type of DELIVERY }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

(2)

with { UE (MCData Client) having sent a SDS OFF-NETWORK MESSAGE message and started timer TFS1 (SDS retransmission) }

ensure that {

when { timer TFS1 (SDS retransmission) expires }

then { UE (MCData Client) retransmits the SDS OFF-NETWORK MESSAGE message and, stops re-transmitting if the counter CFS1 (SDS retransmission) has reached its maximum value and TFS1 (SDS retransmission) has expired }

}

(3)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send a standalone group SDS message with a disposition request type of READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

(4)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send a standalone group SDS message with a disposition request type of DELIVERY AND READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

7.1.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.282 clauses 9.3.2.2, 9.3.2.3. Unless otherwise stated these are Rel-15 requirements.

[TS 24.282, clause 9.3.2.2]

Upon receiving an indication to send an SDS message, the MCData client:

1) if the request to send the SDS message is for a MCData group, shall check if the value of "/<x>/<x>/Common/MCData/AllowedSDS" leaf node, present in the group configuration as specified in 3GPP TS 24.483 [42], is set to "false". It the value is set to "false", shall reject the request to send the SDS message and not continue with the remaining procedures in this clause;

2) if:

a) a one-to-one SDS message is to be sent then, shall store the MCData user ID of the intended recipient as the target MCData user ID; or

b) a group SDS message is to be sent then, shall store the MCData group ID as the target MCData group ID;

3) may set the stored SDS disposition request type as:

a) "DELIVERY", if only delivery disposition is requested;

b) "READ", if only read disposition is requested; or

c) "DELIVERY AND READ", if both delivery and read dispositions are requested;

4) if an existing conversation is indicated then, shall store the conversation identifier of the indicated conversation as SDS conversation ID. Otherwise, shall generate an UUID as described in IETF RFC 4122 [14] and store SDS conversation ID;

5) shall generate an UUID as described in IETF RFC 4122 [14] and store as the SDS message ID;

6) if indicated that the SDS message is in reply to another SDS message then, shall store the message identifier of the indicated message as SDS reply ID;

7) if indicated that the target recipient of the SDS message is an application then, shall store the application ID of the indicated application as the SDS application ID or as the SDS extended application ID;

8) shall store the received payload as the SDS payload;

9) shall store the received payload type as the SDS payload type;

10) shall store the current UTC time as the SDS transmission time;

11) shall generate a SDS OFF-NETWORK MESSAGE message as specified in clause 15.1.7. In the SDS OFF-NETWORK MESSAGE message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID;

b) if:

i) a one-to-one SDS message is to be sent then shall set the Recipient MCData user ID IE to the stored target MCData user ID as specified in clause 15.2.15; or

ii) a group SDS message is to be sent then, shall set the MCData group ID IE to the stored target MCData group ID as specified in clause 15.2.14;

c) may set the SDS disposition request type IE to the stored the SDS disposition request type as specified in clause 15.2.3;

d) shall set the Conversation ID IE to the stored conversation ID as specified in clause 15.2.9;

e) shall set the Message ID IE to the stored SDS message ID as specified in clause 15.2.10;

f) shall set the Date and time IE to the stored SDS transmission time as specified in clause 15.2.8;

g) may include the InReplyTo message ID IE set to the stored SDS reply ID as specified in clause 15.2.11;

h) may include:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE set to the stored SDS extended application ID as specified in clause 15.2.24;

i) if end-to-end security is required for a one-to-one communication and the security context does not exist or if the existing security context has expired, shall include the Security parameters and Payload IE with security parameters as described in 3GPP TS 33.180 [26];

j) if

i) end-to-end security is not required for a one-to-one communication, or

ii) sending the SDS OFF-NETWORK MESSAGE message to a MCData group;

may include the Payload IE as specified in clause 15.2.13 with:

i) the Payload content type to the stored SDS payload type; and

ii) the Payload data set to the stored SDS payload;

12) if:

a) a one-to-one SDS message is to be sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.1; or

b) a group SDS message is to be sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.2;

13) shall initialise the counter CFS1 (SDS retransmission) with the value set to 1; and

14) shall start timer TFS1 (SDS retransmission).

[TS 24.282, clause 9.3.2.3]

Upon expiry of timer TFS1 (SDS retransmission), the MCData client:

1) shall generate a SDS OFF-NETWORK MESSAGE message as specified in clause 15.1.7. In the SDS OFF-NETWORK MESSAGE message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID;

b) if:

i) a one-to-one SDS message is to be sent then, shall set the Recipient MCData user ID IE to the stored target MCData user ID; or

ii) a group SDS message is to be sent then, shall set the MCData group ID IE to the stored target MCData group ID;

c) may set the SDS disposition request type IE to the stored the SDS disposition request type as specified in clause 15.2.3;

d) shall set the Conversation ID IE to the stored conversation ID as specified in clause 15.2.9;

e) shall set the Message ID IE to the stored SDS message ID as specified in clause 15.2.10;

f) shall set the Date and time IE to the stored the SDS transmission time as specified in clause 15.2.8;

g) may include the InReplyTo message ID IE set to the stored SDS reply ID as specified in clause 15.2.11;

h) may include:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE set to the stored SDS extended application ID as specified in clause 15.2.24;

i) if end-to-end security is required for a one-to-one communication and the security context does not exist or if the existing security context has expired, shall include the Security parameters IE with security parameters as described in 3GPP TS 33.180 [26]; and

j) if:

i) end-to-end security is not required for a one-to-one communication, or

ii) sending the SDS OFF-NETWORK MESSAGE message to a MCData group;

may include the Payload IE as specified in clause 15.2.13 with:

i) the Payload content type to the stored SDS payload type; and

ii) the Payload data set to the stored SDS payload;

2) if:

a) a one-to-one SDS message was sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.1; or

b) a group SDS message was sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.2;

3) shall increment the counter CFS1(SDS retransmission) by 1; and

4) shall start timer TFS1 (SDS retransmission) if the associated counter CFS1 (SDS retransmission) has not reached its upper limit.

7.1.3.3 Test description

7.1.3.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCData 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 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

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

– SS-NW (MCData 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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCData Client)

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

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

– CFS1 (SDS retransmission) is set to the default value of 5.

– TFS1 (SDS retransmission) is set to the default value of 40 ms.

Preamble:

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

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.1.3.3.2 Test procedure sequence

Table 7.1.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power up the UE.

–

–

–

–

2

Trigger the UE to reset UTC time and location.

NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

3

Activate the MCData Client Application and register User A as the MCData User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password).

(NOTE 1)

–

–

–

–

4

Make the MCData User request to send a standalone group SDS message with an SDS disposition request type of DELIVERY.

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 5-7 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

5

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with a disposition request type of DELIVERY?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

1,2

P

6

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

7

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 8-10 are repeated 5 times.

–

–

–

–

8

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of DELIVERED.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

9

Start 40 millisecond timer.

–

–

–

–

10

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

11

Make the MCData User request to send a standalone group SDS message with an SDS disposition request type of READ.

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 12-14 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

12

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with a disposition request type of READ?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

3,2

P

13

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

14

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 15-17 are repeated 5 times.

–

–

–

–

15

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of READ.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

16

Start 40 millisecond timer.

–

–

–

–

17

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

18

Make the MCData User request to send a standalone group SDS message with an SDS disposition request type of DELIVERY AND READ.

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 12-14 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

19

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with a disposition request type of DELIVERY AND READ?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

4,2

P

20

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

21

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 15-17 are repeated 5 times.

–

–

–

–

22

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of DELIVERED AND READ.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

23

Start 40 millisecond timer.

–

–

–

–

24

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

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

7.1.3.3.3 Specific message contents

Table 7.1.3.3.3-1: SDS OFF-NETWORK MESSAGE (step 5, Table 7.1.3.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED, MCD_grp

Table 7.1.3.3.3-2: SDS OFF-NETWORK NOTIFICATION (step 8, Table 7.1.3.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED

Table 7.1.3.3.3-3: SDS OFF-NETWORK MESSAGE (step 12, Table 7.1.3.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition READ, MCD_grp

Table 7.1.3.3.3-4: SDS OFF-NETWORK NOTIFICATION (step 15, Table 7.1.3.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition READ

Table 7.1.3.3.3-5: SDS OFF-NETWORK MESSAGE (step 19, Table 7.1.3.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED_READ, MCD_grp

Table 7.1.3.3.3-6: SDS OFF-NETWORK NOTIFICATION (step 22, Table 7.1.3.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED_READ

7.1.4 Off-network / Short Data Service (SDS) / Standalone SDS using signalling control plane / Group SDS message / Client Terminated (CT)

7.1.4.1 Test Purpose (TP)

(1)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an SDS OFF-NETWORK MESSAGE message with a disposition of DELIVERY }

then { UE (MCDATA Client) sends SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission) }

}

(2)

with { UE (MCData Client) having sent a SDS OFF-NETWORK NOTIFICATION message and started timer TFS2 (SDS notification retransmission) }

ensure that {

when { TFS2 (SDS notification retransmission) expires }

then { UE (MCData Client) retransmits the SDS OFF-NETWORK NOTIFICATION message and, stops re-transmitting if the counter CFS2 (SDS notification retransmission) has reached its maximum value and TFS2 (SDS notification retransmission) }

}

(3)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an SDS OFF-NETWORK MESSAGE message with a disposition of READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of READ upon receiving a display indication for the payload to the MCData User and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission) }

}

(4)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an SDS OFF-NETWORK MESSAGE message with a disposition of DELIVERY AND READ }

then { UE (MCDATA Client) sends a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED AND READ after the message is rendered to the user if the timer TFS3 (delivery and read) has not expired, or, if the timer TFS3 (delivery and read) expires before the message is rendered to the MCData User, sends first a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED and then sends a SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of READ after the payload is rendered to the MCData User, and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission) after each sending of the SDS OFF-NETWORK NOTIFICATION message }

}

7.1.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.282 clauses 9.3.2.4, 9.3.2.5, 9.3.2.6, 12.3.2, 12.3.3, 12.3.4, 12.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.282, clause 9.3.2.4]

Upon receiving an SDS OFF-NETWORK MESSAGE message with a SDS disposition request type IE, the MCData client:

1) shall store the value of Sender MCData user ID IE as the stored notification target MCData user ID;

2) shall store the value of Conversation ID IE as the stored conversation ID;

3) shall store the value of Message ID IE as the stored SDS message ID;

4) shall store the current UTC time as the stored SDS notification time;

5) if present, shall store the value of Application ID IE as the stored SDS application ID;

6) if present, shall store the value of the Extended application ID IE as the stored SDS extended application ID;

7) if present, shall store the value of MCData group ID IE to the stored target MCData group ID; and

8) if the SDS disposition request type IE is set to:

a) "DELIVERY" then, shall send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.2;

b) "READ" then, shall send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.3; or

c) "DELIVERY AND READ" then, shall start timer TFS3 (delivery and read).

NOTE: Duplicate messages (re-transmissions) that are received by the MCData client should not be processed again.

[TS 24.282, clause 9.3.2.5]

Upon receiving a display indication before timer TFS3 (delivery and read) expires, the MCData client:

1) shall generate and send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.4.

[TS 24.282, clause 9.3.2.6]

Upon expiry of timer TFS3 (delivery and read), the MCData client:

1) shall generate and send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.2; and

2) upon receiving a display indication, shall generate and send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.3.

[TS 24.282, clause 12.3.2]

To send an off-network SDS delivery notification, the MCData client:

1) shall store "DELIVERED" as the disposition type;

2) shall generate a SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the stored SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

3) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored notification target MCData user ID as specified in clause 9.3.1.1;

4) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

5) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.3]

Upon receiving a display indication for the payload to the user or processing of the payload by the target application, the MCData client:

1) shall store "READ" as the disposition type;

2) shall store the current UTC time as the stored SDS notification time;

3) shall generate SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Data and time IE as the SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

4) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

5) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

6) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.4]

Upon receiving a display indication for the payload to the user or processing of the payload by the target application, the MCData client:

1) shall store "DELIVERED AND READ" as the disposition type and stop the timer TFS3 (display and read);

2) shall store the current UTC time as the stored SDS notification time;

3) shall generate SDS OFF-NETWORK NOTIFICATION message. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

4) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

5) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

6) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.5]

Upon expiry of timer TFS2 (SDS notification retransmission), the MCData client:

1) shall generate a SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the stored SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

2) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

3) shall increment the counter CFS2 (SDS notification retransmission) by 1; and

4) shall start timer TFS2 (SDS notification retransmission) if the associated counter CFS2 (SDS notification retransmission) has not reached its upper limit.

7.1.4.3 Test description

7.1.4.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCData 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 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

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

– SS-NW (MCData 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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCData Client)

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

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

– CFS2 (SDS notification retransmission)is set to the default value of 5.

– TFS2 (SDS notification retransmission)is set to the default value of 40 ms.

– TFS3 (delivery and read)is set to the default value of 120 ms.

Preamble:

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

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.1.4.3.2 Test procedure sequence

Table 7.1.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power up the UE.

–

–

–

–

2

Trigger the UE to reset UTC time and location.

NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

3

Activate the MCData Client Application and register User A as the MCData User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password).

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

4

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition request type of DELIVERY.

<–

SDS OFF-NETWORK MESSAGE

–

–

–

EXCEPTION: Steps 5-7 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

5

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

1,2

P

6

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

7

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

8

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition request type of READ.

<–

SDS OFF-NETWORK MESSAGE

–

–

–

EXCEPTION: Steps 9-11 are repeated CFS2=5 times (CFS2 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

9

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of READ upon receiving a display indication for the payload to the MCData User?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

3,2

P

10

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

11

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

12

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition request type of DELIVERY AND READ.

NOTE: Timer TFS3 (delivery and read).is started upon receipt of the SDS OFF-NETWORK MESSAGE message that contains a "DELIVERY AND READ" disposition request. TFS3 (delivery and read)=120ms according to the default value defined in TS 24.282 [31] Table F.3.1-1.

<–

SDS OFF-NETWORK MESSAGE

–

–

–

EXCEPTION: Steps 13a1-13b2 describe behaviour that depends on the UE implementation. Steps 13a1-13a6 describe the behaviour of the UE when the timer TFS3 (delivery and read) expires before the contents of the Payload IE are rendered to the MCData User. Steps 13b1-13b3 describe the behaviour of the UE when the contents of the Payload IE are rendered to the MCData User before the timer TFS3 (delivery and read) expires.

–

–

–

–

–

EXCEPTION: Steps 13a1-13a3 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

13a1

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

4,2

P

13a2

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

13a3

TFS2 expires.

–

–

–

–

–

EXCEPTION: Steps 13a4-13a6 are repeated CFS2=5 times (CFS2 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

13a4

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of READ upon receiving a display indication for the payload to the MCData User?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

4,2

P

13a5

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

13a6

TFS2 expires.

–

–

–

–

–

EXCEPTION: Steps 13b1-13b3 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

13b1

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED AND READ?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

4,2

P

13b2

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

13b3

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

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

7.1.4.3.3 Specific message contents

Table 7.1.4.3.3-1: SDS OFF-NETWORK MESSAGE (step 4, Table 7.1.4.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED, MCD_grp

Table 7.1.4.3.3-2: SDS OFF-NETWORK NOTIFICATION (steps 5, 13a1, Table 7.1.4.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED

Table 7.1.4.3.3-3: SDS OFF-NETWORK MESSAGE (step 8, Table 7.1.4.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition READ, MCD_grp

Table 7.1.4.3.3-4: SDS OFF-NETWORK NOTIFICATION (steps 9, 13a4, Table 7.1.4.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition READ

Table 7.1.4.3.3-5: SDS OFF-NETWORK MESSAGE (step 8, Table 7.1.4.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED_READ, MCD_grp

Table 7.1.4.3.3-6: SDS OFF-NETWORK NOTIFICATION (step 13b1, Table 7.1.4.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED_READ

7.2 Enhanced Status (ES)

7.2.1 Off-network / Enhanced Status (ES) / Client Originated (CO)

7.2.1.1 Test Purpose (TP)

(1)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the MCDATA User requests to send an Enhanced Status with a disposition of only Delivery }

then { UE (MCDATA Client) sends an Enhanced Status with a disposition request of only Delivery via the SDS OFF-NETWORK MESSAGE message, and, initiates counter CFS1 (SDS retransmission) to 1 and starts timer TFS1 (SDS retransmission) }

}

(2)

with { UE (MCData Client) having sent a SDS OFF-NETWORK MESSAGE message and started timer TFS1 (SDS retransmission) }

ensure that {

when { timer TFS1 (SDS retransmission) expires }

then { UE (MCData Client) retransmits the SDS OFF-NETWORK MESSAGE message and, stops re-transmitting if the counter CFS1 (SDS retransmission) has reached its maximum value and TFS1 (SDS retransmission) has expired }

}

7.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.282 clauses 14.3.1, 9.3.2.2, 9.3.2.3. Unless otherwise stated these are Rel-15 requirements.

[TS 24.282, clause 14.3.1]

Upon receiving request from MCData user to share enhanced for selected group:

1) if the value of "/<x>/<x>/Common/MCData/AllowedEnhSvc" leaf node present in the group configuration as specified in 3GPP TS 24.483 [4] is set to "true" for the MCData group, the MCData client:

a) shall use "/<x>/<x>/Common/MCData/EnhSvcOpValues/<x>/EnhSvcOpID" leaf node associated with user selected enhanced status operation value present in the group configuration as specified in 3GPP TS 24.483 [4] to generate a group standalone SDS message by following the procedure described in clause 9.3.2.2.

[TS 24.282, clause 9.3.2.2]

Upon receiving an indication to send an SDS message, the MCData client:

1) if the request to send the SDS message is for a MCData group, shall check if the value of "/<x>/<x>/Common/MCData/AllowedSDS" leaf node, present in the group configuration as specified in 3GPP TS 24.483 [42], is set to "false". It the value is set to "false", shall reject the request to send the SDS message and not continue with the remaining procedures in this clause;

2) if:

a) a one-to-one SDS message is to be sent then, shall store the MCData user ID of the intended recipient as the target MCData user ID; or

b) a group SDS message is to be sent then, shall store the MCData group ID as the target MCData group ID;

3) may set the stored SDS disposition request type as:

a) "DELIVERY", if only delivery disposition is requested;

b) "READ", if only read disposition is requested; or

c) "DELIVERY AND READ", if both delivery and read dispositions are requested;

4) if an existing conversation is indicated then, shall store the conversation identifier of the indicated conversation as SDS conversation ID. Otherwise, shall generate an UUID as described in IETF RFC 4122 [14] and store SDS conversation ID;

5) shall generate an UUID as described in IETF RFC 4122 [14] and store as the SDS message ID;

6) if indicated that the SDS message is in reply to another SDS message then, shall store the message identifier of the indicated message as SDS reply ID;

7) if indicated that the target recipient of the SDS message is an application then, shall store the application ID of the indicated application as the SDS application ID or as the SDS extended application ID;

8) shall store the received payload as the SDS payload;

9) shall store the received payload type as the SDS payload type;

10) shall store the current UTC time as the SDS transmission time;

11) shall generate a SDS OFF-NETWORK MESSAGE message as specified in clause 15.1.7. In the SDS OFF-NETWORK MESSAGE message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID;

b) if:

i) a one-to-one SDS message is to be sent then shall set the Recipient MCData user ID IE to the stored target MCData user ID as specified in clause 15.2.15; or

ii) a group SDS message is to be sent then, shall set the MCData group ID IE to the stored target MCData group ID as specified in clause 15.2.14;

c) may set the SDS disposition request type IE to the stored the SDS disposition request type as specified in clause 15.2.3;

d) shall set the Conversation ID IE to the stored conversation ID as specified in clause 15.2.9;

e) shall set the Message ID IE to the stored SDS message ID as specified in clause 15.2.10;

f) shall set the Date and time IE to the stored SDS transmission time as specified in clause 15.2.8;

g) may include the InReplyTo message ID IE set to the stored SDS reply ID as specified in clause 15.2.11;

h) may include:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE set to the stored SDS extended application ID as specified in clause 15.2.24;

i) if end-to-end security is required for a one-to-one communication and the security context does not exist or if the existing security context has expired, shall include the Security parameters and Payload IE with security parameters as described in 3GPP TS 33.180 [26];

j) if

i) end-to-end security is not required for a one-to-one communication, or

ii) sending the SDS OFF-NETWORK MESSAGE message to a MCData group;

may include the Payload IE as specified in clause 15.2.13 with:

i) the Payload content type to the stored SDS payload type; and

ii) the Payload data set to the stored SDS payload;

12) if:

a) a one-to-one SDS message is to be sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.1; or

b) a group SDS message is to be sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.2;

13) shall initialise the counter CFS1 (SDS retransmission) with the value set to 1; and

14) shall start timer TFS1 (SDS retransmission).

[TS 24.282, clause 9.3.2.3]

Upon expiry of timer TFS1 (SDS retransmission), the MCData client:

1) shall generate a SDS OFF-NETWORK MESSAGE message as specified in clause 15.1.7. In the SDS OFF-NETWORK MESSAGE message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID;

b) if:

i) a one-to-one SDS message is to be sent then, shall set the Recipient MCData user ID IE to the stored target MCData user ID; or

ii) a group SDS message is to be sent then, shall set the MCData group ID IE to the stored target MCData group ID;

c) may set the SDS disposition request type IE to the stored the SDS disposition request type as specified in clause 15.2.3;

d) shall set the Conversation ID IE to the stored conversation ID as specified in clause 15.2.9;

e) shall set the Message ID IE to the stored SDS message ID as specified in clause 15.2.10;

f) shall set the Date and time IE to the stored the SDS transmission time as specified in clause 15.2.8;

g) may include the InReplyTo message ID IE set to the stored SDS reply ID as specified in clause 15.2.11;

h) may include:

i) the Application ID IE set to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE set to the stored SDS extended application ID as specified in clause 15.2.24;

i) if end-to-end security is required for a one-to-one communication and the security context does not exist or if the existing security context has expired, shall include the Security parameters IE with security parameters as described in 3GPP TS 33.180 [26]; and

j) if:

i) end-to-end security is not required for a one-to-one communication, or

ii) sending the SDS OFF-NETWORK MESSAGE message to a MCData group;

may include the Payload IE as specified in clause 15.2.13 with:

i) the Payload content type to the stored SDS payload type; and

ii) the Payload data set to the stored SDS payload;

2) if:

a) a one-to-one SDS message was sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.1; or

b) a group SDS message was sent then, shall send the SDS OFF-NETWORK MESSAGE message as specified in clause 9.3.1.2;

3) shall increment the counter CFS1(SDS retransmission) by 1; and

4) shall start timer TFS1 (SDS retransmission) if the associated counter CFS1 (SDS retransmission) has not reached its upper limit.

7.2.1.3 Test description

7.2.1.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCData 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 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

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

– SS-NW (MCData 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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCData Client)

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

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

– CFS1 (SDS retransmission) is set to the default value of 5.

– TFS1 (SDS retransmission) is set to the default value of 40 ms.

Preamble:

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

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.2.1.3.2 Test procedure sequence

Table 7.2.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power up the UE.

–

–

–

–

2

Trigger the UE to reset UTC time and location.

NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

3

Activate the MCData Client Application and register User A as the MCData User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password).

(NOTE 1)

–

–

–

–

4

Make the MCDATA User request to send an enhanced status to Group A using Enhanced Status Id "1" with a disposition request type of "DELIVERY".

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 5-7 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

5

Check: Does the UE (MCData Client) send an enhanced status via the SDS OFF-NETWORK MESSAGE message with a disposition request type of DELIVERY?

NOTE: It is expected that the UE

– shall initialize the counter CFS1 (SDS retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS1 (SDS retransmission)

–>

SDS OFF-NETWORK MESSAGE

1,2

P

6

Start TFS1 (SDS retransmission) 40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

7

TFS1 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 8-10 are repeated 5 times.

–

–

–

–

8

SS-UE1 (MCData Client) sends a SDS OFF-NETWORK NOTIFICATION message with disposition notification type of DELIVERED.

<–

SDS OFF-NETWORK NOTIFICATION

–

–

9

Start 40 millisecond timer.

–

–

–

–

10

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

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

7.2.1.3.3 Specific message contents

Table 7.2.1.3.3-1: SDS OFF-NETWORK MESSAGE (step 5, Table 7.2.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.9-1, condition DELIVERED, MCD_grp

Information Element

Value/remark

Comment

Reference

Condition

Payload

Payload as described in Table 7.2.1.3.3-2

Table 7.2.1.3.3-2: Payload in the SDS OFF-NETWORK MESSAGE (Table 7.2.1.3.3-1)

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

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Payload

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Length of Payload

length of the content

Payload content type

‘00000110’B

ENHANCED STATUS

Payload data

"1"

The id as defined in the MCData Group Configuration Document

TS 36.579-1 [2], Table 5.5.7.3-1

Table 7.2.1.3.3-3: SDS OFF-NETWORK NOTIFICATION (step 8, Table 7.2.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.12-1, condition DELIVERED

7.2.2 Off-network / Enhanced Status (ES) / Client Terminated (CT)

7.2.2.1 Test Purpose (TP)

(1)

with { UE (MCData Client) registered and authorized for MCData Service, including authorized for MCData Service in off-network environment, and, the UE is in an off-network environment }

ensure that {

when { the UE (MCData Client) receives an enhanced status via the SDS OFF-NETWORK MESSAGE message with a disposition of DELIVERY }

then { UE (MCDATA Client) sends SDS OFF-NETWORK NOTIFICATION message with a disposition notification type of DELIVERED and, initiates counter CFS2 (SDS notification retransmission) to 1 and starts timer TFS2 (SDS notification retransmission), and, renders the operational value of the received Enhanced Status ID as enhanced status to the MCDATA User }

}

(2)

with { UE (MCData Client) having sent a SDS OFF-NETWORK NOTIFICATION message and started timer TFS2 (SDS notification retransmission) }

ensure that {

when { TFS2 (SDS notification retransmission) expires }

then { UE (MCData Client) retransmits the SDS OFF-NETWORK NOTIFICATION message and, stops re-transmitting if the counter CFS2 (SDS notification retransmission) has reached its maximum value and TFS2 (SDS notification retransmission) }

}

7.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.282 clauses 14.3.2, 9.3.2.4, 12.3.2, 12.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.282, clause 14.3.2]

Upon receipt of a SDS OFF-NETWORK MESSAGE message, the MCData client:

1) shall follow the procedure defined in clause 9.3.2.4;

2) shall attempt to match the received value with a "/<x>/<x>/Common/MCData/EnhSvcOpValues/<x>/EnhSvcOpID" leaf node present in the group configuration as specified in 3GPP TS 24.483 [4]; and

3) if a match is found, shall render the associated operational value from "/<x>/<x>/Common/MCData/EnhSvcOpValues/<x>/EnhSvcOpValue" leaf node as enhanced status to the MCData user.

[TS 24.282, clause 9.3.2.4]

Upon receiving an SDS OFF-NETWORK MESSAGE message with a SDS disposition request type IE, the MCData client:

1) shall store the value of Sender MCData user ID IE as the stored notification target MCData user ID;

2) shall store the value of Conversation ID IE as the stored conversation ID;

3) shall store the value of Message ID IE as the stored SDS message ID;

4) shall store the current UTC time as the stored SDS notification time;

5) if present, shall store the value of Application ID IE as the stored SDS application ID;

6) if present, shall store the value of the Extended application ID IE as the stored SDS extended application ID;

7) if present, shall store the value of MCData group ID IE to the stored target MCData group ID; and

8) if the SDS disposition request type IE is set to:

a) "DELIVERY" then, shall send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.2;

b) "READ" then, shall send a SDS OFF-NETWORK NOTIFICATION message as described in clause 12.3.3; or

c) "DELIVERY AND READ" then, shall start timer TFS3 (delivery and read).

NOTE: Duplicate messages (re-transmissions) that are received by the MCData client should not be processed again.

[TS 24.282, clause 12.3.2]

To send an off-network SDS delivery notification, the MCData client:

1) shall store "DELIVERED" as the disposition type;

2) shall generate a SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the stored SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition notification type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

3) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored notification target MCData user ID as specified in clause 9.3.1.1;

4) shall initialise the counter CFS2 (SDS notification retransmission) with the value set to 1; and

5) shall start timer TFS2 (SDS notification retransmission).

[TS 24.282, clause 12.3.5]

Upon expiry of timer TFS2 (SDS notification retransmission), the MCData client:

1) shall generate a SDS OFF-NETWORK NOTIFICATION message as specified in clause 15.1.8. In the SDS OFF-NETWORK NOTIFICATION message, the MCData client:

a) shall set the Sender MCData user ID IE to its own MCData user ID as specified in clause 15.2.15;

b) shall set the Conversation ID IE as the stored conversation ID as specified in clause 15.2.9;

c) shall set the Message ID IE as the stored SDS message ID as specified in clause 15.2.10;

d) shall set the Date and time IE as the stored SDS notification time as specified in clause 15.2.8;

e) shall set the SDS disposition type IE to the stored disposition type as specified in clause 15.2.5; and

f) may set:

i) the Application ID IE to the stored SDS application ID as specified in clause 15.2.7; or

ii) the Extended application ID IE to the stored extended SDS application ID as specified in clause 15.2.24;

2) shall send the SDS OFF-NETWORK NOTIFICATION message to the stored sender MCData user ID as specified in clause 9.3.1.1;

3) shall increment the counter CFS2 (SDS notification retransmission) by 1; and

4) shall start timer TFS2 (SDS notification retransmission) if the associated counter CFS2 (SDS notification retransmission) has not reached its upper limit.

7.2.2.3 Test description

7.2.2.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCData 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 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

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

– SS-NW (MCData 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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCData Client)

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

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

– CFS2 (SDS notification retransmission)is set to the default value of 5.

– TFS2 (SDS notification retransmission)is set to the default value of 40 ms.

Preamble:

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

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.2.2.3.2 Test procedure sequence

Table 7.2.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power up the UE.

–

–

–

–

2

Trigger the UE to reset UTC time and location.

NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

3

Activate the MCData Client Application and register User A as the MCData User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password).

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCData call establishment are described in TS 36.579-1 [2], subclause 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’. The test sequence below shows only the MCData relevant messages exchanged.

–

–

–

–

–

EXCEPTION: Steps 4-6 are repeated 5 times.

–

–

–

–

4

SS-UE1 (MCData Client) sends an enhanced status via the SDS OFF-NETWORK NOTIFICATION message with disposition request type of DELIVERY.

<–

SDS OFF-NETWORK MESSAGE

–

–

5

Start 40 millisecond timer.

–

–

–

–

6

40 millisecond timer expires

–

–

–

–

–

EXCEPTION: Steps 7-9 are repeated CFS1=5 times (CFS1 defined in 24.282 [31] Table G.3.1-1)

–

–

–

–

7

Check: Does the UE (MCData Client) send a SDS OFF-NETWORK MESSAGE message with disposition notification type of DELIVERED?

NOTE: It is expected that the UE

– shall initialize the counter CFS2 (SDS notification retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission.

– shall start timer TFS2 (SDS notification retransmission)

–>

SDS OFF-NETWORK NOTIFICATION

1,2

P

8

Start TFS2 (SDS notification retransmission)=40 milliseconds as defined in 24.282 [31] Table F.3.1-1.

–

–

–

–

9

TFS2 expires.

–

–

–

–

–

EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCData call release are described in TS 36.579-1 [2], subclause 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’.

–

–

–

–

10

Check: Does the UE (MCDATA Client) render the operational value of the received Enhanced Status ID as enhanced status to the MCDATA User?

(NOTE 1)

–

–

1

P

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

7.2.2.3.3 Specific message contents

Table 7.2.2.3.3-1: SDS OFF-NETWORK MESSAGE (step 4, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.10-1, condition DELIVERED, MCD_grp

Information Element

Value/remark

Comment

Reference

Condition

Payload

Payload as described in Table 7.2.2.3.3-2

Table 7.2.2.3.3-2: Payload in the SDS OFF-NETWORK MESSAGE (step 4, Table 7.2.2.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.10-3, condition DELIVERED, MCD_grp

Information Element

Value/remark

Comment

Reference

Condition

Data payload message identity

‘00000011’B

Data payload

TS 24.282 [87] clause 15.2.2

Number of payloads

1

1 payload

TS 24.282 [87] clause 15.2.12

Payload

TS 24.282 [87] clause 15.2.13

Payload IEI

’78’O

Length of Payload

length of the content

Payload content type

‘00000110’B

ENHANCED STATUS

Payload data

"0"

The id as defined in the MCData Group Configuration Document

TS 36.579-1 [2], Table 5.5.7.3-1

Table 7.2.2.3.3-3: SDS OFF-NETWORK NOTIFICATION (steps 7, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.8.11-1, condition DELIVERED

Annex A (normative):
Test Files