T-SIX An Indexing System for XML Siblings
【cisco】architecture wifi offload
White PaperArchitecture for Mobile Data Offload over Wi-Fi Access NetworksIntroductionMobile network traffic is growing exponentially, and service providers must manage their networks efficiently to meet consumer demand. The technology evolution of radio access networks is limited by the laws of physics, and significant growth in radio frequency (RF) efficiency can no longer be expected. Long-Term Evolution (LTE) radio access is reaching the limits of Shannon’s law, the spectrum available for mobile data applications is limited, and the only solution for increasing overall mobile network capacity is to increase the carrier-to-interference ratio while decreasing cell size and deploying small cell technologies. The most efficient way to use small cells is to position them in locations where significant amounts of data are generated (shopping malls, stadiums, university campuses, public transportation hubs, etc.) and where subscribers spend most of their time and therefore consume significant amounts of data (homes, offices, etc.). Wi-Fi, one of the small cell technologies, appeals to many operators as a cost-effective mean of offloading large amounts of mobile data traffic while delivering a variety of new services. It offers these features:● ● ● ●Widespread existing deployments Availability of user devices that support the technology Cost efficiency Capability to address new users and devices without mobile subscription (without a subscriber identity module [SIM])● ●Globally available spectrum capacity Standards availability for integration into mobile core networksThis document explores technical aspects of Wi-Fi offload architecture and its capabilities and integration into existing mobile networks to provide a viable and efficient way to offload subscriber traffic.Overview of Wi-Fi Offload ArchitectureThe Third-Generation Partnership Project (3GPP) standard differentiates two types of Wi-Fi access (also referred to as non-3GPP IP access):●Untrusted: Introduced in the early stages of the Wi-Fi specification in 3GPP Release 6 (2005), untrusted access includes any type of Wi-Fi access that either is not under control of the operator (public open hotspot, subscriber’s home WLAN, etc.) or that does not provide sufficient security (authentication, encryption, etc.).●Trusted: Trusted access generally refers to operator-built Wi-Fi access with over-the-air encryption and a secure authentication method. Trusted non-3GPP IP access was introduced only with the LTE standard in 3GPP Release 8 (2008). Although most of today’s offload designs are build on the trusted model, 3GPP does not currently offer guidance for integration with the 3G or 2G packet core. However, as discussed in this document, this type of access is natively integrated into LTE’s evolved packet core (EPC).© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 1 of 23Because most of today’s mobile networks are 3G based, a significant part of this document describes the possible methods of integrated trusted non-3GPP IP access into the 3G mobile packet core (MPC) together with its associated policy and charging control (PCC) architecture. Although the term “trusted non-3GPP IP access” is defined for EPC only, this document extends its definition in 3G contexts to describe Wi-Fi networks controlled by mobile operators. 3GPP 24.302 has the following definition: “For a trusted non-3GPP IP access network, the communication between the user equipment and the EPC is secure.” Thus, with the latest service provider Wi-Fi architectures encompassing Extensible Authentication Protocol (EAP) and IEEE 802.1X-based authentication, and with IEEE 802.11i-based RF encryption and optional use of control and provisioning of wireless access points and Datagram Transport Layer Security (DTLS) for secured user and control planes, all the elements exist for service provider Wi-Fi to be considered as trusted non-3GPP. After the 3G designs, this document describes the evolution of the architectures toward EPC integration as specified in 3GPP standards. Session mobility and, more generally, IP address persistence when moving between 3G, LTE, and Wi-Fi are also covered. The document also discusses the integration models for untrusted networks, although these are less commonly deployed in mobile networks. In the 3GPP specification, the Wi-Fi network is referred to as the Wi-Fi access network only. No details about the Wi-Fi network structure are specified. This document, however, separates the network into the access and gateway components. The Wi-Fi network infrastructure for mobile data offload consists of three parts:● ●Wi-Fi radio access network (Wi-Fi RAN) Wi-Fi access gateway (WAG) and Wi-Fi back-end systems (this document expands the definition from 3GPP TS 23.234 to refer also to non-3GPP WAG)●Packet core integration elements (multiple options)© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 2 of 23Figure 1 illustrates the architecture. It includes integration elements for 3G as well as LTE to show a summary of all designs built throughout this document.Figure 1. Wi-Fi Network ArchitectureIf the Wi-Fi network is used for mobile data offload, which is the topic of this document, it needs to take care of these tasks:● ●Authentication: To help ensure that only authorized subscribers can access the network PCC: For proper billing, quality of service (QoS), and policy enforcement for the traffic generated through Wi-Fi access, ideally compliant with 3GPP PCC●IP persistence: For service mobility between different access networks (3G to Wi-Fi, Wi-Fi to 3G, or across the Wi-Fi network)The following sections examine the details of each of these functions.AuthenticationTo control subscriber access to Wi-Fi networks, multiple authentication methods can be used. The choice of method is crucial to the usability of the network. The more transparent the authentication method is for the subscriber, the greater the likelihood that the subscriber will connect to the network. The authentication method also determines the subscriber and device types that can be addressed in a particular network (subscribers with or without SIM cards, the operator’s subscribers, visiting subscribers, etc.). In a typical modern Wi-Fi network, two types of authentication are available to address all possible subscribers and at the same time provide convenient access to the network for frequent Wi-Fi users. The first method, portalbased authentication, targets customers without a permanent contract with the operator (vouchers, time-limited© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 3 of 23access, SMS payments, etc.). Alternatively, EAP authentication provides transparent and easy access for the operator’s own subscribers with SIM cards or certificates.Portal-Based AuthenticationPortal-based authentication depends on Layer 3 connectivity to the network and HTTP communication before granting access to the subscriber. The Wireless Internet Service Provider Roaming (WISPr) standard also uses HTTP communication with the portal for automatic authentication, with the user device launching HTTP communication in the background without user intervention (Figure 2).Figure 2. Portal-Based Authentication ArchitectureThis method relies on the WAG in the Wi-Fi network, which blocks all IP communication for unknown (new) subscribers and redirects HTTP connections to a captive portal. The captive portal is responsible for requesting user credentials from the subscriber and triggering authentication, authorization, and accounting (AAA) to authenticate the subscriber. After successful login, the WAG will typically be signaled by the AAA server. From this moment, the subscriber is known in the AAA cache, and WAG allows the subscriber to send and receive data. Usually, the user’s IEEE 802.11 MAC address is also cached in the AAA server, together with the user data and granted service. If the subscriber leaves the Wi-Fi coverage area and then returns, the subscriber’s device will be recognized by the WAG based on the MAC address and automatically authenticated against the cached AAA record, so the subscriber is not repeatedly redirected to the portal after losing Wi-Fi coverage. This method of MAC address caching is also referred to as transparent automatic logon (TAL).© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 4 of 23A typical TAL attachment call flow is shown in Figure 3 for the case of a Layer 2 attached WAG.Figure 3. Typical Transparent Automatic Logon Call FlowEAP-Based AuthenticationEAP-based authentication uses EAP and IEEE 802.1x to provide Layer 2 authentication for subscribers accessing the network with EAP-capable devices. For actual authentication, multiple credentials can be used, depending on the capability of the device. Devices with SIM cards encapsulate the SIM application information exchange into the EAP message, and these are proxied by the AAA server to the home-location register (HLR) for authentication. EAP-SIM (RFC 4186) or EAP-Authentication and Key Agreement (EAP-AKA; RFC 4187) standards are used for the encapsulation, depending on the type of SIM card used and the HLR capabilities. Obviously, this method requires interconnection between the AAA server and the HLR or home-subscriber server (HSS). The architecture is shown in Figure 4.© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 5 of 23Figure 4.EAP-Based Authentication ArchitectureFor subscribers with non-SIM devices, the operator can distribute certificates for EAP-Transport Layer Security (EAP-TLS) or similar versions of EAP authentication. The typical call flow of EAP authentication (with HLR integration) is shown in Figure 5.Figure 5. Typical EAP Authentication Call Flow© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 6 of 23Note that EAP-based authentication offers a radio security advantage. Because the authentication is handled at Layer 2, EAP messages can be used to negotiate encryption keys for the IEEE 802.11i-based encryption of the radio interface. This approach provides much stronger security for radio communication compared to the unencrypted radio interface of portal-based authentication and is uniquely able to prevent simple MAC address spoofing attacks.Next Generation HotspotIn 2010, Cisco and industry leaders formed the Next Generation Hotspot Task Group in the Wireless Broadband Alliance (WBA). The goal was to rally the industry around a common set of Wi-Fi Alliance (WFA) standards called Hotspot 2.0 that would bring a 3G-like end-user experience to Wi-Fi authentication and roaming. The outcome of the Next Generation Hotspot Task Group is a set of operator guidelines and the Wi-Fi Certified Passpoint interoperability for operators and equipment vendors. The Cisco SP Wi-Fi solution features Next Generation Hotspot, enabling service providers to better manage and monetize their carrier-grade Wi-Fi networks. There are three main building blocks of the next-generation hotspot: IEEE 802.11u, Wi-Fi Protected Access 2 (WPA 2) Enterprise, and EAP-based authentication. For a detailed description of the initiative, see The Future of Hotspots: Making Wi-Fi as Secure and Easy to Use as Cellular.® ™program expected in 2012 from the Wi-Fi Alliance. The certification will help ensure authentication and roamingAuthentication SummaryBecause of the complementary functions of both authentication methods, mobile operators deploying Wi-Fi access networks usually implement both EAP and IEEE 802.1X authentication and portal-based authentication in their networks. Portal-based authentication is used to attract subscribers visiting the network who don’t yet have a relation to the operator. It allows typical public Wi-Fi use cases such as credit card payments, vouchers, and SMS passwords. In general, it enables generation of new revenue from Wi-Fi networks. EAP-based authentication targets primarily devices with the operator’s SIM card. It allows transparent authentication and secure communication without much interaction from the subscriber (only initial configuration of the service set ID (SSID) is needed when a device detects the Wi-Fi network for the first time). In real-life deployments, the introduction of EAP-SIM or EAP-AKA authentication leads to significantly better utilization of the network by subscribers and therefore enables much greater savings from offloading. With the introduction of Wi-Fi Certified Passpoint devices, operators will be able to simplify Wi-Fi network access even more. IEEE 802.11u devices do not need any intervention from the subscriber to connect to the Wi-Fi network (unlike traditional devices, which require SSID selection). Roaming agreements based on the Next Generation Hotspot recommendation (WLAN Roaming Inter-Exchange [WRIX]) enable user equipment with IEEE 802.11u support to choose the right SSID automatically, even in visited networks.Policy and Charging ControlAn important concern of mobile operators is the availability of similar or identical policy enforcement and charging rules for the subscriber, regardless of the RAN being used. Therefore, the design of PCC integration is a crucial part of Wi-Fi offload.© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 7 of 23Experience from live deployments shows that the most efficient approach to PCC integration is the reuse of the elements deployed for the 3GPP services. The actual integration option will depend on the PCC infrastructure implemented in the particular mobile operator network. If the operator uses a device with the standalone policy and charging enforcement function (PCEF), the WAG will be integrated as an additional gateway served by the PCEF. If the PCEF is integrated into the gateway General Packet Radio Service (GPRS) support node (GGSN), the WAG may emulate a serving GPRS support node (SGSN) and switch the Wi-Fi sessions to a GPRS Tunneling Protocol (GTP) tunnel to the traditional GGSN. The following sections discuss the details of these two options. Note that this document describes trusted non-3GPP access integration into 2G and 3G PCC. The 3GPP standard offers no guidance for this integration. Later this document explores standardized architecture for LTE integration and untrusted non-3GPP IP access integration.Standalone PCEFIn the standalone PCEF scenario, the WAG is set up to send user data traffic to the PCEF for PCC integration. At the same time, traffic that does not need policy control (traffic from visiting customers, wholesale traffic, onetime voucher users, etc.) is allowed to go directly to the Internet (Figure 6).Figure 6. Standalone PCEF ArchitectureBecause the PCEF needs to be able to correlate the user identity with the data flows passing the PCEF, a mechanism is needed that can synchronize the user identity with the IP address of the subscriber (so that individual data packets can be associated with the user data plan and processed accordingly). Commonly, the RADIUS proxy function on the PCEF is used to create user session information based on the attributes included in the accounting messages coming from the access gateway for a particular user. Figure 7 shows the typical call flow.© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 8 of 23Figure 7.Typical PCEF Authentication Call FlowIf this model is deployed, the operator needs to help ensure that all mandatory information needed by the PCEF is included in the RADIUS messages from the access gateway or proxied through AAA, where the necessary attributes are added to the message. In addition to the IP address of the subscriber session, information about the international mobile subscriber identity (IMSI), the mobile station international subscriber directory number (MSISDN), and the associated access point name (APN) is usually required.GTP to Traditional GGSNIf the PCEF is an integral part of the GGSN, the option of forcing Wi-Fi sessions into a GTP tunnel (packet data protocol [PDP] context) may provide the best solution for PCC integration. The traffic that does not belong to the mobile subscribers of the operator, and which therefore cannot be processed on the GGSN, is forwarded directly to the Internet (Figure 8).© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 9 of 23Figure 8.GTP-to-Traditional GGSN ArchitectureClearly, GTP support is required on the WAG for this deployment model. Also important to consider is the availability of the required attributes in the PDP context request, which are mandatory in the operator’s PCC system. Again, these attributes commonly include the IMSI, MSISDN, QoS profile, and APN. The call flow for this deployment model is shown in Figure 9.Figure 9. GTP-to-Traditional GGSN Call Flow© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 10 of 23Note that even though all sessions (3G and Wi-Fi) are anchored on the GGSN, this solution does not provide transparent handover of the IP sessions between the Wi-Fi and 3G radio networks. This limitation exists because the Wi-Fi and 3G PDP contexts are individual sessions, and the user device can open them simultaneously. Unfortunately, the 3GPP standard does not provide a mechanism to help ensure that the same GGSN is chosen for both of these PDP contexts, and therefore anchoring of the sessions on the same device cannot be achieved.PCC Integration ConsiderationsWhen performing PCC integration, note the following:●The options listed are valid and needed for 3G. As discussed later, LTE provides native integration into theEPC and therefore into the PCC●The critical element is the capability of the WAG to provide all necessary information for charging(specifically, some of these attributes are not part of EAP authentication and need to be retrievedseparately, if needed: for example, the MSISDN, the QoS profile, and optionally, the 3GPP chargingcharacteristics)●Usually, the PCEF does not handle traffic from users who are not mobile customers of the operator(non-SIM subscribers). This traffic is sent directly to the Internet. If these particular sessions need policy or charging functions, these are usually handled by the WAG and Wi-Fi back-end systems directlyLTEBefore describing the third function of the Wi-Fi offload architecture, session handover, this document examines the integration of PCC in an LTE scenario. This examination will help you later understand user session mobility and anchoring.3GPP TS 23.402 describes native integration of trusted and untrusted non-3GPP IP access networks into the EPC. The standard accepts that the Wi-Fi network is as valid an access network as any other 3GPP radio access network. This acceptance enables operators to use the standards-based EPC components for integration and therefore helps ensure a good level of interoperability between different access types.As mentioned earlier, this document concentrates first on the trusted part of the architecture. To force the Wi-Fi traffic to the EPC, two interfaces are defined, both of them terminating Wi-Fi sessions on the packet data network gateway (P-GW) as shown in Figure 10.Figure 10. 3GPP Architecture for Non-3GPP IP Access Integration into EPC, S2c OptionThe S2c interface is based on the Dual-Stack Mobile IP Version 6 (DSMIPv6) protocol and requires user equipment to support it. DSMIPv6 creates a tunneled connection between the user equipment and the P-GW, which is used to forward all traffic to and from the user equipment. The P-GW is responsible for assigning a virtual IP address to the tunnel during the setup process. This IP address is from the same IP pool that is used for LTE sessions. Because all traffic to and from the user equipment is sent through the tunnel, the P-GW has complete visibility of the user traffic and can apply PCC and other necessary functions to the traffic in the same manner as it does to the LTE sessions (Figure 11).Figure 11. 3GPP Architecture for Non-3GPP IP Access Integration into EPC, S2a OptionAnother option shown in Figure 11 is to choose the S2a interface for forwarding traffic from the Wi-Fi network to the EPC. This interface is based on the Proxy Mobile IPv6 (PMIPv6) protocol. As with S2c, the interface terminates on the P-GW and enables visibility into the user traffic. The difference is that the PMIPv6 protocol does not require any changes on the user equipment. The wireless access gateway (WAG) in the trusted non-3GPP IP access network provides the mobile IP functions transparently for the client. It creates the tunnel, requests the IP address from the P-GW, and then assigns this address to the Wi-Fi connection. In this way, the user equipment is assigned an IP address that is part of the P-GW pool, but it does not see the address as virtual but as a physical address directly on the Wi-Fi interface.Figure 12 shows an overview of LTE architecture. Again, in addition to tunneled traffic to the EPC, direct connection from the WAG to the Internet is enabled for users who are not mobile subscribers of the operator.Figure 12. LTE ArchitectureTwo methods of integration (S2a and S2c) have been used here, and each has different implications for the deployment. The S2c approach requires changes on the user equipment; therefore, it is considered client-based. This feature may not be trivial in a mobile network because of the need for client software for functions. The mobile operator must help ensure that large numbers of different handsets and operating systems can be addressed by the software, must keep the user equipment updated with new versions of software, and must motivate subscribers to use the client software. Figure 13 illustrates the attachment as defined by 3GPP. Phase A represents attachment to the Wi-Fi network. In phase B, the DSMIPv6 tunnel is opened to the P-GW; and in phase C, the session is signaled as the active one. Also illustrated is the establishment of policies for the session using the PCRF.Figure 13. S2c Network Attachment As Defined by 3GPPThe S2a approach eliminates the problem of the client software. The trade-off here is that the operator loses control of Wi-Fi activation and session handover on the user equipment. This loss of control may result in unexpected behavior of the user equipment during switchover from 3GPP access to Wi-Fi and back. Figure 14 shows the attachment as defined by 3GPP. The trusted non-3GPP IP access network represents the Wi-Fi network, with the WAG as part of this network. For a detailed description of the call flow, please refer to 3GPP TS 23.402.Figure 14. S2a Network Attachment As Defined by 3GPPInter-Radio HandoverBefore analyzing different methods of handover, it is important to understand the terms often used in this context. Specifically, you need to understand what session handover is and the types of handover that can be implemented depending on the requirements of the mobile operator.In mobile data networks, one of the most important procedures is handover - when a subscriber moves from one radio station to another. The handover procedure describes the behavior of the network when the subscriber switches from one radio type to another (for example, from 3G to Wi-Fi).Today, few handover types can be used. The one required in the operator’s network needs to balance the expectations of subscribers and the complexity of the architecture.●Handover without IP address persistency (connectivity handover): When a subscriber connects to the Wi-Fiaccess network, the subscriber is authenticated transparently and is assigned a new IP address by theWi-Fi network. All new communications can use the new IP address as the source. All established TCP and UDP connections can, however, still continue over the 3G network. If the user equipment logicdisables the 3G interface, then these established sockets will need to be (automatically) reestablished over Wi-Fi, using the new IP address.●Handover with IP persistency (IP handover): When a subscriber connects to the Wi-Fi network, thesubscriber will be assigned the same IP address as he used on the 3G or LTE network. If the established TCP and UDP connections are bound to a physical interface (because of the TCP/IP stack implementation of the UE), they will need to be (automatically) reestablished using the new Wi-Fi interface, even though they will use the same IP address.●Session handover (transparent handover): This type of handover is similar to IP handover, but thehandover must occur in a time range that allows real-time media applications (voice over IP, streamingvideo, etc.) - for example, using established UDP sockets for media and TCP sockets for the control-plane protocol - to continue without interruption or user-experience degradation as the device switches between Wi-Fi and 3G cellular connectivity.Note that seamless handover can be achieved only with user equipment cooperation, which means that software updating (for client software) is needed on terminals. At minimum, this software needs to provide a virtual interface adapter, to mask the physical interface structure for TCP and UDP sockets. The challenges of client software have already been discussed above.3GPP defines handover mechanisms for trusted Wi-Fi only as part of the LTE architecture. For untrusted Wi-Fi, proposals exist for 3G and LTE. This document starts with a look at trusted non-3GPP IP access networks in LTE.S2a-Based Handover (Clientless)The advantage of PMIPv6 as protocol for the S2a interface is that the protocol is built for network-based IP mobility. Therefore, it can provide, without client involvement, handover of the IP address between different access types. In this design, the P-GW is responsible for anchoring the session, assigning the IP addresses, and switching the PMIPv6 or Ga TP tunnels between different access gateways in the event of handover. The access gateways must support the mobile access gateway (MAG) function to fulfill all mobile IP-related mobile-node functions.Figure 15 illustrates the handover call flow as defined in 3GPP TS 23.402. The trusted non-3GPP IP access element is equivalent to a WAG.Figure 15. Handover Call Flow As Defined in 3GPP TS 23.402Although S2a-based handover is clientless, recall that the problems with Wi-Fi-to-3GPP handover are the existence of two radio interfaces on the user equipment and the role of the user equipment as the handover decision point. Because of these two factors, the network can never ensure that the user equipment is using the proper interface.Note: The definition of what constitutes a proper interface can change on an operator-by-operator basis.Also, at the user equipment, the TCP/IP stack needs to be able to cope with two physical interfaces that may eventually have identical IP addresses. Additionally, in some TCP/IP stack implementations, application sockets may be bound to a physical interface. Therefore, when the user equipment or application switches between interfaces, the application connections must be dropped and may need to be reestablished from the new interface.Given all of these dependencies, the PMIPv6-based architecture cannot (without user equipment support) guarantee operation of a transparent handover function on all user equipment types. This situation can be improved if a properly designed connection manager (with virtual adapters) is installed on all user equipment.Cisco is actively working with chipset and handset vendors to support standardization and development of user equipment that meets the requirements for smooth clientless handover.S2c-Based Handover (Client-based)For the S2c interface, 3GPP reuses the IETF-defined DSMIPv6 protocol between the user equipment and theP-GW as the anchor point. When on the non-3GPP network, the user equipment builds the DSMIPv6 to the appropriate P-GW and is assigned a virtual IP address, which is then used for application communication.The same IP address will be assigned to the user equipment over a 3GPP access network in the event of handover. The 3GPP network is treated as the home network, and therefore the user equipment does not need to set up a DSMIPv6 tunnel on the 3GPP access network.Figure 16, from 3GPP TS 23.402, summarizes the call flow during handover from an LTE access network to aWi-Fi access network.。
SequenceManager Logix Controller-based Batch和排队解决方
SequenceManagerLogix Controller-based Batch and Sequencing SolutionA Scalable Batch Solution for Process Control ApplicationsA modern batch system must account for the growing need for architecture flexibility, true distribution of control, and scalability. SequenceManager software provides batch sequencing in the Logix family of controllers by adding powerful new capability closer to the process and opening new possibilities for skids, off network systems, and single unit control. SequenceManager allows you to configure operations in Studio 5000 Logix Designer®, run sequence in FactoryTalk® View SE, and to capture and display batch results.SequenceManager directs PhaseManager™ programs inside a Logix-based controller in an ordered sequence to implement process-oriented tasks for single unit or multiple independent unit operations. Using industry standard ISA-88 methodology, SequenceManager enables powerful and flexible sequencing capabilities that allow for the optimal control of sequential processes.With SequenceManager, you can deliver fast and reliable sequence execution while reducing infrastructure costs for standalone units and complete skid-based system functionality.Key BenefitsSequenceManager™ software significantly reduces engineering time for system integrators and process equipment builders while providing key controller-based batch management capabilities for end users. Key benefits include:• Enables distributed sequence execution • Fast and excellent reliability of sequence execution native to controller • Efficient sequence development and monitoring in core product • Integrated control and HMI solution for intuitive operation • Reduced infrastructure costs for small systems • Provides data necessary for sequence reportingDistributed Batch Management Based on Proven TechnologyBuilt Upon Rockwell AutomationIntegrated ArchitectureSequenceManager was built using the standard control and visualization capabilities found in Rockwell Automation® Integrated Architecture® software. SequenceManager is a new capability that is builtinto Logix firmware that uses visualization through FactoryTalk® View SE to create an integrated sequencing solution. Combined with event and reporting tools, SequenceManager software is a complete batch solution for single unit and skid-based process applications.Scalable Controller-based Solution SequenceManager allows flexible design for skid-based equipment to be developed, tested and delivered asa fully functioning standalone solution but, if needed, seamlessly integrated into a larger control system. This strategy provides the end user with the option to integrate equipment without imposing design constraints on the OEM delivering the skid. Additionally, it enables the end user to deliver equipment as a standalone system without the constraint to scale to a larger process solution in the future. This batch solution offers scalability to help prevent costly redesign and engineering.Flexibility to Meet Process Needs SequenceManager enables you to expand your process control on skid based equipment that performs repetitive tasks and decision-making abilities. By using the ISA-88 methodology, SequenceManager allows for control design that can be adopted to fit the needs of the process industries without the constraints of custom application code. Built-in state model handling provides for fast and easy configuration while maintainingcontrol of the process.Editor and ViewerAs a brand new program type in Studio 5000 Logix Designer®, SequenceManager™ software gives the user the power and flexibility necessary to create dynamic recipes to maximize the effectiveness of the process control system.Without limitations on steps and parameters, and the ability to run parallel phases, to branch, and to loop back and rerun steps, SequenceManager removes the barriers in achieving effective batch within the controller.Sequence ExecutionProcedural sequences are executed through nativefunctions in the controller. With an integrated ISA-88 state model, the control and states of phases can be assured. Standard batch functionality, such as manual control and active step changes, are included to give the operational flexibility that is needed to respond toabnormal process conditions.Allowing for an Intuitive Batch ApplicationResponsive batch interactions between the controller and equipment, along with intuitive operator interfaces, provide the core of a truly distributed batching strategy that drives ISA-88 procedural models.Allen-Bradley, FactoryTalk Batch, FactoryTalk® View SE, Integrated Architecture, Listen.Think.Solve., PhaseManager, PlantPAx, Rockwell Automation, Rockwell Software, SequenceManager, and Studio 5000 Logix Designer are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.Operator ViewerFactoryTalk® View SE and ActiveX controls monitor and interact with a running procedural sequence through the HMI. Advance ActiveX controls provide an intuitive interface for controlling sequences and changingparameters from the operational environment. Improved capabilities allow the user to perform manual step changes and acquire control easily.Reporting and AnalyticsSequenceManager data generates events that are used to produce batch reports and procedural analysis. A separate event client transfers the event data from the Logixcontroller to a historical database. SequenceManager uses the same data structure and reports as FactoryTalk Batch, which provides a consistent and intuitive batch reporting tool among Rockwell Automation® Batch Solutions.Additional InformationVisit us at /processPublication PROCES-PP001A-EN-E – June 2016Copyright © 2016 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.。
Infoblox ActiveTrust数据表说明说明书
Key Features• Infoblox Threat Insight in the Cloud detects DNS based data exfiltration and newer threats such as DNSMessenger, DGA, and Fast Flux. Threat Insightis the only DDI solution that leverages reputation, signatures and behavioral analytics to detect DNS based data exfiltration• Infoblox DNS Firewall executes administrator-defined policy action (block, redirect device to a walled garden site, and/or log event)to help stop devices anytime, anywhere from communicating with C&Cs or botnets via DNS • Infoblox Threat IntelligenceData Exchange (TIDE) collects and manages curated threat intelligence from internal and external sources in a single platform. It enables security operations to remediatethreats more rapidly by sharing normalized TIDE data in real time with third-party security systems such as Palo Alto Networks, SIEM, etc• Infoblox Dossier is a threat investigation tool that provides immediate threat context and allows threat analysts to save precious time, shortening the attack window for criminals• Integration with Security Ecosystem Integration with third-party security systems extends the unique visibility we have into DNS to other security systems such as Qualys and Carbon Black Security ChallengesInternet communications, including malware, rely on DNS. Attackers are taking advantage of DNS as a data-exfiltration and malware control point. Over 91 percent of malware uses DNS for data exfiltration and to communicate with C&C servers or redirect traffic to malicious sites. Existing security controls such as firewalls, email proxies, and web proxies rarely focus on DNS and associated threats.Using unverified threat data residing in silos in your cybersecurity infrastructure is like trying to pick out instruments in an orchestra that is playing outdoors in the midst of rush-hour traffic. The noise blocks out everything you really want to hear. Low-quality data creates nuisance red flags that threat analysts still must track down. They can easily be swamped by false-positives, leaving them unable to detect and prevent genuine threats.T o research information and gather context about threats, analysts must go to multiple tools. The process is manual and time consuming, which slows response and often requires high levels of expertise. In addition, they often lack a centralized tool for threat investigation that aggregates threat and indicator data from multiple sources and quickly shares context.The Infoblox SolutionIntercepting DNS traffic is an ideal approach to counter DNS-based data exfiltration and malware communications with C&C sites. In addition, it is an ideal approach for devices on which endpoint agent software cannot be deployed (e.g. POS, medical equipment, certain IoT devices, etc.). ActiveT rust is a highly efficient, scalable solution that offers:Infoblox DNS Firewall for prevention of malware communications with C&C sites and botnetsIn foblox Threat Insight in the Cloud prevents (with DNS firewall) DNS-based data exfiltrationby uniquely leveraging reputation, signatures, and behavioral analytics. It is also able to block (using DNS firewall) newer threats such as DNSMessenger, DGA, and Fast Flux. Threat Insightin the Cloud is offered as a service to scale in the cloud and is bundled with ActiveTrust Plus and ActiveT rust Advanced.SummaryInfoblox ActiveT rust® proactively detects and prevents cyberthreats. ActiveT rust bundles Infoblox DNS Firewall, InfoBlox Threat Insight in the Cloud, Infoblox Threat Intelligence Data Exchange (TIDE), and Infoblox Dossier. The solution prevents data exfiltration and malware command-and-control (C&C) communications via DNS, centrally aggregates curated internal and external threat intelligence, distributes validated threat data to the customer’s security ecosystem for remediation, and enables rapid investigation to identify context and prioritize threats.ActiveTrust Standard ActiveTrust Plus ActiveTrust AdvancedAnnual SubscriptionLicensed by Appliance by model Organization-wide by number ofprotected usersOrganization-wide by number ofprotected usersInfoblox DNS Firewall Zones(RPZs)Standard (4)Standard (4) + Advanced (7) +SURBL (2)Standard (4) + Advanced (13) +SURBL (2)Infoblox Threat Insight inthe Cloud Not available Included IncludedInfoblox Data via ThreatIntelligence Data Exchange Not available One of:* Hostnames* IP Addresses* URLsAll of:R HostnamesR IP AddressesR URLsInfoblox Dossier No (threat lookup via CloudServices Portal only)32,000 queries/year(supports 2 analysts)65,000 queries/year(supports 4 analysts)Third-party Data viaInfoblox Threat IntelligenceData Exchange (TIDE)Not available Available a la carte Available a la carteHardware Requirements If you intend to use Infoblox DNS Firewall for RPZ-based policy enforcement, you need to buy:One or more Infoblox T rinzic (physical) or vNIOS (virtual) appliances with DNS with recursion enabled. Trinzic models:IB Series: IB-800, IB-1400, IB-2200, IB-4000, and IB-4030PT Series: PT-1400/1405, PT-2200/2205, and PT-4000TE Series (physical and virtual appliances): TE-100, TE-810/815/820/825, TE-1410/1415/1420/1425, TE-2210/2215/2220/2225, and TR-4010/TR-4010-10GESoftware Requirements • If you want Threat Insight in the Cloud, then you can purchase either ActiveTrust Plus or ActiveTrust Advanced license. If you will NOT deploy ActiveT rust threat intelligence data on third-party infrastructure, then buy an ActiveT rust Standard license, which is based on the T rinzic appliance models.• If you intend to deploy ActiveT rust threat intelligence data on third-party infrastructure (e.g. next-generationfi rewall, SIEM, Web proxy), then you can buy either ActiveT rust Plus or ActiveTrust Advanced license. The license is based on total number of protected users’ organization-wide (Grid-wide license). The two products vary based on the amount of data sets that can be applied and total number of annual Dossier threat indica-tor queries that can be transacted.Infoblox Threat Intelligence Data Exchange (TIDE) leverages highly accurate machine-readable threat intelligence (MRTI) datato aggregate and selectively distribute data across a broad range of security infrastructure. Our threat intelligence team curates, normalizes, and refines the high-quality threat data to minimize false positives. Our threat feeds begin with information gained from native investigations and harvesting techniques. We then combine them with verified and observed data from trusted partners including government agencies, academic institutions, several premier Internet infrastructure providers, and law enforcement. The end result is a highly refined feed with a very low historical false-positive rate.Infoblox Dossier threat indicator investigation provides rich threat context to prioritize incidents and respond quickly.Optional Services • Infoblox Threat Insight (on premises) for protection against DNS tunneling and sophisticated data ex fi ltration techniques is available as a separate standalone option for purchase for all AT customers.-Note: this only works on the following Infoblox models: PT-1405, TE-1415/V1415, TE-1425/V1425,TE-2210/v2210, 2215/v2215, TE-2220/v2220, 2225/v2225, PT-2200, PT-2205, IB-4010/v4010, V4015,TE-V4010/V4015, PT-4000, IB-4030-DCAGRID-AC/DC, IB-4030-DCAGRID-T1-AC/DC, IB-4030-DCA-GRID-T2-AC/DC, and IB-4030-DCAGRID-T3-AC/DC.• Infoblox Security Ecosystem license enables integration of Infoblox DNS RPZ/Firewall with third-party security systems: FireEye, Qualys and threat intelligence platforms.• Infoblox Dossier (portal, 65,700 queries package) 1-year subscription-ActiveTrust Standard customers can purchase if they want to perform threat investigation, since Dossier is not bundled with ActiveTrust Standard.-ActiveTrust Plus and ActiveT rust Advanced customers that need additional queries beyond what is provid-ed in the base product can also purchase this:-Third-party marketplace threat feeds-Prerequisite: ActiveTrust Plus or ActiveT rust Advanced must be purchased in order for customers topurchase and subscribe to one or more 3rd party marketplace threat feeds-Does NOT Include Maintenance/Support• Infoblox Reporting and Analytics (appliance) – provides rich reporting on Infoblox DNS Firewall (top RPZ hits, top malicious hostnames, users)Note: The SURBL (an Infoblox premium threat intelligence data partner) OEM license is bundled with the ActiveT rust Plus and ActiveT rust Advanced bundles for use by Infoblox DNS Firewall. The Infoblox ActiveT rust and SURBL data sets (Multi-domain and Multi Lite domain) are complementaryand if used together, can enable increased threat coverage. T o learn more about the Infoblox threat intelligence data, please refer to the solution note “Overview of Infoblox Threat Intelligence for ActiveT rust” on the Infoblox website.Key BenefitsWith Infoblox ActiveT rust, you get actionable network intelligence with flexible threat intelligence integrated into your DDI enthronement. this enables you to proactively detect, investigate, prioritize, remediate, and prevent cyber threats.Prevent DNS-based Data exfiltration at Scale in the CloudWith Threat Insight in the Cloud, you can detect and block (with DNS Firewall) DNS-based data exfiltration using a combination of reputation, signature, and behavioral analysis.Detect and Block DNSMessenger, DGA, and Fast FluxOffered as a service, Threat Insight in the Cloud can also detect and block (with DNS Firewall) new threats such as DNSMessenger, DGA, and Fast Flux.Stop DNS-based Malware C&C/botnet CommunicationsWith Infoblox DNS Firewall, you gain proactive network protection against fast-evolving, elusive malware threats that exploit DNS to communicate with C&C sites.Collect and Manage Curated Threat Intelligence from Internal and External Sources in a Single PlatformInfoblox TIDE enables you to aggregate, normalize, and manage internal and multiple third-party threat intelligence data in a single location, preventing siloed and disjointed threat intel.Improve Security Posture by Sharing Curated Threat Intelligence Data in Real Time with Security EcosystemsCreating custom API data feeds built for specific use cases is quick and easy. Combine threat data from all your sources, use contextual metadata to select the relevant subset, and leverage the right format such as JSON, STIX, CSV, CEF, and RPZ to RPZto improve the security posture and situational awareness of your existing security ecosystem, such as NGFW, IPS, web proxy,and SIEM.Extend the Unique Visibility Infoblox Provides into DNS such as Indicators of Compromise (IoCs) to Other Security Systems Infoblox provides the unique visibility into DNS data as the market-leading vendor of DDI that other vendors cannot match. DNS data such as indicators of compromise (IoC) can be shared with other security systems such as vulnerability scanners (Qualys and Rapid7) to kick off a scan when a new device comes on the network to determine whether it is malware infected.Expedite Threat Investigation to Free Up Security Personnel and Provide Timely Access to Context for Threat Indicators Use the Infoblox Dossier research tool as a single source of truth to rapidly understand the types of threats happening on your network, where they are coming from, and the risks they pose to your organization, including understanding the data source, threat severity, and priority. Gain insight into questionable activities related to inbound or outbound network communications. Furthermore, quickly learn about and understand what a variety of trusted sources report about the indicator in question to improve the operational efficiency of scarce security operations resources, saving you time and effort.About InfobloxInfoblox delivers Actionable Network Intelligence to enterprises, government agencies, and service providers around the world. As the industry leader in DNS, DHCP, and IP address management (DDI), Infoblox provides control and security from the core—empowering thousands of organizations to increase efficiency and visibility, reduce risk, and improve customer experience.Corporate Headquarters: +1.408.986.4000 1.866.463.6256(toll-free,U.S.andCanada)********************。
智慧图书馆建设标准探析
DOI:10.13530/ki.jlis.2021002智慧图书馆建设标准探析”卢小宾宋姬芳蒋玲洪先锋刘静张藕摘要“智慧图书馆”理念于2003年被首次提出,代表一种不受空间限制、可感知的移动图书馆服务,旨在帮助用户快速便捷地找到所需要的文献信息资源。
目前,智慧图书馆的建设尚处于探索阶段,构建科学、合理、完备的标准体系对智慧图书馆的健康发展至关重要。
本文从智慧图书馆的资源建设、服务模式和技术应用等核心要素入手,对比分析国内外已有的图书馆建设相关标准,探索我国智慧图书馆建设标准的选采策略,提出我国智慧图书馆建设标准体系的构建对策:①重视多维度标准体系构建,保障智慧图书馆建设行稳致远;②注重与现有标准体系的融合,适应国家政策要求与行业发展变化;③深化标准制定领域的国际合作,提升我国智慧图书馆相关标准的话语权;④推动制定主体多元化,提升智慧图书馆标准体系的科学性与完备性。
表70参考文献39。
关键词图书馆智慧图书馆建设标准标准体系分类号G250.1Study on the Construction Standards of Smart LibraryLU Xiaobin,SONG JifangJIANG Ling,HONG Xianfeng,LIU Jing&ZHANG RuABSTRACTThe concept"smart library"was first put forward in2003.It refers to a perceptible mobile library service which is not limited by space and helps users find the information resources conveniently.The construction of smart libraries is still in its exploratory stage.Current research mainly focuses on the definition,characteristics,content and functions,while the fact that there is less discussion on the construction standards of smart libraries delays the implementation and development to a certain extent. Therefore,it is significant to create a scientific,reasonable and complete standard system for the sound development of smart libraries.This article begins with the discussion of the core elements such as resource construction,service mode and technology application of smart libraries,compares and analyzes the relevant standards of smart library construction at home and abroad,and then explores the strategies of deciding on the corresponding construction standards of smart libraries in China:1)In smart transformation,the standards of resource construction of Chinese libraries should draw on achievements abroad.To conform to actual conditions in China,the standard system of smart libraries should be built on the construction of core collection,physical digitization,a resource sharing cooperation network,*本文系教育部学校规划建设发展中心委托项目“雄安大学数字图书馆建设策略研究”的研究成果之一。
operating system《操作系统》ch11-file system implementation-50
I/O Using a Unified Buffer Cache
11.32
11.7 Recovery
Consistency checking – compares data in directory structure with data blocks on disk, and tries to fix inconsistencies
Brings all pointers together into the index block. Logical view.
index table
11.20
Example of Indexed Allocation
11.21
Indexed Allocation (Cont.)
Need index table Random access Dynamic access without external fragmentation, but
Efficiency dependent on:
disk allocation and directory algorithms types of data kept in file’s directory entry
Performance
disk cache – separate section of main memory for frequently used blocks
File-allocation table (FAT) – disk-space allocation used by MS-DOS and OS/2.
11.17
Linked Allocation
11.18
File-Allocation Table
Oracle Autonomous Health Framework (AHF) 概述说明书
Oracle Database Autonomous Health FrameworkFrequently Asked QuestionsQ:What is Oracle Autonomous Health Framework (AHF)?A:Oracle Autonomous Health Framework (AHF) presents the next generation of tools as components, which work together autonomously 24x7 to keep database systems healthy and running while minimizing human reaction time.Utilizing machine-learning technologies, Oracle AHF provides early warning or automatically solves operational runtime issues faced by Database and System administrators in the areas of availability and performance.Q:What is autonomous in Oracle Autonomous Health Framework (AHF)?A:Autonomous in Oracle Autonomous Health Framework refers to the fact that the components in the framework require miminal human intervention to do their work. They run 24x7 in their daemon mode to resolve the operational runtime issues in the database system in the space of availability and performance. These components of Oracle AHF include Cluster Health Monitor (CHM), ORAchk, Cluster Verification Utility (CVU), Cluster Health Advisor (CHA), Trace File Analyzer (TFA), Quality of Service Management (QoSM), Hang Manager, and Memory Guard.Q:What kind of Availability issues can be resolved with Oracle Autonomous Health Framework (Oracle AHF)?A:Oracle AHF resolves runtime issues that threaten the availability of the software stack either through a software issue (DB, GI, OS) that can cause the database or one of its instances to become unresponsive, or the issues with the underlying hardware resources (CPU, Memory, Network, Storage) that can cause a server to be evicted from the cluster and shut down all the database instances running there.Q:What kind of Performance issues can be resolved with Oracle Autonomous Health Framework (Oracle AHF)?A:Oracle AHF resolves the runtime issues that threaten the performance of the system as seen by the database client or application either due to software issues (bugs,configuration, contention, etc.), or client issues (demand, query types, connection management, etc).Q:What are the different components in Oracle Autonomous Health Framework?A:Oracle Autonomous Health Framework consists of both new components such as Cluster Health Advisor and Hang Manager and already existing tools as components that run in daemon mode such as ORAchk, Cluster Verification Utility, Cluster Health Monitor, Cluster Trace File Analyzer, Quality of Service Management, and Memory Guard.These components work 24x7 autonomously (in daemon mode) to address performance and availability issues.Q:How does Oracle Autonomous Health Framework (Oracle AHF) resolve availability and performance issues?A:Oracle AHF components work 24x7 in daemon mode to address the availability and performance issues, and ensure high availability for the database system. They collaborate with each other to provide a framework that continuously monitors the database system, maintains best practice configurations, and alerts about vulnerability to known issues. It monitors performance of the database system autonomously and manages resources to maintain SLAs. It also preserves resource availability during common situations of memory stress and resources being blocked by hung sessions. Oracle AHF uses machine learning to even discover potential cluster and database problems, and notifies with corrective actions to prevent the issues altogether. And finally, for the issues that are hard to detect and require Oracle Support, Oracle AHF speeds the issue diagnosis, triage and resolution process.Q:Is Oracle Autonomous Health Framework integrated with Enterprise Manager?A:Currently, Oracle AHF components - Cluster Health Monitor (CHM), Quality of Service Management (QoSM), ORAchk and Cluster Health Advisor (CHA) are integrated with Enterprise Manager. Hang Manager and Memory Guard use EMCC to send alert notifications.Q:Where can I see the output for checks performed by Cluster Verification Utility (CVU)?A:Users can access the results of CVU checks through its generated report in text or HTML file format. These reports can also be saved for later reference.Q:Hang Manager resolves hangs autonomously. How do I know if a session is being terminated in the process?A:Hang Manager detects and resolves hangs autonomously.However, it continuously logs all detections and resolutions in DB Alert Logs. So, if a session is terminated, it will belogged in these alert logs. The details of complete hangresolution are also available in dump trace files.Q:Where can I find details of actions performed by Memory Guard to relieve memory stress?A:Even though Memory Guard works autonomously, actions performed by it are logged in the audit logsunder $ORACLE_BASE/crsdata/nodename/qos/logs/dbwlm/auditing.Q:Is Oracle Autonomous Health Framework a Real Application Clusters -only feature?A:Oracle Autonomous Health Framework compoents Cluster Health Advisor, and Quality of Service Management require Oracle Real Application Clusters database deployments.However, other components of Oracle Autonomous Health Framework, Memory Guard, ORAchk, Cluster Verification Utility, Cluster Health Monitor, Hang Manager, and Trace File Analyzer do not.Q:Is Oracle Autonomous Health Framework a 12.2-only feature?A:Oracle Autonomous Health Framework as a framework is a12.2 only feature. However, Oracle Autonomous HealthFramework components, Cluster Verification Utility, ORAchk, and Trace File Analyzer, have been in existence even before 12.2 in non-daemon mode. In Oracle Autonomous Health Framework, they have now been launched in their daemon mode where the components work together with other AHF ones to resolve operational runtime issues related to availability and performance in the database system.Q:What is Cluster Health Advisor?Oracle Autonomous Health Framework component Cluster Health Advisor (CHA) uses machine learning to provide system and database administrators with early warning of pending performance issues, and root causes and corrective actions for Oracle RAC databases and cluster nodes. It also sends warning messages generated to Enterprise Manager Cloud Control. When Grid Infrastructure (GI) is installed for RAC or RAC One Node database, Cluster Health Advisor is automatically enabled by default. Q:Most of the components in Oracle Autonomous Health Framework are the tools that I already use. How is Oracle Autonomous Health Framework different?A:Even though components of Oracle Autonomous Health Framework already exist, their value in Oracle AHF comes from the fact that they run 24x7 in daemon mode working together to resolve runtime issues related to performance and availability in the database systems.Q:What is Collections Manager in Oracle Autonomous Health Framework?A:Collection Manager in Oracle Autonomous Health Framework is an Apex application that provides a single view of the health of all the clusters in the database system and helps to identify the availability and performance issues related to best practices and compliance. Each time ORAchk performs its checks, the output (collection) is uploaded into the Collection Manager database. Collection Manager aggregates the data from these collections to display the database system health. With Collection Manager, the user can browse either an individual collection to understand the system health at a give time, compare two collections to assess the change in health of the system over time, or browse multiple collections at a time based on various parameters such as platform, DB version, etc.Q:How does Hang Manager resolve hangs?A:Hang Manager autonomously detects and resolves hangs.A hang occurs when a chain of one or more sessions isblocked by another session and are not able to make any progress. Usually, these chains of sessions have a root ora final blocker session which blocks all the other sessionsin the chain called the victim session. Once a victim session is selected, Hang Manager applies hang resolution heuristics on the victim. If the chain of sessions or the hang resolves itself automatically, then Hang Manager does not take any action. However, if the hang does not resolve itself, then Hang Manager may resolve the hang by terminating the victim session or if that is unsuccessful, then terminating the process.Q:Where can I find more information about Oracle Autonomous Health Framework?Information on Oracle Autonomous Health Framework isavailable on OracleTechNetwork:/goto/ahf2 | Oracle Autonomous Health Famework FAQ3 | Oracle Autonomous Health Famework FAQOracle Autonomous Health Framework also has its own user guide which can be referred to at:/database/122/ATNMS/toc.htm Q: Do I need a separate license for Oracle AutonomousHealth Framework?Oracle Autonomous Health Framework consists of multiple components. Oracle Autonomous Health Framework compoents Cluster Health Advisor and Quality of Service Management, require an Oracle RAC license. However, the other components, Cluster Health Monitor, Cluster Verification Utility, ORAchk, Trace File Analyzer, Memory Guard, and Hang Manager do not. Please follow this link to the license guide for more information:/database/122/DBLIC/toc.htmOracle Corporation, World Headquarters 500 Oracle ParkwayRedwood Shores, CA 94065, USACO N N E C T W I T H U S /blogs /oracle /oracle 。
税收支付系统接口用户指南说明书
Tax Payment System Interface User Guide Oracle FLEXCUBE Universal Banking Release 12.2.0.0.0Part No. E74659-01May 2016Tax Payment System Interface User GuideOracle Financial Services Software LimitedOracle ParkOff Western Express HighwayGoregaon (East)Mumbai, Maharashtra 400 063IndiaWorldwide Inquiries:Phone: +91 22 6718 3000Fax: +91 22 6718 3001/financialservices/Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.Contents1. Preface ......................................................................................................1-11.1 Introduction..............................................................................................................1-11.2 Audience..................................................................................................................1-1Accessibility.................................................................................... 1-11.3 Documentation1.4 Organization............................................................................................................1-11.5 Acronyms and Abbreviations................................................................................... 1-21.6 Organization............................................................................................................1-21.7 Glossary of Icons..................................................................................................... 1-21.8 Related Documents................................................................................................. 1-22. Oracle FLEXCUBE – Tax Payment Interface .........................................2-12.1 Details for Tax Payment Interface........................................................................... 2-12.1.1 Maintaining Interface Parameterization...................................................... 2-1Files......................................................................................................... 2-22.2 Incoming2.2.1 Incoming File Format.................................................................................. 2-22.3 Customer Tax Payment Report............................................................................... 2-32.3.1 Contents of the Report............................................................................... 2-33. Function ID Glossary ...............................................................................3-11. Preface 1.1 IntroductionThis manual is designed to help acquaint you with the interface between Oracle FLEXCUBE and Tax Payment System.This manual provides you extensive explanations about the maintenances and processing with respect to the interface. Besides this User Manual, while maintaining the details, you can invoke the context sensitive help available for each field. This help encapsulates the purpose of each field within a screen. Placing the cursor on the relevant field and striking the <F1> key on the keyboard can obtain information specific to a particular field. 1.2 AudienceThis manual is intended for the following User/User Roles:1.3 Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at /pls/topic/lookup?ctx=acc&id=docacc.1.4 OrganizationThis manual is organized as follows:RoleFunction Back office data entry ClerksInput functions for maintenances Back office Managers/Officers Authorization functions ChapterDescription Chapter 1About this Manual gives information on the intended audience. Italso lists the various chapters covered in this User Manual.Chapter 2Oracle FLEXCUBE – Tax Payment Interface helps you understandthe interfaced Tax Payment System for exchange of the tax paymentdetails of customers.Chapter 3Function ID Glossary has alphabetical listing of Function/Screen ID'sused in the module with page references for quick navigation.1.5 Acronyms and Abbreviations 1.6 OrganizationThis document talks about the required maintenance and further processing of data transfer between Oracle FLEXCUBE and FGL. This includes the following:● Processing Incoming Files● Generating Customer Tax Payment Report● Screen Glossary1.7 Glossary of IconsThis User Manual may refer to all or some of the following icons.1.8 Related DocumentsYou can refer to the following documents:● XML Interface Document● Procedures User Manual● Oracle FLEXCUBE Generic Interface User Manual AbbreviationDescription System Unless and otherwise specified, it shall always refer to OracleFLEXCUBE systemIcons FunctionExitAdd rowDelete rowOption List2. Oracle FLEXCUBE – Tax Payment InterfaceOracle FLEXCUBE interfaces with the Tax Payment System for exchange of the tax paymentdetails of customers. This interface also helps you view the reports related to customers’ taxpayments.This chapter contains the following sections:● Section 2.1, "Details for Tax Payment Interface"● Section 2.2, "Incoming Files"● Section 2.3, "Customer Tax Payment Report"2.1 Details for Tax Payment InterfaceThis section contains the following topic:● Section 2.1.1, "Maintaining Interface Parameterization"The following are maintained for Tax Payment interface, internally:● Details of External System (EXTSTPS)● Details of the Interface● Interface Parameterization.For further details on maintaining external system and interface, refer to the Oracle FLEXCUBE Generic Interface user manual.ParameterizationInterface2.1.1 MaintainingFor tax payment interface, you need to maintain the interface parameterization details. Toinvoke the ‘Interface Parameterization’ screen, type ‘IFDPARAM’ in the field at the top rightcorner of the Application toolbar and click the adjoining arrow button.Specify the following details:Interface CodeSelect the interface code from the adjoining option list. This list displays all interface codesmaintained in the system.Parameter NameSpecify a unique parameter name for the interface upload.Parameter ValueSpecify the default values assigned for every unique parameter name and interface code.Account DescriptionSpecify the description of the selected parameter is here.Files2.2 IncomingOracle FLEXCUBE picks up the file containing the tax payment details of customers from theintermediate data store. This file contains the following information:● Customer account number● Tax amountThe system further debits the tax amount from the customer account and credits the'SIMPATI' GL.The system will not process if the records are empty or does not contain mandatory fields.Before passing the accounting entries, the system checks whether sufficient balance isavailable in the account. In case of insufficient balance, the transaction is rejected.This section contains the following topic:● Section 2.2.1, "Incoming File Format"2.2.1 Incoming File FormatThe file format is given below:Attribute Name Attribute ValueInterface Type IncomingFrom System EXTSTPSTo System FLEXCUBETo be ConfirmedDirectory Loca-tionFile Name TxPmt$Y$M$D$H$M$S.txtFrequency DailyCharacter Set ASCIIFile Header NoFile Footer NoDelimiter |Record Length VariableFormat Line Sequential, Variable Length Records2.3 Customer Tax Payment ReportYou can generate and view customer tax payment reports using ‘Customer Tax Payment’ screen. To invoke the screen, type ‘IFRTXPM’ in the field at the top right corner of theApplication toolbar and click the adjoining arrow button. To generate the report, you need to specify the following details:Branch CodeThe system displays the branch code.Account NumberSpecify the account number for which you need to generate the tax payment report. Assessment YearSpecify the assessment year. The tax payment report will contain the details of payment of tax during the assessment year specified here.From DateYou need to indicate period. Specify the start date of the tax payment report period here. The system will generate the report for the period from this date.To DateYou need to indicate period. Specify the end date of the tax payment report period here. The system will generate the report for the period from the start date until this date.Once you have captured the details, click ‘Ok’ button. The system generates and displays the tax payment report for the selected account and period.2.3.1 Contents of the ReportThe tax payment report contains the following details:End of theRecordCR/LF Numeric paddingNo Text padding No● Report name● Branch code● Assessment year● Period● Source● Customer number● Account number● Taxable amount● Paid amount● Payment date● Tax reference number3. Function ID GlossaryIIFDPARAM........................2-1IFRTXPM..........................2-3。
LabVIEW 8.6 Datalogging and Supervisory Control Mo
RELEASE AND UPGRADE NOTESLabVIEW Datalogging and™Supervisory Control ModuleVersion 8.6This document describes the system requirements and the process ofinstalling the LabVIEW8.6 Datalogging and Supervisory Control (DSC)Module and the DSC Module8.6 Run-Time System. This document alsodescribes the new features available with version8.6 and compatibility andupgrade issues you might encounter when you use version8.6.To upgrade the DSC Module from 7.x or earlier, refer to the LabVIEW8.2Datalogging and Supervisory Control Module Release and Upgrade Notes.The Upgrading from the LabVIEW DSC Module7.x section providesimportant information for upgrade users. Refer to the National InstrumentsWeb site at /info and enter the info code dsc820 to access theLabVIEW8.2 Datalogging and Supervisory Control Module Release andUpgrade Notes.Refer to the Getting Started with the LabVIEW Datalogging andSupervisory Control Module manual for exercises you can complete tofamiliarize yourself with the DSC Module.ContentsSystem Requirements (2)Installation Instructions (2)Activating the LabVIEW License (Windows) (3)Evaluating LabVIEW, Modules, or Toolkits (4)Single-Seat and Multi-Seat Licensing (4)New Features in the DSC Module8.6 (4)Enhancements to the NI Distributed System Manager (5)New Example VIs (5)Performance Improvements (5)Compatibility Issues (5)Considerations for the DSC Module Run-Time System (6)Known Issues (6)System RequirementsTo use the DSC Module, your computer must meet the following minimumsystem requirements:•Windows Vista, Windows XP Service Pack 2, or Windows 2000Service Pack 4.•800MB free disk space.•512MB of RAM. National Instruments recommends 1GB of RAM.•LabVIEW8.6 Base, Full, or Professional Development System. Referto the LabVIEW Release Notes for the LabVIEW system requirements.The DSC Module does not support Windows NT/Me/98/95/Server2003. Installation InstructionsRefer to /support if you encounter errors during installation.You can install the DSC Module8.6 by using the LabVIEW PlatformDVDs or the CDs.The LabVIEW Platform DVDs contain LabVIEW, the DSC Module, otheradd-ons, and device drivers. You can install and activate both LabVIEWand the DSC Module by using the LabVIEW Platform DVDs. If youinstalled LabVIEW, the DSC Module, and the appropriate NI device driversfrom the LabVIEW8.6 Platform DVD, you do not need to reinstall usingthe CDs described in this section. Refer to the LabVIEW Release Notes formore information about installing the LabVIEW development system.The CDs contain the DSC Module only. Complete the following steps toinstall the DSC Module from the CD.1.Log in to the development computer as an administrator or as a userwith administrative privileges.2.Install LabVIEW8.6 from the LabVIEW8.6 installation CD. Referto the LabVIEW Release Notes for information about installing theLabVIEW development system.3.Install the DSC Module from the LabVIEW8.6 DSC Moduleinstallation CD. Follow the instructions that appear on the screen.4.Follow the directions on the screen to activate your DSC Module.Refer to the Activating the LabVIEW License (Windows) section ofthis document for more information about activating LabVIEW.5.Restart the computer.The DSC Module installs program files, documentation, and examples. LabVIEW DSC Module Release and Upgrade © National Instruments Corporation 3LabVIEW DSC Module Release and Upgrade Notes Note By default, the NI Keyboard Filter Driver is not installed. The NI Keyboard Filter Driver activates special security features, including the ability to restrict users fromswitching between applications by pressing the <Alt-Tab> keys. This driver does not work on laptop computers or on computers with hibernation enabled.Activating the LabVIEW License (Windows)Note (Mac OS and Linux) LabVIEW does not require activation.National Instruments uses activation to better support evaluation of oursoftware, to enable additional software features, and to support licensemanagement in large organizations. To find out more about NationalInstruments software licensing, visit /activate to find frequentlyasked questions, resources, and technical support.You can activate licenses you have purchased for LabVIEW, modules, andtoolkits during installation. If you do not activate a valid license forLabVIEW or any modules or toolkits that you install, the unlicensedproduct operates in evaluation mode. After you install the product, theevaluation begins the first time you launch the product and lasts30consecutive days. When the evaluation period expires, you must activatea valid license to continue using the product.To activate the product license, use the serial number you received on theCertificate of Ownership included in the software kit. If your software kitdoes not include a Certificate of Ownership, you can find the serial numberon the product packing slip or on the shipping label. You can activate theLabVIEW license in any of the following ways:•During installation, enter the serial number when prompted and complete the installation and activation process.•After you launch LabVIEW in evaluation mode, click the Activate Products button in the LabVIEW dialog box.•Select Help»Activate LabVIEW Components while LabVIEW isrunning in evaluation mode or select Start»All Programs»National Instruments»NI License Manager to launch NI LicenseManager. The license activation does not take effect until you restartLabVIEW.If you do not activate LabVIEW, modules, or toolkits during installation,LabVIEW prompts you for activation when you launch LabVIEW. Afteryou activate the licenses for all LabVIEW products you installed, you nolonger see this prompt.Evaluating LabVIEW, Modules, or ToolkitsYou can access all the tools, VIs and functions, help, and examplesavailable to the LabVIEW Professional Development System and mostmodules or toolkits in a free 30-day evaluation mode.After the evaluation period for a module or toolkit expires, you are nolonger able to perform the following actions:•Run VIs that use VIs from the module or toolkit.•Run VIs from the module or toolkit.•Build VIs that use VIs from the module or toolkit into an executable orshared library.•Access menus, tools, or palettes installed by the module or toolkit.When you install a module or toolkit for evaluation, you install the help forthe module or toolkit. The help for the module or toolkit remains installedafter the 30-day evaluation period. Also, the NI Example Finder displaysall module or toolkit examples after the 30-day evaluation period. You mustuninstall the module or toolkit to remove the help and examples.If you run LabVIEW in evaluation mode, you receive functionality of theProfessional Development System. If you then purchase and activate aLabVIEW license, you receive full functionality of the development systemyou purchase. For example, if you create a VI using tools and subVIs thatare only available in the Professional Development System and then youpurchase and activate the Full Development System, the VI you createdusing Professional Development System features will be broken.Single-Seat and Multi-Seat LicensingLabVIEW supports both single-seat and multi-seat licenses. Single-seatlicensing is the use of LabVIEW on up to three computers but by onlyone user. Multi-seat, or volume, licensing is the use of LabVIEW onseveral computers or by several users. Each seat using LabVIEW musthave a valid license from a license server. Refer to the National InstrumentsWeb site at /license for more information.New Features in the DSC Module8.6The following sections describe the new features in the DSC Module8.6.Refer to the LabVIEW Help, available by selecting Help»Search theLabVIEW Help, for more information about using these new features. LabVIEW DSC Module Release and Upgrade Enhancements to the NI Distributed System ManagerUse the NI Distributed System Manager to create and monitor sharedvariables, network variables, processes, and I/O servers. You also can usethe System Manager to manage security and aliases. In LabVIEW, selectTools»Distributed System Manager to launch the System Manager.The DSC Module adds the following features to the System Manager:•Configuring alarms by using the Auto View and Probe views.•Monitoring alarms and events by using the Alarms and Events views.•Acknowledging alarms and events by using the Alarms and Eventsviews.New Example VIsThe DSC Module provides the following two new example VIs:•Boiler—This example simulates a boiler HMI monitoring station.•HVAC—This example simulates a heating and ventilation airconditioning (HV AC) system.Use the NI Example Finder, available by selecting Help»Find Examples,to launch these and other example VIs.Performance ImprovementsLabVIEW8.6 improves the edit-time and run-time performance of sharedvariables. LabVIEW also improves the launching performance androbustness of the Shared Variable Properties dialog box. The DSCModule8.6 takes advantage of these improvements. Compatibility IssuesIf you open a VI saved in the DSC Module8.2 or earlier, the VI might bebroken if the VI contains an indicator, constant, or control created from theshared variable value change notification output of the following VIs:•Cancel Value Change Notifications VI•Enable Value Change Notifications VI•Request Value Change Notifications VITo fix the broken VI, delete the indicator, constant, or control. Then createa new indicator, constant, or control from the shared variable valuechange notification output and wire it to the appropriate parameter.© National Instruments Corporation5LabVIEW DSC Module Release and Upgrade NotesConsiderations for the DSC Module Run-Time SystemTo run applications built with LabVIEW, the DSC Module, and theLabVIEW Application Builder on a computer without the DSC Moduleinstalled, you must install the DSC Module Run-Time System on thatcomputer. The DSC Module Run-Time System contains components thatenable the DSC features in the built applications.To use the DSC Module Run-Time System, a computer must meet thefollowing minimum system requirements:•Windows Vista, Windows XP Service Pack 2, or Windows 2000Service Pack 4.•700MB free disk space.•512MB of RAM.Complete the following steps to install the DSC Module Run-Time System.1.Log in to the computer as an administrator or as a user withadministrative privileges.2.Install the DSC Module8.6 Run-Time System from the LabVIEW8.6Platform DVDs or LabVIEW8.6 DSC Module Run-Time Systeminstallation CD.3.Follow the instructions that appear on the screen.4.Restart the computer.Known IssuesRefer to the readme_DSC.html file, available by selecting Start»AllPrograms»National Instruments»LabVIEW8.6»Readme or on theDSC Module installation media, for information about known issues withthe DSC Module.Refer to the readme_DSC_RTS.html file, available by selecting Start»AllPrograms»National Instruments»LabVIEW8.6»Readme or on theDSC Module Run-Time System installation media, for information aboutknown issues with the DSC Module Run-Time System.LabVIEW DSC Module Release and Upgrade National Instruments, NI, , and LabVIEW are trademarks of National Instruments Corporation.Refer to the Terms of Use section on /legal for more information about NationalInstruments trademarks. Other product and company names mentioned herein are trademarks or tradenames of their respective companies. For patents covering National Instruments products, refer to theappropriate location: Help»Patents in your software, the patents.txt file on your media, or/patents. Refer to the LabVIEW Help for a listing of the conditions and disclaimers.© 2005–2008 National Instruments Corporation. All rights reserved.374128D-01Jun08。
以XML为基础的心电图管系统XML-based ECG Management System
Vol. 1 No. 2 September, 2006, pp. 115-121以XML為基礎的心電圖管理系統XML-based ECG Management System曾文慶中華大學生物資訊學系ttzeng@.tw蔣家正交通大學電控所博士班財團法人國泰綜合醫院新竹分院m9102045@.tw鄭涵菁中華大學生物資訊學系財團法人為恭紀念醫院急診部m09402031@.tw莊文南中華大學資訊工程學系m09302057@.tw陳朝慶中華大學資訊工程學系m9202059@.tw摘要心電圖(Electrocardiogram, ECG),是醫生用來診斷心臟疾病的最普遍方式。
心電儀輸出的方式一般分為兩種,一為紙本ECG,另一為電腦化的數位檔案。
紙本ECG將心電儀量測所得的心電訊號及相關資訊,列印在一張A4大小規格的紙上。
這是目前最普遍的輸出與存取方式,但不利於資訊交換、資料存取及數據之研究分析。
由於醫療資訊電腦化之需求,大部分的心電儀本身也具有數位化輸出的功能,但是因為商用心電儀一般採用專屬的資料格式,須有專用商業軟體才可使用,這不但增加操作成本,且不同的機型間也無法進行資料交換。
基於上述理由,本研究將商用心電儀產生的數位資料轉換成XML-ECG格式以利於資訊的交換與分析。
本研究與地區醫院合作,收集心電儀的SCP-ECG資料,解碼取得內含資訊及心臟各導程原始電位數據後,轉為符合HL7與FDA標準之XML格式,並開發XML-ECG之資料庫管理系統。
至於ECG波形閱覽及數據分析,本研究以SVG技術開發互動式SVG-ECG,一方面提供臨床醫師熟悉的傳統ECG圖形介面;另一方面,藉由SVG的互動性,提供ECG數據比對與分析之功能。
關鍵字 : 心電圖、心電圖管理系統、SCP-ECG、XML、資料庫Wen-Ching TzengDepartment of Bioinformatics, Chung Hua Universityttzeng@.twChia-Cheng ChiangDepartment of Electrical and Control Engineering, National Chiao Tung UniversityDepartment of Emergency, Cathay General Hospital, Hsinchu Branchm9102045@.twHan-Chin ChengDepartment of Bioinformatics, Chung Hua UniversityEmergency Department, Wei-Gong Memorial Hospital, Maio-Li Countym09402031@.twWen-Nan JuangDepartment of Computer Science and Information Engineering, Chung Hua Universitym09302057@.twChau-Ching ChenDepartment of Computer Science and Information Engineering, Chung Hua Universitym9202059@.twAbstractElectrocardiogram (ECG) is the most commonly used tool for diagnosis of heart-related diseases. In general, there are two types of output forms from commercial electrocardiographs: paper ECG and computerized digital format. In paper ECG, the measured electrocardiac signal and related information are printed on a sheet of A4-size paper. Paper ECG has been widely adopted as the standard output for most of commercial electrocardiographs. However, it is unfavorable for information exchange, information management, and signal analysis. To meet the requirement of hospital information system, most of modern electrocardiographs can also output digital electronic files (e-files). Nevertheless, e-files so generated are encoded in various proprietary formats. This not only increases operation cost, but hinders information exchange among different models.Due to the reasons mentioned above, this study transformed digital data obtained form commercial electrocardiographs into the XML-ECG format so that information in ECG can be conveniently exchanging and analyzed. In this study, we worked with a regional hospital, collected SCP-ECG data from electrocardiographs, and decoded SCP-ECG file to acquire raw data of 12-lead electrocardiac signal and related annotative information. The content of decoded SCP-ECG files was then transformed into the XML format based on HL7 and FDA standards. In addition, a database system for managing the XML-ECG files was developed in this study. As for browsing and analysis of ECG waveform, SVG was used to develop interactive SVG-ECG, not only providing a graphic ECG representation which is widely accepted by clinical physicians, but offering comparison and analysis of ECG data through interactivity of SVG.Keyword:ECG、ECG management system、SCP-ECG、XML、SVG、database1.Introduction自從1924年發明了心電儀,到現今數十年來,由於心電儀非侵入性且快速的特性,所以一直是心臟醫學最重要且常用的診斷工具之一[1]。
WHO_TRS_937__annex6_eng
Guidelines on submission of documentation for a multisource (generic) finished pharmaceutical product: quality part
1. Introduction
1.1 Background 1.2 Objectives 1.3 Scope 1.4 General principles 1.5 Guidance on format
4. Module 3: Quality
4.1 Table of contents of Module 3 4.2 Body of data 3.2.S Drug substance (or active pharmaceutical ingredient (API)) 3.2.P Drug product (or finished pharmaceutical product (FPP)) 3.2.A Appendices 3.2.R Regional information 4.3 Literature references
1
Stringent regulatory authority (SRA): a regulatory authority which is: a member of the International Conference on Harmonisation (ICH) (as specified at ); or an ICH observer, being the European Free Trade Association (EFTA), as represented by Swissmedic, and Health Canada (as may be updated from time to time); or a regulatory authority associated with an ICH member through a legally-binding, mutual recognition agreement including Australia, Iceland, Liechtenstein and Norway (as may be updated from time to time). 319
StorageTek SL150模块化磁带库说明书
STORAGETEK SL150MODULAR TAPE LIBRARYOracle’s StorageTek SL150 modular tape library is the first scalable tape library designed for growing businesses. Built from Oracle software and StorageTek library technology, it delivers an industry-leading combination of ease of use and scalability. Ideal for backup and archival applications, the StorageTek SL150 modular tape library saves both time and money, setting the new standard for entry tape automation.S I M P L E A N D S C A L A B L E D A T AS T O R A G EK E Y F E A T U R E S•Remote management capability and an installation wizard ensure swift installation and ease of use•Scalability from 30 to 450 cartridge slots enables capacity to reach 20 PB, compressed •Expansion modules offer seamless performance and capacity upgradeability•Easy consolidation of multiple libraries with up to eight (8) partitions•Maximize security through library managed encryption with Oracle Key Manager Simplify Tape ManagementThe StorageTek SL150 emphasizes simplicity and reduces costs through exceptional scalability, common storage management tools and do-it-yourself installation and upgrades. The easy-to-use remote browser GUI, built from Oracle software, helps streamline library management and allows you to perform library operations, manage library settings, and proactively monitor the library’s health. Maximize security by enabling library managed encryption, which works with Oracle Key Manager to encrypt tapes and securely manage keys. The platform-independent Oracle Key Manager complies with Federal Information Processing Standards Publications (FIPS PUBS) 140-2 and runs without regard to application, operating platform, or primary storage device.With the StorageTek SL150, simplicity begins with the library installation and continues throughout the life of the product, even as you expand for data growth. The library can initialize in a few steps via the local touchscreen operator panel, and upgrades are easy because they require no tools, complicated cabling, or technical support.Figure 1. StorageTek SL150 modular tape library touchscreen operator panelK E Y B E N E F I T S•Reduce complexity―the tapelibrary is customer installableand upgradable•Reduce costs with low-costscalability, reliability, and entry-level pricing•Enable consolidation of smalltape libraries into one scalabletape libraryFigure 2. Oracle’s StorageTek Tape Analytics software simplifies tape storage management because ittakes a proactive approach to eliminate library, drive, and media errors.For intelligent monitoring of StorageTek tape libraries, StorageTek Tape Analytics software providestape storage customers with access to leading-edge tape monitoring software that goes far beyondexposing a red, yellow, or green indicator. Rather, StorageTek Tape Analytics software providesinsights into hundreds of drive, media, and library health attributes that empower tape storageadministrators to make proactive decisions about their tape environments prior to device failures. Aproactive approach to managing the health of a tape environment improves the performance andreliability of existing tape investments and helps executives make informed decisions about futureexpenditures.Scale EffortlesslyThe StorageTek SL150 modular tape library scales up to 15x, from 30 to 450 slots, withoutconsuming significant time and resources. In addition, it is the only library in the world that auto-discovers new modules via USB. In the entry to midrange market segment, the StorageTek SL150modular tape library offers higher density and lower-cost scaling than comparable products. Higherdensity saves rack space and enables you to store more data in the library. The StorageTek SL150modular tape library’s base module provides up to 540 TB (with StorageTek LTO 9 half-height tapedrives) and each expansion module adds an additional 540 TB of native capacity as your storageneeds grow. With two additional tape drives per expansion module, the StorageTek SL150 alsoallows for increased performance as storage needs grow. The StorageTek SL150 supports aheterogeneous drive environment, so you can seamlessly use the drive types and generations thatmake sense for your access and storage needs – add new LTO generations or drive types as youscale your library. Choose the drive supplier, generation and interface to support your growingbusiness. The StorageTek SL150 currently supports LTO 5, 6, 7, 8 or 9 tape drives.Count Your SavingsThe market-leading scalability of the StorageTek SL150 modular tape library offers an importantcost-saving advantage. Competitive systems require you to transition among three separate anddistinct products in order to grow from an entry to a midrange library. Oracle launched the first library that can address the full breadth of scale from 30 to 450 slots with a single product.As a result, the StorageTek SL150 negates the need to rip and replace smaller, individual products as your storage needs grow. In addition, single-product scalability saves media, drives, servicing, power, cooling, and other management costs. Scalability also allows you to do more with less by consolidating multiple libraries into a single product that is far less expensive than replacing libraries over time. For those who want to consolidate multiple libraries or manage distinct sections of the library, the StorageTek SL150 supports one to eight partitions. Native physical partitioning requires no extra hardware or software and provides great flexibility for users.For more than 40 years, customers have trusted StorageTek reliability and quality. Oracle’s StorageTek SL150 leverages technology and design from the award-winning StorageTek SL500 modular library system, and it provides StorageTek reliability at an entry-level price point. Furthermore, by working with an end-to-end solution provider like Oracle, you can reduce management and service costs.Maximize AvailabilityThe StorageTek SL150 has a CRU serviceability model—meaning it is customer installable and has customer replaceable spares. However, if you do need installation or service assistance, the following offerings are available from Oracle:•Oracle Premier Support provides the complete system support you need to proactively manage your Oracle storage systems. With swift resolution and rapid-response hardware service when problems do arise, you can keep your business information available 24/7.•Oracle Advanced Customer Support provides mission-critical support from a focused support team, proactive guidance to tailor storage systems for optimal performance and increased competitiveness, and preventative monitoring to help you achieve high availability and optimized system performance.For more information about Oracle Premier Support and Oracle Advanced Customer Support, please speak with your Oracle representative or Oracle authorized partner, or visit/support or /acs.StorageTek SL150 Modular Tape Library Specifications2MechanicalBase Module (Minimum Configuration)Expansion Module (Each Module, Modules 2‒14)Height 5.15 in. (130.8 mm), 3U rack space 3.5 in. (88.9 mm), 2U rack spaceDepth36.42 in. (925 mm) 36.42 in. (925 mm)Width18.94 in. (481 mm) 18.94 in. (481 mm)Weight47 lb. (21.5 kg)* 23.1 lb. (10.5 kg)**EnvironmentalTemperature•Operating: +50°F to +104°F (+10°C to +40°C), 20%–80% relative humidity,noncondensing•Nonoperating: –40°F to +140°F (–40°C to +60°C), 10%–95% relative humidity,noncondensingPowerVoltage100 VAC–240 VAC at50 Hz–60 Hz single phase (auto-ranging)Library (operatingmax. continuous—notpeak)1.42 A at 120 V or 0.75 A at 240 V, 614 BTU/hrDrives Drive power consumption varies (refer to individual drive specifications)Regulatory ComplianceElectromagneticcompatibilityFCC (47CFR15 Subpart B) Class A; EN55022 Class A; EN55024; EN61000-3-2; EN61000-3-3; ICES-003 Class A; AS/NZS CISPR22 Class A; VCCI V-3 Class A; KN22 Class A;KN24; CNS13438 Class ASafety UL 60950-1, CAN/CSA 22.2 No. 60950-1-07, EN 60950-1, IEC 60950-1, 60825-1, Class 1Laser Product1 Maximum performance, native: LTO 6—17.25 TB/hr, LTO7, LTO8, LTO9 —32.4 TB/hr (30 drives)2 Maximum capacity, native: LTO 6—1.1 PB, LTO7 – 2.7 PB, LTO8 – 5.4 PB, LTO9 – 8.1 PB (450 cartridges)* Weight includes library with one drive installed and one power supply**Weight is expansion only, no drives or power suppliesC O N T A C T U SFor more information about Oracle’s StorageTek SL150 modular tape library, visit or call+1.800.ORACLE1 to speak to an Oracle representative.C O N N E C T W I T H U S/oracle/oracle/oracleCopyright © 2022, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and thecontents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any otherwarranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability orfitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations areformed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means,electronic or mechanical, for any purpose, without our prior written permission.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license andare trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo aretrademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0618。
基于微服务架构的众包图像数据集标注系统
基于微服务架构的众包图像数据集标注系统①袁晓晨1, 张卫山1, 高绍姝1, 时 斌2, 赵永俊2, 王 冶3, 安云云41(中国石油大学(华东) 计算机科学与技术学院, 青岛 266580)2(青岛海尔空调电子有限公司 电控模块开发部, 青岛 266101)3(解放军9144部队, 青岛 266102)4(国网山东省电力公司 青岛市黄岛区供电公司, 青岛 266500)通讯作者: 张卫山摘 要: 深度学习在图像识别领域凸显出了优势, 而在深度学习图像识别模型训练的准备阶段, 制备图像数据集需要人工将图片上的信息进行标注. 这一准备过程往往需要耗费大量人力成本与时间成本. 为了提升数据制备阶段的工作效率, 从而加速深度学习模型的生成与迭代, 提出了一种基于微服务架构的多人协作众包式图像数据集标注系统. 通过将繁重的标注任务划分为不同的小任务, 使更多的人能够参与并协同完成数据标定. 通过引入对象存储机制并采用微服务架构, 提升了系统性能, 在开发阶段使用了基于Gitlab 的持续集成与持续部署, 实现了系统的快速迭代与部署, 提升了微服务系统在开发过程中的集成效率.关键词: 微服务; Spring Cloud; 持续集成; 持续部署; 图像标注引用格式: 袁晓晨,张卫山,高绍姝,时斌,赵永俊,王冶,安云云.基于微服务架构的众包图像数据集标注系统.计算机系统应用,2021,30(5):83–91./1003-3254/7900.htmlImage Dataset Annotation System in Crowdsourcing Based on Microservice ArchitectureYUAN Xiao-Chen 1, ZHANG Wei-Shan 1, GAO Shao-Shu 1, SHI Bin 2, ZHAO Yong-Jun 2, WANG Ye 3, AN Yun-Yun 41(College of Computer Science and Technology, China University of Petroleum, Qingdao 266580, China)2(Electronic Control Module Development Department, Haier Air Conditioning Electronic Ltd. (Qingdao), Qingdao 266101, China)3(No. 9144 Troops of PLA, Qingdao 266102, China)4(Qingdao Huangdao District Power Supply Company, State Grid Shandong Electric Power Company, Qingdao 266500, China)Abstract : Deep learning has shown visible advantages in the artificial intelligence-based image classification. It usually costs plenty of time on manual information annotation for preparing image datasets. Then this study proposes an online collaborative system for image dataset annotation based on microservice architecture to improve the efficiency of annotating datasets and thus to accelerate the generation and iteration of deep learning models and applications. More users can join for image annotation after the heavy annotation task is divided into smaller ones. Besides, the system performance has been improved by introducing an object storage system and microservice architecture, and the integration efficiency of the system in the development progress has been enhanced by continuous integration and deployment.Key words : microservice; Spring Cloud; continuous integration; continuous deployment; image annotation计算机系统应用 ISSN 1003-3254, CODEN CSAOBNE-mail: Computer Systems & Applications,2021,30(5):83−91 [doi: 10.15888/ki.csa.007900] ©中国科学院软件研究所版权所有.Tel: +86-10-62661041① 基金项目: 国家自然科学基金(62072469); 国家重点科研计划(2018YFE0116700); 山东省自然科学基金(ZR2019MF049); 中央高校基础研究基金(2015020031); 西海岸人工智能技术创新中心建设专项(2019-1-5, 2019-1-6); 上海可信工业控制平台开放项目(TICPSH202003015-ZC)Foundation item: National Natural Science Foundation of China (62072469); National Key R&D Program (2018yfe0116700); Shandong Natural Science Foundation (ZR2019MF049); Basic Research Fund of Central University (2015020031); West Coast Artificial Intelligence Technology Innovation Center (2019-1-5, 2019-1-6); the Opening Project of Shanghai Trusted Industrial Control Platform (TICPSH202003015-ZC)收稿时间: 2020-09-10; 修改时间: 2020-10-09; 采用时间: 2020-10-13; csa 在线出版时间: 2021-04-28计算机视觉图像识别是人工智能的重要应用, 广泛应用在工业、医学、军事、教育、商业、体育、安防检测等行业与领域中. 机器学习, 尤其是深度学习展现出了针对图像识别领域优秀的识别性能. 而机器学习本身需要建立在大量的带有指导意义的既有数据集基础之上. 在进行深度学习模型训练流程中, 往往需要针对海量图片进行人工数据标注, 繁重的图像标注任务增添了大量时间成本.传统的图像标注工具, 如表 1所示, 大多以单机运行的传统单体式系统架构为主, 运行在单机之上, 同一时间同一系统运行实例上只允许一个用户对本地资源进行图像标定. 当使用传统图像标注工具进行协作标定时, 需要用户手动进行图像集的分组并拷贝至协作组员的工作站. 协作组员各自完成任务后仍需要用户自行合并制作数据集. 由于缺少集中化的图像与工作流, 导致传统单机标注工具在协作场景下存在大量的文件与数据传输, 在海量图像文件的压缩、打包与传输过程中产生了大量的时间与人工成本.表1 传统图像标注工具对比图像标注工具实例系统架构兼容系统开源与付费模式协作模式支持的图像标注类型导出格式网址LabelImg单机(PyQt5)全平台开源免费可独立部署手动资源分组打包后独立运行协作标注矩形PASCAL、VOC、ImageNethttps:///tzutalin/labelImgLabelMe单机(PyQt5)全平台开源免费多边形、矩形、圆形、线标注、关键点COCOhttps:///wkentaro/labelmeVIA-VGG Image Annotator Web本地静态页面全平台开源免费多边形、矩形JSON、CSV、COCOhttps:///PixelAnnotaion单机(Qt5)Windows、MacOS、Linux(自行编译)开源免费填充区域JSONhttps:///abreheret/PixelAnnotationToolRectLabel单机MacOS 不开源付费$55多边形、填充区域、矩形PASCAL、VOC、YOLO、COCO、CSVhttps:///OpenCV/CVAT Web本地部署(Django)全平台开源免费单实例不支持直接协作, 需要手动对资源分组打包独立部署多实例图像分类、多边形工具预定义XML格式https:///opencv/cvatVoTT Web本地部署(NodeJs)全平台开源免费矩形Azure自有格式、CNTK、Pascal、VOC、TFRecords、VOTT(JSON)、CSVhttps:///microsoft/VoTTLabelBox纯前端库全平台不开源需要引用公网库资源需要额外系统支持图像分类、多边形、矩形CSV、JSON(由官方后端提供)https:///Labelbox/Labelbox)为了解决机器学习图像识别训练的各种前置准备工作费时费力的问题, 本文提出并设计实现了一种基于Spring Cloud、面向机器学习模型训练的协作式图像数据管理与标注平台, 通过众包任务的方式, 优化图像标注流程, 设计实现了面向海量图像的存储、标定集管理、图像标定任务管理等功能模块. 系统采用微服务架构, 将系统各个部分进行解耦[1], 实现服务注册与发现、负载均衡、容错处理, 提升了系统的高可用性、可维护性与可扩展性. 基于GitLab-CICD实现了微服务的增量更新、持续部署与灰度更新. 通过将海量图像标定数据进行分组划分, 简化数据标注过程中的操作, 降低了数据标注人员的时间成本, 提升了数据标注工作效率.1 概述1.1 众包任务模式众包任务模式指的是将本应当由单一机构或个人执行的工作内容在公开或非公开网络上以公开的方式外包给特定或非特定用户[2]. 通过采用众包任务的模式,将庞大的图像标注任务切分为小的任务, 能够有效提计算机系统应用2021 年 第 30 卷 第 5 期升标定的速度与质量, 从而加速深度学习模型训练流程.1.2 微服务架构微服务[3]是一系列功能简单、互相之间采用轻量级通信协议协同工作的功能区块. 每个小的功能区块具有高内聚、低耦合的特点, 能够独立自主地运行.微服务架构是一种架构模式, 它是SOA架构(Service Of Application)的进一步发扬, 通过将庞大的系统根据业务边界细粒度地拆分为小的服务模块. 每个小的服务模块具有高内聚、低耦合的特点, 均能够独立地运行. 每个模块可以由不同的团队进行开发[4].微服务架构拥有着许多传统单体式应用所不具备的优势[5]:① 复杂度可控: 通过将复杂的系统细粒度地拆分为小体积、业务简单的模块, 降低了每个模块的开发难度与复杂度. 各个模块间互相解耦[6], 当需求变更时,只需要修改对应的模块即可实现系统整体功能上的变更, 无需考虑其他模块可能因为接口实现的变更而无法正常工作的问题.② 团队协作效率高: 当确定系统各个微服务接口定义后即可分组并行开发不同的微服务模块, 从而提升了整体开发效率. 同时不同微服务模块无需集成为一个整体, 只需要能够互相调用即可保证系统的正常运行, 避免了单体式应用集成过程中出现的组件源码不兼容, 降低了集成成本.③ 独立部署: 每个小模块都能够独立地运行, 不会因为其他服务故障而受到影响. 通过微服务调度系统的支持, 能够实现快速部署在单机或集群上, 从而充分利用计算性能.④ 维护难度低: 配合持续集成与持续部署(CI/CD),即可实现灰度发布与服务热更新, 无需系统全部停机或重启即可完成功能更新.⑤ 多种技术允许共存: 微服务独立部署使得微服务间只需要约定技术、语言无关的RPC协议即可实现不同技术、语言实现的微服务共存并配合工作[7].⑥ 系统稳定性高: 微服务架构的系统拥有熔断机制, 当系统部分组件失效时能够及时阻止故障船体, 从而避免系统发生雪崩式功能失效, 提升了系统的稳定性.1.3 对象存储系统基于对象的云存储即对象存储(object storage)是近几年逐渐流行的一个新兴且切实可行的大规模存储方案[8], 使用较为简便的方法实现数据存储, 即充分利用已有的存储组件、网络技术和处理技术, 使系统拥有较好的可扩展性以及高吞吐量[9]. 对象存储思想的核心为对象, 每个对象都有唯一的标识[10]. 对象存储将文件划分为一个个对象, 为用户提供了统一的存储空间,从而能更好的对文件进行访问控制和存储管理[11]. 这些对象被分布在整个集群之中, 为保障数据安全、防止数据丢失将每一个对象多重备份复制到多个设备上.对象存储系统将数据块列表映射为对象列表, 将各类数据块简化成为一个个对象来进行管理[12], 极大改善了系统的可伸缩性, 可以轻易实现海量数据的管理.2 系统设计2.1 需求分析传统的数据集标注往往在单终端中进行, 大量的图像需要由一个部门或者个人完成. 使用传统的标注工具进行多人协作式图像标注时, 在图像整理上浪费了大量时间. 协作前需要人工将大量图像打包分组, 协作后需要将图像与标定数据回收合并为同一个数据集合. 常见的文件系统针对海量小文件的处理性能往往不及少量大文件, 导致人工打包也是一项耗时的工作.针对以上痛点, 图像标注系统主要有以下需求:① 图像数据托管: 为避免文件系统直接频繁操作大量小文件, 从而节省任务分配数据打包的时间, 图像数据应当由专门的机制进行托管, 必要时以图像为基本单位提供图像及其元数据检索服务.② 任务划分与管理: 为实现众包模式的图像标注,需要将包含大量图像的任务拆分为小任务, 交由不同的个人进行标注.③ 支持多种标注模式: 系统应当支持机器视觉训练常用的关键点、矩形、多边形标注模式.④ 支持多种导出格式: 针对主流深度学习源码所接受的格式, 系统应当具备良好的扩展性以支持更多的深度学习框架.⑤ 数据统计: 任务发起者应当能够看到子任务的标注进度、标签数量等统计信息, 从而有针对性地决定是否需要增加或者调整图像组成.⑥ 支撑模块需求: 除此之外, 系统应当具有基本的用户与权限控制功能.2.2 微服务划分与系统架构设计① 系统微服务划分根据系统需求分析结果, 将系统划分为4个功能2021 年 第 30 卷 第 5 期计算机系统应用性微服务和3个架构支撑服务: 图像对象存储服务、图像集合管理服务、标定集合管理服务、数据输入输出服务、用户及授权管理和服务网关.图像对象存储服务用于面向海量图片的对象存储,将图片统一以相同规则生成的不重复定位符作为索引,避免图片重复存储与图片文件名重复冲突的问题.图像集合管理服务用于将离散的图片在逻辑上组成一个集合, 作为系统中图片操作的基本单位.标定集合管理服务用于管理和存储图像集对应的标定数据, 同时提供标定任务的划分与分配.数据导入导出服务主要用于图像、标签数据的解包导入与打包导出. 提供常见的压缩与视频格式的解析与常见数据集格式的导出等功能.② 系统架构设计系统整体采用分层式结构, 如图 1所示. 为了开发过程中能够更明确的分工, 其中服务层按照微服务的思想进行拆分. 各层主要包含内容如下:持久化层: 为了方便使用微服务编排框架进行部署, 所有有状态的服务均从整体架构中分离整合在持久化层中. 其中包括用于对象数据存储的NoSQL 数据库; 用于关系型信息数据存储的SQL 数据库; 用于全局数据缓存的内存NoSQL 数据库; 用于全局消息同步的消息队列中间件.微服务层: 包含了业务逻辑微服务群和架构支撑服务群两部分. 架构支撑服务群中包含了微服务架构必需的注册发现中心、日志监控、配置中心等基础微服务. 业务逻辑微服务群提供了实现业务逻辑的相关微服务, 包括图像对象存储微服务、图像集管理微服务、标定管理微服务和数据导入导出微服务.网关层: 网关层包含了由Spring Gateway 实现的API 网关微服务、前端站点微服务和Nginx 总代理微服务, 提供了系统接入入口.CI/CD 支撑部分: 系统源代码采用了Gitlab 私服进行托管, Gitlab 也提供了对持续集成的支持, 故直接采用Gitlab-CICD 实现系统开发过程中的持续集成与部署.系统采用现有完整的微服务方案, 使用服务发现实现松散的服务间耦合, 采用声明式RPC 客户端实现微服务间的互相调用, 使用统一网关代理微服务作为系统入口, 添加负载均衡机制以扩展系统负载容量, 使用OAuth2开放认证协议作为认证机制.系统部署业务逻辑服务数据导入导出微服务图像对象存储微服务持久化层SSDB 数据库MySQL 数据库Redis 缓存RabbitMQ 消息队列图像集管理微服务标定管理微服务数据导入导出微服务微服务支撑前端微服务Nginx 总代理Spring gateway API 网关Eureka 注册中心Config server 配置中心日志&监控自动化部署CI/CD 支撑Gitlab 代码仓库Gitlab-runner 宿主机代码提交开发团队图1 图像标注系统架构3 持续集成、持续部署与微服务架构实现3.1 微服务注册与发现在微服务架构的系统中, 为了实现微服务间既有松散的耦合度, 又能够互相访问, 微服务注册与发现机制是一种常用方法[13]. 通过由微服务自行将自身的信息主动注册至注册中心的方式, 使得其他微服务可以计算机系统应用2021 年 第 30 卷 第 5 期通过查询注册中心注册记录的方式间接地发现其存在并获得访问相关参数. 注册中心是注册与发现中最重要的一部分, 在Spring Cloud 微服务套件中, 提供了注册中心的一种原生实现和两种接入实现:① Eureka Server: 由Netflix 开发的基于原生Java 的开源注册中心实现, Spring Cloud 套件给出了基于Spring Boot 快速构建注册中心的方案.② Spring Cloud Consul: Consul 是由HashiCorp 公司开发的一种服务网格解决方案, 提供具有服务发现,配置和分段功能的全功能控制平面[14]. 通过添加org.springframework.cloud.spring-cloud-starter-consul-all 依赖, 同样可以实现类似的注册发现功能.Spring Cloud Zookeeper: Apache ZooKeeper 是一项集中式服务, 用于维护配置信息, 命名, 提供分布式同步和提供组服务[15]. 基于Spring Cloud 的微服务可以通过添加org.springframework.cloud.spring-cloud-starter-zookeeper-all 依赖实现基于ZooKeeper 的注册发现.由于后两种注册发现的方案需要单独部署第三方的应用实例来支撑微服务注册与发现的功能, 故选择可自行构建的Eureka Server 方案.Eureka 的注册与发现方案整体流程如图 2所示,主要分为两部分.Eureka 注册中心微服务1微服务2DCFeign 3. 调用服务1. 注册2. 获取实例列表DCDC: Discovery clientFeign图2 基于Eureka 的注册发现实现流程第一部分为Eureka 注册中心. Spring 提供了一套项目生成工具Spring Initializer [16], 允许开发人员直接通过可视化配置直接生成Spring Boot 项目, 这里借用Spring Initializer 可以直接生成Eureka Server 的项目.如图 3所示, 在Spring Initializer 中输入项目信息并选中Eureka Server 依赖, 点击Generate 即可得到初始项目模板. 在Spring Boot 启动类上添加@EnableEurekaServer 参数即可开启项目依赖中的Eureka Server.图3 使用Spring Initializer 生成Eureka Server 实例第二部分即业务微服务中的Discovery Client. 在需要通过服务发现感知其他服务实例的微服务中, 增加org.springframework.cloud.spring-cloud-starter-netflix-eureka-client 依赖, 并在项目引导类上添加@Enable-DiscoveryClient 注解, 即可为Feign 客户端添加服务发现的功能.完成其他业务微服务开发后, 同时启动各个微服务, 可通过登录Eureka 监控页面看到各个微服务的注册情况, 如图4所示.图4 通过Eureka Server 查看服务发现注册状态3.2 微服务接口网关与负载均衡相较于传统的单体式应用, 微服务架构的应用更接近于单体式应用站群. 微服务架构应用为了实现从外部表现为与单体式应用类似的形式, 需要一个微服务作为接口网关, 同时需要提供负载均衡的特性.对于API 网关, Spring Cloud 提供了两套方案:① Zuul: Zuul 来源于Netflix 开源的微服务架构套件. Zuul 底层采用了Tomcat Embeded 版本作为HTTP 支撑层.② Spring Cloud Gateway: Spring Cloud Gateway 是由Spring 项目组基于其自研Web 框架WebFlux 实现的API 网关. Spring Cloud Gateway 是Spring Cloud 去Netflix 进程中非常重要的一个项目, 旨在替代Zuul 成为未来的Spring Cloud 框架下的API 网关组件.WebFlux 底层为直接使用Netty 等高性能非阻塞2021 年 第 30 卷 第 5 期计算机系统应用服务器, 相较于采用Servlet架构的Tomcat(Embeded)性能上略胜一筹 [17]. 考虑到未来Spring项目组开发的方向与性能预期, 采用Spring Cloud Gateway作为系统API网关.Spring Cloud Gateway同样可以使用Spring Initializer 进行项目初始化, 初始化完成后可以通过在application. yml中的spring.cloud.gateway.route字段中配置接口路径与微服务的映射.代码1. Spring Cloud Gateway路由配置spring: application: name: application-gateway cloud: gateway: routes: # 用户服务 - id: user-service uri: lb://user-service predicates: - > Path= /oauth/**, /user/**, /role/** # 其他服务 # …对于负载均衡, Spring Cloud框架提供了Ribbon 组件. Ribbon是一款客户端侧负载均衡器, 它可以自动从Discovery Client中获取微服务实力列表, 应用常见的负载均衡算法实现在同一服务的多个冗余实例上的负载均衡[18]. 通过添加org.springframework.cloud. spring-cloud-starter-netflix-ribbon依赖即可在服务调用侧引入负载均衡组件.3.3 微服务熔断机制微服务之间往往避免不了互相调用对方的服务.当进行同步接口调用时, 被调用方宕机、接口调用超时往往会引起调用方的异常. 为了避免因微服务之间的依赖关系而出现大面积故障, 调用方服务应当感知被调用方的异常并作出防御性动作, 防止故障继续的蔓延.在Spring Cloud框架中, 提供了Hystrix组件. Hystrix能够在被调用微服务出现异常时及时熔断, 触发调用方的异常处理流程, 防止调用方产生异常. Hystrix 组件可以通过在微服务中添加org.springframework.cloud.spring-cloud-starter-netflix-hystrix依赖来添加至微服务中. 在微服务启动类上添加@EnableHystrix注解即可启用熔断器.3.4 基于SSDB的图像对象存储系统在深度学习图像识别模型训练过程中往往需要准备大量图像, 而实现存储并快速索引图像数据就是标注系统性能提升的关键点.SSDB是一个高性能的支持丰富数据结构的NoSQL 数据库, 其底层实现为Google的高性能键值对数据库LevelDB.首先是一个高性能SSDB集群, SSDB采用的是与Redis相同的网络通信实现, 故可以采用Redis集群常用的TwemProxy代理实现如图 5所示的对象存储架构.微服务集群SSDB 实例群SSDB 实例SSDB 实例SSDB 实例SSDB 实例SSDB 实例SSDB 实例SSDB 实例SSDB 实例图像存储微服务图像存储微服务图像存储微服务图像存储微服务TwemProxy TwemProxy TwemProxy···图5 SSDB集群架构图5上部分是图像对象存储微服务. 图像存储微服务使用图像原始数据经哈希运算得到的索引号作为图像在对象系统中的唯一索引. 每一张图像采用一个哈希表进行存储, 在哈希表中额外增加有关图像内容相关的元信息, 对于重复上传的内容采取增加元信息中记录的索引数量而不重复存储.3.5 基于Gitlab-CICD的持续集成与部署在传统的单体式应用中, 只需要编译一次即可得到可运行的产物, 而在微服务架构应用中, 因为划分为了多个实例, 这种类似于“站群”的系统往往需要编译多个“单体式应用”并封装为Docker镜像进行部署. 为了减少编译部署阶段的工作量, 使用Gitlab-CICD实现全自动化的编译、测试与部署.首先是准备一个Gitlab实例, 可以使用Gitlab官方站点或者建立开源的Gitlab-CE实例, 本文不再赘述计算机系统应用2021 年 第 30 卷 第 5 期有关Gitlab 实例搭建的内容.系统采用了Docker Swarm 作为微服务编排框架,使用Harbor 作为Docker Swarm 集群的私有镜像源.Gitlab-CICD 中另一个重要组成部分便是Gitlab-Runner. Gitlab-Runner 是实际执行持续集成任务的主体. Gitlab-Runner 支持多种部署方式, 本项目选择了基于裸机系统的编译环境, 方便做一些特殊的环境配置.Gitlab-CICD 执行流程如图 6所示, 主要环节包括:① 代码提交: 在各个微服务中建立Git 仓库, 并将仓库托管至Gitlab. 当微服务代码得到更新并推送提交至Gitlab 时, Gitlab 会自动检查仓库目标分支中的.gitlab-ci.yml 文件中的配置, 并在流水线(pipeline)中添加持续集成的任务.② CICD 任务的执行: Gitlab-Runner 定时向Gitlab 的流水线队列请求任务, 当Gitlab-Runner 得到任务后在其宿主机上执行配置文件中定义的脚本. 脚本中定义的动作完成微服务的编译、测试、镜像打包与提交、灰度更新.Docker swarm集群Harbor镜像仓库⑤ 拉取更新后的镜像④ 触发灰度更新② 获取任务开发主机① 提交代码到Git 仓库③ 推送镜像GitlabGitlab-Runner图6 Gitlab-CICD 执行流程以图像管理服务为例, 编写了如代码2所示的gitlab-CICD.yml 配置文件.代码2. Gitlab 持续集成与持续部署配置stages: - 测试 - 构建 - 部署测试: stage: 测试 only: - master tags: - dlp script: - mvn test 构建: stage: 构建 only: - master tags: - dlp script: - mvn package -Dmaven.test.skip=true - docker build -t ${DOCKER_REGISTRY}/dlp/${SERVICE_NAME}:latest . - docker push ${DOCKER_REGISTRY}/dlp/${SERVICE_NAME}:latest 部署: stage: 部署 only: - master tags: - dlp script: - docker -H ${DOCKER_SWARM} service update --image ${DOCKER_REGISTRY}/dlp/${SERVICE_NAME}:latest${DOCKER_SWARM_ STACK_NAME}_${SERVICE_NAME}如代码2所示, CICD 一次任务将分为3个阶段:构建、测试与部署. 其中测试阶段由Maven 进行编译并执行系统中的单元测试; 构建阶段直接使用Maven 进行服务器端编译, 随后使用Gitlab-Runner 宿主机上的docker 构建镜像并推送至Harbor; 部署阶段通过暴露Docker Swarm 中的Manager 节点上dockerd 的2375端口, 实现从Gitlab-Runner 宿主机直接控制集群并触发微服务镜像更新. 运行效果如图 7所示.通过在各个微服务实例中分别修改相同逻辑后分别以手动部署与持续集成在多节点集群上部署并统计用时, 得到逻辑更新至生产环境的耗时如表 2所示.图7 Gitlab-CICD 执行效果表2 手动部署与CICD 部署效率对比微服务实例手动部署耗时CICD 耗时图像存储(5实例)30 min 12 s 3 min 8 s 图像集管理(3实例)21 min 05 s 1 min 26 s 标定集管理(3实例)20 min 40 s 1 min 6 s 数据导入导出(1实例)13 min 23 s 6 min 42 s 其他微服务支撑服务16 min 41 s1 min 5 s2021 年 第 30 卷 第 5 期计算机系统应用由表 2可知, CICD 有效减少了系统集成过程中的集成与部署时间成本, 提升了系统逻辑变更同步至生产环境的效率.4 系统测试4.1 系统后端接口测试项目采用了微服务系统常见的前后端分离结构,前端在接口确定后采用桩服务器(mock-server)与后端并行开发. 后端系统测试过程中使用了postman 进行接口的测试, 如图8所示.Postman [19]是一个用于API 接口开发的协作平台.它提供了一套API 接口开发工具, 包括API 客户端、文档生成、自动化测试、API 接口监控、API 设计与桩服务器与接口文档协作.Postman 内嵌了OAuth2的认证模型, 通过配置即可实现一系列共用同认证服务的API 同时获得登录认证的功能.图8 使用postman 对后端接口进行测试4.2 系统功能测试以深度学习图像数据制备流程为例, 对系统中图像导入、任务分配与标定、数据导出流程进行功能测试.首先是图像导入. 图像标注系统支持图像、视频、PDF 、OpenDocument 等格式混合打包上传, 上传界面如图 9所示. 上传完成数据传输后转入异步解压处理流程, 异步解压完成后前端显示实际图像集大小.在图像集中创建出标定集后即可向系统中其他用户分配标定任务进行图像标定的团队协作. 分配任务过程如图 10所示.切换至任务执行用户, 可以在“我的任务”页面中看到由任务发起用户分配的任务, 点击“开始”按顺序对图像进行标定. 进入标定流程后, 如图 11所示,通过在图像上拖拽创建图像区域, 完成对图像内容的标记.图9 创建图像集图10 分配标定任务标注过程中发起任务的用户能够看到各个任务执行用户的标定进度与当前已标定图像的标签统计信息.当图像集标定完成后, 任务发起者可以对图像进行最终修正并导出图像集合与标定集合开展深度学习模型训练. 以导出的VOC XML 格式为例, 最终导出的标签集如图 12所示.图11 图像标注过程图12 标签集合导出计算机系统应用2021 年 第 30 卷 第 5 期。
图书情报专业词汇及缩写(中英双语)
图书情报专业词汇及缩写(中英双语)a * annual年刊(鉴)A and I abstracting and indexing编制文摘和标引AA *Cataloguing Rules: Author and Title Entries英美条例AAC Anglo-American Code英美条例(规则)AACR *Anglo-American Cataloguing Rules英美编目条例AAL Association of Assistant Librarians [UK][英国]助理图书馆长协会AALS Association of American Library Shools美国图书馆学院协会AAP Association of American Publishers美国出版商协会AB automated bibliography自动化文献目录ABA American Booksellers Association美国书商协会ABACUS Association of Bibliographic Agencies of Britain,Australia,Canada and the United States英国、澳大利亚、加拿大与美国书目机构协会ABC (1) Abridged Building Classification [UDC][国际十进分类法] 建筑专业简表(2) American Bibliographical Center美国书目中心ABI advance book information form新书预告单ABPB Annual Bibliography of the Printed Books and Libraries [Holland][荷兰]《印本图书与文库书目年刊》abr. * abridgment节略(本),摘要abs. * abstract摘要,文摘ABTICS Abstract and Book Title Index Card Service [UK][英国]文摘与图书书名索引卡片服务ACORDD Advisory Committee for the Research and Development Department [BL,UK] [英国图书馆]研究与发展部咨询委员会ACRILIS Australian Centre for Research in Library and Information Science 澳大利亚图书馆与情报学研究中心ACRL Association of College and Research Libraries[USA][美国]学院图书馆与参考图书馆协会ACSTI Advisory Committee for Scientific and Technical Information[UK][英国]科技情报咨询委员会act. std. actual standard现行标准ad. * addenda补遗,附录ADA (1) automatic data acquisition自动数据收集(2) automatic document analysis自动文献分析ADAM automatic document abstracting method自动编制文摘方法adap. adapted改写(编)的ADI * American Documentation I nstitute美国文献学会ADONIS * Article Delivery Over Network Information Systems ADONIS 系统,网络文章提供情报系统ADP (1) American Data Pro.cessing,Inc.美国数据处理公司(2) automatic data processing自动数据处理ADPC automatic data processing center自动化数据处理中心ADPS automatic data processing system自动化数据处理系统ADRS Automatic Document Request Service [BLLD][不列颠(英国)图书馆外借部]自动文献需求服务A.D.S. autograph document signed签署人手迹文件ADX automatic data exchange自动数据交换AFIPS American Federation of Information Processing Societies 美国信息处理学会联合会AFLA Asian Federation of Library Associations亚洲图书馆协会联合会AFNOR Association Francaise de Normalisation法国标准化学会AFP * associative file processor相联文件处理机AFR automatic field/format recognition字段格式自动识别AFSARI automation for storage and retrieval of information 情报存贮与检索自动化AGLINET Agricultural Libraries Information Network[UN][联合国]农业图书馆情报网络AGRIS * Agricultural I nformation System [FAO][联合国粮农组织]农业情报系统AIC automatic information center自动化情报中心AID (1) automatic information distribution自动情报分发[系统](2) International Association of Documentalists and Information Officers 国际文献与情报工作者协会AIDS automated information dissemination system自动情报提供系统AIDUS automated input and document update system自动化输入与文献更新系统AIL Association of International Libraries国际图书馆协会AIRS (1) automatic image retreval system自动影像检索系统(2) automatic information retrieval system自动情报检索系统AKWIC author-and-keywordin-context上下文关键词及作者索引ALA * American Library Association美国图书馆协会ALAS automated literature alerting system自动化文献快报系统ALBIS Australian LibraryBased Information System澳大利亚图书馆情报系统ALDP automatic languagedata processing自动语言数据处理ALG Automation in Libraries Group [UK][英国]图书馆自动化小组ALIS automated library information system自动化图书馆情报系统ALMS automated library management system自动化图书馆管理系统ALPHA automated literature processing,handling and analysis文献自动化处理、加工与分析A.L.S. autograph letter signed签署人手迹信件ALS Automated Library System [Company,Ltd.]自动化图书馆系统[公司]AMACUS automated microfilm aperture card updating system自动缩微胶卷窗孔卡片更新系统AMFIS automatic microfilm information system自动缩微胶卷情报系统A.Ms.S. autograph manuscri t signed签署人手迹手稿A.N. absque nota出版情况不详ANA American National Archives美国国家档案馆ann * annual年刊(鉴)Ann.Rep. annual report年报annot. (1) annotated注释的,提要的(2) * annotation注解(释),提要A.N.S. autograph note signed签署人手迹记录ANSI American National Standards Institute美国国家标准学会ANSTEL Australian National Scientific and T echnological Library 澳大利亚国家科学技术图书馆antq. antique珍本,古旧书anx. * annex[e]附录(件)app. * appendix附录appx. * appendix附录APR annual progress report年度进展报告AR (1) accession/report num,ber索取或报告号(2) annual report年报ARL Association of Research Libraries [USA][美国]研究图书馆协会ARLIS Art Libraries Society[UK][英国]艺术图书馆学会art. * article论文,文章ASCII American Standard Code for Information Interchange 美国信息交换用标准代码ASDI automatic (automated) selective dissemination of information自动化定题情报提供ASI (1) * alphabetical subject index字顺主题索引(2) American Society of Indexers美国标引员学会(3) * articulated subject index挂接主题索引ASIDIC Association of Information and Dissemination Centers[USA][美国]科技情报提供中心协会ASIS * American Society for Information Science美国情报科学学会ASLIB * Association of Special Libraries and Information Bureaux[UK][英国]专门图书馆及情报机构协会ASTED Association pour l’Avancement des Sciences et des Techniques de la Documentation [Canada][加拿大]文献工作科学技术促进协会ASTIA Armed Services Technical Information Agency [USA] [美国]武装部队技术情报局ATIS automatic terminal information service自动终端情报服务auth. * author著(作)者AUTODOC automatic documentation自动化文献管理AV audio-visual视听的,声像的AVIP Association of Viewdata Information Providers可视数据系统提供者协会AVLINE * Audiovisual OnLine视听资料联机数据库BB * bit[二进制]位,比特BA * Biological Abstracts《生物学文摘》BAC British Archives Council英国档案委员会BAIT bibliography,abstracts,index,translation书目、文摘、索引、译文BALLOTS Bibliographic Automation of Large Library Operations using Time-Sharing [USA][美国]大型图书馆管理中使用分时系统的书目自动化BALS bachelor of arts in library science图书馆学文学士BASE basic semantic element基本语义单位BASIC Biological Abstracts’Subjects in Context 《生物学文摘》题中关键词轮排索引BBC basic bibliographic citation基本书目引证(文)BC (1)* Bibliographic Classification书目分类法(2) Bliss Classification布利斯分类法(3) British Council英国委员会BCD binary-coded decimal[interchange code]二一十进制[交换码]BCM British Catalogue of Music《英国音乐目录》bd. bound装订成册的,合订本bdg. * binding装订BDU basic display unit基本显示装置BHI British Humanities Index《英国人文科学索引》Bibl. *bibliography书目,目录Bibl. Ind. bibliographic index书目索引BI DAP bibliographic data processing programme 文献目录数据处理程序biog. biography传记Biog.Ind. biographical index传记(人名)索引BIOSIS Biosciences Information Service [USA] [美国]生物科学情报服务社BIP (1)*books in print在版图书(2)* Books in Print《在版图书目录》BIRS (1) basic indexing and retrieval system基本索引与检索系统(2) British Institute of Recorded Sound英国录音学会BIS Biological Information Service [UK][英国]生物情报服务社bi-w * biweekly双周刊bk. * book图书,书籍bk. rev. * book review书评bklt. booklet小册子BL * British Library不列颠图书馆BLAISE * British Library Automated Information Service不列颠图书馆自动化情报服务处BLBSD British Library Bibliographic Services Division不列颠图书馆书目服务部BLCMP * Birmingham Libraries Co-operative Mechanisation Project [UK] [英国]伯明翰图书馆机械化协作计划BLEND Birmingham Loughborough Electronic Network Development [UK] [英国]伯明翰-拉夫巴勒电子网络开发[计划] BLLD British Library Lending Division不列颠图书馆外借部BLLR Bureau of Libraries and Learning Resources[USA][美国]图书馆与学术资源委员会BLRD British Library Reference Division不列颠图书馆参考部BLRDD British Library Research and Development Department不列颠图书馆研究与发展部BLS bachelor of library science图书馆学学士bm. * bimonthly双月刊BML * British Museum Library不列颠博物院图书馆BN *Bibliothéque Nationale[France][法国]国家图书馆BNB * British National Bibliography《英国国家书目》BNBC British National Book Centre英国国家图书中心BNCDST British National Committee on Data for Science and Technology英国科技数据全国委员会BOLD bibliographic on-line display system书目联机显示系统BPA British Patents Abstracts《英国专利文摘》BPR American Book Publishing Record《美国图书出版记录》BRASTACS Bradford Scientific,Technical and Commercial Service [UK][英国]布拉德福科学、技术与商业服务社BRIMARC BNB/Brighton MARC英国国家书目/布赖顿机读目录BROWER * Browsing Online with Selective Retrieval浏览联机定题检索系统BRS *Bibliographic Retrieval Services Inc. [USA][美国]文献检索服务公司BRT BioResearch Titles《生物研究题录》BS (1) Bibliographical Society [UK][英国]目录学会(2) British Standard英国标准BSA Bibliographical Society of America美国目录学会BSD [British Library] Bibliographic Services Division[不列颠图书馆]书目服务部BSH * Basic Subject Headings基本件名标目表BSIB British Society for International Bibliography英国国际目录学会BSLS bachelor of science in library science图书馆学理学士BSO * Broad System of Ordering.概略分类体系BTI British Technology Index《英国工程索引》BUCCS Bath University Comparative Catalogue Study [UK] [英国]巴思大学比较目录研究BUCOP * British Union-Catalogue of Periodicals《英国期刊联合目录》BUCOP -WLSP British UnionCatalogue of PeriodicalsWorld List of Scientific Periodicals《英国期刊联合目录——世界科学期刊目录》Bull. * bulletin.通报CC (1)* chapter章,回(2)* citation引证(文)(3)* copy抄(副)本(4)* copyright版权,著作权CA (1)* Chemical Abstracts《化学文摘》(2) current awareness新书预告,现期文献报道CAAS * computer-assisted acquisition system计算机辅助采购系统CABLIS Current Awareness for British Library Staff不列颠图书馆工作者现期通报服务CABS computerized annotated bibliography system 计算机化提要书目系统CAG Co-operative Automation Group [UK][英国]协作自动化小组CAIA * computer-assisted information analysis计算机辅助情报研究CAIC computer-assisted indexing and classification 计算机辅助标引与分类CAIRS computer-assisted information retrieval system 计算机辅助情报检索系统CALM computer-assisted library mechanization计算机辅助图书馆机械化CAN/SDI Canadian Selective Dissemination of Information 加拿大定题情报提供系统CAR * computer-assisted retrieval计算机辅助检索CAS (1)*Chemical Abstracts Service化学文摘社(2) computerised acquisition system计算机化采购系统CASIA Chemical Abstracts Subject Index Alert《化学文摘主题索引通报》cat. catalog[ue]目录CAT (1) computer-aided translation计算机辅助翻译(2) computer-aided typesetting计算机辅助排版CATCALL completely automated technique for cataloguing and acquisition of literature for libraries图书馆文献全自动编目与采购技术catlg. *catalog[ue]目录CATNI Catchword and Trade Name Index [CTI][《现期技术索引》] 《关键词与商标名索引》CATNIP computer-assisted technique for numerical index preparation计算机辅助数值索引编制技术CATV * community antenna television共用天线电视CBI * Cumulative Book Index《累积图书索引》c.c. carbon copy复写副本CC (1) card code卡片代码(2) * card column卡片列(3) * Colon Classification冒号分类法(4) Current Contents《现期期刊目次》CCC (1) Central Classification Committee [FID][国际文献工作联合会]中央分类法委员会(2) Copyright Clearance Center [USA][美国]版权批准中心CCF * Common Communication Format通用交换格式CCLN Council for Computerized Library Network[USA][美国]计算机化图书馆网络委员会CCTV * closed circuit television闭路电视cd catalogued已编目的CD compact disc小型光盘CDCR Center for Documentation and Communication Research [USA][美国]文献处理与通信研究中心CD-I compact disc interactive交互型小型光盘CD-ROM * compact discread-only memory小型光盘只读存贮器CDS Computerized Documentation Service [UNESCO][联合国教科文组织]计算机化文献服务CDU central display unit中央显示装置CED capacitance electronic disc电容式电子录像片(盘)CEIS cost and economic information system成本与经济情报系统CERN European Organization for Nuclear Research欧洲核研究组织CETIS Centre Europeen pour le Traitement de l’Information Scientifique欧洲科学情报处理中心cfr confer参看,对照CFSTI Clearinghouse for Federal Scientific and Technical Information[USA] [美国]联邦科学技术情报交换中心ch. * chapter章,回ch. lbr. * chief librarian图书馆馆长chap. * chapter章,回CHAR * character字符CI (1) cham index链式索引(2) cumulative index累积索引CICRIS Co-operative Industrial and Commercial Reference and Information Service [UK][英国]工商业合作咨询与情报服务CIF central information file中央情报文档CIM (1) computer-input media计算机输入载体(2) * computer-input microfilm计算机输入缩微胶片(3) continuous image microfilm连续影像缩微胶片(4) Cumulated Index Medicus《累积医学索引》CIP * cataloguing in publication在版编目CIRCA computerized information retrieval and current awareness计算机化情报检索与现期文献通报CIS (1) cataloguing in source书源编目(2) country information system国家情报系统(3) current information selection现期情报选报CISTI Canada Institute for Scientific and Technical Information加拿大科学技术情报学会CISTIP Committee on International Scientific and TechnicalInformation Programs[USA][美国]国际科学技术情报计划委员会cl. * cloth布面[装订]CLA Canadian Library Association加拿大图书馆协会CLR Council on Library Resources,Inc. [USA][美国]图书馆资源委员会CM *cartographic materials地(制)图资料CMC code for magnetic characters磁字符代码CMDR Council for Microphotography and Documentary Reproduction [UK][英国]缩微摄影与文献复制理事会CNK common noun keyword普通名词关键词CNLA Council of National Library Associations全国图书馆协会理事会CNPIEC * China National Publications Import & Export Corporation中国图书进出口总公司CNRS Centre National de la Recherche Scientifique et Technique [France] [法国]国家科学技术研究中心CODASYL Conference on Data System(s) Language(s) [UK] [英国]数据系统语言会议CODATA * Committee on Data for Science and Technology [ICSU][国际科学协会理事会]科学技术数据委员会COINS computer and information sciences计算机与信息科学col. coloured彩色的COM (1)* computer-output microfilm计算机输出缩微胶片(2) computer-output microfilming计算机输出缩微化设备(3) computer-output microform计算机输出缩微品COMAC continuous multiple access collator连续多次存取校对程序COMARC Cooperative Machine-Readable Cataloging [LC,USA][美国国会图书馆]合作机读编目COMEINDORS composite mechanized information and documentation retrieval system 综合机械化情报与文献检索系统comp. (1) compiled编纂(辑)的(2) *compiler编纂人(者)COMP computer output microfilm peek-a-boo计算机输出缩微胶片重叠比孔COMPAC computer output microfilm package计算机输出缩微胶片软件包COMPENDEX Computerized Engineering Index《计算机化工程索引》CONLIS Joint Committee on National Library Information Systems[USA][美国]国家图书情报系统联合委员会CONSER (1) Conversion of Serials Project[USA][美国]连续出版物建库计划(2)* Cooperative Conversion of Serials连续出版物合作转换计划cont. * contents目次,内容contin. * continuation续编contr. controlled限制发行cop. (1)* copy抄(副)本(2)* copyright版权,著作权co-part counterpart副(复)本COPIC Computer Program Information Center[European Community][欧洲共同体]计算机程序情报中心corr. (1) corrected校订的(2) corrigendum勘误表COSATI * Committee on Scientific and Technical Information [USA] [美国]科学技术情报委员会COSI Committee on Science Information [USA][美国]科学情报委员会COSTAR conversational online storage and retrieval会话式联机存贮与检索CP * card punch卡片穿孔机CPM cards per minute[卡片阅读速度]卡片/分CPS characters per second字符/秒CPU (1) card punching unit卡片穿孔机(2)* central processing unit中央处理机CR (1) card reader卡片阅读机,读片机(2) confefence report会议报告CRAM card random access mechanism磁卡片随机存取方法CRESS computerized reader enquiry service system 计算机化读者咨询服务系统CRG *Classification Research Group [UK][英国]分类法研究小组CRIS (1) Command Retrieval Information System 命令检索情报系统(2) Current Research Information System当前研究情报系统CRL (1) Central Reference Library [UK][英国]中央参考图书馆(2) certified record librarian合格图书馆员(3) certified reference librarian合格参考图书馆员(4) college and research libraries学院图书馆和研究图书馆CRSG Classification Research Study Group [USA][美国]分类法研究小组CRT cathode-ray tube阴极射线管CRUS Centre for Research in User Studies [UK] [英国]用户研究中心CSBN * China Standard Book Number中国标准书号CSF central serials file中央连续出版物文档CSR central serials record中央连续出版物记录CT Chemical Title《化学题录》ctd. continued接上页(期)CTI Current Technology Index《现期技术索引》CTR contract technical report合同技术报告CTS (1) card-to-magnetic tape conversion system 卡片-磁带转换系统(2) communication technology satellite通信技术卫星(3)* computer typesetting计算机排版CULS college and university libraries高等院校图书馆cum. ind. cumulative index累积索引CUMARC cumulated machine readable cataloguing累积机读编目Dd. *daily日报(刊)DA (1) data administrator数据管理员(2) data analysis数据分析(3) Documentation Abstracts《文献工作文摘》DACOM datascope computer output microfilmer计算机数据显示输出缩微胶片机DARE documentation automated retrieval equipment 文献自动化检索设备DAS (1) data acquisiton system数据采集系统(2 ) data automation system数据自动处理系统dat. datum数据DATACOM * data communication数据通信DATAX * data transmission数据传输DB * data base数据库DBAM database access method数据库存取方法DBK data bank数据(资料)库DBMS *database management system数据库管理系统DC (1)* data centre数据中心(2)* data conversion数据转换(3) Decimal Classification[Dewey][杜威]十进分类法DCAS data collection and analysis system 数据收集与分析系统DCE data communications equipment数据通信设备DCR (1) data conversion receiver数据转换接收机(2) digital conversion receiver数字转换接收机DCS data communication system数据通信系统DDC (1) data distribution center数据分配中心(2) Defense Documentation Center [USA] [美国]国防文献中心(3)* Dewey Decimal Classification杜威十进分类法DDCE digital data conversion equipment 数字数据转换设备DDP (1) digital data processor数字式数据处理机(2) distributed data processing分布型数据处理DE (1) digital element数字单元(2) display element显示单元(3) display equipment显示设备diagr. diagram图,图表DIANE * Direct Information Access Network for Europe欧洲直接情报存取网络dict. * dictionary字(词)典dig. *digest摘要,文摘DIGICOM digital communications system数字通信系统DIMDI Deutsches Institut für medizinische Dokumentation und Information 德国医学文献与情报研究所DIN Deutsche Industrie Norm德国工业标准DIODE digital input/output display system数字输入输出显示系统DIRS * DIMDI Information Retrieval ServiceDIMDI情报检索服务处DISISS Design of Information Services in the Social Sciences [UK][英国]社会科学情报系统设计diss. * dissertation学位论文DLAI documentation,library and archives infrastructures文献工作、图书馆与档案馆基础DLS. doctor of library science图书馆学博士DM data management数据管理D.M.C. district materials center地区教材中心DMS * data management system数据管理系统do. ditto同上,同前doc. * document文献(件)DOR digital optical recording数字光学记录DOS disk operation system磁盘操作系统DP * data processing数据处理DPIR data processing and information retrieval 数据处理和情报检索DPS (1) data processing system数据处理系统(2) document processing system文献处理系统DRAW * direct read after write写后直读DRDW * direct read during write边写边读DRIC Defence Research Information Centre [UK] [英国]国防研究情报中心DRS document retrieval system文献检索系统DS data set数据集D.S. document signed著者签署文件(献)DSE data storage equipment数据存贮设备DSR data survey report数据调查报告DSTI Division of Scientific and Technical Information [IAEA] [国际原子能机构]科技情报部DT (1)* data transmission数据传输(2) display terminal显示终端DTIC Defense Technical Information Center [USA][美国]国防技术情报中心DTS data transmission system数据传输系统DTU display terminal unit显示终端设备dup. *duplicate抄(副)本d.w. * dust wrapper包封,封套DXS data exchange system数据交换系统EEB *Encyclopaedia Britannica《不列颠百科全书》,《大英百科全书》EBCDIC Extended Binary Coded Decimal Interchange Code 扩充二一十进制交换码EBR electronic beam recording电子束记录EC * Expansive Classification展开分类法ed. (1) edited编辑(2)* edition版[本](3) *editor编者EDIAC electronic display of indexing association and content 标引结合与内容的电子显示EDICT engineering document information collection technique 工程文献情报搜集技术edit. (1) edited编辑(2) * edition版[本](3) * editor编者e.d.l. edition de luxe豪华版EDP (1)* electronic data processing电子数据处理(2) estimated date of publication估计的出版日期EDPC electronic data processing center电子数据处理中心EDPM electronic data processing machine 电子数据处理机EDPS electronic data processing system 电子数据处理系统EDRS engineering data retrieval system 工程数据检索系统。
OXYMAT 6 气体分析仪安全手册说明书
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Danger
indicates that death or severe personal injury will result if proper precautions are not taken.
Warning indicates that death or severe personal injury may result if proper precautions are not taken.
EIA SFF-8088 Rev 3.3 Mini Multilane 4X 盾屏连接器壳和插头规格
SFF CommitteeSFF-8088Specification forMini Multilane 4X Shielded Connector Shell and PlugStandardized as EIA-976 at Rev 3.2 on April 16, 2011This specification was submitted as a project to become a standard, and was Expired at that time.If there were modifications subsequent to the date of submittal, or any were made during the EIA approvals process, they may not be reflected in this copy.EIA standards can be purchased from /CONTINUING ACTIVITYCompanion and subsequent specifications have been developed.SFF-8086 Mini Multilane 10 Gb/s 4X Common Elements ConnectorSFF-8087 Mini Multilane 4X Unshielded Connector Shell and PlugSFF-8642 Mini Multilane 10 Gb/s 12X Shielded Cage/ConnectorSFF-8643 Mini Multilane 12 Gb/s 8/4X Unshielded ConnectorSFF-8644 Mini Multilane 12 Gb/s 8/4X Shielded Cage/ConnectorSFF-8645 Mini Multilane 24 Gb/s 8/4X Shielded Cage/ConnectorSFF-8647 Mini Multilane 14 Gb/s 12X Shielded Cage/ConnectorSFF-8648 Mini Multilane 28 Gb/s 12X Shielded Cage/ConnectorSFF Committee documentation may be purchased in hard copy or electronic form.SFF specifications are available at ftp:///sffSFF CommitteeSFF-8088 Specification forMini Multilane 4X Shielded Connector Shell and PlugRev 3.3 March 14, 2013Secretariat: SFF CommitteeAbstract: This specification defines the physical interface and general performance requirements for the Mini Multilane Shielded connector. One such use is as the Serial Attached SCSI Mini SAS 4X (wide compact external connector).This specification provides a common reference for systems manufacturers, system integrators, and suppliers. This is an internal working specification of the SFF Committee, an industry ad hoc group.This specification is made available for public review, and written comments are solicited from readers. Comments received by the members will be considered for inclusion in future revisions of this document.The description of a connector in this specification does not assure that the specific component is actually available from connector suppliers. If such a connector is supplied it must comply with this specification to achieve interoperability between suppliers.Support: This specification is supported by the identified member companies of the SFF Committee.POINTS OF CONTACT:Jay Neer I. Dal AllanMolex Chairman SFF Committee2222 Wellington Court 14426 Black Walnut CourtLisle, IL 60532 Saratoga, CA 95070561-447-2907x3889 408-867-6630*************************@EXPRESSION OF SUPPORT BY MANUFACTURERSThe following member companies of the SFF Committee voted in favor of this industry specification.3M Hitachi CableAdaptec Hitachi GSTAMCC IBMAmphenol LSIComax MolexDell SeagateEMC Sun MicrosystemsENDL Toshiba AmericaFCI TycoFoxconn UnisysHewlett Packard Vitesse SemiconductorThe following member companies of the SFF Committee voted to abstain on thisindustry specification.Arista Networks MaxtorCinch PanasonicEmulex PicolightETRI Pioneer NewMediaFinisar Sandisk/RADFujitsu CPA SumitomoInfineon VolexIntelThe user's attention is called to the possibility that implementation to this Specification may require use of an invention covered by patent rights. By distribution of this Specification, no position is taken with respect to thevalidity of this claim or of any patent rights in connection therewith. Members of the SFF Committee that advise that a patent exists are required to provide a statement of willingness to grant a license under these rights on reasonable and non-discriminatory terms and conditions to applicants desiring to obtain such a license.Updated History:Rev 3.2 (April 16, 2011)- Editorial revision to incorporate 2011 titling and review content for consistency prior to being submitted for EIA standardization.Rev 3.3 (March 14, 2013)- EIA ballot drew the comment that SFF-8087 and SFF-8088 are shells, and have no speed or electrical characteristics. The title and affected text were changed to reflect this correction.ForewordThe development work on this specification was done by the SFF Committee, anindustry group. The membership of the committee since its formation in August 1990 has included a mix of companies, which are leaders across the industry.When 2 1/2" diameter disk drives were introduced, there was no commonality on external dimensions e.g. physical size, mounting locations, connector type, connector location, between vendors.The first use of these disk drives was in specific applications such as laptop portable computers and system integrators worked individually with vendors to develop the packaging. The result was wide diversity, and incompatibility.The problems faced by integrators, device suppliers, and component suppliers led to the formation of the SFF Committee as an industry ad hoc group to address the marketing and engineering considerations of the emerging new technology.During the development of the form factor definitions, other activities were suggested because participants in the SFF Committee faced more problems than the physical form factors of disk drives. In November 1992, the charter was expanded to address any issues of general interest and concern to the storage industry. The SFF Committee became a forum for resolving industry issues that are either notaddressed by the standards process or need an immediate solution.Those companies, which have agreed to support a specification, are identified inthe first pages of each SFF Specification. Industry consensus is not an essential requirement to publish an SFF Specification because it is recognized that in an emerging product area, there is room for more than one approach. By making the documentation on competing proposals available, an integrator can examine the alternatives available and select the product that is felt to be most suitable. SFF Committee meetings are held during T10 weeks (see ), and Specific Subject Working Groups are held at the convenience of the participants. Material presented at SFF Committee meetings becomes public domain, and there are no restrictions on the open mailing of material presented at committee meetings.Most of the specifications developed by the SFF Committee have either been incorporated into standards or adopted as standards by EIA (Electronic Industries Association), ANSI (American National Standards Institute) and IEC (International Electrotechnical Commission).If you are interested in participating or wish to follow the activities of the SFF Committee, the signup for membership and/or documentation can be found at:/ie/join.htmlThe complete list of SFF Specifications, which have been completed or are currently being worked on by the SFF Committee, can be found at:ftp:///sff/SFF-8000.TXTIf you wish to know more about the SFF Committee, the principles which guide the activities can be found at:ftp:///sff/SFF-8032.TXTSuggestions for improvement of this specification will be welcome. They should be sent to the SFF Committee, 14426 Black Walnut Ct, Saratoga, CA 95070.SFF Committee --Mini Multilane 4X Shielded Connector1.ScopeThis specification defines the plug, guide/strain relief shell, and latching requirements for the Mini Multilane Shielded connector based upon the mating interface defined in SFF-8086.2.ReferencesThe SFF Committee activities support the requirements of the storage industry, and it is involved with several standards.2.1Industry DocumentsThe following interface standards and specifications are relevant to this Specification.- T10/1601D SAS 1-1 (Serial Attached SCSI - 1.1)- SFF-8410 High Speed Serial Testing for Copper Links- SFF-8086 Mini Multilane 10 Gb/s 4X Common Elements Connector2.2SFF SpecificationsThere are several projects active within the SFF Committee. The complete list of specifications which have been completed or are still being worked on are listed in the specification at ftp:///sff/SFF-8000.TXT2.3SourcesThose who join the SFF Committee as an Observer or Member receive electronic copies of the minutes and SFF specifications (/ie/join.html).Copies of ANSI standards may be purchased from the InterNational Committee for Information Technology Standards (/c4psg).Copies of SFF, ASC T10 (SCSI), T11 (Fibre Channel) and T13 (ATA/SATA) standards and standards still in development are available on the HPE version of CD_Access(/85fts).TABLE OF CONTENTS1.Scope (5)1.1Description of Clauses.........................Error! Bookmark not defined.2.References (5)2.1Industry Documents (5)2.2SFF Specifications (5)2.3Sources (5)3.General Description (7)4.Definitions and Conventions (7)4.1Definitions (7)4.2Conventions (7)5.Connector Description (8)5.1Performance Requirements (8)5.2General View (8)5.3Configurations (9)6.Dimensions (9)6.1Shielded Free (Plug) Cable Connector (10)6.2Shielded Fixed (Receptacle) Right Angle Shell (13)6.3 Shell Blocking Key (Optional) (18)6.4 Plug Blocking Key (Optional) (19)6.5 Color Coding and Keying Definition (20)FIGURESFigure 5-1 General View of Shrouded Versions (8)Figure 5-2 Shielded Fixed (Receptacle) Right Angle Shell Configurations (9)Figure 6-1 Shielded Free (Plug) Cable Connector (11)Figure 6-2 Shielded Free (Plug) Cable Connector Latch and Pull Tab (12)Figure 6-3 Shielded Fixed (Receptacle) Right Angle Ground Pad (14)Figure 6-4 Shielded Fixed (Receptacle) Right Angle Shell (16)Figure 6-5 Shielded Fixed (Receptacle) Right Angle Shell (16)Figure 6-6 Shielded FIxed (Receptacle) Right Angle Panel Cutout (17)Figure 6-7 Shell Blocking Key Dimensions (19)TABLESTable 5-1 Shielded Fixed (Receptacle) Right Angle Shell Configurations (9)Table 6-1 Shielded Free (Plug) Cable Connector Dimensions (10)Table 6-2 Shielded Free (Plug) Cable Connector Latch and Pull Tab Dimensions (12)Table 6-3 Shielded Fixed (Receptacle) Right Angle Ground Pad Dimensions (13)Table 6-4 Shielded Fixed (Receptacle) Right Angle Shell Dimensions (15)Table 6-5 Shielded Fixed (Receptacle) Right Angle Panel Cutout Dimensions (17)Table 6-6 Shell Blocking Key/Keyway Dimensions (Optional) (18)3.General DescriptionThis specification defines the plug, guide/strain relief, and latching requirements for the Shielded Mini Multilane connector. This specification plus the mating interface and connector footprint defined in SFF-8086 meets the requirements to enable functional multiple sourcing.The connector provides positive retention along with ease of insertion and removal. The guide/strain relief is incorporated in the shell and works together with the cable plug and latching mechanism to ensure that stress induced by normal cable routing and management is not passed through to the solder joints, which attach the receptacle body to the printed circuit board.The latch is designed to prevent the plug from bottoming, and a hard stop has been defined to prevent bottoming out should the cable plug be out of spec.This specification defines the contact range that the retention scheme has to provide to assure acceptable connector performance.The low profile and small size is well suited to high-speed transmissionapplications where space is limited.4.Definitions and Conventions4.1DefinitionsFor the purpose of this specification, the definitions in SFF-8086 apply.4.2ConventionsThe ISO convention of numbering is used i.e., the thousands and higher multiplesare separated by a space and a period is used as the decimal point. This is equivalent to the English/American convention of a comma and a period.English French ISO0.6 0,6 0.61,000 1 000 1 0001,323,462.9 1 323 462,9 1 323 462.95.Connector Description5.1Performance RequirementsThe performance requirements for the contact mating interface for this connector system are defined in SFF-8086 Mini Multilane 10 Gb/s 4X Common Elements Connector. An additional performance requirement for the shielded versions is that the connector system with retention shall withstand 20 lbf minimum axial stress.5.2General ViewThe connector system is based upon a common footprint for the receiving body. The footprint positioning holes contain the critical dimensions for locating the receptacle shell. The receptacle shell also functions as the guide and strainrelief for the free (plug) connector interface. Figure 5-1 illustrates an exampleof one such configuration.FIGURE 5-1 GENERAL VIEW OF SHROUDED VERSIONSThe fixed (receptacle) right angle shell comes in alternative versions, as seen in Figure 5-2.FIGURE 5-2 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE SHELL CONFIGURATIONS5.3ConfigurationsTable 5-1 lists the versions described in this specification.TABLE 5-1 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE SHELL CONFIGURATIONSShielded Version Orientation 1-by-1 Port 26-circuit Shielded Mini Multilane Connector Right Angle1-by-2 Port 26-circuit Shielded Mini Multilane Connector Right Angle1-by-4 Port 26-circuit Shielded Mini Multilane Connector Right Angle Note: There are no straight versions specified in this document. In addition, the 26-circuit Shielded Mini Multilane Connector is referred to in SAS as the ”Mini SAS 4x” connector.6.DimensionsThe dimensioning conventions are described in ANSI-Y14.5M, Geometric Dimensioning and Tolerancing. All dimensions are in millimeters.Dimension related requirements for the connector system addressed in this document are specified in the tables and figures in this clause.6.1Shielded Free (Plug) Cable ConnectorTABLE 6-1 SHIELDED FREE (PLUG) CABLE CONNECTOR DIMENSIONS Designator Description Dimension Tolerance E01 Plug Thickness 12.75 ±0.13E02 Rail Guide Way Length 27.04 ±0.13E03 Snout Bottom to Plug Top 10.55 ±0.13E04 Snout Thickness 5.54 +0.15/-0.05E05 Clearance Groove Length 6.79 ±0.13 E06 Snout Tip to Lower Tab Tip 0.75 ±0.13 E07 Snout Internal Width 13.72 ±0.10E08 Lower Tab Forward Edge Width 8.88 ±0.13 E09 Snout Tip to PCB Tip 0.42 ±0.13 E10 Snout Length 28.31 ±0.13E11 Plug Width 18.70 ±0.10E12 UnusedE13 UnusedE14 PCB CL to Rail Guide Way Top 1.83 ±0.13E15 Rail Guide Way Width 1.25 ±0.05E17 Snout Top Surface Thickness/ Key Way Depth 0.70 ±0.05E18 Rail Guide Way Top to Snout Top 1.07 ±0.05E19 Rail Guide Way Top to Lower Tab Top 3.86 +0.15/-0.05E20 SnoutWidth 17.14 +0.20/-0.05 E21 Rail Guide Way Root to Root – Zone A 15.64 ±0.05E21 Rail Guide Way Root to Root – Zone B 15.94 ±0.05E22 Zone B Length for E21 5.20 ±0.13E23 Zone A Length for E21 18.45 ±0.13Depth 0.30 ±0.05 E24 ChamferLength 1.00 ±0.10 E25 ChamferDepth 0.20 ±0.05 E26 ChamferFIGURE 6-1 SHIELDED FREE (PLUG) CABLE CONNECTORTABLE 6-2 SHIELDED FREE (PLUG) CABLE CONNECTOR LATCH AND PULL TAB DIMENSIONS Designator Description Dimension Tolerance F01 Latch to PCB 26.28 ±0.20F02 Width of Barbs 9.20 ±0.10F05 Latch Clearance 1.14 ±0.10F06 Latch Barb Length 1.50 ±0.10F07 Latch Barb Lead-in Height 1.14 ±0.10F08 Latch Barb Lead-in Angle 33.5° ±1.0°F09 Latch to End of Pull 46.50 MinimumF10 Unused --- ---F11 Unused --- ---F12 Unused --- --- Width 18.80 Maximum F13 PullThickness 0.75 Minimum F14 PullF15 Latch to Plug Body 1.60 ±0.13FIGURE 6-2 SHIELDED FREE (PLUG) CABLE CONNECTOR LATCH AND PULL TAB6.2 Shielded Fixed (Receptacle) Right Angle ShellTABLE 6-3 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE GROUND PAD DIMENSIONSDesignator Description 1-by-4 1-by-2 1-by-1 ToleranceG01 Ground Pad Width 80.00 41.97 22.96 ±0.05G02 Screw Hole Spacing 77.25 39.22 20.21 ±0.05G03 Alignment Hole Spacing 75.53 38.24 19.22 ±0.05G04 Ground Pad Datum to Port 4 Datum 72.65 N/A N/A ±0.05 G05 Ground Pad Datum to Port 3 Datum 53.64 N/A N/A ±0.05 G06 Port Spacing 19.01 = = ReferenceG07 Ground Pad Datum to Port 2 Datum 34.63 = N/A ±0.05 G08 Ground Pad Datum to Port 1 Datum 15.62 = = ±0.05 G09 Connector Hole Spacing 12.00 = = ±0.05 G10 Port Datum to Ground Pad 2.87 = = ±0.05 G11 Port Mask Width 17.74 = = ±0.05 G12 Ground Pad to Edge of PCB 29.48 = = ±0.05 G13 Port Mask to Edge of PCB 27.37 = = ±0.05 G14 Notch to Datum B 16.80 = = ±0.05 G15 Pad Width 3.20 = = ±0.13 G16 Screw Hole Spacing 15.00 = = ±0.05 G17 Screw Hole to Datum 6.00 = = ±0.05 G18 Trace Alley Width 1.50 = = ±0.05 G19 Port CL to Trace Alley 1 3.80 = = ±0.05 G20 Port CL to Trace Alley 2 1.40 = = ±0.05 G21 Port CL to Trace Alley 4 3.40 = = ±0.05 G22 Port CL to Trace Alley 3 1.00 = = ±0.05 G23 Card Edge to Datum B 18.67 = = ±0.13G24 Fillet 1.00 = = Maximum G25 Screw Hole Diameter 2.50 = = ±0.05 G26 Locating Hole Diameter 1.55 = = ±0.05 G27 Notch to Ground Pad Offset 1.00 = = Minimum G28 Pad Edge to Datum B 15.80 = = ±0.05FIGURE 6-3 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE GROUND PADTABLE 6-4 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE SHELL DIMENSIONSDesignator Description 1-by-4 1-by-2 1-by-1 ToleranceH01 EMI Shield to Datum 24.96 = = ReferenceH02 PCI Rail to Datum 19.71 = = ±0.05 H03 Guide Rail Angle 1.0° = = ReferenceH04 Shield Locator Pin Diameter 1.46 = = ±0.05 H05 Flange Height 8.95 = = ±0.05 H06 EMI Shield to Datum 25.09 = = ReferenceH07 Face Plate to Datum 19.71 = = ±0.05 H08 EMI Gasket Gap Width 1.63 = = ±0.50 H09 Gasket Mate Surface to Datum 18.09 = = ±0.05 H10 Rear Height of EMI Shield 7.38 = = ±0.05 H11 Flange Height 8.63 = = ±0.05 H12 Guide Rail Set Back 1.00 = = ±0.05 H13 Guide Rail to Opening Top 1.38 = = ±0.05 H14 Guide Rail Thickness 1.00 = = ±0.05 H15 Guide Rail to PCB 5.61 = = ±0.05 H16 Guide Rail to PCB 5.19 = = ±0.05 H17 Guide Rail Angle 0.0° = = Reference H18 Port Opening Height 5.84 = = ±0.05 H19 EMI Shield Snout Height 7.29 = = ±0.05 H20 Guide Rail Internal Spacing 16.14 = = ±0.05 H21 Port Opening Width 17.74 = = ±0.05 H22 Key Height 0.70 = = ±0.05 H23 EMI Shield Snout Width 76.30 38.30 19.26 ±0.05 H24 Datum to Port 1 9.63 = = ±0.05 H25 Datum to Port 2 28.64 = N/A ±0.05 H26 Datum to Port 3 47.65 N/A N/A ±0.05 H27 Datum to Port 4 66.66 N/A N/A ±0.05 H28 Latch Hole Spacing 8.70 = = ±0.05 H29 Latch Hole Width 1.50 = = ±0.05 H30 Latch Hole Length 2.00 = = ±0.05 H31 Latch Hole Datum 24.09 = = ±0.05 H32 Latch Hole to Snout Face 1.00 = = ±0.05 H33 Guide Rail Height at Flange (1°) 7.42 = = ±0.05 H34 Guide Rail Height at Rear (1°) 6.89 = = ±0.05 H35 Datum to back edge (0º and 1º) 15.25 = = MAXFIGURE 6-4 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE SHELL Standard Application – 0 Deg. PCI Card Application – 1 Deg.FIGURE 6-5 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE SHELLTABLE 6-5 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE PANEL CUTOUT DIMENSIONSDesignator Description 1-by-4 1-by-2 1-by-1 ToleranceL01 Conductive Zone Length 79.79 41.76 22.74 ±0.25L02 Opening Length 76.79 38.76 19.74 ±0.10L03 Conductive Zone Width 10.50 = = ±0.25L04 Opening Width 7.70 = = ±0.10 L05 Opening Corner Radius 1.00 = = Maximum L06 Conductive Zone Corner Radius 2.00 = = Maximum L07 Opening to PCB Offset 1° (above PCB) 0.33 = = +0/-0.20 L08 Opening to PCB Offset 0° (below PCB) 0.20 = = ±0.10FIGURE 6-6 SHIELDED FIXED (RECEPTACLE) RIGHT ANGLE PANEL CUTOUT6.3 Shell Blocking Key (Optional)The keying scheme is defined by the respective standard.TABLE 6-6 SHELL BLOCKING KEY/KEYWAY DIMENSIONS (OPTIONAL) Designator Description Dimension Tolerance K01 Plug CL to Key Way 1 6.00 ±0.05 K02 Plug CL to Key Way 2 2.40 ±0.05 K03 Plug CL to Key Way 3 1.20 ±0.05K04 Plug CL to Key Way 4 0.00 ±0.05 K05 Plug CL to Key Way 5 1.20 ±0.05 K06 Plug CL to Key Way 6 2.40 ±0.05 K07 Plug CL to Key Way 7 6.00 ±0.05 K08 Key Way Width 1.20 ±0.05 K09 Key Way Lead-in Width 1.70 ±0.05 K10 Key Way Lead-in Length 2.40 ±0.05 J01 Port CL to Key 1 6.00 ±0.05 J02 Port CL to Key 2 2.40 ±0.05J03 Port CL to Key 3 1.20 ±0.05J04 Port CL to Key 4 0.00 ±0.05J05 Port CL to Key 5 1.20 ±0.05J06 Port CL to Key 6 2.40 ±0.05J07 Port CL to Key 7 6.00 ±0.05J08 KeyWidth 1.00 ±0.05FIGURE 6-7 SHELL BLOCKING KEY DIMENSIONS 6.4 Plug Blocking Key (Optional)The keying scheme is defined by the respective standardFIGURE 6-8 SHELL KEYWAY DIMENSIONSFIGURE 6-9 PLUG BLOCKING KEY DIMENSIONS – TOP VIEWFIGURE 6-10 PLUG BLOCKING KEY DIMENSIONS – SIDE VIEWTABLE 6-7 PLUG BLOCKING KEY DIMENSIONSDesignator Description Dimension Tolerance M01 Key Way Length 4.70 ±0.05M02 Key Way Width 1.36 ±0.05 Width 0.95 ±0.05 N01 KeyLength 3.50 ±0.05 N02 KeyN03 Key End to Plug Body 5.00 ±0.05Height 1.00 ±0.05 N04 Key6.5 Color Coding and Keying DefinitionThe pull tab color may be used to indicate the intended application for theinterface of the cable assembly as defined by the respective application standards. Similarly, specific key arrangements are defined by the respective application standards.FIGURE 6-11 SHIELDED FREE (PLUG) CABLE CONNECTOR PULL TAB。
未能加载基类system
未能加载基类system未能加载基类System在进行软件开发过程中,我们常常会遇到各种各样的错误和异常情况。
其中之一便是“未能加载基类System”错误。
这个错误通常在我们尝试运行或者调试我们的项目时出现,给我们带来了一些麻烦。
那么,为什么会出现这个错误呢?该错误又应该如何解决呢?本文将为您详细介绍。
首先,让我们来了解一下这个错误的背后原因。
当我们编写代码时,我们经常会使用到多个类,而这些类之间存在继承关系。
而在运行期间,如果我们的项目中某个类或者资源文件与基类System之间存在矛盾或者不一致,那么就会导致“未能加载基类System”错误的发生。
这意味着,我们需要找到并解决这些矛盾,才能顺利地运行我们的项目。
那么,出现这个错误后,我们应该如何解决呢?以下是一些可能的解决方法:1. 检查引用的程序集:首先,我们应该仔细检查我们的项目中所引用的所有程序集和资源文件。
确保它们与基类System兼容并且版本匹配。
如果存在不一致的情况,我们需要更新或者重新引用正确的程序集。
2. 检查代码中的重复引用:有时候,我们的代码中可能存在重复引用的情况,而这些重复引用可能会导致类或者资源文件之间的冲突。
因此,我们需要检查代码并移除这些重复引用,以解决这个问题。
3. 清除并重建项目:如果以上两种方法都没有解决问题,我们可以尝试清除并重建我们的项目。
这将清除项目中的临时文件和缓存,并重新构建整个项目。
这个过程有时可以解决一些隐藏的问题和冲突。
4. 更新.NET框架:另一个可能的解决方案是更新我们的.NET框架版本。
有时,旧版本的.NET框架可能无法正确加载基类System,导致出现这个错误。
通过更新.NET框架,我们可以获得修复的错误和更好的兼容性。
需要注意的是,以上解决方法并不是一劳永逸的。
由于每个项目的特殊性和复杂性不同,出现这个错误的原因也可能各不相同。
因此,在解决这个问题的过程中,我们需要不断尝试和实验,找到最适合我们项目的解决方案。
Oriental Motor HF-3118 操作手册说明书
HF-3118Cooling Module FM SeriesIP4X Rated Filter PanelThank you for purchasing an Oriental Motor product.This Operating Manual describes product handling procedures and safety precautions.• Please read it thoroughly to ensure safe operation. • Always keep the manual where it is readily available.Before using the productOnly qualified personnel should work with the product.The product described in this manual has been designed and manufactured for use in general industrial machinery, and must not be used for any other purpose. Oriental Motor Co., Ltd. is not responsible for any damage caused through failure to observe this warning.Hazardous substancesRoHS (Directive 2002/95/EC 27Jan.2003) compliantChecking the productUpon opening the package, verify that the items listed below are included.Report any missing or damaged items to the branch or sales office from which you purchased the product.FMZ1 A-M , FMZ1 A-A• Filter panel.............................1 pc.• Mounting screw set................1 set (Nut, M4 screw, 2 pcs. each) • Operating manual..................1 copy (this manual)FMZ1 A-B , FMZ1 A-C• Filter panel.............................1 pc.• Mounting screw set................1 set (Nut, M4 screw, 4 pcs. each) • Operating manual..................1 copy (this manual)FMZ1 A-L• Filter panel.............................1 pc.• Mounting screw set................1 set (Nut, M4 screw, 8 pcs. each,) • Operating manual..................1 copy (this manual)Checking the model nameCheck the model number against the number indicated on the product.Location for installationThe filter panel is designed and manufactured for installation in equipment. Install it in a well-ventilated location that provides easy access for inspection. The location must also satisfy the following conditions:• Inside an enclosure that is installed indoors (provide vent holes) • Operating ambient temperature−10 to +60 °C (+14 to +140 °F) (non-freezing)• Operating ambient humidity 85% or less (non-condensing)• Area that is free of explosive atmosphere or toxic gas (such as sulfuric gas) or liquid• Area not exposed to direct sun• Area free of excessive amount of dust, iron particles or the like• Area not subject to splashing water (rains, water droplets), oil (oil droplets) orother liquids• Area not subject to continuous vibration or excessive shocks• Area free of excessive electromagnetic noise (from welders, power machinery, etc.)• Area free of radioactive materials, magnetic fields or vacuumInstallation dimensionsDimensions [mm (in.)]Model Dimension drawingL1 L2 L3 L4 FMZ1 A-M145 (5.71) – 135 (5.31)135 (5.31)FMZ1 A-A A 170 (6.69) – 160 (6.30)160 (6.30)FMZ1 A-B 295 (11.61) 170 (6.69) 285 (11.22)160 (6.30)FMZ1 A-C B 420 (16.54) 170 (6.69) 410 (16.14)160 (6.30)FMZ1 A-LC263 (10.35) 263 (10.35) 250 (9.84)250 (9.84)OptionReplacement filter media ● IP4X rated filter mediaSet of 5 sheetsModel Applicable product FMXAA-M FM series – External dimensions: 155×155 mm (6.10×6.10 in.) FMXAA-A FM series – External dimensions: 180×180 mm (7.09×7.09 in.) FMXAA-B FM series – External dimensions: 305×180 mm (12.01×7.09 in.) FMXAA-C FM series – External dimensions: 430×180 mm (16.93×7.09 in.) FMXAA-L FM series – External dimensions: 284×284 mm (11.18×11.18 in.)1 sheetModel Applicable product FMXAA-L-1 FM series – External dimensions: 284×284 mm (11.18×11.18 in.)Cooling of the filter media reduces the cooling capacity. Clean or replace thefilter media regularly.• Unauthorized reproduction or copying of all or part of this manual is prohibited.• Oriental Motor shall not be liable whatsoever for any problems relating to industrial property rights arising from use of any information, circuit, equipment or device provided or referenced in this manual.• Characteristics, specifications and dimensions are subject to change without notice.• While we make every effort to offer accurate information in the manual, we welcome your input. Should you find unclear descriptions, errors or omissions, please contact the nearest office.• andare registered trademarks or trademarks of Oriental Motor Co., Ltd., in Japan and other countries.© Copyright ORIENTAL MOTOR CO., LTD. 2010Printed on Recycled Paper• Please contact your nearest Oriental Motor office for further information.Headquarters Tokyo, JapanTel:(03)3835-0684 Fax:(03)3835-1890Tel:01 47 86 97 50Fax:01 47 82 45 16Tel:(02)8228-0707 Fax:(02)8228-0708Technical Support Tel:(800)468-39828:30 A.M. to 5:00 P .M., P .S.T. (M-F)7:30 A.M. to 5:00 P .M., C.S.T. (M-F)E-mail:*****************************Headquarters and Düsseldorf Office Tel:0211-52067-00 Fax:0211-52067-099Munich Office Tel:089-3181225-00 Fax:089-3181225-25Hamburg Office Tel:040-76910443Fax:040-76910445Tel:01256-347090 Fax:01256-347099Tel:02-93906346 Fax:02-93906348Tel:(6745)7344 Fax:(6745)9405KOREATel:(032)822-2042~3 Fax:(032)819-8745Tel:(03)22875778 Fax:(03)22875528Tel:66-2-254-6113 Fax:66-2-254-6114。
Stata数据分析软件用户手册说明书
6Managing memoryContents6.1Memory-size considerations6.2Compressing data6.3Setting maxvar6.4The memory command6.5Setting aside memory for temporary storage of preserved datasets6.1Memory-size considerationsStata works with a copy of data that it loads into memory.To be precise,Stata can work with multiple datasets in memory at the same time.See[D]frames intro.Memory allocation is automatic.Stata automatically sizes itself up and down as your session progresses.Stata obtains memory from the operating system and draws no distinction between real and virtual memory.Virtual memory is memory that resides on disk that operating systems supply when physical memory runs short.Virtual memory is slow but adequate in cases when you havea dataset that is too large to load into real memory.If you wish to limit the maximum amount ofmemory Stata can use,you can set max memory;see[D]memory.If you use the Linux operating system,we strongly suggest you set max memory;see Serious bug in Linux OS in[D]memory. 6.2Compressing dataStata stores data in memory.The compress command reduces the amount of memory required to store the data without loss of precision or any other disadvantages;see[D]compress.Typing compress every so often is a good idea.compress works by examining the values you have stored and changing the data types of variables when that can be done without loss of precision.For instance,you may have a variable stored as float but that records only integer values between−press would change the storage type of that variable to byte and save3bytes per observation.If you had100variables like that,the savings would be300bytes per observation,and if you had3,000,000observations,the total savings would be nearly900megabytes.6.3Setting maxvarIf you get the error message“no room to add more variables”,r(900),do not jump to the conclusion that you have exceeded Stata’s capacity.maxvar specifies the maximum number of variables you can use.The default setting depends on whether you are using Stata/MP,Stata/SE,or Stata/BE.To determine the current setting,type query memory at the Stata prompt.If you use Stata/MP,you can reset this maximum number to120,000.If you use Stata/SE,you can reset this maximum number to32,767.Set maxvar to more than you need—at least20more than you need but not too much more than you need.Figure that each10,000variables consumes roughly0.5megabytes of memory.12[U ]6Managing memoryYou reset maxvar using the set maxvar command,set maxvar #,permanentlywhere 2,048≤#≤120,000,depending on your edition of Stata.You can reset maxvar repeatedly during a session.If you specify the permanently option,you change maxvar not only for this session but also for future sessions.Each additional 10,000variables specified with set maxvar requires Stata to set aside roughly 1.3megabytes of memory for variable names,not including the data stored in those variables.6.4The memory commandThe memory command will show you the major components of Stata’s memory footprint..use https:///data/r18/regsmpl (NLS women 14-26in 1968).memoryMemory usageUsed Allocated Data 856,02067,108,864strLs 00Data &strLs856,02067,108,864Data &strLs856,02067,108,864Variable names,%fmts,...4,644191,927Overhead1,081,3441,081,744Stata matrices 00ado-files34,50534,505Stored results 00Mata matrices 00Mata functions 0set maxvar usage 5,281,7385,281,738Other 2,8412,841Total7,251,97673,701,619See [D ]memory .6.5Setting aside memory for temporary storage of preserved datasetsStata has a feature to preserve and restore datasets,allowing you to manipulate the data during an analysis and bring them back without harm.Stata/MP uses memory to make copies of these datasets as fast as possible.Stata/SE and Stata/BE make the copies on disk.To control the amount of memory Stata/MP will use for these temporary dataset copies before it falls back to slower disk storage,use the set max preservemem setting.See [P ]preserve for more details.Stata,Stata Press,and Mata are registered trademarks of StataCorp LLC.Stata and Stata Press are registered trademarks with the World Intellectual Property Organization of the United Nations.Other brand and product names are registered trademarks ortrademarks of their respective companies.Copyright c1985–2023StataCorp LLC,College Station,TX,USA.All rights reserved.®。
计算机导论题库_新
8578Which of the following is not contained in a CPU?8678Which of the following instructions (as described in the language description table) changes the contents of a memory cell?8778Which of the following instructions (as described in the language description table) places 00000000 in register A?8878Which of the following instructions (as described in the language description table) places 00000000 in register 5?8978Which of the following instructions (as described in the language description table) will not change the contents of register 5?9078Which of the following instructions (as described in the language description table) is equivalent to requesting that register A be rotated to the left by three bits?9178Which of the following instructions (as described in the language description table) changes the contents of register 7?9278Which of the following instructions does not fall in the category of arithmetic/logic instructions?9378Which of the following instructions falls in the category of data transfer instructions?9478Which of the following is not an activity performed entirely within a CPU?9578What mask in register F would cause the instruction 8AAF (refer to the language description table) to put a 0 in the most significant bit of register A without disturbing the other bits?9678What mask in register F would cause the instruction 7AAF (refer to the language description table) to put a 1 in the most significant bit of register A without disturbing the other bits?9778Which of the following instructions will not produce the same result as the other two? (Refer to the language description table.)9878Which of the following instructions will not produce the same result as the other two? (Refer to the language description table.)9978If register A contained the pattern 00000000, which of the following instructions could alter the contents of register 0? (Refer to the language description table.)10078Which of the following instructions (as described in the language description table) is essentially an unconditional jump?10178为了保证程序能连续执行,CPU必须确定下一条指令的地址,起到这一作用的是_____。
Sendyne SIM100MOD 隔离监控器安全指南说明书
Safety Manual for Sendyne SIM100MOD Isolation MonitorThis document describes how to use the Sendyne SIM100MOD isolation monitor in a safety related system. ContentsSafety Manual for Sendyne SIM100MOD Isolation Monitor 1Introduction (2)Sendyne SIM100MOD overview (2)Safety functions and diagnostics overview (3)Target applications (4)Assumptions (6)Custom development (6)Safety documentation (6)Audits and certification (6)Device operating states (6)Product lifecycle support (7)Appendix (8)Proper connection to the target system (8)Revision history (10)List of figuresFigure 1: SIM100MOD functional diagram (3)Figure 2: The boundary diagram of SIM100MOD as SEooC in EV implementations (4)Figure 3: The boundary diagram of SIM100MOD as SEooC in EV implementations (5)Figure 4: Operating states of the SIM100MOD (7)Figure 5: Proper connection to IT power system terminals (8)Figure 6: Proper connection at two distinct point to the chassis (8)Figure 7: Presence of Y-capacitors is a requirement for proper function of the SIM100MOD. (9)IntroductionThe system and equipment manufacturer or designer intending to use this product is responsible to ensure that their system incorporating Sendyne’s SIM100MOD meet all applicable safety, regulatory and system level performance requirements. All information presented in this document is for reference only. Users understand and agree that their use of SIM100MOD in safety-critical applications is entirely at their risk, and that user (as buyer) agrees to defend, indemnify, and hold harmless Sendyne from any and all damages, claims, suits, or expense resulting from such use.This safety manual provides information to assist system developers in creating safety-related systems incorporating the Sendyne SIM100MOD isolation monitoring device. This document contains:•Overview of the SIM100MOD architecture•Overview of the safety architecture for management of hardware failures•Assumptions of UseSendyne assumes that the user of this document has a general familiarity of the SIM100MOD. This document is intended to be used in conjunction with the relevant datasheet and application notes.Sendyne SIM100MOD overviewThe SIM100MOD is an electrically isolated device that when connected properly to an idle or active high voltage IT power system (floating ground) can estimate the resistive and capacitive paths between each power rail of the IT system and a third reference point. The SIM100MOD can communicate through CAN bus (250 or 500 kbits/s) and when interrogated by a host it can provide estimates on the values of each resistive and capacitive path.The SIM100MOD, based on information programmed by the host for the designed maximum voltage of the IT power system, will calculate a value for the minimum resistance path between the two IT power system rails and the third voltage reference point, expressed in Ohms/Volt (max designed voltage). In addition, it will estimate the total energy that can be potentially stored in the IT power system capacitances. If the CAN bus host fails to provide information on the maximum IT power system voltage, the SIM100MOD will calculate these values based on the maximum voltage observed during its operation.The SIM100MOD power input accepts any supply voltage between 4.8 V and 53 V. The input voltage is pre-regulated and then stepped down through a DC/DC converter feeding through galvanically isolated inputs the +5 V IC supply and the 12.5 V excitation voltage source supply.The SIM100MOD safety architecture includes a watchdog timer, CRC check on internal non-volatile program memory, diagnostics for proper connections of chassis and IT power system terminals, monitoring of the unregulated power supply voltage level for the main IC before local voltage regulator (LDO), environment temperature monitoring and excitation pulse voltage monitoring. In addition, theSIM100MOD safety architecture monitors the voltage divider values for chassis, positive and negative voltage connections and provides a visual heartbeat signal indicating proper IC operation.All estimates of isolation resistances and capacitances are submitted along with an uncertainty percentage value. This value defines the interval within which the actual value lies with a probability of 95%.Figure 1: SIM100MOD functional diagramSafety functions and diagnostics overviewThe SIM100MOD is intended for use in automotive and industrial safety-relevant applications. All components used are automotive rated.HardwareThe following list of monitoring functions are implemented in the SIM100MOD.•V U, SUPPLY monitor•V X, SUPPLY monitor•V X1 connection monitor•V X2 connection monitor•V X1 voltage divider ratio monitor•V X2 voltage divider ratio monitor•V CH1 and V CH2 connections monitor•V X_CH voltage divider ratio monitor•V X_CH Excitation Voltage Source voltage value monitor•V X_THR environment temperature monitorUpon diagnosing a hardware error, the SIM100MOD will set the appropriate flags and enter a SAFE state.SoftwareOn the RESET state the SIM100MOD performs CRC check on the non-volatile memory. During active operation a watchdog timer ensures proper program flow. In addition, every estimate on the isolation state of the monitored IT power system is accompanied by the uncertainty value of this estimate.Target applicationsThe Sendyne SIM100MOD has been designed to be used as an element for the isolation safety system in applications such as:•Automotive•Charging stations•Industrial high voltage ungrounded systemsFig. 2 and Fig. 3 show the boundary diagram for the SIM100MOD as a SEooC (Safety Element out of Context) in two different applications.Figure 2: The boundary diagram of SIM100MOD as SEooC in EV implementationsFigure 3: The boundary diagram of SIM100MOD as SEooC in EV implementationsAssumptionsThe following table lists the assumptions made for safe employment of the SIM100MOD is a safety critical system.ID Type Assumed RequirementAR01 Assumed Requirement The SEooC is defined as the SIM100MOD playing a role as an isolationmonitoring element as shown in Fig. 2 and Fig. 3AR02 Assumed Requirement Thermal environment is between -40 o C and +105 o C (Temperature range islimited by connector thermal specifications. For SIM100MODAZ1, operatingrange is -40 o C to +125 o C )AR03 Assumed Requirement The IT Power System voltage monitored by the SIM100MOD will varybetween 15 V and 962 VAR04 Assumed Requirement The IT Power System is connected to chassis through Y-Capacitors of at least100 nF on each side of the power supplyAR05 Assumed Requirement The SIM100MOD-xxx is supplied with proper power according to thespecifications of the SIM100MOD datasheetAR06 Assumed Requirement Safety Integrity Level is ASIL BAR07 Assumed Requirement No other isolation monitoring device is active in the monitored system Table 1: Assumed Requirements for SIM100MOD as a SEooCCustom developmentThe SIM100MOD has been developed as a safety element out of context and it is offered as a commercial off-the-shelf product. Safety requirements used were based on Sendyne’s understanding of the safety requirements of potential applications. Sendyne can customize the product in order to meet specific customer safety requirements through a development interface agreement (DIA). To request customization contact ****************Safety documentationVerification and validation of the SIM100MOD safety features was performed through testing and computer simulation. Results of SIM100MOD testing following guidelines of different standards as well as the model used for SIM100MOD safety function testing can be made available at Sendyne’s discretion under an NDA (non-disclosure agreement)Audits and certificationSendyne has no plans to perform an external audit of the SIM100MOD to ISO 26262 or other standards. Documentation, including this manual can be made available to support customer system audit and certification. Forward any request for an independent audit to your sales contact or ****************. Device operating statesFig. 3 shows an overview of the operating states of SIM100MOD. Refer to the product datasheet and other documentation for details.Figure 4: Operating states of the SIM100MODProduct lifecycle supportThe SIM100MOD contains a safe bootloader capable of field upgrades through the CAN bus interface.AppendixProper connection to the target systemConnection to the IT power systemFigure 5: Proper connection to IT power system terminalsConnection to chassisThe SIM100MOD should connect through J1 at two separate chassis points. The SIM100MOD relies on this type of connection to detect proper connection to the chassis. If both leads from J1 are connected to the same point there is a possibility of an undetected disconnection. Such an event will jeopardize theSIM100MOD safety function.Figure 6: Proper connection at two distinct point to the chassisPresence of Y-capacitorsThe SIM100MOD relies on the presence of the ubiquitous Y-capacitors to perform its safety function. Absence of Y-capacitors with a minimum value of 100 nF will flag a connection error and lead theSIM100MOD into the SAFE state.Figure 7: Presence of Y-capacitors is a requirement for proper function of the SIM100MOD. The capacitors should be connected directly to the power lines. Connecting them on the SIM100MOD boardinstead would impair the ability of the monitor to detect disconnection from the monitored IT power lines.Revision historyDate Revision Changes11/15/2018 0.1 Initial release1/17/2019 0.2 Added image for proper connection of Y capacitors2/11/2019 0.2a Added image for isolation monitoring in charging stations. Addedassumed requirement for no other active isolation monitoring device in theIT power systemTable 2: Document revision historyInformation contained in this publication regarding device applications and the like, is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications.SENDYNE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESSED OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Sendyne disclaims all liability arising from this in-formation and its use. Use of Sendyne devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemni-fy and hold harmless Sendyne from any and all dam-ages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Sendyne intellectual property rights.。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
T-SIX:An Indexing System for XML SiblingsSungRan ChoL3S,University of Hannoverscho@l3s.deABSTRACTWe present a system for efficient indexed querying of XML doc-uments,enhanced with sibling operations.R-tree index proposed in[5]has a very high cost for the following-sibling and preceding-sibling axes.We develop a family of index structures,which we refer to as transformed split-tree indexes,to address this problem, in which(i)XML data is horizontally split by a simple,yet efficient criteria,(ii)the split value is associated with tree labeling,(iii)all data elements are transformed into new dimensions to avoid possi-ble overlap between bounding boxes representing data elements in the split tree.The T-SIX system incorporates building transformed split-tree index for XML documents as well as query processing on all XPath axes to provide query answers.1.INTRODUCTIONEfficient querying XML documents is an increasingly important is-sue considering the fact that XML becomes the de facto standard for data representation and exchange over the Web,and XML data in diverse data sources and applications is growing rapidly in size. Given the importance of XPath based query access,XML query evaluation engines need to be able to efficiently identify the ele-ments along each location step in the XPath query.In this context, several index structures for XML documents have been proposed [4,5,7,8,10],in a way to efficiently querying XML documents. As XML documents are modeled by a tree structure,a numbering scheme,labeling tree elements,allows for managing the hierarchy of XML data.For example,each element has the position,a pair of its beginning and end locations in a depthfirst search.In general, the numbering approach has the benefit of easily determining the ancestor-descendant relationship in a tree.In this respect,R-tree index using node’s preorder and postorder,we refer to as whole-tree indexes(WI),has been proposed in[5].Such index,however, does not consider issues related to the costs of the preceding-sibling and following-sibling axes.In this paper,we develop index techniques to reduce the cost of XML siblings.It also addresses an issue of what efficient pack-ing for XML tree data is.An efficient packing method for a tree Copyright is held by the author/owner.Eighth International Workshop on the Web and Databases(WebDB2005), June16-17,2005,Baltimore,Maryland.is not only to group together data elements which are close in a tree,but also to reduce dead space resulting in false positives(no data in indexed space).In the WI,packing method,taking a whole tree,may cover considerable dead space,which influences query-ing XML siblings.We design the transformed split-tree index to address the problem,in which(i)an XML tree is horizontally split by the simple,but efficient criteria,(ii)the split value is associated with tree labeling,(iii)all data elements are transformed into new dimensions to avoid possible overlap between bounding boxes rep-resenting data elements in the split tree.To take advantage of the semantics of the index structure,we develop novel index lookup algorithms for XPath axes for the transformed split-tree index. We describe T-SIX,a system for indexed querying enhanced with XML sibling operations.T-SIX incorporates tree labeling and co-ordinate transformation for XML documents.T-SIX implements novel index lookup algorithms for querying,providing query an-swers for the entire set of XPath query axes.This demonstration is organized as follows.Section2shows the architecture of T-SIX.Section3gives the structure of our index and describes functionality and features that T-SIX encompasses.2.Figure1:Architecture of T-SIXT-SIX is a Java-based prototype.Its architecture is depicted in Figure1.It consists of two main components:the transformed split-tree index management module and the XPath querying mod-ule.Thefirst component implements various aspects of managing transformed split-tree index including tree labeling and coordinate transformation.It accepts the split value of a tree through a graph-ical interface and builds the index based on the value.The secondcomponent implements a query processor on all XPath axes,that accepts queries and returns desired elements.3.DEMONSTRATION OUTLINEThe system encompasses the following functionality and features that will be demonstrated:(a)facilitates browsing of different XML data sets,(b)facilitates browsing of element’s original and trans-formed positional numbers,(c)incorporates building transformed split-tree index for XML data,(d)incorporates novel index lookup algorithms in the transformed split-tree index for XPath query process-ing,(e)implements aflexible and interactive graphical interface and display of queries and query results,(f)supportsflexible waysto input split value information for XML documents,and(g)sup-ports adjusting page size parameter of the index in an interactive mode.3.1Transformed Split-Tree Index Management Tree Labeling:We use an encoding scheme,Ln and Rn,for nodesin XML documents that has the same effect as preorder and pos-torder.Ln is the rank at which the node is encountered in a leftto right depthfirst search(DFS)of the XML data tree,and Rn is the rank at which the node is encountered in a right to left DFS.In order to handle level sensitive matching,such as child and parent axes(matching nodes one level apart),and following-sibling and preceding-sibling axes(matching nodes with the same parent),the parent node’s Ln,written as PLn is associated with each node.Thus each XML element node is labeled with three numbers:Ln,Rn, and PLn.These numbers become coordinates in multi-dimensions. Users can view element’s positional information,Ln,Rn,and PLn, through an interface.In Figure2,an example XML database rep-resents an e-store that contains information about items and clients.Split Value Specification:XML documents can be selected and browsed in graphical form.XML element nodes are labeled with element tags or string values;edges are either between elements or between an element and a string value.Once XML documentis selected,a user can specify the split value,which is associated with element’s Ln and Rn.In effect XML data tree is divided hor-izontally by the split value.T-SIX system provides conveniently visualize XML tree split.In Figure2,for example,once a user submits the split value of12,the e-store document is split by the value,in which e-store,toys,CDs,pop elements are cutin the XML tree and highlighted through a graphical interface.Split value information for XML documents can be dynamically modi-fied on demand.Transformation:While the separate packing reduces long thin boundary boxes,that may contain dead space(space which is in-dexed but does not have data),it causes the overlap between bound-ing boxes at each region of the tree.Due to overlap,multiple paths from the root downwards on the SI may need to be traversed, which results in increasing page accesses.Before building the in-dex,T-SIX transforms coordinates of element nodes to avoid possi-ble overlap.An element node n=(Ln,Rn,PLn)is transformed inton =(Ln ,Rn ,PLn ),such thatLn =LnRn =Ln+RnPLn =PLnFigure2:XML dataAs a result,the original dimensions are extended with in the Rn direction with respect to ers can view the transformed coor-dinate information of elements.Building Index:A transformed split-tree index is constructed on new dimensions(Ln ,Rn ,PLn ).T-SIX supports for loading new documents to construct the index in the hierarchical structure.Trans-formed split-tree index contents as well as index operations can be efficiently visualized in the ers can input the page ca-pacity through a graphical interface.Figure3,for example,shows a transformed split-tree index over the split e-store dataset of Figure2with a page capacity of2.The leaf pages in the index contain both leaf and non-leaf XML elements,and non-leaf index pages indicate page boundaries by the smallest and the largest val-ues occurring in the page.3.2XPath QueryingOnce an XML document to be queried is selected,users can spec-ify XPath queries through aflexible graphical interface.After a user query is submitted,T-SIX uses the transformed split-tree in-dex to return all relevant XML data.T-SIX system supports all XPath axes and provides various ways to conveniently visualize query results.In Figure3,for example,a user issues a query,“re-trieve all elements preceding the clinets element”.As a result, elements returned as well as non-leaf pages scanned in the index are highlighted in the graphical interface.The XML data tree also highlights the query results for easy understanding of XPath query operations.4.CONCLUSIONThe T-SIX system provides XPath querying enhanced with sibling operations.It supports novel transformed split-tree indexing meth-ods to facilitate query operations in XML documents and dynamic changes of split value information on the XML data tree.It ac-cepts XPath queries and displays query results through a graphical user interface.Furthermore,it supports dynamic visualization ofFigure3:XPath queryingthe index.5.REFERENCES[1]M.Altinel and M.Franklin.Efficientfiltering of XMLdocuments for selective dissemination of information.InProc.of VLDB,Cairo,Egypt,53–64,2000.[2]J.Clark and S.DeRose.XML path language(XPath)version1.0w3c recommendation,Technical ReportREC-xpath-19991116,World Wide Web Consortium,1999.[3]E.Cohen,H.Kaplan and beling dynamic XMLtrees,In Proc.of PODS,271–281,2002.[4]B.F.Copper,N.Sample,M.J.Franklin,G.R.Hjaltason andM.Shadmon.A fast index for semistructured data,In Proc.of VLDB,Rome,Italy,341–350,2001.[5]T.Grust.Accelerating XPath location steps,In Proc.ofSIGMOD,2002.[6]A.Guttman.R-trees:a dynamic index structure for spatialsearching,In Proc.of SIGMOD,45–47,1984.[7]Q.Li and B.Moon.Indexing and querying XML data forregular path expressions,In Proc.of VLDB,Rome,Italy,361–370,2001.[8]o and D.Suciu.Index structure for path expressions,InProc.of ICDT,Jerusalem,Israel,271–295,1999.[9]K.V.Ravikanth,D.Agrawal,A.E.Abbadi,A.K.Singh andT.Smith.Indexing hierarchical data,Univ.of California,CS-Tr-9514,1995.[10]H.Wang,S.Park,W.Fan and P.Yu.ViST:a dynamic indexmethod for querying XML data by tree structures,In Proc.of SIGMOD,San Diego,USA,2003.[11]H.V.Jagadish,S.Al-Khalifa,A.Chapman,kshmanan,A.Nierman,S.Paparizos,J.M.Patel,D.Srivastava,N.Wiwatwattana,Y.Wu,C.Yu,TIMBER:Anative XML database,VLDB Journal11(4):274-291,2002.[12]XQuery1.0:An XML query language,W3C Working Draft,November2002.[13]K.Deschler and E.Rundensteiner.MASS:A multi-axisstorage structure for large XML documents,In Proc.ofCIKM,Louisiana,USA,2003.。