Content model for the entity TIMING in the absolutely scheduled peculiarity. Identifier for the (fixed) slot where the frame described by this timing is sent in the static part of a application cycle. Used as priority for arbitration in the dynamic part of a cycle. Usualy used (with cycleCounter) for frame identification The communication cycle where the frame described by this timing is sent. If a timing is given in this way the referencing cluster must specify the NUMBER-OF-CYCLES as upper bound and point of total repetition. The first communication cycle where the frame described by this timing is sent The number of communication cycles (after the frist cycle) whenever the frame described by this timing is sent again Reserved space providing schema extendibility. For reusability active conditions content model is specified using a type definition. System state that must rule that the referencing timing is activated. To enable the description of combined states the occurence of SYSTEM-TRIGGER as well as of SYSTEM-STATE is unbounded. Use one trigger with many states, if these states must rule simultaneously (AND related) for activation. Use a separate trigger for each state if only one state needs to rule for activation. System state that must rule that the referencing timing is activated. The channel(s) on which the signal shall be sent. Content model for the entity CHANNEL with platform specific extendability. Top level element of all PDU-Triggerings on a channel A PDU's send behavior and identification on a certain channel Top level element of all frameTriggerings on a channel A frames send behavior and identification on a certain channel Reserved space providing schema extendibility. Content model for the entity CLUSTER with platform specific extendability. A channels speed in bits per second Indicates whether the significance of the bits (in a byte) is decreasing (value=true) or increasing (value=false) with the time. All frames on this cluster have to be encoded in this bit order. Usually the bit order is fixed with the protocol specification. A clusters protocol A clusters physical layer Collection of references (foreign keys) A clusters medium type Total number of cycles until a temporal transmission pattern is repeated. The CYCLE-COUNTER of an ABSOLUTELY-SCHEDULED-TIMING is evaluated against this parameter. Maximal supported length in bytes for frames in this cluster. Reserved space providing schema extendibility. Content model for the entity CODING. Application Type of data. Coded Type of data on communication system. Method to calulate the transmitted value to the physical representation Reserved space providing schema extendibility. Top level element of all codings Predefined encoding of one or more signals Content model for the entity COMPOSITE Describing the level of composition. See e.g. fibex4lin for platform specific restrictions. Collection of subordenated composites Collection of subordenated PDUs Refering a subordenated composite. Collection of subordenated ecus Refering a subordenated composite. Collection of subordenated functions Refering a subordenated composite. Collection of subordenated signals Reserved space providing schema extendibility. Content model for the entity CONNECTOR with platform specific extendability. An ECUs reception gate on the referenced channel as a collection of signal instances (on this channel) or (in case of using the functional layer) as a collection of referenced functional input ports. An ECUs reception port as a referenced frame, pdu and signal instance. An ECUs send gate on the referenced channel as a collection of provided frameTriggerings (frames on this channel) An ECUs send port as a referenced frame, pdu and signal instance. Reserved space providing schema extendibility. All controllers (usually a single one) where the referenced port(s) should be located. Refering a controller. Content model for the entity CONTROLLER with platform specific extendability. For hardware classification For hardware classification A controllers termination impedance (same on all channels) A controllers transceiver Reserved space providing schema extendibility. Content model for the entity TIMING in the cyclic peculiarity. Specification of the repeating cycle whenever the frame described by this timing is sent Specification of the time that is needed before the frame can be sent the first time Condition that must be fulfiled by the system that the cylce can be started Condition that must be fulfiled by the system or some signals that the cylce is started Condition that must be fulfiled by the system or some signals that the cylce is stopped Number of repetitions the frame is sent from the moment the stop condition has been met Reserved space providing schema extendibility. ECU relevant diagnostic addresses An ECU specific ID for repsonses of diagnostic routines An ECU relevant diagnostic address of the type given as attribute. Switched area of the multiplexer. The content changes dependent on the switch Content model for the entity PORT in the ECU related peculiarity. Selected PDUs within the referenced FRAME Single PDU within the referenced FRAME All PDUs within the FRAME are selected Reserved space providing schema extendibility. Describes, which value of the SIGNAL is to be send dependent on the current system state. The value corresponds to the CONSTRS in COMPU-METHOD Global state of the system General sending behavior dependent on various system states Describes, which value of the SIGNAL is to be send dependent on the current system state. The value can correspond to the CONSTRS in COMPU-METHOD Content model for the entity ECU. Platform-specific extensions are not possible, to maintain the capability to describe multi-platform networks. Collection of references (foreign keys) Top level element of all controllers inside of an ECU Dedicated hardware inside of an ECU realizing its interface to one or more channels All channels controlled by a single controller The connection between the referencing ECU and the referenced channel via the referenced controller Reserved space providing schema extendibility. Root of all stand-alone elements Top level element of all clusters In multi-channel systems such as TTP or FlexRay known as 'bus'. To avoid confusion, we decides not to use this term any more. Top level element of all channels In single-channel systems such as CAN or LIN known as 'bus'. To avoid confusion, we decides not to use this term any more. Top level element of all gateways A gateway is a specific ECU translating frames and signals from one channel into another. Further description of gateway behaviour is intended for a later version of FIBEX Top level element of all ECUs Electronic Control Unit (sometimes called 'node') Top level element of all PDUs Top level element of all frames Smallest piece of information exchanged over the communication system. A frame normally consists of a header and a data (payload) section. The data section contains signals. Top level element of all functions Part of the application running in an ECU Top level element of all signals Smallest logical piece of information exchanged by applications Top level element of all composite A hierarchical structure on functions or ecus. Content model for the entity TIMING in the event controlled peculiarity. Specification of the time that elapses before the frame can be sent the next time Condition that must be fulfiled by the system that an event will be registrated Condition (Event) that must be fulfiled by the system or some signals to cause the frame to be sent Number of repetitions the frame is sent from the moment the send condition has been breached Reserved space providing schema extendibility. For reusability execute conditions content model is specified using a type definition. Additional data of a company involved in FIBEX project. The LIN-wide unique identification of the referenced company . Collecting the products or specifications of the referenced company. Time behavior of a frame specified in a sequence of cluster specific timing types Specification of a sending behaviour where the transmission order is predefined, e.g. used on LIN clusters Specification of a sending behaviour where the exact time for the frames transmission is guaranteed, e.g. used on FLEXRAY clusters Content model for the entity FRAME-TRIGGERING. Refering a frame Reserved space providing schema extendibility. Content model for the entity FRAME. The used length (in bytes) of the referencing frame. Should not be confused with a static byte length reserved for each frame by some platforms (e.g. FlexRay). See the FIBEX specification for examples. Reserved space providing schema extendibility. Content model for the entity PORT in the function related peculiarity. Reserved space providing schema extendibility. A functions reception gate A functions reception gate for the referenced signal A functions reception gate A functions reception gate for the referenced signal All functions affected by this requirement. Content model for the entity FUNCTION. A functions (seen as a task) cycle period. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation. A functions (seen as a task) cycle offset from the applications start up. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation A functions (seen as a task) worst case execution time from the applications start up. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation A functions (seen as a task) deadLine for execution. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation Reserved space providing schema extendibility. Content model for the entity FUNCTION. Reserved space providing schema extendibility. Content model for the entity GATEWAY. Platform-specific extensions are not allowed, to maintain the capability to describe multi-platform networks. Reserved space providing schema extendibility. Content model for the entity PDU-INSTANCE. Reserved space providing schema extendibility. A frames unique id on a channel. The usage depends on the communication system. E.g. on a CAN or LIN cluster this parameter represents the CAN (resp. LIN) ID in the frames header section. On a FlexRay channel this parameter represents the frames (optional) messageId in the leading word of the frames data part. SIGNALs within a referenced PDU All signals within the PDU are selected Selected signal Selected SIGNALs within the referenced PDU Single SIGNAL within the referenced PDU Content model for the entity MULTIPLEXER. A flag indicating whether the multiplexer is used for extended addressing. Content model for the entities STATIC-PART and DYNAMIC-PART Reserved space providing schema extendibility. Base content model for all ELEMENTS Extension point for the network management schemata. Collection of ordered signals An ordered signal. A signals order may either be given by the signals index in the referencing collection or explicitly with certain LAYOUT-DETAILS. Content model for the entity PDU-INSTANCE. Indication to the receivers that the corresponding PDU was updated by the sender. This attribute describes the position of the update bit in the frame that aggregates this PDU-INSTANCE-TYPE. In context of IS-HIGH-LOW-BYTE-ORDER, BIT-COUNTING-POLICY and IS-HIGH-LOW-BIT-ORDER of this PDU-INSTANCE. A frames layout as a sequence of PDUs A PDU's location in a PDU Content model for the entity PDU-REQUIREMENT List of PDUs belonging to this Requirement Time behavior of a PDU specified in a sequence of cluster specific timing types Specification of a cyclic sending behaviour, e.g. used on CAN clusters Specification of a event driven sending behaviour, e.g. used on CAN clusters Specification of a request driven sending behaviour, e.g. used on CAN clusters Content model for the entity PDU-TRIGGERING. Refering a frame Content model for the entity PDU. The used length (in bytes) of the referencing PDU. Two reserved spaces in a PDU, on one hand used to transport varying signals at the same position, on the other hand used to encode what variation is currently transported All ports affected by this requirement. Refering a functional input. Refering a port (functional input or output or an ECUs input port). Refering a functional output port. Refering a port (functional input or output or an ECUs input port). Refering an ECUs input port. Refering a port (functional input or output or an ECUs input port). Content model for the entity PORT-REQUIREMENT The upper bound on the refresh period of the signal in the referenced port. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation The required cycle period of the signal in the referenced port. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation. The required cycle offset from the applications start up of the signal in the referenced port. See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#duration for syntax explanation Indicating the number of redundant transmissions for one signal Reserved space providing schema extendibility. Data needed to process data in elements. Describing a product or specification of the referenced company. The product id. Especially used for a LIN slaves company specific (function-) id and a LIN frames company specific frame id. The id has to be unique inside of each company. The product variant. Especially used to identify a LIN slaves variant. Content model for the entity PROJECT. Platform-specific extensions are not possible, to maintain the capability to describe multi-platform networks. Containing document management information Collecting the companies involved in project Replenishing the companies involved in FIBEX project. Reserved space providing schema extendibility. Root of all higher level protocol elements Top level element for all used network management configurations Configuration of the network management protocol Top level element for all used transport layers Configuration of a transport layer protocol Content model for the entity TIMING in the relatively scheduled peculiarity. Identifier of the schedule table containing the frame described by the referencing timing on the triggering channel Relative position of the frame described by this timing in the schedule table Relative delay of the frame described by this timing to its predescessor in the schedule table Reserved space providing schema extendibility. Content model for the entity TIMING in the request controlled peculiarity. Specification of the time that is needed before the frame can be sent after the requests arrival Condition that must be fulfiled by the system that a request will be registrated Number of repetitions the frame is sent for a single request Reserved space providing schema extendibility. Root of all requirements Top level element of port-specific requirements on the frequency and quality of signals Port-specific requirement on the frequency and quality of a signal Top level element of requirements on the activity of functions (seen as tasks) Requirement on the activity of a function (seen as a task) Top level element of all signal groups The referenced signals must always be kept together in a common frame. In a LIN cluster signal groups are used to rebind a signal that had to be split in parts of at most 16 bits. Top level element of PDU-specific requirements on the frequency and quality of signals PDU-specific requirement on the frequency and quality of a signal Base content model for all ELEMENTS Containing an elements change history Describing an elements state Refering a product. Especially used to determine a LIN-slaves or frames company specific id. Fragment positions of the enclosing multiplexer part (PDU) Position and length of a fragment of the PDU Content model for the entity SIGNAL-GROUP Reserved space providing schema extendibility. Content model for the entity SIGNAL-INSTANCE Indicates to the receivers that the signal was updated by the sender. This attribute describes the position of the update bit within the PDU. In context of IS-HIGH-LOW-BYTE-ORDER, BIT-COUNTING-POLICY and IS-HIGH-LOW-BIT-ORDER of this SIGNAL-INSTANCE. Reserved space providing schema extendibility. A PDUs layout as a sequence of Signal-Instances A signals location in a PDU Refering a signal Refering a signal Signal state that must rule that the referencing timing is executed. To enable the description of combined tirggers the occurence of SIGNAL-TRIGGER as well as of SIGNAL-STATE combined with SIGNAL-INSTANCE-REF is unbounded. Use one trigger with many states, if these states must rule simultaneously (AND related) for execution. Use a separate trigger for each state if only one state needs to rule for execution. Signal state that must rule that the referencing timing is started or stoped. Content model for the entity SIGNAL. A signals encoded value (internal) indicating that the actual value is currently not published / not of interest Refering a signal coding Category of the signal A positive integer indicating the signals priority. 1 means highest priority. Reserved space providing schema extendibility. General category (type) of a SIGNAL Method used to calculate the content of the signal (e.g. CRC16 for TYPE=CHECKSUM) Additional values for METHOD used for the calculation as key-value pairs Additional value for METHOD used for the calculation (e.g. starting value (denominator) for TYPE=CHECKSUM) Static part of the multiplexer. This part is independent of the switch value A PDU's location in the Multiplexer Reserved space in a PDU, used to encode what variation of signals is currently transported at the position given by the corresponding dynamic part Reserved space providing schema extendibility. List of all possible PDUs Single PDU which is transmitted with the given value of the switch A switchs value implying a variation of signals that is in a PDU System state that must rule that the referencing timing is executed. To enable the description of combined states the occurence of SYSTEM-TRIGGER as well as of SYSTEM-STATE is unbounded. Use one trigger with many states, if these states must rule simultaneously (AND related) for execution. Use a separate trigger for each state if only one state needs to rule for execution. System state that must rule that the referencing timing is started or stoped. For reusability time ranges content model is specified using a type definition. Average value of a date Maximum allowable deviation Minimum allowable value Maximum allowable value tbd Extension point for the transport layer schemata. Transport Layer Addresses A signal's/PDU's bit position relatively to the beginning of the containing element (i.e., PDU/FRAME/SIGNAL-GROUP) The integer value of a freely defined data byte. Refering a channel Refering a composite. Refering a connector Refering a controller Refering a cluster Refering an ECU Describing the exported extent of elements from the referenced project in this file Root element The project/vehicle described in the referencing file To identify the schemas version that should be applied on the referencing file. Note that this value is fixed on the current schema version to avoid confusion checking old FIBEX instances against a new FIBEX schema or oposite. Refering a frame Refering a frameTriggering Refering a function To describe a frames identifier on the communication system, usualy with a fixed identifierValue. Manufacturers may mark up here alternative identification strategies instead of exporting a fixed identifier value Refering a PDU Refering a PDU-Triggering Version specifier for a electrical physical layer Version specifier for a communication protocol Refering a signal instance Refering a TP address An ECU relevant diagnostic address of the type given as attribute. Common attributes to describe a certain data section in a frame Indicates whether the significance of the bytes (in a signal) is decreasing or increasing with the time. A signal with a decreasing byte order (value=true) is usually called a Big endian, a signal with a increasing byte order (value=false) a Little endian. A signals ordered position relatively to the beginning of the containing element (i.e., PDU/FRAME/SIGNAL-GROUP) This type provides all agreed active conditions (for a trigger) as an enumeration. Two counting policies have been established. We will call them monotone and sawtooth counting. While monotone counting is strictly geared to the time axis, sawtooth counting inside of a byte is in diametrical opposition to the time. The bits of all frames on this cluster are counted in this way. For platform specific restrictability a composition level is specified using a type definition. For platform specific restrictability a cycle counter is specified using a type definition. For platform specific restrictability a cycle repetition is specified using a type definition. Content model for the entity DIRECTION Base type for ECU-SENDING-BEHAVIOR-TYPE (XML schema does not allow a restriction with enumerations together with extension for an attribute) This type provides all agreed signal triggers as an enumeration. This type provides all agreed start or stop or send conditions (for a trigger) as an enumeration. To distinguish application frames from certain services Describing how the signal should/can be generated. For platform specific restrictability the number of cycles is specified using a type definition. To distinguish application data from certain services For platform specific restrictability a physical layer is specified using a type definition. For platform specific restrictability a composition level is specified using a type definition. For platform specific restrictability a protocol is specified using a type definition. For platform specific restrictability a composition level is specified using a type definition. For platform specific restrictability a slot id is specified using a type definition. A channels speed in bits per second For platform specific restrictability a transceiver is specified using a type definition. General purpose of the signal