Package: simu5g.stack.pdcp
IPdcpLegSplitter
module interfaceModule interface for the TX-side leg dispatcher of a PDCP entity (see PdcpEntityBase): implementations pick the RLC leg for each PDCP PDU and apply that leg's id mapping. Instantiated by the PdcpEntityBase compound via a typename parameter when a leg needs it: on a multi-leg bearer, and on a single-leg bearer whose leg is not the anchor's (an SCG bearer).
Inheritance diagram
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Implemented by
| Name | Type | Description |
|---|---|---|
| DcPdcpLegSplitter | simple module |
TX-side leg dispatcher of a dual-connectivity split bearer (two legs), steering each PDCP PDU to a leg from the split policy RRC pushes off the bearer's definition (TS 38.331 PDCP-Config, TS 38.323 5.2.1). A splitter serves exactly one direction: a UE's TX side is uplink, a base station's is downlink. |
Used in compound modules
| Name | Type | Description |
|---|---|---|
| PdcpEntityBase | compound module |
Base type of the PDCP entity of one data radio bearer: packages the transmitting and the receiving side of TS 36.323 / 38.323, plus the leg split/join stage of a multi-leg bearer (e.g. an NR dual connectivity split bearer). Created dynamically by BearerManagement, one per (peer, DRB) pair. |
Properties
| Name | Value | Description |
|---|---|---|
| display | i=block/dispatch |
Source code
// // Module interface for the TX-side leg dispatcher of a PDCP entity // (see ~PdcpEntityBase): implementations pick the RLC leg for each PDCP PDU and // apply that leg's id mapping. Instantiated by the PdcpEntityBase compound via a // typename parameter when a leg needs it: on a multi-leg bearer, and on a // single-leg bearer whose leg is not the anchor's (an SCG bearer). // moduleinterface IPdcpLegSplitter { parameters: @display("i=block/dispatch"); gates: input in; // PDUs from the TX entity output out[]; // To leg k }File: src/simu5g/stack/pdcp/IPdcpLegSplitter.ned