SPAN_147_5_10_2016

elementtable⽰例1<template>2<div>3<el-form ref="form" :model="form" label-width="80px">4<el-col :span="8">5<el-form-item label="活动名称" prop="name">6<el-input v-model="" style="width:300px"></el-input>7</el-form-item>8</el-col>9<el-col :span="8">10<el-form-item label="城市" prop="city">11<div @click="centerDialogVisible = true">12<el-input v-model="form.city" style="width:300px"></el-input>13</div>14<el-dialog15:show-close=false16:visible.sync="centerDialogVisible"17 width="30%"18 height="500px"19 center>20<el-checkbox :indeterminate="indeterminate" v-model="ischeckAll" @change="handleCheckAllChange">全选</el-checkbox>21<div style="position: relative;left:15px;height:300px;overflow: auto;">22<div class="table-body" v-for="(partition,partitionIndex) in distributorsInfo" :key="partitionIndex">23<div class="width185"><p>{{ partition.partitionName }}</p></div>24<span class="width265">25<el-checkbox style="width:20%" v-for="country in partition.country" v-model="country.selected" @change="handleCheckedCountryChange(partitionIndex,country.id,$event)" :label="country" :key="country.id" 26</span>27</div>28</div>29</el-dialog>30</el-form-item>31</el-col>32<div style="height:60px"></div>33<el-form-item>34<el-button type="primary" @click="onSubmit">查询</el-button>35<el-button @click="resetForm('form')">重置</el-button>36</el-form-item>37</el-form>38<div style="height:20px"></div>39<el-button :style="{background:shift?'gray':'white'}" @click="shiftButton">shift</el-button>40<el-button style="background:white;" @click="colorButton('white')"></el-button>41<el-button style="background:blue;" @click="colorButton('blue')"></el-button>42<el-button style="background:green;" @click="colorButton('green')"></el-button>43<el-button style="background:gray;" @click="colorButton('gray')"></el-button>44<el-button style="background:yellow;" @click="colorButton('yellow')"></el-button>45<div style="height:20px"></div>46<el-table47@selection-change="changeFun"48 @row-click="clickRow"49 ref="moviesTable"50 :data="tableData"51 :show-header=true52border53 highlight-current-row54 :row-class-name="tableRowClassName"55 style="width: 100%">56<el-table-column57type="selection"58 width="55">59</el-table-column>60<el-table-column61fixed62 prop="date"63 label="⽇期"64 width="150">65</el-table-column>66<el-table-column67prop="name"68 sortable69 label="姓名"70 width="120">71</el-table-column>72<el-table-column73prop="province"74 label="省份"75 width="120">76</el-table-column>77<el-table-column78prop="city"79 label="市区"80 width="120">81</el-table-column>82<el-table-column83:show-overflow-tooltip=true84prop="address"85 label="地址"86 width="300">87<template slot-scope="scope">8889<div :style="{background:scope.row.color}">90 {{ scope.row.address }}91</div>92</template>93</el-table-column>94<el-table-column95prop="zip"96 label="邮编"97 width="120">98</el-table-column>99<el-table-column100fixed="right"101 label="操作"102 width="100">103<template slot-scope="scope">104<el-button @click="handleClick(scope.row)" type="text" size="small">查看</el-button>105<el-button type="text" size="small">编辑</el-button>106</template>107</el-table-column>108</el-table>109<div style="height:20px"></div>110<el-pagination111@size-change="handleSizeChange"112 @current-change="handleCurrentChange"113 :current-page="currentPage4"114 :page-sizes="[100, 200, 300, 400]"115 :page-size="100"116 layout="slot, prev, pager, next, jumper,sizes"117 :total="40000">118<span>1-100 共200条</span>119</el-pagination>120</div>121</template>122123<script>124 export default {125 data() {126return {127 ischeckAll:false,//⼀级全选状态128 indeterminate:false,//⼀级⾮全选状态129 distributorsInfo:[130 { partitionName:'江西',131 country:[132 { id: "1",fieldName: "南昌",selected: false},133 { id: "2",fieldName: "九江",selected: false},134 { id: "3",fieldName: "鹰潭",selected: false},135 { id: "4",fieldName: "宜春",selected: false},136 { id: "9",fieldName: "抚州",selected: false},137 { id: "10",fieldName: "吉安",selected: false},]138 },139 { partitionName:'⼴东',140 country:[141 { id: "5",fieldName: "深圳",selected: false},142 { id: "6",fieldName: "惠州",selected: false},]143 },144 { partitionName:'湖南',145 country:[146 { id: "7",fieldName: "长沙",selected: false},147 { id: "8",fieldName: "常德",selected: false}]148 }149 ],150 checkAll: false,151 checkedCities: [],//被选中的数据city152 isIndeterminate: false,153 centerDialogVisible: false,154 multipleSelection:[],//被选中的数据155 currentPage4: 4,156 shift:false,157 form: {158 name: '',159 region: '',160 date1: '',161 date2: '',162 delivery: false,163 type: [],164 resource: '',165 desc: '',166 city:""167 },168 tableData: [{169 color:"",170 date: '2016-05-03',171 name: '王⼩虎',172 province: '上海',173 city: '普陀区',174 address: '上海市普陀区⾦沙江路 1518',175 zip: 200333176 }, {177 color:"",178 date: '2016-05-01',179 name: '⼩虎',180 province: '上海',181 city: '普陀区',182 address: '上海市普陀区⾦沙江路 1518 弄',183 zip: 200333184 }]185 }186 },187 methods: {188 handleCheckAllChange(e){//⼀级change事件189this.ischeckAll = e190if(e == true){191this.indeterminate = false192for(var i=0,len=this.distributorsInfo.length; i<len; i++){ //⼆级全选反选不确定193this.distributorsInfo[i].selected = e194for(var j=0,len1=this.distributorsInfo[i].country.length; j<len1; j++){195this.distributorsInfo[i].country[j].selected = e196 }197 }198 }else{199this.indeterminate = false200for(var i=0,len=this.distributorsInfo.length; i<len; i++){ //三级全选反选不确定201this.distributorsInfo[i].selected = e202for(var j=0,len1=this.distributorsInfo[i].country.length; j<len1; j++){203this.distributorsInfo[i].country[j].selected = e204 }205 }206 }207 },208 handleCheckedCountryChange(topIndex, sonId, e){//三级change事件209this.form.city = "";210var checkCount = 0;//选中的211var unChickCount = 0;//未选中的212var distributorsInfo_total = 0;//总数213for(var ii=0;ii<this.distributorsInfo.length;ii++){214 distributorsInfo_total = distributorsInfo_total + this.distributorsInfo[ii].country.length; 215for(var jj = 0; jj < this.distributorsInfo[ii].country.length; jj++){216if(this.distributorsInfo[ii].country[jj].id == sonId){217this.distributorsInfo[ii].country[jj].selected = e;218 }219if(this.distributorsInfo[ii].country[jj].selected == true){220var tem = this.distributorsInfo[ii].country[jj].fieldName;221if("" == this.form.city){222this.form.city = tem;223 }else{224this.form.city = this.form.city + "," + tem;225 }226 checkCount++;227 }else{228 unChickCount++;229 }230 }231 }232if(checkCount == distributorsInfo_total){233this.ischeckAll = true234this.indeterminate=false235 }else if(unChickCount == distributorsInfo_total){236this.ischeckAll = false237this.indeterminate=false238 }else{239this.ischeckAll = false240this.indeterminate=true241 }242 },243244 onSubmit() {245 console.log('submit!');246 },247 resetForm(formName) {248this.$refs[formName].resetFields();249 },250 handleClick(row) {251 console.log(row);252 },253 handleSizeChange(val) {254 console.log(`每页 ${val} 条`);255 },256 handleCurrentChange(val) {257 console.log(`当前页: ${val}`);258 },259 clickRow(row){//点击单元格选中该⾏260if(this.shift){261this.$refs.moviesTable.toggleRowSelection(row)262if(this.multipleSelection.length > 2){263this.$refs.moviesTable.clearSelection();//清除选中项264this.$refs.moviesTable.toggleRowSelection(row)265 }266if(this.multipleSelection.length == 2){267var tableDataArray = this.$refs.moviesTable.tableData;//当前表格的数据268var start = tableDataArray.indexOf(this.multipleSelection[0]);269var end = tableDataArray.indexOf(this.multipleSelection[1]);270var newArray = [];271if(start>end){272 newArray = tableDataArray.slice(end+1,start);273 }else{274 newArray = tableDataArray.slice(start+1,end);275 }276if(newArray.length>0){277for(var i=0;i<newArray.length;i++){278this.$refs.moviesTable.toggleRowSelection(newArray[i])279 }280 }281 }282283284 }285 },286 tableRowClassName({row, rowIndex}) {//如果该⾏选中则⾼亮287if (this.multipleSelection.indexOf(row)!=-1) {288return 'warning-row';289 }290return '';291 },292 changeFun(val){//全选事件293this.multipleSelection = val;294 },295 colorButton(a){//修改列的颜⾊296if(this.multipleSelection.length>0){297for(var i=0;i<this.tableData.length;i++){298if(this.multipleSelection.indexOf(this.tableData[i])!=-1){299this.tableData[i].color=a;300 }301 }302this.$refs.moviesTable.clearSelection();//清除选中项303 }304 },305 shiftButton(){306this.shift=!this.shift;307 }308 }309 }310</script>311<style>312.el-table .warning-row {313 background: oldlace;314 }315 .el-table .success-row {316 background: #f0f9eb;317318 }319 .el-dialog--center .el-dialog__body{320 padding: 0px 20px 30px;321 }322 .el-dialog--center{323 position: absolute;324 right: 450px;325 top: 5px;326 }327</style>View Code。

GLOBAL CERTIFICATION FORUM (GCF) LtdWork Item DescriptionField Trial requirements for GSM/GPRS/EGPRSReference: GCF WI-108Version: v3.1.0Date: 29.01.2010Document Type: Technical1 ScopeThe scope of this work item covers the renewal of Field Trial requirements for GSM/(E)GPRS including SIM/USIM.2 DescriptionThis Work Item description has been created to handle the renewal of GSM/(E)GPRS including SIM/USIM Field Trial requirements.3 JustificationField Trials are an integral part of the GCF scheme and therefore are required to evolve in conjunction with the implementation of associated mobile technology.4 Supporting companiesCSR, Ericsson Mobile Platforms, Motorola, NEC, Nokia, O2 UK, Orange France, RIM, Sony Ericsson, Vodafone Group, Broadcom, TIM, TeliaSonera5 RapporteurMarc OuwehandNokia CorporationTelephone: +358 40828 0908E-mail: marc.ouwehand@6 Affected bandsNote: GSM 850 and 1900 are outside the GCF certification scheme.7 Core Specifications8 Test SpecificationsNote: The operator expectations on each identified Field Trial Requirement can be derived from the GSMA PRD DG 11 ‘DG Field and Lab Trial Guidelines’, It is emphasised that DG.11 is only a guideline and that manufacturers may use their own test procedures.9 Work Item Certification Entry9.1 Work Item Certification Entry Criteria (CEC)N/A.9.2 Target Work Item Certification Entry Date / GCF-CC versionN/A10 Work Item Freeze and Completion CriteriaDuring the next PRP review this WI should be set to ‘Completed’.11 Conformance Test RequirementsN/A12 IOP Test RequirementsN/A13 Field Trial RequirementsFor BSS/MSC network dependent Field Trial Requirements (BM)For GPRS network dependent Field Trial Requirements (GPRS)For SIM/UICC dependent Field Trial Requirements (2GSIM)For SMSC dependent Field Trial Requirements (SMS)For Network/SIM/UICC/Client independent Field Trial Requirements (NI)14 Periodic Review PointsThe next PRP-review for this WI will be held at the t FT AG meeting during Q3 2010.15 Other commentsThe information below is coming from both WI’s, which during the FT AG #15 meeting has been merged into this WI.Former WI-028 Comments:- During the SG 25 meeting a concern was raised about the approval of this Work Item as well as the CR’s attached to this Work Item via 10 day rule process. The SG made clear that this approval process is not conform the official GCF rules. The SG supposed to approve this Work Item and CR’s. During the SG 25 meeting document S-06-053 was created and approved by the SG to give a mandate for approval via 10 day rule. This mandate applies only for CR’s concerning this Work Item.- Due to the introduction of this Work Item and Work Item 27 (HSDPA) it is required that GCF operators re-declare their status as GCF Qualified operator by using the new Annex B, which should be available in thePRD GCF-OP released in April 2006. The CR for this renewed Annex B is a part of this Work Item and will be uploaded as CR FT-06-022r4During the teleconference of 20.3.2006 there was agreed that an agenda point will be made for FT AG #04,3-4 May 2006 concerning re-declaration.- During the teleconference of 20.3.2006, there was noticed that the mandate for this Work Item didn’t include the EGPRS feature. Therefore it was agreed that the EGPRS topic will be put on the agendafor FT AG #04.Mr. M. Ouwehand (Nokia) will take care that there will be a discussion/input documentavailable for the FT AG #04.When WI-028 has been activated there was agreed to put a ‘transition period’ in place, due the fact that bythat time there were no enough FTQ ANNEX B documents available.During the FT AG #08, 2-3 May 2007, there has been agreed that the ‘transition period’ is ended by therelease of GCF-CC 3.26.0.Former WI-048 Comments:It was suggested during the FTAG meeting discussions of this WI that the most effective method ofadministrating and executing the EDGE classified test requirements while maintaining confidence in GCF FTfor both GPRS and EDGE networks is:a) Introduce a new classification called EDGEb) Copy all existing GPRS requirements to the EDGE Requirements.c) FT on GPRS NW Configurations do not need to perform the EDGE classified test requirementsd) FT on EDGE NW Configurations do not need to perform the GPRS classified test requirements.When this WI meet the CEC and therefore will be activated, it should be considered by FT AG to merge the EDGE Field Trial requirements table into the existing GPRS Field Trial requirements table as has been done with PS, HSDPA & EUL requirements table merge.The CR’s to GCF-CC related to this Work Item need to be submitted at the same time that CR to activate this Work item will be submitted.16 Document Change Record。

Migrating to a two-node switched cluster with CN1610cluster switchesIf you have an existing two-node switchless cluster environment that uses cluster network switches,you can migrate to a two-node switched cluster environment using CN1610cluster network switches.The procedure you use depends on whether you have two dedicated cluster-network ports on each controller (as required on most systems)or a single cluster port on each controller(a supported option on N3150,N3220,and N3240storage systems).About this taskThere are two migration options available:v Migrating from a switchless cluster to a switched CN1610cluster environmentv Migrating from a switchless cluster(systems with a single cluster-network connection)Migrating from a switchless cluster to a switched CN1610cluster environmentIf you have an existing two-node switchless cluster environment,you can migrate to a two-node switched-cluster environment using CN1610cluster network switches.Before you beginTwo-node switchless configuration:v The two-node switchless configuration must be properly set up and functioning.v The nodes must be running Data ONTAP8.2or later.v All cluster ports must be in the up state.v All cluster LIFs must have be in the up state and on their home ports.CN1610cluster switch configuration:v The CN1610cluster switch infrastructure be redundant and fully functional on both switches.Refer to the IBM N series support website to ensure you have the latest RCF and FASTPATH versions on your switches.v Management network connectivity on both switches.v Console access to the cluster switches.v Necessary cabling for the node-to-switch and switch-to-switch connections has been completed.Twinax or fiber is supported for the CN1610switch.For more information on cabling,see Installation and Setup Instructions of your storage system and Clustered Data ONTAP Switch Setup and Configuration Guide.v Inter-Switch Link(ISL)cables are connected to ports13through16on both CN1610switches.v Initial customization of both CN1610switches has been completed.About this taskThis procedure migrates nodes in a two-node switchless environment into a two-node switched environment.The examples in this procedure use the following switch and node nomenclature:v cs1and cs2are the CN1610switches.v clus1and clus2are the cluster logical interfaces(LIFs).v The names of the Vservers are node1and node2.v The cluster::*>prompt indicates the name of the cluster.v The cluster ports used in this procedure as an example are e1a and e2a.Refer to the Installation and Setup Instructions of your storage system for the supported cluster ports.Procedure1.Disable all node-facing ports on both new cluster switches cs1and cs2.Do not disable the ISL ports.e the show port channel command to verify that the ISL and the physical ports on the ISLbetween the two CN1610cluster switches cs1and cs2are up.Results for the cs2switch:2e the show isdp neighbors command to display the list of neighboring devices.e the run*cdpd show-neighbors to ensure that each cluster port is connected to thecorresponding port on its partner cluster node.This example verifies that cluster ports e1a and e2a are connected to the same port on its cluster partner node:3e the network interface show-role cluster to ensure that all cluster LIFs are up ande the network interface modify command and set the auto revert parameter to false on clus1e the network interface migrate command on the console of each node to migrate clus1to port8.Shut down cluster port e1a on both nodes with the network port modify command.Verify the portstatus with the network port show command:49.Disconnect the cable from e1a on node1.Connect e1a on node1to port1on cs1,using theappropriate cabling supported by the CN1610switches.For more information on cabling,seeInstallation and Setup Instructions of your storage system and Clustered Data ONTAP Switch Setup and Configuration Guide.10.Disconnect the cable from cluster port e1a on node2.Connect e1a to port2on cs1,using theappropriate cabling supported by CN1610switches.11.12.13.14.Revert clus1(which was previously migrated)on both nodes back to e1a with the network interfacee the network interface show command to ensure that all cluster LIFs are up and operational anddisplay true in the Is Home column:516.17.On the console of each node,use the network interface migrate command to migrate clus2to porte the network port modify to shut down cluster port e2a on both e the network port19.Disconnect the cable from e2a on node1.Connect e2a on node1to port1on cs2using theappropriate cabling supported by CN1610switches.20.On node2,disconnect the cable from cluster port e2a.Connect e2a to port2on cs2,using theappropriate cabling supported by CN1610switches.21.622.23.24.On all nodes,revert clus1(which was previously migrated)back to e1a with the network interfacee the network interface show command to verify that all of the interfaces display true in the Ise the show isdp neighbors command to verify that both nodes have two connections to eachswitch.7e the run*cdpd show-neighbors command to ensure that each cluster port is connected correctlyto each cluster switch.This example verifies that cluster ports e1a and e2a are connected to the corresponding ports on28.29.e the network interface modify command and set the auto revert parameter to true on clus131.For more information,see Clustered Data ONTAP Switch Setup and Configuration Guide.Migrating to a two-node switched cluster(systems with a single cluster-network connection)If you have N3150,N3220,and N3240systems in an existing two-node switchless cluster in which each controller has a single,back-to-back10-GbE connection for cluster connectivity,you can use the switchless-cluster networking option and replace the direct back-to-back connectivity with switch connections.This is a non-disruptive procedure.Before you beginv Two cluster connections are required to migrate from a switchless configuration to a switched configuration.8v The cluster must be healthy and consist of two nodes connected with back-to-back connectivity.The nodes must be running Data ONTAP8.2or later.v The switchless cluster feature cannot be used with more than two nodes.v All cluster ports must be in the up state.About this taskThis procedure removes the direct cluster connectivity in a switchless environment and replaces each connection to the switch with a connection to the partner node.Procedure1.Check the cluster status of the nodes by entering the following command at the system console ofeither node:cluster show2.Check the status of the by entering the following command at the system console of either node:storage failover show3.Enter the following command at either node's prompt to change to the advanced privilege level:set-privilege advancedYou can respond y when prompted to continue into advanced mode.The advanced mode prompt appears(*>).4.Verify that the current state of the switchless cluster is true and then disable switchless-cluster mode:network options switchless-cluster modify-enabled false5.Enter the following command to return to the admin privilege level:set-privilege admin6.Take over the target node by entering the following command:storage failover takeover-ofnode target_node_nameIt does not matter which node is the target node.When it is taken over,the target nodeautomatically reboots and displays the Waiting for giveback...message.The active node is now serving data for the partner(target)node that has been taken over.7.It a node is impaired,wait at least two minutes after the takeover of the impaired node to ensurethat the takeover completed successfully.8.With the target node showing the Waiting for giveback...message,shut it down.The method youuse to shut down the node depends on whether remote management via a Service Processor(SP)is used.Is the SP configured?Then...Yes Log in to theimpaired node's SP and enter the followingcommand:system power off.9Is the SP configured?Then...No At the impaired node's prompt,press Ctrl-C andrespond Y to halt the node.9.On each controller,disconnect the cable that connects the10G cluster port to the switchless cluster.10.Connect the10-GbE cluster port to the switch on both controllers.Verify that the10-GbE clusterports connected on the switch are configured to be part of the same VLAN.If you plan onconnecting the cluster ports on each controller to different switches,verify that the ports on which the cluster ports are connected on each switch are configured for the same VLAN and that trunking is properly configured on both switches.11.Enter the following command to give back storage to the target node:storage failover giveback-ofnode node212.Enter the storage failover show-giveback command to monitor the progress of the givebackoperation.13.After the giveback operation is complete,enter the storage failover show command to confirm that14.Verify that the cluster port LIFs are operating correctly:15.Check the cluster status of the nodes by entering the following command at the system console ofeither node:cluster show16.Verify cluster connectivity with the cluster ping-cluster local command:a.Enter the following command at either node's prompt to change to the advanced privilege level:set-privilege advancedYou can respond y when prompted to continue into advanced mode.The advanced mode prompt appears(*>).b.Enter the following command to ping the cluster ports:cluster ping-cluster localThe command output should show connectivity between all cluster ports.c.Enter the following command to return to the admin privilege level:set-privilege admin10©Copyright IBM Corporation2013.US Government Users Restricted Rights–Use,duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.SC27-6298-00。

招标人12021-08-03 22:29:50,635 [0x000022e4] <sgucscsdk>: INFO SysLog - ---------- Win32 x86_64 3.5 3.5.0.125 ----------2021-08-03 22:29:50,635 [0x000022e4] <sgucscsdk>: DEBUG SysLog - work directory : C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK2021-08-03 22:29:50,638 [0x000022e4] <sgucscsdk>: DEBUG SysLog - sqlite3 thread safe: 1 2021-08-03 22:29:50,649 [0x000022e4] <sgucscsdk>: DEBUG SysLog.Cipherer - decrypt [data]...2021-08-03 22:29:50,650 [0x000022e4] <sgucscsdk>: DEBUG SysLog.Cipherer - Decrypt finished.2021-08-03 22:29:50,705 [0x000022e4] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:50,705 [0x000022e4] <sgucscsdk>: DEBUG SysLog - SPELite2021-08-03 22:29:50,705 [0x000022e4] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:50,750 [0x000022e4] <sgucscsdk>: DEBUG SysLog - module args: 'SPELite.exe' with params: --thread-pool-profile=normal --cfgfile=C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\etc\spelite.xml --nodaemon --noerrorbox2021-08-03 22:29:50,750 [0x000022e4] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:50,750 [0x000022e4] <sgucscsdk>: DEBUG SysLog - WFELite2021-08-03 22:29:50,750 [0x000022e4] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:50,751 [0x000022e4] <sgucscsdk>: DEBUG SysLog - module args: 'WFELite.exe' with params: --thread-pool-profile=normal --nodaemon --noerrorbox2021-08-03 22:29:50,751 [0x000022e4] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:50,751 [0x000022e4] <sgucscsdk>: DEBUG SysLog - elma2021-08-03 22:29:50,751 [0x000022e4] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:50,751 [0x000022e4] <sgucscsdk>: DEBUG SysLog - module args: 'elma.exe' with params: --thread-pool-profile=normal --nodaemon --noerrorbox2021-08-03 22:29:50,752 [0x000022e4] <sgucscsdk>: DEBUG SysLog.Cipherer - decrypt [data]...2021-08-03 22:29:50,753 [0x000022e4] <sgucscsdk>: DEBUG SysLog.Cipherer - Decrypt finished.2021-08-03 22:29:51,054 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 1 failed.2021-08-03 22:29:51,055 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 2 failed.2021-08-03 22:29:51,056 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 3 failed.2021-08-03 22:29:51,061 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 4 failed.2021-08-03 22:29:51,062 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize downloadsession of type: 5 failed.2021-08-03 22:29:51,063 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 6 failed.2021-08-03 22:29:51,064 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 7 failed.2021-08-03 22:29:51,066 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 8 failed.2021-08-03 22:29:51,067 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 9 failed.2021-08-03 22:29:51,068 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 10 failed.2021-08-03 22:29:51,069 [0x000022e4] <sgucscsdk>: ERROR SysLog - initialize download session of type: 11 failed.2021-08-03 22:29:51,652 [0x000022e4] <sgucscsdk>: WARN SysLog.CertificateStatus - pfx file: 'C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\certs\client.pfx' is not exists. 2021-08-03 22:29:51,653 [0x000022e4] <sgucscsdk>: INFO SysLog.CertificateManager - client crt file is not exists.2021-08-03 22:29:51,722 [0x00002740] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:29:51,722 [0x00002740] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:29:52,711 [0x000022e4] <sgucscsdk>: INFO SysLog.DMCerts - register dm success, 192.168.3.136:8836, result<0>.2021-08-03 22:29:52,711 [0x000022e4] <sgucscsdk>: INFO SysLog.DMCerts - short id=10000012021-08-03 22:29:52,718 [0x000022e4] <sgucscsdk>: INFO SysLog.CertificateStatus - update pfx file successful.2021-08-03 22:29:52,736 [0x0000124c] <sgucscsdk>: ERROR SysLog.thrift - TPipeServer ConnectNamedPipe GLE=errno = 9952021-08-03 22:29:52,737 [0x0000124c] <sgucscsdk>: ERROR SysLog.thrift - TPipeServer: client connection failed exit 1042021-08-03 22:29:57,471 [0x000020dc] <sgucscsdk>: INFO SysLog - ---------- Win32 x86_64 3.5 3.5.0.125 ----------2021-08-03 22:29:57,500 [0x000020dc] <sgucscsdk>: DEBUG SysLog - work directory : C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK2021-08-03 22:29:57,504 [0x000020dc] <sgucscsdk>: DEBUG SysLog - sqlite3 thread safe: 1 2021-08-03 22:29:57,505 [0x000020dc] <sgucscsdk>: DEBUG SysLog.Cipherer - decrypt [data]...2021-08-03 22:29:57,505 [0x000020dc] <sgucscsdk>: DEBUG SysLog.Cipherer - Decrypt finished.2021-08-03 22:29:57,545 [0x000020dc] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:57,552 [0x000020dc] <sgucscsdk>: DEBUG SysLog - SPELite2021-08-03 22:29:57,556 [0x000020dc] <sgucscsdk>: DEBUG SysLog -+++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:57,562 [0x000020dc] <sgucscsdk>: DEBUG SysLog - module args: 'SPELite.exe' with params: --thread-pool-profile=normal --cfgfile=C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\etc\spelite.xml --nodaemon --noerrorbox2021-08-03 22:29:57,574 [0x000020dc] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:57,579 [0x000020dc] <sgucscsdk>: DEBUG SysLog - WFELite2021-08-03 22:29:57,583 [0x000020dc] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:57,592 [0x000020dc] <sgucscsdk>: DEBUG SysLog - module args: 'WFELite.exe' with params: --thread-pool-profile=normal --nodaemon --noerrorbox2021-08-03 22:29:57,601 [0x000020dc] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:57,608 [0x000020dc] <sgucscsdk>: DEBUG SysLog - elma2021-08-03 22:29:57,612 [0x000020dc] <sgucscsdk>: DEBUG SysLog - +++++++++++++++++++++++++++++++++++++++++++++++++++2021-08-03 22:29:57,620 [0x000020dc] <sgucscsdk>: DEBUG SysLog - module args: 'elma.exe' with params: --thread-pool-profile=normal --nodaemon --noerrorbox2021-08-03 22:29:57,631 [0x000020dc] <sgucscsdk>: DEBUG SysLog.Cipherer - decrypt [data]...2021-08-03 22:29:57,636 [0x000020dc] <sgucscsdk>: DEBUG SysLog.Cipherer - Decrypt finished.2021-08-03 22:29:58,052 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 1 failed.2021-08-03 22:29:58,060 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 2 failed.2021-08-03 22:29:58,067 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 3 failed.2021-08-03 22:29:58,074 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 4 failed.2021-08-03 22:29:58,081 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 5 failed.2021-08-03 22:29:58,086 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 6 failed.2021-08-03 22:29:58,091 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 7 failed.2021-08-03 22:29:58,098 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 8 failed.2021-08-03 22:29:58,103 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 9 failed.2021-08-03 22:29:58,108 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 10 failed.2021-08-03 22:29:58,113 [0x000020dc] <sgucscsdk>: ERROR SysLog - initialize download session of type: 11 failed.2021-08-03 22:29:58,834 [0x000020dc] <sgucscsdk>: INFO SysLog - ThriftMode chose:[0]2021-08-03 22:29:58,836 [0x000020dc] <sgucscsdk>: INFO SysLog.ModuleService - starting thrift server ...2021-08-03 22:29:58,837 [0x00001074] <sgucscsdk>: INFO SysLog - thrift starting with port: 8800, ip: 127.0.0.12021-08-03 22:29:58,938 [0x000020dc] <sgucscsdk>: INFO SysLog.ModuleService - starting thrift server true2021-08-03 22:29:58,952 [0x00001b4c] <sgucscsdk>: INFO SysLog - start module: 'SPELite.exe' with params: SPELite --mid=2 --cip=127.0.0.1 --cport=8816 --heartbeat=30 --mip=127.0.0.1 --mport=8800 --protocol=AF_INET --thread-pool-profile=normal --cfgfile=C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\etc\spelite.xml --nodaemon --noerrorbox2021-08-03 22:29:58,952 [0x000009dc] <sgucscsdk>: INFO SysLog - start module: 'WFELite.exe' with params: WFELite --mid=8 --cip=127.0.0.1 --cport=8846 --heartbeat=30 --mip=127.0.0.1 --mport=8800 --protocol=AF_INET --thread-pool-profile=normal --nodaemon --noerrorbox2021-08-03 22:30:00,990 [0x000026b4] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ORS.cache2021-08-03 22:30:01,587 [0x000017fc] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ORS.cache2021-08-03 22:30:01,951 [0x000020dc] <sgucscsdk>: INFO .SystemManager::updateSystemInfo - \test is login, session id=12021-08-03 22:30:01,952 [0x000020dc] <sgucscsdk>: INFO erSessionManager::addUserSession - elma info {"elma_data_path" : "","elma_ip" : "127.0.0.1","elma_mid" : 9,"elma_port" : 8860,"login_time" : 1628001001,"session_id" : 1,"user_bind_name" : "","user_name" : "\\test"}2021-08-03 22:30:01,952 [0x000020dc] <sgucscsdk>: INFO SysLog. UCSCManager::onUserLogin - session id=12021-08-03 22:30:01,952 [0x000020dc] <sgucscsdk>: WARN SysLog.UCSCManager::onUserLogin - label fature is not enabled, won't start elma2021-08-03 22:30:01,952 [0x000020dc] <sgucscsdk>: INFO SysLog.UCSCManager::onUserLogin - add module 9 profile success. isstart=02021-08-03 22:30:01,952 [0x000020dc] <sgucscsdk>: INFO SystemManager::notifyELMAChanged - notify ucsc_sdk.elma.port config size=12021-08-03 22:30:01,952 [0x000020dc] <sgucscsdk>: INFO SystemManager::notifyELMAChanged - 1->127.0.0.1:88602021-08-03 22:30:01,955 [0x000013bc] <sgucscsdk>: INFO SysLog.DMAgent - work thread <13bc> begin running ...2021-08-03 22:30:01,960 [0x000013bc] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:30:01,970 [0x000020dc] <sgucscsdk>: INFO SysLog.SystemManager - protection status changed, <Disabled> .2021-08-03 22:30:01,970 [0x000020dc] <sgucscsdk>: INFO SysLog.UCSCMNotification - ProtectionStatusChanged <PS_DISABLED>.2021-08-03 22:30:01,977 [0x000020dc] <sgucscsdk>: INFO SysLog.UCSCMNotification - RunStatusChanged <RS_RUNNING>.2021-08-03 22:30:01,977 [0x000020dc] <sgucscsdk>: INFO SysLog.UCSCManager - manager started.2021-08-03 22:30:01,981 [0x000020dc] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:30:01,984 [0x00000a04] <sgucscsdk>: INFO SysLog.TimerTask - work thread <a04> begin running ...2021-08-03 22:30:02,040 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:02,040 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:02,046 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:02,046 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:02,053 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:02,053 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 9 notify system config exception, Called write on non-open socket2021-08-03 22:30:02,181 [0x000013bc] <sgucscsdk>: INFO SysLog.SystemManager - connect dm: '192.168.3.136:8837' success, timedelta_from_server: -285002021-08-03 22:30:02,182 [0x000013bc] <sgucscsdk>: INFO SysLog.SystemManager - local endpoint profile changed.2021-08-03 22:30:02,376 [0x000013bc] <sgucscsdk>: INFO SysLog.SystemManager - engine resource mode changed from [ERM_NORMAL] to [undefined]2021-08-03 22:30:02,376 [0x000013bc] <sgucscsdk>: INFO SysLog.UCSCManager - restart spelite.2021-08-03 22:30:02,425 [0x00001fa4] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:02,425 [0x00001fa4] <sgucscsdk>: ERROR SysLog - Called write on non-open socket2021-08-03 22:30:02,492 [0x000020dc] <sgucscsdk>: WARN SysLog.AppIdentityDBSession - the database is not open.2021-08-03 22:30:03,028 [0x00001b4c] <sgucscsdk>: INFO SysLog.ModuleGuard - module(SPELite.exe:2) exits, exit code: 12021-08-03 22:30:03,028 [0x000013bc] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.FPDBServer2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 1, server is changed.2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 2, server is changed.2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 3, server is changed.2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 4, server is changed.2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 5, server is changed.2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 6, server is changed.2021-08-03 22:30:03,029 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 7, server is changed.2021-08-03 22:30:03,030 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 9, server is changed.2021-08-03 22:30:03,030 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 10, server is changed.2021-08-03 22:30:03,030 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 11, server is changed.2021-08-03 22:30:03,030 [0x000013bc] <sgucscsdk>: INFO SysLog.UCSCMNotification - ConnectionStatusChanged <CS_CONNECTED>.2021-08-03 22:30:03,030 [0x000013bc] <sgucscsdk>: INFO SysLog.BypassManager - bypass code file is not exists.2021-08-03 22:30:03,031 [0x000013bc] <sgucscsdk>: INFO SysLog.UCSCMNotification - previous dm is null, the first connect to dm.2021-08-03 22:30:03,031 [0x000013bc] <sgucscsdk>: INFO SystemManager::ELMAConfigChanged - notify elma dm new ip=192.168.3.1362021-08-03 22:30:03,053 [0x00002ad4] <sgucscsdk>: INFO SysLog - start module: 'SPELite.exe' with params: SPELite --mid=2 --cip=127.0.0.1 --cport=8816 --heartbeat=30 --mip=127.0.0.1 --mport=8800 --protocol=AF_INET --thread-pool-profile=normal --cfgfile=C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\etc\spelite.xml --nodaemon --noerrorbox2021-08-03 22:30:03,072 [0x00002ad8] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/profiles/7D6F766C6A6C7569737C63896D7A756A/1-1-0-14 -16, from size: 02021-08-03 22:30:03,074 [0x00002adc] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/appdb/7D6F766C6A6C7569737C63896D7A756A/3/app.db, from size: 02021-08-03 22:30:03,089 [0x00002ae0] <sgucscsdk>: INFO SysLog - should sync with delta file, but not found base version.2021-08-03 22:30:03,089 [0x00002ae0] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/ors/7D6F766C6A6C7569737C63896D7A756A/617/ors.db, from size: 02021-08-03 22:30:03,092 [0x00002ae4] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: , type: 4, last_state: 22021-08-03 22:30:03,121 [0x00002b00] <sgucscsdk>: INFO SysLog.MQMAgent - check thread <2b00> begin running ...2021-08-03 22:30:03,133 [0x00002ae8] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/fpdb/7D6F766C6A6C7569737C63896D7A756A/fpdb_1_polic y_566/unstruct.db, from size: 02021-08-03 22:30:03,134 [0x00002aec] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/fpdb/7D6F766C6A6C7569737C63896D7A756A/fpdb_1_polic y_566/machine.db, from size: 02021-08-03 22:30:03,135 [0x00002af0] <sgucscsdk>: INFO SysLog - should sync with delta file, but not found base version.2021-08-03 22:30:03,135 [0x00002af0] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/policies/7D6F766C6A6C7569737C63896D7A756A/566/policy .db, from size: 02021-08-03 22:30:03,136 [0x00002af4] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/swg_policy/7D6F766C6A6C7569737C63896D7A756A/220/sw g_policy.db, from size: 02021-08-03 22:30:03,138 [0x00002af8] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/swg_urlmisc/7D6F766C6A6C7569737C63896D7A756A/114-107, from size: 02021-08-03 22:30:03,139 [0x00002afc] <sgucscsdk>: INFO ysLog.DownloadDriver::initialize - download file: https://192.168.3.136:8837/dm/v2/swg_settings/7D6F766C6A6C7569737C63896D7A756A/0-1-1, from size: 02021-08-03 22:30:03,505 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,505 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:03,580 [0x00002afc] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\swg_advance_profile\0-1-1\swg_advance_profile, type: 11, last_state: 02021-08-03 22:30:03,585 [0x00002afc] <sgucscsdk>: INFO SysLog.SystemManager - protection status changed, <Enabled> .2021-08-03 22:30:03,585 [0x00002afc] <sgucscsdk>: INFO SysLog.UCSCMNotification - ProtectionStatusChanged <PS_ENABLED>.2021-08-03 22:30:03,586 [0x00002afc] <sgucscsdk>: INFO SysLog.SystemManager - all profile file download finished.2021-08-03 22:30:03,870 [0x00002af8] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\swg_url_category\114-107\swg_url_category, type: 10, last_state: 02021-08-03 22:30:03,887 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,887 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:03,892 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,893 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 9 notify system config exception, Called write on non-open socket2021-08-03 22:30:03,928 [0x00002af4] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\swg_policy\220\swg_policy, type: 9, last_state: 02021-08-03 22:30:03,941 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,941 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:03,957 [0x00002ad8] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\ep_profile\1-1-0-14-16\ep_profile, type: 1, last_state: 02021-08-03 22:30:03,962 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,962 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 9 notify system config exception, Called write on non-open socket2021-08-03 22:30:03,967 [0x00002af0] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\policy\566\policy, type: 7, last_state: 02021-08-03 22:30:03,974 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,974 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 8 notify system config exception, Called write on non-open socket2021-08-03 22:30:03,982 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:03,982 [0x00002278] <sgucscsdk>: ERRORSysLog.ModuleSupervisorManager - mid: 8 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,001 [0x00002ae8] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\fpdb_unstructured\fpdb_1_policy_566\fpdb_unstructured, type: 5, last_state: 02021-08-03 22:30:04,003 [0x00002adc] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\appdb\3\appdb, type: 2, last_state: 02021-08-03 22:30:04,012 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,012 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 8 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,033 [0x00000a04] <sgucscsdk>: INFO SysLog.UCSCMNotification - EndpointLocationChanged <L_INTERNAL>.2021-08-03 22:30:04,039 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,039 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,040 [0x00002aec] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\machine_learning\fpdb_1_policy_566\machine_learning, type: 6, last_state: 02021-08-03 22:30:04,066 [0x00002ae0] <sgucscsdk>: INFO SysLog.DownloadSession - download is end, filename: C:\Program Files\SkyGuard\SkyGuard Endpoint\UCSCSDK\downloads\orsdb\617\orsdb, type: 3, last_state: 02021-08-03 22:30:04,072 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,072 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,097 [0x00002a50] <sgucscsdk>: INFO SysLog.EndpointProfileParser - work thread <2a50> begin running ...2021-08-03 22:30:04,099 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,100 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - channel.controlList2021-08-03 22:30:04,101 [0x00002a50] <sgucscsdk>: INFO SysLog.addEmbedFile - add 7d2e968c-2113-4d83-9fd0-91a7c3bb5df0 into embedded file list2021-08-03 22:30:04,122 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,122 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,133 [0x00002adc] <sgucscsdk>: INFO SysLog.SystemManager - app identity db changed.2021-08-03 22:30:04,134 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,134 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,196 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,196 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,209 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,209 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 2 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,239 [0x00002278] <sgucscsdk>: ERROR SysLog.ClientDecorator - connect() failed: errno = 100492021-08-03 22:30:04,239 [0x00002278] <sgucscsdk>: ERROR SysLog.ModuleSupervisorManager - mid: 9 notify system config exception, Called write on non-open socket2021-08-03 22:30:04,563 [0x00001d38] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:30:04,664 [0x0000276c] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ORS.cache2021-08-03 22:30:04,998 [0x00002a50] <sgucscsdk>: WARN SysLog.SystemManager - download file : ui_resource.zip failure!2021-08-03 22:30:04,999 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - http response code 5032021-08-03 22:30:04,999 [0x00002a50] <sgucscsdk>: WARN SysLog.EndpointProfileParser - server response 503, retry it again after 300seconds2021-08-03 22:30:05,681 [0x000025b4] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:30:13,404 [0x0000276c] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, ponent.wfeDebug2021-08-03 22:30:14,660 [0x00001dd4] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.FingerprintConfig2021-08-03 22:30:14,661 [0x000026b4] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ML2021-08-03 22:30:14,662 [0x000017fc] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ContentParserConfig2021-08-03 22:30:16,151 [0x000021a0] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ContentParserConfig2021-08-03 22:30:16,151 [0x000017fc] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.FingerprintConfig2021-08-03 22:30:16,152 [0x000026b4] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ML2021-08-03 22:30:16,154 [0x000021a0] <sgucscsdk>: WARN SysLog.SPESetting - key is not exists, DLPServer.global.ORS.cache2021-08-03 22:30:57,578 [0x000013bc] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:30:57,600 [0x000013bc] <sgucscsdk>: INFO SysLog.SystemManager - connect dm: '192.168.3.136:8837' success, timedelta_from_server: -285002021-08-03 22:30:57,601 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 4, new version or checksum is empty, trait it as no changed.2021-08-03 22:30:57,649 [0x00001ffc] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:31:03,816 [0x000025a8] <sgucscsdk>: INFO SystemManager::notifyAllElmaSync - notify all elma sync is called.2021-08-03 22:31:03,817 [0x000013bc] <sgucscsdk>: ERROR SysLog.SystemManager - RequestDiscoveryStatus failed.2021-08-03 22:31:03,840 [0x000013bc] <sgucscsdk>: INFO SysLog.SystemManager - connect dm: '192.168.3.136:8837' success, timedelta_from_server: -285002021-08-03 22:31:03,841 [0x000013bc] <sgucscsdk>: INFO ysLog.DownloadSession::isChanged - type: 4, new version or checksum is empty, trait it as no changed.2021-08-03 22:31:03,887 [0x000024b4] <sgucscsdk>: ERROR SysLog.SystemManager -。

Google Spanner （中文版）翻译者：厦门大学计算机系教师林子雨翻译时间：2012年9月E-mail: ziyulin@ 个人主页：/linziyu【摘要】：Spanner是谷歌公司研发的、可扩展的、多版本、全球分布式、同步复制数据库。

它是第一个把数据分布在全球范围内的系统，并且支持外部一致性的分布式事务。

本文描述了Spanner的架构、特性、不同设计决策的背后机理和一个新的时间API，这个API可以暴露时钟的不确定性。

这个API及其实现，对于支持外部一致性和许多强大特性而言，是非常重要的，这些强大特性包括：非阻塞的读、不采用锁机制的只读事务、原子模式变更。

【关键词】Google Spanner, Bigtable, distributed database【全文目录结构】1. 介绍2. 实现2.1 Spanserver软件栈2.2 目录和放置2.3 数据模型3. TrueTime4. 并发控制4.1 时间戳管理4.2 细节5. 实验分析5.1 微测试基准5.2 可用性5.3 TrueTime5.4 F16. 相关工作7. 未来的工作8. 总结致谢参考文献1 介绍Spanner是一个可扩展的、全球分布式的数据库，是在谷歌公司设计、开发和部署的。

在最高抽象层面，Spanner就是一个数据库，把数据分片存储在许多Paxos[21]状态机上，这些机器位于遍布全球的数据中心内。

复制技术可以用来服务于全球可用性和地理局部性。

客户端会自动在副本之间进行失败恢复。

随着数据的变化和服务器的变化，Spanner会自动把数据进行重新分片，从而有效应对负载变化和处理失败。

Spanner被设计成可以扩展到几百万个机器节点，跨越成百上千个数据中心，具备几万亿数据库行的规模。

应用可以借助于Spanner来实现高可用性，通过在一个洲的内部和跨越不同的洲之间复制数据，保证即使面对大范围的自然灾害时数据依然可用。

我们最初的客户是F1[35]，一个谷歌广告后台的重新编程实现。

crc_2_pentest_8_phpwind解题思路题目描述：在PHPWind 论坛中，存在一个叫做crc_2_pentest_8 的PHP 文件。

这个文件有一个漏洞，导致它可以被利用来获取任意文件的内容。

攻击者可以利用这个漏洞来获取其他文件的内容，例如数据库的配置文件，从而获得敏感信息。

为了修复这个漏洞，我们需要找到一个方法来防止攻击者利用该漏洞获取其他文件的内容。

解题思路：1.首先，我们需要了解该漏洞是如何被利用的。

攻击者可以利用该漏洞来获取其他文件的内容，主要是通过在URL 中传递参数来触发该漏洞。

2.为了防止攻击者利用该漏洞获取其他文件的内容，我们需要对URL 参数进行验证和过滤。

我们可以使用PHP 的过滤函数来验证参数是否为预期的值，例如使用filter_input() 函数来验证参数是否存在且为预期的类型。

3.在PHPWind 论坛中，存在一个函数叫做include_once($filename)。

该函数会将指定的文件包含到当前文件中，并在包含之后立即执行。

攻击者可以利用该函数来包含其他文件的内容，从而获取敏感信息。

为了防止攻击者利用该函数包含其他文件的内容，我们可以将该函数重写为一个自定义函数，并在其中添加验证和过滤逻辑。

4.在自定义的include_once() 函数中，我们可以首先验证参数是否为预期的值。

如果参数不符合预期的值，我们可以返回一个错误消息或跳转到另一个页面。

如果参数符合预期的值，我们可以继续执行正常的包含逻辑。

5.在编写代码时，我们需要注意代码的安全性和可维护性。

我们可以使用安全的编程实践，例如避免使用eval() 函数、对用户输入进行验证和过滤、使用安全的数据库查询语句等。

总结：要修复crc_2_pentest_8 文件的漏洞，我们需要对URL 参数进行验证和过滤，并将include_once() 函数重写为一个自定义函数，在其中添加验证和过滤逻辑。

在编写代码时，我们需要注意代码的安全性和可维护性，并使用安全的编程实践来保护我们的应用程序免受攻击。

秀丽隐杆线虫在衰老与延缓衰老研究中的应用张宗敏【期刊名称】《贵州医药》【年(卷),期】2018(042)006【总页数】3页(P670-672)【关键词】秀丽隐杆线虫;衰老;延缓衰老【作者】张宗敏【作者单位】遵义医学院附属医院,贵州遵义 563000【正文语种】中文【中图分类】R383.1衰老是机体各种组织和器官功能随着时间的推移逐渐退行性变化的过程。

衰老可以降低机体面对环境胁迫维持自身稳态的能力，从而增加机体患病和死亡的可能性。

伴随衰老，许多疾病的发病率增加，而这些疾病已逐渐成为人类死亡的主要原因[1]。

秀丽隐杆线虫(C.elegans)由于具有寿命短、身体透明易于观察、饲养成本低、容易获取大量同期化样本、可长期保存、实验可操作性强等优点，已成为衰老研究中常用的模式生物。

在遗传学方面，C.elegans的基因与哺乳类动物在进化上都是保守的，且与人类基因的同源性达60%～80%，可通过基因操作技术获得变异株，构建与衰老及衰老相关疾病相似的模型，使得C.elegans广泛应用于衰老与延缓衰老的研究[2-3]。

1 C.elegans与衰老相关的实验1.1 寿命实验 C.elegans由于其具有寿命短、同期化后可减少个体差异、便于大规模筛选等优点，使其成为寿命实验的优选模型[2]。

在寿命实验中，C.elegans通常使用固体或液体培养基进行培养，其中固体培养基比较常用。

线虫用固体培养基进行培养时，同期化的L1线虫生长于涂布有OP50大肠杆菌的标准线虫生长培养基(NGM)中，待线虫生长到L4期，将线虫转移到添加有测试药物的NGM上。

存活的线虫每天被转移到新的NGM上，并准确记录下当天线虫存活和死亡数目，直至线虫全部死亡，然后计算存活率或死亡率[4]。

线虫液体培养基的寿命分析是在小容积的微孔板中进行的，同期化的L1期线虫在含有大肠杆菌的S培养基中进行培养至L4期，然后将L4期线虫平均分配到微孔板上，向微孔板中添加测试的药物，每天计算一次活体线虫的数量，直至所有的线虫死亡[5]。

echartsdemo<!DOCTYPE html><html><head><meta charset="utf-8"><title>Visualization</title><meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"><script src="/jquery/2.0.0/jquery.js"></script><script src="/dist/echarts.min.js"></script><!-- link href="Style/cover.css" rel="stylesheet" --><style>@keyframes backgroundMove{0% {background-position:0 0;}100% {background-position:-2560px 0;}}@keyframes tipAnimate{0% {transform:rotateX(0deg);opacity:1;}90% {transform:rotateX(0deg);opacity:0.8;}95% {transform:rotateX(180deg);opacity:0.2;}100% {transform:rotateX(360deg);opacity:0.9;}}@keyframes tip2Animate{0% {background:rgba(255,255,255,0.2);}50% {background:rgba(255,255,255,0.2);}80% {background:rgba(255,255,255,0.1);}100% {background:rgba(255,255,255,0.2);}}body::-webkit-scrollbar{display:none;}* {margin: 0;padding: 0;border: 0;font-size: 100%;vertical-align: baseline;box-sizing:border-box;font-family:sans-serif;}body, html {height: 100%;}body {transform-origin: left top 0px;background-color:black;background-image:url(/notes/pics/201711/17/104455a0j6v5ccv267nchx.jpg);animation: backgroundMove 100s linear infinite;}.boxTitle{color:white;font-weight:bold;font-size:16px;padding:0 20px;line-height:58px;height:60px;}.boxTitle span{color:#FB9008;font-size:20px;}.boxRTText{color:#aaa;font-weight:bold;font-size:12px;line-height:58px;position:absolute;right:20px;top:0px;}.boxRTText span{font-size:14px;}.tableTh{color:#44BBBB;font-size:14px;border-top:1px solid #3f556f;border-bottom:1px solid #3f556f;}.tableTh span{color:#44BBBB;font-size:14px;border-right:1px solid #3f556f;display:inline-block;line-height:38px;height:40px;text-align:center;}.tableTr{color:#44BBBB;font-size:14px;overflow:hidden;}.tableTr span{color:#94BEE8;font-size:14px;border-right:1px solid #3f556f;display:block;line-height:40px;text-align:center;float:left;overflow:hidden;white-space:nowrap;text-overflow:ellipsis;padding:0 8px;}.tip{color:white;text-align:center;padding:12px 22px;float:left;font-size:16px;animation: tipAnimate 10s linear infinite;}.tip span{font-size:25px;}.tip2{float:right;overflow:hidden;}.tip2_item{margin:8px;overflow:hidden;}.tip2_item span{display:block;color:white;float:left;overflow:hidden;white-space:nowrap;text-overflow:ellipsis;line-height:30px;font-size:14px;}.tip2_item span:nth-of-type(1){width:100px;text-align:right;}.tip2_item span:nth-of-type(2){width:120px;padding:0 10px;background:rgba(255,255,255,0.2);color:#02AAEB;border-radius:8px;font-size:18px;animation: tip2Animate 10s linear infinite;}.tip2_item span:nth-of-type(3){text-align:center;width:40px}.cornerLine{position:absolute;border:2px solid #aaa;height:20px;width:20px;}.TLCorner{top:0px;left:0px;border-right:none;border-bottom:none;}.TRCorner{top:0px;right:0px;border-left:none;border-bottom:none;}.BLCorner{bottom:0px;left:0px;border-right:none;border-top:none;}.BRCorner{bottom:0px;right:0px;border-left:none;border-top:none;}.MD_title{font-size:35px;padding:20px;color:#0E84EE;font-weight:bold;font-family:微软雅⿊;}.MDdiv_title{color:white;font-size:16px;}.MDdiv_title span{font-size:12px;}.MDTipTitle{font-size:20px;color:white;padding:5px 20px;}.MDTipLine{color:#94BEE8;font-size:16px;color:white;padding:5px 20px;}.MDTipLine2{background:rgba(14,132,238,0.2);border-radius:8px;margin-bottom:8px;font-size:14px;padding:5px 20px;color:white;padding:5px 20px;}.MDTipLine2 span{font-size:22px;}</style></head><body><div id="box" style="position:relative;height:1060px;width:2500px;overflow:hidden;left:0px;top:0px;"><div id="example" style="position:absolute;height:1060px;width:2500px;left:0;top:0px;background:rgba(111,20,255,0.0);"><div class="example-title" style="text-align:center;" ><img src="/notes/pics/201711/17/104523x79au2aip57dyfaf.png"></div></div><div id="example2" style="position:absolute;height:1060px;width:2500px;left:2500px;top:0px;background:rgba(11,111,255,0.0);"><div class="example-title" style="text-align:center;" ><img src="/notes/pics/201711/17/104523x79au2aip57dyfaf.png"></div></div></div><script>var ningMap='\<svg width="640" height="480" version="1.1" xmlns="/2000/svg" xmlns:xlink="/1999/xlink" stroke="#000099" fill="none">\<path class="svgMap" id="yys" d="M155.3686 45.35257L156.0096 49.35898L154.8077 50.72116L153.6859 52.64423C151.7628 53.04487 150.4007 54.2468 150.4007 54.2468L149 55L148 58C150 59 152 60 152 60L155 59C156 59 159 58 159 58 <path class="svgMap" id="cxs" d="M156.891 42.46795L158 45L158 48L157 50L157 52L155 54L152.2436 56.57051L153 58L155 57L157 56L159 56L161 56L163 58L165 60L165 62L166 64L165 69L165 72L164 74L163 76L163 78L165 80L167 80L1 <path class="svgMap" id="jdq" d="M308 184L308 187L307 189L307 190L306 192L304.4872 193.109L304 195L305 197L306 197L324 198L325 197L326 196L326.4423 195.3526L328 194L329 192L330 191L331 188L331 187L330 186L329 184L328 <path class="svgMap" id="zhq" d="M280 131L281 130L283 130L283 129C284 129 285 129 285 129L286 128L287 126L288 125L288 124L289 122L290 121L291 119L295 119L297 120L297.7163 121.1539L298.2404 122L301.2404 123L303 124L30 <path class="svgMap" id="jbq" d="M282 124L283 126C283 127 279 128 279 128L278 130L277 132L279 135L279 136L280 139L280 142L281 144L282 146L284 146L285 146L288 146L292 147L295 147L296 149L299 152L302 154L304 156L307 15 <path class="svgMap" id="yzq" d="M257 164L259 164L260 166L261 167L264 167C265 167 268 167 268 167L268 166L270 166C271 167 272 168 272 168L272 169L274 172L274 174L275 175L277 176L281 176L283 176L284 174L285 173L287 17 <path class="svgMap" id="fhs" d="M275 222L275.1602 221.9551L276 225L277 228L278 230L278 234L279 237L279 240L279 242L280 246L281 248L283 249C285 249 288 250 288 250C289 250 292 251 292 251L295 251L297 250C297 250 298 2 <path class="svgMap" id="hsq" d="M293 176L295 177L297 178L300 180L301 181L303 183C304 183 305 185 305 185L306 186L305 188L304 190L303 192L302 195L300 196L296 196L295 199L294 200L293 202L291 201L292 199L292 198C292 1 <path class="svgMap" id="blq" d="M363 157L365 153L366 151L368 150L369 149L371 149L373 149L373 150L374 151L375 152C376 152 378 152 378 152C379 152 381 152 381 152C382 152 383 152 383 152L384 153L385 155C386 155 387 156.svgMap{stroke:white;opacity:0.5;}\.svgMap:hover{opacity:0.7;cursor:pointer;}\</style>\';</script><script>//地区名var areaData=["余姚市","慈溪","奉化区","宁海县","象⼭县","鄞州区","海曙区","江东区","江北区","镇海区","北仑区","杭州湾新区","保税区","⼤榭开发区","⾼新区","东钱湖旅游度假区","梅⼭保税港区"]; //定时器数组var sta = [];//清除所有定时器function clearIntervals(array){for (i=0; i <array.length; i++) {clearInterval(array[i]);};sta = [];}/*除输⼊框外禁⽌选中*/$(function(){var isInputText = false;$("input[type='text'] ,textarea").focus(function () {isInputText = true;}).blur(function () {isInputText = false;})document.onselectstart = function () {return isInputText;};})//⾃适应屏幕function setBodySize(){$("body").css({"transform":"scale("+($(this).width()/2500)+")"});return;}//加载内容function fillExample(boxObj){clearIntervals(sta);getECharts1(boxObj);getECharts2(boxObj);getECharts3(boxObj);getECharts4(boxObj);getECharts5(boxObj);getTable1(boxObj);getTip1(boxObj);getMainDiv(boxObj);}//创建DIVfunction creatDiv(id,style,parentObj){$("#" + id).remove();var html = "<div id='" + id + "'></div>";var div = $(html);div.css(style);parentObj.append(div);return div;}//坐标轴颜⾊var lineColor = {lineStyle:{color:'#fff',width:1,}}var labelColor = {show: true,textStyle: {color: '#fff'}}function getECharts1(boxObj){var id = boxObj.attr("id") + "-echarts-1";var style={width:500,height:300,top:-100,left:-200,padding:20,border:"1px solid #3f556f",position:"absolute",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({top:40,left:40,opacity:1},500)var chart = echarts.init(div[0]);var option = {color: ['#3398DB'],title : [{text: '企业类型',textStyle:{color:"#fff",fontSize:16},x:'left',top:4},{text: '产值',textStyle:{color:"#FB9008",fontSize:20},x:'left',left:66},{text: '排⾏',textStyle:{color:"#fff",fontSize:16},x:'left',left:108,top:4},{text: '2016年',backgroundColor:"rgba(255,255,255,0.2)",textStyle:{color:"#00AEF1",fontSize:12},x:'left',left:160,top:5}],tooltip : {trigger: 'axis',axisPointer : { // 坐标轴指⽰器，坐标轴触发有效type : 'shadow' // 默认为直线，可选为：'line' | 'shadow'}},grid: {left: '3%',right: '3%',bottom: '3%',containLabel: true},xAxis : [{type : 'category',data : ['施⼯', '监理', '安全房屋\n鉴定', '勘察', '设计', '施⼯图\n审查'], axisTick: {alignWithLabel: true},axisLine:lineColor,axisLabel:labelColor}],yAxis : [{type : 'value',max:700,axisLine:lineColor,axisLabel:labelColor,splitArea : {show : false}}],series : [{name:'产值',itemStyle:{normal:{color:"#00AEF1"}},type:'bar',barWidth: '40%',data:[152, 200, 334, 390, 330, 220],animationDelay: function (idx) {return idx * 50 + 100;}}],animationEasing: 'elasticOut',animationDelayUpdate: function (idx) {return idx * 5;}};chart.setOption(option);sta.push(setInterval(function (){var data = option.series[0].data;var num = Math.floor(Math.random() * data.length);data[num] = Math.round(Math.random() * 400 + 200);div.animate({opacity:0},1000,function(){chart.clear();chart.setOption(option);div.animate({opacity:1},1500);})}, 16100))}function getECharts2(boxObj){var id = boxObj.attr("id") + "-echarts-2"var style={width:500,height:300,top:300,left:40,padding:20,border:"1px solid #3f556f",position:"absolute",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,top:380},400)var chart = echarts.init(div[0]);var option = {title : [{text: '建筑业⾛出去产值',textStyle:{color:"#fff",fontSize:16},x:'left',top:4},{text: '分布',textStyle:{color:"#FB9008",fontSize:20},x:'left',left:130},{text: '图',textStyle:{color:"#fff",fontSize:16},x:'left',left:172,top:4},{text: '2015年',backgroundColor:"rgba(255,255,255,0.2)",textStyle:{color:"#00AEF1",fontSize:12},x:'left',left:210,top:5}],tooltip : {orient: 'vertical',left: 'left',top: 60,textStyle:{color:"white"},data: ['直接访问','邮件营销','联盟⼴告','视频⼴告','搜索引擎'] },series : [{name: '访问来源',type: 'pie',radius : '60%',center: ['65%', '60%'],data:[{value:335, name:'直接访问'},{value:310, name:'邮件营销'},{value:234, name:'联盟⼴告'},{value:135, name:'视频⼴告'},{value:1548, name:'搜索引擎'}],itemStyle: {emphasis: {shadowBlur: 10,shadowOffsetX: 0,shadowColor: 'rgba(0, 0, 0, 0.5)'}}}]};chart.setOption(option,false,false);sta.push(setInterval(function (){var data = option.series[0].data;var num = Math.floor(Math.random() * data.length);data[num].value = Math.round(Math.random() * 1200 + 300); chart.clear();chart.setOption(option);}, 7200))}function getECharts3(boxObj){var id = boxObj.attr("id") + "-echarts-3"var style={width:500,height:300,top:720,left:140,padding:20,border:"1px solid #3f556f",position:"absolute",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,left:40},800)var chart = echarts.init(div[0]);var option = {title: [{text: '建筑业',textStyle:{color:"#fff",fontSize:16},x:'left',top:4},{text: '产值及增速',textStyle:{color:"#FB9008",fontSize:20},x:'left',left:50},{text: '单位：亿元',textStyle:{color:"#fff",fontWeight:"normal",fontSize:14},x:'right',}],tooltip: {trigger: 'axis',axisPointer: {type: 'cross',crossStyle: {color: '#fff',width: 1,type: 'dashed'},label: {backgroundColor: '#666',}}},grid: {left: '3%',right: '3%',bottom: '3%',containLabel: true},legend: {textStyle:{color:"white"},data:['⽣产总值', '建筑业增速'],top:50},dataZoom: {show: false,start: 0,end: 100},xAxis: [{type: 'category',boundaryGap: true,axisLine:lineColor,axisLabel:labelColor,data: (function (){var now = new Date();var res = [];var len = 10;while (len--) {res.unshift(now.toLocaleTimeString().replace(/^\D*/,''));now = new Date(now - 2000);boundaryGap: true,axisLine:{show:false},axisLabel:{show:false},data: (function (){var res = [];var len = 10;while (len--) {res.push(len + 1);}return res;})()}],yAxis: [{type: 'value',scale: true,max: 30,min: 0,axisLine:lineColor,axisLabel:labelColor,boundaryGap: [0.2, 0.2],splitLine : {show : false}},{type: 'value',scale: true,max: 1200,min: 0,axisLine:lineColor,axisLabel:labelColor,boundaryGap: [0.2, 0.2],splitLine : {show : false}}],series: [{name:'⽣产总值',type:'bar',barWidth: '70%',itemStyle:{normal:{color:"#85DAF4"}},xAxisIndex: 1,yAxisIndex: 1,data:(function (){var res = [];var len = 10;while (len--) {res.push(Math.round(Math.random() * 1000));}return res;})()},{name:'建筑业增速',type:'line',data:(function (){var res = [];var len = 0;while (len < 10) {res.push((Math.random()*10 + 5).toFixed(1) - 0);len++;}return res;})()}]};chart.setOption(option);var count = 11;sta.push(setInterval(function (){axisData = (new Date()).toLocaleTimeString().replace(/^\D*/,''); var data0 = option.series[0].data;var data1 = option.series[1].data;data0.shift();data0.push(Math.round(Math.random() * 1000));data1.shift();data1.push((Math.random() * 10 + 5).toFixed(1) - 0);option.xAxis[0].data.shift();option.xAxis[0].data.push(axisData);option.xAxis[1].data.shift();option.xAxis[1].data.push(count++);chart.setOption(option);}, 2100))}function getECharts4(boxObj){var id = boxObj.attr("id") + "-echarts-4"var style={width:500,height:300,top:40,right:140,padding:20,border:"1px solid #3f556f",position:"absolute",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,right:40,top:40},800);var chart = echarts.init(div[0]);var option = {title: [{text: '房屋⼯程',textStyle:{color:"#fff",fontSize:16},x:'left',top:4},{textStyle:{color:"#fff",fontWeight:"normal",fontSize:14},x:'right',}],tooltip: {trigger: 'axis',axisPointer: {type: 'cross',crossStyle: {color: '#fff',width: 1,type: 'dashed'},label: {backgroundColor: '#666',}}},grid: {left: '3%',right: '3%',bottom: '3%',containLabel: true},legend: {textStyle:{color:"white"},data:['竣⼯⾯积', '竣⼯增长'],top:50},dataZoom: {show: false,start: 0,end: 100},xAxis: [{type: 'category',boundaryGap: true,axisLine:lineColor,axisLabel:labelColor,data: ["2008","2009","2010","2011","2012","2013","2014","2015"] },{type: 'category',boundaryGap: true,axisLine:lineColor,axisLabel:{show:false},data: (function (){var res = [];var len = 8;while (len--) {res.push(len + 1);}return res;})()}],yAxis: [{type: 'value',scale: true,max: 30,min: 0,axisLine:lineColor,axisLabel:labelColor,boundaryGap: [0.2, 0.2],splitLine : {show : false}},{type: 'value',scale: true,max: 1200,min: 0,axisLine:lineColor,axisLabel:labelColor,boundaryGap: [0.2, 0.2],splitLine : {show : false}}],series: [{name:'竣⼯⾯积',type:'bar',barWidth: '30%',itemStyle:{normal:{color:"white"}},xAxisIndex: 1,yAxisIndex: 1,data:(function (){var res = [];var len = 8;while (len--) {res.push(Math.round(Math.random() * 1000));}return res;})()},{name:'竣⼯增长',type:'line',itemStyle:{normal:{color:"#00AEF1"}},data:(function (){var res = [];var len = 0;while (len < 8) {res.push((Math.random()*8 + 5).toFixed(1) - 0);len++;}return res;})()}]};var option2 = {title : [{text: '房建⼯程',text: '竣⼯⾯积构成',textStyle:{color:"#FB9008",fontSize:20},x:'left',left:66},{text: '图',textStyle:{color:"#fff",fontSize:16},x:'left',left:188,top:4}],tooltip : {trigger: 'item',formatter: "{a} <br/>{b} : {c} ({d}%)"},legend: {orient: 'vertical',left: 'right',top: 60,textStyle:{color:"white"},data: ['住宅房屋','⼚房及建筑物','商业及服务⽤房屋','办公⽤房屋','其他'] },series : [{name: '竣⼯⾯积',type: 'pie',radius : '50%',center: ['30%', '60%'],data:[{value:335, name:'住宅房屋'},{value:310, name:'⼚房及建筑物'},{value:234, name:'商业及服务⽤房屋'},{value:135, name:'办公⽤房屋'},{value:1548, name:'其他'}],itemStyle: {emphasis: {shadowBlur: 10,shadowOffsetX: 0,shadowColor: 'rgba(0, 0, 0, 0.5)'}}}]};chart.setOption(option);var echarts_b = false;sta.push(setInterval(function (){var thisOption = echarts_b?option:option2;echarts_b = !echarts_b;div.animate({opacity:0},2000,function(){chart.clear();chart.setOption(thisOption);div.animate({opacity:1},1000);})}, 28000))}function getECharts5(boxObj){var id = boxObj.attr("id") + "-echarts-5"var style={width:500,height:300,top:420,right:40,padding:20,border:"1px solid #3f556f",position:"absolute",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,right:40,top:380},900)var chart = echarts.init(div[0]);var xAxisData = [];var data1 = [];var data2 = [];for (var i = 0; i < 100; i++) {xAxisData.push('T' + i);data1.push((Math.sin(i / 5) * (i / 5 -10) + i / 6) * 5);data2.push((Math.cos(i / 5) * (i / 5 -10) + i / 6) * 5);}var option = {title: [{text: '柱状图',textStyle:{color:"#fff",fontSize:16},x:'left',top:4},{text: '动画延迟',textStyle:{color:"#FB9008",fontSize:20},x:'left',left:50}],legend: {data: ['bar', 'bar2'],textStyle:{color:"#fff"},align: 'left',x:"right",},grid: {left: '3%',right: '3%',bottom: '3%',containLabel: true},tooltip: {},xAxis: {},axisLine:lineColor,axisLabel:labelColor},yAxis: {axisLine:lineColor,axisLabel:labelColor,},series: [{name: 'bar',type: 'bar',data: data1,animationDelay: function (idx) {return idx * 10;}}, {name: 'bar2',type: 'bar',data: data2,itemStyle:{normal:{color:"#00AEF1"}},animationDelay: function (idx) {return idx * 10 + 100;}}],animationEasing: 'elasticOut',animationDelayUpdate: function (idx) {return idx * 5;}};chart.setOption(option);sta.push(setInterval(function (){div.animate({opacity:0},1200,function(){chart.clear();chart.setOption(option);div.animate({opacity:1},400);})}, 20100))}function getTable1(boxObj){var id = boxObj.attr("id") + "-table-1"var style={width:500,height:300,top:820,right:-100,border:"1px solid #3f556f",position:"absolute",overflow:"hidden",//background:"rgba(0,174,241,0.2)",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,right:40,top:720},500);var data = [["浙江省⼆建建设集团有限公司","建筑企业","108.18"],["龙元建设集团有限公司","建筑企业","285.22"],["浙江欣捷建设有限公司","建筑企业","145.20"],["浙江万华建设集团股份有限公司","建筑企业","110.68"],["博宏恒基集团有限公司","建筑企业","114.54"],["⼤荣建设有限公司","建筑企业","110.68"],["宁波建⼯股份有限公司","建筑企业","541.88"],["华丰建设股份有限公司","建筑企业","138.50"],];var divContent = "<div class='boxTitle'>2015年宁波市<span>龙头企业</span></div>"; divContent += "<div class='boxRTText'>单位:<span>亿元</span></div>";divContent += "<div class='tableTh'>";divContent += "<span style='width:45%;'>企业名称</span>";divContent += "<span style='width:30%;'>企业类型</span>";divContent += "<span style='width:25%;border:none;'>产值额</span>";divContent += "</div>";divContent += "<div class='tableBody'>";for(var i=0;i<data.length;i++){var trStyle = i%2==0?"background:rgba(0,174,241,0.15);":"";divContent += "<div class='tableTr' style='" + trStyle + "'>";divContent += "<span style='width:45%;color:white;'>" + data[i][0] + "</span>";divContent += "<span style='width:30%;'>" + data[i][1] + "</span>";divContent += "<span style='width:25%;border:none;'>" + data[i][2] + "</span>";divContent += "</div>";}divContent += "</div>";div.html(divContent);sta.push(setInterval(function(){div.find(".tableBody .tableTr").eq(0).slideUp(1000,function(){$(this).show();div.find(".tableBody").append($(this));});},5000))}function getTip1(boxObj){var id = boxObj.attr("id") + "-tip-1"var style={width:1340,height:90,bottom:100,left:580,position:"absolute",overflow:"hidden",padding:"0 20px",//background:"rgba(0,174,241,0.2)",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,bottom:40},500);var flowOutMessage = 9617;var flowInMessage = 17902;divContent += "<div class='tip'>项⽬总数<br><span>59609</span>个</div>";divContent += "<div class='tip'>起重机械<br><span>9617</span>架</div>";divContent += "<div class='tip2'>";divContent += "<div class='tip2_item'><span>今⽇流出：</span><span id='flowoutM'>" + flowOutMessage.toLocaleString() + "</span><span>条</span></div>"; divContent += "<div class='tip2_item'><span>累计数据总量：</span><span>98.9</span><span>GB</span></div>";divContent += "</div>";divContent += "<div class='tip2'>";divContent += "<div class='tip2_item'><span>今⽇流⼊：</span><span id='flowinM'>" + flowInMessage.toLocaleString() + "</span><span>条</span></div>"; divContent += "<div class='tip2_item'><span>累计数据总数：</span><span>885.6366</span><span>万条</span></div>";divContent += "</div>";div.html(divContent);sta.push(setInterval(function (){flowOutMessage += Math.floor(Math.random() * 50);flowInMessage += Math.floor(Math.random() * 50);$("#flowoutM").html(flowOutMessage.toLocaleString());$("#flowinM").html(flowInMessage.toLocaleString());}, 1000))}function getMainDiv(boxObj){var id = boxObj.attr("id") + "-main-div"var style={width:1340,height:800,bottom:150,left:580,position:"absolute",overflow:"hidden",padding:"0 20px",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,bottom:170},500);var divContent = "<div class='cornerLine TLCorner'></div>";divContent += "<div class='cornerLine TRCorner'></div>";divContent += "<div class='cornerLine BLCorner'></div>";divContent += "<div class='cornerLine BRCorner'></div>";divContent += "<div class='MD_title'>宁波建筑业专题</div>";div.append($(divContent));getMDECharts(div);getMDTip(div);getMDMap(div);}function getMDMap(boxObj){var id = boxObj.attr("id") + "-MD-map"var style={width:600,height:600,top:120,left:370,position:"absolute",overflow:"hidden",border:"0px solid #3f556f",background:"rgba(63,85,111,0)",padding:"0 20px","z-index":"2",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1},500);div.html("<div style='zoom:1.2;position:absolute;left:-60px;top:20px;'>" + ningMap + "</div>");//var chart = echarts.init(div[0]);//chart.setOption(option);}function getMDTip(boxObj){var id = boxObj.attr("id") + "-MD-tip"var style={width:300,height:450,top:20,right:65,position:"absolute",overflow:"hidden",//border:"1px solid #3f556f",padding:"0 20px","z-index":"3",opacity:0}var div = creatDiv(id,style,boxObj);div.animate({opacity:1,top:150},500);var divContent = "<div class='MDTipTitle'>鄞州区</div>";divContent += "<div class='MDTipLine'>开⼯项⽬数量与⾯积</div>";divContent += "<div class='MDTipLine2' id='MDTip1'><span>4,017</span>个<span>／28,741</span>万㎡</div>";divContent += "<div class='MDTipLine'>竣⼯项⽬数量与⾯积</div>";divContent += "<div class='MDTipLine2' id='MDTip2'><span>345</span>个<span>／4,216</span>万㎡</div>";divContent += "<div class='MDTipLine'>企业数量</div>";divContent += "<div class='MDTipLine2' id='MDTip3'><span>519</span>家</div>";divContent += "<div class='MDTipLine'>龙头企业</div>";divContent += "<div class='MDTipLine2' id='MDTip4'>";divContent += "浙江万华建设集团股份有限公司";divContent += "<br>⼤荣建设有限公司";divContent += "<br>宁波建⼯股份有限公司";divContent += "</div>";div.html(divContent);sta.push(setInterval(function (){div.fadeOut(1000,function(){var r = Math.floor(Math.random() * areaData.length + 1);div.find("div").eq(0).html(areaData[r]);$("#MDTip1 span").eq(0).html((Math.floor(Math.random() * 5000 + 1000)).toLocaleString());$("#MDTip1 span").eq(1).html(" / "+(Math.floor(Math.random() * 20000 + 4000)).toLocaleString());$("#MDTip2 span").eq(0).html((Math.floor(Math.random() * 2000 + 100)).toLocaleString());$("#MDTip2 span").eq(1).html(" / "+(Math.floor(Math.random() * 5000 + 1000)).toLocaleString());$("#MDTip3 span").html((Math.floor(Math.random() * 1500 + 150)).toLocaleString());div.slideDown(300);})}, 17400))。

RFC 2865 RADIUS 中文翻译收藏Network Working Group C. Rigney Request for Comments: 2865 S. Willens Obsoletes: 2138 LivingstonCategory: Standards Track A. RubensMeritW. SimpsonDaydreamerJune 2000远程认证拨号用户服务（RADIUS）备忘录状态本文档描述了一种Internet社区的Internet标准跟踪协议，它需要进一步进行讨论和建议以得到改进。

请参考最新版的“Internet正式协议标准” (STD1)来获得本协议的标准化程度和状态。

本备忘录可以不受限制地传播。

版权说明Copyright (C) The Internet Society (2000). All Rights Reserved.IESG说明:本协议已经被广泛实现和使用，经验表明当本协议在一个大范围的系统中使用会降低性能和丢失数据。

部分原因是协议中没有提供拥塞控制的机制。

读者可以发现阅读本文对跟踪IETF组织的AAA工作组的工作进程有很大的帮助，AAA工作组可能会开发一个能够更好的解决扩展性和拥塞控制问题的成功的协议。

摘要本文描述了一个传输认证、授权和配置信息的协议。

这些信息在想要认证链路的网络接入服务器（Network Access Server）和共享的认证服务器务器之间传递。

实现说明本备忘录记录了RADIUS协议，RADIUS协议的早期版本使用的UDP端口是16 45，由于和"datametrics"服务冲突，官方为RADIUS协议分配了一个新的端口号1812。

Rigney, et al. Standards Track [Page 1]RFC 2865 RADIUS June 2000目录1. 简介 (3)1.1 描述文档的约定 (4)1.2 术语 (5)2. 操作 (5)2.1 挑战/回应 (7)2.2 使用PAP和CHAP互操作 (8)2.3 代理 (8)2.4 为什么使用UDP (11)2.5 重发提醒 (12)2.6 被证明是有害的心跳 (13)3. 报文格式 (13)4. 报文类型 (17)4.1 接入请求报文 (17)4.2 接入成功回应报文 (18)4.3 接入拒绝回应报文 (20)4.4 接入挑战报文 (21)5. 属性 (22)5.1 User-Name (26)5.2 User-Password (27)5.3 CHAP-Password (28)5.4 NAS-IP-Address (29)5.5 NAS-Port (30)5.6 Service-Type (31)5.7 Framed-Protocol (33)5.8 Framed-IP-Address (34)5.9 Framed-IP-Netmask (34)5.10 Framed-Routing (35)5.11 Filter-Id (36)5.12 Framed-MTU (37)5.13 Framed-Compression (37)5.14 Login-IP-Host (38)5.15 Login-Service (39)5.16 Login-TCP-Port (40)5.17 (unassigned) (41)5.18 Reply-Message (41)5.19 Callback-Number (42)5.20 Callback-Id (42)5.21 (unassigned) (43)5.22 Framed-Route (43)5.23 Framed-IPX-Network (44)5.24 State (45)5.25 Class (46)5.26 Vendor-Specific (47)5.27 Session-Timeout (48)5.28 Idle-Timeout (49)5.29 Termination-Action (49)Rigney, et al. Standards Track [Page 2] RFC 2865 RADIUS June 20005.30 Called-Station-Id (50)5.31 Calling-Station-Id (51)5.32 NAS-Identifier (52)5.33 Proxy-State (53)5.34 Login-LAT-Service (54)5.35 Login-LAT-Node (55)5.36 Login-LAT-Group (56)5.37 Framed-AppleTalk-Link (57)5.38 Framed-AppleTalk-Network (58)5.39 Framed-AppleTalk-Zone (58)5.40 CHAP-Challenge (59)5.41 NAS-Port-Type (60)5.42 Port-Limit (61)5.43 Login-LAT-Port (62)5.44 Table of Attributes (63)6. IANA注意事项 (64)6.1 术语定义 (64)6.2 推荐的注册策略 (65)7. 举例 (66)7.1 用户Telnet到指定主机上 (66)7.2 用户使用CHAP认证方式认证 (67)7.3 用户使用挑战-回应卡 (68)8. 安全事项 (71)9. 更新记录 (71)10. 参考文献 (73)11. 致谢 (74)12. AAA工作组主席地址 (74)13. 作者地址 (75)14. 版权声明 (76)1. 简介本文档废弃了RFC 2138 [1]。

施乐故障诊断代码1 维修呼叫程序呼叫流程……………………………………………………………………………… 2-13 002-xxx HDD002-770 作业模板处理-HD 满RAP……………………………………………… 2-15 003-xxx IPS-ESS 通讯003-318 IIT 软件故障RAP ……………………………………………………… 2-17 003-319 IIT 视频驱动程序检测故障RAP ……………………………………… 2-17 003-320 IISS-ESS 通讯故障1 RAP …………………………………………… 2-18 003-321 IISS-ESS 通讯故障2 RAP …………………………………………… 2-18 003-322 IISS-ESS 通讯故障3 RAP …………………………………………… 2-19 003-323 IISS-ESS 通讯故障4 RAP …………………………………………… 2-19 003-324 IISS-ESS 通讯故障5 RAP …………………………………………… 2-20 003-325 IISS-ESS 通讯故障6 RAP …………………………………………… 2-20 003-326 IISS-ESS 通讯故障7 RAP …………………………………………… 2-21 003-327 IISS-ESS 通讯故障8 RAP …………………………………………… 2-21 003-328 IISS-ESS 通讯故障9 RAP …………………………………………… 2-22 003-329 IISS-ESS 通讯故障10 RAP ………………………………………… 2-22 003-330 IISS-ESS 通讯故障11 RAP ………………………………………… 2-23 003-331 IISS-ESS 通讯故障12 RAP ………………………………………… 2-23 003-332 IISS-ESS 通讯故障13 RAP ………………………………………… 2-24 003-333 IISS-ESS 通讯故障14 RAP ………………………………………… 2-24 003-334 IISS-ESS 通讯故障15 RAP ………………………………………… 2-25 003-335 IISS-ESS 通讯故障16 RAP ………………………………………… 2-25 003-336 IISS-ESS 通讯故障17 RAP ………………………………………… 2-26 003-337 IISS-ESS 通讯故障18 RAP ………………………………………… 2-26 003-338 IISS-ESS 通讯故障19 RAP ………………………………………… 2-27 003-339 IISS-ESS 通讯故障20 RAP ………………………………………… 2-27 003-340 IISS-ESS 通讯故障21 RAP ………………………………………… 2-28 003-341 IISS-ESS 通讯故障22 RAP ………………………………………… 2-28 003-342 IISS-ESS 通讯故障23 RAP ………………………………………… 2-29 003-343 IISS-ESS 通讯故障24 RAP ………………………………………… 2-29 003-345 X PIO 未锁定故障1 RAP ……………………………………………… 2-30 003-346 X PIO 未锁定故障2 RAP ……………………………………………… 2-30 003-750 书本双面-原稿不够RAP ……………………………………………… 2-31 003-751 PANTHER 容量低下（扫描）RAP …………………………………… 2-31 003-753 扫描不能超过300dpi RAP …………………………………………… 2-32 003-760 扫描设置故障RAP……………………………………………………… 2-32 003-761 不正确的纸盘尺寸RAP………………………………………………… 2-33 003-763 未发现调整表RAP……………………………………………………… 2-33 003-780 扫描图像压缩故障RAP………………………………………………… 2-34 003-795 AMS 限制错误RAP …………………………………………………… 2-34 003-942 原稿尺寸自动检测故障RAP…………………………………………… 2-35 003-944 图像重复计数RAP……………………………………………………… 2-35003-945 放大倍率不适合RAP…………………………………………………… 2-36 003-946 每个方向都矛盾（复印APS）RAP…………………………………… 2-36 003-947 返回原稿计数错误RAP………………………………………………… 2-37 003-948 返回原稿不匹配RAP…………………………………………………… 2-37 003-949 原稿不适当（图像覆盖）RAP………………………………………… 2-38 003-950 混合原稿尺寸错误RAP………………………………………………… 2-38 003-955 原稿尺寸交换错误RAP………………………………………………… 2-39 003-956 原稿尺寸不明错误RAP………………………………………………… 2-39 003-957 原稿尺寸错误RAP……………………………………………………… 2-40 003-963 无APS 目标纸盘RAP ………………………………………………… 2-40 003-965 ATS/APS 无纸（IIT 检测）RAP ……………………………………… 2-41 003-966 ATS/APS 无目标（IIT）RAP ………………………………………… 2-41 003-970 传真行存储器溢出RAP………………………………………………… 2-42 003-972 最大存储页溢出RAP…………………………………………………… 2-42 003-973 各个方向都矛盾………………………………………………………… 2-43 003-974 下一原稿规格RAP ……………………………………………………… 2-43 003-976 传真行存储器溢出（N up）RAP ……………………………………… 2-44 003-977 原稿不匹配（多重扫描）RAP ………………………………………… 2-44 003-980 装钉位置错误RAP ……………………………………………………… 2-45 003-981 装钉尺寸错误RAP ……………………………………………………… 2-45 005-xxx DADF005-121 CVT 输送传感器On 卡纸RAP………………………………………… 2-47 005-122 CVT 单面/面1 预定位On 卡纸RAP ………………………………… 2-48 005-123 CVT 单面/面1 定位卡纸RAP ………………………………………… 2-49 005-125 CVT 定位传感器Off 卡纸RAP………………………………………… 2-50 005-131 CVT 翻转On 卡纸RAP………………………………………………… 2-51 005-132 CVT 翻转On 卡纸2RAP ……………………………………………… 2-52 005-134 CVT 翻转传感器Off 卡纸（翻转器）RAP …………………………… 2-53 005-135 CVT 面2 预定位On 卡纸RAP…………………………………………2-54 005-136 CVT 面2 定位On 卡纸RAP…………………………………………… 2-55 005-139 CVT 翻转传感器Off 卡纸RAP………………………………………… 2-56 005-145 CVT 定位传感器Off 卡纸（翻转器）RAP …………………………… 2-57 005-146 CVT 预定位传感器Off 卡纸RAP……………………………………… 2-58 005-147 CVT 预定位传感器Off 卡纸（翻转器）RAP ………………………… 2-59 005-194 在FF 混合尺寸中SS 尺寸不匹配卡纸RAP ………………………… 2-60 005-196 CVT 尺寸不匹配卡纸（无混合）RAP………………………………… 2-61 005-197 禁止组合尺寸卡纸RAP………………………………………………… 2-62 005-198 太短尺寸卡纸RAP……………………………………………………… 2-63 005-199 太长尺寸卡纸RAP……………………………………………………… 2-64 005-280 DADF EEPROM 故障RAP …………………………………………… 2-65 005-283 DADF 高度传感器逻辑故障RAP……………………………………… 2-65 005-284 DADF APS 传感器故障RAP ………………………………………… 2-66 005-285 DADF 轻推辊提升故障RAP…………………………………………… 2-67 005-286 DADF 输出传感器故障RAP…………………………………………… 2-68005-302 DADF 输送器盖联锁打开RAP………………………………………… 2-69 005-304 CVT 稿台联锁打开RAP ……………………………………………… 2-70 005-305 CVT 输送器联锁打开（运行）RAP…………………………………… 2-70 005-307 CVT 稿台联锁在运行中打开RA ……………………………………… 2-71 005-906 CVT 输送传感器静态卡纸RAP ……………………………………… 2-71 005-907 CVT 预定位传感器静态卡纸RAP……………………………………… 2-72 005-908 CVT 定位传感器静态卡纸RAP………………………………………… 2-72 005-913 CVT 翻转传感器静态卡纸RAP………………………………………… 2-73 005-915 CVT APS No1 传感器静态卡纸RAP ………………………………… 2-73 005-916 CVT APS No2 传感器静态卡纸RAP ………………………………… 2-74 005-917 CVT APS No3 传感器静态卡纸RAP ………………………………… 2-74 005-942 DADF 中放置的原稿故障RAP ………………………………………… 2-75 005-943 DADF 盘提升故障RAP ………………………………………………… 2-76 010-xxx 定影器2nd Version 09/2004 状态-指示-维修DC236/286 2-1010-313 控制热敏电阻故障RAP………………………………………………… 2-77 010-314 侧端热敏电阻故障RAP………………………………………………… 2-77 010-318 热-下跌恢复故障RAP ………………………………………………… 2-78 010-320 热辊过热故障RAP……………………………………………………… 2-78 010-327 定影器On 时间故障RAP……………………………………………… 2-79 010-398 定影器锁位故障RAP…………………………………………………… 2-80 012-xxx 装订器012-111 装订器H-传输入口传感器Off 卡纸RAP……………………………… 2-81 012-112 装订器H-传输入口传感器On 卡纸RAP……………………………… 2-82 012-121 H-传输出口传感器Off 卡纸RAP ……………………………………… 2-83 012-126 H-传输入口传感器Off 卡纸RAP ……………………………………… 2-84 012-151 编辑盘入口传感器Off 卡纸RAP ……………………………………… 2-85 012-152 编辑盘入口传感器On 卡纸RAP ……………………………………… 2-86 012-161 装订器压板卡纸RAP…………………………………………………… 2-87 012-162 H-传输出口传感器On 卡纸RAP……………………………………… 2-88 012-211 堆积盘故障RAP………………………………………………………… 2-89 012-212 堆积盘上限故障RAP…………………………………………………… 2-90 012-221 前对齐板原位传感器On 故障RAP…………………………………… 2-91 012-223 前对齐板原位传感器Off 故障RAP…………………………………… 2-92 012-224 后对齐板原位传感器Off 故障RAP…………………………………… 2-93 012-260 排出压板原位传感器On 故障RAP…………………………………… 2-94 012-263 后对齐板故障RAP……………………………………………………… 2-95 012-282 排出压板原位传感器Off 故障RAP ………………………………… 2-96 012-283 放置压板原位传感器On 故障RAP ………………………………… 2-97 012-284 放置压板原位传感器Off 故障RAP ………………………………… 2-98 012-291 装订器故障RAP …………………………………………………… 2-99012-293 装订前角传感器On 故障RAP ………………………………………… 2-100 012-294 装订前角传感器Off 故障RAP ………………………………………… 2-101012-295 装订移动传感器On 故障RAP ………………………………………… 2-102 012-296 装订移动传感器Off 故障RAP ………………………………………… 2-103 012-301 装订器顶盖打开RAP …………………………………………………… 2-104 012-302 装订器前盖打开RAP …………………………………………………… 2-104 012-303 装订器H-传输盖打开RAP …………………………………………… 2-105 012-901 装订器H-传输入口传感器静态卡纸RAP……………………………… 2-105 012-902 H-传输出口传感器静态卡纸RAP……………………………………… 2-106 012-903 纸张留在编辑盘入口传感器RAP……………………………………… 2-106 012-905 编辑盘纸张传感器静态卡纸RAP……………………………………… 2-107 012-923 H-传输入口传感器静态卡纸B RAP…………………………………… 2-107 016-xxx 传真服务016-210 SW 选项故障（HDD 不存在）RAP…………………………………… 2-109 016-211 SW 选项故障（系统存储器不足）RAP ……………………………… 2-109 016-212 SW 选项故障（页存储器不足）RAP ………………………………… 2-110 016-213 SW 选项故障（打印机卡不存在）RAP ……………………………… 2-110 016-214 SW 选项故障（传真卡不存在）RAP ………………………………… 2-111 016-215 SW 选项故障（JPEG 板不存在）RAP ……………………………… 2-111 016-311 扫描器未安装RAP……………………………………………………… 2-112 016-315 IIT 接口故障RAP ……………………………………………………… 2-112 016-316 未检测到页存储器RAP………………………………………………… 2-113 016-317 页存储器中止-标准RAP ……………………………………………… 2-113 016-318 页存储器中止-选项RAP ……………………………………………… 2-114 016-321 传真模块故障RAP …………………………………………………… 2-114 016-322 JBA 帐户满RAP………………………………………………………… 2-115 016-450 SMB 主机名重复RAP ………………………………………………… 2-115 016-454 DNS 动态更新故障RAP ……………………………………………… 2-116 016-455 SNTP 服务器超时RAP ………………………………………………… 2-116 016-456 SNTP 时间异步RAP …………………………………………………… 2-117 016-503 SMTP 服务器重定向故障RAP………………………………………… 2-117 016-504 POP 服务器重定向故障RAP ………………………………………… 2-118 016-505 POP 重定向验证故障RAP …………………………………………… 2-118 016-600 KO 验证锁定RAP ……………………………………………………… 2-119 016-601 非法访问检测RAP……………………………………………………… 2-119 016-701 ART EX 内存不足RAP………………………………………………… 2-120 016-702 页缓冲器不足RAP……………………………………………………… 2-120 016-703 E-mail 至无效邮箱R AP………………………………………………… 2-121 016-704 邮箱满RAP……………………………………………………………… 2-121 016-705 安全打印故障RAP……………………………………………………… 2-122 016-706 最大用户数超出RAP…………………………………………………… 2-122 016-707 样本打印故障RAP……………………………………………………… 2-123 016-708 HD 因注解/水印图象而满RAP………………………………………… 2-123 016-709 ART EX 命令故障RAP………………………………………………… 2-124 016-710 延时打印故障RAP……………………………………………………… 2-124 016-711 E-mail 传输尺寸限制超出RAP………………………………………… 2-125016-712 PANTHER 能下低下（I-Formatted）RAP…………………………… 2-125016-716 TIFF 数据溢出RAP …………………………………………………… 2-126016-718 超出PCL6 存储器RAP………………………………………………… 2-126016-719 超出PCL 存储器RAP ………………………………………………… 2-127016-720 PCL 命令故障RAP……………………………………………………… 2-127016-721 其它错误RAP…………………………………………………………… 2-128016-722 作业被装订位置NG 删除RAP………………………………………… 2-128016-728 不支持TIFF 数据RAP ………………………………………………… 2-129016-729 TIFF 数据尺寸太大RAP ……………………………………………… 2-129016-730 不支持ART 命令RAP ………………………………………………… 2-130016-731 无效TIFF 数据RAP …………………………………………………… 2-130016-732 表格未注册RAP………………………………………………………… 2-131016-735 更新作业模板RAP……………………………………………………… 2-131016-736 远程目录加锁错误……………………………………………………… 2-132016-737 远程加锁目录卸载错误………………………………………………… 2-132016-746 不支持PDF 文件RAP ………………………………………………… 2-133016-748 HD 满RAP ……………………………………………………………… 2-133016-749 JCL 语法错误RAP……………………………………………………… 2-134016-751 PDF 故障RAP ………………………………………………………… 2-134016-752 PDF 内存不足RAP……………………………………………………… 2-135016-753 PDF 命令不匹配RAP…………………………………………………… 2-135016-754 PDF LZW 未安装RAP ………………………………………………… 2-136016-755 PDF 打印被禁止RAP ………………………………………………… 2-136016-756 审计-禁止服务RAP …………………………………………………… 2-137016-757 审计-无效用户RAP …………………………………………………… 2-137016-758 审计-禁止功能RAP …………………………………………………… 2-138016-759 审计-达到限制RAP …………………………………………………… 2-138016-760 PS 解压缩故障RAP …………………………………………………… 2-139016-761 FIFO 空RAP …………………………………………………………… 2-139016-762 打印语言未安装RAP…………………………………………………… 2 - 1 4 0状态-指示-维修09/2004 2nd Version2-2 DC236/286016-764 SMTP 服务器连接故障RAP…………………………………………… 2 - 1 4 0 016-765 SMTP 服务器HDD 满RAP …………………………………………… ___________2 - 1 4 1016-766 SMTP 服务器文件系统RAP…………………………………………… 2 - 1 4 1 016-767 无效的E-mail 地址RAP ……………………………………………… 2 - 1 4 2016-768 无效的发送者地址……………………………………………………… 2 - 1 4 2 016-769 SMTP 服务器不支持DNS RAP ……………………………………… 2 - 1 4 3016-771 扫描数据贮藏室（DNS 地址）错误RAP …………………………… 2 - 1 4 4016-772 扫描数据贮藏室（DNS 库）错误RAP ……………………………… 2 - 1 4 4016-773 无效的IP 地址RAP …………………………………………………… 2 - 1 4 4016-774 HD 满-压缩转换RAP…………………………………………………… 2 - 1 4 5 016-775 HD 满-图像转换RAP…………………………………………………… 2 - 1 4 5016-776 图像转换错误RAP……………………………………………………… 2 - 1 4 6016-777 图像转换错误RAP……………………………………………………… 2 - 1 4 6016-778 HD 满-扫描图像转换RAP……………………………………………… 2 - 1 4 7 016-779 扫描图像转换错误RAP………………………………………………… 2 - 1 4 7016-780 HD 访问错误-图像转换RAP…………………………………………… 2 - 1 4 8 016-781 扫描服务器连接错误RAP……………………………………………… 2 - 1 4 8016-782 扫描服务器登录错误RAP……………………………………………… 2 - 1 4 9016-783 无效的服务器路径RAP………………………………………………… 2 - 1 4 9016-784 服务器写错误RAP……………………………………………………… 2 - 1 5 0016-785 服务器HD 满RAP……………………………………………………… 2 - 1 5 0 016-786 HD 满-扫描写入错误RAP……………………………………………… 2 - 1 5 1 016-787 无效的服务器IP 地址RAP …………………………………………… 2 - 1 5 1016-788 检查浏览器故障RAP…………………………………………………… 2 - 1 5 2016-789 HD 满-作业存储器RAP………………………………………………… 2 - 1 5 2 016-791 文件检索故障RAP……………………………………………………… 2 - 1 5 3016-792 未发现指定作业RAP…………………………………………………… 2 - 1 5 3016-793 MF I/O HD 满RAP……………………………………………………… 2 - 1 5 4 016-798 No Trust Marking 选择RAP…………………………………………… 2 - 1 5 4016-799 PL W 打印指令故障RAP ……………………………………………… 2 - 1 5 5016-981 HDD 访问错误RAP …………………………………………………… 2 - 1 5 5016-982 HDD 访问错误2 RAP ………………………………………………… 2 - 1 5 6016-985 数据尺寸溢出（扫描到E-mail）RAP………………………………… 2 - 1 5 6021-xxx 传真021-360 EP 附件故障RAP……………………………………………………… ___________2-15 7021-361 EP 附件各类配置错误RAP…………………………………………… 2-15 7021-732 EP 附件-服务被禁用RAP …………………………………………… 2-15 8021-733 EP 附件-服务受彩色模式限制RAP ………………………………… 2-15 8021-750 用过零件请求处理故障（EP-SV）RAP …………………………… 2-15 9021-751 维护请求故障（EP-SV）RAP………………………………………… 2-1 5 9021-770 用过零件请求处理故障（EP-SV）RAP……………………………… 2-1 6 0021-771 维护请求故障（EP-DX）RAP………………………………………… 2 - 1 6 0021-772 EP-DX-安装/卸载故障RAP…………………………………………… 2-16 1021-941 EP-扫描服务因禁用而暂行RAP……………………………………… 2-16 1021-942 EP-扫描服务因彩色模式而暂行RAP………………………………… 2-16 2021-943 EP-打印服务因禁用而暂行RAP……………………………………… 2-16 2021-944 EP-打印服务因彩色模式而暂行RAP………………………………… 2-16 3021-945 EP-服务因禁用而暂行RAP…………………………………………… 2-16 3021-946 EP-服务因彩色模式而暂行RAP……………………………………… 2-16 4024-xxx IOT-ESS 通讯024-340 IOT-ESS 通讯故障1 RAP……………………………………………… 2-165024-341 IOT-ESS 通讯故障2 RAP……………………………………………… 2-165024-342 IOT-ESS 通讯故障3 RAP……………………………………………… 2-166024-343 IOT-ESS 通讯故障4 RAP……………………………………………… 2-166024-345 IOT-ESS 通讯故障5 RAP……………………………………………… 2-167 024-346 IOT-ESS 通讯故障6 RAP……………………………………………… 2-167 024-347 IOT-ESS 通讯故障7 RAP……………………………………………… 2-168 024-348 IOT-ESS 通讯故障8 RAP……………………………………………… 2-168 024-349 IOT-ESS 通讯故障9 RAP……………………………………………… 2-169 024-350 IOT-ESS 通讯故障10 RAP …………………………………………… 2-169 024-351 IOT-ESS 通讯故障11 RAP …………………………………………… 2-170 024-354 IOT-ESS 通讯故障14 RAP …………………………………………… 2-170 024-356 IOT-ESS 通讯故障16 RAP …………………………………………… 2-171 024-362 页面同步非法启动RAP………………………………………………… 2-171 024-363 页面同步非法停止RAP………………………………………………… 2-172 024-364 DMA 传输故障RAP …………………………………………………… 2-172 024-367 解压缩其他故障RAP…………………………………………………… 2-173 024-368 PCI 错误RAP…………………………………………………………… 2-173 024-370 标志码检测故障RAP…………………………………………………… 2-174 024-371 IOT-ESS 通讯故障21 RAP …………………………………………… 2-174 024-372 IOT-ESS 通讯故障22 RAP …………………………………………… 2-175 024-373 IOT-ESS 通讯故障23 RAP …………………………………………… 2-175 024-375 IOT-ESS 通讯故障23 RAP …………………………………………… 2-176 024-746 打印请求故障—纸张RAP……………………………………………… 2-176 024-747 打印指令故障RAP……………………………………………………… 2-177 024-910 纸盘1 尺寸不匹配RAP………………………………………………… 2-177 024-911 纸盘2 尺寸不匹配RAP………………………………………………… 2-178 024-912 纸盘3 尺寸不匹配RAP………………………………………………… 2-179 024-913 纸盘4 尺寸不匹配RAP………………………………………………… 2-180 024-916 混合满堆积盘RAP……………………………………………………… 2-181 024-917 堆积盘装订超出计数RAP……………………………………………… 2-182 024-919 面朝上盘关闭RAP……………………………………………………… 2-183 024-946 纸盘1 不在位RAP …………………………………………………… 2-183 024-947 纸盘2 不在位RAP……………………………………………………… 2-184 024-948 纸盘3 不在位RAP……………………………………………………… 2-184 024-949 纸盘4 不在位RAP……………………………………………………… 2-185 024-950 纸盘1 空RAP ………………………………………………………… 2-185 024-951 纸盘2 空RAP…………………………………………………………… 2-186 024-952 纸盘3 空RAP…………………………………………………………… 2-186 024-953 纸盘4 空RAP…………………………………………………………… 2-187 024-954 MSI 空RAP …………………………………………………………… 2-187 024-958 MSI 尺寸故障RAP …………………………………………………… 2-188 024-959 纸盘1 尺寸不匹配RAP ……………………………………………… 2-188 024-960 纸盘2 尺寸不匹配RAP………………………………………………… 2-189 024-961 纸盘3 尺寸不匹配RAP………………………………………………… 2-189 024-962 纸盘4 尺寸不匹配RAP………………………………………………… 2-190 024-964 装订器张数超出RAP…………………………………………………… 2-190 024-965 ATS/APS 无纸（IOT 检测）RAP …………………………………… 2-191024-966 ATS/APS 元目标错误RAP …………………………………………… 2-192 024-967 不同宽度混合纸张检测(装订器作业) RAP …………………………… 2-192 2nd Version 09/2004 状态-指示-维修DC236/286 2-3024-976 装订器装订静态NG RAP ……………………………………………… 2-193 024-977 装订器输送准备故障RAP……………………………………………… 2-193 024-979 装订器接近空RAP……………………………………………………… 2-194 024-980 装订器堆积盘满RAP…………………………………………………… 2-194 024-982 堆积盘下安全警告RAP………………………………………………… 2-195 024-985 MSI 输送故障RAP……………………………………………………… 2-196 024-986 打印全部确认RAP……………………………………………………… 2-197 025-xxx 诊断HDD025-596 诊断HDD 维护故障RAP ……………………………………………… 2-199 025-597 诊断HDD 初始化故障RAP …………………………………………… 2-199 027-xxx MAIL027-452 重复IP 地址RAP ……………………………………………………… 2-201 027-500 SMTP 服务器邮件I/O 故障RAP……………………………………… 2-201 027-501 POP 服务器邮件I/O 故障RAP………………………………………… 2-202 027-502 POP 邮件I/O 验证故障RAP…………………………………………… 2-202 027-700 媒体故障RAP…………………………………………………………… 2-203 027-701 未找到媒体RAP………………………………………………………… 2-203 027-702 媒体数据未找到/不支持RAP ………………………………………… 2-204 027-703 媒体读出器故障/未连接RAP ………………………………………… 2-204 027-710 因效S/MIME 邮件错误RAP…………………………………………… 2-205 027-711 S/MIME 邮件发送者证书未找到RAP ………………………………… 2-205 027-712 S/MIME 邮件发送者证书无效RAP …………………………………… 2-206 027-713 S/MIME 邮件被改变RAP……………………………………………… 2-206 027-714 S/MIME 邮件发送者假冒RAP………………………………………… 2-207 027-715 S/MIME 邮件证书不被支持RAP……………………………………… 2-207 027-716 禁止接收没有签名的E-mail RAP……………………………………… 2-208 027-720 未找到扩展服务器主机RAP…………………………………………… 2-208 027-721 未找到扩展服务器RAP………………………………………………… 2-209 027-722 扩展服务器时故障RAP …………………………………………… 2-209 027-723 扩展服务器验证故障RAP……………………………………………… 2-210 027-724 扩展服务器访问故障故障RAP………………………………………… 2-210 027-725 扩展服务器操作故障RAP……………………………………………… 2-211 027-726 扩展服务器未知状态RAP……………………………………………… 2-211 027-727 扩展服务器请求无效参数RAP………………………………………… 2-212 027-737 模板服务器读取错误RAP……………………………………………… 2-212 027-739 无效模板服务器路径RAP……………………………………………… 2-213 027-740 模板服务器登录错误RAP……………………………………………… 2-213 027-741 模板服务器连接故障RAP……………………………………………… 2-214 027-742 HD 文件系统满RAP …………………………………………………… 2-214 027-743 模板服务器安装错误RAP……………………………………………… 2-215027-744 模板服务器地址错误（CDNS 带）RAP ……………………………… 2-215 027-745 模板服务器地址错误（CDNS 地址）RAP …………………………… 2-216 027-746 作业模板服务器未准备RAP…………………………………………… 2-216 027-750 传真文件不适合RAP…………………………………………………… 2-217 027-751 作业模板分析错误RAP………………………………………………… 2-217 027-752 要求的用户输入未输入RAP…………………………………………… 2-218 027-753 作业流服务请求禁止RAP……………………………………………… 2-218 027-796 E-mail 不打印RAP……………………………………………………… 2-219 027-797 无效输出目标RAP……………………………………………………… 2-219 033-xxx 传真控制033-363 传真卡复位(重新引导)RAP …………………………………………… 2-221 033-710 原稿不存在RAP………………………………………………………… 2-221 033-711 文档中存在非法页面RAP……………………………………………… 2-222 033-712 系统内存溢出RAP……………………………………………………… 2-222 033-713 未指定链-环RAP ……………………………………………………… 2-223 033-714 扫描错误（未指定文档）RAP ………………………………………… 2-223 033-715 不能启动作业RAP……………………………………………………… 2-224 033-716 无指定MAILBOX RAP ………………………………………………… 2-224 033-717 不正确口令RAP………………………………………………………… 2-225 033-718 邮箱中无文档RAP……………………………………………………… 2-225 033-719 被删除传真作业不能恢复RAP………………………………………… 2-226 033-720 文档创建故障RAP……………………………………………………… 2-226 033-721 页面创建故障RAP……………………………………………………… 2-227 033-724 传真接收存储器溢出RAP……………………………………………… 2-227 033-725 HDD 空间不足RAP …………………………………………………… 2-228 033-726 不能打印双面RAP……………………………………………………… 2-228 033-727 不能旋转图像RAP……………………………………………………… 2-229 033-728 删除自动打印RAP……………………………………………………… 2-229 033-730 传真服务恢复错误RAP………………………………………………… 2-230 033-731 指令不一致RAP………………………………………………………… 2-230 033-732 打印作业被强制轮询删除RAP………………………………………… 2-231 033-733 传真文档号获取错误RAP……………………………………………… 2-231 033-734 传真打印悬置RAP……………………………………………………… 2-232 033-735 传真存储器地址分配超时RAP………………………………………… 2-232 033-736 IFAX Off Ramp 错误RAP……………………………………………… 2-233 033-737 传真卡作业删除RAP…………………………………………………… 2-233 033-738 JBIG 信息故障RAP…………………………………………………… 2-234 033-740 传真直接接收打印删除RAP…………………………………………… 2-234 033-741 传真页面读取打开超时RAP…………………………………………… 2-235 033-742 传真页面读取关闭超时RAP…………………………………………… 2-235 033-743 传真页面写入打开超时RAP…………………………………………… 2-236 033-744 传真页面写入关闭超时RAP…………………………………………… 2-236 033-745 传真数据写入超时RAP………………………………………………… 2-237 033-746 传真数据读取超时RAP………………………………………………… 2-237033-747 传真服务不能启动RAP………………………………………………… 2-238 033-748 传真服务非法顺序RAP………………………………………………… 2-238 033-749 传真卡内存错误RAP…………………………………………………… 2-239 033-750 传真格式错误RAP……………………………………………………… 2-239 033-790 EP-DX 呼叫等待(不重拨计数)RAP …………………………………… 2-240 033-791 EP-DX 呼叫等待(重拨计数)RAP ……………………………………… 2-240 033-792 EP-DX 呼叫停止RAP ………………………………………………… 2-241 034-xxx 传真通讯034-211 传真选项槽1 板故障RAP……………………………………………… 2-243 034-212 传真选项槽1 板故障RAP……………………………………………… 2-243 034-500 不正确拨号数据RAP…………………………………………………… 2-244 034-501 所连通道拨号错误RAP………………………………………………… 2-244 034-502 传真内部不可缺少参数错误RAP……………………………………… 2-245 034-503 传真内部高层服务错误RAP…………………………………………… 2-245 034-504 传真储存存储器溢出RAP……………………………………………… 2-246 034-505 传真工作存储器溢出RAP……………………………………………… 2-246 状态-指示-维修09/2004 2nd Version2-4 DC236/286034-506 不支持远程功能RAP…………………………………………………… 2-247 034-507 口令检查错误RAP……………………………………………………… 2-247 034-508 通过DTMF 删除传输RAP …………………………………………… 2-248 034-509 DTMF 非法程序错误RAP……………………………………………… 2-248 034-510 DTMF 程序错误RAP…………………………………………………… 2-249 034-511 远程机器不能发送文件RAP…………………………………………… 2-249 034-512 检测到无尽循环RAP…………………………………………………… 2-250 034-513 接收命令错误RAP……………………………………………………… 2-250 034-514 请求的功能不支持RAP………………………………………………… 2-251 034-515 非法命令被接收RAP…………………………………………………… 2-251 034-519 接收数量超出RAP……………………………………………………… 2-252 034-520 服务数量超出RAP……………………………………………………… 2-252 034-521 内部I/F 错误RAP ……………………………………………………… 2-253 034-522 无手动发送线路RAP…………………………………………………… 2-253 034-523 传真服务被禁止RAP…………………………………………………… 2-254 034-524 不能删除操作RAP……………………………………………………… 2-254 034-525 指定的链-环不存在RAP ……………………………………………… 2-255 034-526 不正确的链-环值RAP ………………………………………………… 2-255 034-527 拨号控制错误RAP……………………………………………………… 2-256 034-528 不能执行手动发送RAP………………………………………………… 2-256 034-529 无打印的纸张尺寸RAP………………………………………………… 2-257 034-530 DTMF I/F 超时RAP …………………………………………………… 2-257 034-700 G3 节Dicep 超时RAP ………………………………………………… 2-258 034-701 软件复位RAP…………………………………………………………… 2-258 034-702 无指定目标RAP………………………………………………………… 2-259 034-703 D 信道与网络连接切断RAP…………………………………………… 2-259034-704 ISDN D 信道数据连接错误RAP ……………………………………… 2-260 034-705 ISDN 层1 停止-电源ON ……………………………………………… 2-260 034-706 ISDN 层1 停止-电源OFF……………………………………………… 2-261 034-707 FRMR 被接收…………………………………………………………… 2-261 034-708 非法帧接收N（R）…………………………………………………… 2-262 034-709 非法帧接收……………………………………………………………… 2-262 034-710 …………………………………………………………………………… 2-263 034-711 等待连接超时…………………………………………………………… 2-263 034-712 内部错误（中断）……………………………………………………… 2-264 034-713 超时-传输删除…………………………………………………………… 2-264 034-714 线路断开-超时T305 …………………………………………………… 2-265 034-715 线路断开-超时3082 …………………………………………………… 2-265 034-716 连接超时（T313）……………………………………………………… 2-266 034-717 Resume 超时…………………………………………………………… 2-266 034-718 正常断开………………………………………………………………… 2-267 034-719 无空闲和有效线路……………………………………………………… 2-267 034-720 超时（60s,T330,309,301,310）……………………………………… 2-268 034-721 错误（格式化，内容）………………………………………………… 2-268 034-722 悬挂超时………………………………………………………………… 2-269 034-723 无指定计时器RAP……………………………………………………… 2-269 034-724 非法顺序RAP…………………………………………………………… 2-270 034-725 L3 任务内部错误RAP ………………………………………………… 2-270 034-726 HD81501 I/F 缓冲器忙RAP…………………………………………… 2-271 034-727 任务无响应（对1,300Hz 输入呼叫为3 秒）RAP ………………… 2-271 034-728 无效的目标RAP………………………………………………………… 2-272 034-729 线路切断，内部通道PB 发送RAP…………………………………… 2-272 034-730 输入和输出呼叫冲突…………………………………………………… 2-273 034-731 传真网络切断（设置错误）…………………………………………… 2-273 034-732 传真网络因超时而被切断……………………………………………… 2-274 034-733 不正确顺序，呼叫状态………………………………………………… 2-274 034-734 HI 任务内部错误RAP ………………………………………………… 2-275 034-735 只与ISDN D 信道连接………………………………………………… 2-275 034-736 来自传真网络的错误通知……………………………………………… 2-276 034-737 输入呼叫响应错误RAP………………………………………………… 2-276 034-738 层1 启动错误…………………………………………………………… 2-277 034-739 层1 不同步……………………………………………………………… 2-277 034-740 帧传输错误……………………………………………………………… 2-278 034-741 不能发送帧……………………………………………………………… 2-278 034-742 帧发送低速被检测……………………………………………………… 2-279 034-743 不正常发送帧DMA RAP ……………………………………………… 2-279 034-744 不能接受的信道RAP…………………………………………………… 2-280 034-745 呼出信道设置…………………………………………………………… 2-280 034-746 无可使用线路…………………………………………………………… 2-281 034-747 转换设备拥挤…………………………………………………………… 2-281034-748 指定线路无法使用……………………………………………………… 2-282 034-750 网络错误………………………………………………………………… 2-282 034-751 临时网络错误…………………………………………………………… 2-283 034-752 目标终端忙……………………………………………………………… 2-283 034-753 目标不应答……………………………………………………………… 2-284 034-754 无来自目标的响应……………………………………………………… 2-284 034-755 目标拒绝呼叫…………………………………………………………… 2-285 034-756 目标故障………………………………………………………………… 2-285 034-757 其它（正常，半正常）………………………………………………… 2-286 034-758 不正确目标传真拨号号码……………………………………………… 2-286 034-759 无中转网络路由………………………………………………………… 2-287 034-760 无到目标线路…………………………………………………………… 2-287 034-761 不正确格式目标传真号码……………………………………………… 2-288 034-762 设备拒绝………………………………………………………………… 2-288 034-763 通讯能力不允许………………………………………………………… 2-289 034-764 通讯能力未被配置……………………………………………………… 2-289 034-765 服务，性能限制带来的错误…………………………………………… 2-290 034-766 所选择的通讯不执行…………………………………………………… 2-290 034-767 所选模式不执行………………………………………………………… 2-291 034-768 只有有限数字信息……………………………………………………… 2-291 034-769 服务，性能产生的错误………………………………………………… 2-292 034-770 应答状态查询…………………………………………………………… 2-292 034-771 访问信息被放弃………………………………………………………… 2-293 034-772 工作之间连接错误……………………………………………………… 2-293 034-773 指定拨号号码无效……………………………………………………… 2-294 034-774 指定的线路无效………………………………………………………… 2-294 034-775 其他（无效信息类）…………………………………………………… 2-295 034-776 所需信息不够…………………………………………………………… 2-295 034-777 不明确的信息类型……………………………………………………… 2-296 034-778 不正确信息或类型……………………………………………………… 2-296 034-779 无信息或未定义………………………………………………………… 2-297 034-780 无效信息………………………………………………………………… 2-297 034-781 呼叫状态，信息不匹配………………………………………………… 2-298 034-782 因超时而被错误清除…………………………………………………… 2-298 2nd Version 09/2004 状态-指示-维修DC236/286 2-5034-783 其它错误（操作等）…………………………………………………… 2-299 034-784 目标号码改变…………………………………………………………… 2-299 034-785 不兼容目标……………………………………………………………… 2-300 034-786 呼叫识别码不在使用中………………………………………………… 2-300 034-787 呼叫识别码在使用中…………………………………………………… 2-301 034-788 显示其它原因…………………………………………………………… 2-301 034-789 G4 表示层非法事件…………………………………………………… 2-302 034-790 线路1 未被连接RAP…………………………………………………… 2-302034-791 线路0（分机）未被连接RAP ………………………………………… 2-303034-792 线路2 未被连接RAP…………………………………………………… 2-303034-793 线路3 未被连接RAP…………………………………………………… 2-304034-794 线路4 未被连接RAP…………………………………………………… 2-304034-795 线路5 未被连接RAP…………………………………………………… 2-305034-796 拨号错误（不正确传真号码2）RAP ………………………………… 2-305034-797 通讯参数错误RAP……………………………………………………… 2-306034-798 数据参数错误RAP……………………………………………………… 2-306034-799 自动拨号无拨号数据RAP……………………………………………… 2-307035-xxx 传真网络035-700 Modem 故障RAP ……………………………………………………… ___________2-309035-701 T1 传输超时RAP ……………………………………………………… 2-309035-702 目标接收被拒绝RAP ………………………………………………… 2-310035-703 以相位B 发送时接收到DCN RAP …………………………………… 2-310035-704 目标轮询错误RAP……………………………………………………… 2-311035-705 DCS/NSS 重新发送超限RAP ………………………………………… 2-311035-706 减速运行错误RAP …………………………………………………… 2-312035-707 错误的口令/接收错误RAP …………………………………………… 2-312035-708 后-信息重发超限RAP ………………………………………………… 2-313035-709 RTN 接收RAP ………………………………………………………… 2-313035-710 PIN 接收RAP…………………………………………………………… 2-314035-711 DCN 接收在相位D RAP ……………………………………………… 2-314035-712 3 NSC 后无响应RAP ………………………………………………… 2-315035-713 发送FTT 之后T2 超时RAP…………………………………………… 2-315035-714 NSC/DTC 之后接收到DCN RAP……………………………………… 2-316035-715 错误口令-轮询错误RAP ……………………………………………… 2-316035-716 无后信息-T2 超时RAP ………………………………………………… 2-317035-717 RTN 发送RAP ………………………………………………………… 2-317035-718 接收T1 超时RAP ……………………………………………………… 2-318035-719 检测到忙音RAP………………………………………………………… 2-318035-720 不能被远程机器接收RAP……………………………………………… 2-319035-721 DCN 接收在相位B RAP ……………………………………………… 2-319035-722 错误的300bps 帧长度RAP …………………………………………… 2-320035-723 接收标记之后无CD RAP ……………………………………………… 2-320035-724 发送FTT 之后接收DCN RAP ………………………………………… 2-321035-725 远程机器没有邮箱/中继RAP ………………………………………… 2-321035-726 相位C 不能接收-10 秒RAP…………………………………………… 2-322035-727 G3 接收期间50%错误RAP…………………………………………… 2-322035-728 C EOL 不能在10 秒之内接收RAP…………………………………… 2-323035-729 检测到载波减弱RAP…………………………………………………… 2-323035-730 相位C 高速无CS RAP………………………………………………… 2-324035-731 传真V.8 错误RAP ……………………………………………………… 2-324035-732 传真V.34 PCH CD Off RAP ………………………………………… 2-325035-733 传真V.34 C/PCH CS 无RAP………………………………………… 2-325 035-734 远程V8 程序轮询错误RAP …………………………………………… 2-326 035-735 轮询箱V8 程序中无文件RAP ………………………………………… 2-326 035-736 发送CTC 之后无应答DCN RAP……………………………………… 2-327 035-737 发送EOR 之后无应答DCN RAP……………………………………… 2-327 035-738 发送RR 之后无应答DCN RAP ……………………………………… 2-328 035-739 传真15 超时RAP ……………………………………………………… 2-328 035-740 E-OR 发送之后发送停止RAP ………………………………………… 2-329 035-741 ECM 相位C 标记超时RAP …………………………………………… 2-329 035-742 EOR 发送或接收RAP ………………………………………………… 2-330 035-743 远程机器不能接收SUB RAP ………………………………………… 2-330 035-744 远程机器不能接收口令RAP…………………………………………… 2-331 035-745 PTX 无SEP 功能RAP ………………………………………………… 2-331 035-746 忙-不能检测拨号音RAP ……………………………………………… 2-332 035-747 拨号时中止RAP………………………………………………………… 2-333 035-748 传输期间中止RAP……………………………………………………… 2-333 035-749 无来自远程站的应答RAP……………………………………………… 2-334 035-750 传输期间电源Off RAP ………………………………………………… 2-334 035-751 文件发送操作被删除RAP……………………………………………… 2-335 035-752 作业数限制错误RAP…………………………………………………… 2-335 035-753 传真存储器满RAP……………………………………………………… 2-336 035-754 文件管理存储器满RAP………………………………………………… 2-336 035-755 文件加页错误RAP……………………………………………………… 2-337 035-756 不能加页RAP…………………………………………………………… 2-337 035-757 无接收页RAP…………………………………………………………… 2-338 035-758 无指定文件或页RAP…………………………………………………… 2-338 035-759 无指定作业RAP………………………………………………………… 2-339 035-760 文件公共处理错误RAP………………………………………………… 2-339 035-761 文件其它处理错误RAP………………………………………………… 2-340 035-762 ISDN 期间线路切断RAP ……………………………………………… 2-340 036-xxx 传真参数036-500 非法PDRP 参数………………………………………………………… 2-341 036-501 非法RDPBP 参数……………………………………………………… 2-341 036-502 非法RDPBN 参数……………………………………………………… 2-342 036-503 非法RDCLP 参数……………………………………………………… 2-342 036-504 非法RDGR 参数………………………………………………………… 2-343 036-505 未定义响应……………………………………………………………… 2-343 036-506 不可协商………………………………………………………………… 2-344 036-507 在容量满时接收RDPBN ……………………………………………… 2-344 036-508 RDPBN 接收终端错误………………………………………………… 2-345 036-509 RDPBN 接收其它……………………………………………………… 2-345 036-510 RDGR 接收……………………………………………………………… 2-346 036-511 非法程序1551 RAP …………………………………………………… 2-346 036-512 非法CDS 参数………………………………………………………… 2-347。

AS-International AssociationActuator Sensor Interface(AS-Interface®)Test Requirements MasterVersion 1.2, Revision 1.1Apr. 05, 2002ConfidentialFor internal use of the members only or for companies which have bought the documentation from the AssociationTest Requirements Master 1.2 Rev. 1.1AcceptanceThese test requirements have been accepted by the Technical Commission of the AS International Association in its meeting on April 10, 2002 and by the Management Committee in its meeting on May 14, 2002.File date: August 8th, 2002Test Requirements for AS-Interface MasterContents:A. General (1)1. Basic tests (4)2. Simplified test (4)3. Additional tests (4)4. Precedence (4)B. Test instructions (4)1. Test instruction: Current consumption (5)2. Test instruction: Noise emission AS-i master (8)3. Test instructions: Impedance and symmetry measurement (11)4. Test instruction: Power-on behaviour (21)5. Test instruction: Burst test (25)6. Test instruction: Analogue part (31)7. Test instruction: Voltage cutoff (34)8. Test instruction: Logical start-up behaviour (37)9. Test instruction: Logical behaviour in normal operation (40)10. Test instruction: Analogue profile (43)11. Test instruction: Functions in accordance with PICS (45)12. Test instruction: Time response (49)13. Test instruction: Security of data (52)C. Forms for technical reports (56)Annex: (77)Test Requirements Master 1.2 Rev. 1.1A. General1. Basic testsThese test requirements for the AS-Interface master describe the minimum extent of a basic test to be carried out on the AS-i master to section 4.4 (2) of the Certification Guidelines (ZRL) for AS-i products.AS-i masters forming a part of a higher-level system, e.g. couplers (gateways) to higher-level bus systems or masters with integrated host functions (AS-i control) are also tested in accordance with these test requirements if applicable. Host functions shall be accessible or realised in the higher-level system in accordance with these test requirements.If an AS-i power supply is integrated in the AS-i master, the master is additionally subject to the test requirements for AS-i power supplies.If the AS-i master contains components already tested and approved by the AS-i Association these components will not be tested again (section 4.4 (3) of the ZRL).All standard AS-i components used for testing purposes shall be AS-i certified.2. Simplified testSimplified tests to section 4.5 ZRL shall use parts of these test requirements if applicable.3. Additional testsIn special cases the test laboratory is entitled to execute additional tests beyond these test requirements in accordance with the valid specification or shall demand them from the manufacturer.4. PrecedenceIn the case of discrepancies between these test requirements and the AS-i specifications the complete specification takes precedence.instructionsB. TestAll tests described in these test requirements shall have an accuracy of 1% unless stated otherwise, and shall be documented accordingly in the test protocols.For test purposes, the connection between the master and the AS-i shall be made by means of a split plug.All logical tests shall be recorded via AS-i bus monitor. All recordings of the monitor are saved as a file on a diskette which shall be part of the test report. In the case of errors in the logical tests a printout of the monitor recordings shall be made additionally. To protect the files from corruption, a check sum shall be put on the contents of the files. The directory listing contents and check sum shall be enclosed with the test report.1. Test instruction: Current consumptionReference: Specification AS-i master (chapter 7 of the Complete Specification),Master profiles,Test requirements for AS-i power supplies1.1 GeneralThe test requirements allow measurement of the current consumption of an AS-i master. These test requirements become obsolete if the master has an integrated AS-i power supply. In that case, however, all tests of the test requirements for AS-i power supplies have to be additionally fulfilled by the master.The manufacturer shall provide the following information:1. current data sheet,used2. profile1.2 Test circuitFigure 1 shows the required test circuit.Figure 1: Test circuit for current consumption test1.3 Measuring and test equipment·AS-i reference network·AS-i data decoupling network· ammeter· oscilloscope·test circuit to figure 1·variable power supply1.4 Test procedure1. Set up test circuit to figure 12. Operate the master to be tested in normal operation3. Check the master functions at the following DC voltages on the AS-i-line: 31.6V,26.5V, 23.5V, 21.5V and again at 23.5V4. Check the maximum current consumption1.5 EvaluationThe maximum current consumption as stated by the manufacturer shall not be greater than the value stated in the data sheet or than the requirements of the specification.The function test at the operating voltage limits shall correspond to the data stated in the data sheets and the applicable specifications, i.e. at DC voltages on the AS-i line of 31.6V, 26.5Vmaster activity is detected by means of an oscilloscope directly on the AS-i line.Test recordingsDate:Tested by:Test laboratory:Test report no.:ofPage:Current consumptionTest piece code: ___________________Network configurationMaster: __________________________Power supply: __________________________ Data decoupling: ___________________ Slaves: __________________________Measured values:Voltage U /(V) 31.6 26.5 23.5 21.5 23.5Current I / (mA)Communication yes/no yes/no yes/no yes/no yes/nomax. current consumption: ______mA < current stated in data sheet:yes/noResult:Test passed: Yes / No Signature: _________________Test Requirements Master 1.2 Rev. 1.1 2. Test instruction: Noise emission AS-i masterReference: Specification AS-i master (chapter 7 of the Complete Specification),2.1 GeneralThis test instruction allows the measurement of the noise emission of an AS-i master in a power-fail state on the AS-i network.2.2 Test circuitFigure 1 shows the required test circuit.Figure 1: Test circuit noise emission AS-i masterThe change in current consumption in a master should only cause a noise voltage £ 50mVss on the AS-i line in the frequency range between 10kHz and 500kHz. The voltage on the AS-i line is measured by means of an oscilloscope via a bandpass (see figure 2, see spice simulation in the appendix to the test requirements for impedance and symmetry measurement). The oscilloscope is to be operated in the mode Envelope, Peak Detection on at a cut-off frequency > 10 MHz. The FET probe is to be terminated with an impedance of 50 Ohm. The test circuit is to be screened from noise so that the measured maximum noise voltage without the master is smaller than 15 mV. For this purpose, the cable length between master and AS-i equivalent line (see figure 3) is to be limited to max. 20 cm. The master is to be operated in the power-fail state (direct voltage on the AS-i line of 21 V).50 Ohm or AS-i 10 … 1MOhm 10 … 30 pFFigure 2: bandpass 10kHz ... 500kHzR = 0,125O hmL = 1,25 µHC=700 p FFigure 3: equivalent circuit of the 10m AS-i equivalent line2.3. Measuring and test equipment·AS-i power supply·oscilloscope with FET probe (50 Ohm output impedance)· bandpass·test circuit to figure 12.4 Test procedure1. Apply a voltage of 21 V to the AS-i line2. Measure the noise voltage without the master by means of the oscilloscope over 60seconds3. Connect the master4. Check the power-fail state of the master5. Measure the noise voltage with the master on the AS-i line by means of an oscilloscopeover 60 secondsThe measurements shall have an accuracy of 5%.2.5 EvaluationThe noise voltage on the AS-i line must not be increased by more than 50 mVss by the master in the power-fail state.Test Requirements Master 1.2 Rev. 1.1 Test recordingsDate:by:TestedTest laboratory:Test report no.:Page:of Noise emission AS-i masterTest piece code: ___________________Network configurationMaster: __________________________Power supply: _________________________Measured values:Noise voltage:without master: _______mVsswith master: _______mVss difference: ______ £ 50mVss : yes / noTest criteria: In the power-fail state the noise voltage of the master on the AS-i line must not exceed 50 mVss!Result:Test passed: Yes / No Signature: _________________3. Test instructions: Impedance and symmetry measurementReference: Specification AS-i master (chapter 7 of the Complete Specification),3.1. Impedance measurement3.1.1 GeneralThe impedance measurement of the master is to be performed in the "ready state" under laboratory conditions.An AC signal U~ with Ri £20 Ohm is to be superimposed on the AS-i DC voltage. This AC voltage and the resulting AC current I~ of the master are to be measured3.1.2 Test circuitFigure 1 shows the test circuit for the impedance measurement. The operation of the master in switch position "test" has been purposefully selected as asymmetrical, i.e. metal parts of the master must not be grounded. Switch S1 allows a switching of AC ground (switch position shown: AS-i- = GND).The AC input current I~ is measured by means of the current probe. The input impedance is calculated as follows:| Z | = | U~ | / | I~ |The distance to the AS-i master shall be 20 cm.The DC voltage is to be set to 21V to put the master in the offline state.3.1.3 Measuring and test equipment·power supply (universal)· signal generator· current probe·test circuit (IMP_SYM) to figure 1for point 3.2 (symmetry measurement)· FET probe· HF voltmeter· bandpassFigure 1: Test circuit impedance measurement (IMP_SYM)3.1.4 Test procedure·Switch S1: position "AS-i- = GND"·Determine the AC current I~ at U~ = 6 Vss·The measurement is to be carried out as described in chapter 7.2.1.1 of the Complete Specification.The accuracy of the measurements shall be within 3%.3.1.5 EvaluationThe evaluation is to be carried out as described in chapter 7.2.1.1 of the Complete Specification and must not exceed the limit values stated there.3.1.6 DC resistanceThe DC resistance between ASI+, ASI- and all metallic parts of the master with the exception of outer connections shall be ³ 250 kOhm.3.2. Symmetry measurement:3.2.1 General:Figure 2: Master connection for symmetry measurementThe partial impedances Z1 and Z2 respectively form a voltage divider at measurement point M. This measurement point may be the metallic housing or a metallic mounting plate. The measurement point shall be connected to the external supplies of the master or the host respectively.In the off-load state the currents through Z1 and Z2 are identical.For an asymmetry of 10% this means10.190.02121£=£Z Z U U r r .r U 1r: voltage between M and ASI+ for ASI+ = GNDU 2: voltage between M and ASI- for ASI- = GND3.2.3 Test circuit:Figure 3: Test circuit symmetry measurement of the AS-i master50 Ohm or AS-i10 … 1MOhm 10 … 30 pFFigure 4: bandpass 10 kHz ... 500 kHzThe test circuit corresponds to the one of the impedance measurement (compare figures 1 and 2). With the test circuit in figure 3 the voltage drops U1 of ASI+ to M and U2 of ASI- to M are determined by means of a FET probe (Ri=1MOhm//2pF) with AC coupling Ck ³1nF at an output impedance of 50 Ohm and an HF voltmeter (frequency range up to 300 kHz, Ri=10MOhm//30pF). The capacitance Ckomp=Cfet is to be taken into account in the circuit to compensate for the probe capacitance.By means of calibrating C 3, |U1| = |U2| = UE/2 can be achieved and the capacitances of C 1 and C 2 can be determined independent of Z.A possible measurement error of the HF voltmeter in higher frequency ranges is eliminated by means of the ratio |U1| / |U2|.The appendix shows the frequency response of the bandpass from a SPICE simulation with different combinations of the terminating resistor.3.2.4 Test procedure· Set a measurement voltage Ue of 2.0 Veff displayed on the evaluation meter at afrequency of 160 kHz· Determine |U1| and |U2| at a frequency of 300 kHz without C 3 · Check the condition10.190.02121£=£Z Z U U r r .· If this condition is met, determine at frequencies of 50kHz, 100kHz, 125kHz, 160kHz,200kHz, 300kHz and check if this condition is met.· for ASI+ = GND determine the frequency response of |U1| · for ASI- = GND determine the frequency response of |U2| · define the ratio |U1| / |U2| as stated in point 2.1 (General)·If the condition10.190.02121£=£Z Z U U r ris not met:· Add C3 between ASI+ and M or ASI- and M respectively, depending on the voltage testand calibrate until you reach |U1| = |U2| = UE/2 at a measurement frequency of 300kHz · Determine C3The accuracy of the measurements shall be within 3%.3.2.5 Evaluation / symmetry criteriaOne of the following conditions shall be met:1. 10.190.02121£=£Z Z U U r r or2.90.080.021££U U r r or 20.110.21££U U r 1r with C 3 £ 15 pF or3. 80.021£U U r r or 2120.1U U r r £ with C 3 £ 30 pFTest recordingsDate: Tested by: Test laboratory: Test report no.: Page: ofImpedance and symmetry measurementNetwork configurationMaster: _________________________ Test circuit: IMP_SYMImpedance measurement:R min L min C maxlimits5k W3mH 400pF measurementsTest criteria: R meas > R min ; L meas > L min ; C meas < C maxDC resistance (R ³ 250 kOhm): ASI+ - M: _______ ASI- - M: _______Symmetry measurement:f / (kHz) 50 100 125 160 200 300 |U1| / (V)|U2| / (V)|U1 / |U2||U1| / |U2| = ________ , C3=______ pFOne of the following conditions shall be met: 1.10.190.02121£=£Z Z U U r r2.90.080.021££U U r r or 20.110.21££U U r 1r withC 3 £ 15 pF or 3.80.021£U U r r or 2120.1U U r r £ with C 3 £ 30 pFSymmetry sufficient? yes/noResult:_________________ Yes/No Signature:passed:TestAppendix: Frequency responses bandpass with different terminating impedances4. Test instruction: Power-On behaviourReference: Specification ASI master (Chapter 7 of the Complete Specification),4.1 GeneralBy testing the Power-ON behaviour, the switch-on delay time t E of the ASI master and its current consumption shall be tested. The settings of the oscilloscope can be seen on the oscillograms.AS-i masters with integrated AS-i power supply must have an internal voltage supply which is accessible and can be interrupted for this test so that the external AS-i supply can be connected.4.2 Measuring and test equipment· power supply with AS-i data decoupling network· oscilloscope· constant current source (KONST_I)4.3 On-delay4.3.1 GeneralThe offline flag of the master is reset (normal operation). In the initial state the master is not connected with the AS-i line (switch S is open). The master shall communicate with the slaves for min. one second after switch S has been closed. The oscilloscope shall be triggered by the rising edge of the supply voltage on the AS-i line. The start of communication is shown on the oscilloscope via peak detection on and DC coupling.4.3.2 Test circuitFigure 1: Test circuit: On-delayFigure 2: Oscillogram on-delay (example)4.3.3 EvaluationThe time t E is to be determined from the oscillogram. It shall be longer than 1.00s. The accuracy of the measurements shall be within 3%.4.4 Current consumption4.4.1 GeneralIf the master is supplied (see circuit figure 4) with a current corresponding to the total current consumption as stated in the data sheet + 12.5mA (to be set with an accuracy of ± 2.5 mA), the master shall have reached an operating voltage of 26.5V within one second after closing switch S in figure 4. The final operating voltage value to be reached shall be 30V at the output of the circuit with a set constant current.4.4.2 Test circuitFigure 3: Block circuit diagram current consumption measurement of the AS-i master++--Trigger output30V in the stationary state Figure 4: Constant current source with trigger output (KONST_I)Figure 5: Oscillogram current consumption (example)4.4.3 EvaluationThe time t shall be determined from the oscillogram to figure 5. It shall be smaller than 1s. The accuracy of the measurement shall be within 3%.Test recordingsDate:by:TestedTest laboratory:Test report no.:ofPage:Power-On behaviourTest piece code: __________________Network configurationMaster: _________________________Power supply: ______________________ Data decoupling: _____________________Test circuit: KONST_IMeasured values:On-delay t E: ______ s > 1s: yes / noCurrent consumption t : __________ s < 1s: yes / noThe oscillograms are to be added to the appendix.Result:Test passed: Yes / No Signature: _________________5. Test instruction: Burst testReference: Specification AS-i master (Chapters 7 and 8 of the Complete Specification),5.1 GeneralThe test shall be performed with fast transient bursts in form of pulse groups. The interferences are injected on the AS-i line by means of a capacitive coupling clamp. The test shall be made with the following data:·level 3 for data lines·test voltage 1 kV·pulse rate 5 kHz·burst length 15 ms·burst period 300 ms.The following requirements are to be met to minimise the environmental influence on the test results:·ambient temperature: 15° C to 35° C·relative humidity: 45% to 75%·air pressure: 680 hPa to 1060 hPaFigure 1 shows the curve of the transient interferences.Figure 1: Overall curve of the transient interference5.2 Test circuit (principle)Figure 2 shows the test circuit (principle) for the burst test of the AS-i master. Figure 3 shows the circuit diagram of the filter to be used to protect the slaves from burst pulses.K a p . 5.2.2Figure 3: Test installation burst tester (BURST_T)The master operates an AS-i network (see figure 2, consisting of the first 90m of the reference network, see test instruction "Operation on the reference network" from the test requirements for AS-i-slaves and and a burst tester at measurement point 1 of the reference network, see figure 3) in the cyclic normal operation with active data exchange. The burst tester includes 2 AS-i slaves (addresses 1 and 2) and a data strobe evaluation for these two slaves, i.e. all data strobe pulses of slaves 1 and 2 are recorded, the timing is defined for the undisturbed case and the timing violation in the case of bursts is recorded. If the time defined in undisturbed operation is exceeded by more than 100 µs, this indicates an error. In the case of double pulses at slave 1 the time measurement refers to the first pulse.The reference measurements (no faults in the case of burst) require ferrite cores (define number and position) for decoupling (filter).Burst pulses of the burst generator are injected via a capacitive coupling clamp.Measurements are taken over a longer period of time (e.g. 2 min, but for a minimum of 100,000 cycles).5.3 Test installationFigure 4 shows the test installation for the burst test.10 cm above the grounded metal plateFigure 4: Test installation burst test5.4 Measuring and test equipment· burst generator·capacitive coupling clamp·20 m AS-i line (burst setup)· filter·part of the AS-i reference network (90m)·burst tester (BURST_T)·AS-i power supply5.5 Test procedure·The AS-i slaves shall be protected from the effects of burst pulses by means of filters. ·The master shall be grounded according to IEC 801 part 4. The master shall be mounted as described in the data sheet. Supplied mounting material shall be used. Measurements shall be carried out at a distance of 10cm from the metal plate for all designs.·10m AS-i line shall be mounted s-shaped at 10cm above the grounded metal plate; the remaining 10m shall be used to connect the AS-i slaves of the reference network protected by filters and the burst tester.· A test voltage of 1kV shall be set at the burst generator.·The tests shall be made with both burst polarities.·The test period shall be 2 min.5.6 EvaluationThe errors caused by the master to be tested shall be evaluated.To calculate the error rate caused by the system without the master, a test with insensitive reference master (symmetrical design) is performed.5.6.1 Calculation of the maximum error rateBased on the assumption that each AS-i message is disturbed during the burst period of 15 ms each we get a maximum percentage of disturbed messages of (see figure 1):15 ms / 300 ms = 5% = Nmax .5.6.2 Measurement of the actual error rate using a reference masterThe reference master is set up with the lowest possible stray capacitance to mass. It is assumed that no error in the network will occur during operation without burst.5.7 TestThe master shall be installed ready for operation (see data sheet) and – if applicable – connected to mass (ground).Under the influence of the burst pulses the number of exceeded timings of the data strobe pulses between slaves 1 and 2 is measured5.8 EvaluationThe limit value according to specification defines: "Max. every 30th message shall be distorted".This means that:Nmess £ Nmax ·1 30Nmess £16 %has to be met.Test criteria: The number of exceeded timings must not exceed 1 %. 65.9 Enhanced test5.9.1 Test voltage 2kVThe test master shall be installed ready for operation and – if applicable – connected to mass (ground). Refer to the installation notes in the data sheet or the instructions in the box.A test voltage of 2kV shall be set at the burst generator. The test period shall be 2 min.For this test one of the AS-i line shall be grounded at the power supply (protective earth). The functional earth of the power supply shall be removed.5.9.2 EvaluationAt a voltage of 2kV it has to be ensured that no errors occur, in particular:· no RESET,·no destruction of the master during the test.Test recordingsDate: Tested by: Test laboratory: Test report no.: Page: ofBurst test to IEC 801, part 4Test piece code: __________________________ Test piece type: ____________________________ Switching state: ___________________________ Burst generator type: _______________________ Coupling clamp type: ________________________ Mass reference surface: ______________________ Ambient temperature: _______________ Relative humidity: ________________ Air pressure: ________________Network configurationSlaves: __________________Power supply: ___________________ Test level: 3 (1kV)Burst duration: 15ms, burst period 300ms, spike frequency 5kHz Test duration (> 1min): ______________ Test condition: Nmess £ 1/6 % + Nref Test circuit: BURST_TTest results:Test at 1kV:Polarity Nref 1/6 % + Nref Nmess at a distance of 10 cmTest passed:positive yes / no negativeyes / noTest at 2kV:positive polarity negative polarity yes no yes no RESET destructionResult:Test passed: Yes / No Signature: _________________6. Test instruction: Analogue partReference Specification AS-i master (Chapter 7 of the Complete Specification),profiles,Master6.1 GeneralThis test instruction will assess the analogue part of the master.A manufacturer declaration is to guarantee a bit time of the master transmitter of 6µs ±0.1% .6.2 Measuring and test equipment· AS-i master·AS-i power supply· 2 pcs. 4O modules as slaves 1 and 2·AS-i monitor (e.g. SINEC S1 – PC card (CP 2413) with monitor program SCOPE S1, version 1.0), with a capacitive load on the AS-i line of C monitor≤ 0.4 nF·equivalent network (29 slaves, 300 Ohm||(3 nF-C monitor))·data decoupling with HF ground6.3 Test circuit1m (+/-0,1m)99m (+/- 1m)Laboratorypower supply39 OhmFigure 2: Data decoupling and HF groundThe AS-i line (99m) shall be mounted s-shaped (length: 2.50m, distance 0.1m). The data decoupling network shall be made up of a core EF 25 consisting of 2 parts, material N27(Siemens, order nos.: B 66 317-G-X127 and B 66 317-G-X127, see data sheet) with 1mm total air gap, equipped with a bifilar winding of 16.5 windings, wire diameter 0.8mm, wound parallel and the parallel resistor of 39R 1%. The equivalent circuit Zn (copy of an impedance of 29 slaves) is to consist of the parallel wiring of 10 pcs. 3.3kOhm 1% metal film resistors and a capacitance of 3nF 2% (The equivalent circuit Zn includes the impedance of the AS-i monitor, i.e. Zn = 330W || (3nF-C monitor) || monitor).6.4 Test procedureTest 1:1. Set up the test installation as shown in figure 1,2. Set slave 1 on address 21 and slave 2 on address 13. Slave 1 shall be polled by the master with data message ("0xA"), slave 2 with datamessage ("0x0")4. After the error rate has been measured via the monitor, the positions of slaves 1 and2 shall be changed and test shall be repeatedTest 2:1. The test installation shall be changed by removing the 99m AS-i line between slaves 1and 2 and the equivalent network Zn, i.e. slave 2, the AS-i monitor and slave 1 shall be connected at a distance of 1m from the master2. Set slave 1 on address 21 and slave 2 on address 13. Slave 1 shall be polled by the master with data message ("0xA"), slave 2 with datamessage ("0x0")4. The error rate shall be measured via monitor6.5 EvaluationThe monitor shall show an error rate of £ 0.5% for all tests.The error rate shall be defined as the number of master request /slave response combinations for slave 1 not correctly detected by the master, referred to a total number of master requests to slave 1.Test recordingsDate:by:TestedTest laboratory:Test report no.:ofPage:Analogue partTest piece code: ___________________AS-i master: ______________________Power supply: _________________________Test results:Test 1:correct? yes/no Error rate measurement 1: _____% £0.5%correct? yes/no Error rate measurement 2: _____% £0.5%Test 2:correct? yes/no Error rate measurement: _____% £0.5%Result:Test passed: Yes / No Signature: _________________7. Test instruction: Voltage cutoffReference: Specification AS-i master (chapter 7 of the Complete Specification),profiles,Master7.1 GeneralThe reaction of the master to voltage cutoff on the AS-i line of 1ms and a reduced voltage on the AS-i line from approx. 23.5V to 14.5V shall be tested.7.2 Measuring and test equipment· AS-i master·AS-i power supply·AS-i bus monitor· generator· oscilloscope7.3 Test circuitFigure 1 shows the basic principle of the test installation to check the reaction of the master to voltage cutoffs as well as the reduction of the DC voltage on the AS-i line. The connectedslave puts the master in the normal operation mode.7.4 Test procedure:1. Interrupt the voltage on the AS-i line for 0.6 ms with a repetition frequency of < 1Hzand check the AS-i messages by means of the bus monitor.2. Interrupt the voltage on the AS-i line for 2.1ms with a repetition frequency of <1Hz andcheck the AS-i messages by means of the bus monitor.3. Check the transmitting amplitude of the master at an AS-i-DC voltage of 23.5V4. Reduce the DC voltage on the AS-i line from 23.5V to 14.5V.Check AS-i message sequence "RESET_Slave" to all slaves by the master by means of a bus monitor and check their transmitting amplitude and subsequent offline operation of the master.7.5 Evaluation。

A Peer-to-Peer Spatial Cloaking Algorithm for AnonymousLocation-based Services∗Chi-Yin Chow Department of Computer Science and Engineering University of Minnesota Minneapolis,MN cchow@ Mohamed F.MokbelDepartment of ComputerScience and EngineeringUniversity of MinnesotaMinneapolis,MNmokbel@Xuan LiuIBM Thomas J.WatsonResearch CenterHawthorne,NYxuanliu@ABSTRACTThis paper tackles a major privacy threat in current location-based services where users have to report their ex-act locations to the database server in order to obtain their desired services.For example,a mobile user asking about her nearest restaurant has to report her exact location.With untrusted service providers,reporting private location in-formation may lead to several privacy threats.In this pa-per,we present a peer-to-peer(P2P)spatial cloaking algo-rithm in which mobile and stationary users can entertain location-based services without revealing their exact loca-tion information.The main idea is that before requesting any location-based service,the mobile user will form a group from her peers via single-hop communication and/or multi-hop routing.Then,the spatial cloaked area is computed as the region that covers the entire group of peers.Two modes of operations are supported within the proposed P2P spa-tial cloaking algorithm,namely,the on-demand mode and the proactive mode.Experimental results show that the P2P spatial cloaking algorithm operated in the on-demand mode has lower communication cost and better quality of services than the proactive mode,but the on-demand incurs longer response time.Categories and Subject Descriptors:H.2.8[Database Applications]:Spatial databases and GISGeneral Terms:Algorithms and Experimentation. Keywords:Mobile computing,location-based services,lo-cation privacy and spatial cloaking.1.INTRODUCTIONThe emergence of state-of-the-art location-detection de-vices,e.g.,cellular phones,global positioning system(GPS) devices,and radio-frequency identification(RFID)chips re-sults in a location-dependent information access paradigm,∗This work is supported in part by the Grants-in-Aid of Re-search,Artistry,and Scholarship,University of Minnesota. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on thefirst page.To copy otherwise,to republish,to post on servers or to redistribute to lists,requires prior specific permission and/or a fee.ACM-GIS’06,November10-11,2006,Arlington,Virginia,USA. Copyright2006ACM1-59593-529-0/06/0011...$5.00.known as location-based services(LBS)[30].In LBS,mobile users have the ability to issue location-based queries to the location-based database server.Examples of such queries include“where is my nearest gas station”,“what are the restaurants within one mile of my location”,and“what is the traffic condition within ten minutes of my route”.To get the precise answer of these queries,the user has to pro-vide her exact location information to the database server. With untrustworthy servers,adversaries may access sensi-tive information about specific individuals based on their location information and issued queries.For example,an adversary may check a user’s habit and interest by knowing the places she visits and the time of each visit,or someone can track the locations of his ex-friends.In fact,in many cases,GPS devices have been used in stalking personal lo-cations[12,39].To tackle this major privacy concern,three centralized privacy-preserving frameworks are proposed for LBS[13,14,31],in which a trusted third party is used as a middleware to blur user locations into spatial regions to achieve k-anonymity,i.e.,a user is indistinguishable among other k−1users.The centralized privacy-preserving frame-work possesses the following shortcomings:1)The central-ized trusted third party could be the system bottleneck or single point of failure.2)Since the centralized third party has the complete knowledge of the location information and queries of all users,it may pose a serious privacy threat when the third party is attacked by adversaries.In this paper,we propose a peer-to-peer(P2P)spatial cloaking algorithm.Mobile users adopting the P2P spatial cloaking algorithm can protect their privacy without seeking help from any centralized third party.Other than the short-comings of the centralized approach,our work is also moti-vated by the following facts:1)The computation power and storage capacity of most mobile devices have been improv-ing at a fast pace.2)P2P communication technologies,such as IEEE802.11and Bluetooth,have been widely deployed.3)Many new applications based on P2P information shar-ing have rapidly taken shape,e.g.,cooperative information access[9,32]and P2P spatio-temporal query processing[20, 24].Figure1gives an illustrative example of P2P spatial cloak-ing.The mobile user A wants tofind her nearest gas station while beingfive anonymous,i.e.,the user is indistinguish-able amongfive users.Thus,the mobile user A has to look around andfind other four peers to collaborate as a group. In this example,the four peers are B,C,D,and E.Then, the mobile user A cloaks her exact location into a spatialA B CDEBase Stationregion that covers the entire group of mobile users A ,B ,C ,D ,and E .The mobile user A randomly selects one of the mobile users within the group as an agent .In the ex-ample given in Figure 1,the mobile user D is selected as an agent.Then,the mobile user A sends her query (i.e.,what is the nearest gas station)along with her cloaked spa-tial region to the agent.The agent forwards the query to the location-based database server through a base station.Since the location-based database server processes the query based on the cloaked spatial region,it can only give a list of candidate answers that includes the actual answers and some false positives.After the agent receives the candidate answers,it forwards the candidate answers to the mobile user A .Finally,the mobile user A gets the actual answer by filtering out all the false positives.The proposed P2P spatial cloaking algorithm can operate in two modes:on-demand and proactive .In the on-demand mode,mobile clients execute the cloaking algorithm when they need to access information from the location-based database server.On the other side,in the proactive mode,mobile clients periodically look around to find the desired number of peers.Thus,they can cloak their exact locations into spatial regions whenever they want to retrieve informa-tion from the location-based database server.In general,the contributions of this paper can be summarized as follows:1.We introduce a distributed system architecture for pro-viding anonymous location-based services (LBS)for mobile users.2.We propose the first P2P spatial cloaking algorithm for mobile users to entertain high quality location-based services without compromising their privacy.3.We provide experimental evidence that our proposed algorithm is efficient in terms of the response time,is scalable to large numbers of mobile clients,and is effective as it provides high-quality services for mobile clients without the need of exact location information.The rest of this paper is organized as follows.Section 2highlights the related work.The system model of the P2P spatial cloaking algorithm is presented in Section 3.The P2P spatial cloaking algorithm is described in Section 4.Section 5discusses the integration of the P2P spatial cloak-ing algorithm with privacy-aware location-based database servers.Section 6depicts the experimental evaluation of the P2P spatial cloaking algorithm.Finally,Section 7con-cludes this paper.2.RELATED WORKThe k -anonymity model [37,38]has been widely used in maintaining privacy in databases [5,26,27,28].The main idea is to have each tuple in the table as k -anonymous,i.e.,indistinguishable among other k −1tuples.Although we aim for the similar k -anonymity model for the P2P spatial cloaking algorithm,none of these techniques can be applied to protect user privacy for LBS,mainly for the following four reasons:1)These techniques preserve the privacy of the stored data.In our model,we aim not to store the data at all.Instead,we store perturbed versions of the data.Thus,data privacy is managed before storing the data.2)These approaches protect the data not the queries.In anonymous LBS,we aim to protect the user who issues the query to the location-based database server.For example,a mobile user who wants to ask about her nearest gas station needs to pro-tect her location while the location information of the gas station is not protected.3)These approaches guarantee the k -anonymity for a snapshot of the database.In LBS,the user location is continuously changing.Such dynamic be-havior calls for continuous maintenance of the k -anonymity model.(4)These approaches assume a unified k -anonymity requirement for all the stored records.In our P2P spatial cloaking algorithm,k -anonymity is a user-specified privacy requirement which may have a different value for each user.Motivated by the privacy threats of location-detection de-vices [1,4,6,40],several research efforts are dedicated to protect the locations of mobile users (e.g.,false dummies [23],landmark objects [18],and location perturbation [10,13,14]).The most closed approaches to ours are two centralized spatial cloaking algorithms,namely,the spatio-temporal cloaking [14]and the CliqueCloak algorithm [13],and one decentralized privacy-preserving algorithm [23].The spatio-temporal cloaking algorithm [14]assumes that all users have the same k -anonymity requirements.Furthermore,it lacks the scalability because it deals with each single request of each user individually.The CliqueCloak algorithm [13]as-sumes a different k -anonymity requirement for each user.However,since it has large computation overhead,it is lim-ited to a small k -anonymity requirement,i.e.,k is from 5to 10.A decentralized privacy-preserving algorithm is proposed for LBS [23].The main idea is that the mobile client sends a set of false locations,called dummies ,along with its true location to the location-based database server.However,the disadvantages of using dummies are threefold.First,the user has to generate realistic dummies to pre-vent the adversary from guessing its true location.Second,the location-based database server wastes a lot of resources to process the dummies.Finally,the adversary may esti-mate the user location by using cellular positioning tech-niques [34],e.g.,the time-of-arrival (TOA),the time differ-ence of arrival (TDOA)and the direction of arrival (DOA).Although several existing distributed group formation al-gorithms can be used to find peers in a mobile environment,they are not designed for privacy preserving in LBS.Some algorithms are limited to only finding the neighboring peers,e.g.,lowest-ID [11],largest-connectivity (degree)[33]and mobility-based clustering algorithms [2,25].When a mo-bile user with a strict privacy requirement,i.e.,the value of k −1is larger than the number of neighboring peers,it has to enlist other peers for help via multi-hop routing.Other algorithms do not have this limitation,but they are designed for grouping stable mobile clients together to facil-Location-based Database ServerDatabase ServerDatabase ServerFigure 2:The system architectureitate efficient data replica allocation,e.g.,dynamic connec-tivity based group algorithm [16]and mobility-based clus-tering algorithm,called DRAM [19].Our work is different from these approaches in that we propose a P2P spatial cloaking algorithm that is dedicated for mobile users to dis-cover other k −1peers via single-hop communication and/or via multi-hop routing,in order to preserve user privacy in LBS.3.SYSTEM MODELFigure 2depicts the system architecture for the pro-posed P2P spatial cloaking algorithm which contains two main components:mobile clients and location-based data-base server .Each mobile client has its own privacy profile that specifies its desired level of privacy.A privacy profile includes two parameters,k and A min ,k indicates that the user wants to be k -anonymous,i.e.,indistinguishable among k users,while A min specifies the minimum resolution of the cloaked spatial region.The larger the value of k and A min ,the more strict privacy requirements a user needs.Mobile users have the ability to change their privacy profile at any time.Our employed privacy profile matches the privacy re-quirements of mobiles users as depicted by several social science studies (e.g.,see [4,15,17,22,29]).In this architecture,each mobile user is equipped with two wireless network interface cards;one of them is dedicated to communicate with the location-based database server through the base station,while the other one is devoted to the communication with other peers.A similar multi-interface technique has been used to implement IP multi-homing for stream control transmission protocol (SCTP),in which a machine is installed with multiple network in-terface cards,and each assigned a different IP address [36].Similarly,in mobile P2P cooperation environment,mobile users have a network connection to access information from the server,e.g.,through a wireless modem or a base station,and the mobile users also have the ability to communicate with other peers via a wireless LAN,e.g.,IEEE 802.11or Bluetooth [9,24,32].Furthermore,each mobile client is equipped with a positioning device, e.g.,GPS or sensor-based local positioning systems,to determine its current lo-cation information.4.P2P SPATIAL CLOAKINGIn this section,we present the data structure and the P2P spatial cloaking algorithm.Then,we describe two operation modes of the algorithm:on-demand and proactive .4.1Data StructureThe entire system area is divided into grid.The mobile client communicates with each other to discover other k −1peers,in order to achieve the k -anonymity requirement.TheAlgorithm 1P2P Spatial Cloaking:Request Originator m 1:Function P2PCloaking-Originator (h ,k )2://Phase 1:Peer searching phase 3:The hop distance h is set to h4:The set of discovered peers T is set to {∅},and the number ofdiscovered peers k =|T |=05:while k <k −1do6:Broadcast a FORM GROUP request with the parameter h (Al-gorithm 2gives the response of each peer p that receives this request)7:T is the set of peers that respond back to m by executingAlgorithm 28:k =|T |;9:if k <k −1then 10:if T =T then 11:Suspend the request 12:end if 13:h ←h +1;14:T ←T ;15:end if 16:end while17://Phase 2:Location adjustment phase 18:for all T i ∈T do19:|mT i .p |←the greatest possible distance between m and T i .pby considering the timestamp of T i .p ’s reply and maximum speed20:end for21://Phase 3:Spatial cloaking phase22:Form a group with k −1peers having the smallest |mp |23:h ←the largest hop distance h p of the selected k −1peers 24:Determine a grid area A that covers the entire group 25:if A <A min then26:Extend the area of A till it covers A min 27:end if28:Randomly select a mobile client of the group as an agent 29:Forward the query and A to the agentmobile client can thus blur its exact location into a cloaked spatial region that is the minimum grid area covering the k −1peers and itself,and satisfies A min as well.The grid area is represented by the ID of the left-bottom and right-top cells,i.e.,(l,b )and (r,t ).In addition,each mobile client maintains a parameter h that is the required hop distance of the last peer searching.The initial value of h is equal to one.4.2AlgorithmFigure 3gives a running example for the P2P spatial cloaking algorithm.There are 15mobile clients,m 1to m 15,represented as solid circles.m 8is the request originator,other black circles represent the mobile clients received the request from m 8.The dotted circles represent the commu-nication range of the mobile client,and the arrow represents the movement direction.Algorithms 1and 2give the pseudo code for the request originator (denoted as m )and the re-quest receivers (denoted as p ),respectively.In general,the algorithm consists of the following three phases:Phase 1:Peer searching phase .The request origina-tor m wants to retrieve information from the location-based database server.m first sets h to h ,a set of discovered peers T to {∅}and the number of discovered peers k to zero,i.e.,|T |.(Lines 3to 4in Algorithm 1).Then,m broadcasts a FORM GROUP request along with a message sequence ID and the hop distance h to its neighboring peers (Line 6in Algorithm 1).m listens to the network and waits for the reply from its neighboring peers.Algorithm 2describes how a peer p responds to the FORM GROUP request along with a hop distance h and aFigure3:P2P spatial cloaking algorithm.Algorithm2P2P Spatial Cloaking:Request Receiver p1:Function P2PCloaking-Receiver(h)2://Let r be the request forwarder3:if the request is duplicate then4:Reply r with an ACK message5:return;6:end if7:h p←1;8:if h=1then9:Send the tuple T=<p,(x p,y p),v maxp ,t p,h p>to r10:else11:h←h−1;12:Broadcast a FORM GROUP request with the parameter h 13:T p is the set of peers that respond back to p14:for all T i∈T p do15:T i.h p←T i.h p+1;16:end for17:T p←T p∪{<p,(x p,y p),v maxp ,t p,h p>};18:Send T p back to r19:end ifmessage sequence ID from another peer(denoted as r)that is either the request originator or the forwarder of the re-quest.First,p checks if it is a duplicate request based on the message sequence ID.If it is a duplicate request,it sim-ply replies r with an ACK message without processing the request.Otherwise,p processes the request based on the value of h:Case1:h= 1.p turns in a tuple that contains its ID,current location,maximum movement speed,a timestamp and a hop distance(it is set to one),i.e.,< p,(x p,y p),v max p,t p,h p>,to r(Line9in Algorithm2). Case2:h> 1.p decrements h and broadcasts the FORM GROUP request with the updated h and the origi-nal message sequence ID to its neighboring peers.p keeps listening to the network,until it collects the replies from all its neighboring peers.After that,p increments the h p of each collected tuple,and then it appends its own tuple to the collected tuples T p.Finally,it sends T p back to r (Lines11to18in Algorithm2).After m collects the tuples T from its neighboring peers, if m cannotfind other k−1peers with a hop distance of h,it increments h and re-broadcasts the FORM GROUP request along with a new message sequence ID and h.m repeatedly increments h till itfinds other k−1peers(Lines6to14in Algorithm1).However,if mfinds the same set of peers in two consecutive broadcasts,i.e.,with hop distances h and h+1,there are not enough connected peers for m.Thus, m has to relax its privacy profile,i.e.,use a smaller value of k,or to be suspended for a period of time(Line11in Algorithm1).Figures3(a)and3(b)depict single-hop and multi-hop peer searching in our running example,respectively.In Fig-ure3(a),the request originator,m8,(e.g.,k=5)canfind k−1peers via single-hop communication,so m8sets h=1. Since h=1,its neighboring peers,m5,m6,m7,m9,m10, and m11,will not further broadcast the FORM GROUP re-quest.On the other hand,in Figure3(b),m8does not connect to k−1peers directly,so it has to set h>1.Thus, its neighboring peers,m7,m10,and m11,will broadcast the FORM GROUP request along with a decremented hop dis-tance,i.e.,h=h−1,and the original message sequence ID to their neighboring peers.Phase2:Location adjustment phase.Since the peer keeps moving,we have to capture the movement between the time when the peer sends its tuple and the current time. For each received tuple from a peer p,the request originator, m,determines the greatest possible distance between them by an equation,|mp |=|mp|+(t c−t p)×v max p,where |mp|is the Euclidean distance between m and p at time t p,i.e.,|mp|=(x m−x p)2+(y m−y p)2,t c is the currenttime,t p is the timestamp of the tuple and v maxpis the maximum speed of p(Lines18to20in Algorithm1).In this paper,a conservative approach is used to determine the distance,because we assume that the peer will move with the maximum speed in any direction.If p gives its movement direction,m has the ability to determine a more precise distance between them.Figure3(c)illustrates that,for each discovered peer,the circle represents the largest region where the peer can lo-cate at time t c.The greatest possible distance between the request originator m8and its discovered peer,m5,m6,m7, m9,m10,or m11is represented by a dotted line.For exam-ple,the distance of the line m8m 11is the greatest possible distance between m8and m11at time t c,i.e.,|m8m 11|. Phase3:Spatial cloaking phase.In this phase,the request originator,m,forms a virtual group with the k−1 nearest peers,based on the greatest possible distance be-tween them(Line22in Algorithm1).To adapt to the dynamic network topology and k-anonymity requirement, m sets h to the largest value of h p of the selected k−1 peers(Line15in Algorithm1).Then,m determines the minimum grid area A covering the entire group(Line24in Algorithm1).If the area of A is less than A min,m extends A,until it satisfies A min(Lines25to27in Algorithm1). Figure3(c)gives the k−1nearest peers,m6,m7,m10,and m11to the request originator,m8.For example,the privacy profile of m8is(k=5,A min=20cells),and the required cloaked spatial region of m8is represented by a bold rectan-gle,as depicted in Figure3(d).To issue the query to the location-based database server anonymously,m randomly selects a mobile client in the group as an agent(Line28in Algorithm1).Then,m sendsthe query along with the cloaked spatial region,i.e.,A,to the agent(Line29in Algorithm1).The agent forwards thequery to the location-based database server.After the serverprocesses the query with respect to the cloaked spatial re-gion,it sends a list of candidate answers back to the agent.The agent forwards the candidate answer to m,and then mfilters out the false positives from the candidate answers. 4.3Modes of OperationsThe P2P spatial cloaking algorithm can operate in twomodes,on-demand and proactive.The on-demand mode:The mobile client only executesthe algorithm when it needs to retrieve information from the location-based database server.The algorithm operatedin the on-demand mode generally incurs less communica-tion overhead than the proactive mode,because the mobileclient only executes the algorithm when necessary.However,it suffers from a longer response time than the algorithm op-erated in the proactive mode.The proactive mode:The mobile client adopting theproactive mode periodically executes the algorithm in back-ground.The mobile client can cloak its location into a spa-tial region immediately,once it wants to communicate withthe location-based database server.The proactive mode pro-vides a better response time than the on-demand mode,but it generally incurs higher communication overhead and giveslower quality of service than the on-demand mode.5.ANONYMOUS LOCATION-BASEDSERVICESHaving the spatial cloaked region as an output form Algo-rithm1,the mobile user m sends her request to the location-based server through an agent p that is randomly selected.Existing location-based database servers can support onlyexact point locations rather than cloaked regions.In or-der to be able to work with a spatial region,location-basedservers need to be equipped with a privacy-aware queryprocessor(e.g.,see[29,31]).The main idea of the privacy-aware query processor is to return a list of candidate answerrather than the exact query answer.Then,the mobile user m willfilter the candidate list to eliminate its false positives andfind its exact answer.The tighter the spatial cloaked re-gion,the lower is the size of the candidate answer,and hencethe better is the performance of the privacy-aware query processor.However,tight cloaked regions may represent re-laxed privacy constrained.Thus,a trade-offbetween the user privacy and the quality of service can be achieved[31]. Figure4(a)depicts such scenario by showing the data stored at the server side.There are32target objects,i.e., gas stations,T1to T32represented as black circles,the shaded area represents the spatial cloaked area of the mo-bile client who issued the query.For clarification,the actual mobile client location is plotted in Figure4(a)as a black square inside the cloaked area.However,such information is neither stored at the server side nor revealed to the server. The privacy-aware query processor determines a range that includes all target objects that are possibly contributing to the answer given that the actual location of the mobile client could be anywhere within the shaded area.The range is rep-resented as a bold rectangle,as depicted in Figure4(b).The server sends a list of candidate answers,i.e.,T8,T12,T13, T16,T17,T21,and T22,back to the agent.The agent next for-(a)Server Side(b)Client SideFigure4:Anonymous location-based services wards the candidate answers to the requesting mobile client either through single-hop communication or through multi-hop routing.Finally,the mobile client can get the actualanswer,i.e.,T13,byfiltering out the false positives from thecandidate answers.The algorithmic details of the privacy-aware query proces-sor is beyond the scope of this paper.Interested readers are referred to[31]for more details.6.EXPERIMENTAL RESULTSIn this section,we evaluate and compare the scalabilityand efficiency of the P2P spatial cloaking algorithm in boththe on-demand and proactive modes with respect to the av-erage response time per query,the average number of mes-sages per query,and the size of the returned candidate an-swers from the location-based database server.The queryresponse time in the on-demand mode is defined as the timeelapsed between a mobile client starting to search k−1peersand receiving the candidate answers from the agent.On theother hand,the query response time in the proactive mode is defined as the time elapsed between a mobile client startingto forward its query along with the cloaked spatial regionto the agent and receiving the candidate answers from theagent.The simulation model is implemented in C++usingCSIM[35].In all the experiments in this section,we consider an in-dividual random walk model that is based on“random way-point”model[7,8].At the beginning,the mobile clientsare randomly distributed in a spatial space of1,000×1,000square meters,in which a uniform grid structure of100×100cells is constructed.Each mobile client randomly chooses itsown destination in the space with a randomly determined speed s from a uniform distribution U(v min,v max).When the mobile client reaches the destination,it comes to a stand-still for one second to determine its next destination.Afterthat,the mobile client moves towards its new destinationwith another speed.All the mobile clients repeat this move-ment behavior during the simulation.The time interval be-tween two consecutive queries generated by a mobile client follows an exponential distribution with a mean of ten sec-onds.All the experiments consider one half-duplex wirelesschannel for a mobile client to communicate with its peers with a total bandwidth of2Mbps and a transmission range of250meters.When a mobile client wants to communicate with other peers or the location-based database server,it has to wait if the requested channel is busy.In the simulated mobile environment,there is a centralized location-based database server,and one wireless communication channel between the location-based database server and the mobile。