The V2X USD information is provided to the VAE-C to allow the V2X service to send V2X messages using MBMS.

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-USD-announcement> element;

the VAE-C:

1. shall store the received V2X USD information; and
2. if the SEAL layer (see TS 24.548) indicates that the V2X USD information was sent by unicast, the VAE-C shall send an acknowledgement of the V2X USD information to the VAE-S.

For each VAE-C that the VAE-S is sending a V2X USD announcement to, the VAE-S shall generate an HTTP POST request message 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-USD-announcement> element associated with the MBMS bearer used to send V2X messages 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. shall include a <V2X-USD-configuration-data> element set to the V2X USD configuration data as specified in TS 23.285 which:
      1. shall include a <TMGI> element set to a TMGI value;
      2. shall include one or more MBMS service area IDs in <mbms-service-area-id> elements in the <mbms-service-areas> element;
      3. if multiple carriers are supported, shall include the frequency to be used in the <frequency> element; and
      4. shall include a <V2X-mbms-sdp> element set to the SDP configuration information applicable to MBMS bearer to use for sending V2X messages; and
4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.

The PC5 parameters ares provided to the VAE-C to allow the V2X service to send V2X messages using V2X communication over PC5.

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 <set-PC5-parameters-info> element;

the VAE-C:

1. shall store the received PC5 parameters; and
2. shall send an HTTP 200(OK) response message including a <set-PC5-parameters-info> element with a <result> child element set to "success" or "failure" in the <VAE-info> root element as an acknowledgement of the PC5 parameters to the VAE-S.

For each VAE-C that the VAE-S is sending PC5 parameters to, the VAE-S shall generate an HTTP POST request message 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 <set-PC5-parameters-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 <PC5-parameters-configuration-data> element set to the PC5 parameters configuration data as specified in TS 23.285 which shall include:
      1. an <expiration-time> set to the validity of the configuration parameters for V2X communication over PC5;
      2. one or more <plmn-id> elements in the <plmn-list> element which indicate the PLMNs in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRAN for V2X communication;
      3. an <authorized-when-not-served-by-E-UTRAN> element which indicates that the UE is authorized to use V2X communication over PC5 when the UE is not served by E-UTRAN; and
      4. a <radio-parameters> element which shall include the following elements:
         1. one or more <radio-parameters-contents> elements set to the radio parameters for V2X communication over PC5 applicable when the UE is not served by E-UTRAN;
         2. a <geographical-area> element set to the geographical location where the radio parameters are applicable; and
         3. an <operator-managed> element which indicates that the radio parameters are "operator managed";
   3. may include one or more <V2X-service-id> elements and one or more <layer-2-id> elements in the <V2X-service-ids-list> element which indicate the V2X services authorized for V2X communication over PC5; and
   4. may include a <result> element set to either "success" or "failure" used to indicate success or failure of the PC5 parameters provisioning; and
4. shall send the HTTP POST request towards the VAE-C according to RFC 7231.