6.1.3 On-network / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / Group Standalone SDS / Client Originated (CO)

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

6.1.3.1 Test Purpose (TP)

(1)

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

ensure that {

when { the MCDATA User requests to send a group standalone SDS message with a disposition of only Delivery }

then { UE (MCDATA Client) sends a group standalone SDS message with a disposition of only Delivery via s SIP MESSAGE message }

}

(2)

with { UE (MCDATA Client) having sent a group standalone SDS message }

ensure that {

when { the UE (MCDATA Client) receives a disposition response via a SIP MESSAGE message from the SS (MCDATA Server) }

then { UE (MCData Client) responds to the SIP MESSAGE message by sending a SIP 200 (OK) message and delivers the notification to the MCDATA User }

}

6.1.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.282, clauses 9.2.2.2.1, 6.2.2.1, 6.2.4.1, 12.2.1.2. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core spec they have been copied from. Unless otherwise stated, these are Rel-14 requirements.

[TS 24.282, clause 9.2.2.2.1]

The MCData client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6] with the clarifications given below.

The MCData client:

1) shall build the SIP MESSAGE request as specified in subclause 6.2.4.1;

…

3) if a group standalone SDS message is to be sent:

a) if the "/<x>/<x>/Common/MCData/AllowedSDS" leaf node present in the group document of the requested MCData group, configured on the group management client as specified in 3GPP TS 24.483 [42] is set to "false", shall reject the request to send SDS and not continue with the rest of the steps in this subclause; and

b) shall insert in the SIP MESSAGE request an application/vnd.3gpp.mcdata-info+xml MIME body with:

i) the <request-type> element set to a value of "group-sds";

ii) the <mcdata-request-uri> element set to the MCData group identity; and

iii) the <mcdata-client-id> element set to the MCData client ID of the originating MCData client;

4) shall generate a standalone SDS message as specified in subclause 6.2.2.1; and

5) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5].

[TS 24.282, clause 6.2.2.1]

In order to generate an SDS message, the MCData client:

1) shall generate an SDS SIGNALLING PAYLOAD message as specified in subclause 15.1.2;

2) shall generate a DATA PAYLOAD message as specified in subclause 15.1.4;

3) shall include in the SIP request, the SDS SIGNALLING PAYLOAD message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1; and

4) shall include in the SIP request, the DATA PAYLOAD message in an application/vnd.3gpp.mcdata-payload MIME body as specified in subclause E.2.

When generating an SDS SIGNALLING PAYLOAD message as specified in subclause 15.1.2, the MCData client:

1) shall set the Date and time IE to the current time as specified in subclause 15.2.8;

2) if the SDS message starts a new conversation, shall set the Conversation ID IE to a newly generated Conversation ID value as specified in subclause 15.2.9;

3) if the SDS message continues an existing unfinished conversation, shall set the Conversation ID IE to the Conversation ID value of the existing conversation as specified in subclause 15.2.9;

4) shall set the Message ID IE to a newly generated Message ID value as specified in subclause 15.2.10;

5) if the SDS message is in reply to a previously received SDS message, shall include the InReplyTo message ID IE with the Message ID value in the previously received SDS message;

6) if the SDS message is for user consumption, shall not include an Application ID IE as specified in subclause 15.2.7;

7) if the SDS message is intended for an application on the terminating MCData client, shall include an Application ID IE with an Application ID value representing the intended application as specified in subclause 15.2.7;

NOTE: The value chosen for the Application ID value is decided by the mission critical organisation.

8) if only a delivery disposition notification is required shall include a SDS disposition request type IE set to "DELIVERY" as specified in subclause 15.2.3;

9) if only a read disposition notification is required shall include a SDS disposition request type IE set to "READ" as specified in subclause 15.2.3; and

10) if both a delivery and read disposition notification is required shall include a SDS disposition request type IE set to "DELIVERY AND READ" as specified in subclause 15.2.3.

When generating an DATA PAYLOAD message for SDS as specified in subclause 15.1.4, the MCData client:

1) shall set the Number of payloads IE to the number of Payload IEs that needs to be encoded, as specified in subclause 15.2.12;

2) if end-to-end security is required for a one-to-one communication, shall include the Security parameters and Payload IE with security parameters as described in 3GPP TS 33.180 [26]. Otherwise, if end-to-end security is not required for a one-to-one communication, shall include the Payload IE as specified in subclause 15.1.4; and

3) for each Payload IE included:

a) if the payload is text, shall set the Payload content type as "TEXT" as specified in subclause 15.2.13;

b) if the payload is binary data, shall set the Payload content type as "BINARY" as specified in subclause 15.2.13;

c) if the payload is hyperlinks, shall set the Payload content type as "HYPERLINKS" as specified in subclause 15.2.13;

d) if the payload is location, shall set the Payload content type as "LOCATION" as specified in subclause 15.2.13; and

e) shall include the data to be sent in the Payload data.

[TS 24.282, clause 6.2.4.1]

This subclause is referenced from other procedures.

In a SIP MESSAGE request, the MCData client:

1) when sending SDS messages or SDS disposition notifications:

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

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

c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), in a P-Preferred-Service header field according to IETF RFC 6050 [7] in the SIP MESSAGE request;

…

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

4) shall set the Request-URI to the public service identity identifying the participating MCData function serving the MCData user.

[TS 24.282, clause 12.2.1.2]

Upon receipt of a:

"SIP MESSAGE request for SDS disposition notification for terminating MCData client"; or

"SIP MESSAGE request for FD disposition notification for terminating MCData client";

the MCData client:

1) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body; and

2) shall deliver the notification to the user or application.

6.1.3.3 Test description

6.1.3.3.1 Pre-test conditions

System Simulator:

– SS (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 MCDATA operation in the MCDATA configuration document).

IUT:

– UE (MCDATA Client)

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

Preamble:

– The <max-payload-size-sds-cplane-bytes> element shall not be present in the MCData Service Configuration document so that according to TS 24.484 [24] there is no size limit imposed for the use of C-plane procedures for the SDS message.

– 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.2B.

– UE States at the end of the preamble

– The UE is in E-UTRA Registered, Idle Mode state.

– The MCDATA Client Application has been activated and User has registered-in as the MCDATA User with the Server as active user at the Client.

6.1.3.3.2 Test procedure sequence

Table 6.1.3.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the MCDATA User request to send a group standalone SDS message with disposition request "DELIVERY".

(NOTE 1)

–

–

–

–

2-2B

Check: Does the UE (MCData Client) perform steps 1a1-3 of the procedure for CO SDS or FD message transfer using signalling plane specified in TS 36.579-1 [2] Table 5.3C.1.3-1 to send a standalone group SDS message with disposition request "DELIVERY"?

(NOTE 2)

–

–

1

P

3

Void

–

–

–

–

4

Check: Does the UE (MCData Client) perform the procedure for MCX SIP MESSAGE CT specified in TS 36.579-1 [2] Table 5.3.33.3-1 to receive the disposition notification for the SDS message sent at step 2A?

–

–

2

P

5

Void

–

–

–

–

6

Check: Does the UE (MCDATA Client) deliver the notification to the MCDATA User?

(NOTE 1)

–

–

2

P

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

NOTE 2: The RRC connection is not released at the end of the procedure.

6.1.3.3.3 Specific message contents

Table 6.1.3.3.3-1: SIP MESSAGE (step 2A, Table 6.1.3.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3C.1.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.1-1, condition MCDATA_SDS, MCDATA_SIGNALLING, MCDATA_PAYLOAD

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCData-Info

MIME-part-body

MCData-Info as described in Table 6.1.3.3.3-2

MIME body part

MCData Data signalling message

MIME-part-body

MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in Table 6.1.3.3.3-2A

MIME body part

MCData Data message

MIME-part-body

MCData Protected Payload Message containing DATA PAYLOAD as described in Table 6.1.3.3.3-3

Table 6.1.3.3.3-2: MCDATA-Info (Table 6.1.3.3.3-1)

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

Table 6.1.3.3.3-2A: SDS SIGNALLING PAYLOAD (Table 6.1.3.3.3-1)

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

Table 6.1.3.3.3-3: DATA PAYLOAD (Table 6.1.3.3.3-1)

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

Table 6.1.3.3.3-4: SIP MESSAGE (step 4, Table 6.1.3.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3.33.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.2-1, condition MCDATA_SDS, MCDATA_SIGNALLING

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCData-Info

MIME-part-body

As described in Table 6.1.3.3.3-5

MIME body part

MCData Data signalling message

MIME-part-body

MCData Protected Payload Message containing SDS NOTIFICATION as described in Table 6.1.3.3.3-6

Table 6.1.3.3.3-5: MCDATA-Info (Table 6.1.3.3.3-4)

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

Information Element

Value/remark

Comment

Reference

Condition

mcdata-info

mcdata-Params

mcdata-calling-group-id

Encrypted <mcdata-calling-group-id> with mcdataURI set to px_MCData_Group_A_ID

Encrypted according to TS 36.579-1 [2] Table 5.5.3.2.2-3A

Table 6.1.3.3.3-6: SDS NOTIFICATION (Table 6.1.3.3.3-4)

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

Table 6.1.3.3.3-7: Void