chap5 transport layer-5

OSI七层模型各层分别有哪些协议及它们的功能在互联网中实际使用的是TCP/IP参考模型。

实际存在的协议主要包括在：物理层、数据链路层、网络层、传输层和应用层。

各协议也分别对应这5个层次而已。

要找出7个层次所对应的各协议，恐怕会话层和表示层的协议难找到啊。

应用层·DHCP(动态主机分配协议)· DNS (域名解析）· FTP（File Transfer Protocol）文件传输协议· Gopher （英文原义：The Internet Gopher Protocol 中文释义：（RFC-1436）网际Gopher协议）· HTTP （Hypertext Transfer Protocol）超文本传输协议· IMAP4 (Internet Message Access Protocol 4) 即 Internet信息访问协议的第4版本· IRC （Internet Relay Chat ）网络聊天协议· NNTP （Network News Transport Protocol）RFC-977）网络新闻传输协议· XMPP 可扩展消息处理现场协议· POP3 (Post Office Protocol 3)即邮局协议的第3个版本· SIP 信令控制协议· SMTP （Simple Mail Transfer Protocol）即简单邮件传输协议· SNMP (Simple Network Management Protocol,简单网络管理协议)· SSH （Secure Shell）安全外壳协议· TELNET 远程登录协议· RPC （Remote Procedure Call Protocol）（RFC-1831）远程过程调用协议· RTCP （RTP Control Protocol）RTP 控制协议· RTSP （Real Time Streaming Protocol）实时流传输协议· TLS （Transport Layer Security Protocol）安全传输层协议· SDP( Session Description Protocol）会话描述协议· SOAP （Simple Object Access Protocol）简单对象访问协议· GTP 通用数据传输平台· STUN （Simple Traversal of UDP over NATs，NAT 的UDP简单穿越）是一种网络协议· NTP （Network Time Protocol）网络校时协议传输层·TCP（Transmission Control Protocol）传输控制协议· UDP (User Datagram Protocol）用户数据报协议· DCCP （Datagram Congestion Control Protocol）数据报拥塞控制协议· SCTP（STREAM CONTROL TRANSMISSION PROTOCOL）流控制传输协议· RTP(Real-time Transport Protocol或简写RTP）实时传送协议· RSVP （Resource ReSer Vation Protocol）资源预留协议· PPTP ( Point to Point Tunneling Protocol）点对点隧道协议网络层IP(IPv4 · IPv6) Internet Protocol（网络之间互连的协议）ARP : Address Resolution Protocol即地址解析协议，实现通过IP地址得知其物理地址。

OSE/APP开放系统环境应⽤可移植框架ODA开放⽂件体系结构ODL开放⽂件语⾔ODIF开放⽂件交换格式GKS图形核⼼系统PHIGS编程的层次交换式图形系统GOSIP政府开放系统互联框架EEI:extenal environment interface扩展环境接⼝CGI:common gateway interface公⽤关接⼝Internal web内部环球mail lists邮件列表newgroups新闻组chat闲谈IRC:internet relay chat聊天VRML:virtual reality modeling language 语⾔workflow⼯作流groupware群件video conferencing视频会议ADSL:asymmetric digital subscriber line 不对称数字⽤户DBS:direct broadcast satellite直播⼴播卫星VPN:virtual private networks虚拟专ISPInternet服务提供商SSL:secure sockets layer安全套接层PCT:private communication technology 专通信技术STLP:secure transport layer protocol安全传送层SET:secure electrionic transaction安全电⼦传送proxy server代理服务器POP3:post office protocolPOP3邮局IMAP4:internet message protocol4邮件协议WYSIWYG:what you see is what you get 所见即所得NDIS络设备接⼝标准NETBT:NETBIOS over TCP/IP协议IIS:Internet Information ServerMicrosoftbinding绑定PDC主域控制器BDC备份域控制器DCOM分布组件对象模式WINS:windows internet name service服务器RR:resource record资源记录CSNW:client service for netware客服network address translation络地址转换loopback回送dotted quad notation点分形式packet分组forward向前account帐号compatibility兼容性assume担任dummy哑终端western digitial/SMC cards卡portable便携BIND:berkeley internet name domain service 不知道resolver library不知道spoofing欺骗multi homed多宿主RR:resource record.资源记录Lynx Mosaic Netscape Hotjava浏览器URL:uniform resource locator统⼀资源定位webmaster主HTML hypertext markup language超⽂本语⾔anonymous/ftp匿名FTP/companyUNIX下存放公司本⾝的信息/pubUNIX下的公⽤软件/in-comingUNIX匿名FTP⽤户上载⽂件⽬录/usr /bin /etcFTP占⽤的⽬录mirror sites⽂件服务器镜像系统WAIS:wide area information search查询description描述catalog⽬录、⼿册inverted颠倒internetworked enterprise互联上的企业interenterprise computing企业间的计算CSCW:computer supported cooperative work 计算机⽀持协同⼯作interactive/communication交互通信coordination协调collaboration协作cooperation协同co-located同地协作remote远程协作message systems信报系统platform平台collabration/cooperation协调和协作⽅式commerce主题content/message内容profit利润BtoC(B2C):business to consumer企业对消费者PtoP(C2C):person to person个⼈对个⼈BtoG:business to government企业对政府virtual store虚拟商店virtual electronic mall虚拟电⼦商场virtual electronic commerce city虚拟电⼦商城distance education/learning远程教育network-based distance education远程络教育tele-access远程访问tele-mentoring远程辅导tele-sharing远程共享virtual publishing虚拟出版virtual classroom虚拟教室awareness互相感知CSCL:computer supported cooperative learning 远程合作educational groupware system教育组件系统telemedicine远程医疗。

⽹络通信原理主要内容:1.互联⽹协议2.osi 七层协议3.tcp/ip五层模型讲解4.socket1.互联⽹的本质就是⼀系列的⽹络协议连接两台计算机之间的internet实际上就是⼀系列统⼀的标准,这些标准称之为互联⽹协议,互联⽹的本质就是⼀系列的协议,总称为‘互联⽹协议’（Internet Protocol Suite)。

互联⽹协议的功能：定义计算机如何接⼊internet，以及接⼊internet的计算机通信的标准2.osi 七层协议⼀些协议:各层的功能简述：【1】物理层：主要定义物理设备标准，如⽹线的接⼝类型、光纤的接⼝类型、各种传输介质的传输速率等。

它的主要作⽤是传输⽐特流（就是由1、0转化为电流强弱来进⾏传输,到达⽬的地后在转化为1、0，也就是我们常说的数模转换与模数转换 【2】数据链路层：定义了如何让格式化数据以进⾏传输，以及如何让控制对物理介质的访问，这⼀层通常还提供错误检测和纠正，以确保数据的可靠传输。

【3】⽹络层：在位于不同地理位置的⽹络中的两个主机系统之间提供连接和路径选择，Internet的发展使得从世界各站点访问信息的⽤户数⼤⼤增加，⽽⽹络层正是管理这种连接的层。

【4】传输层：定义了⼀些传输数据的协议和端⼝号（WWW端⼝80等），如：TCP（传输控制协议，传输效率低，可靠性强，⽤于传输可靠性要求⾼，数据量⼤的数据），UDP（⽤户数据报协议，与TCP特性恰恰相反，⽤于传输可靠性要求不⾼ 【5】会话层：通过传输层（端⼝号：传输端⼝与接收端⼝）建⽴数据传输的通路，主要在你的系统之间发起会话或者接受会话请求（设备之间需要互相认识可以是IP也可以是MAC或者是主机名）。

【6】表⽰层：可确保⼀个系统的应⽤层所发送的信息可以被另⼀个系统的应⽤层读取。

例如，PC程序与另⼀台计算机进⾏通信，其中⼀台计算机使⽤扩展⼆⼀⼗进制交换码（EBCDIC），⽽另⼀台则使⽤美国信息交换标准码（ASCII）来表⽰相 【7】应⽤层：是最靠近⽤户的OSI层，这⼀层为⽤户的应⽤程序（例如电⼦邮件、⽂件传输和终端仿真）提供⽹络服务。

3GPP TS 36.331 V13.2.0 (2016-06)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specification(Release 13)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.KeywordsUMTS, radio3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationBluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its membersContentsForeword (18)1Scope (19)2References (19)3Definitions, symbols and abbreviations (22)3.1Definitions (22)3.2Abbreviations (24)4General (27)4.1Introduction (27)4.2Architecture (28)4.2.1UE states and state transitions including inter RAT (28)4.2.2Signalling radio bearers (29)4.3Services (30)4.3.1Services provided to upper layers (30)4.3.2Services expected from lower layers (30)4.4Functions (30)5Procedures (32)5.1General (32)5.1.1Introduction (32)5.1.2General requirements (32)5.2System information (33)5.2.1Introduction (33)5.2.1.1General (33)5.2.1.2Scheduling (34)5.2.1.2a Scheduling for NB-IoT (34)5.2.1.3System information validity and notification of changes (35)5.2.1.4Indication of ETWS notification (36)5.2.1.5Indication of CMAS notification (37)5.2.1.6Notification of EAB parameters change (37)5.2.1.7Access Barring parameters change in NB-IoT (37)5.2.2System information acquisition (38)5.2.2.1General (38)5.2.2.2Initiation (38)5.2.2.3System information required by the UE (38)5.2.2.4System information acquisition by the UE (39)5.2.2.5Essential system information missing (42)5.2.2.6Actions upon reception of the MasterInformationBlock message (42)5.2.2.7Actions upon reception of the SystemInformationBlockType1 message (42)5.2.2.8Actions upon reception of SystemInformation messages (44)5.2.2.9Actions upon reception of SystemInformationBlockType2 (44)5.2.2.10Actions upon reception of SystemInformationBlockType3 (45)5.2.2.11Actions upon reception of SystemInformationBlockType4 (45)5.2.2.12Actions upon reception of SystemInformationBlockType5 (45)5.2.2.13Actions upon reception of SystemInformationBlockType6 (45)5.2.2.14Actions upon reception of SystemInformationBlockType7 (45)5.2.2.15Actions upon reception of SystemInformationBlockType8 (45)5.2.2.16Actions upon reception of SystemInformationBlockType9 (46)5.2.2.17Actions upon reception of SystemInformationBlockType10 (46)5.2.2.18Actions upon reception of SystemInformationBlockType11 (46)5.2.2.19Actions upon reception of SystemInformationBlockType12 (47)5.2.2.20Actions upon reception of SystemInformationBlockType13 (48)5.2.2.21Actions upon reception of SystemInformationBlockType14 (48)5.2.2.22Actions upon reception of SystemInformationBlockType15 (48)5.2.2.23Actions upon reception of SystemInformationBlockType16 (48)5.2.2.24Actions upon reception of SystemInformationBlockType17 (48)5.2.2.25Actions upon reception of SystemInformationBlockType18 (48)5.2.2.26Actions upon reception of SystemInformationBlockType19 (49)5.2.3Acquisition of an SI message (49)5.2.3a Acquisition of an SI message by BL UE or UE in CE or a NB-IoT UE (50)5.3Connection control (50)5.3.1Introduction (50)5.3.1.1RRC connection control (50)5.3.1.2Security (52)5.3.1.2a RN security (53)5.3.1.3Connected mode mobility (53)5.3.1.4Connection control in NB-IoT (54)5.3.2Paging (55)5.3.2.1General (55)5.3.2.2Initiation (55)5.3.2.3Reception of the Paging message by the UE (55)5.3.3RRC connection establishment (56)5.3.3.1General (56)5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/ discovery (58)5.3.3.2Initiation (59)5.3.3.3Actions related to transmission of RRCConnectionRequest message (63)5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message (64)5.3.3.4Reception of the RRCConnectionSetup by the UE (64)5.3.3.4a Reception of the RRCConnectionResume by the UE (66)5.3.3.5Cell re-selection while T300, T302, T303, T305, T306, or T308 is running (68)5.3.3.6T300 expiry (68)5.3.3.7T302, T303, T305, T306, or T308 expiry or stop (69)5.3.3.8Reception of the RRCConnectionReject by the UE (70)5.3.3.9Abortion of RRC connection establishment (71)5.3.3.10Handling of SSAC related parameters (71)5.3.3.11Access barring check (72)5.3.3.12EAB check (73)5.3.3.13Access barring check for ACDC (73)5.3.3.14Access Barring check for NB-IoT (74)5.3.4Initial security activation (75)5.3.4.1General (75)5.3.4.2Initiation (76)5.3.4.3Reception of the SecurityModeCommand by the UE (76)5.3.5RRC connection reconfiguration (77)5.3.5.1General (77)5.3.5.2Initiation (77)5.3.5.3Reception of an RRCConnectionReconfiguration not including the mobilityControlInfo by theUE (77)5.3.5.4Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE(handover) (79)5.3.5.5Reconfiguration failure (83)5.3.5.6T304 expiry (handover failure) (83)5.3.5.7Void (84)5.3.5.7a T307 expiry (SCG change failure) (84)5.3.5.8Radio Configuration involving full configuration option (84)5.3.6Counter check (86)5.3.6.1General (86)5.3.6.2Initiation (86)5.3.6.3Reception of the CounterCheck message by the UE (86)5.3.7RRC connection re-establishment (87)5.3.7.1General (87)5.3.7.2Initiation (87)5.3.7.3Actions following cell selection while T311 is running (88)5.3.7.4Actions related to transmission of RRCConnectionReestablishmentRequest message (89)5.3.7.5Reception of the RRCConnectionReestablishment by the UE (89)5.3.7.6T311 expiry (91)5.3.7.7T301 expiry or selected cell no longer suitable (91)5.3.7.8Reception of RRCConnectionReestablishmentReject by the UE (91)5.3.8RRC connection release (92)5.3.8.1General (92)5.3.8.2Initiation (92)5.3.8.3Reception of the RRCConnectionRelease by the UE (92)5.3.8.4T320 expiry (93)5.3.9RRC connection release requested by upper layers (93)5.3.9.1General (93)5.3.9.2Initiation (93)5.3.10Radio resource configuration (93)5.3.10.0General (93)5.3.10.1SRB addition/ modification (94)5.3.10.2DRB release (95)5.3.10.3DRB addition/ modification (95)5.3.10.3a1DC specific DRB addition or reconfiguration (96)5.3.10.3a2LWA specific DRB addition or reconfiguration (98)5.3.10.3a3LWIP specific DRB addition or reconfiguration (98)5.3.10.3a SCell release (99)5.3.10.3b SCell addition/ modification (99)5.3.10.3c PSCell addition or modification (99)5.3.10.4MAC main reconfiguration (99)5.3.10.5Semi-persistent scheduling reconfiguration (100)5.3.10.6Physical channel reconfiguration (100)5.3.10.7Radio Link Failure Timers and Constants reconfiguration (101)5.3.10.8Time domain measurement resource restriction for serving cell (101)5.3.10.9Other configuration (102)5.3.10.10SCG reconfiguration (103)5.3.10.11SCG dedicated resource configuration (104)5.3.10.12Reconfiguration SCG or split DRB by drb-ToAddModList (105)5.3.10.13Neighbour cell information reconfiguration (105)5.3.10.14Void (105)5.3.10.15Sidelink dedicated configuration (105)5.3.10.16T370 expiry (106)5.3.11Radio link failure related actions (107)5.3.11.1Detection of physical layer problems in RRC_CONNECTED (107)5.3.11.2Recovery of physical layer problems (107)5.3.11.3Detection of radio link failure (107)5.3.12UE actions upon leaving RRC_CONNECTED (109)5.3.13UE actions upon PUCCH/ SRS release request (110)5.3.14Proximity indication (110)5.3.14.1General (110)5.3.14.2Initiation (111)5.3.14.3Actions related to transmission of ProximityIndication message (111)5.3.15Void (111)5.4Inter-RAT mobility (111)5.4.1Introduction (111)5.4.2Handover to E-UTRA (112)5.4.2.1General (112)5.4.2.2Initiation (112)5.4.2.3Reception of the RRCConnectionReconfiguration by the UE (112)5.4.2.4Reconfiguration failure (114)5.4.2.5T304 expiry (handover to E-UTRA failure) (114)5.4.3Mobility from E-UTRA (114)5.4.3.1General (114)5.4.3.2Initiation (115)5.4.3.3Reception of the MobilityFromEUTRACommand by the UE (115)5.4.3.4Successful completion of the mobility from E-UTRA (116)5.4.3.5Mobility from E-UTRA failure (117)5.4.4Handover from E-UTRA preparation request (CDMA2000) (117)5.4.4.1General (117)5.4.4.2Initiation (118)5.4.4.3Reception of the HandoverFromEUTRAPreparationRequest by the UE (118)5.4.5UL handover preparation transfer (CDMA2000) (118)5.4.5.1General (118)5.4.5.2Initiation (118)5.4.5.3Actions related to transmission of the ULHandoverPreparationTransfer message (119)5.4.5.4Failure to deliver the ULHandoverPreparationTransfer message (119)5.4.6Inter-RAT cell change order to E-UTRAN (119)5.4.6.1General (119)5.4.6.2Initiation (119)5.4.6.3UE fails to complete an inter-RAT cell change order (119)5.5Measurements (120)5.5.1Introduction (120)5.5.2Measurement configuration (121)5.5.2.1General (121)5.5.2.2Measurement identity removal (122)5.5.2.2a Measurement identity autonomous removal (122)5.5.2.3Measurement identity addition/ modification (123)5.5.2.4Measurement object removal (124)5.5.2.5Measurement object addition/ modification (124)5.5.2.6Reporting configuration removal (126)5.5.2.7Reporting configuration addition/ modification (127)5.5.2.8Quantity configuration (127)5.5.2.9Measurement gap configuration (127)5.5.2.10Discovery signals measurement timing configuration (128)5.5.2.11RSSI measurement timing configuration (128)5.5.3Performing measurements (128)5.5.3.1General (128)5.5.3.2Layer 3 filtering (131)5.5.4Measurement report triggering (131)5.5.4.1General (131)5.5.4.2Event A1 (Serving becomes better than threshold) (135)5.5.4.3Event A2 (Serving becomes worse than threshold) (136)5.5.4.4Event A3 (Neighbour becomes offset better than PCell/ PSCell) (136)5.5.4.5Event A4 (Neighbour becomes better than threshold) (137)5.5.4.6Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better thanthreshold2) (138)5.5.4.6a Event A6 (Neighbour becomes offset better than SCell) (139)5.5.4.7Event B1 (Inter RAT neighbour becomes better than threshold) (139)5.5.4.8Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better thanthreshold2) (140)5.5.4.9Event C1 (CSI-RS resource becomes better than threshold) (141)5.5.4.10Event C2 (CSI-RS resource becomes offset better than reference CSI-RS resource) (141)5.5.4.11Event W1 (WLAN becomes better than a threshold) (142)5.5.4.12Event W2 (All WLAN inside WLAN mobility set becomes worse than threshold1 and a WLANoutside WLAN mobility set becomes better than threshold2) (142)5.5.4.13Event W3 (All WLAN inside WLAN mobility set becomes worse than a threshold) (143)5.5.5Measurement reporting (144)5.5.6Measurement related actions (148)5.5.6.1Actions upon handover and re-establishment (148)5.5.6.2Speed dependant scaling of measurement related parameters (149)5.5.7Inter-frequency RSTD measurement indication (149)5.5.7.1General (149)5.5.7.2Initiation (150)5.5.7.3Actions related to transmission of InterFreqRSTDMeasurementIndication message (150)5.6Other (150)5.6.0General (150)5.6.1DL information transfer (151)5.6.1.1General (151)5.6.1.2Initiation (151)5.6.1.3Reception of the DLInformationTransfer by the UE (151)5.6.2UL information transfer (151)5.6.2.1General (151)5.6.2.2Initiation (151)5.6.2.3Actions related to transmission of ULInformationTransfer message (152)5.6.2.4Failure to deliver ULInformationTransfer message (152)5.6.3UE capability transfer (152)5.6.3.1General (152)5.6.3.2Initiation (153)5.6.3.3Reception of the UECapabilityEnquiry by the UE (153)5.6.4CSFB to 1x Parameter transfer (157)5.6.4.1General (157)5.6.4.2Initiation (157)5.6.4.3Actions related to transmission of CSFBParametersRequestCDMA2000 message (157)5.6.4.4Reception of the CSFBParametersResponseCDMA2000 message (157)5.6.5UE Information (158)5.6.5.1General (158)5.6.5.2Initiation (158)5.6.5.3Reception of the UEInformationRequest message (158)5.6.6 Logged Measurement Configuration (159)5.6.6.1General (159)5.6.6.2Initiation (160)5.6.6.3Reception of the LoggedMeasurementConfiguration by the UE (160)5.6.6.4T330 expiry (160)5.6.7 Release of Logged Measurement Configuration (160)5.6.7.1General (160)5.6.7.2Initiation (160)5.6.8 Measurements logging (161)5.6.8.1General (161)5.6.8.2Initiation (161)5.6.9In-device coexistence indication (163)5.6.9.1General (163)5.6.9.2Initiation (164)5.6.9.3Actions related to transmission of InDeviceCoexIndication message (164)5.6.10UE Assistance Information (165)5.6.10.1General (165)5.6.10.2Initiation (166)5.6.10.3Actions related to transmission of UEAssistanceInformation message (166)5.6.11 Mobility history information (166)5.6.11.1General (166)5.6.11.2Initiation (166)5.6.12RAN-assisted WLAN interworking (167)5.6.12.1General (167)5.6.12.2Dedicated WLAN offload configuration (167)5.6.12.3WLAN offload RAN evaluation (167)5.6.12.4T350 expiry or stop (167)5.6.12.5Cell selection/ re-selection while T350 is running (168)5.6.13SCG failure information (168)5.6.13.1General (168)5.6.13.2Initiation (168)5.6.13.3Actions related to transmission of SCGFailureInformation message (168)5.6.14LTE-WLAN Aggregation (169)5.6.14.1Introduction (169)5.6.14.2Reception of LWA configuration (169)5.6.14.3Release of LWA configuration (170)5.6.15WLAN connection management (170)5.6.15.1Introduction (170)5.6.15.2WLAN connection status reporting (170)5.6.15.2.1General (170)5.6.15.2.2Initiation (171)5.6.15.2.3Actions related to transmission of WLANConnectionStatusReport message (171)5.6.15.3T351 Expiry (WLAN connection attempt timeout) (171)5.6.15.4WLAN status monitoring (171)5.6.16RAN controlled LTE-WLAN interworking (172)5.6.16.1General (172)5.6.16.2WLAN traffic steering command (172)5.6.17LTE-WLAN aggregation with IPsec tunnel (173)5.6.17.1General (173)5.7Generic error handling (174)5.7.1General (174)5.7.2ASN.1 violation or encoding error (174)5.7.3Field set to a not comprehended value (174)5.7.4Mandatory field missing (174)5.7.5Not comprehended field (176)5.8MBMS (176)5.8.1Introduction (176)5.8.1.1General (176)5.8.1.2Scheduling (176)5.8.1.3MCCH information validity and notification of changes (176)5.8.2MCCH information acquisition (178)5.8.2.1General (178)5.8.2.2Initiation (178)5.8.2.3MCCH information acquisition by the UE (178)5.8.2.4Actions upon reception of the MBSFNAreaConfiguration message (178)5.8.2.5Actions upon reception of the MBMSCountingRequest message (179)5.8.3MBMS PTM radio bearer configuration (179)5.8.3.1General (179)5.8.3.2Initiation (179)5.8.3.3MRB establishment (179)5.8.3.4MRB release (179)5.8.4MBMS Counting Procedure (179)5.8.4.1General (179)5.8.4.2Initiation (180)5.8.4.3Reception of the MBMSCountingRequest message by the UE (180)5.8.5MBMS interest indication (181)5.8.5.1General (181)5.8.5.2Initiation (181)5.8.5.3Determine MBMS frequencies of interest (182)5.8.5.4Actions related to transmission of MBMSInterestIndication message (183)5.8a SC-PTM (183)5.8a.1Introduction (183)5.8a.1.1General (183)5.8a.1.2SC-MCCH scheduling (183)5.8a.1.3SC-MCCH information validity and notification of changes (183)5.8a.1.4Procedures (184)5.8a.2SC-MCCH information acquisition (184)5.8a.2.1General (184)5.8a.2.2Initiation (184)5.8a.2.3SC-MCCH information acquisition by the UE (184)5.8a.2.4Actions upon reception of the SCPTMConfiguration message (185)5.8a.3SC-PTM radio bearer configuration (185)5.8a.3.1General (185)5.8a.3.2Initiation (185)5.8a.3.3SC-MRB establishment (185)5.8a.3.4SC-MRB release (185)5.9RN procedures (186)5.9.1RN reconfiguration (186)5.9.1.1General (186)5.9.1.2Initiation (186)5.9.1.3Reception of the RNReconfiguration by the RN (186)5.10Sidelink (186)5.10.1Introduction (186)5.10.1a Conditions for sidelink communication operation (187)5.10.2Sidelink UE information (188)5.10.2.1General (188)5.10.2.2Initiation (189)5.10.2.3Actions related to transmission of SidelinkUEInformation message (193)5.10.3Sidelink communication monitoring (195)5.10.6Sidelink discovery announcement (198)5.10.6a Sidelink discovery announcement pool selection (201)5.10.6b Sidelink discovery announcement reference carrier selection (201)5.10.7Sidelink synchronisation information transmission (202)5.10.7.1General (202)5.10.7.2Initiation (203)5.10.7.3Transmission of SLSS (204)5.10.7.4Transmission of MasterInformationBlock-SL message (205)5.10.7.5Void (206)5.10.8Sidelink synchronisation reference (206)5.10.8.1General (206)5.10.8.2Selection and reselection of synchronisation reference UE (SyncRef UE) (206)5.10.9Sidelink common control information (207)5.10.9.1General (207)5.10.9.2Actions related to reception of MasterInformationBlock-SL message (207)5.10.10Sidelink relay UE operation (207)5.10.10.1General (207)5.10.10.2AS-conditions for relay related sidelink communication transmission by sidelink relay UE (207)5.10.10.3AS-conditions for relay PS related sidelink discovery transmission by sidelink relay UE (208)5.10.10.4Sidelink relay UE threshold conditions (208)5.10.11Sidelink remote UE operation (208)5.10.11.1General (208)5.10.11.2AS-conditions for relay related sidelink communication transmission by sidelink remote UE (208)5.10.11.3AS-conditions for relay PS related sidelink discovery transmission by sidelink remote UE (209)5.10.11.4Selection and reselection of sidelink relay UE (209)5.10.11.5Sidelink remote UE threshold conditions (210)6Protocol data units, formats and parameters (tabular & ASN.1) (210)6.1General (210)6.2RRC messages (212)6.2.1General message structure (212)–EUTRA-RRC-Definitions (212)–BCCH-BCH-Message (212)–BCCH-DL-SCH-Message (212)–BCCH-DL-SCH-Message-BR (213)–MCCH-Message (213)–PCCH-Message (213)–DL-CCCH-Message (214)–DL-DCCH-Message (214)–UL-CCCH-Message (214)–UL-DCCH-Message (215)–SC-MCCH-Message (215)6.2.2Message definitions (216)–CounterCheck (216)–CounterCheckResponse (217)–CSFBParametersRequestCDMA2000 (217)–CSFBParametersResponseCDMA2000 (218)–DLInformationTransfer (218)–HandoverFromEUTRAPreparationRequest (CDMA2000) (219)–InDeviceCoexIndication (220)–InterFreqRSTDMeasurementIndication (222)–LoggedMeasurementConfiguration (223)–MasterInformationBlock (225)–MBMSCountingRequest (226)–MBMSCountingResponse (226)–MBMSInterestIndication (227)–MBSFNAreaConfiguration (228)–MeasurementReport (228)–MobilityFromEUTRACommand (229)–Paging (232)–ProximityIndication (233)–RNReconfiguration (234)–RNReconfigurationComplete (234)–RRCConnectionReconfiguration (235)–RRCConnectionReconfigurationComplete (240)–RRCConnectionReestablishment (241)–RRCConnectionReestablishmentComplete (241)–RRCConnectionReestablishmentReject (242)–RRCConnectionReestablishmentRequest (243)–RRCConnectionReject (243)–RRCConnectionRelease (244)–RRCConnectionResume (248)–RRCConnectionResumeComplete (249)–RRCConnectionResumeRequest (250)–RRCConnectionRequest (250)–RRCConnectionSetup (251)–RRCConnectionSetupComplete (252)–SCGFailureInformation (253)–SCPTMConfiguration (254)–SecurityModeCommand (255)–SecurityModeComplete (255)–SecurityModeFailure (256)–SidelinkUEInformation (256)–SystemInformation (258)–SystemInformationBlockType1 (259)–UEAssistanceInformation (264)–UECapabilityEnquiry (265)–UECapabilityInformation (266)–UEInformationRequest (267)–UEInformationResponse (267)–ULHandoverPreparationTransfer (CDMA2000) (273)–ULInformationTransfer (274)–WLANConnectionStatusReport (274)6.3RRC information elements (275)6.3.1System information blocks (275)–SystemInformationBlockType2 (275)–SystemInformationBlockType3 (279)–SystemInformationBlockType4 (282)–SystemInformationBlockType5 (283)–SystemInformationBlockType6 (287)–SystemInformationBlockType7 (289)–SystemInformationBlockType8 (290)–SystemInformationBlockType9 (295)–SystemInformationBlockType10 (295)–SystemInformationBlockType11 (296)–SystemInformationBlockType12 (297)–SystemInformationBlockType13 (297)–SystemInformationBlockType14 (298)–SystemInformationBlockType15 (298)–SystemInformationBlockType16 (299)–SystemInformationBlockType17 (300)–SystemInformationBlockType18 (301)–SystemInformationBlockType19 (301)–SystemInformationBlockType20 (304)6.3.2Radio resource control information elements (304)–AntennaInfo (304)–AntennaInfoUL (306)–CQI-ReportConfig (307)–CQI-ReportPeriodicProcExtId (314)–CrossCarrierSchedulingConfig (314)–CSI-IM-Config (315)–CSI-IM-ConfigId (315)–CSI-RS-Config (317)–CSI-RS-ConfigEMIMO (318)–CSI-RS-ConfigNZP (319)–CSI-RS-ConfigNZPId (320)–CSI-RS-ConfigZP (321)–CSI-RS-ConfigZPId (321)–DMRS-Config (321)–DRB-Identity (322)–EPDCCH-Config (322)–EIMTA-MainConfig (324)–LogicalChannelConfig (325)–LWA-Configuration (326)–LWIP-Configuration (326)–RCLWI-Configuration (327)–MAC-MainConfig (327)–P-C-AndCBSR (332)–PDCCH-ConfigSCell (333)–PDCP-Config (334)–PDSCH-Config (337)–PDSCH-RE-MappingQCL-ConfigId (339)–PHICH-Config (339)–PhysicalConfigDedicated (339)–P-Max (344)–PRACH-Config (344)–PresenceAntennaPort1 (346)–PUCCH-Config (347)–PUSCH-Config (351)–RACH-ConfigCommon (355)–RACH-ConfigDedicated (357)–RadioResourceConfigCommon (358)–RadioResourceConfigDedicated (362)–RLC-Config (367)–RLF-TimersAndConstants (369)–RN-SubframeConfig (370)–SchedulingRequestConfig (371)–SoundingRS-UL-Config (372)–SPS-Config (375)–TDD-Config (376)–TimeAlignmentTimer (377)–TPC-PDCCH-Config (377)–TunnelConfigLWIP (378)–UplinkPowerControl (379)–WLAN-Id-List (382)–WLAN-MobilityConfig (382)6.3.3Security control information elements (382)–NextHopChainingCount (382)–SecurityAlgorithmConfig (383)–ShortMAC-I (383)6.3.4Mobility control information elements (383)–AdditionalSpectrumEmission (383)–ARFCN-ValueCDMA2000 (383)–ARFCN-ValueEUTRA (384)–ARFCN-ValueGERAN (384)–ARFCN-ValueUTRA (384)–BandclassCDMA2000 (384)–BandIndicatorGERAN (385)–CarrierFreqCDMA2000 (385)–CarrierFreqGERAN (385)–CellIndexList (387)–CellReselectionPriority (387)–CellSelectionInfoCE (387)–CellReselectionSubPriority (388)–CSFB-RegistrationParam1XRTT (388)–CellGlobalIdEUTRA (389)–CellGlobalIdUTRA (389)–CellGlobalIdGERAN (390)–CellGlobalIdCDMA2000 (390)–CellSelectionInfoNFreq (391)–CSG-Identity (391)–FreqBandIndicator (391)–MobilityControlInfo (391)–MobilityParametersCDMA2000 (1xRTT) (393)–MobilityStateParameters (394)–MultiBandInfoList (394)–NS-PmaxList (394)–PhysCellId (395)–PhysCellIdRange (395)–PhysCellIdRangeUTRA-FDDList (395)–PhysCellIdCDMA2000 (396)–PhysCellIdGERAN (396)–PhysCellIdUTRA-FDD (396)–PhysCellIdUTRA-TDD (396)–PLMN-Identity (397)–PLMN-IdentityList3 (397)–PreRegistrationInfoHRPD (397)–Q-QualMin (398)–Q-RxLevMin (398)–Q-OffsetRange (398)–Q-OffsetRangeInterRAT (399)–ReselectionThreshold (399)–ReselectionThresholdQ (399)–SCellIndex (399)–ServCellIndex (400)–SpeedStateScaleFactors (400)–SystemInfoListGERAN (400)–SystemTimeInfoCDMA2000 (401)–TrackingAreaCode (401)–T-Reselection (402)–T-ReselectionEUTRA-CE (402)6.3.5Measurement information elements (402)–AllowedMeasBandwidth (402)–CSI-RSRP-Range (402)–Hysteresis (402)–LocationInfo (403)–MBSFN-RSRQ-Range (403)–MeasConfig (404)–MeasDS-Config (405)–MeasGapConfig (406)–MeasId (407)–MeasIdToAddModList (407)–MeasObjectCDMA2000 (408)–MeasObjectEUTRA (408)–MeasObjectGERAN (412)–MeasObjectId (412)–MeasObjectToAddModList (412)–MeasObjectUTRA (413)–ReportConfigEUTRA (422)–ReportConfigId (425)–ReportConfigInterRAT (425)–ReportConfigToAddModList (428)–ReportInterval (429)–RSRP-Range (429)–RSRQ-Range (430)–RSRQ-Type (430)–RS-SINR-Range (430)–RSSI-Range-r13 (431)–TimeToTrigger (431)–UL-DelayConfig (431)–WLAN-CarrierInfo (431)–WLAN-RSSI-Range (432)–WLAN-Status (432)6.3.6Other information elements (433)–AbsoluteTimeInfo (433)–AreaConfiguration (433)–C-RNTI (433)–DedicatedInfoCDMA2000 (434)–DedicatedInfoNAS (434)–FilterCoefficient (434)–LoggingDuration (434)–LoggingInterval (435)–MeasSubframePattern (435)–MMEC (435)–NeighCellConfig (435)–OtherConfig (436)–RAND-CDMA2000 (1xRTT) (437)–RAT-Type (437)–ResumeIdentity (437)–RRC-TransactionIdentifier (438)–S-TMSI (438)–TraceReference (438)–UE-CapabilityRAT-ContainerList (438)–UE-EUTRA-Capability (439)–UE-RadioPagingInfo (469)–UE-TimersAndConstants (469)–VisitedCellInfoList (470)–WLAN-OffloadConfig (470)6.3.7MBMS information elements (472)–MBMS-NotificationConfig (472)–MBMS-ServiceList (473)–MBSFN-AreaId (473)–MBSFN-AreaInfoList (473)–MBSFN-SubframeConfig (474)–PMCH-InfoList (475)6.3.7a SC-PTM information elements (476)–SC-MTCH-InfoList (476)–SCPTM-NeighbourCellList (478)6.3.8Sidelink information elements (478)–SL-CommConfig (478)–SL-CommResourcePool (479)–SL-CP-Len (480)–SL-DiscConfig (481)–SL-DiscResourcePool (483)–SL-DiscTxPowerInfo (485)–SL-GapConfig (485)。

WebRTC ——实现视频会议的协议简介WebRTC（Web Real-Time Communication）是一种用于实时通信的开放标准。

它可以在Web浏览器和移动应用程序中实现音频、视频和数据的实时传输。

WebRTC的主要目标是通过使用标准化的API，使开发者能够简单地构建实时通信应用，如视频会议、音频通话和实时游戏。

本文将介绍WebRTC的核心组件和协议，以及实现视频会议的过程。

WebRTC的核心组件WebRTC由三个核心组件组成：1.RTCPeerConnection：负责建立点对点的连接，实现音频、视频和数据的传输。

2.RTCDataChannel：允许浏览器之间双向传输任意类型的数据。

3.getUserMedia：用于从摄像头和麦克风获取本地的音频和视频流。

这三个核心组件共同协作，使得实时通信成为可能。

WebRTC的协议WebRTC实现实时通信的协议主要包括：1.ICE（Interactive Connectivity Establishment）：ICE 协议用于在对等连接之间建立最佳的网络连接。

它通过使用STUN （Session Traversal Utilities for NAT）和TURN（Traversal Using Relays around NAT）服务器来克服各种网络环境中的网络地质转换（NAT）和防火墙限制。

2.SDP（Session Description Protocol）：SDP协议用于描述音频、视频和数据的格式、编解码器、网络地质等信息。

在WebRTC 中，SDP用于在对等连接之间交换媒体协商信息，以便建立适当的音频和视频传输参数。

3.DTLS（Datagram Transport Layer Security）：DTLS协议用于保护WebRTC通信的安全性。

它在传输层使用TLS（Transport Layer Security）协议的基础上，添加了数据报的特性，以适应实时通信的要求。

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 。

Innovative Technology Limited®SSP Smiley® Secure ProtocolDocument Issue 13 - Protocol Version 3COPYRIGHT 2000. Innovative Technology Ltd. Derker Street, Derker, Oldham. OL1 4EQChange History.Innovative Technology LtdTitle: SSP Gaming ProtocolProject:Drawing No: GA138Author: P. Dunlop Date: 26/05/98 Format: MS Word 2000Issue Protocol Ver Release Date Mod By CommentsIssue 1 1 26/05/98 PDIssue 2 1 03/02/99 TBIssue 3 1 11/06/99 AKIssue 4 2 4/02/00 PDIssue 5 2 20/06/00 PDIssue 6 2 26/10/00 PDIssue 7 2 20/11/00 PDIssue 8 2 20/01/01 TBIssue 9 2 4/10/01 TBIssue 10 2 21/01/02 AKIssue 11 2 23/03/04 PK General RevisionIssue 12 3 05/08/04 TB Protocol Version 3Issue 13 3 02/01/06 TB Protocol Version 3 eventsIssue 4. – Peter Dunlop 13/01/2000Introduction of generic commands. Introduction of commands/ responses for coin readers and coin hoppers. Introduction of addressing structure. Introduction of encrypted packets. Upgrade “Protocol Version’ to 2.Issue 5 – Peter Dunlop 20/06/2000Clarification of remote download specification – addition of example sequences. Correction of command conflict – SYNC and LAST REJECT CODE specified with same code, LAST REJECT CODE has been changed to 0x17. Addition of notes to identify function not currently implemented on NV4 / NV4X.Issue 6. – Peter Dunlop 26/10/00Block size missing from header description in version 5 – fixed. Rewording of description of remote downloading protocol.Addition of maximum block size. No code changes required in product firmware or demo code. Changed example CRC codefrom assembler example to C example. Addition of simplified remote programming flow chart.Issue 7. – Peter Dunlop 20/11/00Introduction of basic card reader commands. Addition of FAIL as a generic response. Addition of manufacturers extensiongeneric command for use internally.Issue 8. – Tim Beswick 20/01/01Change SLAVE_RESET form generic response to an event response to reflect correct behaviour. Addition of euro county codeto appendix.Issue 9. – Tim Beswick 04/10/01Addition of HOLD command to allow escrow implementation on BNVIssue 10 – Andrew Kennerley 21/01/02Addition of slave address for a Audit Collection DeviceIssue 11 – Peter King 23/03/04General Revision Correction of Slave ID Reference in section 3.1Addition of extra address allocation for note validatorsIssue 12 – Tim Beswick 05/08/04Addition of SHOW_RESET_EVENTS BNV commands and note cleared at reset events. Protocol taken to Version 3 Issue 13 – Tim Beswick 02/01/06Addition of Cash box removed and replaced events. Explanation of Note start-up events in expanded protocol.Table Of ContentsChange History (2)1.0 Introduction (5)2.0 General Description (6)3.0 Hardware Layer (7)4.0 Transport Layer (8)4.1 Packet Format (8)4.2 Packet Sequencing (8)5.0 Encryption Layer. (Currently not implemented) (9)5.1 Packet Format (9)5.2 Encryption Keys (9)5.3 Encryption Algorithm (9)5.4 Encryption Example (10)6.0 Control Layer (11)6.1 Introduction (11)6.2 Addressing (11)6.3 Peripheral Validation (11)6.4 Generic Commands and Responses (12)6.4.1 Generic Commands (12)6.4.2 Generic Responses (13)6.4.3 Remote Programming (Version 2.65 and later) (13)6.4.4 Example programming file formats (ITL NV4 Validator) (14)6.4.5 Simplified remote programming flow chart (15)6.5 Banknote Validator (16)6.5.1 BNV Operation (16)6.5.2 BNV Commands (16)6.5.3 BNV Response To Polls (18)6.6 Coin Acceptor (20)6.6.1 Coin Acceptor Operation (20)6.6.2 Coin Acceptor Commands (20)6.6.3 Coin Acceptor Responses to Polls (22)6.7 Coin Hopper (23)6.7.1 Coin Hopper Operation (23)6.7.2 Coin Hopper Commands (23)6.7.3 Coin Hopper Responses to Polls (24)6.8 Basic Card Reader (25)6.8.1 Basic Card Reader Operation (25)6.8.2 Basic Card Reader Commands (26)6.8.3 Basic Card Reader Responses to Polls (27)Appendix A – Country Codes (28)Appendix. B – Block Encryption Routines (29)B.1 Encryption routine (29)B.2 Decryption routine (29)Appendix C – CRC Calculation Routines (30)1.0 IntroductionThis manual describes the operation of the Smiley® Secure Protocol - SSP as fitted with Firmware Version 1.10 or greater.ITL recommend that you study this manual as there are many new features permitting new uses and more secure applications.If you do not understand any part of this manual please contact the ITL for assistance. In this way we may continue to improve our product. Alternatively visit our web site at www.innovative-Enhancements of SSP can be requested by contacting: support@Innovative Technology Ltd.StreetDerkerOldhamEnglandOL1 4EQ9999Tel:161626+44(0)6202090161+44Fax:(0)Email support@web site 2.0 General Description.Smiley® Secure Protocol - SSP is a secure interface specifically designed by ITL® to address the problems experienced by cash handling systems in gaming machines. Problems such as acceptor swapping, reprogramming acceptors and line tapping are all addressed.The interface uses a master slave model, the host machine is the master and the peripherals (note acceptor, coin acceptor or coin hopper) are the slaves.Data transfer is over a multi-drop bus using clock asynchronous serial transmission with simple open collector drivers. The integrity of data transfers is ensured through the use of 16 bit CRC checksums on all packets.Each SSP device of a particular type has a unique serial number; this number is used to validate each device in the direction of credit transfer before transactions can take place. To provide extra security the protocol can operate in an encrypted mode to protect the system from fraud through bus monitoring.To provide this security a constantly changing random 64 bit key is used. Commands are currently provided for coin acceptors, note acceptors and coin hoppers. All current features of these devices are supported.Features:• Serial control of Note / Coin Validators and Hoppers• 4 wire (Tx, Rx, +V, Gnd) system• RS232 (like) - open collector driver• High Speed 9600 Baud Rate• 16 bit CRC error checking• Data Transfer Mode• 64 Bit Encrypted ModeBenefits:• Proven in the field• Simple and low cost interfacing of transaction peripherals.• High security control of payout peripherals.• Defence against surrogate validator fraud.• Straightforward integration into host machines.• Remote programming of transaction peripherals• Open standard for universal use.To help in the software implementation of the SSP, ITL can provide, C Code, DLL controls and Visual Basic applications on request. Please contact support@.3.0 Hardware LayerCommunication is by character transmission based on standard 8-bit asynchronous data transfer. Only four wires are required TxD, RxD, +V and ground. The transmit line of the host is open collector, the receive line of each peripheral has a 10Kohm pull-up to 5 volts. The transmit output of each slave is open collector, the receive input of the host has a single 3k3 ohm pull-up to 5 volts.The data format is as follows:Encoding: NRZ Baud Rate: 9600 Duplex: Full Duplex Start bits: 1 Data Bits: 8 Parity:none Stop bits: 2Recommended ConnectorsTwo types of connectors are recommended the first is a 15 pin 0.1” pitch header (Molex 22-01-2155), this is primarily for use on bank note acceptors (see table 1).Pin Signal Pin 1 TxD Pin 5 RxDPin 6 Address 0 (Currently not implemented)Pin 12 GND Pin 11+12V Link Pin 3 to Pin 8.ENABLETable 1 – Bank Note Acceptor Connector DetailsThe second is a 10-pin 0.1” dual row shrouded header with polarized slot. This is primarily for use with coin acceptors. The pin out is shown below (see table 2).PinSignal PinSignal 1 TxD 2 Reserved 3 RxD 4 Reserved 5 Address 0 6 Address 1 7 + 12 Volts 8 Ground 9 Address 2 10 Address 4Table 2 – Coin Acceptor Connector Details4.0 Transport Layer.4.1 Packet Format.Data and commands are transported between the host and the slave(s) using a packet format asshown below.LENGTH DATA CRCL CRCH STX SEQ/SlaveIDSTX:Single byte indicating the start of a message - 0x7F hex.SEQ/Slave ID:Bit 7 is the sequence flag of the packet, bits 6-0 represent the address of theslave the packet is intended for, the highest allowable slave ID is 0x7D LENGTH:The length of the data included in the packet - this does not includeSTX, the CRC or the slave ID.Slave ID:Single byte used to identify the address of the slave the packet isfor.intendedDATA:Commands or data to be transferred.CRCL, CRCH:Low and high byte of a forward CRC-16 algorithm using the(X16 + X15 + X2 +1) calculated on all bytes,Polynomialexcept STX. It is initialised using the seed 0xFFFF. The CRC isbytestuffing.calculatedbefore4.2 Packet Sequencing.Byte stuffing is used to encode any STX bytes that are included in the data to be transmitted. If 0x7F (STX) appears in the data to be transmitted then it should be replaced by 0x7F, 0x7F.Byte stuffing is done after the CRC is calculated, the CRC its self can be byte stuffed. The maximum length of data is 0xFF bytes. The sequence flag is used to allow the slave to determine whether apacket is a re-transmission due to its last reply being lost.Each time the master sends a new packet to a slave it alternates the sequence flag. If a slavereceives a packet with the same sequence flag as the last one, it does not execute the command but simply repeats its last reply.In a reply packet the address and sequence flag match the command packet. This ensures that noother slaves interpret the reply as a command and informs the master that the correct slave replied.After the master has sent a command to one of the slaves, it will wait for 1 second for a reply. Afterthat, it will assume the slave did not receive the command intact so it will re-transmit it with the same sequence flag.The host should also record the fact that a gap in transmission has occurred and prepare to poll theslave for its serial number identity following the current message. In this way, the replacement of the host’s validator by a fraudulent unit can be detected.The frequency of polling should be selected to minimise the possibility of swapping a validatorbetween polls. If the slave has not received the original transmission, it will see the re-transmission asa new command so it will execute it and reply. If the slave had seen the original command but its replyhad been corrupted then the slave will ignore the command but repeat its reply. After twenty retries,the master will assume that the slave has crashed.A slave has no time-out or retry limit. If it receives a lone sync byte part way through receiving apacket it will discard the packet received so far and treat the next byte as an address byte.5.0 Encryption Layer. (Currently not implemented)5.1 Packet Format.Encrypted data and commands are transported between the host and the slave(s) using the transport mechanism described above, the encrypted information is stored in the data field in the format shown below (see figure 1).Figure 1 – Encrypted Data FormatSTEX:Single byte indicating the start of an encrypted data block - 0x7E hex. LENGTH:The length of the data included in the packet - this does not includeSTEX, the next key or the CRC.DATA:Commands or data to be transferred.NEXT KEY:The key needed to decrypt the next encrypted packet from the host. CRCL, CRCH:Low and high byte of a forward CRC-16 algorithm using the(X16 + X15 + X2 +1) calculated on all bytes,polynomialexcept STEX. It is initialised using the seed 0xFFFF.5.2 Encryption Keys.At power up the first encrypted data packet sent to the peripheral will be encrypted using the peripherals serial number (the host requests and stores the serial number of each peripheral when it is installed – see control layer).After the first transmission data is encrypted/decrypted using the key contained in the last packet, the host generates this randomly. The peripheral will always reply to an encrypted packet with data encrypted using the same key as the original packet from the host.After the data has been decrypted the CRC algorithm is preformed on all bytes including DATA, NEXT KEY, CRCL and CRCH. The result of this calculation will be zero if the data has been decrypted with the correct key.If the result of this calculation is non-zero then the peripheral should assume that the host did not encrypt the data (transmission errors are detected by the transport layer). The slave should go out of service until it is reset.5.3 Encryption Algorithm.The encryption algorithm has a 64-bit key. This is only a short key but when combined with the mechanism for changing the key in every packet the system provides a high level of security. Appendix B contains C source code for encryption and decryption.The algorithm will easily translate into assembly code as long as the XOR is an operation. The routines works on blocks of 16 bytes that are packed into an array of four long integers, the key is 8 bytes long and is packed into an array of 2 long integers. If the data to be sent is not a multiple of 16 bytes then the remaining bytes are packed out with zeros (see tables 3).5.4 Encryption Example.Convert key into long integerKey() 0 1 2 3 4 5 6 7Value Ox67 Ox45 Ox23 Ox01 OxEF OxCD OxAB Ox89L_key() 0 1Value Ox01234567 Ox89ABCDEFGet data bytesData 0 1 2 3 4 5 6 7 8 9 10Value OxFF OxEE OxDD OxCC OxBB OxAA Ox99 Ox88 Ox77 Ox66 Ox55Convert data into array of 4 long integers any unused bytes set to Ox00Data 0 1 2 3Ox00000000Ox00556677Value OxCCDDEEFFOx8899AABBPass data through encryption algorithm.E_Data 0 1 2 3OxDA441723Ox5D2743D2 Value Ox1500F4F6OxF56E7CBABreak up into individual bytes for transmission:E_Data 0 1 2 3Ox5D2743D2Value Ox1500F4F6 OxF56E7CBA OxDA4417230 1 2 3 4 5 6 7 8 9 A B C D E FValue F6 F4 00 15 BA 7C 6E F5 23 17 44 DA D2 43 27 5DTables 3 – Encryption Examples6.0 Control Layer6.1 IntroductionThe slave can only respond to requests from the master with an address byte that matches the slaves address, at no time will the slave transmit any data that is not requested by the host. Any data that is received with an address that does not match the slave’s address will be discarded.The master will poll each slave at least every 5 seconds. The slave will deem the host to be inactive, if the time between polls is greater than 5 seconds. If the slave does not receive a poll within 5 seconds it should change to its disabled state. The minimum time between polls is specified for individual peripherals. Only one command can be sent in any one poll sequence.6.2 Addressing.The address of a peripheral consists of two parts, the fixed part that determines the type of deviceand the variable part. The variable part is used if there is a number of the same type of peripheral in the same machine, for example hoppers (see table 4).The variable part of the address can be set in one of two ways. Firstly it can be programmed to a fixed number using a PC tool, or the peripheral can be programmed to take the rest of the address from external pins on the interface connector(Currently not implemented).Slave ID (Hex) Peripheral0x00 Note validator 00x01 Note validator 10x02 Coin Validator 00x03 Coin Validator 10x04 Card Reader 00x05 Card Reader 1Device0x07 Audit0x08 Handheld Audit Collection Device0x09 – 0x0F Reserved0x10 – 0x1F Coin Hoppers 0 – 150x20 – 0x2F Note Dispensers 0 – 150x30 – 0x3F Card Dispensers 0 – 150x40 – 0x4F Ticket Dispensers 0 – 150x50 – 0x5F Extra Note Validators0x60 – 0x7E UnallocatedTable 4 – Peripheral Addressing6.3 Peripheral Validation.To ensure that credit transfers are only received from or sent to genuine devices, the device receiving the credit must first request the serial number from the sending device and only accept if the serial number matches a pre-programmed number.The serial number should be requested after each reset and also after each break in communications. For example a host machine should request a coin acceptors serial number at reset or if a poll sequence is unanswered, before enabling the device. Also, a coin hopper should not process any dispense commands until the host machine has sent its serial number.6.4 Generic Commands and Responses.Generic commands are a set of commands that every peripheral must understand and act on (seetable 5).6.4.1 Generic CommandsAction Command code (HEX)Reset 0x01 Host Protocol Version 0x06Poll 0x07 Get Serial Number 0x0CSynchronisation command 0x11Disable 0x09Enable 0x0A Program Firmware / currency 0x0B, Programming TypeManufactures Extension 0x30, Command, DataTable 5 – Generic CommandsReset:Single byte command, causes the slave to reset.Host Protocol Version: Dual byte command, the first byte is the command, the second byte is theversion of the protocol that is implemented on the host, current version is 02.Poll: Single byte command, no action taken except to report latest events.Get Serial Number: Single byte command, used to request the slave serial number. Returns 4-bytelong integer.Most significant byte first e.g.Serial number = 01873452 = 0x1C962CSo response data would be 0x00 0x1C 0x96 0x2CSync: Single byte command, which will reset the validator to expect the next sequence ID to be 0.Disable: Single byte command, the peripheral will switch to its disabled state, it will not execute anymore commands or perform any actions until enabled, any poll commands will report disabled.Enable: Single byte command, the peripheral will return to service.Program Firmware / currency:See section 6.4.3 – Remote Programming.Manufactures Extension: This command allows the manufacturer of a peripheral to send commandsspecific to their unit. The intention is that the manufacturer only uses the extension commandinternally; it should not when operating in a host machine. The specific command and any data forthat command should follow the Extension command.6.4.2 Generic ResponsesGeneric Response Response codeOK 0xFOCommand not known 0xF2Wrong number of parameters 0xF3Parameter out of range 0xF4Command cannot be processed 0xF5Software Error 0xF6FAIL 0xF8Table 6 - Generic ResponsesOK: Returned when a command from the host is understood and has been, or is in the process of,being executed.Command Not Known: Returned when an invalid command is received by a peripheral.Wrong Number Of Parameters: A command was received by a peripheral, but an incorrect numberof parameters were received.Parameter Out Of Range: One of the parameters sent with a command is out of range. E.g. trying tochange the route map for channel 34 on a coin acceptor.Command Cannot Be Processed: A command sent could not be processed at that time. E.g.sending a dispense command before the last dispense operation has completed.Software Error: Reported for errors in the execution of software e.g. Divide by zero. This may alsobe reported if there is a problem resulting from a failed remote firmware upgrade, in this case thefirmware upgrade should be redone.6.4.3 Remote Programming (Version 2.65 and later).Code Description0x0B, Type Start Programming, type (00 – firmware, 01 - currency)Status.0x16 ProgrammingTable 7 - Remote Programming Code SummaryUsing the command 0x0B followed by a parameter that indicates the type of programming requiredperforms remote programming (see table 7). Send 0x00 for firmware programming and 0x01 forcurrency data programming.The peripheral will respond with a generic reply. If the reply is OK, the host should send the first blockof the data file (the file header). The header has the format shown below (see table 8). The block sizedepends on the peripheral used but must be a minimum of 10 bytes to contain the header data.When the block size for a peripheral is greater than the header length (11 bytes) then the header ispadded out with 0’s to the length of a block. The maximum length of a block is 236 bytes.File offset Description Size0 Number of blocks to send (low byte, high byte), including header block 2 bytes2 Manufacture code (of file) e.g. ‘ITL’3 bytes5 File type – 0x00 firmware, 0x01 currency 1 byte6 Unit subtype 1 byte7 Unit version 1 bytebyte8 Block length (B L) 19 Checksum (CRC of data section of file) CRC low byte 1 byteA Checksum (CRC of data section of file) CRC high byte 1 byteB Padded 0’s to block size B L-11 bytesTable 8 - Remote Programming / Header and Block SizeThe peripheral will then respond with OK or HEADER_FAIL depending on the acceptability of this file(see table 9).Response CodeOK 0xF0 HEADER_FAIL 0xF9Table 9 – Peripheral ResponseThe host will then send the required number of data blocks. The peripheral will respond with ageneric response when each packet has been processed (see table 10).If the host receives any response other than an OK then that packet is retried three times beforeaborting the programming (the peripheral should then be reset).After the last data packet has been sent and a response received, the host will send a programmingstatus command 0x16. The peripheral will respond with one of the following codes:Response CodeOK 0xF0 Checksum Error 0xF7FAIL 0xF8 Table 10 - Peripheral Response CodesAfter a successful programming cycle, the peripheral should be reset. If the programming cycle doesnot complete successfully, then the peripheral should be disabled until it can be programmedsuccessfully.In the case of an unsuccessful firmware programming cycle, the new firmware will either be discardedor partly programmed. If the firmware has been partly programmed, then the peripheral will respondto all Polls with the generic response ‘Software Error’.The peripheral will not allow the host to enable it until it receives a complete and valid firmware file.6.4.4 Example programming file formats (ITL NV4 Validator).Programming files supplied by Innovative Technology Ltd for NV4 BNV are formatted as follows (seetables 11 and 12): Variable number of blocks depending on currency, fixed block length (128 bytes).Header block 92, 01, 49, 54, 4C, 01, 01, 01, 80, 8D, 2C Padded to block length with 0’s1st data block F0, 34, C0, 21, D3, 00, 00, 5F, 5F, 80h data bytes2nd data block FF, 24, D3, 21, 45, 01, 00, 3F, 5F, 80h data bytes..257th data block FF, 24, D3, 21, 45, 01, 00, 3F, 5F, 80h data bytesTable 11 - Currency File ExampleHeader block 01, 01, 49, 54, 4C, 00, 01, 01, 80, FD, 22 Padded to block length with 0’s1st data block FF, 24, D3, 21, 45, 01, 00, 3F, 5F, 80h data bytes2nd data block F0, 34, C0, D1, D3, 00, 00, 5F, 5F 80h data bytes..257th data block FF, 24, D3, 21, 45, 01, 00, 3F, 5F, 80h data bytesTable 12 - Firmware File Example6.4.5 Simplified remote programming flow chart.Figure 2 - Programming Flow Chart6.5 Banknote Validator6.5.1 BNV Operation.When the validator has recognised a note, it will not start to stack it until it receives the next valid pollcommand after the read n (n<>0) has been sent. The note will be rejected if the host responds with aREJECT.6.5.2 BNV CommandsAction Command code (HEX)Set inhibits 0x02Display on 0x03Display Off 0x04Set-up Request 0x05Reject 0x08Unit data 0x0DChannel Value data 0x0EChannel Security data 0x0FChannel Re-teach data 0x10Last Reject Code 0x17Hold 0x18 Enable Protocol Version Events 0x19Table 13 – Bank Note Validator CommandsSet Inhibits: Variable length command, used to control which channels are enabled. The commandbyte is followed by 2 data bytes, these bytes are combined to create the INHIBIT_REGISTER, eachbit represents the state of a channel (LSB= channel 1, 1=enabled, 0=disabled). At power up allchannels are inhibited and the validator is disabled.Display On: Single Byte command, turns on the display illumination bulb.Display Off: Single Byte command, turns off the display illumination bulb.Reject: Single byte command causing the validator to reject the current note.Set-up Request: Single byte command, used to request information about a slave. Slave will returnthe following data: Unit Type, Firmware version, Country Code, Value multiplier, Number of channels,(if number of channels is 0 then 0 is returned and next two parameters are not returned) Value perchannel, security of channel, Reteach count, Version of Protocol (see table 14).Data Size/type NotesUnit Type 1 byte, integer 0x00 Note ValidatorFirmware Version 4 bytes, string XX.XX (can include space)Country Code 3 bytes, string See Country Code TableValue Multiplier 3 bytes, integer 24 bit valueNumber of channels 1 byte, integer Highest used channelChannel Value 15 bytes, integer bytes 1 – 15 valuesSecurity of Channel 15 bytes, integer bytes 1 – 15 securityReteach count 3 byte, integer Byte 1 - reteach count.Byte 2, 3 flag register indicatingwhich channels have beenmodified. All set to zero atfactory.Protocol version 1 byte, integerTable 14 - Response to Set-up requestUnit Data Request: Single byte command which returns, Unit type (1 Byte integer), FirmwareVersion (4 bytes ASCII string), Country Code (3 Bytes ASCII string), Value Multiplier (3 bytes integer), Protocol Version (1 Byte, integer)Channel Value Request: Single byte command which returns a number of channels byte (thehighest channel used) and then 1 to n bytes which give the value of each channel up to the highestone, a zero indicates that the channel is not implemented.e.g. A validator has notes in Channels 1,2,4,6,7 so this command would return07,01,02,00,04,00,06,07. (The values are just examples and would depend on the currency of the unit).The actual value of a note is calculated by multiplying the value multiplier by channel value.If the number of channels is 0 then only one 0 will be returned.Channel Security Data: Single byte command which returns a number of channels byte (the highest channel used) and then 1 to n bytes which give the security of each channel up to the highest one, azero indicates that the channel is not implemented.(1 = low, 2 = std, 3 = high, 4 = inhibited).E.g. A validator has notes in Channels 1,2,4,6,7 channel 1 is low security, channel 6 is high security,all the rest are standard security.The return bytes would be07,01,02,00,02,00,02,03If the number of channels is 0 then only one 0 will be returned.Channel Reteach Data: Single byte command, which returns 3 bytes.First byte - the number of times the unit has been manually taught. (1 for each face).Second byte - Channels 1 to 8 flag register bit 0 = channel 1 to bit 7 = channel 8 if set shows that the indicated channel has been altered.Third byte is as second but the channels shown are bit 1 = channel 9 to bit 6 = channel 15.Last Reject Code: Single byte command, which will return a single byte that indicates the reason forthe last reject. The codes are shown below (see table 15). Specifics of note validation not shown to protect integrity of manufacturers securit y (Version 2.66 and later).Code Reject ReasonAccepted 0x00 Note0x01 Note length incorrect0x02 Reject reason 20x03 Reject reason 30x04 Reject reason 40x05 Reject reason 5Inhibited 0x06 Channel0x07 Second Note Inserted0x08 Reject reason 80x09 Note recognised in more than one channel0x0A Reject reason 100x0B Note too long0x0C Reject reason 120x0D Mechanism Slow / StalledAttempt 0x0E Striming0x0F Fraud Channel Reject0x10 No Notes InsertedTable 15 – Reject Code ReasonsHold: This command may be sent to BNV when Note Read has changed from 0 to >0 (valid noteseen) if the user does not wish to accept or reject the note with the next command.This command will also reset the 10 second time-out period after which a note held would be rejected automatically, so it should be sent before this time-out if an escrow function is required.。

UC-8430 SeriesOverviewThe UC-8430 embedded computer comes with 8 RS-232/422/485 serial ports, 3 Ethernet ports, dual displays, 4 digital input channels, 4 digital output channels, a CompactFlash socket, and 6 USB 2.0 hosts.The computer uses the Intel XScale IXP435 533 MHz RISC CPU. This powerful computing engine supports several useful communication functions, but will not generate too much heat. The built-in 32 MB NOR Flash ROM and 256 MB SDRAM give you enough memory to run your application software directly on the UC-8430, and the 32 MB NAND Flash can be used to provide additional data storage.Moreover, the 256 KB SRAM offers a better data retention mechanism for avoiding data loss. The UC-8430 computer comes with 8 RS-232/422/485 serial ports, digital I/O, and has 3 LAN ports, making it ideal as a communication platform for industrial applications thatrequire network redundancy. As an added convenience, the UC-8430 comes with dual VGA outputs; this is particularly helpful when establishing an industrial application at a remote field site.The UC-8430 comes with the Linux 2.6 or Windows CE 6.0 platform pre-installed to provide an open software operating system forsoftware program development. Software written for a desktop PC can be easily ported to the UC-8430 platform by using a common compiler, without needing to modify the code. This makes the UC-8430 an optimal solution for use with industrial applications, but with minimal cost and effort.A wide temperature model of the UC-8430, designed to operate reliably in temperatures ranging from -40 to 75°C, is also available.AppearanceFront ViewRear View(RS-232/422/485)LAN Port x 3, RJ45DO x 4Ready, Storage)Hardware SpecificationsComputerCPU: Intel XScale IXP435, 533 MHzOS (pre-installed): Linux, Window CE 6.0DRAM: 256 MB DDR2 SDRAM onboard (supports DDR2 up to 512 MB)SRAM: 256 KB, battery backupFlash:32 MB NOR Flash onboard to store OS32 MB NAND Flash onboard to store dataUSB: USB 2.0 host x 6StorageStorage Expansion: CompactFlash socketExpansion Bus: PCI/104Other PeripheralsAudio: SM502 chip with line-in/out interfaceDisplayGraphics Controller: SM502 chipDisplay Interface: 15-pin D-Sub connector x 2Resolution: CRT display mode with pixel resolution up to 1024 x 768 Ethernet InterfaceLAN: 3 auto-sensing 10/100 Mbps ports (RJ45)Magnetic Isolation Protection: 1.5 kV built-inSerial InterfaceSerial Standards: 8 RS-232/422/485 ports, software-selectable (8-pin RJ45)Console Port: RS-232 (TxD, RxD, GND), 4-pin pin header output (115200, n, 8, 1)Serial Communication ParametersData Bits: 5, 6, 7, 8Stop Bits: 1, 1.5, 2Parity: None, Even, Odd, Space, MarkFlow Control: RTS/CTS, XON/XOFF, ADDC® (automatic data direction control) for RS-485Baudrate: 50 bps to 921.6 kbps (supports non-standard baudrates; see user’s manual for details)Serial SignalsRS-232: TxD, RxD, DTR, DSR, RTS, CTS, DCD, GNDRS-422: TxD+, TxD-, RxD+, RxD-, GNDRS-485-4w: TxD+, TxD-, RxD+, RxD-, GNDRS-485-2w: Data+, Data-, GNDDigital InputInput Channels: 4, source typeInput Voltage: 0 to 30 VDCDigital Input Levels for Dry Contacts:• Logic level 0: Close to GND• Logic level 1: OpenDigital Input Levels for Wet Contacts:• Logic level 0: +3 V max.• Logic level 1: +10 V to +30 V (COM to DI)Connector Type: 10-pin screw terminal block (4 points, COM, GND) Isolation: 3 kV optical isolationDigital OutputOutput Channels: 4, sink typeOutput Current: Max. 200 mA per channelOn-state Voltage: 24 VDC nominal, open collector to 30 V Connector Type: 10-pin screw terminal block (4 points, GND) LEDsSystem: Power, Ready, Storage, Battery for SRAMLAN: 10M/Link x 3, 100M/Link x 3 (on connector)Serial: TxD x 8, RxD x 8Reset Button: Supports “Reset to Factory Default”Physical CharacteristicsHousing: SECC sheet metal (1 mm)Weight: 1 kgDimensions: 200 x 57 x 120 mm (7.87 x 2.24 x 4.72 in) Mounting: DIN-Rail, wallEnvironmental LimitsOperating Temperature:Standard Models: -10 to 60°C (14 to 140°F)Wide Temp. Models: -40 to 75°C (-40 to 167°F)Storage Temperature:Standard Models: -20 to 75°C (-4 to 167°F)Software SpecificationsOrdering InformationLinuxOS: Linux 2.6.23File System: JFFS2, NFS, Ext2, Ext3Internet Protocol Suite: TCP, UDP, IPv4, IPv6, SNMPv1, ICMP, ARP, HTTP, CHAP, PAP, DHCP, NTP, NFS, SMTP, Telnet, FTP, TFTP, PPP, PPPoEInternet Security: OpenVPN, iptables firewallWeb Server (Apache): Allows you to create and manage web sites; supports PHP and XMLTerminal Server (SSH): Provides secure encrypted communications between two un-trusted hosts over an insecure networkDial-up Networking: PPP Daemon for Linux that allows Unix machines to connect to the Internet through dialup lines, using the PPP protocol, as a PPP server or client. Works with ‘chat’, ‘dip’, and ‘diald’, among (many) others. Supports IP, TCP, UDP, and (for Linux) IPX (Novell).Watchdog: Features a hardware function to trigger system reset in a user specified time interval (Moxa API provided)Application Development Software:• Moxa API Library (Watchdog timer, Moxa serial I/O control, Moxa DI/DO API)• GNU C/C++ cross-compiler • GNU C library• GDB source-level debugging serverQT Embedded: Supports GUI developmentSoftware Protection: Encryption tool for user executable files (based on patented Moxa technology)Windows Embedded CE 6.0OS: Windows Embedded CE 6.0 R3File System: FATInternet Protocol Suite: TCP, UDP, IPv4, IPv6, SNMPv2, ICMP, IGMP, ARP, HTTP, CHAP, PAP, SSL, DHCP, SNTP, SMTP, Telnet, FTP, PPP Web Server (WinCE IIS): Supports ASP, ISAPI Secure Socket Layer (SSL 2/3) and Transport Layer Security (TLS/SSL 3.1) public key-based protocols, and Web Administration ISAPI Extensions Dial-up Networking: Supports RAS client API and PPP, Extensible Authentication Protocol (EAP), and RAS scriptingWatchdog: Features a hardware function to trigger system reset in a user specified time interval. (Moxa API provided)Application Development Software: • Moxa WinCE 6.0 SDK • Moxa API Library• C Libraries and Run-times• Component Services (COM and DCOM) • Microsoft® .NET Compact Framework 3.5• XML, including DOM, XQL, XPATH, XSLT, SAX, SAX2 • SOAP Toolkit Client • Winsock 2.2Available ModelsUC-8430-LX: RISC-based industrial embedded computer with 8 serial ports, 4 DIs, 4 DOs, 3 LANs, CompactFlash, Dual VGA, Audio, 6 USB, Linux OS, -10 to 60°C operating temperature UC-8430-CE: RISC-based industrial embedded computer with 8 serial ports, 4 DIs, 4 DOs, 3 LANs, CompactFlash, Dual VGA, Audio, 6 USB, Windows CE 6.0 OS, -10 to 60°C operating temperatureUC-8430-T-LX: RISC-based industrial embedded computer with 8 serial ports, 4 DIs, 4 DOs, 3 LANs, CompactFlash, Dual VGA, Audio, 6 USB, Linux OS, -40 to 75°C operating temperature UC-8430-T-CE: RISC-based industrial embedded computer with 8 serial ports, 4 DIs, 4 DOs, 3 LANs, CompactFlash, Dual VGA, Audio, 6 USB, Windows CE 6.0 OS, -40 to 75°C operating temperatureAmbient Relative Humidity: 5 to 95% (non-condensing)Anti-vibration: 2 g rms @ IEC-68-2-34, random wave, 5-500 Hz, 1 hr per axisAnti-shock: 20 g @ IEC-68-2-27, half sine wave, 30 msPower RequirementsInput Voltage: 12 to 48 VDC (3-pin terminal block)Power Consumption: 14 W • 270 mA @ 48 VDC • 533 mA @ 24 VDC • 1120 mA @ 12 VDCStandards and CertificationsSafety: UL 60950-1, EN 60950-1, CCC (GB9254, GB17625.1)EMC: EN55022 Class B, EN 55024-4-2, EN 55024-4-3, EN 55024-4-4, FCC Part 15 Subpart B Class BReliabilityAlert Tools: Built-in buzzer and RTC (real-time clock)Automatic Reboot Trigger: Built-in WDT (watchdog timer)MTBF (mean time between failures): 217,675 hrsWarrantyWarranty Period: 5 yearsDetails: See /warrantyNote: The Hardware Specifications apply to the embedded computer unit itself, but not to accessories. In particular, the wide temperature specification does not apply to accessories such as the power adaptor and cables.。

1.(DEC）CSMA/CD 载波监听多路访问/冲突检测2.（IBM）DNA 数字网络体系构3.access 访问4.access control 访问控制5.access matrix 访问矩阵6.account 帐号7.ACL(access control list）访问列表8.acquisition confirm 获取确认9.acquisition request 获取请求10.across certificate 交叉证书11.active 激活12.address size 地址13.ADSL 对称数字用户服务线14.ADSL(asymmetric digital subscriber line) 不对称数字用户15.AFS（andrew file system) 分布式文件系统16.agent 代理17.AH（authentication header 鉴别报头18.ANSI 美国国家标准协会19.ASK（amplitude shift keying) 幅移键控法20.assume 担任21.asymmetric key cryptography 不对称加密22.ATM（ Asynchronous Transfer Mode) 异步传输模式23.attempt limit 最大重传次数24.AUI 连接单元接口25.authenticated 已认证26.authentication 鉴别27.authentication mechanisms 路由控制机制28.authenticatior 身份认证29.awareness 互相感知30.back 前一步31.back off limit 避免算法参数32.BIOS(Basic—input—Output System) 基本输入输出系统33.bridge 网桥34.broadcast storm 广播风暴35.BtoC（B2C）business to consumer 企业对消费者36.BtoG（business to government 企业对政府37.CA(certificate authority) 证书权威机构38.Cable-modem 机顶盒39.catalog 目录手册40.CBX（computerized branch exchange）程控交换ITT 国际电报电话咨询委员会42.CDE(common desktop environment) 通用桌面环境43.CD-R 光盘刻录机44.CD-ROM 光盘驱动器(光驱）45.cease 中止46.cell rate decoupling 信元率去耦48.certificate hierarchy 证书层次结构49.certificate verify 证书检验报文50.CGI(common gateway interface) 公用网关接口51.CHAP（challenge handshake authentication protocol）请求握手验证协议52.chat 闲谈53.chip 芯片54.ciphertext 脱密55.click 点击56.Client/Server 客户机/服务器57.cluster 群集地址58.CMIS/CMIP 公共管理信息服务/协议59.CMISE 公共管理信息服务60.code 密码61.CODEC（Code decoder）编码解码器62.collaboration 协作63.collabration/cooperation 协调和协作方式64.collaspsed backone 折叠式主干网65.co—located 同地协作66.column 行merce 主题patibility 兼容性puter language 计算机语言言70.configuration 配置71.content/message 内容72.cooperation 协同73.coordination 协调74.copy 复制75.CORBA 面向对象的分布系统应用76.COSE(common open software environment) 普通开放软件环境RPC远程过程调用77.COSE(common opensystem environment）通用开放系统环境78.course grained 粗粒度访问控制79.CPU(Central Processing Unit）央处理单元80.cruise 漫游81.CSCL(Computer Supported Cooperative Learning）计算机支持的合作学习82.CSCW(computer supported cooperative work 计算机支持协同工作83.cut 剪切84.data 数据85.data base 数据库86.data confidentiality 保密87.data integrity 数据完整性88.DBMS（Data Base Manage System) 数据库管理系统89.DBS(direct broadcast satellite）直播广播卫星90.DCE（distributed computing environment）分布计算环境91.DDCS 数据库管理和分布数据库连接服务92.debug 调试94.default receive windows) 预设接收窗口95.Demo 演示96.DES（data encryption standard）数据加密标准97.description 描述98.Destination Folder 目的文件夹99.digital signature mechanisms 数据完整性100.distance education/learning 远程教育101.DNS(domain name service）域名服务102.double click 双击103.dummy 哑终端104.edit 编辑cational groupware system 教育组件系统106.EEI（extenal environment interface) 扩展环境接口107.EGP（exterior gateway protocol）扩展网关协议108.Email 电子邮件109.encapsulation 封装110.enciphermant 加密机制111.encopulation security payload 封装安全负载112.encryption 加密113.exception 异常114.execute 执行115.exit 退出116.FCS 帧校验序117.FDM 频分路复用118.find file 文件查寻119.fine grained 细粒度访问控制120.finish 结束121.Firewall 防火墙122.Fixed disk setup program 硬盘安装程序123.Floppy Disk 软盘124.folder 文件夹125.font 字体126.FSK（frequency shift eying）移键控法127.full screen 全屏128.function 函数129.gateway 网关130.graphics 图形131.groupware 群件132.GSM(roup pecial mobile) 移动通讯133.GSS—API 通用安全服务134.GUI(graphical user interfaces ）图形用户界面135.Hard Disk 硬盘136.HDSL（high bit rate）两对双绞线137.Homepage 主页138.HTML hypertext markup language 超文本语言139.HUB 集线器140.hyperlink 超级链接141.hypertext 超文本142.ICCC 国际计算机信会议143.ICMP internet 控制报文协议144.icon 图标145.ICQ 网上寻呼146.IDEA（international data encryption algorithm）国际加密算法147.IE（Internet Explorer) 微软公司的网络浏览器148.IGP(inter gateway protocol) 内部网关连接器协议149.IGP(interior gateway rotocol) 核心网关协议150.IIS（Internet Information server) internet 信息服务151.IKE(Internet key exchange）因特网密钥交换152.image 图像153.IMAP（internet message access protocol) 协议154.integrated model 集成模型155.Inter Frame Gap 帧156.interactive communication 交互通信157.interenterprise computing 企业间的计算158.interface 界面159.Internal web 内部环球网160.Internet 互联网161.internetworked enterprise 互联网上的企业162.interrupt 中断163.inverted 颠倒164.IP（Address）互联网议（地址) 165.IPSEC(IP security) 安全IP166.IPSP(IP security protocol） IP安全协议167.IRC(internet relay chat) 聊天168.ISO 国际标准化组织169.ISP(internet service provider) 服务商170.Jam size 阻塞参数171.KDC(key distribuetion center）密钥分发中心172.keyboard 键盘N 局域网PB（line access protocol balanced）链路访问协议平衡175.LDAP(light weight directory access protocol）轻量目录访问协议176.license 许可(证)177.LIP（serial line）IP 串行IP178.Lynx Mosaic Netscape Hotjava 浏览器179.mail lists 邮件列表180.mainboard 主板181.manual 指南182.MAU 介质连接口183.max frame size 最大帧184.MDI 介质相关接口185.medium grained 中粒度访问控制186.message systems 信报系统187.middleware 中间件188.MIPS PC的处理能力189.Modem（MOdulator-DEModulator）调制解调器190.monitor 监视器191.more flag 标识192.mouse 鼠标193.MSS(maximum segment size) 最大分段尺寸194.MTU(maximum transmission unit）最大传输单位195.multi homed 多宿主196.multicast 组播地址197.multimedia 多媒体198.NAT(network address translation) 网络地址转换199.Navigator 网景公司的浏览器200.NCP(network control protocol) 网络控制协议201.NDIS（network device interface specification) 网络设备接口work—based distance education 远程网络教育203.newgroups 新闻组204.next 下一步205.nonlinear encoding 非线性编程206.non—reputation 防止否认207.notarization mechanisms 公证208.NRZ （Non return to zero) 不归零制209.NSP（name service protocol）域名服务协议210.NTDS（windows NT directory server) windows NT目录服务211.NWC（newwave computingHP) 新波形计算212.object 对象213.OCCA(open cooperative computing architecture）开放合作计算体系结构214.ODI 开放数据链路接口215.OEM 原始设备制造商216.offset 偏移217.On semble stackable 10BASE 可叠加组合型集线器218.online 在线219.OO(Object—Oriented）面向对象220.option pack 功能补丁221.OSF 开放软件中心222.OSF（open software foundation）开放软件基金223.OSPF 开放最短径优先协议224.OSPF（open shortest path control protocol）开放的最短路径优先协议225.PABX(private automatic branch exchange）自动交换机226.PAD 填充字段227.pan 漫游228.PAP（password authentication protocol）密码验证协议229.paragraph 段落230.password 口令231.paste 粘贴232.PBX(private branch exchange) 专用换网233.PCM(pulse code modulation）脉冲代码调制234.PCS 便携式智能终端235.PCT（private communication technology）专网通信技术236.PIN(personal identification number) 个人标识符237.plaintext 明文238.platform 平台239.PMA 物理介质接口240.poll 轮询241.portable 便携242.P-P(Plug and Play) 即插即用243.PPP（Point to Point protocol）点对点协议244.previous 前一个245.print preview 打印预览246.private 保密247.private key 私钥248.profit 利润249.program 程序250.progress 进展251.protocol 协议252.proxy server 代理服务器253.PSK（phase shift keying) 相移键控法254.PtoP（C2C）person to person 个人对个人255.public key 公钥256.PWS（peer web serviceWEB）服务器257.RADSL（rate adaptive DSL）速率自适应DSL 258.RAM（random access memory）随机存储器（内存) 259.RAS 远程访问服务260.realm 域261.redirector 重定向器262.reference monitor 引用监控器263.registration 登录264.release 发布265.remote 远程协作266.repeater 中继器267.Replace 替换268.reply attack 检测重放攻击269.restart 重新启动270.right click 右击271.RIP（routing information protocol) 路由信息协议272.RIP（Routing Information protocol）路由信息协议273.rogue programs 捣乱程序274.ROM(Read Only Memory) 只读存储器275.router 路由器276.row 列277.RR(resource record) 资源记录278.ruler 标尺279.SBS(source route switching）源路由交换网桥280.scable model 可伸缩模型281.SDH 同步数字复用282.SDSL（symmetric DSL) 单对双绞线283.seal 封装284.search 查询285.Search Engine 搜索引擎286.security audit trail 安全审计跟踪287.security domain 安全领域288.security labels 安全标记289.security recovery 安全恢复290.select all 全选291.service pack 服务补丁292.session key 会话层密钥293.SET（secure electrionic transaction）安全电子传送294.settings 设置295.settop box 机顶盒296.setup 安装297.SFD 起始定界符298.SFT（system fault tolerant) 系统容错299.short cut 快捷方式300.sign 签名301.SMI（structer of management information）管理信息结构302.SMT(station management) 管理站303.SMTP（simple mail transfer protocol) 简单邮件传输304.SMTP(simple mail transfer protocol）简单邮件传输协议305.SMTP(simple mail transfer protocol) 简单邮件传输协议306.SNA 系统网络体系结构307.SNMP(simple network management protocol) 简单网管协议308.SNMP（simple network management protocol) 简单网络管理协议309.SNR(signal noise ratio）信噪比310.solttime 时间片311.SONENT（synchronous optical network) 同步光纤网络312.source routing bridge 源路径桥313.SPF(shortest path first）最短路径314.spoofing 欺骗315.SRT 源地址选择透明桥316.SRT(source route transparent) 源路由透明网桥317.status bar 状态条318.STDM 统计时分多路复用319.STLP（secure transport layer protocol) 安全传送层320.style 风格321.symbol 符号322.symmetric key cryptography 对称加密323.table 表324.TDM 时分多路复用325.tele-access 远程访问326.TELEGP（exterior gateway protocol）外部网关连接器协议327.telemedicine 远程医疗328.tele-mentoring 远程辅导329.tele-sharing 远程共享330.Telnet 远程登录331.template 模版332.text 文本333.ticket 凭证334.timestamp 时间标记335.tool bar 工具条336.translation bridging 转换桥接方式337.transparent bridge 传输桥338.trusted function 可信339.TTL(time to live）留存时间340.UDP(user datagram protocol）用户数据报协议341.uninstall 卸载342.UPS(Uninterruptable Power Supply）不间断电源343.URL(Uniform resource locator）同意资源定位符344.URL(uniform resource locator) 统一资源定位er 用户346.video conferencing 视频会议347.view 视图348.virtual classroom 虚拟教室349.virtual electronic commerce city 虚拟电子商城350.virtual electronic mall 虚拟电子商场351.virtual publishing 虚拟出版352.virtual store 虚拟商店353.virus 病毒354.VPN（virtual private networks) 虚拟专网355.WAN 广域网356.WAP（wireless application protocol）无线应用协议357.WDH 波分复用358.Webpage 网页359.website 网站360.Windows NT 微软公司的网络操作系统361.workflow 工作流362.WWW（World Wide Web）万维网363.WYSIWYG(what you see is what you get）所见即所得364.xDSL(x digital subscriber line）数字用户线路365.zoom in 放大366.zoom out 缩小。

The V2401/2402 Series embedded computers are based on the Intel Atom N270 x86 processor, and feature 4 RS-232/422/485 serial ports, 8 RS-232 serial ports, dual Gigabit LAN ports, 6 USB 2.0 hosts, and a CompactFlash socket. The V2401 computer provides VGA, DVI, and LVDS outputs, and the V2402 computer provides both VGA and DVI outputs, making them particularly well-suited for industrial applications such as SCADA and factory automation.The V2401 and V2402 come with 4 RS-232/422/485 serial ports, and the V2401 has an additional 8 RS-232 ports, making them ideal for connecting a wide range of serial devices, and the dual 10/100/1000 Mbps Ethernet ports offer a reliable solution for network redundancy, Front View promising continuous operation for data communication and management. As an added convenience, the V2401/2402 computers have 4 DIs, and 4 DOs for connecting digital input/output devices. In addition, the CompactFlash and USB sockets provide the V2401/2402 computers with the reliability needed for industrial applications that require data buffering and storage expansion.Pre-installed with Linux, Windows CE 6.0, or Windows Embedded Standard 2009, the V2401/2402 Series provides programmers with a friendly environment for developing sophisticated, bug-free application software at a low cost.In addition, the V2402 series also offers -40 to 70°C wide temperature models for harsh environments.V2401/2402 SeriesOverviewAppearancePower/Storage 10/100/1000 Mbps(V2401)Rear ViewHardware SpecificationsComputerCPU: Intel Atom N270 1.6 GHz processorOS (pre-installed): Linux, Windows CE 6.0 or Windows Embedded Standard 2009System Chipset: Intel 945GSE + ICH7-MBIOS: 8 Mbit Flash BIOS, SPI type, ACPI function supportedFSB: 400/533 MHzSystem Memory: 2 GB capacity, 1 GB pre-installed: 1 x 2 GBDDR2-533 200 pin SO-DIMM SDRAM slotUSB: USB 2.0 compliant hosts x 6, type A connector, supports system boot upStorageBuilt-in: 2 GB onboard industrial DOM to store OSStorage Expansion: CompactFlash socket for CF card expansion, supporting CF Type-I/II socket with DMA modeHDD Support: 1 SATA-II connector for HDD expansionOther PeripheralsKB/MS: 1 PS/2 interface supporting standard PS/2 keyboard and mouse through Y-type cableAudio: HD audio, with line-in and line-out interfaceDisplayGraphics Controller: Intel Gen 2.5 Integrated Graphics Engine, 250 MHz core render clock and 200 MHz core display clock at 1.05-V core voltage VGA Interface: DB15 female connectorLVDS Interface: Onboard HIROSE DF13-40DP-1.25 V connector (V2401 only)DVI Interface: DVI-connector (chrontel CH7307 SDVO to DVI transmitter)Ethernet InterfaceLAN: 2 auto-sensing 10/100/1000 Mbps ports (RJ45)Serial InterfaceSerial Standards:• V2401/2402: 4 RS-232/422/485 ports*, software selectable (DB9 male connector)• V2401 only: 8 RS-232 ports (68-pin VHDC connector)*COM1’s pin 9 signal can be set by jumper as N/C (default), +5 V, or +12 V ESD Protection: 4 kV for all signalsSerial Communication ParametersData Bits: 5, 6, 7, 8Stop Bits: 1, 1.5, 2Parity: None, Even, Odd, Space, MarkFlow Control: RTS/CTS, XON/XOFF, ADDC® (automatic data direction control) for RS-485Baudrate: 50 bps to 921.6 kbps (non-standard baudrates supported; see user’s manual for details)Serial LEDs RS-232/422/485RS-232 Serial Port x 8 DI x 4Software SpecificationsSerial SignalsRS-232: TxD, RxD, DTR, DSR, RTS, CTS, DCD, GND RS-422: TxD+, TxD-, RxD+, RxD-, GND RS-485-4w: TxD+, TxD-, RxD+, RxD-, GND RS-485-2w: Data+, Data-, GNDDigital InputInput Channels: 4, source type Input Voltage: 0 to 30 VDC at 25 Hz Digital Input Levels for Dry Contacts: • Logic level 0: Close to GND • Logic level 1: OpenDigital Input Levels for Wet Contacts: • Logic level 0: +3 V max.• Logic level 1: +10 V to +30 V (Source to DI)Isolation: 3 kV opticalDigital OutputOutput Channels: 4, sink typeOutput Current: Max. 200 mA per channelOn-state Voltage: 24 VDC nominal, open collector to 30 VDC Connector Type: 10-pin screw terminal block (4 DI points, 4 DO points, DI Source, GND)Isolation: 3 kV optical isolationLEDsSystem: Power, StorageLAN: 100M/Link x 2, 1000M/Link x 2 (on connector)Switches and ButtonsPower Switch: on/off (front panel)Reset Button: For warm reboot (rear panel)Physical CharacteristicsHousing: Aluminum Weight:• V2401: 2.1 kg • V2402: 2 kg Dimensions:Without ears: 250 x 57 x 152 mm (9.84 x 2.24 x 5.98 in)With ears: 275 x 63 x 152 mm (10.83 x 2.48 x 5.98 in)Mounting: DIN rail, wall, VESAEnvironmental LimitsOperating Temperature:• Standard models: -10 to 60°C (14 to 140°F) • Wide temp. models : -40 to 70°C (-40 to 158°F)Storage Temperature: -40 to 85°C (-40 to 185°F)Ambient Relative Humidity: 5 to 95% (non-condensing)Anti-vibration: 5 g rms @ IEC-68-2-34, random wave, 5-500 Hz, 1 hr/axisAnti-shock: 50 g @ IEC-68-2-27, half sine wave, 11 msPower RequirementsInput Voltage: 9 to 36 VDC (3-pin terminal block for V+, V-, SG)Power Consumption: 26 W (without LVDS output) 2.9 A @ 9 VDC 1.08 A @ 24 VDC 720 mA @ 36 VDCStandards and CertificationsSafety: UL 508, UL 60950-1, CSA C22.2 No. 60950-1-07, EN 60950-1, CCC (GB9254, GB17625.1)EMC: EN 55022 Class A, EN 61000-3-2 Class D, EN 61000-3-3, EN 55024, FCC Part 15 Subpart B Class A Wheeled Vehicles: e-Mark (e4)Green Product: RoHS, CRoHS, WEEEReliabilityAutomatic Reboot Trigger: Built-in WDT (watchdog timer) supporting 1-255 level time interval system reset, software programmable MTBF (mean time between failures): V2401: 238,762 hrs V2402: 228,172 hrsWarrantyWarranty Period: 3 yearsDetails: See /warrantyLinuxOS: Linux 2.6.26, Debian Lenny 5.0File System: EXT2Internet Protocol Suite: TCP, UDP, IPv4, SNMPv1/v2c/v3, ICMP, ARP, HTTP, CHAP, PAP, SSH 1.0/2.0, SSL, DHCP, NTP, NFS, Telnet, FTP, TFTP, PPP, PPPoEInternet Security: OpenVPN, iptables firewallWeb Server (Apache): Allows you to create and manage web sites; supports PHP and XMLTerminal Server (SSH): Provides secure encrypted communications between two un-trusted hosts over an insecure networkDial-up Networking: PPP Daemon for Linux that allows Unix machines to connect to the Internet through dialup lines, using the PPP protocol, as a PPP server or client. Works with ‘chat’, ‘dip’, and ‘diald’, among (many) others. Supports IP, TCP, UDP, and (for Linux) IPX (Novell).File Server: Enables remote clients to access files and other resources over the networkWatchdog: Features a hardware function to trigger system reset in a user specified time interval (Moxa API provided)Application Development Software:• Moxa API Library (Watchdog timer, Moxa serial I/O control, Moxa DI/DO API)• GNU C/C++ compiler • GNU C library • PerlWindows XP EmbeddedOS: Windows Embedded Standard 2009 SP3File System: NTFSInternet Protocol Suite: DHCP, DNS, FTP, HTTP, SNTP, NTP, Telnet, SMTP, SNMPv2, TCP, UDP, IPv4, ICMP, IGMP, IPsec, TAPI, ICS, PPP, CHAP, EAP, PPPoE, PPTP, NetBIOSWeb Server (IIS): Allows users to create and manage websitesSilverlight 2.0: A free runtime that powers rich application experiences and delivers high quality, interactive video across multiple platforms and browsers, using the .NET frameworkRemote Registry Service: Enables remote users to modify registry settings on this computerRemote Desktop: The Terminal Server Remote Desktop component provides remote access for the desktop of a computer running Terminal ServicesWatchdog: Features a hardware function to trigger system reset in a user specified time interval (Moxa API provided)Enhanced Writer Filter: Redirect disk write operations to volatile (RAM) or non-volatile (disk) storageFile Based Write Filter: The File Based Write Filter (FBWF) component redirects all write requests directed at protected volumes to the overlay cache, which records and displays the changes while preserving the protected status of the target volume.Application Development Software: • Moxa API Library• Microsoft .Net Framework 3.5 with SP1• Active Directory Service Interface (ADSI) Core • Active Template Library (ATL), 2.0 • Common Control Libraries • Common File Dialogs• Direct3D, DirectPlay, DirectShow, and Direct show filtersOrdering InformationAvailable ModelsV2401-CE: x86 ready-to-run embedded computer with Intel Atom N270, VGA, LVDS, DVI, Audio, 2 LANs, 12 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, WinCE 6.0V2401-XPE: x86 ready-to-run embedded computer with Intel Atom N270, VGA, LVDS, DVI, Audio, 2 LANs, 12 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, Windows Embedded Standard 2009V2401-LX: x86 ready-to-run embedded computer with Intel Atom N270, VGA, LVDS, DVI, Audio, 2 LANs, 12 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, Linux 2.6V2402-CE: x86 ready-to-run embedded computer with Intel Atom N270, VGA, DVI, Audio, 2 LANs, 4 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, WinCE 6.0V2402-XPE: x86 ready-to-run embedded computer with Intel Atom N270, VGA, DVI, Audio, 2 LANs, 4 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, Windows Embedded Standard 2009, -10 to 60°C operating temperatureV2402-LX: x86 ready-to-run embedded computer with Intel Atom N270, VGA, DVI, Audio, 2 LANs, 4 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, Linux 2.6, -10 to 60°C operating temperatureV2402-T-XPE: x86 ready-to-run embedded computer with Intel Atom N270, VGA, DVI, Audio, 2 LANs, 4 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF, Windows Embedded Standard 2009, -40 to 70°C operating temperatureV2402-T-LX: x86 ready-to-run embedded computer with Intel Atom N270, VGA, DVI, Audio, 2 LANs, 4 serial ports, 4 DIs, 4 DOs, 6 USB 2.0 ports, CF,Linux 2.6, -40 to 70°C operating temperatureOptional Accessories (can be purchased separately) CBL-M68M9x8-100: 8-port RS-232 cable with VHDC connector PWR-24250-DT-S1: Power adaptorPWC-C7US-2B-183: Power cord with 2-pin connector, USA plug PWC-C7EU-2B-183: Power cord with 2-pin connector, Euro plug PWC-C7UK-2B-183: Power cord with 2-pin connector, British plug PWC-C7AU-2B-183: Power cord with 2-pin connector, Australia plug PWC-C7CN-2B-183: Power cord with 2-pin connector, China plug FK-75125-01: Hard disk installation package (for SSD)DK-DC50131-01: DIN-Rail mounting kit Package Checklist• V2401 or V2402 embedded computer • Terminal block to power jack converter • PS2 to KB/MS Y-type cable• Wall mounting kit• Documentation and software CD or DVD • Quick installation guide (printed)• Warranty card• Mapi32 Libraries• Message Queuing (MSMQ) Core• Microsoft Visual C++ Run Time Libraries• Power Management dynamic-link library• RPC• Windows API, Script Engines, and WMIWindows Embedded CE 6.0OS: Windows Embedded CE 6.0 R3File System: FAT (for on-board flash)Internet Protocol Suite: TCP, UDP, IPv4, SNMPv2, ICMP, IGMP, ARP, HTTP, CHAP, PAP, SSL, DHCP, SNTP, SMTP, Telnet, FTP, PPPWeb Server (WinCE IIS): Supports ASP, ISAPI Secure Socket Layer (SSL 2/3) and Transport Layer Security (TLS/SSL 3.1) publickey-based protocols, and Web Administration ISAPI ExtensionsDial-up Networking: Supports RAS client API and PPP, Extensible Authentication Protocol (EAP), and RAS scriptingFile Server: Enables remote clients to access files and other resources over the networkWatchdog: Features a hardware function to trigger system reset in a user specified time interval. (Moxa API provided)Application Development Software:• Moxa WinCE 6.0 SDK• Moxa API Library• C Libraries and Run-times• Component Services (COM and DCOM)• Microsoft® .NET Compact Framework 2.0• XML, including DOM, XQL, XPATH, XSLT, SAX, SAX2• SOAP Toolkit Client• Winsock 2.2。

EVENT GUIDEThe FoxHalf Marathon, Marathonand UltraSaturday 27th May 2023CLICK FOR ENTRY LIST Included:Bib numberBaggage LabelTiming ChipRACE PACK COLLECTIONIf you entered after this date, or haven't received your race pack in the post, please collect it from the Event Village at The Bury's Field in Godalming.Allow plenty of time to then travel to your race start location. (Train times from Godalming to West Clandon (HM start) and Worplesdon (Marathon start) can be found in the travel section below)Attach your number to the front of your shirt (we recommend safety pins or magnets).Your timing chip will be attached to the bottom of your race bib, tear this off and slot into your shoe laces.ultra- 7:00amMarathon- 9:00amHalf marathon: 10:00amStart Times:minutes to fill out thebrief runner Informationform on the back of yourbib.This will help us in caseof an emergency!Step 1Step 2Step 3Step 4**IF YOU’VE ENTERED PRIOR TO THE 17TH MAY YOU CAN EXPECT TO RECEIVE YOUR RACE PACK IN THE POST**RACE STARTWe will have a briefing 15 minutes prior to the start ofeach race at each respective start line.From here you will be called to the start.There will be 4 Half Marathon waves based offestimated finish time, which will go off every 5 minutes.The course will be marked out by signs, Trail Flags and tape.For marking turns, there will be tape hanging on the gate/tree/rock located on the side of the trailtowards which you will be turning.If you haven’t seen a flag, tape or sign for more than a few hundred metres, turn around and re-findthe course.There are stiles on route so please be cooperative and understanding of fellow participants shouldthere be any queues at these.There are ROAD CROSSINGS on route, please be careful and follow marshals' instructions particularlyat these points.There are also a few very steep downhill sections. Please walk if you need to and take your time overthese sections.The whole route is open to members of the public, please be mindful of this at all times.There will be arrow signs at key locations only, and there will be no distance markers.We will have marshals positioned at key points to help you find your way.Please familiarise yourself with the route map.You must have the GPS track downloaded to your Mobile phone and/or GPS device and ensure youare familiarised with the route prior to setting off.Having the GPX is a requirement for the Ultra and Marathon, and highly recommend for the HalfMarathon.DURING THE RACECLICK FOR ULTRA GPXCLICK FOR MARATHON GPXCLICK FOR HALF MARATHON GPXRoutes can be opened on , garmin & all major tracking devicesRunner 1 will go from the Ultra start to AS2 @ Jolly Farmer Pub Runner 2 will go from AS2 to AS4 @ West Clandon Village Hall Runner 3 will go from AS4 to the Finish at Burys FieldsEach team member has been assigned an individual bib number. Your team time will be calculated using the start time of your first runner and the finish time of your last runner.If you would like to record the separate leg times for each team member, please do so on your personal devices.Team results will be ranked based on total time only.Please arrange personal logistics accordingly.TEAM RELAYSREFRESHMENTS & AID STATIONS In an effort to reduce waste, this race is bottle-free, meaning you’ll need to pack your own cup for fluids at aid stations during the race. We suggest that you bring either a hand flask, running vestwith water bottles or a collapsible cup.Please bring your own water and drinking vessel to the event.There will be a water station within the event village where you can fill up your own bottles.THERE WILL BE NO BOTTLED WATER GIVEN OUT ON THE COURSES, YOU CAN REFILL YOUR OWNBOTTLES/CUPS AT THE AID STATIONS AND EVENT VILLAGE.There are 5 aid stations along the route. These will all provide water, gels and some snacks. We will also have marquees, chairs and foil blankets just in case the weather turns. We will have marshals and medics at all of these points, please inform a member of staff if you have any issues along theway.We recommend staying hydrated in the lead up to the event.Please ensure you carry all litter with you, and nothing is left out on the course. This includes allwater bottles, gel and food wrappers.REQUIRED KITCUT OFF TIMESRECOMMENDED KIT LIST (ALL DISTANCES);Trail Running Shoes Running Vest or Belt Sunglasses Suncream Food & Water (to be re-filled at Aid Stations)Mobile phone and/or GPS device (fully charged) REQUIRED KIT LIST (ULTRA DISTANCE ONLY);Hooded waterproof jacket First aid kit (to include minimum blister plasters, bandage and tape to secure dressing)Spare long-sleeved base layer top Hat Whistle Mobile phone and/or GPS device (fully charged)Emergency foil blanket or bivi bag Emergency food & drink Please contact the medical team if you or any other participants require medical treatment out on the course.Theirnumberis************. Please plan for being outside for a prolonged period of timein unpredictable weather.There is a 12hr cut off on completing this race.Each Aid station has it's own cut off time.If you have not reached an aid station by therequired time, you will officially be removed fromthe race. We will have a member of staff walkingthe course and packing down each section at therespective cut off times.Should you be cut off, you are then welcome towalk with our staff, who can ensure you reach theevent village safely, or continue on entirely at yourown risk.Aid station 1- 09:15amAid station 2- 11:00amAid station 3- 12:35pmAid station 4- 14:40pmAid station 5- 17:00pmFinish - 19:00pmRT2321 Code valid until 28.05.23COURSE MAPAFTER THE RACEPlease continue through the finish to collect your medal and goodies!Marathon Startrelay leg 2Half Marathon Startrelay leg 3Ultra Start/ relay leg 1All finishSPECTATORSCOFFEETOILETS There will be a coffee van located in theevent village at the Bury's Field servingsnacks and hot drinks.The Jolly Farmer (marathon start) will alsobe serving refreshments.We recommend spectators car share wherepossible, and park at the Bury's Field toavoid any congestions for runners gettingto the marathon and half marathon starts.There will be portable toilets available at each start line. Ultra and marathon runners will pass throughthe later start lines so will have access tothese on route. There will be no toilets on thehalf marathon section of the course.Please limit the number of belongings you bring to the event. There will be a bag drop marquee at each start line.Please leave any belongings at the bag drop by your start line in a sealed bag,with your baggage label clearly visible.Your baggage tag is attached to your race number.Tear it off and attach to your bag.We will transport this to the finish linefor you.Collect your bag after your race fromthe Bury's Field bag drop.BAGGAGETRAVELUltramarathonRegistration/ Start: The Bury's Field - The Bury's, Godalming GU7 1HR Parking: Godalming Crown Court Car Park (300 spaces available). We would recommend using theRingo app to update your hours if needed, prices are from £8 for 6 hours, up to £20 for 10 hours.MarathonRegistration: The Bury's Field - The Bury's, Godalming GU7 1HRStart: The Jolly Farmer, Burdenshott Road, Worplesdon, Guildford GU3 3RN Transport: Trains run direct from both Godalming and Guildford, to Worplesdon. Please check train times at and it is a 20-minute walk to The Jolly Farmer from Worplesdon trainstation.Parking: LIMITED- CAR SHARING IS ESSENTIAL where possible. Please don’t use the Jolly Farmer carpark (approximately 20 spaces available).We recommend parking in Godalming, then getting the train to Worplesdon for the start. Parking is available in the Godalming Crown Court Car Park. We would recommend using the Ringo app to update your hours if needed, prices are from £8 for 6 hours, up to £20 for 10 hours.Bag drop: one small bag per participant (remember to attach your baggage tag). This will betransported to the finish at Godalming for you.Half MarathonRegistration: The Bury's Field - The Bury's, Godalming GU7 1HRStart: West Clandon Village Hall Playing Field, West Clandon, Guildford GU4 7TN.Public Transport: If you plan to leave your car at the finish in Godalming, it will take 30 mins on the train to Clandon (via Guildford). The 9:12am train from Godalming is the latest train that will arriveahead of the 10am start.Parking: West Clandon Village Hall has no parking, there is a limited parking available for us to use at Clandon Train station car park (91 spaces available). CAR SHARING IS ESSENTIAL where possible. We would recommend using the Ringo app to update your hours if needed, prices are from £8 for 6 hours,up to £20 for 10 hours.Bag drop: one small bag per participant (remember to attach your baggage tag). This will betransported to the finish at Godalming for you.As with all sporting events, please expect there to be traffic on arrival.Due to limited spaces, CAR SHARING IS ESSENTIAL or getting dropped off by family/friends where possible. There is plenty of parking at the finish line at Bury Fields.If using the What3Words app, please use the following words for each start location:The Bury's Field (Ultra)- souk.pencil.criedThe Jolly Farmer (Marathon) - bands.bliss.year West Clandon Village Hall Playing Fields (Half Marathon) - trucks.likely.courierRESULTS AVAILABLE AT PICTURESWe will have a photographer taking a few snaps of the race, which will be made available on our photos pageafter the race.SOCIAL MEDIAFor updates leading up to the race, please check out our Twitter @runthroughuk and use the hashtag #Runthroughuk in thebuild-up to the race.If you want to talk all things running before and after the eventjoin our RunThrough Chat group on Facebook.If you #RunThroughUK and #RunThroughTrails on Instagram with your race day collages, the best ones will feature on ourpage!Click the icons to visit our pages!Alternatively, purchase a RunThrough T-shirt or Hoody to celebrateyour race with us!These Unisex products are comfortable, and designed with your daily workouts inmind.These will probably be your favourite pieces of kit. Made to keep you comfortableand fresh on your run, and warm in the winter months.Any RunThrough Tees and Hoodies purchased with your race entry or via thefollowing links will be available to collect on the day from the kit stall at Bury's Field.PURCHASE A T-SHIRT PURCHASE A HOODYPURCHASE AN EVENT T-SHIRTF.A.Q'SIs the event chip timed?Yes!What is the minimum age for this event?17(All RunThrough races follow the minimum ages of 11yrs for 5k, 15 for 10k & 17 for Half Marathons +)Is there a time restriction to complete the race?Yes,thereisa12hrcutofonthisrace,********************************************.ukifyou plan to take more than 12hrs to complete your race as we may need to make special arrangementsaround the course and event village.I can no longer make the event, can I get a refund?We are sadly unable to refund or transfer your entry within 14 days of the race as your race pack and everything associated with your entry fee including your medal, and post race goodies have already been paid for by this time. We'd love for you to run virtually and we can post out your medaland goodies!Can I transfer my entry to a friend or swap distance?Yes, we can happily swap the names and details associated with a booking. Please email in with your order number, and the new runners' name, email, address and date of birth. Or alternatively, visit the information desk on the morning of the race to do this.Will there be a water station on the course?There will be 5 aid stations along the route, where you can re-fill bottles/cups. However, there won'tbe any bottles provided.Am I allowed to wear headphones?Headphones are not permitted, unless bone conducting. Should you choose to wear these, we ask you keep the volume low in order to remain aware of your surroundings at all times and can hearany marshal instructions during the race.When will I get the add on RTKit I ordered with my entry?This will be available to collect at the RTKit Stall on the day. Please have your email confirmationready to show to our staff.How should I get to the event?We highly recommend using public transport where possible. If driving, please try to park inGoldaming and commute or car share to your start line.Where is the best place to spectate?We advise staying within the event village to be sure you catch the finish! You're more than welcome to walk around the route however if you're following the race course route, we askspectators to be respectful of other runners on the paths.Will there be a prize giving?The top 3 male and female participants can expect an email reward in the week following the race. There will be no presentation on the day. However check out our podium and photo wall to get yourcelebratory pictures!Supportedby...。