Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

text clarification #9

Closed
mglt opened this issue Jun 7, 2021 · 5 comments
Closed

text clarification #9

mglt opened this issue Jun 7, 2021 · 5 comments

Comments

@mglt
Copy link

mglt commented Jun 7, 2021

1.2.2. Network RID
"""
Command and Control (C2) must flow from the GCS to the UA via some
path, currently (in the year of 2021) typically a direct RF link, but
with increasing BVLOS operations expected often to be wireless links
"""
BVLOS needs to be expanded. It is also unclear to me what the difference is beween RF and wireless link. I tend to see the RF as a wireless link. I have the impression the text wants to mention that in some case, a human will be the C2, while it is foreseen in the future that a sort of base station will be used.
If that is correct, I believe the base station will only relay C2 from a remote GCS, but will not implement a C2. Am I missing something ?

It seems the text may be clarified.

@ShuaiZhao
Copy link
Contributor

ShuaiZhao commented Jun 25, 2021

1.2.2. Network RID
"""
Command and Control (C2) must flow from the GCS to the UA via some
path, currently (in the year of 2021) typically a direct RF link, but
with increasing BVLOS operations expected often to be wireless links
"""
BVLOS needs to be expanded.

I will expand BVLOS to "beyond Visual Line of Sight (BVLOS)"

It is also unclear to me what the difference is beween RF and wireless link. I tend to see the RF as a wireless link.

I am wondering if read the whole sentence below would help. I think it is saying that RF wireless link needs to be connected with the Internet for C2 to work. There is no confusion about RF is/not a wireless link

"Command and Control (C2) must flow from the GCS to the UA via some path, currently (in the year of 2021) typically a direct RF link, but with increasing beyond Visual Line of Sight (BVLOS) operations expected often to be wireless links at either end with the Internet between."

I have the impression the text wants to mention that in some case, a human will be the C2, while it is foreseen in the future that a sort of base station will be used. If that is correct, I believe the base station will only relay C2 from a remote GCS, but will not implement a C2. Am I missing something ?

It seems the text may be clarified.

As I explained above, C2 only works with GCS with an internet connection for Network RID.

@mglt
Copy link
Author

mglt commented Jun 28, 2021

"""but
with increasing BVLOS operations expected often to be wireless links
"""

We need to explain the difference with wireless and RF link clearly. Probably explicitly listing the "either end" would be clarifying also.

Again, the architecture document should be primarily clarifying for the basic usage - of today. How it might be extended and used in the future is informative - even though we now that has impacted the architecture design.

@cardsw
Copy link
Collaborator

cardsw commented Jun 29, 2021

The remote pilot uses the GCS to exercise essential Command & Control (C2) of the UA via some data path. That may be a direct RF (aka wireless) link. It may be a path through the Internet. In the latter case, both the GCS and the UA have Internet connectivity, so either could use it to send Network RID to the NetRID-SP. In the former case, one end or the other (typically the GCS) would need not only direct C2 link but also Internet connectivity to send Network RID to the NetRID-SP.

@ShuaiZhao
Copy link
Contributor

added editor-note 2

> Editor-note 2:  Explain the difference with wireless and RF link includes what are the end entities, usages for each transport media.

@ShuaiZhao
Copy link
Contributor

closed. no more comments from the mailing list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants