43.040.15 - Car informatics. On board computer systems
ICS 43.040.15 Details
Car informatics. On board computer systems
Kfz-Informatik. Bordcomputer
Informatique automobile. Systemes informatiques embarqués
Avtomobilska informatika. Vgrajeni računalniški sistemi
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 43.040.15 - Car informatics. On board computer systems
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document provides a common framework of definitions and measurement methods for the design, and ergonomics testing of automotive head-up displays (HUDs) independent of technologies except where noted. Applications in both passenger cars (including sport utility vehicles and light trucks) and commercial vehicles (including heavy trucks and buses) are covered. This document does not include helmet-mounted HUDs or other head carried gear such as glasses. Areas covered in this document include: — guidance on how to establish reference points and representative viewing conditions based on vehicle coordinates and ranges of driver's/passenger's eye points; — descriptions of the HUD image geometry and optical properties measurements; — definitions of the HUD virtual image and driver vision measurements; — static and dynamic laboratory tests, and dynamic field operational assessments that include suggested vehicle setup procedures in order to measure HUD image attributes.
- Technical specification76 pagesEnglish languagesale 15% off
- Draft76 pagesEnglish languagesale 15% off
- Draft76 pagesEnglish languagesale 15% off
It defines the test suite structure and the test purposes for conformity evaluation of on-board and roadside equipment designed for compliance with the requirements set up in EN 15509.
- Standard122 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft147 pagesEnglish languagesale 10% offe-Library read for1 day
This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available. This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.
- Standard344 pagesEnglish languagesale 15% off
- Draft345 pagesEnglish languagesale 15% off
- Draft345 pagesEnglish languagesale 15% off
This document addresses light-duty vehicles, such as passenger cars, pick-up trucks, light vans and sport utility vehicles (motorcycles excluded) equipped with Manoeuvring Aids for Low Speed Operation (MALSO) systems. It specifies the minimum functionality requirements which the driver can generally expect of the device, i.e. detection of and information on the presence of relevant obstacles within a defined (short) detection range. It defines minimum requirements for failure indication as well as performance test procedures; it includes rules for the general information strategy but does not restrict the kind of information or display system. MALSO systems use object-detection devices (sensors) for ranging in order to provide the driver with information based on the distance to obstacles. Although sensing technology is not addressed in this document, technology does affect the performance-test procedures set up in Clause 7. The current test objects are defined based on systems using ultrasonic sensors, which reflect the most commonly used technology at the time of publication. For other sensing technologies which will potentially emerge in the future, these test objects shall be checked and changed if required. Visibility-enhancement systems like video-camera aids without distance ranging and warning are not covered by this document. Reversing aids and obstacle-detection devices on heavy commercial vehicles are not addressed by this document.
- Standard21 pagesEnglish languagesale 15% off
- Draft21 pagesEnglish languagesale 15% off
This document specifies diagnostic application requirements and OSI-layer related communication profiles to ensure the interchange of digital information between towing and towed vehicles with a maximum authorized total mass greater than 3 500 kg. The conformance and interoperability test plans are not part of this document.
- Standard30 pagesEnglish languagesale 15% off
- Draft30 pagesEnglish languagesale 15% off
- Draft30 pagesEnglish languagesale 15% off
This document specifies the SAE J1939-based application layer, the payload of messages, and parameter groups for electronically controlled braking systems, including anti-lock braking systems (ABS), vehicle dynamics control systems (VDC), and running gears equipment, to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles. Conformance and interoperability test plans are not part of this document.
- Standard103 pagesEnglish languagesale 15% off
- Draft103 pagesEnglish languagesale 15% off
- Draft103 pagesEnglish languagesale 15% off
This document specifies requirements and recommendations for software update engineering for road vehicles on both the organizational and the project level. This document is applicable to road vehicles whose software can be updated. The requirements and recommendations in this document apply to vehicles, vehicle systems, ECUs, infrastructure, and the assembly and deployment of software update packages after the initial development. This document is applicable to organizations involved in software update engineering for road vehicles. Such organizations can include vehicle manufacturers, suppliers, and their subsidiaries or partners. This document establishes a common understanding for communicating and managing activities and responsibilities among organizations and related parties. The development of software for vehicle functions, except for software update engineering, is outside the scope of this document. Finally, this document does not prescribe specific technologies or solutions for software update engineering.
- Standard24 pagesEnglish languagesale 15% off
- Standard24 pagesEnglish languagesale 15% off
IEC 63005-2:2019 describes test methods on evaluating performance of basic functionalities of EVDR described in IEC 63005-1.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft17 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies measurement methods for the surround view system that is specified in IEC 63033-1.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft17 pagesEnglish languagesale 10% offe-Library read for1 day
IEC TR 63246-4:2022 describes the CCIS protocol, which includes the protocol messages, parameters and procedures performed by protocol entities. This part is informative; its intent is to provide information that can be considered in order to implement the CCIS protocol.
- Technical report27 pagesEnglish languagesale 15% off
ISO 15118-9:2022 This document 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 WLAN-based high-level communication (HLC) according to ISO 15118‑8 and against the background of ISO 15118-1. These conformance tests specify the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118‑8 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‑8. The behaviour tests of the ATS examine an implementation as thoroughly as practical over the full range of dynamic conformance requirements defined in ISO 15118‑8 and within the capabilities of the SUT (see NOTE below).
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are described leveraging this test architecture and are specified in descriptive tabular format for the ISO/OSI physical and data link layers (layers 1 and 2).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118‑8. This document can additionally refer to specific tests for requirements on referenced standards (e.g. IEEE, or industry consortia standards, like WiFi Alliance) as long as they are relevant in terms of conformance for implementations according to ISO 15118‑8. However, it is explicitly not intended to widen the scope of this conformance specification to such external standards, if it is not technically necessary for the purpose of conformance testing for ISO 15118‑8. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, nor the environment of the protocol implementation. Furthermore, the abstract test cases defined in this document only consider the communication protocol and the system's behaviour defined ISO 15118‑8. The power flow between the EVSE and the EV is not considered.
NOTE Practical limitations make it impossible to define an exhaustive test suite, and economic considerations can restrict testing even further. Hence, the purpose of this document is to increase the probability that different implementations are able to interwork. This is achieved by verifying them by means of a protocol test suite, thereby increasing the confidence that each implementation conforms to the protocol specification. However, the specified protocol test suite cannot guarantee conformance to the specification since it detects errors rather than their absence. Thus, conformance to a test suite alone cannot guarantee interworking. Instead, it gives confidence that an implementation has the required capabilities and that its behaviour conforms consistently in representative instances of communication.
- Standard72 pagesEnglish languagesale 15% off
This part of IEC 63033 specifies recording methods of the surround view system that is specified in IEC 63033-1 in order to view the recorded video file with free eye point technology.
- Standard13 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft10 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies that is the multiple camera composite images generated by the surround view system of IEC 63033-1 is applied to the FOV and display requirement specified UN Regulation No. 46.
- Standard21 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 63033 specifies the model for generating the surrounding visual image of the surround view system.
- Standard27 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft26 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 63246 specifies the CCIS requirements, which include the general, functional and service requirements for CCIS.
- Standard16 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft12 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63033-3:2019 specifies measurement methods for the drive monitoring system that is specified in IEC TS 63033-1:2017.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft18 pagesEnglish languagesale 10% offe-Library read for1 day
In respect of 112-eCall (operating requirements defined in EN 16072), this document defines adaptations to eCall specifications defined in EN 16072 and other related documents to enable the provision of eCall for Powered Two Wheel Vehicles.
As with the existing provisions for eCall for Category M1/N1 vehicles, these are specified within the paradigm of being OEM fit equipment supplied with new vehicles.
For the purposes of the present document, the P2WV ‘L’ categories, as defined in Directive 2002/24/EC, Regulation (EU) No 168/2013, UNECE and as referenced/specified in EN 15722 apply.
This document includes only the requirements for Category L1 and L3 P2WV (vehicle based) with the exception of L1e-A (powered cycle), although other documents may subject other ‘L’ subcategories to use this document. Other Technical Specifications may be prepared for other UNECE category ‘L’ variants.
This document is a revision of CEN/TS 17249-5:2019 based on results achieved in sAFE project (sub-activity 3.5) [11] to obtain a specification allowing a more practical implementation of eCall for P2WVs.
The specifications herein relate only to the provision of pan-European eCall, and does not provide specifications for third party service provision of eCall. Other than in the 112-eCall paradigm, which involves a direct call from the vehicle to the most appropriate PSAP, third party service provision involves the support of an intermediary third party service provider before the call is forwarded to the PSAP.
NOTE The provision of eCall for vehicles via the aftermarket (post sales and registration), and the operational requirements for any such aftermarket solution. will be the subject of other work, that will use the specifications of this document as a principle reference point.
- Technical specification18 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines the OTX core requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in the requirements section. The data model specification aims at an exhaustive definition of all OTX core features implemented to satisfy the core requirements. Since OTX is designed for describing test sequences, which themselves represent a kind of program, the core data model follows the basic concepts common to most programming languages. Thus, this document establishes rules for syntactical entities like parameterised procedures, constant and variable declarations, data types, basic arithmetic, logic and string operations, flow control statements like loop, branch or return, simple statements like assignment or procedure call as well as exception handling mechanisms. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents are interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions. With respect to documentation use cases, special attention is paid to defining a specification/realisation concept (which allows for “hybrid” test sequences: human readable test sequences that are at the same time machine-readable) and so-called floating comments (which can refer to more than one node of the sequence). The core data model does not define any statements, expressions or data types that are dependent on a specific area of application. For the convenience of the user, the ISO 13209-2 OTX XML schema definition file (XSD) is published alongside this document.
- Standard191 pagesEnglish languagesale 15% off
This document defines the Open Test sequence eXchange (OTX) extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. This document establishes rules for the syntactical entities of each extension. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents containing extension features are to be interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.
- Standard228 pagesEnglish languagesale 15% off
This document specifies the diagnostic protocol data unit application programming interface (D‑PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. This document covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI module description files accompany this document. The purpose of this document is to ensure that diagnostic and reprogramming applications from any vehicle or tool manufacturer can operate on a common software interface and can easily exchange MVCI protocol module implementations.
- Standard434 pagesEnglish languagesale 15% off
This document specifies the communication between the electric vehicle (EV), including battery electric
vehicle (BEV) and plug-in hybrid electric vehicle (PHEV), and the electric vehicle supply equipment
(EVSE). The application layer messages defined in this document are designed to support the electricity
power transfer between an EV and an EVSE.
This document defines the communication messages and sequence requirements for bidirectional power
transfer.
This document furthermore defines requirements of wireless communication for both conductive
charging and wireless charging as well as communication requirements for automatic connection device
and information services about charging and control status.
The purpose of this document is to detail the communication between an electric vehicle communication
controller (EVCC) and a supply equipment communication controller (SECC). Aspects are specified to
detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication
between the EVCC and the SECC.
This document defines messages, data model, XML/EXI-based data representation format, usage of
V2GTP, TLS, TCP and IPv6. These requirements belong to the 3rd until the 7th OSI layer model. In addition,
the document describes main service sequences of conductive charging, wireless power transfer and
bidirectional power transfer, and how data link layer services can be accessed from an OSI layer 3
perspective.
- Standard570 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft571 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a method for the determination of fuel consumption and resulting CO2 emissions to enable fleet managers to reduce fuel costs and greenhouse gas (GHG) emissions in a sustainable manner. The fuel consumption determination is achieved by extracting trip data and speed profiles from the global navigation satellite system (GNSS) receiver of a nomadic device (ND), by sending it via mobile communication to a database server and by calculating the deviation of the mechanical energy contributions of: a) aerodynamics, b) rolling friction, c) acceleration/braking, d) slope resistance, and e) standstill, relative to a given reference driving cycle in [%]. As the mechanical energy consumption of the reference cycle is known by measurement with a set of static vehicle configuration parameters, the methodology enables drivers, fleet managers or logistics service providers to calculate and analyse fuel consumption and CO2 emissions per trip by simply collecting trip data with a GNSS receiver included in an ND inside a moving vehicle. In addition to the on-trip and post-trip monitoring of energy consumption (fuel, CO2), the solution also provides information about eco-friendly driving behaviour and road conditions for better ex-ante and ex-post trip planning. Therefore, the solution also allows floating cars to evaluate the impact of specific traffic management actions taken by public authorities with the objective of achieving GHG reductions within a given road network. The ND is not aware of the characteristics of the vehicle. The connection between dynamic data collected by the ND and the static vehicle configuration parameters is out of scope of this document. This connection is implementation-dependent for a software or application using the described methodology which includes static vehicle parameters and dynamic speed profiles per second from the ND. Considerations of privacy and data protection of the data collected by a ND are not within the scope of this document, which only describes the methodology based on such data. However, software and application developers using the methodology need to carefully consider those issues. Nowadays, most countries and companies are required to be compliant with strict and transparent local regulations on privacy and to have the corresponding approval boards and certification regulations in force before bringing new products to the market.
- Standard31 pagesEnglish languagesale 15% off
This document specifies measurement methods for the surround view system that is specified in IEC 63033-1.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft17 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 63033 specifies recording methods of the surround view system that is specified in IEC 63033-1 in order to view the recorded video file with free eye point technology.
- Standard13 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft10 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 63033 specifies the model for generating the surrounding visual image of the surround view system.
- Standard27 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft26 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies that is the multiple camera composite images generated by the surround view system of IEC 63033-1 is applied to the FOV and display requirement specified UN Regulation No. 46.
- Standard21 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63033-2:2022 is available as IEC 63033-2:2022 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 63033-2:2022 specifies recording methods of the surround view system that is specified in IEC 63033-1 in order to view the video file recorded with "free eye point" technology. IEC 63033-2:2022 cancels and replaces the first edition published in 2018. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) updates to the text and the title to reflect the change of the scope of the IEC 63033 series.
- Standard20 pagesEnglish and French languagesale 15% off
IEC 63033-3:2022 is available as IEC 63033-3:2022 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 63033-3:2022 specifies measurement methods for the surround view system specified in IEC 63033-1. IEC 63033-3:2022 cancels and replaces the first edition published in 2019. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) updates to the text and the title to reflect the change of the scope of the IEC 63033 series.
- Standard33 pagesEnglish and French languagesale 15% off
IEC 63033-1:2022 specifies the model for generating the surrounding visual image of the surround view system.
IEC 63033-1:2022 cancels and replaces IEC TS 63033-1 published in 2017. This edition constitutes a technical revision.
- Standard49 pagesEnglish and French languagesale 15% off
IEC 63033-4:2022 specifies which composite images generated from the multiple cameras of the surround view system specified in IEC 63033-1 comprise the FOV, and which display requirements specified in UN Regulation No. 46 apply.
- Standard36 pagesEnglish and French languagesale 15% off
This part of IEC 63246 describes the CCIS framework, which includes the information flows for registration, device monitoring and control, and content delivery between CCIS functional entities.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft14 pagesEnglish languagesale 10% offe-Library read for1 day
In addition to the guidelines in ISO 19011, this document provides guidelines to organizations that contribute to the achievement of road vehicle cybersecurity throughout the supply chain on: — managing an audit programme for a cybersecurity management system (CSMS); — conducting organizational CSMS audits; — competencies of CSMS auditors; and — providing evidence during CSMS audits. Elements of the CSMS are based on the processes described in ISO/SAE 21434. This document is applicable to those needing to understand or conduct internal or external audits of a CSMS or to manage a CSMS audit programme. This document does not provide guidelines on cybersecurity assessments.
- Technical specification21 pagesEnglish languagesale 15% off
This part of IEC 63246 describes the general considerations of CCIS, which include the system
model of the CCIS and the types of CCIS clients with the associated service flows.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 63246 specifies the CCIS requirements, which include the general, functional and service requirements for CCIS.
- Standard16 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft12 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 63246 describes the CCIS framework, which includes the information flows for registration, device monitoring and control, and content delivery between CCIS functional entities.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft14 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the data structure and data exchange procedure related to micro mobility service applications utilizing a P-ITS-S (i.e. nomadic devices), including car sharing, parcel delivery and first-mile and last-mile connections. In addition, this document delivers related requirements for the development and operation of the service platform between nomadic devices and micro mobility with intelligent transport systems (ITS) technologies. This document defines a data structure and data exchange procedure based on the datasets and messages which are defined in ISO 22085-2.
- Standard36 pagesEnglish languagesale 15% off
- Draft36 pagesEnglish languagesale 15% off
This part of IEC 63033 specifies recording methods of the drive monitoring system that is specified in IEC TS 63033-1 in order to view the recorded video file with free eye point technology.
- Standard13 pagesEnglish languagesale 10% offe-Library read for1 day
This document includes technical requirements which are related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators.
This document specifies the minimum set of technical requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.
Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme.
This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [15].
- Standard41 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft42 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides a general overview and structure of each part of the ISO 18541 series. This document also describes the use cases applicable to the standardized access to automotive RMI. The use cases address real world scenarios (e.g. servicing vehicles) regarding the information access necessary to perform vehicle roadside assistance, inspection, diagnosis, repair and maintenance, including the updating and replacement of electronic control units (ECU).
Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme.
The RMI systems used by personnel to perform the services consist of:
— a web-based system, which provides access to RMI needed to perform the service(s);
— contact information for specific RMI;
— a security framework to protect access to security-related RMI (vehicle theft protection measures).
This document is applicable to light passenger vehicles and light commercial vehicles.
- Standard49 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft46 pagesEnglish languagesale 10% offe-Library read for1 day
This document includes functional user interface requirements related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators.
This document specifies all functional user interface requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.
- Standard21 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft18 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a conformance test for a vehicle manufacturer assessment of self-conformance of the VM RMI system. The conformance test cases follow the use case definition of ISO 18541‑1 and the requirements stated in ISO 18541‑2 and ISO 18541‑3.
The primary, but not exclusive, purpose of this document is to provide information to the VM RMI system provider to build and test the VM RMI system against the conformance test cases. This final step in the development process of the VM RMI system is an enabler for all providers that their VM RMI system meets a high degree of functional requirements expected by the end user.
Furthermore, this document defines in Annex A conformance test cases for the use cases and requirements versions that apply for granting access to security-related RMI following the SERMI scheme.
This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [9].
- Standard93 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft90 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines how to authenticate users and accessing parties on a web-services interface. It also defines how a resource owner can delegate access to its resources to an accessing party. Within this context, this document also defines the necessary roles and required separation of duties between these in order to fulfil requirements stated on security, data privacy and data protection. All conditions and dependencies of the roles are defined towards a reference implementation using OAuth 2.0 compatible framework and OpenID Connect 1.0 compatible framework.
- Standard24 pagesEnglish languagesale 15% off
- Draft25 pagesEnglish languagesale 15% off
This document states the minimum requirements, recommendations, permissions and possibilities for ensuring interoperable web services from an accessing party’s perspective. The document: — states requirements on the structure and format of resources; — defines the concept of resource identifiers (direct and correlated); — provides different resource categories (e.g. anonymous, pseudonymized, technical, and personal resources); — provides different approaches on how to bundle shareable resources (e.g. resource group or container); — contains guidelines on how to define the unique resources of an individual application; — defines the entities and roles, necessary for granting an accessing party access to resource owner’s resources; — states requirements on how an accessing party accesses resources, including requirements on how to use the defined and referenced technologies, see Table 1. See Annex A for additional information about roles and responsibilities covered by ISO 20078 series.
- Standard19 pagesEnglish languagesale 15% off
- Draft19 pagesEnglish languagesale 15% off
This document defines how to access resources on a web-services interface of an offering party using the Hypertext Transfer Protocol Secure (HTTPS). Resources can be accessed through request/reply and/or requested to be pushed. The Representational State Transfer (REST) architectural pattern is chosen as a common way to format resource paths both for request/reply and push. Some specific extensions to this pattern are defined to allow for asynchronous resource requests, such as, for example, forcing readouts of data from a connected vehicle.
- Standard66 pagesEnglish languagesale 15% off
- Draft66 pagesEnglish languagesale 15% off
This document describes tests which verify on-board unit (OBU) conformance of functions and data structures implementations, as defined in the implementation conformance statement (ICS) based on ISO 14906 for EFC applications.
This document defines tests for assessing OBU conformance in terms of :
— basic dedicated short-range communication (DSRC) L7 functionality,
— EFC application functions,
— EFC attributes (i.e. EFC application information),
— the addressing procedures of EFC attributes and (hardware) components,
— the EFC transaction model, which defines the common elements and steps of any EFC transaction, and
— the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface level.
After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing a complete EFC transaction (C.3). Although this document defines examples of test cases for DSRC and EFC functionality (see Annex C), it does not intend to specify a complete test suite for a certain implementation. To compose a test suite for a specific EFC implementation, the test cases can be modified and new test cases can be defined and added in order for the conformance test suite to be complete. It can be useful to consider the following when defining a complete test suite:
— small range: "exhaustive testing" of critical interoperability/compatibility features,
— large range: testing of boundaries and random values, and
— composite types: testing of individual items in sequence or parallel.
This document does not define tests which assess:
— performance,
— robustness, and
— reliability of an implementation.
NOTE 1 ISO 14907‑1 defines test procedures that are aimed at assessing performance, robustness and reliability of EFC equipment and systems.
NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and related devices that can be relevant for OBUs which support such cards.
Annex D provides an informative overview of Japanese on-board equipment (OBE) conformance tests which are based on the ISO 14907 series, in order to illustrate how these can be applied in practice.
- Standard85 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft86 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes the processes of an offering party’s implementation to provide (ISO 20078‑2) access-controlled (ISO 20078-3) resources (ISO 20078‑1) to accessing parties. The processes are summarized as: registration of different stakeholder as well as granting, denying and revoking of access to resources. Those processes are held as examples of combining ISO 20078‑1, ISO 20078‑2 and ISO 20078‑3 and can vary depending on the actual implementation of the offering party.
- Technical report21 pagesEnglish languagesale 15% off
- Draft21 pagesEnglish languagesale 15% off
IEC 63246-1:2021 describes the general considerations of CCIS, which include the system model of the CCIS and the types of CCIS clients with the associated service flows.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the requirements related to the connection between the external test equipment externally connected to the diagnostic link connector and the in-vehicle CAN network to successfully establish, maintain and terminate communication.
- Standard17 pagesEnglish languagesale 15% off
- Draft17 pagesEnglish languagesale 15% off
This document specifies engineering requirements for cybersecurity risk management regarding concept, product development, production, operation, maintenance and decommissioning of electrical and electronic (E/E) systems in road vehicles, including their components and interfaces. A framework is defined that includes requirements for cybersecurity processes and a common language for communicating and managing cybersecurity risk. This document is applicable to series production road vehicle E/E systems, including their components and interfaces, whose development or modification began after the publication of this document. This document does not prescribe specific technology or solutions related to cybersecurity.
- Standard81 pagesEnglish languagesale 15% off
- Draft81 pagesEnglish languagesale 15% off
IEC 63246-1:2021 describes the general considerations of CCIS, which include the system model of the CCIS and the types of CCIS clients with the associated service flows.
- Standard37 pagesEnglish and French languagesale 15% off