SIGF A family of configurable, secure routing protocols for wireless sensor networks
蓝牙中英文翻译
BluetoothIntroductionBluetooth is a forever, limited radio connect that resides o n a microchip. It was originally expanded through Swedish mo bile phone creator Ericsson in 1994 as a method to let lap top computers make calls above a mobile phone. As then, num erous organizations have signed on to create Bluetooth the low-power thoughtless wireless average for a broad variety ofdevices (LeVitus, 216-220). Industry spectators anticipate Bluetooth to be fitted in billions of devices through 2005. DiscussionDeveloped by engineers at Ericsson in the late 1990s, Blue tooth is more and more special technology that facilitates t houghtless wireless communication among a diversity of electro nic devices. Its mainly important aspect is that it permits devices to “talk”(relocate and orchestrate data) wirelessly with each other, terminating the requirement for the outwar dly continuous tangle of cables, cords, and adapters importan t for numerous today’s expertise.The Bluetooth Special Interest Group (SIG) was formed in 1 998 to manage the expansion and prologue of Bluetooth knowle dge (LeVitus, 216-220). IBM, Intel, Toshiba and Nokia connected with Ericsson as the beginning associates of the SIG, and in exc ess of 8,000 organizations have contracted since. So as to trade products with the Bluetooth requirement and logo, manufacturers should be associates of the SIG and the devices should meet well-outlined credentials. These procedures makesure that Bluetooth wireless devices international may converse with each other, apart from company or nation ofderivation.Speed and RangeRange is application specific and although a minimum rangeis mandated by the Core Specification, there is not a limit and manufacturers can tune their implementation to support the use case they are enabling.Range may vary depending on class of radio used in an impl ementation:·Class 3 radios-have a range of up to 1 meter or 3 feet ·Class 2 radios-most commonly found in mobile devices, have arange of 10 meters or 33 feet.·Class 1 radios-used primarily in industrial use cases,have a range of 100 meters or 300 feet.That creates Bluetooth technology appropriate for transporting lesser files for example cell phone contracts and text documents, also as lower-quality pictures and audio (Kumkum, 160-162).At these relocate speeds; Bluetooth may not actually deal st reaming video or high-quality pictures and audio at this end, except this possibly will alter in the future when fresh Bl uetooth standards are initiated.Simple and Competent to UtilizeCreating and configuring Bluetooth allowed devices is modera tely uncomplicated, with little extra commotion than acquire the two devices close to one another and twist them on.There is no requirement to mount drivers or further software to complex an ad-hoc, personal wireless network (Kumkum, 160-162). It has a uniform organization, meaning that some two wireless products attributing Bluetooth technology,despite of productor nation of origin, have the ability to converse faultlessly with each other.Common ApplicationsOne of the mainly ordinary applications of Bluetooth is hand s -free cell phone procedure. About each cell phone fashioned in our day has constructed Bluetooth (Meier, 15-20). Only pair phone with a Bluetooth headset, and he may talk whereas his phone is in his purse or pocket. Several of today’s car stereo s as well have fitted Bluetooth for hands-free calling in his vehicle. And if his vehicle has a plant stereo or grown-up aftermarket one that he merely doesn’t wish to restore, he may yet like hands-free identifying with a Bluetooth car kit. Bluetooth 3.0Bluetooth 3.0 is the fresh Bluetooth wireless typical adopted through the Bluetooth SIG on April 21, 2009. The fresh st andard supports elevated data remove speeds and constructs ah ead the preceding standards (Meier, 15-20). With its superior speed, the technology has the probable to transfigure the co nsumer electronics industry.PROTOCOLThe Bluetooth technology standard is set to make different a pplications can “communicate”with each other. Remote device s in communication use the same protocol stacks, while diffe rent applications need different protocol stacks. But, every application needs the data link layer and physical layer of the Bluetooth technology.The whole Bluetooth protocol stacksis shown as blow. Not any application should use all of the protocols, but one or some lists of these. The chart b elow shows the relationship between protocols, but the relati onship may change in some applications.The completely protocol stacks include Bluetooth special proto cols (like LMP and L2CAP) and not special ones (such as OB EX and UDP). The basic principle for designing protocol and protocol stacks is that use existing highlevel protocol as p ossible, ensure the combination of protocols and Bluetooth te chnology, and take the best advantage of the software and h ardware which adapt to the Bluetooth technology standards. Th e open Bluetooth technology makes device manufacturers can ch oose protocols freely as they like or used to.The protocols in Bluetooth protocol system.There are four layers in Bluetooth protocol system accordingto the SIG:·Core protocols·Cable replacement protocols·Telephony control protocols·Adopted protocolsExcept the protocol layers above, the standard also defines Host/Controller Interface (HCI),which provides command interface for baseband controller, connection manager, hardware state and control register.Bluetooth core protocols consist of the special protocols mad e by SIG. Most Bluetooth devices need core protocols, while other protocols are used depend on needs of the application. After all, cable replacement protocols, technology control p rotocols and adopted protocols based on the core protocols c onstitute the object-oriented protocols.·Core protocols·LMP (Link Management Protocol)Used for control of the radio link between two devices. Implemented onthe controllers.It identifies and encrypts through launching, exchanging and checking the connection, and decides the size of baseband da ta packets through conference. It also controls the power mo de and work cycle of wireless equipment, and connection stat us of unit equipment in piconet.·L2CAP (Logical Link Control & Adaptation Protocol)This protocol is used to multiplex multiple logical connectio ns between two devices using different higher level protocols, and provides segmentation and reassembly of on-air packets.In Basic mode, L2CAP provides packets with a payload configu rable up to 64kB, with 672 bytes as the default MTU, and 48 bytes as the minimum mandatory supported MTU.In Retransmission & Flow Control modes, L2CAP can be configu red for reliable or isochronous data per channel by performi ng retransmissions and CRC checks.Bluetooth Core Specification Addendum 1 adds two additional L 2CAP modes to the core specification. These modes effectively deprecate original Retransmission and Flow Control modes:·Enhanced Retransmission Mode (ERTM): This mode is an improv ed version of the original retransmission mode. This mode pr ovides a reliable L2CAP channel.·Streaming Mode (SM): This is a very simple mode, with no retransmissionor flow control. This mode provides an unreliabl e L2CAP channel.Reliability in any of these modes is optionally and/or addit ionally guaranteed by the lower layer Bluetooth BDR/EDR air interface by configuring the number of retransmissions and fl ush timeout (time after which the radio will flush packets).In-order sequencing is guaranteed by the lower layer.Only L2CAP channels configured in ERTM or SM may be operated over AMP logical links.·SDP (Service Discovery Protocol)Service Discovery Protocol (SDP) allows a device to discover services supported by other devices, and their associated par ameters. For example, when connecting a mobile phone to a B luetooth headset, SDP will be used for determining which Blu etooth profiles are supported by the headset (Headset Profile, Hands Free Profile, Advanced Audio Distribution Profile (A2DP) etc.) and the protocol multiplexer settings needed to connect to each of them. Each service is identified by a Universally Unique Identifier (UUID), with official services (Bluetooth profiles) assigned a short form UUID (16 bits rather than t he full 128)/vichitra·Cable replacement protocols(RFCOMM)Radio frequency communications (RFCOMM) is a cable replacement protocol used to create a virtual serial data stream. RFCOMM provides for binary data transport and emulates EIA-232 (formerly RS-232) control signals over the Bluetooth baseband layer.RFCOMM provides a simple reliable data stream to the user, similar to TCP. It is used directly by many telephony relat ed profiles as a carrier for AT commands, as well as being a transport layer for OBEX over Bluetooth.·Telephony control protocols (TCP).Telephony control protocol-binary (TCS BIN) is the bit-oriented protocol that defines the call control signaling for the establishment of voice and data calls between Bluetoothdevices. Additionally, “TCS BIN defines mobility management p rocedures for handling groups of Bluetooth TCS devices.”TCS-BIN is only used by the cordless telephony profile, which failed to attract implementers. As such it is only of historical interest.Adopted protocolsAdopted protocols are defined by other standards-making organizations and incorporated into Bluetooth’s protocol stack, allowing Bluetooth to create protocols only when necessary. T he adopted protocols include:·Point-to-Point Protocol (PPP): Internet standard protocol for transporting IP datagrams over a point-to-point link.·TCP/IP/UDP: For communicating with the device connected to Internet.·Object Exchange Protocol (OBEX): Session-layer protocol for the exchange of objects, providing a model for object and operation representation. It uses the client-server mode.· Wireless Application Environment/Wireless Application Protocol (WAE/WAP):WAE specifies an application framework for wireless devices and WAP is an open standard to provide mobile users access to telephony and information services.TechnologySPECTRUM AND INTERFERENCEBluetooth technology operates in the unlicensed industrial, sc ientific and medical (ISM) band at 2.4 to 2.485 GHz, usinga spread spectrum, frequency hopping, full-duplex signal at a nominal rate of 1600 hops/sec. The 2.4 GHz ISM band is ava ilable and unlicensed in most countries.SIM frequency band is open to all radio system, So the useof a certain frequency band will meet unpredictable interfe rence sources. Therefore, Bluetooth designs special fast ackno wledge and frequency hopping technique to ensure the stabilit y of link. Frequency hopping technique to divide the band i nto many frequency hopping channels, in a connection, radio transceiver “jump”from a channel to another constantly acc ording to certain code sequence. Only sender and receiver co mmunicate according to this law, and the rest of interferenc e may not press the same rule. The instantaneous bandwidth of Frequency hopping is very narrow, but through the spread spectrum technology it can make the narrow bandwidth one h undred times expanded into wideband, making the influence of interference may become very small. Comparing to other syst ems that work in the same frequency band, frequency hopping of Bluetooth works faster, data packet of Bluetooth is sho rter, which make it more stable than the other.ERROR CORRECTIONBluetooth supports circuit switching and packet switching two techniques, and defines two types of link connection, namel y connection-oriented synchronous link (SCO) and connectionless-oriented asynchronous link (ACL).Bluetooth use three error correction models:1/3 Forward Error Correction (FEC), 2/3forward Forward Error Correction and Au tomatic Repeat Request (ARQ). Purpose to the error correction is to reduce the possibility of retransmission, while at t he same time increase the extra expenses, but in a reasonab le errorless environment, redundant bids will reduce output. So the packet definition itself also keeps flexible ways. He nce the software can be defined whether to adopt FEC. In general, when the channel noise is large, Bluetooth system will uses FEC, in order to ensure the quality of communication: as to SCO link, 1/3 FEC is used; 2/3 FEC is used in ACL link. In Unnumbered ARQ, the data send in a time slot must receive a confirmation of receipt in the next time slot. On ly when the data is checked to be without mistake after he ader error detection and CRC at receiver will the confirmati on sent to sender, or an error message will be sent back. RANGERange is application specific and although a minimum range i s mandated by the Core Specification, there is not a limit and manufacturers can tune their implementation to support the use case they are enabling.Range may vary depending on class of radio used in an impl ementation:Class 3 radios-have a range of up to 1 meter or 3 feet. Class 2 radios-most commonly found in mobile devices , have a range of 10 meters or 33 feet.Class 1 radios-used primarily in industrial use cases , have a range of 100 meters or 300 feet.POWERIn order to make a Bluetooth equipment can also be in conn ection even in a very low power state, Bluetooth stipulates three energy saving state: Park state, Hold state and Snif f state. The energy saving efficiency of these states declin es one by one.The most commonly used radio is Class 2 and users 2.5mW of power. Bluetooth technology is designed to have very low p ower consumption. This is reinforced in the specification byallowing radios to be powered down when inactive.The Generic Alternate MAC/PHY in Version 3.0 HS enables the discovery of remote AMPs for high speed devices and tums on the radio only when needed for data transfer giving a p ower optimization benefit as well as aiding in the security of the radios.Bluetooth low energy technology, optimized for devices requiri ng maximum battery life instead of a high data transfer rat e, consumers between 1/2 and 1/100 the power of classic Blu etooth technology.SECURITYMobility and open of Bluetooth system makes safety problems extremely important. Although the frequency modulation techniqu e used by Bluetooth system has already provided a certain s ecurity, but Bluetooth system still need safety management to link layer and application layer. In link layer, Bluetooth system provides authentication, encryption and key management, and other functions. Each user has a Personal Identificatio n Number (PIN), which will be translated into 128 bit link key for one-way or both-way certification. Once the authentication finished, link will use encryphon key to encrypt. The link layer security mechanism provides a great deal of certification schemes and a flexible encryption scheme (means allow the consultation of the length of password). This me chanism is very important when the equipments in communicatio n are from different countries, because some countries will specify maximum password length. Bluetooth system will select the smallest maximum allowable password length of all equip ments in the piconet.Bluetooth system also supports the high level of protocol st ack in different applications of special security mechanisms. Bluetooth security mechanism builds trust relationship betwee n devices relying on pins. Once this relationship established , these pins can be stored in the equipment, in order to connection more quickly the next time.Source: Baidu Library蓝牙介绍蓝牙是一种永久、有限的无线连接,驻留在微芯片上。
IPsec VPNs Internet Key Exchange (IKE)配置说明书
Configuring Internet Key Exchange for IPsec VPNsThis module describes how to configure the Internet Key Exchange(IKE)protocol for basic IP Security (IPsec)Virtual Private Networks(VPNs).IKE is a key management protocol standard that is used in conjunction with the IPsec standard.IPsec is an IP security feature that provides robust authentication and encryption of IP packets.IPsec can be configured without IKE,but IKE enhances IPsec by providing additional features,flexibility, and ease of configuration for the IPsec standard.IKE is a hybrid protocol,that implements the Oakley key exchange and Skeme key exchange inside the Internet Security Association Key Management Protocol(ISAKMP)framework.(ISAKMP,Oakley,andSkeme are security protocols implemented byIKE.)Security threats,as well as the cryptographic technologies to help protect against them,are constantly changing.For more information about the latest Cisco cryptographic recommendations,see the Next GenerationEncryption(NGE)white paper.Note•Creating IKE Policies,on page1•Configuring IKE Authentication,on page2•Configuring IKE Mode Configuration,on page3•Configuration Examples for an IKE Configuration,on page4•Verifying IKE Policies,on page6•Additional References,on page7Creating IKE PoliciesRestrictions for configuring AES IKE policy•IPsec and long keys(the“k9”subsystem)must be supported.•AES cannot encrypt IPsec and IKE traffic if an acceleration card is present.enableconfigure terminalcrypto isakmp policy10encryption aes256hash shaauthentication pre-sharegroup14endTroubleshooting Tips•Clear(and reinitialize)IPsec SAs by using the clear crypto sa EXEC command.Using the clear crypto sa command without parameters will clear out the full SA database,which will clearout active security sessions.You may also specify the peer,map,or entry keywords to clear out only a subsetof the SA database.For more information,see the clear crypto sa command in the Cisco IOS SecurityCommand Reference.•The default policy and default values for configured policies do not show up in the configuration whenyou issue the show running-config command.To display the default policy and any default values withinconfigured policies,use the show crypto isakmp policy command.•Any IPsec transforms or IKE encryption methods that the current hardware does not support should bedisabled;they are ignored whenever an attempt to negotiate with the peer is made.If a user enters an IPsec transform or an IKE encryption method that the hardware does not support,a warningmessage will be generated.These warning messages are also generated at boot time.When an encrypted cardis inserted,the current configuration is scanned.If any IPsec transforms or IKE encryption methods are foundthat are not supported by the hardware,a warning message will be generated.Configuring IKE AuthenticationAfter you have created at least one IKE policy in which you specified an authentication method(or acceptedthe default method),you need to configure an authentication method.IKE policies cannot be used by IPsecuntil the authentication method is successfullyconfigured.Before configuring IKE authentication,you must have configured at least one IKE policy,which is where the authentication method was specified(or RSA signatures was accepted by default).NoteTo configure IKE authentication,you should perform one of the following tasks,as appropriate:Configuring RSA Keys Manually for RSA EncryptedNoncesThis task can be performed only if a CA is not in use. Noteenableconfigure terminalcrypto key generate rsa general-keys modulus360crypto key generate ec keysize256label Router_1_Key end Configuring Internet Key Exchange for IPsec VPNsTroubleshooting TipsOptional Configuration using Named Keyenableconfigure terminalcrypto key pubkey-chain rsanamed-key address 10.5.5.1key-string003020174A7D385B 1234EF29335FC9732DD50A37C4F4B0FD 9DADE748429618D518242BA32EDFBDD34296142A DDF7D3D8084076852F2190A00B43F1BD 9A8A26DB 0795*******FCDE9A98420F06A82045B 90288A26DBC644687789F76E EE21quitOptional Configuration using Addresses Keyenableconfigure terminalcrypto key pubkey-chain rsaaddressed-key 10.1.1.2encryption address 10.5.5.1key-string003020174A7D385B 1234EF29335FC9732DD50A37C4F4B0FD 9DADE748429618D518242BA32EDFBDD34296142A DDF7D3D8084076852F2190A00B43F1BD 9A8A26DB 0795*******FCDE9A98420F06A82045B 90288A26DBC644687789F76E EE21quitConfiguring PresharedKeysPreshared keys do not scale well with a growing network.Restrictoins for Mask Preshared Keys•The SA cannot be established between the IPsec peers until all IPsec peers are configured for the same preshared key.•The mask preshared key must be distinctly different for remote users requiring varying levels ofauthorization.A new preshared key should be configured for each level of trust and correct keys must be assigned to the correct parties.Otherwise,an untrusted party may obtain access to protected data.Noteenableconfigure terminalcrypto isakmp identity addresscrypto isakmp key sharedkeystring address 192.168.1.33no-xauth crypto isakmp key sharedkeystring address 10.0.0.1endConfiguring IKE Mode Configurationenableconfigure terminalConfiguring Internet Key Exchange for IPsec VPNsConfiguring Preshared Keysip local pool pool1172.16.23.0172.16.23.255crypto isakmp client configuration address-pool local pool1endConfiguration Examples for an IKE ConfigurationExample:Creating IKE PoliciesThis section contains the following examples,which show how to configure an AES IKE policy and a 3DES IKEpolicy.Cisco no longer recommends using 3DES;instead,you should use AES.For more information about the latest Cisco cryptographic recommendations,see the Next Generation Encryption (NGE)white paper.NoteExample:Creating an AES IKE PolicyThe following example is sample output from the show running-config command.In this example,the AES 256-bit key is enabled.Current configuration :1665bytes !version 12.2service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption !hostname "Router1"!!ip subnet-zero !!no ip domain lookup !ip audit notify logip audit po max-events 100!crypto isakmp policy 10encryption aes 256authentication pre-share lifetime 180crypto isakmp key cisco123address 10.0.110.1!!crypto ipsec transform-set aesset esp-aes 256esp-sha-hmac mode transport ...Configuring Internet Key Exchange for IPsec VPNsConfiguration Examples for an IKE ConfigurationConfiguring Internet Key Exchange for IPsec VPNsExample:Creating3DES IKE PoliciesExample:Creating3DES IKE PoliciesThis example creates two IKE policies,with policy15as the highest priority,policy20as the next priority,and the existing default priority as the lowest priority.It also creates a preshared key to be used with policy20with the remote peer whose IP address is192.168.224.33.crypto isakmp policy15encryption3deshash md5authentication rsa-siggroup2lifetime5000!crypto isakmp policy20authentication pre-sharelifetime10000!crypto isakmp key1234567890address192.168.224.33In the example,the encryption DES of policy default would not appear in the written configuration becausethis is the default value for the encryption algorithm parameter.If the show crypto isakmp policy command is issued with this configuration,the output is as follows:Protection suite priority15encryption algorithm:3DES-Triple Data Encryption Standard(168bit keys)hash algorithm:Message Digest5authentication method:Rivest-Shamir-Adleman SignatureDiffie-Hellman group:#2(1024bit)lifetime:5000seconds,no volume limitProtection suite priority20encryption algorithm:DES-Data Encryption Standard(56bit keys)hash algorithm:Secure Hash Standardauthentication method:preshared KeyDiffie-Hellman group:#1(768bit)lifetime:10000seconds,no volume limitDefault protection suiteencryption algorithm:DES-Data Encryption Standard(56bit keys)hash algorithm:Secure Hash Standardauthentication method:Rivest-Shamir-Adleman SignatureDiffie-Hellman group:#1(768bit)lifetime:86400seconds,no volume limitNote that although the output shows“no volume limit”for the lifetimes,you can configure only a time lifetime(such as86,400seconds);volume-limit lifetimes are not configurable.Example:Configuring IKE AuthenticationThe following example shows how to manually specify the RSA public keys of two IPsec peer--the peer at10.5.5.1uses general-purpose keys,and the other peer uses special-usage keys:crypto key pubkey-chain rsanamed-key address10.5.5.1key-string005C300D06092A864886F70D0101010500034B003048024100C5E23B55D6AB2204AEF1BA A54028A69ACC01C5129D99E464CAB820847EDAD9DF0B4E4C73A05DD2Configuring Internet Key Exchange for IPsec VPNs Verifying IKE PoliciesBD62A8A9FA603DD2E2A8A6F898F76E28D58AD221B583D7A4710203010001quitexitaddressed-key10.1.1.2encryptionkey-string003020174A7D385B1234EF29335FC9732DD50A37C4F4B0FD9DADE748429618D518242BA32EDFBDD34296142A DDF7D3D8084076852F2190A00B43F1BD9A8A26DB0795*******FCDE9A98420F06A82045B90288A26DBC644687789F76E EE21quitexitaddressed-key10.1.1.2signaturekey-string0738BC7A2BC3E9F0679B00FE53987BCC010*******DD06AF E228D24C458AD22858BB5DDD F48364012A2D7163219F882E64CE69D4B583748A241BED0F6E7F2F160DE0986E DF02031F4B0B0912F68200C4C625C3890BFF3321A2598935C1B1quitexitexitVerifying IKE PoliciesRouter#show crypto isakmp policyGlobal IKE policyProtection suite of priority1encryption algorithm:Three key triple DEShash algorithm:Secure Hash Standardauthentication method:Pre-Shared KeyDiffie-Hellman group:#5(1536bit)lifetime:86400seconds,no volume limitVerifying RSA KeysRouter#show crypto key pubkey-chain rsaCodes:M-Manually configured,C-Extracted from certificateCode Usage IP-Address/VRF Keyring NameC Signing default cn=Cisco Licensing Root CA,o=CiscoC Signing default cn=CAC Signing default cn=Cisco Root CA M1,o=CiscoC Signing default cn=Cisco Root CA2048,o=CiscoSystemsC Signing default cn=Cisco Manufacturing CA,o=CiscoSystemsC Signing default ou=Class3Public PrimaryCertification Authority,o=VeriSign,Inc.,c=USC Signing default cn=Cisco Root CA M2,o=CiscoC Signing default cn=Cisco Manufacturing CASHA2,o=CiscoC Signing default cn=Licensing Root-DEV,o=CiscoAdditional ReferencesRelated Documents Document TitleRelated Topic Cisco IOS Master Commands List,All Releases Cisco IOS commands•Cisco IOS Security Command Reference Commands A to C•Cisco IOS Security Command Reference Commands D to L•Cisco IOS Security Command Reference Commands M to R•Cisco IOS Security Command Reference Commands S to ZSecurity commands:complete command syntax,command mode,command history,defaults,usage guidelines,and examplesConfiguring Security for VPNs with IPsec IPsec configuration Configuring Internet Key Exchange Version 2IKE Version 2Deploying RSA Keys Within a PKI Configuring RSA keys to obtain certificates from a CAConfiguring Security for VPNs with IPsecSuite-B ESP transformsConfiguring Certificate Enrollment for a PKI Suite-B support for certificate enrollment for a PKIStandards Title Standards --None MIBsMIBs LinkMIBs To locate and download MIBs for selected platforms,Cisco IOS software releases,and feature sets,use Cisco MIB Locator found at the following URL:/go/mibsNone Configuring Internet Key Exchange for IPsec VPNsAdditional ReferencesRFCs TitleRFCsInternet Security Association and Key Management Protocol (ISAKMP)RFC 2408The Internet Key Exchange (IKE)RFC 2409The OAKLEY Key Determination Protocol RFC 2412Technical Assistance LinkDescription/cisco/web/support/index.html The Cisco Support and Documentation website provides online resources to download documentation,software,and e these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies.Access to most tools on the Cisco Support and Documentation website requires a user ID and password.Configuring Internet Key Exchange for IPsec VPNsAdditional References。
OWASP ESAPI
Copyright © 2008 – Aspect Security –
3
)
More Vulnerability Theory
Every vulnerability stems from….
Missing control
) Lack of encryption ) Failure to perform access control
User Message (no detail)
Enterprise Security Exceptions
Logger
Log Message (w/Identity)
AccessControlException AuthenticationException AvailabilityException EncodingException EncryptionException ExecutorException IntegrityException IntrusionException ValidationException
Validator
Encoder
Canonicalization Double Encoding Protection Sanitization Normalization
encodeForJavaScript encodeForVBScript encodeForURL encodeForHTML encodeForHTMLAttribute encodeForLDAP encodeForDN encodeForSQL encodeForXML encodeForXMLAttribute encodeForXPath
Broken control
MXP7000 商品说明书
MISSION-CRITICAL CONVERGED TETRA AND LTE PORTABLE DEVICEThe MXP7000 provides versatile communications. It delivers mission-critical TETRA and 4G LTE broadband voice and data communications, in a secure and rugged Android device.It’s easy to use and operate the MXP7000. The large push-to-talk button lets users connect instantly, and the field-swappable battery helps them stay connected longer. Innovative audio technology enables your personnel to hear and be heard clearly, even in noisy and windy conditions. It has a 5-inch touchscreen and the device can run applications for optimal workforce productivity.The MXP7000 is easy to deploy and manage, and it supports Bluetooth® 5.1 for data transfer. It has a GCAI-mini connector, so you can provide your teams with accessories tailored to their needs.No matter their mission, the MXP7000is a device that helps your teams getthe job done.MXP7000TETRA AND LTE PORTABLE DEVICE YOUR APPS. YOUR COMMS. YOUR TEAM. TOGETHERGENERAL SPECIFICATIONSDimensions Height: 210mm (with antenna) Height: 150mm (without antenna) Width: 80mmDepth: 29.85mm (with battery)Weight440g (with battery and antenna) Battery Options5600mAh IMPRES™ 2Housing Colour BlackGreen (selected models)Display 5.0”, 1280 x 720 Capacitive, touch-screen with Corning® Gorilla® glassSupports use with disposable and combat glovesControls Large Push-to-talk button Emergency buttonDual function rotary knob 2 configurable side buttonsMemory 4GB RAM64GB Internal Storage Supports microSDSIM Slots TETRA SIM: 2FF (Mini SIM) LTE: 4FF (Nano SIM)Camera Rear 13MP, with integrated flash Front 8MPVideo Recording Quality1080p at 60 fpsSensors Proximity Ambient Light Accelerometer Barometer GyroscopeE-CompassPorts GCAI-mini USB-CDEVICE SECURIITYUser Authentication PIN or passwordKey Storage Hardware-backed encryption with Trusted Execution Environment (TEE)Trusted Boot Process Included with the use of tamper resistant hardware OS Hardening Android OS hardening and SELinux access controlAuditing Auditing / logging functionality, with security logs captured and stored in a secured mannerData-at-Rest Using Android’s AES256 File Based Encryption Data-in-Transit Encryption with IPSec VPN supportSecured Device Management With the use of Integrated Terminal Management (iTM) solutionRestricted Recovery Mode Included to avoid unauthorised access to features AUDIOAudio Power at Rated2WAudio Distortion at Rated<1%Audio Power at Maximum3WMax loudness99PhonNoise supression Adaptive Multi-Microphone Beam-Forming Number of Microphones3 dedicated + 1 loudspeaker as microphone TETRA SERVICEAuthentication Infrastructure initiated and made mutual by radio terminal Air Interface Encryption- AlgorithmsTEA 1, TEA 2, TEA 3Protocols - Security ClassesClass 1 (Clear)Class 2 (SCK)Class 3 (DCK/CCK, OTAR-CCK, OTAR-SCK)Class 3G (GCK, OTAR-GCK)End-to-End Encryption SIM based encryption including BSIOther Security FeaturesTemporary disable (stun)Permanent disable (either ETSI standard orcustomer restorable)CONNECTIVITYBluetooth Versions Supported Bluetooth 5.1 (data transfer only)Bluetooth Profiles Generic Attribute (GATT)Attribute Protocol (ATT)Generic Access Profile (GAP)Serial Port Profile (SPP)Personal Area Networking Profile (PAN) Object Push Profile (OPP)Headset Profile (HSP)LOCATION SERVICESConstellation Supported GPS, aGPS, Galileo, GLONASS, BDS (BeiDou) GNSS Antenna Internal antennaGNSS Tracking Sensitivity GPS:-158dBm (50% Fix losses) -162dBm (typical)Horizontal Accuracy, 2D <5m (95% probable, -130dBm) TTFF Cold Start<60 sec (95% probable at -130dBm) ProtocolsETSI LIP (short and long), Motorola Solutions LRRP KEY FEATURES & SETTINGSTalkgroup Management User friendly, flexible, fast and efficient interface TalkgroupsTMO folders: up to 256, TMO talkgroups: up to 10000DMO folders: up to 128, DMO talkgroups: up to 2000 Favourite Talkgroup Folders Up to 3Contacts Management Rapid search to find the contact easilyContacts Up to 1000 contactsMultiple Dialling Methods Dialling direct, scroll and select via touchscreenCall Alert Vibrate alert and set ringtones via Android SettingsFall Alert (Man-down)Triggers an emergency alert if the device is continuouslytilted beyond a pre-defined angleMessage ManagementDistinct folders for each message type forflexible message managementText Message ListUp to 200 entries (short messages)At least 20 entries for outbox(long messages up to 1000 characters)At least 10 entries for inbox(long messages up to 1000 characters)Status ListUp to 100 user-defined messagesAssignable to One Touch ButtonsText Entry Touchscreen for ease of useTransmit Inhibit Disables TETRA transmit and puts device into Airplane Mode 1 TETRA communications is still availableDEVICE MANAGEMENT SOLUTIONSIntegrated Terminal Management (iTM)Supports iTM version 8.0 onwardsENVIRONMENTAL SPECIFICATIONSOperating Temperature 2-20°C to + 60°C Storage Temperature -40°C to +85°CHumidity (High) , Low and High Temperature ETSI 300 019-1-7 class 7.3E Shock (bumps & shock), vibration (random)ETSI 300-019 1-7 class 5M3Dust and Water Ingress ProtectionBlack model: IP68 per IEC 60529Green model: IP67 per IEC 60529 Compliance to US Military Standard 810See table to the right2Performance may be limited when operating at extreme temperatures.US MILITARY STANDARD MATRIXMethodProc/CatLow Pressure 500.6II High Temperature 501.7I/A1,II Low Temperature 502.7I,II Thermal Shock 503.7I-C Solar Radiation 505.7I/A1Humidity 507.6II / AggravatedSalt Fog509.7-Blowing Sand 510.7II Vibration 514.8I/Cat 24,II/Cat 5Shock 3516.8I,IV,VI3Drop test is covered as part of Shock Method 516.8 Proc IV, VIMotorola Solutions UK Limited, Nova South, 160 Victoria Street, London, SW1E 5LB.All specifications are subject to change without notice.MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylised M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under licence. The Bluetooth ® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc. and any use of such marks by Motorola Solutions, Inc. is under licence. All other trademarks are the property of their respective owners. © 2023 Motorola Solutions, Inc. All rights reserved. (09-23)For more information, please visit us at /mxp7000。
Infoprint 250 導入と計画の手引き 第 7 章ホスト
SUBNETMASK
255.255.255.128
Type of service...............: TOS
*NORMAL
Maximum transmission unit.....: MTU
*LIND
Autostart.....................:
AUTOSTART
*YES
: xx.xxx.xxx.xxx
: xx.xxx.xxx.xxx
*
(
)
IEEE802.3
60 1500
: xxxx
48 Infoprint 250
31. AS/400
IP
MTU
1
1
IPDS TCP
CRTPSFCFG (V3R2)
WRKAFP2 (V3R1 & V3R6)
RMTLOCNAME RMTSYS
MODEL
0
Advanced function printing............:
AFP
*YES
AFP attachment........................:
AFPATTACH
*APPC
Online at IPL.........................:
ONLINE
FORMFEED
*CONT
Separator drawer......................:
SEPDRAWER
*FILE
Separator program.....................:
SEPPGM
*NONE
Library.............................:
Cisco Secure ACS 购买指南说明书
Ordering GuideCisco Secure ACSThis document provides guidance on how to order Cisco Secure Access Control System (ACS) family products. It includes information on upgrade scenarios as well as information on software and hardware service offerings.OverviewCisco® ACS is designed to address both current and future corporate network access policy challenges. The world’s most trusted enterprise access and policy platform, it is used by more than 40,000 enterprises worldwide.The Cisco Secure ACS family includes:●Cisco Secure ACS: The Cisco flagship access and policy system, Cisco Secure ACSsupports up to hundreds of thousands of users and tens of thousands of network devices and is ideal for medium or large enterprises.●Cisco Secure ACS View: A dedicated reporting and monitoring device designed tocomplement Cisco Secure ACS, View helps ensure the highest level of network accesscontrol and compliance.●Cisco Secure ACS Express: Ideal for small and medium-sized businesses (SMBs) ormedium/small enterprises, ACS Express is an easy-to-deploy device with built-in reporting and monitoring. It supports up to 50 devices and 350 users.Cisco Secure ACSCisco Secure ACS is available as software for Windows servers (ACS for Windows) and as a dedicated appliance (ACS Solution Engine). Product part numbers are shown in Table 1. For guidelines on Cisco Secure ACS deployment, see the deployment guide at/en/US/products/sw/secursw/ps2086/prod_white_papers_list.html.Table 1. Cisco Secure ACS New Order Part NumbersPart Number DescriptionCSACS-4.2-WIN-K9 Cisco Secure ACS 4.2 for WindowsCSACSE-1113-K9 Cisco ACS Solution Engine – Cisco 1113 hardware with ACS version 4.2 preinstalledFor ACS for Windows, Software Application Support (SAS) is available. SAS entitles customers to maintenance and minor updates, plus access to online resources and support services.For ACS Solution Engine, SAS is required for software coverage and SMARTnet® is required for hardware coverage. SMARTnet has various service options to provide the hardware replacement coverage desired. For more information on SAS and SMARTnet, please visit/en/US/products/svcs/ps3034/ps2827/serv_category_home.html.Software upgrades are available for current ACS for Windows and ACS Solution Engine customers. Customers that have SAS contracts are entitled to minor upgrades. For example, a customer with SAS running ACS version 4.0 software would be entitled to ACS 4.1 and 4.2 upgrades. Customers that do not have SAS contracts can purchase minor upgrades. Part numbers for minor upgrades are identified by the “MR” designation.Customers that have SAS contracts can obtain upgrade kits using the Product Upgrade Tool (requires login) at /upgrade.SAS contracts do not cover major upgrades and these upgrades must always be purchased. For example, customers running ACS for Windows version 3.3 software that want to upgrade to ACS version 4.2 must purchase the upgrade part number CSACS-4.2-WINUP-K9.Upgrade part numbers are shown in Table 2. Note that there are different part numbers for ACS for Windows and ACS Solution Engine software upgrades.Table 2. Cisco Secure ACS Upgrade Part NumbersPart Number DescriptionCSACS4.2-WIN-MR-K9 ACS for Windows minor upgrade for customers with ACS for Windows versions 4.0 or 4.1 CSACS-4.2-WINUP-K9 ACS for Windows major upgrade for customers with ACS for Windows versions earlier than 4.0 CSACSE4.2-SW-MR-K9 ACS Solution Engine minor upgrade for customers with versions 4.0 or 4.1 (1112 or 1113hardware required)CSACSE-4.2-SWUP-K9 ACS Solution major upgrade for customers with versions earlier than 4.0 (1112 or 1113hardware required)CSACSE-1113-UP-K9 ACS Solution Engine hardware and software upgrade – for customers with 1111 or 1112hardware; includes Cisco 1113 hardware with ACS version 4.2 installedImportant: ACS Solution Engine version 4.2 is only supported on Cisco 1112 and 1113 hardware. Customers with Cisco 1111 hardware should consider upgrading to 1113 by purchasing CSACSE-1113-UP-K9. Trade-in credit may also be available through the Cisco Technology Migration Program (TMP).Cisco Secure ACS ViewCisco Secure ACS View collects and correlates data from multiple Cisco Secure ACS servers and logs to provide aggregate views of system activity as well as detailed information at the transaction level for both network access and device administration. Cisco Secure ACS View provides essential information for network monitoring and planning, access problem detection and troubleshooting, and entitlement and compliance reporting.Cisco Secure ACS View is recommended for all ACS 4.2 deployments. For guidelines on Cisco Secure ACS View deployment, see the deployment guide at/en/US/products/ps9302/prod_white_papers_list.html.Cisco Secure ACS View part numbers are shown in Table 3.Table 3. Cisco Secure ACS View Part NumbersPart Number DescriptionCSACS4.0-VIEW-K9 Cisco Secure ACS View appliance with ACS View 4.0 software and license for managing twoACS servers (version 4.1.4 or 4.2 required). ACS View does not support ACS Express.CSACS4.0-VIEWLIC License for managing an additional ACS server with Cisco Secure ACS View 4.0.For the ACS View appliance, an SAS contract is required for software coverage and SMARTnet isrequired for hardware coverage. SAS entitles customers to maintenance and minor updates, plusaccess to online resources and support services.Cisco Secure ACS ExpressCisco Secure ACS Express offers a comprehensive yet simplified feature set, a user-friendlygraphical user interface, and an attractive price point that allows placement of this product insituations where Cisco Secure ACS for Windows or Cisco Secure ACS Solution Engine may notbe suitable.Cisco Secure ACS Express part numbers are shown in Table 4.Table 4. Cisco Secure ACS Express Part NumbersPart Number DescriptionCSACS-5.0-EXP-K9 Cisco Secure ACS Express 5.0 applianceFor ACS Express, an SAS contract is required for software coverage and SMARTnet is requiredfor hardware coverage. SAS entitles customers to maintenance and minor updates, plus access toonline resources and support services.For More InformationPlease check the Cisco Secure ACS homepage at /go/acs for the latestinformation about Cisco Secure ACS.For more information contact the ACS marketing team at *****************, or contact youraccount representative.Printed in USA C07-500695-00 10/08。
LTC2208 16 14 位 ADC 示范电路 854 130MSPS ADC说明书
QUICK START GUIDE FOR DEMONSTRATION CIRCUIT 85416/14 BIT, 130,105, 80, 65 MSPS ADCLTC2208, LTC2208-14, LTC2217, LTC2216, LTC2215DESCRIPTION DESCRIPTIONDemonstration circuit 854 supports a family of 16/14-Bit 130Msps ADCs. Each assembly features one of the following devices: LTC2208, LTC2208-14, LTC2217, LTC2216, LTC2215 high speed family of high dynamic range ADCs.This Demonstration circuit only supports CMOS operation. For demonstration of LVDS output sig-naling, please see DC996.Other members of this family include the LTC2207, a 105Msps 16-Bit CMOS-only version of this device, as well as lower speed versions and single-ended clock versions. These 7x7mm QFN devices are supported by Demonstration circuits 918 and 919 (for single-ended clock input).The versions of the DC854C and DC854D demoboard that support the LTC2208 16-Bit and LTC2208-14 14-Bit series of A/D converters are listed in Table 1. Depending on the required reso-lution, sample rate and input frequency, the DC854 is supplied with the appropriate ADC and with an optimized input circuit. The circuitry on the analog inputs is optimized for analog input frequencies be-low 70MHz or from 70MHz to 140MHz. For higher input frequencies, contact the factory for support. avai Design files for this circuit board are avail l able. Call the LTC factory.Call the LTC factory.LTC is a trademark of Linear Technology Corporation1. DC854 Variants DC854 VariantsDC854 VARIANT DC854 VARIANTS SADC PART NUMBER ADC PART NUMBERRESOLUTION*RESOLUTION*MAXIMUM SA MAXIMUM SAM M PLE RATE PLE RATEINPUT FREQUENCY INPUT FREQUENCY 854D-A LTC2208 16-Bit 130Msps 1MHz - 70MHz 854D-B LTC2208 16-Bit 130Msps 70MHz -140MHz 854D-C LTC2208-14 14-Bit 130Msps 1MHz - 70MHz 854D-D LTC2208-14 14-Bit 130Msps 70MHz -140MHz 854D-E LTC2217 16-Bit 105Msps 1MHz - 70MHz 854D-F LTC2217 16-Bit 105Msps 70MHz -140MHz 854D-G LTC2216 16-Bit 80Msps 1MHz - 70MHz 854D-H LTC2216 16-Bit 80Msps 70MHz -140MHz 854D-I LTC2215 16-Bit 65Msps 1MHz - 70MHz 854D-J LTC2215 16-Bit 65Msps 70MHz -140MHz 854C-P LTC2208 16-Bit 130Msps >140MHz 854C-QLTC2208-1414-Bit130Msps>140MHz2. Performance Su Performance Sum m mary (T A = 25°C) = 25°C)PARAMETER PARAMETER CONDITION CONDITIONVALUE VALUESupply Voltage Depending on sampling rate and the A/D converter provided, this supply must provide up to 500mA. Optimized for 3.3V[3.15V 3.45V min/max] Analog input range Depending on PGA Pin Voltage 1.5V PP to 2.25V PP Minimum Logic High 2.4V Logic Input Voltages Maximum Logic Low0.8V*********************** 2.3V (33Ω Series terminations) Logic Output Voltage(74VCX245 output buffer, V cc = 2.5V)*********************0.7V (33Ω Series terminations) Sampling Frequency (Convert Clock Frequency) See Table 1Convert Clock Level50 Ω Source Impedance, AC coupled or ground referenced (Convert Clock input is capacitor coupled on board and ter-minated with 50Ω.) 2V P-P 2.5V P-P Sine Wave or Square wave ResolutionSee Table 1 Input frequency range See Table 1SFDR See Applicable Data Sheet SNRSee Applicable Data SheetQUICK START PROCEDUR QUICK START PROCEDURE EDemonstration circuit 854 is easy to set up to evalu-ate the performance of most members of the LTC2208 family of A/D converters. Refer to Figure 1for proper measurement equipment setup and follow the procedure below:SETUP SETUPIf a DC718 QuickDAACS Data Analysis and Collection System was supplied with the DC854 demonstration circuit, follow the DC718 Quick Start Guide to install the required software and for connecting the DC718 to the DC854 and to a PC running Windows98, 2000 or XP .1) DC854 Setup (zoom for detail)JUMP JUMPERS ERS ERSThe DC854 demonstration circuit board should have the following jumper set-tings as default: (as per figure 1) JP1: Output clock polarity: GNDJP2: SENSE: VDD, (Internal reference) JP3: PGA: GND 2.25V range JP4: RAND: GND Not randomized JP5: SHDN: GND Not ShutdownJP6: DITH: GND No internal ditheringPOWERIf a DC718 is used to acquire data from the DC854, the DC718 must FIRST be connected to a powered USB port or provided an external 6-9V BEFORE ap-plying +3.3V across the pins marked “+3.3V” and “PWR GND” on the DC854. The DC854 demonstra-tion circuit requires up to 500mA depending on the sampling rate and the A/D converter supplied. The DC718 data collection board is powered by the USB cable and does not require an external power supply unless it is connected to the PC through an un-powered hub. In this case it must be supplied with 6-9V on turrets G7 (+) and G1 (-) or the adja-cent 2.1mm power jack.ENCODE CLOCK ENCODE CLOCKNOTE: This is not a logic compatible i NOTE: This is not a logic compatible in n put. It is termi terminated with 50 Ohms nated with 50 Ohmsnated with 50 Ohms. Apply an encode clock to the SMA connector on the DC854 demonstration circuit board marked “J3 ENCODE INPUT”. The transformer is terminated on the secondary side with 100 ohms, and further terminated at the ADC (at C11).For the best noise performance, the ENCODE INPUT must be driven with a very low jitter source. When using a sinusoidal generator, the amplitude should often be large, up to 3V P-P or 13dBm. Using band pass filters on the clock and the analog input will improve the noise performance by reducing the wideband noise power of the signals. Data sheet FFT plots are taken with 10 pole LC filters made by TTE (Los Angeles, CA) to suppress signal generator harmonics, non-harmonically related spurs and broad band noise. Low phase noise Agilent 8644B generators are used with TTE band pass filters for both the Clock input and the Analog input. Apply the analog input signal of interest to the SMA connectors on the DC854 demonstration circuit board marked “J2 ANALOG INPUT”. These inputsare capacitive coupled to Balun transformers ETC1-1-13, or directly coupled through Flux coupled transformers ETC1-1T. (See Schematic) ANALOG INPUT NETWORK ANALOG INPUT NETWORKFor optimal distortion and noise performance the RC network on the analog inputs should be opti-mized for different analog input frequencies. Refer to the provided schematics. These two input net-works cover a broad bandwidth and are not opti-mized for operation at a specific input frequency. For input frequencies less than 5MHz, or greater than 150MHz, other input networks may be more appropriate.In almost all cases, filters will be required on both analog input and encode clock to provide data sheet SNR.This Demo board has provision for additional com-ponents that may be used to implement a band pass filter, or more optimal return loss in a given frequency range. The default population is a simple network as shown below.In some cases, 3-10dB pads may be required to obtain low distortion.If your generator cannot deliver full scale signals without distortion, you may benefit from a medium power amplifier based on a Gallium Arsenide Gain block prior to the final filter. This is particularly true at higher frequencies where IC based operational amplifiers may be unable to deliver the combination of low noise figure and High IP3 point required. A high order filter can be used prior to this final am-plifier, and a relatively low Q filter used between the amplifier and the demo circuit.DIGITAL OUTPUTS DIGITAL OUTPUTSAn internally generated conversion clock output is available on pin 3 of J1 and the data samples are available on Pins 7-37 for 16-Bits (or 7-33 for 14-Bits) of J1 which can be collected via a logic ana-lyzer, cabled to a development system through aSHORT 2 to 4 inch long 40-pin ribbon cable or col-lected by the DC718 QuickEval-II Data Acquisition Board.SOFTWARESOFTWAREThe DC718B board is configurable by PScope Sys-tem Software provided or down loaded from the Linear Technology website at /software/. If a DC718 was provided, follow the DC718 Quick Start Guide and the instructions below.To start the data collection software if “PScope.exe”, is installed (by default) in \Program Files\LTC\PScope\, double click the PScope Icon or bring up the run window under the start menu and browse to the PScope directory and select PScope.If the DC854 demonstration circuit is properly con-nected to the DC718, PSCOPE should automatically detect the DC854, and configure itself accordingly. If necessary the procedure below explains how to manually configure PSCOPE.Configure PScope for the appropriate variant of the DC854 demonstration circuit by selecting the cor-rect A/D Converter as installed on the DC854. Un-der the “Configure” menu, go to “Device.” Under the “Device” pull down menu, select the appropriate device. Selecting the part in the Device List will automatically blank the last two LSBs when using a DC854 supplied with a 14-Bit part. If you are oper-ating with a version of PScope that does not include the IC of interest it can be manually selected by us-ing the device menu. PScope may be manually configure by selecting the following options:User configure16-Bit (or 14-Bit if using LTC2208-14) Alignment: Left-16Bipolar (2’s complement)Positive clock edgeType: CMOSIf everything is hooked up properly, powered and a suitable convert clock is present, clicking the “Col-lect” button should result in time and frequency plots displayed in the PScope window. Additional information and help for PScope is available in the DC718 Quick Start Guide and in the online help available within the PScope program itself.。
个人信息安全 英语作文
Personal information security is a critical issue in todays digital age.With the rapid advancement of technology,our personal data is increasingly being collected,stored,and processed.This has led to a heightened need for individuals to be aware of how to protect their information and safeguard their privacy.The Importance of Personal Information SecurityPersonal information security is essential for several reasons.Firstly,it helps to prevent identity theft,which can lead to financial loss and damage to ones reputation.Secondly,it ensures that sensitive data such as medical records and financial transactions remain confidential.Thirdly,it protects individuals from cyberbullying and harassment,which can have severe psychological impacts.Threats to Personal Information SecurityThere are numerous threats to personal information security,including:1.Phishing Attacks:These are attempts to trick individuals into revealing their personal information through deceptive emails,text messages,or websites.2.Malware:Malicious software can infect devices and steal personal data without the users knowledge.3.Data Breaches:Companies and organizations can be compromised,leading to the exposure of customer data.4.Social Engineering:Manipulative tactics used to extract information from individuals by exploiting their trust or curiosity.Strategies for Protecting Personal InformationTo safeguard personal information,individuals can adopt the following strategies:e Strong Passwords:Create complex passwords that are difficult to guess and change them regularly.2.Enable TwoFactor Authentication:This adds an extra layer of security by requiring a second form of verification.3.Be Cautious with Public WiFi:Public networks can be insecure,making it easier for hackers to intercept data.4.Regularly Update Software:Keeping devices and applications updated can protect against known vulnerabilities.5.Limit Information Sharing:Be mindful of the personal information shared on social media and other online platforms.e Secure Websites:Look for websites that use HTTPS,which encrypts data during transmission.The Role of Legislation and RegulationGovernments and regulatory bodies play a crucial role in ensuring personal information security.They can enact laws that require companies to protect customer data and impose penalties for noncompliance.Additionally,they can educate the public about the importance of data protection and the steps they can take to safeguard their information.ConclusionIn conclusion,personal information security is a shared responsibility that requires vigilance from both individuals and organizations.By being proactive and informed,we can protect our data and enjoy the benefits of technology without compromising our privacy.It is essential to stay updated on the latest security practices and to be aware of the potential risks associated with our digital footprint.。
Microchip CoreFIR_PF v3.0 多项式滤波器核心数据手册说明书
CoreFIR_PF Release NotesCoreFIR_PF provides a configurable high performance Multiplier-Accumulator (MACC)-based FIR filter. The core is available as a Register Transfer Level (RTL) code of the filter in VHDL language.This release notes is a part of the production release of CoreFIR_PF v3.0. This document provides details about the features, enhancements, system requirements, supported families, implementations, known issues, workarounds, and resolved issues.Features (Ask a Question)CoreFIR_PF supports various filter types: Fully Enumerated and polyphase interpolator. The following table liststhe key features for each type.Supported Families (Ask a Question)•PolarFire® SoC•PolarFireTable of ContentsIntroduction (1)Features (1)Supported Families (1)1. Overview (3)1.1. Licensing (3)1.2. Supported Tool Flows (3)1.3. Installation Instructions (3)1.4. Supported Test Environments (3)2. Discontinued Features and Devices (4)3. Known Limitations and Workarounds (5)4. Resolved Issues (6)4.1. Resolved Issues in the CoreFIR_PF v3.0 Release (6)4.2. Resolved Issues in the CoreFIR_PF v2.3 Release (6)4.3. Resolved Issues in the CoreFIR_PF v2.2 Release (6)4.4. Resolved Issues in the CoreFIR_PF v2.1 Release (6)4.5. Resolved Issues in the CoreFIR_PF v2.0 Release (6)5. Revision History (7)Microchip FPGA Support (8)Microchip Information (8)The Microchip Website (8)Product Change Notification Service (8)Customer Support (8)Microchip Devices Code Protection Feature (8)Legal Notice (9)Trademarks (9)Quality Management System (10)Worldwide Sales and Service (11)Overview 1. Overview (Ask a Question)This release contains a copy of the CoreFIR_PF user guide. The user guide, describes the IP corefunctionalities and provides step-by-step instructions on how to simulate, synthesize, and place-and-route this IP core, and also provides implementation suggestions.For updates and additional information about the software, devices, and hardware, visit theIntellectual Property pages on the Microchip FPGA Products Group website.1.1 Licensing (Ask a Question)CoreFIR_PF is freely distributed with Microchip Libero SoC. Complete HDL source code is providedfor the core and testbenches.1.2 Supported Tool Flows (Ask a Question)CoreFIR_PF v3.0 requires Libero System-on-Chip (SoC) software v12.0 or later.1.3 Installation Instructions (Ask a Question)The IP core must be installed to the IP Catalog of Libero SoC software. This is done automaticallythrough the IP Catalog update function in Libero SoC software, or the IP core can be manuallydownloaded from the catalog. Once the IP core is installed in Libero SoC software IP Catalog, thecore can be configured, generated, and instantiated within SmartDesign for inclusion in the Liberoproject.1.4 Supported Test Environments (Ask a Question)The test environment supported for default configuration constant coefficient set, VHDL usertestbench.Discontinued Features and Devices 2. Discontinued Features and Devices (Ask a Question)CoreFIR_PF discontinued support for SmartFusion2 and IGLOO2 devices. These devices aresupported in CoreFIR v8.6.Known Limitations and Workarounds 3. Known Limitations and Workarounds (Ask a Question)None.4. Resolved Issues (Ask a Question)This topic describes the resolved issues for the various CoreFIR_PF core releases.4.1 Resolved Issues in the CoreFIR_PF v3.0 Release (Ask a Question)The following table lists all the resolved issues in the CoreFIR_PF v3.0 release.4.2 Resolved Issues in the CoreFIR_PF v2.3 Release (Ask a Question)There were no issues reported or resolved in the CoreFIR_PF v2.3 release. PolarFire SoC support was added.4.3 Resolved Issues in the CoreFIR_PF v2.2 Release (Ask a Question)The following table lists all the resolved issues in the CoreFIR_PF v2.2 release.4.4 Resolved Issues in the CoreFIR_PF v2.1 Release (Ask a Question)The following table lists all the resolved issues in the CoreFIR_PF v2.1 release.4.5 Resolved Issues in the CoreFIR_PF v2.0 Release (Ask a Question)The following table lists all the resolved issues in the CoreFIR_PF v2.0 release.5. Revision History (Ask a Question)The revision history describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication.Microchip FPGA products group backs its products with various support services, including Customer Service, Customer Technical Support Center, a website, and worldwide sales offices. Customers are suggested to visit Microchip online resources prior to contacting support as it is very likely that their queries have been already answered.Contact Technical Support Center through the website at /support. Mention the FPGA Device Part number, select appropriate case category, and upload design files while creating a technical support case.Contact Customer Service for non-technical product support, such as product pricing, product upgrades, update information, order status, and authorization.•From North America, call 800.262.1060•From the rest of the world, call 650.318.4460•Fax, from anywhere in the world, 650.318.8044The Microchip Website (Ask a Question)Microchip provides online support via our website at /. This website is used to make files and information easily available to customers. Some of the content available includes:•Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software•General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online discussion groups, Microchip design partner program member listing•Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factoryrepresentativesProduct Change Notification Service (Ask a Question)Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will receive email notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest.To register, go to /pcn and follow the registration instructions.Customer Support (Ask a Question)Users of Microchip products can receive assistance through several channels:•Distributor or Representative•Local Sales Office•Embedded Solutions Engineer (ESE)•Technical SupportCustomers should contact their distributor, representative or ESE for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in this document. Technical support is available through the website at: /support Microchip Devices Code Protection Feature (Ask a Question)Note the following details of the code protection feature on Microchip products:•Microchip products meet the specifications contained in their particular Microchip Data Sheet.•Microchip believes that its family of products is secure when used in the intended manner, within operating specifications, and under normal conditions.•Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code protection features of Microchip product is strictly prohibited and may violate the Digital Millennium Copyright Act.•Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code protection does not mean that we are guaranteeing the product is “unbreakable”.Code protection is constantly evolving. Microchip is committed to continuously improving the code protection features of our products.Legal Notice (Ask a Question)This publication and the information herein may be used only with Microchip products, includingto design, test, and integrate Microchip products with your application. Use of this informationin any other manner violates these terms. Information regarding device applications is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. Contact your local Microchip sales office for additional support or, obtain additional support at /en-us/support/design-help/ client-support-services.THIS INFORMATION IS PROVIDED BY MICROCHIP "AS IS". MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION ORITS USE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THE INFORMATION.Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.Trademarks (Ask a Question)The Microchip name and logo, the Microchip logo, Adaptec, AVR, AVR logo, AVR Freaks, BesTime, BitCloud, CryptoMemory, CryptoRF, dsPIC, flexPWR, HELDO, IGLOO, JukeBlox, KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, Flashtec, Hyper Speed Control, HyperLight Load, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus, ProASIC Plus logo, Quiet- Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider, TrueTime, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, Augmented Switching, BlueSky, BodyCom, Clockstudio, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM, , DynamicAverage Matching, DAM, ECAN, Espresso T1S, EtherGREEN, GridTime, IdealBridge, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, IntelliMOS, Inter-Chip Connectivity, JitterBlocker, Knob-on-Display, KoD, maxCrypto, maxView, memBrain, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, , PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, RTAX, RTG4, SAM-ICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SmartHLS, SMART-I.S., storClad, SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, Trusted Time, TSHARC, USBCheck, VariSense, VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks of Microchip Technology Inc. in other countries.GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.All other trademarks mentioned herein are property of their respective companies.© 2023, Microchip Technology Incorporated and its subsidiaries. All Rights Reserved.ISBN:Quality Management System (Ask a Question)For information regarding Microchip’s Quality Management Systems, please visit/quality.Worldwide Sales and ServiceRelease Note© 2023 Microchip Technology Inc. and its subsidiaries A - 11。
Poly VVX 450 IP 电话 - OBI 版说明书
POLY VVX 450 IP PHONE - OBI EDITIONMore lines—more contacts at your fingertips. Feel in command of your day with this high quality, color, twelve-line phone that gets the job done without distracting background noise. Be confident that your conversations will always sound great on Google Voice and other selected cloud VoIP platforms. IT will appreciate robust provisioning and management capabilities that take the headache out of telephony deployment and support. Need even more lines? The optional VVX EM50 expansion module puts them right where you need them.• 12 line keys with a 4.3 inch color LCD display (480 x 272 pixels)• Crystal clear sound with Poly HD Voice and Poly Acoustic Clarity • Full duplex speakerphone with world-class echo cancellation • Easy to install anywhere with optional Poly Wi-Fi USB accessory • Headset options to suit any style (USB, RJ9, EHS ports)GO PRO WITH TWELVE LINESBENEFITS• C onversations stay on track. Hear every nuance with industry-leading sound quality featuring Poly HD Voice • Eliminate distracting background noise at the source with exclusive award-winning Poly Acoustic Fence technology • With the Obi Edition VVX, every pixel can be customized to reflect a corporate brand, color or image• Easy deployment and administration with web-based management tools andzero-touch provisioningSPECIFICATIONSUSER INTERFACE FEATURES• 4.3” color LCD (480x272 pixel resolution) • Adjustable base height• Unicode UTF-8 character support• Two USB ports (2.0 compliant) for Plantronics USB headsets or Wi-Fi5G dongle• Multilingual user interface including Chinese, Danish, Dutch, English (Canada/ US/UK), French, German, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Russian, Slovenian, Spanish and Swedish AUDIO FEATURES• Poly HD Voice delivers lifelike voice quality for each audio path, handset, hands-free speakerphone, and optional headset.• Poly Acoustic Clarity provides full-duplex conversations, acoustic echo cancellation and background noise suppression.• TIA-920 wideband audio type 1-compliant (IEEE 1329 full duplex)• Frequency response—150 Hz—7 kHz for handset, optional headset and handsfree speakerphone modes• Codecs: G.711 (A-law and μ-law), G.729AB, G.722 (HD Voice), iLBC, OPUS• Individual volume settings with visual feedback for each audio path• Voice activity detection• Comfort noise generation• DTMF tone generation (RFC 2833and in-band)• Low-delay audio packet transmission• Adaptive jitter buffers• Packet loss concealment HEADSET AND HANDSET COMPATIBILITY• Dedicated RJ-9 headset port• Hearing aid compatibility to ITU-T P.370 andTIA 504A standards• Compliant with ADA Section 508 Subpart B1194.23 (all)• Hearing aid compatible (HAC) handset formagnetic coupling to hearing aids• Compatible with commercially-available TTYadapter equipmentCALL HANDLING FEATURES• 12 lines (programmable line keys)• Shared call/bridged line appearance• Busy lamp field (BLF)• Flexible line appearance (one or moreline keys can be assigned for eachline extension)• Distinctive incoming call treatment/call waiting• Call timer and call waiting• Call transfer, hold, divert (forward), pickup• Called, calling, connected party information• Local three-way audio conferencing• One-touch speed dial, redial remote missedcall notification• Do not disturb function• Electronic hook switch capable• Local configurable digit map/dial plan• OBi XML applications• Corporate directory access using LDAPNETWORK AND PROVISIONING• SIP protocol support• SDP• IETF SIP (RFC 3261 and companion RFCs)• Two-port Gigabit Ethernet switch10/100/1000Base-TX across LAN andPC ports• Conforms to IEEE802.3-2005 (Clause 40)for Physical media attachment• Conforms to IEEE802.3-2002 (Clause 28)for link partner auto-negotiation• Static or dynamic host configurationprotocol (DHCP) network setup• Time and date synchronization using SNTP• TFTP/HTTP/HTTPS server-based centralprovisioning for mass deployments• call server redundancy supported1• QoS Support—IEEE 802.1p/Q tagging• (VLAN), Layer 3 TOS,• DHCP VLAN discovery, LLDP-MED forVLAN discovery• Network address translation support forstatic configuration and “keep-alive”• RTCP and RTP support• Event logging• Syslog• Hardware diagnostics• Status and statistics reporting• IPv4• TCP• UDP• DNS-SRVPOLY VVX 450 IP PHONE -OBI EDITIONSECURITY• 802.1X authentication and EAPOL media encryption via SRTP• Transport layer security (TLS)• Encrypted configuration files• Digest authentication• Password login• HTTPS secure provisioning• Support for signed software executables POWER• Built-in auto sensing IEEE 802.3af power over Ethernet (Class 0) 13W (Max)• External Universal AC/DC Adapter (optional) 5VDC @ 3A (15W)• ENERGY STAR® ratedAPPROVALS• FCC Part 15 (CFR 47) Class B• ICES-003 Class B• EN55032 Class B• CISPR32 Class B• VCCI Class B• EN55024• EN61000-3-2; EN61000-3-3• NZ Telepermit• Korea KCC• UAE TRA • Russia CU• Brazil ANATEL• Australia RCM• South Africa ICASA• Saudi Arabia CITC• Indonesia SDPPI• S.Korea KC• Mexico NOM ANCE• RoHS Compliant• TAASAFETY• UL 60950-1/62368-1• CE Mark• CAN/CSA C22.2 No 60950-1/62368-1-1• EN 60950-1/62368-1• IEC 60950-1/62368-1• AS/NZS 60950-1OPERATING CONDITIONS• Temperature-0 to 40°C (+32 to 104°F)• Relative humidity-5% to 95%, noncondensingSTORAGE TEMPERATURE• -40 to +70° C (-40 to +160° F)POLYCOM VVX 450 COMES WITH• Console• Handset with handset cord• Network (LAN) cable—CAT-5E• Desk stand/wall mount bracket• Setup sheetSIZE• 24cm x 23cm x 5.7cm WxHxD• 9.5in x 10in x 2.2in WxHxDPART NUMBER• 2200-48842-025 OBi Edition VVX 450 PoEWEIGHT• Carton weight- 1.043kg (2.23 lbs)MASTER CARTON QUANTITY• Ten (10)WARRANTY• One (1) year1. M ost software-enabled features and capabilitiesmust be supported by the server. Please contactyour IP PBX/Softswitch vendor or serviceprovider for a list of supported features.©2020 Plantronics, Inc. All rights reserved. Poly and the propeller design are trademarks of Plantronics, Inc. The Bluetooth trademark is owned by Bluetooth LEARN MOREFor more information on Poly VVX 450 IP Phone - Obi Edition visitwww. /us/en/products/phones。
Poly Clariti解决方案规范:Poly Clariti核心和Poly Clariti边缘主机
POLY CLARITI SOLUTION SPECIFICATIONSPOLY CLARITI CORE AND POLY CLARITI EDGE HOST SPECIFICATIONS AND CAPACITIESVirtual Machine (KVM), Amazon Web Services (AWS), and Appliance Server Virtual Machine (KVM), Amazon Web Services (AWS), and Appliance ServerVirtual Core612Minimum CPU Speed 2.4 GHz 2.4 GHzTotal Required GHz14.4 GHz28.8 GHzMinimum CPU Family Haswell HaswellMemory16GB16GBStorage146 GB146GBRandom IOPS110 total210 totalPerformance200 concurrent calls• Poly Core-5000 concur rent calls-Up to 1200 H.323 calls, not to exceed 5000total calls-Up to 3600 SIP calls (encrypted orunencrypted), not to exceed 5000 total calls• Poly Edge and combination systems(Poly Clariti Core and Poly Clariti Edge)-Up to 1000 concurrent callsNote• AWS deployment-Use instance type t2.2xlarge• Azure deployment-Use instance type D8d v4• AWS deployment-Use instance type t4.4xlarge • Azure deployment-Use instance type D16s v2POLY CLARITI RELAY HOST SPECIFICATIONS AND CAPACITIESVirtual Machine (KVM), and Amazon Web Services (AWS)Virtual Machine (KVM), and Amazon Web Services (AWS)Virtual Core612Minimum CPU Speed 2.4 GHz 2.4 GHzTotal Required GHz14.4 GHz28.8 GHzMinimum CPU Family Haswell HaswellMemory16GB16GBStorage146 GB146GBRandom IOPS110 total210 totalPerformance200 concurrent calls• Poly Clariti Relay-Up to 1000 concurrent callsNote• AWS deployment-Use instance type t2.2xlarge• Azure deployment-Use instance type D8d v4• AWS deployment-Use instance type t4.4xlarge • Azure deployment-Use instance type D16s v2POLY CLARITI WORKFLOW LITE HOST SPECIFICATIONS AND CAPACITIESVirtual Machine (KVM), Amazon Web Services (AWS), and customer server Virtual Machine (KVM), Amazon Web Services (AWS), and customer serverOperating System Customer provided Microsoft Server Customer provided Microsoft Server Virtual Core24Minimum CPU Speed 2.4 GHz 2.4 GHzTotal Required GHz 4.8 GHz9.6 GHzMinimum CPU Family Haswell HaswellMemory8 GB16 GBStorage80 GB80 GBRandom IOPS110 total210 totalPerformance Up to 500 devices Up to 1000 devicesNote• AWS deployment-Use instance type t2.2xlarge• Azure deployment-Use instance type D8d v4• AWS deployment-Use instance type t2.xlarge • Azure deployment-Use instance type D4d v4POLY CLARITI CORE AND POLY CLARITI EDGE FEATURES• Redundant/fault tolerant application clusters• Cluster/supercluster configuration • Geographical distribution of application cluster• Geographic distribution of MCUs• Web server for Poly Clariti App and Poly Clariti Roster• Poly Clariti Relay MCU management • Poly EVO Signaling• Conference Control (Roster) APIs• Signaling gateway between SIP MRC and Poly EVO• Access proxy• Firewall/NAT traversal• Combined edge and corecombo configuration for all core conferencing and firewall traversal needs on one device• Auto-cascade for size and bandwidth • SVC cascade between RPCS/RMX and Poly Clariti Relay MCUs• Automatic call routing using H.323/SIP • API Suite for provisioning, billing and conference management• Automatic SIP conference failover• Unified communications support• Configurable conference templates • Configurable group policies• Support of multiple dial plans• HTML5 user interface for administration • Point-to-point call to VMR escalation (works with Poly Group Series v6.1.5 or higher)• Simplified deployment options for Polycom ContentConnect using the Clariti Core MatchMaker load balancer • SIP and H.323 remote users (registered/ provisioned endpoints)• SIP and H.323 guest users (unregistered/ un-provisioned endpoints)• SIP and H.323 business-to-business calling• RTP/SRTP media relay• AVC and SVC support• LDAP/H.350 directory • XMPP presence• HTTPS/XML provisioning• TLS security• STUN/TURN server• E.164 dialing• Poly EVO audio/video/content• H.323 audio/video/content• SIP audio/video/content support• PSTN/ISDN audio/video via PolycomRealPresence Collaboration Server2000/4000• Telepresence Interoperability Protocol(TIP)• License pooling across clusters• Support for NIC bonding• High system availability-Duplicate application servers (clusters)-Geographically distributed• Scalable Video Coding (SVC)• VLAN Reliability• Supports full redundancy with automaticfailover• Cluster and super cluster configurationsfor full redundancy with automaticfailover throughout the networkapplication clusters-Replicated databases-Synchronized data updates and callprocessing-Mix and match appliance and virtualmachine for high availability• Media server and dynamic resource(port) management-Multiple routing policies: zone-based,least used, priority-Media server management Capacity• Supports up to 64 Polycom RealPresenceCollaboration Servers and CiscoTelepresence MCU• Single cluster (node) supports:-Registrations: 15,000-Point to point concurrent calls: 5,000-VMR concurrent calls - SIP = 2,400 -H.323 = 1,200 Poly EVO = 5000• Supercluster-up to 10 servers in a cluster• Poly Clariti Edge supports up to 1,000concurrent calls• Linux operating system• Integration with existing IT accesscontrol mechanisms (e.g., MicrosoftActive Directory)• Lock-down of all nonessential services• Does not provide or affect AssuredServices Features (ASFs)• Access List (ACL) Call control features• SIP registrar as released, reducedowntime• User adoption services• Increase usage through training andawareness• Support services- Access features and enhancementsPOLY CLARITI RELAY FEATURESPOLY CLARITI WORKFLOW LITE FEATURESPOLY CLARITI APP FEATURESVIDEO SUPPORT• From QCIF to 1080p including intermediate resolutions • H.264 (H.264 Annex G (SVC) • 16:9 aspect ratio• H.264 content sharing resolution • No video / content transcoding • High scale AUDIO SUPPORT• Siren 22 LPR for SVC calls • Siren 22 LPR SAC (Scalable Audio Coding) for SVC calls • Opus for SVC callsIP QOS• Polycom Lost Packet Recovery (LPR) • Polycom error resiliency algorithms for SVC calls • DiffServ• Voice and video error concealment NETWORK SUPPORT• SRTP Support–video and content • SIP video and content • IPV4• 10/100/1000 Mb interfaceSECURITY• AES 128/256 bit media encryption • Transport layer security (Poly EVO and management network) • Unified conferencing (voice, video and data) -Advanced error resiliency for SVC calls -Lobby support-SVC cascade with Poly RealPresence Collaboration Server/RMX MANAGEMENT• Done via Poly Clariti Core/EdgeSIMPLIFIED SCHEDULING • Interoperability -Poly EVO -SIP-H.323 conferences • Calendaring-Microsoft Exchange Server 2010 or after, Microsoft Office 365 with Modern Auth, Microsoft Office 365 vNext • SSO integration• VMR/Meeting ID-Random, Assigned, Manual Entry, Audio/Video mute on Join, meeting passcodes • Customizable meeting invitation/notification templates • Deploy templates and settings for mass user deployment • One Touch Dial (OTD) from Poly Endpoints• Poly Studio X30, Poly Studio X50 and G7500• Poly EVO Client • Poly Group Series • Polycom HDX • RealPresence Desktop • High Availability Support• Upgrade from Poly Clariti Workflow Lite to Poly Clariti Workflow SuiteVIDEO SUPPORT • H.264• Up to 16 Streams visible • Up to 1080p/30 fps AUDIO SUPPORT • Opus• Content support• Configurable content sharing policy • Up to 1080p/30 fps BROWSER SUPPORT • ChromeSECURITY• dTLS (SRTP with AES 128/256 bit) for media encryption • HTTPS signalingEND USER CALL CONTROLS • Group Chat • Polling/voting • Hand Raising• Mute/Unmute Self/Other • Mute/Unmute on Join • Participant List• Chairperson/Moderator • Guest Mode• Integration with Outlook via Poly Workflow Lite Easy Schedule add-in LICENSING• Poly Clariti Call License • Management• Done via Poly Clariti Core/Edge • Content support• Configurable content sharing policy • Up to 1080p/30 fps SIGNALING• WebRTC with Poly EVO©2021 Plantronics, Inc. All rights reserved. Poly and the propeller design are trademarks of Plantronics, Inc. The Bluetooth trademark is owned by Bluetooth SIG, Inc. and any use of the mark by Plantronics, Inc. is under license. All other trademarks are the property of their respective owners. 7.21 1294288LEARN MOREFor more information about Poly Services, contact your authorized Poly representative for partner. Alternately, visit 。
TD信息元素详解
信息元素功能性定义作者:李欣目录目录 (1)信息元素功能性定义 (11)1 核心网信息元素 (11)1.1 CN Information elements (11)1.2 CN Domain System Information (11)1.3 CN Information info (11)1.4 IMEI (11)1.5 IMSI (GSM-MAP) (11)1.6 Intra Domain NAS Node Selector (11)1.7 Location Area Identification (12)1.8 NAS message (12)1.9 NAS system information (GSM-MAP) (12)1.10 Paging record type identifier (12)1.11 PLMN identity (12)1.12 PLMN Type (12)1.13 P-TMSI (GSM-MAP) (12)1.14 RAB identity (12)1.15 Routing Area Code (12)1.16 Routing Area Identification (13)1.17 TMSI (GSM-MAP) (13)2 UTRAN 移动信息元素 (13)2.1 Cell Access Restriction (13)2.2 Cell identity (13)2.3 Cell selection and re-selection info for SIB3/4 (13)2.4 Cell selection and re-selection info for SIB11/12 (13)2.5 Mapping Info (14)2.6 URA identity (14)3 UE 信息元素 (14)3.1 Activation time (14)3.2 Capability Update Requirement (14)3.3 Cell update cause (15)3.4 Ciphering Algorithm (15)3.5 Ciphering mode info (15)3.6 CN domain specific DRX cycle length coefficient (15)3.7 CPCH Parameters (15)3.8 C-RNTI (15)3.9 DRAC system information (15)3.10 Void (16)3.11 Establishment cause (16)3.12 Expiration Time Factor (16)3.13 Failure cause (16)3.14 Failure cause and error information (16)3.15 Initial UE identity (16)3.16 Integrity check info (16)3.17 Integrity protection activation info (17)3.18 Integrity protection Algorithm (17)3.19 Integrity protection mode info (17)3.20 Maximum bit rate (17)3.21 Measurement capability (17)3.22 Paging cause (17)3.23 Paging record (17)3.24 PDCP capability (17)3.25 Physical channel capability (18)3.26 Protocol error cause (18)3.27 Protocol error indicator (18)3.28 RB timer indicator (18)3.29 Redirection info (18)3.30 Re-establishment timer (18)3.31 Rejection cause (18)3.32 Release cause (18)3.33 RF capability FDD (19)3.34 RLC capability (19)3.35 RLC re-establish indicator (19)3.36 RRC transaction identifier (19)3.37 Security capability (19)3.38 START (19)3.39 Transmission probability (19)3.40 Transport channel capability (20)3.41 UE multi-mode/multi-RAT capability (20)3.42 UE radio access capability (20)3.43 UE Timers and Constants in connected mode (21)3.44 UE Timers and Constants in idle mode (21)3.45 UE positioning capability (21)3.46 URA update cause (21)3.47 U-RNTI (21)3.48 U-RNTI Short (21)3.49 UTRAN DRX cycle length coefficient (21)3.50 Wait time (21)3.51 UE Specific Behavior Information 1 idle (21)3.52 UE Specific Behavior Information 1 interRAT (22)4 无线承载信息元素 (22)4.0 Default configuration identity (22)4.1 Downlink RLC STATUS info (22)4.2 PDCP info (22)4.3 PDCP SN info (22)4.4 Polling info (22)4.5 Predefined configuration identity (23)4.6 Predefined configuration value tag (23)4.7 Predefined RB configuration (23)4.8 RAB info (23)4.9 RAB info Post (23)4.10 RAB information for setup (23)4.11 RAB information to reconfigure (24)4.12 NAS Synchronization indicator (24)4.13 RB activation time info (24)4.14 RB COUNT-C MSB information (24)4.15 RB COUNT-C information (24)4.16 RB identity (24)4.17 RB information to be affected (24)4.18 RB information to reconfigure (25)4.19 RB information to release (25)4.20 RB information to setup (25)4.21 RB mapping info (25)4.22 RB with PDCP information (25)4.23 RLC info (25)4.24 Signaling RB information to setup (26)4.25 Transmission RLC Discard (26)5 传输信道信息元素 (26)5.1 Added or Reconfigured DL TrCH information (26)5.2 Added or Reconfigured UL TrCH information (27)5.3 CPCH set ID (27)5.4 Deleted DL TrCH information (27)5.5 Deleted UL TrCH information (27)5.6 DL Transport channel information common for all transport channels (27)5.7 DRAC Static Information (27)5.8 Power Offset Information (28)5.9 Predefined TrCH configuration (28)5.10 Quality Target (28)5.11 Semi-static Transport Format Information (28)5.12 TFCI Field 2 Information (28)5.13 TFCS Explicit Configuration (28)5.14 TFCS Information for DSCH (TFCI range method) (29)5.15 TFCS Reconfiguration/Addition Information (29)5.16 TFCS Removal Information (29)5.17 Void (29)5.18 Transport channel identity (29)5.19 Transport Format Combination (TFC) (29)5.20 Transport Format Combination Set (29)5.21 Transport Format Combination Set Identity (29)5.22 Transport Format Combination Subset (29)5.23 Transport Format Set (29)5.24 UL Transport channel information common for all transport channels (30)6 物理信道信息元素 (30)6.1 AC-to-ASC mapping (30)6.2 AICH Info (30)6.3 AICH Power offset (30)6.4 Allocation period info (30)6.5 Alpha (30)6.6 ASC Setting (30)6.7 Void (31)6.8 CCTrCH power control info (31)6.9 Cell parameters Id (31)6.10 Common timeslot info (31)6.11 Constant value (31)6.12 CPCH persistence levels (31)6.13 CPCH set info (31)6.14 CPCH Status Indication mode (31)6.15 CSICH Power offset (32)6.16 Default DPCH Offset Value (32)6.17 Downlink channelisation codes (32)6.18 Downlink DPCH info common for all RL (32)6.19 Downlink DPCH info common for all RL Post (32)6.20 Downlink DPCH info common for all RL Pre (32)6.21 Downlink DPCH info for each RL (32)6.22 Downlink DPCH info for each RL Post (33)6.23 Downlink DPCH power control information (33)6.24 Downlink information common for all radio links (33)6.25 Downlink information common for all radio links Post (33)6.26 Downlink information common for all radio links Pre (33)6.27 Downlink information for each radio link (33)6.28 Downlink information for each radio link Post (33)6.29 Void (33)6.30 Downlink PDSCH information (33)6.31 Downlink rate matching restriction information (34)6.32 Downlink Timeslots and Codes (34)6.33 DPCH compressed mode info (34)6.34 DPCH Compressed Mode Status Info (34)6.35 Dynamic persistence level (34)6.36 Frequency info (34)6.37 Individual timeslot info (35)6.38 Individual Timeslot interference (35)6.39 Maximum allowed UL TX power (35)6.40 Void (35)6.41 Midamble shift and burst type (35)6.42 PDSCH Capacity Allocation info (35)6.43 PDSCH code mapping (36)6.44 PDSCH info (36)6.45 PDSCH Power Control info (36)6.46 PDSCH system information (36)6.47 PDSCH with SHO DCH Info (36)6.48 Persistence scaling factors (36)6.49 PICH Info (36)6.50 PICH Power offset (37)6.51 PRACH Channelisation Code List (37)6.52 PRACH info (for RACH) (37)6.53 PRACH partitioning (37)6.54 PRACH power offset (37)6.55 PRACH system information list (37)6.56 Predefined PhyCH configuration (38)6.57 Primary CCPCH info (38)6.58 Primary CCPCH info post (38)6.59 Primary CCPCH TX Power (38)6.60 Primary CPICH info (38)6.61 Primary CPICH Tx power (38)6.62 Primary CPICH usage for channel estimation (38)6.63 PUSCH info (38)6.64 PUSCH Capacity Allocation info (38)6.65 PUSCH power control info (39)6.66 PUSCH system information (39)6.67 RACH transmission parameters (39)6.68 Radio link addition information (39)6.69 Radio link removal information (39)6.70 SCCPCH Information for FACH (39)6.71 Secondary CCPCH info (39)6.72 Secondary CCPCH system information (40)6.73 Secondary CPICH info (40)6.74 Secondary scrambling code (40)6.75 SFN Time info (40)6.76 SSDT cell identity (40)6.77 SSDT information (40)6.78 STTD indicator (40)6.79 TDD open loop power control (41)6.80 TFC Control duration (41)6.81 TFCI Combining Indicator (41)6.82 TGPSI (41)6.83 Time info (41)6.84 Timeslot number (41)6.85 TPC combination index (41)6.86 TSTD indicator (41)6.87 TX Diversity Mode (41)6.88 Uplink DPCH info (41)6.89 Uplink DPCH info Post (42)6.90 Uplink DPCH info Pre (42)6.91 Uplink DPCH power control info (42)6.92 Uplink DPCH power control info Post (42)6.93 Uplink DPCH power control info Pre (42)6.94 Uplink Timeslots and Codes (42)6.95 Uplink Timing Advance (42)6.96 Uplink Timing Advance Control (43)7 测量信息元素 (43)7.1 Additional measurements list (43)7.2 Cell info (43)7.3 Cell measured results (43)7.4 Cell measurement event results (44)7.5 Cell reporting quantities (44)7.6 Cell synchronization information (44)7.7 Event results (44)7.8 FACH measurement occasion info (45)7.9 Filter coefficient (45)7.10 HCS Cell re-selection information (45)7.11 HCS neighboring cell information (45)7.12 HCS Serving cell information (45)7.13 Inter-frequency cell info list (46)7.14 Inter-frequency event identity (46)7.15 Inter-frequency measured results list (46)7.16 Inter-frequency measurement (46)7.17 Inter-frequency measurement event results (47)7.18 Inter-frequency measurement quantity (47)7.19 Inter-frequency measurement reporting criteria (47)7.20 Inter-frequency measurement system information (47)7.21 Inter-frequency reporting quantity (47)7.22 Inter-frequency SET UPDATE (48)7.23 Inter-RAT cell info list (48)7.24 Inter-RAT event identity (48)7.25 Inter-RAT info (48)7.26 Inter-RAT measured results list (48)7.27 Inter-RAT measurement (49)7.28 Inter-RAT measurement event results (49)7.29 Inter-RAT measurement quantity (49)7.30 Inter-RAT measurement reporting criteria (49)7.31 Inter-RAT measurement system information (50)7.32 Inter-RAT reporting quantity (50)7.33 Intra-frequency cell info list (50)7.34 Intra-frequency event identity (50)7.35 Intra-frequency measured results list (50)7.36 Intra-frequency measurement (50)7.37 Intra-frequency measurement event results (51)7.38 Intra-frequency measurement quantity (51)7.39 Intra-frequency measurement reporting criteria (51)7.40 Intra-frequency measurement system information (51)7.41 Intra-frequency reporting quantity (52)7.42 Intra-frequency reporting quantity for RACH reporting (52)7.43 Maximum number of reported cells on RACH (52)7.44 Measured results (52)7.45 Measured results on RACH (52)7.46 Measurement Command (52)7.47 Measurement control system information (53)7.48 Measurement Identity (53)7.49 Measurement reporting mode (53)7.50 Measurement Type (53)7.51 Measurement validity (53)7.52 Observed time difference to GSM cell (53)7.53 Periodical reporting criteria (53)7.54 Primary CCPCH RSCP info (54)7.55 Quality measured results list (54)7.56 Quality measurement (54)7.57 Quality measurement event results (54)7.58 Quality measurement reporting criteria (54)7.59 Quality reporting quantity (54)7.60 Reference time difference to cell (54)7.61 Reporting Cell Status (55)7.62 Reporting information for state CELL_DCH (55)7.63 SFN-SFN observed time difference (55)7.64 Time to trigger (55)7.65 Timeslot ISCP info (55)7.66 Traffic volume event identity (55)7.67 Traffic volume measured results list (55)7.68 Traffic volume measurement (55)7.69 Traffic volume measurement event results (56)7.70 Traffic volume measurement object (56)7.71 Traffic volume measurement quantity (56)7.72 Traffic volume measurement reporting criteria (56)7.73 Traffic volume measurement system information (56)7.74 Traffic volume reporting quantity (56)7.75 UE internal event identity (56)7.76 UE internal measured results (57)7.77 UE internal measurement (57)7.78 UE internal measurement event results (57)7.79 UE internal measurement quantity (57)7.80 UE internal measurement reporting criteria (57)7.81 Void (58)7.82 UE Internal reporting quantity (58)7.83 UE Rx-Tx time difference type 1 (58)7.84 UE Rx-Tx time difference type 2 (58)7.85 UE Transmitted Power info (58)7.86 UE positioning Ciphering info (58)7.87 UE positioning Error (58)7.88 UE positioning GPS acquisition assistance (59)7.89 UE positioning GPS almanac (59)7.90 UE positioning GPS assistance data (59)7.91 UE positioning GPS DGPS corrections (59)7.92 UE positioning GPS ionospheric model (59)7.93 UE positioning GPS measured results (59)7.94 UE positioning GPS navigation model (60)7.95 UE positioning GPS real-time integrity (60)7.96 UE positioning GPS reference time (60)7.97 UE positioning GPS UTC model (61)7.98 UE positioning IPDL parameters (61)7.99 UE positioning measured results (61)7.100 UE positioning measurement (61)7.101 UE positioning measurement event results (61)7.102 Void (62)7.103 UE positioning OTDOA assistance data for UE-assisted (62)7.104 Void (62)7.105 UE positioning OTDOA measured results (62)7.106 UE positioning OTDOA neighbor cell info (62)7.107 UE positioning OTDOA quality (63)7.108 UE positioning OTDOA reference cell info (63)7.109 UE positioning position estimate info (64)7.110 UE positioning reporting criteria (64)7.111 UE positioning reporting quantity (64)7.112 T ADV info (65)8 其它信息元素 (65)8.1 BCCH modification info (65)8.2 BSIC (65)8.3 CBS DRX Level 1 information (65)8.4 Cell Value tag (65)8.5 Inter-RAT change failure (65)8.6 Inter-RAT handover failure (66)8.7 Inter-RAT UE radio access capability (66)8.8 Void (66)8.9 MIB Value tag (66)8.10 PLMN Value tag (66)8.11 Predefined configuration identity and value tag (66)8.12 Protocol error information (66)8.13 References to other system information blocks (66)8.14 References to other system information blocks and scheduling blocks (67)8.15 Rplmn information (67)8.16 Scheduling information (67)8.17 SEG COUNT (67)8.18 Segment index (67)8.19 SIB data fixed (67)8.20 SIB data variable (67)8.21 SIB type (67)8.22 SIB type SIBs only (67)9 ANSI-41 Information elements (68)10 Multiplicity values and type constraint values (68)信息元素功能性定义消息是由多个信息元素组合而成,信息元素根据其功能的不同划分为:核心网域信息元素、UTRAN 移动信息元素、UE 信息元素、无线承载信息元素、传输信道信息元素、物理信道信息元素和测量信息元素。
DRAFT NIST Special Publication 800-38B DRAFT Recommendation for Block Cipher Modes of Opera
NIST Special Publication 800-38BDRAFTRecommendation for Block Cipher Modes of Operation: The RMAC Authentication ModeMethods and TechniquesMorris DworkinNovember 4, 2002AbstractThis Recommendation defines an authentication mode of operation, called RMAC, for a symmetric key block cipher algorithm. RMAC can provide cryptographic protection of sensitive, but unclassified, computer data. In particular, RMAC can provide assurance of the authenticity and, therefore, of the integrity of the data.KEY WORDS: Authentication; block cipher; cryptography; encryption; Federal Information Processing Standard; information security; integrity; mode of operation.Table of Contents1PURPOSE (5)2AUTHORITY (5)3INTRODUCTION (5)4DEFINITIONS, ABBREVIATIONS, AND SYMBOLS (6)4.1D EFINITIONS AND A BBREVIATIONS (6)4.2S YMBOLS (7)4.2.1Variables (7)4.2.2Operations and Functions (8)5PRELIMINARIES (9)5.1T HE U NDERLYING B LOCK C IPHER A LGORITHM (9)5.2E LEMENTS OF RMAC (9)5.3E XAMPLES OF O PERATIONS AND F UNCTIONS (10)6RMAC SPECIFICATION (10)6.1M ESSAGE F ORMATTING (10)6.2P ARAMETER S ETS (10)6.3MAC G ENERATION (11)6.4T AG G ENERATION AND V ERIFICATION (12)APPENDIX A: SECURITY CONSIDERATIONS (13)A.1E XHAUSTIVE K EY S EARCH (13)A.2G ENERAL F ORGERY (13)A.3E XTENSION F ORGERY B ASED ON A C OLLISION (13)A.4S UMMARY OF S ECURITY P ROPERTIES OF P ARAMETER S ETS (14)APPENDIX B: THE GENERATION OF RMAC PARAMETERS (15)B.1 D ERIVATION OF RMAC KEYS FROM A M ASTER K EY (15)B.2 S ALT G ENERATION (15)APPENDIX C: EXAMPLE VECTORS FOR THE MAC GENERATION FUNCTION (16)C.1RMAC-AES128 E XAMPLE V ECTORS (16)C.1.1RMAC-AES128-I (16)C.1.2RMAC-AES128-II (17)C.1.3RMAC-AES128-III (18)C.1.4RMAC-AES128-IV (19)C.1.5RMAC-AES128-V (20)C.2RMAC-AES192 E XAMPLE V ECTORS (21)C.2.1RMAC-AES192-I (21)C.2.2RMAC-AES192-II (22)C.2.3RMAC-AES192-III (23)C.2.4RMAC-AES192-IV (24)C.2.5RMAC-AES192-V (26)C.3RMAC-AES256 E XAMPLE V ECTORS (27)C.3.1RMAC-AES256-I (27)C.3.2RMAC-AES256-II (28)C.3.3RMAC-AES256-III (29)C.3.4RMAC-AES256-IV (30)C.3.5RMAC-AES256-V (32)C.4RMAC-TDES112 E XAMPLE V ECTORS (33)C.5RMAC-TDES168 E XAMPLE V ECTORS (33)APPENDIX D: REFERENCES (34)Table of FiguresFigure 1: The RMAC MAC Generation Function (12)1 PurposeThis publication is the second part in a series of Recommendations regarding modes of operation of symmetric key block cipher algorithms.2 AuthorityThis document has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Computer Security Act of 1987 (Public Law 100-235) and the Information Technology Management Reform Act of 1996, specifically 15 U.S.C. 278 g-3(a)(5). This is not a guideline within the meaning of 15 U.S.C. 278 g-3 (a)(5).This Recommendation is neither a standard nor a guideline, and as such, is neither mandatory nor binding on federal agencies. Federal agencies and nongovernment organizations may use this Recommendation on a voluntary basis. It is not subject to copyright.Nothing in this Recommendation should be taken to contradict standards and guidelines that have been made mandatory and binding upon federal agencies by the Secretary of Commerce under statutory authority. Nor should this Recommendation be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, the Director of the Office of Management and Budget, or any other federal official.Conformance testing for implementations of the modes of operation that are specified in this Recommendation will be conducted within the framework of the Cryptographic Module Validation Program (CMVP), a joint effort of NIST and the Communications Security Establishment of the Government of Canada. An implementation of a mode of operation must adhere to the requirements in this Recommendation in order to be validated under the CMVP. The requirements of this Recommendation are indicated by the word “shall.”3 IntroductionThis Recommendation specifies an algorithm, RMAC [1], that can provide assurance of data origin authentication and, hence, assurance of data integrity. In particular, RMAC is an algorithm for generating a message authentication code (MAC) from the data to be authenticated and from an associated value called the salt, using a block cipher and two secret keys that the parties to the authentication of the data establish beforehand. One party generates the MAC and provides the MAC and the associated salt as the authentication tag; subsequently, any party with access to the secret keys may verify whether the received MAC was generated from the received data and the received salt. Successful verification of the MAC provides assurance of the authenticity of the data, i.e., that it originated from a source with access to the secret keys. Consequently, successful verification of the MAC also provides assurance of the integrity of the data, i.e., that it was not altered after the generation of the MAC.A MAC is sometimes called a cryptographic checksum, because it is generated from a keyed cryptographic algorithm in order to provide stronger assurance of data integrity than an ordinary checksum. The verification of an ordinary checksum or an error detecting code is designed to reveal only accidental modifications of the data, while the verification of a MAC is designed to reveal intentional, unauthorized modifications of the data, as well as accidental modifications. Because RMAC is constructed from a block cipher algorithm, RMAC can be considered a mode of operation of the block cipher algorithm. The block cipher algorithm shall be approved, i.e., specified or adopted in a Federal Information Processing Standard (FIPS) or a NIST Recommendation; for example, FIPS Pub. 197 [2] specifies the AES algorithm, and FIPS Pub. 46-3 [3] adopts the Triple DES algorithm.FIPS Pub. 198 [4] specifies a different MAC algorithm, called HMAC, that is also appropriate for the protection of sensitive data. Because HMAC is constructed from a hash function rather than a block cipher algorithm, RMAC may be preferable for application environments in which an approved block cipher is more convenient to implement than an approved hash function.4 Definitions, Abbreviations, and Symbols4.1 Definitions and AbbreviationsApproved FIPS approved or NIST recommended: an algorithm or technique thatis either 1) specified in a FIPS or NIST Recommendation, or 2) adoptedin a FIPS or NIST Recommendation.Authenticity The property that data indeed originated from its purported source. Authentication Mode A block cipher mode of operation that can provide assurance of theauthenticity and, therefore, the integrity of data.Authentication Tag (Tag) A pair of bit strings associated to data to provide assurance of its authenticity: the salt and the message authentication code that is derived from the data and the salt.Bit A binary digit: 0 or 1.Bit String An ordered sequence of 0s and 1s.Block A bit string whose bit length is the block size of the block cipheralgorithm.Block Cipher See forward cipher function.Block Cipher Algorithm A family of functions and their inverses that is parameterized by cryptographic keys; the functions map bit strings of a fixed length to bit strings of the same length.Block Size The number of bits in an input (or output) block of the block cipher. Cryptographic Key A parameter used in the block cipher algorithm that determines theforward cipher function.Data Integrity The property that data has not been altered by an unauthorized entity. Exclusive-OR The bitwise addition, modulo 2, of two bit strings of equal length. FIPS FederalInformationProcessing Standard.Forward Cipher Function One of the two functions of the block cipher algorithm that is determined by the choice of a cryptographic key.Initialization Vector(IV)A data block that some modes of operation require as an initial input.Message Authentication Code (MAC) A cryptographic checksum on data that is designed to reveal both accidental errors and intentional modifications of the data.Mode of Operation (Mode) An algorithm for the cryptographic transformation of data that features a symmetric key block cipher algorithm.Most Significant Bit(s) The left-most bit(s) of a bit string.Nonce A value that is used only once within a specified context.RMAC The name of the authentication mode that is specified in thisRecommendation.Salt A parameter of an algorithm whose role is to randomize the value ofanother parameter.4.2 Symbols4.2.1 Variablesb The block size, in bits.k The key length for the block cipher.m The bit length of the RMAC MAC.n The number of data blocks in the padded message.r The bit length of the salt.CNST j The j th fixed, i.e., constant, block.K A block cipher key.K1 The first RMAC key.K2 The second RMAC key.K3 A key that is derived from the second RMAC key and the salt.M The message.Mlen The bit length of the message.M j The j th block in the partition of the padded message.j th output block.O j ThePAD The padding that is appended to the message.salt.R The4.2.2 Operations and Functions0s The bit string consisting of s ‘0’ bits.X || Y The concatenation of two bit strings X and Y.X ⊕Y The bitwise exclusive-OR of two bit strings X and Y of the same length.CIPH K(X) The forward cipher function of the block cipher algorithm under the key K applied to the data block X.MSB s(X) The bit string consisting of the s most significant bits of the bit string X.RMAC(R,M) The RMAC message authentication code for message M with salt R.5 Preliminaries5.1 The Underlying Block Cipher AlgorithmThe RMAC algorithm specified in this Recommendation depends on the choice of an underlying symmetric key block cipher algorithm; the RMAC algorithm is thus a mode of operation (mode, for short) of the symmetric key block cipher. The underlying block cipher algorithm must be approved, and two secret, random keys for the block cipher algorithm shall be established. The keys regulate the functioning of the block cipher algorithm and, thus, by extension, the functioning of the mode. The specifications of the block cipher algorithm and the mode are public, so the security of the mode depends, at a minimum, on the secrecy of the keys.For any given key, the underlying block cipher algorithm of the mode consists of two processes that are inverses of each other. As part of the choice of the block cipher algorithm, one of the two processes of the block cipher algorithm is designated as the forward cipher function. The inverse of this process is called the inverse cipher function. Because the RMAC mode does not require the inverse cipher function, the forward cipher function in this Part of the Recommendation is simply called the block cipher.5.2 Elements of RMACThe block cipher keys that are required for the RMAC mode are bit strings, denoted K1and K2, whose bit length, denoted k, depends on the choice of the block cipher algorithm. The keys shall be random or pseudorandom, distinct from keys that are used for other purposes, and secret. The two keys shall each be established by an approved key establishment method, or the keys shall be derived from a single key K, which is established by an approved key establishment method.A method for deriving K1and K2 from a single, master key K is given in Appendix B.1.The block cipher is a function on bit strings of a fixed bit length. The fixed bit length of the bit strings is called the block size and is denoted b; any bit string whose bit length is b is called a (data) block. Under a key K, the block cipher function is denoted CIPH K.For the AES algorithm, b=128 and k=128, 192, or 256; for Triple DES, b=64 and k=112 or 168. The data to be authenticated is one input to the RMAC MAC generation function; the data in this context is called the message, denoted M.Another input to the MAC generation function is a parameter associated with the message called the salt, denoted R. The role of the salt in the MAC generation function is to randomize (i.e., “flavor”) the second key, K2. The bit length of the salt, denoted r, is determined by the choice of a parameter set that is specified in Section 6.2. The use of the salt is optional in the sense that a parameter set may be chosen in which r=0. When r1234567487569 4 9 4 7 7 5 45674 54 6 4 ensure that the expected probability of repeating the salt for different messages is negligible. The generation of the salt is discussed further in Appendix B.2.The RMAC MAC generation function is denoted RMAC, so that the output of the function, the MAC, is denoted RMAC(R,M). The bit length of the MAC, denoted m, is determined by thechoice of a parameter set that is specified in Section 6.2. The authentication tag to the message is the ordered pair (R, RMAC(R,M)); thus, the tag consists of one part, the salt, that may be independent of the message and a second part, the MAC, that depends on both the salt and the message. The total number of bits in the tag is r+m.5.3 Examples of Operations and FunctionsFor a nonnegative integer s, the bit string consisting of s ‘0’ bits is denoted 0s.The concatenation operation on bit strings is denoted ||; for example, 001 || 10111 = 00110111.Given bit strings of equal length, the exclusive-OR operation, denoted ⊕, specifies the addition, modulo 2, of the bits in each bit position, i.e., without carries. Thus, 10011 ⊕ 10101= 00110, for example.The function MSB s returns the s most significant bits of the argument. Thus, for example, MSB4(111011010) = 1110.6 RMAC Specification6.1 Message FormattingThe first steps of the MAC generation function are to append padding to the message and to partition the resulting string into complete blocks. The padding, denoted PAD, is a single ‘1’ bit followed by the minimum number of ‘0’ bits such that the total number of bits in the padded message is a multiple of the block size. The padded message is then partitioned into a sequence of n complete blocks, denoted M1, M2, …, M n. Thus,M || PAD = M1 || M2 ||…|| M n .If the bit length of M is a multiple of the block size, then PAD = 1 || 0b-1, i.e., a complete block.6.2 Parameter SetsA parameter set is a pair of values for the bit lengths r and m of the two parts of the authentication tag, the salt and the MAC. The parameter sets for RMAC depend on the block size of the underlying block cipher algorithm. A parameter set shall be chosen from Table 1 below; five parameter sets are given for the 128 bit block size, and two for the 64 bit block size. Although parameter set I offers the shortest authentication tags, it is not recommended for general use. The decision to use parameter set I requires a risk-benefit analysis of at least three factors: 1) the relevant attack models, 2) the application environment, and 3) the value and longevity of the data to be protected. In particular, parameter set I shall only be used if the controlling protocol or application environment sufficiently restricts the number of times that verification of an authentication tag can fail under any given pair of RMAC keys. For example,the short duration of a session, or, more generally, the low bandwidth of the communication channel may preclude many repeated trials.Parameter sets II, III, IV, and V are appropriate for general use.Table 1: Parameter Setsb=128 b=64Parameter Set r m r m32I 03264 6464II 0n/a80III 16n/a96IV 64V 128 128 n/aSome of the security considerations that underlie the selection of a parameter set are summarized in Appendix A. The expected work factors for important aspects of the attacks that are discussed in the appendix are summarized for each parameter set in Table 2 in Section A.4.6.3 MAC GenerationThe following is a specification of the RMAC MAC generation function:Input:block cipher CIPH;block cipher keys K1 and K2 of bit length k;parameter set (r, m);message M;salt R of bit length r.Output:message authentication code RMAC(R, M) of bit length m.Steps:toM the padding string PAD, as described in Section 6.1.1. Append2.Partition M || PAD into n blocks M1, M2, …, M n, as described in Section 6.1.3.O1 =CIPH K1(M1).j = 2 to n, do O j= CIPH K1(M j⊕O j-1).4. Forr=0, then K3=K2; else K3 = K2 ⊕ (R || 0k-r).5. If6.Return RMAC(R, M) = MSB m(CIPH K3(O n)).The calculations in Steps 3 and 4 are equivalent to encrypting the padded message using the cipher block chaining (CBC) mode [5] of the block cipher, under the first RMAC key, with the zero block as the initialization vector. However, unlike CBC encryption, in which every output block from Steps 3 and 4 is part of the encryption output (i.e., the ciphertext), in RMAC, the output blocks in Steps 3 and 4 are intermediate results. In Step 6, the block cipher under a newkey is applied to the final output block from Step 4, and the result is truncated as specified in the parameter set. The new key for this final application of the block cipher is obtained in Step 5 by exclusive-ORing the salt into the most significant bits of the second RMAC key.The RMAC MAC generation function is illustrated in Figure 1.6.4 Tag Generation and VerificationThe prerequisites for the authentication process are the establishment of an approved block cipher algorithm, two secret RMAC keys, and a parameter set1 among the parties to the authentication of the data.To generate an authentication tag on a message M, a party shall determine an associated salt R in accordance with Appendix B, generate RMAC(R,M), as specified in Section 6.3, and provide the authentication tag (R, RMAC(R,M)) to the data.To verify an authentication tag (R', MAC'), a party shall apply the RMAC MAC generation function, as specified in Section 6.3, to the received message M' and the received salt R' within the tag. If the computed MAC, i.e., RMAC(R',M'), is identical to the received MAC, i.e., MAC', then verification succeeds; otherwise, verification fails, and the message should not be considered authentic.1 For tag verification, the parameter set is implicit in the bit length of the tag.Appendix A: Security ConsiderationsThe submitters of RMAC present a security analysis of RMAC in [6]. In this appendix, three types of attacks on general MAC algorithms are summarized, and discussed with respect to RMAC: exhaustive key search, general forgery, and extension forgery based on birthday collisions.A.1 Exhaustive Key SearchIn principle, given sufficiently many valid message-tag pairs, an unauthorized party can exhaustively search, off-line, every possible key to the MAC generation algorithm. After recovering the secret key, by this method or any other method, the unauthorized party could generate a forgery, i.e., a valid authentication tag, for any message.The number of RMAC keys is so large that exhaustive key search of RMAC is impractical for the foreseeable future. In particular, for the key size k, which is at least 112 bits for the approved block cipher algorithms, the exhaustive search for the two RMAC keys would be expected to require the generation of 22k-1 MACs. Even if the two RMAC keys are derived from a single master key, as discussed in Appendix B.1, the exhaustive search for the master key would be expected to require the generation of 2k-1 MACs.ForgeryA.2 GeneralThe successful verification of a MAC does not guarantee that the associated message is authentic: there is a small chance that an unauthorized party can guess a valid MAC of an arbitrary (i.e., inauthentic) message. Moreover, if many message forgeries are presented for verification, the probability increases that, eventually, verification will succeed for one of them. This limitation is inherent in any MAC algorithm.The protection that the RMAC algorithm provides against such forgeries is determined by the bit length of MAC, m, which in turn is determined by the choice of a parameter set. The probability of successful verification of an arbitrary MAC with any given salt on any given message is expected to be 2-m; therefore, larger values of m offer greater protection against general forgery.A.3 Extension Forgery Based on a CollisionThe underlying idea of extension forgery attacks is for the unauthorized party to find a collision, i.e., two different messages with the same MAC (before any truncation). If the colliding messages are each concatenated with a common string, then, for many MAC algorithms, including RMAC, the two extended messages have a common MAC. Therefore, the knowledge of the MAC of one extended message facilitates the forgery of the other extended message. The unauthorized party can choose the second part of the forged message, i.e., the common string, but generally cannot control the first part, i.e., either of the original, colliding messages.In principle, collisions may exist, because there are many more possible messages than possible MACs. A collision may be detected by the collection and search of a sufficiently large set of message-MAC pairs. By the so-called “birthday surprise” (see, for example, [7]), the size of this sufficiently large set is expected to be, approximately, the square root of the number of possible MAC strings, before any truncation.For RMAC, the extension forgery requires that the salt values, R, are the same for the two colliding messages, as well as the untruncated MACs, i.e., CIPH K3(O n) in the specification of Section 6.3. Therefore, larger values of the block size, b, and the salt size, r, provide greater protection against extension forgery. In particular, the unauthorized party would have to collect at least 2(b+r)/2 message-tag pairs in order to expect to detect a collision.Moreover, if a parameter set is chosen in which m<b, i.e., if CIPH K3(O n) is truncated to produce the MAC, then the discarded bits may be difficult for an unauthorized party to determine, so collisions may be difficult to detect. Parameter sets in which m<b may also provide some protection against other types of attacks.A.4 Summary of Security Properties of Parameter SetsIn Table 2, the expected work factors for the important aspects of the attacks discussed in Sections A.1-A.3 are summarized for the RMAC parameter sets. The values for exhaustive key search are given for the case in which the two RMAC keys are generated from a single master key as discussed in Section B.1.Table 2: Expected Work Factors for Three Types of Attacks on RMACRMAC Parameter Set Exhaustive Key Search(MAC GenerationOperations)General Forgery(Success Probabilityfor a Single Trial )Extension Forgery(Message-Tag Pairs)I 2k-12-32232 (b=64) or 264 (b=128) II 2k-12-64264III 2k-12-80272IV 2k-12-96296V 2k-12-1282128Appendix B: The Generation of RMAC ParametersB.1 Derivation of RMAC keys from a Master KeyThe two secret RMAC keys, K1 and K2, may be derived from a single master key, K, in order to save bandwidth or storage, at the cost of extra invocations of the block cipher to set up the RMAC keys. For example, let CNST1, CNST2, CNST3, CNST4, CNST5, and CNST6 be constants, i.e., fixed, distinct blocks, and let k and b be the key length and block length of the approved block cipher, as before. If k 4 b, then K1 and K2 may be derived from the set of constants as follows:K1=MSB k(CIPH K(CNST1) || CIPH K(CNST3) || CIPH K(CNST5))K2=MSB k(CIPH K(CNST2) || CIPH K(CNST4) || CIPH K(CNST6)).If k=b, then this definition reduces to K1=CIPH K(CNST1) and K2=CIPH K(CNST2), and thus only two constants are actually required.Similarly, if b<k≤2b, then the definition becomes K1= MSB k(CIPH K(CNST1) || CIPH K(CNST3)) and K2=MSB k(CIPH K(CNST2) || CIPH K(CNST4)), and thus only four constants are required.B.2 Salt GenerationThe salt values associated with messages shall repeat with no more than negligible probability. In particular, the expected probability that the same salt will be associated with two different messages that are authenticated under the scope of any pair of RMAC keys shall be no greater than for random values of salt. Therefore, one approach to meeting the requirement is to generate the salt by an approved deterministic random number generator.Another approach is to ensure that the probability of associating the same salt to different messages is zero, in other words, to generate a nonce to be the salt. For example, the salt may be a counter or a message number.Appendix C: Example Vectors for the MAC Generation FunctionIn this appendix, examples vectors are provided for the RMAC MAC generation function with either the AES algorithm or Triple DES as the underlying block cipher. For each allowed key size of the underlying block cipher, MACs are generated on three messages for each parameter set. The lengths of the three messages, denoted Mlen , are 128 bits, 384 bits, and 400 bits. In addition to the MAC for the given input values, intermediate results are provided. All strings are represented in hexadecimal notation.C.1 RMAC-AES128 Example VectorsC.1.1 RMAC-AES128-I RMAC-AES128, r =0, m =32, Mlen =128 M : 000102030405060708090a0b0c0d0e0f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_n : 3a3807ffe3cb3e978953017210335f0f K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): bfc3c92e04100777be98f7a93e178381 RMAC (R ,M ): bfc3c92e RMAC-AES128, r =0, m =32, Mlen =384 M : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_2: 3cf456b4ca488aa383c79c98b34797cb O_3: 7e163e30ea49d32152a51a08a10ec02d O_n : c5b089e3e4710856581f28b42824c651 K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): a3c33ae5f5d19094c5f65faa4ee60696 RMAC (R ,M ): a3c33ae5 RMAC-AES128, r =0, m =32, Mlen =400 M : 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 3031 K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 30318000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_2: 3cf456b4ca488aa383c79c98b34797cb O_3: 7e163e30ea49d32152a51a08a10ec02d O_n : 6a83b72738a946e319702dfd323fae52 K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): 4577d30eac2b9a438e507ecf22cc5fbd RMAC (R ,M ): 4577d30eC.1.2 RMAC-AES128-IIRMAC-AES128, r =0, m =64, Mlen =128 M : 000102030405060708090a0b0c0d0e0f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_n : 3a3807ffe3cb3e978953017210335f0f K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): bfc3c92e04100777be98f7a93e178381 RMAC (R ,M ): bfc3c92e04100777 RMAC-AES128, r =0, m =64, Mlen =384 M : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_2: 3cf456b4ca488aa383c79c98b34797cb O_3: 7e163e30ea49d32152a51a08a10ec02d O_n : c5b089e3e4710856581f28b42824c651 K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): a3c33ae5f5d19094c5f65faa4ee60696。
心力衰竭患者血浆sIGF-1、sTRAIL、sDR5水平的变化及其相关性
半定量参数 与微血管密度的相关性 . 中国医学影 像技
术 ,O72 ( )38 2O ,33 :8
[ 9]
Mih e A, ee P d a A e 1 . o b n d d r ca l P tr B, e r m t o C m ie y ̄
水平可能是评价 C F 者心功能和心肌细胞凋亡状态有价值的指标之一 。 H患
【 关键词】 心力衰竭 细胞凋亡 放射 免疫 法 酶联免疫吸 附法 胰 岛素生长 因子 一 T F 关的 凋亡诱导配体 、 l N相 死 亡受体
a
【 中国图书分类号 】 14 . 1 19 1 16 1 2 5 5
20 , ( )68 072 5 :8 3
f o i gn n a ied ca a cn ma f h ra t e md r ma i gi iv sv u t c rio so e be s . n l t
Jl a n R s n I gn ,O O 1 3 9 Ig e o  ̄ ma ig 2 O , 8: 7
分别用放射免疫法 、 酶联免疫吸附法 ( A 检测 8 Ⅱ ) 0例 C F患者和 3 H o ( )H 1C F
体(1 A . 死亡受体 (D 5 水平及其相关性 。方法 s R Ⅱ) 1 、 sR )
例健康人 ( 对照组 ) 血浆 s F 、 R I、D 5水平 , I —I8 AL sR G T 用多普勒超声心动图测定 C F患者左室射血分数 (M ) H I 。结果
生成的研究 . 中国肿瘤 临床 ,O5 3 ()56 2O ,29 :1
嘲 胡删
.i e a 日0 e, Bo dHlm (t r m I : h
IS1678S蓝牙4.0双模芯片说明书
IS1678SBluetooth ® 4.0 Dual mode ICFeatures:•Bluetooth Classic (BR/EDR) and Low Energy (LE)•Complete , Fully Certified, Embedded 2.4 GHz Bluetooth® Version 4.0 IC • Bluetooth SIG Certified•Transparent UART mode for seamless serial data over UART interface•Easy to configure with Windows GUI or direct by MCU• Firmware can be field upgradable via UART • IC Size: 6 x 6 mm 2•Castellated surface mount pads for easy and reliable host PCB mounting•Perfect for Portable Battery Operated Devices• Internal Battery Regulator Circuitry • Worldwide regulatory certifications •1 LED and it has 16 steps Brightness.Operational:• Single operating voltage: 3.2V to 4.3V •Temperature range: ‐20℃ to 70℃ Industrial• Simple, UART interface•Integrated crystal, internal voltage regulator, and matching circuitry•Multiple I/O pins for control and statusRF/Analog:• Frequency: 2.402 to 2.480 GHz•Receive Sensitivity: ‐90 dBm (BR/EDR); ‐92 dBm (LE)•Power Output: +2 dBm (typ.)Data Throughput:•11k bps (BR/EDR)@ UART baud Rate is 115200 bps•8 Kbps (LE) UART baud Rate is 115200 bpsMAC/Baseband/Higher Layer: • Secure AES128 encryption• BTv3.0: GAP, SPP, SDP, RFCOMM and L2CAP •BTv4.0: GAP, GATT, ATT, SMP and L2CAP .General Description:The IS1678S is a fully‐certified Bluetooth® Version 4.0 (BR/EDR/LE) IC for designers who want to easily add dual mode Bluetooth® wireless capability to their products.Delivering local connectivity for the Internet of Things (IoT), the IC bridges your product to Smart Phones and Tablets for convenient data transfer, control and access to cloud applications.It supports GAP, SDP, SPP , and GATT profiles. Data is transferred over the Bluetooth link by sending/receiving data via transparent UART mode, making it easy to integrate with any processor or Microcontroller with a UART interface. Configuration is made easy using a Windows® based GUI or directly via UART by a MCUApplications: • Mobile Point of Sales (mPOS) • LED lighting (16 step) • Wearables • Digital Sports • Fitness Devices • Health Care/ Medical • Automotive Accessories • Home Automation • Remote Control Toys1.0 DEVICE OVERVIEW2.0 PIN DESCRIPTION AND UART INTERFACE3.0 STATA MACHINE4.0 Software Button (SW_BTN)5.0 WAKE UP6.0 EXTERNAL RESET7.0 REFERENCE CLOCK8.0 LED DRIVER9.0 MEMORY10.0 Throughput11.0 ANTENNA PLACEMENT RULE12.0 Electrical Characteristics13.0 Radio Characteristics:14.0 System Current Consumption15.0 REFERENCE CIRCUIT16.0 Package Information17.0 REFLOW PROFILE AND STORAGE CINDITION1.0 DEVICE OVERVIEWThe IS1678S is a complete, fully certified, embedded 2.4 GHz Bluetooth® version 4.0 (BR/EDR/LE) wireless IC. It incorporates an on‐board Bluetooth stack, cryptographic accelerator, power management subsystem, 2.4 GHz transceiver, and RF power amplifier (see Figure 1-1). With the IS1678S, designers can embed Bluetooth functionality rapidly into virtually any device.The IS1678S provides cost and time‐to‐market savings as a self‐contained Bluetooth solution. The IC has been designed to provide integrators with a simpleBluetooth solution that features:•Ease of integration and programming •Vastly reduced development time •Minimum system cost •Interoperability with Bluetooth hosts •Maximum value in a range of applicationsThe IS1678S can independently maintain a low‐power wireless connection.Low‐power usage and flexible powermanagement maximize the IC’s lifetime inbattery‐operated devices. A wide operating temperature range allows use in indoor and outdoor environments (industrialtemperature range).FIGURE 1-1:Block DiagramPIN DESCRIPTION AND UART INTERFACE1.1 Pin AssignmentTABLE 2-1: IS1678S PIN DESCRIPTIONNote 1: Pin type abbreviation: A = Analog, D = Digital, I = Input, O = OutputUI setting:FIGURE 1‐2 : P0_4 UART_TX_IND UI setting1.2 Power TreeFigures 1-3 : Power Tree1.3 UART InterfaceFigures 1-4 : Power and MCU interface examples.Figure 1-4 shows an example power scheme using a 3.3 volt to MCU VDD. Battery power is applied to BAT_IN pin. From the LDO33_O pin, voltage can be routed the VDD_IO pin and external circuitry including the MCU. This power scheme ensures that IS1678S and MCU I/O voltages are compatible.CAUTION: The internal 3.3volt LDO current source: 50mA maximum!!2.0Bluetooth behavior auto/manual pattern configurationFigures 2-1 : Auto/Manual pattern configuration2.1 auto pattern2.2 Manual pattern2.3 UI settingFIGURE 2‐2 : P0_4 UART_TX_IND UI settingNOTE: Please reference “Application Note_IS1678S_Draft.docx”and “IS1678S Command Set v097 20140924.docx.”3.0Control and Indication I/O PinsI/O pins P0_0, P0_5, P1_7, P3_1, P3_2, P3_3, P3_4 and P3_7 are configurable control and indication I/O. Control signals are input to the IS1678S. Indication signals are output from theIS1678S. Table 3-1 shows configurable I/O pin assignment to control and indication signals. Note: that RTS can only be assigned to P0_0 and CTS is assigned to P1_7.Configuring the IS1678S can reference the “Application Note_IS1678S_Draft.docx” and “IS1678S Command Set v0 97 20140924.docx.”3.1 UI setting4.0Status Indication I/O PinsI/O pins P1_5 and P0_4 are Status Indicator 1 and 2 signals respectively. Together they provide status indication to the MCU as shown in Table 4-1.4.1 System ConfigurationI/O pins P2_0, P2_4, and EAN place the IS1678S into operation modes as shown in Table 4-2. P2_0 , P2_4and EAN each have internal pull‐ups.5.0 Software Button (SW_BTN)The Software Button (SW_BTN) input pin powers the IS1678S on (high) or off (low) in to S4 mode.Figures 5-1 : SW_BTN Time (high) @APP modeNote:A.P0_4/P1_5 state: Refer to table5‐1B.Reset is floating.Figures 5-2 : SW_BTN Time (low) at access states.Note:A.SW_BTN pull low can’t active on Shutdown State.B.Reset is floating.Figures 5-3 : SW_BTN Time (low) at link states.Note:C.*1: this time by iPhone LE mode disconnect time.D.SW_BTN pull low can’t active on Shutdown State.E.Reset is floating.6.0 WAKE UPThe Wake Up input pin wakes the IS1678S from shutdown mode (active low).Figures 6-1 : WAKE_UP Time at Shutdown State.7.0 EXTERNAL RESETA watchdog timer capable of reset the chip. It has an integrated Power-On Reset (POR) circuit that resets all circuits to a known power-on state. This action can also be driven by an external reset signal that can be used to externally control the device, forcing it into a power-on reset state. The RST signal input is active low and no connection is required in most applications.Figures 7-1 : Reset Time at Shutdown State.Note:a.Auto pattern can use external reset.b.Manual pattern can use external reset and reset command.8.0 REFERENCE CLOCKIS1678S is composed of an integrated crystal oscillation function. It used a 16MHz external crystal and two specified load capacitors that a high quality system reference timer source is obtained. This feature is typically used to remove the initial tolerance frequency errors associated with the crystal and its equivalent load capacitance in mass production. Frequency trim is achieved by adjusting the crystal load capacitance through on‐chip trim capacitors C trim integrated in chip.The value of trimming capacitance is around 200fF (200x10‐15 F)per LSB at 5 bits word, therefore the overall adjustable clock frequency is around 40 KHz.C trim =200fF * (1~31), cap inside chip, could be trimmed in MP process.C int 3pF, C int is a sub‐total cap value on the path, derived from layout trace and chip padCL=[(C L1*C L2)/(C L1+C L2)]+(C trim/2)+C int(e.g. Set trim value as 16, then C trim= 3.2pF.For a 16MHz crystal which C L=9pF, we can get C L1 = C L2 = 9.1 pF in this case.)For C L selection, please refer to the datasheet of crystal vendor9.0LED DRIVERThere are one dedicate LED drivers to control the LEDs. The LED can be connected directly with IS1678S. The LED max current is 4 mA and it has 16 steps to trim Brightness.The status LED (LED1) indicates:•Standby•Link Back•Low Battery•Inquiry•Link•PageEach indication is a configurable flashing sequence. LED brightness can also be configured.10.0MEMORYA synchronous single port RAM interface is used. There are sufficient ROM and RAM to fulfill the requirement of processor. A register bank, a dedicated single port memory and a flash memory are connected to the processor bus. The processor coordinates all the link control procedures and data movement using a set of pointers registers.11.0ThroughputThe IS1678S UART pins TXD and RXD connect to the UART pins of the host MCU. It is highly recommended to use hardware flow control pins RTS and CTS. The IS1678S hardware flow control is disabled by default and must be configured to enable. The UART Baud is configurable. The available signal rates are listed in Table 12-1.TABLE 11-2: APP mode Throughput report12.0TRANSCEIVERThe IS1678S is designed and optimized for Bluetooth 2.4 GHz system. It contains a complete radio frequency transmitter/receiver section. An internal synthesizer generates a stable clock for synchronize with another device.12.1 TRANSMITTERThe internal PA has a maximum output power of +4dBm. This is applied into Class2/3 radios without external RF PA.The transmitter directly performs IQ conversion to minimize the frequency drift, and it can excess 12dB power range with temperature compensation mechanism.12.2 RECEVIERThe LNA operates with TR‐combined mode for single port application. It can save a pin on package and without an external TX/RX switch.The ADC is utilized to sample the input analog wave and convert into digital signal for de‐modulator analysis. A channel filter has been integrated into receiver channel before the ADC, which to reduce the external component count and increase the anti‐interference capability.The image rejection filter is used to reject image frequency for low‐IF architecture. This filter for low‐IF architecture is intent to reduce external BPF component for super heterodyne architecture. RSSI signal is feedback to the processor to control the RF output power to make a good tradeoff for effective distance and current consumption.12.3 SYNTHESIZERA synthesizer generates a clock for radio transceiver operation. There is a VCO inside with tunable internal LC tank. It can reduce variation for components. A crystal oscillation with internal digital trimming circuit provides a stable clock for synthesizer.12.4 MODEMFor Bluetooth v1.2 specification and below, 1 Mbps was the standard data rate based on Gaussian Frequency Shift Keying (GFSK) modulation scheme. This basic rate modem meets BDR requirements of Bluetooth v2.0 with EDR specification.For Bluetooth v2.0 with EDR specification, Enhanced Data Rate (EDR) has been introduced to provide 2 and 3 Mbps data rates as well as 1 Mbps. This enhanced data rate modem meets EDR requirements of Bluetooth v2.0 with EDR specification. For the viewpoint of baseband, both BDR and EDR utilize the same 1MHz symbol rate and 1.6 KHz slot rate. For BDR, 1 symbol represents 1 bit. However each symbol in the payload part of EDR packets represents 2 or 3 bits. This is achieved by using two different modulations, π/4 DQPSK and 8DPSK.12.5 AFH (Adaptive Frequency Hopping)IS1678S have AFH function to avoid RF interference. It has an algorithm to check the interference nearby and choice clear channel to transceiver Bluetooth signal.ANTENNA PLACEMENT RULEFor Bluetooth product, antenna placement will affect whole system performance. Antenna need free space to transmit RF signal, it can’t be surround by GND plane.Here are some examples of good and poor placement on a Main Application board with GND plane.FIGURE 13-1: ANTENNA PLACEMENT EXAMPLESFIGURE 13-2: KEEP OUT AREA SUGGESTION FOR ANTENNAFor more detail free space of antenna placement design, you can reference the design rule of antenna produce vendor.13.0 Electrical CharacteristicsRecommended Operating Conditions1)HTOL life test condition : +125ºC , BAT_IN=4.2V, LDO33_O= 3.3V, LDO18_O=1.9V1)With 1uF capacitors at LDO18_O as the condition of IP verification.2)Output voltage can calibration by MP tool3)When V in>2.4V, the LDO could supply 100mA loading, when V in<2.4V, the output voltagedrop out depends on the loading.3.3V LDO1)With 10uF capacitor at LDO33_O as the condition of IP verification2)Output voltage can calibration by MP tool1)With 1uF capacitor at PMULDO_O as the condition of IP verification.2)Output voltage can calibration by MP toolSAR-ADC and Battery Voltage Detector1)SAR_BAT is shorted to BAT_IN internally for battery voltage detection. Intensity controllable LED driver14.0 Radio Characteristics:NOTE:1)The RF Transmit power calibrated during production using MP Tool software and MT8852 BluetoothTest equipment.2) Test condition: VCC_RF= 1.80V, temperature=25 ºC.Receiver Performance (25℃)NOTE:1) Test condition: VCC_RF= 1.80V, temperature=25 ºC.15.0 System Current Consumption(1)2. The DATA from IS1678S-151(1)2. The DATA from IS1678S-1513. Only LEIS1678S16.0 REFERENCE CIRCUITIS1678S Reference CircuitL D O 18_M A I N C I R C U I T1.0I S 1678S R E F E R A N C E C I R C U I TC u s t o m24W e d n e s d a y , M a y 20, 201502225F , N o .5, I n d u s t r y E . R d . V I I , H s i n c h u S c i e n c e P a r k ,H s i n c h u C i t y 30078, T a i w a n T E L . 886-3-5778385T P 2T P -2T P 6T P -2T P 10T P -2T P 3T P -2T P 7T P -2T P 11T P -2T P 5T P -2T P 13T P -2T P 9T P -2S W _B T NR S T _N_OM C UP 3_4P 3_7P 3_6P 0_5P 3_1P 3_3P 3_2S W _B T N W A K E U PU A R T _T X DU A R T _R X D P 0_4P 1_5U A R T T X D / R X DS t a t u s _I N DR e s e t f o r I 2C I CF u n c t i o n a lG P I OR S T _NU A R T C T S / R T SS W _B T NR S T _NW A K E U PP 1_7P 0_0B A T _I NU A R T _R X DE A NP 2_0P 2_4U A R T _T X DT e s t P I NT P 4T P -2T P 8T P -2P M U L D O _T P 12T P -2P M U L D O _OL D O 18_OL D O 33_O17.0 Package Information18.1 PACKAGE MARKING INFORMATION40 Lead QFN (6x6x0.9 mm) ExampleLegend:XXX: Chip serial number and versionYY: Year code (last 2 digits of calendar year)WW: Week code (week of January 1 is week “1”)NNN: Alphanumeric traceability code18.2 PACKAGE DETAIL18.3 Footprint dimensions18.0 REFLOW PROFILE AND STORAGE CONDITION19.1 STENCIL OF SMT ASSEMBLY SUGGESTION19.1.1 STENCIL TYPE & THICKNESS●Laser cutting●Stainless steel●Thicknedd0.5 mm Pitch : thickness < 0.15 mm19.1.2 APERTURE SIZE AND SHAPE FOR TERMINAL PAD●Aspect ratio ( width/thickness ) > 1.5●Aperture shapeThe stencil aperture is typically designed to match the pad size on the PCB.Oval-shaped opening should be used to get the optimum paste release.Rounded corners to minimize clogging.Positive taper walls (5o tapering ) with bottom opening larger than the top.19.1.3 APERTURE DESIGN FOR THERMAL PAD●The small multiple openings should be used in steady of one big opening.●60~80% solder paste coverage●Rounded corners to minimize clogging●Positive taper walls (5° tapering ) with bottom opening larger than the topDon’t recommend Recommend RecommendCoverage 91% Coverage 77% Coverage 65%19.2 REFLOW CONDITIONStandard : IPC/JEDEC J-STD-020Condition :Preheat:150~200℃、60~120 secondsAverage ramp-up rate (217℃ to peak): 3℃/sec max. Temperature maintained above 217℃ : 60~150 seconds Time within 5℃ of peak temperature: 30 ~ 40 seconds. Peak temperature:260 +5/-0 ℃Ramp-down rate (peak to 217℃) : 6℃/sec. max.Time 25℃ to peak temperature : 8 minutes max.Cycle interval:5 minutes19.3 STORAGE CONDITION1.Calculated shelf life in sealed bag: 24 months at < 40 ℃ and <90% relative humidity (RH)2.After bag is opened, devices that will be subjected to reflow solder or other high temperatureprocess must beMounted within 168 hours of factory conditions <30℃/60% RHFIGURE 19-2: LABEL OF CHIP BAG(Please notice the baking requirement)19.0 Packing Information1. Tape Orientation2. Dimensions (only reference)Minimum Order Quantity is 5000 Tape & Reel。
Keysight Technologies PXIe Optical Extenders for I
Keysight TechnologiesPXIe Optical Extenders for InstrumentationConiguration GuideOverviewThis configuration guide contains a step-by-step process to help you configure the family of PXI Optical Extenders including the use of the M9408A RF Reflectometer.For more detailed product and specification information refer to Keysight Technologies, Inc. Optical Extensions for Instrumentation literature:–Keysight PXIe Optical Extenders for Instruments Datasheet (literature no. 5991-0383EN)–Keysight PXIe Optical Extenders for Instruments – F lyer (literature no. 5990-9069EN)Coniguration Steps–Select your modules –Configure your modules –Add the chassis–Consider additional accessoriesFigure 1. Link Eficiency (dB) M9405A, M9403A and M9404A.Figure 2. Keysight M9018A PXI Chassis with 18-slot capacity.Select Your Modulesequipped with a configurable test set.300 kHz to 10 Mhz (coupling values willdegrade performance)The M9403A and M9404A complete an Optical Link. The optional M9405A can be added prior to or after the link, or included within the M9403A or M9404A. The M9406A and M9407A Optical to USB modules enables you to extend control devices to remote locations such as:–USB mouse–USB keyboard–VGA display (using USB to VGA adapter)–Keysight PNA series electronic calibration modules–USB power sensor–Other USB 1.1 and 2.0 compliant devicesThe M9408A RF Reflectometer enables full port extension of a vector network analyzer with a configurable test set such asthe PNA family of analyzers and can be used with the optical port extenders.Figure 3. Transmit and receive link with the Keysight M9403A and M9404A optical modules.A complete RF/ Optical/ RF link consists of 2 modules:–M9403A PXIe Optical Transmit module –M9404A PXIe Optical Receive moduleConfiguring a transmit and received linkConfiguring the M9403A Optical TransmitterFigure 4. M9403A Optical transmitter1. The internal preamplifier can be used to improve the Noise Figure of the Link. The maximum RF input level of the link is +7 dBm. With the preamplifier the maximum input level is -23 dBm.M9403A PXIe Optical Transmitter moduleThe M9403A is a two slot PXI module that converts your RF signal into a 1550 nm single mode optical signal. Step 1. Standard or Amplified?Select one option:–Standard Optical Transmitter module (M9403A_H01 E/O converter), or–Internal 30 dB preamp option (M9403A-H02 E/O converter with Amplifier)¹Step 2. Frequency Range?Select the desired frequency range for the M9403A Optical Transmitter module:–10 MHz to 26.5 GHz (M9403A-F26), or –10 MHz to 50 GHz (M9403A-F50)Figure 5. M9404A Optical receiverThe M9404A is a single slot PXI module that converts the modulated optical signal back to RF. The conversion loss of the link with no amplification is ~30 dB. Refer to the technical support information for complete nominal performance information at /litweb/pdf/5991-0383EN.pdf .Step 3. Standard or Amplified? Select one option:–Standard M9404A Optical Receiver module M9404A-H01 E/O converter), or –Internal 30 dB built in post amplifier (M9404A-H02 E/O converter)Step 4. Frequency Range?Select the desired frequency range for the M9404A Optical Transmitter module:–10 MHz to 26.5 GHz (M9404A-F26), or –10 MHz to 50 GHz (M9404A-F50)This provides a complete end to end optical link with E2000 APC (Angled Polished Connector) connectors. Operating the link requires a PXI chassis, such as the KeysightTechnologies M9018A at each end of the link. One chassis powers the M9403A and one chassis powers the M9404A. The optical link also requires a customer provided single mode fiber cable with E2000 APC connectors which completes the transmitter and receiver RF path.Configuring the M9404A Optical ReceiverConfiguring the optional M9405A 30 dB RF Amplifier ModuleFigure 6. M9405A 30 dB RF AmplifierThe M9405A 30 dB RF amplifier is a standalone, single module. A 30 dB amplifier can also be integrated directly into the M9403A Optical Transmitter and/or the M9404A Optical Receiver module by selecting option H02. When the M9405A is chosen, the amplifier is a standalonemodule providing the flexibility to be used on either end of the link as needed.Step 5. What Frequency Range?Choose the frequency range to match your Optical Link:–10 MHz to 26.5 GHz (M9405A-F26), or –10 MHz to 50 GHz (M9405A-F50)M9405A 30 dB RF Amplifier ModuleFigure 7. M9406A and M9407A USB Optical ExtendersConfiguring the optional M9406A and M9407A USB modulesConfiguring the M9408A RF Reflectometer 2Figure 8. M9408A RF Reflectometer2. Requires three each of the M9403A and M9404A pairs to fully extend the VNA port, one link for the Source RF in, one link for the Ref Coupler Arm, and one link for the Test Coupler Arm.The M9408A fully extends the port of a vector network analyzer equipped with a configurable test set such as a PNA. It is designed to work with three of the optical link pairs to accommodate the test coupler arm or reflected path, the reference coupler arm, and the source RF or test signal. It operates over the 300 kHZ to 50 GHz frequency range.Step 7. Extending the vector network analyzer port.Select the RF Reflectometer select:–M9408AThe M9406A and M9407A are 2-slot PXI USB modules that optically extend the USB 2.0 ports for the use of remote devices such as a keyboard, mouse or display. The USB ports can also support USB devices such as power sensors for remote power measurements.Step 6. Add the USB 2.0 Extenders, both are required:–M9406A-H01 –M9407A-H01These provide a complete end to end Optical USB extension. A pair of customer furnished optical cables with SC connectors are required to complete the link.M9404A RxM9408A PXIe Optical RF ReflectometerTest Coupler Arm Ref Coupler ArmSource RF in Source out Coupler thruPort 1 (extended)Add the ChassisAdditional AccessoriesM9018A PXIe Chassis (requires two)18-slot capacity2 PXI chassis are required to power the modules: –one chassis at the transmit end–one chassis at the receive end of the link –embedded controller not requiredY1213A PXI EMC Filler Panel Kit for 5 slotsThere are 21 total slots in the M9018A Mainframe. To en-sure proper cooling, please select the appropriate amount of blank panels to complete your systemY1215A Chassis rack mount kit for M9018AmyKeysight/find/mykeysightA personalized view into the information most relevant to you.AdvancedTCA® Extensions for Instrumentation and Test (AXIe) is anopen standard that extends the AdvancedTCA for general purpose and semiconductor test. Keysight is a founding member of the AXIe consortium. ATCA®, AdvancedTCA®, and the ATCA logo are registered US trademarks of the PCI Industrial Computer Manufacturers Group.PCI eXtensions for Instrumentation (PXI) modular instrumentation delivers arugged, PC-based high-performance measurement and automation system.Three-Year Warranty/find/ThreeYearWarrantyKeysight’s commitment to superior product quality and lower total costof ownership. The only test and measurement company with three-yearwarranty standard on all instruments, worldwide.Keysight Assurance Plans/find/AssurancePlansUp to five years of protection and no budgetary surprises to ensure yourinstruments are operating to specification so you can rely on accuratemeasurements./qualityKeysight Technologies, Inc.DEKRA Certified ISO 9001:2008Quality Management SystemKeysight Channel Partners/find/channelpartnersGet the best of both worlds: Keysight’s measurement expertise and productbreadth, combined with channel partner convenience.PICMG and the PICMG logo, CompactPCI and the CompactPCI logo, ATC® AdvancedTCA®and the ATCA logo are US registered trademarks of the PCI IndustrialComputers Manufacturers Group.“PCIe” and “PCI EXPRESS” are registered trademarksand/or service marks of PCI-SIG./find/modular/find/emailupdatesFor more information on KeysightTechnologies’ products, applications orservices, please contact your local Keysightoffice. The complete list is available at:/find/contactusAmericasCanada(877) 894 4414Brazil55 11 3351 7010Mexico001 800 254 2440United States(800) 829 4444Asia PaciicAustralia 1 800 629 485China800 810 0189Hong Kong800 938 693India 1 800 112 929Japan0120 (421) 345Korea080 769 0800Malaysia 1 800 888 848Singapore180****8100Taiwan0800 047 866Other AP Countries(65) 6375 8100Europe & Middle EastAustria0800 001122Belgium0800 58580Finland0800 523252France0805 980333Germany***********Ireland1800 832700Israel 1 809 343051Italy800 599100Luxembourg+32 800 58580Netherlands0800 0233200Russia8800 5009286Spain0800 000154Sweden0200 882255Switzerland0800 805353Opt. 1 (DE)Opt. 2 (FR)Opt. 3 (IT)United Kingdom0800 0260637For other unlisted countries:/find/contactus(BP-07-01-14)08 | Keysight | PXIe Optical Extenders for Instrumentation - Coniguration SheetThis information is subject to change without notice.© Keysight Technologies, 2012-2014Published in USA, August 2, 20145991-0368EN。
NVIDIA DOCA应用识别应用程序版本1.4说明书
ApplicationTable of ContentsChapter 1. Introduction (1)Chapter 2. System Design (2)Chapter 3. Application Architecture (5)Chapter 4. DOCA Libraries (6)Chapter 5. Configuration Flow (7)Chapter 6. Running Application (9)Chapter 7. Arg Parser DOCA Flags (13)Chapter 8. Deploying Containerized Application (15)Chapter 9. Managing gRPC-Enabled Application from Host (16)Chapter 10. References (18)Chapter 1.IntroductionApplication Recognition (AR) allows identifying applications that are in use on a monitored networking node.AR enables the security administrator to generate consolidated reports that show usage patterns from the application perspective. AR is also used as a corner stone of many security applications such as L7-based firewalls.Due to the massive growth in the number of applications that communicate over Layer 7 (HTTP), effective monitoring of network activity requires looking deeper into Layer 7 traffic so individual applications can be identified. Different applications may require different levels of security and service.This document describes how to build AR using the deep packet inspection (DPI) engine, which leverages NVIDIA® BlueField®-2 DPU capabilities such as regular expression (RXP) acceleration engine, hardware-based connection tracking, and more.Chapter 2.System DesignThe AR application is designed to run as "bump-on-the-wire" on the BlueField-2 instance, it intercepts the traffic coming from the wire, and passes it to the Physical Function (PF) representor connected to the host.System DesignSystem DesignChapter 3.Application ArchitectureAR runs on top of Data Plan Development Kit (DPDK) based Stateful Flow Tracking (SFT) to identify the flow that each packet belongs to, then uses DPI to process L7 classification.1.Signatures are compiled by DPI compiler and then loaded to DPI engine.2.Ingress traffic is identified using the stateful table module in the DPDK libs which utilizesthe connection tracking hardware offloads. This allows flow classifications to be done in the hardware level and be forwarded to the hairpin queue without being processed by the software, which increases performance dramatically.3.Traffic is scanned against DPI engine compiled signature DB.4.Post processing is performed for match decision.5.Matched flows are identified, and actions can be offloaded to the hardware to increaseperformance as no further inspection is needed.6.Flow termination is done by the aging timer set in the SFT to 60 seconds. When a flow isoffloaded it cannot be tracked and destroyed.Chapter 4.DOCA LibrariesThis application leverages the following DOCA libraries:‣DOCA DPI library‣DOCA Telemetry libraryChapter 5.Configuration Flow1.Parse application argument.doca_argp_init();a).Initialize arg parser resources and register DOCA general parameters.doca_argp_init();b).Register AR application parameters.register_ar_params();c).Parse the arguments.doca_argp_starti.Parse DPDK flags and invoke the handler for calling the rte_eal_init() function.ii.Parse app flags.2.DPDK initialization.dpdk_init();Calls rte_eal_init() to initialize EAL resources with the provided EAL flags.3.DPDK port initialization and start.dpdk_queues_and_ports_init();a).Initialize SFT.b).Initialize DPDK ports, including mempool allocation.4.AR initialization.ar_init();a).Initialize signature database.b).Initialize DPI engine.c).Load signatures to DPI.5.Configure DPI packet processing.dpi_worker_lcores_run();a).Configure DPI enqueue packets.b).Send jobs to RegEx engine.c).Configure DPI dequeue packets.6.Send statistics and write database.sig_database_write_to_csv();send_netflow_record();a).Send statistics to the collector.b).Write CSV file with signature statistics.Configuration Flow 7.AR destroy.ar_destroy();a).Clear thread.b).Stop DPI worker.c).Stop DOCA DPI.8.DPDK ports and queues destruction.dpdk_queues_and_ports_fini();9.DPDK finish.dpdk_fini();Calls rte_eal_destroy() to destroy initialized EAL resources.10.DPI destroydoca_dpi_destroy();11.Arg parser destroy.doca_argp_destroy()Chapter 6.Running Application1.Refer to the following documents:‣NVIDIA DOCA Installation Guide for Linux for details on how to install BlueField-related software‣NVIDIA DOCA Troubleshooting Guide for any issue you may encounter with the installation, compilation, or execution of DOCA applications‣NVIDIA DOCA Applications Overview for additional compilation instructions and development tips regarding the DOCA applications2.The application recognition binary is located under /opt/mellanox/doca/applications/ application_recognition/bin/doca_application_recognition. To build all the applications together, run:cd /opt/mellanox/doca/applications/meson buildninja -C build3.To build only the application recognition application:a).Edit the following flags in /opt/mellanox/doca/applications/meson_option.txt:‣Set enable_all_applications to false‣Set enable_application_recognition to trueb).Run the commands in step 2.Note:doca_application_recognition will be created under ./build/application_recognition/src/.Application usage:Usage: doca_application_recognition [DPDK Flags] -- [DOCA Flags] [Program Flags] DOCA Flags:-h, --help Print a help synopsis-v, --version Print program version information-l, --log-level Set the log level for the program <CRITICAL=20,ERROR=30, WARNING=40, INFO=50, DEBUG=60>Program Flags:-p, --print-match Prints FID when matched in DPI engine-n <source_id>, --netflow exports data from BlueField to remote DOCA Telemetry service, also sets source_id to be written to the Netflow packet.-i, --interactive Adds interactive mode for blocking signatures-o, --output-csv <path> Path to the output of the CSV file-c, --cdo <path> Path to CDO file compiled from a valid PDD-f, --fragmented Enables processing fragmented packetsNote: For additional information on available flags for DPDK, use -h before the --separator:/opt/mellanox/doca/applications/application_recognition/bin/doca_application_recognition -hNote: For additional information on the application, use -h after the -- separator:/opt/mellanox/doca/applications/application_recognition/bin/doca_application_recognition -- -h4.Running the application on BlueField:‣Pre-run setup:a).The application recognition example is based on DPDK libraries. Therefore, theuser is required to provide DPDK flags, and allocate huge pages.sudo echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepagesb).Make sure the RegEx engine is active:systemctl status mlx-regexIf the status is inactive (Active: failed), run:systemctl start mlx-regexc).To use the supplied signature file (suricata_rules_example), which is installedto the bin directory, the DPI compiler must be used, as the RegEx engine acceptsonly .cdo files. The CDO files are constructed by compiling a signature file writtenin the Suricata open-source format.Compile the signature file:doca_dpi_compiler -i /opt/mellanox/doca/applications/application_recognition/bin/ar_suricata_rules_example -o /tmp/ar.cdo -fsuricataA .cdo is created in the output path flagged as the -o input path of the compiler.That file can be used when executing the application using the -c flag.‣CLI example for running the app:/opt/mellanox/doca/applications/application_recognition/bin/doca_application_recognition -a 0000:03:00.0,class=regex -aauxiliary:mlx5_core.sf.4,sft_en=1 -a auxiliary:mlx5_core.sf.5,sft_en=1 -- -c /tmp/ar.cdo -pNote: The SFT supports a maximum of 64 queues. Therefore, the application cannot berun with more than 64 cores. To limit the number of cores, run:/opt/mellanox/doca/applications/application_recognition/bin/doca_application_recognition -a 0000:03:00.0,class=regex -aauxiliary:mlx5_core.sf.4,sft_en=1 -a auxiliary:mlx5_core.sf.5,sft_en=1-l 0-64 -- -pThis limits the application to 65 cores (core-0 to core-64) with 1 core for the mainthread and 64 cores to serve as workers.Note: The flags -a 0000:03:00.0,class=regex -aauxiliary:mlx5_core.sf.4,sft_en=1 -a auxiliary:mlx5_core.sf.5,sft_en=1are necessary for proper usage of the application. Modifying them results inunexpected behavior as only 2 ports are supported. The subfunction number isarbitrary and configurable. The RegEx device, however, is not and must be initiated onport 0.Note: Sub-functions must be enabled according to the Scalable Function Setup Guide.5.Running the application on the host, CLI example:doca_application_recognition -a 0000:04:00.0,class=regex -a 04:00.3 -a 04:00.4 -v -- -c suricata_rules_example.cdo -o /tmp/check.csv -pNote: Refer to section "Running DOCA Application on Host" in NVIDIA DOCA VirtualFunctions User Guide.6.To run doca_application_recognition using a JSON file:doca_application_recognition --json [json_file]For example:cd /opt/mellanox/doca/applications/application_recognition/bin./doca_application_recognition --json ./ar_params.jsonThe application periodically dumps a .csv file with the recognition results containing statistics about the recognized apps in the format SIG_ID, APP_NAME, MATCHING_FIDS, and DROP.As per the example above, a file called ar_stats.csv will be created.Additional features can be triggered by using the shell interaction. This allows blocking and unblocking specific signature IDs using the following commands:‣block <sig_id>‣unblock <sig_id>The TAB key allows autocompletion while the quit command terminates the application. NetFlow collector UI example:The NetFlow module uses the DOCA Telemetry Netflow library to export NetFlow packets in the NetFlow v9 format. The usage of telemetry is hardcoded to send packets to a collectorset on the host connected to the Bluefield device through the rshim interface (specifically 192.168.100.2:2055).It is recommended to use the DOCA telemetry service (DTS) as an aggregator to export records instead of exporting directly from the client side which requires enabling IPC. Refer to the NVIDIA DOCA Telemetry Service Guide guide for additional information.Chapter 7.Arg Parser DOCA FlagsRefer to NVIDIA DOCA Arg Parser User Guide for more information., "id": "00"id": "4","s"id": "5","sArg Parser DOCA FlagsChapter 8.Deploying ContainerizedApplicationThe application recognition example supports a container-based deployment:1.Refer to the NVIDIA DOCA Container Deployment Guide for details on how to deploy aDOCA container to the BlueField.2.Application-specific configuration steps can be found on NGC under the application'scontainer page.Chapter 9.Managing gRPC-EnabledApplication from HostRefer to NVIDIA DOCA gRPC Infrastructure User Guide for instructions on running the gRPC application server on the BlueField.Managing gRPC-Enabled Application from Host To run the Python client of the gRPC-enabled application:./doca_application_recognition_gRPC_client.py -d/--debug <server address[:serverport]>For example:/opt/mellanox/doca/applications/application_recognition/bin/grpc/client/doca_application_recognition_gRPC_client.py 192.168.104.2Chapter 10.References‣/opt/mellanox/doca/applications/application_recognition/src/ application_recognition.c‣/opt/mellanox/doca/applications/application_recognition/src/grpc/ application_recognition.proto‣/opt/mellanox/doca/applications/application_recognition/bin/ ar_suricata_rules_exampleNoticeThis document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation nor any of its direct or indirect subsidiaries and affiliates (collectively: “NVIDIA”) make no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assume no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice. Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk. NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.TrademarksNVIDIA, the NVIDIA logo, and Mellanox are trademarks and/or registered trademarks of Mellanox Technologies Ltd. and/or NVIDIA Corporation in the U.S. and in other countries. The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a world¬wide basis. Other company and product names may be trademarks of the respective companies with which they are associated.Copyright© 2022 NVIDIA Corporation & affiliates. All rights reserved.NVIDIA Corporation | 2788 San Tomas Expressway, Santa Clara, CA 95051。
FortiConverter 配置迁移到 FortiOS说明书
FortiConverter™Configuration Migration to FortiOSFortiConverter Service helps you migrate to the latest versionof FortiOS. This service is useful for migrating a pre-existingthird-party firewall policy to a new FortiGate appliance, oreven an older FortiGate policy to a new one.§Reduces migration complexities§Eliminates common migration configuration errors§Includes change logs to documents that were migratedFortiConverter Service supports migration of interface NAT,firewall policy and address objects, as well as static routes for third-party vendor configuration to FortiGate configuration. All FortiGate to FortiGate configurations are fully supported.Many organizations and consulting services companies use FortiConverter Service for their migration projects, but you may choose to engage Fortinet Professional Services to provide customized consulting service for your migration. By engaging the skills and experience of Fortinet Professional Services, you avoid pitfalls that can befall migration projects.Typical migration tasks include:§Solution design, design guides, and best practice §Project and migration plans §Migration risk analyses §Appliance commissioning §Policy migration§Cutover support and troubleshooting §Test plan execution and validation §Post-cutover incident managementTo engage Fortinet Professional Services for your project, contact your Fortinet partner account manager.FortiConverter Migration T oolSome organizations planning to perform multiple migrations over a year prefer to purchase a software tool, allowing them to perform and tune their own migration files. Purchased as a subscription for a one year period, the FortiConverter Migration Tool allows an organization to perform an unlimited number of migrations during the year over the entire FortiConverter library of third-party firewalls, including some fine tuning to customize the migration file.FortiConverter Service is sold as a one-time service to convert one third-party or older FortiOS configuration to the latest FortiOS for the new FortiGate. FortiConverter Service is currently available for the following newer FortiGate hardware and virtual appliances:FortiGate-30E FortiWiFi-30E FortiGate-30E-3G4G FortiWiFi-30E-3G4G FortiGate-50E FortiWiFi-50E FortiWiFi-50E-2R FortiGate-51E FortiWiFi-51E FortiGate-52E FortiGate-60E FortiWiFi-60E FortiGate-60E-DSL FortiWiFi-60E-DSL FortiGate-60E-POE FortiGate-61E FortiWiFi-61E FortiGate-80E FortiGate-80E-POE FortiGate-81E FortiGate-81E-POE FortiGate-90EFortiGate-100E FortiGate-100EF FortiGate-101EFortiGate-140E FortiGate-140E-POE FortiGate-200E FortiGate-201E FortiGate-300E FortiGate-301E FortiGate-500E FortiGate-501E FortiGate-2000E FortiGate-2500E FortiGate-3960E FortiGate-3960E-DC FortiGate-3980E FortiGate-3980E-DC FortiGate-6300F FortiGate-6301F FortiGate-6500F FortiGate-6501FFortiGate-VM00FortiGate-VM01FortiGate-VM01V FortiGate-VM02FortiGate-VM02V FortiGate-VM04FortiGate-VM04V FortiGate-VM08FortiGate-VM08V FortiGate-VM16FortiGate-VM16V FortiGate-VM32FortiGate-VM32V FortiGate-VMUL FortiGate-VMULVFortiConverter ServiceAdd-on SKU Product Base Product SKU DescriptionFC-10-0030E-189-02-DD FortiGate FG-30E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00038-189-02-DD FortiGate FWF-30E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-E30EI-189-02-DD FortiGate FG-30E-3G4G-INTL FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-I30EI-189-02-DD FortiGate FWF-30E-3G4G-INTL FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-G30EN-189-02-DD FortiGate FG-30E-3G4G-NAM FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-I30EN-189-02-DD FortiGate FWF-30E-3G4G-NAM FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0050E-189-02-DD FortiGate FG-50E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00055-189-02-DD FortiGate FWF-50E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-W502R-189-02-DD FortiGate FWF-50E-2R FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0051E-189-02-DD FortiGate FG-51E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00056-189-02-DD FortiGate FWF-51E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0052E-189-02-DD FortiGate FG-52E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0060E-189-02-DD FortiGate FG-60E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-W060E-189-02-DD FortiGate FWF-60E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FG60E-189-02-DD FortiGate FG-60E-DSL FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FW60F-189-02-DD FortiGate FWF-60E-DSL FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FG60P-189-02-DD FortiGate FG-60E-POE FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0061E-189-02-DD FortiGate FG-61E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-W061E-189-02-DD FortiGate FWF-61E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00E80-189-02-DD FortiGate FG-80E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0080E-189-02-DD FortiGate FG-80E-POE FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00E81-189-02-DD FortiGate FG-81E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0081E-189-02-DD FortiGate FG-81E-POE FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0090E-189-02-DD FortiGate FG-90E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FG1HE-189-02-DD FortiGate FG-100E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FG1HF-189-02-DD FortiGate FG-100EF FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00119-189-02-DD FortiGate FG-101E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00144-189-02-DD FortiGate FG-140E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00143-189-02-DD FortiGate FG-140E-POE FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00207-189-02-DD FortiGate FG-200E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00208-189-02-DD FortiGate FG-201E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00306-189-02-DD FortiGate FG-300E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-00307-189-02-DD FortiGate FG-301E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0500E-189-02-DD FortiGate FG-500E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-0501E-189-02-DD FortiGate FG-501E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-002KE-189-02-DD FortiGate FG-2000E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-02K5E-189-02-DD FortiGate FG-2500E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-03961-189-02-DD FortiGate FG-3960E FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration serviceGLOBAL HEADQUARTERS Fortinet Inc.899 KIFER ROAD Sunnyvale, CA 94086United StatesTel: +/salesEMEA SALES OFFICE 905 rue Albert Einstein 06560 Valbonne FranceTel: +33.4.8987.0500APAC SALES OFFICE 8 Temasek Boulevard#12-01 Suntec Tower Three Singapore 038988Tel: +65.6395.2788LATIN AMERICA SALES OFFICE Sawgrass Lakes Center13450 W. Sunrise Blvd., Suite 430 Sunrise, FL 33323United StatesTel: +1.954.368.9990Copyright© 2018 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., in the U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any commitment related to future deliverables, features or development, and circumstances may change such that any forward-looking statements herein are not accurate. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.FST -PROD-DS-FCCC FC-DAT -R9-201808FortiConverter™Product SKUDescriptionFortiConverter FC-10-CON01-401-01-121-year multi-vendor configuration migration tool for building FortiOS configurations, requires Windows.FortiConverterFC-10-CON01-401-02-121-year renewal multi-vendor configuration migration tool for building FortiOS configurations, requires Windows.Add-on SKUProduct Base Product SKU DescriptionFC-10-FVM16-189-02-DD FortiGate VM FG-VM16FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-F16VM-189-02-DD FortiGate VM FG-VM16V FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FVM32-189-02-DD FortiGate VM FG-VM32FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-F32VM-189-02-DD FortiGate VM FG-VM32V FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FVMUL-189-02-DD FortiGate VM FG-VMUL FortiConverter Service for FortiGate-to-FortiGate one-time configuration migration service FC-10-FULVM-189-02-DDFortiGate VMFG-VMULVFortiConverter Service for FortiGate-to-FortiGate one-time configuration migration serviceORDER INFORMATIONFortiConverter ServiceFortiConverter Migration T ool。
2023 捷达买家指南说明书
The 2023 VW JettaThey say ‘never judge a book by its cover’. The same goes for the 2023 Volkswagen Jetta. Because this isn’t your typical ride. It’s a German-engineered icon, inside and out.Let’s start in the driver’s seat. The Standard Digital Cockpit with 8” digital display serves up driving info for you at a glance. Upgrade to the available 10.25” Digital Cockpit Pro and you can customize the full-screen display with the info you want. With the 10 colours of Interior Ambient Lighting, you can customize the cabin with the vibe you want, too. Intuitive design and ultimate comfort come together in the Jetta, with a driver-centric dash and premium leather materials that prove no detail is too small.When it comes to performance, the Jetta givesyou more get-up with fewer fill-ups thanks tothe 1.5 TSI® engine with class-leading torque and exceptional fuel efficiency.Pure thrillsThe fun-to-drive Jetta performance comes with peace-of-mind driving thanks to a full suite of active safety features. Like Front Assist with Autonomous EmergencyBraking * which acts as an extra set of eyes, and a quicker set of brakes to help prevent accidents before they happen.The 2023 Jetta is fully-connected with some impressive tech. With the available Car-Net® App, you can connect to your Jetta in over 20 ways, from your smartphone. From anywhere. Speaking of smartphones, with available wireless Apple CarPlay® and Android Auto™ and Wireless Charging , you can spend more time connected on the road and less time fumbling for cords. When it comes style, tech, and fun, there’s nothing like the Jetta.Connected and protectedThe 2023 VW Jetta*Driver assistance feature. Drivers must continue to perform manual checks and pay full attention to the road and safe driving at all times. See owner’s manual for important information and feature limitations.Fuel consumption figures are estimates based on Natural Resources Canada’s approved criteria and testing methods. Refer to the EnerGuide 2023 for Natural Resources Canada’s estimated fuel consumption figures. Actual fuel consumption will vary based on driving conditions, driver habits and the vehicle’s condition, weight carried and additional equipment.Paint & upholstery options by trimCustomize your JettaMake your Jetta your own with styles and features you’ll love.Wheel options0217" Viper(Comfortline)0317" Singapore(Comfortline Sport Package)0417" Single(Highline)0116" Kiwano(Trendline)√√√√√_√√√√√√_√√When compared to pay-as-you- go maintenance, VW Prepaid Maintenance isn’t just better for your Volkswagen, it’s better for your wallet too, with up to 26% in savings.2On top of our 3,-4, and-5 year plans, we now offer a new, comprehensive 2-year Prepaid Maintenance plan designed to give you even more savings and peace of mind.Why it pays to go Prepaid:• VW expertise• Genuine parts and fluids • Rigorous multipoint inspection • Comprehensive coverage • Lower cost of ownership • Regularly scheduled serviceLearn more at www.vw.caCost of maintenancePrepaid MaintenanceEasy to get into Easy to maintainThe Jetta is built to perform now, and down the road. With a longer-than-average warranty and world-class German engineering, owning and maintaining one is a lot more affordable than you think. In fact, it’s among the most cost-effective vehicles to maintain in its entire segment.1 Use the convenient third party Vincentric cost of maintenance tool at vw.ca to see for yourself.A whole lot less than you’d expectBased on a comparison to other 2023 vehicles available at the time of publication.Up to 26% savings compared to the cost of paying for maintenance, on a per service basis. Potential savings percentage determined using the average savings amount of all model/year plans vs. the retail cost of individual services in 2022. See dealer for details.© 2022 Volkswagen Canada. Items, specifications, availability, standard features, options, fabrics and colours are subject to change without notice. Volkswagen Canada is not responsible for errors in typography or photography. Some features may be unavailable when your vehicle is built or available at extra cost. Although we endeavour to ensure that the information is accurate, as errors may occur from time to time, customers should contact their local Volkswagen dealer for details. Tires are supplied and warranted by their manufacturer. The vehicle is sold equipped with four all-season tires. However, please remember that the use of winter tires may be mandatory in your province or territory. Airbags are supplemental restraints only and will not deploy under all accident scenarios. Always use safety belts and seat children only in the rear seats, using restraint systems appropriate for their size and age. The navigation system depends upon signals from the GPS network and is designed to provide you with suggested routes only. Discrepancies may occur between the mapping and the actual location due to changes in street names, construction or other road system changes which are beyond the control of Volkswagen Canada. Please rely on your individual judgment in determining whether or not to follow a suggested navigation route. “Jetta”, “4MOTION”, “Climatronic”, “TSI”, “Volkswagen” and the Volkswagen logo are registered trademarks of Volkswagen AG. The Bluetooth word mark and logos are registered trademarks of Bluetooth SIG, Inc. “SiriusXM”, the SiriusXM logo, channel names and logos are trademarks of Sirius XM Radio Inc. and are used under licence. “Tiptronic” is a registered trademark of Dr. Ing. h.c. F. Porsche AG. “Android Auto” is a trademark of Google LLC. “Apple CarPlay” is a trademark of Apple Inc., registered in the US and other countries. “MirrorLink” is a registered trademark of Car Connectivity Consortium LLC. For further information regarding any Volkswagen model, please call 1-800 DRIVE VW or just look us up at vw.ca. Before we sign off, drive responsibly and obey the rules of the road. Version date: September 7, 2022.The 2023 JettaTrims and optionsTrendlinePerformance• Start/stop system with regenerative braking – automatic transmission • ECO driving mode• Speed-sensitive power steering • Electronic parking brakeSafety• Hill Hold Assist • Alarm system• Front Assist with Autonomous Emergency Braking and Pedestrian Detection• Front and rear Side Curtain Protection® with front side airbags • Cruise control• Rearview camera with static guidance lines • Tool kit• Tire mobility set• Washer fluid level indicatorInfotainment & Technology• 6.5" touchscreen infotainment system• Volkswagen Digital Cockpit (8" instrument cluster)• App-Connect smartphone integration (Apple CarPlay® and Android Auto TM )• USB Type C port (x1)• Bluetooth® mobile phone connectivity • 4 speakersExterior• 16" Kiwano alloy wheels (6.5J x 16)• All-season tires, 205/60 R16 92H• Tire Pressure Monitoring System (TPMS)• Automatic headlights with coming and leaving home function • Power-adjustable, heated exterior mirrors • Body-coloured exterior mirror housings • Chrome window surrounds • Heated washer nozzles • LED tail lights• LED headlights with LED signature Daytime Running Lights (DRLs)Interior• 6-way manually adjustable driver seat • Cloth seating surfaces• Heated front comfort seats • 60/40 split-folding rear seats• Resistive heating element for cabin • Manual air conditioning• First- and second-row floor mats • Front centre armrest • Leather gearshift knob • Interior chrome accents • Decorative inserts: Fishbone • Leatherette door inserts• Multifunction heated leather steering wheelHighlineTransmission8-speed automatic with Tiptronic® onlyIncludes Comfortline equipment plus:Performance• Electronic differential lock XDS • Driving Profile SelectionInfotainment & Technology• Volkswagen Digital Cockpit Pro(10.25" configurable instrument cluster)• BeatsAudio® Premium Audio System – 6 speakers plus subwoofer • Satellite navigationExterior• 17" Single alloy wheels (7J x 17)• Rail2Rail power sunroof • Heated wiper park• Illuminated exterior design elements • LED headlights with LED signature Daytime Running Lights (DRLs)• Sport bumper• Power-adjustable, heated exterior mirrors with memory functionInterior• Overhead storage compartment• Interior ambient lighting – customizable up to 10 colours • 2 front and 2 rear LED reading lights • Illuminated vanity mirrors • Ventilated front seats • Leather seating surfaces• 6-way power-adjustable driver seat with memory function • Heated front and outer rear seats • Leatherette door inserts• Decorative inserts: Sliced Metal BrushComfortlineIncludes Trendline equipment plus:Safety• Light Assist (automatic high beam control)• Blind Spot Monitor with Rear Traffic Alert• Travel Assist (Adaptive Cruise Control and Lane Assist) – manual transmission• Travel Assist (Adaptive Cruise Control, Lane Assist and Emergency Assist) – automatic transmission • Adaptive Cruise Control – manual transmission • Adaptive Cruise Control with Stop and Go – automatic transmission • Tool kit and jack• Space- and weight-saving spare tire (18")Infotainment & Technology• Wireless App-Connect smartphone integration (Apple CarPlay® and Android Auto TM )• USB Type C port (x2)• Volkswagen Car-Net® (remote connectivity) • 8" touchscreen infotainment system • Emergency Call Service • Voice control• KESSY – keyless access with push-start button • SiriusXM® satellite radio • Wireless device charging • 6 speakers• Remote start – automatic transmissionExterior• Rain-sensing wipers• 17" Viper alloy wheels (7J x 17)• All-season tires, 205/55 R17 91H, low rolling resistanceInterior• Climatronic® dual-zone front electronic air conditioning • 60/40 split-folding rear seats with centre armrest • Auto-dimming interior rearview mirror • 2-way driver power lumbar support • Front sport seats• Decorative inserts: Technical Rain • Leatherette seating surfaces• 10-way power-adjustable driver seatOptional equipmentSport Package• Overhead storage compartment • “Rail2Rail” power sunroof• Interior ambient lighting – customizable up to 10 colours • 2 front and 2 rear LED reading lights • Volkswagen Digital Cockpit Pro(10.25" configurable instrument cluster) • Illuminated vanity mirrors • Heated wiper park• Illuminated exterior design elements • Driving Profile Selection• Electronic differential lock XDS • Black exterior mirror housings • Black headliner• Black window surrounds• 17" Singapore alloy wheels (7J x 17) • Sports suspension • Sport bumper。
吉尔范(Gefran)产品介绍:压力传感器与传输器的数据手册说明书
SENSORSC OD . 81221FPRESSURE TRANSDUCERS AND TRANSMITTERSENG2Thanks to forty years of experience, Gefran is the world leader in the design and production of solutions for meas-uring, controlling, and driving industrial production processes .We have branches in 14 countries and a network of over 80 worldwide distributors.QUALITY AND TECHNOLOGYA pressure transducer is an electronic device that converts a physical variable (pressure) into an electrical sig-nal (current or voltage) that can be read or acquired by various control, measurement, and adjustment devices.Gefran, with its own Technological Pole, is one of the few international companies with the know-how to create sensitive elements based on the following technologies: Thick film on stainless steel, Bonded strain gauge, Piezoresistive silicon .Gefran sensors can measure the pressure of fluids and gases in all industrial applications, with a complete line for ranges from 0…50 mbar to 0…5000bar for both relative and absolute pressures.ONE STOP SHOPGefran offers complete display solutions for industry , providing its own sensors and ensuring maximum compo-nent compatibility and integration .SERVICESA team of Gefran experts works with the customer to select the ideal product for its application and to help install andconfiguredevices(***********************)..Gefran offers a wide range of courses at different levels for the technical-commercial study of the Gefran product range as well as specific courses on demand..APPLICATIONSPLASTIC AND RUBBER INJECTIONPRESSESBLOWING MACHINESPRESSES AND METAL WORKINGMACHINERY FLUID POWER AND HYDRAULIC POWER PACKS AGRICULTURAL AND EARTH-MOVINGMACHINERYAUTOMOTIVE TEST EQUIPMENTS, ENGINE TEST BEDSTEST BENCHES AND TEST EQUIPMENTSTEAM TREATMENT PLANTSTEST BENCHES AND TEST EQUIPMENTMATERIAL TEST MACHINES ATEXFOOD INDUSTRY4BONDED STRAIN GAUGEBonded strain-gauge technology is very often used to produce pres-sure sensors thanks to its applicative versatility, reliability, and ac-curacy.The measurement element (resistance) consists of an extremely thin foil of metal alloy, chemically etched using a specific process.The resistance and diaphragm are bonded with sophisticated tech-niques after precise positioning of the strain-gauge (extensometer)to ensure perfect adhesion to the surface and to guarantee linearity and repeatability.PIEZORESISTIVE SILICONPiezoresistive silicon technology is characterised by complex and de-licate installation of the chip (solid state Wheatstone bridge) on the metal support and by a separating metal diaphragm with interposi-tion (under vacuum) of insulating silicone oil (filling).Thanks to this technology, the measurement range of Gefran sen-sors can be very low (0-50 mbar), with high precision and overpres-sure capacity.Gefran owns the technology for its transducers.:THICK FILM ON STAINLESS STEELThe Wheatstone bridge is made with the screen printing process, which deposits the insulating layer (dielectric), the conducting layer (Cermet) and the resistive layer on the steel diaphragm.The thickness of the diaphragm determines the measurement range, and the increase from 200°C to 900°C makes the sensor extremely sturdy and reliable.To further ensure quality, the diaphragm is connected to the electro-nics by means of Wire Bonding .OUR PASSION FOR TECHNOLOGYMEASUREMENT RANGESWIDE RANGE OF PRODUCTS FOR EVERY APPLICATIONGefran offers an extremely wide range of transducers topressure in all industrial applicationsThe range includes models for specialprecision, as well as for use in veryronments as typical on mobile machines.The TPF/TPFADA series is an advancedvery sturdy steel flush measurement diaphragm.TPFAS This makes it unique and especiallypressure of very dense and harsh fluids and pastesAdd to this the new series TPFAS that introduces thediaphragms down to Ø 8.6 mm, which are the smallest of this kindonthe market.The TPH/TPHADA, series, with monolithic measurement diaphragm,is the ideal product for measuring very high pressures (up to 5000bar), including with highly dynamic pressure pulsation.KS6≥ 0.15% FS ÷ ≤≥ 0.25% FS ÷ ≤ 0.5% FSGUIDE TO SELECTIONPRESSURE TRANSDUCERS AND TRANSMITTERSDISPLAYThe TDP-1001 plug-in display is a universal PRESSURE INDICATORS- universal inputs for amplified sensors - very high acquisition speed - high accuracy- math calculations, pressure delta - 4 configurable outputs- Modbus and Profibus communications - input for non-amplified pressure sensors - 4 configurable outputs - Modbus communications- input for amplified pressure sensors - 4 configurable outputs - Modbus communicationADAPTERS AND SEALSGefran pressure transducers offer a very wide selection of built-in pressure connec-tions: metric, gas, NPT and UNF, as well as a wide range of stainless steel adapters (both male/male and male/female) with seals, cal-led PKITxxx , to satisfy all possible process connection requirements.CONNECTORS AND EXTENSION CABLESGefran pressure transducers are available with various types of electrical connectors (EN 175301-803, M12x1, etc.), and for each of these Gefran supplies the female connector for the cable to be soldered (called CON xxx) or an extension cable pre-attached to the fe-male connector (called CAV xxx) with length up to 30 metres.Drive & Motion Control Unit Via Carducci, 2421040 GERENZANO (VA) ITALY Ph. +39 02967601Fax +39 029682653**********************Technical Assistance:*********************Customer Service*************************Ph. +39 02 96760500 Fax +39 02 96760278GEFRAN HEADQUARTER Via Sebina, 7425050 PROVAGLIO D’ISEO (BS) ITALY Ph. +39 03098881Fax +39 0309839063GEFRAN DEUTSCHLAND GmbH Philipp-Reis-Straße 9a D-63500 SeligenstadtPh. +49 (0) 61828090Fax +49 (0) 6182809222******************GEFRAN BENELUX NV ENA 23 Zone 3, nr . 3910 Lammerdries-Zuid 14A B-2250 OLENPh. +32 (0) 14248181Fax +32 (0) 14248180**************GEFRAN SIEI - ASIA 31 Ubi Road 1 #02-07,Aztech Building, Singapore 408694Ph. +65 6 8418300Fax +65 6 7428300***************.sg SIEI AREG - GERMANY Gottlieb-Daimler Strasse 17/3D-74385 PleidelsheimPh. +49 (0) 7144 897360Fax +49 (0) 7144 8973697****************GEFRAN UK LtdUnit 7 Brook Business Centre 54a Cowley Mill Road Uxbridge UB8 2FXPh. +44 (0) 8452 604555Fax +44 (0) 8452 604556 ***************.uk GEFRAN INDIASurvey No. 191/A/1,Chinchwad Station Road, Chinchwad, Pune-411033, Maharashtra Ph. +91 20 6614 6500Fax +91 20 6614 6501**********************SENSORMATE AGSteigweg 8,CH-8355 Aadorf, Switzerland Ph. +41(0)52-2421818 Fax +41(0)52-3661884http://www.sensormate.chGEFRAN MIDDLE EAST ELEKTRIK VE ELEKTRONIK San. ve Tic. Ltd. StiYesilkoy Mah. Ataturk Cad. No: 12/1 B1 Blok K:12 D: 389 Bakirkoy /Istanbul TURKIYE Ph. +90212 465 91 21Fax +90212 465 91 22GEFRAN Inc.8 Lowell AvenueWINCHESTER - MA 01890Toll Free 1-888-888-4474Fax +1 (781) 7291468******************GEFRAN FRANCE SA 4, rue Jean Desparmet BP 823769355 LYON Cedex 08Ph. +33 (0) 478770300Fax +33 (0) 478770320********************GEFRAN SIEIDrives Technology Co., Ltd No. 1285, Beihe Road, Jiading District, Shanghai, China 201807Ph. +86 21 69169898Fax +86 21 69169333***************.cnGEFRAN BRASILELETROELETRÔNICA Avenida Dr . Altino Arantes,377 Vila Clementino04042-032 SÂO PAULO - SP Ph. +55 (0) 1155851133Fax +55 (0) 1132974012********************.br04/2016。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
SIGF:A Family of Configurable,Secure Routing Protocols for Wireless Sensor NetworksAnthony D.Wood,Lei Fang,John A.StankovicDepartment of Computer ScienceUniversity of Virginia {wood,leifang,stankovic}@Tian HeDept.of Computer Science and Engineering University of Minnesotatianhe@ABSTRACTAs sensor networks are deployed in adversarial environments and used for critical applications such as battlefield surveil-lance and medical monitoring,security weaknesses become a big concern.The severe resource constraints of WSNs give rise to the need for resource bound security solutions.In this paper we present SIGF(Secure Implicit Geographic Forwarding),a configurable secure routing protocol family for wireless sensor networks that provides“good enough”se-curity and high performance.By avoiding or limiting shared state,the protocols prevent many common attacks against routing,and contain others to the local neighborhood. SIGF makes explicit the tradeoffbetween security pro-vided and state which must be stored and maintained.It comprises three protocols,each forming a basis for the next: SIGF-0keeps no state,but provides probabilistic defenses; SIGF-1uses local history and reputation to protect against certain attacks;and SIGF-2uses neighborhood-shared state to provide stronger security guarantees.Our performance evaluation shows that SIGF achieves high packet delivery ratios with low overhead and end-to-end delay.We evaluate the security of SIGF protocols under various security attacks and show that it effectively contains the damage from compromised nodes and defends against black hole,selective forwarding,Sybil,and some denial of service attacks.Categories and Subject DescriptorsC.2.2[Computer-Communication Networks]:Network Protocols—Routing ProtocolsGeneral Terms:Security,Design,Performance Keywords:Wireless Sensor Network,Secure Routing1.INTRODUCTIONSecurity is critical for many wireless sensor network appli-cations such as battlefield surveillance,medical monitoring, Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on thefirst page.To copy otherwise,to republish,to post on servers or to redistribute to lists,requires prior specific permission and/or a fee.SASN’06,October30,2006,Alexandria,Virginia,USA.Copyright2006ACM1-59593-554-1/06/0010...$5.00.and emergency response.However,many security mecha-nisms developed for the Internet or ad-hoc networks cannot be applied directly to wireless sensor networks(WSNs)due to their limited resources in computation,memory,commu-nication bandwidth,and energy.The severe resource constraints of WSNs give rise to the need for resource bound security solutions.There are at least two interesting aspects of this concept.First,indi-vidual security mechanisms must be efficient in memory, computation,energy and bandwidth.For example,certain cryptographic schemes are inappropriate because ciphertext message expansion results in costly memory,bandwidth and energy use.Second,the resource consumption of all security mechanisms installed together at a node must not exceed the amount of resources allocated for security and they cannot degrade performance to an unacceptable level during normal operation nor when an attack is underway.It is not possible in today’s state of the art to include strong security mechanisms for each of the services at a node such as medium access control,routing,localization,time synchronization,power management,sensing,and group management.Consequently,even if a secure(to a wide vari-ety of attacks)routing protocol is implemented,it may suffer from low efficiency and would not protect against attacks on the other services.Our approach for resource bound security is to have min-imal active security protection.This results in very high performance and minimal resource consumption when no attacks are underway.Then upon detecting an attack or if the system designers expect increased threats,the appro-priate security mechanism is activated.The result is not 100%security protection—but good enough security,acti-vated at the right time.This general approach makes it possible to have high performance and to react to current security attacks,and is even more evolvable to new attacks than approaches thatfix a set of solutions into a node.In this paper we present Secure Implicit Geographic For-warding(SIGF),a family of configurable secure routing pro-tocols that follow this general approach.For a complete WSN solution similar families of protocols would be required for each of the other services.SIGF is based on IGF[1],a nondeterministic Network/ MAC hybrid routing protocol that is completely stateless. This allows it to handle network dynamics effortlessly,and intrinsically limits the effects of a compromised node to a local area.There are no routing tables to corrupt,since forwarding decisions are made as late as possible—when a packet is ready to transmit over the air.Nevertheless,itis susceptible in the local neighborhood to a simple CTS rushing attack[9].SIGF comprises three protocols which extend IGF and populate the gap between pure statelessness and traditional shared-state security.SIGF-0keeps no state,but uses non-determinism and candidate sampling to achieve high packet delivery ratios probabilistically.SIGF-1keeps local state, building reputations for its neighbors to aid in next-hop se-lection.SIGF-2uses state shared with neighbors to provide the strongest defense against attack,yet at the greatest cost. Each protocol encompasses the features of the previous,lay-ering additional mechanisms to defend against more sophis-ticated attacks.The layered family of protocols allows a network to activate only the protections currently necessary, and to change to stronger ones only if they are warranted. We evaluate the performance of each protocol by simulat-ing with no attacks,and with black hole,selective forward-ing,Sybil,and denial of service attacks.We show that each protocol represents a tradeoffbetween state and security, and that despite keeping no state,SIGF-0performs well. We make several contributions in this work.First,we show that even with no security countermeasures,the base protocol IGF has desirable attack containment properties, but nevertheless falls to several attacks that completely dis-rupt communication in a local neighborhood.Then we pre-sent the design and evaluation of SIGF,a secure routing protocol family built upon IGF.In our tested scenarios,un-der black hole attack from a single node the stateless SIGF-0 protocol maintains45%packet delivery ratio(PDR),while the reputation-based SIGF-1achieves97%PDR.In the six-node Sybil attack,SIGF-1still delivers83%of packets.To the best of our knowledge,SIGF is thefirst configurable routing protocol for WSNs that makes explicit the trade-offs between resources required and security provided,and enables resource bound security that is both efficient and effective.It is possible that some WSNs require much stronger se-curity than what our dynamic approach offers.However, no perfect solution exists—nor is likely to exist on severely resource constrained devices.Our approach,as exemplified by the SIGF routing protocols presented in this paper,can significantly improve security(not make it absolute),allow operation in the presence of attacks,and support a high performance system.For example,consider a military surveillance,tracking, and classification system for rare-event areas.The system may operate undetected for months,with no attacks and great performance using lightweight protocols.When an ad-versary eventually detects the system and drops in a node to create a routing black hole,then our solution would ac-tivate a form of secure routing that can recover from this attack.In most cases the loss of some messages is not criti-cal because of the periodic and highly redundant nature of the system.The rest of this paper is organized as follows.In the next section we briefly review our foundational routing proto-col,IGF.Then Section3describes system assumptions and routing attacks on IGF.Section4presents SIGF,our secure routing protocol family.In Section5we present our ex-periments and a detailed evaluation of the protocols under various attacks.Finally,we discuss related work in Section6 and then conclude.2.IMPLICIT GEOGRAPHIC FORW ARDING Our foundational routing protocol is Implicit Geographic Forwarding(IGF)[1],which is completely stateless,with-out dependence on knowledge of the network topology or the presence/absence of any other nodes.It makes non-deterministic routing decisions,implicitly allowing receiv-ing nodes to determine a packet’s next-hop at transmission time.IGF couples the routing and MAC components into a single integrated Network/MAC protocol.It identifies the best forwarding candidate during MAC-layer handshaking at the instant a packet is sent.Figure1:Forwarding area for message sender S. Figure1presents an example topology,where source node S transmits a message toward D.Routing is integrated with the RTS/CTS hand-shake of MACA/802.11[10]DCF MAC protocols.The communication handshake for this example topology is shown in Figure2.It begins when the sender S’s NAV timer is zero and it carrier senses an idle channel for DIFS time.Having verified that the channel is free,S broadcasts an Open RTS(ORTS)containing its location S and desti-nation D.Figure2:IGF handshake timeline. Neighbors are eligible to forward the message if they are within a60◦sextant centered on the direct line from the sender to the destination(the forwarding area).We call the nodes in the forwarding area candidate nodes.Such nodes set a CTS Response timer inversely proportional to a weighted sum of their distance from the sender,remain-ing energy,and perpendicular distance to a line from the sender to the destination.This favors the nodes that are more desirable for forwarding.On the expiry of a node’s CTS response timer,it responds with a CTS packet,and the data is transferred from the Open RTS sender in a DATA message.The valid duration of the CTS timers is called the CTS-response window.Ideally, other candidate nodes can hear the CTS(by virtue of lying inside the sextant)and cancel their timers before the end of the window.Therefore,in IGF,a single node with the shortest CTS response timer responds to the ORTS.11IGF deals with network voids by shifting the forwardingSince IGF keeps no routing state information,it provides fault tolerance and is robust under topology changes.It also eliminates expensive communication for routing and neigh-bor information maintenance,and the associated routing ing the concept of lazy binding,the IGF pro-tocol defers next-hop selection until the packet forwarding operation actually happens at a sending zy binding dramatically reduces the chance that packets are forwarded to a node that fails,moves out of range,or transits to a sleep state,and also enables the use of recently awakened or newly arriving nodes.To avoid neighbor tables and do lazy binding,IGF must use an RTS/CTS handshake.This overhead is well paid back in performance,however,as shown in the experimental results.Compared with other established protocols for sensor and ad-hoc networks(such as GPSR[14],DSR[11],and LAR [16]),IGF achieves up to a ten-fold increase in delivery ratio and significantly reduces both end-to-end delay and control overhead.It is therefore a good protocol to serve as a foun-dation for secure routing.IGF has no routing tables,so it naturally confines the attacker’s impact to the neighborhood and prevents attacks that spoof,alter,or replace routing information.This is a significant advantage over link-state and distance vector routing protocols,which must carefully manage updates and route requests to avoid contamination by attackers. Unfortunately,a single attacker can completely disrupt routing for all of its neighbors.For example,the attacker arranges for itself to be chosen as the next-hop relay simply by sending an immediate CTS message upon receiving an ORTS.When the attacker gets the DATA,it replies with an ACK,but drops the DATA packet.The packet delivery ratio becomes zero—a simple attack,but devastating in the local neighborhood.We designed SIGF to secure routing in the local neigh-borhood while preserving the performance and attack con-tainment properties of IGF.3.ASSUMPTIONS AND ATTACKSRouting is an essential service for enabling communication in sensor networks,and is therefore potentially the target of many different attacks.First,we identify our assumptions about the system.We review the general classes of attacks on sensor network routing,then focus on attack mechanisms specific to our protocol in the next section.3.1System AssumptionsWe assume that radio links are insecure,i.e.,attackers may eavesdrop on radio transmissions,inject messages,and record and later replay messages.If an attacker is able to interact with the routing protocol,it can also drop messages for which it is responsible.Attackers possess hardware ca-pabilities similar to that of legitimate nodes,and wireless transmissions use the same power levels.Network nodes move only infrequently or slowly once de-ployed,and know their own locations.They may addition-ally know that of their neighbors(in SIGF-1and SIGF-2). Nodes know the location of important resources,like base stations,and use it for geographic routing.sextant to the side and retrying[1].SIGF inherits this mech-anism,which we do not discuss further in this paper.We do not require time synchronization among nodes. For SIGF-0and SIGF-1,no shared keys are required be-tween nodes in the network.SIGF-2assumes the presence of pairwise-shared keys in the neighborhood,which may be fulfilled by many different key distribution schemes in the literature[4,2,27].Nodes trust their own clocks,measure-ments,and storage.3.2Routing AttacksKarlof and Wagner[13]and others[24,20]have systemat-ically studied attacks on routing protocols.We summarize these attacks below,noting whether they are applicable to IGF(and therefore to SIGF).Then we discuss those attacks which are not obviously thwarted in greater detail.1.Routing state corruption.By spoofing,altering,or re-playing routing information,attackers are able to cre-ate routing loops,attract or redirect network traffic,increase end-to-end delay,etc.IGF keeps no informa-tion,and SIGF keeps only locally generated informa-tion.2.Wormholes.In this attack,an adversary tunnels mes-sages received in one part of the network over a lowlatency link and replays them elsewhere.Since IGFchooses the next-hop dynamically,a wormhole doesnot cause disruption when it ceases to operate.3.HELLOfloods.An attacker convinces nodes in thenetwork that the attacker is a neighbor by broadcast-ing HELLO messages with high energy.As with thewormhole attack,dynamic routing in IGF prevents dis-ruption by a HELLOflood.4.Black holes.In a black hole attack,an adversary orcompromised node lures nearly all the traffic from aparticular area through itself,where the messages aredropped.We further discuss this attack below.5.Selective forwarding.Attackers selectively forward pack-ets instead of faithfully forwarding all received packetsor completely dropping all packets.At one end of thespectrum,messages are rarely dropped.At the otherend is a black hole attack.We group this attack withthe black hole attack since its mechanism is the sameand consider its impact on IGF.6.Sybil attack.In the Sybil attack,a malicious nodebehaves as if it were a larger number of nodes by im-personating other nodes or simply by claiming falseidentities.We further discuss this attack below.7.Denial of Service.Most attacks result in a denial ofservice of some sort,but this moniker is usually re-served for attacks that waste resources or disrupt ser-vice in a way that far exceeds the effort required ofan attacker.Message amplification and jamming aregeneral examples.We consider specific mechanisms formounting this attack on IGF below.In an insider attack,a compromised node uses any means available to legitimate nodes to disrupt the protocol or per-form a specific attack listed above.All state,including keys possessed by the node,may be used by the attacker.Since IGF keeps no routing tables,it prevents a priori attacks such as state corruption,wormholes,and HELLO floods.Further,the impact of all attacks is limited to the local area,since routing is fully distributed and independent from hop to hop.IGF and SIGF do not trust neighboring nodes to behave correctly,so they are resistant to attacks from outsiders and insiders alike.The main attacks available to an adversary are to create a black hole,pose as multiple identities(Sybil attack),or dis-rupt the routing protocol through denial of service attacks. We describe specific mechanisms for performing these at-tacks on IGF in the next sections.When we describe and evaluate SIGF in Sections4–5,we focus particularly on its resilience to these attacks.3.2.1Black Hole/Selective Forwarding Attack Within the local neighborhood,the easiest way for an at-tacker to create a black hole is to manage to always be se-lected by neighbors as the next hop,whether this is proper, or not.In the CTS rushing attack,an attacker exploits the coop-erative nature of IGF’s next-hop selection.When an Open RTS(ORTS)message is received,neighbors set timers pro-portional to their desirability as forwarding candidates.The attacker disregards this mechanism and always replies im-mediately with a CTS,volunteering to forward the packet. Once selected as the next relay,the attacker may modify, totally drop(black hole attack)or selectively forward the DATA message.This attack is very effective against IGF, easy to perform,and requires moderate power consumption, as it is completely reactive.Figure3:CTS Rushing Attack by A against S. Figure3shows how this attack works.When attacker A overhears an ORTS message,it sends a CTS message, whether it is in the forwarding area or not.Other nodes overhear the CTS from the attacker and abort the protocol. Unsuspecting ORTS senders in the neighborhood of the at-tacker always choose to send their messages into the black hole created by A.3.2.2Sybil AttackIn a Sybil attack,an attacker illegitimately claims to be multiple nodes by sending messages with different identi-ties and locations.Its additional identities are virtual Sybil nodes.Without cryptographic authentication,a receiver of a message cannot determine the true identity of its origina-tor,and does not know how many of the claimed identities are truly unique.Our foundational routing protocol IGF is vulnerable to Sybil attack because it does not maintain any neighborhood state with which to validate the identities. Identity and Location.A Sybil node can either fabricatea new identity,or steal an identity from a legitimate node[20].In our experiments,an attacker creates several Sybil nodes surrounding its true location and assigns each either a random orfixed location.Communication.We assume Sybil nodes can communi-cate directly with legitimate nodes in the following way.When a legitimate node sends a message to a Sybil node, the attacker overhears the message.Likewise,messages sent fromSybil nodes are actually from the attacker,but with the proper identity enclosed.Figure4:Node A performs a Sybil attack against S. Communication with a Sybil node is illustrated in Fig-ure4.After receiving an ORTS message,the attacker sends a CTS addressed from one of the Sybil nodes.Once the Sybil node is selected as the next relay,the attacker overhears and acknowledges the DATA.It can then drop,tamper,or forward the DATA in a black hole or selective forwarding attack.3.2.3Denial of Service AttackThe goal of this type of attack is to deny service to the nearby nodes in a manner that is less intrusive and costly than jamming.The attacker partially executes the IGF pro-tocol to cause nearby nodes to waste energy transmitting messages,waste time waiting on completion of the protocol, or prematurely abort the protocol.We describe two spe-cific attacks which cause denial of service by recording and replaying legitimate messages.In an ORTS replay attack,a node captures an overheard ORTS message and subsequently replays it repeatedly.Each time it is replayed,neighbors of the attacker respond with CTS messages and wait for data exchange.The wireless channel cannot be used in this local neighborhood for legit-imate traffic during the CTS collection window.In a CTS replay attack,the old CTS message falsely causes other eligible receivers in IGF to abort the proto-col(cancel their CTS response timers).The ORTS sender selects an unsuspecting or absent node(the originator of the captured CTS)as the next hop.The sender transmits the DATA,wasting energy and channel capacity,and then must retry or drop the DATA message when no acknowledgement is forthcoming.A captured ACK could be replayed by the attacker as well,causing the sender to believe the transmis-sion was successful.This attack is less costly to the attacker than an ORTS replay because it is reactive:the protocol is only disrupted when a neighbor actually tries to send a message.4.SIGF:SECURE IGFWe propose a novel secure routing protocol family,called Secure IGF(SIGF)which keeps the advantages of dynamic binding in IGF,yet provides effective defenses against the attacks discussed above.The protocols provide tradeoffs between security and state maintenance,and configurability that can be adapted at runtime.1if(include destination)2ORTS← S,S location,D,D location,FwdArea3else4ORTS← S6broadcast ORTS message8/∗Every neighbor N receives ORTS message,and if in FwdArea,sets CTS response timerproportional to next−hop desirability,sendingCTS= N,N location upon expiry.∗/10CTS candidates←∅11while(collection window open)12if(CTS received AND N location∈FwdArea)13add N to CTS candidates15choose C∈CTS candidates for next hop16send DATA to CAlgorithm1:SIGF-0next-hop selection for message from current node S to ultimate destination D.The configurability of the SIGF protocol family gives a significant advantage over other more static routing proto-cols.Some provide no security,while others provide strong guarantees—but at the cost of more assumptions,computa-tion,and communication.These higher costs must be borne even when no attacks are occurring.SIGF protocols can be selected and configured for the security requirements of a particular deployment.Network planners can select among three classes of secu-rity solutions,grouped by the amount of state they keep:no state at all(SIGF-0),locally generated state(SIGF-1),and pairwise-shared state within the neighborhood(SIGF-2). This choice is currently static,but in the future it will be dynamically adjustable.SIGF-0is a stateless protocol that maintains no routing information,but provides only probabilistic defenses against attack.SIGF-1keeps limited information learned from in-teractions with neighbors.SIGF-2uses keys and sequence numbers shared among neighbors to provide cryptographic guarantees in routing.Each protocol is a subset of the next. That is,SIGF-1uses mechanisms from SIGF-0,and likewise SIGF-2uses some from SIGF-1.The main weakness of a last-instant dynamic binding ap-proach,as used by IGF,is in the selection of the next-hop relay.Each of these protocols uses different means to pre-vent or minimize the probability of selecting an attacker as the relay,while achieving high packet delivery rates with low delay and overhead.In the following sections we present each protocol in turn.4.1SIGF-0:Stateless Secure IGFSIGF-0is the basis of the other protocols in the Secure IGF family.Without keeping forwarding history or infor-mation about neighbors,it chooses the next-hop relay non-deterministically and dynamically.This lessens,but does not eliminate,the chance ofselecting an attacker in the neighborhood.The logic for sending a message from source S to des-tination D is shown in Algorithm1.The ORTS message (as described in Section2)is constructed in Lines1–4and broadcast to the one-hop neighbors in Line6.Neighbors of S that receive the ORTS and which are in the forwarding area start CTS response timers.Upon timer expiry,a node sends a CTS response that includes its own location.In Lines10–13,node S collects CTS responses until the collec-tion window closes.Then a candidate C is chosen among the responders and the DATA is relayed to node C.The algorithm is configurable in four dimensions,each of which is described here.Each is annotated with the list of options and the line number in Algorithm1where it appears.1.Forwarding Area∈{60◦sextant,closer,wholeneighborhood}Line2In the foundational routing protocol IGF,a60◦sex-tant toward the destination is always used as the for-warding area.This gives some assurance that CTSresponders can overhear each other and cancel theirtimers.In the presence of multi-ple neighboring adversaries,however,this sextant maynot provide enough responsesfrom which to select.Low-density deployments allowattackers tofill the CTScandidate set to the exclu-sion of legitimate forwarders.SIGF-0allows the use oflarger forwarding areas,since for a given number ofattackers this increases the probability of selecting alegitimate node.In addition to the60◦sextant,anynode that is closer to the destination than the sendermay respond,or all neighbors may respond.Thisdoes not increase the number of attackers included,since they already may disregard the forwarding areawhen attacking.Performance is affected both by allowing messages to take longer paths,and by lengthening the collection window to accomodate greater CTS candidates.How-ever,this is offset by the ease with which multiple attackers may capture forwarding when the narrower sextant is used.Allowing more neighbors to be con-sidered in the forwarding area does not automatically cause worse performance when there are no attacks, since correct nodes still respond according to their de-sirability for forwarding(as described in Section2).2.Collection Window∈{one responder,fixed multi-ple,dynamically lengthened}Line11 SIGF-0collects one or more CTS responses before choosing the next-hop relay among them.IGF closes the collection window immediately upon receiving the first CTS,but this is vulnerable to the CTS rushing at-tack presented earlier.The attacker disregards the cor-rect response delay and respondsfirst,creating a black hole in the neighborhood.Still,this option is available in SIGF-0since it provides best performance(lowest delay and overhead)when no attacker is present.By allowing a longer collection window,SIGF-0col-lects more CTS messages before selecting a relay.The ORTS sender waits afixed amount of time,storingCTS responses.One is chosen according to the cri-teria given in the next part.Afixed-length window gives predictability and constant cost,and allows CTS response timers to be scaled a priori to avoid unneces-sary contention during the window.Aflag is included in the ORTS to prevent CTS responders from aborting the protocol when another CTS is overheard.If not enough CTS responses are received,the window may optionally be extended dynamically.At a greater cost in delay,this allows the ORTS sender to collect enough responses to give better assurance that an at-tacker is not chosen.3.Forwarding Candidate Choice∈{first,by priority,random,multiple}Line15 Given a set of forwarding candidates collected dur-ing the window(CTS candidates in Algorithm1),this parameter determines how one is chosen to be the next-hop relay.IGF always chooses thefirst respon-der,which is vulnerable to the CTS rushing attack.We allow this option since it is compatible with IGF and because it is most efficient when no attackers are present.Selecting by priority means choosing the node that makes the most progress toward the ultimate desti-nation of the message.For other protocols,this is extended to include other criteria.This option has the advantage of minimizing path dilation when no attacker is present.Random selection is robust against a wide variety of attackers,since it does not give credence to the lo-cation information contained in the CTS.The larger the pool of forwarding candidates,the less likely that a neighboring attacker performing a CTS rushing attack or masquerading as a legimitate node is chosen.Per-formance suffers,however,since progress toward the destination is pared with the impact ofa black hole attack,this is most likely an acceptabletradeoff.The originator of a message may choose more than one candidate to relay messages along multiple paths.This redundancy lessens the impact of attackers met along the way,though if afixed number of attackers is present,the higher cost may be justified by its effec-tiveness.4.Omit Location∈{yes,no}Line1Even when selecting among multiple responses in the collection window,an attacker can manipulate a choice if it is made by priority.Since the ORTS includes the ultimate destination,an attacker can fabricate an optimal location for inclusion in its CTS to maximize its chances of being selected.An option to omit the source and destination loca-tions in the ORTS message mitigates this threat.In this case,the neighbors of S cannot determine whether they are in the forwarding area,nor how close they lie to the line SD.Therefore,all neighbors respond by setting timers proportional to their remaining energy only.The ORTS sender then chooses the relay accord-ing to the previous configuration setting.When the DATA message is relayed to the selected node,it must contain the destination’s location to en-able subsequent routing.Omitting the destination does not eliminate the threat of a black hole attack,since an adversary may infer the ultimate destination from a stream of messages using traffic analysis.We do not consider that attack in this paper.Note that during protocol operation,both a sender and its neighbors(forwarding candidates)retain some state.It is transient,however,since it need not be retained after the message is relayed.For this reason we classify SIGF-0as stateless.The configuration options presented give SIGF-0robust-ness against a black hole caused by CTS rushing.They are similar enough to IGF to allow a smooth,runtime transition between option settings,according to the current attack sit-uation.We are exploring the dynamic transition between settings,and between protocols in future work.4.2SIGF-1:Local-State Secure IGFSIGF-1builds on the capabilities and operation of SIGF-0, while aiming to further reduce the chances of selecting an attacker as the next-hop relay.By keeping some limited information about its current state and statistics of neighbor performance,a node can also defend against Sybil attacks. This state is summarized by a per-neighbor reputation value that influences the choice of forwarding candidates.Since the state kept is not shared with neighbors,there is no overhead associated with initialization,synchronization, or repair.By limiting the information to that which can be verified locally,the protocol avoids state corruption attacks. Further,neighborhood dynamics due to mobility,failure,or transient communication are still considered.We classify state kept in SIGF-1in three categories:data about the local node,statistics about neighboring nodes, and values derived from both together.Each is presented below.For the local node,we maintain T,the total number of messages sent by the node to all neighbors.It is used to calculate derived values for each neighbor.Nodes also have a small buffer B in which recently relayed messages are stored. For each neighbor N among those discovered dynamically (i.e.,neighbor tables are not exchanged),we keep the following:1.N sent=number of messages sent to neighbor N forforwarding.It is increased by one each time N is se-lected as the next-hop relay.2.N forward=number of messages forwarded by neighborN on this node’s behalf.This is counted by overhear-ing a message on its retransmission by node N to a downstream node,albeit imperfectly due to collisions and collusion.3.N location=last claimed location of node N in its CTSmessage.4.N delay=average delay between relaying a message tonode N and overhearing the subsequent relay of the same.After transmitting a message to a neighboring node,a copy of the message is stored in the message buffer B,along with a timestamp.If the message is overheard on its relay to a downstream node,the difference between the recorded and。