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.4 UAS UE registration  6.4.1 Client procedure  6.4.2 Server procedure  6.5 UAS UE de-registration  6.5.1 Client procedure  6.5.2 Server procedure  6.6 UAS UE registration update  6.6.1 Client procedure  6.6.2 Server procedure 
...

 

6.4  UAS UE registration  p. 13

6.4.1  Client procedure  p. 13

Upon receiving a request from a UAV application to register for receiving UAV application messages from the UAS application specific server, 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 <registration-info> element in the <UAE-info> root element:
    1. shall include a <UAV-id> element set to the identity of the UAV which initiates the UAS UE registration procedure;
    2. may include a <UAS-UE-information> element set to the related information (e.g. UAS UE IP address, Multi-USS capability, DAA assist capability) the UAS UE needs to provide to the UAE-S; and
    3. may include a <proposed-registration-lifetime> element set to the time during which the UAS UE wants to stay registered to the UAE-S for receiving UAV application messages from the UAS application specific server; and
  4. shall send the HTTP POST request message towards the UAE-S.
Up

6.4.2  Server procedure  p. 14

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 <registration-info> element in the <UAE-info> root element;
the UAE-S:
  1. shall store the received registration information for the UAE-C;
  2. 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. shall include an application/vnd.3gpp.uae-info+xml MIME body and in the <registration-info> element in the <UAE-info> root element:
      1. shall include a <result> element set to the value "success" or "failure" indicating success or failure of the UAS UE registration; and
      2. may include a <registration-lifetime> element set to the time during which the UAS UE can stay registered to the UAE-S for receiving UAV application messages from the UAS application specific server; and
  3. shall send the HTTP 200 (OK) response towards the UAE-C.
Up

6.5  UAS UE de-registration  p. 14

6.5.1  Client procedure  p. 14

Upon receiving a request from a UAV application to de-register for receiving UAV application messages from the UAS application specific server, 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 of the UAE-S for which the UAS UE has successfully registered (see clause 6.4);
  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 <de-registration-info> element in the <UAE-info> root element:
    1. shall include a <UAV-id> element set to the identity of the UAV which initiates the UAS UE de-registration procedure; and
  4. shall send the HTTP POST request message towards the UAE-S.
Up

6.5.2  Server procedure  p. 15

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 <de-registration-info> element in the <UAE-info> root element;
the UAE-S:
  1. shall remove the stored UAS UE information for the UAE-C;
  2. 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. shall include an application/vnd.3gpp.uae-info+xml MIME body and in the <de-registration-info> element in the <UAE-info> root element:
      1. shall include a <result> element set to the value "success" or "failure" indicating success or failure of the UAS UE de-registration; and
  3. shall send the HTTP 200 (OK) response towards the UAE-C.
Up

6.6  UAS UE registration update  p. 15

6.6.1  Client procedure  p. 15

Upon receiving a request from a UAV application, if the UAE-C needs to update the registration for receiving UAV application messages from the UAS application specific server, 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 of the UAE-S for which the UAS UE has successfully registered (see clause 6.4);
  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 <registration-info> element in the <UAE-info> root element:
    1. shall include a <UAV-id> element set to the identity of the UAV which initiates the UAS UE registration update procedure;
    2. shall include a <UAS-UE-information> element set to the related information (e.g. UAS UE IP address, Multi-USS capability, DAA assist capability) the UAS UE needs to update; and
    3. may include a <proposed-registration-lifetime> element set to the time during which the UAS UE wants to stay registered to the UAE-S for receiving UAV application messages from the UAS application specific server; and
  4. shall send the HTTP POST request message towards the UAE-S.
Up

6.6.2  Server procedure  p. 16

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 <registration-info> element in the <UAE-info> root element;
the UAE-S:
  1. shall update the stored registration information with the received registration information for the UAE-C;
  2. 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. shall include an application/vnd.3gpp.uae-info+xml MIME body and in the <registration-info> element in the <UAE-info> root element:
      1. shall include a <result> element set to the value "success" or "failure" indicating success or failure of the UAS UE registration update; and
      2. may include a <registration-lifetime> element set to the time during which the UAS UE can stay registered to the UAE-S for receiving UAV application messages from the UAS application specific server; and
  3. shall send the HTTP 200 (OK) response towards the UAE-C.
Up

Up   Top   ToC