The Application of SiNx Layers to Multicrystalline Buried Contact Silicon Solar Cells
激波_爆炸波_与物体相互作用的数值模拟_英_乐嘉陵
![激波_爆炸波_与物体相互作用的数值模拟_英_乐嘉陵](https://img.taocdn.com/s3/m/48c91524b90d6c85ec3ac6eb.png)
第13卷 第3期 1999年9月 流 体 力 学 实 验 与 测 量EXPER IM EN T S A N D M EA SU R EM EN T S IN FL U I D M ECHAN ICS Vol.13 No.3 Sep.1999收稿日期:1999-05-15基金项目:国家自然科学基金作者简介:乐嘉陵(1936-),男,浙江镇海人,中国空气动力研究与发展中心研究员,中国工程院院士.Numerical simulation of shock (blast )wave interaction with bodiesLE Jia -ling , NI Hong -li(China A er odynamics Resear ch a nd Develo pment Center ,M iany ang 621000,China )Abstract : Some typical results o f com putation o n the sho ck (blast )wav einteraction (2-D and 3-D)w ith bodies and its ex perimental validatio n in shocktube ar e sum marized,the sugg estion for improv ing the numerical m ethod(dif-ference scheme and grid systems),developing 3-D optical quantitativ e visualiza-tio n techno logy and further study ing the unsteady tur bulent flow are put for-w ar d.Key words : shock w ave ;blast w ave ;num er ical simulation激波(爆炸波)与物体相互作用的数值模拟乐嘉陵, 倪鸿礼(中国空气动力研究与发展中心,四川绵阳 621000)摘要: 给出了在二维和三维条件下激波(爆炸波)与物体相互作用的一些典型计算结果,概括总结了激波管中实验的有效性,提出了改进数值方法(包括差分格式,网格系统),发展三维光学定量可视化技术和进一步研究非定常湍流的建议。
Extreme Networks SLX 9640高性能固定路由器商品介绍说明书
![Extreme Networks SLX 9640高性能固定路由器商品介绍说明书](https://img.taocdn.com/s3/m/795dc9a0f71fb7360b4c2e3f5727a5e9856a27a1.png)
ExtremeRouting? SLX 9640
Built to Suit Your Business Needs Ext rem e Elem ent s are t he b uild ing b locks t hat allow you t o t ailor your net w ork t o your sp ecific b usiness environm ent , g oals, and ob ject ives. They enab le t he creat ion of an A ut onom ous Net w ork t hat d elivers t he p osit ive exp eriences and b usiness out com es m ost im p ort ant t o your org anizat ion.
W W W.EXTREMENETW
1
Flexib le Bo rd er Ro ut ing w it h Int ernet Scale, Ult ra-Deep Buffers,
MPLS and EVPN
The SLX 964 0 is a very p ow erful com p act d eep b uffer Int ernet b ord er rout er, p rovid ing a cost -efficient solut ion t hat is p urp ose-b uilt for t he m ost d em and ing service p rovid er and ent erp rise d at a cent ers and MA N/ WA N ap p licat ions. The rob ust syst em archit ect ure sup p ort ed by SLX-OS and a versat ile feat ure set includ ing IPv4 , IPv6, and MPLS/ VPLS w it h Carrier Et hernet 2.0 and OA M cap ab ilit ies t o p rovid e d ep loym ent flexib ilit y.
MIPI_DSI_Specification_v1b_8320061508
![MIPI_DSI_Specification_v1b_8320061508](https://img.taocdn.com/s3/m/c445fd0c02020740be1e9b70.png)
MIPI Alliance Standard for Display Serial InterfaceV1.0MIPI Board approved 5 April 2006* Caution to Implementers *This document is a MIPI Specification formally approved by the MIPI Alliance Board of Directors per the process defined in the MIPI Alliance Bylaws. However, the Display Working Group has identified certain technical issues in this approved version of the specification that are pending further review and which may require revisions of or corrections to this document in the near future. Such revisions, if any, will be handled via the formal specification revision process as defined in the Bylaws.A Release Notes document has been prepared by the Display Working Group and is available to all members. The intent of the Release Notes is to provide a list of known technical issues under further discussion with the working group. This may not be an exhaustive list; its purpose is to simply catalog known issues as of this release date. Implementers of this specification should be aware of these facts, and take them into consideration as they work with the specification.Release Notes for the Display Serial Interface Specification can be found at the following direct, permanent link:https:///members/file.asp?id=4844MIPI Alliance Standard for Display Serial InterfaceVersion 1.00a – 19 April 2006MIPI Board Approved 5-Apr-2006Further technical changes to DSI are expected as work continues in the Display Working GroupNOTICE OF DISCLAIMER12The material contained herein is not a license, either expressly or impliedly, to any IPR owned or controlled 3by any of the authors or developers of this material or MIPI. The material contained herein is provided on 4an “AS IS” basis and to the maximum extent permitted by applicable law, this material is provided AS IS 5AND WITH ALL FAULTS, and the authors and developers of this material and MIPI hereby disclaim all 6other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if7any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of8accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of 9negligence.10ALSO, THERE IS NO WARRANTY OF CONDITION OF TITLE, QUIET ENJOYMENT, QUIET11POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD 12TO THIS MATERIAL OR THE CONTENTS OF THIS DOCUMENT. IN NO EVENT WILL ANY13AUTHOR OR DEVELOPER OF THIS MATERIAL OR THE CONTENTS OF THIS DOCUMENT OR 14MIPI BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE15GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, 16CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER17CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR18ANY OTHER AGREEMENT, SPECIFICATION OR DOCUMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH1920DAMAGES.21Without limiting the generality of this Disclaimer stated above, the user of the contents of this Document is further notified that MIPI: (a) does not evaluate, test or verify the accuracy, soundness or credibility of the2223contents of this Document; (b) does not monitor or enforce compliance with the contents of this Document;24and (c) does not certify, test, or in any manner investigate products or services or any claims of compliance 25with the contents of this Document. The use or implementation of the contents of this Document may26involve or require the use of intellectual property rights ("IPR") including (but not limited to) patents,27patent applications, or copyrights owned by one or more parties, whether or not Members of MIPI. MIPI does not make any search or investigation for IPR, nor does MIPI require or request the disclosure of any2829IPR or claims of IPR as respects the contents of this Document or otherwise.30Questions pertaining to this document, or the terms or conditions of its provision, should be addressed to: 31MIPI Alliance, Inc.32c/o IEEE-ISTO33445 Hoes Lane34Piscataway, NJ 0885435Attn: Board SecretaryContents3637Version 1.00 – 13 April 2006 (i)381Overview (8)391.1Scope (8)401.2Purpose (8)412Terminology (Informational) (9)422.1Definitions (9)432.2Abbreviations (10)442.3Acronyms (10)453References (Informational) (13)463.1DBI and DBI-2 (Display Bus Interface Standards for Parallel Signaling) (13)473.2DPI and DPI-2 (Display Pixel Interface Standards for Parallel Signaling) (13)3.3DCS (Display Command Set) (14)48493.4CSI-2 (Camera Serial Interface 2) (14)503.5D-PHY (MIPI Alliance Standard for Physical Layer) (14)514DSI Introduction (15)524.1DSI Layer Definitions (16)534.2Command and Video Modes (17)4.2.1Command Mode (17)54554.2.2Video Mode Operation (17)564.2.3Virtual Channel Capability (18)5DSI Physical Layer (19)57585.1Data Flow Control (19)595.2Bidirectionality and Low Power Signaling Policy (19)605.3Command Mode Interfaces (20)615.4Video Mode Interfaces (20)625.5Bidirectional Control Mechanism (20)5.6.1Clock Requirements (21)64655.6.2Clock Power and Timing (22)666Multi-Lane Distribution and Merging (23)676.1Multi-Lane Interoperability and Lane-number Mismatch (24)686.1.1Clock Considerations with Multi-Lane (25)696.1.2Bi-directionality and Multi-Lane Capability (25)706.1.3SoT and EoT in Multi-Lane Configurations (25)717Low-Level Protocol Errors and Contention (28)727.1Low-Level Protocol Errors (28)737.1.1SoT Error (28)747.1.2SoT Sync Error (29)757.1.3EoT Sync Error (29)7.1.4Escape Mode Entry Command Error (30)76777.1.5LP Transmission Sync Error (30)787.1.6False Control Error (31)797.2Contention Detection and Recovery (31)807.2.1Contention Detection in LP Mode (32)817.2.2Contention Recovery Using Timers (32)7.3Additional Timers (34)82837.3.1Turnaround Acknowledge Timeout (TA_TO) (34)847.3.2Peripheral Reset Timeout (PR_TO) (35)7.4Acknowledge and Error Reporting Mechanism (35)85868DSI Protocol (37)878.1Multiple Packets per Transmission (37)888.2Packet Composition (37)898.3Endian Policy (38)908.4General Packet Structure (38)8.4.2Short Packet Format (40)92938.5Common Packet Elements (40)948.5.1Data Identifier Byte (40)958.5.2Error Correction Code (41)968.6Interleaved Data Streams (41)978.6.1Interleaved Data Streams and Bi-directionality (42)988.7Processor to Peripheral Direction (Processor-Sourced) Packet Data Types (42)998.8Processor-to-Peripheral Transactions – Detailed Format Description (43)1008.8.1Sync Event (H Start, H End, V Start, V End), Data Type = xx 0001 (x1h) (43)1018.8.2Color Mode On Command, Data Type = 00 0010 (02h) (44)1028.8.3Color Mode Off Command, Data Type = 01 0010 (12h) (44)1038.8.4Shutdown Peripheral Command, Data Type = 10 0010 (22h) (44)8.8.5Turn On Peripheral Command, Data Type = 11 0010 (32h) (44)1041058.8.6Generic Short WRITE Packet, 0 to 7 Parameters, Data Type = xx x011 (x3h and xBh) (44)1068.8.7Generic READ Request, 0 to 7 Parameters, Data Type = xx x100 (x4h and xCh) (44)1078.8.8DCS Commands (45)1088.8.9Set Maximum Return Packet Size, Data Type = 11 0111 (37h) (46)1098.8.10Null Packet (Long), Data Type = 00 1001 (09h) (46)8.8.11Blanking Packet (Long), Data Type = 01 1001 (19h) (46)1101118.8.12Generic Non-Image Data (Long), Data Type = 10 1001 (29h) (47)1128.8.13Packed Pixel Stream, 16-bit Format, Long packet, Data Type 00 1110 (0Eh) (47)8.8.14Packed Pixel Stream, 18-bit Format, Long packet, Data type = 01 1110 (1Eh) (48)1131148.8.15Pixel Stream, 18-bit Format in Three Bytes, Long packet, Data Type = 10 1110 (2Eh) (49)1158.8.16Packed Pixel Stream, 24-bit Format, Long packet, Data Type = 11 1110 (3Eh) (50)1168.8.17DO NOT USE and Reserved Data Types (50)1178.9Peripheral-to-Processor (Reverse Direction) LP Transmissions (51)1188.9.1Packet Structure for Peripheral-to-Processor LP Transmissions (51)1198.9.2System Requirements for ECC and Checksum and Packet Format (51)1208.9.3Appropriate Responses to Commands and ACK Requests (52)1218.9.4Format of Acknowledge with Error Report and Read Response Data Types (53)1228.9.5Error-Reporting Format (53)8.10Peripheral-to-Processor Transactions – Detailed Format Description (54)1231248.10.1Acknowledge with Error Report, Data Type 00 0010 (02h) (55)1258.10.2Generic Short Read Response with Optional ECC, Data Type 01 0xxx (10h – 17h) (55)8.10.3Generic Long Read Response with Optional ECC and Checksum, Data Type = 01 1010 126127(1Ah) 551288.10.4DCS Long Read Response with Optional ECC and Checksum, Data Type 01 1100 (1Ch)..56 1298.10.5DCS Short Read Response with Optional ECC, Data Type 10 0xxx (20h – 27h) (56)1308.10.6Multiple-packet Transmission and Error Reporting (56)1318.10.7Clearing Error Bits (56)1328.11Video Mode Interface Timing (56)1338.11.1Traffic Sequences (57)1348.11.2Non-Burst Mode with Sync Pulses (58)1358.11.3Non-Burst Mode with Sync Events (58)1368.11.4Burst Mode (59)1378.11.5Parameters (60)1388.12TE Signaling in DSI (61)1399Error-Correcting Code (ECC) and Checksum (63)1409.1Hamming Code for Packet Header Error Detection/Correction (63)1419.2Hamming-modified Code for DSI (63)9.3ECC Generation on the Transmitter and Byte-Padding (67)1421439.4Applying ECC and Byte-Padding on the Receiver (67)9.5Checksum Generation for Long Packet Payloads (68)14414510Compliance, Interoperability, and Optional Capabilities (70)14610.1Display Resolutions (70)14710.2Pixel Formats (71)14810.3Number of Lanes (71)14910.4Maximum Lane Frequency (71)15010.5Bidirectional Communication (71)15110.6ECC and Checksum Capabilities (72)15210.7Display Architecture (72)15310.8Multiple Peripheral Support (72)154Annex A (Informative) Contention Detection and Recovery Mechanisms (73)A.1PHY Detected Contention (73)155156A.1.1Protocol Response to PHY Detected Faults (73)MIPI Alliance Standard for Display Serial Interface 1571 Overview158The Display Serial Interface (DSI) specification defines protocols between a host processor and peripheral 159160devices that adhere to MIPI Alliance specifications for mobile device interfaces. The DSI specification 161builds on existing standards by adopting pixel formats and command set defined in MIPI Alliance 162standards for DBI-2 [2], DPI-2 [3], and DCS [1].1.1 Scope163Interface protocols as well as a description of signal timing relationships are within the scope of this 164165specification.166Electrical specifications and physical specifications are out of scope for this document. In addition, legacy interfaces such as DPI-2 and DBI-2 are also out of scope for this specification. Furthermore, device usage 167168of auxiliary buses such as I2C or SPI, while not precluded by this specification, are also not within its 169scope.1.2 Purpose170171The Display Serial Interface specification defines a standard high-speed serial interface between a 172peripheral, such as an active-matrix display module, and a host processor in a mobile device. By 173standardizing this interface, components may be developed that provide higher performance, lower power, 174less EMI and fewer pins than current devices, while maintaining compatibility across products from 175multiple vendors.2 Terminology (Informational)176177The MIPI Alliance has adopted Section 13.1 of the IEEE Standards Style Manual, which dictates use of the 178words “shall”, “should”, “may”, and “can” in the development of documentation, as follows:179The word shall is used to indicate mandatory requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to).180181The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is 182used only to describe unavoidable situations.183The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is 184only used in statements of fact.185The word should is used to indicate that among several possibilities one is recommended as particularly 186suitable, without mentioning or excluding others; or that a certain course of action is preferred but not 187necessarily required; or that (in the negative form) a certain course of action is deprecated but not 188prohibited (should equals is recommended that).189The word may is used to indicate a course of action permissible within the limits of the standard (may 190equals is permitted).191The word can is used for statements of possibility and capability, whether material, physical, or causal (can 192equals is able to).193All sections are normative, unless they are explicitly indicated to be informative.2.1 Definitions194195Forward Direction: The signal direction is defined relative to the direction of the high-speed serial clock. 196Transmission from the side sending the clock to the side receiving the clock is the forward direction.197Half duplex: Bidirectional data transmission over a Lane allowing both transmission and reception but 198only in one direction at a time.199HS Transmission: Sending one or more packets in the forward direction in HS Mode. A HS Transmission 200is delimited before and after packet transmission by LP-11 states.201Host Processor: Hardware and software that provides the core functionality of a mobile device.Lane: Consists of two complementary Lane Modules communicating via two-line, point-to-point Lane 202203Interconnects. A Lane is used for either Data or Clock signal transmission.204Lane Interconnect: Two-line point-to-point interconnect used for both differential high-speed signaling 205and low-power single ended signaling.206Lane Module: Module at each side of the Lane for driving and/or receiving signals on the Lane.207Link: A complete connection between two devices containing one Clock Lane and at least one Data Lane. 208LP Transmission: Sending one or more packets in either direction in LP Mode or Escape Mode. A LP 209Transmission is delimited before and after packet transmission by LP-11 states.Packet: A group of two or more bytes organized in a specified way to transfer data across the interface. All 210211packets have a minimum specified set of components. The byte is the fundamental unit of data from which 212packets are made.213Payload: Application data only – with all Link synchronization, header, ECC and checksum and other 214protocol-related information removed. This is the “core” of transmissions between host processor and 215peripheral.216PHY: The set of Lane Modules on one side of a Link.217PHY Configuration: A set of Lanes that represent a possible Link. A PHY configuration consists of a 218minimum of two Lanes: one Clock Lane and one or more Data Lanes.219Reverse Direction: Reverse direction is the opposite of the forward direction. See the description for 220Forward Direction.221Transmission: Refers to either HS or LP Transmission. See the HS Transmission and LP Transmission 222definitions for descriptions of the different transmission modes.223Virtual Channel: Multiple independent data streams for up to four peripherals are supported by this 224specification. The data stream for each peripheral is a Virtual Channel. These data streams may be 225interleaved and sent as sequential packets, with each packet dedicated to a particular peripheral or channel. 226Packet protocol includes information that directs each packet to its intended peripheral.227Word Count: Number of bytes.2.2 Abbreviations228229e.g. Forexample2.3 Acronyms230231AM Active matrix (display technology)232ProtocolAIP ApplicationIndependent233ASP Application Specific Protocol234BLLP Blanking or Low Power intervalPixel235perBPP Bits236Turn-AroundBTA Bus237InterfaceCSI CameraSerial238DBI Display Bus InterfaceDI Data239Identifier240DMA Direct Memory Access241DPI Display Pixel InterfaceDSIDisplay Serial Interface242 DT Data Type243 ECC Error-Correcting Code 244 EMI Electro Magnetic interference 245 EoTEnd of Transmission246 ESD Electrostatic Discharge 247 FpsFrames per second248 HS High Speed 249 ISTOIndustry Standards and Technology Organization250 LLP Low-Level Protocol 251 LP Low Power 252 LPI Low Power Interval 253 LPS Low Power State (state of serial data line when not transferring high-speed serial data) 254 LSBLeast Significant Bit255 Mbps Megabits per second256 MIPI Mobile Industry Processor Interface 257 MSBMost Significant Bit258 PE Packet End 259 PF Packet Footer 260 PH Packet Header 261 PHY Physical Layer 262 PI Packet Identifier 263 PPI PHY-Protocol Interface 264 PS Packet Start 265 PT Packet Type 266 PWB Printed Wired Board267 QCIFQuarter-size CIF (resolution 176x144 pixels or 144x176 pixels)268 QVGA Quarter-size Video Graphics Array (resolution 320x240 pixels or 240x320 pixels)269RAM Random Access Memory270271RGB Color presentation (Red, Green, Blue)272SLVS Scalable Low Voltage Signaling273SoT Start of Transmission274SVGA Super Video Graphics Array (resolution 800x600 pixels or 600x800 pixels) 275VGA Video Graphics Array (resolution 640x480 pixels or 480x640 pixels)VSA Vertical276ActiveSync277WVGA Wide VGA (resolution 800x480 pixels or 480x800 pixels)278CountWC Word3 References (Informational)279280[1] MIPI Alliance Standard for Display Command Set, version 1.00, April 2006281[2] MIPI Alliance Standard for Display Bus Interface, version 2.00, November 2005[3] MIPI Alliance Standard for Display Parallel Interface, version 2.00, September 2005282283[4] MIPI Alliance Standard for D-PHY, version 0.65, November 2005284Design and Analysis of Fault Tolerant Digital System by Barry W. Johnson285Error Correcting Codes: Hamming Distance by Don Johnson paper286Intel 8206 error detection and correction unit datasheet287National DP8400-2 Expandable Error Checker/Corrector datasheetMuch of DSI is based on existing MIPI Alliance standards as well as several MIPI Alliance standards in 288289simultaneous development. In the Application Layer, DSI duplicates pixel formats used in MIPI Alliance 290Standard for Display Parallel Interface [3] when it is in Video Mode operation. For display modules with a 291display controller and frame buffer, DSI shares a common command set with MIPI Alliance Standard for 292Display Bus Interface [2]. The command set is documented in MIPI Alliance Standard for Display 293Command Set [1].3.1 DBI and DBI-2 (Display Bus Interface Standards for Parallel Signaling)294295DBI and DBI-2 are MIPI Alliance specifications for parallel interfaces to display modules having display 296controllers and frame buffers. For systems based on these specifications, the host processor loads images to 297the on-panel frame buffer through the display processor. Once loaded, the display controller manages all 298display refresh functions on the display module without further intervention from the host processor. Image 299updates require the host processor to write new data into the frame buffer.300DBI and DBI-2 specify a parallel interface; that is, data is sent to the peripheral over an 8-, 9- or 16-bit-301wide parallel data bus, with additional control signals.302The DSI specification supports a Command Mode of operation. Like the parallel DBI, a DSI-compliant 303interface sends commands and parameters to the display. However, all information in DSI is first serialized 304before transmission to the display module. At the display, serial information is transformed back to parallel 305data and control signals for the on-panel display controller. Similarly, the display module can return status 306information and requested memory data to the host processor, using the same serial data path.3.2 DPI and DPI-2 (Display Pixel Interface Standards for Parallel Signaling)307DPI and DPI-2 are MIPI Alliance specifications for parallel interfaces to display modules without on-panel 308309display controller or frame buffer. These display modules rely on a steady flow of pixel data from host 310processor to the display, to maintain an image without flicker or other visual artifacts. MIPI Alliance 311specifications document several pixel formats for Active Matrix (AM) display modules.312Like DBI and DBI-2, DPI and DPI-2 are specifications for parallel interfaces. The data path may be 16-, 31318-, or 24-bits wide, depending on pixel format(s) supported by the display module. This specification 314refers to DPI mode of operation as Video Mode.Some display modules that use Video Mode in normal operation also make use of a simplified form of 315316Command Mode, when in low-power state. These display modules can shut down the streaming video 317interface and continue to refresh the screen from a small local frame buffer, at reduced resolution and pixel318depth. The local frame buffer shall be loaded, prior to interface shutdown, with image content to be319displayed when in low-power operation. These display modules can switch mode in response to power-320control commands.3.3 DCS (Display Command Set)321322DCS is a specification for the command set used by DSI and DBI-2 specifications. Commands are sent 323from the host processor to the display module. On the display module, a display controller receives andinterprets commands, then takes appropriate action. Commands fall into four broad categories: read 324325register, write register, read memory and write memory. A command may be accompanied by multiple 326parameters.3.4 CSI-2 (Camera Serial Interface 2)327CSI-2 is a MIPI Alliance standard for serial interface between a camera module and host processor. It is 328329based on the same physical layer technology and low-level protocols as DSI. Some significant differencesare:330331•CSI-2 uses unidirectional high-speed Link, whereas DSI is half-duplex bidirectional Link332•CSI-2 makes use of a secondary channel, based on I2C, for control and status functions333CSI-2 data direction is from peripheral (Camera Module) to host processor, while DSI’s primary data334direction is from host processor to peripheral (Display Module).3.5 D-PHY (MIPI Alliance Standard for Physical Layer)335MIPI Alliance Standard for D-PHY [4] provides the physical layer definition for DSI. The functionality 336337specified by the D-PHY standard covers all electrical and timing aspects, as well as low-level protocols, 338signaling, and message transmissions in various operating modes.4 DSI Introduction339340DSI specifies the interface between a host processor and a peripheral such as a display module. It builds on 341existing MIPI Alliance standards by adopting pixel formats and command set specified in DPI-2, DBI-2 342and DCS standards.343Figure 1 shows a simplified DSI interface. From a conceptual viewpoint, a DSI-compliant interface 344performs the same functions as interfaces based on DBI-2 and DPI-2 standards or similar parallel display 345interfaces. It sends pixels or commands to the peripheral, and can read back status or pixel information 346from the peripheral. The main difference is that DSI serializes all pixel data, commands, and events that, in 347traditional or legacy interfaces, are normally conveyed to and from the peripheral on a parallel data bus 348with additional control signals.349From a system or software point of view, the serialization and deserialization operations should be 350transparent. The most visible, and unavoidable, consequence of transformation to serial data and back to 351parallel is increased latency for transactions that require a response from the peripheral. For example, 352reading a pixel from the frame buffer on a display module will have a higher latency using DSI than DBI. 353Another fundamental difference is the host processor’s inability during a read transaction to throttle the 354rate, or size, of returned data.355356Figure 1 DSI Transmitter and Receiver Interface4.1 DSI Layer Definitions357Application Processor Peripheral358Figure 2 DSI Layers359360A conceptual view of DSI organizes the interface into several functional layers. A description of the layers 361follows and is also shown in Figure 2.362PHY Layer: The PHY Layer specifies transmission medium (electrical conductors), the input/output 363circuitry and the clocking mechanism that captures “ones” and “zeroes” from the serial bit stream. This part 364of the specification documents the characteristics of the transmission medium, electrical parameters for 365signaling and the timing relationship between clock and Data Lanes.366The mechanism for signaling Start of Transmission (SoT) and End of Transmission (EoT) is specified, as 367well as other “out of band” information that can be conveyed between transmitting and receiving PHYs. 368Bit-level and byte-level synchronization mechanisms are included as part of the PHY. Note that the 369electrical basis for DSI (SLVS) has two distinct modes of operation, each with its own set of electrical 370parameters.371The PHY layer is described in MIPI Alliance Standard for D-PHY [4].372Lane Management Layer: DSI is Lane-scalable for increased performance. The number of data signals 373may be 1, 2, 3, or 4 depending on the bandwidth requirements of the application. The transmitter side of the 374interface distributes the outgoing data stream to one or more Lanes (“distributor” function). On the receiving end, the interface collects bytes from the Lanes and merges them together into a recombined data 375376stream that restores the original stream sequence (“merger” function).Protocol Layer: At the lowest level, DSI protocol specifies the sequence and value of bits and bytes 377378traversing the interface. It specifies how bytes are organized into defined groups called packets. The 379protocol defines required headers for each packet, and how header information is generated and interpreted.The transmitting side of the interface appends header and error-checking information to data being 380381transmitted. On the receiving side, the header is stripped off and interpreted by corresponding logic in the 382receiver. Error-checking information may be used to test the integrity of incoming data. DSI protocol also383documents how packets may be tagged for interleaving multiple command or data streams to separate384destinations using a single DSI.385Application Layer: This layer describes higher-level encoding and interpretation of data contained in the386data stream. Depending on the display subsystem architecture, it may consist of pixels having a prescribed387format, or of commands that are interpreted by the display controller inside a display module. The DSI 388specification describes the mapping of pixel values, commands and command parameters to bytes in the389packet assembly. See MIPI Alliance Standard for Display Command Set [1].4.2 Command and Video Modes390391DSI-compliant peripherals support either of two basic modes of operation: Command Mode and Video392Mode. Which mode is used depends on the architecture and capabilities of the peripheral. The mode393definitions reflect the primary intended use of DSI for display interconnect, but are not intended to restrict 394DSI from operating in other applications.Typically, a peripheral is capable of Command Mode operation or Video Mode operation. Some Video 395396Mode displays also include a simplified form of Command Mode operation in which the display may 397refresh its screen from a reduced-size, or partial, frame buffer, and the interface (DSI) to the host processor398may be shut down to reduce power consumption.Mode3994.2.1 Command400Command Mode refers to operation in which transactions primarily take the form of sending commands401and data to a peripheral, such as a display module, that incorporates a display controller. The display 402controller may include local registers and a frame buffer. Systems using Command Mode write to, and readfrom, the registers and frame buffer memory. The host processor indirectly controls activity at the 403404peripheral by sending commands, parameters and data to the display controller. The host processor can also 405read display module status information or the contents of the frame memory. Command Mode operationrequires a bidirectional interface.406407Operation4.2.2 VideoMode408Video Mode refers to operation in which transfers from the host processor to the peripheral take the form of409a real-time pixel stream. In normal operation, the display module relies on the host processor to provide410image data at sufficient bandwidth to avoid flicker or other visible artifacts in the displayed image. Video 411information should only be transmitted using High Speed Mode.412Some Video Mode architectures may include a simple timing controller and partial frame buffer, used to413maintain a partial-screen or lower-resolution image in standby or low-power mode. This permits the 414interface to be shut down to reduce power consumption.415To reduce complexity and cost, systems that only operate in Video Mode may use a unidirectional data416path.。
3GPP TS 36.213 V9.2.0 (2010-06)
![3GPP TS 36.213 V9.2.0 (2010-06)](https://img.taocdn.com/s3/m/468e0e254b35eefdc8d3335a.png)
3GPP TS 36.213 V9.2.0 (2010-06)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA);Physical layer procedures(Release 9)The present docu ment has been developed within the 3rd Generation Partnership Project (3G PP TM ) and may be fu rther elaborated for the purposes of 3GPP.The present d ocument has not been subject to any approval process by the 3G PP Organisational Partners and shall not be implemented.This Specification is provided for fu ture development work within 3GPP only. The Organisational 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 Organisational Partners ‟ Publications Offices.KeywordsUMTS, radio, layer 13GPPPostal 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.© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, 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 i ts Members and of the 3GPP Organizational Partners GSM® and the GS M logo are registered and owned by the GSM AssociationContentsForeword (5)1Scope (6)2References (6)3Definitions, symbols, and abbreviations (7)3.1Symbols (7)3.2Abbreviations (7)4Synchronisation procedures (8)4.1Cell search (8)4.2Timing synchroni sation (8)4.2.1Radio link monitoring (8)4.2.2Inter-cell synchronisation (8)4.2.3Transmission timing adjustments (8)5Power control (9)5.1Uplink power control (9)5.1.1Physical uplink shared channel (9)5.1.1.1UE behaviour (9)5.1.1.2Power headroom (12)5.1.2Physical uplink control channel (12)5.1.2.1UE behaviour (12)5.1.3Sounding Reference Symbol (14)5.1.3.1UE behaviour (14)5.2Downlink power allocation (15)5.2.1 eNodeB Relative Narrowband TX Power restrictions (16)6Random access procedure (16)6.1Physical non-synchronized random access procedure (17)6.1.1Timing (17)6.2Random Access Response Grant (17)7 Physical downlink shared channel related procedures (19)7.1UE procedure for receiving the physical downlink shared channel (19)7.1.1 Single-antenna port scheme (22)7.1.2Transmit diversity scheme (23)7.1.3Large delay CDD scheme (23)7.1.4Closed-loop spatial multiplexing scheme (23)7.1.5Multi-user MIMO scheme (23)7.1.5A Dual layer scheme (23)7.1.6Resource allocation (23)7.1.6.1Resource allocation type 0 (23)7.1.6.2Resource allocation type 1 (24)7.1.6.3Resource allocation type 2 (25)7.1.7Modulation order and transport block size determination (26)7.1.7.1Modulation order determination (27)7.1.7.2Transport block size determination (27)7.1.7.2.1Transport blocks not mapped to two-layer spatial multiplexing (28)7.1.7.2.2Transport blocks mapped to two-layer spatial multiplexing (34)7.1.7.2.3Transport blocks mapped for DCI Format 1C (34)7.1.7.3Redundancy Version determination for Format 1C (35)7.2UE procedure for reporting channel quality indication (CQI), precoding matrix indicator (PMI) and rankindication (RI) (35)7.2.1Aperiodic CQI/PMI/RI Reporting using PUSCH (38)7.2.2Periodic CQI/PMI/RI Reporting using PUCCH (42)7.2.3Channel quality indicator (CQI) definition (48)7.2.4Precoding Matrix Indicator (PMI) definition (50)7.3UE procedure for reporting ACK/NA CK (51)8Physical uplink shared channel related procedures (54)8.1Resource Allocation for PDCCH DCI Format 0 (57)8.2UE sounding procedure (57)8.3UE A CK/NACK procedure (60)8.4UE PUSCH Hopping procedure (60)8.4.1 Type 1 PUSCH Hopping (61)8.4.2 Type 2 PUSCH Hopping (62)8.5UE Reference Symbol procedure (62)8.6Modulation order, redundancy version and transport block size determination (62)8.6.1Modulation order and redundancy version determination (62)8.6.2Transport block size determination (64)8.6.3Control information MCS offset determination (64)8.7UE Transmit Antenna Selection (66)9Physical downlink control channel procedures (66)9.1UE procedure for determining physical downlink control channel assignment (66)9.1.1 PDCCH Assignment Procedure (66)9.1.2 PHICH Assignment Procedure (67)9.2PDCCH validation for semi-persistent scheduling (68)10Physical uplink control channel procedures (70)10.1UE procedure for determining physical uplink control channel assignment (70)10.2Uplink A CK/NACK timing (75)11 Physical multicast channel related procedures (76)11.1UE procedure for receiving the physical multicast channel (76)11.2UE procedure for receiving MCCH change notification (76)Annex A (informative): Change history (77)ForewordThis Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document specifies and establishes the characteristics of the physicals layer procedures in the FDD and TDD modes of E-UTRA.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.∙References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.∙For a specific reference, subsequent revisions do not apply.∙For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.[1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”[2] 3GPP TS 36.201: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer –General Description”[3] 3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels andmodulation”[4] 3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing andchannel c oding”[5] 3GPP TS 36.214: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer –Measurements”[6] 3GPP TS 36.101: “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)radio transmission and reception”[7] 3GPP TS 36.104: “Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS)radio transmission and reception”[8] 3GPP TS36.321, “Evolved Universal Terrestrial Radio Access (E-UTRA); Medium AccessControl (MAC) protocol specification”[9] 3GPP TS36.423, “Evolved Universal Terrestrial Radio Access (E-UTRA); X2 ApplicationProtocol (X2AP)”[10] 3GPP TS36.133, “Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements forsupport of radio resource management”[11] 3GPP TS36.331, “Evolved Universal Te rrestrial Radio Access (E-UTRA); Radio ResourceControl (RRC) protocol specification”3Definitions, symbols, and abbreviations3.1SymbolsFor the purposes of the present document, the following symbols apply:f nS ystem frame number as defined in [3]s nS lot number within a radio frame as defined in [3]DLRB N Downlink bandwidth configuration, expressed in units of RBsc N as defined in [3] UL RB NUplink bandwidth configuration, expressed in units of RB sc N as defined in [3]ULsymb N Number of SC-FDMA symbols in an uplink slot as defined in [3]RBsc NResource block size in the frequency domain, expressed as a number of subcarriers as defined in [3]s TBasic time unit as defined in [3]3.2 AbbreviationsFor the purposes of the present document, the following abbreviations apply. ACK Acknowledgement BCH Broadcast ChannelCCE Control Channel Element CQI Channel Quality Indicator CRC Cyclic Redundancy Check DAI Downlink Assignment Index DCI Downlink Control Information DLDownlinkDL-SCH Downlink Shared Channel DTX Discontinuous Transmission EPRE Energy Per Resource Element MCS Modulation and Coding Scheme NACK Negative Acknowledgement PBCH Physical Broadcast ChannelPCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared ChannelPHICH Physical Hybrid ARQ Indicator Channel PMCH Physical Multicast ChannelPRA CH Physical Random Access Channel PRB Physical Resource BlockPUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QoS Quality of Service RBG Resource Block Group RE Resource Element RPF Repetition Factor RS Reference SignalSIR Signal-to-Interference RatioSINRSignal to Interference plus Noise Ratio SPS C-RNTI Semi-Persistent Scheduling C-RNTI SR Scheduling RequestSRS Sounding Reference Symbol TA Time alignmentTTI Transmission Time Interval UEUser EquipmentUL UplinkUL-SCH Uplink Shared ChannelVRB Virtual Resource Block4 Synchronisation procedures4.1 Cell searchCell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the physical layer Cell ID of that cell. E-UTRA cell search supports a scalable overall transmission bandwidth corresponding to 6 resource blocks and upwards.The following signals are transmitted in the downlink to facilitate cell search: the primary and secondary synchronization signals.4.2 Timing synchronisation4.2.1 Radio link monitoringThe downlink radio link quality of the serving cell shall be monitored by the UE for the purpose of indicating out-of-sync/in-sync status to higher layers.In non-DRX mode operation, the physical layer in the UE shall every radio frame assess the radio link quality, evaluated over the previous time period defined in [10], against thresholds (Q out and Q in) defined by relevant tests in [10].In DRX mode operation, the physical layer in the UE shall at least once every DRX period assess the radio link quality, evaluated over the previous time period defined in [10], against thresholds (Q out and Q in) defined by relevant tests in [10].The physical layer in the UE shall in radio frames where the radio link quality is assessed indicate out-of-sync to higher layers when the radio link quality is worse than the threshold Q out. When the radio link quality is better than the threshold Q in, the physical layer in the UE shall in radio frames where the radio link quality is assessed indicate in-sync to higher layers.4.2.2 Inter-cell synchronisationNo functionality is specified in this section in this release.4.2.3 Transmission timing adjustmentsUpon reception of a timing advance command, the UE shall adjust its uplink transmission timing forPUCCH/PUSCH/SRS. The timing advance command indicates the change of the uplink timing relative to the current uplink timing as multiples of 16T. The start timing of the random access preamble is specified in [3].sIn case of random access response, 11-bit timing advance command [8], T A, indicates N TA values by index values ofT A = 0, 1, 2, ..., 1282, where an amount of the time alignment is given by N TA = T A⨯16. N TA is defined in [3].In other cases, 6-bit timing advance command [8], T A, indicates adjustment of the current N TA value, N TA,old, to the new N TA value, N TA,new, by index values of T A = 0, 1, 2,..., 63, where N TA,new = N TA,old + (T A-31)⨯16. Here, adjustment of N TA value by a positive or a negative amount indicates advancing or delaying the uplink transmission timing by a given amount respectively.For a timing advance command received on subframe n, the corresponding adjustment of the timing shall apply from the beginning of subframe n+6.When the UE‟s uplink PUCCH/PUSCH/SRS transmissions in subframe n and subframe n+1 are overlapped due to the timing adjustment, the UE shall transmit complete subframe n and not transmit the overlapped part of subframe n+1.If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing adjustment without timing advance command as specified in [10], the UE changes N TA accordingly.5 Power controlDownlink power control determines the energy per resource element (EPRE). The term resource element energydenotes the energy prior to CP insertion. The term resource element energy also denotes the average energy taken over all constellation points for the modulation scheme applied. Uplink power control determines the average power over a SC-FDMA symbol in which the physical channel is transmitted.5.1 Uplink power controlUplink power control controls the transmit power of the different uplink physical channels.A cell wide overload indicator (OI) and a High Interference Indicator (HII) to control UL interference are defined in [9].5.1.1Physical uplink shared channel5.1.1.1UE behaviourThe setting of the UE Transmit power PUSCH P for the physical uplink shared channel (PUSCH) trans mission in subframe i is defined by)}()()()())((log10,min{)(TF O_PUSCH PUSCH10CMAX PUSCH i f i PL j j P i MP i P +∆+⋅++=α [dBm]where,∙ CMAX P is the configured UE transmitted power defined in [6]∙ )(PUSCH i M is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks validfor subframe i .∙)(O_PUSCH j P is a parameter composed of the sum of a cell specific nominal component )( PUSCHO_NOMINAL_j Pprovided from higher layers for j=0 and 1 and a UE specific component )(O_UE_PUSCH j P provided by higher layers for j=0 and 1. For PUSCH (re)transmissions corresponding to a semi-persistent grant then j=0 , for PUSCH (re)transmissions corresponding to a dynamic scheduled grant then j=1 and for PUSCH(re)trans missions corresponding to the random access response grant then j=2. 0)2(O_UE_PUSCH =P and 3_O_PRE PUSCHO_NOMINAL_)2(Msg PREAMBLEP P ∆+=, where the parameterPREAMBLE_INITIA L_RECEIVED_TA RGET_POW ER [8] (O_PRE P ) and 3_Msg PREAMBLE ∆ are signalledfrom higher layers. ∙For j =0 or 1, {}1,9.0,8.0,7.0,6.0,5.0,4.0,0∈α is a 3-bit cell specific parameter provided by higher layers. For j=2, .1)(=j α∙PL is the downlink pathloss estimate calculated in the UE in dB and PL = referenceSignalPower – higher layer filtered RSRP, where referenceSignalPower is provided by higher layers and RSRP is defined in [5] and the higher layer filter configuration is defined in [11]∙T F 10()10log ((21))SM PR K PUSC Hoffseti β⋅∆=-for 25.1=S K and 0 for 0=S K where S K is given by the UE specificparameter deltaMCS-Enabled provided by higher layerso/CQIRE MPR O N =for control data sent via PUSCH without UL-SCH data and1/C rRE r KN -=∑for othercases.▪where C is the number of code blocks, r K is the size for code block r , CQI O is the number of CQI bits including CRC bits and RE N is the number of resource elementsdetermined as initial-PUSCH symbN M N initialPUSCHscRE ⋅=-, where C , r K , initialPUSCH scM- andinitial-PUSCH symbN are defined in [4].oPUSCHCQIoffsetoffset ββ= for control data sent via PUSCH without UL-SCH data and 1 for other cases.∙PUSCH δ is a UE specific correction value, also referred to as a TPC command and is included in PDCCH withDCI format 0 or jointly coded with other TPC commands in PDCCH with DCI format 3/3A whose CRC parity bits are scrambled with TPC-PUSCH-RNTI. The current PUSCH power control adjustment state is given by )(i f which is defined by:o)()1()(PUSCH PUSCH K i i f i f -+-=δ if accumulation is enabled based on the UE-specific parameterAccumulation-enabled provided by higher layers or if the TPC command PUSCH δ is included in a PDCCH with DCI format 0 where the CRC is scrambled by the Temporary C-RNTI▪where )(PUSCH PUSCH K i -δwas signalled on PDCCH with DCI format 0 or 3/3A on subframe PUSCH K i -, and where )0(f is the first value after reset of accumulation. ▪The value of PUSCH K is∙ For FDD,PUSCH K = 4∙ For TDD UL/DL configurations 1-6, PU SC H K is given in Table 5.1.1.1-1∙For TDD UL/DL configuration 0o If the PUSCH transmission in subframe 2 or 7 is scheduled with a PDCCHof DCI format 0 in which the LSB of the UL index is set to 1, PUSC H K = 7 o For all other PUSCH transmissions,PU SC HK is given in Table 5.1.1.1-1.▪The UE attempts to decode a PDCCH of DCI format 0 with the UE ‟s C-RNTI or SPS C-RNTI and a PDCCH of DCI format 3/3A with this UE ‟s TPC-PUSCH-RNTI in every subframe except when in DRX▪If DCI format 0 and DCI format 3/3A are both detected in the same s ubframe, then the UE shall use the PUSCH δ provided in DCI format 0.▪ 0PUSCH =δdB for a subframe where no TPC command is decoded or where DRX occurs ori is not an uplink subframe in TDD.▪The PUSCH δ dB accumulated values signalled on PDCCH with DCI format 0 are given in Table 5.1.1.1-2. If the PDCCH with DCI format 0 is validated as a SPS activation or release PDCCH, then PUSCH δ is 0dB.▪The PUSCH δ dB accumulated values signalled on PDCCH with DCI format 3/3A are one of SET1 given in Table 5.1.1.1-2 or SET2 given in Table 5.1.1.1-3 as determined by the parameter TPC-Index provided by higher layers.▪ If UE has reached maximum power, positive TPC commands shall not be accumulated ▪ If UE has reached minimum power, negative TPC commands shall not be accumulated ▪UE shall reset accumulation∙when O_UE_PUSCHP value is changed by higher layers∙when the UE receives random access response messageo)()(PUS CH PUS CH K i i f -=δif accumulation is not enabled based on the UE-specific parameterAccumulation-enabled provided by higher layers▪where )(PUSCH PUSCH K i -δwas signalled on PDCCH with DCI format 0 on subframePUSCH K i -▪The value of PUSCH K is∙ For FDD,PUSCH K = 4∙ For TDD UL/DL configurations 1-6, PU SC H K is given in Table 5.1.1.1-1∙For TDD UL/DL configuration 0o If the PUSCH transmission in subframe 2 or 7 is scheduled with aPDCCHof DCI format 0 in which the LSB of the UL index is set to 1, PUSC H K = 7 o For all other PUSCH transmissions, PU SC H Kis given in Table 5.1.1.1-1.▪The PUSCH δ dB absolute values signalled on PDCCH with DCI format 0 are given in Table 5.1.1.1-2. If the PDCCH with DCI format 0 is validated as a SPS activation or release PDCCH, then PUSCH δ is 0dB.▪)1()(-=i f i f for a subframe where no PDCCH with DCI format 0 is decoded or whereDRX occurs or i is not an uplink subframe in TDD.o For both types of )(*f (accumulation or current absolute) the first value is set as follows:▪If O_UE_PUS C HP value is changed by higher layers, ∙()00f =▪Else∙2)0(msg rampup P f δ+∆=o where 2msg δ is the TPC command indicated in the random accessresponse, see Section 6.2, and orampup P ∆ is provided by higher layers and corresponds to the total powerramp-up from the first to the last preambleTable 5.1.1.1-1PU SC HK for TDD configuration 0-6Table 5.1.1.1-2: Mapping of TPC Command Field in DCI format 0/3 to absolute and accumulatedPUSCH δ values.Table 5.1.1.1-3: Mapping of TPC Command Field in DCI format 3A to accumulated PUSCH δ values.5.1.1.2 Power headroomThe UE power headroom PH valid for subframe i is defined by{}CM AX 10PUSCH O_PUSCH TF ()10log (())()()()()PH i P M i P j j PL i f i α=-++⋅+∆+ [dB]where, CMAX P , )(PUS C H i M , )(O_PUS C H j P , )(j α, PL, )(TF i ∆ and )(i f are defined in section 5.1.1.1. The power headroom shall be rounded to the closest value in the range [40; -23] dB with steps of 1 dB and is delivered by the physical layer to higher layers.5.1.2Physical uplink control channel5.1.2.1UE behaviourThe setting of the UE Transmit power PUCCH P for the physical uplink control channel (PUCCH) transmission in subframe i is defined by()()()(){}i g F n n h PL P P i P HARQCQI +∆+++=F_PUCCH0_PUCCH CMAX PUCCH ,,min [dBm]where∙ CMAX P is the configured UE transmitted power defined in [6]∙The parameter F_PUCCH ()F ∆ is provided by higher layers. Each F_PUCCH ()F ∆ value corresponds to a PUCCH format (F ) relative to PUCCH format 1a, where each PUCCH format (F ) is defined in Table 5.4-1 [3].∙(),CQI HARQ h n n is a PUCCH format dependent value, where CQI n corresponds to the number of informationbits for the channel quality information defined in section 5.2.3.3 in [4] and HARQ n is the number of HA RQ bits.o For PUCCH format 1,1a and 1b ()0,=HARQ CQI n n h o For PUCCH format 2, 2a, 2b and normal cyclic prefix()⎪⎩⎪⎨⎧≥⎪⎪⎭⎫ ⎝⎛=otherwise04if 4log 10,10CQI CQI HARQCQI n n n n ho For PUCCH format 2 and extended cyclic prefix()1010log if 4,40otherw iseC Q I H ARQ C Q I H ARQ C Q I H ARQn n n n h n n ⎧+⎛⎫+≥⎪ ⎪ ⎪=⎨⎝⎭⎪⎩∙O_PUCCH P is a parameter composed of the sum of a cell specific parameter PUCCHO_NOMINAL_P provided byhigher layers and a UE specific component O_UE_PUCCHP provided by higher layers.∙PUCCH δ is a UE specific correction value, also referred to as a TPC command, included in a PDCCH with DCIformat 1A/1B/1D/1/2A/2/2B or sent jointly coded with other UE specific PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC parity bits are scrambled with TPC-PUCCH-RNTI.o The UE attempts to decode a PDCCH of DCI format 3/3A with the UE ‟s TPC-PUCCH-RNTI and oneor several PDCCHs of DCI format 1A/1B/1D/1/2A/2/2B with the UE ‟s C-RNTI or SPS C-RNTI on every subframe except when in DRX. o If the UE decodes a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B and the corresponding detectedRNTI equals the C-RNTI or SPS C-RNTI of the UE, the UE shall use the PUCCH δ provided in that PDCCH.else▪if the UE decodes a PDCCH with DCI format 3/3A, the UE shall use the PUCCH δ provided in that PDCCHelse the UE shall set PUCCH δ = 0 dB.o 1()(1)()M PU C C H m m g i g i i k δ-==-+-∑where )(i g is the current PUCCH power control adjustmentstate and where ()0g is the first value after reset.▪ For FDD, 1=M and 40=k .▪ For TDD, values of M and m k are given in Table 10.1-1.▪The PUCCH δ dB values signalled on PDCCH with DCI format 1A/1B/1D/1/2A/2/2B are given in Table 5.1.2.1-1. If the PDCCH with DCI format 1/1A/2/2A/2B is validated as an SPS activation PDCCH, or the PDCCH with DCI format 1A is validated as an SPS release PDCCH, then PUCCH δ is 0dB. ▪ The PUCCH δ dB values signalled on PDCCH with DCI format 3/3A are given in Table 5.1.2.1-1 or in Table 5.1.2.1-2 as semi-statically configured by higher layers. ▪If O_UE_PUC C HP value is changed by higher layers,∙()00g =▪Else∙2(0)rampup msg g P δ=∆+o where 2msg δ is the TPC command indicated in the random accessresponse, see Section 6.2 and orampup P ∆ is the total power ramp -up from the first to the last preambleprovided by higher layers▪ If UE has reached maximum power, positive TPC commands shall not be accumulated ▪ If UE has reached minimum power, negative TPC commands shall not be accumulated ▪UE shall reset accumulation∙ when O_UE_PUCCHP value is changed by higher layers∙when the UE receives a random access response message▪()(1)g i g i =- if i is not an uplink subframe in TDD.Table 5.1.2.1-1: Mapping of TPC Command Field in DCI format 1A/1B/1D/1/2A/2B/2/3 to PUCCH δvalues.Table 5.1.2.1-2: Mapping of TPC Command Field in DCI format 3A to PUCCH δ values.5.1.3Sounding Reference Symbol5.1.3.1UE behaviourThe setting of the UE Transmit power SRS P for the Sounding Reference Symbol transmitted on subframe i is defined bySRS CM AX SRS_OFFSET 10SRS O_PUSCH ()min{,10log ()()()()}P i P P M P j j PL f i α=+++⋅+ [dBm]where∙ CMAX P is the configured UE transmitted power defined in [6]∙For 1.25S K =,SRS_OFFSET P is a 4-bit UE specific parameter semi-statically configured by higher layers with1dB step size in the range [-3, 12] dB. ∙For 0=S K ,SRS_OFFSETP is a 4-bit UE specific parameter semi-statically configured by higher layers with 1.5dB step size in the range [-10.5,12] dB ∙SRS M is the bandwidth of the SRS transmission in subframe i expressed in number of resource blocks.∙ )(i f is the current power control adjustment state for the PUSCH, see Section 5.1.1.1.∙ )(O_PUSCH j P and )(j α are parameters as defined in Section 5.1.1.1, where 1=j .5.2 Downlink power allocationThe eNodeB determines the downlink trans mit energy per resource element.A UE may assume downlink cell-specific RS EPRE is constant across the downlink system bandwidth and constant across all subframes until different cell-specific RS power information is received. The downlink reference-signal EPRE can be derived from the downlink reference-signal transmit power given by the parameter Reference-signal-power provided by higher layers. The downlink reference-signal transmit power is defined as the linear average over the power contributions (in [W]) of all resource elements that carry cell-specific reference signals within the operating system bandwidth.The ratio of PDSCH EPRE to cell-specific RS EPRE among PDSCH REs (not applicable to PDSCH REs with zero EPRE) for each OFDM symbol is denoted by either A ρ or B ρaccording to the OFDM symbol index as given by Table 5.2-2. In addition,A ρ and B ρare UE-specific.For a UE in transmission mode 8 when UE-specific RSs are not present in the PRBs upon which the correspondingPDSCH is mapped or in trans mission modes 1 – 7, the UE may assume that for 16 QAM, 64 QAM, spatial multiplexing with more than one layer or for PDSCH transmissions associated with the multi-user MIMO transmission scheme,▪A ρ is equal to )2(log1010offset-power++A P δ [dB] when the UE receives a PDSCH data transmission usingprecoding for transmit diversity with 4 cell-specific antenna ports according to Section 6.3.4.3 of [3]; ▪A ρ is equal to A P +offset-powerδ [dB] otherwisewhere offset-power δis 0 dB for all PDSCH transmission schemes except multi-user MIMO and where A P is a UE specificparameter provided by higher layers.For transmission mode 7, if UE-specific RSs are present in the PRBs upon which the corresponding PDSCH is mapped, the ratio of PDSCH EPRE to UE-specific RS EPRE within each OFDM symbol containing UE-specific RSs shall be a constant, and that constant shall be maintained over all the OFDM symbols containing the UE-specific RSs in the corresponding PRBs. In addition, the UE may assume that for 16QAM or 64QAM, this ratio is 0 dB.For transmission mode 8, if UE-specific RSs are present in the PRBs upon which the corresponding PDSCH is mapped, the UE may assume the ratio of PDSCH EPRE to UE-specific RS EPRE within each OFDM symbol containing UE-specific RSs is 0 dB.A UE may assume that downlink positioning reference signal EPRE is constant across the positioning reference signal bandwidth and across all OFDM symbols that contain positioning reference signals in a given positioning reference signal occasion [10].The cell-specific ratio A B ρρ/ is given by Table 5.2-1 according to cell-specific parameter B P signalled by higher layers and the number of configured eNodeB cell specific antenna ports.Table 5.2-1: The cell-specific ratio A B ρρ/ for 1, 2, or 4 cell specific antenna ports。
VR中英文对照
![VR中英文对照](https://img.taocdn.com/s3/m/0c41fa6e58fafab069dc025a.png)
Global Switches(全局光照开关设置)Materials(材质)Reflection/Refraction(反射/折射)Max Depth(最大深度)2 Max Transp.Level(最大透明级别)50Transp. Cutoff(透明终止值)0.001 Maps(帖图)Filter Maps(过滤贴图)Glossy Effects(光滑效果)Override materials(覆盖材质)Indirect Illumination(间接照明)Don't render final image(不渲染最终的图象)Raytracing(光线跟踪)Secondary ray bias(二级光线偏移)0Render(渲染)Batch render(批量渲染)Low thread priority(低线程优先权)Show progress window(显示步进窗口)Lighting(照明)Lights(灯光)Hidden Lights(隐蔽灯光)Default Lights(缺省灯光)Shadows(阴影)Show GI Only(只显示全局光照)Gamma Correction(伽玛值修正)Output(导出)2.2 Input(导入)2.2 LCorrect RGB(修正三原色)Correct LDR Textures(修正LDR材质)System(系统设置)Raycaster Params(光线追踪参数)Max Depth(最大深度)60 Min Leaf(最小树叶)0Face/Level(面/级)2 Mem Limit(限制)400Distributed Rendering(分布式渲染设置)Distributed Rendering(分布式渲染)Settings(设置)Region Division(区域分割)Width(宽)48 Height(高)48Means(方法):Region W/H(区域宽/高)▲Sequence(排序):Triangulation(三角剖分)▲Reverse Sequence(区域排序)Camera(照相机设置)Default Camera(缺省照相机)Type(类型):Standard(标准)▲Height(高度)400 Delta(深度)2Override FOV(视野)45 Auto Fit Curve(自动适合曲线)1Physical Camera(物理照相机)On(开)Type(类型):Still camera(静止照相机)▲Override Focal Length(焦距)40Shutter speed(快门速度)125 Film Width(宽)36 Distortion(矢真)0Shutter angle(快门角度)180 Zoom(焦距缩放)1 Lens shift(焦距移动)0Shutter offset(快门位移)0 F-number(焦距比数)11 White balance(白平衡)Latency(潜伏)0 Film speed (ISO)(感光度)125Exposure(曝光)V ignetting(渐晕)Depth of Field(景深)On(开)Aperture(光圈)0.1 Sides(段数)5 Rotation(旋转)0 Center Bias(中心偏移)0 Anisotropy(各向异性)0 Subdivs(细分)6 Override Focal Dist.(焦距)200Motion Blur(运动模糊)On(开)Duration(持续时间)1 Interval Center(间隔中心)0.5 Subdivs(细分)6Bias(偏移)0 Geometry samples(几何结构采样)2Output(导出设置)Output Size(导出大小)Override Viewport(替代视窗)Width(宽)320 640x480 / 1024x768 / 1600x1200Height(高)240 800x600 / 1280x960 / 2048x1536Image Aspect(图像比率)1.3333 L Pixel Aspect(像素)1 LRender Output(渲染导出)Save file(保存文件)V-Ray Raw Image File(VRay专用RA W格式图像文件)Render to VRImage(渲染到VRay图像)Animation(动画)On(开)Frame Rate(框架率)NTSC / PAL / Film(电影)/ Custom(自定义)FPS(帧)30Environment(环境设置)GI (Skylight)(全局光照(天空光))1 M Reflection(反射)1 mBackground(背景)1 M Refraction(折射)1 mImage Sampler(图像采样设置)Image Sampler(图像采样)Fixed Rate(固定细分)■Subdivs(细分)1Adaptive QMC(自适应准蒙特卡罗)■Min Subdivs(最小细分)1 Max Subdivs(最大细分)16Adaptive Subdivision(自适应细分)■Min Rate(最小比率)-1 Max Rate(最大比率)2 Threshold(极限值)0.1 Normaks (法线)0.1Antialiasing filter(边缘抗齿锯过滤)On(开)Area(面积):Size(大小)1.5▲QMC Sampler(准蒙特卡罗采样设置)QMC Sampler(准蒙特卡罗采样)Adaptive Amount(自适应数量)1 Min Samples(最小采样值)8Noise Threshold(噪波极限值)0.01 Subdiv Mult(细分倍增)1Path Sampler(路径采样器):Randomized Halton(使随机化)▲Color Mapping(颜色映射设置)Color Mapping(颜色映射)Type(类型):Reinhard()▲Multiplier(倍增)1 Burn V alue(曝光值)0.8 Affect Background(影响背景)Clamp Output(加强输出)Sub-pixel(子像素贴图)VFB Channels(VFB通道设置)VFB Channels(VFB通道):Atmosphere(空气)▲Diffuse(漫反射)Shadow(阴影)Lighting(照明)GI(全局光照)Caustics(散焦)Raw GI(RA W全局光照)Raw Shadow(RA W阴影)Z-Depth(Z轴深度)Normals(法向)Background (背景)Displacement(置换设置)Displacement(置换)Edge Length(pix)(边界长度)4 Max Subdivs(最大细分)256 Amount(数量)1 Relative to bbox(相对边界盒)V iew-Dependent(依靠视图)Tight Bounds(紧密跳跃`)Indirect Illumination(间接照明设置)GI(全局光照)On(开)Reflect Caustics(反射)Refract Caustics(折射)Post-Processing(布置数据处理)Saturation(饱和度)1 Contrast Base(基本对比度)0.5Contrast(对比度)1 Save maps per frame(保存每帖贴图)Primary Engine(首次反弹)Multiplier(倍增)1 Quasi Monte-Carlo(准蒙特卡罗算法)■▲Secondary Engine(二次反弹)Multiplier(倍增)1 Light Cache(灯光缓冲)■▲Quasi-Monte Carlo GI(准蒙特卡罗全局光照设置)■QMC GI(准蒙特卡罗全局光照)Subdivs(细分)8 Secondary Bounces(二次反弹)3Light Cache(灯光缓冲设置)■Calculation Parameters(计算参数)Subdivs(细分)1000 Scale(比例):Screen(屏幕)▲Sample Size(采样大小)0.02 Num.Phases(进程数量)4Store Direct Light(存储直接灯光)Show Calc.Phase(显示计算相位)Adaptive(自适应)Reconstruction Parameters(重建参数)Pre-filter(预滤器)10 Use For Glossy Rays(使用灯光缓冲光滑光线)Filter(过滤):Nearest(接近)▲Interp.Samples(插补采样)5Mode(方式)Single Frame(单帧)Fly Through(通过)Path Tracing(路径跟踪)From File(来自文件)Current Map(当前贴图)Save(保存)Reset(清除)Post Render(渲染后)Don't Delete(不删除)Auto Save(自动保存)Irradiance Map(发光贴图)■Basic Parameters(基本参数)Min Rate(最小比率)-3 Max Rate(最大比率)0 Color Threshold(色彩极限值)0.3 HSph.Subdivs(半球细分)50 Samples(采样)20 Normal Threshold(法线极限值)0.1Distance Threshold(距离极限值)0.1Basic Options(基本选项)Show Calculation Phase(显示计算相位)Show Samples(显示采样点)Show Direct Light(存储直接灯光)Detail enhancement(细节增强)On(开)Scale(比例):Screen(屏幕)▲Radius(半径)60 Subdiv mult(细分倍增)0.3 Advanced Options(高级选项)Interpolation Type(插值类型):Least Squares Fit(最小平方适应)▲Sample Lookup Type(采样查找类型):Density Based(基于密度)▲Calc Samples(计算采样)15 Multipass(多重预计算)Randomize Samples(随机采样)Check Sample Visibility(检查样本可见性)Mode(方式)Single Frame(单帧)Incremental add to current map(添加方式增加到当前贴图)Bucket Mode(块模式)From File(来自文件)Current Map(当前贴图)Save(保存)Reset(清除)Post Render(渲染后)Don't Delete(不删除)Auto Save(自动保存)Photon Map(光子贴图)■Basic Parameters(基本参数)Bounces(反弹)10 Max Photons(最大光子)30Search Distance(搜寻距离)20 Multiplier(倍增)1Retrace Threshold(反射极限值)0 Max Density(最大密度)0Retrace Bounces(反射反弹数)10 Interp. Samples(插值采样)10Convex Hull Estimate(凸起表面区域评估)Store Direct Light(存储直接灯光)Mode(方式)New Map(新贴图)From File(来自文件)Current Map(当前贴图)Save(保存)Reset(清除)0 samples(采样)Post Render(渲染后)Don't Delete(不删除)Auto Save(自动保存)Caustics(散焦设置)Caustics(散焦)On(开)Max Photons(最大光子)50 Multiplier(倍增)1Max Density(最大密度)0 Search Distance(搜索距离)20Mode(方式)New Map(新贴图)From File(来自文件)Current Map(当前贴图)Save(保存)Reset(清除)0 samples(采样)Post Render(渲染后)Don't Delete(不删除)Auto Save(自动保存)Material Editor(材质编辑)Material Preview(材质预览)Update Preview(更新查阅)Material Workspace(材质预览)Scene Materials(场材质)Default_VRay_Material(默认材质)Add material(增加材质)*Add V rayMld(增加VRay专用材质)*Add VRay2SidedMld(增加VRat双面材质)[ Front(正面)Back(背面)Color(颜色)] *Add VRaySKp2SidedMld(增加VRaySKp双面材质)[ Front(正面)Back(背面)] Import new material(导入新材质)Purge unused materials(清除不用的材质)Rename(改名)Remove(移除)Duplicate(副本复制)Import(导入)Export(导出)Select objects by material(选择对象到材质)Apply material to object(s)(应用到物体)Apply material to layer(s)(应用到层)Add new layer(增加新的层)Emissive(发光)Color(颜色)Intensity(强度)1 Transparency(透明度)Reflection(反射)Reflection(反射)Filter(过滤)Highlight Glossiness(高光光泽)1 Reflection Glossiness(反射光泽)1Subdivs(细分)8 Anisotropy(各向异性)0Shader Type(阴影类型):Blinn(材质)▲Rotation(旋转)0Diffuse(漫反射)Color(颜色)Transparency(透明度)Refraction(折射)Refraction(折射)Transparency(透明度)Glossiness(光泽度)1 IOR(折射率)1.55 Subdivs(细分)8Translucency(透明)Translucent(半透明)Fog Color(雾色)Thickness(厚度)1000 Fog Multiplier(雾强度)1Scatter coeff(扩散系数)0 Affect Shadows(影响阴影)Fwd/bck coeff(前向/后向系数)1 Affect Alpha(影响通道)Options(选项)Trace Reflections(追踪反射)Double-Sided(双面)Trace Refractions(追踪折射)Reflect on Backside(内表面反射)Cutoff(终止)0.001 Disable V olume Fog(禁止体积雾)Maps(贴图)Bump(凹凸)Background(背景)Reflection(反射)Displacement(置换)GI(全局光照明)Refraction(折射)Keep continuity(保持连续性)Spotlight(聚光灯)Intensity(强度)On(开)Color(颜色)Multiplier(倍增)1Options(选项)Decay(衰退):Linear(线状的)▲Hardness(坚硬)0.5Sampling(采样)Photon Subdivs(光子细分)500 Caustic Subdivs(腐蚀细分)1000 Shadows(阴影)Enabled(开启)Bias(偏移)0 Radius(半径)0 Subdivs(细分)8Point light(点光源)Intensity(强度)On(开)Color(颜色)Multiplier(倍增)1Options(选项)Decay(衰退):Linear(线状的)▲Sampling(采样)Photon Subdivs(光子细分)500 Caustic Subdivs(腐蚀细分)1000 Shadows(阴影)Enabled(开启)Bias(偏移)0 Radius(半径)0 Subdivs(细分)8Directional light(平行光)Intensity(强度)On(开)Color(颜色)Multiplier(倍增)1Sampling(采样)Photon Subdivs(光子细分)500 Caustic Subdivs(腐蚀细分)1000 Shadows(阴影)Enabled(开启)Bias(偏移)0 Radius(半径)0 Subdivs(细分)8Rectangular light(区域光)Intensity(强度)On(开)Color(颜色)Multiplier(倍增)1Options(选项)Light Portal(光线入口)Invisible(不可见)Double Sided(双面)No Decay(不衰减)Store with Irradiance Map(存储发光贴图)Ignore Light Normals(忽略灯光法向)Sampling(采样)Subdivs(细分)8 Photon Subdivs(光子细分)500 Caustic Subdivs (腐蚀细分)1000Shadows(阴影)Enabled(开启)Bias(偏移)0Linear light(管状光)Color(颜色)On(开)Shadows intensity(阴影厚度)100 Spotlight hardness(聚光灯锐利度)100Displacement(置换)On(开)Advanced controls(高级控制器)Texture(材质)Mapping channel(映射通道)1Displacement(置换)Black point(黑点)0.00 White point(白点)1.00 Ignore creases (忽略皱痕)Subdivision(细分)Subdivide(细分)Contrast(对比度)20% Max steps(最大步幅)4。
MIPS芯片架构说明
![MIPS芯片架构说明](https://img.taocdn.com/s3/m/58799d11f18583d04964594b.png)
MIPS32™ Architecture For Programmers Volume I: Introduction to the MIPS32™ArchitectureDocument Number: MD00082Revision 2.00June 8, 2003MIPS Technologies, Inc.1225 Charleston RoadMountain View, CA 94043-1353Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Copyright ©2001-2003 MIPS Technologies, Inc. All rights reserved.Unpublished rights (if any) reserved under the copyright laws of the United States of America and other countries.This document contains information that is proprietary to MIPS Technologies, Inc. ("MIPS Technologies"). Any copying,reproducing,modifying or use of this information(in whole or in part)that is not expressly permitted in writing by MIPS Technologies or an authorized third party is strictly prohibited. At a minimum, this information is protected under unfair competition and copyright laws. Violations thereof may result in criminal penalties and fines.Any document provided in source format(i.e.,in a modifiable form such as in FrameMaker or Microsoft Word format) is subject to use and distribution restrictions that are independent of and supplemental to any and all confidentiality restrictions. UNDER NO CIRCUMSTANCES MAY A DOCUMENT PROVIDED IN SOURCE FORMAT BE DISTRIBUTED TO A THIRD PARTY IN SOURCE FORMAT WITHOUT THE EXPRESS WRITTEN PERMISSION OF MIPS TECHNOLOGIES, INC.MIPS Technologies reserves the right to change the information contained in this document to improve function,design or otherwise.MIPS Technologies does not assume any liability arising out of the application or use of this information, or of any error or omission in such information. Any warranties, whether express, statutory, implied or otherwise, including but not limited to the implied warranties of merchantability orfitness for a particular purpose,are excluded. Except as expressly provided in any written license agreement from MIPS Technologies or an authorized third party,the furnishing of this document does not give recipient any license to any intellectual property rights,including any patent rights, that cover the information in this document.The information contained in this document shall not be exported or transferred for the purpose of reexporting in violation of any U.S. or non-U.S. regulation, treaty, Executive Order, law, statute, amendment or supplement thereto. The information contained in this document constitutes one or more of the following: commercial computer software, commercial computer software documentation or other commercial items.If the user of this information,or any related documentation of any kind,including related technical data or manuals,is an agency,department,or other entity of the United States government ("Government"), the use, duplication, reproduction, release, modification, disclosure, or transfer of this information, or any related documentation of any kind, is restricted in accordance with Federal Acquisition Regulation12.212for civilian agencies and Defense Federal Acquisition Regulation Supplement227.7202 for military agencies.The use of this information by the Government is further restricted in accordance with the terms of the license agreement(s) and/or applicable contract terms and conditions covering this information from MIPS Technologies or an authorized third party.MIPS,R3000,R4000,R5000and R10000are among the registered trademarks of MIPS Technologies,Inc.in the United States and other countries,and MIPS16,MIPS16e,MIPS32,MIPS64,MIPS-3D,MIPS-based,MIPS I,MIPS II,MIPS III,MIPS IV,MIPS V,MIPSsim,SmartMIPS,MIPS Technologies logo,4K,4Kc,4Km,4Kp,4KE,4KEc,4KEm,4KEp, 4KS, 4KSc, 4KSd, M4K, 5K, 5Kc, 5Kf, 20Kc, 25Kf, ASMACRO, ATLAS, At the Core of the User Experience., BusBridge, CoreFPGA, CoreLV, EC, JALGO, MALTA, MDMX, MGB, PDtrace, Pipeline, Pro, Pro Series, SEAD, SEAD-2, SOC-it and YAMON are among the trademarks of MIPS Technologies, Inc.All other trademarks referred to herein are the property of their respective owners.Template: B1.08, Built with tags: 2B ARCH MIPS32MIPS32™ Architecture For Programmers Volume I, Revision 2.00 Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Table of ContentsChapter 1 About This Book (1)1.1 Typographical Conventions (1)1.1.1 Italic Text (1)1.1.2 Bold Text (1)1.1.3 Courier Text (1)1.2 UNPREDICTABLE and UNDEFINED (2)1.2.1 UNPREDICTABLE (2)1.2.2 UNDEFINED (2)1.3 Special Symbols in Pseudocode Notation (2)1.4 For More Information (4)Chapter 2 The MIPS Architecture: An Introduction (7)2.1 MIPS32 and MIPS64 Overview (7)2.1.1 Historical Perspective (7)2.1.2 Architectural Evolution (7)2.1.3 Architectural Changes Relative to the MIPS I through MIPS V Architectures (9)2.2 Compliance and Subsetting (9)2.3 Components of the MIPS Architecture (10)2.3.1 MIPS Instruction Set Architecture (ISA) (10)2.3.2 MIPS Privileged Resource Architecture (PRA) (10)2.3.3 MIPS Application Specific Extensions (ASEs) (10)2.3.4 MIPS User Defined Instructions (UDIs) (11)2.4 Architecture Versus Implementation (11)2.5 Relationship between the MIPS32 and MIPS64 Architectures (11)2.6 Instructions, Sorted by ISA (12)2.6.1 List of MIPS32 Instructions (12)2.6.2 List of MIPS64 Instructions (13)2.7 Pipeline Architecture (13)2.7.1 Pipeline Stages and Execution Rates (13)2.7.2 Parallel Pipeline (14)2.7.3 Superpipeline (14)2.7.4 Superscalar Pipeline (14)2.8 Load/Store Architecture (15)2.9 Programming Model (15)2.9.1 CPU Data Formats (16)2.9.2 FPU Data Formats (16)2.9.3 Coprocessors (CP0-CP3) (16)2.9.4 CPU Registers (16)2.9.5 FPU Registers (18)2.9.6 Byte Ordering and Endianness (21)2.9.7 Memory Access Types (25)2.9.8 Implementation-Specific Access Types (26)2.9.9 Cache Coherence Algorithms and Access Types (26)2.9.10 Mixing Access Types (26)Chapter 3 Application Specific Extensions (27)3.1 Description of ASEs (27)3.2 List of Application Specific Instructions (28)3.2.1 The MIPS16e Application Specific Extension to the MIPS32Architecture (28)3.2.2 The MDMX Application Specific Extension to the MIPS64 Architecture (28)3.2.3 The MIPS-3D Application Specific Extension to the MIPS64 Architecture (28)MIPS32™ Architecture For Programmers Volume I, Revision 2.00i Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.3.2.4 The SmartMIPS Application Specific Extension to the MIPS32 Architecture (28)Chapter 4 Overview of the CPU Instruction Set (29)4.1 CPU Instructions, Grouped By Function (29)4.1.1 CPU Load and Store Instructions (29)4.1.2 Computational Instructions (32)4.1.3 Jump and Branch Instructions (35)4.1.4 Miscellaneous Instructions (37)4.1.5 Coprocessor Instructions (40)4.2 CPU Instruction Formats (41)Chapter 5 Overview of the FPU Instruction Set (43)5.1 Binary Compatibility (43)5.2 Enabling the Floating Point Coprocessor (44)5.3 IEEE Standard 754 (44)5.4 FPU Data Types (44)5.4.1 Floating Point Formats (44)5.4.2 Fixed Point Formats (48)5.5 Floating Point Register Types (48)5.5.1 FPU Register Models (49)5.5.2 Binary Data Transfers (32-Bit and 64-Bit) (49)5.5.3 FPRs and Formatted Operand Layout (50)5.6 Floating Point Control Registers (FCRs) (50)5.6.1 Floating Point Implementation Register (FIR, CP1 Control Register 0) (51)5.6.2 Floating Point Control and Status Register (FCSR, CP1 Control Register 31) (53)5.6.3 Floating Point Condition Codes Register (FCCR, CP1 Control Register 25) (55)5.6.4 Floating Point Exceptions Register (FEXR, CP1 Control Register 26) (56)5.6.5 Floating Point Enables Register (FENR, CP1 Control Register 28) (56)5.7 Formats of Values Used in FP Registers (57)5.8 FPU Exceptions (58)5.8.1 Exception Conditions (59)5.9 FPU Instructions (62)5.9.1 Data Transfer Instructions (62)5.9.2 Arithmetic Instructions (63)5.9.3 Conversion Instructions (65)5.9.4 Formatted Operand-Value Move Instructions (66)5.9.5 Conditional Branch Instructions (67)5.9.6 Miscellaneous Instructions (68)5.10 Valid Operands for FPU Instructions (68)5.11 FPU Instruction Formats (70)5.11.1 Implementation Note (71)Appendix A Instruction Bit Encodings (75)A.1 Instruction Encodings and Instruction Classes (75)A.2 Instruction Bit Encoding Tables (75)A.3 Floating Point Unit Instruction Format Encodings (82)Appendix B Revision History (85)ii MIPS32™ Architecture For Programmers Volume I, Revision 2.00 Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Figure 2-1: Relationship between the MIPS32 and MIPS64 Architectures (11)Figure 2-2: One-Deep Single-Completion Instruction Pipeline (13)Figure 2-3: Four-Deep Single-Completion Pipeline (14)Figure 2-4: Four-Deep Superpipeline (14)Figure 2-5: Four-Way Superscalar Pipeline (15)Figure 2-6: CPU Registers (18)Figure 2-7: FPU Registers for a 32-bit FPU (20)Figure 2-8: FPU Registers for a 64-bit FPU if Status FR is 1 (21)Figure 2-9: FPU Registers for a 64-bit FPU if Status FR is 0 (22)Figure 2-10: Big-Endian Byte Ordering (23)Figure 2-11: Little-Endian Byte Ordering (23)Figure 2-12: Big-Endian Data in Doubleword Format (24)Figure 2-13: Little-Endian Data in Doubleword Format (24)Figure 2-14: Big-Endian Misaligned Word Addressing (25)Figure 2-15: Little-Endian Misaligned Word Addressing (25)Figure 3-1: MIPS ISAs and ASEs (27)Figure 3-2: User-Mode MIPS ISAs and Optional ASEs (27)Figure 4-1: Immediate (I-Type) CPU Instruction Format (42)Figure 4-2: Jump (J-Type) CPU Instruction Format (42)Figure 4-3: Register (R-Type) CPU Instruction Format (42)Figure 5-1: Single-Precisions Floating Point Format (S) (45)Figure 5-2: Double-Precisions Floating Point Format (D) (45)Figure 5-3: Paired Single Floating Point Format (PS) (46)Figure 5-4: Word Fixed Point Format (W) (48)Figure 5-5: Longword Fixed Point Format (L) (48)Figure 5-6: FPU Word Load and Move-to Operations (49)Figure 5-7: FPU Doubleword Load and Move-to Operations (50)Figure 5-8: Single Floating Point or Word Fixed Point Operand in an FPR (50)Figure 5-9: Double Floating Point or Longword Fixed Point Operand in an FPR (50)Figure 5-10: Paired-Single Floating Point Operand in an FPR (50)Figure 5-11: FIR Register Format (51)Figure 5-12: FCSR Register Format (53)Figure 5-13: FCCR Register Format (55)Figure 5-14: FEXR Register Format (56)Figure 5-15: FENR Register Format (56)Figure 5-16: Effect of FPU Operations on the Format of Values Held in FPRs (58)Figure 5-17: I-Type (Immediate) FPU Instruction Format (71)Figure 5-18: R-Type (Register) FPU Instruction Format (71)Figure 5-19: Register-Immediate FPU Instruction Format (71)Figure 5-20: Condition Code, Immediate FPU Instruction Format (71)Figure 5-21: Formatted FPU Compare Instruction Format (71)Figure 5-22: FP RegisterMove, Conditional Instruction Format (71)Figure 5-23: Four-Register Formatted Arithmetic FPU Instruction Format (72)Figure 5-24: Register Index FPU Instruction Format (72)Figure 5-25: Register Index Hint FPU Instruction Format (72)Figure 5-26: Condition Code, Register Integer FPU Instruction Format (72)Figure A-1: Sample Bit Encoding Table (76)MIPS32™ Architecture For Programmers Volume I, Revision 2.00iii Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Table 1-1: Symbols Used in Instruction Operation Statements (2)Table 2-1: MIPS32 Instructions (12)Table 2-2: MIPS64 Instructions (13)Table 2-3: Unaligned Load and Store Instructions (24)Table 4-1: Load and Store Operations Using Register + Offset Addressing Mode (30)Table 4-2: Aligned CPU Load/Store Instructions (30)Table 4-3: Unaligned CPU Load and Store Instructions (31)Table 4-4: Atomic Update CPU Load and Store Instructions (31)Table 4-5: Coprocessor Load and Store Instructions (31)Table 4-6: FPU Load and Store Instructions Using Register+Register Addressing (32)Table 4-7: ALU Instructions With an Immediate Operand (33)Table 4-8: Three-Operand ALU Instructions (33)Table 4-9: Two-Operand ALU Instructions (34)Table 4-10: Shift Instructions (34)Table 4-11: Multiply/Divide Instructions (35)Table 4-12: Unconditional Jump Within a 256 Megabyte Region (36)Table 4-13: PC-Relative Conditional Branch Instructions Comparing Two Registers (36)Table 4-14: PC-Relative Conditional Branch Instructions Comparing With Zero (37)Table 4-15: Deprecated Branch Likely Instructions (37)Table 4-16: Serialization Instruction (38)Table 4-17: System Call and Breakpoint Instructions (38)Table 4-18: Trap-on-Condition Instructions Comparing Two Registers (38)Table 4-19: Trap-on-Condition Instructions Comparing an Immediate Value (38)Table 4-20: CPU Conditional Move Instructions (39)Table 4-21: Prefetch Instructions (39)Table 4-22: NOP Instructions (40)Table 4-23: Coprocessor Definition and Use in the MIPS Architecture (40)Table 4-24: CPU Instruction Format Fields (42)Table 5-1: Parameters of Floating Point Data Types (45)Table 5-2: Value of Single or Double Floating Point DataType Encoding (46)Table 5-3: Value Supplied When a New Quiet NaN Is Created (47)Table 5-4: FIR Register Field Descriptions (51)Table 5-5: FCSR Register Field Descriptions (53)Table 5-6: Cause, Enable, and Flag Bit Definitions (55)Table 5-7: Rounding Mode Definitions (55)Table 5-8: FCCR Register Field Descriptions (56)Table 5-9: FEXR Register Field Descriptions (56)Table 5-10: FENR Register Field Descriptions (57)Table 5-11: Default Result for IEEE Exceptions Not Trapped Precisely (60)Table 5-12: FPU Data Transfer Instructions (62)Table 5-13: FPU Loads and Stores Using Register+Offset Address Mode (63)Table 5-14: FPU Loads and Using Register+Register Address Mode (63)Table 5-15: FPU Move To and From Instructions (63)Table 5-16: FPU IEEE Arithmetic Operations (64)Table 5-17: FPU-Approximate Arithmetic Operations (64)Table 5-18: FPU Multiply-Accumulate Arithmetic Operations (65)Table 5-19: FPU Conversion Operations Using the FCSR Rounding Mode (65)Table 5-20: FPU Conversion Operations Using a Directed Rounding Mode (65)Table 5-21: FPU Formatted Operand Move Instructions (66)Table 5-22: FPU Conditional Move on True/False Instructions (66)iv MIPS32™ Architecture For Programmers Volume I, Revision 2.00 Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Table 5-23: FPU Conditional Move on Zero/Nonzero Instructions (67)Table 5-24: FPU Conditional Branch Instructions (67)Table 5-25: Deprecated FPU Conditional Branch Likely Instructions (67)Table 5-26: CPU Conditional Move on FPU True/False Instructions (68)Table 5-27: FPU Operand Format Field (fmt, fmt3) Encoding (68)Table 5-28: Valid Formats for FPU Operations (69)Table 5-29: FPU Instruction Format Fields (72)Table A-1: Symbols Used in the Instruction Encoding Tables (76)Table A-2: MIPS32 Encoding of the Opcode Field (77)Table A-3: MIPS32 SPECIAL Opcode Encoding of Function Field (78)Table A-4: MIPS32 REGIMM Encoding of rt Field (78)Table A-5: MIPS32 SPECIAL2 Encoding of Function Field (78)Table A-6: MIPS32 SPECIAL3 Encoding of Function Field for Release 2 of the Architecture (78)Table A-7: MIPS32 MOVCI Encoding of tf Bit (79)Table A-8: MIPS32 SRL Encoding of Shift/Rotate (79)Table A-9: MIPS32 SRLV Encoding of Shift/Rotate (79)Table A-10: MIPS32 BSHFL Encoding of sa Field (79)Table A-11: MIPS32 COP0 Encoding of rs Field (79)Table A-12: MIPS32 COP0 Encoding of Function Field When rs=CO (80)Table A-13: MIPS32 COP1 Encoding of rs Field (80)Table A-14: MIPS32 COP1 Encoding of Function Field When rs=S (80)Table A-15: MIPS32 COP1 Encoding of Function Field When rs=D (81)Table A-16: MIPS32 COP1 Encoding of Function Field When rs=W or L (81)Table A-17: MIPS64 COP1 Encoding of Function Field When rs=PS (81)Table A-18: MIPS32 COP1 Encoding of tf Bit When rs=S, D, or PS, Function=MOVCF (81)Table A-19: MIPS32 COP2 Encoding of rs Field (82)Table A-20: MIPS64 COP1X Encoding of Function Field (82)Table A-21: Floating Point Unit Instruction Format Encodings (82)MIPS32™ Architecture For Programmers Volume I, Revision 2.00v Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.vi MIPS32™ Architecture For Programmers Volume I, Revision 2.00 Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Chapter 1About This BookThe MIPS32™ Architecture For Programmers V olume I comes as a multi-volume set.•V olume I describes conventions used throughout the document set, and provides an introduction to the MIPS32™Architecture•V olume II provides detailed descriptions of each instruction in the MIPS32™ instruction set•V olume III describes the MIPS32™Privileged Resource Architecture which defines and governs the behavior of the privileged resources included in a MIPS32™ processor implementation•V olume IV-a describes the MIPS16e™ Application-Specific Extension to the MIPS32™ Architecture•V olume IV-b describes the MDMX™ Application-Specific Extension to the MIPS32™ Architecture and is notapplicable to the MIPS32™ document set•V olume IV-c describes the MIPS-3D™ Application-Specific Extension to the MIPS64™ Architecture and is notapplicable to the MIPS32™ document set•V olume IV-d describes the SmartMIPS™Application-Specific Extension to the MIPS32™ Architecture1.1Typographical ConventionsThis section describes the use of italic,bold and courier fonts in this book.1.1.1Italic Text•is used for emphasis•is used for bits,fields,registers, that are important from a software perspective (for instance, address bits used bysoftware,and programmablefields and registers),and variousfloating point instruction formats,such as S,D,and PS •is used for the memory access types, such as cached and uncached1.1.2Bold Text•represents a term that is being defined•is used for bits andfields that are important from a hardware perspective (for instance,register bits, which are not programmable but accessible only to hardware)•is used for ranges of numbers; the range is indicated by an ellipsis. For instance,5..1indicates numbers 5 through 1•is used to emphasize UNPREDICTABLE and UNDEFINED behavior, as defined below.1.1.3Courier TextCourier fixed-width font is used for text that is displayed on the screen, and for examples of code and instruction pseudocode.MIPS32™ Architecture For Programmers Volume I, Revision 2.001 Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.Chapter 1 About This Book1.2UNPREDICTABLE and UNDEFINEDThe terms UNPREDICTABLE and UNDEFINED are used throughout this book to describe the behavior of theprocessor in certain cases.UNDEFINED behavior or operations can occur only as the result of executing instructions in a privileged mode (i.e., in Kernel Mode or Debug Mode, or with the CP0 usable bit set in the Status register).Unprivileged software can never cause UNDEFINED behavior or operations. Conversely, both privileged andunprivileged software can cause UNPREDICTABLE results or operations.1.2.1UNPREDICTABLEUNPREDICTABLE results may vary from processor implementation to implementation,instruction to instruction,or as a function of time on the same implementation or instruction. Software can never depend on results that areUNPREDICTABLE.UNPREDICTABLE operations may cause a result to be generated or not.If a result is generated, it is UNPREDICTABLE.UNPREDICTABLE operations may cause arbitrary exceptions.UNPREDICTABLE results or operations have several implementation restrictions:•Implementations of operations generating UNPREDICTABLE results must not depend on any data source(memory or internal state) which is inaccessible in the current processor mode•UNPREDICTABLE operations must not read, write, or modify the contents of memory or internal state which is inaccessible in the current processor mode. For example,UNPREDICTABLE operations executed in user modemust not access memory or internal state that is only accessible in Kernel Mode or Debug Mode or in another process •UNPREDICTABLE operations must not halt or hang the processor1.2.2UNDEFINEDUNDEFINED operations or behavior may vary from processor implementation to implementation, instruction toinstruction, or as a function of time on the same implementation or instruction.UNDEFINED operations or behavior may vary from nothing to creating an environment in which execution can no longer continue.UNDEFINED operations or behavior may cause data loss.UNDEFINED operations or behavior has one implementation restriction:•UNDEFINED operations or behavior must not cause the processor to hang(that is,enter a state from which there is no exit other than powering down the processor).The assertion of any of the reset signals must restore the processor to an operational state1.3Special Symbols in Pseudocode NotationIn this book, algorithmic descriptions of an operation are described as pseudocode in a high-level language notation resembling Pascal. Special symbols used in the pseudocode notation are listed in Table 1-1.Table 1-1 Symbols Used in Instruction Operation StatementsSymbol Meaning←Assignment=, ≠Tests for equality and inequality||Bit string concatenationx y A y-bit string formed by y copies of the single-bit value x2MIPS32™ Architecture For Programmers Volume I, Revision 2.00 Copyright © 2001-2003 MIPS Technologies Inc. All rights reserved.1.3Special Symbols in Pseudocode Notationb#n A constant value n in base b.For instance10#100represents the decimal value100,2#100represents the binary value 100 (decimal 4), and 16#100 represents the hexadecimal value 100 (decimal 256). If the "b#" prefix is omitted, the default base is 10.x y..z Selection of bits y through z of bit string x.Little-endian bit notation(rightmost bit is0)is used.If y is less than z, this expression is an empty (zero length) bit string.+, −2’s complement or floating point arithmetic: addition, subtraction∗, ×2’s complement or floating point multiplication (both used for either)div2’s complement integer divisionmod2’s complement modulo/Floating point division<2’s complement less-than comparison>2’s complement greater-than comparison≤2’s complement less-than or equal comparison≥2’s complement greater-than or equal comparisonnor Bitwise logical NORxor Bitwise logical XORand Bitwise logical ANDor Bitwise logical ORGPRLEN The length in bits (32 or 64) of the CPU general-purpose registersGPR[x]CPU general-purpose register x. The content of GPR[0] is always zero.SGPR[s,x]In Release 2 of the Architecture, multiple copies of the CPU general-purpose registers may be implemented.SGPR[s,x] refers to GPR set s, register x. GPR[x] is a short-hand notation for SGPR[ SRSCtl CSS, x].FPR[x]Floating Point operand register xFCC[CC]Floating Point condition code CC.FCC[0] has the same value as COC[1].FPR[x]Floating Point (Coprocessor unit 1), general register xCPR[z,x,s]Coprocessor unit z, general register x,select sCP2CPR[x]Coprocessor unit 2, general register xCCR[z,x]Coprocessor unit z, control register xCP2CCR[x]Coprocessor unit 2, control register xCOC[z]Coprocessor unit z condition signalXlat[x]Translation of the MIPS16e GPR number x into the corresponding 32-bit GPR numberBigEndianMem Endian mode as configured at chip reset (0→Little-Endian, 1→ Big-Endian). Specifies the endianness of the memory interface(see LoadMemory and StoreMemory pseudocode function descriptions),and the endianness of Kernel and Supervisor mode execution.BigEndianCPU The endianness for load and store instructions (0→ Little-Endian, 1→ Big-Endian). In User mode, this endianness may be switched by setting the RE bit in the Status register.Thus,BigEndianCPU may be computed as (BigEndianMem XOR ReverseEndian).Table 1-1 Symbols Used in Instruction Operation StatementsSymbol MeaningChapter 1 About This Book1.4For More InformationVarious MIPS RISC processor manuals and additional information about MIPS products can be found at the MIPS URL:ReverseEndianSignal to reverse the endianness of load and store instructions.This feature is available in User mode only,and is implemented by setting the RE bit of the Status register.Thus,ReverseEndian may be computed as (SR RE and User mode).LLbitBit of virtual state used to specify operation for instructions that provide atomic read-modify-write.LLbit is set when a linked load occurs; it is tested and cleared by the conditional store. It is cleared, during other CPU operation,when a store to the location would no longer be atomic.In particular,it is cleared by exception return instructions.I :,I+n :,I-n :This occurs as a prefix to Operation description lines and functions as a label. It indicates the instruction time during which the pseudocode appears to “execute.” Unless otherwise indicated, all effects of the currentinstruction appear to occur during the instruction time of the current instruction.No label is equivalent to a time label of I . Sometimes effects of an instruction appear to occur either earlier or later — that is, during theinstruction time of another instruction.When this happens,the instruction operation is written in sections labeled with the instruction time,relative to the current instruction I ,in which the effect of that pseudocode appears to occur.For example,an instruction may have a result that is not available until after the next instruction.Such an instruction has the portion of the instruction operation description that writes the result register in a section labeled I +1.The effect of pseudocode statements for the current instruction labelled I +1appears to occur “at the same time”as the effect of pseudocode statements labeled I for the following instruction.Within one pseudocode sequence,the effects of the statements take place in order. However, between sequences of statements for differentinstructions that occur “at the same time,” there is no defined order. Programs must not depend on a particular order of evaluation between such sections.PCThe Program Counter value.During the instruction time of an instruction,this is the address of the instruction word. The address of the instruction that occurs during the next instruction time is determined by assigning a value to PC during an instruction time. If no value is assigned to PC during an instruction time by anypseudocode statement,it is automatically incremented by either 2(in the case of a 16-bit MIPS16e instruction)or 4before the next instruction time.A taken branch assigns the target address to the PC during the instruction time of the instruction in the branch delay slot.PABITSThe number of physical address bits implemented is represented by the symbol PABITS.As such,if 36physical address bits were implemented, the size of the physical address space would be 2PABITS = 236 bytes.FP32RegistersModeIndicates whether the FPU has 32-bit or 64-bit floating point registers (FPRs).In MIPS32,the FPU has 3232-bit FPRs in which 64-bit data types are stored in even-odd pairs of FPRs.In MIPS64,the FPU has 3264-bit FPRs in which 64-bit data types are stored in any FPR.In MIPS32implementations,FP32RegistersMode is always a 0.MIPS64implementations have a compatibility mode in which the processor references the FPRs as if it were a MIPS32 implementation. In such a caseFP32RegisterMode is computed from the FR bit in the Status register.If this bit is a 0,the processor operates as if it had 32 32-bit FPRs. If this bit is a 1, the processor operates with 32 64-bit FPRs.The value of FP32RegistersMode is computed from the FR bit in the Status register.InstructionInBranchDelaySlotIndicates whether the instruction at the Program Counter address was executed in the delay slot of a branch or jump. This condition reflects the dynamic state of the instruction, not the static state. That is, the value is false if a branch or jump occurs to an instruction whose PC immediately follows a branch or jump, but which is not executed in the delay slot of a branch or jump.SignalException(exce ption, argument)Causes an exception to be signaled, using the exception parameter as the type of exception and the argument parameter as an exception-specific argument). Control does not return from this pseudocode function - the exception is signaled at the point of the call.Table 1-1 Symbols Used in Instruction Operation StatementsSymbolMeaning。
3GPP TS 36.331 V13.2.0 (2016-06)
![3GPP TS 36.331 V13.2.0 (2016-06)](https://img.taocdn.com/s3/m/be566ac0195f312b3169a564.png)
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)。
wm8978数据手册_引脚图_参数
![wm8978数据手册_引脚图_参数](https://img.taocdn.com/s3/m/ded28032a300a6c30c229fec.png)
The device integrates preamps for stereo differential mics, and includes drivers for speakers, headphone and differential or stereo line output. External component requirements are reduced as no separate microphone or headphone amplifiers are required.
BLOCK DIAGRAM ................................................................................................ 1
FEATURES ............................................................................................................ 1
ISO 14229-3-2012在CAN实施上的统一诊断服务
![ISO 14229-3-2012在CAN实施上的统一诊断服务](https://img.taocdn.com/s3/m/72bb4404650e52ea54189813.png)
Published in Switzerland
6
Unified diagnostic services implementation on CAN ..................................................................................................... 4
4
Conventions ............................................................................................................................................................................................................... 2
INTERNATIONAL STANDARD
ISO 14229-3
First edition 2012-12-01
Road vehicles — Unified diagnostic services (UDS) —
Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)
3.1 Terms and definitions ....................................................................................................................................................................... 1
GSM0710中文版
![GSM0710中文版](https://img.taocdn.com/s3/m/6ac84486a0116c175f0e481b.png)
杭州波导软件有限公司
3.4. 过程和状态..................................................................................................................... 20 3.4.1. 建立 DLC 链路 ........................................................................................ 20 3.4.2. 释放 DLC 链路 ........................................................................................ 20 3.4.3. 信息传输 .................................................................................................. 21 3.4.4. 帧变量...................................................................................................... 21 3.4.5. 超时的考虑 .............................................................................................. 22 3.4.6. 多路控制通道 .......................................................................................... 22 3.4.6.1. 控制消息格式........................................................................................... 22 3.4.6.2. 控制消息类型参数 ................................................................................... 23 3.4.7. 电源控制与唤醒机制 .............................................................................. 32 3.4.8. 流控.......................................................................................................... 32 3.5. 集成层 Convergence Layer ............................................................................................ 34 3.5.1. 类型 1-未结构化的字节流...................................................................... 34 3.5.2. 类型 2-带参数的未结构化的字节流...................................................... 34 3.5.3. 类型 3-不可中断的帧数据...................................................................... 36 3.5.4. 类型 4-可中断的帧数据.......................................................................... 36 3.6. DLCI 值 ........................................................................................................................... 37 3.7. 系统参数......................................................................................................................... 37 3.7.1. 确认时间 T1 ............................................................................................ 37 3.7.2. 帧的最大长度 N1 .................................................................................... 38 3.7.3. 最大重发次数 N2 .................................................................................... 38 3.7.4. 窗口大小 k ............................................................................................... 38 3.7.5. 控制通道的响应时间 T2 ........................................................................ 38 3.7.6. 唤醒流程的响应时间 T3 ........................................................................ 38 3.8. 启动和关闭 MUX .......................................................................................................... 38 4. Error Recovery Mode ................................................................................................................. 39
第5章-SPSS基本统计分析
![第5章-SPSS基本统计分析](https://img.taocdn.com/s3/m/79b8ed17bf1e650e52ea551810a6f524cdbfcb43.png)
To tal 21
21 .0 10 0.0%
70 .0 % 70 .0 %
9 9.0 10 0.0% 30 .0 % 30 .0 %
30 30 .0 10 0.0% 10 0.0% 10 0.0%
2.描述离散程度的统计量
(1)标准差(standard deviation--Std Dev) (2)方差(variance) (3)极差(range):
最大值(minimum)-最小值(minimum) 极差很小表明所有数据几乎集中在一起 应用于相同样本容量的两组数据离散程度
比较
3.描述分布特征的统计量
2.Option 选项
四、分组计算描述统计量
1.菜单选项:Data->Split File; 2.选择拆分变量到Groups Based on 框中; 3.选择输出方式:Compare groups
/Organize output by groups; 4.点选Sort the file by grouping
文 化 程度
专科
1
高中
1
5
0
1
3
7
4
1
0
0
2
0
3
1
5
初中
0 0 6 6 0 3 0 3
To tal 3 6
12 21
1 5 3 9
一、交叉分组下的频数分析
交叉列联表单元格中的数据项:
(1)观察频数(Observed Counts)
(2)期望频数(Expected Counts)
S1D13305中文资料
![S1D13305中文资料](https://img.taocdn.com/s3/m/e6ca321459eef8c75fbfb3b4.png)
元器件交易网
The information of the product number change
Starting April 1, 2001, the product number will be changed as listed below. To order from April 1, 2001 please use the new product number. For further information, please contact Epson sales representative.
SDU1374#0C SDU1375#0C SDU1376#0C SDU1376BVR SDU1378#0C
• S1D1380x Series New No. Previous No.
SDU1386#0C
New No.
S5U13806P00C
S5U13503P00C S5U13504P00C S5U13505P00C S5U13506P00C
S1D13305 Series S1D13305D00A S1D13305F00A S1D13305F00B
S1D1370x Series S1D13704F00A S1D13705F00A S1D13706B00A S1D13706F00A S1D13708 Series
• S1D1350x Series Previous No.
S5U13704P00C S5U13705P00C S5U13706P00C S5U13706B32R S5U13708P00C
• S1D13A0x Series Previous No.
SDU13A3#0C SDU13A4#0C
New No.
Gate_of_Heaven
![Gate_of_Heaven](https://img.taocdn.com/s3/m/1b2b1b63ef06eff9aef8941ea76e58fafbb04510.png)
Culturehinese CultureC82 | China Book Internationalthree ears form an equilateral triangle, creating a circular pattern that complements the motif. This ingenious design seamlessly unifies the dynamic scene, bringing it to the center of vision. Surrounding the double-layered lotus pattern are eight red-garbed apsaras dancing in the clouds, positioned in different directions, their fluid and elegant lines breaking the central stable layout, as if the entire lotus revolves with the flying apsaras. The caisson’s core is adorned with neatly arranged triangular drapes, representing the outermost decoration. The precision and varying colors of these drapes exemplify the traditional Chinese concept of unity in diversity. The overall pattern moves beyond the simplicity of the Northern Dynasties, with extensive use of cold tones of stone green and blue, interspersed with touches of red and white, creating a strong visual impact through complementary and contrasting colors, thereby enhancing its artistic appeal. The motif of the three rabbits often appears as the main pattern in Sui Dynasty caisson ceilings, with remarkably similar designs found in Mogao Caves 407, 406, and 420. Various-sized beads from Western Asia are meticulously arranged around and diagonally to thecaisson pattern, visually enhancing its brightness and depth.Sui Dynasty caisson patterns exhibit significant changes in pictorial structure, thematic content, decorative techniques, and color application compared to the Northern Dynasties,adding a sense of lively natural beauty to the dignified simplicity. Simultaneously, they laid a solid foundation for the flourishing of Tang Dynasty caisson art.Flourishing Period: Dazzling IntricacyIn the Tang Dynasty, with increased interaction between the Central Plains and the Western Regions, new developments emerged in Dunhuang caisson patterns, characterized by complexstructures, intricate decorations, and lavish colors.Early Tang caisson patterns,while maintaining the structural framework of the Sui Dynasty, began to subtly evolve, notably with a broader central area, fewer decorative layers on the periphery, and a focus onhighlighting the central motif. The central motifs typically featured grape pomegranate patterns, pomegranate lotus patterns, and lotus patterns. The lotus pattern remained the mainstream caisson motif of this period, with its diverse forms leading to different types like the flat-petal lotus pattern, peach-shaped petal lotus pattern, and irregular lotus pattern caissons. The pomegranate and grape patterns come from exotic lands. Thepomegranate or grape lotus caisson patterns are arranged in a “cross” or “X” shape. The realistic grape patterns are often used with lotus patterns. The gaps are filled with small lotus flowers, cloud patterns,A caisson ceiling with three rabbits and lotus flower patterns, Cave No. 407, Sui Dynasty。
补中益气汤抗感染_抗肿瘤与免疫药理学研究_胡兵
![补中益气汤抗感染_抗肿瘤与免疫药理学研究_胡兵](https://img.taocdn.com/s3/m/3cb00cd5d15abe23482f4d3b.png)
C ent ral S out h Ph armacy. D ecember 2008, V ol 6 N o 6
t he t ransport of epiru bicin i n human in test inal epit hel ial Caco 2 cell layers and evert ed gu t sacs of rat s [ J] . Biochem. Pharma col, 2000, 60 ( 9) : 1381 1390. M ichiel i M , Damiani D, Ermacora A , et al. Liposome encap sul at ed daunorubi cin for PG P relat ed mult idrug res ist an ce [ J] . Br J Haem at ol, 1999, 106 ( 1) : 92 99. G oren D , H orowit z A T, T zemach D , et al. N uclear delivery of doxorubicin via folat e t arget ed liposomes w it h b ypas s of m ult i drug res ist an ce eff lux pump [ J ] . Clin Cancer Res, 2000, 6 ( ) : 1949 1957. K obayash i T, Ishida T , O kada Y, et al. Ef f ect of t ransf errin recept or t arget ed li posomal doxorubicin in P glycoprot ein medi at ed drug resist ant t umor cel ls [ J ] . Int J Pharm, 2007, 329 ( 1 2) : 94 102. V ogel gesang S, Cascorb i I, S chroeder E, et al. D epos iti on of A lz heim er's b et a amyloid is in vers ely correlat ed wit h Pgl ycop rot ein ex pres sion in t he brains of elderly n on demen t ed h umans [ J] . Pharmacogeneti cs, 2002, 12 ( 7) : 535 541. Furun o T , Lan di M T, Ceroni M , et al. Expressi on pol ymor phism of t he blood b rain bar rier componen t P glycoprot ein ( M D R1 ) in relati on t o Parkin son's dis ease [ J] . Pharm acoge net ics 2002, 12 ( 7) : 529 534. T homas H , C ol ey HM . O vercom ing m ult idrug resi st an ce in cancer: an updat e on t h e clinical st rat egy of inhibit in g p glyco prot ein [ J] . Can cer Cont rol, 2003, 10 ( 2) : 159 165. V arma M V , A s hokraj Y , Dey CS, et al . P glycoprotein inh ibi t ors an d t heir screenin g: a perspect ive f rom bioavailabilit y en hancement [ J] . Pharmacol Res. 2003, 48 ( 4) : 347 359. ( 收稿日期 : 2007 12 20; 修回日期 : 2008 03 30)
Layer-Based Dependency Parsing
![Layer-Based Dependency Parsing](https://img.taocdn.com/s3/m/9ac750c36f1aff00bed51ee8.png)
Layer-Based Dependency Parsing*Ping Jian and Chengqing ZongInstitute of Automation, Chinese Academy of SciencesNo. 95 Zhongguancun East Road, Beijing, 100190, China{pjian, cqzong}@Abstract. In this paper, a layer-based projective dependency parsing approach is presented.This novel approach works layer by layer from the bottom up. Inside the layer thedependency graphs are searched exhaustively while between the layers the parser statetransfers deterministically. Taking the dependency layer as the parsing unit, the proposedparser has a lower computational complexity than graph-based models which search for awhole dependency graph and alleviates the error propagation that transition-based modelssuffer from to some extent. Furthermore, our parser adopts the sequence labeling models tofind the optimal sub-graph of the layer which demonstrates that the sequence labelingtechniques are also competent for hierarchical structure analysis tasks. Experimental resultsindicate that the proposed approach offers desirable accuracies and especially a fast parsingspeed.Keywords: dependency parsing, dependency layer, sequence labeling1IntroductionGraph-based models (McDonald et al., 2005; McDonald and Pereira, 2006) and transition-based models (Yamada and Matsumoto, 2003; Nivre and Scholz, 2004) are two dominant paradigms in the dependency parsing community. McDonald and Nivre (2007) have made elaborate analyses about the very different theoretical properties of these two kinds of models and the corresponding experimental behaviors.Generally, graph-based approaches learn a model for scoring possible dependency graphs of an input sentence and apply exhaustive search algorithms to find the one that maximizes the score. The unit graph-based models calculate is the whole sentence (the whole dependency graph) both in training and inference procedures, which results in a cubic computational complexity (in projective case). By contrast, transition-based approaches train a classifier to greedily choose the best parsing action under the current parser state. They make decisions at a configuration which is usually composed by a couple of focus tokens and the parsing contexts. Therefore, these two kinds of dependency parsing methods represent the two extremes when they seek the best dependency structure of the input sentence. In this paper, we adopt a moderate structural granularity to calculate the parser: a dependency layer.The dependency layer we mean here is a set of tokens whose dependency depth (the depth of the dependency tree) is at most one. Inside the layer the dependency graphs can be searched exhaustively while between the layers the parser state transfers deterministically. On one hand, this design will decrease the computational cost for searching the whole tree like graph-based models do; on the other hand, it may alleviate the error propagation resulting from the complete no “search” outside the parsing configuration in transition-based models.*The research work has been partially funded by the Natural Science Foundation of China under grant No.60736014, 60723005 and 90820303, the National Key Technology R&D Program under grant No.2006BAH03B02, the Hi-Tech Research and Development Program (863 Program) of China under grant No.2006AA010108-4, and also supported by the China-Singapore Institute of Digital Media as well.Copyright 2009 by Ping Jian and Chengqing Zong23rd Pacific Asia Conference on Language,Information and Computation,pages230–239It is well known that chunking, which is deemed to be a useful and tractable precursor to full parsing, has been successfully handled by sequence labeling techniques (Kudo and Matsumoto, 2001; Sha and Pereira, 2003). Inspired by this scheme, we adopt the globally optimal sequence labeling to search the best depth-one sub-graph in the dependency layer. We believe that the line-typed sequential models are potent complementarities to the tree-typed hierarchical ones or even the latent substitutes.The experiments show that our layer-based parser yields comparable dependency attachment accuracies to the state-of-the-art dependency parsers on both English and Chinese datasets. Especially, it is quite efficient due to the layer-based search and sequence typed analysis. The remainder of the paper is organized as follows: Section 2 describes the details of the algorithm and feature set. Section 3 presents the experimental results. The related work is discussed in Section 4. Conclusion and future work comprise Section 5.2 Layer-based Parsing Approach2.1 AlgorithmsWu et al. (2007) designed a neighbor parser to identify the neighboring parent-child relations between two consecutive tokens in the input sentence. Following their framework we label the dependency relations in our parsing layer. An example is shown in Figure 1(a). The first and second columns represent the words and part-of-speech (POS) tags respectively. The third column implies whether the token modifies its left neighbor (LH, left-headed) or right neighbor (RH, right-headed) or neither (O). The string behind the character “_” indicates the dependency type of the neighboring link.Wu et al. (2007) employed linear chain conditional random fields (CRFs) as the labelingalgorithm to capture the higher order features and avoid the greedy search when labeling with sequential classifiers (Cheng et al., 2006). To prevent the error propagation, they regarded the labeling results as features of the subsequent parsing stage instead of reducing the child words. However, this weakens the strength that neighboring parsing can provide. In our approach, besides the CRF-based relation labeler, an additional tagger is introduced to examine whether a dependent child can be reduced, i.e., whether it has found its head and has already been a complete sub-tree. The reduce tagger tries to guarantee safe reductions and ensures the parsed structures can be formed into a tree after several passes of analysis. In Figure 1(b), the letter “r” in the rightmost column implies that the corresponding token will be reduced while others are reserved for the next stage.The reduce tagger is also trained by linear chain CRFs to fulfill the globally optimal property of the layer-based labeling. Specially, when continuous attachments happen in the same direction, only the lowest child token is reduced although other tokens in this chain are complete sub-trees after the current labeling. This enables the tokens to change their Figure 1: Example of (a) the sequential neighboring relation labeling, (b) the reduce decision labeling.TheDT RH_NMOD chairNN O ofIN LH_NMOD theDT RH_NMOD conferenceNN O declaredVBD O thatDT RH_NOMD decision NN OThe chair of the conference declared that decision(b)The DT RH_NMOD r chair NN O o of IN LH_NMOD o the DT RH_NMOD r conference NN O o declared VBD O o that DT RH_NOMD r decision NN O o (a)attachments when the context is refreshed in the next layer. For example, in Figure 2, if the parent word “of” and the child word “conference” are far from each other in the early parsing stage, the child “conference” may be wrongly attached to the word “declared” (Figure 2(a)) because long distance interrelations are difficult to be caught in sequence labeling models. If the tagger is learned to only reduce the lowest child token each time, i.e., the leftmost word “the”, the word “conference” has the chance to adjoin “of” and be attached correctly at last (Figure 2(b)).As the dependency relations only exist between adjacent tokens and all the survivals will berelabeled in the next layer, the dependency depth of the layer is at most one.Pseudo-code of the parsing algorithm is given as follows:Input sentence: w 1, w 2, …, w n Initialize: L = {w 1, w 2, …, w n };have_reduce = false ; Start: While |L|>1 do begin x = get_feature (L);y 1 = estimate_relation (model 1, x);y 2 = estimate_reduce (model 2, x, y 1);have_reduce = sign(count_reduce (y 2));if(have_reduce == true )reduce (L, y 2);have_reduce = false ; else break; end; end.At each processing stage, two functions, estimate_relation and estimate_reduce , are employed to label the sequence L with neighboring dependency relations (y 1) and reduce decisions (y 2). model 1 and model 2 are the pre-trained models accordingly. Then the parser reduces the “r” tagged tokens and transfers them as the children features for the next labeling stage. This process is repeated until there is no token to be reduced or the size of L equals 1. The remaining parsing process for the example sentence in Figure 1 is illustrated step by step in Figure 3 to give a more specific description of the algorithm.Together with the initial labeling stage showed in Figure 1(b), the layer-based algorithm spends five iterations, i.e., five layers to get the final dependency graph of the input sentence. In each layer, the neighboring dependency relations and reduce decisions are traded off at different chair the - Oo of - - LH_NMODo conference the - LH_PMODr declared - - Oo decision that - LH_OBJ r chair the - O o of - conference LH_NMOD r declared - decision O o chair the of RH_SUB rdeclared - decision O odeclared chair decision O o Figure 3: The parsing process following th e stage showed in Figure 1(b). The second column lists the left child of the current token attached in the latest analysis and the third column is the right one. of… theRH_NMOD conferenceRH_SUB × declared … of … conference LH_PMOD √ declared …(a): (b): Figure 2: Long dependency attaching error in neighboring relation labelingsequence positions to obtain a globally optimal depth-one dependency sub-graph. Between the layers, the pre-built structure is handed on through the surviving tokens as well as their children. Since dependency relations only exist between two consecutive tokens, the child appearing in the observation sequence is always the leftmost or rightmost one of the parent token. Previous work based on deterministic models (Nivre and Scholz, 2004; Hall et al., 2007) has verified that the information of the children at these positions is more useful than that of others.For training, the parsing process described above is repeated on each sentence in the training set to pick up instances on different layers.In addition, the reduce examiner in the two-time labeling algorithm described above relies too much on the relation labeling results since it takes the relation labels as features. Therefore, a one-time labeling framework is introduced to be an alteration of the two-time labeling one. Figure 4 shows an example. The strings in the third column are the integrated symbols of the dependency relation labels and the reduce labels. Because the token whose head is not found will not be tagged with “r”, a unique symbol “O” is enough to express this case.The DT RH_NMOD_rchair NN Oof IN LH_NMOD_othe DT RH_NMOD_rconference NN Odeclared VBD Othat DT RH_NOMD_rdecision NN OFigure 4: Integration of the relation and reduce labels2.2Usage of N-best Searching ResultsThe algorithm described above stops the parsing process if there is no reduce label “r” in the current layer. However, sometimes the fact is that the parser quits so early while the tree is not well formed yet at that point. One reason is that the reduce tagger is more prone to assign an “o” than an “r” due to the unbalanced training instances. Taking this into account, we use the n-best searching results produced by the CRF-based labeler to amend.Taking the two-time labeling for example, although there is no “r” assigned in the current stage, the parsing process still continues if there is a relation annotated between the neighbors. The parser will ask for the next best relation label sequence (y1’) and consequently estimate the reduce labels based on it. But if y1’ is not assigned with relations, the parser will fall back on the initial best labels (y1) and further request the next best reduce labels for y1. In our experiments, only 2-best outputs of the labeler are utilized and the experimental results show that it works well.2.3Feature DesignThe features used in our labelers are summarized in Table 1. Features of the tokens and children are prepared to parameterize the dependency attachment model. The relation features are added when tagging the reduce decisions in two-time labeling case.As a typical sequence labeling task, the features chosen for our parser are similar to those adopted in (Sha and Pereira, 2003) for shallow parsing, and a first-order Markov dependency between labels is considered.Cheng et al. (2006) argued that the features and the strategies for parsing in the early stage are different from parsing in the upper stages in bottom-up deterministic parsing approaches. Because the initial stage parses “words” while the upper stages parse “phrases”. For this reason, we improve the proposed parser to a model-divided one in which one model is only for the first parsing layer and the other takes charge of the higher layers. The children features listed in Table 1 will not be used to parameterize the first layer model.Table 1: Feature set for the neighboring parsing. w is the word and p is the POS tag of the token. lc and rc represent the leftmost and rightmost child, and the dependency relation type of them uses typ. The relation features like “RH_SUB” are denoted by rel. Digit bracketed marks the position of the token where the feature is sampled, negative for the left and positive for the right. “ ” denotes the combination.Tokens w[-3], w[-2], w[-1], w[0], w[1], w[2], w[3]p[-3], p[-2], p[-1], p[0], p[1], p[2], p[3]p[-2] p[-1], p[-1] p[0], p[0] p[1], p[1] p[2], p[-1] p[0] p[1]w[-1] p[-1], w[0] p[0], w[1] p[1]Children w_lc[0], w_rc[0]p_lc[-1], p_rc[-1], p_lc[0], p_rc[0], p_lc[1], p_rc[1]p[-1] p_lc[-1], p[-1] p_rc[-1], p[0] p_lc[0], p[0] p_rc[0], p[1] p_lc[1], p[1] p_rc[1]typ_lc[-1], typ_rc[-1], typ_lc[0], typ_rc[0], typ_lc[1], typ_rc[1]Relations rel[-3], rel[-2], rel[-1], rel[0], rel[1], rel[2], rel[3]3ExperimentsTo evaluate the effectiveness and efficiency of the layer-based approach, we conducted dependency parsing experiments on both English and Chinese datasets.The English experiments were carried out on the WSJ part of Penn Treebank (Marcus et al., 1993). To match the previous work (Nivre and Scholz, 2004; Hall et al., 2006; McDonald and Pereira, 2006), we used sections 02-21 for training, section 22 for development and section 23 (about 56,684 words) for testing. The head-finding rules employed by Yamada and Matsumoto (2003) were adopted here to convert the constituent structures to dependency ones and a set of 12 dependency types was utilized as what Hall et al. (2006) did.1 The POS tags for the development and testing set were automatically assigned by MXPOST (Ratnaparkhi, 1996). A tagging accuracy 97.05% was achieved on the testing set.The Chinese experiments were evaluated on the Penn Chinese Treebank (CTB) version 5.0 (Xue et al., 2005). The corpus was split into training, development, and testing data as Duan et al. (2007) did to balance the different resources. 16,079 sentences were for training, 803 for development, and 1,905 (about 50,319 words) for testing. The head-finding rules and dependency type set also followed Hall et al. (2006). 2 Gold standard POS tags were used.Eight parsers involved in our main experiments are concisely introduced as following: MaltParser (Nivre et al., 2006): adopts transition-based model described in (Nivre, 2004). Here, MaltParser version 1.1 is employed.Yamada03: our implementation of another typical transition-based model proposed in (Yamada and Matsumoto, 2003).MSTParser1: The first-order paradigm of MSTParser3 which implements the graph-based models described in (McDonald et al., 2005; McDonald and Pereira, 2006). Version 0.2 is used. MSTParser2: The second-order paradigm of MSTParser.Duan07: A probabilistic parsing action model proposed by Duan et al. (2007) which globally seeks the optimal action sequence above the transition-based model described in (Yamada and Matsumoto, 2003) with beam search algorithm and employs SVMs for learning.LDParser1: One of the layer-based dependency parsers which labels the relations and reduce decisions at one time.LDParser2: One of the layer-based dependency parsers which labels the relations and reduce decisions separately.1The tree conversion and the arc labeling were implemented by Penn2Malt(http://w3.msi.vxu.se/~nivre/research/Penn2Malt.html) with the “Malt” hard-coding setting.2It was realized by Penn2Malt with the head-finding rules it provided for Chinese and the hard-coding setting.3/~strctlrn/MSTParser/MSTParser.htmlLDP1div: LDParser1 using divided models. In our experiments, the first layer instances in the training set are used to train the first layer model while the instances on all of the layers are trained for the higher layer model.The first five models are taken as the baselines in the experiments and the last three ones are the proposed parsers to be compared.The results are evaluated by the unlabeled attachment score (UAS), labeled attachment score (LAS), root accuracy (RA) and complete match (CM) according to Nivre and Scholz (2004) except that RA is the proportion of sentences in which the root word is correctly identified. All the metrics are calculated excluding the punctuations besides CM. We also present the detailed comparisons with the baselines in aspects of the computational complexity and the testing time (the CPU time). All the experiments were done on a 32-bit Intel Xeon 2.33GHz processor.3.1English ResultsIn the English experiments, all the parsers listed above except Duan07 were compared. For MaltParser, we chose the arc-eager algorithm (Nivre, 2004) and the feature set which got the best performance for English in (Hall et al., 2006) (the feature model Φ5 in their work). Hall et al. (2006) reported that the SVMs learning algorithm outperformed memory-based learning (MBL) on this feature set and could parse faster. It is the same case for Chinese. Therefore, SVMs were used for both our English and Chinese experiments. We also compared the split MaltParser which utilizes the efficient Classifiers Splitting in the experiment where the POS tag of the next input token was selected for splitting and the split threshold was 1,000. For Yamada03, the optimal feature context window size six was chosen and the dependency relation type of the child tokens was added into the feature set. The model was also trained dividedly according to the POS tag of the left target token. For MSTParser, we tried to reproduce the results in (McDonald et al., 2005) and (McDonald and Pereira, 2006) by using the 5-best projective parsing algorithm and not including punctuations in Hamming loss calculation.Considering the training cost, only the features that occur more than twice were modeled in LDParser1 and LDP1div. The combination of the children features and the combination between the word and POS features in Table 1 were also omitted.The final results are compiled in Table 2. n denotes the length of the input sentence and R is the number of the dependency types appearing in the corpus. The complexity of LDParser is a constant multiple of R2n2 according to the labeling strategies (one or two times labeling).Table 2: Parsing results on the English testing setParser UAS (%)LAS (%)RA (%)CM (%)Complexity Testing timeMaltParser MaltParser (split) Yamada03 (split) MSTParser1 MSTParser2 LDParser2 LDParser1LDP1div 89.6889.5289.5991.0391.7288.6089.1689.6888.4888.1988.7289.7890.4687.3487.9188.4384.7384.8185.1194.2194.4187.9688.7089.1633.6933.7734.1535.7239.5331.1332.6233.90O(n)O(n)O(n2)O(n3)O(n3)O(R2n2)O(R2n2)O(R2n2)2hour 46min10min 20sec20min 8sec6min 58sec9min 44sec1min 18sec2min 6sec1min 58secAmong the three proposed parsers, LDParser1 outperforms LDParser2 and LDP1div is the best one. Concerning the terms for parent-prediction accuracies and sentence complete matching, the LDParsers perform similarly to the transition-based models but exceed them more in root accuracy. Thanks to the global search over the whole dependency tree the graph-based models realized by MSTParser gain the best performance among the competitors on the English dataset. However, considering the parsing efficiency, the LDParsers are quite competitive. They havelower complexity than graph-based models and accordingly parse faster than them under the current implementations in projective case. Transition-based models can be implemented in linear time but SVMs which have been proved to achieve the highest performance in parser learning (Cheng et al., 2005; Wang et al., 2006) are not regarded as fast algorithms especially when the number of classes is large. The Classifier Splitting heuristic strategy and SVM speeding up methods (Goldberg and Elhadad, 2008) are gold choices to accelerate these implementations. However, even considering these cases, the parsing speed of the proposed LDParsers (up to 480 English words per second) is still desirable. Moreover, the speed boosting of SVMs is usually accompanied with the decrease of the accuracies or more memory consumption.3.2Chinese ResultsWe compared LDParser (LDP1div) with MaltParser, Yamada03, MSTParser and Duan07 in the Chinese experiments. Arc-standard algorithm (Nivre, 2004) is adopted in MaltParser because the experiments on the development set revealed that it got a higher performance than the arc-eager one. We also used the best Φ5 feature set in Hall et al. (2006) for Chinese and the setting of classifier splitting was kept the same as what it was for English. So were the feature model and splitting for Yamada03. All the settings for Chinese experiments of MSTParser were not changed from English ones except the 1-best parse set size. The results on the development set indicated that the k-best (k>1) models did not surpass the 1-best one remarkably.Only the features that appear more than once were utilized in LDP1div. Table 3 illustrates the parsing accuracies and speeds.Table 3: Parsing results on the Chinese testing set. The complexity of Duan07 is O(BKn2), where B is the beam size of beam-search algorithm and K is the number of action steps in PAPM (Duan et al., 2007) Parser UAS (%)LAS (%)RA (%)CM (%)Testing timeMaltParser (split) Yamada03 (split) MSTParser1 MSTParser2 Duan07LDP1div 83.8283.9183.3985.2384.3883.4482.1582.4481.7583.4782.9481.8973.5470.3870.7675.7071.2870.2932.5531.3226.3031.8132.1729.6622min 42sec27min10min 28sec15min 40sec9hour 57min1min 53secThe scores in Table 3 imply that LDParser is comparable to first-order MSTParser for Chinese parsing and a little weaker than transition-based approaches. The reason is that the transition-based models are more suitable for Chinese parsing than English because of the richer feature representations. This is also the reason why LDParser catches up with MSTParser on Chinese dataset. The optimal sub-graphs are delivered deterministically between the layers in LDParser which makes the parser be able to use the dependency graph pre-built. Duan07 which added global search to Yamada03 obtains further better performance.4Similar to the experiments for English,LDParser spends the shortest time. It parses Chinese sentences about 450 words per second. Moreover, the gaps between the speeds of LDParser and others’ consistently increase. For example, LDP1div is about 8 times faster than MSTParser2 and 15 times faster than split MaltParser while it was both 5 times faster in the English experiments. We think it is partially due to the character encoding mechanism in the Java implementation of MaltParser and MSTParser. Another reason is that the average sentence length of the Chinese testing set is 26.4 words, which is longer than that of English (23.5). Profiting from the layer-based search and sequence typed analysis, LDParser handles long 4The rank of the parsers under the metrics of parsing accuracies in Table 3 is not quite the same as what was in Duan et al. (2007). It is because the dependency structures of the data were differently converted in our experiments.sentences more efficiently. The global search of the transitions adopted in Duan07 makes the parser the most laggard one.3.3Additional ResultsTo further study the character of the layer-based parser, we present two additional results in this section. Table 4 illustrates the unlabeled attachment scores (UAS) of different dependency lengths in the English parsing experiment. The dependencies are calculated separately according to their length, equal to 1 (the neighboring relations), shorter than 3 or longer than 3. The threshold is chosen in terms of the average dependency length of the corpus which is 3.28.Table 4: Unlabeled attachment scores of different dependency lengths on the English datasetParser =1 ≤ 3 > 3MaltParser MSTParser2 LDP1div 94.2494.6794.5693.0993.5993.0773.9283.2374.53The moderate behavior of LDParser in neighboring attachment accuracy demonstrates that the globally optimal sequence labeling is competent for neighboring relation parsing compared with the tree-typed hierarchical ones. It even exceeds the transition-based parser. For the long dependencies, LDParser also does well than the transition-based one which verifies that the global search inside the parsing layer lightens the error propagation in transition-based models.By keeping partial parsing history through factoring over adjacent edge pairs of the dependency tree, the second-order MSTParser performs the best both for short and long dependencies. Making use of the pre-built structures, LDParser achieved a similar performance as MSTParser for short dependencies but gets worse for long ones. It is because LDParser is still a deterministic model in nature, the error propagation is unavoidable when the dependencies grow long. Another reason is that the higher layers are not modeled separately from each other in the current LDParser and it depresses the disambiguation ability of the model for higher layer parsing.We further examined the behaviors of the parsers on long sentences. 171 sentences with more than 40 words in the English testing set were tested and the results are listed in Table 5. The percentages represent the decrease of the speed when parsing the long sentences. Taking both the dependency accuracy and root accuracy into account, LDParser is almost the same as MaltParser. Although MSTParser is still the best, the parsing speed has dropped a lot (57%) when sentences grow long. Contrarily, there is only 8% slower for LDParser to parse these sentences which further implies that the layer-based approach is not sensitive to the length of the sentences and can be more efficient for long sentences than other parsers compared.Table 5: Results for sentences longer than 40 words. 8,019 words were analyzed in the experiment.Parser UAS RA Testing timeMaltParser (split) MSTParser2 LDP1div 87.3489.8486.5871.9294.7478.951min 45sec (17%)3min 11sec (57%)18sec (8%)4Related WorkActually, as a bottom-up framework the proposed approach is a little similar to the model proposed by Yamada and Matsumoto (2003) which employed a shift-reduce algorithm with multiple passes over the input. The transitions in this model are greedily selected at each parser state, i.e., configuration, from the left to the right during the parsing pass. To remove the greedy properties in the transition-based models, Johansson and Nugues (2007) and Duan et al. (2007) added a global search over the transition sequences. Our approach also uses multiple passes。
ISO 11992-4-2005
![ISO 11992-4-2005](https://img.taocdn.com/s3/m/62abc839bd64783e09122b1c.png)
ICS 43.040.15 Ref. No. ISO 11992-4:2005/Cor.1:2006(E)© ISO 2006 – All rights reservedPublished in SwitzerlandINTERNATIONAL STANDARD ISO 11992-4:2005TECHNICAL CORRIGENDUM 1Published 2006-05-15INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATIONRoad vehicles — Interchange of digital information on electrical connections between towing and towed vehicles —Part 4:DiagnosticsTECHNICAL CORRIGENDUM 1Véhicules routiers — Échange d'informations numériques sur les connexions électriques entre véhicules tracteurs et véhicules tractés —Partie 4: DiagnosticsRECTIFICATIF TECHNIQUE 1Technical Corrigendum 1 to ISO 11992-4:2005 was prepared by Technical Committee ISO/TC 22, Road vehicles , Subcommittee SC 3, Electrical and electronic equipment.ISO 11992-4:2005/Cor.1:2006(E)Page 6, subclause 5.4.3Replace Figure 3 with the following:Figure 3 — Client service state diagram — Service request with physical server target address2 ©ISO 2006 – All rights reservedISO 11992-4:2005/Cor.1:2006(E)Page 24, subclause 6.4.6Replace Figure 5 with the following:Figure 5 — A_PDU timing diagram confirmed services — physical target address©ISO 2005 – All rights reserved3ISO 11992-4:2005/Cor.1:2006(E)Page 25, subclause 6.4.6Replace Figure 6 with the following:Figure 6 — A-PDU timing diagram confirmed services — functional target address4 ©ISO 2006 – All rights reservedReference numberISO 11992-4:2005(E)© ISO 2005INTERNATIONALSTANDARD ISO 11992-4First edition2005-07-15Road vehicles — Interchange of digitalinformation on electrical connectionsbetween towing and towed vehicles —Part 4:DiagnosticsVéhicules routiers — Échange d'informations numériques sur lesconnexions électriques entre véhicules tracteurs et véhicules tractés —Partie 4: DiagnosticsISO 11992-4:2005(E)PDF disclaimerThis PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area.Adobe is a trademark of Adobe Systems Incorporated.Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.© ISO 2005All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.ISO copyright officeCase postale 56 • CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyright@Web Published in Switzerlandii © ISO 2005 – All rights reservedISO 11992-4:2005(E)Contents PageForeword (iv)Introduction (v)1Scope (1)2Normative references (1)3Terms and definitions (1)4Syntax applied (2)5Diagnostic application specification (2)5.1General (2)5.2Basic diagnostics (2)5.3Enhanced diagnostics (3)5.4Client and server state diagrams (3)6Application layer specification (7)6.1General (7)6.2Application layer functions (7)6.3Application layer services (10)6.4Application layer protocol (22)7Presentation layer specification (27)8Session layer specification (27)9Transport layer specification (27)10Network layer specification (27)10.1General (27)10.2Network layer functions (27)10.3Network layer services (30)10.4Network layer protocol (34)11Data link layer specification (42)11.1General (42)11.2Data link layer service parameter (42)12Physical layer specification (43)Annex A (normative) Addresses (44)Annex B (normative) Basic diagnostic service parameters (46)Annex C (informative) Trailer message routing example (65)Annex D (normative) CAN identifier and frame format (67)Bibliography (68)© ISO 2005 – All rights reserved iiiISO 11992-4:2005(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote.Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights.ISO 11992-4 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment.ISO 11992 consists of the following parts, under the general title Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles:⎯Part 1: Physical and data-link layers⎯Part 2: Application layer for brakes and running gear⎯Part 3: Application layer for equipment other than brakes and running gear⎯Part 4: Diagnosticsiv © ISO 2005 – All rights reservedISO 11992-4:2005(E)© ISO 2005 – All rights reserved vIntroductionISO 11992 has been established in order to define the data interchange between road vehicles and their towed vehicles using a Controller Area Network (CAN) serial data link as specified in ISO 11898[4].The description of this part of ISO 11992 is based on the Open Systems Interconnection (OSI) Basic Reference Model in accordance with ISO/IEC 7498[2] (and ISO/IEC 10731[3]), which structures communication systems into seven layers.When mapped on this model, the communication system specified by ISO 11992 is broken down into: Layer 7Application layer for brakes and running gear.Application layer for equipment other than brakes and running gear.Application layer for diagnostics.Layer 3Network layer for diagnostics.Layer 2Data link layer for all communication types.Layer 1Physical layer for all communication types.Table 1 — Applicability and relationship between International Standards Normal communication Diagnostic communication Applicability Brakes and running gearEquipment other than brakes and running gear All applications Layer 7: Application layer ISO 11992-2ISO 11992-3 ISO 11992-4 ISO 14229-1 Layer 6: Presentation layer No functions specified for this layer.Layer 5: Session layer No functions specified for this layer.Layer 4: Transport layer No functions specified for this layer.Layer 3: Network layer No functions specified for this layer.ISO 11992-4 ISO 15765-2 Layer 2: Data link layer ISO 11992-1Layer 1:Physical layerISO 11992-1INTERNATIONAL STANDARD ISO 11992-4:2005(E) Road vehicles — Interchange of digital information on electricalconnections between towing and towed vehicles —Part 4:Diagnostics1 ScopeThis part of ISO 11992 specifies the data communication for diagnostic purposes on a serial data link between a road vehicle and its towed vehicle(s).This part of ISO 11992 is applicable to road vehicles of a maximum authorized total mass greater than 3 500 kg.2 Normative referencesThe following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signallingISO 11992-1, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 1: Physical and data-link layersISO 11992-2, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 2: Application layer for brakes and running gearISO 11992-3, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 3: Application layer for equipment other than brakes and running gearISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements ISO 15765-2, Road vehicles — Diagnostics on Controller Area Networks (CAN) — Part 2: Network layer services3 Terms and definitionsFor the purposes of this document, the terms and definitions given in ISO 11992-1, ISO 14229-1 and ISO 15765-2 apply.© ISO 2005 – All rights reserved1ISO 11992-4:2005(E)4 Syntax appliedFor the description of services and service parameters of this part of ISO 11992, the following syntax is used: Name: Type Parameter name and type specificationName Mandatory parameter value<Name> Parameter name representing a set of mandatory parameter values [Name] Optional parameter value[<Name>] Parameter name representing a set of optional parameter values{Name 1;Name 2} List of mandatory parameter values{<Name 1>;<Name 2>} List of parameter names representing sets of mandatory parameter values [<Name 1>;<Name 2>] List of parameter names representing sets of optional parameter values{<Name 1>|<Name 2>} Parameter names selection list representing sets of mandatory parameter values[<Name 1>|<Name 2>] Parameter names selection list representing sets of optional parameter valuesName.req Service request primitiveName.ind Service indication primitiveName.rsp Service response primitiveName.rsp- Service negative response primitiveName.rsp+ Service positive response primitiveName.con Service confirmation primitiveName.con- Service negative confirmation primitiveName.con+ Service positive confirmation primitive5 Diagnostic application specification5.1 GeneralThe diagnostic applications are divided into basic diagnostic applications and enhanced diagnostic applications.Functions, services and protocols of the layers 1 to 4 shall be identical for basic diagnostics and enhanced diagnostics.5.2 Basic diagnosticsThe purpose of the basic diagnostics is to provide vehicle-independent identification and diagnostic information.All basic diagnostic functions and services shall be provided under all operation conditions in the default diagnostic session without the need for specific access rights.2 © ISO 2005 – All rights reservedISO 11992-4:2005(E)5.3 Enhanced diagnosticsThe support and the conditions under which enhanced diagnostic functions and services are provided are manufacturer-specific. It is the responsibility of the manufacturer to secure a server against unauthorized access and to guarantee performance and safe operation in all operation modes allowing enhanced diagnostics.5.4 Client and server state diagrams5.4.1 GeneralThe client and server state diagrams describe the diagnostic service processing of the client and server application entity.5.4.2 Client service primitives handlingThe client service primitives handling shall be as specified in Figure 1 and Figure 2.Client states while processing a diagnostic service shall be as specified in Table 2, events resulting in a client state change shall be as specified in Table 3.Figure 1 — Client service state diagram — Service request with physical server target address© ISO 2005 – All rights reserved3ISO 11992-4:2005(E)4© ISO 2005 – All rights reservedFigure 2 — Client service state diagram — Service request with functional server target addressTable 2 — Client state description Client state Description ASAny client state in which a service request can take place. WS Client state while waiting for a confirmation from the server.NCS a) Following a service request with a physical server target address:client state after the reception of a negative confirmation from the server.b) Following a service request with a functional server target address:client state if no positive service confirmation has been received.PCS Client state after the reception of a positive confirmation from a server.ESClient state for error handling, e.g. in case of a time out condition.ISO 11992-4:2005(E)© ISO 2005 – All rights reserved 5Table 3 — Client event description Client eventDescription Tas1.1Transmit <a.>.req The client transmits an <a> service request with a physical server target address. Tas1.2 Transmit <a.>.req The client transmits an <a> service request with a functional server target address.Tws1.1 Receive <a>.con- Following a service request with a physical server target address:the client receives a negative <a> service confirmation with the response code 'Request correctly received - response pending'.The client shall then reset the time outs and enter the WS state again.Tws1.2 Receive <a>.con+ Following a service request with a functional server target address:the client receives a positive <a> service confirmation. The client shall then process the positive service confirmation and enter the WSstate again.Tws2.1 Receive <a>.con- Following a service request with a physical server target address:the <a> service request has been rejected, a corresponding negative <a> service confirmation with a response code has been received.The client shall then change to the NCS state.Tws2.2 ACT1 expiredFollowing a service request with a functional server target address:the time ACT1 for the reception of the first service confirmation has expired andno positive service confirmation has been received.The client shall then change to the NCS state. Tws3.1 Receive <a>.con+ Following a service request with a physical server target address:the <a> service has been executed, a positive <a> service confirmation, i.e. the result of the service, has been received.The client shall then change to the PCS state.Tws3.2 ACT3.2 expired Following a service request with a functional server target address the time ACT3.2for the reception of consecutive service confirmations has expired and at least one positive service confirmation has been received.The client shall then change to the PCS state.Tes1 Error.ind An error condition, e.g. a time out condition, is signalled to the client.The client shall then change to the ES state for error handling.NOTE Negative service responses with a response code 1016, 1116 or 1216 shall not be sent by a server in case of a service request with a functional server target address.<a> Any diagnostic service.5.4.3 Server service primitives handlingThe server diagnostic service primitives handling shall be as specified in Figure 3.Server states while processing a diagnostic service shall be as specified in Table 4, events resulting in a server state change shall be as specified in Table 5.Table 4 — Server state descriptionServer stateDescription ASAny server state in which the reception of a service indication can take place. PSServer state while processing a service. PCSServer state after the diagnostic service has been executed. ES Server state error handling, e.g. after reaching a time out condition.ISO 11992-4:2005(E)Figure 3 — Server state diagram6 © ISO 2005 – All rights reservedISO 11992-4:2005(E)© ISO 2005 – All rights reserved 7Table 5 — Server event description Event Description Tas1Receive <a.>.ind The server receives any <a> service.indication. Tws1 AST1max expiredTransmit <a>.res- The service execution time AST1max has expired. the server shall then send a negative service response with the response code 'Request correctly received - response pending' and change back to the PS state to proceed the service execution.Tws2 Received <b>.indRespond <b>.res± The server receives a <b> service indication, while service <a> is in progress.the server shall reject the service <b> if service <b> ≠ service <a> and send a negative response with response code "Busy - Repeat Request". If service <b> =service <a>, the server shall send a negative service response with response code"Request Correctly Received - Response Pending".The server shall then enter again the PS state to proceed the service execution.Tws3.1 Service execution not completed Respond <a>.res- Following a service request with a physical server target address:the server rejects the service request.The server shall then send a negative <a> service response with a correspondingresponse code and change to the AS state.Tws3.2 Service execution not completed No response Following a service request with a functional server target address:the server rejects the service request.The server shall then send no response code and change to the AS state.Tws4 Service execution completed Respond <a>.res+ The server sends a positive <a> service response.the service has been executed.The server shall then transmit a positive <a> service response, i.e. the serviceresults, and shall change again to the PCS state.Tes1 Error.indAn error condition is indicated to the server, e.g. a time out condition.The server changes to the ES state for error handling. NOTE Negative service responses with a response code 1016, 1116 or 1216 shall not be sent by a server in case of a service request with a functional server target address.<a> Any first diagnostic service.<b> Any second diagnostic service.6 Application layer specification6.1 GeneralThe application layer function, service and protocol specifications comply with ISO 14229-1. In case of differences, the specifications of this part of ISO 11992 shall have precedence.For the diagnostic communication between road vehicles and their towed vehicles, the restrictions described in this clause apply additionally.6.2 Application layer functions6.2.1 GeneralThe application layer provides functions for the execution of the vehicle diagnostics. These functions are used by client and server applications requesting the respective application layer services.6.2.2 Processing of diagnostic services requests and responsesDiagnostic service requests from the client application and diagnostic service responses from the server application shall be processed according to the service identifier. The diagnostic data shall be encoded as an application layer protocol data unit (A_PDU). The A_PDU shall be transmitted to the respective application layer peer entity by requesting services of the layers beneath the application layer.ISO 11992-4:2005(E)6.2.3 Processing of diagnostic service indications and confirmationsDiagnostic data shall be received as an A_PDU from the layers beneath the application layer. If the received A_PDU is addressed to one of the local server or client application, the received A_PDU shall be decoded and processed according to the diagnostic service identifier and delivered to the server or client application as a service indication or confirmation.6.2.4 Determination of network layer service parametersNetwork layer service parameters are determined by the application layer service type, i.e. ClientIdentifier, ServerIdentifier, ServiceIdentifier and ServiceParameter. In addition the specified parameters Priority and ReservedBit shall be used.NOTE As no specific functions have been specified for the presentation, session and transport layer, the PDUs of these layers are identical to the respective application layer PDUs.6.2.5 Application layer protocol timing supervisionThe peer application layer entities communicating shall supervise the specified timing and shall take the respective actions in case a specified time out expires.6.2.6 Server and client addressing6.2.6.1 Vehicle network architectureTowed vehicle server and client applications shall be addressed and identified by means of remote network addressing. The physical sub-networks between towing and towed vehicles are part of the local motor vehicle network and share the same address range. The address type of the target address (TA) and of the remote address (RA) in the case of encoding a remote target address shall be identified by the target address type (TA_Type).Figure 4 shows an example of the vehicle network architecture.Figure 4 — Vehicle network architecture example8 © ISO 2005 – All rights reservedISO 11992-4:2005(E)6.2.6.2 Towing to towed vehicle <Service>.Request and <Service>.IndicationFor a diagnostic service request transmitted from a towing vehicle to a towed vehicle, the address parameters of the service primitives have the following meaning:SA = <Towing vehicle client source address>TA = <Towed vehicle target address>RA = <Towed vehicle remote server target address>TA_type = {<Physical target addresses>|<Functional target addresses>}See Annex A.NOTE TA_type identifies the TA and the RA target address type.6.2.6.3 Towed to towing vehicle <Service>.Response and <Service>.ConfirmationFor a diagnostic service response transmitted from a towed vehicle to a towing vehicle, the address parameters of the service primitives have the following meaning:SA = <Towed vehicle source address>TA = <Towing vehicle client target address>RA = <Towed vehicle remote server source address>TA_type = <Physical target addresses>NOTE TA_type identifies only the TA target address type.6.2.6.4 Towed to towing vehicle <Service>.Request and <Service>.IndicationFor a diagnostic service request transmitted from a towed vehicle to a towing vehicle, the address parameters of the service primitives have the following meaning:SA = <Towed vehicle source address>TA = <Towing vehicle server target address>RA = <Towed vehicle remote client source address>TA_type = {<Physical target addresses>|<Functional target addresses>}NOTE TA_type identifies only the TA target address type.© ISO 2005 – All rights reserved9ISO 11992-4:2005(E)6.2.6.5 Towing to towed vehicle <Service>.Response and <Service>.ConfirmationFor a diagnostic service response transmitted from a towing vehicle to a towed vehicle, the address parameters of the service primitives have the following meaning:SA = <Towing vehicle server source address>TA = <Towed vehicle target address>RA = <Towed vehicle remote client target address>TA_type = <Physical target addresses>NOTE TA_type identifies the TA and RA target address type.6.3 Application layer services6.3.1 GeneralThis subclause specifies the application layer services for diagnostics.6.3.2 Application layer service parameters6.3.2.1 GeneralThis subclause specifies the general application layer service parameter and the respective parameter format. Service specific parameters are specified in 6.3.4.6.3.2.2 Source address (SA)The parameter source address (SA) contains the client or server source address. It represents the physical location of a client or server on the local network.SA = {<Towing vehicle client source address>|<Towed vehicle source address>}6.3.2.3 Target address (TA)The parameter target address (TA) contains the client or server target address. It represents the physical location of a client or server or a functional group of servers on the local network. The target address type is determined by the parameter TA_type.TA = {<Towed vehicle target address>|<Towing vehicle client target address>|<Towing vehicle server target address>}6.3.2.4 Target address type (TA_type)The parameter target address type (TA_type) determines the address type of the target address TA and the remote address RA, in the case that the remote address corresponds to a target address.TA_type = {<Physical target addresses>|<Functional target addresses>}10 © ISO 2005 – All rights reserved6.3.2.5 Remote address (RA)The remote address (RA) contains the remote addresses of servers or clients on a remote network. Depending on the respective application layer primitive, RA represents either a remote target address or a remote source address.RA = {<Towed vehicle remote server target address>|<Towed vehicle remote server source address>|<Towed vehicle remote client source address>|<Towed vehicle remote client target address>}6.3.2.6 ServiceParameterServiceParameter is a record which contains the respective service parameters of the service primitive. ServiceParameter = {<<Service name> request service parameter>|<<Service name> positive response service parameter>|<<Service name> negative response service parameter>}<Service name> request service parameters are those following the <service name> request service identifier. <Service name> positive response service parameters are those following the <service name> positive response service identifier.<Service name> negative response service parameters are those following the negative response service identifier.6.3.3 Application layer service data units (A_SDU)The application layer service data units (A_SDU) of the diagnostic service primitives have the following formats:<Service name>.Request = {<SA>;<TA>;<TA_Type>;<RA>;<<Service name> request service identifier>;<<Service name> request service parameter>}<Service name>.Indication = < <Service name>.Request><Service name>.Response = {<SA>;<TA>;<TA_Type>;<RA>;<<Service name> response service identifier>;<<Service name> response service parameter>}<Service name>.Confirmation = <<Service name>.Response>© ISO 2005 – All rights reserved 11。
MODFLOW软件介绍及实例分析
![MODFLOW软件介绍及实例分析](https://img.taocdn.com/s3/m/91700259bceb19e8b9f6ba80.png)
❖ DIS for the Discretization File
❖ BAS6 for the Basic Package
❖ OC for the Output Control Option
❖ BCF6 for the Block-Centered Flow Package
❖ LPF for the Layer Property Flow package
hm i, j,k
)
CVi,
j,k 1/ 2
(hm i, j,k 1
hm i, j,k
)
Pi,
j,k
hm i, j,k
ECE 118
![ECE 118](https://img.taocdn.com/s3/m/2597a4126edb6f1aff001fa0.png)
E/ECE/324 )Rev.2/Add.117E/ECE/TRANS/505 )April 20, 2005STATUS OF UNITED NATIONS REGULATIONECE 118UNIFORM PROVISIONS CONCERNING THE:BURNING BEHAVIOUR OF MATERIALS USED IN THEINTERIOR CONSTRUCTION OF CERTAIN CATEGORIESOF MOTOR VEHICLESIncorporating:00 series of amendments Date of Entry into Force: 06.04.05E/ECE/324 )Rev.2/Add.117E/ECE/TRANS/505 )April 20, 2005UNITED NATIONSAGREEMENTCONCERNING THE ADOPTION OF UNIFORM TECHNICAL PRESCRIPTIONS FOR WHEELED VEHICLES, EQUIPMENT AND PARTS WHICH CAN BE FITTED AND/OR BE USED ON WHEELED VEHICLES AND THE CONDITIONS FOR RECIPROCAL RECOGNITION OF APPROVALS GRANTED ON THE BASIS OF THESE PRESCRIPTIONS (*) (Revision 2, including the amendments which entered into force on October 16, 1995)Addendum 117: Regulation No. 118Date of entry into force: April 6, 2005UNIFORM TECHNICAL PRESCRIPTIONS CONCERNING THE BURNINGBEHAVIOUR OF MATERIALS USED IN THE INTERIOR CONSTRUCTIONOF CERTAIN CATEGORIES OF MOTOR VEHICLES(*)Former title of the Agreement:Agreement Concerning the Adoption of Uniform Conditions of Approval and Reciprocal Recognition of Approval for Motor Vehicle Equipment and Parts, done at Geneva on March 20, 1958.REGULATION NO. 118UNIFORM TECHNICAL PRESCRIPTIONS CONCERNING THE BURNINGBEHAVIOUR OF MATERIALS USED IN THE INTERIOR CONSTRUCTIONOF CERTAIN CATEGORIES OF MOTOR VEHICLESCONTENTSREGULATION1. Scope2. Definitions3. Application for approval4. Approval− Definitions − Specifications5. PartIII− Definitions − Specifications6. Part7. Modification of the type and extension of approval8. Conformity of production9. Penalties for non-conformity of production10. Production definitely discontinued11. Names and addresses of technical services responsible for conducting approval tests, and ofadministrative departmentsANNEXESAnnex 1− Information document for vehicleAnnex 2 − Information document for componentAnnex 3− Communication concerning the approval of a vehicle typeAnnex 4− Communication concerning the approval of a component typeAnnex 5− Arrangements of approval marksAnnex 6− Test to determine the horizontal burning rate of materialsAnnex 7− Test to determine the melting behaviour of materialsAnnex 8− Test to determine the vertical burning rate of materialsREGULATION NO. 118UNIFORM TECHNICAL PRESCRIPTIONS CONCERNING THE BURNINGBEHAVIOUR OF MATERIALS USED IN THE INTERIOR CONSTRUCTIONOF CERTAIN CATEGORIES OF MOTOR VEHICLES1. SCOPE1.1.This Regulation applies to the burning behaviour (ignitibility, burning rate and meltingbehaviour) of interior materials used in vehicles of Categories M3, Classes II and III (1),carrying more than 22 passengers, not being designed for standing passengers and urbanuse (city buses).Type approvals are granted according to:I− Approval of a vehicle type with regard to the burning behaviour of the interior 1.2. Partcomponents used in the passenger compartment.− Approval of a component (materials, seats, curtains, separation walls, etc.) with 1.3. PartIIregard to its burning behaviour.2. DEFINITIONS: General2.1."Manufacturer" means the person or body who is responsible to the approval authority forall aspects of the type approval process and for ensuring conformity of production. It is notessential that the person or body is directly involved in all stages of the construction of thevehicle or component which is the subject of the approval process.compartment" means the space for occupants’ accommodation including bar, 2.2. "Passengerkitchen, toilet, etc.), bounded by:–roof,thethefloor,–walls,sidethe–thedoors,–– the outside glazing,– the rear compartment bulkhead, or the plane of the rear seat,support,back–– at the driver's side of the longitudinal vertical median plane of the vehicle, the vertical transversal plane through the driver's R-point as defined in Regulation No. 17.– at the opposite side of the longitudinal vertical median plane of the vehicle, the front bulkhead.(1)As defined in the Consolidated Resolution on the Construction of Vehicles (R.E.3), Annex 7 (document TRANS/WP.29/78/Rev.1/Amend.2).2.3. "Productionmaterials" means products, in the form of bulk materials (e.g. rolls of upholstery) or preformed components, supplied to a manufacturer for incorporation in avehicle type approved under this Regulation, or to a workshop for use in the business ofvehicle maintenance or repair.2.4. "Seat" means a structure which may or may not be integral with the vehicle structure,complete with trim, intended to seat one adult person. The term covers both an individualseat or part of a bench seat intended to seat one adult person.2.5. "Group of seats" means either a bench-type seat, or seats which are separate but side byside (i.e. with the foremost anchorages of one seat in line with or forward of the rearmostanchorages and in line with or behind the foremost anchorages of another seat) and whichaccommodate one or more seated adult persons.seat" means a structure complete with trim, intended to seat more than one adult 2.6. "Benchperson.3. APPLICATION FOR APPROVAL3.1.The application for approval of a vehicle or component type with regard to this Regulationshall be submitted by the manufacturer.3.2.It shall be accompanied by an information document conforming to the model shown inAnnex 1 or in Annex 2.3.3.The following must be submitted to the technical service responsible for conducting the typeapproval tests:3.3.1.In the case of approval of a vehicle: a vehicle representative of the type to be approved.3.3.2.In the case of interior components already type approved: a list of the type approvalnumbers and maker's type designations of the parts concerned, shall be enclosed in theapplication for the vehicle type approval;3.3.3.In the case of interior components without ECE type approval:3.3.3.1. Samples, the number of which is specified in Annexes 6 to 8, of the components used in thevehicles, which are representative of the type to be approved;3.3.3.2. Furthermore, one sample shall be submitted to the technical service for future referencepurposes;3.3.3.3. For devices such as seats, curtains, separation walls, etc., the samples specified inParagraph 3.3.3.1. plus one complete device as mentioned above.3.3.3.4. The samples shall be clearly and indelibly marked with the applicant's trade name or markand the type designation;4. APPROVAL4.1.If the type submitted for approval to this Regulation meets the requirements of the relevantpart(s) of this Regulation, approval of that type shall be granted.4.2.An approval number shall be assigned to each type approved. Its first two digits (atpresent 00, corresponding to the Regulation in its original form) shall indicate the series ofamendments incorporating the most recent major technical amendments made to theRegulation at the time of issue of the approval. The same Contracting Party shall not assignthe same number to another type of vehicle or component as defined in this Regulation.4.3.Notice of approval or of extension of approval of a type pursuant to this Regulation shall becommunicated to the Contracting Parties to the Agreement applying this Regulation, bymeans of one of the forms conforming to the models in Annexes 3 or 4, as appropriate, tothis Regulation.4.4.There shall be affixed, conspicuously and in a readily accessible location specified on theapproval form, to every vehicle conforming to a type approved under this Regulation, to thepackaging of every material (see Paragraph 4.4.2.3.) conforming to a type approved underthis Regulation and to every component supplied separately conforming to a type approvedunder this Regulation, an international approval mark consisting of:4.4.1. A circle surrounding the Letter "E" followed by the distinguishing number of the countrywhich has granted component type approval (1),4.4.2.In the vicinity of the circle:4.4.2.1. Symbols indicating the direction for which the burning rate of the component has beendetermined:↔For the horizontal direction (Annex 6),↑For the vertical direction (Annex 8),↓For the horizontal and vertical directions(Annexes 6 and 8);4.4.2.2. The Symbol "V" indicating that the component has been approved according to its meltingbehaviour (Annex 7) and/or the Symbol "CD" indicating that the component has beenapproved as a complete device, such as seats, separation walls, luggage racks, etc.4.4.2.3. Production materials do not need to be individually marked. However, the packaging withwhich they are supplied must be clearly marked with the approval mark described above. 4.4.2.4. If separately marked, large components, for example seats, comprising of more than onepiece of approved material, may have a single mark indicating the approval number(s) of thematerial(s) used.(1)1 for Germany,2 for France,3 for Italy,4 for the Netherlands,5 for Sweden,6 for Belgium,7 for Hungary,8 for the CzechRepublic, 9 for Spain, 10 for Serbia and Montenegro, 11 for the United Kingdom, 12 for Austria, 13 for Luxembourg, 14 for Switzerland, 15 (vacant), 16 for Norway, 17 for Finland, 18 for Denmark, 19 for Romania, 20 for Poland, 21 for Portugal,22 for the Russian Federation, 23 for Greece, 24 for Ireland, 25 for Croatia, 26 for Slovenia, 27 for Slovakia, 28 for Belarus,29 for Estonia, 30 (vacant), 31 for Bosnia and Herzegovina, 32 for Latvia, 33 (vacant), 34 for Bulgaria, 35 (vacant), 36 forLithuania, 37 for Turkey, 38 (vacant), 39 for Azerbaijan, 40 for The former Yugoslav Republic of Macedonia, 41 (vacant),42 for the European Community (Approvals are granted by its Member States using their respective ECE symbol), 43 forJapan, 44 (vacant), 45 for Australia, 46 for Ukraine, 47 for South Africa, 48 for New Zealand, 49 for Cyprus, 50 for Malta and51 for the Republic of Korea. Subsequent numbers shall be assigned to other countries in the chronological order in whichthey ratify or accede to the Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles, Equipment and Parts which can be Fitted and/or be Used on Wheeled Vehicles and the Conditions for Reciprocal Recognition of Approvals Granted on the Basis of these Prescriptions, and the numbers thus assigned shall be communicated by the Secretary-General of the United Nations to the Contracting Parties to the Agreement.4.4.3.If a type conforms to a type approved, under one or more other Regulations annexed to theAgreement, in the country which has granted approval under this Regulation, the symbolprescribed in Paragraph 4.4.1. need not be repeated; in such a case, the Regulation underwhich approval has been granted in the country which has granted approval under thisRegulation shall be placed in vertical columns to the right of the symbol prescribed inParagraph 4.4.1.4.4.4.The approval mark shall be clearly legible and be indelible.4.4.5.In the case of a vehicle, the approval mark shall be placed close to or on the vehicle dataplate affixed by the manufacturer.4.4.6.Annex 5 to this Regulation gives examples of arrangements of approval marks.5. PART I: APPROVAL OF A VEHICLE TYPE WITH REGARD TO THE BURNINGBEHAVIOUR OF THE INTERIOR COMPONENTS USED IN THE PASSENGERCOMPARTMENT5.1. DefinitionFor the purpose of Part I of this Regulation,5.1.1."Vehicle type" means vehicles that do not differ in such essential respects as themanufacturer's type designation.5.2. Specifications5.2.1.The interior materials of the passenger compartment used in the vehicle to be typeapproved shall meet the requirements of Part II of this Regulation.5.2.2.The materials and/or equipment used in the passenger compartment and/or in devicesapproved as components shall be so installed as to minimize the risk of flame developmentand flame propagation.5.2.3.Such interior materials and/or equipment shall only be installed in accordance with theirintended purposes and the test(s) which they have undergone (see Paragraphs 6.2.1.,6.2.2. and 6.2.3.), especially in relation to their burning and melting behaviour(horizontal/vertical direction).5.2.4.Any adhesive agent used to affix the interior material to its supporting structure shall not, asfar as possible, exacerbate the burning behaviour of the material.6. PART II: APPROVAL OF A COMPONENT WITH REGARD TO ITS BURNINGBEHAVIOUR6.1. DefinitionsFor the purpose of Part II of this Regulation,6.1.1."Type of a component" means components which do not differ in such essential respectsas:6.1.1.1. The manufacturer's type designation,6.1.1.2. The intended use (seat upholstery, roof lining, etc.),6.1.1.3. The base material(s) (e. g. wool, plastic, rubber, blended materials),6.1.1.4. The number of layers in the case of composite materials, and6.1.1.5. Other characteristics in so far as they have an appreciable effect on the performanceprescribed in this Regulation.6.1.2."Burning rate" means the quotient of the burnt distance measured according to Annex 6and/or Annex 8 to this Regulation and the time taken to burn this distance. It is expressedin millimetres per minute.6.1.3."Composite material" means a material composed of several layers of similar or differentmaterials intimately held together at their surfaces by cementing, bonding, cladding,welding, etc. When different materials are connected together intermittently (for example,by sewing, high-frequency welding, riveting), such materials shall not be considered ascomposite materials.6.1.4."Exposed face" means the side of a material which is facing towards the passengercompartment when the material is mounted in the vehicle.6.1.5."Upholstery" means the combination of interior padding and surface finish material whichtogether constitute the cushioning of the seat frame.6.1.6."Interior lining(s)" means material(s) that (together) constitute(s) the surface finish andsubstrate of a roof, wall or floor.6.2. Specifications6.2.1.The following materials shall undergo the test described in Annex 6 to this Regulation:(a) Material(s) used for the upholstery of any seat and its accessories (including thedriver's seat),(b) Material(s) used for the interior lining of the roof,(c) Material(s) used for the interior lining of the side and rear walls, including separationwalls,(d) Material(s) with thermal and/or acoustic function,(e) Material(s) used for the interior lining of the floor,(f) Material(s) used for the interior lining of luggage-racks, heating and ventilation pipes,(g) Material(s) used for the light fittingsThe result of the test shall be considered satisfactory if, taking the worst test results intoaccount, the horizontal burning rate is not more than 100 mm/minute or if the flameextinguishes before reaching the last measuring point.6.2.2.The following materials shall undergo the test described in Annex 7 to this Regulation:(a) Material(s) used for the interior lining of the roof,(b) Material(s) used for the interior lining of the luggage-racks, heating and ventilationpipes situated in the roof,(c) Material(s) used for the lights situated in the luggage-racks and/or roof.The result of the test shall be considered satisfactory if, taking the worst test results intoaccount, no drop is formed which ignites the cotton wool.6.2.3.The materials used for the curtains and blinds (and/or other hanging materials) shallundergo the test described in Annex 8.The result of the test shall be considered satisfactory if, taking the worst test results intoaccount, the vertical burning rate is not more than 100 mm/minute.6.2.4.Materials which are not required to undergo the tests described in Annexes 6 to 8 are:6.2.4.1. Parts made of metal or glass;6.2.4.2. Each individual seat accessory with a mass of non-metallic material less than 200 g. If thetotal mass of these accessories exceeds 400 g of non-metallic material per seat, then eachmaterial must be tested;6.2.4.3. Elements of which the surface area or the volume does not exceed respectively:cm2 or 40 cm3 for the elements which are connected to an individual seating place;6.2.4.3.1. 100cm2 or 120 cm3 per seat row and, at a maximum, per linear metre of the interior of the 6.2.4.3.2. 300passenger compartment for these elements which are distributed in the vehicle and whichare not connected to an individual seating place;6.2.4.4. Electriccables;6.2.4.5. Elements for which it is not possible to extract a sample in the prescribed dimensions asspecified in Paragraph 3.1. of Annex 6, Paragraph 3. of Annex 7, and Paragraph 3.1. ofAnnex 87. MODIFICATION OF THE TYPE AND EXTENSION OF APPROVAL7.1.Every modification of a vehicle or component type with regard to this Regulation shall benotified to the administrative department which approved the vehicle or the component type.The department may then either:7.1.1.Consider that the modifications made are unlikely to have an appreciable adverse effect andthat in any case vehicles or components still comply with the requirements, or7.1.2.Require a further test report from the technical service responsible for conducting the tests.7.2.Confirmation or refusal of approval, specifying the alterations shall be communicated by theprocedure specified in Paragraph 4.3. above to the Contracting Parties to the Agreementapplying this Regulation.7.3.The competent authority issuing the extension of approval shall assign a serial number toeach communication form drawn up for such an extension and inform thereof the otherParties to the 1958 Agreement applying this Regulation by means of a communication formconforming to the model in Annex 3 or Annex 4 to this Regulation.8. CONFORMITY OF PRODUCTIONThe conformity of production procedures shall comply with those set out in the Agreement,Appendix 2 (E/ECE/324-E/ECE/TRANS/505/Rev.2), with the following requirements:8.1.Vehicles/components approved under this Regulation shall be so manufactured as toconform to the type approved by meeting the requirements of the relevant part(s) of thisRegulation.8.2.The authority that has granted type approval may at any time verify the conformity controlmethods applied in each production facility. The normal frequency of these verificationsshall be one every two years.9. PENALTIES FOR NON-CONFORMITY OF PRODUCTION9.1.The approval granted in respect of a vehicle/component type pursuant to this Regulationmay be withdrawn if the requirements set forth above are not met.9.2.If a Contracting Party to the Agreement applying this Regulation withdraws an approval ithas previously granted, it shall forthwith so notify the other Contracting Parties applying thisRegulation by means of a communication form conforming to the models in Annex 3 orAnnex 4 to this Regulation.10. PRODUCTION DEFINITELY DISCONTINUEDIf the holder of the approval completely ceases to manufacture a vehicle type approved inaccordance with this Regulation, he shall so inform the authority which granted theapproval. Upon receiving the relevant communication that authority shall inform thereof theother Parties to the 1958 Agreement applying this Regulation by means of a communicationform conforming to the model in Annex 3 or Annex 4 to this Regulation.11. NAMES AND ADDRESSES OF TECHNICAL SERVICES RESPONSIBLE FORCONDUCTING APPROVAL TESTS AND OF ADMINISTRATIVE DEPARTMENTSThe Parties to the 1958 Agreement applying this Regulation shall communicate to theUnited Nations Secretariat the names and addresses of the technical services responsiblefor conducting approval tests and of the administrative departments which grant approvaland to which forms certifying approval or extension or refusal or withdrawal of approval,issued in other countries, are to be sent.ANNEX 1INFORMATION DOCUMENT(in accordance with Paragraph 3.2. of this Regulation relating to theECE Type Approval of a vehicle with regard to the burning behaviourof the interior components used in the passenger compartment)If the systems, components or separate technical units have electronic controls, information concerning their performance must be supplied1. GENERALnameof manufacturer): ...........................................................................................(trade1.1. Make1.2. Type and general commercial description(s): .............................................................................1.3. Means of identification of type, if marked on the vehicle: ............................................................that marking: .............................................................................................................of1.4. Location1.5. Category of vehicle: (1) .................................................................................................................1.6. Name and address of manufacturer: ...........................................................................................assembly plant(s): ...............................................................................................of1.7. Address(es)2. GENERAL CONSTRUCTION CHARACTERISTICS OF THE VEHICLEof a representative vehicle:drawings2.1. Photographsand/or3. BODYWORKInteriorfittings3.1. Seats3.1.1. Number: .......................................................................................................................................3.2. Burning behaviour of materials used in the interior construction of the vehicle3.2.1. Material(s) used for the interior lining of the rooftype-approval number(s): .........................................................................................3.2.1.1. Component3.2.2. Material(s) used for the rear and side wallstype-approval number(s): .........................................................................................3.2.2.1. Component(1)As defined in the Consolidated Resolution on the Constuction of Vehicles (R.E.3.), Annex 7 (document TRANS/WP.29/78/Rev.1/Amend.2).3.2.3. Material(s) used for the floortype-approval number(s): .........................................................................................3.2.3.1. Component3.2.4. Material(s) used for the upholstery of the seatstype-approval number(s): .........................................................................................3.2.4.1. Component3.2.5. Material(s) used for heating and ventilation pipestype-approval number(s): .........................................................................................3.2.5.1. Component3.2.6. Material(s) used for luggage rackstype-approval number(s): .........................................................................................3.2.6.1. Component3.2.7. Material(s) used for other purposes3.2.7.1. Intended purposes: ......................................................................................................................type-approval number(s): .........................................................................................3.2.7.2. Component3.2.8. Components approved as complete devices (seats, separation walls, luggage racks, etc.)type-approval number(s): .........................................................................................3.2.8.1. ComponentANNEX 2INFORMATION DOCUMENT(in accordance with Paragraph 3.2. of the Regulation relating tothe ECE Type approval of a component with regard to its burning behaviour)If the systems, components or separate technical units have electronic controls, information concerning their performance must be supplied1. GENERAL1.1. Makenameof manufacturer): .............................................................................................(trade1.2. Type and general commercial description(s): ................................................................................1.3. Name and address of manufacturer: .............................................................................................1.4. In the case of components and separate technical units, location and method of affixing of theEEC approval mark: .......................................................................................................................1.5. Address(es)assembly plant(s): .................................................................................................ofMATERIALS2. INTERIOR2.1. Material(s) used for: .......................................................................................................................material(s)/designation: . . . / . . . ..........................................................................................2.2. Base2.3. Composite/single (1) material, number of layers (1): ......................................................................2.4. Type of coating (1): ........................................................................................................................2.5. Maximum/minimum thickness ................................................................................................. mm 2.6. Type-approvalnumber, if available: ...............................................................................................(1)Delete where not applicable.ANNEX 3(Maximum format: A4 (210 mm x 297 mm))COMMUNICATION(Maximum format: A4 (210 x 297 mm))(1)issued by: Name of administration:.......................................................................................................................................GRANTEDconcerning (2) APPROVALEXTENDEDAPPROVALREFUSEDAPPROVALWITHDRAWNAPPROVALPRODUCTION DEFINITELY DISCONTINUEDof a vehicle type pursuant to Regulation No. 118Approval No.............................................. Extension No................................................... Reason for extension:SECTION IGENERALof manufacturer): .............................................................................................name1.1. Make(trade..............................................................................................................................................1.2. Type:1.3. Means of identification of type, if marked on the vehicle/component/separate technicalunit (2)(3): .........................................................................................................................................1.3.1. Locationthat marking: ................................................................................................................of1.4. Category of vehicle (4): ....................................................................................................................(1)Distinguishing number of the country which has granted/extended/refused/withdrawn approval (see approval provisions in the Regulation).(2)Strike out what does not apply (there are cases where nothing needs to be deleted, when more than one entry is applicable).(3)If the means of identification of type contains characters not relevant to describe the vehicle, component or separate technical unit types covered in this information document, such characters shall be represented in the documentation by the symbol "?" (e.g. ABC??123??).(4)As defined in Annex 7 to the Consolidated Resolution on the Construction of Vehicles (R.E.3) (document TRANS/WP.29/78/Rev.1/Amend.2, as amended).。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
The Application of SiN x Layers to Multicrystalline Buried Contact Silicon Solar Cells Shin Hey Won, Sang Wook Park, Jeong Kim and S.H.LeeNational Research Laboratory for Si Photovoltaics, Corporate R&D Center, SAMSUNG SDI Co. Ltd.,P.O.Box111, Suwon, Korea, 440-600AbstractConventional multicrystalline buried contact solar cells (BCSC) need thick SiO2 films which are used as barrier layers for the diffusion and metallization. However, the high temperature process for preparing SiO2 layers causes many difficulties during the production of the multicrystalline BCSC.In this work, silicon nitride (SiN x) films were deposited by plasma enhanced chemical vapor deposition (PECVD) method to replace SiO2 as SiN xin BCSC process. For low thermal budget of SiN x, fabrication process was modified and the results were compared with conventional BCSC.1. IntroductionSilicon nitride (SiN x) films not only act as an antireflection coating layer with a suitable refractive index, but can also improve the performance of photovoltaic devices by defect, surface and bulk passivation. For these reasons, recent studies have shown that the application of PECVD SiN x thin films can be very helpful in improving the efficiency of the multicrystalline silicon solar cells.PECVD SiN x layer is used as barrier layers for the diffusion and metallization of BCSC process. The SiN x layer played an important role as an antireflecting layer and passivating layer. Consequently, we obtained effective lifetime about two times as high as the SiO2 films due to the passivation effect of surface and bulk for solar cell. Therefore we expect that the J sc and the V oc will increase due to the decreasing of the reflectance by the SiN x films and efficiency of the solar cell will be increased.2. Experimental procedureFor the formation of the hydrogen-rich SiN x films, ammonia (NH3), silane (5 % SiH4 in N2) and nitrogen gases were used as source materials. The deposition temperature and the rf power were 300 o C and 60 W, respectively. The refractive index and the extinction coefficient of the SiN x, as measured by spectroscopic ellipsometer, were used as input for the ray-tracing program Sunrays and the thickness of SiN x was optimized. In addition, it is known that the annealing after deposition SiN x films is effective to improve the minority carrier lifetime of mc-Si wafer. In order to increase passivation effect, as-grown SiN x films were post-annealed at 4000C for 30min in forming gas ambient.3. Results and discussion3.1 SiN x layer as a passivation and antireflectionlayerEffective carrier lifetime of multi-Si was measured by microwave photoconductive decay (µW-PCD) to verify the passivation effect before and after annealing.Table 1. Effective carrier lifetimes before and after SiN x deposition.Process AfteremitterAfterSiN xAfterannealing Lifetime 22µs 44µs 65µsTable 2. Comparison of effective carrier lifetimes of the wafer coated with SiO2 and SiN x, respectively on the emitter.Passivation SiO2 layer SiN x layer Carrier lifetime 35µs 65µsWe found that the effective lifetime of mc-Si greatly increased after annealing the introducing SiN x film. It seems that atomic hydrogen in SiN x diffused into the bulk silicon and passivated mc-Si during annealing process and the effective lifetime is higher than that of mc-Si coated with SiO2 films. The surface reflectance of mc-Si with SiN x layer could be remarkably lowered as shown in Fig.1. The refractive index of SiN x film was measured to be 2.01 at 632.6 nm. It is shown that the reflectance of the textured mc-Si wafer with SiN x films is extremely low. It is expected that the SiN x improve the performance of BCSC by increasing V oc and J sc of the cell.3.2 Application of SiNx to BCSC process Multicrystalline –BAYSIX cast silicon wafers were used for fabrication of BCSC cells. The wafers received saw damage etching in isotropic etching solution. The emitter was formed using phosphorous solid source. SiN x films were deposited on theemitter to serve as a diffusion barrier for heavy diffusion and as barrier layer for metallization. The solar cell fabrication process was summarized in Table 3.Figure 1. Reflectances of mc-Si coated with SiN x and SiO2. Texturing of mc-Si wafer was carried out in KOH solution.Table 3. Fabrication process of BCSC cells.1. Saw damage etching2. Phosphorus gettering3. Front junction formation (n+ layer)4. SiNx deposition by PECVD5. Groove formation]6. Groove diffusion (n++ layer)7. Al deposition and sintering8. Metallization (Ni, Cu plating)The output performance of BCSC cell with SiN x is shown Fig. 3. The conversion efficiency of cell was 6.14 % in spite of the improvement of the effective lifetime after the deposition of SiN x films. It is likely that the high temperature processes, heavy diffusion (940 o C) and aluminum sintering (980 o C) degraded the passivation effects of SiN x film. Therefore, we found that the high temperature process should be avoided after depositon of deposition of SiN x film to utilize the advantage of hydrogen passivation effects of SiN x films. Two fabrication processes were tried to use SiN x films effectively. One is to adapt RTP (rapid thermal process) for groove diffusion and aluminum sintering. The other one is to introduce SiN xfilms after all high temperature process. The first one is under study using spin on source and RTA machine in our group. The second one was tried using process sequence similar to that of PESC (Passivated Emitter Solar Cell).By using SiNx films after diffusion and aluminum sintering process, V oc of the cells with PESC structure increased up to 612 mV giving effciency of 15.44 % as shown in Table 3. Therefore it is expected that the efficiency of multi-Si BCSC will be enhanced up to 15 %. Figure 2. The result of the buried contact multicrystalline silicon solar cell fabricated using SiN x films instead of the SiO2 films.Table 3. Output performance of PESC cell fabricated using SiN x film after high temperature process ( AM1.5, 100mW/cm2, 45 cm2 cell area ).ParameterV oc(mV)Jsc(mA/cm2)FF(%)Eff(%) PESC 612 31.8 79.27 15.444. ConclusionThe purpose of this paper is that the fabrication of the buried contact silicon solar cell is applied to the SiN x layer as barrier layers for the diffusion and metallization instead of SiO2 layer and as an antireflection layer. High temperature processes degraded passivation effects of SiN x films. Introduction of SiN x film to after high temperature process gave high V oc resulting in high efficiency of 15.44 %. It is expected that BCSC cell with the efficiency of over 15 will be obtained if the high temperature process is replaced with RTP process or fabrication process is optimized by introducing SiN x after high temperature process.AcknowledgementThis work was supported by the Korean Ministry of Commerce, Industry, and Energy.References[1] Zhizhang Chen, Peyman Sana, CIEEE Transactions on electron devices, V ol. 40, No. 6, Jane (1993)[2] Li Cai, Student Member and Ajeet Rohatgi, IEEE Transactions on electron devices, V ol. 44, No. 1, January(1997)[3] F. Duerinckx, J. Szlufcik, 2nd World conference and exhibition on photovoltaic solar energy conversion 6-10 July(1998)[4] Den Coates, Scott Morrison, 16th European Photovoltaic Solar Energy Conference, 1-5 May(2000)。