chap2-3-lex-re

合集下载

SAF7741_Datasheet_N1F_V5

Signals received from the tuner front-end chips are digitized with integrated IntermediateFrequency Analog-to-Digital Converters (IFADCs). The resulting digital signals are then down-sampled, error-corrected and filtered in the digital domain to be suitable for further radio and audio processing by the DSPs.
SAF7741HV
Dual IF car radio and audio DSP (N1F)
Rev. 05 — 09 May 2008
Байду номын сангаас
Objective data sheet
1. General description
The SAF7741HV is a combined Intermediate-Frequency (IF) car radio and audio Digital Signal Processor (DSP) with several powerful cores integrated onto a single device. It combines analog IF input, digital radio and audio processing, sample-rate converters and digital and analog audio output to enhance listening clarity and noise suppression while reducing multipath channel effect.

【cisco】architecture wifi offload

White PaperArchitecture for Mobile Data Offload over Wi-Fi Access NetworksIntroductionMobile network traffic is growing exponentially, and service providers must manage their networks efficiently to meet consumer demand. The technology evolution of radio access networks is limited by the laws of physics, and significant growth in radio frequency (RF) efficiency can no longer be expected. Long-Term Evolution (LTE) radio access is reaching the limits of Shannon’s law, the spectrum available for mobile data applications is limited, and the only solution for increasing overall mobile network capacity is to increase the carrier-to-interference ratio while decreasing cell size and deploying small cell technologies. The most efficient way to use small cells is to position them in locations where significant amounts of data are generated (shopping malls, stadiums, university campuses, public transportation hubs, etc.) and where subscribers spend most of their time and therefore consume significant amounts of data (homes, offices, etc.). Wi-Fi, one of the small cell technologies, appeals to many operators as a cost-effective mean of offloading large amounts of mobile data traffic while delivering a variety of new services. It offers these features:● ● ● ●Widespread existing deployments Availability of user devices that support the technology Cost efficiency Capability to address new users and devices without mobile subscription (without a subscriber identity module [SIM])● ●Globally available spectrum capacity Standards availability for integration into mobile core networksThis document explores technical aspects of Wi-Fi offload architecture and its capabilities and integration into existing mobile networks to provide a viable and efficient way to offload subscriber traffic.Overview of Wi-Fi Offload ArchitectureThe Third-Generation Partnership Project (3GPP) standard differentiates two types of Wi-Fi access (also referred to as non-3GPP IP access):●Untrusted: Introduced in the early stages of the Wi-Fi specification in 3GPP Release 6 (2005), untrusted access includes any type of Wi-Fi access that either is not under control of the operator (public open hotspot, subscriber’s home WLAN, etc.) or that does not provide sufficient security (authentication, encryption, etc.).●Trusted: Trusted access generally refers to operator-built Wi-Fi access with over-the-air encryption and a secure authentication method. Trusted non-3GPP IP access was introduced only with the LTE standard in 3GPP Release 8 (2008). Although most of today’s offload designs are build on the trusted model, 3GPP does not currently offer guidance for integration with the 3G or 2G packet core. However, as discussed in this document, this type of access is natively integrated into LTE’s evolved packet core (EPC).© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 1 of 23Because most of today’s mobile networks are 3G based, a significant part of this document describes the possible methods of integrated trusted non-3GPP IP access into the 3G mobile packet core (MPC) together with its associated policy and charging control (PCC) architecture. Although the term “trusted non-3GPP IP access” is defined for EPC only, this document extends its definition in 3G contexts to describe Wi-Fi networks controlled by mobile operators. 3GPP 24.302 has the following definition: “For a trusted non-3GPP IP access network, the communication between the user equipment and the EPC is secure.” Thus, with the latest service provider Wi-Fi architectures encompassing Extensible Authentication Protocol (EAP) and IEEE 802.1X-based authentication, and with IEEE 802.11i-based RF encryption and optional use of control and provisioning of wireless access points and Datagram Transport Layer Security (DTLS) for secured user and control planes, all the elements exist for service provider Wi-Fi to be considered as trusted non-3GPP. After the 3G designs, this document describes the evolution of the architectures toward EPC integration as specified in 3GPP standards. Session mobility and, more generally, IP address persistence when moving between 3G, LTE, and Wi-Fi are also covered. The document also discusses the integration models for untrusted networks, although these are less commonly deployed in mobile networks. In the 3GPP specification, the Wi-Fi network is referred to as the Wi-Fi access network only. No details about the Wi-Fi network structure are specified. This document, however, separates the network into the access and gateway components. The Wi-Fi network infrastructure for mobile data offload consists of three parts:● ●Wi-Fi radio access network (Wi-Fi RAN) Wi-Fi access gateway (WAG) and Wi-Fi back-end systems (this document expands the definition from 3GPP TS 23.234 to refer also to non-3GPP WAG)●Packet core integration elements (multiple options)© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 2 of 23Figure 1 illustrates the architecture. It includes integration elements for 3G as well as LTE to show a summary of all designs built throughout this document.Figure 1. Wi-Fi Network ArchitectureIf the Wi-Fi network is used for mobile data offload, which is the topic of this document, it needs to take care of these tasks:● ●Authentication: To help ensure that only authorized subscribers can access the network PCC: For proper billing, quality of service (QoS), and policy enforcement for the traffic generated through Wi-Fi access, ideally compliant with 3GPP PCC●IP persistence: For service mobility between different access networks (3G to Wi-Fi, Wi-Fi to 3G, or across the Wi-Fi network)The following sections examine the details of each of these functions.AuthenticationTo control subscriber access to Wi-Fi networks, multiple authentication methods can be used. The choice of method is crucial to the usability of the network. The more transparent the authentication method is for the subscriber, the greater the likelihood that the subscriber will connect to the network. The authentication method also determines the subscriber and device types that can be addressed in a particular network (subscribers with or without SIM cards, the operator’s subscribers, visiting subscribers, etc.). In a typical modern Wi-Fi network, two types of authentication are available to address all possible subscribers and at the same time provide convenient access to the network for frequent Wi-Fi users. The first method, portalbased authentication, targets customers without a permanent contract with the operator (vouchers, time-limited© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 3 of 23access, SMS payments, etc.). Alternatively, EAP authentication provides transparent and easy access for the operator’s own subscribers with SIM cards or certificates.Portal-Based AuthenticationPortal-based authentication depends on Layer 3 connectivity to the network and HTTP communication before granting access to the subscriber. The Wireless Internet Service Provider Roaming (WISPr) standard also uses HTTP communication with the portal for automatic authentication, with the user device launching HTTP communication in the background without user intervention (Figure 2).Figure 2. Portal-Based Authentication ArchitectureThis method relies on the WAG in the Wi-Fi network, which blocks all IP communication for unknown (new) subscribers and redirects HTTP connections to a captive portal. The captive portal is responsible for requesting user credentials from the subscriber and triggering authentication, authorization, and accounting (AAA) to authenticate the subscriber. After successful login, the WAG will typically be signaled by the AAA server. From this moment, the subscriber is known in the AAA cache, and WAG allows the subscriber to send and receive data. Usually, the user’s IEEE 802.11 MAC address is also cached in the AAA server, together with the user data and granted service. If the subscriber leaves the Wi-Fi coverage area and then returns, the subscriber’s device will be recognized by the WAG based on the MAC address and automatically authenticated against the cached AAA record, so the subscriber is not repeatedly redirected to the portal after losing Wi-Fi coverage. This method of MAC address caching is also referred to as transparent automatic logon (TAL).© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 4 of 23A typical TAL attachment call flow is shown in Figure 3 for the case of a Layer 2 attached WAG.Figure 3. Typical Transparent Automatic Logon Call FlowEAP-Based AuthenticationEAP-based authentication uses EAP and IEEE 802.1x to provide Layer 2 authentication for subscribers accessing the network with EAP-capable devices. For actual authentication, multiple credentials can be used, depending on the capability of the device. Devices with SIM cards encapsulate the SIM application information exchange into the EAP message, and these are proxied by the AAA server to the home-location register (HLR) for authentication. EAP-SIM (RFC 4186) or EAP-Authentication and Key Agreement (EAP-AKA; RFC 4187) standards are used for the encapsulation, depending on the type of SIM card used and the HLR capabilities. Obviously, this method requires interconnection between the AAA server and the HLR or home-subscriber server (HSS). The architecture is shown in Figure 4.© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 5 of 23Figure 4.EAP-Based Authentication ArchitectureFor subscribers with non-SIM devices, the operator can distribute certificates for EAP-Transport Layer Security (EAP-TLS) or similar versions of EAP authentication. The typical call flow of EAP authentication (with HLR integration) is shown in Figure 5.Figure 5. Typical EAP Authentication Call Flow© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 6 of 23Note that EAP-based authentication offers a radio security advantage. Because the authentication is handled at Layer 2, EAP messages can be used to negotiate encryption keys for the IEEE 802.11i-based encryption of the radio interface. This approach provides much stronger security for radio communication compared to the unencrypted radio interface of portal-based authentication and is uniquely able to prevent simple MAC address spoofing attacks.Next Generation HotspotIn 2010, Cisco and industry leaders formed the Next Generation Hotspot Task Group in the Wireless Broadband Alliance (WBA). The goal was to rally the industry around a common set of Wi-Fi Alliance (WFA) standards called Hotspot 2.0 that would bring a 3G-like end-user experience to Wi-Fi authentication and roaming. The outcome of the Next Generation Hotspot Task Group is a set of operator guidelines and the Wi-Fi Certified Passpoint interoperability for operators and equipment vendors. The Cisco SP Wi-Fi solution features Next Generation Hotspot, enabling service providers to better manage and monetize their carrier-grade Wi-Fi networks. There are three main building blocks of the next-generation hotspot: IEEE 802.11u, Wi-Fi Protected Access 2 (WPA 2) Enterprise, and EAP-based authentication. For a detailed description of the initiative, see The Future of Hotspots: Making Wi-Fi as Secure and Easy to Use as Cellular.® ™program expected in 2012 from the Wi-Fi Alliance. The certification will help ensure authentication and roamingAuthentication SummaryBecause of the complementary functions of both authentication methods, mobile operators deploying Wi-Fi access networks usually implement both EAP and IEEE 802.1X authentication and portal-based authentication in their networks. Portal-based authentication is used to attract subscribers visiting the network who don’t yet have a relation to the operator. It allows typical public Wi-Fi use cases such as credit card payments, vouchers, and SMS passwords. In general, it enables generation of new revenue from Wi-Fi networks. EAP-based authentication targets primarily devices with the operator’s SIM card. It allows transparent authentication and secure communication without much interaction from the subscriber (only initial configuration of the service set ID (SSID) is needed when a device detects the Wi-Fi network for the first time). In real-life deployments, the introduction of EAP-SIM or EAP-AKA authentication leads to significantly better utilization of the network by subscribers and therefore enables much greater savings from offloading. With the introduction of Wi-Fi Certified Passpoint devices, operators will be able to simplify Wi-Fi network access even more. IEEE 802.11u devices do not need any intervention from the subscriber to connect to the Wi-Fi network (unlike traditional devices, which require SSID selection). Roaming agreements based on the Next Generation Hotspot recommendation (WLAN Roaming Inter-Exchange [WRIX]) enable user equipment with IEEE 802.11u support to choose the right SSID automatically, even in visited networks.Policy and Charging ControlAn important concern of mobile operators is the availability of similar or identical policy enforcement and charging rules for the subscriber, regardless of the RAN being used. Therefore, the design of PCC integration is a crucial part of Wi-Fi offload.© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 7 of 23Experience from live deployments shows that the most efficient approach to PCC integration is the reuse of the elements deployed for the 3GPP services. The actual integration option will depend on the PCC infrastructure implemented in the particular mobile operator network. If the operator uses a device with the standalone policy and charging enforcement function (PCEF), the WAG will be integrated as an additional gateway served by the PCEF. If the PCEF is integrated into the gateway General Packet Radio Service (GPRS) support node (GGSN), the WAG may emulate a serving GPRS support node (SGSN) and switch the Wi-Fi sessions to a GPRS Tunneling Protocol (GTP) tunnel to the traditional GGSN. The following sections discuss the details of these two options. Note that this document describes trusted non-3GPP access integration into 2G and 3G PCC. The 3GPP standard offers no guidance for this integration. Later this document explores standardized architecture for LTE integration and untrusted non-3GPP IP access integration.Standalone PCEFIn the standalone PCEF scenario, the WAG is set up to send user data traffic to the PCEF for PCC integration. At the same time, traffic that does not need policy control (traffic from visiting customers, wholesale traffic, onetime voucher users, etc.) is allowed to go directly to the Internet (Figure 6).Figure 6. Standalone PCEF ArchitectureBecause the PCEF needs to be able to correlate the user identity with the data flows passing the PCEF, a mechanism is needed that can synchronize the user identity with the IP address of the subscriber (so that individual data packets can be associated with the user data plan and processed accordingly). Commonly, the RADIUS proxy function on the PCEF is used to create user session information based on the attributes included in the accounting messages coming from the access gateway for a particular user. Figure 7 shows the typical call flow.© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 8 of 23Figure 7.Typical PCEF Authentication Call FlowIf this model is deployed, the operator needs to help ensure that all mandatory information needed by the PCEF is included in the RADIUS messages from the access gateway or proxied through AAA, where the necessary attributes are added to the message. In addition to the IP address of the subscriber session, information about the international mobile subscriber identity (IMSI), the mobile station international subscriber directory number (MSISDN), and the associated access point name (APN) is usually required.GTP to Traditional GGSNIf the PCEF is an integral part of the GGSN, the option of forcing Wi-Fi sessions into a GTP tunnel (packet data protocol [PDP] context) may provide the best solution for PCC integration. The traffic that does not belong to the mobile subscribers of the operator, and which therefore cannot be processed on the GGSN, is forwarded directly to the Internet (Figure 8).© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 9 of 23Figure 8.GTP-to-Traditional GGSN ArchitectureClearly, GTP support is required on the WAG for this deployment model. Also important to consider is the availability of the required attributes in the PDP context request, which are mandatory in the operator’s PCC system. Again, these attributes commonly include the IMSI, MSISDN, QoS profile, and APN. The call flow for this deployment model is shown in Figure 9.Figure 9. GTP-to-Traditional GGSN Call Flow© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 10 of 23Note that even though all sessions (3G and Wi-Fi) are anchored on the GGSN, this solution does not provide transparent handover of the IP sessions between the Wi-Fi and 3G radio networks. This limitation exists because the Wi-Fi and 3G PDP contexts are individual sessions, and the user device can open them simultaneously. Unfortunately, the 3GPP standard does not provide a mechanism to help ensure that the same GGSN is chosen for both of these PDP contexts, and therefore anchoring of the sessions on the same device cannot be achieved.PCC Integration ConsiderationsWhen performing PCC integration, note the following:●The options listed are valid and needed for 3G. As discussed later, LTE provides native integration into theEPC and therefore into the PCC●The critical element is the capability of the WAG to provide all necessary information for charging(specifically, some of these attributes are not part of EAP authentication and need to be retrievedseparately, if needed: for example, the MSISDN, the QoS profile, and optionally, the 3GPP chargingcharacteristics)●Usually, the PCEF does not handle traffic from users who are not mobile customers of the operator(non-SIM subscribers). This traffic is sent directly to the Internet. If these particular sessions need policy or charging functions, these are usually handled by the WAG and Wi-Fi back-end systems directlyLTEBefore describing the third function of the Wi-Fi offload architecture, session handover, this document examines the integration of PCC in an LTE scenario. This examination will help you later understand user session mobility and anchoring.3GPP TS 23.402 describes native integration of trusted and untrusted non-3GPP IP access networks into the EPC. The standard accepts that the Wi-Fi network is as valid an access network as any other 3GPP radio access network. This acceptance enables operators to use the standards-based EPC components for integration and therefore helps ensure a good level of interoperability between different access types.As mentioned earlier, this document concentrates first on the trusted part of the architecture. To force the Wi-Fi traffic to the EPC, two interfaces are defined, both of them terminating Wi-Fi sessions on the packet data network gateway (P-GW) as shown in Figure 10.Figure 10. 3GPP Architecture for Non-3GPP IP Access Integration into EPC, S2c OptionThe S2c interface is based on the Dual-Stack Mobile IP Version 6 (DSMIPv6) protocol and requires user equipment to support it. DSMIPv6 creates a tunneled connection between the user equipment and the P-GW, which is used to forward all traffic to and from the user equipment. The P-GW is responsible for assigning a virtual IP address to the tunnel during the setup process. This IP address is from the same IP pool that is used for LTE sessions. Because all traffic to and from the user equipment is sent through the tunnel, the P-GW has complete visibility of the user traffic and can apply PCC and other necessary functions to the traffic in the same manner as it does to the LTE sessions (Figure 11).Figure 11. 3GPP Architecture for Non-3GPP IP Access Integration into EPC, S2a OptionAnother option shown in Figure 11 is to choose the S2a interface for forwarding traffic from the Wi-Fi network to the EPC. This interface is based on the Proxy Mobile IPv6 (PMIPv6) protocol. As with S2c, the interface terminates on the P-GW and enables visibility into the user traffic. The difference is that the PMIPv6 protocol does not require any changes on the user equipment. The wireless access gateway (WAG) in the trusted non-3GPP IP access network provides the mobile IP functions transparently for the client. It creates the tunnel, requests the IP address from the P-GW, and then assigns this address to the Wi-Fi connection. In this way, the user equipment is assigned an IP address that is part of the P-GW pool, but it does not see the address as virtual but as a physical address directly on the Wi-Fi interface.Figure 12 shows an overview of LTE architecture. Again, in addition to tunneled traffic to the EPC, direct connection from the WAG to the Internet is enabled for users who are not mobile subscribers of the operator.Figure 12. LTE ArchitectureTwo methods of integration (S2a and S2c) have been used here, and each has different implications for the deployment. The S2c approach requires changes on the user equipment; therefore, it is considered client-based. This feature may not be trivial in a mobile network because of the need for client software for functions. The mobile operator must help ensure that large numbers of different handsets and operating systems can be addressed by the software, must keep the user equipment updated with new versions of software, and must motivate subscribers to use the client software. Figure 13 illustrates the attachment as defined by 3GPP. Phase A represents attachment to the Wi-Fi network. In phase B, the DSMIPv6 tunnel is opened to the P-GW; and in phase C, the session is signaled as the active one. Also illustrated is the establishment of policies for the session using the PCRF.Figure 13. S2c Network Attachment As Defined by 3GPPThe S2a approach eliminates the problem of the client software. The trade-off here is that the operator loses control of Wi-Fi activation and session handover on the user equipment. This loss of control may result in unexpected behavior of the user equipment during switchover from 3GPP access to Wi-Fi and back. Figure 14 shows the attachment as defined by 3GPP. The trusted non-3GPP IP access network represents the Wi-Fi network, with the WAG as part of this network. For a detailed description of the call flow, please refer to 3GPP TS 23.402.Figure 14. S2a Network Attachment As Defined by 3GPPInter-Radio HandoverBefore analyzing different methods of handover, it is important to understand the terms often used in this context. Specifically, you need to understand what session handover is and the types of handover that can be implemented depending on the requirements of the mobile operator.In mobile data networks, one of the most important procedures is handover - when a subscriber moves from one radio station to another. The handover procedure describes the behavior of the network when the subscriber switches from one radio type to another (for example, from 3G to Wi-Fi).Today, few handover types can be used. The one required in the operator’s network needs to balance the expectations of subscribers and the complexity of the architecture.●Handover without IP address persistency (connectivity handover): When a subscriber connects to the Wi-Fiaccess network, the subscriber is authenticated transparently and is assigned a new IP address by theWi-Fi network. All new communications can use the new IP address as the source. All established TCP and UDP connections can, however, still continue over the 3G network. If the user equipment logicdisables the 3G interface, then these established sockets will need to be (automatically) reestablished over Wi-Fi, using the new IP address.●Handover with IP persistency (IP handover): When a subscriber connects to the Wi-Fi network, thesubscriber will be assigned the same IP address as he used on the 3G or LTE network. If the established TCP and UDP connections are bound to a physical interface (because of the TCP/IP stack implementation of the UE), they will need to be (automatically) reestablished using the new Wi-Fi interface, even though they will use the same IP address.●Session handover (transparent handover): This type of handover is similar to IP handover, but thehandover must occur in a time range that allows real-time media applications (voice over IP, streamingvideo, etc.) - for example, using established UDP sockets for media and TCP sockets for the control-plane protocol - to continue without interruption or user-experience degradation as the device switches between Wi-Fi and 3G cellular connectivity.Note that seamless handover can be achieved only with user equipment cooperation, which means that software updating (for client software) is needed on terminals. At minimum, this software needs to provide a virtual interface adapter, to mask the physical interface structure for TCP and UDP sockets. The challenges of client software have already been discussed above.3GPP defines handover mechanisms for trusted Wi-Fi only as part of the LTE architecture. For untrusted Wi-Fi, proposals exist for 3G and LTE. This document starts with a look at trusted non-3GPP IP access networks in LTE.S2a-Based Handover (Clientless)The advantage of PMIPv6 as protocol for the S2a interface is that the protocol is built for network-based IP mobility. Therefore, it can provide, without client involvement, handover of the IP address between different access types. In this design, the P-GW is responsible for anchoring the session, assigning the IP addresses, and switching the PMIPv6 or Ga TP tunnels between different access gateways in the event of handover. The access gateways must support the mobile access gateway (MAG) function to fulfill all mobile IP-related mobile-node functions.Figure 15 illustrates the handover call flow as defined in 3GPP TS 23.402. The trusted non-3GPP IP access element is equivalent to a WAG.Figure 15. Handover Call Flow As Defined in 3GPP TS 23.402Although S2a-based handover is clientless, recall that the problems with Wi-Fi-to-3GPP handover are the existence of two radio interfaces on the user equipment and the role of the user equipment as the handover decision point. Because of these two factors, the network can never ensure that the user equipment is using the proper interface.Note: The definition of what constitutes a proper interface can change on an operator-by-operator basis.Also, at the user equipment, the TCP/IP stack needs to be able to cope with two physical interfaces that may eventually have identical IP addresses. Additionally, in some TCP/IP stack implementations, application sockets may be bound to a physical interface. Therefore, when the user equipment or application switches between interfaces, the application connections must be dropped and may need to be reestablished from the new interface.Given all of these dependencies, the PMIPv6-based architecture cannot (without user equipment support) guarantee operation of a transparent handover function on all user equipment types. This situation can be improved if a properly designed connection manager (with virtual adapters) is installed on all user equipment.Cisco is actively working with chipset and handset vendors to support standardization and development of user equipment that meets the requirements for smooth clientless handover.S2c-Based Handover (Client-based)For the S2c interface, 3GPP reuses the IETF-defined DSMIPv6 protocol between the user equipment and theP-GW as the anchor point. When on the non-3GPP network, the user equipment builds the DSMIPv6 to the appropriate P-GW and is assigned a virtual IP address, which is then used for application communication.The same IP address will be assigned to the user equipment over a 3GPP access network in the event of handover. The 3GPP network is treated as the home network, and therefore the user equipment does not need to set up a DSMIPv6 tunnel on the 3GPP access network.Figure 16, from 3GPP TS 23.402, summarizes the call flow during handover from an LTE access network to aWi-Fi access network.。

邮件缩写

和老外聊天、发邮件常用英语缩写邮件里常用的四个英文缩写CC,FYI,ASAP,RESEND1. CC 抄送Literal meaning: Carbon Copy. When used in an e-mail, it means to send a copy of the e-mail to someone else.Hidden meaning: If you are on the CC list, you may simply read the e-mail. You're not always obligated to reply. But if an e-mail sent to you has your boss' e-mail on the CC l ist, watch out. When the boss is involved, you'd better take the e-mail more seriously. 2. FYI 供你参考Literal meaning: For your information.Hidden meaning: By adding "FYI", the sender indicates that the e-mail contains informatio n that may be valuable to your company or job responsibilities.3. ASAP / urgent 紧急文件Literal meaning: As soon as possible.Hidden meaning: When you see "ASAP" or "urgent" in an e-mail or document, you should quickly carry out the e-mail's orders.4. RESEND! 重传Literal meaning: Please resend your reply to me.Hidden meaning: "I haven't received your reply. I don't have much time. Please hurry."Y ou might get such a message from someone who sent you an e-mail, to which you've yet to reply.others:数字：2 = to/too2B or not 2B = To be or not to be4 = for4ever = foreverA：ASL = Age/Sex/LocationAFAIC = As Far As I’m ConcernedAFAIK = As Far As I KnowAFK = Away From KeyboardAIAM U = And I’m A Monkey’s UncleAISI = As I See ItAKA = Also Known AsAMBW = All My Best WishesANFAWFOWS = And Now For A Word Word From Our Web Sponsor AOTS = All Of The SuddenASAFP = As Soon As "Friggin" PossibleASAP = As Soon As PossibleATST = At The Same TimeAWGTHTGTTA = Are We Going To Have To Go Through This Again AWGTHTGTTSA = Are We Going To Have To Go Through This Sh Again AYSOS = Are You Stupid Or SomethingB：B4 = BeforeB4N = Bye For NowBBFBBM = Body By Fisher, Brains by MattelBBIAB = Be Back In A BitBBIAF = Be Back In A FewBBL = Be Back LaterBBN = Bye Bye NowBCNU = Be Seein’ YouBF = BoyfriendBFD = Big Fing DealBFN = Bye For NowBHOF = Bald Headed Old FartBIF = Basis In FactBITD = Back In The DayBiz = BusinessBM = Byte MeBMOTA = Byte Me On The AssBNF = Big Name FanBOHICA = Bend Over Here It Comes Again BOM=bill of material 材料清单BR = Best regardsBRB = Be Right BackBRT = Be Right ThereBS = Big SmileBT = Byte ThisBTDT = Been There Done ThatBTSOOM = Beats The Sh Out Of MeBTW = By The WayBTWBO = Be There With Bells OnBWDIK = But What Do I Know?BWO = Black, White or OtherC：Cam = Web CameraCIAO = Goodbye (in Italian)CID = Consider It DoneCIS = CompuServe Information ServiceCMF = Count My FingersCof$ = Church of ScientologyCRAFT = Can’t Remember A Fing Thing CRAWS = Can’t Remember Anything Worth A Sh CSL = Can’t Stop LaughingCTC = Choaking The ChickenCU = See YouCUL/CYL/CUL8R = See You LaterCWYL = Chat With You LaterCYA = Cover Your AssD：DBEYR = Don’t Believe Everything You ReadDD = Due DiligenceDDD = Direct Distance DialDETI = Don’t Even Think ItDGT = Don’t Go ThereDHYB = Don’t Hold Your BreathDIIK = Damned If I KnownDILLIGAD = Do I Look Like I Give A d\\amn DILLIGAS = Do I Look Like I Give A ShDKDC = Don’t Know Don’t CareDL = DownloadDLTM = Don’t Lie To MeDQYDJ = Don’t Quit You’re Day JobDRIB = Don’t Read If BusyDS = Dunce SmileyDYSTSOTT = Did You See The Size Of That ThingE：EG = Evil GrinEOM = End Of MessageESO = Equipment Smarter than OperatorF：F2F/FTF = Face To FaceFAQ = Frequently Asked QuestionFBKS = Failure Between Keyboard and SeatFE = For Example/Fatal ErrorFF&PN = Fresh Fields And Pastures NewFOAF = Friend Of A FriendFTASB = Faster Than A Speeding BulletFT = FaintFTL = Faster Than LightFTTB = For The Time BeingFUBAR = Fed Up Beyond All RecognitionFUBB = Fed Up Beyond BeliefFUD = (Spreading) Fear, Uncertainty, and Disinformation FWIW = For What It’s WorthFYA = For Your AmusementFYI = For Your InformationFYM = For Your MisinformationG：G2G = Got To GoG8T/GR8 = GreatGAL = Get A LifeGDGD = Good,GoodGF = girlfriendGG = Good Game/Gotta GoGIGO = Garbage In, Garbage OutGIWIST = Gee, I Wish I’d Said ThatGL = Good LuckGLYASDI = God Loves You And So Do IGMTA = Great Minds Think AlikeGNBLFY = Got Nothing But Love For YouGR&D = Grinning Running And DuckingGRRRR = "Growling"GSOAS = Go Sit On A SnakeGTG = Got To GoGTGB = Got To Go, ByeGTGP = Got To Go PeeGTH = Go To HellGTSY = Glad To See YaGYPO = Get Your Pants OffBE A QUEEN.H：HAGO = Have A Good OneHAK = Hugs And KissesHB = Hurry BackHD = HoldHHO1/2K = Ha Ha, Only Half Kidding HHOK = Ha Ha, Only Kidding HIOOC = Help! I’m Out Of Coffee Howz = How isHTH = Hope This (That) HelpsHUA = Heads Up AceHUYA = Head Up Your AI：IAC = In Any CaseIAE = In Any EventIANAC = I Am Not A CrookIANAL = I Am Not A LawyerIBT = In Between TechnologyIBTD = I Beg To DifferIC = I See/In CharacterIDGAF = I Don’t Give A FIDGI = I Don’t Get ItIDK = I Don’t KnowIDKY = I Don’t Know YouIDST = I Didn’t Say ThatIDTS = I Don’t Think SoIFAB = I Found A BugIFU = I Fed UpIGGP = I Gotta Go PeeIIIO = Intel Inside, Idiot Outside IIMAD = If It Makes An(y) Difference IIRC = If I Remember CorrectlyIIWM = If It Were MeILICISCOMK = I Laughed, I Cried, I Spat/Spilt Coffee/Crumbs/Coke On My Keyboard ILY = I Love YouIMHO = In My Humble OpinionIMNSHO = In My Not So Humble OpinionIMO = In My OpinionINMP = It’s Not My ProblemINPO = In No Particular OrderIOH = I’m Outta HereIOW = In Other WordsIRL = In Real LifeISS = I Said SoITM = In The MoneyIYKWIM = If You Know What I MeanIYSS = If You Say SoJ：J/C = Just CheckingJ/K = Just Kidding!J/W = Just WonderingJAFO = Just Another Fing OnlookerK：K/KK = OK/OK, OKKFY = Kiss For YouKISS = Keep It Simple StupidKIT = Keep In TouchKMA = Kiss My AssKWIM = Know What I MeanKX = kissKYPO = Keep Your Pants OnL：L8R = LaterLD = Long DistanceLDTTWA = Let’s Do The Time War p Again LLTA = Lots And Lots Of Thunderous Applause LMAO = Laughing My Ass OffLMK = Let Me KnowLOL = Laughing Out Loud/Lots Of Luck(Love) LTIC = Laughing ’Til I CryLTNS = Long Time No SeeLYL = Love Ya LotsLYLAS = Love You Like A SisterM：M8T = MateMHOTY = My Hat’s Off To YouMM = Market MakerMorF = Male or Female?MOTD = Message Of The DayMOTSS = Members Of The Same Sex MTFBWY = May The Force Be With You MWBRL = More Will Be Revealed Later MYOB = Mind Your Own BusinessN：N = And/Know/NowNAK = Nursing At KeyboardNAZ = Name, Address, Zip (also means Nasdaq) NBD = No Big DealNBIF = No Basis In FactNFI = No Fing IdeaNFW = No Fing WayNIFOC = Nude In Front Of The ComputerNM = Never MindNMP = Not My ProblemNMU = Nothing Much YouNOYB = None Of Your BusinessNP = No ProblemNQOCD = Not Quite Our Class DearNRG = EnergyNRN = No Reply NecessaryNYCFS = New York City Finger SaluetO：OAUS = On An Unrelated SubjectOBTW = Oh, By The WayOIC = Oh, I SeeOICU = Oh, I See YouOMDB = Over My Dead BodyOMG = Oh My God/Oh My GoshOMIK = Open Mouth, Insert KeyboardONNA = Oh No, Not AgainOOC = Out Of CharacterOOTB = Out Of The Box/Out Of The BlueOT = Off TopicOTOH = On The Other HandOWTTE = Or Words To That EffectOZ = stands for "Australia"P：PEBCAK = Problem Exists Between Chair And Keyboard PEM = Privacy Enhanced MailPic = PicturePIMP = Peeing In My PantsPITA = Pain In The AssPLS/PLZ = PleasePMFJI = Pardon Me For Jumping InPO = Piss Off/product order/purchase orderPOS = Parents Over ShoulderPOV = Point Of ViewPPL = PeoplePro = ProfessionalPS = By The Way/PhotoshopS:SS:spring/summerT：TAH = Take A HikeTANSTAAFL = There Ain’t No Such Thing As A Free Lunch TARFU = Things Are Really Fed UpTDTM = Talk Dirty To MeTEOTWAWKI = The End Of The World As We Know It TFN = Thanks For Nothin’THX/TX/THKS = ThanksTIA = Thanks In AdvanceTIAIL = Think I Am In LoveTIC = Tongue In CheekTKS/TKX=ThanksTLA = Three Letter AcronymTLGO = The List Goes OnTM = Trust MeTMI = Too Much InformationTMTOWTDI = There’s More Than One Way To Do ItTPTB = The Powers That BeTSR = Totally Stuck in RAMTTFN = Ta Ta For NowTTT = That’s The Ticket/To The Top TTUL/TTYL = Talk To You Later TWHAB = This Won’t Hurt A BitTY = Thank YouTYVM = Thank You Very MuchU：U = YouUR = YourU R = You areunPC = unPolitically CorrectURYY4M = You Are Too Wise For MeV：VFM = Values For MoneyVG = Very GoodW：WAG = Wild Ass GuessWAI = What An IdiotWB = Welcome BackWCA = Who Cares AnywayWDYS = What Did You Say?WDYT = What Do You Think?WE = WhateverWEG = Wicked Evil GrinWG = Wicked GrinWGAFF = Who Gives A Flying F WIIFM = What’s In It For Me?WIT = Wordsmith In TrainingWITFITS = What in the F is this ShWOG = Wise Old GuyWot/Wut = WhatWRT = With Respect To/With Regard To WTF = What The FWTG = Way To Go!WTSDS = Where The Sun Don’t Shine WYMM = Will You Marry MeWYP = What’s Your Problem?WYRN = What’s Your Real Name?WYS = Whatever You SayWYSIWYG = What You See Is What You Get WYT = Whatever You ThinkX：X U = Kiss YouY：Y = WhyYa = YouYA = Yet AnotherYAFIYGI = You Asked For It You Got It YDKM = You Don’t Know MeYep/Yup = YesYGBK = You Gotta Be Kiddin’YMMV = Your Mileage May VaryYNK = You Never KnowYOYO = You’re On Your OwnYR = Yeah, RightYSYD = Yeah, Sure You DoYTTT = You Telling The Truth?YYSSW = Yeah Yeah Sure Sure Whatever缩略语含义说明BTW 或btw顺便说一句by the way 的首字母缩略词。

译林版七年级下册英语Unit6Period3Reading习题课件

2. 我醒来时, 发现自己独自一人在一个房间里面。 I ___fo_u_n__d_ __m_y_s_e_l_f _ __a_l_o_n_e__ in a room when I woke up.
题组专训·突破考点
3. —Look, there is a cute bird, Mom.
—It flew into our kitchen ____B____ the window just now, 【点A拨lex】. 本题用词义辨析法。句意为“——快看, 那有A一. a只cro可ss爱的小B鸟. t,h妈ro妈ug。h ——ACl.eaxb, o它ve是刚才D通. u过nd窗er 户飞进我们厨房的”。above, 在物体的上方; under, 在物体的下面。很容易排除C 、D选项。across指的是从物体的表面穿过, 而through指的是从物体的内部穿过。结合语境, 小鸟穿过窗户, 故选B。
37 swam
28 D 33 activities 38 us
29 A 34 healthy 39 more
30 E 35 First
40 colourful
题组专训·突破考点
1. His grandfather lives ____B____ in a small house, but
he doesn't feel ________.
课后巩固·拓展延伸
19. 【2021·毕节】My grandma can use WeChat (微信).
She learns it all by ____B____.
A. she
B. herself
C. her
D. hers
【点拨】考查代词辨析。句意为“我的祖母会使用微信。她自学的”。all by oneself是固定搭配, 意为“某人自己”。故选B。

starscream函数 -回复

starscream函数-回复如何使用Python编写一个Starscream函数。

尽管Python本身在处理网络通信方面已经相当强大，但星际战士（Starscream）函数是一个非常有用的库，它为我们提供了更高层次的抽象，使得编写网络应用程序变得更加简单。

在本文中，我将一步一步地向您展示如何使用Python编写一个Starscream函数，并演示如何在实际项目中使用它。

首先，让我们简要了解一下Starscream函数。

Starscream是一个用于客户端和服务器实现WebSocket的跨平台库。

WebSocket是一种在Web 浏览器和服务器之间交换数据的通信协议，它能够在连接建立后保持持久性连接，并进行全双工通信。

Starscream允许我们使用WebSocket进行实时通信，例如聊天应用程序、游戏中的实时更新等。

接下来，我们将使用以下步骤创建一个Starscream函数。

步骤1：安装Starscream库在开始之前，我们需要先安装Starscream库。

打开终端，输入以下命令来安装库：pip install starscream步骤2：导入Starscream库在您的Python脚本中，使用以下代码行导入Starscream库：pythonimport starscream步骤3：创建WebSocket连接创建一个WebSocket连接是使用Starscream函数的第一步。

使用以下代码行来创建一个WebSocket连接：pythondef connect(url):ws = starscream.websocket.WebSocket()ws.connect(url)return ws在上述代码中，我们首先创建一个WebSocket实例，然后使用该实例的connect()方法连接到指定的URL。

最后，我们将WebSocket实例返回给调用方。

步骤4：发送数据一旦我们成功建立了WebSocket连接，我们可以使用send()方法发送数据。

ReadyNAS 3312 4312X系列网络附加存储数据表说明书

State-of-the-art Performance and Data ProtectionReadyNAS 3312 and 4312X are best-in-class high performance network attached storage systems. The RR4312X has two built-in 10 Gigabit Ethernet interfacesto further meet the storage demandsof next generation business networks. Featuring an architecture powered by blazing fast quad-core 5th generation Intel Xeon processors along with DDR4 ECC memory that is expandable up to 64GB, the RR3312 and RR4312 are the no compromise, high performing data storage systems of choice for businesses that need the very best in capacity, performance and security.ReadyNAS brings state-of-the-art datastorage and protection technologies inan affordable and easy-to-use system tothe SMB. All ReadyNAS are built on therevolutionary ReadyNAS OS 6 operatingsystem and next-gen BTRFS file system.A best-in-class 5 levels of data protection- X-RAID, Unlimited Snapshots, Bit rotprotection, real-time anti-virus and easyoffsite replication work in concert to securelyprotect your data from common risks.All ReadyNAS systems utilize proprietaryReadyCLOUD technology. WithReadyCLOUD, remotely accessing andsharing files in your own secure privatecloud has never been easier. No VPNsetup, no port forwarding, no dynamicDNS required. Designed specificallyfor the unique needs of business users,RR3312 and RR4312X are virtualization-ready with iSCSI support, thin provisioningcapability and VMware certified.To maximize storage capacity, an SASexpansion card (RRSASEXP-10000S) canbe purchased separately for expansionsupport. Expansion chassis fromNETGEAR, EDA2000 and EDA4000, offer12 and 24 bay expansion, respectively.Key Business Features and Solutions• Automatic Backup & Sync: Using the ReadyCLOUD app for PC, scheduled protection is easier than ever before• Bit Rot Protection: A proprietary technology protecting your files from unplanned degradation• Unlimited Snapshots: Unlimited data snapshot capability for on-box protection and flexible data recovery • X-RAID & Instant Provisioning: Easily expand capacity and feel confident knowing that data is always protected • Cloud-managed Replication: Maintaindata sets in multiple locations or ensureprotection of data from remoteor branch office locations• iSCSI and Thin Provisioning: Powerfultools for a businesses taking advantageof virtual infrastructures• Anti-virus & Encryption: Keep dataprotected from outside threats and safefrom prying eyes• Modern GUI and ReadyCLOUDManagement: Sleek, modern interfacethat puts the tools you need, where andwhen you need them• File Server: Unified storage platform forsharing files between Windows, Macand Linux-based computers• Backup: RAID redundancy withautomatic expansion and unlimited datasnapshots for point-in-time restore• Disaster Recovery: Cloud-managedreplication for maintaining multiple setsof data and performing easy restores incase of disaster• Virtualization: Thin provisioning, iSCSIsupport and certified with VMwareHardware ReadyNAS 3312ReadyNAS 4312S ReadyNAS 4312XCPU-10000S Intel Xeon E3-1225v63.3GHzQuad Core Processor,Max Turbo Speed3.7GHzIntel® Xeon E3-1245v6 3.5GHzQuad Core, HyperThreaded Processor,Max Turbo Speed3.9GHzIntel® Xeon E3-1245v6 3.5GHzQuad Core, HyperThreaded Processor,Max Turbo Speed3.9GHzCPU-20000S Intel Xeon E3-1225v63.3GHz, Max TurboSpeed 3.7GHzIntel Xeon E3-1245v63.5GHz, Max TurboSpeed 3.9GHzIntel Xeon E3-1245v63.5GHz, Max TurboSpeed 3.9GHzMemory8GB DDR4 ECC16GB DDR4 ECC16GB DDR4 ECC Memory Expansion64GB DDR464GB DDR464GB DDR4 Drive Bays121212Drive T ypes Supported SATA/SSD 2.5” or 3.5”SATA/SSD 2.5” or 3.5”SATA/SSD 2.5” or 3.5”Hot Swappable Drives Yes Yes Yes eSATA Ports222SAS Ports for Expansion Chassis (sold separately)222 Gigabit LAN Ports44410Gbps LAN Optical SFP+02010Gbps LAN Copper 10GBase-T002USB Ports2x USB3.02x USB3.02x USB3.0Power SupplyDual RedundantInternal 550 W; input100-240V AC,50-60HzDual RedundantInternal 550 W; input100-240V AC,50-60HzDual RedundantInternal 550 W; input100-240V AC,50-60HzChassis Warranty5 years including5 years NextBusiness Day hard-ware replacement5 years including5 years NextBusiness Day hard-ware replacement5 years including5 years NextBusiness Day hard-ware replacementFan (mm) 3 x 80 3 x 80 3 x 80 Dimensions DxWxH (mm)707 x 445 x 88 707 x 445 x 88 707 x 445 x 88 Weight (diskless) (kg)11.96 11.96 11.96 Software and Functionality ReadyNAS 3312ReadyNAS 4312S ReadyNAS 4312XCertification and Compatibility VMware vSphereESXi 6.0 VMware vSphereESXi 6.0VMware vSphereESXi 6.0Cloud-discovery, Setup and Management Yes Yes Yes Data Protection with Unlimited Snapshots Yes Yes Yes Web-managed Replication for Disaster Recovery Yes Yes Yes Real-time Antivirus Yes Yes Yes iSCSI and Thin Provisioning Yes Yes Yes ReadyNAS Rackmount ComparisonTechnical SpecificationsData Protection (Backup & Replication)• Unlimited block-based snapshots for continuous data protection• Restore Snapshots to any point in time• Restore Snapshot data from local admin GUI, ReadyCLOUD, or native Windows File Explorer• Scheduled and manual snapshots• File Synchronization (rsync)• Encrypted Remote Replication• Data compression• Cloud managed Remote Replication (ReadyNAS to ReadyNAS). No licenses required for ReadyNAS OS 6 devices.• AES 256-bit volume based encryption• X-RAID (automatic single volume online expansion)• Single Disk, JBOD• RAID Levels: 0, 1, 5, 6, 10, 50, 60• RAID Global Hot Spare• Backup to external storage (USB/eSATA)• Apple Time Machine support• Amazon Cloud Drive synchronization (requires Amazon account)• ReadyNAS Vault™ Cloud backup (optional service)• Dropbox™ file synchronization (requires Dropbox account)• Real-time Anti-Virus scanning using signature and heuristic algorithms. (No end-user licenses required)Protection for viruses, malware, worms, and Trojans.• Bitrot automatic detection & correction for degraded mediaStorage Area Networks (SAN), Virtualization• Unlimited iSCSI LUN Snapshot• Thin or thick provision LUNs• Multi-LUN per target• LUN mapping and masking• SPC-3 Persistent Reservation (iSCSI)• MPIO and MC/S (iSCSI)• Max # iSCSI Target: 256• Max # iSCSI LUN: 256• VMware vSphere 6• Citrix XenServer 6• Windows Server 2008 Hyper-V• Windows Server 2008 Failover Clustering• Windows Server 2012 R2ReadyCLOUD (cloud access to ReadyNAS• ReadyCLOUD portal based data access and management• Upgrade firmware remotely• VPN quality remote data transfer and management• Share data with friends & co-workers directly from portal• Share file via email linkReadyCLOUD Client Applications• ReadyCLOUD client applications for Apple OS X, Microsoft Windows, Android, and Apple iOS• VPN quality remote data transfer and management• Simple remote access through ReadyCLOUD client (no firewall or router configuration needed)• Sync files/folders between PC (Mac/Windows) & ReadyNAS• Sync files/folders between multiple PCs and ReadyNAS• Sync files/folders between multiple users and ReadyNAS• Backup files/folders from PC to ReadyNASFile System & Transfer Protocols• ReadyNAS OS 6.5 or later• Linux 4.x• Internal File System: BTRFS• External File System: EXT3, EXT4, NTFS, FAT32, HFS+• Copy-on-write file system• Microsoft Network (CIFS/SMB 3)• Apple OS X (AFP 3.3)• Linux/Unix (NFS v4)• Internet (HTTP)• Secure Internet (HTTPS)• File Transfer Protocol (FTP)• FTP over SSL / TLS (explicit)• FTP Passive mode with port range setup• FTP Bandwidth control• FTP Anonymous• FTP Transfer Log• Secure Shell (SSH)• Web Authoring (WebDAV)• Storage Array Network (iSCSI)• File Synchronization (rsync)• Local web file managerUsers/Groups• Max # Users: 8192• Max # User Groups: 8192• Max # Share Folder: 1024• Max # Concurrent Connections: 1024• Share Folder Level ACL Support• Advanced Folder Permissions with Subfolder ACL support for CIFS/SMB, AFP, FTP• Microsoft Active Directory (AD) Domain Controller Authentication• Local access list• ReadyCLOUD based ACL• Domain user login via CIFS/SMB, AFP, FTPManagement• ReadyCLOUD cloud based discovery and management• RAIDar local discovery agent (Windows/Mac)• Save and restore system configuration (clone devices)• Local event log• Local Graphical User Interface (GUI) Languages: English, German, French, Japanese, Chinese (Traditional &Simplified), Russian, Swedish, Portuguese, Italian, Spanish, Polish, Czech, Dutch, Korean• Unicode support• Volume Management• Thin provision Shares and LUNs• Instant Provisioning/Expansion with data protection• Restore to factory default• Operating Systems supported: Microsoft Windows 7, 8/8.1, 10, Microsoft Windows Server 2008 R2/2012, AppleOS X, Linux/Unix, Solaris, Apple iOS, Google Android• Supported Web Browsers (Microsoft Internet Explorer 9+, Microsoft Edge, Mozilla Firefox 14+, Google Chrome50+, Apple Safari 5+)System Monitoring• Device capacity, performance, resource and health monitoring• Bad block scan• Hard Drive S.M.A.R.T.• File System Check• Disk Scrubbing• Disk Defragment• Volume balance• Alerts (SMTP email, SNMP, local log)• Auto-shutdown (hard drive, fan, UPS)• Auto-restart on power recoveryNetworking Protocols• TCP/IP• IPv4• IPv6• Static IP Address• Dynamic IP Address• Multiple IP Settings• DHCP Client• UPnP Discovery• Bonjour Discovery• Link Aggregation IEEE 802.3ad• Port Trunking (balanced round robin, active backup, balance xor, broadcast, 802.3ad link aggregation LACP,transmit load balancing, adaptive load balancing)• Hash Types IEEE 802.3ad LACP or XOR (Layer 2, Layer3, Layer 4)• Jumbo Frames• Static routes• Secure Shell (SSH)• Simple Network Management Protocol v2, v3• Network Time Protocol (NTPMedia• ReadyDLNA (UPnP DLNA Media Server)• ReadyDLNA streams to any compliant device including Playstation and Xbox• ReadyDLNA mobile clients for remote media streaming (iOS, Android)• ReadyDLNA supported music formats (wav, wma, pcm, ogg, mp3, m4a, flac, aac)• ReadyDLNA supported photo formats (jpg, jpeg)• ReadyDLNA supported video formats (3gp, mp4, wmv, xvid, vob, ts, tivo, mts, mpeg, mpg, mp4, mov, mkv, m4v,m4p, m2t, m2ts, flv, flc, fla, divx, avi, asf)• ReadyDLNA supported playlist formats (pls, m3u)• ReadyNAS Surveillance (free trial, license required) supports over 70 brands and 1600 models of IP cameras• iTunes Server• iTunes supported audio formats (mp3, m4a, m4p, wav, aif)• iTunes supported video formats (m4v, mov, mp4)• iTunes supported playlist formats (m3u, wpl)• TiVo Archiving• Plex Media Server streams to DLNA and Plex clients (mobile, desktop, Android TV, Roku, Samsung & LG TVs)HardwareCPU• ReadyNAS 3312: Intel® Xeon E3-1225v5 3.3GHz Quad Core Processor, Max Turbo Speed 3.7GHz• ReadyNAS 4312S: Intel® Xeon E3-1245v5 3.5GHz Quad Core, Hyper Threaded Processor, Max Turbo Speed 3.9GHz• ReadyNAS 4312X: Intel® Xeon E3-1245v5 3.5GHz Quad Core, Hyper Threaded Processor, Max Turbo Speed 3.9GHzMemory• ReadyNAS 3312: 8GB DDR4 ECC• ReadyNAS 4312S:16GB DDR4 ECC• ReadyNAS 4312X:16GB DDR4 ECC• Memory Expansion: 64GB DDR4• Flash: 256MB for OS• 12 Hot Swappable Drive Bays• Drive Types Supported: SATA/SSD 2.5” or 3.5”• Two eSATA ports• Two USB3.0 ports• Total solution capacity: 120TB w/o expansion 600TB w/ 2 x EDA4000• RR4312X: dual 10GbE copper ports• RR4312S: dual 10GbE SFP+ ports• Quad Gigabit Ethernet ports with link aggregation and failover• LEDs: Power, System, 4 x LAN• Three 80mm fans• Dimensions (DxWxH):707mm x 445mm x 88mm• Weight (diskless): 11.96 kg• Dual 550 watt redundant power supplies• Power cord localized to country of sale• Rackmount sliding rail includedCompliance• ENGR 10049 EST Environmental Stress Test Guideline• ENGR 10045 EVT Engineering Validation Test Guideline• ENGR 10048 CVT Compliance Validation Test Guideline• ENGR 10046 System Validation Test Guideline• ENGR 10023 HALT Accelerated Life Test Guideline• ENGR 10036 CDG Component Derating GuidelineEnvironment• Noise levels: <49dBA @ 25C• Operating Temperature: 0-45C• Operating Humidity: 20-80% relative humidity, non-condensing• Smart Fan• Scheduled Power on/off• UPS Support• Network UPS with SNMP Management• Wake on LANEnvironment• Hard drive disk spin down• Auto-power on (after shutdown)• AC Input Power Voltage 100V to 240V• Power Frequency: 50Hz to 60Hz, Single Phase• Power Consumption (Max/Wake on LAN) RR3312: 210/9.2 watts• Power Consumption (Max/Wake on LAN) RR4312S: 210/9.2 watts• Power Consumption (Max/Wake on LAN) RR4312X: 210/9.2 watts• Certification: FCC Class A, CE Class A, RoHS, VCCI Class A• MTBF: 70,723 hoursAccessories• RTRAY04-10000S: Replacement/additional 3.5” or 2.5” hard drive tray• RFAN04-10000S: Replacement 80mm fan• RRAIL03-10000S: Replacement/additional sliding rack mount rail• RPSU03-10000S: Replacement/additional 550W power supply unit• RMEM04-10000S: Replacement 8GB memory module for RR3312 and RR4312X• RMEM05-10000S:16GByte DDR4 ECC U-DIMM 2Rx8 Memory Expansion, applicable to RR3312, RR4312X andRR4312S• RRSASEXP-10000S: SAS Expansion cardAdd-on Applications• One click installation of add-on applications directly through local GUI• Application available for productivity, media, backup, surveillance, and many others• NETGEAR applications include Surveillance, Photo Sharing, Advanced configuration tools• Partner applications include BitTorrent Sync, Plex, Memeo, DVBlink• Community applications include Transmission, ownCloud, qBittorent, MySQL, VPN server, Syslog, Wordpress,joomla, Media Wiki, and others• Application availability subject to change• Applications may impact overall performance• Software Development Kit (SDK) available for 3rd party developersWarranty and SupportHardware Limited Warranty 5 years*Next-Business-Day (NBD) Replacement YesT echnical Support 90 days free from date of purchase** This product comes with a limited warranty that is valid only if purchased from a NETGEAR authorized reseller, and covers unmodified hardware, fans and internal power supplies – not software or external power supplies, and requires product registration at https:// or using the Insight App within 90 days of purchase; see https:///about/warranty for details. Intended for indoor use only.NETGEAR, the NETGEAR Logo, ReadyNAS, ReadyCLOUD, ReadyNAS Vault, and X-RAID are trademarks of NETGEAR, Inc. in the United States and/or other countries. Other brand names mentioned herein are for identification purposes only and may be trademarks of their respective holder(s). Information is subject to change without notice.© 2022 NETGEAR, Inc. All rights reserved.NETGEAR,Inc.350E.PlumeriaDrive,SanJose,CA95134-1911USA,1-888-NETGEAR(638-4327),E-mail:****************,DS-3312/4312S/4312X -25May22。

斑马技术公司DS8108数字扫描仪产品参考指南说明书

Chapter 1: Getting Started Introduction .................................................................................................................................... 1-1 Interfaces ....................................................................................................................................... 1-2 Unpacking ...................................................................................................................................... 1-2 Setting Up the Digital Scanner ....................................................................................................... 1-3 Installing the Interface Cable .................................................................................................... 1-3 Removing the Interface Cable .................................................................................................. 1-4 Connecting Power (if required) ................................................................................................ 1-4 Configuring the Digital Scanner ............................................................................................... 1-4

Web of Science和InCites API客户端R包说明说明书

Package‘wosr’October12,2022Type PackageTitle Clients to the'Web of Science'and'InCites'APIsDescription R clients to the'Web of Science'and'InCites'<https:///products/data-integration/>APIs,whichallow you to programmatically download publication and citation dataindexed in the'Web of Science'and'InCites'databases.URL https://vt-arc.github.io/wosr/index.htmlBugReports https:///vt-arc/wosr/issuesVersion0.3.0License MIT+ﬁle LICENSEEncoding UTF-8LazyData trueDepends R(>=3.1)Imports httr,xml2,jsonlite,pbapply,utils,toolsRoxygenNote6.1.0Suggests testthat,knitr,rmarkdown,dplyrNeedsCompilation noAuthor Christopher Baker[aut,cre]Maintainer Christopher Baker<************************>Repository CRANDate/Publication2018-11-0205:30:03UTCR topics documented:auth (2)create_ut_queries (3)pull_cited_refs (3)pull_incites (4)pull_related_recs (5)12auth pull_wos (6)pull_wos_apply (8)query_wos (9)query_wos_apply (10)read_wos_data (11)wosr (11)write_wos_data (12)Index13 auth Authenticate user credentialsDescriptionauth asks the API’s server for a session ID(SID),which you can then pass along to either query_wos or pull_wos.Note,there are limits on how many session IDs you can get in a given period of time (roughly5SIDs in a5minute period).Usageauth(username=Sys.getenv("WOS_USERNAME"),password=Sys.getenv("WOS_PASSWORD"))Argumentsusername Your username.Specify username=NULL if you want to use IP-based authenti-cation.password Your password.Specify password=NULL if you want to use IP-based authenti-cation.ValueA session IDExamples##Not run:#Pass user credentials in manually:auth("some_username",password="some_password")#Use the default of looking for username and password in envvars,so you#don t have to keep specifying them in your code:Sys.setenv(WOS_USERNAME="some_username",WOS_PASSWORD="some_password")auth()##End(Not run)create_ut_queries3 create_ut_queries Create a vector of UT-based queriesDescriptionUse this function when you have a bunch of UTs whose data you want to pull and you need to writea series of UT-based queries to do so(i.e.,queries in the form"UT=(WOS:000186387100005ORWOS:000179260700001)").Usagecreate_ut_queries(uts,uts_per_query=200)Argumentsuts UTs that will be placed inside the UT-based queries.uts_per_query Number of UTs to include in each query.Note,there is a limit on how long your query can be,so you probably want to keep this set to around200.ValueA vector of queries.You can feed these queries to pull_wos_apply to download data for eachquery.Examples##Not run:data<-pull_wos( TS=("animal welfare")AND PY=(2002-2003) )queries<-create_ut_queries(data$publication$ut)pull_wos_apply(queries)##End(Not run)pull_cited_refs Pull cited referencesDescriptionPull cited referencesUsagepull_cited_refs(uts,sid=auth(Sys.getenv("WOS_USERNAME"),Sys.getenv("WOS_PASSWORD")),...)4pull_incitesArgumentsuts Vector of UTs(i.e.,publications)whose cited references you want.sid Session identiﬁer(SID).The default setting is to get a fresh SID each time youquery WoS via a call to auth.However,you should try to reuse SIDs acrossqueries so that you don’t run into the throttling limits placed on new sessions....Arguments passed along to POST.ValueA data frame with the following columns:ut The publication that is doing the citing.These are the UTs that you submitted to pull_cited_refs.If one of your publications doesn’t have any cited refs,it will not appear in this column.doc_id The cited ref’s document identiﬁer(similar to a UT).title Roughly equivalent to the cited ref’s title.journal Roughly equivalent to the cited ref’s journal.author The cited ref’sﬁrst author.tot_cites The total number of citations the cited ref has received.year The cited ref’s publication year.page The cited ref’s page number.volume The cited ref’s journal volume.Examples##Not run:sid<-auth("your_username",password="your_password")uts<-c("WOS:000362312600021","WOS:000439855300030","WOS:000294946900020")pull_cited_refs(uts,sid)##End(Not run)pull_incites Pull data from the InCites APIDescriptionImportant note:The throttling limits on the InCites API are not documented anywhere and are difﬁcult to determine from experience.As such,whenever pull_incites receives a throttling error from the server,it uses exponential backoff(with a maximum wait time of45minutes)to determine how long to wait before retrying.Usagepull_incites(uts,key=Sys.getenv("INCITES_KEY"),as_raw=FALSE,...)pull_related_recs5Argumentsuts A vector of UTs whose InCites data you would like to download.Each UTis a15-digit identiﬁer for a given publication.You can specify the UT us-ing only these15digits or you can append the15digits with"WOS:"(e.g.,"000346263300011"or"WOS:000346263300011").key The developer key that the server will use for authentication.as_raw Do you want the data frame that is returned by the API to be returned to you inits raw form?This option can be useful if the API has changed the format ofthe data that it is serving,in which case specifying as_raw=TRUE may avoid anerror that would otherwise occur during pull_incites’s data processing step....Arguments passed along to GET.ValueA data frame where each row corresponds to a different publication.The deﬁnitions for the columnsin this data frame can be found online at the API’s documentation page(see the DocumentLevelMetricsByUT method details for deﬁnitions).Note that the column names are all converted to lowercase bypull_incites and the0/1ﬂag variables are converted to booleans.Also note that not all publica-tions indexed in WoS are also indexed in InCites,so you may not get data back for some UTs.Examples##Not run:uts<-c("WOS:000346263300011","WOS:000362312600021","WOS:000279885800004","WOS:000294667500003","WOS:000294946900020","WOS:000412659200006")pull_incites(uts,key="some_key")pull_incites(c("000346263300011","000362312600021"),key="some_key")##End(Not run)pull_related_recs Pull related recordsDescriptionPull the records that have at least one citation in common with a publication of interest.Usagepull_related_recs(uts,num_recs,editions=c("SCI","SSCI","AHCI","ISTP","ISSHP","BSCI","BHCI","IC","CCR","ESCI"),sid=auth(Sys.getenv("WOS_USERNAME"),Sys.getenv("WOS_PASSWORD")),...)Argumentsuts The documents whose related records you want to pull.num_recs Number of related records to pull for each UT.This value must be<=100.editions Web of Science editions to query.Possible values are listed here.sid Session identiﬁer(SID).The default setting is to get a fresh SID each time you query WoS via a call to auth.However,you should try to reuse SIDs acrossqueries so that you don’t run into the throttling limits placed on new sessions....Arguments passed along to POST.ValueA data frame with the following columns:ut The publications that you passed into pull_related_recs.If one of your publications doesn’t have any related records,it won’t appear here.related_rec The publication that is related to ut.rec_num The related record’s ordering in the result set returned by the API.Records that share more citations with your UTs will have smaller rec_num s.Examples##Not run:sid<-auth("your_username",password="your_password")uts<-c("WOS:000272877700013","WOS:000272366800025")out<-pull_related_recs(uts,5,sid=sid)##End(Not run)pull_wos Pull data from the Web of ScienceDescriptionpull_wos wraps the process of querying,downloading,parsing,and processing Web of Science data.Usagepull_wos(query,editions=c("SCI","SSCI","AHCI","ISTP","ISSHP","BSCI","BHCI","IC","CCR","ESCI"),sid=auth(Sys.getenv("WOS_USERNAME"),Sys.getenv("WOS_PASSWORD")),...)Argumentsquery Query string.See the WoS query documentation page for details on how to writea query as well as this list of example queries.editions Web of Science editions to query.Possible values are listed here.sid Session identiﬁer(SID).The default setting is to get a fresh SID each time you query WoS via a call to auth.However,you should try to reuse SIDs acrossqueries so that you don’t run into the throttling limits placed on new sessions....Arguments passed along to POST.ValueA list of the following data frames:publication A data frame where each row corresponds to a different publication.Note that each publication has a distinct ut.There is a one-to-one relationship between a ut and each of the columns in this table.author A data frame where each row corresponds to a different publication/author pair(i.e.,a ut/author_no pair).In other words,each row corresponds to a different author on a publica-tion.You can link the authors in this table to the address and author_address tables to get their addresses(if they exist).See example in FAQs for details.address A data frame where each row corresponds to a different publication/address pair(i.e.,a ut/addr_no pair).In other words,each row corresponds to a different address on a publication.You can link the addresses in this table to the author and author_address tables to see which authors correspond to which addresses.See example in FAQs for details.author_address A data frame that speciﬁes which authors correspond to which addresses on a given publication.This data frame is meant to be used to link the author and address tables together.jsc A data frame where each row corresponds to a different publication/jsc(journal subject cate-gory)pair.There is a many-to-many relationship between ut’s and jsc’s.keyword A data frame where each row corresponds to a different publication/keyword pair.These are the author-assigned keywords.keywords_plus A data frame where each row corresponds to a different publication/keywords_plus pair.These keywords are the keywords assigned by Clarivate Analytics through an automated process.grant A data frame where each row corresponds to a different publication/grant agency/grant ID triplet.Not all publications acknowledge a speciﬁc grant number in the funding acknowledge-ment section,hence the grant_idﬁeld can be NA.doc_type A data frame where each row corresponds to a different publication/document type pair. Examples##Not run:sid<-auth("your_username",password="your_password")pull_wos("TS=(dog welfare)AND PY=2010",sid=sid)8pull_wos_apply #Re-use session ID.This is best practice to avoid throttling limits:pull_wos("TI=\"dog welfare\"",sid=sid)#Get fresh session ID:pull_wos("TI=\"pet welfare\"",sid=auth("your_username","your_password"))#It s best to see how many records your query matches before actually#downloading the data.To do this,call query_wos before running pull_wos:query<-"TS=((cadmium AND gill*)NOT Pisces)"query_wos(query,sid=sid)#shows that there are1,611matching publicationspull_wos(query,sid=sid)##End(Not run)pull_wos_apply Run pull_wos across multiple queriesDescriptionRun pull_wos across multiple queriesUsagepull_wos_apply(queries,editions=c("SCI","SSCI","AHCI","ISTP","ISSHP","BSCI","BHCI","IC","CCR","ESCI"),sid=auth(Sys.getenv("WOS_USERNAME"),Sys.getenv("WOS_PASSWORD")),...)Argumentsqueries Vector of queries to issue to the WoS API and pull data for.editions Web of Science editions to query.Possible values are listed here.sid Session identiﬁer(SID).The default setting is to get a fresh SID each time you query WoS via a call to auth.However,you should try to reuse SIDs acrossqueries so that you don’t run into the throttling limits placed on new sessions....Arguments passed along to POST.ValueThe same set of data frames that pull_wos returns,with the addition of a data frame named query.This data frame frame tells you which publications were returned by a given query.query_wos9 Examples##Not run:queries<-c( TS="dog welfare" , TS="cat welfare" )#we can name the queries so that these names appear in the queries data#frame returned by pull_wos_apply():names(queries)<-c("dog welfare","cat welfare")pull_wos_apply(queries)##End(Not run)query_wos Query the Web of ScienceDescriptionReturns the number of records that match a given query.It’s best to call this function before calling pull_wos so that you know how many records you’re trying to download before attempting to do so.Usagequery_wos(query,editions=c("SCI","SSCI","AHCI","ISTP","ISSHP","BSCI","BHCI","IC","CCR","ESCI"),sid=auth(Sys.getenv("WOS_USERNAME"),Sys.getenv("WOS_PASSWORD")),...)Argumentsquery Query string.See the WoS query documentation page for details on how to writea query as well as this list of example queries.editions Web of Science editions to query.Possible values are listed here.sid Session identiﬁer(SID).The default setting is to get a fresh SID each time you query WoS via a call to auth.However,you should try to reuse SIDs acrossqueries so that you don’t run into the throttling limits placed on new sessions....Arguments passed along to POST.ValueAn object of class query_result.This object contains the number of publications that are re-turned by your query(rec_cnt),as well as some info that pull_wos uses when it calls query_wos internally.10query_wos_apply Examples##Not run:#Get session ID and reuse it across queries:sid<-auth("some_username",password="some_password")query_wos("TS=(\"dog welfare\")AND PY=(1990-2007)",sid=sid)#Finds records in which Max Planck appears in the address field.query_wos("AD=Max Planck",sid=sid)#Finds records in which Max Planck appears in the same address as Mainzquery_wos("AD=(Max Planck SAME Mainz)",sid=sid)##End(Not run)query_wos_apply Run query_wos across multiple queriesDescriptionRun query_wos across multiple queriesUsagequery_wos_apply(queries,editions=c("SCI","SSCI","AHCI","ISTP","ISSHP","BSCI","BHCI","IC","CCR","ESCI"),sid=auth(Sys.getenv("WOS_USERNAME"),Sys.getenv("WOS_PASSWORD")),...)Argumentsqueries Vector of queries run.editions Web of Science editions to query.Possible values are listed here.sid Session identiﬁer(SID).The default setting is to get a fresh SID each time you query WoS via a call to auth.However,you should try to reuse SIDs acrossqueries so that you don’t run into the throttling limits placed on new sessions....Arguments passed along to POST.ValueA data frame which lists the number of records returned by each of your queries.read_wos_data11Examples##Not run:queries<-c( TS="dog welfare" , TS="cat welfare" )query_wos_apply(queries)##End(Not run)read_wos_data Read WoS dataDescriptionReads in a series of CSVﬁles(which were written via write_wos_data)and places the data in an object of class wos_data.Usageread_wos_data(dir)Argumentsdir Path to the directory where you wrote the CSVﬁles.ValueAn object of class wos_data.Examples##Not run:sid<-auth("your_username",password="your_password")wos_data<-pull_wos("TS=(dog welfare)AND PY=2010",sid=sid)#Write files to working directorywrite_wos_data(wos_data,".")#Read data back into Rwos_data<-read_wos_data(".")##End(Not run)wosr wosrDescriptionwosr12write_wos_data write_wos_data Write WoS dataDescriptionWrites each of the data frames in an object of class wos_data to its own csvﬁle.Usagewrite_wos_data(wos_data,dir)Argumentswos_data An object of class wos_data,created by calling pull_wos.dir Path to the directory where you want to write theﬁles.If the directory doesn’t yet exist,write_wos_data will create it for you.Note,this directory cannotalready have WoS dataﬁles in it.ValueNothing.Files are written to disk.Examples##Not run:sid<-auth("your_username",password="your_password")wos_data<-pull_wos("TS=(dog welfare)AND PY=2010",sid=sid)#Write files to working directorywrite_wos_data(wos_data,".")#Write files to"wos-data"dirwrite_wos_data(wos_data,"wos-data")##End(Not run)Indexauth,2,4,6–10create_ut_queries,3GET,5POST,4,6–10pull_cited_refs,3pull_incites,4pull_related_recs,5pull_wos,2,6,8,9,12pull_wos_apply,3,8query_wos,2,9query_wos_apply,10read_wos_data,11wosr,11wosr-package(wosr),11write_wos_data,11,1213。

第四版钱晓捷课后习题答案

⑦主板芯片组是主板的核心部件，它提供主板上的关键逻辑电路。
⑧MASM是微软开发的宏汇编程序。
⑨指令的处理过程。处理器的“取指—译码—执行周期”是指处理器从主存储器读取指令（简称取指），翻译指令代码的功能（简称译码），然后执行指令所规定的操作（简称执行）的过程。
⑩机器语言层，即指令集结构。
（学生很多认为是：层。前4章主要涉及汇编语言，但本书还有很多处理器原理等内容）
（4）DOS主要支持两种可执行文件，它们的扩展名分别是___________和___________。
（5）英文缩写ISA常表示PC机工业标准结构（Industry Standard Architecture）总线，也表示指令集结构，后者的英文原文是___________。
（6）Windows的文件夹对应的专业术语是___________。
题外话：大家可以通过阅读相关资料、查询互联网获得更加详细的发展情况。可以考虑组织成一篇或多篇论文。
〔习题
区别如下概念：助记符、汇编语言、汇编语言程序和汇编程序。
〔解答〕
助记符：人助记符。
汇编语言：用助记符表示的指令以及使用它们编写程序的规则就形成汇编语言。
外部设备：外部设备是指可与微机进行交互的输入（Input）设备和输出（Output）设备，也称I/O设备。I/O设备通过I/O接口与主机连接。
总线：互连各个部件的共用通道，主要含数据总线、地址总线和控制总线信号。
〔习题
什么是通用微处理器、单片机（微控制器）、DSP芯片、嵌入式系统？
〔解答〕
通用微处理器：适合较广的应用领域的微处理器，例如装在PC机、笔记本电脑、工作站、服务器上的微处理器。
〔习题
英特尔公司最新Intel 80x86处理器是什么？请通过查阅相关资料（如英特尔公司网站），说明其主要特点和采用的新技术。

paste or drop activation code here -回复

paste or drop activation code here -回复[paste or drop activation code here]Activation codes, also known as serial keys or product keys, play a crucial role in the software industry. They are alphanumeric strings provided by software developers to authenticate and validate legitimate copies of their programs. Activation codes are unique to each software package and are required to unlock and activate all the features and functionalities of the software.In this article, we will explore the importance of activation codes, how they work, and why they are necessary. We will also discuss the various methods used to obtain activation codes and the potential issues that may arise when using them.1. What are Activation Codes?Activation codes are unique strings of characters provided by software developers to validate the authenticity of the software being installed. These codes serve as a proof of purchase and are necessary to activate and use the software legally. Activation codes are usually sent together with the software package or provided through email upon purchase.2. How do Activation Codes Work?When you install a software program for the first time, you are usually prompted to enter the activation code. The code is then verified by the software's activation server to confirm its validity. If the code is valid, the software is activated, allowing you to access all the features and functionalities. On the other hand, if the code is invalid or has already been used, the activation process will fail.3. Why are Activation Codes Necessary?Activation codes serve multiple purposes for software developers. Firstly, they prevent unauthorized usage and distribution of their software. By requiring users to enter a valid activation code, developers can ensure that only paid users can access their software, protecting their intellectual property rights.Secondly, activation codes also enable software developers to track and manage their user base. Activation codes can be linked to specific users or computers, allowing developers to monitor software installations, control updates and upgrades, and provide technical support if needed.4. Obtaining Activation CodesThere are different methods through which you can obtain activation codes. The most common way is by purchasing the software directly from the official website or authorized resellers. In this case, the activation code is provided when you make the purchase.Some software programs offer a trial version with limited features. To unlock the full version, you need to purchase an activation code from the developer. Activation codes can also be obtained through promotions, contests, or special offers provided by the software developers.5. Potential Issues and SolutionsWhile activation codes serve important purposes, they can sometimes cause inconvenience or issues for users. For example, if you lose your activation code or accidentally delete the email containing it, you may not be able to reinstall and reactivate the software. In such cases, it is important to contact the software developer's support team for assistance.If you encounter any issues with the activation process, such as invalid or expired codes, it is crucial to contact the softwaredeveloper or vendor immediately. They will be able to provide you with a solution or a new activation code to resolve the problem.In conclusion, activation codes are essential in the software industry to validate the authenticity of purchased software. They serve as proof of purchase and enable software developers to protect their intellectual property. While they may come with certain inconveniences, such as potential loss or expiration, timely communication with the software developer can help resolve any issues encountered during the activation process.。

PROMAFOUR 自凝钙硅酸板产品说明书

Supersedes : 0 / 0 / 01.1. Product identifierTrade name:PROMAFOUR®Identification of the product:Self-supporting calcium silicate board.Type of product:Article.1.2. Relevant identified uses of the substance, mixture or article and uses advised against Use:High temperature insulation.1.3. Details of the supplier of the safety data sheetCompany identification:Promat UK LtdThe Sterling CentreEastern Road - BerkshireRG12 2TD Bracknell UNITED KINGDOMTel.: +44 (0) 1344 381400Fax: +44 (0) 1344 3814011.4. Emergency telephone numberEmergency phone nr:+44 (0) 1344 381 400Symptoms relating to use:For the installed product in its final application: no hazards known.During machining the product (drilling, cutting, sanding, etc.), airborne dust can bereleased.- Inhalation:As with most types of nuisance dust, excessive inhalation of dust may causeirritation of the bronchial tubes.The handling and machining of this product may lead to the release of quartzcontaining dust. The inhalation of dust containing quartz, in particular the fine (respirable) dust fraction, in high concentrations or over a prolonged period of timemay lead to lung disease (silicosis) and an increased risk of lung cancer.Long term hazards: see section 11.- Skin contact:Prolonged skin contact may lead to skin irritation for sensitive persons.- Eye contact:Eye contact with dust may lead to transient eye irritation or inflammation.- Ingestion:Not expected to present a significant ingestion hazard under anticipated conditionsof normal use.2.1. Classification of the substance or mixtureClassification EC 67/548 or EC 1999/45This product is classified as not hazardous.Hazard Class and Category Code Regulation EC 1272/2008 (CLP)This product is classified as not hazardous.2.2. Label elementsLabelling EC 67/548 or EC 1999/45Supersedes : 0 / 0 / 0No labelling required.Labelling Regulation EC 1272/2008 (CLP)No labelling required.2.3. Other hazardsNone under normal conditions.Components:This article is classified as not hazardous.This product is a manufactured article, not a substance nor a preparation.Substance name Contents CAS No EC No Annex No Ref REACH ClassificationWollastonite:13983-17-0237-772-5----------Not classified. (DSD/DPD)----------------------------------Not classified. (GHS)Cellulose fibers:65996-61-4265-995-8----------Not classified. (DSD/DPD)----------------------------------Undefined. (GHS)Quartz (SiO2):14808-60-7238-878-4----------Not classified. (DSD/DPD)----------------------------------Not classified. (GHS)Crystalline calcium silicate hydrate:1344-95-2215-710-8----------Not classified. (DSD/DPD)----------------------------------Undefined. (GHS)Vermiculite:1318-00-9---------------Not classified. (DSD/DPD)----------------------------------Not classified. (GHS)4.1. Description of first aid measuresFirst aid measures- Inhalation:Remove to fresh air and drink water.- Skin contact:Rinse the skin with water.- Eye contact:Do not rub the eye. Rinse the eye out with plenty of clean water for at least 15minutes. If eye irritation or inflammation persists, seek medical advice.- Ingestion:Drink water.4.2. Most important symptoms and effects, both acute and delayedSee sections 7 and 8.4.3. Indication of any immediate medical attention and special treatment neededNo data available.5.1. Extinguishing mediaSuitable extinguishing media:All extinguishing media can be used.5.2. Special hazards arising from the substance or mixtureSupersedes : 0 / 0 / 0Nothing to report.5.3. Advice for fire-fightersFlammable class:The product is non-combustible.Protection against fire:Do not enter fire area without proper protective equipment, including respiratoryprotection.6.1. Personal precautions, protective equipment and emergency proceduresPersonal precautions:Minimize generation of dust. Avoid breathing dusts. Avoid eye and skin contact.Use recommended respiratory protection.6.2. Environmental precautionsEnvironmental precautions:Prevent spread of dust.6.3. Methods and material for containment and cleaning upMethods and material for containment:Use closed containers to avoid dust release.Clean up methods:Shovel up small pieces. Dampen down any dust before putting into appropriateskips.6.4. Reference to other sectionsSee sections 7 and 8.7.1. Precautions for safe handlingPersonal protection:Dust, generated during machining and processing must be exhausted and theregulatory occupational exposure limits (workplace exposure limits in UK) for totaland respirable dust and respirable quartz dust must be respected.Use always respiratory protective equipment when exposures are likely or can beforeseen to exceed the Occupational Exposure Limits or Workplace ExposureLimits in UK (refer to local regulations).Collect dust with a vacuum cleaner or soak with water before sweeping up. Technical protective measures:Work in a well ventilated areaUse tools with appropriate dust exhaust equipment.7.2. Conditions for safe storage, including any incompatibilitiesStorage:Store in dry, covered and frost proof area.7.3. Specific end use(s)Fire protection in buildings. High temperature insulation.Supersedes : 0 / 0 / 08.1 Control parametersOccupational Exposure Limits:When machining boards (drilling, cutting, sanding, etc.), respect Occupational (UK: Workplace Exposure Limits)Exposure Limits (OEL) or Workplace Exposure Limits (WEL in the UK) for inhalableand respirable dust and for respirable quartz dust.Check the latest Occupational Exposure Limits (OEL) or Workplace ExposureLimits (WEL in the UK) for airborne contaminants that are applicable in yourcountry.Typical Occupational Exposure Limits or Workplace Exposure Limits in the UK (8hrs TWA) and Ireland on the date of issue of this document are:Control parameters for airborn:- Quartz dust (CAS number: 14808 - 60 - 7):contaminants - Respirable: 0.1 mg/m³(UK) - 0.05 mg/m³ (IE)- Particles not otherwise classified or regulated (nuisance dust)- Inhalable: 10 mg/m³.- Respirable: 4 mg/m³.8.2 Occupational exposure controls8.2.1 General protection controls- Industrial hygiene:Ensure vacuum dust exhaust with correct filter when using motorised machiningtools.8.2.2. Individual protection controls- Respiratory protection:Avoid breathing dusts.Use appropriate respiratory equipment when exposures are likely or can beforeseen to exceed the Occupational Exposure Limits or Workplace ExposureLimits for the UK (e.g. for exposures up to 10 times the OEL (WEL) use at least aP2 type duct mask. For higher exposure, use a P3 type mask).- Skin protection:Avoid contact with skin.Use working clothes and gloves to protect against mechanical injury and direct skincontact.- Eye protection:Avoid contact with eyes.Use safety glasses whenever tools are used and dusts are produced.- Ingestion:When using, do not eat, drink or smoke.• Appearance:Board (solid)• Physical state at 20 °C:Solid.• Colour:White-beige• Odour:None.• pH value:10 - 11• Flammability:Non flammable.• Density:ca. 950 kg/m3• Solubility in water:Insoluble.• Other properties:Information on other physical and chemical properties, as listed in the section 9.1 ofAnnex II of the Commission Regulation EU 453/2010 of 20 May 2010 is notavailable10.1. ReactivitySupersedes : 0 / 0 / 0Stability and reactivity:Stable under normal conditions.10.2. Chemical stabilityChemical stability:Stable under normal conditions of storage, handling and use.10.3. Possibility of hazardous reactionsHazardous reactions:None.Hazardous properties:None10.4. Conditions to avoidConditions to avoid:None known.10.5. Incompatible materialsMaterials to avoid:Strong acids.10.6. Hazardous decomposition productsNone known.11.1. Information on toxicological effectsToxicity information:No data available.Acute toxicity:No acute toxicity has been reported, apart from some exceptional cases oftransient eye irritation or inflammation, skin irritation or irritation of the mucosae (throat, bronchial tubes) by excessive exposure to dust.11.2 Additional information:• On product:The inhalation of quartz containing dust, in particular the fine dust fraction(respirable size), in high concentrations or over repeated or prolonged periods oftime can be hazardous to health and may lead to chronic lung disease and anincreased risk of lung cancer. This risk will be minimal if correct working practicesare observed and applied. (Refer to Section 8). However, for this product, withexposure assessments performed by accredited European laboratories usingreference workplace monitoring methods, any quartz levels in the respirable dustwere below the detection limit.According to the International Agency for Research on Cancer (IARC MonographVolume 100C - 2012) “Crystalline silica inhaled in the form of quartz or cristobaliteis carcinogenic to humans(Group 1).”12.1. ToxicityNo known effects.12.2. Persistence - degradabilitySupersedes : 0 / 0 / 0No data available.12.3. Bioaccumulative potentialNo data available.12.4. Mobility in soilNo data available.12.5. Results of PBT and vPvB assessmentNo data available.12.6. Other adverse effectsNo information available.Ecological effects information:No data available.13.1. Waste treatment methodsHandle as construction industry waste.13.2. GeneralProduct disposal:Dispose in a safe manner in accordance with local/national regulations. Packaging disposal:Dispose according to local legislation.EWC (European Waste Catalogue) -:170107N°.General information:Not classified as dangerous in the meaning of transport regulations.Symbol(s):None.R Phrase(s):None.S Phrase(s):None.Further information:None.DISCLAIMER OF LIABILITYThe information in this SDS was obtained from sources which we believe are reliable. However, the information is provided without any warranty, express or implied, regarding its correctness. The conditions or methods of handling, storage, use or disposal of the product are beyond our control and may be beyond our knowledge. For this and other reasons, we do not assume responsibility and expressly disclaim liability for loss, damage or expense arising out of or in any way connected with the handling, storage, use or disposal of the product. This SDS was prepared and is to be used only for this product. If the product is used as a component in another product, this SDS information may not be applicable.This data sheet and the information it contains is not intended to supersede any terms or conditions of sale and does notSupersedes : 0 / 0 / 0constitute a specification. Nothing contained herein is to be construed as a recommendation for use in violation of any patent or applicable laws or regulations.The contents and format of this SDS are in accordance with REGULATION (EC) No 1907/2006 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCILEnd of document。

IO-Link线性传感器使用手册 NOVOtechnik SIEDLE GRUPPE 版本00 20

Gebrauchsanleitung IO-Link für Lineare Sensoren User manual IO-Link for Linear Sensors NOVOtechnik SIEDLE GRUPPEContentIO-Link 2 1IODD Files 2 2Device specification 2 3Process data 2 4Parameter Data 34.1Identification data 34.2Device parameter data 34.2.1Device Access Locks 44.2.2Profile Characteristics 44.2.3PD Input Descriptor 44.2.4Application Specific Tag 44.2.5Null point offset 44.2.6Averaging 44.2.7Resolution 44.2.8Mode 44.2.9Error Messages while Parametrization 55Events: Warnings and Errors 5 6Storage of Parameter Data 5 7Factory Reset 5 8Document Changes 5IO-LinkThis document reflects the Novotechnik sensor protocol implementation of the standard IO-Link protocol.A basic knowledge of the IO-link interface is required for a proper understanding of this document.Most of the definitions made are according to the IO-Link Standard specifications.For making use of all the features that these specifications offer, a knowledge about them is absolutely necessary.The linear sensors supports the IO-Link Smart Sensor Profile specifications (Edition 2011) according IEC 61131-9.The IO-Link interface is a point-to-point connection based on a UART protocol with 24 V pulse modulation. Data isexchanged cyclically between the IO-Link Master and the IO-Link device using the IO-Link protocol. The protocol con-tains process data and also requested additional data for state determination or configuration.1 IODD FilesFor integration in a common IO-Link projecting tool, IO Device Description (*.IODD) files are provided. These files canbe downloaded from the Novotechnik Web Site, see Downloads/Operating manuals where also this document can befound.IODD see file Product series_IODD_model. zip2 Device specification3 Process dataThe process data are transmitted cyclically. The sensor outputs a signed integer value via the IO-Link interface, e.g.:32 bits = position or 48 bits = 32 bits position and 16 bits speedThe absolute position relates to the factory default null point.Resolution of position data: 1 or 5 μmResolution of speed data: 0.1 or 0.5 mm/sThe factory default null point can be shifted via the parameter “Null point offset".The validity of the process data 0xF000 FF10 ... 0x7FFF FFF0 is confirmed by a PD Valid Infomation (process data valid).In case of an error, if no position marker or magnet can be detected, the error value 0x7FFF FFFC is put out and the data is labeled as invalid (PD Invalid Bit).Hint: The IO-Link functionality PD Invalid Bit is handled differently by different IO-Link masters (refer to the manual for the respective master).4 Parameter DataDevice parameters are exchanged non-cyclically and on request of the IO-Link master. Parameter values can be written into the sensor (Write) or device states can be read out of the sensor (Read) by means of the "On-Request Data Ob-jects".4.1 Identification data4.2 Device parameter data*) changeable during operation.Only TP1/TH1 series: Process data are invalid until renewed output of valid process data after 10 ms**) changeable during operation but only effective after Power Off / Power On4.2.1 Device Access LocksWith this parameter, it is possible to active or deactivate the function of the parameter manager.In order to lock the parameter manager, bit #1 of the 2 byte value must be set to "1" (locked), to unlock bit #1 is set to "0".4.2.2 Profile CharacteristicsThis parameter indicates which profile is supported by the IO-Link device.The sensor supports the Smart Sensor Profile:Profile Identifier -> DeviceProfileID: 0x0001 "Smart Sensor Profile"Profile Identifier -> FunctionClassID: 0x8000 "Device Identification"Profile Identifier -> FunctionClassID: 0x8002 "ProcessDataVariable“Profile Identifier -> FunctionClassID: 0x8003 "Sensor Diagnosis"4.2.3 PD Input DescriptorThis parameter describes the composition of the process data variables used. The sensor processes the process data variable as follows:0x000E Subindex 0:0x03 -> Data type = IntegerT 0x20 -> Data size = 32 bits 0x00 -> Offset = 0 bit0x30 -> Data size = 48 bitsOnly TP1/TH1 series:0x40 -> Data size = 64 bits0x60 -> Data size = 96 bits4.2.4 Application Specific TagThis parameter makes it possible to assign the IO-Link device an arbitrary, 32-byte string. This can only be used by the customer for application-specific identification and applied in the parameter manager. The entire object is accessed via subindex 0.4.2.5 Null point offsetSame as process data value, this parameter is a signed 32-bits decimal value.The null point offset can be done without magnet or position marker. The value is added to the factory default null point as a simple offset: maximum value corresponding sensor length.Access takes place via subindex 0.4.2.6 AveragingThe behavior of the output filter can be adjusted for smoothing the signal noise of the output signal. This allows to achieve a better repeatability.0 without moving average1 (or 2, 3, 4, 5) moving average across2 (or 4, 8, 16, 32) values4.2.7 ResolutionThe setting of the resolution can be changed (see IODD: 0 = 1 µm, 1 = 5 µm). When changing the resolution of the position signal from 1 to 5 µm, the resolution of the speed signal changes from 0.1 to 0.5 mm/s and vice versa.4.2.8 ModeThe ordered product model can be configured regarding number of position markers and measured variables:mode 0 = 1x positionmode 1 = 1x position + 1x speedOnly TP1/TH1 series:mode 2 = 2x positionmode 3 = 2x position + 2x speedmode 4 = 3x position4.2.9 Error Messages while ParametrizationThe following IO-Link error messages are stored if parametrization fails:5 Events: Warnings and ErrorsWhen an event occurs, the sensor sets the so-called "Event Flag". During an event is read by the master, no parameter data can be exchanged6 Storage of Parameter DataThe device parameters that have been set by the configuration tool and IODD are stored non-volatile.They can be changed and stored again in the sensor any time via the configuration tool or by the PLC.The device acknowledges any change of the parameters to the master.7 Factory ResetResetting to factory default settings is done with command 0x80 in index 0x0002 subindex 00.8 Document Changes。

chattr的参数

chattr的参数chattr是一个Linux下的命令，可以用来修改文件系统对象的特性，包括添加文件锁、设置只读属性、设置不可变属性等等。

该命令可以帮助管理员进一步控制文件系统，增加系统的安全性。

当我们打开一个文件时，系统会分配一些属性，比如读/写/执行权限、文件所有者、时间戳等等。

而使用chattr，用户可以对这些属性进行更改，以满足特定的系统需求。

本文将详细介绍chattr命令，其参数，以及如何使用它来改变文件系统对象的特性。

chattr的语法chattr命令的使用非常简单，其语法如下：chattr [选项] 文件名该命令有一些选项，可以用来修改文件系统对象的特性。

下面我们将介绍chattr命令的各个选项以及其用途。

chattr的参数chattr命令主要包括以下参数：1. -i 表示设置文件不可被修改，即设置文件的不可变属性。

使用该选项将会把文件设置为只可读状态，不能被删除或者修改。

如果想要修改该文件，需要在命令行中使用chattr -i 选项来解除不可变属性。

2. -a 表示设置文件为只追加模式。

当文件设置了该属性之后，不允许用户在其中任意位置插入或删除数据，只能在末尾追加数据。

这在一些日志文件或记录文件中非常有用。

3. -d 表示设置目录不能被删除。

如果某个目录设置了该属性，就不能再通过rm -r命令删除该目录（注意rm -r命令会删除目录及其所有子目录和文件）。

要删除该目录，需要先解除该属性。

同时，该选项也可以用来保护重要的目录，避免被误删。

4. -R 表示递归修改目录下的所有文件。

5. -V 表示打印详细信息。

执行该命令时，系统会显示每个文件被修改的属性信息。

6. +i 表示解除文件的不可变属性。

该选项可以用来取消-i选项的效果，让用户可以修改该文件。

7. +a 表示取消文件的只追加模式。

该选项取消-a选项的效果，允许用户在任意位置插入或删除文件内容。

DSC-RX100M3 数字单反摄影机用户指南说明书

Step 17. Enter Alarm 1 Enable/Disable Submenu Press d to display flashing DSBL / ENBL .Step 18. Enable Alarm 1 SubmenuIf flashing ENBL is displayed, press a , if DSBL is displayed,press b until ENBL is displayed, then press d to store and go to the next menu item.Step 19. Select the Deviation Control Type Submenu Press d . If flashing _DEV Deviation is displayed press a ,otherwise press b until flashing _DEV is shown. Now press d to store and go to next menu item.Step 20. Select the Latched Type SubmenuPress d . If flashing UNLT Unlatched is displayed press a ,otherwise press b until UNLT is displayed.Press d to store and advance to next menu item.Step 21. Select the Normally Open Type of Contact Closure SubmenuPress d . If flashing N.o.Normally Open is displayed,press a , otherwise press b until N.o.is displayed. Press d to store and advance to next menu item.Step 22. Select the Above Type of Active Submenu Press d . If flashing ABoV Above is displayed, press a ,otherwise press b until ABoV is displayed. Press d to store and advance to next menu item.Step 23. Enable Alarm 1 at Power On (A.P.oN )Press d . If flashing ENBL is displayed, press a , otherwise press b until ENBL is displayed. Press d to store and advance to next menu item.Step 24. Enter Alarm 1 High SubmenuPress a twice to skip ALR.L Alarm 1 Low value. ALR.L is for below & ALR.H for above.Step 25. Set the Alarm 1 High value (ALR.H )Press d . Press b or c until value to set the display to 002.0. Press d to save.Step 26. Enter the Alarm 2 MenuThe display will show ALR2the top menu for Alarm 2.Repeat steps from 17 to 25 to set for Alarm 2 the same conditions as for Alarm 1.Step 29. Configuration of Display Color Selection Press a until the COLR Display Color Selection Menu appears on the Display. Configure COLR as N.CLR /GRN (green), 1.CLR / RED (red), 2.CLR /AMBR (amber). Please refer to the operator’s manual if needed.For color change on Setpoints refer to Owners Manual Section 2.MQS4003/0611SPECIFICATIONSENSOR SPECIFICATIONSRelative Humidity Accuracy/Range:±2% for 10 to 90%±3% for 5 to 10% and 90 to 95%±4% for 0 to 5% and 95 to 100%Non-linearity : ±3%Hysteresis : ±1% RH Response Time :8 sec, tau 63%Repeatability : ±0.1%Resolution : 0.1%, 12bitTemperature Accuracy/Range*:±0.5°C for 5 to 45°C (±1°F for 41 to 113°F); up to ±1.5°C for -40 to 5°C and 45 to 124°C (up to ±2.7°F for -40 to 41°F and 113 to 257°F)*NOTE:extended temp range is for Probe only, the Controller’s operating temp is 0-50°CResponse Time : 5 to 30 sec, tau 63%Repeatability : ±0.1°C Resolution : 0.1°C, 14 bit METER SPECIFICATIONS Display:4-digit, 9-segment LED,•10.2 mm (0.40"): DPiTH-i8DV Dual Vertical •10.2 mm (0.40") and 21 mm (0.83")DPiTH-i8DH Dual HorizontalRed, green, and amber programmable colors for setpoint and temperature units.Output 1†:Relay 250 Vac @ 3 A Resistive Load,SSR, Pulse Output 2†:Relay 250 Vac @ 3 A Resistive Load,SSR, Pulse †Only with -AL Limit Alarm optionOptions:Communication RS-232 / RS-485 or 10BaseT or Excitation:24 Vdc @ 25 mAExc. n ot available for Low Power OptionLine Voltage/Power:90 - 240 Vac ±10%,50 - 400 Hz*, or 110 - 375 Vdc, 5 W* No CE compliance above 60 HzLow Voltage Power Option:20 - 36 Vdc or 24Vac** ±10%,4 W**Units can be powered safely with 24 Vac but No Certification for CE/UL are claimed.Dimensions:Dual Horizontal: 48H x 96W x 127D mm (1.89 x 3.78 x 5")Dual Vertical: 48W x 96H x 127D mm (1.89 x 3.78 x 5")Weight:295 g (0.65 lb)Approvals:CE per EN61010-1:2001It is the policy of OMEGA to comply with all worldwide safety and EMC/EMI regulations that apply.OEMGA is constantly pursuing certification of its products to the European New Approach Directives.OMEGA will add the CE mark to every appropriate device upon certification.The information contained in this document is believed to be correct, but OMEGA Engineering,Inc.accepts no liability for any errors it contains, and reserves the right to alter specifications without notice.TRADEMARK NOTICE:®,®,, andare Trademarks ofOMEGA ENGINEERING, INC.®This Quick Start Reference provides informationon setting up your instrument for basic operation.The latest complete Communication and OperationalManual as well as free Software and ActiveX Controlsare available at /specs/iseries oron the CD-ROM enclosed with your shipment. SAFETY CONSIDERATIONThe instrument is a panel mount device protected in accordance with EN61010-1:2001. Remember that the unit has no power-on switch. Building installation should include a switch or circuit-breaker that must be compliant to IEC 947-1 and 947-3.SAFETY:•Do not exceed voltage rating on the label located onthe top of the instrument housing.•Always disconnect power before changing signal andpower connections.•Do not use this instrument on a work bench withoutits case for safety reasons.•Do not operate this instrument in flammable orexplosive atmospheres.•Do not expose this instrument to rain or moisture. EMC:•Whenever EMC is an issue, always use shielded cables.•Never run signal and power wires in the same conduit.•Use signal wire connections with twisted-pair cables.•Install Ferrite Bead(s) on signal wire close to theinstrument if EMC problems persist.MOUNTINGPanel Mounting Instruction:ing the dimensions from the panel cutout shown inexploded views, cut an opening in the panel.45mm +.61/-.00x 92mm +.81/-.00with R 1.5, 4 places(1.772”+.024/-.000x 3.622”+.032/-.000with R 0.06”, 4 places)Panel thickness: 6.4mm (0.25”) max / 0.8mm (0.03”) min.2. Remove sleeve from the rear of the case by removingthumbnuts.3.Insert the unit into the opening from the front of the panel, sothe gasket seals between the bezel and the front of the panel.4.Slip the sleeve over the rear of the case.5.Tighten the thumbnuts to hold the unit firmly in the panel.。

TableTextServiceYi

VK_U, 0 = INPUT // U
VK_V, 0 = INPUT // V
VK_W, 0 = INPUT // W
VK_X, 0 = INPUT // X
"cip"=""
"cit"=""
"cix"=""
"co"=""
"cop"="""
"cot"=""
"cox"=""
"cu"=""
"cuo"=""
"cuop"=""
"cuox"=""
"cup"=""
"cur"=""
"curx"=""
"cut"=""
"cux"=""
"cy"=""
VK_M, 0 = INPUT // M
VK_N, 0 = INPUT // N
VK_O, 0 = INPUT // O
VK_P, 0 = INPUT // P
KeyDefineImeMode=VK_SHIFT, TF_MOD_ON_KEYUP_SHIFT_ONLY
DescriptionImeMode="@%programFiles%\Windows NT\TableTextService\TableTextService.dll,-20"

Yealink 1810 IPB说明书

ILLUSTRATED PARTS BREAKDOWN - IPB1810 Surface Mount1810-080UMItem Part Number Quantity Description10 1804-004 1 EA Cover Lexan Clr 3.75 x .85 x .125FCC15 1804-023 1a lEA Dec20 2600-735 1 EA Hole Plug Black Nylon .250” dia.25 1810-030 1 EA Bracket Directory Holder30 1810-007 1 EA Cover Plastic 1810 Directorya sticPlEA Cover33 1502-005 135 1810-006 1 EA Cover Plastic - Large40 1804-042 1PlugEA HoleIdentifica la tion45 1400-009 1EA Dec50 1804-039 2 EA Retaining Strip KeypadPa tenta bel55 2599-008 1EA L57 1998-190 1 EA PCB Microphone Short, SMT60 2356-010 3 EA PCB LED Light Straight65 4001-035 1 EA Lock N16058BDxSFx2K Key 161207/8”a mEA C67 1702-501 170 2902-006 2 EA Nut Nylon Lock 10-32(6 USED)Nut Nylon Lock 4-4075 2902-002 2EA(2 Different Brackets)Bracket LED Mount77 1810-145 2EA(26 USED)Nut Nylon Lock 6-32EA80 2902-003 1785 1810-101 1 EA Box Phone Slant(NONE USED)Washer #10 SAEEA86 2620-010 2a tea ceplPhoneEA F90 1810-053 1a tePhoneEA Subpl95 1810-023 196 2600-734 1 EA Nameplate Plastic DKS Small97 2802-040 2 EA Washer Push on Clamp98 1897-050 2 EA Gasket Support Thick 1/16”100 1862-010 1 EA PCB Telephone 2 Relay103 1890-010 1 EA PCB Display LCD 8 x 1 Line(5 USED + P/N 107)Screw Phillips Head 6-32 x 3/16”104 2616-006 2EA105 2905-003 2 EA Screw Round Head 6-32 x 1/2”108 2900-905 1 EA Standoff Aluminum 7/16”, 6-32115 2905-001 1 EA Screw Round Head 6-32 x 1/4”130 3002-004 2 EA Spacer Nylon 6 x 7/16”140 1804-024 1 EA Switch Micro NO NC C145 1802-031 1 EA Terminal 14 Pin150 1804-060 1 EA Transformer 16.5 VAC, 20 VA Plug160 1800-018 2.91 FT Weather Strip .125”x .187”175 7082-059 1 EA Wire - Green 18 AWG Strd180 1804-040 1 EA WIre Telephone Line Cord(3 USED)Mount Wire Clip185 1804-028 1EA195 1895-017 1 EA Keypad 10 Pin Numbers Header197 1804-038 1 EA Wire Ribbon Cable Assy 10 CondAssemblya kerEA Spe205 1804-290 1210 1860-126 4 EA Washer Nylon Shoulder211 1860-032 4 EA Washer Nylon Retaining #6215 3002-021 4 EA Spacer Nylon 6 x 3/8”225 1800-060 1 EA Manual - Installation230 2600-884 1 EA Label E.T.L. Separable245 1804-196 1 EA Gasket, Speaker 1/16” Thicka sket,MicrophoneEA G250 1897-053 1255 1810-075 1 EA Memory 1000 Phone Numbers260 1876-025 1 EA Ferrite Snap-On Filter StewardXXA 1 EA Wire Harness 1810 Surface Front PanelXXB 2 EA Mount WIre Tie Wrap。

5G优化案例：SA接入成功率优化思路总结及案例分析

1^?"6743 V NR >hROSctupComplctc•眾诂儿N任uDp北;卜疋y u ly
1 "16砂咅NR->NR Capability
114716743
11.47.16.743
11:47:16.748
11:47:16.743
1]-47-16748
114716850
4
•fl-
NR->DLInfon*ndtionTfansfer
11.47.19.185
11:47:19.186
11:47:19.186
11.4L192
NR・'RRCRGConfiginationCornpQGNR->PDU session establishment request NR->UL NAS transpoit
NR-> ULInformationT e nsfc r NR->RRCReconfiauration NR->CellGroupConfig
NR->Regi5iration requestNR->RRCSeajpReque5lNR->RRCSeOjp
N R->CellGcoupConfig NR->RRCSetupComplcte
NR-^UECspabil ityEnquiryNR->NRCapability-
NR->DLIHonnat»onTrancfrrNR->ld6notyr8qu88t
5.2排查方法2-无信令20
5.3排查方法3-只读取其他小区SIB/MIB或只接入其他小区21
5.4排查方法4-可读取系统消息，但不发起接入21
5.5排查方法5-随机接入过程失败22

starscream函数 -回复

starscream函数-回复什么是starscream函数？如何使用starscream函数？starscream函数有哪些常见应用场景？Starscream函数是一个流行的第三方WebSocket框架，用于在iOS和OS X应用程序中创建和管理WebSocket连接。

它是一个开源项目，由Gilt Groupe公司开发和维护。

使用Starscream函数来创建和管理WebSocket连接非常简单。

首先，你需要将Starscream源代码导入你的项目中，并包含所需的头文件。

接下来，你可以使用下面的代码来初始化一个WebSocket连接：Swiftlet socket = WebSocket(url: URL(string: "wss:example")!) socket.delegate = selfsocket.connect()这里，我们实例化了一个WebSocket对象，并使用URL对象指定了连接的目标地址。

设置了socket.delegate，以便接收来自WebSocket的消息。

最后，我们调用了socket.connect()方法来建立与服务器之间的连接。

一旦建立了WebSocket连接，您可以使用下面的代码来向服务器发送消息：Swiftsocket.write(string: "Hello, server!")此外，Starscream函数提供了很多其他功能，如心跳检测、SSL支持和断线重连。

你可以通过查看Starscream的文档以及在Stack Overflow等社区论坛上提问来了解更多关于如何使用这些功能的信息。

Starscream函数在许多应用场景中被广泛使用，包括实时游戏、即时聊天和物联网设备控制。

在这些场景中，WebSocket连接通常被用作背景通信机制，用于传输消息和事件，以便在客户端和服务器之间实现实时数据交换。

总之，如果您正在构建一个需要与服务器进行实时通信的应用程序，则Starscream函数是一个值得尝试的工具。

Endress+Hauser Graphic Data Manager RSG35软件更新说明说明书

Manufacturer Informationfor users regarding software updates(following the NAMUR recommendation 53)1 Type of deviceField device / signal processing deviceMonitoring- / operation system / hand held terminal etc.Modem / interfaceManufacturer : Endress+HauserDevice : Graphic Data ManagerType : RSG35Previous software version : 1.00.zzHow can the previous software version number be identified:Display of current firmware version at device start-up,nameplate, parameter in configuration software, parameter inlocal set-up2 Firmware/Software: 1.01.zzNew firm-/softwareversionDescription of the modification in comparison with the predecessor version:Sending of encrypted e-mails, Device TAG with 32 char,search functions in stored data3 CompatibilityIs the newly installed firmware/software compatible with the operating tools?YesNo, description:The new firmware requires a new DTM (FDT-Tool) for device configuration Is a firm/software update generally recommended?Yes, reasons:The firm-/software update can be performed by means of …Manufacturer Informationfor users regarding software updates(following the NAMUR recommendation 53)No, reasons:If the additional properties are not required for the operation of the measurementsystem, then no firmware update is necessary.4 Instruction manualIs a new instruction manual necessary due to the modification of the firm-/software?YesNoWhich manual corresponds to the new firm-/software:Device Communication options Manual Marking RSG35 all Operating instructions BA01146R/09/EN/02.14The new instruction manuals can be referred in Internet: - area …DOWNLOAD“- declaration of the device and kind of manual5 PriceChange in price of device in comparison with the predecessor version?Yes, new list price and update costs (without installation) are enclosuredNo。

rfc5869.HMAC-based Extract-and-Expand Key Derivation Function (HKDF)

Internet Engineering Task Force (IETF) H. Krawczyk Request for Comments: 5869 IBM Research Category: Informational P. Eronen ISSN: 2070-1721 Nokia May 2010 HMAC-based Extract-and-Expand Key Derivation Function (HKDF)AbstractThis document specifies a simple Hashed Message Authentication Code(HMAC)-based key derivation function (HKDF), which can be used as abuilding block in various protocols and applications. The keyderivation function (KDF) is intended to support a wide range ofapplications and requirements, and is conservative in its use ofcryptographic hash functions.Status of This MemoThis document is not an Internet Standards Track specification; it is published for informational purposes.This document is a product of the Internet Engineering Task Force(IETF). It represents the consensus of the IETF community. It hasreceived public review and has been approved for publication by theInternet Engineering Steering Group (IESG). Not all documentsapproved by the IESG are a candidate for any level of InternetStandard; see Section 2 of RFC 5741.Information about the current status of this document, any errata,and how to provide feedback on it may be obtained at/info/rfc5869.Copyright NoticeCopyright (c) 2010 IETF Trust and the persons identified as thedocument authors. All rights reserved.This document is subject to BCP 78 and the IETF Trust’s LegalProvisions Relating to IETF Documents(/license-info) in effect on the date ofpublication of this document. Please review these documentscarefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e ofthe Trust Legal Provisions and are provided without warranty asdescribed in the Simplified BSD License.Krawczyk & Eronen Informational [Page 1]1. IntroductionA key derivation function (KDF) is a basic and essential component of cryptographic systems. Its goal is to take some source of initialkeying material and derive from it one or more cryptographicallystrong secret keys.This document specifies a simple HMAC-based [HMAC] KDF, named HKDF,which can be used as a building block in various protocols andapplications, and is already used in several IETF protocols,including [IKEv2], [PANA], and [EAP-AKA]. The purpose is to document this KDF in a general way to facilitate adoption in future protocols and applications, and to discourage the proliferation of multiple KDF mechanisms. It is not intended as a call to change existingprotocols and does not change or update existing specifications using this KDF.HKDF follows the "extract-then-expand" paradigm, where the KDFlogically consists of two modules. The first stage takes the inputkeying material and "extracts" from it a fixed-length pseudorandomkey K. The second stage "expands" the key K into several additional pseudorandom keys (the output of the KDF).In many applications, the input keying material is not necessarilydistributed uniformly, and the attacker may have some partialknowledge about it (for example, a Diffie-Hellman value computed by a key exchange protocol) or even partial control of it (as in someentropy-gathering applications). Thus, the goal of the "extract"stage is to "concentrate" the possibly dispersed entropy of the input keying material into a short, but cryptographically strong,pseudorandom key. In some applications, the input may already be agood pseudorandom key; in these cases, the "extract" stage is notnecessary, and the "expand" part can be used alone.The second stage "expands" the pseudorandom key to the desiredlength; the number and lengths of the output keys depend on thespecific cryptographic algorithms for which the keys are needed.Note that some existing KDF specifications, such as NIST SpecialPublication 800-56A [800-56A], NIST Special Publication 800-108[800-108] and IEEE Standard 1363a-2004 [1363a], either only consider the second stage (expanding a pseudorandom key), or do not explicitly differentiate between the "extract" and "expand" stages, oftenresulting in design shortcomings. The goal of this specification is to accommodate a wide range of KDF requirements while minimizing the assumptions about the underlying hash function. The "extract-then-expand" paradigm supports well this goal (see [HKDF-paper] for moreinformation about the design rationale).Krawczyk & Eronen Informational [Page 2]2. HMAC-based Key Derivation Function (HKDF)2.1. NotationHMAC-Hash denotes the HMAC function [HMAC] instantiated with hashfunction ’Hash’. HMAC always has two arguments: the first is a keyand the second an input (or message). (Note that in the extractstep, ’IKM’ is used as the HMAC input, not as the HMAC key.)When the message is composed of several elements we use concatenation (denoted |) in the second argument; for example, HMAC(K, elem1 |elem2 | elem3).The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [KEYWORDS].2.2. Step 1: ExtractHKDF-Extract(salt, IKM) -> PRKOptions:Hash a hash function; HashLen denotes the length of thehash function output in octetsInputs:salt optional salt value (a non-secret random value);if not provided, it is set to a string of HashLen zeros. IKM input keying materialOutput:PRK a pseudorandom key (of HashLen octets)The output PRK is calculated as follows:PRK = HMAC-Hash(salt, IKM)2.3. Step 2: ExpandHKDF-Expand(PRK, info, L) -> OKMOptions:Hash a hash function; HashLen denotes the length of thehash function output in octetsKrawczyk & Eronen Informational [Page 3]Inputs:PRK a pseudorandom key of at least HashLen octets(usually, the output from the extract step)info optional context and application specific information(can be a zero-length string)L length of output keying material in octets(<= 255*HashLen)Output:OKM output keying material (of L octets)The output OKM is calculated as follows:N = ceil(L/HashLen)T = T(1) | T(2) | T(3) | ... | T(N)OKM = first L octets of Twhere:T(0) = empty string (zero length)T(1) = HMAC-Hash(PRK, T(0) | info | 0x01)T(2) = HMAC-Hash(PRK, T(1) | info | 0x02)T(3) = HMAC-Hash(PRK, T(2) | info | 0x03)...(where the constant concatenated to the end of each T(n) is asingle octet.)3. Notes to HKDF UsersThis section contains a set of guiding principles regarding the useof HKDF. A much more extensive account of such principles and design rationale can be found in [HKDF-paper].3.1. To Salt or not to SaltHKDF is defined to operate with and without random salt. This isdone to accommodate applications where a salt value is not available. We stress, however, that the use of salt adds significantly to thestrength of HKDF, ensuring independence between different uses of the hash function, supporting "source-independent" extraction, andstrengthening the analytical results that back the HKDF design.Random salt differs fundamentally from the initial keying material in two ways: it is non-secret and can be re-used. As such, salt values are available to many applications. For example, a pseudorandomnumber generator (PRNG) that continuously produces outputs byapplying HKDF to renewable pools of entropy (e.g., sampled systemevents) can fix a salt value and use it for multiple applications of Krawczyk & Eronen Informational [Page 4]HKDF without having to protect the secrecy of the salt. In adifferent application domain, a key agreement protocol derivingcryptographic keys from a Diffie-Hellman exchange can derive a saltvalue from public nonces exchanged and authenticated betweencommunicating parties as part of the key agreement (this is theapproach taken in [IKEv2]).Ideally, the salt value is a random (or pseudorandom) string of thelength HashLen. Yet, even a salt value of less quality (shorter insize or with limited entropy) may still make a significantcontribution to the security of the output keying material; designers of applications are therefore encouraged to provide salt values toHKDF if such values can be obtained by the application.It is worth noting that, while not the typical case, someapplications may even have a secret salt value available for use; in such a case, HKDF provides an even stronger security guarantee. Anexample of such application is IKEv1 in its "public-key encryptionmode", where the "salt" to the extractor is computed from nonces that are secret; similarly, the pre-shared mode of IKEv1 uses a secretsalt derived from the pre-shared key.3.2. The ’info’ Input to HKDFWhile the ’info’ value is optional in the definition of HKDF, it isoften of great importance in applications. Its main objective is to bind the derived key material to application- and context-specificinformation. For example, ’info’ may contain a protocol number,algorithm identifiers, user identities, etc. In particular, it mayprevent the derivation of the same keying material for differentcontexts (when the same input key material (IKM) is used in suchdifferent contexts). It may also accommodate additional inputs tothe key expansion part, if so desired (e.g., an application may want to bind the key material to its length L, thus making L part of the’info’ field). There is one technical requirement from ’info’: itshould be independent of the input key material value IKM.3.3. To Skip or not to SkipIn some applications, the input key material IKM may already bepresent as a cryptographically strong key (for example, the premaster secret in TLS RSA cipher suites would be a pseudorandom string,except for the first two octets). In this case, one can skip theextract part and use IKM directly to key HMAC in the expand step. On the other hand, applications may still use the extract part for thesake of compatibility with the general case. In particular, if IKMis random (or pseudorandom) but longer than an HMAC key, the extract step can serve to output a suitable HMAC key (in the case of HMAC Krawczyk & Eronen Informational [Page 5]this shortening via the extractor is not strictly necessary sinceHMAC is defined to work with long keys too). Note, however, that if the IKM is a Diffie-Hellman value, as in the case of TLS with Diffie- Hellman, then the extract part SHOULD NOT be skipped. Doing so would result in using the Diffie-Hellman value g^{xy} itself (which is NOT a uniformly random or pseudorandom string) as the key PRK for HMAC.Instead, HKDF should apply the extract step to g^{xy} (preferablywith a salt value) and use the resultant PRK as a key to HMAC in the expansion part.In the case where the amount of required key bits, L, is no more than HashLen, one could use PRK directly as the OKM. This, however, isNOT RECOMMENDED, especially because it would omit the use of ’info’as part of the derivation process (and adding ’info’ as an input tothe extract step is not advisable -- see [HKDF-paper]).3.4. The Role of IndependenceThe analysis of key derivation functions assumes that the inputkeying material (IKM) comes from some source modeled as a probability distribution over bit streams of a certain length (e.g., streamsproduced by an entropy pool, values derived from Diffie-Hellmanexponents chosen at random, etc.); each instance of IKM is a samplefrom that distribution. A major goal of key derivation functions is to ensure that, when applying the KDF to any two values IKM and IKM’ sampled from the (same) source distribution, the resultant keys OKMand OKM’ are essentially independent of each other (in a statistical or computational sense). To achieve this goal, it is important that inputs to KDF are selected from appropriate input distributions andalso that inputs are chosen independently of each other (technically, it is necessary that each sample will have sufficient entropy, evenwhen conditioned on other inputs to KDF).Independence is also an important aspect of the salt value providedto a KDF. While there is no need to keep the salt secret, and thesame salt value can be used with multiple IKM values, it is assumedthat salt values are independent of the input keying material. Inparticular, an application needs to make sure that salt values arenot chosen or manipulated by an attacker. As an example, considerthe case (as in IKE) where the salt is derived from nonces suppliedby the parties in a key exchange protocol. Before the protocol canuse such salt to derive keys, it needs to make sure that these nonces are authenticated as coming from the legitimate parties rather thanselected by the attacker (in IKE, for example this authentication is an integral part of the authenticated Diffie-Hellman exchange). Krawczyk & Eronen Informational [Page 6]4. Applications of HKDFHKDF is intended for use in a wide variety of KDF applications.These include the building of pseudorandom generators from imperfect sources of randomness (such as a physical random number generator(RNG)); the generation of pseudorandomness out of weak sources ofrandomness, such as entropy collected from system events, user’skeystrokes, etc.; the derivation of cryptographic keys from a shared Diffie-Hellman value in a key-agreement protocol; derivation ofsymmetric keys from a hybrid public-key encryption scheme; keyderivation for key-wrapping mechanisms; and more. All of theseapplications can benefit from the simplicity and multi-purpose nature of HKDF, as well as from its analytical foundation.On the other hand, it is anticipated that some applications will not be able to use HKDF "as-is" due to specific operational requirements, or will be able to use it but without the full benefits of thescheme. One significant example is the derivation of cryptographickeys from a source of low entropy, such as a user’s password. Theextract step in HKDF can concentrate existing entropy but cannotamplify entropy. In the case of password-based KDFs, a main goal is to slow down dictionary attacks using two ingredients: a salt value, and the intentional slowing of the key derivation computation. HKDF naturally accommodates the use of salt; however, a slowing downmechanism is not part of this specification. Applications interested in a password-based KDF should consider whether, for example, [PKCS5] meets their needs better than HKDF.5. Security ConsiderationsIn spite of the simplicity of HKDF, there are many securityconsiderations that have been taken into account in the design andanalysis of this construction. An exposition of all of these aspects is beyond the scope of this document. Please refer to [HKDF-paper]for detailed information, including rationale for the design and for the guidelines presented in Section 3.A major effort has been made in the above paper [HKDF-paper] toprovide a cryptographic analysis of HKDF as a multi-purpose KDF that exercises much care in the way it utilizes cryptographic hashfunctions. This is particularly important due to the limitedconfidence we have in the strength of current hash functions. Thisanalysis, however, does not imply the absolute security of anyscheme, and it depends heavily on the strength of the underlying hash function and on modeling choices. Yet, it serves as a strongindication of the correct structure of the HKDF design and itsadvantages over other common KDF schemes.Krawczyk & Eronen Informational [Page 7]6. AcknowledgmentsThe authors would like to thank members of the CFRG (Crypto ForumResearch Group) list for their useful comments, and to Dan Harkinsfor providing test vectors.7. References7.1. Normative References[HMAC] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- Hashing for Message Authentication", RFC 2104,February 1997.[KEYWORDS] Bradner, S., "Key words for use in RFCs to IndicateRequirement Levels", BCP 14, RFC 2119, March 1997.[SHS] National Institute of Standards and Technology, "Secure Hash Standard", FIPS PUB 180-3, October 2008.7.2. Informative References[1363a] Institute of Electrical and Electronics Engineers, "IEEE Standard Specifications for Public-Key Cryptography -Amendment 1: Additional Techniques", IEEE Std1363a-2004, 2004.[800-108] National Institute of Standards and Technology,"Recommendation for Key Derivation Using PseudorandomFunctions", NIST Special Publication 800-108,November 2008.[800-56A] National Institute of Standards and Technology,"Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography (Revised)", NISTSpecial Publication 800-56A, March 2007.[EAP-AKA] Arkko, J., Lehtovirta, V., and P. Eronen, "ImprovedExtensible Authentication Protocol Method for 3rdGeneration Authentication and Key Agreement (EAP-AKA’)", RFC 5448, May 2009.[HKDF-paper] Krawczyk, H., "Cryptographic Extraction and KeyDerivation: The HKDF Scheme", Proceedings of CRYPTO 2010 (to appear), 2010, </2010/264>.[IKEv2] Kaufman, C., Ed., "Internet Key Exchange (IKEv2)Protocol", RFC 4306, December 2005.Krawczyk & Eronen Informational [Page 8][PANA] Forsberg, D., Ohba, Y., Ed., Patil, B., Tschofenig, H., and A. Yegin, "Protocol for Carrying Authentication for Network Access (PANA)", RFC 5191, May 2008.[PKCS5] Kaliski, B., "PKCS #5: Password-Based CryptographySpecification Version 2.0", RFC 2898, September 2000. Krawczyk & Eronen Informational [Page 9]Appendix A. Test VectorsThis appendix provides test vectors for SHA-256 and SHA-1 hashfunctions [SHS].A.1. Test Case 1Basic test case with SHA-256Hash = SHA-256IKM = 0x0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b (22 octets)salt = 0x000102030405060708090a0b0c (13 octets)info = 0xf0f1f2f3f4f5f6f7f8f9 (10 octets)L = 42PRK = 0x077709362c2e32df0ddc3f0dc47bba6390b6c73bb50f9c3122ec844ad7c2b3e5 (32 octets)OKM = 0x3cb25f25faacd57a90434f64d0362f2a2d2d0a90cf1a5a4c5db02d56ecc4c5bf34007208d5b887185865 (42 octets)Krawczyk & Eronen Informational [Page 10]Test with SHA-256 and longer inputs/outputsHash = SHA-256IKM = 0x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f404142434445464748494a4b4c4d4e4f (80 octets)salt = 0x606162636465666768696a6b6c6d6e6f707172737475767778797a7b7c7d7e7f808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeaf (80 octets)info = 0xb0b1b2b3b4b5b6b7b8b9babbbcbdbebfc0c1c2c3c4c5c6c7c8c9cacbcccdcecfd0d1d2d3d4d5d6d7d8d9dadbdcdddedfe0e1e2e3e4e5e6e7e8e9eaebecedeeeff0f1f2f3f4f5f6f7f8f9fafbfcfdfeff (80 octets)L = 82PRK = 0x06a6b88c5853361a06104c9ceb35b45cef760014904671014a193f40c15fc244 (32 octets)OKM = 0xb11e398dc80327a1c8e7f78c596a49344f012eda2d4efad8a050cc4c19afa97c59045a99cac7827271cb41c65e590e09da3275600c2f09b8367793a9aca3db71cc30c58179ec3e87c14c01d5c1f3434f1d87 (82 octets)A.3. Test Case 3Test with SHA-256 and zero-length salt/infoHash = SHA-256IKM = 0x0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b (22 octets)salt = (0 octets)info = (0 octets)L = 42PRK = 0x19ef24a32c717b167f33a91d6f648bdf96596776afdb6377ac434c1c293ccb04 (32 octets)OKM = 0x8da4e775a563c18f715f802a063c5a31b8a11f5c5ee1879ec3454e5f3c738d2d9d201395faa4b61a96c8 (42 octets)Krawczyk & Eronen Informational [Page 11]Basic test case with SHA-1Hash = SHA-1IKM = 0x0b0b0b0b0b0b0b0b0b0b0b (11 octets)salt = 0x000102030405060708090a0b0c (13 octets)info = 0xf0f1f2f3f4f5f6f7f8f9 (10 octets)L = 42PRK = 0x9b6c18c432a7bf8f0e71c8eb88f4b30baa2ba243 (20 octets)OKM = 0x085a01ea1b10f36933068b56efa5ad81a4f14b822f5b091568a9cdd4f155fda2c22e422478d305f3f896 (42 octets)A.5. Test Case 5Test with SHA-1 and longer inputs/outputsHash = SHA-1IKM = 0x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f404142434445464748494a4b4c4d4e4f (80 octets)salt = 0x606162636465666768696a6b6c6d6e6f707172737475767778797a7b7c7d7e7f808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeaf (80 octets)info = 0xb0b1b2b3b4b5b6b7b8b9babbbcbdbebfc0c1c2c3c4c5c6c7c8c9cacbcccdcecfd0d1d2d3d4d5d6d7d8d9dadbdcdddedfe0e1e2e3e4e5e6e7e8e9eaebecedeeeff0f1f2f3f4f5f6f7f8f9fafbfcfdfeff (80 octets)L = 82PRK = 0x8adae09a2a307059478d309b26c4115a224cfaf6 (20 octets)OKM = 0x0bd770a74d1160f7c9f12cd5912a06ebff6adcae899d92191fe4305673ba2ffe8fa3f1a4e5ad79f3f334b3b202b2173c486ea37ce3d397ed034c7f9dfeb15c5e927336d0441f4c4300e2cff0d0900b52d3b4 (82 octets)Krawczyk & Eronen Informational [Page 12]Test with SHA-1 and zero-length salt/infoHash = SHA-1IKM = 0x0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b (22 octets)salt = (0 octets)info = (0 octets)L = 42PRK = 0xda8c8a73c7fa77288ec6f5e7c297786aa0d32d01 (20 octets)OKM = 0x0ac1af7002b3d761d1e55298da9d0506b9ae52057220a306e07b6b87e8df21d0ea00033de03984d34918 (42 octets)A.7. Test Case 7Test with SHA-1, salt not provided (defaults to HashLen zero octets), zero-length infoHash = SHA-1IKM = 0x0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c (22 octets)salt = not provided (defaults to HashLen zero octets)info = (0 octets)L = 42PRK = 0x2adccada18779e7c2077ad2eb19d3f3e731385dd (20 octets)OKM = 0x2c91117204d745f3500d636a62f64f0ab3bae548aa53d423b0d1f27ebba6f5e5673a081d70cce7acfc48 (42 octets)Krawczyk & Eronen Informational [Page 13]Authors’ AddressesHugo KrawczykIBM Research19 Skyline DriveHawthorne, NY 10532USAEMail: hugokraw@Pasi EronenNokia Research CenterP.O. Box 407FI-00045 Nokia GroupFinlandEMail: pasi.eronen@Krawczyk & Eronen Informational [Page 14]。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

M | N = {M, N} MN = {mn| m M, n N} M* = {, M, MM, MMM, …}
正则表达式的形式表示
e -> | | | | c e | e e e e*
问题：对于给定字符集={a, b}，可以写出哪些正则表达式？
例子：关键字

C语言中的关键字，例如if，while等

我们已经讨论了第一种实现方案

从这一讲开始讨论第二种方案
自动生成
声明式的规范词Βιβλιοθήκη 分析器正则表达式
对给定的字符集={c1, c2, …, cn} 归纳定义：

空串是正则表达式对于任意c，c是正则表达式如果M和N是正则表达式, 则以下也是正则表达式

选择连接闭包

如何用正则表达式表示？
例子：标识符

C语言中的标识符：以字母或下划线开头，后跟零个或多个字母、数字或下划线。

如何用正则表达式表示？
例子：C语言中的无符号整数

（十进制整型数）规则：或者是0；或者是以1到9开头，后跟零个或多个0到9

如何用正则表达式表示？
语法糖

可以引入更多的语法糖，来简化构造

[c1-cn] e+ e? “a*” e{i, j} .
== c1|c2|…|cn == 一个或多个 e == 零个或一个 e == a* 自身, 不是a的Kleen闭包 == i到j个e的连接 == 除‘\n’外的任意字符
词法分析---正则表达式
编译原理
华保健
bjhua@
回顾
字符流
词法分析器
记号流
回顾：词法分析器的实现方法

至少两种实现方案:

手工编码实现法

相对复杂、且容易出错但是目前非常流行的实现方法

GCC, LLVM, …

词法分析器的生成器

可快速原型、代码量较少但较难控制细节