1. Explain the common functional path
An RF inventory line can retain a frequency label yet omit how a component relates different signal paths. Murata's basic diplexer explanation describes filters for two frequency regions sharing a common port. The common role is therefore a relationship within the documented filtering arrangement. It is not another name for a centre frequency or for whichever visible terminal happens to appear central on a package. Preserve that logical role before trying to interpret the short filter description attached to the offered item.
The branch roles explain what is shared: different frequency regions connect through the filtering arrangement to the common path. This is useful product information even when a seller has no application-level RF report. It lets the recipient distinguish a documented diplexer function from an isolated filter label. Keep the explanation at that functional level. A board connector name, an assembly reference and a component terminal are different identifiers; this article does not derive their relationship from the common-port concept or from an image of removed hardware.
2. Preserve the branch filter combination
Murata describes low-pass/high-pass, low-pass/band-pass and band-pass/band-pass combinations. These terms identify different qualitative relationships between the branch filtering functions. They should not be collapsed into one assumption that every diplexer has identical branch types. For an identified product, preserve the combination its applicable description actually supports. A list saying only filter and a nominal frequency can lose both the shared common path and the distinction between the two branches, leaving the functional identity incomplete.
The type of combination is separate from its numerical operating limits. A low-pass or band-pass description tells a different story from a numerical band edge, insertion loss or attenuation entry. The existing RF-filter guide covers those response-description fields and their evidence. Here the inventory decision is whether the documented branches form the stated diplexer relationship. It neither reconstructs a response curve nor assigns a particular frequency label to a physical terminal. Keep any numerical information in its own exact-product reference rather than deriving it from the combination name.
3. Keep frequency routing distinct from switched routing
A diplexer explanation based on frequency separation should not be rewritten as a control-selected switch description. The RF-switch guide concerns logical routes selected by control state and the behaviour of unselected branches. Murata's diplexer explanation concerns filters sharing a common port for different frequency regions. These are different functional questions, even though both discussions can use common and branch terminology. Preserve the component's documented function instead of assuming that similar port words mean the same routing mechanism.
Terminology also needs its manufacturer context. Murata discusses diplexer and duplexer usage in its explanation, including the relevant filtering context. Keep that explanation attached to Murata rather than announcing a universal naming rule for every RF manufacturer or assembly. An equipment record's abbreviated name can be useful context without replacing the applicable component document. Where the two descriptions differ, the question is which functional relationship the exact item supports, not which familiar catalogue label can be applied to make the line look complete.
4. Stop functional roles becoming physical assignments
Knowing the meaning of common and branch roles does not identify a physical pad, lead or board connector. That relationship belongs to the readable documentation for the actual component and assembly. A removed part can have a supported functional category while its physical mapping remains unestablished. Keeping those levels separate is particularly important when a stock photograph or former radio-band description is the only available application context. Neither should be used to assign terminals using the generic diplexer explanation.
For an ICULTRA buyback enquiry, describe the exact identified product and the supported common/branch relationship, retaining its filter combination where documented. State whether the actual offer concerns loose components or a larger assembly, without claiming that internal parts are separately released. Keep existing RF reports as separate evidence for the hardware they cover. This guide provides no pin map, S-parameter result or current routing assessment. The recipient can review the disclosed functional identity and request the appropriate product records before any lot-specific acceptance or commercial agreement.
Sources and further reading
Murata's bounded official LC-diplexer web text supports common/branch functions, qualitative filter combinations and its contextual terminology. No physical pin map, numerical bands, plotted response, S-parameters or installed routing result is supplied.