D2dBinder¶

simple module D2dBinder

Global holder of the D2D-specific network state, split out of the core Binder.

It keeps the D2D peering map (whether pairs of D2D-capable UEs communicate in Direct or Infrastructure Mode) and the set of D2D one-to-many transmitters, and answers the D2D capability/mode queries derived from them.

Every network with D2D-capable nodes declares one instance, normally named ‘d2dBinder’ next to the Binder; the D2D modules reach it through their d2dBinderModule parameter. The module is a passive state container with no events, signals or statistics.

Usage diagram¶

Used in¶

Name	Type	Description
Highway	network	Two eNodeB cells on a shared EPC PgwStandard, joined by an X2 link, with a router and a server behind the core. The cars are LteCar nodes created at run time by the VeinsInetManager from a SUMO road traffic simulation, so the car[] vector is empty in the topology itself.
MultiCell	network	Two eNodeB cells on a shared EPC PgwStandard, joined by an X2 link, with a router and a server behind the core. Four LteUe terminals are placed two per cell, and numExtCells ExtCell cells can be added as interferers. With hasD2D, the network holds the D2dBinder that D2D-capable nodes need, so that ‘**.hasD2D = true’ turns D2D on in the network and in all its nodes.
MultiCell_D2DMultihop	network	Five eNodeB cells, each reaching the EPC PgwStandard through a router of its own, with a further router and a server behind the core. There are no X2 links. numUe1 to numUe5 LteUe terminals attach per cell, and an EventGenerator and a MultihopD2DStatistics module sit beside them, wired to nothing.
SingleCell_D2D	network	SingleCell with its UEs split into three vectors, so that a configuration can address cellular terminals (ueCell), D2D transmitters (ueD2DTx) and D2D receivers (ueD2DRx) separately. The rest of the topology is the same: one eNodeB on an EPC PgwStandard, with a router and a server behind it.
SingleCell_D2DMulticast	network	SingleCell with its UEs split into cellular terminals (ueCell) and members of a D2D multicast group (ueD2D). The rest of the topology is the same: one eNodeB on an EPC PgwStandard, with a router and a server behind it.
Highway	network	Two gNodeB cells on a shared 5GC Upf, joined by an X2 link, with a router and a server behind the core. The cars are NrCar nodes created at run time by the VeinsInetManager from a SUMO road traffic simulation, so the car[] vector is empty in the topology itself.
SingleCell_Standalone_D2D	network	SingleCell_Standalone with its UEs split into three vectors, so that a configuration can address cellular terminals (ueCell), D2D transmitters (ueD2DTx) and D2D receivers (ueD2DRx) separately. The rest of the topology is the same: one gNodeB behind an intermediate and an anchor Upf, with a router and a server on the data network, plus numBgCells BackgroundCell interferers.

Parameters¶

Name	Type	Default value	Description
binderModule	string	“binder”

Properties¶

Name	Value	Description
display	i=block/cogwheel

Source code¶

//
// Global holder of the D2D-specific network state, split out of the core ~Binder.
//
// It keeps the D2D peering map (whether pairs of D2D-capable UEs communicate in
// Direct or Infrastructure Mode) and the set of D2D one-to-many transmitters,
// and answers the D2D capability/mode queries derived from them.
//
// Every network with D2D-capable nodes declares one instance, normally named
// 'd2dBinder' next to the ~Binder; the D2D modules reach it through their
// d2dBinderModule parameter. The module is a passive state container with no
// events, signals or statistics.
//
simple D2dBinder
{
    parameters:
        string binderModule = default("binder");
        @display("i=block/cogwheel");
}

File: src/simu5g/stack/d2d/binder/D2dBinder.ned