[IPS_Aero] FW: A858P3 - Datalink IDs

[Sam Buckwalter]

Hello All:

Please read the email message from Michal Skorepa, Honeywell.


Sam Buckwalter
AEEC Executive Secretary
Director

ARINC Industry Activities an SAE ITC Program

m 1+443.454.0584
sam.buckwalter at sae-itc.org<mailto:sam.buckwalter at sae-itc.org>



From: Skorepa, Michal <Michal.Skorepa at Honeywell.com>
Sent: Thursday, January 11, 2024 10:07 AM
To: Sam Buckwalter <Sam.Buckwalter at sae-itc.org>
Cc: luc.emberger <luc.emberger at airbus.com>; gregory.t.saccone at boeing.com; Michael Olive <mike.olive at verticlesquared.com>
Subject: A858P3 - Datalink IDs


Hello Sam,

Happy new year! I would like to distribute the following message to the 858 experts, but I do not have the distribution list. Could you please distribute this?

Thank you,
Michal

---------------------------


Dear A858 experts,

Happy New Year! [Party]

I started working on my Action Items regarding the CIRI specification in A858P3 and would like to discuss the topic of Datalink IDs with you. During the November meeting we agreed that:

  1.  The Datalink IDs for individual radios would be defined in the A858P3 document
  2.  For existing radios, like SDUs, the Datalink IDs would be based on A429 SALs

My doubt is about point 2. While for SDUs this approach would work well, I believe that for other radios this can be rather confusing for the following reasons:

  1.  For VDLm2 using the VDR labels would not be appropriate – A429 defines labels for individual VDRs (VDR #1, VDR #2, VDR #3), while on the IPS level we do not really care about this – we do not differentiate the individual radios, but rather interface with the link layer in the CMU. So, we would need to either define a new VLDm2 Datalink ID, or use one of the three values defined for the VDRs
  2.  For new radios, like LDACS, AeroMACS, Hyperconnected links etc. we would need define new values, as these radios currently do not have A429 SALs. BUT, since the Datalink ID is an 8-bit value just like the A429 SAL, AND since A429 SALs do not have any reserved values (as far as I could tell), these new Datalink IDs would need to overlap with some existing A429 SALs.

It could look something like this:
Airborne Radio
Datalink ID
VDLm2
SAL(VDR #1) = 169 [dec]
SDU #1
SAL(SDU #1) = 199 [dec]
SDU #2
SAL(SDU #2) = 123 [dec]
LDACS
new value (e.g., SAL for non-radio) = 1 [dec]
AeroMACS
new value = 2 [dec]




However, given the two points above, it seems that linking the Datalink ID values to the A429 SAL values would not be as beneficial as we originally thought, and could rather cause confusion. So, it may be better to define all the Datalink IDs from scratch, for example like:

Airborne Radio
Datalink ID
VDLm2
0
SDU #1
1
SDU #2
2
LDACS
3
AeroMACS
4



Please let me know if you have any thoughts on this. We can discuss during the call on Jan 23.

Thank you,
Michal



Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. This email, and any attachments, may contain confidential and/or proprietary material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited. If you received this message in error, please contact the sender and permanently delete any printout of the message, the original and any copy of the e-mail and its attachments from your computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/ips_aero/attachments/20240111/49b380ac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1152 bytes
Desc: image001.png
URL: <http://mailman.sae-itc.org/pipermail/ips_aero/attachments/20240111/49b380ac/attachment-0001.png>