hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 3.1 Terms | Void. |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 3.2 Symbols | Void. |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Alternating Current AES Advanced Encryption Standard AP Access Point DC Direct Current F5G Fifth Generation Fixed Network FDU Fibre Distribution Unit FTTP Fibre-To-The-Premises FTTR Fibre To The Room HFC Hybrid Fiber Coax IFDN In-premises F... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 4.1 FTTR for home area networking | The development of fixed networks, driven by service requirements and supported by technology development, has experienced era of voice, web, video, and 4K ultra-high definition. The Fifth Generation Fixed network (F5G) is represented by technologies such as 10G PON, Wi-Fi® 6, 200G/400G, and next-generation OTN. ETSI E... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 4.2 FTTR for small and medium-sized enterprises networking | More and more Small and Medium-sized Enterprises (SME) are integrating digital and intelligent tools into their offices and services. All industries are actively embracing innovation technologies such as the Internet, big data, and cloud computing to enhance their market competitiveness and improve operation indicators... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 5.1 Energy consumption analyse of FTTR system | Energy consumption refers to all energy used to access and utilise a service via the in-premises network. As in-premises Wi-Fi® is not impacted by the networking technology used, this clause will analyse the power consumption of different backhauling solutions. There are mainly 2 parts that contribute to the total powe... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 5.2 Environmental impacts analyse of FTTR system | Ethernet cables or coaxial cables are made of copper. The transmission performance of copper-based cables deteriorates under high-temperatures and in high-humid environments. Optical fibre is made of silica. Optical fibre is oxidation , and corrosion resistant . The diameter of optical fibre is 125 µm which is much sma... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 5.3 Security analyse of FTTR system | The security of the network includes the security of the network infrastructures and the security of the user data. For an in-premises network, the devices and transmission medium of the network are inside the users' building. and an attacker cannot connect a malicious device to the network without the users' knowledge... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.1 Topology of FTTR system | The FTTR network includes a Main FTTR Unit (MFU), In-premises Fibre Distributed Network (IFDN), and Sub FTTR Units (SFUs). The MFU is directly connected to an access network through a PON system, and MFU is connected to SFUs through IFDN. The MFU and SFUs can provide wireless and wired network interface for users' term... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.2 System design of IFDN | |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.2.1 General requirements | The IFDN of the FTTR system consists of an in-premises optical cable, an optical splitter and a fibre socket. As the lead-in optical cable of the access network is terminated at the multi-medium access box, the main FTTR unit can be deployed at the multi-medium access box at the beginning of the IFDN. Deployed in the l... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.2.2 Planning of IFDN | The planning of IFDN is subject to active FTTR devices. Each device of the FTTR system is recommended to be located according to the types of building such as residential buildings and commercial buildings. The deployments of active FTTR devices are recommended with the following regulations: 1) Main FTTR unit: a) For ... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.3 Optical component requirements | |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.3.1 Fibre cable | For in-premises fibre distribution network, different types of fibre cable such as multi-core or single core optical fibre, transparent optical cables, and optical/electrical hybrid fibre cables can be used. The selection of optical fibre shall meet the following requirements: 1) Recommendation ITU-T G.652 [1] optical ... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.3.2 Fibre connector | The connector shall match the type of the cable and shall meet the following requirements: 1) The type of the optical fibre connector should match the type of optical fibre, and SC, LC or other micro fibre connectors are recommended. 2) Optical/electrical hybrid cables shall be terminated by optical/electrical composit... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 6.3.3 Optical splitter | Optical splitters with asymmetric splitting ratio are recommended for FTTR system: 1) The cascaded extension link of optical splitters should be connected by single core fibre, and normally should not exceed three stages (including main optical splitter and extended optical splitters). 2) If optical/electrical hybrid f... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 7 Installation and deployment of fibre network | |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 7.1 Distribution pipe network design | The distribution pipeline network of the FTTR system shall follow the following recommendations: 1) The pipeline network of FTTR system shall be coordinated with the generic cabling system in the building. 2) Distribution ducts shall be safe and economical, and with short routing path. 3) Pipeline and trough boxes shal... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 7.2 Equipment Installation Requirements | According to the application scenario, the FTTR devices can be installed on the wall, on the ceiling, on the desktop or in embedded multi-medium access box. Indoor fibre distribution equipment shall include distribution cabinets and wall-mounted distribution boxes. Installation positions shall meet the following requir... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 7.3 In-premises Fibre Cabling Recommendations | Pre-connectorized optical fibre cable can be used for quick in-premises installation. Indoor optical fibre can also be can also be terminated by splicing onsite which should meet the following requirements: 1) Optical fibre should be protected at the splicing point. 2) It is recommended that pigtails (with connectors) ... |
ebcf585fa5170c3654956a3bcb309d45 | 103 933 | 7.4 Acceptance requirements of fibre deployment | Acceptance requirements of fibre deployment includes product quality inspection, project implementation quality control and project completion acceptance. The construction and acceptance of fibre deployment project can be performed as a sub-project of the weak current system project. The construction of fibre deploymen... |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 1 Scope | The present document is the PP-Configuration for the combination of the Consumer Mobile Device PP and the Biometric Authentication PP-Module. |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 2 References | |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 3 Definition of terms, symbols and abbreviations | |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 3.1 Terms | Void. |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 3.2 Symbols | Void. |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Common Criteria CMD Consumer Mobile Device PP Protection Profile SAR Security Assurance Requirement SFR Security Functional Requirement ST Security Target TOE Target Of Evaluation |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 4 PP-Configuration Reference | This PP-Configuration is identified as follows: PP-Configuration Short Name CFG_CMD_BIO PP-Configuration Title ETSI TS 103 932-1: "Consumer Mobile Devices Base PP-Configuration; Part 1: CMD and Biometric Verification". PP-Configuration Version 1.1.2 PP-Configuration Date November 16, 2023 |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 5 PP-Configuration Components Statement | This PP-Configuration includes the following components: • Base-PP: ETSI TS 103 732-1 [6]: "Consumer Mobile Device; Part 1: Base Protection Profile", November 16, 2023, V2.1.2 • PP-Module: ETSI TS 103 732-2 [7]: "Consumer Mobile Device; Part 2: Biometric Authentication Protection Profile Module", November 16, 2023, V1.... |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 6 Conformance Claim and Statement | |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 6.1 Common Criteria Conformance Claim | This PP-Configuration, the Base-PP and the PP-Module are conformant to Common Criteria Version 3.1, Revision 5 [1], [2], [3], and [4] as extended by the requirements in each document. ETSI ETSI TS 103 932-1 V1.1.2 (2023-11) 8 |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 6.2 Conformance Type | To be conformant to this PP-Configuration, the Security Target shall demonstrate Exact Conformance as defined by "CC and CEM addenda, Exact Conformance, Selection-Based SFRs, Optional SFRs", Version 0.5, May 2017 CCDB-2017-05-xxx [5]. |
512a5d3537e139020e17a88a4d97c240 | 103 932-1 | 6.3 Assurance Package Conformance Claim | In order to evaluate a TOE that claims conformance to this PP-Configuration, the evaluator shall evaluate the TOE against the following SARs that are defined in the Base-PP. Assurance Class Assurance Components Development (ADV) ADV_ARC.1 Security architecture description ADV_FSP.2 Security-enforcing functional specifi... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 1 Scope | The present document specifies the Release 2 of the Geographical Area Definition. |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 2 References | |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 3 Definition of terms, symbols and abbreviations | |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 3.1 Terms | For the purposes of the present document, the following terms apply: location referencing: method for referencing a location to facilitate the exchange of location-related information |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: a the distance between the centre point and the short side of a rectangle (perpendicular bisector of the long side) or the length of the short semi-axis of an ellipse b the distance between the centre point and the long side of a rectangle (perpendi... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 3.3 Abbreviations | Void. |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 4 Definition of geographical areas | |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 4.1 Overview | Geographical areas shall be specified by geometric shapes. The following geographical areas are defined: • circular area; • rectangular area; and • elliptical area. Figure 1 depicts all shapes in a single drawing. The shapes are detailed in the following clauses. Figure 1: Overview of geometric shapes for the definitio... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 4.2 Definition of a circular area | The circular area shall be described by a circular shape with a single point A that represents the centre of the circle and a radius r as shown in figure 2. ETSI ETSI TS 103 899 V2.1.1 (2025-07) 7 Figure 2: Circular area |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 4.3 Definition of a rectangular area | The rectangular area shall be defined by a rectangular shape (figure 3) with point A that represents the centre of the rectangle and the following parameters: a the distance between the centre point and the short side of the rectangle (perpendicular bisector of the short side); b the distance between the centre point a... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 4.4 Definition of an elliptical area | The elliptical area shall be defined by an elliptical shape (figure 4) with point A that represents the centre of the ellipse and the following parameters: a the length of the long semi-axis; b the length of the short semi-axis; θ azimuth angle of the long semi-axis. ETSI ETSI TS 103 899 V2.1.1 (2025-07) 8 A North θ a ... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 5 Elementary geometry | 5.1 Geometric function F to determine spatial characteristics of a point P(x,y) This clause defines a function F that an ITS station can use to determine whether a point P(x,y) is located inside, outside, at the centre, or at the border of a geographical area. The function has the following properties: ( ) ... |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 5.2 Geometric function F for a circular area | For a circular area the function F is defined by equation (1). 2 2 1 ) , ( − − = r y r x y x F (1) |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 5.3 Geometric function F for a rectangular area | For a rectangular area the function F is defined by equation (2). − − = 2 2 1 , 1 ) , ( b y a x Minimum y x F (2) ETSI ETSI TS 103 899 V2.1.1 (2025-07) 9 |
cc99485295014175a4a1f50d4ec48536 | 103 899 | 5.4 Geometric function F for an elliptical area | For an elliptical area the function F is defined by equation (3). 2 2 1 ) , ( − − = b y a x y x F (3) ETSI ETSI TS 103 899 V2.1.1 (2025-07) 10 Annex A (informative): Bibliography • EU FP7 GEONET Project: "Deliverable D2.2 Final GeoNet Specification", January 2010, ETSI Document ITSWG3(10)0011. •... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 1 Scope | The present document provides mapping tables to show which security requirements and provisions from the IEC 62443-4-2 [i.4] and the ETSI EN 303 645 [i.3], respectively, cover the specific requirements from the standardisation request for the RED articles 3(3)(d), 3(3)(e) and 3(3)(f) and are therefore relevant to fulfi... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 2 References | |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 3 Definition of terms, symbols and abbreviations | |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 3.1 Terms | For the purposes of the present document, the terms given in [i.1], [i.2], [i.3], [i.4], [i.5] and the following apply: process-related requirement: requirement that is addressed to the process around the product functionality EXAMPLE: If a standard requires that a product manufacturer provides a publicly available vul... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 3.2 Symbols | Void. |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: EN European Standard hEN harmonised European Standard IEC International Electrotechnical Commission RE Requirement Enhancement RED Radio Equipment Directive |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 4 Methodology | |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 4.1 Mapping of IEC 62443-4-2 requirements | • In the present document a rough mapping table and a detailed mapping table is provided to map the requirements of the IEC 62443-4-2 [i.4] to the specific requirements of the standardisation request [i.5]. • The detailed mapping table is the one that maps every single specific requirement of the standardisation reques... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 4.2 Mapping of ETSI EN 303 645 provisions | • To perform the mapping of the ETSI EN 303 645 [i.3] provisions the same mapping methodology as described in clause 4.1 is used. Hence, the mappings result in a rough mapping table, which shows the relevance of the provisions to the essential requirements in the RED articles 3(3)(d), (e) and (f), as well as a detailed... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 4.3 Mapping notations | In the present document a rough mapping table and a detailed mapping table are provided for both mappings (mapping with IEC 62443-4-2 [i.4] and ETSI EN 303 645 [i.3]), respectively, which results in four different mapping tables - two rough mappings and two detailed mappings. Three different mapping assignments are use... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 5 Mapping results and resulting transition requirements | |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 5.1 Mapping results based on IEC 62443-4-2 requirements | Table 1: "Rough Mapping" - Mapping the essential requirements of the RED articles 3(3)(d), (e) and (f) to the requirements of the IEC 62443-4-2 [i.4] based on the specific requirements of the standardisation request [i.5] IEC 62443-4-2 [i.4] Requirement RED article 3(3)(d) 3(3)(e) 3(3)(f) 1 Identification and authentic... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 5.2 Mapping results based on ETSI EN 303 645 provisions | The following mapping tables use the same assignments as described in clause 5.1, respectively. Table 3: "Rough Mapping" - Mapping the essential requirements of the RED articles 3(3)(d), (e) and (f) to the provisions of the ETSI EN 303 645 [i.3] based on the specific requirements of the standardisation request [i.5] ET... |
1b83bd5297aac5f795ebc6fac5ccaf21 | 103 929 | 5.3 Transition requirements based on mapping results | To realize the transition from product conformity with requirements and/or provisions of IEC 62443-4-2 [i.4] and ETSI EN 303 645 [i.3], respectively, to product conformity based on the future hENs for the RED articles 3(3)(d), 3(3)(e) and 3(3)(f), the following transition requirements are to be met. TReq1: Process-rela... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 1 Scope | The present document specifies Automated Vehicle Marshalling (AVM) messages at the Facilities layer, which are agnostic to the lower layers and thus supported by different transport and network layer protocols e.g. Basic Transport Protocol (BTP)/Geonetworking, or Internet Protocol (IP) based stacks. AVM is a specific c... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 2 References | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 3 Definition of terms, symbols and abbreviations | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 3.1 Terms | For the purposes of the present document, the term authority given in ISO 23374-1 [i.6] and the following apply: Automated Vehicle Marshalling (AVM): orchestration and remote VMC of vehicles at low speed communication protocol: formal description of a message format and its rules logical architecture: decomposition of ... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 3.2 Symbols | Void. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 5GAA 5G Automotive Association ADU Application Data Unit ASIL Automotive Safety Integrity Level ASN.1 Abstract Syntax Notation One AVM Automated Vehicle Marshalling AVMS Automated Vehicle Marshalling System AVP Automated Valet Parking BTP Basi... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4 AVM entity introduction and general functionality | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.1 Introduction | The AVM entity is a functionality supporting marshalling operations in an AVM system. An illustrative logical architecture of an AVM system is given in Figure 1. The AVM entity relates to an implementation of the operation interface Vehicle Motion Control (VMC) shown in green in Figure 1. Figure 1: Illustrative logical... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.2 AVM entity at the Facilities layer | Within the scope of the present document, the term AVM entity as shown in Figure 2, refers to a Facilities layer implementation of the AVM messages Marshalling Infrastructure Message (MIM) and Marshalling Vehicle Message (MVM). The term "message" refers to the Facilities layer Protocol Data Unit (PDU) and the term "pay... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.3 General functionality | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.3.1 Introduction | The AVM entity enables the marshalling operation described in clause 4.1 and therefore it has a clear boundary and functionality within an AVM architecture. This clause defines the boundary and explains the functionality of the AVM entity as follows: • Clause 4.3.2 defines the functional boundary of the AVM entity. • C... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.3.2 AVM entity functional boundary | The AVM entity supports AVM operation when the SV is under system Authority, in other words, the System Operator (SO) has authority to perform marshalling operations at the SV through the operation interface VMC stablished between the RO and the VO subsystems. The functional boundary of the AVM entity is shown in Figur... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.3.3 AVM operation interface | Within an AVM architecture, such as the one shown in Figure 1, the AVM operation is enabled by an implementation of the VMC operation interface between the RO and the VO subsystems as shown in Figure 4. The communication between the AVM entity in the RO system and the AVM entity in the VO system is supported by the AVM... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 4.3.4 AVM Automated Vehicle Operation | The AVM entity supports two methodologies to realize the VMC operation interface within the Automated Vehicle Operation domain shown in Figure 3: 1) The Path Control methodology, which is based on the transmission of way points from the RO to the VO. Through an implementation of the VMC operation interface using the Pa... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5 Architecture and interface description | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.1 Introduction | The AVM entity features several functionalities which are specified hereafter. The present clause is organized as follows: • Clause 5.2 introduces the AVM entity architecture. • Clause 5.3 defines functionalities of the AVM entity. • Clause 5.4 defines the interfaces for the AVM entity. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.2 AVM entity architecture in the ITS ecosystem | The AVM entity is a Facilities layer entity in the ITS-S architecture as defined in ETSI TS 103 898 [i.12]. It may interface with other entities of the Facilities layer and with ITS applications (in particular, with the AVM application). Figure 5 depicts the AVM entity within the ITS-S architecture along with the logic... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.3 AVM entity functional architecture | The AVM entity shall provide at least the following functions in the RO subsystem and the VO subsystem for sending and receiving the AVM messages defined in clause 4.2: • Encode AVM message: This sub-function shall construct the AVM message according to the format specified in normative Annex A and informative Annex B.... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4 Interfaces to the AVM entity | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4.1 Introduction | The AVM entity may interface to other entities and communication layers for the realization of the functionality specified in clauses 5.2 and 5.3. This clause presents such interfaces and is organized as follows: • Clause 5.4.2 explains interfacing to ITS applications. • Clause 5.4.3 explains interfacing to other Facil... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4.2 Interface to ITS applications | An ITS application, such as the AVM application, is an application layer functionality that implements the logic for fulfilling one or more ITS use cases. For the provision of received data, the AVM entity provides the interface IF.App (also implemented as IF.AVM) to ITS application as illustrated in Figure 5. |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4.3 Interface to other Facilities layer entities | For the generation of MIMs and MVMs, the AVM entity may interact with other Facilities layer entities to obtain the required data. This set of other facilities is referred to as data provisioning facilities, e.g. the ITS-S's POTI or DDP mentioned in clause 5.2. Data is exchanged between the data provisioning facilities... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4.4 Interface to Network & Transport layer | The AVM entity can use any compatible communication stack for the transmission and reception of MIMs and MVMs as illustrated in Figure 6. At the originating ITS-S, the AVM entity can provide the MIM or MVM embedded in a Facility-Layer Service Data Unit (FL-SDU) to the ITS Network & Transport layer, optionally together ... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4.5 Interface to the ITS management entity | The AVM entity of an originating ITS-S obtains configuration parameters and other control information from the Management Information Base (MIB) located in the Management entity via the IF.Mng interface, as shown in Figure 5. NOTE 1: A list of primitives exchanged with the management layer are provided in ETSI TS 102 7... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 5.4.6 Interface to the security entity | The AVM entity may exchange primitives with the Security entity of the ITS-S using the IF.Sec interface provided by the Security entity as depicted in Figure 5. NOTE: Depending on the security requirements of AVM implementation scenarios, different security solutions may be used. Specification of the interface configur... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 6 MIM and MVM dissemination | |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 6.1 Introduction | This clause introduces requirements and constraints for the dissemination of MIM and MVM messages and it is structured as follows: • Clause 6.2 specifies requirements for the generation of MIMs and MVMs. • Clause 6.3 defines constraints for the dissemination of MIMs and MVMs. ETSI ETSI TS 103 882 V2.1.1 (2024-05) 20 |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 6.2 MIM and MVM generation | MIM messages shall be generated upon the activation of the AVM entity. MVMs shall only be generated by SV ITS-Ss and MIMs shall only be generated by SO ITS-Ss. The generation of MVMs by SV ITS-Ss shall start after the first successful reception of a MIM with a valid addressing to the SV ITS-S receiving the MIM. Each MI... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 6.3 MIM and MVM dissemination constraints | In an implementation of the AVM entity, some constraints for the dissemination of MIMs and MVMs related to the Maximum Transmission Unit (MTU) size limit of the Network & Transport layer exist. The size of an ASN.1 encoded MIM or MVM shall not exceed MTU_MIM or MTU_MVM, respectively. MTU_MIM and MTU_MVM depend on the M... |
3de14d1e28d8b7752a880e033db3bf4d | 103 882 | 7 MIM containers and data elements |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.