6.3 Location

36.579-23GPPMission Critical (MC) services over LTEPart 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specificationRelease 15TS

6.3.1 On-network / Location / Event Triggered Location Information report

6.3.1.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client)registered and authorized for MCPTT service and not in an emergency state and having received a location information configuration message providing configuration parameters for NonEmergencyLocationInformation requesting indication of ESGIs and location information, and, TriggeringCriteria set to Cell change, and, a none zero minimumReportInterval timer }

ensure that {
when { UE moves to a different cell }

then { UE (MCPTT Client) sends location report obeying the set in the location configuration parameters for NonEmergencyLocationInformation including waiting for the expiry of minimumIntervalLength timer for before reporting }

}

(2)

with { UE (MCPTT Client)registered and authorized for MCPTT service and not in an emergency state and having received a location information configuration message providing configuration parameters for NonEmergencyLocationInformation requesting indication of ESGIs and location information, and, TriggeringCriteria set to PLMN change and PERIODIC, and, a none zero minimumReportInterval timer }

ensure that {
when { UE moves to a cell belonging to different however allowed for communication PLMN }

then { UE (MCPTT Client) sends location report obeying the set in the location configuration parameters for NonEmergencyLocationInformation and resets all triggers }

}

(3)

with { UE (MCPTT Client) registered and authorized for MCPTT service and having received a location information configuration message providing configuration parameters for NonEmergencyLocationInformation requesting indication of ESGIs and location information, and, TriggeringCriteria set to PLMN change and PERIODIC, and, a none zero minimumReportInterval timer }

ensure that {

when { when the PERIODIC trigger fires up }

then { UE (MCPTT Client) sends location report obeying the set in the location configuration parameters for NonEmergencyLocationInformation }

}

6.3.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379, clause 13.3.2, 13.3.4.1, 13.3.4.2. Unless otherwise stated, these are Rel-13 requirements.

[TS24.379 clause 13.3.2]

Upon receiving a SIP MESSAGE request containing:

1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";

2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and

3) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Configuration> root element included in the <location-info> root element;

then the MCPTT client:

1) shall store the contents of the <Configuration> elements;

2) shall set the location reporting triggers accordingly; and

3) shall start the minimumReportInterval timer.

[TS 24.379 clause 13.3.4.1]

If a location reporting trigger fires the MCPTT client checks if the minimumReportInterval timer is running. If the timer is running the MCPTT client waits until the timer expires. When the minimumReportInterval timer fires, the MCPTT client:

1) shall, if any of the reporting triggers are still true, send a location information report as specified in subclause 13.3.4.2.

[TS 24.379 clause 13.3.4.2]

If the MCPTT client does not need to send a SIP request for other reasons, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The MCPTT client;

1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration;

2) shall include a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml";

3) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include:

a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request;

b) a <TriggerId> child element set to the value of each <Trigger-Id> value of the triggers that have fired; and

c) the location reporting elements corresponding to the triggers that have fired;

4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcptt along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6];

5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer;

6) shall reset all triggers; and

7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].

6.3.1.3 Test description

6.3.1.3.1 Pre-test conditions

System Simulator:

– SS (MCPTT 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 and Cell 2 shall belong to PLMN1 (the PLMN specified for MCPTT operation in the MCPTT configuration document). The simulated Cell 4 shall belong to PLMN2. Which cell is simulated at which time and with what power is described in TS 36.579-1 [2], subclause 5.4.9 ‘Generic Test Procedure for MCPTT communication in E-UTRA / Change of cells’ which is called during the test sequence.

– GNSS simulator to simulate a location.

IUT:

– UE (MCPTT client)

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

Preamble:

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

– The MCPTT User performs the procedure for MCPTT 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 to provide a location, as defined in TS 36.508 [24] Table 4.11.2-2, step 1 of scenario #4.

– UE States at the end of the preamble

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

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

6.3.1.3.2 Test procedure sequence

Table 6.3.1.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

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

–

–

–

–

–

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

–

–

–

–

1

The SS sends a location reporting configuration containing the cell change trigger criteria and the minimum report interval to the UE (MCPTT Client). Provision of serving and neighbouring cells ECGIs is requested in addition to the Location Information. The minimumReportInterval time is set to 25 sec.

<—

SIP MESSAGE

–

–

1A

SS starts timer=25 sec (the non-emergency minimumReportInterval interval length defined in the SIP MESSAGE sent in step 1).

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection

–

–

–

–

1B

Trigger the GNSS simulator to start step 2 of Scenario #4 to simulate the UE moving to location #7 inside Geographical area #1 as defined in TS 36.508 [24] Table 4.11.2-2.

–

–

–

–

1C

Wait 10 sec to allow the simulated location to move approximately 100 m from the original location to location #7.

–

–

–

–

2

Make the SS simulate cell change (same PLMN). The related E-UTRA/EPC actions are described in TS 36.579-1 [2], subclause 5.4.9 ‘Generic Test Procedure for MCPTT communication in E-UTRA / Change of cells’ steps 1 and 2. The test sequence below shows only the MCPTT relevant messages exchanged.

NOTE: Cell 2 and Cell 1 will be active.

–

–

–

–

2A

Timer=25 sec expires.

–

–

–

–

–

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

–

–

–

–

3

Check: Does the UE (MCPTT Client) send a SIP MESSAGE containing the Cell change trigger identification along with the location information report, the current location coordinates as specified in step 1B, and, the ECGIs of Cells 1 and 2?

—>

SIP MESSAGE

1

P

4-8

Void

–

–

–

–

9

The SS sends a location reporting configuration containing the PLMN change trigger criteria, and, periodic trigger criteria with PeriodicReport reporting interval set to 60 sec and the minimum report interval to the UE (MCPTT Client). Provision of cells ECGIs is requested in addition to the Location Information. The minimumReportInterval time is set to 10 sec.

<—

SIP MESSAGE

–

–

9A

SS starts timer=60 sec (the PeriodicReport interval defined in the SIP MESSAGE sent in step 9).

NOTE: The value of 60 sec has been chosen arbitrary however if the behaviour described in steps 9B-11 takes longer than 60 sec then this value needs to be adjusted.

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection

–

–

–

–

9B

Trigger the GNSS simulator to start step 4 of Scenario #4 to simulate the UE moving to location #8 inside Geographical area #1 as defined in TS 36.508 [24] Table 4.11.2-2.

–

–

–

–

9C

Wait 10 sec to allow the simulated location to move approximately 100 m from the original location to location #8.

–

–

–

–

10

Make the SS simulate PLMN change. The related E-UTRA/EPC actions are described in TS 36.579-1 [2], subclause 5.4.9 ‘Generic Test Procedure for MCPTT communication in E-UTRA / Change of cells’ steps 3 and 4. The test sequence below shows only the MCPTT relevant messages exchanged.

NOTE: Cell 4 only will be active.

–

–

–

–

–

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

–

–

–

–

11

Check: Does the UE (MCPTT Client) send (NOTE) a SIP MESSAGE containing the PLMN change trigger identification along with the location information report, the current location coordinates as specified in step 9B, and the ECGI of cell 4 (the only cell being active at this moment of time)?

NOTE: The minimumReportInterval time (set in step 9) has already expired latest at the end of step 9B.

—>

SIP MESSAGE

2

P

11A

SS cancels Timer=60.

–

–

–

–

11B

SS starts Timer=60.

–

–

–

–

–

EXCEPTION: SS releases the E-UTRA connection

–

–

–

–

12

Void.

–

–

–

–

13

Timer=60 sec expires

–

–

–

–

–

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

–

–

–

–

14

Check: Does the UE (MCPTT Client) send a SIP MESSAGE containing the periodic trigger identification along with location information report after the non-emergency minimum interval length expired?

NOTE: The minimumReportInterval time (set in step 9) has already expired before step 13.

—>

SIP MESSAGE

3

P

–

EXCEPTION: SS releases the E-UTRA connection

–

–

–

–

6.3.1.3.3 Specific message contents

Table 6.3.1.3.3-1: SIP MESSAGE (Step 1, Table 6.3.1.3.2-1)

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

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body not including MCPTT-Info and not including MCPPT-Affiliation-Command

not including any MIME body part with Content-Type being "application/vnd.3gpp.mcptt-info+xml" or "application/vnd.3gpp.mcptt-affiliation-command+xml"

MIME body part

Location info

MIME-part-headers

Content-Type

"application/vnd.3gpp.mcptt-location-info+xml"

MIME-part-body

Location-info as described in Table 6.3.1.3.3-2

Table 6.3.1.3.3-2: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-1)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

NonEmergencyLocationInformation

ServingEcgi

present

Provision of information in the report is requested.

NeighbouringEcgi

present

Provision of information in the report is requested.

MbmsSaId

not present

Provision of information in the report is not requested.

MbsfnArea

not present

Provision of information in the report is not requested.

GeographicalCoordinate

present

minimumIntervalLength

"25"

the value in seconds

EmergencyLocationInformation"

ServingEcgi

present

Provision of information in the report is requested.

NeighbouringEcgi

present

Provision of information in the report is requested.

MbmsSaId

not present

Provision of information in the report is not requested.

MbsfnArea

not present

Provision of information in the report is not requested.

GeographicalCoordinate

present

Provision of information in the report is requested.

minimumIntervalLength

"30"

the value in seconds

TriggeringCriteria

CellChange

AnyCellChange

TriggerID

"CELLCHANGE"

Table 6.3.1.3.3-3: SIP MESSAGE (Step 3, Table 6.3.1.3.2-1)

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

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body not including MCPTT-Info and not including MCPPT-Affiliation-Command

not including any MIME body part with Content-Type being "application/vnd.3gpp.mcptt-info+xml" or "application/vnd.3gpp.mcptt-affiliation-command+xml"

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-headers

Content-Type

"application/vnd.3gpp.mcptt-location-info+xml"

MIME-part-body

Location-info as described in Table 6.3.1.3.3-4

Table 6.3.1.3.3-4: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-3)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

TriggerID

"CELLCHANGE"

CurrentLocation

CurrentServingEcgi

The E-UTRAN Cell Global Identification (ECGI) of Cell 2

NeighbouringEcgi

The ECGI of Cell 1

CurrentCoordinate

The location simulated by the GNSS simulator at the time of transmission of the message.

longitude

The longitude value as specified for location number #7 defined in TS 36.508 [24] Table 4.11.2-3 +/- 0.00016 degrees.

latitude

The latitude value as specified for location number #7 defined in TS 36.508 [24] Table 4.11.2-3 +/- 0.00013 degrees.

ReportType

"NonEmergency"

Table 6.3.1.3.3-5 to 8: Void

Table 6.3.1.3.3-9: SIP MESSAGE (Step 9, Table 6.3.1.3.2-1)

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

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body not including MCPTT-Info and not including MCPPT-Affiliation-Command

not including any MIME body part with Content-Type being "application/vnd.3gpp.mcptt-info+xml" or "application/vnd.3gpp.mcptt-affiliation-command+xml"

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-headers

Content-Type

"application/vnd.3gpp.mcptt-location-info+xml"

MIME-part-body

Location-info as described in Table 6.3.1.3.3-10

Table 6.3.1.3.3-10: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-9)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

NonEmergencyLocationInformation

ServingEcgi

present

Provision of information in the report is requested.

NeighbouringEcgi

present

Provision of information in the report is requested.

MbmsSaId

not present

Provision of information in the report is not requested.

MbsfnArea

not present

Provision of information in the report is not requested.

GeographicalCoordinate

present

Provision of information in the report is requested.

minimumIntervalLength

"10"

the value in seconds

EmergencyLocationInformation"

ServingEcgi

present

Provision of information in the report is requested.

NeighbouringEcgi

present

Provision of information in the report is requested.

MbmsSaId

not present

Provision of information in the report is not requested.

MbsfnArea

not present

Provision of information in the report is not requested.

GeographicalCoordinate

present

Provision of information in the report is requested.

minimumIntervalLength

"70"

the value in seconds

TriggeringCriteria

PLMNChange

AnyPLMNChange

TriggerID

"ANY PLMN"

PeriodicReport

extension base

"60"

the value in seconds of the time which determines the periodic provision of the report

TiggerID

"PERIODIC"

Table 6.3.1.3.3-11: SIP MESSAGE (Step 11, Table 6.3.1.3.2-1)

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

Information Element

Value/remark

Comment

Reference

Condition

Content-Type

"multipart/mixed;boundary="any allowed value

Content-Length

length of message body

Message-body

MIME-Content-Type

not present

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

MIME-Content-Type

not present

"application/vnd.3gpp.mcptt-affiliation-command+xml"

MIME-Content-Type

"application/vnd.3gpp.mcptt-location-info+xml"

"application/vnd.3gpp.mcptt-affiliation-command+xml"

TS 24.379 [9] clause F.3

Location-Info

As described in Table 6.3.1.3.3-12

Table 6.3.1.3.3-12: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-11)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

TriggerID

"ANY PLMN"

CurrentLocation

CurrentServingEcgi

The ECGI of Cell 4

NeighbouringEcgi

not present

Only Cell 4 is active at this moment of time (see TS 36.579-1 [2], subclause 5.4.9)

CurrentCoordinate

The location simulated by the GNSS simulator at the time of transmission of the message.

longitude

The longitude value as specified for location number #8 defined in TS 36.508 [24] Table 4.11.2-3 +/- 0.00016 degrees.

latitude

The latitude value as specified for location number #8 defined in TS 36.508 [24] Table 4.11.2-3 +/- 0.00013 degrees.

ReportType

"NonEmergency"

Table 6.3.1.3.3-13: SIP MESSAGE (Step 14, Table 6.3.1.3.2-1)

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

Information Element

Value/remark

Comment

Reference

Condition

Content-Type

"multipart/mixed;boundary="any allowed value

Content-Length

length of message body

Message-body

MIME-Content-Type

not present

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

MIME-Content-Type

not present

"application/vnd.3gpp.mcptt-affiliation-command+xml"

MIME-Content-Type

"application/vnd.3gpp.mcptt-location-info+xml"

"application/vnd.3gpp.mcptt-affiliation-command+xml"

TS 24.379 [9] clause F.3

Location-Info

As described in Table 6.3.1.3.3-14

Table 6.3.1.3.3-14: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-13)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

TriggerID

"PERIODIC"

CurrentLocation

CurrentServingEcgi

The ECGI of Cell 4

NeighbouringEcgi

not present

CurrentCoordinate

The location simulated by the GNSS simulator at the time of transmission of the message.

longitude

The longitude value as specified for location number #8 defined in TS 36.508 [24] Table 4.11.2-3 +/- 0.00016 degrees.

latitude

The latitude value as specified for location number #8 defined in TS 36.508 [24] Table 4.11.2-3 +/- 0.00013 degrees.

ReportType

"NonEmergency"

6.3.2 On-network / Location/ On-demand Location Information Request

6.3.2.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client)registered and authorized for MCPTT service and not in an emergency state and having received a location information configuration message providing configuration parameters for both NonEmergencyLocationInformation and EmergencyLocationInformation }

ensure that {

when { UE (MCPTT Client) receives a location information request before the minimumReportInterval timer has expired }

then { UE (MCPTT Client)does not wait for the minimumReportInterval timer to expire, and, sends"immediately" a SIP MESSAGE containing location information report including information in accordance with the NonEmergencyLocationInformation configuration and the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request, and, resets the minimumReportInterval timer }

}

(2)

with { UE (MCPTT Client)registered and authorized for MCPTT service and not in an emergency state and having received a location information configuration message }

ensure that {

when { UE (MCPTT Client) receives a new location information configuration message and ConfigScope set to ‘Full’ }

then { UE (MCPTT Client) stores the contents of the <Configuration> elements thereby overriding the previous configuration }

}

6.3.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379, clauses 13.3.1, 13.3.2, 13.3.3, 13.3.4.2, F.3.3. Unless otherwise stated, these are Rel-13 requirements.

[TS 24.379 clause 13.3.2]

The MCPTT client sends a location report when one of the trigger criteria is fulfilled or when it receives a request from the participating MCPTT function to send a location report. To send the location report the MCPTT client can use an appropriate SIP message that it needs to send for other reasons, or it can include the location report in a SIP MESSAGE request.

To send a location report, the MCPTT client includes in the SIP MESSAGE request an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3. The MCPTT client populates the elements in accordance with its reporting configuration. Further location information may also be included in the P-Access-Network-Info header field.

[TS 24.379 clause 13.3.2]

Upon receiving a SIP MESSAGE request containing:

1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";

2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and

3) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Configuration> root element included in the <location-info> root element;

then the MCPTT client:

1) shall store the contents of the <Configuration> elements;

…

3) shall start the minimumReportInterval timer.

[TS 24.379 clause 13.3.3]

Upon receiving a SIP MESSAGE request containing

1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";

2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and

3) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Request> element included in the <location-info> root element;

then the MCPTT client:

1) shall send a location report as specified in subclause 13.3.4; and

2) shall reset the minimumReportInterval timer.

[TS 24.379 clause 13.3.4.2]

If the MCPTT client does not need to send a SIP request for other reasons, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The MCPTT client;

1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration;

2) shall include a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml";

3) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include:

a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request;

…

4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcptt along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6];

5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer;

…

7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].

[TS 24.379 clause F.3.3]

<Configuration> element has a <ConfigScope> attribute that can assume the values "Full" and "Update". The value "Full" means that the Configuration> element contains the full location configuration which replaces any previous location configuration. The value "Update" means that the location configuration is in addition to any previous location configuration. To remove configuration elements a "Full" configuration is needed. The <Configuration> element contains the following child elements:

6.3.2.3 Test description

6.3.2.3.1 Pre-test conditions

System Simulator:

– SS (MCPTT 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 and Cell 2 shall belong to PLMN1 (the PLMN specified for MCPTT operation in the MCPTT configuration document).

IUT:

– UE (MCPTT client)

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

Preamble:

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

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

– UE States at the end of the preamble

– The UE is in E-UTRA Registered, Idle Mode state on Cell 1 (Serving cell).

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

6.3.2.3.2 Test procedure sequence

Table 6.3.2.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Void.

–

–

–

–

1-1AB

Steps 1a1 to 3 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 are performed to configure a location reporting containing configuration parameters for both NonEmergencyLocationInformation and EmergencyLocationInformation, and, minimumReportInterval timer set to 20 sec and, periodic trigger criteria with PeriodicReport reporting interval set to 15 sec. NOTE: The handling of the PeriodicReport is not tested in this test. It is added here for the purpose of verifying that the UE restarts the minimumReportInterval – when the Periodic report trigger fires before the expiration of the minimumReportInterval the UE needs to wait for its expiry before sending the periodic report.

–

–

–

–

1A

Start timer t_Wait=10s (NOTE 1)

–

–

–

–

1B

Start timer t_PeriodicReport=15s (PeriodicReport timer set in step 1).

–

–

–

–

–

EXCEPTION: The SS waits 2 seconds before it releases the RRC connection

–

–

–

–

1C

t_Wait expires.

–

–

–

–

2-2B

Steps 1a1 to 3 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 are performed to request an on-demand location report.

–

–

–

–

3-3AA

Check: Does the UE (MCPTT Client) correctly perform steps 2 to 3 of the procedure for MCX SIP MESSAGE CO as described in TS 36.579-1 [2] Table 5.3.32.3-1 before t_PeriodicReport expires containing the location information report with the correct ReportID providing only the parameters set in the NonEmergencyLocationInformation configuration provided in step 1?

–

–

1

P

3A

Start timer t_MinimumReportInterval=20s

–

–

–

–

3B

Stop timer t_PeriodicReport

–

–

–

–

–

EXCEPTION: The SS waits 2 seconds before it releases the RRC connection

–

–

–

–

3C

Void.

–

–

–

–

3D

t_MinimumReportInterval expires

–

–

–

–

3E-3G

Check: Does the UE (MCPTT Client) correctly perform steps 1a1 to 3 of the procedure for MCX SIP MESSAGE CO as described in TS 36.579-1 [2] Table 5.3.32.3-1 containing the SIP MESSAGE periodic trigger identification along with location information report?

–

–

1

P

4-4A

Steps 2 to 3 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 are performed changing some of the parameters and not including periodic trigger criteria, and, ConfigScope set to ‘Full’.

–

–

–

–

5-5A

Steps 2 to 3 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 are performed to request an on-demand location reporting request.

–

–

–

–

6-6A

Check: Does the UE (MCPTT Client) correctly perform steps 2 to 3 of the procedure for MCX SIP MESSAGE CO as described in TS 36.579-1 [2] Table 5.3.32.3-1 containing the location information report with the correct ReportID and in accordance with the latest configuration parameters provided in step 4?

–

–

2

P

7-8

Void.

–

–

–

–

9

Check: Does the UE (MCPTT Client) send any SIP MESSAGE in the next 25s?

—>

SIP MESSAGE

2

F

EXCEPTION: The SS waits 2 seconds before it releases the RRC connection

NOTE 1: The value of 10s is arbitrary chosen. However, it needs to be long enough to ensure that if the UE did not reset the minimumReportInterval timer after it sent the message in step 3 the UE will send the SIP MESSAGE for the periodic reporting before step 3D and will fail, and, it needs to be short enough so that step 2 happens reasonably before t_PeriodicReport expires.

6.3.2.3.3 Specific message contents

Table 6.3.2.3.3-1: SIP MESSAGE from the SS (Step 1, Table 6.3.2.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 LOCATION-CONFIG

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCPTT-Info

MIME-part-body

MCPTT-info as described in Table 6.3.1.3.3-13

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-2

Table 6.3.2.3.3-2: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-1)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

NonEmergencyLocationInformation

ServingEcgi

not present

NeighbouringEcgi

not present

.

MbmsSaId

not present

MbsfnArea

not present

GeographicalCoordinate

present

Provision of <GeographicalCoordinate> in the report is requested.

minimumIntervalLength

"20"

TriggeringCriteria

PeriodicReport

extension base

"15"

the value in seconds of the time which determines the periodic provision of the report

TiggerID

"PERIODIC"

Table 6.3.2.3.3-3: SIP MESSAGE from the SS (Step 2, Table 6.3.2.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 LOCATION-INFO

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCPTT-Info

MIME-part-body

MCPTT-info as described in Table 6.3.1.3.3-13

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-4

Table 6.3.2.3.3-4: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-3)

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

Table 6.3.2.3.3-5: SIP MESSAGE from the UE (Step 3, Table 6.3.2.3.2-1;
step 2, TS 36.579-1 [2], Table 5.3.32.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.1-1 condition LOCATION-REPORT

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

Not present

MCPTT-Info

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-6

Table 6.3.2.3.3-6: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-5)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.4.1-1 condition LOCATION-INFO

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

ReportID attribute

"1"

The same as the ID in the request message.

ReportType attribute

"NonEmergency"

CurrentLocation

Contains the information corresponding to the location reporting configuration of table 6.3.2.3.3-2

CurrentServingEcgi

not present

NeighbouringEcgi

not present

MbmsSaId

not present

MbsfnArea

not present

CurrentCoordinate

longitude

Encrypted <longitude> with any content

Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.4.1-1

latitude

Encrypted <latitude> with any content

Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.4.1-1

Table 6.3.2.3.3-6A: SIP MESSAGE from the UE (Step 3E, Table 6.3.2.3.2-1;
step 2, TS 36.579-1 [2], Table 5.3.32.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.1-1 condition LOCATION-INFO

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

Not present

MCPTT-Info

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-6B

Table 6.3.2.3.3-6B: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-6A)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Report

ReportType attribute

"NonEmergency"

TriggerID

"PERIODIC"

CurrentLocation

Contains the information corresponding to the location reporting configuration of table 6.3.2.3.3-2

CurrentServingEcgi

not present

NeighbouringEcgi

not present

MbmsSaId

not present

MbsfnArea

not present

CurrentCoordinate

longitude

Encrypted <longitude> with any content

Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.4.1-1

latitude

Encrypted <latitude> with any content

Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.4.1-1

Table 6.3.2.3.3-7: SIP MESSAGE from the SS (Step 4, Table 6.3.2.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 LOCATION-CONFIG

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCPTT-Info

MIME-part-body

MCPTT-info as described in Table 6.3.1.3.3-13

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-8

Table 6.3.2.3.3-8: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-7)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Configuration

NonEmergencyLocationInformation

ServingEcgi

present

Provision of <ServingEcgi> in the report is requested.

NeighbouringEcgi

not present

MbmsSaId

not present

MbsfnArea

not present

GeographicalCoordinate

not present

Table 6.3.2.3.3-9: SIP MESSAGE from the SS (Step 5, Table 6.3.2.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 LOCATION-INFO

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

MCPTT-Info

MIME-part-body

MCPTT-info as described in Table 6.3.1.3.3-13

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-10

Table 6.3.2.3.3-10: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-9)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

Request

RequestID

"2"

The RequestID that the MCPTT Client shall reference in the Report

Table 6.3.2.3.3-11: SIP MESSAGE from the UE (Step 6, Table 6.3.2.3.2-1;
step 2, TS 36.579-1 [2], Table 5.3.32.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.7.1-1 condition LOCATION-REPORT

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

Not present

MCPTT-Info

MIME body part

Location info

TS 24.379 [9] clause F.3

MIME-part-body

Location-info as described in Table 6.3.1.3.3-12

Table 6.3.2.3.3-12: Location-Info in SIP MESSAGE (Table 6.3.2.3.3-11)

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

Information Element

Value/remark

Comment

Reference

Condition

location-info

present

Report

present

ReportID

"2"

The same as the ID in the request message.

ReportType

"NonEmergency"

CurrentLocation

present

Contains the information corresponding to the location reporting configuration of table 6.3.2.3.3-8

CurrentServingEcgi

Encrypted <CurrentServingEcgi> with any content

Encryption according to NOTE 1 in TS 36.579-1 [2] Table 5.5.3.4.1-1

NeighbouringEcgi

not present

MbmsSaId

not present

MbsfnArea

not present

CurrentCoordinate

not present

Table 6.3.2.3.3-13: MCPTT-Info in SIP MESSAGE (Table 6.3.2.3.3-1, 6.3.2.3.3-3, 6.3.2.3.3-7, 6.3.2.3.3-9)

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

Information Element

Value/remark

Comment

Reference

Condition

mcpttinfo

mcptt-Params

mcptt-calling-user-id

not present