-
Notifications
You must be signed in to change notification settings - Fork 132
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
Multi-hop #58
Comments
Artery itself does not provide any forwarding algorithms, however, it integrates Vanetza for this task. Vanetza supports all forwarding algorithms given by EN 302 636-4-1 including Greedy Forwarding and Contention Based Forwarding. |
Hi @riebl Thanks for the help. I try to use Vanetza routing for multi-hop, but I can't make it work. Do you have an example on how to use any Vanetza forwarding algorithms with Artery? Regards, |
From the perspective of an Artery service there is not much to do: Any packet with transport type set to "GBC" (GeoBroadcast) will be subject to forwarding operations by |
Hi @riebl I set the settings at MIB setup to:
In my scenario, the source node are outside the destination area, so when I send a packet two hops are executed using I have been debugging the Can you help me? Regards, |
@danieladriano Can you share your scenario with me, possibly sending it confidentially via e-mail? Your selection of forwarding algorithms is actually Vanetza's default setup, so that is not changing anything. |
Hi @riebl Of course! Can you send me a e-mail and then I send back to you with my scenario. My e-mail: Thanks for helping me! Regards, |
Note to the public: Daniel and me have investigated this issue further and we currently believe that Artery is behaving correctly according to ETSI specification. A possible (not yet standardised) solution is work-in-progress. |
Hi, @danieladriano and @riebl I am also very interested in this issue and if you need a hand, I would like to take part in the discussion and test. |
Hi, @riebl I think I may face the same problem as @danieladriano . Could u tell if there is any progress for this problem? |
@ruisonghan I am still working on this. In the meantime, you may work-around multi-hop routing issues by repeating transmissions (see the |
Hi, Riebl and Daniel I think my problem is different from Daniel's and I am trying to get the reason. I defined my own scenario and DEN use cases called TranssecRiskLevel and TranssecRiskLevelReceiver. The basic function of them is sending an alert to other vehicles and makING other vehicles evacuate. Currently, I found that when my own use cases were used with the DEN use case "ImpactReductionContainerExchange", multi-hop GBC worked normally. However, when "TrafficJamAhead" was used with my use cases, multi-hop didn't work. <?xml version="1.0" encoding="UTF-8"?>
<usecases>
<usecase type="artery.application.den.TranssecRiskLevel">
<filters><name pattern="truck0.0" /></filters>
</usecase>
<usecase type="artery.application.den.TranssecRiskLevelReceiver">
<filters><name pattern="truck0.0" match="inverse"/></filters>
</usecase>
<usecase type="artery.application.den.TrafficJamAhead" />
<!-- <usecase type="artery.application.den.ImpactReductionContainerExchange" /> -->
</usecases> I am a little confused with why the DEN use cased may affect the multi-hop communication. I will contact you when I find a clue. |
@ruisonghan Maybe too many messages are generated by your station, i.e. DCC may enqueue them. I have recently added a |
Hi, @riebl Currently, I found 2 ways to temporarily solve my problems, but I still don't know the reasons.
For 2, I think my problem is related to the communication congestion, but when testing my use case with I am still working on it and hope to find an answer. |
Regarding 1), these limits are just set as required by C2C-CC's Triggering Conditions. Possibly these conditions simply do not trigger with a longer sample buffer in your scenario. |
Hi,
Artery implements any type of forwarding for multi-hop, like Greedy Forwarding or Contention Based Forwarding ?
Regards,
Daniel
The text was updated successfully, but these errors were encountered: