Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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.8  Dynamic group management procedurep. 18

6.8.1  On-network dynamic group creation procedurep. 18

6.8.1.1  Server procedurep. 18

Upon receiving a Configure Dynamic Group request from a V2X application specific server (see TS 29.486) the VAE-S shall assign a ProSe Layer-2 Group ID to the received dynamic group information from the available ProSe Layer-2 Group ID pool. Then the VAE-S shall generate an HTTP PUT request message according to procedures specified in RFC 7231. In the HTTP PUT request message, the VAE-S:
  1. shall include a Request-URI set to the URI corresponding to the identity of the VAE-C of the group leader;
  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 <layer2-group-id-mapping> element in the <VAE-info> root element which shall include:
    1. a <dynamic-group-info> element which shall include:
      1. a <dynamic-group-id> element set to the identity of the dynamic group;
      2. a <group-definition> element set to information about the V2X group; and
      3. a <group-leader-id> element set to the identity of the group leader; and
    2. a <prose-layer2-group-id> element corresponding to the dynamic group information; and
  4. shall send the HTTP PUT request message towards the VAE-C according to RFC 7231.
Up

6.8.1.2  Client procedurep. 18

Upon receiving an HTTP PUT 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 <layer2-group-id-mapping> element in the <VAE-info> root element;
the VAE-C shall store the content of the <layer2-group-id-mapping> element and may further announce the dynamic group information including the corresponding ProSe Layer-2 Group ID to the other VAE clients within the PC5 communication proximity on a PC5 channel dedicated for V5-AE communications, enabling more V2X UEs to join the dynamic group.
Up

6.8.2  On-network dynamic group notification procedurep. 18

6.8.2.1  Client procedurep. 18

Once the on-network dynamic group is created as defined in clause 6.8.1, if the group changes (i.e. UE joins or leaves the group), the VAE-C shall generate an HTTP POST request message according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-C:
  1. shall include a Request-URI set to the URI corresponding to the identity of the VAE-S;
  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 an <id-list-notification> element in the <VAE-info> root element which shall include:
    1. a <dynamic-group-id> element set to the identity of the dynamic group; and
    2. one or more <group-member-id> element(s), each of which contains a <V2X-UE-id> child element set to the identity of the joined or left V2X UE and a <group-scope> child element that has the value "joined" or "left"; and
  4. shall send the HTTP POST request message towards the VAE-S according to RFC 7231.
Up

6.8.2.2  Server procedurep. 19

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 <id-list-notification> element in the <VAE-info> root element;
the VAE-S shall send Notify Dynamic Group request (see TS 29.486) towards the V2X application specific server according to RFC 7231.
Up

6.8.3  VAE client initiated on network dynamic group information update procedure |R17|p. 19

6.8.3.1  Client procedurep. 19

In order to update dynamic group information of an on-network V2X dynamic group, 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 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 <dynamic-group-update-info> element included in the <VAE-info> root element which:
    1. shall include a <dynamic-group-info> element which shall include at least one of the followings;
      1. a <dynamic-group-id> element set to the identity of the dynamic group;
      2. a <group-definition> element set to information about the V2X group; and
      3. a <group-leader-id> element set to the identity of the new group leader; and
    2. shall include an <endpoint-info> element set to the end point information to which response has to be sent;
  4. shall send the HTTP POST request towards the VAE-S according to RFC 7231.
Up

6.8.3.2  Server procedurep. 19

Upon receiving an HTTP POST request message containing:
a) a Content-Type header field set to "application/vnd.3gpp.vae-info +xml"; and
b) an application/vnd.3gpp.vae-info+xml MIME body with an <dynamic-group-update-info> element in the <VAE-info> root element;
the VAE-S:
  1. shall check for the V2X user authorization to update the group information, and
    1. if the authorization fails or if the updated group information is not valid, respond with a HTTP 403 (Forbidden) response to the HTTP POST request and skip rest of the steps;
  2. if the update in group information requires consent from other group member(s), shall obtain the consent from the user as specified in clause 6.8.5;
  3. 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 with a <dynamic-group-update-info> element in the <VAE-info> root element which:
      1. shall include a <result> child element set to the value "success" or "failure" indicating success or failure of the Dynamic group information update request; and
      2. may include a <suggestion> child element including a <group-leader-id> element set to the identity of new potential group leader;
  4. shall send the HTTP 200 (OK) response towards the VAE-C; and
  5. shall update the group document as specified in clause 6.2.5.1 of TS 24.544.
Up

6.8.4  VAE server initiated on network dynamic group information update procedure |R17|p. 20

6.8.4.1  Client procedurep. 20

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 <dynamic-group-info-update-indication> element in the <VAE-info> root element;
the VAE-C:
  1. shall notify the V2X application specific client about the possible update to group information.

6.8.4.2  Server procedurep. 20

In order to update dynamic group information of an on-network V2X dynamic group, if the update in group information requires consent from the group member(s), the VAE-S shall obtain the consent from the user as specified in clause 6.8.5 and shall generate an HTTP POST request according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall include a Request-URI set to the URI corresponding to the identity of the VAE-C;
  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 <dynamic-group-info-update-indication> element in the <VAE-info> root element which shall include:
    1. a <dynamic-group-info> element which shall include:
      1. a <dynamic-group-id> element set to the identity of the dynamic group;
      2. a <group-definition> element set to information about the V2X group; and
      3. a <group-leader-id> element set to the identity of the new group leader;
  4. shall send the HTTP POST request message towards the VAE-C according to RFC 7231; and
  5. shall update the group document as specified in clause 6.2.5.1 of TS 24.544.
Up

6.8.5  VAE Server taking consent from user procedure |R17|p. 21

6.8.5.1  Client procedurep. 21

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 <dynamic-group-update-consent-info> element in the <VAE-info> root element;
the VAE-C:
  1. shall notify the V2X application specific client about the dynamic group information update consent request.
Upon receiving the result of dynamic group information update consent request from the V2X application specific client, the VAE-C:
  1. shall send an HTTP 200(OK) response message including a <dynamic-group-update-consent-info> element with a <result> child element set to "accept" or "reject" in the <VAE-info> root element indicating acceptance or rejection of the request by the V2X user.
Up

6.8.5.2  Server procedurep. 21

If the update in group information requires consent from other group member(s), 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 include a Request-URI set to the URI corresponding to the identity of the VAE-C;
  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 <dynamic-group-update-consent-info> element in the <VAE-info> root element which shall include:
    1. a <dynamic-group-info> element which shall include:
      1. a <dynamic-group-id> element set to the identity of the dynamic group;
      2. a <group-definition> element set to information about the V2X group; and
      3. a <group-leader-id> element set to the identity of the group leader; and
  4. shall send the HTTP POST request message towards the VAE-C according to RFC 7231.
Up

6.9  Network monitoring by the V2X UE procedurep. 21

6.9.1  V2X UE subscription for network monitoring informationp. 21

6.9.1.1  Client procedurep. 21

In order to subscribe for the network monitoring information from the 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 corresponding to the identity of the VAE-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 with a <network-monitoring-subscription-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 <subscription-events> element with one or more <event> child element set to the network monitoring events (e.g. uplink degradation, congestion, overload, coverage) to be subscribed; and
    3. shall include a <triggering-criteria> element set to the criteria to indicate when the VAE-S sends the monitoring reports to the VAE-C.
Up

6.9.1.2  Server procedurep. 22

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 <network-monitoring-subscription-info> element in the <VAE-info> root element;
the VAE-S:
  1. shall store the received subscription information if the VAE-C is authorized and allowed to access the network monitoring 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"; and
    2. shall include an application/vnd.3gpp.vae-info+xml MIME body with a <network-monitoring-subscription-info> element in the <VAE-info> root element:
      1. shall include a <V2X-UE-id> element set to the identity of the V2X UE subscribing the network monitoring information; and
      2. shall include a <result> child element set to the value "success" or "failure" indicating success or failure of subscribing the network monitoring information; and
    3. shall send the HTTP 200 (OK) response towards the VAE-C.
Up

6.9.2  Notifications for network monitoring informationp. 22

6.9.2.1  Server procedurep. 22

Based on the UE subscription for network monitoring information, the VAE-S shall generate an HTTP POST request message according to procedures specified in RFC 7231. In the HTTP POST request, the VAE-S:
  1. shall include a Request-URI set to the URI corresponding to the identity of the VAE-C;
  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 <network-monitoring-info-notification> element in the <VAE-info> root element which shall include:
    1. a <V2X-UE-id> element set to the identity of the subscribed V2X UE;
    2. a <network-monitoring-info> element, which:
      1. shall include one or more <trigger-id> elements set to the identity of the triggering criteria that resulted in the VAE-S sending the monitoring report to the VAE-C;
      2. may include an <uplink-quality-level> element set to the uplink quality level;
      3. may include a <congestion-info> element set to the congestion value;
      4. may include a <geographical-area> element which shall include at least one of the followings:
        1. <cell-area>, an element specifying an NCGI which when entered triggers a request for a location report coded as specified in clause 19.6A in TS 23.003 for which the monitoring applies; and
        2. <tracking-area>, an element specifying a tracking area identity coded as specified in clause 19.4.2.3 in TS 23.003 for which the monitoring applies;
      5. may include a <time-validity> element set to the period for which the monitoring applies; and
      6. may include an <MBMS-level> element, which may include:
        1. an <MBMS-coverage-level> element set to the coverage level for MBMS; and
        2. an <MBMS-bearer-level-event> element set to the MBMS bearer level events; and
  4. shall send the HTTP POST request message towards the VAE-C according to RFC 7231.
Up

Up   Top   ToC