Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.486  Word version:  17.1.0

Top   Top   Up   Prev   Next
1…   6…   6.8…   6.10…   7…   8…

 

6  VAE proceduresWord‑p. 10

6.1  GeneralWord‑p. 10

Void

6.2  V2X UE registration procedureWord‑p. 10

6.2.1  Client procedureWord‑p. 10

Upon receiving a request from a V2X application to register for receiving V2X messages from the V2X AS, the VAE-C 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 message for 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 <registration-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE which requests the registration;
    2. shall include a <reception-uri> element set to the URI for subsequent messages to the VAE-C; and
    3. shall include one or more <V2X-service-id> element(s), each element set to the V2X service ID which the V2X UE is interested in receiving; and
  4. shall send the HTTP POST request towards the VAE-S according to RFC 7231.
Up

6.2.2  Server procedureWord‑p. 10

Upon reception of 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 <registration-info> element in the <VAE-info> root element
the VAE-S:
  1. shall store the received registration information;
  2. shall generate an HTTP 200 (OK) response according to RFC 7231. In the HTTP 200 (OK) response message, the VAE-S:
    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 and in the <VAE-info> root element:
      1. shall include a <registration-info> element with a <result> child element set to the value "success" or "failure" indicating success or failure of the registration; and
      2. if success and if the V2X service IDs as present in the <registration-info> element of the received HTTP POST request is not fully acceptable to the VAE-S, the VAE-S may change the V2X service IDs to a subset and shall include one or more <V2X-service-id> child elements set to the identities of the new V2X service IDs; and
    3. shall send the HTTP 200 (OK) response towards the VAE-C.
Up

6.3  V2X UE de-registration procedureWord‑p. 11

6.3.1  Client procedureWord‑p. 11

Upon receiving a request from a V2X application to de-register for receiving certain V2X service-IDs from the V2X AS, the VAE-C shall send 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 message for 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 <de-registration-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of a UE which requests the de-registration; and
    2. shall include one or more <V2X-service-id> child element(s), each element set to the V2X service ID that the UE is no longer interested in receiving; and
  4. shall send the HTTP POST request towards the VAE-S according to RFC 7231.
Up

6.3.2  Server procedureWord‑p. 11

Upon reception of 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 <de-registration-info> element in the <VAE-info> element in the <VAE-info> element,
the VAE-S:
  1. shall remove the received V2X service IDs from registration information corresponding to the V2X UE;
  2. shall generate an HTTP 200 (OK) response according to RFC 7231. In the HTTP 200 (OK) response message, the VAE-S:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
    2. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <VAE-info> root element:
      1. shall include a <de-registration-info> element with a <result> child element set to the value "success" or "failure" indicating success or failure of the de-registration; and
  3. shall send the HTTP 200 (OK) response towards the VAE-C.
Up

6.4  Application level location tracking procedureWord‑p. 11

6.4.1  Client procedureWord‑p. 11

Upon entering a new geographical area if the V2X UE has been provisioned with geographical identifier groups (see clause 7) and the V2X UE has subscribed to a certain geographical area identifier group in order to receive V2X messages from the V2X AS for this area, the VAE-C shall send 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 message for V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <location-tracking-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE that subscribes to a geographical area;
    2. shall include a <geo-id> element set to the identity of the geographical area to be subscribed, i.e. the new geographical area where the UE entered; and
    3. shall include an <operation> element set to "subscribe".
Upon a successful subscription to a geographical area, the VAE-C shall send 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 message 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"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <location-tracking-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE that unsubscribes to a geographical area;
    2. shall include a <geo-id> element set to the identity of the geographical area to be unsubscribed, i.e. the old geographical area where the UE exited; and
    3. shall include an <operation> element set to "unsubscribe".
Up

6.4.2  Server procedureWord‑p. 12

Upon reception of 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 <VAE-info> root element with a <location-tracking-info> element with a <V2X-UE-id> element and an <operation> element set to "subscribe",
the VAE-S:
  1. shall store the received geographical area information and associate this area with the UE identity provided in the <V2X-UE-id> element;
  2. shall generate an HTTP 200 (OK) response according to RFC 7231. In the HTTP 200 (OK) response message, the VAE-S:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
    2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <location-tracking-info> element in the <VAE-info> root element:
      1. shall include a <result> child element set to the value "success" or "failure" indicating success or failure of the subscription; and
      2. shall include an <operation> element set to "subscribe"; and
  3. shall send the HTTP 200 (OK) response towards the VAE-C.
Upon reception of 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-registration-+xml MIME body with a <VAE-info> root element with a <location-tracking-info> element with an <V2X-UE-id> element and an <operation> element set to "unsubscribe",
the VAE-S:
  1. shall remove the received geographical area information associated with the UE identity provided in the <V2X-UE-id> element;
  2. shall generate an HTTP 200 (OK) response according to RFC 7231. In the HTTP 200 (OK) response message, the VAE-S:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
    2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <location-tracking-info> element in the <VAE-info> root element:
      1. shall include a <result> child element set to the value "success" or "failure" indicating success or failure of the unsubscription; and
      2. shall include an <operation> element set to "unsubscribe"; and
  3. shall send the HTTP 200 (OK) response towards the VAE-C.
Up

6.5  V2X message delivery procedureWord‑p. 13

6.5.1  Client procedureWord‑p. 13

6.5.1.1  Reception of a V2X messageWord‑p. 13

Upon receiving an HTTP POST request 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 <payload>element included in the <message-info> element in the <VAE-info> root element;
the VAE-C:
  1. shall provide the received information to the V2X application identified by the service indicated in the V2X message, if the identity or group of theV2X message matches the identity of the V2X UE or the group of the VAE client; and
  2. shall send a V2X message reception report as specified in clause 6.5.1.3 if the <message-reception-ind> element and <message-reception-uri> element are included in the received V2X message.
Up

6.5.1.2  Reception of a V2X message reception reportWord‑p. 13

Upon receiving an HTTP POST request 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 <result> element included in the <message-info> root element;
the VAE-C:
  1. evaluates the content of the <result> element.

6.5.1.3  Sending of a V2X message reception reportWord‑p. 13

In order to send a V2X message reception report, the VAE-C shall generate an HTTP 200(OK) response message according to procedures specified in RFC 7231. In the HTTP 200(OK) message, the VAE-C:
  1. shall set the Request-URI to the URI included in the <message-reception-uri> element in the received HTTP POST request message 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"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <reception-report> element included in the <VAE-info> root element. In the <reception-report> element, the VAE-C:
    1. shall include a <result> element set to a value "success" or "fail" indicating success or failure of the V2X message reception.
Up

6.5.1.4  Sending of a V2X messageWord‑p. 14

In order to send a V2X message, the VAE-C shall send an HTTP POST request message according to procedures specified in RFC 7231. In the HTTP POST request message, the VAE-C:
  1. shall set the Request-URI to the URI included in the received HTTP response message for V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <message-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE which requests the sending of the V2X message;
    2. shall include a <V2X-service-id> element set to the identity of the V2X service which is interested in sending the V2X message;
    3. may include one or more <geo-id> element(s), each element set to the identity of the geographical area containing the location of the V2X UE;
    4. may include a <message-reception-ind> element to indicate to the VAE server that a reception report is required; and
    5. if a <message-reception-ind> element is included, shall include a <message-reception-uri> element set to the URI for a response to the VAE-C.
Up

6.5.2  Server procedureWord‑p. 14

6.5.2.1  Reception of a V2X messageWord‑p. 14

Upon receiving an HTTP POST request 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 <payload> element included in the <message-info> element in the <VAE-info> root element;
the VAE-S:
  1. shall provide the received information to the V2X application server identified by the service indicated in the V2X message; and
  2. shall send a V2X message reception report as specified in clause 6.5.2.3 if the <message-reception-ind> element and <message-reception-uri> element are included in the received V2X message.
Up

6.5.2.2  Reception of a V2X message reception reportWord‑p. 14

Upon receiving an HTTP POST request 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 <result> element included in the <message-info> element in the <VAE-info> root element;
the VAE-S:
  1. evaluates the content of the <result> element.

6.5.2.3  Sending of a V2X message reception reportWord‑p. 15

In order to send a V2X message reception report, the VAE-S shall send a HTTP POST request message according to procedures specified in RFC 7231. In the HTTP POST request message, the VAE-S:
  1. shall set the Request-URI to the URI included in the <message-reception-uri> element in the received HTTP POST request message for reception of a V2X message (see clause 6.5.2.1);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and a <result> element of the <message-info> element set to a value "success" or "fail".
Up

6.5.2.4  Sending of a V2X message to target geographical areasWord‑p. 15

In order to send a V2X message received from a V2X application server to target geographical areas, the VAE-S shall send a HTTP POST request message to each VAE-C associated with the target geographical area according to procedures specified in RFC 7231. In each HTTP POST request message, the VAE-S:
  1. shall set the Request-URI to the URI included in the received HTTP response message for V2X UE registration procedure (see clause 6.2) for the VAE-C identified by a <V2X-UE-id> element, determined by association from the target geographical area indicated by the V2X application server;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <message-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE to receive the V2X message, determined by association from the target geographical area indicated by the V2X application server;
    2. shall include a <V2X-service-id> element set to the identity of the V2X service which is interested in sending the V2X message;
    3. may include a <geo-id> element set to the identity of the geographical area containing the location of the V2X UE;
    4. may include a <message-reception-ind> element to indicate to the VAE server that a reception report is required; and
    5. if a <message-reception-ind> element is included, shall include a <message-reception-uri> element set to the URI for a response to the VAE-S.
Up

6.5.2.5  Sending of a V2X message to a V2X groupWord‑p. 15

In order to send a V2X message received from a V2X application server, the VAE-S shall send a HTTP POST request message according to procedures specified in RFC 7231 to each VAE-C which has registered for the V2X message delivery service. In the HTTP POST request message, the VAE-S:
  1. shall set the Request-URI to the URI of each VAE-C registered for V2X message delivery service (see clause 6.2);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <message-info> root element:
    1. shall include a <V2X-group-id> child element set to the V2X group identity of the VAE-C to receive the V2X message, determined by registration with the identity of the V2X group indicated by the V2X application server;
    2. shall include a <V2X-service-id> element set to the identity of the V2X service which is interested in sending the V2X message;
    3. may include a <geo-id> element set to the identity of the geographical area applicable for the V2X message;
    4. may include a <message-reception-ind> element to indicate to the VAE-C that a reception report is required; and
    5. if a <message-reception-ind> element is included, shall include a <message-reception-uri> element set to the URI for a response to the VAE-C.
Up

6.6  V2X service discovery procedureWord‑p. 16

6.6.1  Client procedureWord‑p. 16

In order to discover V2X service information from a VAE-S (e.g. available VAE services identified by V2X service identities), the VAE-C shall send 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 received in the VAE client UE configuration document via the SCM-S;
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <service-discovery-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE which requests the service discovery.
Up

6.6.2  Server procedureWord‑p. 16

Upon reception of 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 <service-discovery-info> element in the <VAE-info> root element,
the VAE-S:
  1. shall generate an HTTP 200 (OK) response according to RFC 7231. In the HTTP 200 (OK) response message, the VAE-S:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
    2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <service-discovery-info> element in the <VAE-info> root element:
      1. shall include a <result> child element set to the value "success" or "failure" indicating success or failure of getting the service discovery information; and
      2. if <result> element is set to "success", shall include a <service-discovery-data> element with one or more <V2X-service-map> element(s), each <V2X-service-map> element shall include:
        1. one or more <V2X-service-id> element(s) set to the identities of the available V2X service IDs; and
        2. a <V2X-AS-address> element set to the V2X AS address; and
    3. shall send the HTTP 200 (OK) response towards the VAE-C.
Up

6.7  V2X service continuity procedureWord‑p. 16

6.7.1  Client procedureWord‑p. 16

In order to obtaining dynamic local V2X service information from a VAE-S, the VAE-C shall send 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 message for V2X service discovery procedure (see clause 6.6);
  2. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  3. shall include an application/vnd.3gpp.vae-info+xml MIME body and in the <local-service-info> element in the <VAE-info> root element:
    1. shall include a <V2X-UE-id> element set to the identity of the UE which requests the local service information; and
    2. shall include a <geo-id> element set to the identity of the geographical area for which the local service information is requested.
Up

6.7.2  Server procedureWord‑p. 17

Upon reception of 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 <V2X-UE-id> element and a <geo-id> element in the <local-service-info> element in the <VAE-info> root element;
the VAE-S:
  1. shall determine the local service information (e.g. V2X server USD(s), V2X USD) corresponding to the geographical location information received in <geo-id>; and
  2. shall generate an HTTP 200 (OK) response according to RFC 7231. In the HTTP 200 (OK) response message, the VAE-S:
  3. shall include a Content-Type header field set to "application/vnd.3gpp.vae-info+xml"; and
  4. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <local-service-info> element in the <VAE-info> root element:
    1. shall include a <result> child element set to the value "success" or "failure" indicating success or failure of getting the local service information; and
    2. if the result is "success", the VAE-S shall include a <local-service-info-content> element which provides the local service information to the VAE-C; and
  5. shall send the HTTP 200 (OK) response towards the VAE-C.
Up

Up   Top   ToC