How to detect hidden terminal from collision packet
up vote
-2
down vote
favorite
I am using omnet++-5.4.1, veins-4.7.1 and sumo-0.25.0 to simulate vehicle frame transmission. I'd like to determine if the collision frame is from a hidden terminal.
In order to judge whether it is a hidden terminal it is necessary to have the coordinates of the vehicles that sent the collision frame. However, I believe that it is not possible to obtain information on vehicles that sent from collision frames in Decider80211p.
Is there a good way to determine if a conflicting frame is caused by a hidden terminal?
Thank you
omnet++ veins
add a comment |
up vote
-2
down vote
favorite
I am using omnet++-5.4.1, veins-4.7.1 and sumo-0.25.0 to simulate vehicle frame transmission. I'd like to determine if the collision frame is from a hidden terminal.
In order to judge whether it is a hidden terminal it is necessary to have the coordinates of the vehicles that sent the collision frame. However, I believe that it is not possible to obtain information on vehicles that sent from collision frames in Decider80211p.
Is there a good way to determine if a conflicting frame is caused by a hidden terminal?
Thank you
omnet++ veins
OMNeT++ simulations are C++ programs. Everything you need is accessible by writing additional C++ code. If you need help with a particular piece of code, just post your question here.
– Christoph Sommer
Nov 12 at 17:44
Thank you, I currently think of ways to examine hidden terminals in other ways, so there was no need to change Decider80211p.
– 7ufi
Nov 19 at 5:56
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
I am using omnet++-5.4.1, veins-4.7.1 and sumo-0.25.0 to simulate vehicle frame transmission. I'd like to determine if the collision frame is from a hidden terminal.
In order to judge whether it is a hidden terminal it is necessary to have the coordinates of the vehicles that sent the collision frame. However, I believe that it is not possible to obtain information on vehicles that sent from collision frames in Decider80211p.
Is there a good way to determine if a conflicting frame is caused by a hidden terminal?
Thank you
omnet++ veins
I am using omnet++-5.4.1, veins-4.7.1 and sumo-0.25.0 to simulate vehicle frame transmission. I'd like to determine if the collision frame is from a hidden terminal.
In order to judge whether it is a hidden terminal it is necessary to have the coordinates of the vehicles that sent the collision frame. However, I believe that it is not possible to obtain information on vehicles that sent from collision frames in Decider80211p.
Is there a good way to determine if a conflicting frame is caused by a hidden terminal?
Thank you
omnet++ veins
omnet++ veins
edited Nov 8 at 7:02
asked Nov 8 at 6:40
7ufi
112
112
OMNeT++ simulations are C++ programs. Everything you need is accessible by writing additional C++ code. If you need help with a particular piece of code, just post your question here.
– Christoph Sommer
Nov 12 at 17:44
Thank you, I currently think of ways to examine hidden terminals in other ways, so there was no need to change Decider80211p.
– 7ufi
Nov 19 at 5:56
add a comment |
OMNeT++ simulations are C++ programs. Everything you need is accessible by writing additional C++ code. If you need help with a particular piece of code, just post your question here.
– Christoph Sommer
Nov 12 at 17:44
Thank you, I currently think of ways to examine hidden terminals in other ways, so there was no need to change Decider80211p.
– 7ufi
Nov 19 at 5:56
OMNeT++ simulations are C++ programs. Everything you need is accessible by writing additional C++ code. If you need help with a particular piece of code, just post your question here.
– Christoph Sommer
Nov 12 at 17:44
OMNeT++ simulations are C++ programs. Everything you need is accessible by writing additional C++ code. If you need help with a particular piece of code, just post your question here.
– Christoph Sommer
Nov 12 at 17:44
Thank you, I currently think of ways to examine hidden terminals in other ways, so there was no need to change Decider80211p.
– 7ufi
Nov 19 at 5:56
Thank you, I currently think of ways to examine hidden terminals in other ways, so there was no need to change Decider80211p.
– 7ufi
Nov 19 at 5:56
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53202622%2fhow-to-detect-hidden-terminal-from-collision-packet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
OMNeT++ simulations are C++ programs. Everything you need is accessible by writing additional C++ code. If you need help with a particular piece of code, just post your question here.
– Christoph Sommer
Nov 12 at 17:44
Thank you, I currently think of ways to examine hidden terminals in other ways, so there was no need to change Decider80211p.
– 7ufi
Nov 19 at 5:56