Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.486  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   6…   6.8…   6.10…   7…   8… 
6.10 PC5 Provisioning in multi-operator V2X scenarios procedure  6.11 Obtaining dynamic information of the UEs in proximity range procedure  6.12 V2X groupcast/broadcast configuration by VAE layer procedure  6.13 Session-oriented services procedure  6.14 Switching modes of operations for V2V communications procedure 
...

 

6.10  PC5 Provisioning in multi-operator V2X scenarios procedure |R17|  p. 23

6.10.1  Client procedure  p. 23

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <PC5-provisioning-status-info> element;
    the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  3. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  4. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  5. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <PC5-provisioning-status-info> element included in the <VAE-info> root element which:
    1. shall include a <result> element set to the value "success" or "failure" indicating success or failure of the PC5 provisioning status request; and
    2. shall include a <PC5-policy-status-report> corresponding to the PC5 policy status request; and
  6. shall send the HTTP 200(OK) response towards the VAE-S according to RFC 7231.
Up

6.10.2  Server procedure  p. 23

Upon receiving a V2X PC5 provisioning requirement from the V2X application specific server, the VAE-S:
    a) may generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
    1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
    2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
    3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <PC5-provisioning-status-info> element in the <VAE-info> root element which:
      1. shall include a <VAE-server-id> element set to the identity of the VAE server which is requester of the PC5 parameters status;
      2. shall include a <V2X-service-id> element set to the identity of the V2X service for which the VAE server's request corresponds to; and
      3. may include a <PC5-provisioning-status-report-configuration> element set to the configuration of the VAE-client reporting related to the PC5 Policy status, and optionally PC5 events like PC5 unavailability, PQI load info; and
    4. shall send the HTTP POST request towards the VAE-C according to RFC 7231;
Up

6.11  Obtaining dynamic information of the UEs in proximity range procedure |R17|  p. 24

6.11.1  Client procedure  p. 24

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <subscribe-dynamic-info> element;
the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <subscribe-dynamic-info> element included in the <VAE-info> root element which:
    1. shall include a <result> element set to the value "success" or "failure" indicating success or failure of the subscribe dynamic information request; and
    2. shall include a <configuration-report> element corresponding to the <reporting-configuration> element; and
  4. shall send the HTTP 200(OK) response towards the VAE-S according to RFC 7231.
Up

6.11.2  Server procedure  p. 24

In order to manage the dynamic UE location group, the VAE-S shall generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <subscribe-dynamic-info> element in the <VAE-info> root element which:
    1. shall include a <V2X-UE-id> element set to the identity of the UE who are part of the dynamic UE location group; and
    2. shall include a <reporting-configuration> element indicating which configuration the UE should report (e.g. frequency of reporting, event based); and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
Up

6.12  V2X groupcast/broadcast configuration by VAE layer procedure |R17|  p. 25

6.12.1  Client procedure  p. 25

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <V2X-groupcast/broadcast-configuration-info> element;
the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <V2X-groupcast/broadcast-configuration-info> element included in the <VAE-info> root element which:
    1. shall include a <result> element set to the value "success" or "failure" indicating success or failure of the V2X groupcast/broadcast configuration request; and
  4. shall send the HTTP 200(OK) response towards the VAE-S according to RFC 7231.
Up

6.12.2  Server procedure  p. 25

Upon receiving an V2V configuration requirement request from the V2X application specific server, the VAE-S shall generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <V2X-groupcast/broadcast-configuration-info> element in the <VAE-info> root element which:
    1. shall include a <V2X-server-id> element set to the identity of the VAE server which is requester of the V2X groupcast/broadcast configuration;
    2. shall include a <V2X-group-id> element set to the V2X group identity for which the V2X groupcast/broadcast configuration is requested;
    3. shall include a <V2X-service-id> element set to the V2X service ID for which the groupcast/broadcast configuration is requested;
    4. shall include a <PC5-provisioning-policies> element indicating the PC5 provisioning policies/parameters to be used by the V2X-UEs within the V2X service;
    5. may include a <relay-V2X-UE-id-list> element which shall include one or more <V2X-UE-id> child element(s), each of which set to the identity of the V2X UE to serve as application layer relays; and
    6. may include a <minimum-number-of-transmissions> element set to the minimum number of allowed re-transmissions for the V2X message delivery; and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
Up

6.13  Session-oriented services procedure |R17|  p. 26

6.13.1  Client procedure  p. 26

6.13.1.1  UE initiated session-oriented service establishment  p. 26

In order to establish a session-oriented service with one or more V2X UEs (remote vehicle), the VAE-C (acting as remote controller) shall generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-service-trigger-info> element included in the <VAE-info> root element which:
    1. shall include a <V2X-UE-id> element set to the identity of the V2X UE which is the remote vehicle;
    2. shall include a <V2X-service-id> element set to the V2X service ID for which application requirement corresponds to;
    3. shall include a <V2X-application-specific-server-id-info> element set to the identity information of the V2X application specific server;
    4. may include a <session-id> element set to the session identifier to be used for the session-oriented service; and
    5. may include a <V2X-application-QoS-requirements> element indicating the application QoS requirements (reliability, delay, jitter) for the session-oriented service; and
  4. shall send the HTTP POST request towards the VAE-S according to RFC 7231.
Up

6.13.1.2  UE initiated session-oriented service update  p. 26

In order to update a session-oriented service with one or more V2X UEs (remote vehicle), the VAE-C (acting as remote controller) shall generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-change-trigger-info> element included in the <VAE-info> root element which shall include:
    1. a <session-id> element set to the session identifier of the session-oriented service; and
    2. a <V2X-application-QoS-requirements> element indicating the application QoS requirements (reliability, delay, jitter) for the session-oriented service that is to be updated; and
  4. shall send the HTTP POST request towards the VAE-S according to RFC 7231.
Up

6.13.1.3  UE initiated session-oriented service termination  p. 26

In order to terminate a session-oriented service with one or more V2X UEs (remote vehicle), the VAE-C (acting as remote controller) shall generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-termination-trigger-info> element included in the <VAE-info> root element which shall include:
    1. a <session-id> element set to the session identifier of the session-oriented service that is to be terminated; and
  4. shall send the HTTP POST request towards the VAE-S according to RFC 7231.
Up

6.13.1.4  Session-oriented service establishment  p. 27

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-service-info> element;
the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in IETF RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-service-info> element included in the <VAE-info> root element which shall include:
    1. an <acknowledgement> element indicating the acknowledgement for the request; and
  3. shall send the HTTP POST request towards the VAE-S according to IETF RFC 7231 and send a session-oriented service establish notification to the V2X application-specific client.
Up

6.13.1.5  Session-oriented service update  p. 27

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-change-info> element;
the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in IETF RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-change-info> element included in the <VAE-info> root element which shall include an <acknowledgement> child element indicating the acknowledgement for the change request; and
  3. shall send the HTTP POST request towards the VAE-S according to IETF RFC 7231 and send a session-oriented service change notification to the V2X application-specific client.
Up

6.13.1.6  Session-oriented service termination  p. 27

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-termination-info> element;
the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in IETF RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-termination-info> element included in the <VAE-info> root element which shall include an <acknowledgement> element indicating the acknowledgement for the termination request; and
  3. shall send the HTTP POST request towards the VAE-S according to IETF RFC 7231 and send a session-oriented service termination notification to the V2X application-specific client.
Up

6.13.2  Server procedure  p. 28

6.13.2.1  UE initiated session-oriented service establishment  p. 28

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-service-trigger-info> element,
the VAE-S shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-service-trigger-info> element in the <VAE-info> root element which shall include an <acknowledgement> element indicating the acknowledgement for the request; and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
If the VAE-S acknowleges the request, the VAE-S shall perform the procedure to establish session oriented service with VAE client (e.g. remote vehicle) according to procedures specified in clause 6.13.2.4.
Up

6.13.2.2  UE initiated session-oriented service update  p. 28

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-change-trigger-info> element,
the VAE-S shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-change-trigger-info> element in the <VAE-info> root element which shall include an <acknowledgement> element indicating the acknowledgement for the request; and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
If the VAE-S acknowleges the request, the VAE-S shall perform the procedure to change session oriented service with VAE client (e.g. remote vehicle) according to procedures specified in clause 6.13.2.5.
Up

6.13.2.3  UE initiated session-oriented service termination  p. 28

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-termination-trigger-info> element,
the VAE-S shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-termination-trigger-info> element in the <VAE-info> root element which shall include a <result> element indicating success or failure to terminate the session-oriented service; and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
If the VAE-S terminates the requested session successfully, the VAE-S shall perform the procedure to terminate session oriented service with VAE client (e.g. remote vehicle) according to procedures specified in clause 6.13.2.6.
Up

6.13.2.4  Session-oriented service establishment  p. 29

Upon the request from the V2X application specific server or from the VAE client, in order to establish a session-oriented service with one or more VAE clients, the VAE-S shall generate an HTTP POST request according to procedures specified in IETF RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-service-info> element in the <VAE-info> root element which:
    1. shall include a <VAE-client-id> element set to the identity of the VAE client;
    2. shall include a <V2X-service-id> element set to the V2X service ID for which application requirement corresponds to;
    3. may include a <session-id> element set to the session identifier to be used for the session-oriented service; and
    4. shall include a <reporting-configuration> element indicating which configuration the UE should report (e.g. frequency of reporting, event based); and
  4. shall send the HTTP POST request towards the VAE-C according to IETF RFC 7231.
Up

6.13.2.5  Session-oriented service update  p. 29

Upon the request from the V2X application specific server or from the VAE client, in order to update a session-oriented service with one or more VAE clients, the VAE-S shall generate an HTTP POST request according to procedures specified in IETF RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-change-info> element in the <VAE-info> root element which:
    1. shall include a <session-id> element set to the session identifier of the session-oriented service that is to be updated; and
    2. may include a <V2X-application-QoS-requirements> element indicating the application QoS requirements (reliability, delay, jitter) for the session-oriented service that is to be updated;
    3. may include a <network-info> element indicating the change of network; and
    4. may include a <server-info> element indicationg the change of server; and
  4. shall send the HTTP POST request towards the VAE-C according to IETF RFC 7231.
Up

6.13.2.6  Session-oriented service termination  p. 30

Upon the request from the V2X application specific server or from the VAE client, in order to terminate a session-oriented service with one or more VAE clients, the VAE-S shall generate an HTTP POST request according to procedures specified in IETF RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <session-oriented-termination-info> element in the <VAE-info> root element which shall include a <session-id> element set to the session identifier of the session-oriented service that is to be terminated; and
  4. shall send the HTTP POST request towards the VAE-C according to IETF RFC 7231.
Up

6.14  Switching modes of operations for V2V communications procedure |R17|  p. 30

6.14.1  Client procedure  p. 30

Upon receiving an HTTP POST request message containing:
  1. a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  2. an application/vnd.3gpp.vae-info+xml MIME body with an <communication-status-info> element;
the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) response, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response for the V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <communication-status-info> element included in the <VAE-info> root element which:
    1. shall include a <V2X-UE-id> element set to the identity of the V2X UE;
    2. shall include a <V2V-communication-mode> element indicating which V2V communication mode supported by the V2X UE;
    3. may include a <V2X-service-id> element corresponding to the communication status;
    4. may include a <cell-info> element indicating the cell information of which the V2X UE is located; and
    5. may include a <communication-link-status-info> element indicating the communication status of the V2X UE; and
  4. shall send the HTTP 200(OK) response towards the VAE-S according to RFC 7231.
Up

6.14.2  Server procedure  p. 30

In order to provide the assistance for V2V communication mode switching, the VAE-S may have acquired the application requirement from the V2X application specific server and may generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <communication-status-info> element in the <VAE-info> root element which:
    1. shall include a <V2X-UE-id> element set to the identity of the V2X UE; and
    2. may include a <V2X-service-id> element set to the identity of the V2X service being requested; and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
Based on the reception of the network monitoring information from the 3GPP network or the communication status information from the <communication-link-status-info> element of an HTTP 200(OK) response, the VAE-S may generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall set the Request-URI to the URI corresponding to the identity of the V2X UE;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml";
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <V2V-communication-assistance-info> element in the <VAE-info> root element which:
    1. shall include a <V2X-UE-id> element set to the identity of the V2X UE;
    2. may include a <V2X-service-id> element set to the identity of the V2X service corresponding to the recommendation information; and
    3. shall include a <V2V-communication-assistance> element indicating the assistance information for V2V communication mode switching to the V2X UE; and
  4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.
Up

Up   Top   ToC