(CHS)Inversion of Control Containers and the Dependency Injection pattern
惠普彩色激光打印机 Pro M454 和惠普彩色激光多功能一体机 Pro M479 维修手册说明书
Table -1 Revision history Revision number 1
Revision date 6/2019
Revision notes HP LaserJet Pro M454 HP LaserJet Pro MFP M479 Repair manual initial release
Additional service and support for HP internal personnel HP internal personnel, go to one of the following Web-based Interactive Search Engine (WISE) sites: Americas (AMS) – https:///wise/home/ams-enWISE - English – https:///wise/home/ams-esWISE - Spanish – https:///wise/home/ams-ptWISE - Portuguese – https:///wise/home/ams-frWISE - French Asia Pacific / Japan (APJ) ○ https:///wise/home/apj-enWISE - English ○ https:///wise/home/apj-jaWISE - Japanese ○ https:///wise/home/apj-koWISE - Korean ○ https:///wise/home/apj-zh-HansWISE - Chinese (simplified)
Find information about the following topics ● Service manuals ● Service advisories ● Up-to-date control panel message (CPMD) troubleshooting ● Install and configure ● Printer specifications ● Solutions for printer issues and emerging issues ● Remove and replace part instructions and videos ● Warranty and regulatory information
计算机术语的英文缩写
小隐的博客Posted on 2007-01-08 22:05 小隐任行阅读(1441) 评论(3)编辑收藏所属分类: 编程资料3DNOW！-AMD公司开发的多媒体扩展指令集(共有27条指令)3G 第三代移动通信业务A/D Analog/Digital 模拟/数字AB Address Bus 地址总线AC Alternating Current 交流电AC×97 Intel推荐的音频电路系统标准AC-3 由Dolby实验室制定的一个音频标准ACPI Advanced Configuration and Power Interface 高级配置和电源管理界面ACS Accounting Control System 记帐管理系统(Univac公司)[统计控制系统]Adaptive Computer System 自适应计算机系统Advanced Connectivity System 先进布线系统Alternating Current Synchronous 交流同步Automatic Coding System 自动编码系统ActiveX ActiveX 微软倡导的ActiveX 网络化多媒体对象技术ADCCP 高级数据通信控制规程ADO ActiveX Data Objects Microsoft的一种新的数据访问模型ADP Automatic Data Processing 自动数据处理ADPCM 自适应音频脉冲编码ADSL Asymmetrical Digital Subscriber Loop 非对称数字用户环线Analog to Digital Simulation Language 模-数模拟语言Asymmetric digital Subscriber Line 异步数字用户线ADTS 抽象数据类型Automated Data and Telecommunications Service 自动数据和远程通信服务AGP Accelerated Graphics Port 加速图形接口AI Artificial Intelligence 人工智能ALI Asynchronous Line Interface 异步线路接口Automatic Location Identification 自动位置识别ALT Alternate Key 备用键Automatic Line Test 线路自动测试ALU -Arithmetic and Logic Unit 算术与逻辑部件[运算器,算术逻辑单位]AMD -Advanced Micro Device (美国)AMD公司(生产半导体及芯片)-Air Movement Data 空气运动数据-Analog Memory Device 模拟存储器件-Associative Memory Data 相联存储数据-Associative Memory Device 相联存储器件-AMI Access Method Interface 存取方法接口-Alternate Mark Inversion 传号交替变换-American MIcro system 美国微型系统AMR -Audio/Modem Riser 声音、调制解调器插卡-Arithmetic Mask Register 运算屏蔽寄存器-Automatic Message Recording 自动信息记录-Automatic Message Registering 自动信息[报文]挂号[登记]AN -Access Network 接入网ANSI -American National Standards Institute 美国国家标准协会[美国国家标准局]AOL -American On-Line 美国在线服务公司-All On-Line 全部联机APC -Adaptive Predictive Coding 自适应预测编码(法，技术)-Angular Position Counter 角位置计数器-Associative Processor Controller 相联处理机控制器-Automatic Peripheral Control 自动外(围)设(备)控制(器)-Automatic Program Control 自动程序控制API -Application Program Interface 应用程序接口[应用程式界面]APM -Advanced Power Management 高级电源管理-Automatic Predictive Maintenance 自动预测性维护-Automatic Programming Machine 自动程序设计机APNIC -亚太互联网络信息中心APPC -Advanced Program to Program Communications 先进的程序间通信技术[方法,(子)系统,协议,程序]-Automatic Power Plant Checker 电源设备自动检验器APTC -美国的Sylvan授权考试中心ARPA -Advanced Research Project Agency 高级研究计划局[(美国)高等研究计划署]ARX -Automatic Retransmission eXchange 自动重发交换机ASCII -American Standard Code for Information Interchange 美国信息交换标准代码ASP Active Server Pages 动态网页应用服务提供商ATL Active Task List 有效任务表Active Time List 有效时间表Analog Transmission Line 模拟传输线路ActiveX Template Library ActiveX 模板库Application Terminal Language 应用终端语言Artificial Transmission Line 仿真传输线Automatic TeLling 自动出纳ATM Asynchronous Transfer(Transmission) Mode 异步传输模式Automatic Teller Machine 自动取款[出纳]机Auxiliary Tape Memory 辅助磁带存储器ATX 一种新的PC主板架构规范A VGA Accelerated Video Graphics Array 加速的视频图形阵列显示卡A VI Audio Video Interlaced Video for windows 的多媒体文件格式BASIC Beginner's All-purpose Symbolic Instruction Code 初学者通用符号指令码BBL Be Back Later 稍候便回BBS Bulletin Board System 电子布告栏系统BCD Binary-Coded Decimal 二～十进制码BDE Borland Database Engine Borland的数据库引擎BGA Ball Grid Array 球栅阵列(组件)BGP 边界网关协议BIOS Basic Input/Output System 基本输入输出系统BLOBs 很大的二进制数据块BNC 同轴电缆接插件BO Back Orifice 后门(一种黑客程序)BPL Borland Package LibraryBps Bytes Per Second 比特每秒bps Bits Per Second 位每秒BRI Basic Rate Interference 基本速率干扰BTB Branch Target Buffer 分支目标缓冲器CA Certificate AuthorityCable TV 有线电视CAD Computer Aided Design 计算机辅助设计CAE Computer Aided Engineering 计算机辅助工程CAI Computer-Assisted Instruction 计算机辅助教学CAM Computer Aided Manufacturing 计算机辅助制造CAPP Computer-Aided Process Planning 计算机辅助工艺规划CAQ 计算机辅助质量管理CAS 数据盒存取站CASE Computer Aided Software Engineering 计算机辅助软件工程CASL Computer Assembly System Language CA T Computer-Aided Test 计算机辅助测试CAX Community Automatic eXchange 公用自动交换(机)CB Control Bus 控制总线CBD Central Business District 中央商务区CBE Computer-Based Education 计算机辅助教育CCITT 国际电报电话咨询委员会CCW Channel Command Word 通道命令字Channel Control Word 通道控制字China ComputerWorld 计算机世界(中国) CounterClockWise 逆时针方向(的)CD-DA Compact Disc Digital Audio 数字音频光盘CD-I Compact Disc Interactive 交互式CD CDMA Code Division Multiple Access 码分多路访问(通信)CD-R Compact Disc Recordable 一次性可写入光盘CD-ROM Compact Disc Read-Only Memory 光盘只读存储器CD-RW CD-ReWritable 可重复擦写光盘CE Call Entry 调用入口Channel End 通道传送结束[通道末端]Chip Enable 芯片启动Circular Error 循环误差Clear Entry 清除输入Common Emitter 共射极Communication Equipment 通信设备Computer Engineer 计算机工程师CEO Chief Executive Officer 执行总裁Chip Enable Output 芯片启用(使能)输出全面电子化办公室CERNet China Education and Research Computer Network 中国教育和科研计算机网络CES Communication Engineering Standard 通信工程标准(日本)Computer Education System(s) 计算机教育系统Consumer Electronics Show 家用[日用]电子产品展览CGA 彩色图形适配器CGI Common Gateway Interface 公共网关接口Computer Graphics Interface 计算机图形接口CHINAMDN 公用移动数据通信网CHS CHaracterS 字符Cylinders, Heads, Sectors 柱面数、磁头数、每柱面扇区数CIA Communication Interface Adaptor 通信接口适配器Communication Interrupt Analysis 通信中断分析Computer Industry Association 计算机工业协会Computers Interface Adaptor 计算机接口适配器the Central Intelligence Agency of the U.S. 中央情报局CIMS Computer-Integrated Manufacturing System 计算机集成制造系统CIP Catalog(u)ing In Publication 预编目录,出版过程中编目Commercial Instruction Processor 商用指令处理机Communication Interrupt Program 通信中断程序Console Interface Program 控制台接口程序CISC Complex Instruction Set Computer 复杂指令集(系统)计算机CIT Cambridge Information Technology 剑桥信息技术CIX Commercial Internet Exchange 商业Internet交换中心CJK China-Japan-Korea 中日韩CMI Computer-Management Instruction 计算机管理教学CMM Commission for Maritime[Marine] Meteorology 海洋气象委员会［联合国］Computerized Modular Monitoring 计算机化组件监控Controllable Memory Module 可控存储组件CMOS Complementary Metal Oxide Semiconductor 互补金属氧化物半导体CNN 美国有线新闻网络（以提供即时电视新闻报导而闻名）CNNIC China Internet Network Information Center 中国互联网络信息中心CODEC 多媒体数字信号编解码器COFF Common Object File Format 公用目标[对象]文件格式COM Component Object Model 组件对象模型Commercial organizations [域]商业组织,公司Check Operations Manual 检验操作手册COMmand 命令COMmon compiler 公共编译程序COMmon function (Logic Block), 公用功能(逻辑块)；公共操作COMmunications 通信Commutator 整流子，换向器，转接器COMpiler 编译COMDEX Computer Distributor Exph 计算机分销商展览CORBA Common Object Request Broker Architecture (OOP)公用对象请求代理(调度)程序体系结构CPU Central Processing Unit 中央处理器CRC Cyclic Redundancy Check 循环冗余校验法[循环冗余核对]CREF Cross REFerence 相互参照[交叉参照] CRM Customer Relationship Management 客户关系管理CRT Cathode-Ray Tube 阴极射线管CSP Communication Scanner Processor 通信扫描处理器Coder Sequential Pulse 编码器顺序脉冲Commercial Subroutine Package 商用子例行程序包Completely-Self-Protected 全自保护Control Setting Panel 控制参数设定板Control Signal Processor 控制信号处理机CSP/AD Cross System Product/Application Development 跨系统(程序)产品/应用软件开发程序CSP/AE Cross System Product/Application Execution 跨系统(程序)产品/应用软件执行程序CSS Communication SubSystem (In 9370, some features which provide some functions equivalent to NCP function.) 通信子系统低温存储系统Common Support System 公用支援系统Computer Scheduling System 计算机调度系统Computer SubSystem 计算机子系统Computer System Simulation 计算机系统模拟Contact Start Stop 接触起停CSTNet China Science and Technology Network 中国科学技术网CTEC (Microsoft) Certified Technical Education Center 微软认证高级技术教育中心CTO Chief Technical Officer 首席技术执行官CUA Channel and Unit Address 通道和单元地址Common User Access 公共用户访问(程序) D.O.S Denial of ServiceDAC Digital-to-Analog Converter 数模转换器DAO Data Access Object 数据访问对象DB Data Base 数据库Data Bus 数据总线Data Bank, 库集，数据库，资料库Data Bit 数据位Dead Band, 静带死区DeciBel 分贝DBMS Data Base Management System 数据库管理系统DBS Data Base System 数据库系统DC Direct Current 直流电Device Context 设备描述表DCB Device Controller Block 设备控制块DCC 罗马数字700 直接电缆连接DCCC 罗马数字800DCD 数据载波检测DCE Data Communication Equipment 数据通信设备DCI 显示控制接口DCOM Distributed Component Object Model 分布式组件对象模型以前叫做“网络OLE”。
2010-26-EU-欧盟新排放指令
DIRECTIVESCOMMISSION DIRECTIVE 2010/26/EUof 31 March 2010amending Directive 97/68/EC of the European Parliament and of the Council on the approximation of the laws of the Member States relating to measures against the emission of gaseous and particulate pollutants from internal combustion engines to be installed in non-road mobile machinery(Text with EEA relevance)THE EUROPEAN COMMISSION, Having regard to the Treaty on the Functioning of the European Union,Having regard to Directive 97/68/EC of 16 December 1997 of the European Parliament and of the Council on the approxi mation of the laws of the Member States relating to measures against the emission of gaseous and particulate pollutants from internal combustion engines to be installed in non-road mobile machinery ( 1 ), and in particular Articles 14 and 14a thereof, Whereas:(1) Article 14a of Directive 97/68/EC sets out the criteria and the procedure for extending the period referred to in Article 9a(7) of that Directive. Studies carried out in accordance with Article 14a of Directive 97/68/EC show that there are substantial technical difficulties to comply with stage II requirements for professional use, multi- positional, hand-held mobile machinery in which engines of classes SH:2 and SH:3 are installed. It is therefore necessary to extend the period referred to in Article 9a(7) until 31 July 2013. (2) Since the amendment of Directive 97/68/EC in 2004, technical progress has been made in the design of diesel engines with a view to make them compliant with the exhaust emission limits for stages IIIB and IV. Electronically controlled engines, largely replacing me- chanically controlled fuel injection and control systems, have been developed. Therefore, the current general type- approval requirements in Annex I to Directive 97/68/EC should be adapted accordingly and general type-approval requirements for stages IIIB and IV should be introduced. (3) Annex II to Directive 97/68/EC specifies the technical details of the information documents that need to be submitted by the manufacturer to the type-approval authority with the application for engine type-approval. The details specified regarding the additional anti- pollution devices are generic and should be adapted to the specific after-treatment systems that need to be used to ensure that engines comply with exhaust emission limit stages IIIB and IV. More detailed information on the after-treatment devices installed on the engines should be submitted to enable type-approval authorities to assess the engine’s capability to comply with stages IIIB and IV.(4) Annex III to Directive 97/68/EC sets out the methodtesting the engines and determining their level of emissions of gaseous and particulate pollutants. The type-approval testing procedure of engines to demon strate compliance with the exhaust emission limits of stage IIIB and IV should ensure that the simultaneous compliance with the gaseous (carbon monoxide, hydro carbons, oxides of nitrogen) and the particulate emission limits is demonstrated. The non-road steady cycle (NRSC) and non-road transient cycle (NRTC) should be adapted accordingly. (5) Point 1.3.2 of Annex III to Directive 97/68/EC foreseesthe modification of the symbols (section 2.18 of Annex I), the test sequence (Annex III) and calculation equations (Appendix III to Annex III), prior to the introduction of the cold/hot composite test sequence. The type approval procedure to demonstrate compliance with the exhaust emission limits of stage IIIB and IV requires the intro duction of a detailed description of the cold start cycle. (6) Section 3.7.1 of Annex III to Directive 97/68/EC sets out the test cycle for the different equipment specifications. The test cycle under point 3.7.1.1 (specification A) needs to be adapted to clarify which engine speed needs to be used in the type approval calculation method. It is also necessary to adapt the reference to the updated version of the international testing standard ISO 8178-4:2007.( 1 ) OJ L 59, 27.2.1998, p. 1.(7) Section 4.5 of Annex III to Directive 97/68/EC outlines the emissions test run. This section needs to be adapted to take account of the cold start cycle. (8) Appendix 3 of Annex III to Directive 97/68/EC sets out the criteria for the data evaluation and calculation of the gaseous emissions and the particulate emissions, for both the NRSC test and the NRTC test set out in Annex III. The type approval of engines in accordance with stage IIIB and IV requires the adaptation of the calculation method for the NRTC test. (9) Annex XIII to Directive 97/68/EC sets out the provisions for engines placed on the market under a ‘flexible scheme’. To ensure a smooth implementation of stage IIIB, an increased use of this flexibility scheme may be needed. Therefore, the adaptation to technical progress to enable the introduction of stage IIIB compliant engines needs to be accompanied by measures to avoid that the use of the flexibility scheme may be hampered by notifi cation requirements which are no longer adapted to the introduction of such engines. The measures should aim at simplifying the notification requirements and the reporting obligations, and at making them more focused and tailored to the need for market surveillance authorities to respond to the increased use of the flexi bility scheme that will result from the introduction of stage IIIB. (10) Since Directive 97/68/EC provides for the type-approval of stage IIIB engines (category L) as from 1 January 2010 it is necessary to provide for the possibility to grant type approval from that date. (11) For reasons of legal certainty this Directive should enter into force as a matter of urgency. (12) The measures provided for in this Directive are in accordance with the opinion of the Committee estab lished in Article 15(1) of Directive 97/68/EC, HAS ADOPTED THIS DIRECTIVE: Article 1 Amendments to Directive 97/68/EC Directive 97/68/EC is amended as follows: 1. in Article 9a(7), the following subparagraph is added: ‘Notwithstanding the first subparagraph, an extension of the derogation period is granted until 31 July 2013, within the category of top handle machines, for professional use, multi- positional, hand-held hedge trimmers and top handle tree service chainsaws in which engines of classes SH:2 and SH:3 are installed.’;2. Annex I is amended in accordance with Annex I to this Directive;3. Annex II is amended in accordance with Annex II to this Directive;4. Annex III is amended in accordance with Annex III to this Directive;5. Annex V is amended in accordance to Annex IV to this Directive;6. Annex XIII is amended in accordance with Annex V to this Directive.Article 2Transitional provisionWith effect from the day following the publication of this Directive in the Official Journal, Member States may grant type-approval in respect of electronically controlled engines which comply with the requirements laid down in Annexes I, II, III, V and XIII to Directive 97/68/EC, as amended by this Directive.Article 3Transposition1. Member States shall bring into force the laws, regulations and administrative provisions necessary to comply with the Directive within 12 months after the publication of the Directive. They shall forthwith communicate to the Commission the text of those provisions.They shall apply those provisions from 31 March 2011.When Member States adopt those provisions, they shall contain a reference to this Directive or be accompanied by such a reference on the occasion of their official publication. Member States shall determine how such reference is to be made.2. Member States shall communicate to the Commission the text of the main provisions of national law which they adopt in the field covered by this Directive.Article 4Entry into forceThis Directive shall enter into force on the day following its publication in the Official Journal of the European Union .Article 5AddresseesThis Directive is addressed to the Member States. Done at Brussels, 31 March 2010. For the Commission The President José Manuel BARROSOANNEX IThe following section 8 is added to Annex I to Directive 97/68/EC:IIIBIVSTAGESANDFOR‘8. TYPEAPPROVALREQUIREMENTS8.1. This section shall apply to the type-approval of electronically controlled engines, which uses electronic control todetermine both the quantity and timing of injecting fuel (hereafter “engine”). This section shall apply irrespective of the technology applied to such engines to comply with the emission limit values set out in sections 4.1.2.5 and 4.1.2.6 of this Annex.8.2. DefinitionsFor the purpose of this section, the following definitions shall apply:8.2.1. “emission control strategy” means a combination of an emission control system with one base emission controlstrategy and with one set of auxiliary emission control strategies, incorporated into the overall design of an engine or non-road mobile machinery into which the engine is installed.8.2.2. “reagent” means any consumable or non-recoverable medium required and used for the effective operation of theexhaust after-treatment system.8.3. Generalrequirements8.3.1. Requirements for base emission control strategy8.3.1.1. The base emission control strategy, activated throughout the speed and torque operating range of the engine,shall be designed as to enable the engine to comply with the provisions of this Directive8.3.1.2. Any base emission control strategy that can distinguish engine operation between a standardised type approvaltest and other operating conditions and subsequently reduce the level of emission control when not operating under conditions substantially included in the type approval procedure is prohibited.8.3.2. Requirements for auxiliary emission control strategy8.3.2.1. An auxiliary emission control strategy may be used by an engine or a non-road mobile machine, provided thatthe auxiliary emission control strategy, when activated, modifies the base emission control strategy in response toa specific set of ambient and/or operating conditions but does not permanently reduce the effectiveness of theemission control system:(a) where the auxiliary emission control strategy is activated during the type approval test, sections 8.3.2.2 and8.3.2.3 shall not apply;(b) where the auxiliary emission control strategy is not activated during the type approval test, it must bedemonstrated that the auxiliary emission control strategy is active only for as long as required for thepurposes identified in section 8.3.2.3.8.3.2.2. The control conditions applicable to this section are all of the following:(a) an altitude not exceeding 1 000 metres (or equivalent atmospheric pressure of 90 kPa);(b) an ambient temperature within the range 275 K to 303 K (2 °C to 30 °C);(c) the engine coolant temperature above 343 K (70 °C).Where the auxiliary emission control strategy is activated when the engine is operating within the control conditions set out in points (a), (b) and (c), the strategy shall only be activated exceptionally.8.3.2.3. An auxiliary emission control strategy may be activated in particular for the following purposes:(a) by onboard signals, for protecting the engine (including air-handling device protection) and/or non-roadmobile machine into which the engine is installed from damage;(b) for operational safety and strategies;(c) for prevention of excessive emissions, during cold start or warming-up, during shut-down;(d) if used to trade-off the control of one regulated pollutant under specific ambient or operating conditions, formaintaining control of all other regulated pollutants, within the emission limit values that are appropriate forthe engine concerned. The purpose is to compensate for naturally occurring phenomena in a manner thatprovides acceptable control of all emission constituents.8.3.2.4. The manufacturer shall demonstrate to the technical service at the time of the type-approval test that theoperation of any auxiliary emission strategy complies with the provisions of section 8.3.2. The demonstration shall consist of an evaluation of the documentation referred to in section 8.3.3.8.3.2.5. Any operation of an auxiliary emission control strategy not compliant with section 8.3.2 is prohibited.8.3.3. Documentation requirements8.3.3.1. The manufacturer shall provide an information folder accompanying the application for type-approval at thetime of submission to the technical service, which ensures access to any element of design and emission control strategy and the means by which the auxiliary strategy directly or indirectly controls the output variables. The information folder shall be made available in two parts:(a) the documentation package, annexed to the application for type-approval, shall include a full overview of theemission control strategy. Evidence shall be provided that all outputs permitted by a matrix, obtained fromthe range of control of the individual unit inputs, have been identified. This evidence shall be attached to theinformation folder as referred to in Annex II;(b) the additional material, presented to the technical service but not annexed to the application for type-approval, shall include all the modified parameters by any auxiliary emission control strategy and theboundary conditions under which this strategy operates and in particular:(i) a description of the control logic and of timing strategies and switch points, during all modes ofoperation for the fuel and other essential systems, resulting in effective emissions control (such asexhaust gas recirculation system (EGR) or reagent dosing);(ii) a justification for the use of any auxiliary emission control strategy applied to the engine, accompanied by material and test data, demonstrating the effect on exhaust emissions. This justification may be basedon test data, sound engineering analysis, or a combination of both;(iii) a detailed description of algorithms or sensors (where applicable) used for identifying, analysing, or diagnosing incorrect operation of the NO x control system;(iv) the tolerance used to satisfy the requirements in section 8.4.7.2, regardless of the used means.8.3.3.2. The additional material referred to in point (b) of section 8.3.3.1 shall be treated as strictly confidential. It shallbe made available to the type-approval authority on request. The type-approval authority shall treat this material as confidential.ofoperationNO x control measures8.4. Requirementstoensurecorrect8.4.1. The manufacturer shall provide information that fully describes the functional operational characteristics of theNO x control measures using the documents set out in section 2 of Appendix 1 to Annex II and in section 2 of Appendix 3 to Annex II.8.4.2. If the emission control system requires a reagent, the characteristics of that reagent, including the type of reagent,information on concentration when the reagent is in solution, operational temperature conditions and reference to international standards for composition and quality must be specified by the manufacturer, in section 2.2.1.13 of Appendix 1 and in section 2.2.1.13 of Appendix 3 to Annex II.8.4.3. The engine emission control strategy shall be operational under all environmental conditions regularly pertainingin the territory of the Community, especially at low ambient temperatures.8.4.4. The manufacturer shall demonstrate that the emission of ammonia during the applicable emission test cycle ofthe type approval procedure, when a reagent is used, does not exceed a mean value of 25 ppm.8.4.5. If separate reagent containers are installed on or connected to a non-road mobile machine, means for taking asample of the reagent inside the containers must be included. The sampling point must be easily accessible without requiring the use of any specialised tool or device.8.4.6. Use and maintenance requirements8.4.6.1. The type approval shall be made conditional, in accordance with Article 4(3), upon providing to each operator ofnon-road mobile machinery written instructions comprising the following:(a) detailed warnings, explaining possible malfunctions generated by incorrect operation, use or maintenance ofthe installed engine, accompanied by respective rectification measures;(b) detailed warnings on the incorrect use of the machine resulting in possible malfunctions of the engine,accompanied by respective rectification measures;(c) information on the correct use of the reagent, accompanied by an instruction on refilling the reagentbetween normal maintenance intervals;(d) a clear warning, that the type-approval certificate, issued for the type of engine concerned, is valid only whenall of the following conditions are met:(i) the engine is operated, used and maintained in accordance with the instructions provided;(ii) prompt action has been taken for rectifying incorrect operation, use or maintenance in accordance with the rectification measures indicated by the warnings referred to in point (a) and (b);(iii) no deliberate misuse of the engine has taken place, in particular deactivating or not maintaining an EGR or reagent dosing system.The instructions shall be written in a clear and non-technical manner using the same language as is used in the operator’s manual on non-road mobile machinery or engine.8.4.7. Reagent control (where applicable)8.4.7.1. The type approval shall be made conditional, in accordance with the provisions of section 3 of Article 4, uponproviding indicators or other appropriate means, according to the configuration of the non-road mobile machinery, informing the operator on:(a) the amount of reagent remaining in the reagent storage container and by an additional specific signal, whenthe remaining reagent is less than 10 % of the full container’s capacity;(b) when the reagent container becomes empty, or almost empty;(c) when the reagent in the storage tank does not comply with the characteristics declared and recorded insection 2.2.1.13 of Appendix 1 and section 2.2.1.13 of Appendix 3 to Annex II, according to the installedmeans of assessment.(d) when the dosing activity of the reagent is interrupted, in cases other than those executed by the engine ECUor the dosing controller, reacting to engine operating conditions where the dosing is not required, providedthat these operating conditions are made available to the type approval authority.8.4.7.2. By the choice of the manufacturer the requirements of reagent compliance with the declared characteristics andthe associated NO x emission tolerance shall be satisfied by one of the following means:(a) direct means, such as the use of a reagent quality sensor.(b) indirect means, such as the use of a NO x sensor in the exhaust to evaluate reagent effectiveness.(c) any other means, provided that its efficacy is at least equal to the one resulting by the use of the means ofpoints (a) or (b) and the main requirements of this section are maintained.’ANNEX IIAnnex II to Directive 97/68/EC is amended as follows:1. Section 2 of Appendix 1 is replaced by the following:POLLUTIONAIRAGAINSTTAKEN‘2. MEASURESyes/no(*)............................................................................................................gases:recyclingcrankcase2.1. Deviceforcoverednotbyheading)ifanother(ifanti-pollutiondevices2.2. Additionalandany,(*)yes/noconverter:2.2.1. Catalytic.......................................................................................................................................................................................2.2.1.1. Make(s):........................................................................................................................................................................................2.2.1.2. Type(s):converterselements................................................................................................................andcatalytic2.2.1.3. Numberofconverter(s):...............................................................................................thecatalyticofandvolume2.2.1.4. Dimensions-........................................................................................................................................................action:ofcatalytic2.2.1.5. Typeprecious........................................................................................................................................metals:of2.2.1.6. Totalchargeconcentration:...........................................................................................................................................................2.2.1.7. Relative.....................................................................................................................................material):and2.2.1.8. Substrate(structure...............................................................................................................................................................................2.2.1.9. Celldensity:2.2.1.10. Type of casing for the catalytic converter(s): .................................................................................................................2.2.1.11. Location of the catalytic converter(s) (place(s) and maximum/minimum distance(s) from engine): ............2.2.1.12. Normal operating range (K): ................................................................................................................................................2.2.1.13. Consumable reagent (where appropriate): .......................................................................................................................2.2.1.13.1. Type and concentration of reagent needed for catalytic action: .............................................................................2.2.1.13.2. Normal operational temperature range of reagent: ......................................................................................................2.2.1.13.3. International standard (where appropriate): ....................................................................................................................2.2.1.14. NO x sensor: yes/no (*)(*)yes/nosensor:2.2.2. Oxygen.......................................................................................................................................................................................2.2.2.1. Make(s):............................................................................................................................................................................................2.2.2.2. Type:.....................................................................................................................................................................................2.2.2.3. Location:(*)yes/noinjection:2.2.3. Airetc.):.........................................................................................................................................pump,2.2.3.1. Type(pulseair,air(*)yes/no2.2.4. EGR:etc.):pressure,........................................................................2.2.4.1. Characteristicspressure/low(cooled/uncooled,high(*)yes/no2.2.5. Particulatetrap:particulate.........................................................................................................thetrap:capacityof2.2.5.1. Dimensionsandparticulatetrap:.........................................................................................................................theandof2.2.5.2. Typedesignengine):..................................................................fromdistance(s)2.2.5.3. Locationand(place(s)maximum/minimumdescriptionand/ordrawing:regeneration,............................................................................ofor2.2.5.4. Methodsystempressure(kPa)and..................................................................................range:2.2.5.5. Normal(K)operatingtemperature(*)yes/nosystems:2.2.6. Otheroperation:...................................................................................................................................................and2.2.6.1. Description___________(*) Strike out what does not apply.’2. Section 2 of Appendix 3 is replaced by the following:POLLUTIONAGAINSTAIRTAKEN‘2. MEASURESyes/no(*)............................................................................................................gases:crankcase2.1. Deviceforrecyclingcoverednotbyheading)ifanotherany,anti-pollutiondevices(ifand2.2. Additional(*)yes/noconverter:2.2.1. Catalytic.......................................................................................................................................................................................2.2.1.1. Make(s):........................................................................................................................................................................................2.2.1.2. Type(s):and................................................................................................................converterselementscatalyticof2.2.1.3. Numberconverter(s):...............................................................................................thecatalyticofandvolume2.2.1.4. Dimensions-........................................................................................................................................................action:ofcatalytic2.2.1.5. Typeprecious........................................................................................................................................metals:of2.2.1.6. Totalchargeconcentration:...........................................................................................................................................................2.2.1.7. Relative.....................................................................................................................................material):and2.2.1.8. Substrate(structure...............................................................................................................................................................................2.2.1.9. Celldensity:2.2.1.10. Type of casing for the catalytic converter(s): .................................................................................................................2.2.1.11. Location of the catalytic converter(s) (place(s) and maximum/minimum distance(s) from engine): ............2.2.1.12. Normal operating range (K) .................................................................................................................................................2.2.1.13. Consumable reagent (where appropriate): .......................................................................................................................2.2.1.13.1. Type and concentration of reagent needed for catalytic action: .............................................................................2.2.1.13.2. Normal operational temperature range of reagent: ......................................................................................................2.2.1.13.3. International standard (where appropriate): ....................................................................................................................2.2.1.14. NO x sensor: yes/no (*)yes/no(*)sensor:2.2.2. Oxygen.......................................................................................................................................................................................2.2.2.1. Make(s):............................................................................................................................................................................................2.2.2.2. Type:.....................................................................................................................................................................................2.2.2.3. Location:(*)yes/noinjection:2.2.3. Airetc.):.........................................................................................................................................pump,2.2.3.1. Type(pulseair,air(*)yes/no2.2.4. EGR:etc.):pressure,........................................................................2.2.4.1. Characteristicspressure/low(cooled/uncooled,high(*)yes/no2.2.5. Particulatetrap:particulate.........................................................................................................thetrap:capacityof2.2.5.1. Dimensionsandparticulatetrap:.........................................................................................................................theandof2.2.5.2. Typedesignengine):..................................................................fromdistance(s)2.2.5.3. Locationand(place(s)maximum/minimumdescriptionand/ordrawing:regeneration,............................................................................ofor2.2.5.4. Methodsystempressure(kPa)and..................................................................................range:2.2.5.5. Normal(K)operatingtemperature(*)yes/nosystems:2.2.6. Otheroperation:...................................................................................................................................................and2.2.6.1. Description___________(*) Strike out what does not apply.’。
计算机专业英语名词(缩写及翻译)
AAT（Average access time，平均存取时间）ABS（Auto Balance System，自动平衡系统）AM（Acoustic Management，声音管理）ASC（Advanced Size Check，高级尺寸检查）ASMO（Advanced Storage Magneto-Optical，增强形光学存储器）AST（Average Seek time，平均寻道时间）ATA（Advanced Technology Attachment，高级技术附加装置）ATOMM（Advanced super Thin-layer and high-Output Metal Media，增强形超薄高速金属媒体）BBS（BIOS Boot Specification，基本输入/输出系统启动规范）BPI（Bit Per Inch，位/英寸）bps（bit per second，位/秒）bps（byte per second，字节/秒）CAM（Common Access Model，公共存取模型）CF（CompactFlash Card，紧凑型闪存卡）CHS（Cylinders、Heads、Sectors，柱面、磁头、扇区）CSS（Common Command Set，通用指令集）DBI（dynamic bus inversion，动态总线倒置）DIT（Disk Inspection Test，磁盘检查测试）DMA（Direct Memory Access，直接内存存取）DTR（Disk Transfer Rate，磁盘传输率）EIDE（enhanced Integrated Drive Electronics，增强形电子集成驱动器）eSATA（External Serial ATA，扩展型串行ATA）FDB（fluid-dynamic bearings，动态轴承）FAT（File Allocation T ables，文件分配表）FC（Fibre Channel，光纤通道）FDBM（Fluid dynamic bearing motors，液态轴承马达）FDB（Fluid Dynamic Bearing，非固定动态轴承）FDC（Floppy Disk Controller，软盘驱动器控制装置）FDD（Floppy Disk Driver，软盘驱动器）GMR（giant magnetoresistive，巨型磁阻）HDA（Head Disk Assembly，头盘组件）HiFD（high-capacity floppy disk，高容量软盘）IDE（Integrated Drive Electronics，电子集成驱动器）IPEAK SPT（Intel Performance Evaluation and Analysis Kit - Storage Performance Toolkit，英特尔性能评估和分析套件- 存储性能工具包）JBOD（Just a Bunch Of Disks，磁盘连续捆束阵列）LBA（Logical Block Addressing，逻辑块寻址）MR（Magneto-resistive Heads，磁阻磁头）MBR（Master Boot Record，主引导记录）ms（Millisecond，毫秒）MSR（Magnetically induced Super Resolution，磁感应超分辨率）MTBF（Mean Time Before Failure，平均无故障时间）NQC（Native Queuing Command，内部序列命令）NTFS（Net Technology File System，新技术文件系统）OTF（on-the-fly，高速数据传输错误纠正）PCBA（Pring Circuit Board Assembly，印刷电路电路板组件）PIO（Programmed Input Output，可编程输入输出模式）PRML（Partial Response Maximum Likelihood，最大可能部分反应，用于提高磁盘读写传输率）RAID（Redundant Array of Independent Disks，独立磁盘冗余阵列）RAID（Redundant Array of Inexpensive Disks ，廉价磁盘冗余阵列）RPM（Rotation Per Minute，转/分）RSD: Removable Storage Device（移动式存储设备）RST（Read Service Times，读取服务时间）SAMS（Seagate's Advanced Multi Drive System，希捷高级多硬盘系统）SAS（Serial Attached SCSI，串行SCSI）SATA（Serial ATA，串行ATA）SBT（sound barrier technology，声音阻碍技术）SCSI（Small Computer System Interface，小型计算机系统接口）SCMA：SCSI Configured Auto Magically，SCSI自动配置SLDRAM（Synchnonous Link DRAM，同步链路内存）S.M.A.R.T.（Self-Monitoring, Analysis and ReportingTechnology，自动监测、分析和报告技术）SPS（Shock Protection System，抗震保护系统）SSO（simultaneously switching outputs，同时开关输出）STA（SCSI Trade Association，SCSI同业公会）STR（sequential transfer rates，连续内部数据传输率）TCQ（tagged command queuing，标签命令序列）TFI（Thin-Film Inducted Heads，薄膜感应磁头）TPI （Track Per Inch，磁道/英寸）Ultra CF（Ultra CompactFlash Card，超级紧凑型闪存卡）Ultra DMA（Ultra Direct Memory Access，超高速直接内存存取）LVD（Low Voltage Differential）Wpcom（Write-Precompensation Cylinders，写电流补偿柱面数）WST（Write Service Times，写入服务时间）AAM（Automatic Acoustic Management，自动机械声学管理）CBDS（Continuous Background Defect Scanning，连续后台错误扫描）DiscWizard（磁盘控制软件）DST（Drive Self Test，磁盘自检程序）SeaShield（防静电防撞击外壳）ADIP（Address In Pre-Groove，预凹槽寻址）ASPI（Advanced SCSI Programming Interface，高级SCSI可编程接口）ATAPI（AT Attachment Packet Interface，AT扩展包接口）BCF（Boot Catalog File，启动目录文件）BURN-Proof（Buffer UnderRuN-Proof，防止缓冲区溢出，三洋的刻录保护技术）BIF（Boot Image File，启动映像文件）CAV（Constant Angular Velocity，恒定角速度）CD（Compact Disc）CDR（CD Recordable，可记录光盘）CD-ROM/XA（CD－ROM eXtended Architecture，唯读光盘增强形架构）CDRW（CD-Rewritable，可重复刻录光盘）CLV（Constant Linear Velocity，恒定线速度）DAE（digital Audio Extraction，数据音频抓取）DAO（Disc At Once，整盘刻录）DAO－RAW（Disc At Once Read after Write，整盘刻录－写后读）DDSS（Double Dynamic Suspension System，双悬浮动态减震系统）DDSS II（Double Dynamic Suspension System II，第二代双层动力悬吊系统）DVD（Digital Video/Versatile Disk，数字视频/万能光盘）DVD-R（DVD Recordable，可记录DVD盘）DVD-RW（DVD Rewritable，可重复刻录DVD盘）DVD-RAM（Digital Video/Versatile Disk - Random AccessMemory，随机存储数字视频/万能光盘）ESER（EAC Secure Extract Ripping，EAC安全抓取复制）GM（Glass Mould，玻璃铸制）GSM（Galvanization Superconductive Material，电镀锌超导材料）IPW（Incremental Packet Writing，增量包刻录）LIMDOW（Light Intensity Modulation Direct OverWrite，光学调制直接覆盖）LG（Land Groove，岸地凹槽）MAMMOS（magnetic amplifying magneto-optical system，磁畴放大播放系统）MD（MiniDisc，微型光盘）ML（multi-level，多层光盘技术）MO（Magneto Optical，磁光盘）OTF（On The Fly，飞速刻录）OWSC（Optimum Write Speed Control、优化写入速度控制）PCAV（Part Constant Angular Velocity，部分恒定角速度）PPLS（Pure Phase Laser System，纯相位激光系统）RS-PC（Reed-Solomon Product Code，里德所罗门编码）RLL（Run Length limited，运行长度限制码）SACD（Super Audio CD，超级音频CD）SAO（Sessino At Once，区段刻录）SARC（Super－Advanced Rapid Cooling，超高级快速冷却）SC（Spin Coat，旋转覆盖）SCM（Spin Coat Method，旋压覆盖法）SLL（SeamLess Link，无缝连接）SMT（Superconductive Microtherm Technology，超导体散热材料）Super RENS（super resolution near-field structure，超精细近场结构）TAO（Track At Once，轨道刻录）TBW（Thermo Balanced Writing，热电平衡写入）VCD（Video COMPACT DISC，视频CD）VIPC（Intelligent Variable Power Correct，智能变功纠错技术）WD（Working Distance，工作距离）SOS（Smart Object Salvation，智能目标分析拯救系统）TADS（Target Acquisition and Designantion For DVD，DVD目标获取和指定）AAS（Automatic Area Seagment?）dpi（dot per inch，每英寸的打印像素）ECP（Extended Capabilities Port，延长能力端口）EPP（Enhanced Parallel Port，增强形平行接口）IPP（Internet Printing Protocol，因特网打印协议）MPT（Micro Piezo Technology，微针点压电）ppm（paper per minute，页/分）SPP（Standard Parallel Port，标准并行口）TA（Thermo Autochrome，全彩色感热式热感打印）TB（Thermal Bubble，热泡式）TET（Text Enhanced Technology，文本增强技术）USBDCDPD（Universal Serial Bus Device Class Definition for Printing Devices，打印设备的通用串行总线级标准）VD（Variable Dot，变点式列印）CIS（Contact Image Sensors，接触图像传感器）TWAIN（Toolkit Without An Interesting Name，无注名工具包协议）ADT（Advanced DRAM Technology，高级内存技术）ANSI（American National Standards Institute，美国国立标准协会）BAD（Best Amiga Dominators）CBF: Cable Broadband Forum，电缆宽带论坛CEA（Consumer Electronics Association，消费者电子协会）CEMA（Consumer Electronics Manufacturing Association（消费者电子制造业协会）CPE: Customer Premise Equipment（用户预定设备）CSA（Canadian Standards Association，加拿大标准协会）DCA: Defense Communication Agency，国防部通信局DOJ: Department of Justice（反不正当竞争部门）DSP: Delivery Service Partner（交付服务合伙人）DVB：Digital Video Broadcasting，数字视频广播E3（Electronic Entertainment Expo，电子娱乐展览会）EFF: Electronic Frontier Foundation（电子前线基金会）EPA（Environmental Protection Agency，美国环境保护局）ETRI（Electronics and Telecommunications ResearchInstitute，电子和电信研究协会）FCC（Federal Communications Commission，联邦通信委员会）FTC（Federal Trade Commission，联邦商业委员会）GDC（Game Developer Conference，游戏发展商会议）HTTC（HyperTransport Technology Consortium，HyperTransport技术协会）ICT（Information and Communications Technology，信息和通讯技术）IEC（International Electrotechnical Commission，国际电子技术委员会）ISSCC（International Solid-State Circuits Conference，国际晶体管电路讨论会）ICSA: International Computer SecurityAssociation（国际计算机安全协会）,它的前身为NCSA（National ComputerSecurity Association,国家计算机安全协会）ITU（International Telecommunications Union，国际电信同盟）IEEE（Institute of Electrical and Electronics Engineers，电子电路工程师协会）IETF（Internet Engineering T ask Force，因特网工程任务组）IFWP: International Forum White Paper，国际白皮书论坛ISC（International Steering Committee，国际筹划指导委员会）ISO/MPEG: International Standard Organization's Moving PictureExpert Group（国际标准化组织的活动图片专家组）ISOM（International Symposium on Optical Memory，光盘国际会议）ISSCC（IEEE International Solid-State CircuitsConference，IEEE国际固态电路协议）ITAA: Information Technology Association of American，美国信息技术协会ITWG（international technology working groups，国际技术工作组）JCIA（Japan Camera Industry Association，日本摄影机工业协会）。
EN 13445-5 非火焰接触压力容器
European standard
French standard
ISSN 0335-3931
NF EN 13445-5 V1
October 2009
Classification index: E 86-200-5
EXAMPLE Given the adoption of EN 13445-5/A1 in January 2010 and EN 13445-5/A2 in November 2010, the following documents will be available from AFNOR:
2009
All parts NF EN 13445-1 to NF EN 13445-6 and NF EN 13445-8 are intended to support the essential requirements of European Directive 97/23/EC "Pressure Equipment".
the text of the current version
…
Correction : corrected pages to replace the corresponding pages of version N to produce version N+1
For example, NF EN 13445-5/AC1 gives pages that have been corrected in Version 1 to produce Version 2
xx: document available x: document upon request —: document not available
常用Flex IOC框架比较分析
常用Flex IOC框架比较分析IOC（Inversion of Control），也称DI（Dependency Injection），是近年来在软件开发中变得非常流行的一种设计策略。
众多的Flex开发者，探索出了诸如Spring ActionScript、Parsley、Flicc和Swiz这样的IOC框架。
什么是IOC？一言以蔽之，IOC是一种软件设计模式。
借助IOC，可用一个独立的对象为其他对象的数据成员填充正确的实现，而不是由这些对象自己负责此项工作。
这样做的好处有两个。
第一，可将对象的数据成员声明为接口，从而将对象与其具体实现分离（即契约式设计，design by contract）。
第二，可从对象中删除创建逻辑，可以使对象的用途更为明确。
IOC容器提供一个框架，你可借此以一致和宣告的形式使用这个模式。
将此模式和接口结合起来，可以创建出易于测试、使用灵活的对象。
有关IOC模式更深入的讨论，请参看Martin Fowler的文章《Inversion of Control Containers and the Dependency Injection pattern》。
Java和.NET的IOC框架早已建立，在Flex社区，近来也有不小的进展。
本文将讨论Flex中的一些IOC框架的工作原理、使用方法，并对这些框架进行比较。
为了比较方便，我将在同一个工程（ProfileViewer）中使用Spring ActionScript、 Parsley、Flicc和Swiz这几个框架。
IOC的概念一般有两种最常见的对象配置方法：∙对象实例化（例如：var myObject = new Object()）∙对象查找（例如：var myObject = registry.getMyObject()）而利用IOC，你可在一个独立层中实例化应用程序要用到的对象，并传入它们所需的依赖。
具体来说，最常见的实现方法也有两种：∙Setter注入（例如：instance.myObject = new Object()）∙Constructor注入（例如：instance = new Instance( new Object() )）一个IOC框架，通常由如下三个部分组成：配置、工厂和注入机制。
LTE系统消息翻译
系统消息解析1 MIB （Master Information Block）解析MIB主要包含系统带宽、PHICH配置信息、系统帧号。
（下图为实测信令）➢DL_Bandwidth系统带宽，范围enumerate(1.4M(6RB，0)，3M(15RB,1)，5M(25RB,2)，10M(50RB,3)，15M(75RB,4)，20M(100RB,5))，上图为n100，对应的系统带宽为20M（100RB，带宽索引号为5）。
➢Phich_Duration当该参数设置为normal时，PDCCH占用的OFDM符号数可以自适应调整；当该参数设置为extended时，若带宽为1.4M，则PDCCH占用的OFDM符号数可以取3或4，对于其他系统带宽下，PDCCH占用的符号数只能为3。
➢PHICH-Resource该参数用于计算小区PHICH信道的资源；➢SystemFrameNumber系统帧号。
系统帧号，用于UE获取系统时钟。
实际SFN位长为10bit，也就是取值从0-1023循环。
在PBCH的MIB广播中只广播前8位，剩下的两位根据该帧在PBCH 40ms周期窗口的位置确定，第一个10ms帧为00，第二帧为01，第三帧为10，第四帧为11。
PBCH 的40ms窗口手机可以通过盲检确定。
➢Spare：预留的，暂时未用2 SIB1 （System Information Block Type1）解析SIB1上主要传输评估UE能否接入小区的相关信息及其他系统消息的调度信息。
主要包括4部分：➢小区接入相关信息（cell Access Related Info）➢小区选择信息（cell Selection Info）➢调度信息（scheduling Info List）➢TDD配置信息（tdd-Config）SIB1消息解析（UE侧）：RRC-MSG..msg....struBCCH-DL-SCH-Message......struBCCH-DL-SCH-Message........message..........c1............systemInformationBlockType1..............cellAccessRelatedInfo//小区接入相关信息................plmn-IdentityList//PLMN标识列表..................PLMN-IdentityInfo....................plmn-Identity ......................mcc//460 ........................MCC-MNC-Digit:0x4 (4) ........................MCC-MNC-Digit:0x6 (6) ........................MCC-MNC-Digit:0x0 (0) ......................mnc//00 ........................MCC-MNC-Digit:0x0 (0) ........................MCC-MNC-Digit:0x0 (0) ....................cellReservedForOperatorUse:notReserved (1) ................trackingAreaCode:11100(890C)//TAC跟踪区（890C）为16进制数，转换成十进制为35084，查TAC在该消息中可以查到，此条信元重要。
3GPP TS 36.331 V13.2.0 (2016-06)
3GPP TS 36.331 V13.2.0 (2016-06)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specification(Release 13)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.KeywordsUMTS, radio3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationBluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its membersContentsForeword (18)1Scope (19)2References (19)3Definitions, symbols and abbreviations (22)3.1Definitions (22)3.2Abbreviations (24)4General (27)4.1Introduction (27)4.2Architecture (28)4.2.1UE states and state transitions including inter RAT (28)4.2.2Signalling radio bearers (29)4.3Services (30)4.3.1Services provided to upper layers (30)4.3.2Services expected from lower layers (30)4.4Functions (30)5Procedures (32)5.1General (32)5.1.1Introduction (32)5.1.2General requirements (32)5.2System information (33)5.2.1Introduction (33)5.2.1.1General (33)5.2.1.2Scheduling (34)5.2.1.2a Scheduling for NB-IoT (34)5.2.1.3System information validity and notification of changes (35)5.2.1.4Indication of ETWS notification (36)5.2.1.5Indication of CMAS notification (37)5.2.1.6Notification of EAB parameters change (37)5.2.1.7Access Barring parameters change in NB-IoT (37)5.2.2System information acquisition (38)5.2.2.1General (38)5.2.2.2Initiation (38)5.2.2.3System information required by the UE (38)5.2.2.4System information acquisition by the UE (39)5.2.2.5Essential system information missing (42)5.2.2.6Actions upon reception of the MasterInformationBlock message (42)5.2.2.7Actions upon reception of the SystemInformationBlockType1 message (42)5.2.2.8Actions upon reception of SystemInformation messages (44)5.2.2.9Actions upon reception of SystemInformationBlockType2 (44)5.2.2.10Actions upon reception of SystemInformationBlockType3 (45)5.2.2.11Actions upon reception of SystemInformationBlockType4 (45)5.2.2.12Actions upon reception of SystemInformationBlockType5 (45)5.2.2.13Actions upon reception of SystemInformationBlockType6 (45)5.2.2.14Actions upon reception of SystemInformationBlockType7 (45)5.2.2.15Actions upon reception of SystemInformationBlockType8 (45)5.2.2.16Actions upon reception of SystemInformationBlockType9 (46)5.2.2.17Actions upon reception of SystemInformationBlockType10 (46)5.2.2.18Actions upon reception of SystemInformationBlockType11 (46)5.2.2.19Actions upon reception of SystemInformationBlockType12 (47)5.2.2.20Actions upon reception of SystemInformationBlockType13 (48)5.2.2.21Actions upon reception of SystemInformationBlockType14 (48)5.2.2.22Actions upon reception of SystemInformationBlockType15 (48)5.2.2.23Actions upon reception of SystemInformationBlockType16 (48)5.2.2.24Actions upon reception of SystemInformationBlockType17 (48)5.2.2.25Actions upon reception of SystemInformationBlockType18 (48)5.2.2.26Actions upon reception of SystemInformationBlockType19 (49)5.2.3Acquisition of an SI message (49)5.2.3a Acquisition of an SI message by BL UE or UE in CE or a NB-IoT UE (50)5.3Connection control (50)5.3.1Introduction (50)5.3.1.1RRC connection control (50)5.3.1.2Security (52)5.3.1.2a RN security (53)5.3.1.3Connected mode mobility (53)5.3.1.4Connection control in NB-IoT (54)5.3.2Paging (55)5.3.2.1General (55)5.3.2.2Initiation (55)5.3.2.3Reception of the Paging message by the UE (55)5.3.3RRC connection establishment (56)5.3.3.1General (56)5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/ discovery (58)5.3.3.2Initiation (59)5.3.3.3Actions related to transmission of RRCConnectionRequest message (63)5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message (64)5.3.3.4Reception of the RRCConnectionSetup by the UE (64)5.3.3.4a Reception of the RRCConnectionResume by the UE (66)5.3.3.5Cell re-selection while T300, T302, T303, T305, T306, or T308 is running (68)5.3.3.6T300 expiry (68)5.3.3.7T302, T303, T305, T306, or T308 expiry or stop (69)5.3.3.8Reception of the RRCConnectionReject by the UE (70)5.3.3.9Abortion of RRC connection establishment (71)5.3.3.10Handling of SSAC related parameters (71)5.3.3.11Access barring check (72)5.3.3.12EAB check (73)5.3.3.13Access barring check for ACDC (73)5.3.3.14Access Barring check for NB-IoT (74)5.3.4Initial security activation (75)5.3.4.1General (75)5.3.4.2Initiation (76)5.3.4.3Reception of the SecurityModeCommand by the UE (76)5.3.5RRC connection reconfiguration (77)5.3.5.1General (77)5.3.5.2Initiation (77)5.3.5.3Reception of an RRCConnectionReconfiguration not including the mobilityControlInfo by theUE (77)5.3.5.4Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE(handover) (79)5.3.5.5Reconfiguration failure (83)5.3.5.6T304 expiry (handover failure) (83)5.3.5.7Void (84)5.3.5.7a T307 expiry (SCG change failure) (84)5.3.5.8Radio Configuration involving full configuration option (84)5.3.6Counter check (86)5.3.6.1General (86)5.3.6.2Initiation (86)5.3.6.3Reception of the CounterCheck message by the UE (86)5.3.7RRC connection re-establishment (87)5.3.7.1General (87)5.3.7.2Initiation (87)5.3.7.3Actions following cell selection while T311 is running (88)5.3.7.4Actions related to transmission of RRCConnectionReestablishmentRequest message (89)5.3.7.5Reception of the RRCConnectionReestablishment by the UE (89)5.3.7.6T311 expiry (91)5.3.7.7T301 expiry or selected cell no longer suitable (91)5.3.7.8Reception of RRCConnectionReestablishmentReject by the UE (91)5.3.8RRC connection release (92)5.3.8.1General (92)5.3.8.2Initiation (92)5.3.8.3Reception of the RRCConnectionRelease by the UE (92)5.3.8.4T320 expiry (93)5.3.9RRC connection release requested by upper layers (93)5.3.9.1General (93)5.3.9.2Initiation (93)5.3.10Radio resource configuration (93)5.3.10.0General (93)5.3.10.1SRB addition/ modification (94)5.3.10.2DRB release (95)5.3.10.3DRB addition/ modification (95)5.3.10.3a1DC specific DRB addition or reconfiguration (96)5.3.10.3a2LWA specific DRB addition or reconfiguration (98)5.3.10.3a3LWIP specific DRB addition or reconfiguration (98)5.3.10.3a SCell release (99)5.3.10.3b SCell addition/ modification (99)5.3.10.3c PSCell addition or modification (99)5.3.10.4MAC main reconfiguration (99)5.3.10.5Semi-persistent scheduling reconfiguration (100)5.3.10.6Physical channel reconfiguration (100)5.3.10.7Radio Link Failure Timers and Constants reconfiguration (101)5.3.10.8Time domain measurement resource restriction for serving cell (101)5.3.10.9Other configuration (102)5.3.10.10SCG reconfiguration (103)5.3.10.11SCG dedicated resource configuration (104)5.3.10.12Reconfiguration SCG or split DRB by drb-ToAddModList (105)5.3.10.13Neighbour cell information reconfiguration (105)5.3.10.14Void (105)5.3.10.15Sidelink dedicated configuration (105)5.3.10.16T370 expiry (106)5.3.11Radio link failure related actions (107)5.3.11.1Detection of physical layer problems in RRC_CONNECTED (107)5.3.11.2Recovery of physical layer problems (107)5.3.11.3Detection of radio link failure (107)5.3.12UE actions upon leaving RRC_CONNECTED (109)5.3.13UE actions upon PUCCH/ SRS release request (110)5.3.14Proximity indication (110)5.3.14.1General (110)5.3.14.2Initiation (111)5.3.14.3Actions related to transmission of ProximityIndication message (111)5.3.15Void (111)5.4Inter-RAT mobility (111)5.4.1Introduction (111)5.4.2Handover to E-UTRA (112)5.4.2.1General (112)5.4.2.2Initiation (112)5.4.2.3Reception of the RRCConnectionReconfiguration by the UE (112)5.4.2.4Reconfiguration failure (114)5.4.2.5T304 expiry (handover to E-UTRA failure) (114)5.4.3Mobility from E-UTRA (114)5.4.3.1General (114)5.4.3.2Initiation (115)5.4.3.3Reception of the MobilityFromEUTRACommand by the UE (115)5.4.3.4Successful completion of the mobility from E-UTRA (116)5.4.3.5Mobility from E-UTRA failure (117)5.4.4Handover from E-UTRA preparation request (CDMA2000) (117)5.4.4.1General (117)5.4.4.2Initiation (118)5.4.4.3Reception of the HandoverFromEUTRAPreparationRequest by the UE (118)5.4.5UL handover preparation transfer (CDMA2000) (118)5.4.5.1General (118)5.4.5.2Initiation (118)5.4.5.3Actions related to transmission of the ULHandoverPreparationTransfer message (119)5.4.5.4Failure to deliver the ULHandoverPreparationTransfer message (119)5.4.6Inter-RAT cell change order to E-UTRAN (119)5.4.6.1General (119)5.4.6.2Initiation (119)5.4.6.3UE fails to complete an inter-RAT cell change order (119)5.5Measurements (120)5.5.1Introduction (120)5.5.2Measurement configuration (121)5.5.2.1General (121)5.5.2.2Measurement identity removal (122)5.5.2.2a Measurement identity autonomous removal (122)5.5.2.3Measurement identity addition/ modification (123)5.5.2.4Measurement object removal (124)5.5.2.5Measurement object addition/ modification (124)5.5.2.6Reporting configuration removal (126)5.5.2.7Reporting configuration addition/ modification (127)5.5.2.8Quantity configuration (127)5.5.2.9Measurement gap configuration (127)5.5.2.10Discovery signals measurement timing configuration (128)5.5.2.11RSSI measurement timing configuration (128)5.5.3Performing measurements (128)5.5.3.1General (128)5.5.3.2Layer 3 filtering (131)5.5.4Measurement report triggering (131)5.5.4.1General (131)5.5.4.2Event A1 (Serving becomes better than threshold) (135)5.5.4.3Event A2 (Serving becomes worse than threshold) (136)5.5.4.4Event A3 (Neighbour becomes offset better than PCell/ PSCell) (136)5.5.4.5Event A4 (Neighbour becomes better than threshold) (137)5.5.4.6Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better thanthreshold2) (138)5.5.4.6a Event A6 (Neighbour becomes offset better than SCell) (139)5.5.4.7Event B1 (Inter RAT neighbour becomes better than threshold) (139)5.5.4.8Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better thanthreshold2) (140)5.5.4.9Event C1 (CSI-RS resource becomes better than threshold) (141)5.5.4.10Event C2 (CSI-RS resource becomes offset better than reference CSI-RS resource) (141)5.5.4.11Event W1 (WLAN becomes better than a threshold) (142)5.5.4.12Event W2 (All WLAN inside WLAN mobility set becomes worse than threshold1 and a WLANoutside WLAN mobility set becomes better than threshold2) (142)5.5.4.13Event W3 (All WLAN inside WLAN mobility set becomes worse than a threshold) (143)5.5.5Measurement reporting (144)5.5.6Measurement related actions (148)5.5.6.1Actions upon handover and re-establishment (148)5.5.6.2Speed dependant scaling of measurement related parameters (149)5.5.7Inter-frequency RSTD measurement indication (149)5.5.7.1General (149)5.5.7.2Initiation (150)5.5.7.3Actions related to transmission of InterFreqRSTDMeasurementIndication message (150)5.6Other (150)5.6.0General (150)5.6.1DL information transfer (151)5.6.1.1General (151)5.6.1.2Initiation (151)5.6.1.3Reception of the DLInformationTransfer by the UE (151)5.6.2UL information transfer (151)5.6.2.1General (151)5.6.2.2Initiation (151)5.6.2.3Actions related to transmission of ULInformationTransfer message (152)5.6.2.4Failure to deliver ULInformationTransfer message (152)5.6.3UE capability transfer (152)5.6.3.1General (152)5.6.3.2Initiation (153)5.6.3.3Reception of the UECapabilityEnquiry by the UE (153)5.6.4CSFB to 1x Parameter transfer (157)5.6.4.1General (157)5.6.4.2Initiation (157)5.6.4.3Actions related to transmission of CSFBParametersRequestCDMA2000 message (157)5.6.4.4Reception of the CSFBParametersResponseCDMA2000 message (157)5.6.5UE Information (158)5.6.5.1General (158)5.6.5.2Initiation (158)5.6.5.3Reception of the UEInformationRequest message (158)5.6.6 Logged Measurement Configuration (159)5.6.6.1General (159)5.6.6.2Initiation (160)5.6.6.3Reception of the LoggedMeasurementConfiguration by the UE (160)5.6.6.4T330 expiry (160)5.6.7 Release of Logged Measurement Configuration (160)5.6.7.1General (160)5.6.7.2Initiation (160)5.6.8 Measurements logging (161)5.6.8.1General (161)5.6.8.2Initiation (161)5.6.9In-device coexistence indication (163)5.6.9.1General (163)5.6.9.2Initiation (164)5.6.9.3Actions related to transmission of InDeviceCoexIndication message (164)5.6.10UE Assistance Information (165)5.6.10.1General (165)5.6.10.2Initiation (166)5.6.10.3Actions related to transmission of UEAssistanceInformation message (166)5.6.11 Mobility history information (166)5.6.11.1General (166)5.6.11.2Initiation (166)5.6.12RAN-assisted WLAN interworking (167)5.6.12.1General (167)5.6.12.2Dedicated WLAN offload configuration (167)5.6.12.3WLAN offload RAN evaluation (167)5.6.12.4T350 expiry or stop (167)5.6.12.5Cell selection/ re-selection while T350 is running (168)5.6.13SCG failure information (168)5.6.13.1General (168)5.6.13.2Initiation (168)5.6.13.3Actions related to transmission of SCGFailureInformation message (168)5.6.14LTE-WLAN Aggregation (169)5.6.14.1Introduction (169)5.6.14.2Reception of LWA configuration (169)5.6.14.3Release of LWA configuration (170)5.6.15WLAN connection management (170)5.6.15.1Introduction (170)5.6.15.2WLAN connection status reporting (170)5.6.15.2.1General (170)5.6.15.2.2Initiation (171)5.6.15.2.3Actions related to transmission of WLANConnectionStatusReport message (171)5.6.15.3T351 Expiry (WLAN connection attempt timeout) (171)5.6.15.4WLAN status monitoring (171)5.6.16RAN controlled LTE-WLAN interworking (172)5.6.16.1General (172)5.6.16.2WLAN traffic steering command (172)5.6.17LTE-WLAN aggregation with IPsec tunnel (173)5.6.17.1General (173)5.7Generic error handling (174)5.7.1General (174)5.7.2ASN.1 violation or encoding error (174)5.7.3Field set to a not comprehended value (174)5.7.4Mandatory field missing (174)5.7.5Not comprehended field (176)5.8MBMS (176)5.8.1Introduction (176)5.8.1.1General (176)5.8.1.2Scheduling (176)5.8.1.3MCCH information validity and notification of changes (176)5.8.2MCCH information acquisition (178)5.8.2.1General (178)5.8.2.2Initiation (178)5.8.2.3MCCH information acquisition by the UE (178)5.8.2.4Actions upon reception of the MBSFNAreaConfiguration message (178)5.8.2.5Actions upon reception of the MBMSCountingRequest message (179)5.8.3MBMS PTM radio bearer configuration (179)5.8.3.1General (179)5.8.3.2Initiation (179)5.8.3.3MRB establishment (179)5.8.3.4MRB release (179)5.8.4MBMS Counting Procedure (179)5.8.4.1General (179)5.8.4.2Initiation (180)5.8.4.3Reception of the MBMSCountingRequest message by the UE (180)5.8.5MBMS interest indication (181)5.8.5.1General (181)5.8.5.2Initiation (181)5.8.5.3Determine MBMS frequencies of interest (182)5.8.5.4Actions related to transmission of MBMSInterestIndication message (183)5.8a SC-PTM (183)5.8a.1Introduction (183)5.8a.1.1General (183)5.8a.1.2SC-MCCH scheduling (183)5.8a.1.3SC-MCCH information validity and notification of changes (183)5.8a.1.4Procedures (184)5.8a.2SC-MCCH information acquisition (184)5.8a.2.1General (184)5.8a.2.2Initiation (184)5.8a.2.3SC-MCCH information acquisition by the UE (184)5.8a.2.4Actions upon reception of the SCPTMConfiguration message (185)5.8a.3SC-PTM radio bearer configuration (185)5.8a.3.1General (185)5.8a.3.2Initiation (185)5.8a.3.3SC-MRB establishment (185)5.8a.3.4SC-MRB release (185)5.9RN procedures (186)5.9.1RN reconfiguration (186)5.9.1.1General (186)5.9.1.2Initiation (186)5.9.1.3Reception of the RNReconfiguration by the RN (186)5.10Sidelink (186)5.10.1Introduction (186)5.10.1a Conditions for sidelink communication operation (187)5.10.2Sidelink UE information (188)5.10.2.1General (188)5.10.2.2Initiation (189)5.10.2.3Actions related to transmission of SidelinkUEInformation message (193)5.10.3Sidelink communication monitoring (195)5.10.6Sidelink discovery announcement (198)5.10.6a Sidelink discovery announcement pool selection (201)5.10.6b Sidelink discovery announcement reference carrier selection (201)5.10.7Sidelink synchronisation information transmission (202)5.10.7.1General (202)5.10.7.2Initiation (203)5.10.7.3Transmission of SLSS (204)5.10.7.4Transmission of MasterInformationBlock-SL message (205)5.10.7.5Void (206)5.10.8Sidelink synchronisation reference (206)5.10.8.1General (206)5.10.8.2Selection and reselection of synchronisation reference UE (SyncRef UE) (206)5.10.9Sidelink common control information (207)5.10.9.1General (207)5.10.9.2Actions related to reception of MasterInformationBlock-SL message (207)5.10.10Sidelink relay UE operation (207)5.10.10.1General (207)5.10.10.2AS-conditions for relay related sidelink communication transmission by sidelink relay UE (207)5.10.10.3AS-conditions for relay PS related sidelink discovery transmission by sidelink relay UE (208)5.10.10.4Sidelink relay UE threshold conditions (208)5.10.11Sidelink remote UE operation (208)5.10.11.1General (208)5.10.11.2AS-conditions for relay related sidelink communication transmission by sidelink remote UE (208)5.10.11.3AS-conditions for relay PS related sidelink discovery transmission by sidelink remote UE (209)5.10.11.4Selection and reselection of sidelink relay UE (209)5.10.11.5Sidelink remote UE threshold conditions (210)6Protocol data units, formats and parameters (tabular & ASN.1) (210)6.1General (210)6.2RRC messages (212)6.2.1General message structure (212)–EUTRA-RRC-Definitions (212)–BCCH-BCH-Message (212)–BCCH-DL-SCH-Message (212)–BCCH-DL-SCH-Message-BR (213)–MCCH-Message (213)–PCCH-Message (213)–DL-CCCH-Message (214)–DL-DCCH-Message (214)–UL-CCCH-Message (214)–UL-DCCH-Message (215)–SC-MCCH-Message (215)6.2.2Message definitions (216)–CounterCheck (216)–CounterCheckResponse (217)–CSFBParametersRequestCDMA2000 (217)–CSFBParametersResponseCDMA2000 (218)–DLInformationTransfer (218)–HandoverFromEUTRAPreparationRequest (CDMA2000) (219)–InDeviceCoexIndication (220)–InterFreqRSTDMeasurementIndication (222)–LoggedMeasurementConfiguration (223)–MasterInformationBlock (225)–MBMSCountingRequest (226)–MBMSCountingResponse (226)–MBMSInterestIndication (227)–MBSFNAreaConfiguration (228)–MeasurementReport (228)–MobilityFromEUTRACommand (229)–Paging (232)–ProximityIndication (233)–RNReconfiguration (234)–RNReconfigurationComplete (234)–RRCConnectionReconfiguration (235)–RRCConnectionReconfigurationComplete (240)–RRCConnectionReestablishment (241)–RRCConnectionReestablishmentComplete (241)–RRCConnectionReestablishmentReject (242)–RRCConnectionReestablishmentRequest (243)–RRCConnectionReject (243)–RRCConnectionRelease (244)–RRCConnectionResume (248)–RRCConnectionResumeComplete (249)–RRCConnectionResumeRequest (250)–RRCConnectionRequest (250)–RRCConnectionSetup (251)–RRCConnectionSetupComplete (252)–SCGFailureInformation (253)–SCPTMConfiguration (254)–SecurityModeCommand (255)–SecurityModeComplete (255)–SecurityModeFailure (256)–SidelinkUEInformation (256)–SystemInformation (258)–SystemInformationBlockType1 (259)–UEAssistanceInformation (264)–UECapabilityEnquiry (265)–UECapabilityInformation (266)–UEInformationRequest (267)–UEInformationResponse (267)–ULHandoverPreparationTransfer (CDMA2000) (273)–ULInformationTransfer (274)–WLANConnectionStatusReport (274)6.3RRC information elements (275)6.3.1System information blocks (275)–SystemInformationBlockType2 (275)–SystemInformationBlockType3 (279)–SystemInformationBlockType4 (282)–SystemInformationBlockType5 (283)–SystemInformationBlockType6 (287)–SystemInformationBlockType7 (289)–SystemInformationBlockType8 (290)–SystemInformationBlockType9 (295)–SystemInformationBlockType10 (295)–SystemInformationBlockType11 (296)–SystemInformationBlockType12 (297)–SystemInformationBlockType13 (297)–SystemInformationBlockType14 (298)–SystemInformationBlockType15 (298)–SystemInformationBlockType16 (299)–SystemInformationBlockType17 (300)–SystemInformationBlockType18 (301)–SystemInformationBlockType19 (301)–SystemInformationBlockType20 (304)6.3.2Radio resource control information elements (304)–AntennaInfo (304)–AntennaInfoUL (306)–CQI-ReportConfig (307)–CQI-ReportPeriodicProcExtId (314)–CrossCarrierSchedulingConfig (314)–CSI-IM-Config (315)–CSI-IM-ConfigId (315)–CSI-RS-Config (317)–CSI-RS-ConfigEMIMO (318)–CSI-RS-ConfigNZP (319)–CSI-RS-ConfigNZPId (320)–CSI-RS-ConfigZP (321)–CSI-RS-ConfigZPId (321)–DMRS-Config (321)–DRB-Identity (322)–EPDCCH-Config (322)–EIMTA-MainConfig (324)–LogicalChannelConfig (325)–LWA-Configuration (326)–LWIP-Configuration (326)–RCLWI-Configuration (327)–MAC-MainConfig (327)–P-C-AndCBSR (332)–PDCCH-ConfigSCell (333)–PDCP-Config (334)–PDSCH-Config (337)–PDSCH-RE-MappingQCL-ConfigId (339)–PHICH-Config (339)–PhysicalConfigDedicated (339)–P-Max (344)–PRACH-Config (344)–PresenceAntennaPort1 (346)–PUCCH-Config (347)–PUSCH-Config (351)–RACH-ConfigCommon (355)–RACH-ConfigDedicated (357)–RadioResourceConfigCommon (358)–RadioResourceConfigDedicated (362)–RLC-Config (367)–RLF-TimersAndConstants (369)–RN-SubframeConfig (370)–SchedulingRequestConfig (371)–SoundingRS-UL-Config (372)–SPS-Config (375)–TDD-Config (376)–TimeAlignmentTimer (377)–TPC-PDCCH-Config (377)–TunnelConfigLWIP (378)–UplinkPowerControl (379)–WLAN-Id-List (382)–WLAN-MobilityConfig (382)6.3.3Security control information elements (382)–NextHopChainingCount (382)–SecurityAlgorithmConfig (383)–ShortMAC-I (383)6.3.4Mobility control information elements (383)–AdditionalSpectrumEmission (383)–ARFCN-ValueCDMA2000 (383)–ARFCN-ValueEUTRA (384)–ARFCN-ValueGERAN (384)–ARFCN-ValueUTRA (384)–BandclassCDMA2000 (384)–BandIndicatorGERAN (385)–CarrierFreqCDMA2000 (385)–CarrierFreqGERAN (385)–CellIndexList (387)–CellReselectionPriority (387)–CellSelectionInfoCE (387)–CellReselectionSubPriority (388)–CSFB-RegistrationParam1XRTT (388)–CellGlobalIdEUTRA (389)–CellGlobalIdUTRA (389)–CellGlobalIdGERAN (390)–CellGlobalIdCDMA2000 (390)–CellSelectionInfoNFreq (391)–CSG-Identity (391)–FreqBandIndicator (391)–MobilityControlInfo (391)–MobilityParametersCDMA2000 (1xRTT) (393)–MobilityStateParameters (394)–MultiBandInfoList (394)–NS-PmaxList (394)–PhysCellId (395)–PhysCellIdRange (395)–PhysCellIdRangeUTRA-FDDList (395)–PhysCellIdCDMA2000 (396)–PhysCellIdGERAN (396)–PhysCellIdUTRA-FDD (396)–PhysCellIdUTRA-TDD (396)–PLMN-Identity (397)–PLMN-IdentityList3 (397)–PreRegistrationInfoHRPD (397)–Q-QualMin (398)–Q-RxLevMin (398)–Q-OffsetRange (398)–Q-OffsetRangeInterRAT (399)–ReselectionThreshold (399)–ReselectionThresholdQ (399)–SCellIndex (399)–ServCellIndex (400)–SpeedStateScaleFactors (400)–SystemInfoListGERAN (400)–SystemTimeInfoCDMA2000 (401)–TrackingAreaCode (401)–T-Reselection (402)–T-ReselectionEUTRA-CE (402)6.3.5Measurement information elements (402)–AllowedMeasBandwidth (402)–CSI-RSRP-Range (402)–Hysteresis (402)–LocationInfo (403)–MBSFN-RSRQ-Range (403)–MeasConfig (404)–MeasDS-Config (405)–MeasGapConfig (406)–MeasId (407)–MeasIdToAddModList (407)–MeasObjectCDMA2000 (408)–MeasObjectEUTRA (408)–MeasObjectGERAN (412)–MeasObjectId (412)–MeasObjectToAddModList (412)–MeasObjectUTRA (413)–ReportConfigEUTRA (422)–ReportConfigId (425)–ReportConfigInterRAT (425)–ReportConfigToAddModList (428)–ReportInterval (429)–RSRP-Range (429)–RSRQ-Range (430)–RSRQ-Type (430)–RS-SINR-Range (430)–RSSI-Range-r13 (431)–TimeToTrigger (431)–UL-DelayConfig (431)–WLAN-CarrierInfo (431)–WLAN-RSSI-Range (432)–WLAN-Status (432)6.3.6Other information elements (433)–AbsoluteTimeInfo (433)–AreaConfiguration (433)–C-RNTI (433)–DedicatedInfoCDMA2000 (434)–DedicatedInfoNAS (434)–FilterCoefficient (434)–LoggingDuration (434)–LoggingInterval (435)–MeasSubframePattern (435)–MMEC (435)–NeighCellConfig (435)–OtherConfig (436)–RAND-CDMA2000 (1xRTT) (437)–RAT-Type (437)–ResumeIdentity (437)–RRC-TransactionIdentifier (438)–S-TMSI (438)–TraceReference (438)–UE-CapabilityRAT-ContainerList (438)–UE-EUTRA-Capability (439)–UE-RadioPagingInfo (469)–UE-TimersAndConstants (469)–VisitedCellInfoList (470)–WLAN-OffloadConfig (470)6.3.7MBMS information elements (472)–MBMS-NotificationConfig (472)–MBMS-ServiceList (473)–MBSFN-AreaId (473)–MBSFN-AreaInfoList (473)–MBSFN-SubframeConfig (474)–PMCH-InfoList (475)6.3.7a SC-PTM information elements (476)–SC-MTCH-InfoList (476)–SCPTM-NeighbourCellList (478)6.3.8Sidelink information elements (478)–SL-CommConfig (478)–SL-CommResourcePool (479)–SL-CP-Len (480)–SL-DiscConfig (481)–SL-DiscResourcePool (483)–SL-DiscTxPowerInfo (485)–SL-GapConfig (485)。
Viking 消防救生设备 资料
Scope of supply for each shipset:POS Equipment Specification QTY Page 1Short fireman's axe, 33cm3PCS1 2BATTERY, FOR SIGNAL LAMP6PCS3 3BATTERY, FOR SIGNAL LAMP8PCS3 4EEBD M-20.2 International Maritime - CE7PCS4-5 5EEBD M-20.2 Storage Rack, OCENCO7PCS6 6SAFETYBELT, 2 D-RINGS, WITH SAFETY LINE3PCS7 7RESCUE-DAN M1 FOR LIFEJACKET43PCS8-9 8MOUNTING OF LIGHT 1012426 RESCUE-DAN M13PCS9Personal leather holder, short fireman's3PCS10FIRE EXT., ABC, 6KG, CART., FIRESAFE4PCS10 11FIRE EXT., ABC, 12KG, CART., FIRESAFE86PCS11 12FIRE EXT., FOAM, 9LTR, CART., FIRESAFE43PCS12 13FIRE EXT., CO2, 5 KG, S.P., FIRESAFE4PCS13 14FIRE EXT., CO2, 5 KG, S.P., FIRESAFE4PCS15CARTRIDGE CO2 110 GRAM - UK4PCS14 16CART., FOR 12KG ABC FIRE EXT. FIRESAFE48PCS15 17CARTRIDGE CO2 75 GRAM - UK27PCS16 18FOAM, AFFF, 6%, 0.9LTR BOTTLE, FIRESAFE27PCS17 19CHEMICAL SUIT, TESIMAX GS3 SYKAN 24PCS18 20FIREMAN'S LIFELINE, INCL. SNAPHOOK3PCS19 21TORCH LIGHT, ATEX, 2317C3PCS20 22LIFEBUOY, 72CM, 2.5KG, VIKING10PCS21 23LIFEBUOY, 72CM, 4,3KG VIKING2PCS21 24LIFEBUOY FLOATING LINE, 30 MTR2PCS22 25AFFF FOAM, 6%, 2.7LTR1PCS23-33 26AFFF FOAM, 6% - 9,46 LTR1PCS27AFFF FOAM, 6%, 20 LTR16PCS28ABC DRY POWDER, FOR 6KG4PCS34-40 29ABC DRY POWDER, FOR 12KG48PCS30JET/SPRAY NOZZLE, 16MM, W/STORZ-65, ALU95PCS41 31JET/SPRAY NOZZLE, 16MM, W/STORZ-65, ALU5PCS32FIRE HOSE, STD., 2.5", 15M, STZ-65, ALU5PCS42 33FIRE HOSE, STD., 2.5", 20M, STZ-65, ALU95PCS34NECK PROTECTION FOR BULLARD HELMET3PCS43 35VISOR+ALU.FRAME FOR BULLARD HELMET3PCS44 36CYLINDER FOR SCBA, 6L, 300BAR, AIRFILLED15PCS4537MOB (LIGHT+SMOKE), c/w battery,brckt Hh2PCS46-48 38Line throwing device, 4 shot - HuaHai1PCS49-50 39Parachute Signal rocket - HuaHai12PCS51-53 40LIFEBUOY FLOATING LINE, 50 MTR2PCS22 41PLT - MOORING 150(art no 5000)2PCS42INT. SHORE CONNECTION, STORZ-65, BRASS2PCS54 43FOAM NOZZLE W INDUCTOR 200L,HV225 STZ 658PCS55-56 44Water Fog Applicator w/ storz 65 alu adp18PCS57 45QUICK RELEASE CASES FOR LIFEBUOYS - PAIR2SET58 46SCBA, WITHOUT CYL. SPASCIANI - NEW5PCS59-61 47LIFEBUOY BRACKET Y-STYLE, 72 cm SS31610PCS62 48BRACKET FOR 5KG CO2, FIRE EXT. NEW4PCS63 49BRACKET, FOR 6 KG/LTR, FIRE EXT. NEW4PCS64 50BRACKET, FOR 9 KG/LTR, FIRE EXT. NEW43PCS65 51BRACKET, FOR 12 KG/LTR, FIRE EXT. NEW86PCS66 52GRP BOX, 100X50X50 CM F. LIFEJACKETS NEW3PCS67 53GRP BOX, 100X40X30 CM - NEW8PCS68 54LIFEBUOY LIGHT, EXCL. BAT, INCL. BRACKET4PCS69-70 55FIRE EXT., FOAM, 50LTR, CART., A.B.S2PCS71-72 56FIRE EXT., FOAM, 150LTR, CART., A.B.S1PCS73-74 57CART, FOR 50LTR FOAM, EXT, A.B.S1PCS75 58CART, FOR 150LTR FOAM, EXT, A.B.S1PCS76 59NYLON CLIP FOR LIFEBUOY LIGHT, SDM4PCS60FIRE HOSE, STD., 2.5", 10M, STZ-65, ALU8PCS42 61SHIP PACKAGE, ALU. w/BULLARD HELMET3PCS77 62SOLAS RIGID LIFEJACKET, X-CONCEPT, CHILD3PCS78 63SOLAS RIGID LIFEJACKET, X-CONCEPT, ADULT43PCS79Pls find latest authorized Viking Servicing Stations atITEM NO.: 1001236Short Handled Fireman AxeLenght : 34 mm. Weight : 1 Kg.The fire brigade hatchet according to the new DIN 14924 – FDB substitutes the previous hatchet and offers additional benefits in mission. Due to the integratedthree edged wedge further tools as e.g. key for locking post are no longer necessary.Drop forged head made of high quality steel, clean sharpened blade, accurate processing,hardened steel pipe shafts, slip proof ergonomic rubber handle.ITEM NO.: 1004258D-BatteryThe signal lamp uses one battery (D-battery)Battery for signal lampThe Ocenco M-20.2 compressed oxygen EEBD (Emergency Escape Breathing Device) provides up to 32 minutes of protection.The Ocenco M-20.2 EEBD can be donned in seconds; simply unlatch the case, pull out the unit, and insert the mouthpiece and nose clip. The attached hood can be donned atanytime during the escape.The compressed oxygen andmouthpiece combination allows theOcenco M-20.2 EEBD to be donnedin a smoke filled environment.The compact Ocenco M-20.2 EEBDcan be belt worn in all confined spaces.Quick, easy use —The Ocenco M-20.2 EEBD - THE WORLD’SSMALLEST AND MOST DURABLE EEBD.Think of it as a Life Preserver You Wear on Your BeltTHE OCENCO M-20.2 EEBD:ACCESSORIES M-20.2T Trainer — complete with two extra mouthpieces, in a lightblue secondary container. Teaches donning from both the worn andstored position.M-20.2 Secondary container — included with each M-20.2 but may be ordered separately.M-20.2 Storage bracket — Bright orange welded steel bracket with quick opening Velcro ™ closure.Typical performance duration 15-32 minutesDonning timeless than 10 seconds Weight3.1 lbs (1.4 kg)DimensionsM-20.2 EEBD - 6.8 x 6.8 x 3 in (17 x 17 x 7.6 cm)Secondary Container - 8.2 x 9.2 x 4.2 in (21 x 23 x 10 cm)Storage temperature range-4°F to 149°F (-20° C to 65° C)Service life15 Years Oxygen delivery systemAutomatic on, compressed oxygen, demand regulatedInspectionAnnual visual for stored units M20.2 NSN No.NSN 1HM 4240-01-439-5937M-20.2T Trainer NSN No.NSN 1HM 4240-01-459-0078LakeView Corporate Park10225 82nd AvenuePleasant Prairie, WI 53158-5801U. S. A.Phone: (262) 947-9000Fax: (262) 947-9020 M-20.2 PHYSICAL CHARACTERISTICSAND PERFORMANCE DATABreathing bagPull cord Bottom caseRelief valve GaugeMouthpieceOxygen cylinderRegulatorM-20.2 EEBDEMERGENCY ESCAPEBREATHING DEVICETeflon is a registered trademark of the DuPont Corporation.® Teflon hoodWaist belt, safety belt with 2 D-rings, and 2 metre safety line with snap hook.Fire extinguisher, cartridge,6 KgSpare CO2 cartridge for 6 kg ABC Dry powder extinguisher (110g Zinc CO2 cartridge), Firesafe.Fire extinguisher, cartridge12 Kg, ABC Dry powderSpare CO2 cartridge for 12 kg ABC Dry powder extinguisher (225g Zinc CO2 cartridge), Firesafe.Fire extinguisher, cartridge, 9 liters AFF foamSpare CO2 cartridge for 9 Ltr. AFF foam extinguisher (75g PVC CO2 Cartridge), Firesafe.AFFF 6% foam 0,9 litre concentrate AFFF, 6% foam for fire extinguisher 0.9ltr in a bottle, Firesafe.Chemical Protective Suits Type GS 3The innovative design of the lightweight suits combines improved mechanical strength with a chemical protection barrier against a wide range of chemical and biological hazards. Additionally, the GS 3 SYKA®N 4 offers you as the only one worldwide real heat protection out of KEVLAR®. Quality of the future made in Germany !Suit description:Single piece protective suit with a gas proof elastic rubber seal in the hood for secure fit under full face masks. The suit is cut in such a way that a liquid- and gas-proof zip fastener, integrated horizontally from arm to arm across the back, makes it easy to take the suit on and off. Exchangeable chemical protection gloves and boots type S1 are added in exchange technology. Available in various materials:SYKAN® 2 material description:SYKAN® 2 has a reinforcement fabric made of polyester that is coated with an orange-coloured elastomer. Additionally SYKAN® 2 offers a very economical end price to the consumer through its optimised manufacturing process.Additionally Informations:•Breathing apparatus: worn outside (not supplied)•weight GS 3 SYKAN® 2: approx. 2,5 kg without parts (gloves and boots)•EN Type class (both suits): Category III- part 1 and 2 – Type 1b ET –PSA-Guideline 89/686/EU – MED certification•Boots: S1 FPA (Size 46) EN 345 – Quick Exchange System •Gloves: WIPAN® C – Quick Exchange SystemOrder data:•GS 3 SYKAN® 2 0222-212ITEM NO.: 1022167Fire Proof Safety Line30 m Safety line complate with snap hook at both ends Fire proof safety lineApproved according to MED/SOLASFireproof life line with thimble at both ends with two snaphooks. Length: 30 mtr.Bright Star Lighting Products Engineering Data Sheet: 2317CLifebuoyMED approved by GL with Wheel Mark:Complies with latest requirement of SOLAS'74/96 and LSA Code Completed with retro-reflective strapsDiamention: 720x440x105mmBuoyancy not less than 14.5kgColour: OrangeMaximum stowage height: 50mCode 542 Type XT5555, 2.5kgCode 558 Type XT5555-1, 4.3kgFloating line, orange, for lifebuoyDiameter: 8 mm.Length: 30 m.ITEM NO.: 1022628Description : Line 8 mm. Life Buoy, OrangeDescription of Raw material : High tenacity Polypropylene multifilament, 2% UV Breaking strength min. : 9.20 Kn.Application temp. : -30 to +65 °C.Min. Weight per mtr. : 28 grs.AQUEOUS FILM FORMING FOAM EXTINGUISHING AGENTModel: AFFF6%Technical Specifications1 Specific Gravity (g/cm3) （20℃）: 1.00~1.052. Viscosity（20℃）pa.s : ≤0.0203. Appearance : pale yellow liquidChemical family : surfactant mixture firefighting4. PH: 7.5-8.55. Sediment % V/V ≤0.16. Spreading coefficient (mN/m) Positive numberpatibility : different types of foam concentrate should not be mixed under any circumstances-8.Freezing point : ≤ - 10℃9.Stability : stable10.Expansion : 6.5±20%11.1/4 drainage time : minutes 2.5±20%12.Manufacturing date : not more than six months of placing the order13. Unit of measurement: liter -14. Storage temperature: －2.5℃~ 49℃15. Product Shelflife : 8~10 Years16. Fire extinguishing Time min ≤317. Burn-back time,min ≥ 152(Remark: The area of the fire test vat is 4.52 m, the fire test fuel is 150 liters petrol )18 GOOD COMPATIBILITY WITH DRY CHEMICAL POWDERTESTING STANDARD: ISO 7203 - 1 or China National Standard:GB 15308-2006MATERIAL SAFETY DATA SHEETFor SL - AFFF3%AQUEOUS FILM FORMING FOAM EXTINGUISHING AGENT(AFFF) (Liquid Concentrate)Section 1 –CHEMICAL PRODUCT AND COMPANY IDENTIFICATIONMaterial IdentificationProduct: AFFF3% Aqueous Film Forming Foam Extinguishing Agent Synonyms: AFFF3% Fire Fighting Foam ConcentrateCAS No: Mixture - No single CAS # applicableCompany IdentificationManufacturer:Xinghua Suolong Fire Extinguishing Agents Co., Ltd.Address:No. 109 Fengshou south Road, Xinghua, Jiangsu, ChinaTel:(86)523-82300896 Fax: (86)523-83262095E-mail: suolong@ , Website: Section 2 - COMPOSITION / INFORMATION ON INGREDIENTS40~50 % Distilled water CAS:7732-18-520~30% vesicant from Synthetic Detergents Proprietary Mixture,no single CAS Number applicable0.3~1% amylose（rank: touchable） CAS: 9004-53-90.5%- 5% Fluoro surfactant Confidential Polymer1~10% Ethylene glycol CAS: 107-21-11~15% butyl glycol ether 112-34-51~10% urea 89774-74-3Section 3 - HAZARDS IDENTIFICATIONPotential Health EffectsInhalationVapors are minimal at room temperature. If product is heated or sprayed as an aerosol, airborne material may cause respiratory irritation.Skin ContactContact with liquid may cause moderate irritation or dermatitis due to removal of oils from the skin.Eye ContactProduct is an eye irritant.IngestionNot a hazard in normal industrial use. Small amounts swallowed during normal handling operations are not likely to cause injury; swallowing large amounts may cause injury or irritation.Carcinogenicity InformationNo data available.Section 4 - FIRST AID MEASURESInhalationNo specific treatment is necessary since this material is not likely to be hazardous by inhalation.If exposed to excessive levels of airborne aerosol mists, remove to fresh air. Seek medica attention if effects occur.Skin ContactIn case of skin contact, wash off in flowing water or shower. Launder clothing before reuse.Eye ContactIn case of eye contact, flush eyes promptly with water for 15 minutes. Retract eyelids often to ensure thorough rinsing. Consult a physician if irritation persists.IngestionSwallowing less than an ounce is not expected to cause significant harm. For larger amounts, do not induce vomiting. Give milk or water. Never give anything by mouth to an unconscious person. Seek medical attention.Section 5 - FIRE FIGHTING MEASURESFlammable PropertiesFlash Point - Not applicableFire and Explosion HazardsAvoid contact with water reactive materials, burning metals and electrically energized equipment.Extinguishing MediaProduct is an extinguishing media. Use media appropriate for surrounding materials.Special Fire Fighting InstructionsThis product will produce foam when mixed with water.Section 6 - ACCIDENTAL RELEASE MEASURESSafeguards (Personnel)NOTE: Review FIRE FIGHTING MEASURES and HANDLING (Personnel) sections before proceeding with clean-up. Use appropriate Personal Protective Equipment during clean-up.Accidental Release MeasuresConcentrateStop flow if possible. Use appropriate protective equipment during clean up. For small volume releases, collect spilled concentrate with absorbent material; place in approved container. For large volume releases, contain and collect for use where possible. Flush area with water until it no longer foams. Exercise caution, surfaces may be slippery. Prevent discharge of concentrate to waterways. Disposal should be made in accordance with National , federal, state and local regulations.Foam/Foam SolutionSee above. Flush with water. Prevent discharge of foam/foam solution to waterways. Do not discharge into biological sewer treatment systems without prior approval. Disposal should be made in accordance with National , federal, state and local regulations.Section 7 – HANDLING AND STORAGEHandling (Personnel)Avoid contact with eyes, skin or clothing. Avoid ingestion or inhalation. Rinse skin and eyes thoroughly in case of contact. Review HAZARDS and FIRST AID sections. StorageRecommended storage environment is between －2.5℃ and 49℃. Store product in original shipping container or tanks designed for product storage.Section 8- EXPOSURE CONTROLS/PERSONAL PROTECTIONEngineering ControlsSpecial ventilation is not required.Personal Protective EquipmentRespiratoryRecommended exposure limits have not been determined for this material. Respiratory protection not needed for normal use.The need for respiratory protection should be evaluated by a qualified health specialist.Protective ClothingRubber or PVC gloves recommended.Eye ProtectionSafety glasses, face shield or chemical splash goggles must be worn when possibility exists for eye contact. Contact lenses should not be worn. Eye wash facilities are recommended.Other Hygienic PracticesUse good personal hygiene practices. Wash hands before eating, drinking, smoking, or using toilet facilities. Promptly remove soiled clothing and wash thoroughly before reuse.Exposure GuidelinesExposure Limits(2-Methoxymethylethoxy) Propanol (34590-94-8)PEL(OSHA)100 ppm, 8 hr. TWA Skin150 ppm, 15 min. STEL SkinTLV (ACGIH)100 ppm, 8 hr. TWA Skin150 ppm, 15 min. STEL SkinSection 9- PHYSICAL AND CHEMICAL PROPERTIESPhysical DataAppearance and colour: Pale yellow liquidBoiling Point: Not applicableVapor Pressure: Not applicableVapor Density: Not applicableMelting Point: Not applicableEvaporation Rate: <1 (Butyl Acetate = 1.0)Solubility in Water: 100%pH: 7.5-8.5Specific Gravity: 1.02 @ 25℃Odor: Mild, pleasantSection 10 - STABILITY AND REACTIVITYChemical StabilityStable.Incompatibility, Materials to AvoidAvoid use of product on burning metals, electrically-energized equipment and contact with water reactive materials.PolymerizationWill not occur.Section Section 11 - TOXICOLOGICAL INFORMATIONMammalian ToxicityIngestionThis material was not toxic when administered to Wistar Albino rats at an acute oral dose of 5g/kg body weight.EyeAnimal testing indicates this material is a primary eye irritant when tested undiluted on New Zealand Albino Rabbits.SkinAnimal testing indicates this material is not a primary skin irritant when tested undiluted on New Zealand Albino Rabbits.InhalationNo data available at this time.Carcinogenic, Developmental, Reproductive, Mutagenic EffectsNo data available on this material.Section 12 - ECOLOGICAL INFORMATIONAdopt good working practices, so that the product is not released into the environment.BIODEGRADABLESection 13 -DISPOSAL CONSIDERATIONSIn so doing, comply with the local and national regulations currently in force. ConcentrateDo not discharge into biological sewer treatment systems without prior approval. Specific concerns are high BOD load and foaming tendency. Low dosage flow rate or antifoaming agents acceptable to the treatment plant may be helpful. Do not flush to waterways. Disposal should be made in accordance with the local and national regulations.Foam/Foam SolutionOur AFFF 3% foam solution can be treated by waste water treatment facilities. Discharge into biological sewer treatment facilities may be done with prior approval. Specific concerns are high BOD load. Dilution will reduce BOD and COD factors proportionately. Low dosage flow rate or antifoaming agents acceptable to the treatment plant may be helpful. Do not flush to waterways. Disposal should be made in accordance with the local and national regulations.NOTE: As a service to our customers, Xinghua Suolong Fire Extinguishing Agents Co., Ltd. has approvals in place with disposal facilities for waste water treatment and solidification and landfill of our foam liquid concentrates and foam solutions. If required, Xinghua Suolong Fire Extinguishing Agents Co., Ltd. can also provide information on the disposal of drums used for shipping our concentrates. Please contact Xinghua Suolong Fire Extinguishing Agents Co., Ltd. by Tel: (86)523-82300896 E-mail: suolong@ for additional information.Section 14 - TRANSPORTATION INFORMATIONShipping InformationHazard Class: NoneOTHER REGULATORY INFORMATIONNone.Section 15 - REGULATORY INFORMATIONIrritantIrritating to eyes.In case of contact with eyes, rinse immediately with plenty of water and seek medical advice.Avoid contact with skin and eyes.Section 16 - OTHER INFORMATIONCFPA RatingHealth 0Flammability 0Reactivity 0For further information, see Xinghua Suolong Fire Extinguishing Agents Co., Ltd. product description for SL-AFFF3% , AFFF3%.The information contained herein is furnished without warranty either expressed or implied. This data sheet is not a part of any contract of sale. The information contained herein is believed to be correct or is obtained from sources believed to be generally reliable.However, it is the responsibility of the user of these materials to investigate, understand and comply with national and local guidelines and procedures for safe handling and use of these materials. Xinghua Suolong Fire Extinguishing Agents Co., Ltd. shall not be liable for any loss or damage arising directly or indirectly from the use of this product and Xinghua Suolong Fire Extinguishing Agents Co., Ltd. assumes no obligation or liabilities for reliance on the information contained herein or omissionsherefrom.August 10, 2006Xinghua Suolong Fire Extinguishing Agents Co., Ltd.Test Report of the ProductName of product:Aqueous Film Forming Foam Extinguishing Agent Model: AFFF6% Purchaser: SENOUSSI FREE ZONE CO.Batch No.: 0804SM60804Test Item Technology Requests(testing standard:GB15308-2006)Resultfreezing point ℃－10℃- 4－13℃Acidity(PH) 20℃7.0 - 8.5 8.2 Spreading Coefficient (mN/m) Positive number 2.6 Foam expansion ratio 6.5±20% 7.1 25% Drainage time (min) 2.5±20% 2.4Fire extinguishingTime min ≤5 2.8Gentle applicationtest method 25% burn-backtime;min≥15 15.2Fire Extinguishing PerformanceForceful application test method Fire extinguishingTimemin≤3 2.9Goods Quantity: Ten tons.Production Date:April 16, 2008Verified by: Checked by: Prepared by:MATERIAL SAFETY DATA SHEETFor SL - ABC DRY POWDERABC POWDER EXTINGUISHING AGENT (ABC DRY POWDER)Section 1 –CHEMICAL PRODUCT AND COMPANY IDENTIFICATIONMaterial IdentificationProduct: 40% ABC ABC POWDER EXTINGUISHING AGENTSynonyms: ABC DRY POWDERCAS No: Mixture - No single CAS # applicableCompany IdentificationManufacturer:Xinghua Suolong Fire Extinguishing Agents Co., Ltd.Address:No. 109 Fengshou south Road, Xinghua, Jiangsu, ChinaTel:(86)523-82300896 Fax: (86)523-83262095E-mail: suolong@ , ma.jianmin119@ Website: Section 2 - COMPOSITION / INFORMATION ON INGREDIENTS40±3% Monoammonium Phosphate CAS:7722-76-110~15% Ammonium Sulfate , CAS: 7783-20-210% Silica White CAS: 7631-86-910% Activated clay CAS: 70131-50-910% Mica Powder5% Dimethyl Silicone Oil CAS: 9006-65-9Section 3 - HAZARDS IDENTIFICATIONPotential Health EffectsHarmful if swallowedIrritating to eyes. respiratory system and skin.In case of contact with eyes, rinse immediately with plenty of water and seek medical advice.Wear suitable protective clothing.As part of good industrial and personal hygiene and safety procedure, avoid all unnecessary exposure to the chemical substance and ensure prompt removal from skin, eyes and clothing.Eye ContactMildly irritating for short periods of time.Skin ContactMay be mildly irritatingInhalationTreat as a mineral dust irritant to the respiratory tract. Transient cough, shortness of breath.IngestionNot an expected route of entry.Carcinogenicity InformationNo data available.For Environment:No data available.Section 4 - FIRST AID MEASURESEye ContactIn case of eye contact, flush eyes promptly with water for 15 minutes.If irritation persists,seek medical attention.Skin ContactWash affected area with soap and water. Launder clothing before reuse. InhalationRemove from exposure. If irritation persists,seek medical attention.IngestionIf patient is conscious, give large amounts of water and induce vomiting. seek medical help.Section 5 - FIRE FIGHTING MEASURESThis product is an extinguishing media.No special proective equipment is needed for fire-fighters. Wear protective equipment appropriate for the fire conditions.Section 6 - ACCIDENTAL RELEASE MEASURESFor Personnel Protection:Prevent skin and eye contact.Clean up:Sweep up and recover for use or place in closed container for disposal.No harm to the environment is expected from an accidental release of this product.Section 7 – HANDLING AND STORAGEHandling (Personnel)Avoid contact with eyes, skin. Avoid ingestion or inhalation. Rinse skin and eyes thoroughly in case of contact. Review HAZARDS and FIRST AID sections. StorageThe product should be stored in a cool, and dry environment. Exposure to humidity and damp environments will negatively affect its performance.Specific use:The intended use of this product is as a Fire Extinguishing Agent.Section 8- EXPOSURE CONTROLS/PERSONAL PROTECTIONExposure controls:Respiratory Protection:Dust mask where dustiness is prevalent.Hand Protection:None normally needed. Use chemical resistant gloves when handling the product. Eye Protection:Safety glasses or safety goggles.Skin Protection:No special equipment is needed.Environmental exposure controls:No special controls are needed.Section 9- PHYSICAL AND CHEMICAL PROPERTIESGeneral information:Appearance : powderColour: yellow or pinkPhysical DataPH: Not determinedBoiling Point: Not applicableFlash Point:NoneFlammability: Not flammableExplosive properties: Not explosiveOxidizing properties: Not an oxidizerVapor Pressure: Not applicableVapor Density: Not applicableRelative density: Not applicableSolubility in Water: slightSolubility in Fat: Not solubleSection 10 - STABILITY AND REACTIVITYChemical StabilityStable.Incompatibility, Materials to AvoidNo data available.Hazardous decomposition products:Normally stableHazardous polymerization will not occur.Ammonia and/or phosphorous oxides can be evolved at very high temperatures. Section Section 11 - TOXICOLOGICAL INFORMATIONThis product has not be tested for toxicological effects. Product is treated as a nuisance dust.Components:Monoammonium Phosphate:Material is irritatingHarmful if swallowed.Ammonium sulphate:Toxicity Data:Oral(rat) LD50 2840 mg/kgTarget Organs:Lungs and gestrointestinal.Section 12 - ECOLOGICAL INFORMATIONEcotoxicity:Not determinedPersistance and degradability:Not determinedbioaccumulative potential:Not determinedother adverse effects:ozone depletion potential: NoneGlobal warning potential: NoneSection 13 -DISPOSAL CONSIDERATIONSNo harm to the environment is expected from this product.Dispose of in compliance with national, regional ,and local provisions that may be in force.Section 14 - TRANSPORTATION INFORMATIONHazard Class or Division: Not a hazardous substance.No harm to the environment is expected from this product.Section 15 - REGULATORY INFORMATIONHarmful if swallowed.Irritating to eyes. respiratory system and skin.In case of contact with eyes, rinse immediately with plenty of water and seek medical advice.Wear suitable protective clothing.Environmental restrictions:None are knownRefer to any other national measures that may be relevant.Section 16 - OTHER INFORMATIONCFPA RatingHealth 0Flammability 0Reactivity 0For further information, see Xinghua Suolong Fire Extinguishing Agents Co., Ltd.product description for SL-ABC DRY POWDER, ABC 40%.The information contained herein is furnished without warranty either expressed or implied. This data sheet is not a part of any contract of sale. The information contained herein is believed to be correct or is obtained from sources believed to be generally reliable.However, it is the responsibility of the user of these materials to investigate, understand and comply with national and local guidelines and procedures for safe handling and use of these materials. Xinghua Suolong Fire Extinguishing Agents Co., Ltd. shall not be liable for any loss or damage arising directly or indirectly from the use of this product and Xinghua Suolong Fire Extinguishing Agents Co., Ltd. assumes no obligation or liabilities for reliance on the information contained herein or omissionsherefrom.March 10, 20067Page 1of 1http://www.jakob-eschbach.de/en/img/seiten/en_synthetic_special_500.jpg11/9/2006Neck cover for Bullard fire helmet (1024995)ITEM NO.: 1024862Detachable leather cover.Page 1 of 1Visor for Bullard fire helmet (1024995)ITEM NO.: 1024863Detachable.Page 1 of 1。
IoC-DI容器
本质：创建对象和装配对象、管理对象生命周期 //返回装配好的a 被动实例化，被动接受依赖，被动装配 A a = ApplicationContext.getBean(“a”); （工厂+反射+xml配置文件） <!—配置文件--> <bean id=“a” class=“AImpl”> <property name=“b” ref=“b”/> </bean> <bean id=“b” class=“BImpl”/>
通用
应用程序 类Client
类AImpl
类BImpl
Spring框架（IoC容器）
《深入浅出学Spring3开发》——系列精品教程 深入浅出学Spring3开发》 Spring3开发 系列精品教程
IoC容器：实现了IoC思想的容器就是 容器：实现了 思想的容器就是IoC容器 容器 思想的容器就是 容器 IoC容器特点： 容器特点： 容器特点 【1】无需主动new对象；而是描述对象应该如何被创建即可 】 IoC容器帮你创建，即被动实例化； 容器帮你创建， 容器帮你创建 即被动实例化； 【2】不需要主动装配对象之间的依赖关系，而是描述需要哪个服务（组件）， IoC容器会帮你装配（即负责将它们关联在一起），被动接受装配； 容器会帮你装配（ ），被动接受装配 容器会帮你装配 即负责将它们关联在一起），被动接受装配； 【3】主动变被动，好莱坞法则：别打电话给我们，我们会打给你； 【4】迪米特法则（最少知识原则）：不知道依赖的具体实现，只知道需要提供 某类服务的对象（面向接口编程），松散耦合，一个对象应当对其他对象有尽 可能少的了解,不和陌生人（实现）说话 【5】IoC是一种让服务消费者不直接依赖于服务提供者的组件设计方式， 是一种减少类与类之间依赖的设计原则。 理解IoC容器问题关键：控制的哪些方面被反转了？ 容器问题关键： 理解 容器问题关键 容器控制， 容器控制 而以前是应用程序控制， 1、谁控制谁？为什么叫反转？ IoC容器控制，而以前是应用程序控制，所以叫反转 控制应用程序所需要的资源（对象、文件……） ） 2、控制什么？ 控制应用程序所需要的资源（对象、文件 3、为什么控制？ 解耦组件之间的关系 程序的控制权发生了反转： 4、控制的哪些方面被反转了？ 程序的控制权发生了反转：从应用程序转移到了 IoC容器。 容器。 容器
上汽股份有限公司技术中心企业技术标准-通用电器零部件测试
上汽股份有限公司技术中心 技术标准化委员会
发布 Issue
Technical Standardization Committee of SAIC Motor Technical Center
SMTC 3 800 001—2010
目次
前 言 .......................................................................... IV 通用电器零部件测试标准...................................................................................................................5 1 范围和目的.......................................................................................................................................5 1 Scope and application of purpose ..........................................................................................5 2 总体信息和缩略词...........................................................................................................................5 2 General Information, Abbreviation ......
NFPA30-2008-Chinese
Definition and Classification of Liquids ......................................... 30–20 液体的定义和分类
应用
1.4 Retroactivity ..................................... 30–13 4.1
.................................... 30–28
每个控制区液体超过分类允许的最大量
9.9 Construction Requirements .................
30–29
建筑要求
9.10 Fire Protection
................................. 30–29
通风
9.15 Exhausted Enclosures. (Reserved)
30–32
........ 30–30
应急控制系统（保留）
排气的
9.16
（保留）
Explosion Control ............................. 30–30
爆炸控制
9.17 Separation from Incompatible Materials
等价
1.6 Symbols, Units, and Formulas
.......... 30–20
第四章定义说明 .............. 30–14
4.3 Classification of Liquids ...................... 30–20
符号、单位和公式
1.7 Code Adoption Requirements. (Reserved) ....................................... 30–14
毕业设计论文外文文献翻译
xxxx大学xxx学院毕业设计（论文）外文文献翻译系部xxxx专业xxxx学生姓名xxxx 学号xxxx指导教师xxxx 职称xxxx2013年3 月Introducing the Spring FrameworkThe Spring Framework: a popular open source application framework that addresses many of the issues outlined in this book. This chapter will introduce the basic ideas of Spring and dis-cuss the central “bean factory” lightweight Inversion-of-Control (IoC) container in detail.Spring makes it particularly easy to implement lightweight, yet extensible, J2EE archi-tectures. It provides an out-of-the-box implementation of the fundamental architectural building blocks we recommend. Spring provides a consistent way of structuring your applications, and provides numerous middle tier features that can make J2EE development significantly easier and more flexible than in traditional approaches.The basic motivations for Spring are:To address areas not well served by other frameworks. There are numerous good solutions to specific areas of J2EE infrastructure: web frameworks, persistence solutions, remoting tools, and so on. However, integrating these tools into a comprehensive architecture can involve significant effort, and can become a burden. Spring aims to provide an end-to-end solution, integrating spe-cialized frameworks into a coherent overall infrastructure. Spring also addresses some areas that other frameworks don’t. For example, few frameworks address generic transaction management, data access object implementation, and gluing all those things together into an application, while still allowing for best-of-breed choice in each area. Hence we term Spring an application framework, rather than a web framework, IoC or AOP framework, or even middle tier framework.To allow for easy adoption. A framework should be cleanly layered, allowing the use of indi-vidual features without imposing a whole worldview on the application. Many Spring features, such as the JDBC abstraction layer or Hibernate integration, can be used in a library style or as part of the Spring end-to-end solution.To deliver ease of use. As we’ve noted, J2EE out of the box is relatively hard to use to solve many common problems. A good infrastructure framework should make simple tasks simple to achieve, without forcing tradeoffs for future complex requirements (like distributed transactions) on the application developer. It should allow developers to leverage J2EE services such as JTA where appropriate, but to avoid dependence on them in cases when they are unnecessarily complex.To make it easier to apply best practices. Spring aims to reduce the cost of adhering to best practices such as programming to interfaces, rather than classes, almost to zero. However, it leaves the choice of architectural style to the developer.Non-invasiveness. Application objects should have minimal dependence on the framework. If leveraging a specific Spring feature, an object should depend only on that particular feature, whether by implementing a callback interface or using the framework as a class library. IoC and AOP are the key enabling technologies for avoiding framework dependence.Consistent configuration. A good infrastructure framework should keep application configuration flexible and consistent, avoiding the need for custom singletons and factories. A single style should be applicable to all configuration needs, from the middle tier to web controllers.Ease of testing. Testing either whole applications or individual application classes in unit tests should be as easy as possible. Replacing resources or application objects with mock objects should be straightforward.To allow for extensibility. Because Spring is itself based on interfaces, rather than classes, it is easy to extend or customize it. Many Spring components use strategy interfaces, allowing easy customization.A Layered Application FrameworkChapter 6 introduced the Spring Framework as a lightweight container, competing with IoC containers such as PicoContainer. While the Spring lightweight container for JavaBeans is a core concept, this is just the foundation for a solution for all middleware layers.Basic Building Blockspring is a full-featured application framework that can be leveraged at many levels. It consists of multi-ple sub-frameworks that are fairly independent but still integrate closely into a one-stop shop, if desired. The key areas are:Bean factory. The Spring lightweight IoC container, capable of configuring and wiring up Java-Beans and most plain Java objects, removing the need for custom singletons and ad hoc configura-tion. Various out-of-the-box implementations include an XML-based bean factory. The lightweight IoC container and its Dependency Injection capabilities will be the main focus of this chapter.Application context. A Spring application context extends the bean factory concept by adding support for message sources and resource loading, and providing hooks into existing environ-ments. Various out-of-the-box implementations include standalone application contexts and an XML-based web application context.AOP framework. The Spring AOP framework provides AOP support for method interception on any class managed by a Spring lightweight container.It supports easy proxying of beans in a bean factory, seamlessly weaving in interceptors and other advice at runtime. Chapter 8 dis-cusses the Spring AOP framework in detail. The main use of the Spring AOP framework is to provide declarative enterprise services for POJOs.Auto-proxying. Spring provides a higher level of abstraction over the AOP framework and low-level services, which offers similar ease-of-use to .NET within a J2EE context. In particular, the provision of declarative enterprise services can be driven by source-level metadata.Transaction management. Spring provides a generic transaction management infrastructure, with pluggable transaction strategies (such as JTA and JDBC) and various means for demarcat-ing transactions in applications. Chapter 9 discusses its rationale and the power and flexibility that it offers.DAO abstraction. Spring defines a set of generic data access exceptions that can be used for cre-ating generic DAO interfaces that throw meaningful exceptions independent of the underlying persistence mechanism. Chapter 10 illustrates the Spring support for DAOs in more detail, examining JDBC, JDO, and Hibernate as implementation strategies.JDBC support. Spring offers two levels of JDBC abstraction that significantly ease the effort of writing JDBC-based DAOs: the org.springframework.jdbc.core package (a template/callback approach) and the org.springframework.jdbc.object package (modeling RDBMS operations as reusable objects). Using the Spring JDBC packages can deliver much greater pro-ductivity and eliminate the potential for common errors such as leaked connections, compared with direct use of JDBC. The Spring JDBC abstraction integrates with the transaction and DAO abstractions.Integration with O/R mapping tools. Spring provides support classesfor O/R Mapping tools like Hibernate, JDO, and iBATIS Database Layer to simplify resource setup, acquisition, and release, and to integrate with the overall transaction and DAO abstractions. These integration packages allow applications to dispense with custom ThreadLocal sessions and native transac-tion handling, regardless of the underlying O/R mapping approach they work with.Web MVC framework. Spring provides a clean implementation of web MVC, consistent with the JavaBean configuration approach. The Spring web framework enables web controllers to be configured within an IoC container, eliminating the need to write any custom code to access business layer services. It provides a generic DispatcherServlet and out-of-the-box controller classes for command and form handling. Request-to-controller mapping, view resolution, locale resolution and other important services are all pluggable, making the framework highly extensi-ble. The web framework is designed to work not only with JSP, but with any view technology, such as Velocity—without the need for additional bridges. Chapter 13 discusses web tier design and the Spring web MVC framework in detail.Remoting support. Spring provides a thin abstraction layer for accessing remote services without hard-coded lookups, and for exposing Spring-managed application beans as remote services. Out-of-the-box support is inc luded for RMI, Caucho’s Hessian and Burlap web service protocols, and WSDL Web Services via JAX-RPC. Chapter 11 discusses lightweight remoting.While Spring addresses areas as diverse as transaction management and web MVC, it uses a consistent approach everywhere. Once you have learned the basic configuration style, you will be able to apply it in many areas. Resources, middle tier objects, and web components are all set up using the same bean configuration mechanism. You can combine your entireconfiguration in one single bean definition file or split it by application modules or layers; the choice is up to you as the application developer. There is no need for diverse configuration files in a variety of formats, spread out across the application.Spring on J2EEAlthough many parts of Spring can be used in any kind of Java environment, it is primarily a J2EE application framework. For example, there are convenience classes for linking JNDI resources into a bean factory, such as JDBC DataSources and EJBs, and integration with JTA for distributed transaction management. In most cases, application objects do not need to work with J2EE APIs directly, improving reusability and meaning that there is no need to write verbose, hard-to-test, JNDI lookups.Thus Spring allows application code to seamlessly integrate into a J2EE environment without being unnecessarily tied to it. You can build upon J2EE services where it makes sense for your application, and choose lighter-weight solutions if there are no complex requirements. For example, you need to use JTA as transaction strategy only if you face distributed transaction requirements. For a single database, there are alternative strategies that do not depend on a J2EE container. Switching between those transac-tion strategies is merely a matter of configuration; Spring’s consistent abstraction avoids any need to change application code.Spring offers support for accessing EJBs. This is an important feature (and relevant even in a book on “J2EE without EJB”) because the u se of dynamic proxies as codeless client-side business delegates means that Spring can make using a local stateless session EJB an implementation-level, rather than a fundamen-tal architectural, choice.Thus if you want to use EJB, you can within a consistent architecture; however, you do not need to make EJB the cornerstone of your architecture. This Spring feature can make devel-oping EJB applications significantly faster, because there is no need to write custom code in service loca-tors or business delegates. Testing EJB client code is also much easier, because it only depends on the EJB’s Business Methods interface (which is not EJB-specific), not on JNDI or the EJB API.Spring also provides support for implementing EJBs, in the form of convenience superclasses for EJB implementation classes, which load a Spring lightweight container based on an environment variable specified in the ejb-jar.xml deployment descriptor. This is a powerful and convenient way of imple-menting SLSBs or MDBs that are facades for fine-grained POJOs: a best practice if you do choose to implement an EJB application. Using this Spring feature does not conflict with EJB in any way—it merely simplifies following good practice.Introducing the Spring FrameworkThe main aim of Spring is to make J2EE easier to use and promote good programming practice. It does not reinvent the wheel; thus you’ll find no logging packages in Spring, no connection pools, no distributed transaction coordinator. All these features are provided by other open source projects—such as Jakarta Commons Logging (which Spring uses for all its log output), Jakarta Commons DBCP (which can be used as local DataSource), and ObjectWeb JOTM (which can be used as transaction manager)—or by your J2EE application server. For the same reason, Spring doesn’t provide an O/R mapping layer: There are good solutions for this problem area, such as Hibernate and JDO.Spring does aim to make existing technologies easier to use. For example, although Spring is not in the business of low-level transactioncoordination, it does provide an abstraction layer over JTA or any other transaction strategy. Spring is also popular as middle tier infrastructure for Hibernate, because it provides solutions to many common issues like SessionFactory setup, ThreadLocal sessions, and exception handling. With the Spring HibernateTemplate class, implementation methods of Hibernate DAOs can be reduced to one-liners while properly participating in transactions.The Spring Framework does not aim to replace J2EE middle tier services as a whole. It is an application framework that makes accessing low-level J2EE container ser-vices easier. Furthermore, it offers lightweight alternatives for certain J2EE services in some scenarios, such as a JDBC-based transaction strategy instead of JTA when just working with a single database. Essentially, Spring enables you to write appli-cations that scale down as well as up.Spring for Web ApplicationsA typical usage of Spring in a J2EE environment is to serve as backbone for the logical middle tier of a J2EE web application. Spring provides a web application context concept, a powerful lightweight IoC container that seamlessly adapts to a web environment: It can be accessed from any kind of web tier, whether Struts, WebWork, Tapestry, JSF, Spring web MVC, or a custom solution.The following code shows a typical example of such a web application context. In a typical Spring web app, an applicationContext.xml file will reside in the WEB-INF directory, containing bean defini-tions according to the “spring-beans” DTD. In such a bean definition XML file, business objects and resources are defined, for example, a “myDataSource” bean, a “myInventoryManager” bean, and a “myProductManager” bean. Spring takes care of their configuration, their wiring up, and their lifecycle.<beans><bean id=”myDataSource” class=”org.springframework.jdbc. datasource.DriverManagerDataSource”><property name=”driverClassName”> <value>com.mysql.jdbc.Driver</value></property> <property name=”url”><value>jdbc:mysql:myds</value></property></bean><bean id=”myInventoryManager” class=”ebusiness.DefaultInventoryManager”> <property name=”dataSource”><ref bean=”myDataSource”/> </property></bean><bean id=”myProductManager” class=”ebusiness.DefaultProductManage r”><property name=”inventoryManager”><ref bean=”myInventoryManager”/> </property><property name=”retrieveCurrentStock”> <value>true</value></property></bean></beans>By default, all such beans have “singleton” scope: one instance per context. The “myInventoryManager” bean will automatically be wired up with the defined DataSource, while “myProductManager” will in turn receive a reference to the “myInventoryManager” bean. Those objects (traditionally called “beans” in Spring terminology) need to expos e only the corresponding bean properties or constructor arguments (as you’ll see later in this chapter); they do not have to perform any custom lookups.A root web application context will be loaded by a ContextLoaderListener that is defined in web.xml as follows:<web-app><listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class></listener>...</web-app>After initialization of the web app, the root web application context will be available as a ServletContext attribute to the whole web application, in the usual manner. It can be retrieved from there easily via fetching the corresponding attribute, or via a convenience method in org.springframework.web. context.support.WebApplicationContextUtils. This means that the application context will be available in any web resource with access to the ServletContext, like a Servlet, Filter, JSP, or Struts Action, as follows:WebApplicationContext wac = WebApplicationContextUtils.getWebApplicationContext(servletContext);The Spring web MVC framework allows web controllers to be defined as JavaBeans in child application contexts, one per dispatcher servlet. Such controllers can express dependencies on beans in the root application context via simple bean references. Therefore, typical Spring web MVC applications never need to perform a manual lookup of an application context or bean factory, or do any other form of lookup.Neither do other client objects that are managed by an application context themselves: They can receive collaborating objects as bean references.The Core Bean FactoryIn the previous section, we have seen a typical usage of the Spring IoC container in a web environment: The provided convenience classes allow for seamless integration without having to worry about low-level container details. Nevertheless, it does help to look at the inner workings to understand how Spring manages the container. Therefore, we will now look at the Spring bean container in more detail, starting at the lowest building block: the bean factory. Later, we’ll continue with resource setup and details on the application context concept.One of the main incentives for a lightweight container is to dispense with the multitude of custom facto-ries and singletons often found in J2EE applications. The Spring bean factory provides one consistent way to set up any number of application objects, whether coarse-grained components or fine-grained busi-ness objects. Applying reflection and Dependency Injection, the bean factory can host components that do not need to be aware of Spring at all. Hence we call Spring a non-invasive application framework.Fundamental InterfacesThe fundamental lightweight container interface is org.springframework.beans.factory.Bean Factory. This is a simple interface, which is easy to implement directly in the unlikely case that none of the implementations provided with Spring suffices. The BeanFactory interface offers two getBean() methods for looking up bean instances by String name, with the option to check for a required type (and throw an exception if there is a type mismatch).public interface BeanFactory {Object getBean(String name) throws BeansException;Object getBean(String name, Class requiredType) throws BeansException;boolean containsBean(String name);boolean isSingleton(String name) throws NoSuchBeanDefinitionException;String[] getAliases(String name) throws NoSuchBeanDefinitionException;}The isSingleton() method allows calling code to check whether the specified name represents a sin-gleton or prototype bean definition. In the case of a singleton bean, all calls to the getBean() method will return the same object instance. In the case of a prototype bean, each call to getBean() returns an inde-pendent object instance, configured identically.The getAliases() method will return alias names defined for the given bean name, if any. This mecha-nism is used to provide more descriptive alternative names for beans than are permitted in certain bean factory storage representations, such as XML id attributes.The methods in most BeanFactory implementations are aware of a hierarchy that the implementation may be part of. If a bean is not foundin the current factory, the parent factory will be asked, up until the root factory. From the point of view of a caller, all factories in such a hierarchy will appear to be merged into one. Bean definitions in ancestor contexts are visible to descendant contexts, but not the reverse.All exceptions thrown by the BeanFactory interface and sub-interfaces extend org.springframework. beans.BeansException, and are unchecked. This reflects the fact that low-level configuration prob-lems are not usually recoverable: Hence, application developers can choose to write code to recover from such failures if they wish to, but should not be forced to write code in the majority of cases where config-uration failure is fatal.Most implementations of the BeanFactory interface do not merely provide a registry of objects by name; they provide rich support for configuring those objects using IoC. For example, they manage dependen-cies between managed objects, as well as simple properties. In the next section, we’ll look at how such configuration can be expressed in a simple and intuitive XML structure.The sub-interface org.springframework.beans.factory.ListableBeanFactory supports listing beans in a factory. It provides methods to retrieve the number of beans defined, the names of all beans, and the names of beans that are instances of a given type:public interface ListableBeanFactory extends BeanFactory {int getBeanDefinitionCount();String[] getBeanDefinitionNames();String[] getBeanDefinitionNames(Class type);boolean containsBeanDefinition(String name);Map getBeansOfType(Class type, boolean includePrototypes,boolean includeFactoryBeans) throws BeansException}The ability to obtain such information about the objects managed by a ListableBeanFactory can be used to implement objects that work with a set of other objects known only at runtime.In contrast to the BeanFactory interface, the methods in ListableBeanFactory apply to the current factory instance and do not take account of a hierarchy that the factory may be part of. The org.spring framework.beans.factory.BeanFactoryUtils class provides analogous methods that traverse an entire factory hierarchy.There are various ways to leverage a Spring bean factory, ranging from simple bean configuration to J2EE resource integration and AOP proxy generation. The bean factory is the central, consistent way of setting up any kind of application objects in Spring, whether DAOs, business objects, or web controllers. Note that application objects seldom need to work with the BeanFactory interface directly, but are usu-ally configured and wired by a factory without the need for any Spring-specific code.For standalone usage, the Spring distribution provides a tiny spring-core.jar file that can be embed-ded in any kind of application. Its only third-party dependency beyond J2SE 1.3 (plus JAXP for XML parsing) is the Jakarta Commons Logging API.The bean factory is the core of Spring and the foundation for many other services that the framework offers. Nevertheless, the bean factory can easily be used stan-dalone if no other Spring services are required.Derivative：networkSpring 框架简介Spring框架：这是一个流行的开源应用框架，它可以解决很多问题。
美国电气制造商协会(NEMA)电机应用指导
© Copyright 2001 by the National Electrical Manufacturers Association. All rights including translation into other languages, reserved under the Universal Copyright Convention, the Berne Convention for the Protection of Literary and Artistic Works, and the International and Pan American Copyright Conventions.
NOTICE AND DISCLAIMER
The information in this publication was considered technically sound by the consensus of persons engaged in the development and approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every person participating in the development of this document.
NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in its standards and guideline publications. NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document. NEMA disclaims and makes no guaranty or warranty, express or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller’s products or services by virtue of this standard or guide. In publishing and making this document available, NEMA is not undertaking to render professional or other services for or on behalf of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication. NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety–related information in this document shall not be attributable to NEMA and is solely the responsibility of the certifier or maker of NTS
欧洲药典7.5版
INDEX
To aid users the index includes a reference to the supplement in which the latest version of a text can be found. For example : Amikacin sulfate...............................................7.5-4579 means the monograph Amikacin sulfate can be found on page 4579 of Supplement 7.5. Note that where no reference to a supplement is made, the text can be found in the principal volume.
English index ........................................................................ 4707
Latin index ................................................................................. 4739
EUROPEAN PHARMACOPபைடு நூலகம்EIA 7.5
Index
Numerics 1. General notices ................................................................... 7.5-4453 2.1.1. Droppers...................
大副英语面试指南
大副英语面试指南第一篇：大副英语面试指南1.Could you introduce yourself?您做一下自我介绍好吗？My name is x.x.x.I am x.x years old.I hold a xxx certificate.I have experienced of xx.Xxx.Xxx.I can use a computer system for management(maintenance).I suppose that my English is good enough for work.I am married(single).There are 3 people in my family, my daughter and my son.我的名字叫XXX。
我XX岁了。
我有XXX证书。
我经历过XX，XXX，XXXX。
我可以使用电脑做维护保养工作。
我想我的英语水平足以完成工作。
我结婚了（单身）。
我家有三口人，我女儿，儿子。
2．Where did you graduate from?您是那里毕业的？I graduated from XXX university(college, school).我毕业于某大学（某学院，某学校）3．How long have you worked on board? 您在船上做多久了？I have worked on board ten years.我在船上工作十年了。
4．Which company have you served(worked for)? 您在那个公司做过？I have served xxx.xxxx.我在某某公司做过。
5．What certificate(license)do you hold now?您现在持有什么证书？I have xxx certificate, or I hold xxx certificate, or I am the holder of xxx certificate.6．How long do you have the certificate of master ?您持有船长证书多久了？I hold the master certificate 1 years or in 2015 year。
浅谈IOC--说清楚IOC是什么
浅谈IOC--说清楚IOC是什么博文目录1.IOC的理论背景2.什么是IOC3.IOC也叫依赖注入(DI)4.IOC的优缺点5.IOC容器的技术剖析6.IOC容器的一些产品7.参考博文本文旨在用语言(非代码)说清楚IOC到底是什么，没有什么高深的技术，园中的老牛、大虾们看到这里可以绕行了，以免浪费您宝贵的时间。
IOC这个东西DebugLZQ早就想写了，但是出于对文章权威性的考虑(不能误人子弟- -!)，本文主要内容来源于最近LZ看的一些国内外的关于IOC的博文、博问，所有引用到的文章，在参考博文中均已注明。
1.IOC的理论背景我们知道在面向对象设计的软件系统中，它的底层都是由N个对象构成的，各个对象之间通过相互合作，最终实现系统地业务逻辑[1]。
图1 软件系统中耦合的对象如果我们打开机械式手表的后盖，就会看到与上面类似的情形，各个齿轮分别带动时针、分针和秒针顺时针旋转，从而在表盘上产生正确的时间。
图1中描述的就是这样的一个齿轮组，它拥有多个独立的齿轮，这些齿轮相互啮合在一起，协同工作，共同完成某项任务。
我们可以看到，在这样的齿轮组中，如果有一个齿轮出了问题，就可能会影响到整个齿轮组的正常运转。
齿轮组中齿轮之间的啮合关系,与软件系统中对象之间的耦合关系非常相似。
对象之间的耦合关系是无法避免的，也是必要的，这是协同工作的基础。
现在，伴随着工业级应用的规模越来越庞大，对象之间的依赖关系也越来越复杂，经常会出现对象之间的多重依赖性关系，因此，架构师和设计师对于系统的分析和设计，将面临更大的挑战。
对象之间耦合度过高的系统，必然会出现牵一发而动全身的情形。
图2 对象之间的依赖关系耦合关系不仅会出现在对象与对象之间，也会出现在软件系统的各模块之间，以及软件系统和硬件系统之间。
如何降低系统之间、模块之间和对象之间的耦合度，是软件工程永远追求的目标之一。
为了解决对象之间的耦合度过高的问题，软件专家Michael Mattson 1996年提出了IOC理论，用来实现对象之间的“解耦”，目前这个理论已经被成功地应用到实践当中。
C-TPAT Supply Chain Security self-assessment check list
Container Security 集装箱保安
Task # Priority Control description 控制点 Assessment result(评审结果）
1.01
high risk
Is there secure storage of containers (empty and full) to prevent theft or the introduction of unmanifested and unauthorized material? 集装箱(空柜和满柜)的存放是否安全以防失窃或未申报和未经许可的物料混入?
2.08
Low risk
2.09
high risk
Are employee and visitor identification badges controlled by management or security personnel and are the controls in place adequate? 员工和访客的识别证有否由负责人管理或保安人员控制, 并且这些控制是适当和 充分的? Are procedures for the issuance, removal, and changing of access devices (keys, key cards, etc.) documented? 是否有程序规定并记录进出门设备(如锁匙,钥匙卡等)的发放,回收和变更? Are there procedures in place to identify, challenge, and address unauthorized/unidentified persons? 是否有适当的程序识别,应对和呈报未经许可的/不明身份的来客?
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
IoC容器和Dependency Injection模式Martin Fowler编者语：最近研究IoC，在网上搜索到很多网页推荐阅读Martin Fowler的一片名叫Inversion of Control Containers and the Dependency Injection pattern的文章。
点击到该文章页面便吓了一跳：这什么文章啊，简单一个网页PageRank居然是7！要知道，国内几大门户网站也都还没有到这个值呢！也难怪，Martin Fowler被誉为软件开发教父，他的文章，肯定有N多人拜读。
细细读来，感觉大师确实很厉害，文章条理清晰，论证深入，结论明确！本想将此好文翻译推荐给广大网友，可在网上一搜，早有前人将其翻译成中文了。
这里，我将网上流传的中文版整理后，推荐给广大的编程爱好者，希望大师的精彩讲解能够让你对相关问题有一个透彻的理解。
同时，我还将其整理成了Word文档，需要的朋友点这里下载。
摘要：Java社群近来掀起了一阵轻量级容器的热潮，这些容器能够帮助开发者将来自不同项目的组件组装成为一个内聚的应用程序。
在它们的背后有着同一个模式，这个模式决定了这些容器进行组件装配的方式。
人们用一个大而化之的名字来称呼这个模式：“控制反转”（Inversion of Control，IoC）。
在本文中，我将深入探索这个模式的工作原理，给它一个更能描述其特点的名字——“依赖注入”（Dependency Injection），并将其与“服务定位器”（Service Locator）模式作一个比较。
不过，这两者之间的差异并不太重要，更重要的是：应该将组件的配置与使用分离开——两个模式的目标都是这个。
目录组件和服务 (3)一个简单的例子 (3)控制反转 (5)依赖注入的几种形式 (6)使用PicoContainer 进行构造函数注入 (6)使用Spring 进行设值方法注入 (8)接口注入 (9)使用Service Locator (10)为定位器提供分离的接口 (12)动态服务定位器 (12)用Avalon 兼顾服务定位器和依赖注入 (13)作出一个选择 (14)Service Locator vs. Dependency Injection (14)构造函数注入 vs. 设值方法注入 (15)代码配置 vs. 配置文件 (16)分离配置与使用 (17)更多的问题 (17)结论和思考 (17)致谢 (18)在企业级Java的世界里存在一个有趣的现象：有很多人投入很多精力来研究主流J2EE 技术的替代品——自然，这大多发生在open source社群。
在很大程度上，这可以看作是开发者对主流J2EE技术的笨重和复杂作出的回应，但其中的确有很多极富创意的想法，的确提供了一些可供选择的方案。
J2EE开发者常遇到的一个问题就是如何组装不同的程序元素：如果web控制器体系结构和数据库接口是由不同的团队所开发的，彼此几乎一无所知，你应该如何让它们配合工作？很多框架尝试过解决这个问题，有几个框架索性朝这个方向发展，提供了更通用的“组装各层组件”的方案。
这样的框架通常被称为“轻量级容器”，PicoContainer和Spring都在此列中。
在这些容器背后，一些有趣的设计原则发挥着作用。
这些原则已经超越了特定容器的范畴，甚至已经超越了Java平台的范畴。
在本文中，我就要初步揭示这些原则。
我使用的范例是Java代码，但正如我的大多数文章一样，这些原则也同样适用于别的OO环境，特别是.NET。
组件和服务装配程序元素，这样的话题立即将我拖进了一个棘手的术语问题：如何区分“服务”（service）和“组件”（component）？你可以毫不费力地找出关于这两个词定义的长篇大论，各种彼此矛盾的定义会让你感受到我所处的窘境。
有鉴于此，对于这两个遭到了严重滥用的词汇，我将首先说明它们在本文中的用法。
所谓“组件”是指这样一个软件单元：它将被作者无法控制的其他应用程序使用，但后者不能对组件进行修改。
也就是说，使用一个组件的应用程序不能修改组件的源代码，但可以通过作者预留的某种途径对其进行扩展，以改变组件的行为。
服务和组件有某种相似之处：它们都将被外部的应用程序使用。
在我看来，两者之间最大的差异在于：组件是在本地使用的（例如JAR文件、程序集、DLL、或者源码导入）；而服务是要通过同步或异步的远程接口来远程使用的（例如web service、消息系统、RPC，或者socket）。
在本文中，我将主要使用“服务”这个词，但文中的大多数逻辑也同样适用于本地组件。
实际上，为了方便地访问远程服务，你往往需要某种本地组件框架。
不过，“组件或者服务”这样一个词组实在太麻烦了，而且“服务”这个词当下也很流行，所以本文将用“服务”指代这两者。
一个简单的例子为了更好地说明问题，我要引入一个例子。
和我以前用的所有例子一样，这是一个超级简单的例子：它非常小，小得有点不够真实，但足以帮助你看清其中的道理，而不至于陷入真实例子的泥潭中无法自拔。
在这个例子中，我编写了一个组件，用于提供一份电影清单，清单上列出的影片都是由一位特定的导演执导的。
实现这个伟大的功能只需要一个方法：片搜寻者）对象（我们稍后会谈到这个对象）返回后者所知道的所有影片，然后遍历finder 对象返回的清单，并返回其中由特定的某个导演执导的影片。
非常简单，不过不必担心，这只是整个例子的脚手架罢了。
我们真正想要考察的是finder对象，或者说，如何将MovieLister对象与特定的finder对象连接起来。
为什么我们对这个问题特别感兴趣？因为我希望上面这个漂亮的moviesDirectedBy方法完全不依赖于影片的实际存储方式。
所以，这个方法只能引用一个finder对象，而finder对象则必须知道如何对findAll 方法作出回应。
为了帮助读者更清楚地理解，我给finder定义了一个接口：现在，两个对象之间没有什么耦合关系。
但是，当我要实际寻找影片时，就必须涉及到MovieFinder的某个具体子类。
在这里，我把涉及具体子类的代码放在MovieLister类的构造函数中。
操心具体的实现细节，只要设想这样一个实现类就可以了。
如果这个类只由我自己使用，一切都没问题。
但是，如果我的朋友叹服于这个精彩的功能，也想使用我的程序，那又会怎么样呢？如果他们也把影片清单保存在一个逗号分隔的文本文件中，并且也把这个文件命名为“ movie1.txt ”，那么一切还是没问题。
如果他们只是给这个文件改改名，我也可以从一个配置文件获得文件名，这也很容易。
但是，如果他们用完全不同的方式——例如SQL 数据库、XML 文件、web service，或者另一种格式的文本文件——来存储影片清单呢？在这种情况下，我们需要用另一个类来获取数据。
由于已经定义了MovieFinder接口，我可以不用修改moviesDirectedBy方法。
但是，我仍然需要通过某种途径获得合适的MovieFinder实现类的实例。
图1：在MovieLister 类中直接创建MovieFinder 实例时的依赖关系图1展现了这种情况下的依赖关系：MovieLister类既依赖于MovieFinder接口，也依赖于具体的实现类。
我们当然希望MovieLister类只依赖于接口，但我们要如何获得一个MovieFinder子类的实例呢？在Patterns of Enterprise Application Architecture一书中，我们把这种情况称为插件（plugin）：MovieFinder的实现类不是在编译期连入程序之中的，因为我并不知道我的朋友会使用哪个实现类。
我们希望MovieLister类能够与MovieFinder的任何实现类配合工作，并且允许在运行期插入具体的实现类，插入动作完全脱离我（原作者）的控制。
这里的问题就是：如何设计这个连接过程，使MovieLister类在不知道实现类细节的前提下与其实例协同工作。
将这个例子推而广之，在一个真实的系统中，我们可能有数十个服务和组件。
在任何时候，我们总可以对使用组件的情形加以抽象，通过接口与具体的组件交流（如果组件并没有设计一个接口，也可以通过适配器与之交流）。
但是，如果我们希望以不同的方式部署这个系统，就需要用插件机制来处理服务之间的交互过程，这样我们才可能在不同的部署方案中使用不同的实现。
所以，现在的核心问题就是：如何将这些插件组合成一个应用程序？这正是新生的轻量级容器所面临的主要问题，而它们解决这个问题的手段无一例外地是控制反转（Inversion of Control）模式。
控制反转几位轻量级容器的作者曾骄傲地对我说：这些容器非常有用，因为它们实现了控制反转。
这样的说辞让我深感迷惑：控制反转是框架所共有的特征，如果仅仅因为使用了控制反转就认为这些轻量级容器与众不同，就好象在说我的轿车是与众不同的，因为它有四个轮子。
问题的关键在于：它们反转了哪方面的控制？我第一次接触到的控制反转针对的是用户界面的主控权。
早期的用户界面是完全由应用程序来控制的，你预先设计一系列命令，例如输入姓名、输入地址等，应用程序逐条输出提示信息，并取回用户的响应。
而在图形用户界面环境下，UI框架将负责执行一个主循环，你的应用程序只需为屏幕的各个区域提供事件处理函数即可。
在这里，程序的主控权发生了反转：从应用程序移到了框架。
对于这些新生的容器，它们反转的是如何定位插件的具体实现。
在前面那个简单的例子中，MovieLister类负责定位MovieFinder的具体实现——它直接实例化后者的一个子类。
这样一来，MovieFinder也就不成其为一个插件了，因为它并不是在运行期插入应用程序中的。
而这些轻量级容器则使用了更为灵活的办法，只要插件遵循一定的规则，一个独立的组装模块就能够将插件的具体实现注射到应用程序中。
因此，我想我们需要给这个模式起一个更能说明其特点的名字——“控制反转”这个名字太泛了，常常让人有些迷惑。
与多位IoC 爱好者讨论之后，我们决定将这个模式叫做“依赖注入”（Dependency Injection）。
下面，我将开始介绍Dependency Injection模式的几种不同形式。
不过，在此之前，我要首先指出：要消除应用程序对插件实现的依赖，依赖注入并不是唯一的选择，你也可以用Service Locator模式获得同样的效果。
介绍完Dependency Injection模式之后，我也会谈到Service Locator 模式。
依赖注入的几种形式Dependency Injection 模式的基本思想是：用一个单独的对象（装配器）来获得MovieFinder的一个合适的实现，并将其实例赋给MovieLister类的一个字段。