18 Location procedures

24.2813GPPMission Critical Video (MCVideo) signalling controlProtocol specificationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

18.1 General

If the participating MCVideo function needs to obtain location information, the participating MCVideo function configures the MCVideo client upon successful service authorization. The configuration contains information the MCVideo client uses to set up filter criteria for when the MCVideo client shall send location reports to the participating MCVideo function.

The participating MCVideo function can also explicitly request the MCVideo client to send a location report.

The MCVideo client will, based on the received configuration or when explicitly requested, send location reports.

The location information is used by the participating MCVideo function to determine whether to use MBMS bearers or not as described in clause 16.

18.2 Participating MCVideo function location procedures

18.2.1 General

The participating MCVideo function has procedures to:

– configure the location reporting at the UE;

– request the UE to report the location of the UE; and

– receive a location information report from the UE.

18.2.2 Location reporting configuration

The participating MCVideo function may configure the location reporting in the MCVideo client by generating a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The participating MCVideo function:

1) shall include a Request-URI set to the URI corresponding to the identity of the MCVideo client;

2) shall include 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.mcvideo" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [20];

3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-request-uri> element containing the MCVideo ID of the MCVideo user to receive the configuration;

4) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body with the <Configuration> element contained in the <location-info> root element set to the desired configuration;

5) shall include the TriggerId attribute where defined for the sub-elements defining the trigger criterion;

6) shall include the public service identity of the participating MCVideo function in the P-Asserted-Identity header field;

7) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and

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

18.2.3 Location information request

If the participating MCVideo function needs to request the MCVideo client to report its location, the participating MCVideo functions shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The participating MCVideo function:

1) shall include a Request-URI set to the URI corresponding to the identity of the MCVideo client;

3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-request-uri> element containing the MCVideo ID of the MCVideo user;

4) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body with a <Request> element contained in the <location-info> root element;

5) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and

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

18.2.4 Location information report

If the participating MCVideo function receives a SIP request containing:

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

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

then the participating MCVideo function shall authorise the location report based on the MCVideo ID received. If the MCVideo user is authorised to send a location report the participating MCVideo function:

1) shall use the location information as needed;

2) shall follow the procedure of clause 6.3.3.1.20, if the MCVideo client has entered into or exited from an emergency alert area; and

3) shall follow the procedure of clause 6.3.3.1.21, if the MCVideo client has entered into or exited from a group geographic area.

NOTE: The <Report> element contains the event triggering identity in the location information report from the UE, and can contain location information.

18.2.5 Abnormal cases

Upon receipt of a SIP request:

1) where the P-Asserted-Identity identifies a public user identity not associated with an MCVideo user served by the participating MCVideo function; or

2) with a MIME body with Content-Type header field set to "application/vnd.3gpp.mcvideo-info+xml" and with a <mcvideo-request-URI> element containing an MCVideo ID that identifies an MCVideo user served by the participating MCVideo function;

then, when the SIP request contains:

1) an Accept-Contact header field with the g.3gpp.mcvideo media feature tag;

2) an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and

3) an application/vnd.3gpp.mcvideo-location-info+xml MIME body containing a <Request> element or a <Configuration> element;

the participating MCVideo function shall remove the application/vnd.3gpp.mcvideo-location-info+xml MIME body when sending a SIP request.

18.3 MCVideo client location procedures

18.3.1 General

The MCVideo client sends a location report when one of the trigger criteria is fulfilled or when it receives a request from the participating MCVideo function to send a location report. To send the location report the MCVideo 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 MCVideo client includes in the SIP MESSAGE request an application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause F.3. The MCVideo 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.

18.3.2 Location reporting configuration

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.mcvideo";

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

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

then the MCVideo 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.

18.3.3 Location information request

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.mcvideo";

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

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

then the MCVideo client:

1) shall send a location report as specified in clause 18.3.4; and

2) shall reset the minimumReportInterval timer.

18.3.4 Location information report

18.3.4.1 Report triggering

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

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

If the MCVideo client receives a location information request as specified in clause 18.3.3, the MCVideo client shall send a location report as specified in clause 18.3.4.2.

18.3.4.2 Sending location information report

If the MCVideo client needs to send a SIP request for other reasons (e.g. a SIP MESSAGE request containing an MBMS listening report as described in clause 16), the MCVideo client:

1) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body and in the <location-info> root element the MCVideo client shall 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) <TriggerId> child elements, where each element is set to the value of the <Trigger-Id> attribute associated with the trigger that have fired; and

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

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

3) shall reset all triggers.

If the MCVideo client does not need to send a SIP request for other reasons, the MCVideo client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The MCVideo 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.mcvideo-location-info+xml";

3) shall include an application/vnd.3gpp.mcvideo-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.mcvideo along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [20];

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 [11].