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 UAE procedures  6.1 General  6.2 Communications between UAVs within a geographical area using unicast Uu  6.2.1 Client procedure  6.2.1.1 Sending of a UAV application message  6.2.1.2 Reception of a UAV application message  6.2.2 Server procedure  6.2.2.1 Reception of a UAV application message  6.2.2.2 Sending of a UAV application message 
...

 

6  UAE procedures  p. 8

6.1  General  p. 8

This clause provides the procedures for UAS application communication between the UAE-C and the UAE-S and from a UAE-C to other UAE-C.
In order to send UAS signalling and application data for the procedures defined in this clause, the UAE-C and the UAE-S utilize the services defined by TS 24.543, e.g. SEALDD enabled signalling transmission connection procedures such as connection establishment, connection release.

6.2  Communications between UAVs within a geographical area using unicast Uu  p. 9

6.2.1  Client procedure  p. 9

6.2.1.1  Sending of a UAV application message  p. 9

In order to send a UAV application message, the UAE-C shall generate an HTTP POST request message according to procedures specified in RFC 9110. In the HTTP POST request message, the UAE-C:
  1. shall set the Request-URI to the URI received in the UAE client UE configuration document via the SCM-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 and in the <UAV-application-message-info> element in the <UAE-info> root element:
    1. shall include a <UAV-id> element set to the identity of the UAV which requests the sending of the UAV application message;
    2. shall include an <application-defined-proximity-range-info> element to indicate the range information over which the UAV application message is to be sent; and
    3. shall include an <application-payload> element set to the application payload that is to be delivered to the other UAVs; and
  4. shall send the HTTP POST request message towards the UAE-S.
Up

6.2.1.2  Reception of a UAV application message  p. 9

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 <UAV-application-message-info> element in the <UAE-info> root element;
the UAE-C:
  1. shall store the received <application-payload> information included in the <UAV-application-message-info> element; and
  2. shall generate an HTTP 200 (OK) response according to RFC 9110 and send the HTTP 200 (OK) response towards the UAE-S.
Up

6.2.2  Server procedure  p. 9

6.2.2.1  Reception of a UAV application message  p. 9

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 <UAV-application-message-info> element in the <UAE-info> root element;
the UAE-S:
  1. shall obtain the other UAV(s) information in the location of the UAV based on the range information indicated in the <application-defined-proximity-range-info> element from the SLM-S as specified in TS 24.545;
  2. shall send the received <application-payload> information to each of the UAV obtained from step a) via unicast Uu channel as specified in clause 6.2.2.2;
  3. shall generate an HTTP 200 (OK) response according to RFC 9110 and in the HTTP 200 (OK) response:
    1. shall include a Content-Type header field set to "application/vnd.3gpp.uae-info+xml"; and
    2. may include an application/vnd.3gpp.uae-info+xml MIME body with a <UAV-application-message-info> with an <acknowledgement> child element in the <UAE-info> root element to indicate the acknowledgement of communications between UAVs within a geographical area; and
  4. shall send the HTTP 200 (OK) response towards the UAE-C.
Up

6.2.2.2  Sending of a UAV application message  p. 10

In order to send a UAV application message received from a UAV as specified in clause 6.2.2.1 to each of the UAV within a geographical area of the UAV initiating the communication with other UAVs, the UAE-S shall generate an HTTP POST request message according to procedures specified in 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 UAV obtained in clause 6.2.2.1;
  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 and in the <UAV-application-message-info> element in the <UAE-info> root element:
    1. shall include a <UAV-id> element set to the identity of the UAV which requests the sending of the UAV application message; and
    2. shall include an <application-payload> element set to the application payload that needs to be delivered to the other UAVs; and
  4. shall send the HTTP POST request message towards the UAE-C.
Up

Up   Top   ToC