Content for  TS 24.257  Word version:  18.3.0

To subscribe for host UAV's dynamic information with UAE server, the UAE-C of the host UAV shall generate an HTTP POST request message according to RFC 9110. In the HTTP POST request message, the UAE-C of the host UAV:

1. shall set the Request-URI to the URI corresponding to the identity of the UAE-S;
2. shall include a Content-Type header field set to "application/vnd.3gpp.uae-info+xml";
3. shall include an application/vnd.3gpp.uae-info+xml MIME body with a <subscribe-host-UAV-dynamic-info> element in the <UAE-info> root element which:
   1. shall include a <UAS-id> element set to the identifier of the UAS for which the host UAV client support information applies; and
   2. shall include an <application-defined-proximity-range-info> element indicating the range information over which the host UAV's dynamic information is required; and
4. shall send the HTTP POST request towards the UAE-S.

Upon receiving an HTTP POST request containing:

1. a Content-Type header field set to "application/vnd.3gpp.uae-info+xml"; and
2. an application/vnd.3gpp.uae-info+xml MIME body with a <subscribe-host-UAV-dynamic-info> element,
   the UAE-S:

1. shall store the subscription information;
2. the UAE-S shall generate an HTTP 200 (OK) response according to RFC 9110. In the HTTP 200 (OK) response message, the UAE-S:
   1. shall include a Content-Type header field set to "application/vnd.3gpp.uae-info+xml";
   2. shall include an application/vnd.3gpp.uae-info+xml MIME body with a <subscribe-host-UAV-dynamic-info> element in the <UAE-info> root element which:
      1. shall include a <result> child element set to the value "positive" or "negative" indicating positive or negative result of the reception; and
      2. if the <result> element indicates positive result, shall include a <subscription-ID> element set to the identifier of a successful subscription; and
   3. shall send the HTTP 200 (OK) message towards the UAE-C of the host UAV; and
3. shall obtain and initiate tracking the host UAV location from the location management server (LMS) as specified in TS 23.434.

Once UAE-C of the host UAV or UAS Application Specific Server (USS) has performed subscription for host UAV dynamic information, the UAE server UAE-S sends a notification of host UAV dynamic information to the UAE-C of the host UAV, and UAE-S shall generate an HTTP POST request message according to RFC 9110. In the HTTP POST request message, the UAE-S:

1. shall set the Request-URI to the URI corresponding to the identity of the UAE-C of the host UAV;
2. shall include a Content-Type header field set to "application/vnd.3gpp.uae-info+xml";
3. shall include an application/vnd.3gpp.uae-info+xml MIME body with a <notification-of-host-UAV-dynamic-info> element in the <UAE-info> root element which:
   1. shall include a <subscription-ID> element set to the identifier of a successful subscription;
   2. shall include a <location-of-the-host-UAV> element indicating the location of the host UAV during the host UAV dynamic information subscription; and
   3. shall include a <list-of-UAVs-info> element including the information of the UAVs which were detected in the application defined proximity range, which:
      1. shall include a <nearby-UAV-ID> element set to the identifier of nearby UAS;
      2. shall include a <location-information> element set to the location information of the nearby UAV within the application defined proximity range;
      3. shall include a <distance-information> element set to the distance information of the nearby UAV relative to the host UAV; and
4. shall send the HTTP POST request towards the UAE-C of the host UAV.