|
|
Application module:
Interconnect module connection routing |
ISO/TS 10303-1684:2010-03(E)
© ISO
|
This clause specifies the information requirements for the
Interconnect module connection routing
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
The following EXPRESS specification begins the
Interconnect_module_connection_routing_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Interconnect_module_connection_routing_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Fabrication_joint_arm;
--
ISO/TS 10303-1668
USE FROM
Interconnect_module_with_macros_arm;
--
ISO/TS 10303-1687
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Fabrication_joint_arm |
ISO/TS 10303-1668 |
| Interconnect_module_with_macros_arm |
ISO/TS 10303-1687 |
NOTE 2
See Annex C,
Figures
C.1, C.2and C.3
for a graphical representation of this schema.
This subclause specifies the ARM types
for this application module. The ARM types and
definitions are specified below.
The imcr_requirement_assignment_item type is an extension
of the
requirement_assignment_item type.
It adds the data
types
Dielectric_crossover_area
and
Stratum_feature_conductive_join
to the list of alternate data types.
NOTE The list of entity data types may be
extended in application modules that use the constructs of
this module.
EXPRESS specification:
*)
TYPE
imcr_requirement_assignment_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
requirement_assignment_item
WITH
(Dielectric_crossover_area,
Stratum_feature_conductive_join);
END_TYPE;
(*
The imcr_termination_or_junction type is an extension
of the
termination_or_junction type.
It adds the data
types
Explicitly_located_layer_connection_point
and
Inter_stratum_join_relationship
to the list of alternate data types.
NOTE The list of entity data types may be
extended in application modules that use the constructs of
this module.
EXPRESS specification:
*)
TYPE
imcr_termination_or_junction =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
termination_or_junction
WITH
(Explicitly_located_layer_connection_point,
Inter_stratum_join_relationship);
END_TYPE;
(*
The map_link type allows for the designation of the data
types
Conductive_interconnect_element_terminal_link
and
Passage_terminal_based_fabrication_joint_link.
EXPRESS specification:
*)
TYPE
map_link =
SELECT
(Conductive_interconnect_element_terminal_link,
Passage_terminal_based_fabrication_joint_link);
END_TYPE;
(*
The trace_junction_or_via type is an
extensible list of alternate data types
that allows for the designation of the data
types
Explicitly_located_layer_connection_point
and
Inter_stratum_join_relationship.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
EXPRESS specification:
*)
TYPE
trace_junction_or_via =
EXTENSIBLE
SELECT
(Explicitly_located_layer_connection_point,
Inter_stratum_join_relationship);
END_TYPE;
(*
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
A Dielectric_crossover_area is a relationship that relates one
Stratum_feature
with another that results in the creation of a dielectric crossover feature in a dielectric
Stratum.
EXPRESS specification:
*)
ENTITY Dielectric_crossover_area;
relating_concept : Stratum_feature;
related_concept : Stratum_feature;
resulting_dielectric_crossover : Stratum_feature;
resulting_shape :
OPTIONAL
Geometric_model;
INVERSE
technology_requirement : SET[1:?] OF Requirement_assignment FOR assigned_to;
END_ENTITY;
(*
Attribute definitions:
relating_concept:
one of the instances of
Stratum_feature
that is part of the relationship.
related_concept:
the other instance of
Stratum_feature
that is part of the relationship. If one element of the relationship is dependent up on the other, this attribute shall be
the dependent one.
resulting_dielectric_crossover:
specifies the
Stratum_feature
in a stratum of dielectric material for the Dielectric_crossover_area.
resulting_shape:
specifies the
Geometric_model
for the Dielectric_crossover_area. The value of this attribute need not be specified.
technology_requirement:
specifies an inverse relationship that specifies that the existence of the Dielectric_crossover_area
is dependent on the existence of the
Requirement_assignment
that specifies the Dielectric_crossover_area
as its
assigned_to.
There shall be one or more
Requirement_assignments
for a particular Dielectric_crossover_area.
A Direct_stratum_component_join_implementation is a means to implement a connection between a feature on a stratum and an
Embedded_physical_component_terminal, where the Stratum
and the
Embedded_physical_component_terminal
are in intimate physical contact. The effect is to associate the
Embedded_physical_component_terminal
with the
Layer_connection_point.
This
is required since an embedded component is not a
Stratum
or
Printed_component
and consequently a
Layer_connection_point
cannot directly reference an embedded component as a
resident_design_layer_stratum.
In order to be valid, the implementing_joint must reference a member of
topological_requirement.terminal_to_be_connected,
and at least one member of
topological_requirement.point_to_be_connected
must be related to
implementing_joint.fabrication_feature_1
or
implementing_joint.fabrication_feature_2.
NOTE 1
A Direct_stratum_component_join_implementation may implement a connection to more than one
Stratum.
NOTE 2
The joint shall reference exactly one terminal of SELF inherited from
Plated_inter_stratum_feature;
a member of
topological_requirement.point_to_be_connected
shall be associated with an
Inter_stratum_join_relationship
or with an
Intra_stratum_join_relationship
in order to complete the
Generic_physical_network.
Actually, the above is a rule, not a note.
EXPRESS specification:
*)
ENTITY Direct_stratum_component_join_implementation;
implementing_joint : Fabrication_joint;
topological_requirement : Stratum_embedded_physical_component_join_relationship;
END_ENTITY;
(*
Attribute definitions:
implementing_joint:
specifies the
Fabrication_joint
for the Direct_stratum_component_join_implementation.
topological_requirement:
specifies a role of the
Stratum_embedded_physical_component_join_relationship
for the Direct_stratum_component_join_implementation.
An Indirect_stratum_component_join_implementation is a type of
Plated_inter_stratum_feature.
An Indirect_stratum_component_join_implementation implements a connection between a feature on a stratum and an
Embedded_physical_component_terminal
where the
Stratum
and the
Embedded_physical_component_terminal
are not in intimate physical contact and the connection is made using a
Plated_inter_stratum_feature.
The effect is to associate the
Embedded_physical_component_terminal
with the
Layer_connection_point.
This is required since an embedded component is not a
Stratum
and consequently a
Layer_connection_point
cannot directly reference an embedded component as a
resident_design_layer_stratum. In order to be valid, the implementing_joint must reference a member of
indirect_topological_requirement.terminal_to_be_connected,
and at least one member of
indirect_topological_requirement.point_to_be_connected
must be related to
implementing_joint.fabrication_feature_1
or
implementing_joint.fabrication_feature_2.
The joint shall reference exactly one terminal of SELF inherited from
Plated_inter_stratum_feature;
a member of
indirect_topological_requirement.point_to_be_connected
shall be associated with an
Inter_stratum_join_relationship
or with an
Intra_stratum_join_relationship
in order to complete the
Generic_physical_network.
NOTE 1
An Indirect_stratum_component_join_implementation may implement a connection to more than one
Stratum.
NOTE 2
It is possible for a complex instance to be a member of this Application Object and to be a member of
Physical_network_supporting_inter_stratum_feature.
EXAMPLE
An example of a complex instance would be a case where the
Embedded_physical_component_terminal
is on the terminus of a multi-layer Via.
NOTE 3
The last statement in the description is a formal rule.
EXPRESS specification:
*)
ENTITY Indirect_stratum_component_join_implementation
SUBTYPE OF (Plated_inter_stratum_feature);
indirect_topological_requirement : Stratum_embedded_physical_component_join_relationship;
implementing_joint : Fabrication_joint;
UNIQUE
UR1: indirect_topological_requirement, implementing_joint;
END_ENTITY;
(*
Attribute definitions:
indirect_topological_requirement:
specifies the
Stratum_embedded_physical_component_join_relationship
for the Indirect_stratum_component_join_implementation.
implementing_joint:
specifies the
Fabrication_joint
for the Indirect_stratum_component_join_implementation.
Formal propositions:
UR1:
The combination of indirect_topological_requirement and implementing_joint shall be unique within a population of
Indirect_stratum_component_join_implementation.
A Junction_vertex_allocation is the relationship that specifies one or more
Layer_connection_point
to which a
Topological_junction
is mapped during the layout routing process.
A Junction_vertex_allocation is the result of an assignment process by a designer or a layout routing process that defines the location of
Inter_stratum_join_relationship
or
Explicitly_located_layer_connection_point. A Junction_vertex_allocation maps a node of a
Generic_physical_network
which may be only partially ordered into a network description which is highly ordered using a tree.
A Junction_vertex_allocation associates two
product_view_definitions,
one an
Interconnect_module_design_view
and the other a
Physical_unit_network_definition.
The
Physical_unit_network_definition
may be populated for the express purpose of representing the tree structure of the
Generic_physical_network
in the
Interconnect_module_design_view,
and therefore the version of the design would be the same for both.
EXPRESS specification:
*)
ENTITY Junction_vertex_allocation;
implementation_point : trace_junction_or_via;
required_vertex : Part_connected_terminals_topological_junction;
UNIQUE
UR1: required_vertex;
END_ENTITY;
(*
Attribute definitions:
implementation_point:
specifies the trace_junction_or_via for the Junction_vertex_allocation.
The implementation_point specifies either the
Inter_stratum_join_relationship
or
Explicitly_located_layer_connection_point
that, individually, maps the requirement that a junction participates in a connectivity onto points on conducting
Stratum
for the Junction_vertex_allocation.
NOTE 1
This construct allows the Junction_vertex_allocation to consider an Inter_stratum_join_relationship to be a vertex.
NOTE 2
The Junction_vertex_allocation allows for the specification of the location of the connections between physical traces and connected areas. It is common
practice for the point where a trace, via, pad, etc., connects with other features to be specified by the designer interactively
during layout. This location may be constrained for fabrication, layout, or signal integrity purposes. The Junction_vertex_allocation specifies these relationships.
required_vertex:
specifies the
Part_connected_terminals_topological_junction,
as a vertex of a
Physical_connectivity_definition,
that is to be mapped to an implementation_point by the Junction_vertex_allocation.
Formal propositions:
UR1:
The required_vertex shall be unique within a population of Junction_vertex_allocations.
A Physical_connectivity_abstraction_map is a mapping between an element of a tree structure in a name space based context and an equivalent element in a geometric
context. The element in the name space based context is Physical_connectivity_element. The element in the geometric context is either a Conductive_interconnect_element_terminal_link or a
Passage_terminal_based_fabrication_joint_link. The mapping allows a one to one equivalence to be built between the two contexts for simulation or routing purposes.
EXPRESS specification:
*)
ENTITY Physical_connectivity_abstraction_map;
name_space_context_based_definition : Part_connected_terminals_element;
geometric_context_based_definition : map_link;
UNIQUE
UR1: name_space_context_based_definition, geometric_context_based_definition;
END_ENTITY;
(*
Attribute definitions:
name_space_context_based_definition:
specifies a role of the
Part_connected_terminals_element
for the Physical_connectivity_abstraction_map.
geometric_context_based_definition:
specifies a role of the
map_link
for the Physical_connectivity_abstraction_map.
Formal propositions:
UR1:
The combination of geometric_context_based_definition and
name_space_context_based_definition shall be unique within a population of
Physical_connectivity_abstraction_maps.
*)
END_SCHEMA; -- Interconnect_module_connection_routing_arm
(*
© ISO 2009 — All rights reserved
