Re: [Drip] IETF - 3GPP bridge

[[e-mail]]

Hi Alex,

We do already have the following in -arch:


   The 3rd Generation Partnership Project (3GPP)



      With release 16, the 3GPP completed the UAS RID requirement study

      [TS-22.825] and proposed a set of use cases in the mobile network

      and services that can be offered based on UAS RID.  The Release 17

      study [TR-23.755] and specification [TS-23.255] focus on enhanced

      UAS service requirements and provides the protocol and application

      architecture support that will be applicable for both 4G and 5G

      networks.  The study of Further Architecture Enhancement for

      Uncrewed Aerial Vehicles (UAV) and Urban Air Mobility (UAM)

      [FS_AEUA] in release 18 further enhances the communication

      mechanism between UAS and USS/UTM.  The DRIP Entity Tag in

      Section 3 may be used as the 3GPP CAA-level UAS ID for Remote

      Identification purposes.

That’s the max we can do in -arch because otherwise we will be interfering with the 3GPP.

Now for -registries, I’m not sure yet we can cite 3GPP there. However, if there is a volunteer (you? :-)) to edit a short draft that exemplifies how dime roles can be mapped with other architectures (3GPP, for example), that would be really useful.

Cheers,
Med

De : Tm-rid <[e-mail]> De la part de Alex Pershin
Envoyé : jeudi 23 février 2023 06:47
À : [e-mail]
Objet : [Drip] IETF - 3GPP bridge

Hi guys,
In Release 17 3GPP published requirements, architecture and implementation tests  for 4G and 5G to support UAS. It is about Network RID.  They see their role as not only a data provider but as an active participant in UAS businesses. For example  they offer assistance in UAS authentication, data tracking and managing connectivity for interested parties such as UTM participants, CAAs and enforcements. This assistance becomes very important in critical situations. IMHO those supplement services give 3GPP an essential role as a dedicated DRIP entity. 3GPP operates with their own authentication mechanism having their own identities which must be provided in APIs.  I think DRIP architecture and  DIME should mention 3GPP somewhere, for instance DIME can have a role for 3GPP to bind  UAS Session ID and 3GPP identity.  What do you think about it?
Thanks,
Alex Pershyn

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.