PIM and PSM for Smart Antenna Avatar
  1. OMG Specification

PIM and PSM for Smart Antenna — Closed Issues

  • Acronym: smartant
  • Issues Count: 24
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
SMRTANT-24 Section: 8.3.4 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-23 XSD or DTD file needed for mapping of configuration portions of PIM to XML smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-22 XMI for the profile itself is also needed smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-21 Section: 9.1 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-20 Section: 8.3.4 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-19 Section: 8.3.2,8.3.8 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-18 Section: 8.3.1 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-17 Section: 8.2.4 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-16 Section: 8.2.2 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-15 Section: 6.3 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-14 Section: 6.3 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-13 consider addition or correction of attributes smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-12 Corrections for minor errors and typos smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-11 Section 8 - reference for ModemComponent smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-10 Section 7.2.1 - interElementDistance smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-9 Section 7.2.1 - center frequency smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-8 The description for NumOfArrivals is not clear. smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-7 The description for TolerableBandwidth of AlgorithmType is not clear. smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-6 Section: 8 smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-5 Algorithm limitation of Algorithm Facilities smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-4 The description in section 6.6.2 is not clear. smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-3 base stations are not required smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-2 Make sure sure document is clear and easy to understand smartant 1.0b1 smartant 1.0 Resolved closed
SMRTANT-1 Sweep the document for English grammar and spelling accuracy smartant 1.0b1 smartant 1.0 Resolved closed

Issues Descriptions

Section: 8.3.4

  • Key: SMRTANT-24
  • Legacy Issue Number: 12358
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #23 How does the UShort field of the STCMapping represent a code pattern?

  • Reported: smartant 1.0b1 — Thu, 27 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    If the number of transmit antenna (NumAnt of STCMapping) is N, the space time codes are represented as N by N matrix and elements of the matrix are represented in complex. Therefore, the type of codePattern shall be complexsequence. Each element of the codePattern corresponds to each element of STC matrix as following manner.
    The first element of the codePattern corresponds to the first element of the first column of the matrix. Similarly, the second element of the codePattern is for the second element of the first column of the matrix. And N +1th element of the codePattern is for the first element of the second column of the matrix and N +2th element of the codePattern is for the second element of the second column of the matrix. Finally, N 2th element of the codePattern is for the last element of the last column of the matrix.

  • Updated: Sat, 7 Mar 2015 09:09 GMT

XSD or DTD file needed for mapping of configuration portions of PIM to XML

  • Key: SMRTANT-23
  • Legacy Issue Number: 12352
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #26 Is an XSD or DTD file needed for the mapping of the configuration portions of the PIM to XML? Or is this covered by existing specifications?

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Discussion:
    No additional xml dtds were needed to be defined since the ones in the swradio are sufficient for the properties described in the SA; they can be transformed into the Swradio XML using the swradio transformation rules.

    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

XMI for the profile itself is also needed

  • Key: SMRTANT-22
  • Legacy Issue Number: 12351
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #24 The Smart Antenna Profile.xml file included in sbc-08-02-02.zip appears to be the Smart Antenna PIM model, not the XMI of the UML Profile for Smart Antenna. The XMI for the profile itself is also needed.

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Jerry Bickle reports: "the profile is a profile"
    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 9.1

  • Key: SMRTANT-21
  • Legacy Issue Number: 12350
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #24 What is meant by "Object references map to the name of CORBA objects" in mapping rule #13? Does this refer to names in a naming service or the names of the interface types?

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Resolution:
    This rule means that object reference (such as Algorithms, Synchronizations, or Calibrations in Control Facilities) shall map to the name of CORBA object registered with naming service.

    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 8.3.4

  • Key: SMRTANT-20
  • Legacy Issue Number: 12349
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #22 The Beamforming interface's NullBFDirection attribute and the DOAEstimation interface's DOA attribute are each a FloatSequence. Are these dimensions of some coordinate system? Does anything more need to be specified?

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Discussion:
    5/9/2008: Bob raised this issue earlier in the week at the OMG meetings in March 08. By the conclusion of the week we had an errata that addressed the issue, and I believe the changes were placed in the document which was submitted. This was approved.
    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 8.3.2,8.3.8

  • Key: SMRTANT-19
  • Legacy Issue Number: 12348
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #21 What do the individual elements of the Beamforming interface's BFWeights and the ChannelEstimation interface's ChannelImpulse ComplexSequence attributes correspond to? Are these antenna elements? If so, does the association of indices with the geometry of the antenna need to be specified somewhere?

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Discussion:
    Each element of both BFWeights and ChannelImpulse corresponds to the RF/IF chain of smart antenna system. As it is very well known, the SA specification does not include any comments related to this issue.
    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 8.3.1

  • Key: SMRTANT-18
  • Legacy Issue Number: 12347
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #20 What do the ComplexType values returned by the getPreData() and getPostData() operations of the SAAlgorithmDevice interface contain? It seems an additional parameter may be needed to select which type of data is being requested. Or is this determined by the specific algorithm represented by the SAAlgorithmDevice instance?

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    These two operations had been defined for SAAlgorithm component to get data from modem component. The data are required to perform some typical smart antenna algorithms. However, this processing can be done via "Port" of the SAAlgorithm component. Therefore, we decide to remove these two operations but, for keeping the functionality of getting pre- and post-processing data, we have added two attributes: <<configureproperty>>preData and <<configureproperty>>postData.

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 8.2.4

  • Key: SMRTANT-17
  • Legacy Issue Number: 12346
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #19 No units have been specified for the Timing and Threshold Synchronization interface attributes whose types are ULong and ULongLong.

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Both of attributes have no dimension. Supplemental comments will be added in the specification.
    Usually, signals in baseband are represented by complex numbers without unit. Therefore, Threshold attribute has no unit.
    As for Timing attribute, this attribute should be represented in TimeType. It had been resolved before AB approval in Washington DC.

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 8.2.2

  • Key: SMRTANT-16
  • Legacy Issue Number: 12345
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #17 The CalibrationTable and CalibrationAccuracy attributes of the Calibration interface are of type ComplexSequence. I see no description of what the individual elements of these sequences correspond to. Do they related to individual antenna elements, or maybe times or frequencies? Also, units haven't been specified for these.

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    1. Output of calibration has no units. Therefore both attributes also have no units.
    2. "Each element of CalibrationTable represents a calibration-output which corresponds to each of RF/IF chains." has been added in description of CalibrationTable attribute.
    3. The description of CalibrationAccuracy has been replaced with "The CalibrationAccuracy attribute represents the required variance of calibration-output."

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 6.3

  • Key: SMRTANT-15
  • Legacy Issue Number: 12344
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #16 The relationship between the Device interfaces and the Control interfaces does not seem to be fully specified in this document. For example the AlgorithmControl interface has a <<readwrite>> Algorithms attribute that is a set of SAAlgorithmDevice instances. It doesn't say anything about how the SAAlgorithmDevice instances get created and registered with the AlgorithmControl interface, or what it means to modify this. Is this relationship between Devices and Controls sufficiently specified by the Component Framework Specification? Could you point me to the appropriate section?

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Following resolutions are to clarify the relationship between SAControl and other components.
    1. For the components that are included in Smart Antenna specification (i.e. SAAlgorithm component, Synchronization component and Calibration component), operations for register and unregister have been added in SAControl.
    For example, when SAAlgorithm instance gets created, the SAAlgorithm component shall call SAControl's register operation for registering itself with SAControl. Conversely, when SAAlgorithm component is released, the component shall call unregister operation for unregistering from SAControl.
    2. For RFIFComponent that is not included in Smart Antenna specification, <<configureproperty>>RFDeviceNames: String[1...*] has been added in SAControl. This attribute is used to represent the name of RFIFComponent. To get RFIFComponent instance, SAControl shall request a reference of the component to NamingService with the name of the component.
    3. Stereotype of all SAControl's attributes that contain a set of other components has been replaced with <<readonly>>.

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Section: 6.3

  • Key: SMRTANT-14
  • Legacy Issue Number: 12343
  • Status: closed  
  • Source: Red Hat ( Robert Kukura)
  • Summary:

    Reference (SmartAnt FTF Issues List): #7 The acknowledgments section lists "Office of the Military of Defense". Is this correct? Mark: See also opening section (2nd page of document)

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    This item had been resolved before AB approval in Washington DC.
    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

consider addition or correction of attributes

  • Key: SMRTANT-13
  • Legacy Issue Number: 12342
  • Status: closed  
  • Source: nContext ( Jeff Smith)
  • Summary:

    Reference (SmartAnt FTF Issues List): #7 Responses should specify examples in addition to the results. Choi: We have corrected the typo (CORBA->IDL @ page 11 of presentation material). Jerry: I think the examples are the submission, so I am not sure what additional information can be supplied. Or you specified in the submission where the requirement was satisified. Mark: may not be in scope of the revised submission Choi: We will skip this matter for the revised submission. We will come back to this problem when TC of OMG raises this matter more specifically. In fact, this matter will have to be treated again when we double check the requirements of RFP and consider addition or correction of attributes.

  • Reported: smartant 1.0b1 — Thu, 20 Mar 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Discussion:
    Jerry: I think the examples are the submission, so I am not sure what additional information can be supplied. Or you specified in the submission where the requirement was satisfied.

    Mark: may not be in scope of the revised submission

    Choi: We will skip this matter for the revised submission. We will come back to this problem when TC of OMG raises this matter more specifically. In fact, this matter will have to be treated again when we double check the requirements of RFP and consider addition or correction of attributes.

    This issue is related on submission presentation not specification document.

    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:30 GMT

Corrections for minor errors and typos

  • Key: SMRTANT-12
  • Legacy Issue Number: 12623
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary:
    Summarize minor errors and typos in a single issue.

    Resolution:
    Section Text
    1 This Specification responds to the requirements set by the "Request for Proposals of PIM and PSM for Smart Antenna"(sbc/06-12-10) of a smart antenna subsystem that can be utilized for expanding to expand a single antenna system to an array antenna system.The Smart Antenna specification is physically partitioned into three major chapters: UML Profile for Smart Antenna (SA), SA PIM, and SA PSM. UML Profile for SA defines a language for modeling a smart antenna system by expanding the UML language.SA PIM provides a set of interfaces for interfacing with the signal processing module, RF module, and controller module. SA PSM provides a rule for transforming the elements of the profile and SA PIM into the platform specific model for CORBA IDL and XMLThe SA specification is related to "Communication Channel and Equipment Specification (formal/07-03-02)" volume in such a way that stereotypes and classes that have not been commented in the SA specification are defined in it.
    2.1 A UML model of a specific SA either conforms to the SA profile or it does not. Such a UML model conforms to the SA profile if it satisfies all the constraints imposed by the profile package.
    2.2.2 Ÿ Supports expression of all the constructs defined by the profile, via UML 2.0 notation.
    4 MetadataThe Data that represents a models. For example, a UML model; a CORBA object model expressed in IDL; and a relation database schema expressed using CWM.
    7 This section defines the UML Profile for only a Smart Antenna only. The set of stereotypes and types that are not described in this section are defined in UML Profile for SWRadio components.
    7.1 Ÿ ComplexSequenceComplexSequence is an unbounded sequence of Complex(s).Ÿ <<primitive>>ArrayAntennaTypeArrayAntennaType, a specialization of String, denote the physical configuration of an array antenna(e.g., Phased Array, Circular Array, etc.)
    7.2.1 The ArrayAntenna stereotype, shown in Figure 1, represents an antenna array which consists of multiple antenna elements. The ArrayAntenna class shall have one or more AntennaElement's.AttributesŸ <<configureproperty>>maxMutualCoupling: DecibelThe maxMutualCoupling is the maximum mutual coupling value between antenna elements.Ÿ <<characteristicproperty>>bandwidth: HertzThe bandwidth attribute indicates the bandwidth of the physical array antenna.Ÿ <<characteristicproperty>>interElementDistance: MeterThe interElementDistance attribute represents the physical distance between antenna elements. The id attributes represents the identification of the channel.
    8 The SA Facilities has a dependency on the Communication Channel and Equipment Physical Layter Facilities as shown in Figure 2. Figure 3 illustrates the relation of the three facilities of SA. The Control Facilities, which include SAControl component, RFControl interface, SynchronizationControl interface, and AlgorithmControl interface, are used to control all algorithm operations performed in the digital signal processing parts and RF/IF operations such as analog to digital or digital to analog conversion. The Synchronization Facilities, which include SASynchronization component, CalibrationComponent component, Calibration interface, SynchronizationComponent component, and Synchronization interface, are used for RF chain calibration and symbol (or frame) synchronization. The CalibrationComponent component processes signals fed by the RFIFComponent component and the SynchronizationComponent component processes signals fed by the ModemComponent component. The Algorithm Facilities, which include the SAAlgorithm component and the Algorithm components, i.e. BeamformingComponent, STCComponent, SpatialMultiplexingComponent, DOAEstimationComponent, and ChannelEstimationComponent, and their interfaces, i.e. Beamforming, SpaceTimeCoding, SpatialMultiplexing, DOAEstimation, and ChannelEstimation respectively, are used to execute all the algorithms that are needed for the Smart Antenna System to provide superb performance compared to a Single Antenna System. Algorithm components process signals fed by the ModemComponent component. The Smart Antenna Subsystem shall implement a single SAControl component and one or more Algorithm component(s). More detailed explanations about interfaces among facilities in the SA are provided in the following sections.
    8.1 In this section, each function and interface provided by the Control Facilities is described. Figure 4 illustrates Control Facilities that include SAControl component, Synchronization Control interface, Algorithm Control interface, and RF Control interface. It can be observed from Figures 4 that RFControl interface, SynchronizationControl interface, and AlgorithmControl interface shall be realized by SAControl component, in order for SAControl component to control RFIFComponent component, SASynchronization component, and SAAlgorithm component, respectively, according to the functions to be performed in the SAControl component.
    8.1.1 DescriptionThe SAControl component takes on the definition as described in the UML Profile for Component Framework::Infrastructure::Service in addition to the realization of RFControl interface, AlgorithmControl interface, and SynchronizationControl interface. The SAControl component is used to control the entire Smart Antenna Subsystem with state behavior.AttributesŸ <<readwrite>>OperationMode: SAOperationMode The OperationMode attribute sets on the operation mode of the Smart Antenna Subsystem. The operation mode shall be one of three modes, TRANSMIT, RECEIVE, and COMBINATION. This attribute is only used when the SAControl's state is ACTIVE.Types and ExceptionsŸ <<enumerationproperty>>SAOperationMode ( TRANSMIT, RECIEVE, COMBINATION )The SAOperationMode defines the operation mode of the Smart Antenna Subsystem.TRANSMIT: The Smart Antenna Subsystem operates in transmitting mode.RECEIVE: The Smart Antenna Subsystem operates in receiving mode.COMBINATION: The Smart Antenna Subsystem operates in both transmitting and receiving mode.
    8.1.2 OperationsŸ registerAlgorithm(SAAlgorithm registeringAlgorithm)This operation is used to register the SAAlgorithm component with the AlgorithmControl interface. The SAAlgorithm component shall be registered with the AlgorithmControl interface in its initialization process. When the AlgorithmControl interface receives a registerAlgorithm call from the SAAlgorithm component, a reference to the SAAlgorithm component is provided. The AlgorithmControl interface adds the SAAlgorithm reference to its Algorithms attribute.
    8.1.3 OperationsŸ registerSynch(SynchronizationComponent registeringSynch)This operation is used to register SynchronizationComponent component with SynchronizationControl interface. The SynchronizationComponent component shall be registered with SynchronizationControl interface in its initialization process. Types and ExceptionsŸ <<exception>>InvalidCalObjectReferenceThe InvalidCalObjectReference exception is raised when the CalibrationComponent reference received in the registerSynch call is nil or any error is encountered during the unregisterSynch call on the SynchronizationControl interface.
    8.2.2 DescriptionThe Calibration interface is used to calibrate whole the entire RF/IF chains of the Smart Antenna System. AttributesŸ <<readonly>>CalibrationTable: ComplexSequence The CalibrationTable attribute represents the output of the Calibration. Each element of the CalibrationTable represents a calibration-output which corresponds to each of the RF/IF chains.Ÿ <<configureproperty>>ContinuousRun: Boolean The ContinuousRun attribute indicates whether or not the calibration is executed continuously.Ÿ <<configureproperty>>CalibrationAccuracy: ComplexSequence The CalibrationAccuracy attribute represents the required variance of calibration-output. The required accuracy shall be configured in a ComplexSequence for to representing both amplitude and phase.Ÿ <<configureproperty>>CalibrationPeriod: TimeType The CalibrationPeriod attribute is used to control the calibration period.Ÿ <<queryproperty>>CalibrationTime: TimeType The CalibrationTime attribute return the time required for processing a single calibration processing using the active settings.
    8.2.3 The CalibrationComponent component realizes the Calibration interface and extends the SASynchronization component. Calibration is to compensate for amplitude and phase differences of the RF/IF chain associated with each antenna in transmit and receive mode. The problem of calibration has arisen because the amplitude and phase characteristics of the signal path associated with each antenna are different from each other. Especially even if the optimal weight vector is computed from the received signal for uplink, such that the uplink communication of the smart antenna system can fully exploit the enhancements in both communication capacity and cell coverage downlink beam-forming can never be optimized without accurate calibration. In other words, the objective of calibration is to compensate for the mutual coupling effects between antenna array elements as well as for the mismatches of channel amplitude and/or channel phase in Smart Antenna Systems.
    8.2.4 Ÿ <<configureproperty>>ObservationLength: ULongThe ObservationLength attribute is used to configure the observation length in samples.Ÿ <<readonly>>Timing: TimeType The Timing attribute represents the acquired symbol (or frame) timing.Ÿ <<configureproperty>>Threshold: ULongLong The Threshold attribute is used to configure the threshold for signal detection. Since signals in the baseband are represented by complex numbers without unit, the Threshold attribute also has no unit.
    8.2.5 The SynchronizationComponent component realizes the Synchronization interface and extends the SASynchronization component. Symbol (or frame) synchronization is a processing for detection of which detects the symbol (or frame) timing. Synchronization is performed prior to symbol demodulation of symbol (or frame decoding of frame) and operation of the smart antenna algorithm operation. To enhance the performance of the Smart Antenna System, accurate symbol (or frame) timing shall be provided is required. In addition, to guarantee the QoS (Quality of Service) of the initial network access, fast and robust acquisition of the initial access signal shall be provided to the Smart Antenna System.
    8.3 In this section each function and interface in the Algorithm facilities is described. Figure 6 illustrates the Algorithm Facilities that which include the SAAlgorithm component, Algorithm components, which and the interfaces. The Algorithm components are the BeamformingComponent, STCComponent, SpatialMultiplexingComponent, DOAEstimationComponent, and ChannelEstimationComponent. And, the interfaces are the Beamforming interface, SpaceTimeCoding interface, SpatialMultiplexing interface, ChannelEstimation interface, and DOAEstimation interface.
    8.3.1 DescriptionThe SAAlgorithm component is an abstract component from which all the components in the Algorithm Facilities shall inherit. In other words, this component provides every interface for controlling all the Algorithm components. AttributesŸ <<configureproperty>>OperationType: AlgorithmOperationType The OperationType attribute sets an operation type of SAAlgorithm components. The operation type shall be one of the following three types, CONTUINUOUS, SINGLE_BURST, and REPEATED_BURST.Ÿ <<queryproperty>>AvailableAlgorithm: AlgorithmType[1..*] The AvailableAlgorithm attribute represents a list of the algorithms available for use on the SAalgorithm.Ÿ <<configureproperty>>ActiveAlgorithm: String The ActiveAlgorithm attribute sets algorithm or gets activated algorithm either sets or gets the active algorithm.Ÿ <<configureproperty>>preData: Complex The preData attribute represents the pre-processing data which are used for calculating the beamforming weight vector. For example, the pre-processing data denote the pre-despreading data for CDMA systems and the pre-FFT data for OFDM(A) systems, etc.Ÿ <<configureproperty>>postData: Complex The postData attribute represents the post-processing data which are used for calculating the beamforming weight vector. For example, the post-processing data denote the despread data for CDMA systems and the FFT data for OFDM(A) systems, etc.Types and ExceptionsŸ <<enumerationproperty>>AlgorithmOperationType ( CONTINUOUS, SINGLE_BURST, REPEATED_BURST ) The AlgorithmOperationType defines the operation type of data processing operation type.Ÿ AlgorithmType(Name: String, Delay: TimeType, PowerConsumption: Float, TolerableBandwidth: Hertz) Name: The name of an algorithm as a String. Delay: The time required for an algorithm to perform a single algorithm execution. PowerConsumption: The power consumption for an algorithm to perform a single algorithm execution. TolerableBandwidth: The tolerable bandwidth for an algorithm to converge.
    8.3.2 Ÿ <<readonly>>BFWeights: ComplexSequenceThe BFWeights attribute is weight vectors are computed by the BeamformingComponent. When this attribute is read, the BeamformingComponent computes a new value from the received signals. When this attribute is set up, the BeamformingComponent applies a given value vector that provides the desired radiation pattern.Ÿ <<configureproperty>>PolarUnit: Boolean The PolarUnit attribute is used to switch between the real/imag mode and the mag/phase mode of the Weights attribute.Ÿ <<readwrite>>NullBFDirection: FloatSequence The NullBFDirection attribute is used to specify the directions of the nulls in degrees to block known sources of interference.Ÿ <<readwrite>>FixedBFGainDirection: FloatSequence The FixedBFGainDirection attribute is used to specify fixed gains (dB) in fixed directions (degrees) to amplify weak signals in known directions.Ÿ <<readwrite>>SideLobeLevel: FloatSequenceThe SideLobeLevel attribute is used to limit the side lobe level in decibel (dB). Ÿ <<readonly>>OrderedEigenvalues: FloatSequence The OrderedEigenvalues attribute presents the eigen channel quality metrics used in the BeamformingComponent.Ÿ <<readonly>>OrderedEigenvectors: ComplexSequence The OrderedEigenvectors attribute presents the eigen channel quality metrics used in the BeamformingComponent.Ÿ <<readwrite>>MaxEigenChannels: Short The MaxEigenChannels attribute configures maximum number of eigen channels to be used in the BeamformingComponent.
    8.3.4 Ÿ <<readwrite>>STCPattern: STCMapping[1..*] The STCPattern attribute represents the actual definition of the STC mapping. Each input symbol of the STCComponent is mapped to one of the transmit antennas according to the STCMapping.
    8.3.5 The STCComponent component extends the SAAlgorithm component and realizes the SpaceTimeCoding interface. The STCComponent is for Space Time Coding (STC) processing. A Space Time Coding (STC) is a method employed to improve the reliability of data transmission in wireless communication systems by using multiple transmit antennas. STCs rely on transmitting multiple, redundant copies of a data stream to the receiver in the hope that at least some of them may survive the physical path between transmission and reception in a good enough state to allow reliable decoding.
    8.3.6 DescriptionThe SpatialMutiplexing interface is used to control the SpatialMultiplexingComponent.AttributesŸ <<queryproperty>>AvailableSMScheme: SpatialMultiplexingType[1..*]The AvailableSMScheme attribute represents a list of the spatial multiplexing schemes available for use on the SpatialMultiplexingComponent.Ÿ <<configureproperty>>ActiveSMScheme: SpatialMultiplexingTypeThe ActiveSMScheme attribute sets SpatialMultiplexingType or gets activated either sets or activates the SpatialMultiplexingType.Types and ExceptionsŸ <<Primitive>>SpatialMultiplexingTypeThe SpatialMultiplexingType, a specialization of String, denotes the type of the algorithm used for spatial multiplexing.(e.g.,V-BLAST, D-BLAST, H-BLAST, etc.).
    8.3.7 The SpatialMultiplexingComponent component extends the SAAlgorithm component and realizes the SpatialMultiplexing interface. The SpatialMultiplexingComponent is for spatial multiplexing. The Spatial multiplexing is a transmission technique in MIMO wireless communication to that transmits independent and separately encoded data signals from each of the multiple transmit antennas.
    8.3.8 AttributesŸ <<readwrite>>ChannelCoherenceTime: TimeType The ChannelCoherenceTime attribute represents the channel coherence time.Ÿ <<configureproperty>>ChannelEstimationPeriod: TimeType The ChannelEstimationPeriod attribute is used to control the channel estimation period. This attribute would be especially important to trade overhead time and processing against the rate of change in the channel due to platform motion, etc.Ÿ <<configureproperty>> ChannelEstimationAccuracy: Complex The ChannelEstimationAccuracy attribute represents the required accuracy of the channel estimation.Ÿ <<readwrite>>MaxEigenChannels: Short The MaxEigenChannels attribute configures the maximum number of eigen channels to be used in ChannelEstimationComponent.
    8.3.9 The ChannelEstimationComponent component extends the SAAlgorithm component and realizes the ChannelEstimation interface. The Space-time equalization system or diversity combining system is implemented using the ChannelEstimationComponent. The Space-time Equalization is a receiving technique which makes use of temporal processing on the signals received from multiple antennas to correct frequency distortion in the received signal path. And, the diversity combining is another receiving technique that to mitigates the multipath fading effects, which are inherent in practical wireless networks, by combining the signals of multiple antennas.
    8.3.10 Ÿ <<readonly>>DOA: FloatSequence The DOA attribute represents the direction of arrival (DOA) angle in degree.Ÿ <<configureproperty>>NumOfArrivals: UShort The NumOfArrivals specifies how many DOA estimates are required allowing for estimation of the arrival of the same signal from multiple directions.Ÿ <<configureproperty>>DOAEstSignalType: ShortSequence The DOAEstimationSignalType attribute specifies the character type of the various signals to estimate.Ÿ <<queryproperty>>DOAEstQuality: ULong The DOAEstQuality attribute indicates the DOA estimation quality.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Resolution:
    Section Text
    1 This Specification responds to the requirements set by the "Request for Proposals of PIM and PSM for Smart Antenna"(sbc/06-12-10) of a smart antenna subsystem that can be utilized for expanding to expand a single antenna system to an array antenna system.The Smart Antenna specification is physically partitioned into three major chapters: UML Profile for Smart Antenna (SA), SA PIM, and SA PSM. UML Profile for SA defines a language for modeling a smart antenna system by expanding the UML language.SA PIM provides a set of interfaces for interfacing with the signal processing module, RF module, and controller module. SA PSM provides a rule for transforming the elements of the profile and SA PIM into the platform specific model for CORBA IDL and XMLThe SA specification is related to "Communication Channel and Equipment Specification (formal/07-03-02)" volume in such a way that stereotypes and classes that have not been commented in the SA specification are defined in it.
    2.1 A UML model of a specific SA either conforms to the SA profile or it does not. Such a UML model conforms to the SA profile if it satisfies all the constraints imposed by the profile package.
    2.2.2 Ÿ Supports expression of all the constructs defined by the profile, via UML 2.0 notation.
    4 MetadataThe Data that represents a models. For example, a UML model; a CORBA object model expressed in IDL; and a relation database schema expressed using CWM.
    7 This section defines the UML Profile for only a Smart Antenna only. The set of stereotypes and types that are not described in this section are defined in UML Profile for SWRadio components.
    7.1 Ÿ ComplexSequenceComplexSequence is an unbounded sequence of Complex(s).Ÿ <<primitive>>ArrayAntennaTypeArrayAntennaType, a specialization of String, denote the physical configuration of an array antenna(e.g., Phased Array, Circular Array, etc.)
    7.2.1 The ArrayAntenna stereotype, shown in Figure 1, represents an antenna array which consists of multiple antenna elements. The ArrayAntenna class shall have one or more AntennaElement's.AttributesŸ <<configureproperty>>maxMutualCoupling: DecibelThe maxMutualCoupling is the maximum mutual coupling value between antenna elements.Ÿ <<characteristicproperty>>bandwidth: HertzThe bandwidth attribute indicates the bandwidth of the physical array antenna.Ÿ <<characteristicproperty>>interElementDistance: MeterThe interElementDistance attribute represents the physical distance between antenna elements. The id attributes represents the identification of the channel.
    8 The SA Facilities has a dependency on the Communication Channel and Equipment Physical Layter Facilities as shown in Figure 2. Figure 3 illustrates the relation of the three facilities of SA. The Control Facilities, which include SAControl component, RFControl interface, SynchronizationControl interface, and AlgorithmControl interface, are used to control all algorithm operations performed in the digital signal processing parts and RF/IF operations such as analog to digital or digital to analog conversion. The Synchronization Facilities, which include SASynchronization component, CalibrationComponent component, Calibration interface, SynchronizationComponent component, and Synchronization interface, are used for RF chain calibration and symbol (or frame) synchronization. The CalibrationComponent component processes signals fed by the RFIFComponent component and the SynchronizationComponent component processes signals fed by the ModemComponent component. The Algorithm Facilities, which include the SAAlgorithm component and the Algorithm components, i.e. BeamformingComponent, STCComponent, SpatialMultiplexingComponent, DOAEstimationComponent, and ChannelEstimationComponent, and their interfaces, i.e. Beamforming, SpaceTimeCoding, SpatialMultiplexing, DOAEstimation, and ChannelEstimation respectively, are used to execute all the algorithms that are needed for the Smart Antenna System to provide superb performance compared to a Single Antenna System. Algorithm components process signals fed by the ModemComponent component. The Smart Antenna Subsystem shall implement a single SAControl component and one or more Algorithm component(s). More detailed explanations about interfaces among facilities in the SA are provided in the following sections.
    8.1 In this section, each function and interface provided by the Control Facilities is described. Figure 4 illustrates Control Facilities that include SAControl component, Synchronization Control interface, Algorithm Control interface, and RF Control interface. It can be observed from Figures 4 that RFControl interface, SynchronizationControl interface, and AlgorithmControl interface shall be realized by SAControl component, in order for SAControl component to control RFIFComponent component, SASynchronization component, and SAAlgorithm component, respectively, according to the functions to be performed in the SAControl component.
    8.1.1 DescriptionThe SAControl component takes on the definition as described in the UML Profile for Component Framework::Infrastructure::Service in addition to the realization of RFControl interface, AlgorithmControl interface, and SynchronizationControl interface. The SAControl component is used to control the entire Smart Antenna Subsystem with state behavior.AttributesŸ <<readwrite>>OperationMode: SAOperationMode The OperationMode attribute sets on the operation mode of the Smart Antenna Subsystem. The operation mode shall be one of three modes, TRANSMIT, RECEIVE, and COMBINATION. This attribute is only used when the SAControl's state is ACTIVE.Types and ExceptionsŸ <<enumerationproperty>>SAOperationMode ( TRANSMIT, RECIEVE, COMBINATION )The SAOperationMode defines the operation mode of the Smart Antenna Subsystem.TRANSMIT: The Smart Antenna Subsystem operates in transmitting mode.RECEIVE: The Smart Antenna Subsystem operates in receiving mode.COMBINATION: The Smart Antenna Subsystem operates in both transmitting and receiving mode.
    8.1.2 OperationsŸ registerAlgorithm(SAAlgorithm registeringAlgorithm)This operation is used to register the SAAlgorithm component with the AlgorithmControl interface. The SAAlgorithm component shall be registered with the AlgorithmControl interface in its initialization process. When the AlgorithmControl interface receives a registerAlgorithm call from the SAAlgorithm component, a reference to the SAAlgorithm component is provided. The AlgorithmControl interface adds the SAAlgorithm reference to its Algorithms attribute.
    8.1.3 OperationsŸ registerSynch(SynchronizationComponent registeringSynch)This operation is used to register SynchronizationComponent component with SynchronizationControl interface. The SynchronizationComponent component shall be registered with SynchronizationControl interface in its initialization process. Types and ExceptionsŸ <<exception>>InvalidCalObjectReferenceThe InvalidCalObjectReference exception is raised when the CalibrationComponent reference received in the registerSynch call is nil or any error is encountered during the unregisterSynch call on the SynchronizationControl interface.
    8.2.2 DescriptionThe Calibration interface is used to calibrate whole the entire RF/IF chains of the Smart Antenna System. AttributesŸ <<readonly>>CalibrationTable: ComplexSequence The CalibrationTable attribute represents the output of the Calibration. Each element of the CalibrationTable represents a calibration-output which corresponds to each of the RF/IF chains.Ÿ <<configureproperty>>ContinuousRun: Boolean The ContinuousRun attribute indicates whether or not the calibration is executed continuously.Ÿ <<configureproperty>>CalibrationAccuracy: ComplexSequence The CalibrationAccuracy attribute represents the required variance of calibration-output. The required accuracy shall be configured in a ComplexSequence for to representing both amplitude and phase.Ÿ <<configureproperty>>CalibrationPeriod: TimeType The CalibrationPeriod attribute is used to control the calibration period.Ÿ <<queryproperty>>CalibrationTime: TimeType The CalibrationTime attribute return the time required for processing a single calibration processing using the active settings.
    8.2.3 The CalibrationComponent component realizes the Calibration interface and extends the SASynchronization component. Calibration is to compensate for amplitude and phase differences of the RF/IF chain associated with each antenna in transmit and receive mode. The problem of calibration has arisen because the amplitude and phase characteristics of the signal path associated with each antenna are different from each other. Especially even if the optimal weight vector is computed from the received signal for uplink, such that the uplink communication of the smart antenna system can fully exploit the enhancements in both communication capacity and cell coverage downlink beam-forming can never be optimized without accurate calibration. In other words, the objective of calibration is to compensate for the mutual coupling effects between antenna array elements as well as for the mismatches of channel amplitude and/or channel phase in Smart Antenna Systems.
    8.2.4 Ÿ <<configureproperty>>ObservationLength: ULongThe ObservationLength attribute is used to configure the observation length in samples.Ÿ <<readonly>>Timing: TimeType The Timing attribute represents the acquired symbol (or frame) timing.Ÿ <<configureproperty>>Threshold: ULongLong The Threshold attribute is used to configure the threshold for signal detection. Since signals in the baseband are represented by complex numbers without unit, the Threshold attribute also has no unit.
    8.2.5 The SynchronizationComponent component realizes the Synchronization interface and extends the SASynchronization component. Symbol (or frame) synchronization is a processing for detection of which detects the symbol (or frame) timing. Synchronization is performed prior to symbol demodulation of symbol (or frame decoding of frame) and operation of the smart antenna algorithm operation. To enhance the performance of the Smart Antenna System, accurate symbol (or frame) timing shall be provided is required. In addition, to guarantee the QoS (Quality of Service) of the initial network access, fast and robust acquisition of the initial access signal shall be provided to the Smart Antenna System.
    8.3 In this section each function and interface in the Algorithm facilities is described. Figure 6 illustrates the Algorithm Facilities that which include the SAAlgorithm component, Algorithm components, which and the interfaces. The Algorithm components are the BeamformingComponent, STCComponent, SpatialMultiplexingComponent, DOAEstimationComponent, and ChannelEstimationComponent. And, the interfaces are the Beamforming interface, SpaceTimeCoding interface, SpatialMultiplexing interface, ChannelEstimation interface, and DOAEstimation interface.
    8.3.1 DescriptionThe SAAlgorithm component is an abstract component from which all the components in the Algorithm Facilities shall inherit. In other words, this component provides every interface for controlling all the Algorithm components. AttributesŸ <<configureproperty>>OperationType: AlgorithmOperationType The OperationType attribute sets an operation type of SAAlgorithm components. The operation type shall be one of the following three types, CONTUINUOUS, SINGLE_BURST, and REPEATED_BURST.Ÿ <<queryproperty>>AvailableAlgorithm: AlgorithmType[1..*] The AvailableAlgorithm attribute represents a list of the algorithms available for use on the SAalgorithm.Ÿ <<configureproperty>>ActiveAlgorithm: String The ActiveAlgorithm attribute sets algorithm or gets activated algorithm either sets or gets the active algorithm.Ÿ <<configureproperty>>preData: Complex The preData attribute represents the pre-processing data which are used for calculating the beamforming weight vector. For example, the pre-processing data denote the pre-despreading data for CDMA systems and the pre-FFT data for OFDM(A) systems, etc.Ÿ <<configureproperty>>postData: Complex The postData attribute represents the post-processing data which are used for calculating the beamforming weight vector. For example, the post-processing data denote the despread data for CDMA systems and the FFT data for OFDM(A) systems, etc.Types and ExceptionsŸ <<enumerationproperty>>AlgorithmOperationType ( CONTINUOUS, SINGLE_BURST, REPEATED_BURST ) The AlgorithmOperationType defines the operation type of data processing operation type.Ÿ AlgorithmType(Name: String, Delay: TimeType, PowerConsumption: Float, TolerableBandwidth: Hertz) Name: The name of an algorithm as a String. Delay: The time required for an algorithm to perform a single algorithm execution. PowerConsumption: The power consumption for an algorithm to perform a single algorithm execution. TolerableBandwidth: The tolerable bandwidth for an algorithm to converge.
    8.3.2 Ÿ <<readonly>>BFWeights: ComplexSequenceThe BFWeights attribute is weight vectors are computed by the BeamformingComponent. When this attribute is read, the BeamformingComponent computes a new value from the received signals. When this attribute is set up, the BeamformingComponent applies a given value vector that provides the desired radiation pattern.Ÿ <<configureproperty>>PolarUnit: Boolean The PolarUnit attribute is used to switch between the real/imag mode and the mag/phase mode of the Weights attribute.Ÿ <<readwrite>>NullBFDirection: FloatSequence The NullBFDirection attribute is used to specify the directions of the nulls in degrees to block known sources of interference.Ÿ <<readwrite>>FixedBFGainDirection: FloatSequence The FixedBFGainDirection attribute is used to specify fixed gains (dB) in fixed directions (degrees) to amplify weak signals in known directions.Ÿ <<readwrite>>SideLobeLevel: FloatSequenceThe SideLobeLevel attribute is used to limit the side lobe level in decibel (dB). Ÿ <<readonly>>OrderedEigenvalues: FloatSequence The OrderedEigenvalues attribute presents the eigen channel quality metrics used in the BeamformingComponent.Ÿ <<readonly>>OrderedEigenvectors: ComplexSequence The OrderedEigenvectors attribute presents the eigen channel quality metrics used in the BeamformingComponent.Ÿ <<readwrite>>MaxEigenChannels: Short The MaxEigenChannels attribute configures maximum number of eigen channels to be used in the BeamformingComponent.
    8.3.4 Ÿ <<readwrite>>STCPattern: STCMapping[1..*] The STCPattern attribute represents the actual definition of the STC mapping. Each input symbol of the STCComponent is mapped to one of the transmit antennas according to the STCMapping.
    8.3.5 The STCComponent component extends the SAAlgorithm component and realizes the SpaceTimeCoding interface. The STCComponent is for Space Time Coding (STC) processing. A Space Time Coding (STC) is a method employed to improve the reliability of data transmission in wireless communication systems by using multiple transmit antennas. STCs rely on transmitting multiple, redundant copies of a data stream to the receiver in the hope that at least some of them may survive the physical path between transmission and reception in a good enough state to allow reliable decoding.
    8.3.6 DescriptionThe SpatialMutiplexing interface is used to control the SpatialMultiplexingComponent.AttributesŸ <<queryproperty>>AvailableSMScheme: SpatialMultiplexingType[1..*]The AvailableSMScheme attribute represents a list of the spatial multiplexing schemes available for use on the SpatialMultiplexingComponent.Ÿ <<configureproperty>>ActiveSMScheme: SpatialMultiplexingTypeThe ActiveSMScheme attribute sets SpatialMultiplexingType or gets activated either sets or activates the SpatialMultiplexingType.Types and ExceptionsŸ <<Primitive>>SpatialMultiplexingTypeThe SpatialMultiplexingType, a specialization of String, denotes the type of the algorithm used for spatial multiplexing.(e.g.,V-BLAST, D-BLAST, H-BLAST, etc.).
    8.3.7 The SpatialMultiplexingComponent component extends the SAAlgorithm component and realizes the SpatialMultiplexing interface. The SpatialMultiplexingComponent is for spatial multiplexing. The Spatial multiplexing is a transmission technique in MIMO wireless communication to that transmits independent and separately encoded data signals from each of the multiple transmit antennas.
    8.3.8 AttributesŸ <<readwrite>>ChannelCoherenceTime: TimeType The ChannelCoherenceTime attribute represents the channel coherence time.Ÿ <<configureproperty>>ChannelEstimationPeriod: TimeType The ChannelEstimationPeriod attribute is used to control the channel estimation period. This attribute would be especially important to trade overhead time and processing against the rate of change in the channel due to platform motion, etc.Ÿ <<configureproperty>> ChannelEstimationAccuracy: Complex The ChannelEstimationAccuracy attribute represents the required accuracy of the channel estimation.Ÿ <<readwrite>>MaxEigenChannels: Short The MaxEigenChannels attribute configures the maximum number of eigen channels to be used in ChannelEstimationComponent.
    8.3.9 The ChannelEstimationComponent component extends the SAAlgorithm component and realizes the ChannelEstimation interface. The Space-time equalization system or diversity combining system is implemented using the ChannelEstimationComponent. The Space-time Equalization is a receiving technique which makes use of temporal processing on the signals received from multiple antennas to correct frequency distortion in the received signal path. And, the diversity combining is another receiving technique that to mitigates the multipath fading effects, which are inherent in practical wireless networks, by combining the signals of multiple antennas.
    8.3.10 Ÿ <<readonly>>DOA: FloatSequence The DOA attribute represents the direction of arrival (DOA) angle in degree.Ÿ <<configureproperty>>NumOfArrivals: UShort The NumOfArrivals specifies how many DOA estimates are required allowing for estimation of the arrival of the same signal from multiple directions.Ÿ <<configureproperty>>DOAEstSignalType: ShortSequence The DOAEstimationSignalType attribute specifies the character type of the various signals to estimate.Ÿ <<queryproperty>>DOAEstQuality: ULong The DOAEstQuality attribute indicates the DOA estimation quality.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Section 8 - reference for ModemComponent

  • Key: SMRTANT-11
  • Legacy Issue Number: 12622
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary:
    The ModemComponent in Section 8 is not defined in this spec. If the ModemComponent is in the SWRadio components specification, refer to the SWRadio components spec.

    Resolution:
    As the ModemComponent is in the SWRadio components specification, we refer to the SWRadio components spec.
    Original text:
    Algorithm components process signals fed by ModemComponent component.

    Revised text:
    Algorithm components process signals fed by ModemComponent component of the Communication Channel and Equipment of the SWRadio components specification (refer to Section 3.2.3).

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    As the ModemComponent is in the SWRadio components specification, we refer to the SWRadio components spec.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Section 7.2.1 - interElementDistance

  • Key: SMRTANT-10
  • Legacy Issue Number: 12621
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary:
    The interElementDistance if only allows one value then the system is limited to use antenna arrays with uniform separation. Multiple values are suggested to allow more cases. If the above properties already allow multiple values please ignore the above comments.

    Resolution:
    We have replaced the type of interElementDistance with FloatSequence to allow configuring multiple values.

    Original text:
    o <<characteristicproperty>>interElementDistance: Meter
    The interElementDistance attribute represents physical distance between antenna elements.

    Revised text:
    o <<characteristicproperty>>interElementDistance: FloatSequence
    The interElementDistance attribute represents physical distances between all the pairs of adjacent antenna elements in meter.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    We have replaced the type of interElementDistance with FloatSequence to allow configuring multiple values.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Section 7.2.1 - center frequency

  • Key: SMRTANT-9
  • Legacy Issue Number: 12620
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary:
    The bandwidth property should either allow multiple values or an additional property called center frequency should be allowed.

    Resolution:
    We have added an attribute for configuring the center frequency.

    Original text:
    N/A

    Revised text:
    o <<characteristicproperty>>CenterFreq: Hertz
    The CenterFreq attribute represents the center of the operating frequency of the array antenna.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    We have added an attribute for configuring the center frequency.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

The description for NumOfArrivals is not clear.

  • Key: SMRTANT-8
  • Legacy Issue Number: 12619
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Resolution:
    We have corrected the description for NumOfArrivals.

    Original text:
    o <<configureproperty>>NumOfArrivals: UShort
    The NumOfArrivals specifies how many DOA estimates are required allowing for estimation of the arrival of the same signal from multiple directions.

    Revised text:
    o <<configureproperty>>NumOfArrivals: UShort
    The NumOfArrivals specifies the maximum number of DOA estimations for a single signal having multipath.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    We have corrected the description for NumOfArrivals.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

The description for TolerableBandwidth of AlgorithmType is not clear.

  • Key: SMRTANT-7
  • Legacy Issue Number: 12618
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Resolution:
    We have corrected the the description for TolerableBandwidth of AlgorithmType.

    Original text:
    TolerableBandwidth: The tolerable bandwidth for an algorithm to converge.

    Revised text:
    TolerableBandwidth:.The maximum bandwidth that a given algorithm can guarantee its normal operation.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    We have corrected the the description for TolerableBandwidth of AlgorithmType.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Section: 8

  • Key: SMRTANT-6
  • Legacy Issue Number: 12617
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary:
    "i.e." means "that is", is that the intended usage in introduction of Section 8?

    Resolution:
    We have corrected the sentence in introduction of Section 8.

    Original text:
    The Algorithm Facilities, which include SAAlgorithm component and Algorithm components, i.e. BeamformingComponent, STCComponent, SpatialMultiplexingComponent, DOAEstimationComponent, and ChannelEstimationComponent, and interfaces, i.e. Beamforming, SpaceTimeCoding, SpatialMultiplexing, DOAEstimation, and ChannelEstimation, are used to execute all the algorithms that are needed for the Smart Antenna System to provide superb performance compared to Single Antenna System.
    Revised text:
    The Algorithm Facilities, which include SAAlgorithm component, Algorithm components, and interfaces are used to execute all the algorithms that are needed for the Smart Antenna System to provide a superb performance compared to Single Antenna System. The Algorithm components include BeamformingComponent, STCComponent, SpatialMultiplexingComponent, DOAEstimationComponent, and ChannelEstimationComponent. The interfaces consist of Beamforming, SpaceTimeCoding, SpatialMultiplexing, DOAEstimation, and ChannelEstimation.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    We have corrected the sentence in introduction of Section 8.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Algorithm limitation of Algorithm Facilities

  • Key: SMRTANT-5
  • Legacy Issue Number: 12616
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary:
    Are the algorithms limited to the algorithms mentioned in Algorithm Facilities? Or those are just examples?

    Resolution:
    Algorithm Facilities are capable of handling beamforming systems, MIMO systems, diversity systems, and space time equalization systems. In order for Algorithm Facilities to be able to handle a new kind of array system other than those four kinds of array systems, we have to define necessary components in Algorithm Facilities.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Resolution:
    Algorithm Facilities are capable of handling beamforming systems, MIMO systems, diversity systems, and space time equalization systems. In order for Algorithm Facilities to be able to handle a new kind of array system other than those four kinds of array systems, we have to define necessary components in Algorithm Facilities.

    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:14 GMT

The description in section 6.6.2 is not clear.

  • Key: SMRTANT-4
  • Legacy Issue Number: 12615
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Original Text:
    6.6.2 Space-Time Equalization
    The preceding two techniques usually assume that the signal of interest is a narrowband signal compared to the coherence bandwidth of the channel and is thus subjected to flat fading across the bandwidth of the signal. Multipath fading in wireless communication can also introduce frequency distortion to the received signal. By introducing temporal processing in each antenna element to remove the effect of frequency distortion and doing a spatial combining described above results in mitigating channel induced frequency selective fading and providing antenna gain. Such schemes are called space-time adaptive processing (STAP) or equalization.

    6.6.3 Diversity Combining
    A major limiting factor in wireless communication is multipath fading where the amplitude of the received signal fluctuates over time. The occurrence of a deep fade where the signal amplitude becomes very small can impair the communications link for a conventional or a single antenna system. When multiple antennas are used it becomes less likely that two or more antennas undergo deep fades at the same time. This diversity in the received signal, for the same transmitted information, is exploited by smart antenna processing schemes. Many simple algorithms, such as maximal ratio combining, equal gain combining, and selection diversity have been developed to take advantage of using antenna arrays to exploit diversity reception in wireless systems. These algorithms weight the received signal similar to beamforming but based on a different criterion used in the algorithm

    Revised Text:
    6.6.2 Diversity Combining
    A major limiting factor in wireless communication is multipath fading where the amplitude of the received signal fluctuates over time. The occurrence of a deep fade where the signal amplitude becomes very small can impair the communications link for a conventional or a single antenna system. When multiple antennas are used it becomes less likely that two or more antennas undergo deep fades at the same time. This diversity in the received signal, for the same transmitted information, is exploited by smart antenna processing schemes. Many simple algorithms, such as maximal ratio combining, equal gain combining, and selection diversity have been developed to take advantage of using antenna arrays to exploit diversity reception in wireless systems. These algorithms weight the received signal similar to beamforming but based on a different criterion used in the algorithm

    6.6.3 Space-Time Equalization
    The preceding two techniques usually assume that the signal of interest is a narrowband signal compared to the coherence bandwidth of the channel and is thus subjected to a flat fading across the bandwidth of the signal. Multipath fading in wireless communication can also introduce a frequency distortion to the received signal. By means of a temporal processing for each antenna element and a spatial combining of the temporally processed received signals, a frequency-selective fading introduced by the frequency distortion described above can significantly be mitigated.

  • Reported: smartant 1.0b1 — Thu, 31 Jul 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    We have corrected the description in Section 6.6.2.

  • Updated: Fri, 6 Mar 2015 23:14 GMT

base stations are not required

  • Key: SMRTANT-3
  • Legacy Issue Number: 12535
  • Status: closed  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    Portions of the specification may have dependencies on have a base station. To satisfy the RFP requirement for supporting comms on the move (OTM), base stations are not required

  • Reported: smartant 1.0b1 — Tue, 17 Jun 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    There are no dependencies on base station in the specification.
    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Make sure sure document is clear and easy to understand

  • Key: SMRTANT-2
  • Legacy Issue Number: 12534
  • Status: closed  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    Ensure that the document in general has enough description and clarity for a tool vendor to be able to implement it for each interfaces, attribute, operation etc.

  • Reported: smartant 1.0b1 — Tue, 17 Jun 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Disposition: Closed (Duplication of 12623)

  • Updated: Fri, 6 Mar 2015 23:14 GMT

Sweep the document for English grammar and spelling accuracy

  • Key: SMRTANT-1
  • Legacy Issue Number: 12533
  • Status: closed  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    Sweep the document for English grammar and spelling accuracy

  • Reported: smartant 1.0b1 — Tue, 17 Jun 2008 04:00 GMT
  • Disposition: Resolved — smartant 1.0
  • Disposition Summary:

    Disposition: Closed (Duplication of 12623)

  • Updated: Fri, 6 Mar 2015 23:14 GMT