�??xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>&#20122;&#27954;&#31934;&#36873;&#97;&#118;&#44;&#22269;&#20135;&#31934;&#21697;&#25512;&#33616;&#31934;&#21697;&#44;&#19968;&#21306;&#20108;&#21306;&#22312;&#32447;&#30005;&#24433;</title><link>http://www.aygfsteel.com/lescony/category/11223.html</link><description /><language>zh-cn</language><lastBuildDate>Tue, 27 Feb 2007 12:05:41 GMT</lastBuildDate><pubDate>Tue, 27 Feb 2007 12:05:41 GMT</pubDate><ttl>60</ttl><item><title>[NEWS] EPCglobal宣布数据交换通用性测试成�?</title><link>http://www.aygfsteel.com/lescony/articles/74795.html</link><dc:creator>���单爱</dc:creator><author>���单爱</author><pubDate>Thu, 12 Oct 2006 07:41:00 GMT</pubDate><guid>http://www.aygfsteel.com/lescony/articles/74795.html</guid><wfw:comment>http://www.aygfsteel.com/lescony/comments/74795.html</wfw:comment><comments>http://www.aygfsteel.com/lescony/articles/74795.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.aygfsteel.com/lescony/comments/commentRss/74795.html</wfw:commentRss><trackback:ping>http://www.aygfsteel.com/lescony/services/trackbacks/74795.html</trackback:ping><description><![CDATA[  EPCglobal布鲁塞尔10�?0日最新报道－EPCglobal今天宣布成功实施了��品电子代码信息服务（EPCIS�Q�通用性测试。一份新的技术规范将使��N易伙伴能够在主要供应链流�E�中利用EPC采集和共享事件信息�?br />  <br />   预计�q�䆾新规范将在今�q�末提交至EPCglobal���理委员会核准，�q�将标志着EPC技术在全球范围内的推广又迈�q�了一步。EPC技术通过无线���频识别技术（RFID�Q�在全球供应链中提供了更高的产品�U�d��可见度�?br /><br />    EPCIS v1.0规范通用性测试是由马萨诸塞州理工学院的Auto-ID中心实施的�?2个组�l�参与了该测试，包括�Q�剑桥Auto-ID实验室、Avicon、BEA�pȝ��、Bent�pȝ��、IBM、Globe Ranger、IIJ、NEC、Oracle、Polaris Systems、Samsung、T3Ci。EPCIS规范���通过提供EPC数据交换接口和数据规范本�w�实现天衣无�~�且标准化的通用性，使��N易伙伴能够采集�ƈ�׃�nEPC信息�?<br />    <br />    “当数据可以在供应链中交互共享时�Q�EPC技术的真正价值就体现出来了。EPCIS���在EPCglobal�|�络与��N易伙伴的�q�接中充当信息桥梁的角色�Q�推动EPC数据的交换，使各公司在商业合作流�E�中能够应用�q�些数据。”IBM Websphere的��品经理兼EPCglobal EPCIS工作�l�的联合��d��Craig Asher说道�?br /> <br />    “通用性测试在EPCIS的发展中标志了一个重要的里程���－���过150家公司和�l�织参与了EPCIS工作�l�数�q�后的最高成果。这��Ҏ��试展�C�Z��公开标准的好处和�l�端用户��Z��满��其商业需求在应用EPC技术时可以选择的范围和灉|��性。”Ken Traub说道�?他是Edge Servers、BEA�pȝ��的RFID首席技术官�Q�也是EPCIS规范的主�~��?br /> <br />    “EPCIS v1.0的成功测试标志了在各个行业推�q�EPC技术全球部�|�的重要事�g。”EPCglobal的主席Chris Adcock说道�Q�：“这个测试项目汇集了相当多的工作�Q�我们感谢所有参与该规范制定和测试的公司。�?br /> <br />    EPCIS v1.0规范���通过EPCglobal标准制定���程剩下的步骤，一旦经由EPCglobal���理委员会批准，���成为正式的EPCglobal标准�?br /> <img src ="http://www.aygfsteel.com/lescony/aggbug/74795.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/lescony/" target="_blank">���单爱</a> 2006-10-12 15:41 <a href="http://www.aygfsteel.com/lescony/articles/74795.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>RFID技术和应用的十大误�?/title><link>http://www.aygfsteel.com/lescony/articles/46794.html</link><dc:creator>���单爱</dc:creator><author>���单爱</author><pubDate>Thu, 18 May 2006 05:47:00 GMT</pubDate><guid>http://www.aygfsteel.com/lescony/articles/46794.html</guid><wfw:comment>http://www.aygfsteel.com/lescony/comments/46794.html</wfw:comment><comments>http://www.aygfsteel.com/lescony/articles/46794.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.aygfsteel.com/lescony/comments/commentRss/46794.html</wfw:commentRss><trackback:ping>http://www.aygfsteel.com/lescony/services/trackbacks/46794.html</trackback:ping><description><![CDATA[
		<span style="FONT-SIZE: 14px; LINE-HEIGHT: 150%; FONT-FAMILY: verdana,'宋体',arial,sans-serif">Associate director of <a  target="_blank"><font face="宋体" color="blue">RFID</font></a> solutions and strategy for Manhattan Associates Greg Gilbert takes an honest look at the untold truths behind the promise of RFID technology.<br /><br /><br />With mass speculation and widespread news swirling around the evolution of RFID standards, it is little wonder that the topic has received a sensationalist spin akin to Y2K.<br /><br /><br />Frenzied companies, eager to adopt or comply, are scrambling for answers: instead, they find themselves mired deeper in confusion amid fast-breaking updates about EPC standards and various companies�?latest compliance requirements.<br /><br /><br />It’s time to set the record straight and offer executives some candid-talk about the reality of RFID. For all practical purposes, it is a ‘moving target�?? quite literally. Debunking the myths, misconceptions and mysteries surrounding RFID will help put it in proper perspective and save wasted hours and dollars searching for misguided answers.<br /><br /><br /><b>Myth #1: There are no set standards for RFID today.<br /><br /><br />Truth: GTAG? ISO 18006.A? ISO 18006.B? Gen 2 EPC?</b><br /><br /><br />The acronym soup has thickened into a murky and mind-boggling layer of complexity, further complicated by some vendors�?claims of ‘owning�?the standards.<br /><br /><br />The fact is that there are several RFID standards today. The major reason that the prior standards were never adopted on a broad scale was that the technology companies were the main drivers of these standards. They had a solution and were seeking a problem to address. EPC standards, however, were developed by end-user companies to ensure that the technology developed addressed a specific business need. Recent scuttlebutt regarding the Global Proposal verses the Freedom Proposal within the EPC Global community and company lawsuits have added to the uncertainty.<br /><br /><br />EPC Global is helping to define the standards for the next generation technology, but the big players, Wal-Mart, Metro, Department of Defence (DoD) and select Fortune 500 companies, are aggressively moving forward on the RFID adoption curve, and many have already implemented current generation EPC technology. Smaller businesses will likely take their cue from the industry leaders as RFID standards continue to evolve, emerge and ultimately become more entrenched.<br /><br /><br /><b>Myth #2: Replacing bar code-based processes with RFID processes will achieve ROI.<br /><br /><br />Truth: Feeling the pressure to incorporate RFID into their manufacturing and Logistics operations, some companies will tend to implement technology for technology’s sake.</b><br /><br /><br />Buyer beware: Implementing RFID does not instantly guarantee a fast-path to ROI. In order to impact the bottom line, the decision to implement RFID must be linked to a definitive business goal. For most companies, it’s cost-prohibitive to convert to RFID on a broad scale. And, in some cases, it does not even make sense.<br /><br /><br />For example, if your warehouse is reliably scanning bar coded cartons on a conveyor as they are loaded onto a truck, switching this process to RFID doesn’t really buy you anything. Why? Because the labour savings resulting from replacing an automated bar code scan with RFID simply doesn’t amount to much. However, if every carton is currently scanned manually, changing the process to automate the data capture could reduce labour requirements and increase facility throughput.<br /><br /><br />Further, if there are areas in which data is lacking, adding RFID can increase visibility and accuracy. The reality: RFID technology isn’t new. It has been around for the past decade, whereas bar code technology has surpassed three decades. The promise of achieving greater ROI with RFID is not time-sensitive; it is application-dependent.<br /><br /><b>Myth #3: RFID benefits only retailers, not suppliers.<br /><br /><br />Truth: While the RFID spotlight has clearly illuminated the major retailers (i.e. Wal-Mart, Tesco, Metro, Target, Albertson’s), several major Fortune 500 suppliers including Procter &amp; Gamble, Gillette and others are blazing the trail toward RFID implementation across the supply chain.</b><br /><br /><br />Suppliers might not achieve incremental ROI, but there are benefits to be gained. As the Wal-Marts and Metros of the world implement new RFID requirements, suppliers, in their efforts to comply, must be prepared to execute the right technology strategy to serve their own business.<br /><br /><br />Suppliers should view RFID compliance as a means to capture more detailed inventory information, increase visibility throughout the supply chain and reduce the number of claims. For example, while retailers will use RFID to reduce stock outs and increase sales as cases are received into stores and brought out to the sales floor, suppliers can utilise this shared data, for the first time, to gain new insights, better source products to meet demand patterns, take pre-emptive corrective actions to avoid claims and better satisfy their customers�?needs. More satisfied customers and increased store in stocks leads to more business.<br /><br /><br />M<b>yth #4: RFID is the only way to automate manual warehouse receiving processes.<br /><br /><br />Truth: In certain cases RFID may be appropriate for warehouse automation, but it is not the only solution.</b><br /><br /><br />In fact, one of the biggest paybacks of evaluating potential RFID uses in the warehouse is that this investigation actually helps uncover big savings opportunities that don’t require RFID technology.<br /><br /><br />Savings can be significant for manufacturing companies that are looking to eliminate their labour-intensive, paper-based processes by automating the receiving function. Tagging of cases can be done with bar code (versus RFID) technology and still yield tangible ROI because the company has eliminated the potential for manual intervention and thus human error. Another example is a manufacturer that bar codes pallets and scans these bar coded pallets onto containers.<br /><br /><br />If the company discovers that it never sends the advanced shipping notice (ASN) to the receiving warehouse, they’ve identified a gap that could be rectified and therefore lead to improved customer service. This scenario does not require RFID; rather, it involves the addition of a simple step to close the warehouse receiving process loop ? an especially important link for capable-to-promise (CTP) manufacturers.<br /><br /><br /><b>Myth #5: The EPC is an RFID replacement of the current bar codes (GTIN/UPC).<br /><br /><br />Truth: Electronic Product Code (EPC) used in RFID tags and bar coding are considered complementary data capture technologies.</b><br /><br /><br />Even with large-scale adoption of RFID, there will be a continued need for bar coding to co-exist with RFID into the foreseeable future. While current bar coding offers the same number for every case of a given SKU, EPC is a standard way to serialise all inventory. The unique attributes of RFID enable improved visibility into supply chain movements and history. With RFID technology, the level of information is deeper, allowing inventory to be tracked and data more freely shared between suppliers and retailers. While RFID has the potential to offer a closer technical fit and operational benefits in certain applications, it will not serve as a replacement for bar codes. Both types of technology have a place in today’s business environment.<br /><br /><br /><b>Myth #6: Adoption of RFID won �?t require facility, equipment and process changes.<br /><br /><br />Truth: Incorporation of RFID will necessitate a new look at existing business processes.</b><br /><br /><br />As emerging requirements and technological evolutions arise, companies will be forced to revisit their standard practices if they expect to gain new efficiencies from RFID implementation. They will need to ensure that there is a high level of compatibility in the integration of RFID within the facility ? how the physical layout is organised, how labour is deployed and even how the equipment itself is constructed.<br /><br /><br />Take the example of a forklift truck. If it is blocking the RFID signal at the reader level, something must change in order to get the best point of read and trigger dock door verification onto trucks. The good news is that this level of change can prompt even better practices that otherwise would not have occurred without the company’s consideration of RFID.<br /><br /><br />My<b>th #7: Readability challenges are only for companies with metal and liquid products.<br /><br /><br />Truth: While early use of RFID poses obstacles when used with metal and liquids, the technology is continuing to evolve and undergo more rigorous testing, both in the lab and in the field.</b><br /><br /><br />Companies are carrying forward lessons learned and best practices by continuously applying the science of physics to the art of RFID implementation. There’s no substitute for testing RFID with your own products in your own environment. You need to make sure that you get a consistent, reliable read rate that meets the needs of your use-case, when RFID tags are applied to your products, packaging and pallets. Experiment up front to thoroughly test these applications before making a large investment in an RFID solution.<br /><br /><br /><b>Myth #8: Consistently reading every EPC on a pallet is easy.<br /><br /><br />Truth: While using EPC tags beats scanning, it is not foolproof.</b><br /><br /><br />So many variables can interfere with accurate and reliable read rates. These might include the sizes of boxes, the number of cases, travel speed; types of tags, tag placement, reader/antenna placement and even the product mix itself (i.e. different substances). Where the actual tags get read is a key consideration. Avoid the need to physically break apart boxes to reveal the EPC label. The goal is to eliminate any inconsistencies and increase read rates, not dropout rates!<br /><br /><br /><b>Myth #9: All RFID tags are the same.<br /><br /><br />Truth: All RFID tags are not created equally.</b><br /><br /><br />There are different types of tags for different applications, depending on the environment and business processes where RFID will be applied. Pharmaceutical, food and hospital emergency room RFID applications, for example, require pristine and sanitary conditions that are vastly different than uses for RFID in an automotive factory or steel plant.<br /><br /><br />Use the following checklist to determine which types of RFID tags are most compatible with your unique business environment:<br /><br /><br />? read distance required<br /><br />? frequency at which RFID tags operate/clarity of signal<br /><br />? price (RFID tags range in cost from 15 Eurocents to 60 Eurocents.) Which type can you afford and still yield an ROI?<br /><br />? Compatibility with temperature/humidity (plant, storage, shipping facilities)<br /><br />? type of product to which RFID tags are applied ? wood, liquid, plastic, metal.<br /><br />? orientation of building lay-out to maximise tag readability<br /><br /><br />Other considerations will also affect your selection of appropriate RFID technology, as this list is not all-inclusive.<br /><br /><br /><b>Myth #10: EPC technology can only be used for consumer goods.<br /><br /><br />Truth: While early use of the EPC technology by the Auto-ID centre is focused on the consumer goods value chain, the technology was designed to allow for easy expansion into other industries.</b><br /><br /><br />The EPC code, as designed today, includes a header section that instructs other systems on how to interpret the remainder of the data on the tag. There are 256 possible schemas with the current eight-bit header. Currently, only five are in use. This leaves significant room for the addition of different encoding schemas, from NDC codes in pharmacy applications to automotive parts.<br /><br /><br />Your unique business environment will inherently dictate your RFID requirements. Do not be fooled by the existing hype about RFID. Remember that RFID does not have to be an ‘all or nothing�?proposition. It can be implemented in phases and applied to specific projects to accurately gauge ROI benefits.<br /><br /><br />Learn from the early pioneers who are testing the waters and charting the course toward universal RFID standards. Now is the time to research the possibilities, understand the challenges before you and earmark funds for forthcoming RFID hardware and software investments. Starting conservatively will enable you to progress at a comfortable pace that is right for your business.</span>
<img src ="http://www.aygfsteel.com/lescony/aggbug/46794.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/lescony/" target="_blank">���单爱</a> 2006-05-18 13:47 <a href="http://www.aygfsteel.com/lescony/articles/46794.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>[Oracle]RFID技术与中国自主产品�Ҏ��</title><link>http://www.aygfsteel.com/lescony/articles/46707.html</link><dc:creator>���单爱</dc:creator><author>���单爱</author><pubDate>Wed, 17 May 2006 15:18:00 GMT</pubDate><guid>http://www.aygfsteel.com/lescony/articles/46707.html</guid><wfw:comment>http://www.aygfsteel.com/lescony/comments/46707.html</wfw:comment><comments>http://www.aygfsteel.com/lescony/articles/46707.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.aygfsteel.com/lescony/comments/commentRss/46707.html</wfw:commentRss><trackback:ping>http://www.aygfsteel.com/lescony/services/trackbacks/46707.html</trackback:ping><description><![CDATA[甲骨文宣布， Oracle��Z��传感器的解决�Ҏ��在经�q�了本地化之后已�l�顺利通过���试及评伎ͼ�从即日�v可以全面支持北京�l�深电子技术有限公司具有自�ȝ��识��权的���频识别 (RFID)��d��器Vision R9100。此举不仅意味着甲骨文公司的RFID解决�Ҏ��与中国的RFID自主产品成功完成�Ҏ���?
<p>　　甲骨文中国研发中心本�ơ�ؓVision R9100 RFID��d��器开发了驱动器，从而��Vision R9100能够与Oracle Sensor Edge Server�q�接�Q���而自动采集数据。这是甲骨文公司首次��Z��国自主RFID产品提供支持�?/p><p>　　���频识别�Q�Radio Frequency Identification�Q�简�U�RFID�Q�俗�U�电子标�{�）是一�U���用标�{�֒�阅读讑֤��q�用无线甉|�L来自动识别货物的技术。由于它不再需要通过诸如人工条�Ş码扫描的�U�条识别方式�Q�从而实��C��关键供应铄���交易自动化，赢得了供应商、分销商、制造商和零售商的青睐。根据无�U�数据研�I����团（Wireless Data Research Group�Q�的报告�Q�业界的�q�些做法���有助于���扩大全球RFID的市�����模，估计�?007�q�可�?0亿美元。中国高技术研�I�发展计划（�?63”计划）的“十一五”规划中已经���RFID产业定�ؓ重大专项�q�将投入大量资金�q�行扶植。在新的五年规划中，国家不仅��x��相关产品的自�ȝ��发与创新�Q�同时也更加��x���q�些产品的行业应用，�q�计划徏讄���兌���业的�C����工程�Q�通过应用拉动产业发展�?/p><p>　　北京�l�深电子技术有限公司�ȝ��理张革军指出�Q�“世界各发达国家和国际跨国公叔R��在加速推动RFID技术的研发和应用进�E�，在过��d���q�间�Q�共有超�q?000��关于RFID技术的专利被申��P��主要集中在美、欧、日�{�发辑֛�家和地区。中国是世界上�h口最多的消费大国�Q�也正在成�ؓ世界刉���和加工大国�Q�中国必���成��Z��界RFID技术最大的应用市场。中国企业应�U�极利用国际技术迅猛发展、中国政府大力支持的历史时机�Q�与自��n具备的本土化优势相结合，自主创新�Q��ƈ��d��与国内外RFID技术领先的企业联合�Q�迎接��业发展的新机遇。因此，此次与甲骨文公司合作意义非凡�Q�它不仅使维��q��子获得了与国际知名IT企业合作的宝�늻�验，也��我们的��品走向了更广阔的舞台。�?/p><p>　　甲骨文公�怸�国研发中心副总裁Pascal Sero表示�Q�“甲骨文在深圛_��北京同时拥有两个研发中心�Q�我们专注于包括RFID在内的移动计���新技术�ƈ�׃���q�些新技术在中国有着巨大的应用潜力，中国也有能力���这些技术推动到一个更高的水��^�Q�因此我们非�怹�意与�l�深电子�q�样的中国RFID领先厂商合作。�?他透露�Q�甲骨文正通过与中山大学岭南学院共同成立的供应铄���理研�I�中心展开RFID在物���领域的应用研究�Q�同时还通过深圳的技术资源中心（SSPOCC�Q��ؓRFID应用合作伙伴提供支持。此外，甲骨文中国研发中心还与包括日本、韩国、香港和台湾在内的亚太区RFID相关厂商展开合作研究�?/p><p>　　Oracle��Z��传感器的解决�Ҏ���Q�Oracle Sensor-Based Services�Q�是一�l�范围广泛的功能集合�Q�可以捕莗���管理、分析、访问和响应来自RFID、位�|�和温度�{�传感器的数据。在Oracle数据�?0g、Oracle应用服务�?0g、Oracle企业���理�?0g和Oracle电子商务套�g11i.10的基���上，Oracle��Z��传感器的服务使企业能够快速、轻村֜����基于传感器的信息集成到他们的企业系�l�中。该服务目前支持Intermec、Alien.、Symbol�{�国际著名厂商的RFID讑֤�产品�?/p><p>　　Vision R9100��d��器是中国真正意义的完全自�ȝ��识��权��品，它的诞生与国�?63计划的大力支持密不可分。早�?004�q�底�Q�北京维��q��子技术有限公司就承担了国安���技术研�I�发展计划（�?63”计划）的一个重要研发课题：《无�U�射频关键技术研�I�与开发》（��N���~�号�Q?005AA420050-04�Q�的子课题《UHF��d��器核心模块研�I�》。通过自主创新�Q�维��q��子研发出了完全具有自�ȝ��识��权的UHF��d��器核心模块，�q�也是维��q��子超高频��d��讑֤�R9100的雏形与核心。经�q?005�q�一�q�的不断改进与测试，R9100逐渐走向成熟�Q�该产品实现了多通讯协议兼容、射频输出功率可调、中心工作频率可调等功能�Q�通过对多�U�空中接口协议的实现�Q�项目组�U�篏了大量的�l�验和试验数据，可以为开发中国标准的�I�Z��接口协议提供基础数据�Q�同时课题研发的��d��器��品在本项目其他子��N��“发动机生��U�쀝、“邮攉K��递邮件��d��带牌”等��目中得��C��应用�?/p><img src ="http://www.aygfsteel.com/lescony/aggbug/46707.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/lescony/" target="_blank">���单爱</a> 2006-05-17 23:18 <a href="http://www.aygfsteel.com/lescony/articles/46707.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item></channel></rss>                                        <footer>
<div class="friendship-link">
<a href="http://www.aygfsteel.com/" title="&#29408;&#29408;&#20037;&#20037;&#20122;&#27954;&#27431;&#32654;&#19987;&#21306;&#95;&#20013;&#25991;&#23383;&#24149;&#20122;&#27954;&#32508;&#21512;&#20037;&#20037;&#50;&#48;&#50;&#95;&#22269;&#20135;&#31934;&#21697;&#20122;&#27954;&#31532;&#20116;&#21306;&#22312;&#32447;&#95;&#26085;&#26412;&#20813;&#36153;&#32593;&#31449;&#35270;&#39057;">&#29408;&#29408;&#20037;&#20037;&#20122;&#27954;&#27431;&#32654;&#19987;&#21306;&#95;&#20013;&#25991;&#23383;&#24149;&#20122;&#27954;&#32508;&#21512;&#20037;&#20037;&#50;&#48;&#50;&#95;&#22269;&#20135;&#31934;&#21697;&#20122;&#27954;&#31532;&#20116;&#21306;&#22312;&#32447;&#95;&#26085;&#26412;&#20813;&#36153;&#32593;&#31449;&#35270;&#39057;</a>

</div>

</footer>


��վ֩���ģ�壺
<a href="http://" target="_blank">����ʡ</a>|
<a href="http://" target="_blank">����</a>|
<a href="http://" target="_blank">�°���</a>|
<a href="http://" target="_blank">��˳��</a>|
<a href="http://" target="_blank">����������</a>|
<a href="http://" target="_blank">̫����</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">���ľ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">����ʡ</a>|
<a href="http://" target="_blank">��ʲ��</a>|
<a href="http://" target="_blank">�ݳ���</a>|
<a href="http://" target="_blank">����ɽ��</a>|
<a href="http://" target="_blank">¹Ȫ��</a>|
<a href="http://" target="_blank">Ԫ����</a>|
<a href="http://" target="_blank">�ؿ�˹��</a>|
<a href="http://" target="_blank">�߰���</a>|
<a href="http://" target="_blank">���</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��ƽ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">���п�ǰ��</a>|
<a href="http://" target="_blank">����</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">«ɽ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��ƽ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��ɳ��</a>|
<a href="http://" target="_blank">������</a>|
<script>
(function(){
    var bp = document.createElement('script');
    var curProtocol = window.location.protocol.split(':')[0];
    if (curProtocol === 'https') {
        bp.src = 'https://zz.bdstatic.com/linksubmit/push.js';
    }
    else {
        bp.src = 'http://push.zhanzhang.baidu.com/push.js';
    }
    var s = document.getElementsByTagName("script")[0];
    s.parentNode.insertBefore(bp, s);
})();
</script>
</body>