5G NR V2X for 5G NR 2.2

90 views
Skip to first unread message

Harinder Kaur

unread,
Nov 14, 2022, 6:16:51 AM11/14/22
to 5G-LENA-users
Hi all,
I am using 5G NR V2X with NS 3.35/ 5G NR and want to know can I run V2X code with NS 3.36.1/5G NR 2.2?

Tom Henderson

unread,
Nov 14, 2022, 11:49:31 AM11/14/22
to 5g-len...@googlegroups.com
Yes, the 'nr-v2x-dev' development branch works with 'v2x-lte-dev'
development branch of CTTC's ns-3-dev repository; both are based on
ns-3.36.1 (but haven't been released yet).

Biljana B.

unread,
Nov 15, 2022, 11:41:12 AM11/15/22
to 5G-LENA-users
Hi all, 

we just created a  new release for V2X, based on the upgrade to ns3.36.1 provided by Tom Henderson and other contributions by NIST.

You can find instructions here:

Kind regards,
Biljana

Tom Henderson

unread,
Nov 15, 2022, 12:35:38 PM11/15/22
to 5g-len...@googlegroups.com
Biljana,

Can you clarify the naming scheme on these releases?

- what does the suffix 'y' mean?
- 0.1, 0.2 indicate that these are somewhat pre-releases (not yet a 1.0
release)-- what remains to accomplish, in your view, before this would
become a 1.0 release?

Thanks,
Tom

Biljana Bojovic

unread,
Nov 15, 2022, 1:38:41 PM11/15/22
to Tom Henderson, 5G-LENA-users
Hi Tom,

- regarding 'y', we just followed here the same version naming as we have for the nr module, and also as it was adopted for the first release created by Zoraze. Regarding its meaning, only Natale knows it. This seems that is not documented anywhere, so we kept it for the moment, but i was thinking to remove it, however sometimes it creates more confusion for users to change usual naming, even if it becomes obsolete. But we should reconsider it, I am personally in favor of removing it, because I dont see that we really need some additional indication. We have enough with version and subversion.

- regarding changing version or subversion, we also dont have this very well defined, neither documented. What we usually do for the nr module, we increase subversion (e.g. 0.1 to 0.2) when there are no huge interface changes in the module, when we add some new features, e.g. we are now preparing next nr release which will be named 2.3 and the current one is 2.2. However when we create some big shift in interfaces, we usually indicate it by increasing the version number, e.g. when we introduced DP-MIMO, it was not only adding a new feature, but also existing interfacea changed a lot. So we want to indicate to users that there are major changes coming, especially for those who need to rebase their code.

Kind regards,
Biljana

--
You received this message because you are subscribed to the Google Groups "5G-LENA-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 5g-lena-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/5g-lena-users/9127327c-adb3-b795-c28b-500415fc40a0%40tomh.org.

Tom Henderson

unread,
Nov 15, 2022, 2:44:33 PM11/15/22
to 5g-len...@googlegroups.com
On 11/15/22 10:38, Biljana Bojovic wrote:
Hi Tom,

- regarding 'y', we just followed here the same version naming as we have for the nr module, and also as it was adopted for the first release created by Zoraze. Regarding its meaning, only Natale knows it. This seems that is not documented anywhere, so we kept it for the moment, but i was thinking to remove it, however sometimes it creates more confusion for users to change usual naming, even if it becomes obsolete. But we should reconsider it, I am personally in favor of removing it, because I dont see that we really need some additional indication. We have enough with version and subversion.

- regarding changing version or subversion, we also dont have this very well defined, neither documented. What we usually do for the nr module, we increase subversion (e.g. 0.1 to 0.2) when there are no huge interface changes in the module, when we add some new features, e.g. we are now preparing next nr release which will be named 2.3 and the current one is 2.2. However when we create some big shift in interfaces, we usually indicate it by increasing the version number, e.g. when we introduced DP-MIMO, it was not only adding a new feature, but also existing interfacea changed a lot. So we want to indicate to users that there are major changes coming, especially for those who need to rebase their code.

Thanks for the explanation; so if I understand correctly, 0.x series will change to 1.0 only if there is some major change (that there is no special distinction between the 0.x and 1.x series-- you just started numbering at 0)?

- Tom

Biljana Bojovic

unread,
Nov 15, 2022, 3:26:59 PM11/15/22
to 5G-LENA-users
Yes, correct, we just started with 0, there is no other difference between 0. and 1. series. All of these is as we did up to now. We are open to change the current versions naming scheme. In any case we should try to document it.

Biljana


--
You received this message because you are subscribed to the Google Groups "5G-LENA-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 5g-lena-user...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages