hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.7.1 Total signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean downstream signal power into a resistive load of 100 Ω shall not exceed a level of +19,9 dBm, measured within a frequency... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.7.2 Total signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean upstream signal power into a resistive load of 100 Ω shall not exceed a level of +13,3 dBm, measured within a frequency b... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.7.3 Peak amplitude (upstream and downstream) | The description of this signal characteristic equals that of "ADSL2plus/A (FO)". |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.7.4 Narrow-band signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R, shall not exceed the limits given in table 85, at any point... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.7.5 Narrow-band signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R, shall not exceed the limits given in table 86, at any point... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.7.6 Unbalance about earth (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the balance of the signal that may flow through the LT-port or NT-port shall exceed minimum requirements, under the condition that the local loop wiring and its termination i... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8 "ADSL2plus/B (FDD)" signals (over ISDN) | This category covers signals, generated by ADSL2plus transmission equipment which uses Frequency Division Duplexing (FDD) to separate upstream and downstream. In this mode, the usable frequency band of downstream signals is narrower to limit the overlap with the upstream to four DMT tones. This is to minimize self-NEXT... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8.1 Total signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean downstream signal power into a resistive load of 100 Ω shall not exceed a level of +19,3 dBm, measured within a frequency... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8.2 Total signal power (upstream only) | The description of this signal characteristic equals that of "ADSL2plus/B (FO)". |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8.3 Peak amplitude (upstream and downstream) | The description of this signal characteristic equals that of "ADSL2plus/B (FO)". ETSI ETSI TR 101 830-1 V1.5.2 (2009-05) 99 |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8.4 Narrow-band signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R, shall not exceed the limits given in table 89, at any point... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8.5 Narrow-band signal power (upstream only) | The description of this signal characteristic equals that of "ADSL2plus/B (FO)". |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.8.6 Unbalance about earth (upstream and downstream) | The description of this signal characteristic equals that of "ADSL2plus/B (FO)". |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9 "ADSL2plus/I (FO)" signals (all digital mode) | This category covers signals, generated by ADSL2plus transmission equipment, for which the downstream spectrum overlaps the upstream spectrum (Frequency Overlap). These signals do not share the same wire pair with POTS or ISDN signals. This clause is based on ITU-T Recommendation G.992.5 [i.12]. A signal can be classif... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9.1 Total signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean downstream signal power into a resistive load of 100 Ω shall not exceed a level of +20,4 dBm, measured within a frequency... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9.2 Total signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean upstream signal power into a resistive load of 100 Ω shall not exceed a level of +13,3 dBm, measured within a frequency b... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9.3 Peak amplitude (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the nominal voltage peak of the largest signal pulse into a resistive load of 100 Ω shall not exceed a level of 19V (38 V peak-peak), measured within a frequency band from at... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9.4 Narrow-band signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R, shall not exceed the limits given in table 90, at any point... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9.5 Narrow-band signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R, shall not exceed the limits given in table 91, at any point... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 11.9.6 Unbalance about earth (upstream and downstream) | The description of this signal characteristic equals that of "ADSL2plus/A (FO)". 11.10 "ADSL2plus/I (FDD)" signals (all digital mode) This category covers signals, generated by ADSL2plus transmission equipment, which uses Frequency Division Duplexing (FDD) to separate upstream and downstream. In this mode, the usable f... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12 Cluster 5 signals (broadband up to 30 MHz) | |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1 "VDSL2-NL1" signals ("over POTS") | This category covers signals up to 12 MHz, generated by VDSL2 transmission equipment using band plan 998 (limit PSD mask B8-4). These signals may share the same wire pair with POTS signals. This signal description is derived from the ITU VDSL2 recommendation [i.14] and accounts for Power Back-Off in both downstream (DP... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1.1 Total signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean downstream signal power into a resistive load of 100 Ω shall not exceed the levels given in table 94, measured within a f... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1.2 Total signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean upstream signal power into a resistive load of 100 Ω shall not exceed a level of +14,5 dBm, measured within a frequency b... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1.3 Peak amplitude (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the nominal voltage peak of the largest signal pulse into a resistive load of 100 Ω shall not exceed a level of 19V (38 V peak-peak), measured within a frequency band from at... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1.4 Narrow-band signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R for a given attenuation distance, shall not exceed the limit... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1.5 Narrow-band signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the upstream signal shall comply simultaneously with transmit limits, dedicated to the upstream transmit signal observed at the NT... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.1.6 Unbalance about earth (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the balance of the signal that may flow through the LT-port or NT-port shall exceed minimum requirements, under the condition that... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2 "VDSL2-NL2" signals (over ISDN) | This category covers signals up to 12 MHz, generated by VDSL2 transmission equipment using band plan 998 (limit PSD mask B8-6). These signals may share the same wire pair with ISDN signals. This signal description is derived from the ITU VDSL2 recommendation [i.14] and accounts for Power Back-Off in both downstream (DP... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2.1 Total signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the mean downstream signal power into a resistive load of 100 Ω shall not exceed the levels given in table 101, measured within a frequency band from at least 4 kHz to 30 MHz... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2.2 Total signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean upstream signal power into a resistive load of 100 Ω shall not exceed a level of +14,5 dBm, measured within a frequency b... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2.3 Peak amplitude (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the nominal voltage peak of the largest signal pulse into a resistive load of 100 Ω shall not exceed a level of 19V (38 V peak-peak), measured within a frequency band from at... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2.4 Narrow-band signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R for a given IL-value, shall not exceed the limits given in t... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2.5 Narrow-band signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the upstream signal shall comply simultaneously with transmit limits, dedicated to the upstream transmit signal observed at the NT... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.2.6 Unbalance about earth (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the balance of the signal that may flow through the LT-port or NT-port shall exceed minimum requirements, under the condition that the local loop wiring and its termination i... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3 "VDSL2-UK1" signals | This category covers signals up to 7,05 MHz, generated by VDSL2 transmission equipment using band plan 997 (limit PSD mask B7-1). These signals may share the same wire pair with POTS signals. This signal description is derived from the ITU VDSL2 recommendation G.993.2 [i.14]. The downstream signal is enhanced by loop d... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3.1 Total signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean downstream signal power into a resistive load of 100 Ω shall not exceed +11,5 dBm. Reference: ITU-T Recommendation G.993.... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3.2 Total signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved and indicates the relevant specification(s): To be compliant with this signal category, the mean upstream signal power into a resistive load of 100 Ω shall not exceed a level of +14,5 dBm, measured within the frequency... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3.3 Peak amplitude (upstream and downstream) | No limit is specified. NOTE: Peak amplitude is constrained by safety and DC power dissipation considerations. |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3.4 Narrow-band signal power (downstream only) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R for a given DBBOESEL-value, shall not exceed the limits given in tables 105 and 106, at any point in the... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3.5 Narrow-band signal power (upstream only) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the Narrow-Band Signal Power (NBSP) into a resistive load impedance R for a given UPBO-value, shall not exceed the limits given in tables 107 and 108, at any point in the fre... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 12.3.6 Unbalance about earth (upstream and downstream) | The present document provides information on how compliance with this signal category can be achieved: To be compliant with this signal category, the unbalance about earth shall not exceed the associated limits specified for "VDSL2-NL1" signals. |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13 Measurement methods of signal parameters | |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13.1 Peak amplitude | The present document provides information on the peak amplitude: The peak amplitude is defined as the peak voltage amplitude measured in a continuous sending signal such that the probability of exceeding that amplitude is less than 10-7. It shall be measured into a resistive load R, and over a period of not less than 1... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13.2 Narrow-band signal power (voltage) | The narrow band signal power is defined as the average power P of a sending signal into a resistive load R, within a power bandwidth B centred at a specified frequency. The power bandwidth is different from the commonly used -3 dB bandwidth, since it fully accounts for the shape of the transfer function H(f) of frequen... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13.3 Unbalance about earth | The present document provides information on dealing with unbalance about earth and indicates relevant specification(s): Poor balance of a signal source, connected to a local loop wiring, leads to conditions in the network where systems using the same cable could be harmed. If the combination of system and wire pair sh... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13.3.1 Definition of earth | Measurements of both LOV and LCL must be considered as 3 terminal measurements. These terminals are the conductors of a port to the Local Loop Wiring or to a signal source (ESS, CSS or RSS). Two terminals are those of the differential mode and the third terminal is that of the earth used of the common mode. • In the ca... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13.3.2 Transmitter Balance - LOV | The balance of transmitters is normally expressed in the "Longitudinal Output Voltage" (LOV). This is the common mode portion of the generated signal, and specified for many transmission systems defined by ETSI TM6 (e.g. see [i.6] and [i.7]). The longitudinal output voltage is the longitudinal component of the output s... |
32347bacbd44eee2fd8cd2c5065911f1 | 101 830-1 | 13.3.3 Receiver balance - LCL | The balance of receivers is normally expressed in the "Longitudinal Conversion Loss" (LCL). The definition of the LCL can be found in [i.15]. Additionally, LCL is specified for all transmission systems defined by ETSI TM6 (e.g. see [i.6] and [i.7]). The Longitudinal Conversion Loss (LCL) is given by: LCL = 20 log (el/e... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 1 Scope | The present document defines the Message Sequence Chart (MSC) presentation format for the TTCN-3 core language as defined in ES 201 873-1 [1]. This presentation format uses a subset of Message Sequence Charts as defined in [3] with test specific extensions and extensions of general nature. The present document is based... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [2] ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test C... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BNF Backus-Naur Form CATG Computer Aided Test Generation ETSI European Telecommunication Standards Institute GFT Graphical Format of TTCN-3 MSC Message Sequence Chart MTC Main Test Component PTC Parallel Test Component SUT System Under Test TF... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 4 Overview | According to the OSI conformance testing methodology defined in ISO/IEC 9646-3 [4], testing normally starts with the identification of test purposes. A test purpose is defined as: "A prose description of a well-defined objective of testing, focusing on a single conformance requirement or a set of related conformance re... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 5 GFT language concepts | GFT represents graphically the behavioural aspects of TTCN-3 like the behaviour of a test case or a function. It does not provide graphics for data aspects like declaration of types and templates. GFT defines no graphical representation for the structure of a TTCN-3 module, but specifies the requirements for such a gra... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 6 Mapping between GFT and TTCN-3 Core Notation | GFT provides graphical means for TTCN-3 behaviour definitions. The control part and each function, altstep and test case of a TTCN-3 core notation module can be mapped onto a corresponding GFT diagram and vice versa. This means: • The module control part can be mapped onto a control diagram (see clause 9.2) and vice ve... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 7 Module structure | As shown in figure 6, a TTCN-3 module has a tree structure. A TTCN-3 module is structured into a module definitions part and a module control part. The module definitions part consists of definitions and declarations that may be structured further by means of groups. The module control part cannot be structured into su... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 8 GFT symbols | This clause presents all graphical symbols used within GFT diagrams and comments their typical usage within GFT. GFT Element Symbol Description Frame symbol Used to frame GFT diagrams Reference symbol Used to represent the invocation of functions and altsteps ETSI ETSI TR 101 873-3 V1.2.1 (2002-05) 16 GFT Element Symbo... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9 GFT diagrams | GFT provides the following diagram types: 1) Control diagram for the graphical presentation of a TTCN-3 module control part; 2) Test case diagram for the graphical presentation of a TTCN-3 test case; 3) Altstep diagram for the graphical presentation of a TTCN-3 altstep; and 4) Function diagram for the graphical present... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.1 Common properties | Common properties of GFT diagrams are related to the diagram area, diagram heading and paging. |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.1.1 Diagram area | Each GFT control, test case, altstep and function diagram shall have a frame symbol (also called diagram frame) to define the diagram area. All symbols and text needed to define a complete and syntactically correct GFT diagram shall be made inside the diagram area. NOTE: GFT has no language constructs like the MSC gate... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.1.2 Diagram heading | Each GFT diagram shall have a diagram heading. The diagram heading shall be placed in the upper left-hand corner of the diagram frame. The diagram heading shall uniquely identify each GFT diagram type. The general rule to achieve this is to construct the heading from the keywords testcase, altstep or function followed ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.1.3 Paging | GFT diagrams may be organized in pages and a large GFT diagram may be split into several pages. Each page of a split diagram shall have a numbering in the upper right hand corner that identifies the page uniquely. The numbering is optional if the diagram is not split. NOTE 1: The concrete numbering scheme is considered... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.2 Control diagram | A GFT control diagram provides a graphical presentation of the control part of a TTCN-3 module. The heading of a control diagram shall be the keyword module followed by the module name. A GFT control diagram shall only include one component instance (also called control instance) with the instance name control without ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.3 Test case diagram | A GFT test case diagram provides a graphical presentation of a TTCN-3 test case. The heading of a test case diagram shall be the keyword testcase followed by the complete signature of the test case. Complete means that at least test case name and parameter list shall be present. The runs on clause is mandatory and the ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.4 Function diagram | GFT presents TTCN-3 functions by means of function diagrams. The heading of a function diagram shall be the keyword function followed by the complete signature of the function. Complete means that at least function name and parameter list shall be present. The return clause and the runs on clause are optional in the co... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 9.5 Altstep diagram | GFT presents TTCN-3 altsteps by means of altstep diagrams. The heading of an altstep diagram shall be the keyword altstep followed by the complete signature of the altstep. Complete means that at least altstep name and parameter list shall be present. The runs on clause is optional in the core notation. If the runs on ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 10 Instances in GFT diagrams | GFT diagrams include the following kinds of instances: • control instances describing the flow of control for the module control part; • test component instances describing the flow of control for the test component that executes a test case, function or altstep; • port instances representing the ports used by the diff... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 10.1 Control instance | Only one control instance shall exist within a GFT control diagram (see clause 9.2). A control instance describes the flow of control of a module control part. A GFT control instance shall graphically be described by a component instance symbol with the mandatory name control placed on top of the instance head symbol. ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 10.2 Test component instances | Each GFT test case, function or altstep diagram includes one test component instance that describes the flow of control of that instance. A GFT test component instance shall graphically be described by an instance symbol with: • the mandatory name mtc placed on top of the instance head symbol in the case of a test case... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11 Elements of GFT diagrams | This clause defines general drawing rules for the representation of specific TTCN3 syntax elements (semicolons, comments). It describes how to display the execution of GFT diagrams and the graphical symbols associated with TTCN3 language elements. |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.1 General drawing rules | General drawing rules in GFT are related to the usage of semicolons, TTCN-3 statements in action symbols and comments. |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.1.1 Usage of semicolons | All GFT symbols with the exception of the action symbol shall include only one statement in TTCN-3 core notation. Only an action symbol may include a sequence of TTCN-3 statements (see clause 11.1.2). The semicolon is optional if a GFT symbol includes only one statement in TTCN-3 core notation (see figures 14-a and 14-... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.1.2 Usage of action symbols | The following TTCN-3 declarations, statements and operations are specified within action symbols: declarations (with the restrictions defined in clause 11.3), assignments, log, connect, disconnect, map, unmap and action. A sequence of declarations, statements and operations that shall be specified within action symbols... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.1.3 Comments | GFT provide three possibilities to put comments into GFT diagrams: • Comments may be put into GFT symbols following the symbol inscription and using the syntax for comments of the TTCN-3 core notation (figure 14-d). • Comments in the syntax for comments of the TTCN-3 core notation can be put into text symbols and freel... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.2 Invoking GFT diagrams | This clause describes how the individual kinds of GFT diagrams are invoked. Since there is no statement for executing the control part in TTCN-3 (as it is comparable to executing a program via main and out of the scope of TTCN-3), the clause discusses the execution of test cases, functions, and altsteps. |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.2.1 Execution of test cases | The execution of test cases is represented by use of the execute test case symbol (see figure 15). The syntax of the execute statement is placed within that symbol. The symbol may contain: • an execute statement for a test case with optional parameters and time supervision, • optionally, the assignment of the returned ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.2.2 Invocation of functions | The invocation of functions is represented by the reference symbol (figure 16), except of external and predefined functions (figure 17) and except where a function is called inside a TTCN3 language element that has a GFT representation (figure 18). The syntax of the function invocation is placed within the reference sy... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.2.3 Invocation of altsteps | The invocation of altsteps is represented by use of the reference symbol (see figure 19). The syntax of the altstep invocation is placed within that symbol. The symbol may contain the invocation of an altstep with optional parameters. It shall be used within alternative behaviour only, where the altstep invocation shal... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.3 Declarations | TTCN-3 allows the declaration and initialization of timers, constants and variables at the beginning of statement blocks. GFT uses the syntax of the TTCN-3 core notation for declarations in several symbols. The type of a symbol depends on the specification of the initialization, e.g. a variable of type default that is ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.3.1 Declaration of timers, constants and variables in action symbols | The following declarations shall be made within action symbols: • timer declarations; • declarations of variables without initialization; • declarations of variables and constants with initialization: - if the initialization is not made by means of functions that include communication functions; or - if a declaration i... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.3.3 Declaration of constants and variables within create symbols | Constants and variable declarations of a component type that are initialized by means of create operations shall be made within a create symbols. In contrast to declarations within action symbols, each declaration that is initialized by means of a create operation shall be presented in a separate create symbol. An exam... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.3.4 Declaration of constants and variables within default symbols | Constants and variable declarations of type default that are initialized by means of activate operations shall be made within a default symbol. In contrast to declarations within action symbols, each declaration that is initialized by means of an activate operation shall be presented in a separate default symbol. An ex... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.3.5 Declaration of constants and variables within reference symbols | Constants and variable declarations that are initialized by means of a function that includes communication operations shall be made within reference symbols. In contrast to declarations within action symbols, each declaration that is initialized by means of a function that includes communication functions shall be pre... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4 Basic program statements | Basic program statements are expressions, assignments, operations, loop constructs etc. All basic program statements can be used within GFT diagrams for the control part, test cases, functions and altsteps. GFT does not provide any graphical representation for expressions and assignments. They are textually denoted at ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.1 The Log statement | The log statement shall be represented within an action symbol (see figure 21). Log(“Message x sent log(“Message x sent to MyPort”) log("Message x sent to MyPort"); GFT Core Figure 21: Log statement |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.2 The Label statement | The label statement shall be represented with a label symbol, which is connected to a component instance. Figure 22 illustrates a simple example of a label named MyLabel. MyLabel MyLabel label MyLabel; GFT Core Figure 22: Label statement |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.3 The Goto statement | The goto statement shall be represented with a goto symbol. It shall be placed at the end of a component instance or at the end of an operand in an inline expression symbol. Figure 23 illustrates a simple example of a goto. MyLabel MyLabel goto MyLabel; GFT Core Figure 23: Goto statement |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.4 The If-else statement | The if-else statement shall be represented by an in-line expression symbol labelled with the if keyword and a Boolean expression. The if-else in-line expression symbol may contain one or two operands, separated by a dashed line. Figure 24 illustrates an if statement with a single operand, which is executed when the Boo... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.5 The For statement | The for statement shall be represented by an in-line expression symbol labelled with a for definition as defined in ES 201 873-1 [1], clause 19.7. The for body shall be represented as the operand of the for inline expression symbol. Figure 26 represents a simple for loop in which the loop variable is declared and initi... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.6 The While statement | The while symbol shall be represented by an in-line expression symbol labelled with a while definition as defined in ES 201 873-1 [1], clause 19.8. The while body shall be represented as the operand of the while inline expression symbol. Figure 27 represents an example of a while statement. Template1 while(j<10) MyPort... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.4.7 The Do-while statement | The do-while statement shall be represented by an in-line expression symbol labelled with a do-while definition as defined in ES 201 873-1 [1], clause 19.9. The do-while body shall be represented as the operand of the do-while inline expression symbol. Figure 28 represents an example of a do-while statement. Template1 ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5 Behavioural Program Statements | Behavioural statements may be used within test cases, functions and altsteps, the only exception being the return statement, which can only be used within functions. Test behaviour can be expressed sequentially, as a set of alternatives or using an interleaving statement. Return and repeat are used to control the flow ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.1 Sequential behaviour | Sequential behaviour is represented by the order of events placed upon a test component instance. The ordering of events is taken in a top-down manner, with events placed nearest the top of the component instance symbol being evaluated first. Figure 29 illustrates a simple case in which the test component firstly evalu... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.2 Alternative Behaviour | Alternative behaviour shall be represented using in-line expression symbol with the alt keyword placed in the top left hand corner. Each operand of the alternative behaviour shall be separated using a dashed line. Operands are evaluated top-down. Note that an alternative in-line expression should always cover all port ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.2.1 Selecting/Deselecting an Alternative | It is possible to disable/enable an alternative operand by means of a Boolean expression contained within a condition symbol placed upon the test component instance. Figure 33 illustrates a simple alternative statement in which the first operand is guarded with the expression x>1, and the second with the expression x<=... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.2.2 Else branch in alternatives | The else branch shall be denoted using a condition symbol placed upon the test component instance axis labelled with the else keyword. Figure 34 illustrates a simple alternative statement where the second operand represents an else branch. Template1 alt x>1 else MyErrorHandler() Template1 alt x>1 else MyErrorHandler() ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.3 The Repeat statement | The repeat statement shall be represented by a repeat symbol. This symbol shall only be used as last event of an alternative operand in an alt statement or as last event of an operand of the top alternative in an altstep definition. Figure 35 illustrates an alternative statement in which the second operand, having succ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.4 Interleaved Behaviour | Interleave behaviour shall be represented using an in-line expression symbol with the interleave keyword placed in the top left hand corner (see figure 36). Each operand shall be separated using a dashed line. Operands are evaluated in a top-down order. Template1 Template2 interleave Template1 Template2 interleave MyPo... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.5.5 The Return statement | The return statement shall be represented by a return symbol. This may be optionally associated with a return value. A return symbol shall only be used in a GFT function diagram. It shall only be used as last event of a component instance or as last event of an operand in an inline expression symbol. Figure 37 illustra... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.6 Default handling | GFT provides graphical representation for the activation and deactivation of defaults - ES 201 873-1 [1], clause 21. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.