ITU-T Rec G783 (102000) Characteristics of synchronous…
优化织布缺陷检测的图像处理和模糊逻辑方法说明书
Optimizing Woven Fabric Defect Detection Using Image Processing and Fuzzy Logic Method at PT.Buana Intan GemilangRatna SafitriSchool of Industrial and System EngineeringTelkom University Bandung, Indonesia *************************Tatang MulyanaSchool of Industrial and System EngineeringTelkom University Bandung, Indonesia*********************************.idAbstract —The development of textile industry which 3rd position in the largest export values in Indonesia prove that the quality of textile must be one of factors that should be considered for all of textile companies. Buana Intan Gemilang is one of the companies that produce woven fabric. This company s produce curtain woven fabric. Quality is the most important factor to reach high level customer satisfaction. To get the best quality of product needs to consider their quality control. According to inspection process in Buana Intan Gemilang, manual inspection for woven fabric defect detection need 19.87 second for average inspection time. Therefore, unbalance of production volume with inspection process cause the bottle neck in inspection process. In this research, proposed designing automated fabric inspection using image processing and Fuzzy Logic Model. This processed uses GLCM as feature extraction with three parameters are cluster shade, cluster prominence, and number of object. The proposed fabric inspection using Fuzzy Logic implemented with MATLAB provides better result in identifying fabric defect and optimizing process time. This research using 120 training data, 80 offline test data, and 80 real time test data. Identification automation defect of woven fabric test data can produce accuracy 97, 5% and averaging process time 1.15 second. This result is better than manually inspection process that took 19.87 second for scanning defect of woven fabric.Keywords optimizing; defect; detection; image-processing; fuzzy logic method; woven-fabricsI. I NTRODUCTIONThe statistical value of the top ten industrial groups with the largest export value in Indonesia., shows that the textile industry is in position with export value of 12.26 billion US $. One of the companies engaged in the textile industry is PT. Buana Intan Gemilang located in Banjaran, West Java. This company produces textile in the form of woven curtains. To produce a product that meets the standards and quality of consumer process quality is required to control the resulting product. This is done by conducting an inspection process on products that have been completed in production in order to meet the standards. At this time, the inspection process on the company is still done manually using the human eye with the help of lighting in the form of lights. Based onobservations to the company the manual inspection process takes longer time to process time of 19.7 seconds because of human limitations. Based on the human error factor there will also be defects that are also missed or not visible if the inspection is done without tools. Based on the company's data the company's production volume is not proportional to the inspection volume so as to cause unspoiled fabrication of fabrics on inspection workstations and result in unmet demand on time. The development of image processing technology will help to overcome the problems in the inspection process in order to reduce the time of the inspection process with more accurate results. This study designs a system that focuses on the optimization of the inspection process to detect the types of defects found on the fabric. Thus, appropriate identification techniques are needed to detect defects. The method used in this research is fuzzy logic method that able to handle ambiguity, and variable uncertainty used [1]. This study supports automation systems to identify defects in fabrics using the fuzzy logic method by replacing the function of human vision into digital image processing. The Supervisory Control and Data Acquisition (SCADA) monitoring system is built based on Graphical User Interface (GUI) by using IGSS software. Development of the SCADA application leverages the Wonderware Information Server with Active Factory and Generic Data Grid in order to obtain reporting system a system that can be accessed online. The researcher has been presented these SCADA such as [2-5]. The modelization for the control system is made using Simulink graphical model. In the process, diagram block is used by [6-7]. Mathematical model for a process control plant is important because it provides key information as to the nature and characteristic of the system which is vital for the investigation and prediction of the system operation. Through mathematical equation model, we can study about the dynamics of the process, stability of the system, design controller etc. The mathematical equation model is used to determine a performance of the system [8-16].International Conference on Industrial Enterprise and System Engineering (IcoIESE 2018)Atlantis Highlights in Engineering (AHE), volume 2II. B ASIC T HEORY AND M ETHODOLOGYQuality is a characteristic that a product is expected to have, and is an important factor for customers to choose a product or service [17, 19]. The quality of a product is inversely proportional to the number of defects. The higher the quality of a fabric the less the defects are in the fabric and vice versa. Type of defect in fabric based on Indonesia National Standard (SNI) 08-0277-1989 consisting of 17 types of defects as contained in TABLE I, type of defects based on manual inspection in the company can be seen in TABLE II, and the equation of both can be seen in TABLE III.TABLE I. T YPES OF D EFECTTS ON F ABRICS BASED ON SNI 08-0277-1989No. Defect TypeDefect Definition1 Nep Nep2 Sub Thread wrapped, Broken yarn, Dirt, Knot thread3 Uneven yarn Big thread, Thread.4 Yarn broken Lacking defective defect , Empty feed defect5 Yarn tense / saggy Wrinkle shrub fabrics, arch.6 Fold lines Cloth folded7Warp linesDifferent thread structures, Comb line, Double warp, Tight warrant, Rare warp, Different types of fiber, Big thread, thread.8 The feed line Double feed, stop mark, Feed tight, Empty feed defect, big thread, thread. 9 Wrong pattern Defect pattern, Wrong shape stamp, Wrong webbing, The stamp pattern misses, Wrong color weaving style10 Bare Different thread structures, Different types of fiber, Empty feed defect 11 Striped Colorlessness, different Color 12 TornHole, torn 13 The thread is not woven Yarn jumping14 Stains Rust stains, Color stains 15 Defect width -16 Feed bias Feed bias including curved feed 17Flaw defects-TABLE II.T HE F ABRIC D EFECT T YPE B ASED ON M ANUAL I NSPECTIONIN PT. B UANA I NTAN G EMILANGNo. Type of Defect1Hairy Empty Feed 2Brodol Empty Feed3Lacking Defective 4 Tense Lacking Defective 5Comb DisabilityNo. Type of Defect6 Card Damage7 Plotting8 Lusi Double 9Long MustacheTABLE III. SIMILARITY OF FABRIC DEFECT TYPE BASED ON SNIAND MANUAL INSPECTION IN PT. BUANA INTAN GEMILANGNo.Defect SimilaritySNIObservation Result1 Nep Hairy Empty Feed2 SlubBrodol Empty Feed 3 Yarn Disconnected Lacking defective 4 Yarn Tense Tense Lacking defective 5 Lusi Line Comb Disability 6 Wrong Pattern Card Damage 7Unfinished YarnPlottingFuzzy model is a process of input in the form of a value converted by fuzzification into fuzzy value at U value which is then processed by inference with fuzzy rule which then reasserted with defuzzification which will determine is output in the form of firm value (crisp) [1]. The use of fuzzy model in this research, can be seen in Fig. 1.Defuzzification is a mapping of the fuzzy set on to a firm value (crisp) [17]. It can be interpreted that Defuzzification is a transformation process that states the change of form of the fuzzy set resulting from fuzzy inference to its assertion value (crisp) based on a defined membership function. The value of defuzzification is the output of the fuzzy logic process. In GUI design extraction features, there are three push buttons used, including browse picture, process, exit, and reset. There are also two axes that serve to display images that exes greyscale and axes identification. In addition, there are four edittex, edittext box after browse picture to display the location of the image taken, edittext box beside the number of objects that function display the value of the number of objects, edittext cluster shade box that displays the value of the cluster shade, and the edittext cluster prominence Which serves to display the value of cluster prominence. In addition, there are three statictext that is writing number of object, cluster prominence, and cluster shade contained in GUI extraction feature. GUI design features extraction can be seen in Fig. 2. Extraction feature results in the value of cluster shade, cluster prominence, and number of objects. Examples of extraction feature results can be seen in Fig. 3.Fig. 2.GUI design of feature extraction.Fig. 3.GUI design result of feature extraction.In designing GUI extraction feature there are four push buttons used, including browse picture, manual, auto, and identification. There are also two axes that serve to display images of exes preview and axes identification. In addition, there are three edittext, edittext box after browse picture to display the location of the picture taken if the mode used there is manual mode, edittext box beside identification that serves to show the identification result, and edittext box beside time functioning display real time image identification time, In addition there is one statictext that is writing time found on the GUI identification. The design view of GUI identification can be seen in Fig. 4.Fig. 4.GUI design result of defect identification.III.R ESULT AND D ISCUSSIONThe steps undertaken in this research is done with the steps as follows that is, take pictures or imagery via MATLAB using the distance of 16 cm camera, light intensity 1600 lux, and 1.3 megapixel. The next step is to change the image of the capture that is still in the form of RGB (Red, Green, Blue) to grayscale. After the image is converted into greyscale form then the image is converted into binary form. Once the image is in a binary image, the next step is to extract the image usingthe GLCM extraction feature to find out the value of cluster shade, cluster prominence, and number of objects. The results of the extraction feature can be seen in TABLE IV.TABLE IV. R ESULT OF THE F EATURE E XTRACTIONType of defect Oil defectLackingDefectiveDefectEmptyfeedDefectNormalCluster Shade -9,04638 -1,00373 -0,01449 0,04977 ClusterProminence-3,29245 0,18070 0,31701 -0,03391Number ofObject2 3 7 0 Identification Defect Defect Defect NormalInput on fuzzy Mamdani is the values of cluster shade, cluster prominance, and number of objects. With membership functions A1 through A9, B1 to B9, and C1 to C9. Furthermore, the value will be the limit for each parameter used. For fuzzy Mamdani output this is normal and defective. The total of the rules used is 729. Identification is done on the 120-data train so that obtained the results of identification as in TABLE V. Based on the table can determine a accuracy rate used equation in (1) is 95%.Accuracy rate = (Amount of data is correct)/(Total test data) x 100% (1)TABLE V. I DENTIFICATION R ESULT OF THE T RAINING D ATANo. Image DataTypeInput TrainingdataOutput ModelTrue False1 Oil Defect 30 30 02 LackingDefectivedefect30 30 03 Empty Feeddefect30 30 04 Normal 30 24 6In the offline system the process of detecting defects is done without being integrated with software and hardware other than camera and excel database. The fabrics to be classified are derived from camera captures that have been stored in the database. Matlab software is used to process images taken from the database for identification. TABLE VI shows results of offline identification. Based on the formula, the accuracy of the test data using the fuzzy model with the triangular representation of the fuzzy membership function, fuzzy mamdani inference, and centroid deffuzification, and 729 fuzzy rules is 93.75%.TABLE VI. O FFLINE I DENTIFICATION R ESULTImage Data Input Training Output ModelNo. Type data True False1 Oil Defect 20 20 02LackingDefectivedefect20 20 03Empty Feeddefect20 20 04 Normal 20 15 5In the automatic fabric defect identification system, the process of detecting defects is already integrated with software and other hardware, i.e. PLC, HMI, inverter, motor, webcam, and excel database. Cloth to be classified comes from the results of camera capture in real time. MATLAB software is used to process images taken from the capture process in real time for identification. After the previous fuzzy rules and deffuzification value ranges obtained from the training data, the next step is to test the value against 80 test data. The test results on 80 test data in real time system can be seen in TABLE VII. Based on the formula, the accuracy of test data using fuzzy model with integrated human machine interface system, PLC, database is 97.5%. Trials were conducted to analyze the accuracy and analyze the average processing time. The result of processing time from 80 test data in real time system can be seen in TABLE V.TABLE VII. O NLINE I DENTIFICATION R ESULTNo.Image DataTypeInput TrainingdataOutput ModelTrue False1 Oil Defect 20 20 02LackingDefectivedefect20 19 13Empty Feeddefect20 20 04 Normal 20 19 1From the data table process time 80 test data, obtained the average time for the identification of test data with integrated system of 1.150148 seconds. TABLE VIII shows data processing time identification of automatic fabric defects.TABLE VIII. I DENTIFICATION R ESULT OF D ATA P ROCESSING T IMETestingData ProcessTimeTestingDataProcessTime1 4.32 41 1.244042 3.04 42 0.733393 2.98 43 0.723564 2.88 44 0.707535 2.86 45 0.66115 … … … …Testing Data ProcessTimeTestingDataProcessTime20 2.99 60 0.8144321 1.76464 61 0.6926622 1.73764 62 0.7017123 1.47355 63 0.6778624 1.61301 64 0.6752625 1.74046 65 0.68613… … … …40 1.74136 80 0.69093In the existing process, there is an average time to do a recap of data manually by filling form defects. In this study, the form of defects replaced with a database of excel. Automatic data recap time can be seen in TABLE IX. From the data table recap time 80 test data, obtained the average time for the process of recording test data with an integrated system of 3.54 seconds. Based on the research that has been done, the comparison of processing time from the existing system that is still manual with the system of ideas that have been automated can be seen in TABLE X. Based on TABLE X, process time required to perform scanning process defects in the existing process by manual in the company is equal to 19.87 seconds, while using the automatic defect detection tool that has been integrated to be reduced by the process time of 1.16 seconds. For a manual defect recap in the company takes 13.5 seconds, while using an automated tool is reduced to 3.54 seconds. For the total overall activity, the existing process takes an average time of 33.37 seconds and for the proposed system takes 4.67 seconds. Thus, the decline in processing time for the all system amounted to 28.69 seconds.TABLE IX. R ECAP T IME O NLINE I DENTIFICATION R ESULTTesting Data ProcessTimeTestingDataProcessTime1 4.3241 3.912 3.04 42 3.773 2.98 43 3.834 2.88 44 3.925 2.86 45 3.75 … … … …20 2.99 60 3.9121 2.93 61 3.9222 2.99 62 3.8123 3.26 63 3.93TestingDataProcessTimeTestingDataProcessTime24 3.03 64 3.7425 3.09 65 3.87… … … …40 3.69 80 3.79TABLE X. C OMPARISON OF E XISTING AND P ROPOSED S YSTEMSNo. Activity Existing(Seconds)Proposed(Seconds)1 Defect Scanning 19.87 1.162 Defect Recap 13.50 3.54Process Time 33.374.68IV.C ONCLUSIONImage processing is required to improve accuracy and to reduce inspection time. The use of fuzzy logic method in image processing with GLCM extraction feature and cluster shade parameter, cluster prominence, and number of object is a step proposed in this research. Thus, fuzzy logic applied by using MATLAB software can give better result in detecting defects in fabric. The process time required to perform the scanning process of defects in the existing process by manual in the company is 19.87 seconds, while using the automatic defect detection tool that has been integrated to be reduced with a process time of 1.16 seconds. For a manual defect recap in the company takes 13.5 seconds, while using the automated tool is reduced to 3.54 seconds for the total activity, the existing process takes an average time of 34.08 seconds and for the proposed system takes 4.67 seconds. Thus, the decrease of process time for the all system is 28.69 seconds. Accuracy rate obtained in the training data of 95%, on the offline test data of 93.75% and on the real-time test data of 97.5%R EFERENCES[1]Mulato, F. Y., 2014. Klasifikasi Kematangan Buah Jambu Biji Merah(Psidium Guajava) dengan Menggunakan Model Fuzzy. In: SKRIPSI.Yogyakarta: Universitas Negeri Yogyakarta.[2]H. Rachmat, T. Mulyana, S.H. Hasan, M.R. Ibrahim, Design Selectionof In-UVAT Using MATLAB Fuzzy Logic Toolbox, Proceedings of SCDM 2016.[3]R.A. Anugraha, T. Mulyana, Monitoring and Controlling of EMS-SCADA via SMS Gateway, Proceedings of the 3rd International Conference on Information and Communication Technology 2015 (ICoICT 2015), pp. 615-619.[4]H. Rachmat, R.A. Anugraha, T. Mulyana, EMS-SCADA Design ofAC Usage on a Building, Proceeding 8th International Seminar on Industrial Engineering and Management 2015 (ISIEM 2015), PS45-49.[5]H. Rachmat, T. Mulyana, Website Design of EMS-SCADA for ACUsage on a Building, Proceedings of the 3rd International Conference on Information and Communication Technology 2015 (ICoICT 2015), pp. 17-22.[6] F.D.M. Fauzi, T. Mulyana, Z.I. Rizman, M.T. Miskon, W.A.K.W. Chek,M.H. Jusoh, Supervisory fertigation system using interactive graphical supervisory control and data acquisition system, International Journal on Advanced Science, Engineering and Information Technology, 2016, Vol. 6, Issue No. 4, pp. 489-494.[7]T. Mulyana, M.N.M. Than, D. Hanafi, A. Ali, Digital control designfor the boiler drum BDT921, Proceeding of Conf. on Industrial and Appl. Math., Indonesia 2010, pp. 257-260.[8]T. Mulyana, M.N.M. Than, D. Hanafi, I. Muhaimin, Simulation ofvarious PI controllers setting for boiler drums T11 QAD Model BDT 921, IndoMS International Conference on Mathematics and its Applications 2009 (IICMA 2009), UGM, Yogyakarta - Indonesia, Oct 12-13, 2009 034/Mulyana/IICMA/2009.[9]T. Mulyana, M.N.M. Than, N.A. Mustapha, Identification of heatexchanger QAD Model BDT 921 based on hammerstein-wiener model, Proceedings of the International Seminar on the Application of Science & Mathematics 2011 (ISASM 2011).[10]T. Mulyana, M.N.M. Than, D. Hanafi, A discrete time model of fourheat exchanger types HE158C, Proceedings of the 7th International Conference on Heat Transfer, Fluid Mechanics and Thermodynamics (HEFAT2010), 19-21 July 2010, Antalya, Turkey.[11]T. Mulyana, M.N.M. Than, D. Hanafi, A Discrete Time Model ofBoiler Drum and Heat Exchanger QAD Model BDT 921, Proceedings of the International Conference on Instrumentation, Control & Automation (ICA2009), October 20-22, 2009, Bandung, Indonesia, pp.154-159. [12]T. Mulyana, F.N. Suhaimi, D. Hanafi, M.N.M. Than, ARX Model ofFour Types Heat Exchanger Identification, Proceedings of the MUiCET 2011.[13]T. Mulyana, NNARX model structure for the purposes of controllerdesign and optimization of heat exchanger process control training system operation, AIP Conference Proceedings 1831, 020040 (2017).[14]T. Mulyana, M.N.M. than, Identification of Co Current Plate HeatExchanger Model HE158C, Proceedings of 2010 IEEE Student Conference on Research and Development (SCOReD 2010), 13 - 14 Dec 2010, Putrajaya, Malaysia.[15]T. Mulyana, A nonparametric system identification based on transientanalysis with plant process of heat exchanger as study case, International Journal of Innovation in Mechanical Engineering & Advanced Materials (IJIMEAM) Vol.1 (No.1). 2015. pp. 19-26 Published online: December 1, 2015, ISSN: 2477-541X.[16]T. Mulyana, J. Alhilman, E. Kurniawan, Data Analysis using SystemIdentification Toolbox of Heat Exchanger Process Control Training System, Proceedings of the 2016 Fourth International Conference on Information and Communication Technologies (ICoICT 2016), pp. 466-471.[17] D. C. Montgomery, Design and Analysis of Experiments, New York:John Wesley and Sons, 2013.[18]Wang, Li-Xing, A course in Fuzzy System And Control. Pretice Hall,1997.[19]M.P. Groover, Otomasi Sistem Produksi dan Computer-IntegratedMnufacturing.New Jersey:Pearson, 2001.。
中国联通本地综合承载与传送设备技术规范
中国联通本地综合承载与传送设备技术规范12中国联通公司发布中国联通本地综合承载传送网设备技术规范v1.0Technical Specification for China Unicom Local Unified Transport Network Equipment v1.0(NEQ)中国联通公司企业标准QB/CU 057- -1-18发布-1-18实施目次1范围............................................................................................ 错误!未定义书签。
2规范性引用文件 ....................................................................... 错误!未定义书签。
3定义、术语和缩略语 ............................................................... 错误!未定义书签。
4设备基本要求............................................................................ 错误!未定义书签。
4.1 设备基本要求..................................................................... 错误!未定义书签。
5通用技术规范............................................................................ 错误!未定义书签。
5.1 设备系统架构..................................................................... 错误!未定义书签。
光纤通信系统-第8章 数字光纤通信系统性能
第8章数字光纤通信系统性能为了满足全程全网各种通信的要求，需要对通信网在技术和经济相权衡的基础上进行规划和设计。
规划和设计包含了许多相关的因素，其中首要的因素是系统的传输性能。
光纤通信系统多属于数字系统，因此光纤通信系统的各种性能指标如误码、抖动、漂移、延时等也必须满足数字传输系统的要求。
本章将对这些系统性能指标进行分析研究。
8.1数字传输模型由于数字信号在传输过程中会受到各种损害，因此，在进行传输系统设计时，需要规定各部分设备性能，以保证把它们构成一个完整的传输系统时，能满足总的传输性能要求。
为此，需要确定一个合适的传输模型，以便对数字网的主要传输损伤的来源进行研究，确定系统全程性能指标，并根据传输模型对这些指标进行合理分配，从而为系统传输设计提供依据。
ITU-T提出了各种数字传输模型的建议。
模型分为：假设参考连接(HRX)，假设参考数字链路(HRDL)和假设参考数字段(HRDS)。
8.1.1假设参考连接(HRX)一个通信连接是通信网中从用户至用户，包括参与交换和传输的各个部分(如用户线，终端设备，交换机，传输系统等)的传输全程。
它是根据用户需要建立的各种机线设备的临时组合。
这些实际的连接有长有短，结构上有简单、复杂，传输的业务可能也不相同，难以进行传输质量的核算。
通常找出通信距离最长、结构最复杂、传输质量预计最差的连接作为传输质量的核算对象。
只要这种典型连接的传输质量能满足要求，那么通信距离较短，结构较简单的通信连接肯定能保证传输质量，因而引入了假设参考连接的概念。
假设参考连接(HRX)是以对总的性能进行研究的一个模型，从而便于形成各种标准和指标。
它是两个用户网络接口参考点T之间的全数字64Kbit/s连接，如图8.1所示。
它是标准最长HRX，全长定为27500km。
考虑到大国与小国不同，还考虑到国内长途电路与国际长途电路是同等质量的电路，因此不区分国内与国际部分各占多少长，只规定每个国内部分包含5段电路，国际部分包含4段电路，共有14段电路串联而成，两个LE间共12段电路。
康宁光通信数据中心主要产品速查手册说明书
数据中心主要产品速查手册数据中心创新质量服务康宁光通信—您身边的数据中心网络专家。
作为数据中心技术和创新的引领者，康宁光通信了解数据中心的特殊需求和挑战。
数据中心主要产品速查手册为您提供数据中心布线解决方案的最新产品信息和相关资源，便于快速查找。
具有较强的竞争优势、较低的总拥有成本，并支持下一代应用的演进路径是如今对数据中心光纤基础设施的基本要求。
康宁能够帮助您。
康宁的解决方案不仅能够实现高密度、低成本的10G 部署，而且可以提供向40G, 100G 乃至400G 最便捷的迁移。
目录传输性能/插入损耗并行光通信系统双芯光通信系统 EDGE8® 解决方案EDGE ™ 解决方案资源和工具了解更多内容，请访问我们的网站/cn/zh/products/communication-networks/applications/data-center.html传输性能/插入损耗*假设连接器损耗预算为1 dB配置基于8芯MTP®或基于12芯MTP的并行光通信解决方案只需按照以下几个简单的步骤4U高达288个MTP端口（基于8芯），2304芯4U高达288个MTP端口（基于12芯），3456芯12, 24, 48, 72, 96和144芯EDGE8 MTP适配器面板配置双芯光通信解决方案只需按照以下几个简单的步骤（方式一）。
高达288个MTP®端口（基于8芯），2304芯；高达1152 LC双工连接个MTP端口（基于12芯），3456芯；高达12, 24, 48, 72, 96和144芯配置双芯光通信解决方案只需按照以下几个简单的步骤（方式二）。
4U高达288个LC双工端口，576芯4U高达288个LC双工端口，576芯12, 24, 48, 72, 96和144芯EDGE8®解决方案EDGE8®配线箱 . . . . . . . . . . . . . . . . . . . . . . . . .10 EDGE8 MTP®主干光缆 . . . . . . . . . . . . . . . . . .11 EDGE8 MTP适配器面板 . . . . . . . . . . . . . . . .12 EDGE8 MTP-LC双工模块 . . . . . . . . . . . . . . .12 EDGE8 MTP-LC分支跳线 . . . . . . . . . . . . . . . .14 EDGE8 MTP PRO跳线 . . . . . . . . . . . . . . . . . .15集成尾套LC双工跳线 . . . . . . . . . . . . . . . . . . .16EDGE8®解决方案可旋转应力释放平台可调节安装支架顶部和底部光缆固定可转换极性集成尾套LC 免工具光缆固定夹理线管理器Overhead Distribution on Cable Trays8芯MTP PRO跳线阶梯型MTP®-LC 分支跳线等长型MTP®-LC 分支跳线 1:1配线标签卡内置防尘盖MTP-LC 模块集成光缆模块内置防尘盖MTP面板基于8芯主干光缆EDGE8解决方案光纤链路EDGE8®配线箱EDGE8®MTP ®主干光缆LSZH ™主干光缆备注：xxx=光缆长度，002-300米，从分支到分支长度以1米递增OFNP主干光缆EDGE8 MTP-LC 双工模块EDGE8® MTP ®适配器面板备注：LC 适配器带内置防尘盖，MTP 连接器不含导向针备注：带可更换极性内置防尘盖EDGE8® MTP ®-LC 双工集成光缆模块备注：xxx=MTP 分支长度，001-025米EDGE8® MTP ®-LC 分支跳线备注：阶梯分支类型详情参考AEN157；xxx=MTP 分支长度，001-006米备注：xxx=MTP 分支长度，001-060米阶梯型分支等长型分支EDGE8® MTP ® PRO 跳线备注：MTP PRO 连接器可现场改变极性和导向针，详情参考AEN151和AEN152集成尾套LC 双工跳线备注：集成尾套LC 双工跳线可现场转换极性，光缆外径2.0 mmEDGE™解决方案EDGE™配线箱 . . . . . . . . . . . . . . . . . . . . . . . . . .19 EDGE MTP®主干光缆 . . . . . . . . . . . . . . . . . . .20 EDGE MTP适配器面板 . . . . . . . . . . . . . . . . . .21 EDGE MTP-LC双工模块 . . . . . . . . . . . . . . . . .21 EDGE MTP-LC分支跳线 . . . . . . . . . . . . . . . . .22 EDGE MTP PRO跳线 . . . . . . . . . . . . . . . . . . .24集成尾套LC双工跳线 . . . . . . . . . . . . . . . . . . .25EDGE ™解决方案可旋转应力释放平台可调节安装支架顶部和底部光缆固定固定托盘可选免工具光缆固定夹理线管理器Overhead Distribution on Cable Trays12芯MTP PRO跳线阶梯型MTP®-LC分支跳线等长型MTP®-LC分支跳线基于12芯主干光缆1:1配线标签卡可转换极性集成尾套LC 内置防尘盖MTP-LC模块MTP 适配器面板EDGE 解决方案光纤链路EDGE™配线箱EDGE ™ MTP ®主干光缆LSZH ™主干光缆备注：xxx=光缆长度，002-300米，从分支到分支长度以1米递增OFNP 主干光缆EDGE ™ MTP ®适配器面板EDGE MTP-LC 双工模块*带可更换极性内置防尘盖备注：LC 适配器带内置防尘盖，MTP连接器含导向针EDGE ™ MTP ®-LC 分支跳线备注：阶梯分支类型详情参考AEN157；xxx=MTP 分支长度，001-006米* 类型4为等长型，分支长度150mmEDGE™ MTP®在并行通信中的应用应用：直连（有源设备之间直接连接）应用：互联（从有源设备连接到配线面板）应用：交叉连接（从配线面板连接到配线面板）备注：MTP/p=MTP/含导向针，MTP/n-p=MTP/不含导向针EDGE ™ MTP ® PRO 跳线备注：MTP PRO 连接器可现场改变极性和导向针，详情参考AEN151和AEN152集成尾套LC 双工跳线备注：集成尾套LC 双工跳线可现场转换极性，光缆外径2.0 mm资源和工具技术文章/白皮书/cn/zh/products/communication-networks/resources/articles.html材料清单生成工具/cn/zh/products/communication-networks/resources/bill-of-materials-tool.html购买渠道/cn/zh/products/communication-networks/how-to-buy.html网络安装合作伙伴/cn/zh/products/communication-networks/loyalty-programs.html电话: +86 21 5450 4888 • 传真: +86 21 5427 7898 • /cn/zh.html。
Recommendation ITU-T G.987.2
10-Gigabit-capable passive optical networks (XG-PON): Physical media dependent (PMD) layer specification
Recommendation ITU-T G.987.2
ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIERTRANSMISSION SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS DIGITAL TERMINAL EQUIPMENTS DIGITAL NETWORKS DIGITAL SECTIONS AND DIGITAL LINE SYSTEM General Parameters for optical fibre cable systems Digital sections at hierarchical bit rates based on a bit rate of 2048 kbit/s Digital line transmission systems on cable at non-hierarchical bit rates Digital line systems provided by FDM transmission bearers Digital line systems Digital section and digital transmission systems for customer access to ISDN Optical fibre submarine cable systems Optical line systems for local and access networks Access networks MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USERRELATED ASPECTS TRANSMISSION MEDIA CHARACTERISTICS DATA OVER TRANSPORT – GENERIC ASPECTS PACKET OVER TRANSPORT ASPECTS ACCESS NETWORKS
ITU-T G.983.2
INTERNATIONAL TELECOMMUNICATION UNIONITU-T G.983.2Implementers’Guide TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(17 February 2006) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKSImplementers’ Guide for I TU-T Rec. G.983.2(07/2005)ONT management and control interface specification for B-PONSummaryThis document is an Implementers' Guide for ITU-T Recommendation of G.983.2 (07/2005).SourceThis document was agreed by ITU-T Study Group 15 on 17 February 2006.ITU 2005All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.Table of Contents1.Introduction (1)2.Additions to existing sections of G.983.2 Rev 2. (1)2.1Additions to section (1)2.2Additions to section 5.2 (1)2.3Additions to section 5.3 (1)2.4Additions to section 6.1 (1)2.5Additions to section 6.2 (2)2.6Addition to section 7.1.3 (2)2.7Modification to section 9 (2)3.New sections of G.983.2 Rev 2 (3)IMPLEMENTERS’ GUIDE 1 FOR RECOMMENDATION G.983.2 ONT MANAGEMENT AND CONTROL INTERFACE SPECIFICATION FOR B-PONG.983.2 Rev. 2, OMCI Implementers’ Guide 1SummaryThis document contains informative auxiliary information for the 984.3 standard, aimed to clarify the support of Multimedia over Coax Alliance compliant interfaces.KeywordsB-PON, OMCI, Implemen ters’ Guide1.IntroductionThis Implementers’guide describes the ONT management and configuration interface (OMCI) for Multimedia over Coax Alliance compliant interfaces. Three new managed entities are defined, as well as several modifications to existing entities.*2.Additions to existing sections of G.983.2 Rev 2.2.1Additions to section2 AbbreviationsAdd the following abbreviationsMoCA Multimedia over Coax Alliance2.2Additions to section 5.2Add the following items to list:“PPTP MoCA UNI”2.3Additions to section 5.3Add the following items to the list:“MoCA Ethernet PM History DataMoCA Interface PM History Data”2.4Additions to section 6.1Add the following lines to Table 1.* As there are no published specifications of this interface currently, this material is being put forward as an implementer’s guide. The intention is that once such specifications are published, they will be considered for normative reference in G.983.2.2.5Additions to section 6.2Add the following figure and text at the end of the section.“The MoCA UNI managed entity relationship diagram is shown in Figure 31g.Figure 31g – Managed Entity relation di agram, MoCA UNI”2.6Addition to section 7.1.32.7Modification to section 9.3.New sections of G.983.2 Rev 2Add the following sections.7.3.122 Physical Path Termination Point MoCA UNIThis managed entity represents the points at the MoCA UNI in the ONT where physical paths terminate and physical path level functions (i.e., MoCA function) are performed.RelationshipsAn instance of this managed entity shall exist for each MoCA PPTP port on the ONT. Instances of this managed entity are created automatically by the ONT upon creation/deletion of a circuit pack that supports MoCA UNI functions.Figure 1 Schematic diagram of Loop 3Table X-c/G.983.2 - AVC list for Physical Path Termination Point MoCA UNITable X-d/G.983.2 - Alarm list for Physical Path Termination Point MoCA UNI7.3.123. MoCA Ethernet Performance Monitoring History DataThis managed entity supports the performance monitoring history data for the MoCA Ethernet interface.An instance of this managed entity may be created by the OLT for each instance of the MoCA PPTP managed entity.Table Y/G.983.2 Alarm list for MoCA Ethernet Performance Monitoring History Data B-PO N*This numbering is used with the associated Threshold Data B-PON managed entity. Threshold Data counter 1 indicates the 1st thresholded counter, etc.7.3.124. MoCA Interface Performance Monitoring History DataThis managed entity supports the performance Monitoring History Data for the MoCA interface.An instance of this managed entity may be created by the OLT for each instance of the MoCA PPTP managed entity.Table Z/G.983.2 Alarm list for MoCA Interface Performance Monitoring History Data B-PO N*This numbering is used with the associated Threshold Data B-PON managed entity. Threshold Data counter 1 indicates the 1st thresholded counter, etc.**Because these counters are in a multiple-entry table, and the thresholds are only a single-valued, the sum of counters in the table should be used as the trigger for the threshold AVC._______________。
同步数字传输系统测试方法简介
平均发送光功率
发送机发射的光功率与所传送的数据信号中的 “1”占的比例有关，“1”越多发射的光功率越 大。当传送的数据信号是伪随机序列时，“1” 和“0”大致各占一半，将这种情况下发送机耦 合到光纤s点的光功率定义为平均发送光功率。
SDH测试仪 TX RX 光功率计 S 被测设备 接收 发射
测试方法、注意事项
灵敏度、过载光功率测试环境
测试仪表为SDH测试仪、可变光衰减器、光功 率计。
SDH测试仪 RX TX 光可变衰减器 R
被测设备
发送
接收
光功率计 激光器过载光功率、灵敏度测试配置
灵敏度、过载光功率测试方法
1、由SDH测试仪发送STM－N的光信号，测试图案： 215－1，被测设备的输出光信号连接到测试仪的输入 端，2M支路端口环回，SDH测试仪上应无误码指示。 2、逐渐减少可变光衰减器衰减量，直到测试仪出现 误码，但不能大于规定的1×10－10。实际测试时间可 如下计算：1/（T×155.520Mb/s）＝1×10－10，计算 可得，T＝1.1分钟，为保证测试准确，取实际测试时 间为2分钟。 3、断开图中的R点，将光功率计的输入连接到可变光 衰减器的输出，测出此时的输出光功率即为过载光功 率。 4、重复测试三次，取其平均值作为最后的测试结果。
SDH测试仪 RX R
被测设备
发送 接收
TX
输入允许频偏、AIS信号比特率测试配置
光口输入允许频偏、输出AIS 频偏测试方法
由SDH测试仪发送STM－N的光信号，测试图案：215 －1，被测设备的输出光信号连接到测试仪的输入端， 2M支路端口环回，频偏为0时应无误码。 打开仪表频偏，增加频偏（正方向），直到产生误码； 再减少频偏，直到误码刚好消失，等待三分钟无误码， 记录下此时的正频偏。 增加频偏（负方向），直到产生误码；再减少频偏， 直到误码刚好消失，等待三分钟无误码，记录下此时的 负频偏。 将被测光板时钟设置为自由振荡工作方式，设备为ADM、 REG方式，再将SDH测试仪的发送信号断开，在SDH 测试仪上可直接读出AIS信号比特率 。
基于记忆去噪卷积自编码器的色织物缺陷检测
纺织高校基础科学学报基于记忆去噪卷积自编码器的色织物缺陷检测张宏伟1,2，张伟伟1，熊文博1，陆帅3，陈霞4（1.西安工程大学电子信息学院，陕西西安710048；2.浙江大学工业控制技术国家重点实验室，浙江杭州310027；3.北京理工大学理学院，北京100029；4.西安美术学院服装系，陕西西安710065）摘要：针对传统自编码器泛化能力弱导致色织物缺陷检测性能不佳的问题，提出一种记忆去噪卷积自编码器重构模型和残差分析的无监督色织物缺陷检测与定位方法。
首先，训练阶段仅利用无缺陷样本叠加椒盐噪声构建训练集。
接着，建立记忆去噪卷积自编码器重构模型。
然后，将训练集输入模型进行训练，使模型具有重构修复缺陷区域的能力。
最后，在检测阶段计算待测色织物图像和其对应的重构图像之间的残差，并对残差图像进行阈值分割和闭运算操作，实现色织物缺陷区域的检测和定位。
实验结果表明，提出的方法能有效重构色织物纹理，快速准确地检测和定位多种色织物的缺陷区域。
该方法无需缺陷样本和缺陷样本标记,仅通过记忆无缺陷样本特征来增强模型重构修复缺陷区域的能力,从而提高缺陷检测性能。
关键词：织物缺陷检测；色织物；无监督学习；自编码器；异常检测中图分类号：TS101.91；TP101.91文章编号：1006-8341（2022）02-064-08文献标识码：ADOI ：10.13338/j.issn.1006-8341.2022.02.009Defect detection of yarn -dyed fabric based on memorydenoising convolutional auto -encoderZHANG Hongwei 1,2，ZHANG Weiwei 1，XIONG Wenbo 1，LU Shuai 3，CHEN Xia 4(1.School of Electronic Information,Xi ’an Polytechnic University,Xi ’an 710048,China ；2.State Key Laboratory of Industrial Control Technology,Zhejiang University,Hangzhou 310027,China ；3.School of Science,Beijing Institute of Technology,Beijing 100029,China ；4.School of Clothing Department,Xi ’an Academy of Fine Arts,Xi ’an 710065,China)Abstract:Aiming at the problem of the weak generalization ability of traditional auto-encoder leading to poor perfor-mance of yarn-dyed fabric defect detection,a memory denoising convolutional auto-encoder reconstruction model and引文格式：张宏伟，张伟伟，熊文博，等.基于记忆去噪卷积自编码器的色织物缺陷检测［J ］.纺织高校基础科学学报，2022，35（2）：64-71.ZHANG Hongwei ，ZHANG Weiwei ，XIONG Wenbo ，et al.Defect detection of yarn-dyed fabric based on memory denoising convolu-tional auto-encoder ［J ］.Basic Sciences Journal of Textile Universities ，2022，35（2）：64-71.收稿日期：2021-11-13基金项目：国家自然科学基金（61803292）；陕西省科技厅面上项目（2019JM-263）；陕西省教育厅专项科研计划项目（17JK0577）；陕西省重点研发计划（2019SF-235）第一作者：张宏伟（1983—），男，西安工程大学副教授，博士，研究方向为纺织服装智能视觉检测。
JPEG图像编码标准
SOF0
SOF1 SOF2
0xFFC0
0xFFC1 0xFFC2
Baseline DCT
Extended sequential DCT Progressive DCT
SOF3
SOF5 SOF6 SOF7
0xFFC3
0xFFC5 0xFFC6 0xFFC7
Spatial (sequential) lossless
JPEG图像压缩编码算法
JPEG 2000简介
参考文献
§3.4.1
JPEG与JPEG图像
一、ISO/IEC JPEG (Joint Photographic Experts Group)简介 二、关于JPEG图像
A、参 考 文 献
一. 关于JPEG
• •
JPEG : Joint Photographic Experts Group 由ISO与IEC于1986年联合成立的一个专家委员会(WG1)， 其宪章(charter)是：
0xE0
0xE1 - 0xEF 0xDB 0xC0 0xC4 0xDA 0xD9
第三章 图形、图像与视频处理技术
JPEG图像格式简介 (cont.)
•
附表：JPEG定义的标记列表
Symbol (符号) Code Assignment (标记代码) Description (说明)
Start Of Frame markers, non-hierarchical Huffman coding
第三 图形、图像与视频处理技术 4
2013年9月10日
关于JPEG (cont.)
•
已经发布的标准有：
ISO/IEC 10918-1 | ITU-T Rec. T.81 : Requirements and guidelines ISO/IEC 10918-2 | ITU-T Rec. T.83 : Compliance testing
ITU-T-G.8132
Attention: Some or all of the material attached to this liaison statement may be subject to ITU copyright. In such a case this will be indicated in the individual document.Such a copyright does not prevent the use of the material for its intended purpose, but it prevents the reproduction of all or part of it in a INTERNATIONAL TELECOMMUNICATION UNIONCOM 15 – LS 2 – ETELECOMMUNICATIONSTANDARDIZATION SECTORSTUDY PERIOD 2005-2008English only Original: EnglishQuestion(s): 9/15Madeira, 26-30 November 2007LIAISON STATEMENTSource: ITU-T SG15 Q9/15 Title:T-MPLS Ring ProtectionLIAISON STATEMENTTo: IETF MPLS, CCAMP, PWE3 and L2VPNApproval:ITU-T SG15. Q9/15 meeting (Madeira, 26-30 November 2007)For: Information/comment Deadline: 11/2/2008 Contact:Ghani Abbas Ericsson, SwedenTel: +44 115 850 1011 Fax: +44 115 850 1061Email: Ghani.Abbas@SG15 Q9 has nearly completed its work on a recommendation for T-MPLS Ring Protection -G.8132. It is targeted to consent this new recommendation in the next SG15 plenary meeting scheduled for Feb., 2008.We have attached the latest draft for your information and comments.AbstractThis document contains the latest draft of G.8132 (T-MPLS Shared Protection Ring). It is the result of drafting based on wd18 and other contributions presented in the Q9/15 Madeira meeting in November 2007.Question(s): 9/15Meeting, date:Madeira, 26 – 30 November 2007Study Group: 15 Working Party: 3Intended type of document : WD18r1_ndSource: Editors G.8132Title:Draft ITU-T Recommendation G.8132 (T-MPLS shared protection ring)Contact:Huub van HelvoortHuawei Technologies Co., Ltd. P.R.ChinaTel: +31 36 5315076Email: hhelvoort@ Contact:Igor Umansky Alcatel-Lucent IsraelTel: +972 3 9202871Email: igor.umansky@CONTENTS1 Scope (5)6 Introduction (7)objectives (8)9 TM-SPRing - OAM model (11)9.1 Introduction (11)9.2 APS Process for T-MPLS SPRing (12)10 Architecturetypes (12)types (12)11 SwitchingTypes (13)12 Operationdetection (13)13 Failuretypes (13)14 Trafficsharing (13)14.1 Bandwidth14.2 Bandwidth and QoS considerations (13)14.3 Point-to-point and point-to-multipoint traffic (13)15 Automatic Protection Switching (APS) protocol (13)15.1 APS payload structure (15)15.2 APS protocol type (15)15.3 APS protocol operation (16)15.3.1 Ring node APS state (16)15.3.2 Ring node APS state transition rules (19)16 Transmission and acceptance of APS signals (22)avoidance (22)17 Misconnection17.1 Ring map and squelch table information (23)17.2 Squelching (23)assignment (23)18 Label19 Protection switching trigger mechanism (23)control (24)19.1 Manual19.2 Signal fail declaration conditions (24)20 APS Switch initiation criteria (24)control (24)20.1 Manual20.1.1 Commands not signaled on the APS protocol (24)20.1.2 Commands using the APS protocol (24)20.2 Automatically initiated commands (25)Appendix I (26)I.1 W rapping (26)I.2 S teering (29)I.3 W rapping protection for the p-t-mp connection example (29)Appendix II (31)scenarios (31)II.1 Referencetables (31)II.2 TransitionDraft ITU-T Recommendation G.8132T-MPLS Shared Protection Ring (TM-SPRing)Summary<Mandatory material>KeywordsT-MPLS, ring protection, wrapping, steering, APSIntroduction1ScopeThis Recommendation specifies T-MPLS Shared Protection Ring (TM-SPRing) protection switching mechanisms and the APS protocol to be applied to T-MPLS layer networks as described point-to-point as well as point-to-multipoint T-MPLS connections.2 ReferencesThe following ITU-T Recommendations and other references contain provisions, which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation[1]ITU-T Recommendation G.780 /Y.1351 (2004), Terms and definitions for synchronousdigital hierarchy (SDH) networks.[2]ITU-T Recommendation G.783 (2004), Characteristics of synchronous digital hierarchy(SDH) equipment functional blocks.[3]ITU-T Recommendation G.805 (2000), Generic functional architecture of transportnetworks[4]ITU-T Recommendation G.806 (2000), Characteristics of transport equipment –Description methodology and generic functionality.[5]ITU-T Recommendation G.841 (1998), Types and characteristics of SDH networkprotection architectures.[6]ITU-T Recommendation G.870/Y.1352 (2004), Terms and definitions for OpticalTransport Networks (OTN)[7]ITU-T Recommendation G.8114/Y.1373 (2007), T-MPLS OAM mechanisms[8]ITU-T Recommendation G.8121 (2006), Characteristics of Transport MPLS equipmentfunctional blocks.[9]ITU-T Recommendation G.8110.1 (2006), Architecture of Transport MPLS (T-MPLS)Layer Network.3Definitions<Check in ITU-T Terms and definitions database under http://www.itu.int/sancho/index.htm if the term is not already defined in another recommendation. It could be more consistent to refer to such a definition rather than redefine it>The terms used in the sections below are as those defined in G.780/Y.1351:3.1bidirectional protection switching3.2drop-and-continueThe terms used in the sections below are as those defined in G.805:3.33.4signal fail (SF)3.5trailThe terms used in the sections below are as those defined in G.806:3.6defect3.7failureThe terms used in the sections below are as those defined in G.870/Y.1352:3.8APS protocol: 1-phase3.9Protection class3.9.1Trail protection3.10Switch3.10.1Forced Switch3.10.2Manual Switch3.11Component3.11.1Bridge3.11.2Switch3.12Architecture3.12.1non-revertive protection switching3.13Signals3.13.1Traffic signal3.13.2Normal traffic signal3.13.3Unprotected traffic signal3.14Timers3.14.1Hold-off time3.14.2Wait-to-restore timeEditors’ note: add definition for ‘span’ term.4Abbreviations<Include all abbreviations used in this Recommendation>This Recommendation uses the following abbreviations:APS Automatic Protection SwitchingVerification CV ConnectivityEXER ExerciseSwitchFS ForcedLP Lockout of ProtectionLW Lockout of WorkingMEG Maintenance Entity GroupMEP Maintenance Entity PointMPLS MultiProtocol Label SwitchingSwitchMS ManualNR NorequestOAM Operation, Administration and Maintenance PDU Payload Data UnitSwitchingPS ProtectionRequestRR ReverseDegradeSD SignalFailSF SignalSFSSF ServerSPRing Shared Protection RingCircuitTMC T-MPLSPathTMP T-MPLSMPLST-MPLS TransportSectionTMS T-MPLSWTR Wait to Restore5ConventionsNone.6Introductionwhich is considered a client layer of the T-MPLS section layer.operation of TM-SPRing equipment is described in Recommendation G.8121.7Network objectivesThe following objectives shall be met:1)The T-MPLS Section layer protects against any failure that is detected by the T-MPLSsection OAM2)Protected entities: p-t-p and p-t-mp T-MPLS connections.3)Switch time: the completion time for protection against a single failure shall be less thanand no hold-off timer.Editors’ note: check for validity of this requirement.4)Traffic typesa) Normal traffic: this type of traffic must be protected against any single failure.b) Non-preemptable unprotected traffic: this type of traffic is not protected by the ringprotection scheme.NOTE – In the event of a failure on the ring, only the normal traffic, i.e., type a), is protected5)Hold-off time: to avoid protection switching cascade in different network layers when alower layer network protection mechanism is activated in conjunction with the T-MPLSlayer protection scheme. Usage of hold-off timers allows the lower layer to restore working traffic before the T-MPLS layer initiates a protection action.6)Wait to-restore time: to avoid flapping of the protection switching in case of unstablenetwork failure conditions.7)Extent of protectiona) For a single failure, the ring will restore all normal traffic that would be passingthrough the failed location.b) The ring should restore all normal traffic, if possible, under multiple failure conditions.8)APS protocol and algorithma) The switching protocol shall be able to accommodate as a minimum up to 127 nodes ona ring.b) The APS protocol and associated OAM functions shall accommodate the capability toupgrade the ring (node insertion / removal), limiting the possible impact on existingtraffic on the ring.c) All spans on a ring shall have equal priority in case of multiple failures.d) The APS protocol shall allow coexistence of multiple ring switch requests as a result ofcombination of failures and manual/forced request resulting in the ring segmenting intoseparate segments.e) The APS protocol must be reliable and robust enough to avoid any cases of missingprotection switch requests as well as wrong interpretation of a request.9)Traffic misconnections shall not be allowed when the protection switching event takesplace.10)Operation modes: Revertive switching shall be provided.11)Protection switching modes: bidirectional protection switching shall be supported.12)Manual control: The following externally initiated commands shall be supported: Lockoutof Working, Lockout of Protection, Forced Switch and Manual Switch, Exerciser andClear command.13)Switch initiation criteria: The following automatically initiated commands shall besupported: Signal Failure, Wait-To-Restore, Reverse Request and No Request.NOTE – Multiple ring protection schemes are for further study.8Functional model¾Normal (protected) traffic as well as non-preemptable (unprotected) traffic are supported.¾Add, drop, drop-and-continue, pass-through connections can be normal or unprotected.¾The functional model proposed in this document supports label swapping along the ring.¾Pass-through protection connections in the protection connection function are established only on a failure event, which prevents the creation of the closed loop for protection connections in normal conditions.The following symbols are used in Figure 8-1:•TMS – T-MPLS Section layer•TMSP – T-MPLS Section Protection sub-layer•TMSP_C – T-MPLS section protection sub-layer Connection function•TMP – T-MPLS Path layerEditors’ note: When the functional model will be introduced in G.8121 it shall be removed from this specification.Editors’ note: replace TMSP2fsh with TMSP_C- 10 -ITU-T\COM-T\COM15\LS\2E.DOCNUTTo/from TMP_TT or TMS/TMP_AFigure 8-1 – T-MPLS Shared Protection Ring functional model9 TM-SPRing - OAM model9.1 IntroductionEach ring port in each ring node is configured as a TMS TM-MEP (Maintenance Entity Point). Each pair of ports on a span, i.e. each pair of MEPs in adjacent nodes, forms a MEG (Maintenance Entity Group). So there are n MEGs if there are nspans on the ring.Figure 9-1/G.8132 – OAM Configuration for T-MPLS SPRingT-MPLS SPRing has only one level of OAM functionality. Figure 9-1/G.8132 details the OAM configuration with one MEG level. The MEPs monitor the state of the T-MPLS section between adjacent nodes using the OAM mechanism defined in G.8114/Y.1373. CV is used to check the continuity and connectivity between each pair of MEPs in a MEG.Figure 9-2/G.8132 – OAM Model for T-MPLS SPRingFigure 9-2/G.8132 describes the T-MPLS SPRing OAM model in a ring node. The T-MPLSSPRing process accomplishes the T-MPLS SPRing protection switching and OAM APS packets processing in each node.9.2 APS Process for T-MPLS SPRingWhen the MEP does not detect any defects it sends periodically APS packets in West and East direction, indicating no switch request. The destination node information in APS packets is the Node ID of the adjacent node in the West or the East direction.When a MEP detects a defect (i.e. SF), it will inform the T-MPLS SPRing process, and the T-MPLS SPRing process will generate CI_APS in the West and East directions, indicating the appropriate bridge request. The destination node information in APS packets is the Node ID of the node adjacent to the detected defect.When a MEP receives the APS packets it will send APS information (CI_APS) to the T-MPLS SPRing process, the process checks the destination node information in the APS information field. If the destination node information matched the receiving node ID, the node terminates the APS flow and processes the APS information. Otherwise, if the destination node information indicates other node ID and there is no higher priority local request, the APS information is transferred unaltered to the next node in the ring.10Architecture typesT-MPLS Shared Protection Ring consists of two counter-rotating rings, transmitting in opposite directions relative to each other. T-MPLS switched rings require only two server layer section connections for each span of the ring. Each server layer section connection carries both working and protection traffic (in a ring failure event).The Wrapping technique implies that the node that detects a failure sends a request through the APS protocol to the node adjacent to the failure. When the node detects a failure or receives a bridge request through APS protocol addressed to this node, normal traffic transmitted towards the failed span is switched to the opposite direction (away from the failure). This traffic travels the long way around the ring to the other switching node where it is switched back onto the working direction. The switching nodes restore normal traffic flow when the failure or APS protocol request is cleared. An example of wrapping is provided in Appendix I.1.10.2 SteeringThe Steering technique implies that the node that detects a failure sends a request through the APS protocol to the node adjacent to the failure and all nodes in the ring process this APS information.In case of p-t-p connections, for each affected connection the source node (that adds traffic to the ring) and the sink node (that drops the traffic from the ring) perform switching from working to the protection direction, and restore normal traffic flow when the failure or APS protocol request is cleared.An example of steering is provided in Appendix I.2.NOTE – Steering is for further study.NOTE – The p-t-mp connection protection by the steering mechanism is for further study.11Switching typesTM-SPRing supports only the bi-directional protection switching type. In bi-directional switching, both directions of the monitored T-MPLS section layer, including the affected direction and the unaffected direction, are switched to protection.12Operation TypesTM-SPRing supports only the revertive protection operation type, which implies that the service will always return to (or remain on) the working connection if the switch requests are terminated.If local protection switching requests that have been active previously now have become inactive, a local Wait to Restore state is entered. This state normally times out and becomes a No Request state and reverts back to the normal operation condition. The Wait to Restore timer is stopped if any local request of higher priority pre-empts this state.13Failure detectionLink faults are detected via the server layer’s SSF detection and the T-MPLS Section signal failure (SF) condition via CVv1 OAM. T-MPLS section OAM mechanisms are defined in Recommendation G.8114/Y.1373.14Traffic typessharing14.1 BandwidthThe bandwidth on each ring is shared so that part of ring capacity is guaranteed for the normal traffic and part is used for the protection traffic in case of failure on the ring. The protection part of the ring bandwidth rotating in one direction is used to carry the normal traffic from the ring rotating in other direction in case of failure. Part of ring bandwidth can also be dedicated to carry unprotected non-preemptable traffic.14.2 Bandwidth and QoS considerationsThe TM-SPRing protection mechanism provides for the connectivity restoration of the normal traffic affected by a ring failure. The protection mechanism itself does not distinguish between different types of QoS associated with the given connections. It is also not aware of the bandwidth allocated or guaranteed for the protected or unprotected connections.In the T-MPLS ring, in order to guarantee the bandwidth and QoS of the connections, normal or unprotected, traffic management and engineering measures should be taken. For example, the bandwidth and QoS parameters allocated for each protection connection can be equal to the bandwidth and QoS parameters of the associated working connection.NOTE – bandwidth and QoS parameters calculation and allocation for the normal and protection connections is out of scope of this Recommendation.14.3 Point-to-point and point-to-multipoint trafficBoth point-to-point and drop-and-continue point-to-multipoint T-MPLS connections can be protected by TM-SPRing.The APS protocol functionality as well as the node’s reaction on different protection switching requests in case of ring failure is identical for p-t-p and p-t-mp traffic.An example of p-t-mp traffic protection by wrapping is provided in Appendix I.3.15Automatic Protection Switching (APS) protocolThe TM-SPRing protection operation is controlled with the help of the T-MPLS Section OAM APS protocol. The APS processes in the individual nodes communicate by using T-MPLS section APS messages.The APS protocol is intended to carry the ring status information and APS requests, both automatic and externally generated commands, between the ring nodes.Each node on the ring shall be identified uniquely by assigning it a node ID. The maximum number of nodes on the ring supported by the APS protocol is 127. The node ID is independent of the order in which the nodes appear on the ring. The node ID is used to identity the source and destination nodes of each APS message.Each node has a ring map maintained by a management application. The ring map contains information about the sequence of the nodes around the ring. The method of configuring the nodes with the ring maps is out of scope of this recommendation.When no protection switches are active on the ring, each node dispatches periodically T-MPLS section OAM APS PDUs to the two adjacent nodes, indicating no switch request. When a node determines that a protection switching is required (see clause 17), it sends the appropriate bridge requests in both directions, i.e. West and East. See sub-clause 15.3 for a detailed description of the APS protocol operation.‘Destination node’ is a node that is adjacent to a node that identified a failed span. When a node that is not the destination node receives a bridge request and it has no higher priority local request (see clause 19), it transfers the APS information as received. In this way, the switching nodes can maintain direct APS protocol communication on the ring.Note that in the case of a bidirectional failure such as a cable cut, two nodes would detect the failure and send each other a bridge request in opposite directions.o In rings utilizing the wrapping protection, when the destination node receives the bridge request, it performs the bridge & switch from/to the working connections to/from the protection connection.o In rings utilizing the steering protection, when a ring switch is required, any node shall execute bridges and switches if its added/dropped traffic is affected by the failure. Determination of the affected traffic is performed by examining the APS bridge requests (indicating the nodesadjacent to the failure or failures) and the stored ring maps (indicating the relative position of the failure and the added traffic destined towards that failure).NOTE – Steering is for further study.When the failure has cleared and the WTR timer has expired, the nodes sourcing bridge requests will drop their respective bridge requests (tail end) and will source a bridge request carrying No Request code. The node receiving such a bridge request (head end) will drop its bridge & switch.A switch shall be initiated by one of the criteria specified in clause 19. A failure of the APS protocol or controller shall not trigger a protection switch.Ring switches can be preempted by higher priority bridge requests as defined in clause 19. For example, consider a ring switch that is active due to a manual switch request on the given span, and another ring switch is required due to a failure on another span. Then a ring bridge request will be generated, the former ring switch will be dropped, and the latter ring switch established.Multiple ring switches can exist in the ring, resulting in the ring being segmenting into two or more separate segments. This may happen when several bridge requests of the same priority exist in the ring due to multiple failures or external switch commands.Proper operation of the ring relies on all nodes having knowledge of the state of the ring (nodes and spans) so that nodes do not preempt a request unless they have a higher-priority request. In order to accommodate this ring state knowledge, during a bridge request the APS protocol shall be sent in both directions.15.1 APS payload structureThe APS-specific information is transmitted within specific fields in the APS OAM PDU structure defined in ITU-T Recommendation G.8114. In this version of the Recommendation 4 octets in theAPS PDU are used to carry APS-specific information. Note that in this version of the Recommendation, the TLV offset field has to be set to 0x04.The structure and field values for the four APS data octets are defined in Table 15-1.Table 15-1/G.8132 – TM-SPRing APS protocol payload structure1 2 3 487654321876543218765432187654321Destination node ID Source node ID Bridge request ReservedDestination Node ID: The destination node ID is set to the value of the node ID for which the APS request is destined. The destination node ID is always that of an adjacent node (except for thedefault APS PDU, see Clause 15.3). Valid destination node ID values are 1-127.Source node ID: The source node ID is set to the value of the node ID of the node generating theAPS request. Valid source node ID values are 1-127.Bridge Request code: A code consisting of four bits carrying the bridge request message from atail-end node to the head-end node requesting the head-end to perform a bridge of the normal traffic signals. Bridge request codes are specified in Table 15-2 below.Table 15-2/G.8132 – TM-SPRing APS protocol bridge request codesBits 4-1 (MSB … LSB) Condition, State orexternal RequestOrder ofpriority1 1 1 1 Lockout of Protection (LP) highest1 1 0 1 Forced Switch (FS)1 0 1 1 Signal Fail (SF)0 1 1 0 Manual Switch (MS)0 1 0 1 Wait-To-Restore (WTR)0 0 1 1 Exerciser (EXER)0 0 0 1 Reverse Request (RR) ÅÆ0 0 0 0 No Request NR lowest15.2 APS protocol typeThe protocol type for the TM-SPRing is a 1-phase protocol.Support of acknowledgement mechanism by the 1-phase APS protocol by means of Reverse Request code is described in clause 15.3.1/G.8132. This should be considered as the means of verification of proper operation of the APS protocol (e.g., alarm can be sent to management), but should not affect the protection switching operation.15.3 APS protocol operationThis subclause defines the rules to apply to each node participating in a single TM-SPRingalgorithm instance. The operations described hereafter are assumed to be performed by an APS controller. Each node of the ring contains an APS controller. Its purpose is to handle the inputparameters and provide output actions consistent with the rules described. Figure 15-1 illustrates the conceptual operation of a TM shared protection ring APS controller.Detected ExternallyIncoming failures initiatedprotocol protocol messagesswitching operationFigure 15-1/G.8132 – Conceptual TM Shared Protection Ring APS controller The following general rule applies:Rule G #1 – BRIDGE REQUEST VALIDATIONRule G #1a : The information contained in APS PDU, 3rd byte shall be considered as a bridge request if:– the 3rd byte bits indicate one of the bridge request codes.15.3.1 Ring node APS stateThere are three classes of ring node states: the idle state, the switching state, and the pass-through state.15.3.1.1 Idle stateA node is in the idle state when it is sourcing and receiving NR code to/from both directions. Rule I #1 – IDLE STATE SOURCED APS PDU:Rule I #1a : Any node in the idle state shall source the APS PDU bytes in both directions as given in Table 15-3.Table 15-3/G.8132 – APS PDU bytes’ values sourced in the idle state1st byte=Destination node ID 2nd byte=Source node ID 3rd byte =all 0 (NR)Until the node has knowledge of the ring map, it shall behave as per Rule I-S #3.NOTE – Signaling in the start-up state is for further study.Rule I #2 – IDLE STATE RECEIVED APS PDU: Any node in the idle state shall terminate APS PDU flow in both directions.15.3.1.2Switching stateA node not in the idle or pass-through states is in the switching state. This includes the default signaling status, e.g. node start-up, where there is no ring map available.Rule S #1 – SWITCHING STATE SOURCED APS PDU:Rule S #1a: Any node in the switching state shall source APS PDU bytes as shown in Table 15-4:Table 15-4/G.8132 – APS PDU bytes’ values sourced by a node in the switching state1st byte =Destination node ID2nd byte =Source node ID3rd byte =Bridge RequestRule S #1b – SINGLE BRIDGE REQUEST AT A NODE: Any node in the switching state, shall source a bridge request in both directions. Exceptions to this can occur when there are more than one switch requests active at a node.Rule S #1c - MULTIPLE BRIDGE REQUESTS AT A NODE: Whenever a node in the switching state terminates a new short-path bridge request from an adjacent node, of equal or higher priority than the bridge request it is currently executing, over the same span, it shall source a bridge request of the same priority on the corresponding long path. Whenever a node receives bridge requests on both short paths from its adjacent nodes, the long-path bridge request shall be signaled rather than the short-path reverse requests [See Figure 15-2 a]. This rule takes precedence over Rule S #1b in case of multiple bridge requests at the same node.Rule S #1d - MULTIPLE BRIDGE REQUESTS AT A NODE: Whenever a node detects a local condition requiring a ring switch or an externally initiated command for a ring switch applied at that node, it shall always source over the short path a short-path ring bridge request as long as the ring bridge request is not pre-empted by a higher priority bridge request [See Figure 15-2 b]. This rule takes precedence over Rule S #1c. Note that whenever a node receives in one direction a short-path ring bridge request on one side and detects Signal Fail or an externally initiated command on the other side, it shall signal the bridge request associated with that condition [see Figure 15-2 c)].。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Draft revised ITU-T Recommendation G.783
Characteristics of synchronous digital hierarchy (SDH)
equipment functional blocks
Summary
This Recommendation specifies both the components and the methodology that should be used in order to specify SDH functionality of network elements; it does not specify an individual SDH equipment as such.
This Recommendation forms part of a suite of Recommendations covering the full functionality of network equipment. Those Recommendations are ITU-T G.806 [13] (Conventions and Generic Equipment Functions), ITU-T G.783, ITU-T G.705 (PDH functions) [5], ITU-T G.781 [9] (Synchro-nization functions), G.784 (Management function) [10], ITU-T I.732 (ATM functions) and follows the principles defined in ITU-T G.803 [11].
This Recommendation specifies a library of basic building blocks and a set of rules by which they may be combined in order to describe a digital transmission equipment. The library comprises the functional building blocks needed to specify completely the generic functional structure of the Synchronous Digital Hierarchy. In order to be compliant with this Recommendation, equipment needs to be describable as an interconnection of a subset of these functional blocks contained within this Recommendation. The interconnections of these blocks should obey the combination rules given.
The specification method is based on functional decomposition of the equipment into atomic, and compound functions. The description is generic and no particular physical partitioning of functions is implied. The input/output information flows associated with the functional blocks serve for defining the functions of the blocks and are considered to be conceptual, not physical.
Not every atomic function defined in this Recommendation is required for every application. Different subsets of atomic functions may be assembled in different ways according to the combination rules given in this Recommendation to provide a variety of different capabilities. Network operators and equipment suppliers may choose which functions must be implemented for each application.
_____________。