Radio Transmitter Object

Radio transmitter objects act as the exit points of a node for packets transmitted on radio links. They can contain multiple channel objects, each of which can attempt to access appropriate radio receiver channels in remote nodes via a radio link. The processes of modulation and transmission are modeled to the extent that they affect the correct reception of a packet.

Transmitters can have multiple input streams, each one corresponding to a separate radio channel, and each connected to a separate packet stream originating at other modules in the node. There is a direct correspondence between input stream indices and channel indices. In other words, a packet that is forwarded to the transmitter on input stream j is transmitted on radio channel j. Radio transmitters are considered as data sinks from the perspective of other modules within the node, so they cannot have outgoing packet streams. A single exception is made to this rule to allow the transmitter to connect to an antenna module via an output stream.

In the Node Editor, radio transmitters are represented by default as square boxes with a circle representing the node, an outwardly directed arrow representing the direction of packet flow, and waves representing the propagation of the radio signal and the broadcast nature of the medium. The transmitter’s name is displayed beneath it as shown in the figure below.

Figure 64: Radio Transmitter Representation

Radio Transmitter Representation

Radio transmitter objects are the interface between a node and the radio transmission medium. Because this communication medium is not explicitly represented by a object in the network domain, its attributes are located on the link end points. In other words, the link attributes are divided between the radio transmitter and the radio receiver. Each radio transmitter can participate in simultaneous evaluation of multiple radio links. Properties associated with transmission are specified as attributes of the radio transmitter while properties associated with reception are specified as attributes of the radio receiver.

For more information about the detailed operation of radio links, see “Wireless Communication Links” on page 8.

Radio Transmitter Object Attributes

The built-in attributes of the radio transmitter object are listed below, in alphabetical order.

Table 27: Point-to-Point Transmitter Object Built-In Attributes

Name Data Type
chanmatch model typed file
channel compound
closure model typed file
icon name icon
modulation typed file
name string
propdel model typed file
rxgroup model typed file
tagain model typed file
txdel model typed file

chanmatch model

This attribute specifies the name of a compiled pipeline procedure capable of dynamically computing one of three possible outcomes characterizing the type of interaction which can occur between a radio transmitter channel and a radio receiver channel. The default model is dra_chanmatch, which can dictate that a transmission be viewed by a radio receiver channel as a valid and potentially receivable signal, an effective source of interference, or an irrelevant signal. If the latter outcome occurs, the remainder of the pipeline is not executed for the given transmitter-receiver pair.

If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Default Models” on page 284.

Refer to Chapter 10 “Radio Transceiver Pipeline” on page 263 for more information about this pipeline stage.

Editing Simulation
Data Type typed file string
Access read / write read
Default Value dra_chanmatch
Units
Constraints

channel

This attribute specifies the outgoing channels supported by the transmitter. It consists of any number of radio transmitter channel objects, one for each channel supported by the transmitter. The attributes of each individual channel are described in Radio Transmitter Channel Object.

Editing Simulation
Data Type compound compound
Access read / write / promote read
Default Value
Units
Constraints

closure model

This attribute specifies the name of a compiled pipeline procedure capable of dynamically determining the ability of a given radio transmitter channel to reach a given radio receiver channel. The default model is dra_closure which determines whether or not line of sight is achieved between the transmitter and receiver. The result of this pipeline stage determines if the remainder of the pipeline is executed for the radio link of interest.

If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Default Models” on page 284.

Refer to Chapter 10 “Radio Transceiver Pipeline” on page 263 for more information about this pipeline stage.

Editing Simulation
Data Type typed file string
Access read / write read
Default Value dra_closure
Units
Constraints

icon name

This attribute specifies the name of the icon used to represent the radio transmitter module in node model diagrams. Icons can be created with the icon editor. The value of this attribute has no effect on simulation behavior.

Editing Simulation
Data Type icon N/A
Access read / write N/A
Default Value ra_tx
Units
Constraints

modulation

This attribute specifies the name of a modulation table used to look up the bit error rate (ber) as a function of the effective signal to noise ratio. Antenna tables can be constructed in the Antenna Curve Editor or via the External Model Access (EMA) package. The bit error rate calculation is typically performed in the ber model stage of the Radio Transceiver Pipeline. The calculated bit error rate is used to estimate the number of bit errors in each packet segment. This attribute is also used by the chanmatch model pipeline stage to determine whether the receiver and transmitter channels are compatible.

Editing Simulation
Data Type typed file string
Access read / write / promote read / write
Default Value bpsk
Units
Constraints

name

This attribute is a user-assigned identification for the radio transmitter module. The value assigned to this attribute appears beneath the module’s icon in the node diagram. It can also be used to refer to the object during simulation. Refer to the documentation on the KP op_id_from_name() for more information.

Editing Simulation
Data Type string string
Access read / write read
Default Value rt_n, n >= 0
Units
Constraints unique in node model, no dots

propdel model

This attribute specifies the name of a compiled pipeline procedure capable of computing the propagation delay associated with the transmission of a given packet toward a given receiver. The default model is dra_propdel which calculates two delay times. The first is the propagation delay time separating transmission of the first bit of the packet from reception of the same bit at the destination receiver. The second is the propagation delay time separating transmission of the last bit of the packet from reception of the same bit at the destination receiver.

If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Default Models” on page 284.

Refer to Chapter 10 “Radio Transceiver Pipeline” on page 263 for more information about this pipeline stage.

Editing Simulation
Data Type typed file string
Access read / write read
Default Value dra_propdel
Units
Constraints

rxgroup model

This attribute specifies the name of a compiled pipeline procedure capable of determining the possibility of radio interaction between a given transmitter channel and a given receiver channel. The result of this pipeline stage will be used to statically decouple non-interacting transceiver pairs to minimize the number of invocations of the pipeline during execution of the simulation. The default model is dra_rxgroup which allows all receivers to be potential destinations.

If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Default Models” on page 284.

Refer to Chapter 10 “Radio Transceiver Pipeline” on page 263 for more information about this pipeline stage.

Editing Simulation
Data Type typed file string
Access read / write read
Default Value dra_rxgroup
Units
Constraints

tagain model

This attribute specifies the name of a compiled pipeline procedure capable of computing antenna gain provided by the transmitter’s antenna for a particular outgoing radio transmission in the direction of a particular receiver. The default model is dra_tagain which computes gain based on the vector separating the transmitter and receiver and the pointing attributes of the transmitter’s associated antenna. The result of this pipeline stage is used in a link budget calculation in the power model stage of the transceiver pipeline.

If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Default Models” on page 284.

Refer to Chapter 10 “Radio Transceiver Pipeline” on page 263 for more information about this pipeline stage.

Editing Simulation
Data Type typed file string
Access read / write read
Default Value dra_tagain
Units
Constraints

txdel model

This attribute specifies the name of a compiled pipeline procedure capable of computing the transmission delay associated with the transmission of a given packet. The transmission delay is the time separating the start of transmission of the first bit of the packet from the end of transmission of the last bit. The default model is dra_txdel which computes the delay based on the channel data rate and the length of the packet.

If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Default Models” on page 284.

Refer to Chapter 10 “Radio Transceiver Pipeline” on page 263 for more information about this pipeline stage.

Editing Simulation
Data Type typed file string
Access read / write read
Default Value dra_txdel
Units
Constraints

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com