hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.4 Presence of PE Wire in the US | Following figures (table 9) on housing building permits in the US was found on the web. ETSI ETSI TR 101 562-1 V1.3.1 (2012-02) 26 Table 9: New Houses in the US According to the Census Bureau (source http://www.census.gov) Furthermore: • In 2011, there were 130 M households in total, in the US [i.8] • NEC (National Ele... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5 Presence of PE Wire in Spain | |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.1 Electrical Regulations Data for Spain | The low voltage installations in Spain are regulated by the "Reglamento Electrotécnico para Baja Tensión" (RBT) (Low Voltage Electrotechnical Regulation). The regulation of internal electrical installations (see note 1) was published on 5th July 1933. This regulation was in effect until 1955 and no further investigatio... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.2 Spanish Housing Data | The following data has been obtained from the Bank of Spain (www.bde.es) (see note), the Statistics National Institute of Spain (www.ine.es) and the Ministry of Housing of Spain (www.mviv.es). 16 165 923 houses were constructed in the time frame from January 1971 until December 2009. The total number of houses in Spain... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.3 New Housing built in Spain Since 1974 | Using the reference data of the annual increase of new houses, we have determined the number of houses constructed from January 1974 until December 2009 to be 14 553 529. The total number of houses at the end of 2009 was 26 768 715. We can conclude from these figures that the percentage of houses with a PE installation... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.4 Data on Housing Renovations | The data obtained regarding housing renewal and renovation (see note) is more difficult to interpret because the source does not specify whether the electrical wiring was included in the renovation or if the premise already had a PE installation. NOTE: Data about renewal (housings and buildings) was taken from the stat... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.5 Summary Figures: Housing, Renewals and PE Installations | Table 9a: Summary of Figures of Housing in Spain Total Residences in Spain (Dec.'09) = 26 768 715 Total Residences without PE = 12 215 186 Total Residences with PE = 14 553 529 Total Renewals (Residence + Building) = 485 106 For the analysis of the presence of the PE wire in Spain we will use different approaches and w... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.6 Variation in the Rate of PE Installations in Renovated Housing | Due to the unspecific data available regarding electrical wiring modifications and PE installations in renovated or renewed homes, we have compiled table 9b to demonstrate the shift in total PE wired housing in Spain for different rates of electrical renewal. On the left can be viewed a hypothetical rate of electrical ... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.3.4.5.7 Conclusion: Electrical Installation Practices in Spain | Based on the assumptions detailed above and in light of the data obtained, we estimate the percentage of housing in Spain with PE installations to be 54-56 %. |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.4 Secondary Information for Estimating the Presence of PE | Several marketing institutes and customer research institutes were contacted in regards to: • Sales numbers of RCD • Sales volume of NYM-J/NYM-O - PVC Installation Cables - Share of 3 and 5 wire cables Unfortunately no useful information was found here. Public reports were not available and manufacturers of such equipm... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 6.5.1 Information Collection Methodology | A survey was conducted in order to collect information regarding the grounding situation in each country. The following methodology was used: • Find information regarding the Socket types in use for each country ETSI ETSI TR 101 562-1 V1.3.1 (2012-02) 31 • Cross-check and verify the above data with socket manufacturer'... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1 MIMO PLT Universal Coupler | Figure 18: Photograph of Coupler from Top Figure 19: Photograph of Coupler, Case Opened Figure 18 and figure 19 show photographs of the STF410 coupler from top and with opened case. |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.1 Safety Note | • STF 410 MIMO couplers are designed and built with great care. • STF 410 couplers have to be used exclusively for tests carried out by instructed personnel. • It is recognized that the connection of the Protective Earth of the STF 410 MIMO couplers does not comply with safety standards for commercial products. • For b... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.2 Objectives of the MIMO PLT (STF 410) Design | General Requirements: • Safety for field use by instructed personnel (but no formal safety test). • Safety for connected test equipment (50 Hz level, surge protection). • Well defined electrical characteristics to get reproducible measurement results (namely well defined impedance matching conditions for sender and rec... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.3 Technical Data of Couplers | |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.3.1 Impedance Conditions | Impedance conditions are defined at the center point C (see schematic diagram clause 7.1.6). P E N EP NE PN CM Differential mode impedance example N-E mains slide switch lever position Differential mode (Delta) inputs: via baluns 50 Ω to 200 Ω (measured impedance to be multiplied by 4) Figure 20: Coupler in Impedance M... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.3.2 Insertion Loss | See measurement results in clause 7.1.6. |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.4 Operation | The following figures show the connections to MIMO sender and receiver and the position of the slide switches for the different operation modes. |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.4.1 SISO Transmit and SISO Receive (Example P-N to P-N) | The setup to connect two couplers in SISO mode is shown below. ETSI ETSI TR 101 562-1 V1.3.1 (2012-02) 54 SISO PN P E N P E N EP NE PN IN OUT PN EP NE CM CM slide switch lever position channel SISO transmit / receive P-N Figure 22: Coupler in SISO Attenuation Measurement Mode |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.4.2 MIMO Symmetric Transmit (Example N-E), MIMO Receive Star Plus CM | Figure 23 shows the setup to connect two couplers in a MIMO example mode. MIMO sym transmit N-E P E N P E N EP NE PN Sender PN EP NE CM CM 50 50 channel Receiver slide switch lever position Figure 23: Coupler in MIMO Symmetric Transmit and MIMO Receive (Star Plus CM) Mode |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.4.3 MIMO Asymmetric Transmit (Example N-E), MIMO Receive Star Plus CM | Figure 24 shows the setup to connect two couplers in a MIMO example mode where one port is not terminated. ETSI ETSI TR 101 562-1 V1.3.1 (2012-02) 55 MIMO asym transmit N-E P E N P E N EP NE PN Sender PN EP NE CM CM 50 channel Receiver off slide switch lever position Figure 24: Coupler in MIMO Asymmetric Transmit and M... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.4.4 SISO Common Mode Transmit and SISO Common Mode Receive | Figure 25 shows the setup to connect two couplers in CM-CM mode. (It is not a proposal for practical deployment.) CM transmission P E N P E N EP NE PN Sender PN EP NE CM CM channel Receiver 50 50 50 50 50 50 slide switch lever position Figure 25: Coupler in SISO Common Mode Transmit and Receive Mode ETSI ETSI TR 101 56... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.4.5 Alternative MIMO Mode Using Dual Wire Feed | Figure 26: Coupler in Dual Wire Feed Mode Version A: • The short circuit between P and N is not perfect, because the balun represents a transmission line of about 34 cm of electrical length and Zo = 200 Ω at the secondary. At 30 MHz P and N are "shorted" with about j 43 Ω, at 80 MHz with j 115 Ω. Version B: • There is ... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.5 Circuit Diagram | The center point C in the schematic diagram in figure 29 is the heart of the coupler. It is built in a very compact form in order to reduce spurious inductances and capacitances for proper operation in excess of 100 MHz. All baluns are of the same type (Guanella transformers 1 : 4). They are of very low loss. The commo... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.6 Measurement Results of STF410 Coupler Verification | |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.6.1 SISO | Figure 30 shows the coupler's verification setup for SISO. SISO PN P E N P E N EP NE PN IN OUT PN EP NE CM CM 19.2 dB Zo = 80 Ohm Insertion loss with ideal coupler: total: a = 21,0 dB Excess insertion loss per coupler: 3 MHz < 0,4 dB 30 MHz < 0,3 dB 60 MHz < 0,5 dB 80 MHz < 0,7 dB 100 MHz < 2,4 dB Figure 30: Coupler Se... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.6.2 MIMO Symmetric | Figure 31 shows the coupler's verification setup for MIMO. MIMO sym PN 50 50 50 50 P E N P E N EP NE PN IN OUT PN EP NE CM CM 19.2 dB Zo = 80 Ohm Insertion loss with ideal coupler: total: a = 23,3 dB Excess insertion loss per coupler: 3 MHz < 0,9 dB 30 MHz < 0,6 dB 60 MHz < 0,8 dB 80 MHz < 1,2 dB 100 MHz < 2,1 dB Figur... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.6.3 MIMO Delta Transmit to Star Receive | Figure 33 shows the coupler's verification setup for MIMO delta to star mode. DELTA to STAR P P E N P E N EP NE PN IN OUT PN EP NE 50 50 CM CM 19.2 dB Zo = 80 Ohm Insertion loss with ideal coupler: total: a = 23,2 dB Excess insertion loss per coupler: (ex prototypes) 3 MHz < 0,4 dB 30 MHz < 0,3 dB 60 MHz < 0,5 dB 80 MH... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.6.4 Common Mode Reception | Figure 35 shows the coupler's verification setup for CM reception. P E N EP NE PN CM 50 50 50 G 50 Ohm internal 100 Ohm Schuko out Insertion loss with ideal coupler: total: a = 5,3 dB Absorption and mismatch per coupler: (ex prototypes) 3 MHz < 3,3 dB 30 MHz < 3,4 dB 60 MHz < 4,2 dB 80 MHz < 5,2 dB 100 MHz < 5,8 dB Thi... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.1.6.5 Alternative MIMO Modes (Dual Wire Feed) | Figure 37 shows the coupler's verification setup for MIMO using the alternative (T-style) mode. Comparative losses with respect to previous MIMO symmetric injection (point 12.2) in PN-PN mode (coupler/pad - 11 to 12/F): 3 MHz -1,6 dB 30 MHz -1,3 dB 60MHz -0,2 dB 80 MHz +1 dB (see note) 100 MHz +2,1 dB (see note) NOTE: ... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.2 Coaxial Cables | The coaxial cables used to conduct the measurements have to enable results of a dynamic range of up to 120 dB. Therefore doubled shielded cables are required. Of course, due to long distances inside the buildings, low attenuation cables are preferred. RG214 or Ecoflex 10 cables fulfil these requirements. To avoid signa... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.3 Network Analyzer | The following NWA were used by the measurement teams. |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.3.1 Agilent E5071B | The team Germany used an Agilent E5071B. NOTE: Agilent E5071B is an example of a suitable product available commercially. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of this product. Figure 39: Agilent E5071B Table 17: Technical Propertie... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.3.2 Agilent E5071C | The teams Belgium and France, Lannion used an Agilent E5071C ENA Network Analyzer. NOTE: Agilent E5071C is an example of a suitable product available commercially. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of this product. Figure 40: Ag... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.3.3 Rohde & Schwarz ZVB4 | The team in Spain used a Rohde & Schwarz ZVB4 Network Analyzer. NOTE: Rohde & Schwarz ZVB4 is an example of a suitable product available commercially. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of this product. Figure 41: Rohde & Schwarz... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.4 LISN or Filter to Isolate Measurement Devices from Mains | Figure 42: AMN Table 20: Technical Properties of AMN Property Value Comment Type ESH3-Z5 Manufacturer Rohde & Schwarz PE connection 50 μH "on" For isolation of the PE wire, an additional mains filter as described in the following clause should be inserted in series to the LISN. |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.5 Mains Filter | If the test instruments (namely the network analyzer) are connected to the mains section for EMI, channel impedance and transfer measurements, the instruments represent an additional load and may cause measurement errors. Whenever possible the power supply for the measurement equipment should be used from a neighboring... |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.5.1 Schematic Diagram | A mains filter also attenuating the PE wire is shown below. NWA mains CM choke > 10 uH P N PE 22 // 22 uH // 1,2 k 22 // 22 uH // 1,2 k 3 x 10 nF max 6 A P N PE 820 k 820 k Figure 43: Schematic of Mains Filter |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.5.2 Typical Impedances of Decoupling Components | |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.5.2.1 R/L Combinations - Mains Side | Table 21: Impedance R, L Circuit on Mains Side of STF410 Mains Filter MHz 1,59 3 10 30 60 80 100 │Z│ 79 135 450 1 100 650 440 340 Ω φ 58 58 64 - 4 - 50 - 60 - 60 degree |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.5.2.2 Common Mode Choke - Instrument (NWA) Side (4 turns) | Table 22: Impedance of CM Choke in STF410 Mains Filter MHz 1,59 3 10 30 60 80 100 │Z│ 110 240 610 850 580 400 310 Ω φ 89 82 42 - 16 - 51 - 62 - 64 degree |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.5.3 Figures of Mains Filter | Figure 44: Mains Filter with Closed Lid ETSI ETSI TR 101 562-1 V1.3.1 (2012-02) 70 Figure 45: Filter View Inside |
2e77dfacc095d933b70977e146300d8c | 101 562-1 | 7.6 Ground Plane | To achieve a low impedance or high capacity connection to ground, a huge ground plane is necessary. Especially for reproducibility of the received CM signal; the ground plane is essential. The size of the ground plane is sufficiently large when human contact no longer influences measurement results. Figure 46: Ground P... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 1 Scope | The purpose of the present document is to present and describe issues and design choices made while developing a generic test adapter and codec suited for TTCN-3 interoperability testing within both STF370 and STF407. For further information, the reader is referred to EG 202 810 [i.3] for global view of methodology and... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Official BOOST framework reference. NOTE: Available at: http://www.boost.org/doc/libs/1_39_0/libs/libraries.htm. [i.2] ETSI ES 201 873-1 (V3.4.1): "Me... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DNS Domain Name System (protocol) EUT Equipment Under Test GUI Graphical User Interface HTTP Hypertext Transfer Protocol IP Internet Protocol IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network OS Operating System PCAP Packet C... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 4 Overview | The main purpose of the TTCN-3 interoperability test adapter is to implement the real test system interface as described in ES 201 873-1 [i.2], ES 201 873-6 [i.6] and ES 201 873-5 [i.7] of the TTCN-3 IMS interoperability test system described in TR 102 788 [i.4], i.e. the handling and transport of TTCN-3 messages send ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5 Design proposals for receiving of traffic capture | This clause evaluates different design proposals for integrating the TTCN-3 interoperability codec and test adapter with physical traffic capture. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1 Design proposal for the codec | The following design considerations have been captured based on an analysis of the various protocols that need to be supported by the codec and the type definitions provided by TTCN-3 libraries. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 9 |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.1 Principles | The codec should be extensible at low cost. SIP is still evolving and new headers and messages may be added to the protocol. Therefore it is essential to be able to add new types in the codec without having to fully redesign it. The codec should be as generic as possible and the chosen solution should not be operating ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.2 Encoder | The TTCN-3 types in the SIP library provide an abstract representation of the SIP messages. Only the semantic information is represented, and all syntactic elements which do not carry any useful information are not represented. Among them: • linear white space and new lines between the header fields; • delimiters, e.g.... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.3 Decoder | Extra white space is semantically meaningless and can appear in many places inside a SIP message. The codec will have to be able to deal correctly with these white spaces and ignore them when necessary. Additionally, SIP specification allows some header fields to appear multiple times, but with different encoding, i.e.... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4 Discussion | |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.1 Rejected solutions | |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.1.1 External SIP application | One possible solution could be to use an external SIP application to decode and encode SIP messages. For this approach it is necessary to develop a non-standardized interface with this application. In addition, it would make the codec and thus the complete test environment dependent on that external application. This s... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.1.2 Wireshark | A second alternative would be to use a network protocol analyzer such as Wireshark and use its dissector library to decode SIP messages. This approach brings sensibly the same problems as the previous one: • Possible bugs in external tool. • Extensibility and maintenance dependent on external application. In addition, ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.1.3 Yacc parser | Another approach would be to use a parser generator such as Yacc. A parser typically receives a sequence of tokens from a lexer and tries to derive the unique sequence of grammar rules that can produce that token sequence. It would be then possible to create a parser in order to decode SIP messages. However, parsers us... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.2 Selected solution: T3DEVKIT | T3DevKit [i.5] is a project developed by IRISA which aims to provide tools and libraries to help developing TTCN-3 codecs and adapters. It is composed of two main elements: T3DevLib, a library of C++ classes that handle generic codec & Adapter functionalities, and T3CDGen, a tool that can generate a codec implementatio... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.2.1 Encoder | The encoder mainly appends the syntactic element that do not appear explicitly in the TTCN-3 message (but that can be derived from the structure of the message). This is done by writing the delimiter in question in the buffer before and/or after the adequate field. Encoding of the "Content-Length" field of the SIP mess... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.1.4.2.2 Decoder | Implementing the decoder mostly consists of: • validating the format of the message; • skipping the syntactic elements that are not represented in the TTCN-3 structure; • make predictions for the codec about the length of each fields (so that when the generated codec decodes a variable-length field (typically a charstr... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.2 Design proposals for receiving of traffic capture | This clause evaluates different design proposals for integrating the IMS interoperability test adapter with physical traffic capture. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.2.1 All traffic on single (mirrored) switch port | This design proposal assumes that all traffic produced in interoperability testing is mirrored by a switch on a single port. Multiple cascaded switches may be used to combine multiple monitoring ports into one physical port which is then connected to the computer running the test adapter via its network card. Figure 2:... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.2.2 Traffic on multiple switch ports (no mirroring) | This solution requires that the computer running the test adapter has multiple network interface boards. However, this solution does not require the implementation of switches that support mirroring. Figure 3: Design with a switch providing multiple ports for traffic in context of IMS interoperability testing |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 5.2.3 Discussion | The first proposal has the main advantage that it is easy to deploy. We can use essentially any laptop with, e.g. an Ethernet card. The main problem is that switches with mirroring capability may be hard to find. The second solution will eventually impose some limitations on the number of network cards, i.e. interfaces... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6 Software design | This clause introduces the requirements taken into account for the software design of both test adapter and codec. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.1 Codec design | This clause introduces the software design solutions proposed to implement the Codec. Switch Computer running adapter and potentially TE+Codecs UE A UE B IMS A IMS B Traffic capture Equipment operation messages ETSI ETSI TR 101 561 V1.1.1 (2011-06) 14 |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.1.1 Regular expression | A utility class named "Regex" was developed. It is implemented based on the portable C++ BOOST [i.1] regex library and implements perl regular expressions. Moreover it is integrated partially with the T3DevKit API by providing functions to match the regex on a part of the encoding buffer, to report easily the length of... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.1.2 Template generation | TTCN-3 message templates are generated automatically by a script based on a TTCN-3 type module. The main difficulty is to generate a reasonable amount of templates: it is very easy to generate millions of template due to combinatory explosion. To avoid this problem, it is important to carefully define the rules that wi... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.1.2.1 Generation rules | The following generic rules have been selected for this project: Port primitives are the starting point of the process. Complete templates are generated for each primitive, using a recursive strategy and by applying the following rules: • While processing a record, generate two templates, one containing values for mand... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.1.2.2 Template generator design | The generator developed within STF370 is a Perl script which receives type and port definitions as input and produces three files: one containing all the generated message templates and sub-templates, a second file containing the generic test cases and a test control file. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 15 Figur... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2 Test adapter design | This clause introduces the software design solutions proposed to implement the test adapter. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.1 Requirements | The test adapter software will address the requirements listed in table 2 which are not normative requirements. They only indicate the functionalities within the objective of the test adapter software. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 16 Table 2: Test adapter software requirements Requirements Description On/Off l... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2 Software design | In order to fulfil the above requirements it was decided to design test adapter software architecture with the following main components: • A Lower Test Adapter which provides traffic capture processing functionality which includes handling of IPv4 and TCP fragmentation, isolation of protocol messages, etc. • A PCAP ca... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2.1 Test adapter interfaces | The proposed test adapter has three types of interfaces: • One with the TTCN-3 TE which implements part of the TRI interface. • One with the traffic capture, i.e. the PCAP capture library. • One with EUT operator, i.e. the GUI which interacts with the equipment operator. GUI UE B UE A UE B IMS A IMS B Network TTCN-3 TE... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2.2 Test adapter configuration | In order to fulfil the dynamic adapter configuration requirements, the test adapter supports the following primitives: • A general configuration primitive which is used to communicate parameters which are not specific to a specific monitored EUT interface. These parameters include an indication for live vs. offline cap... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2.3 Adapter configuration message encoding | When TTCN-3 TE and test adapter exchange messages via the TRI, the TRI requires that these messages have to be encoded. The following encoding rules are used to encode adapter configuration messages: • The message type is encoded in the first octet except for capture messages which are pure raw data (see table 3 for de... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2.4 Traffic capture | The adapter has been designed to allow also integration of non-PCAP based trace processing. In this case the PCAP library would be replaced by another traffic capture tool library. The integration of such other tools would however require a vendor specific implementation of the communication with the Lower Test Adapter... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2.5 Merge of multiple trace files | The test adapter assumes all traffic capture files to be merged are located in the same directory. In the case of the PCAP library implementation the merged file is generated during the execution of a test case in that same directory. Note that this feature is only available in offline mode. Note that should the test e... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.2.6 Possibilities for handling of equipment operation messages | There are different ways to handle the TTCN-3 equipment operation messages: • Implement a human friendly GUI to guide the user to operate manually the EUT as specified in the command. Such an approach is required when the interoperability test is executed with real end user equipment, e.g. a mobile terminal with a IMS ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 6.2.3 Discussion | The human friendly GUI solution was selected in the test adapter software design. Due to the variety of different interfaces for the operation of EUTs and their predominately proprietary nature, it is very hard or even impossible to develop only one automatic mechanism to operate EUT or other equipment. In addition, th... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7 TTCN-3 message type definitions | This clause provides an overview of TTCN-3 port and message types used to communicate with the Adapter via the abstract TTCN-3 TSI. Note that the adapter is not directly dependent on the IMS interoperability test suite but rather the TTCN-3 interoperability library called LibIot. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.1 TTCN-3 port description | Three types of TSI ports are defined in LibIot: • Adapter port is used to receive and send general configuration messages, setting of test component specific filter criteria, and for controlling traffic capture. • Monitor data port is used by TTCN-3 components to receive protocol messages from the lower test adapter. •... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.2 TTCN-3 messages description | Figure 8 shows the TTCN-3 message type for general adapter configuration. These types are defined in the LibIot_TypesAndValues TTCN-3 module. type record of charstring PhysicalInterfaceList; type record LiveCapture { PhysicalInterfaceList physicalInterfaces, RecordMode recordMode } type enumerated RecordMode { e_noreco... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.2.1 Record mode | This parameter is used to control the recording of traffic capture in a file in live capture mode. The name and location of the output file is selected based on the naming convention described in clause 6.2.2.3. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.2.2 Merging of captured traffic files | If the mergeFileList is selected in the CaptureMode union and this field contains a list of the traffic capture file names in the mergeFileList field and a mergeFilePath field that contains a directory name where the merged file is to be stored. The traffic capture process will then perform, e.g. a PCAP merge operation... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.2.3 List of physical interfaces | In the live capture mode the physicalInterfaces field allows to specify a list of physical interfaces, Ethernet card information. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 22 7.2.4 Example of setting general adapter configuration message values in TTCN-3 group adapterGeneralConfiguration { /** * * @desc Maximum time limit ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.3 Setting of filter criteria | These messages are used by TTCN-3 test components to request their specific filtering of traffic capture. The adapter combines all filter criteria automatically when it receives a StartCaptureRequest. type UInt16 PortNumber; type record of PortNumber PortNumberList; type record IpInterfaceInfo { charstring domainName o... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.4 Starting and stopping of traffic capture | These messages are used by the adapter process to send its filter to the TrafficCapture process and to command it to start or stop capturing traffic. type record StartTrafficCaptureReq { } type record Status { FncRetCode code, charstring reason optional } type record StartTrafficCaptureRsp { StatusCode result } type re... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 7.5 Equipment operation messages | These messages are used to request the operation of a EUT or other equipment during a test. type record of charstring ParameterList; type charstring EquipmentCommand; type record EquipmentOperationReq { EquipmentCommand cmd, ParameterList params optional } type record Status { FncRetCode code, charstring reason optiona... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 8 Test case suite for Adapter regression tests | This clause introduces the different tests cases developed to test the Adapter functionalities. The code below shows these test cases suite. control { execute(TC_GeneralConfigurationMessageOffLineMode()); execute(TC_GeneralConfigurationMessageLiveMode()); execute(TC_GeneralConfigurationMessageMerge()); execute(TC_Trigg... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 8.2 Description of TC_GeneralConfigurationMessageLiveMode | This script tests a GeneralConfigureReq message to process real time traffic capture. Note that in this case, the UpperTest adapter part will use the human friendly application to guide the user for the actions to achieve. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 8.3 Description of TC_GeneralConfigurationMessageMerge | This script tests a GeneralConfigureReq message to merge first a set of PCAP files and process the resulting file process real time traffic capture. Note that in this case, the UpperTest adapter part will use the human friendly application to guide the user for the actions to achieve. ETSI ETSI TR 101 561 V1.1.1 (2011-... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 8.4 Description of TC_TriggerUERegister | This script tests a UE_REGISTER equipment access message in real time mode in order to use the human friendly application to guide the user for the actions to achieve. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 9 Deployment diagram of the test adapter | In order to specify the most open and flexible software architecture as possible, the PCAP traffic capture component has been implemented as an independent process from the other adapter implementation, so that it can be executed by a remote computer if needed. In the default configuration the PCAP traffic capture proc... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 10.1 Interactions between TTCN-3 script and Adapter | Figure 15 shows the TTCN-3 message exchanges between a TTCN-3 script and the Adapter. Figure 15: Message exchanges between TTCN-3 script and the Adapter The GeneralConfigurationReq message is assumed by the adapter to be always sent prior to starting traffic capture. Parameters of this message are discussed in clause 6... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11 Class diagram of the Adapter component | The Adapter component is built on two main classes: 1) The UpperTestAdapter class provides the implementation for the GUI upper test adapter. 2) The LowerTestAdapter class provides the implementation of captured traffic processing like isolation and dispatching of protocol messages to the correct TTCN-3 components. ETS... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.1 UpperTestAdapter class description | Figure 18 describes the architecture of the Upper test adapter part. The main object is the unique instance of the class UpperTestAdapter. This class manages the equipment access messages with the test script. These equipment messages are processed by the Processor class, one instance per equipment access port. Two kin... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.2 Helpers classes description |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.