The SIRF format enables long-term physical storage, cloud storage and tape-based containers effective and efficient ways to preserve and secure digital information for many decades, even with the ever-changing technology landscape. This SNIA Technical Position specifies the Self-contained Information Retention Format (SIRF) Level 1 and its serialization for LTFS, CDMI and OpenStack Swift.
Cloud Customer Architecture for API Management is an introduction to API Management and the architecture elements of an effective API Management Platform.
An API (Application Programming Interface) exposes defined business assets, data, or services for public consumption. APIs allow companies to open up data and services to create innovative channel applications that drive digital transformation. An effective API Management Platform provides a layer of controlled and secure self-service access to these core business assets for reuse.
This whitepaper describes the lifecycle approach to creating, running, managing and securing APIs. It covers the principles and characteristics of selecting an API Management Platform, as well as runtime
Cloud Customer Architecture for Big Data and Analytics describes the architectural elements and cloud components needed to build out big data and analytics solutions.
Big data analytics and cloud computing are a top priority for CIOs. Harnessing the value and power of big data and cloud computing can give your company a competitive advantage, spark new innovations, and increase revenue. Many companies are experimenting and iterating with different cloud configurations as a way to understand and refine requirements for their big data analytics solutions without upfront capital investment.
This whitepaper includes proven architecture patterns that have been deployed in successful enterprise projects and a description of capabilities offered by cloud providers.
Blockchain technology has the potential to have a major impact on how institutions process transactions and conduct business.
Blockchain technology provides a secure transaction ledger database through a decentralized network. It has the potential to reduce operational costs and friction, create transaction records that are secure and immutable, enable transparent ledgers with nearly instant updates, and open up new opportunities for growth.
This whitepaper introduces basic blockchain concepts that define a standard reference architecture that can be used in creating blockchain applications.
Sections of the paper include:
Blockchain fundamentals
Key characteristics of a blockchain network
Blockchain reference architecture capabilities
An example supply chain scenario using the Hyperledger Fabric blockchain implementation
Interoperability and Portability for Cloud Computing: A Guide was written to provide a clear definition of interoperability and portability and how these concepts relate to various aspects of cloud computing and to cloud services.
The aim of this guide is to give both cloud service customers and cloud service providers guidance in the provision and selection of cloud services indicating how interoperability and portability affect the cost, security, and risk involved.
Version 2.0 is updated to reflect the ISO/IEC 19941 Cloud Computing Interoperability and Portability standard and its facet models of interoperability, data portability, and application portability. Containers and their associated technologies are addressed in the paper, as well as automation in the use of cloud services.
Migrating Applications to Public Cloud Services: Roadmap for Success was written to provide a practical reference to help enterprise information technology (IT) and business decision makers analyze and consider application migration to the cloud. This paper details strategic and tactical activities for developing a business plan and detailed migration plan. Guidance is provided on the types of applications that are best suited for migration to the cloud.
Key considerations include costs of migration, the potential need for application redesign, longevity, performance and availability, security and privacy requirements, the selection of locations, and other potential regulatory requirements.
Version 2.0 takes into account the increasing diversity of approaches used to migrate applications to the cloud. Much of this focuses on the use of containers, virtual machines, and serverless functions, as well as on the increasing use of hybrid cloud solutions. Concerns related to security, privacy, and data residency have also become stronger since the initial version. The guide addresses how to mitigate those issues.
ISO 15118-8:2018 specifies the requirements of the physical and data link layer of a wireless High Level Communication (HLC) between Electric Vehicles (EV) and the Electric Vehicle Supply Equipment (EVSE). The wireless communication technology is used as an alternative to the wired communication technology as defined in ISO 15118‑3.
It covers the overall information exchange between all actors involved in the electrical energy exchange. ISO 15118 (all parts) are applicable for conductive charging as well as Wireless Power Transfer (WPT). For conductive charging, only EVSEs compliant with "IEC 61851‑1 modes 3 and 4" and supporting HLC are covered by this document. For WPT, charging sites according to IEC 61980 (all parts) and vehicles according to ISO/PAS 19363 are covered by this document.
ISO 15118-5:2018 specifies conformance tests in the form of an Abstract Test Suite (ATS) for a System Under Test (SUT) implementing an Electric Vehicle or Supply Equipment Communication Controller (EVCC or SECC) with support for PLC-based High Level Communication (HLC) and Basic Signaling according to ISO 15118‑3. These conformance tests specify the testing of capabilities and behaviors of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118‑3 and against what the implementer states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements defined in ISO 15118‑3. The behavior tests of the ATS examine an implementation as thoroughly as is practical over the full range of dynamic conformance requirements defined in ISO 15118‑3 and within the capabilities of the SUT (see NOTE 1). A test architecture is described in correspondence to the ATS. The conformance test cases in this part of the standard are described leveraging this test architecture and are specified in TTCN-3 Core Language for the ISO/OSI Physical and Data Link Layers (Layers 1 and 2). The conformance test cases for the ISO/OSI Network Layer (Layer 3) and above are described in ISO 15118‑4.
ISO 15118-4:2018 specifies conformance tests in the form of an Abstract Test Suite (ATS) for a System Under Test (SUT) implementing an EVCC or SECC according to ISO 15118-2.
These conformance tests specify the testing of capabilities and behaviors of an SUT as well as checking what is observed against the conformance requirements specified in ISO 15118-2 and against what the supplier states the SUT implementation's capabilities are. The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements defined in ISO 15118-2. The behavior tests of the ATS examine an implementation as thoroughly as is practical over the full range of dynamic conformance requirements defined in ISO 15118-2 and within the capabilities of the SUT (see NOTE). A test architecture is described in correspondence to the ATS. The conformance test cases in this document are described leveraging this test architecture and are specified in TTCN-3 Core Language for ISO/OSI Network Layer (Layer 3) and above. The conformance test cases for the Data Link Layer (Layer 2) and Physical Layer (Layer 1) are described in ISO 15118-5. Test cases with overlapping scopes are explicitly detailed.
ISO 15118-3:2015 specifies the requirements of the physical and data link layer for a high-level communication, directly between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV), termed as EV (electric vehicle) [ISO-1], based on a wired communication technology and the fixed electrical charging installation [Electric Vehicle Supply Equipment (EVSE)] used in addition to the basic signalling, as defined in [IEC-1].
It covers the overall information exchange between all actors involved in the electrical energy exchange. ISO 15118 (all parts) is applicable for manually connected conductive charging. Only "[IEC-1] modes 3 and 4" EVSEs, with a high-level communication module, are covered by this part of ISO 15118.
ISO 15118-2:2014 specifies the communication between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set defined in ISO 15118-2:2014 is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1 contains additional use case elements describing the bidirectional energy transfer. The implementation of these use cases requires enhancements of the application layer message set defined herein. The purpose of ISO 15118-2:2014 is to detail the communication between an EV (BEV or a PHEV) and an EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between EVCC and SECC. ISO 15118-2:2014 defines messages, data model, XML/EXI based data representation format, usage of V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from a layer 3 perspective. The Data Link Layer and Physical Layer functionality is described in ISO 15118-3.
This document, as a basis for the other parts of the ISO 15118 series, specifies terms and definitions, general requirements and use cases for conductive and wireless HLC between the EVCC and the SECC. This document is applicable to HLC involved in conductive and wireless power transfer technologies in the context of manual or automatic connection devices. This document is also applicable to energy transfer either from EV supply equipment to charge the EV battery or from EV battery to EV supply equipment in order to supply energy to home, to loads or to the grid. This document provides a general overview and a common understanding of aspects influencing identification, association, charge or discharge control and optimisation, payment, load levelling, cybersecurity and privacy. It offers an interoperable EV-EV supply equipment interface to all e-mobility actors beyond SECC. The ISO 15118 series does not specify the vehicle internal communication between battery and other internal equipment (beside some dedicated message elements related to the energy transfer).
