Software Radio Components Avatar
  1. OMG Specification

Software Radio Components — Open Issues

  • Acronym: SDRP
  • Issues Count: 17
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Section H; evaluate error conditions

  • Key: SDRP-188
  • Legacy Issue Number: 10420
  • Status: open  
  • Source: MITRE ( Kevin Richardson)
  • Summary:

    The base POSIX version of the AEP is being updated within the specification. In the update a new set of Error Conditions has been defined. The new error conditions need to be evaluated in order to determine whether or not they should be included within the specification.

  • Reported: SDRP 1.0 — Tue, 24 Oct 2006 04:00 GMT
  • Updated: Mon, 9 Mar 2015 04:18 GMT

Implementation Properties

  • Key: SDRP-137
  • Legacy Issue Number: 13932
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    The meta-model needs to allow implementation properties (e.g., entry point arguments for environment types) to be defined at the implementation level

  • Reported: SDRP 1.0b1 — Fri, 15 May 2009 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Definition of Complex type

  • Key: SDRP-136
  • Legacy Issue Number: 11418
  • Status: open  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    Recommendation:
    Complex data type should be defined in UML Profile for SWRadio.

    Resolution:
    Mark have requested SBC DTF to consider this problem.

  • Reported: SDRP 1.0b1 — Tue, 18 Sep 2007 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

issue in section 7.1.4 of SWRadio Component Framework Spec (formal/07-03-04

  • Key: SDRP-135
  • Legacy Issue Number: 11242
  • Status: open  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    Table 7.2 shows 11 stereotypes, but the 7.1.4 subsections support only 2 of them (RequiresPort and StreamPort). The other 9 are NOT detailed.

  • Reported: SDRP 1.0b1 — Thu, 2 Aug 2007 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

DTD XML Relationships Oversight

  • Key: SDRP-134
  • Legacy Issue Number: 10638
  • Status: open  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    I believe there is an error in Figure 7.1 in the "Component Document Type Definition Specification" dtc/06-04-22. Please note that the "DevicePackageDescriptor" is NOT showing any dependency on "Properties". This is a defined relationship in SCA 2.2.2.

    Proposed Resolution: DPD ----> (0..*) Properties

  • Reported: SDRP 1.0b1 — Fri, 2 Feb 2007 05:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Erroneous reference in PIM & PSM for SW Radio dtc/06-04-18

  • Key: SDRP-133
  • Legacy Issue Number: 10588
  • Status: open  
  • Source: Object Management Group ( Jon Siegel)
  • Summary:

    In Section 6.1 of the PIM & PSM for SW Radio intro book dtc/06-04-18,
    currently under DTC vote, one finds these references to Life Science specs:

    ===============================

    • Life Sciences Identifiers (LSID) - There are many
      cross references in the model defined by this specification. They are
      expressed using LSIDs. The relevant specification
      is available as OMG documents: formal/04-12-01 and dtc/04-08-03.
    • Genomic Map (GM) - The definitions in GM
      specification are either too limiting or too generic for SNPs purposes.
      The GM was designed at the time when genetic maps
      were the only genome wide maps. Current focus is on sequence
      maps.
      ===============================

    Presumably this is a cut-n-paste error/artifact, and should be repaired.
    The reference to BQS may be spurious as well.

  • Reported: SDRP 1.0b1 — Thu, 11 Jan 2007 05:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Domain Register Operation Issues

  • Key: SDRP-132
  • Legacy Issue Number: 10419
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    Issue:

    The domain manager register operations take in an object reference, so a callback is needed to get the identifier and profile attributes thus being inefficient.

    Extent of Change: Major

    Resolution:

    Add to the DeviceManagerRegistration interface operations, identifier and profile parameters to eliminate the callbacks.

  • Reported: SDRP 1.0b1 — Tue, 24 Oct 2006 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Unregister Operation Issues

  • Key: SDRP-131
  • Legacy Issue Number: 10414
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    Problem

    The domain manager and device manager unregister operations take in an object reference, which cannot be used directly for determining what component to unregister since one cannot compare on object references, so a callback is needed to get the identifier for unregistering service thus being inefficient.

    Proposed Solution: Replace the unregistering operations and remove device parameters with an unregistering identifier parameter of string type. This change affects CompositeDevice, DeviceManagerRegistration and ServiceRegistration interfaces.

  • Reported: SDRP 1.0b1 — Fri, 20 Oct 2006 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Stream / Channel - Parameters

  • Key: SDRP-130
  • Legacy Issue Number: 9584
  • Status: open  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    The following issue was raised in the SDR Forum's SCA WG:

    The Audio API does not include an interface for configuring or exchanging
    information that is specific to a stream or channel. Such information might
    include: quality of service parameters, packet size, symbol size, priority,
    and audio codec.

  • Reported: SDRP 1.0b1 — Fri, 21 Apr 2006 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

ConcreteDataPdu: New Attributes

  • Key: SDRP-129
  • Legacy Issue Number: 9583
  • Status: open  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    The following issue was raised in the SDR Forum's SCA WG:

    The group was concerned that without a control structure along with the data
    payload, the Audio API might impose unnecessary constraints. Discussion
    within the group identified that a control structure containing at least a
    Stream Id, a Payload Length, and a Sequence number could provide much
    greater flexibility that the API as currently stated

  • Reported: SDRP 1.0b1 — Fri, 21 Apr 2006 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Waveform Response to Audio Device RTS Signal

  • Key: SDRP-128
  • Legacy Issue Number: 9582
  • Status: open  
  • Source: BAE SYSTEMS ( Mark Scoville)
  • Summary:

    The following issue was raised in the SDR Forum's SCA WG:

    The PTT function is a oneway call and the audio device does not wait for an
    RTS signal. This situation prevents the waveform from providing a negative
    response to the PTT. If the waveform is unable to transmit data at the time
    of a PTT, does the waveform just ignore/drop the data without alerting the
    audio device or user through some specified mechanism?

  • Reported: SDRP 1.0b1 — Fri, 21 Apr 2006 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Simple Property Datatype

  • Key: SDRP-127
  • Legacy Issue Number: 9349
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    Simple Property Datatype. This allows users to form common definitions that can be used for components properties. A data/primitive stereotype that similar tags as RadioProperty. Add to properties section.

  • Reported: SDRP 1.0b1 — Wed, 1 Feb 2006 05:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

Wrong Stereotypes for Property Types

  • Key: SDRP-126
  • Legacy Issue Number: 9300
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    Wrong Stereotypes for Property Types. Make struct property and test def property types stereotypes of datatype instead of class in the properties. These should be treated type definitions not classes. EnumerationProperty?

  • Reported: SDRP 1.0b1 — Tue, 24 Jan 2006 05:00 GMT
  • Updated: Sat, 7 Mar 2015 00:33 GMT

A port may have characteristics

  • Key: SDRP-125
  • Legacy Issue Number: 7894
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    Problem: A port may have characteristics, such as throughput, latency,
    non-blocking time, etc.

    Proposed Solution: Add a characteristics property (TAG value) to the
    SWRadioPort
    stereotype. Add characteristics tag value for SWRadioPort in Table 8-3
    Interface
    and Port Stereotypes.

    Related to issue 7888

    Add to

    Attributes section for SWRadioPort

    characteristics : CharacteristicProperty [*]

    The characteristics attribute defines the characteristics for a port.

  • Reported: SDRP 1.0b1 — Mon, 20 Sep 1999 04:00 GMT
  • Updated: Sat, 7 Mar 2015 00:31 GMT

SWRadio UML Model is not referenced in the spec

  • Key: SDRP-3
  • Legacy Issue Number: 8697
  • Status: open  
  • Source: Anonymous
  • Summary:

    The SWRadio UML model is not mentioned in the SWRadio specification. Add a non-normative reference in the convenience document for the UML model. Add a paragraph explaining that the UML model is non-normative at the end of Section 6.2.

  • Reported: SDRP 1.0b1 — Wed, 13 Apr 2005 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:53 GMT

Unable to import the UML Profile for SWRadio into another UML tool

  • Key: SDRP-2
  • Legacy Issue Number: 7869
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • Summary:

    Save the UML Profile for SWRadio into XMI when there is UML 2 tool support
    that allows UML profiles creation and supports saving the profile as XMI.

  • Reported: SDRP 1.0b1 — Mon, 18 Oct 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:53 GMT

Section 9.2.6.1 IStream localSetup operation

  • Key: SDRP-1
  • Legacy Issue Number: 7853
  • Status: open  
  • Source: Anonymous
  • Summary:

    localSetup operation of the IStream interface should take the streamID parameter at a minimum. It may also provide access to the parameters defined by the IQualityOfServiceConnection facility.

  • Reported: SDRP 1.0b1 — Thu, 14 Oct 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:53 GMT