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.257  Word version:  18.3.0

Top   Top   Up   Prev   Next
1…   6…   6.3…   6.4…   6.7…   6.8…   6.9…   7… 
6.8 DAA support  6.8.1 Client procedure  6.8.1.1 DAA support configuration procedure  6.8.1.2 DAA support involving UAVs with U2X support procedure  6.8.1.3 DAA support involving UAVs without U2X support procedure  6.8.2 Server procedure  6.8.2.1 DAA support configuration procedure  6.8.2.2 DAA support involving UAVs with U2X support procedure  6.8.2.3 DAA support involving UAVs without U2X support procedure 
...

 

6.8  DAA support |R18|  p. 18

6.8.1  Client procedure  p. 18

6.8.1.1  DAA support configuration procedure  p. 18

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 <DAA-support-configuration-info> element,
the UAE-C:
  1. shall store the received configuration information;
  2. shall generate an HTTP 200 (OK) response according to RFC 9110. In the HTTP 200 (OK) response message, the UAE-C:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.uae-info+xml"; and
    2. shall include an application/vnd.3gpp.uae-info+xml MIME body and in the <UAE-info> root element:
      1. shall include a <DAA-support-configuration-info> element with a <result> child element set to the value "success" or "failure" indicating positive or negative result of reception and storing of the DAA support configuration parameters; and
  3. shall send the HTTP 200 (OK) response towards the UAE-S.
Up

6.8.1.2  DAA support involving UAVs with U2X support procedure  p. 19

Upon detection of UAVs in proximity by the UAE layer, then the UAE-C shall generate an HTTP POST request message according to RFC 9110. In the HTTP POST request message, the UAE-C:
  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 <DAA-client-event-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 DAA client support information applies;
    2. shall include a <UAE-layer-detected-information> element indicating list of UASes where e.g. U2X layer has detected possible flight path conflict;
      1. shall include a <UAS-identity> element set to identification of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict; and
      2. shall include a <Location-information> element indicating location of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict; and
  4. shall send the HTTP POST request towards the UAE-S.
Up

6.8.1.3  DAA support involving UAVs without U2X support procedure  p. 19

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 <DAA-server-event-info> element,
the UAE-C:
  1. shall generate an HTTP 200 (OK) response according to RFC 9110. In the HTTP 200 (OK) response message, the UAE-C:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.uae-info+xml"; and
    2. shall include an application/vnd.3gpp.uae-info+xml MIME body and in the <UAE-info> root element:
      1. shall include a <DAA-server-event-info> element with an <acknowledgement> child element indicating the acknowledgement of DAA server event information; and
  2. shall send the HTTP 200 (OK) response towards the UAE-S.
Up

6.8.2  Server procedure  p. 20

6.8.2.1  DAA support configuration procedure  p. 20

Upon receiving an application request from UAS application specific server (which can be the USS/UTM) to manage the DAA support configuration for a UAS, the UAE-S shall generate an HTTP POST request message according to RFC 9110. In the HTTP POST request message, the UAE-S:
  1. shall include a Request-URI set to the URI corresponding to the identity of the UAE-C;
  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 <DAA-support-configuration-info> element in the <UAE-info> root element which:
    1. shall include a <UAS-id> element set to the identification of the UAS for which the multi-USS configuration request applies; and
    2. may include a <DAA-application-policy> element that consists of the DAA application policy to be configured at the UAS; and
  4. shall send the HTTP POST request message towards the UAE-C.
Up

6.8.2.2  DAA support involving UAVs with U2X support procedure  p. 20

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 <DAA-client-event-info> element,
the UAE-S shall store the DAA client event information and links information received in the <DAA-client-event-info> element and then forward the DAA client event information and links information to the UAS application specific server and upon receiving a DAA client event information acknowledgement from the UAS application specific server, 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 and in the <UAE-info> root element:
    1. shall include a <DAA-client-event-info> element with an <acknowledgement> child element indicating the acknowledgement of DAA client event information; which
    2. shall include a <UAS-id> element set to the identifier of the UAS for which the DAA client support information applies; and
    3. shall include a <UAE-layer-detected-information> element indicating list of UASes where e.g. U2X layer has detected possible flight path conflict;
      1. shall include a <UAS-identity> element set to identification of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict; and
      2. shall include a <Location-information> element indicating location of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict; and
  3. shall send the HTTP 200 (OK) message towards the UAE-C.
Up

6.8.2.3  DAA support involving UAVs without U2X support procedure  p. 20

Upon receiving an application request from UAS application specific server (which can be the USS/UTM) to manage the DAA support involving UAVs without U2X support, the UAE-S shall generate an HTTP POST request message according to RFC 9110. In the HTTP POST request message, the UAE-S:
  1. shall include a Request-URI set to the URI corresponding to the identity of the UAE-C;
  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 <DAA-server-event-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 DAA client support information applies; and
    2. shall include a <UAE-layer-detected-information> element indicating list of UASes where e.g. U2X layer has detected possible flight path conflict;
      1. shall include a <UAS-identity> element set to identification of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict; and
      2. shall include a <Location-information> element indicating location of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict; and
  4. shall send the HTTP POST request message towards the UAE-C.
Up

Up   Top   ToC