CES 592 Telecommunications System Product Verification Sonoma State University

CES 592 Telecommunications System Product Verification Sonoma State University PowerPoint PPT Presentation


  • 97 Views
  • Uploaded on
  • Presentation posted in: General

6/3/2012. Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved. 2. Instructors. France Antelme Ario Bigattini Jaseem Masood Steven Woody Coordinator: Prof Ravi KumarWebsite:SSU-ES || CES 592. 6/3/2012. Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all

Download Presentation

CES 592 Telecommunications System Product Verification Sonoma State University

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


1. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 1 CES 592 Telecommunications System Product Verification Sonoma State University Class Lecture 4: Hardware Verification 1 Standards Bodies, Standards Testing

2. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 2 Instructors France Antelme Ario Bigattini Jaseem Masood Steven Woody Coordinator: Prof Ravi Kumar Website:SSU-ES || CES 592

3. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 3 Telecom Product Verification Standards Bodies – Physical and Logical Layer Initially we will concentrate on Standards bodies that provide standards and requirements aimed at Physical and higher layer requirements. Standards bodies related to Agency and Regulatory approvals testing will be dealt with in the section on Agency and Regulatory approvals Where there are standards bodies that provide standards overlapping these two areas, mention will be made later in the course

4. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 4 Telecom Product Verification Standards Bodies – Physical and Logical Layer All areas of the Telecom industry are specified by these standards: Equipment: Physical Layer performance Logical Layer performance Electromagnetic Compatibility Environmental Performance Reliability Component Reliabilities Form and Fit Network: Performance Management Central Office: Installation and wiring requirements Power and Grounding requirements Heating, Cooling Etc.

5. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 5 Telecom Product Verification Standards Bodies –Physical and Logical layer Standards Bodies that are applicable to the Telecommunications market: US Market Telcordia (Formerly Bellcore) Telcordia - Store ANSI T1 Committee now ATIS ATIS; Committee T1-Telecommunications; T1A1; T1E1; T1M1; T1P1; T1S1; T1X1; Standards IEEE – For Ethernet etc. IEEE 802.3 European Market: European Telecommunications Standards Institute (ETSI) Welcome to ETSI! International Telecommunications Union (ITU) Worldwide: International Telecommunications Union (ITU) http://www.itu.int/ITU-T/publications/recs.html European Telecommunications Standards Institute (ETSI) Some countries such as Japan, Korea and a few others follow a mixture of US and ITU standards Standards/requirements for Regulatory & Agency approvals not included. Covered in Lecture 5

6. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 6 Telecom Product Verification Standards Bodies : ITU (Europe + World outside US) The ITU: “The main products of ITU-T are the recommendations. At present, more than 2900 Recommendations (Standards) are in force. Recommendations are standards that define how telecommunication networks operate and interwork. ITU-T Recommendations are non-binding, however they are generally complied with due to their high quality and because they guarantee the interconnectivity of networks and enable telecommunication services to be provided on a worldwide scale.” (from ITU Website) ITU recommendations are designated by a letter followed by a number e.g. G.703, G.695…etc.

7. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 7 Telecom Product Verification Standards Bodies: ITU (Europe + World outside US) ITU-T Recommendations are organized in designated by a letter followed by several digits. The letter denotes the area of Telecomm that is being specified A - Organization of the work of ITU-T B - Means of expression: definitions, symbols, classification C - General telecommunication statistics D - General tariff principles E - Overall network operation, telephone service, service operation and human factors F - Non-telephone telecommunication services G - Transmission systems and media, digital systems and networks H - Audiovisual and multimedia systems I - Integrated services digital network J - Cable networks and transmission of television, sound programme and other multimedia signals K - Protection against interference L - Construction, installation and protection of cables and other elements of outside plant M - TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits N- Maintenance: international sound programme and television transmission circuits O- Specifications of measuring equipment P- Telephone transmission quality, telephone installations, local line networks Q- Switching and signalling R- Telegraph transmission S -Telegraph services terminal equipment T - Terminals for telematic services U - Telegraph switching V - Data communication over the telephone network X - Data networks and open system communication Y - Global information infrastructure and internet protocol aspects Z - Languages and general software aspects for telecommunication systems

8. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 8 Telecom Product Verification Standards Bodies: ITU (Europe + World outside US) A few examples of typical ITU recommendations: G.652 - Characteristics of a single-mode optical fibre and cable G.703 - Physical/electrical characteristics of hierarchical digital interfaces G.704 - Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels G.811 - Timing characteristics of primary reference clocks G.812 - Timing requirements of slave clocks suitable for use as node clocks in synchronization networks G.813 - Timing characteristics of SDH equipment slave clocks (SEC)

9. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 9 Telecom Product Verification Standards Bodies : ETSI (Europe) European Telecommunications Standards Institute: Generally ETSI standards precede those of the ITU and in many cases they are formally adopted by the ITU. This organization is focused on European requirements. In most cases, ETSI standards are applied to Environmental and EMC requirements since the ITU does not have detailed environmental requirements and ITU Physical layer standards normally mirror the equivalent ETSI Physical layer standards

10. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 10 Telecom Product Verification Standards Bodies : (Worldwide) Generally most countries outside Europe and the US apply ITU standards augmented by ETSI requirements in areas where the ITU standards are lacking such as environmental parameters etc. In a few countries there are country- specific requirements which are a variant of either US or ITU/ETSO requirements. An example is Japan where there Japan-specific variants of some paragraphs of both the US Telcordia and ITU standards are utilized e.g Japanese DS1, J-SDH standards etc.

11. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 11 Telecom Product Verification Standards Bodies – Telcordia (US and North America) Telcordia , Formerly Bellcore is the dominant standards body for the Telecom Industry for the US today. Bellcore was created by the old Bell System Operating Companies as a Research arm Bell Company Research. They generated extremely comprehensive Requirements for every aspect of the US Telecommunications Industry. All the Bell Operating Companies i.e. (Bell South, AT&T, SBC, etc. etc. follow these requirements In 1999 with the government mandated dissolution of the Bell System, Bellcore was sold to SAIC and the name was changed to Telcordia. Most system level requirements are known as Generic Requirements and designated GR-XXX

12. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 12 Telecom Product Verification Standards Bodies Telcordia (US+ North America) All areas of the Telecom industry are specified by Telcordia standards inlcuding some of the standards for Regulatory and Agency approvals: Equipment: Physical Layer performance Logical Layer performance Electromagnetic Compatibility Environmental Performance Reliability Component Reliabilities Form and Fit Network: Performance Management Central Office: Installation and wiring requirements Power and Grounding requirements Heating, Cooling Etc.

13. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 13 Telecom Product Verification Standards Bodies Telcordia (US+ North America) Examples of Telcordia Standards: GR-499-CORE ISSUE 2, DECEMBER 1998 : Transport Systems Generic Requirements (TSGR): Common Requirements GR–253–CORE ISSUE 2, DECEMBER 1995 WITH REVISION 2, JANUARY 1999: Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria FR-2063 - Network Equipment-Building System NEBS(TM) Family of Requirements (NEBSFR). (This is the requirement that is a the root of what is known in the US Telecom Industry as “NEBS Certification” ) “FR” denotes a Family of Requirements and consists of several GR documents aggregated together

14. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 14 Telecom Product Verification Standards Bodies Telcordia (US+ North America) All the Physical, Environmental Characteristics for the Telecom equipment destined for the US market are defined by Telcordia requirement: FR-2063 - Network Equipment-Building System NEBS(TM) Family of Requirements (NEBSFR) Compliance to this requirement/standard is behind the term “NEBS certified” that will be familiar to anyone involved with the Telecom industry in the US. NEBS 63 amongst all the other parameters relating to equipment performance, provides the Environmental Operating parameters requirements of the EUT. These we will use to evaluate Physical and Logical Layer performance of the EUT

15. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 15 Telecom Product Verification Standards Bodies Telcordia (US+ North America) NEBS-FR 2063 “The Network Equipment Building System NEBS(TM) family of documents are the most common requirements used to access the suitability of equipment being installed in network facilities. Most Service Providers reference NEBS documents as a condition of product development. Telcordia NEBS criteria are used to evaluate the ability of a product to operate as intended under electrical and physical environmental stresses, such as electromagnetic interference, high and low temperatures, and earthquake and vibration conditions. NEBS criteria are also used to assure that equipment does not pose a threat to services or personnel, via analyses for fire resistance, electrical safety and grounding. By incorporating the NEBS documents into your design process, you will be able to produce equipment and systems that perform as intended despite adverse conditions. That means you will avoid the costs of redesign and remanufacture after an unforeseen disaster, when costs can be prohibitive. Customers are spared the down time that can result from equipment failure or malfunction. In addition, the reputation of your company can be saved, which may be severely damaged if a critical piece of equipment or a system fails.” From Telcordia Website

16. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 16 Telecom Product Verification NEBS-FR 2063 : Contents of the so-called “NEBS” document GR-1089 "Electromagnetic Compatibility and Electrical Safety - Generic Criteria for Network Telecommunications Equipment“ GR-1217"Generic Requirements for Separable Electrical Connectors Used in Telecommunications Hardware“ GR-1221"Generic Reliability Assurance Requirements for Passive Optical Components“ GR-2930"Network Equipment Building System NEBS(TM) Raised Floor Generic Requirements for Network and Data Centers“ GR-2969"Generic Requirements for the Design and Manufacture of Short-Life Information Handling Products and Equipment“ GR-3028"Thermal Management In Telecommunications Central Offices: Thermal GR-3028“ GR-357"Generic Requirements for Assuring the Reliability of Components Used in Telecommunications Equipment“ GR-468"Generic Reliability Assurance Requirements for Optoelectronic Devices Used in Telecommunications Equipment“ GR-63"NEBS(TM) Requirements: Physical Protection“ GR-78"Generic Requirements for the Physical Design and Manufacture of Telecommunications Products And Equipment“ SR-3580 "Network Equipment-Building System NEBS(TM) Criteria Levels“ SR-4087"Physical Design Certification of Bare Printed Boards“ SR-4407"Adhesive Certification“ SR-4408"Flux Certification“ SR-4409"Legend Ink, Marking Ink and Adhesive Label Certification“ SR-4410"Solder Mask, Conformal Coating, and Repair Polymer Certification“ SR-4568"Separable Electrical Connector Certification“ SR-4808"Printed Board Assembly Certification“ SR-4935"Connector to Cable Assembly Certification“ TR-NWT-000930"Generic Requirements for Hybrid Microcircuits Used in Telecommunications Equipment

17. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 17 Telecom Product Verification Standards Bodies : ANSI T1X1 committee (USA) “Established in February 1984, Committee T1 develops technical standards and reports regarding interconnection and interoperability of telecommunications networks at interfaces with end-user systems, carriers, information and enhanced-service providers, and customer premises equipment (CPE). Committee T1-Telecommunications is sponsored by the Alliance for Telecommunications Industry Solutions (ATIS) and is accredited by the American National Standards Institute (ANSI). Committee T1 has six technical subcommittees that are advised and managed by the T1 Advisory Group (T1AG). Each technical subcommittee develops draft standards and technical reports in its designated areas of expertise. The subcommittees recommend positions on matters under consideration by other national and international standards bodies. Technical subcommittees and their areas of expertise are: T1A1 - Performance and Signal Processing T1E1 - Interfaces, Power and Protection of Networks T1M1 - Internetwork Operations, Administration, Maintenance & Provisioning T1P1 - Wireless/Mobile Services and Systems T1S1 - Services, Architectures and Signaling T1X1 - Digital Hierarchy and Synchronization” From the ATIS/ANSI T1 Committee website

18. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 18 Telecom Product Verification Standards Bodies : ANSI T1X1 US+ North America) The former ANSI T1X1 committee, now known as the ATIS T1X1 committee, previously did the pioneering work on new standards which were then adopted by Bellcore as the defacto standards for the US. Currently Telcordia/Bellcore standards are still the pre-eminent overhead standards but the ATIS T1X1 committee activities are assuming more importance lately and, in some cases the T1X1 standards may supersede the Telcordia/Bellcore standards. These standards are primarily aimed at physical layer parameters

19. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 19 The Product Development Cycle i.e. Stage 1 of the Product Lifecycle

20. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 20 Product Verification Phase

21. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 21 Product Verification Flow Chart Do you adopt a single or multiple load approach? Integration Overflows but System Test time cannot be compromised. How could code be ported over so late? Requirements tracking is important. How do you know which load is ready for Beta? Do you adopt a single or multiple load approach? Integration Overflows but System Test time cannot be compromised. How could code be ported over so late? Requirements tracking is important. How do you know which load is ready for Beta?

22. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 22 Elements of Hardware Verification

23. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 23 Telecom Product Verification Hardware Verification- Standards Physical layer

24. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 24 Telecom Product Verification Typical Physical layer test parameters Hardware Verification: Physical Layer Standards based testing- Equipment Under Test (EUT) is verified by own test organization (i.e. self certified) against the Product, Industry requirements for performance of the following: Physical layer Transmitters Eye pattern, Pulse mask Line frequency Line Build-out Rx Sensitivity, Dispersion/Reflection power penalty Laser line width, Side Mode suppression etc Tx Power output Jitter generation and jitter tolerance Receivers Rx Sensitivity, Dispersion/Reflection power penalty Synchronization systems ( Where applicable) Wander (<10Hz) & Jitter (>10Hz) performance: MTIE/TDEV Interface Jitter/Wander (Optical and Line) Logical and Higher Layers: Framing Alarming

25. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 25 Telecom Product Verification Typical Compliance/Regulatory approvals test parameters Hardware Verification: Compliance Testing: Equipment Under Test (EUT) is verified against the Industry and Regulatory requirements and certified compliance by independent laboratories: EMI/EMS/ESD: EM radiated & Conducted emissions EM radiated and conducted susceptibility Electrostatic Discharge tolerance Safety: e.g. Underwriters Laboratory etc. Telecom interface: i.e performance certification for inclusion in the Public network Power and grounding: Verification of Power and Grounding layout to regulatory requirements Environmental: Very coarse Industry environmental operation/storage under hi/lo temp, airborne contaminants, Shock and vibration, Flame resistance, Heat generation etc

26. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 26 Telecom Product Verification Hardware Stress Testing Hardware Verification: Stress Testing: Equipment Under Test (EUT) is subjected to external stresses to excite failures HALT: Highly Accelerated Lifecycle Tests: EUT subjected to stress to determine failure modes HASS: Highly Accelerated Stress Screen: EUT is subjected to elevated stresses in order to ensure that there is high yield in production The point of this type of test activity is to use elevated stresses in order to excite failure modes of very low probability of occurrence in a short period of time. The failure mode is remedied and the remedy is used to drive higher yields in production and lower customer failure rates

27. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 27 Telecom Product Verification Hardware Verification Physical and Logical Layer testing

28. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 28 Telecom Product Verification Hardware Verification- Standards / Physical layer testing With this type of test testing, we test the Physical and Logical layer performance of the Equipment Under Test (EUT) This implies the following: Physical layer: Generally evaluating analogue performance parameters of the interfaces and synchronization system, if any of the EUT Logical Layer (Framing, Alarming etc): Generally evaluation that the data being transported over the physical layer interfaces are correctly framed and all bits and bytes are correctly configured. Physical Layer testing is generally Internal testing and it used to satisfy the Product Development team that the product meets all the requirements and will be reproducible with reasonable yield in production Customers generally accept the test plans and test results of the equipment vendor, and will in many cases pick test cases at random to execute in their labs to verify the vendor provided test results Certain of the Physical layer parameters are retested and certified by outside labs/test organizations for the purposes of Compliance/Agency approvals

29. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 29 Telecom Product Verification Physical Layer Measurement Uncertainty When evaluating Physical Layer performance, since you are typically measuring analogue parameters, margin must be allowed for both measurement uncertainty in the test stations as well as component variability from one test sample to another. When evaluating logical layer performance, it is a go/no go situation that provides little room measurement uncertainty How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

30. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 30 Telecom Product Verification Hardware Verification- Standards / Physical layer testing The Physical layer parameters are tested over the operating temperature range of the EUT. Typically performance data is taken at three temperature points: Upper Operating Temperature Room temperature Lowest Operating Temperature range Logical layer performance, if functional at room temperature, will function correctly at all temperatures

31. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 31 Telecom Product Verification Physical Layer Testing: Typical Temperature ramp profile derived from GR-63

32. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 32 Telecom Product Verification Physical layer test example: SONET OC-3 (155MBits/sec Optical Transmitter requirement from Telcordia GR-253 How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

33. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 33 Telecom Product Verification Physical layer test example: SONET OC-3 (155MBits/sec Optical Transmitter Eye mask requirement from Telcordia GR-253 How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

34. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 34 Telecom Product Verification Physical layer test example: Optical Eye Pattern How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

35. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 35 Telecom Product Verification Physical Layer test example : Optical Receiver Sensitivity and Dispersion Power Penalty How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

36. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 36 Telecom Product Verification SONET Jitter Tolerance measurement How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

37. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 37 Telecom Product Verification Physical Layer Test Example: DS3 Pulse mask How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

38. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 38 Telecom Product Verification Physical Layer Test example: 10/100 BaseT Ethernet Pulse mask and bathtub curve How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

39. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 39 Telecom Product Verification Physical Layer test example: 10/100Base T Ethernet Pulse Mask How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

40. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 40 Telecom Product Verification Physical Layer Measurement Uncertainty IT is important to pay attention to the measurement uncertainty of the Test Setup since differences between test systems in Hardware Product Verification and Manufacturing Test can dramatically influence the reject rate in production due to failures to meet the standard. Allowance must also be made for Variances in performance due from one component to another. This can typically be approximated by a Gaussian Probability Density Function when large numbers of components are considered. Therefore the Hardware Product Verification Team needs to make allowance for these two variables in terms of ensuring that there is adequate margin for a Pass Measurement Uncertainty is itself a science and we could spend this entire course discussing it’s various aspects. How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

41. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 41 Telecom Product Verification Physical Layer Measurement Uncertainty Both Test Set-up measurement uncertainty may be modeled by the Gaussian Distribution function: P(x) = e -(x-µ)2 2s? sv2? Where s? = the variance or MS deviation from the mean s = Standard deviation or RMS deviation from mean µ = The mean How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

42. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 42 Telecom Product Verification Measurement Uncertainty

43. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 43 Telecom Product Verification Measurement Uncertainty – Allow for component tolerance when judging pass or failure How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

44. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 44 Telecom Product Verification EUT Sample size When evaluating Physical layer performance the Product Verification team needs to decide upon the number of EUT prototypes to be used for HW Verification. The smaller the sample size, the greater the risk that there will be significant rejects in production at a later date There is always pressure from the Project Management team to keep the number of prototypes to a minimum to reduce cost. Prototypes can cost 2-4 times what it costs to manufacture production boards so prototype costs rapidly mount up. Depending upon the type of product Under Test, 2-6 prototype samples are reasonable. The Product Verification team must then build up a knowledge base over time and compare production test results with Product Verification Test results. Using this comparison, then sample sizes may be adjusted accordingly for new product developments How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

45. 6/4/2012 Steven Woody, France Antelme, Ario Bigattini, Jaseem Masood all rights reserved 45 Telecom Product Verification Useful References An introduction to error analysis: The study of uncertainties in Physical Measurements, John R. Taylor, University Science Books Fiber Optics Test and Measurement, Editor: Dennis Derickson, Prentice-Hall How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?How do you know what the market needs are? Will they change by the time you are ready to deliver? What is a better marketing strategy? First in the market or best quality? How well understood do these requirements need to be? Why do you need requirements. How is the organization to know if it works like the customer wants, what to test or how it supposed to work? Can you leverage other product implementations within the corporation?

  • Login