Child pages
  • TAPI Contributions and Presentations

Proposed equipment model adjustments.

Currently AccessPort provides relates to one or more pins. The relationship is via connectorPin which is of type ConnectorPinAddress (see below). Through this the AccessPort can relate to multiple connectors/pins.

AccessPort

Qualified Name: TapiEquipment::ObjectClasses::AccessPort

A group of pins that together support a signal group where any one pin removed from the group will prevent all signals of the signal group from flowing successfully.
In some cases the AccessPort may simply reference a single connector (e.g., where the pin-connector association is simpe such that the AccessPort references all pinsof one connector).

Applied stereotypes:

  • OpenModelClass
    • support: MANDATORY
  • OpenInterfaceModelClass
    • objectCreationNotification: NA
    • objectDeletionNotification: NA
  • Experimental

 

Inherits properties from:

  • GlobalClass

 

Table 1 : Attributes for AccessPort

Attribute Name

Type

Multiplicity

Access

Stereotypes

Description

connectorPin

 

ConnectorPinAddress

 

1..*

R

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

 

The list of Pins that support the AccessPort.

 

 

uuid

Inherited

Uuid

 

1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

 

UUID: An identifier that is universally unique within an identifier space, where the identifier space is itself globally unique, and immutable.
An UUID carries no semantics with respect to the purpose or state of the entity.
UUID here uses string representation as defined in RFC 4122.  The canonical representation uses lowercase characters.
Pattern: [0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-' + '[0-9a-fA-F]{4}-[0-9a-fA-F]{12}
Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6

 

 

name

Inherited

NameAndValue

 

0..*

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

 

List of names. This value is unique in some namespace but may change during the life of the entity.
A name carries no semantics with respect to the purpose of the entity.

 

 

 


Currently ConnectorPinAddress provides an opportunity to reference one whole connector or a single pin in a connector (see below). If a whole connector is referenced, then it is assumed that all pins are used. If several but not all pins from a connector are used then the structure repeats the connector name and equipment UUID. The pin is referenced by a single pinIdentification.

ConnectorPinAddress

Qualified Name: TapiEquipment::TypeDefinitions::ConnectorPinAddress

The identification of the location of the Connector and/or Pin.

 

Applied stereotypes:

  • Experimental

 

Table 1 : Attributes for ConnectorPinAddress

Attribute Name

Type

Multiplicity

Access

Stereotypes

Description

connectorIdentification

String

 

1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

Identification of the Connector in the conetxt of the referenced Equipment.

 

 

pinIdentification

String

 

0..1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

Where relevant, identification of the Pin in the contect of the connector.
Where the whole connector is used, then individual Pins need not be identified.

 

 

equipmentUuid

Uuid

 

1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

Reference to the Equipment that is fitted with the Connector/Pin.

 

 

 


An enhancement to ConnectorPinAddress to add an attribute “pinAndRole” (a list) is proposed. The structure is currently called “…_UPDATED” for clarity. As the change (highlighted in red ) is additive and optional the enhancement is backward compatible so it should be possible to simply add to the existing ConnectorPinAddress structure (see below). Hence no new structure is required at this level and there is no impact on AccessPort.

ConnectorPinAddress_UPDATED

Qualified Name: TapiEquipment::TypeDefinitions::ConnectorPinAddress_UPDATED

The identification of the location of the Connector and/or Pin.

 

Applied stereotypes:

  • Experimental

 

Table 1 : Attributes for ConnectorPinAddress_UPDATED

Attribute Name

Type

Multiplicity

Access

Stereotypes

Description

connectorIdentification

String

 

1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

Identification of the Connector in the conetxt of the referenced Equipment.

 

 

pinIdentification

String

 

0..1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

Where relevant, identification of the Pin in the contect of the connector.
Where the whole connector is used, then individual Pins need not be identified.

 

 

equipmentUuid

Uuid

 

1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

Reference to the Equipment that is fitted with the Connector/Pin.

 

 

pinAndRole

PinAndRole

 

0..*

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

If there is more than one pin used in a connector and/or there is a need to identify the role of one or more pins then this property can be used.
 

 

 

The proposed change above allows a single connectorPin property in an access port to reference a list of pins. This means that if several pins are used in the same connector, they can be collected in the same connectorPin reference.

The new attribute is of type PinAndRole. PinAndRole offers greater clarity in terms of pin properties. The key properties are:

  • locationInConnector: Providing clear pin referencing so as to relate to the name of the actual pin in the physical connector.
  • pinName: Where the pin in the connector has a distinct name not merged into the location identifier
  • pinRole: Which allows the referenced pin to be tied to a specific functional detail in the NEP referencing the AccessPort. As noted om the description, there may be several pinRoles.

 

PinAndRole

Qualified Name: TapiEquipment::TypeDefinitions::PinAndRole

Provides an opportunity, for a pin, to give the location of the pin and the role of the pin.

 

Applied stereotypes:

  • Experimental

 

Table 1 : Attributes for PinAndRole

Attribute Name

Type

Multiplicity

Access

Stereotypes

Description

locationInConnector

String

 

1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

The named location of the pin in the context of the connector.
This is likely to be the normal numbering/naming for the type of connetor, e.g. "7", "6-GND", "Common" etc.

 

 

pinRole

String

 

0..*

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Experimental

It is not always necessary to specify a role (or list of roles) as the connector locationInConnector may be sufficient (as these are sometimes clearly role based.
Each entry represents a role in the context of the specific access port.
Each entry ties the pin to a functional element in the associated NEP(s) etc.
For example:
- a pin might carry several distinct signals where each signal is idenitified in the list
- a pin may carry a signal and power
- a signal carried by a pin may be the receive flow (INPUT) to a bidirectional NEP or the transmit flow (OUTPUT) or indeed both (BIDIRECTIONAL).

 

 

pinName

String

 

0..1

RW

OpenInterfaceModelAttribute

  • AVC: NA

OpenModelAttribute

  • valueRange: no range constraint
  • support: MANDATORY

Where the pin has a distinct location identifier and a distinct name this field can be used for the name.
For example:
- locationInConnector = 6, pinName = GND

 

 

 

It is recommended that this change is made in TAPI 2.3.