hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.1.4 Network sniffer | To validate the behaviour of the EUT in certain test cases it is necessary to observe the sent and received CPMs. To enable this observation a network sniffer is required. The network sniffer does not participate actively in the communication. Mandatory requirements: • The Network sniffer shall be able to receive and d... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.2 Configurations | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.2.1 MCO configuration | Some use cases test the ability of the CPS to reduce the channel load with MCO features, as specified in ETSI TS 103 141 [2]. The following conditions shall be met to enable these tests: • The EUT supports MCO. • The channel shall provide a load which is defined in the corresponding use case. NOTE: The channel load can... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.2.2 Load Generation | To increase the CBR in the tests it is necessary to generate load on the channel. A load generator could be used to realize this load. The load generator has the following mandatory requirements: • The load generator shall fill the channel with V2X messages which are compliant to V2X messages. • The load generator shal... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.2.3 ITS-S Type Configuration | Some use cases require the EUT to be a specific ITS-S type as the sender of the CPM. The following conditions shall be met to enable the vehicle type tests: • the EUT corresponds to a Sender_ITS-S_type = vehicle; • its heading is 35° in the WGS84 coordinate system with respect to true North; the following conditions sh... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 5 Requirements to be tested | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 5.1 Overview | The clauses below collect and enumerate the requirements that can be tested with the present interoperability test specification. |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 5.2 CPM interoperability requirements | Table 1 NN Requirement Reference UCs 1.1 ITS-S shall encode and decode CPMs with all mandatory and optional DFs. ETSI TS 103 324 [1] UC1-1 1.2 ITS-S shall reconstruct received sensor information's. ETSI TS 103 324 [1] UC1-2 1.3 ITS-S shall reconstruct received perception regions. ETSI TS 103 324 [1] UC1-2 UC1-3 1.4 ITS... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6 Interoperability test descriptions | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.1 Use-case 1-1 General CPM handling | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-1 Objective: Check that EUT can correctly encode and decode the CPM with all allowed DEs and DFs. Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1] with all allowed DEs and DFs. EUT2 shall be capable of receiving an... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.2 Use-case 1-2 Sensor information handling | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-2 Objective: Check that EUT2 can correctly reconstruct the sensor information transmitted by EUT1. Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1]. EUT2 shall be capable of receiving and decoding CPMs as specified... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.3 Use-case 1-3 Perception region handling | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-3 Objective: Check that EUT2 can reconstruct the perceived regions transmitted by EUT1 correctly. Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1]. EUT2 shall be capable of receiving and decoding CPMs as specified ... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.4 Use-case 1-4 Perceived object handling | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-4 Objective: Check that EUT2 can correctly reconstruct the perceived object kinematic and attitude states transmitted by EUT1. Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1]. EUT2 shall be capable of receiving an... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.5 Use-case 1-5 Message Assembly Configuration | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-5 Objective: Check that EUT2 is able to distinguish the message assembly configuration chosen by the transmitter (EUT1). Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1] with all optional DEs and DFs. EUT2 shall be... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.6 Use-case 1-6 Correlation matrix handling | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-6 Objective: Check that EUT2 can correctly reconstruct the covariance information transmitted by EUT1. Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1]. EUT2 shall be capable of receiving and decoding CPMs as speci... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.7 Use-case 1-7 Non-line-of-sight perception | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-7 Objective: Check that EUT2 can correctly interpret non-line-of-sight conditions transmitted by EUT1. Configuration: EUT1 shall be capable of transmitting CPMs as specified in ETSI TS 103 324 [1]. EUT2 shall be capable of receiving and decoding CPMs as speci... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.8 Use-case 1-8 Resource-aware data rate adaptation | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-8 Objective: Check that EUT adapts the number of consumed communication resources according to the provided limits (e.g. by MCO ETSI TS 103 141 [2]). Configuration: MCO Configuration as defined in clause 4.2.1 shall be used with additional requirements: • The... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 6.9 Use-case 1-9 Resource-aware channel offloading | Interoperability Test Description Identifier: TC_ITS_CPS_UC1-9 Objective: Check that EUT1 can offload objects to other available communication channels and EUT2 can reconstruct the list of transmitted objects. Configuration: MCO Configuration as defined in clause 4.2.1 shall be used with additional requirements: • EUT1... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 1 Scope | The present document is part of a series of documents specifying the Test Tool Interface (TTI) for the Smart Secure Platform. It is the technical specification for the Test Tool Interface (TTI) shown in the test environment of ETSI TS 103 999-1 [3]. It describes: • the setup of the (TTI); • the authentication of the TT... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 2 References | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-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. • In the case of a reference... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-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. • In the case of a reference... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 666-1 [1], ETSI TS 103 999-1 [3] and the following apply: impersonated host: virtual host belonging to the SUT host network but executed from a host in the TTI host network NOTE: This host is defined in clause 6.3.2.2 of the present document. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 666-1 [1] and ETSI TS 103 999-1 [3] apply. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 666-1 [1], ETSI TS 103 999-1 [3], and the following apply: AAA Accessor Authentication Application AAS Accessor Authentication Service OEM Original Equipment Manufacturer (Terminal maker) PP Primary Platform PPI Primary Platform Interface ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.4 Formats | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.4.1 Numbers and Strings | The conventions used for decimal numbers, binary numbers and strings. Table 3.1: Convention of Numbering and Strings Convention Description nnnnn A decimal number, e.g. PIN value or phone number 'b' A single digit binary number 'bbbbbbbb' An 8-bit binary number 'hh' A single octet hexadecimal number 'hh hh…hh' A multi-... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.5 ASN.1 syntax | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.5.1 Introduction | The description of some data objects in the present document is based on ASN.1 specified in Recommendation ITU-T X.680 [19] and encoded in TLV structures using DER (Distinguished Encoding Rule) encoding as specified in Recommendation ITU-T X.690 [20]. This provides a flexible description of those data objects. The comp... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 3.5.2 Start of ASN.1 | -- ASN1START TTIDefinitions { itu-t (0) identified-organization (4) etsi (0) smart-secure-platform (3834) part1 (1) } DEFINITIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN EXPORTS ALL; /* Imports */ IMPORTS Version, AccessorRights, AccessControl, UUID FROM SSPDefinitions; -- ASN1STOP NOTE: The ASN.1 code is ended ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 4 Requirements for the TTI | As the TTI shall be useable in test environments as defined in ETSI TS 103 999-1 [3], requirements from various specifications shall be considered. Where the TTI shall be capable to fulfil requirements identified in: • ETSI TS 103 666-1 [1] Smart Secure Platform (SSP); Part 1: General characteristics: - A listing of re... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5 Test Tool Interface (TTI) architecture | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.1 TTI environment | The TTI is to be integrated into the test environment defined in ETSI TS 103 999-1 [3] (see figure 5.1). TEST TOOL REPORT FUNCTIONS APPLICATION EMULATOR FUNCTIONS Report SCL ANALYZER FUNCTIONS Test Descriptions SSP Rich OS ROUTER TERMINAL Test Tool Interface SUT Figure 5.1: SSP test environment overview (according to E... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2 Network Protocol stack | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.1 TTI layers | Figure 5.3 illustrates the protocol stack defining the TTI layers. 7 6 5 4 3 2 1 OSI Application/Service Layer Presentation Layer (optional – e.g., ASN.1) Session Layer (conditional) Transport Layer (conditional) Network Layer (conditional) TTI Underlayers Service n Service 1 Service ... TTI Layers SSP Common Layers Fi... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.2 TTI underlayers | The TTI interacts with the services to test and shall be able to convey the SCL packets supporting the ETSI TS 103 999-1 [3], ETSI TS 103 999-2 [4], ETSI TS 103 666-1 to ETSI TS 103 666-4 [1], [2], [i.1] and [i.2]. The TTI underlayers shall support the same requirements as the ones driving the SCL layers and defined in... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.3 TTI underlayer server | The TTI underlayer (TTI_UL) related to the interface of a TT uses a stream based on TCP/IP technology via IP binding, supporting the transport of IP packets. The TTI_UL may require the support of the TLS protocol as defined in IETF RFC 8446 [9]. The terminal hosting TTI shall establish a stream socket independently of ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.4 TTI UL client/server connection | The TTI server represents the principle shown in figure 5.3. Figure 5.4 illustrates the client/server connection between the TT and the TTI_UL server in the terminal. Test Tool TTI_UL server Terminal TTI_UL client Figure 5.4: TTI_UL server in the Test Tool The URL of the TTI_UL server is either provided by a MQTT broke... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5 TTI MQTT certification paths | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.1 Overview | A TTI certification path for MQTT client authentication shall be prepared to consider the following: • The CI issuers of both MQTT broker and MQTT clients which are respectively CIMB and CIMC may be different. • No credentials from a MQTT client (e.g. CERT CIULC.ECDSA certificate) shall be provisioned into another MQTT... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.2 TTI MQTT certificate policy | Each certificate shall have the appropriate value of the extension for certificate policies. The OIDs used for value of the extension for certificate polices are defined as follows: -- ASN1START id-tti OBJECT IDENTIFIER ::= {itu-t (0) identified-organization (4) etsi (0) smart-secure-platform (3834) part2 (1) } id-mb-r... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.3 Certification path verification | All MQTT clients shall verify the certification path received by each other according to the IETF RFC 5280 [12]. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.4 TTI MQTT parameters | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.4.1 TTI MQTT broker connection parameters | The following parameters shall apply for connecting a TTI MQTT client to a MQTT broker: • User Name Flag: 0 • Password Flag: 0 (the client authentication is performed with digital certificates) • Will Retain: 0 • Will QoS: 1 • Will Flag: 0 • Clean Start: 0 • QoS: 2 • Retain flag: false ETSI ETSI TS 103 834-1 V17.0.0 (2... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.4.2 TTI MQTT client identifiers | The MQTT client identifier is computed from the canonical representation of a UUID version 5 as defined in IETF RFC 4122 [7] in only keeping the authorized symbol as defined in OASIS Standard [8]. The following example illustrates a valid canonical UUID for a client identifier: 4ebd0208-8328-5d69-8c44-ec50939c0967. The... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.4.3 TTI MQTT topic name | The MQTT client topic for getting the TTI UL URL is defined as follow: /geturl/client_identifier. The client_identifier is defined in the clause 5.2.5.4.2 of the present document. As example, the following topic name is valid: /geturl/4ebd0208-8328-5d69-8c44-ec50939c0967 |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.5.4.4 TTI MQTT payload | The payload conveyed between two TTI MQTT client for the defined topic name shall support the JSON syntax as defined in IETF RFC 7159 [10]. The payload for conveying the TTI_UL server URL is defined as follow: {url:"tti:xxx:port"} or {url:"ttis:xxx:port"} Where: • tti defines a simple TCP connection between the TTI_UL ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.6 Certificate description | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.6.1 Certificates common fields | Table 5.1 describes the basic certificate fields for all certificates in the present document follows X.509 v3 certificate format as defined in IETF RFC 5280 [12]. ETSI ETSI TS 103 834-1 V17.0.0 (2022-12) 19 Release 17 Table 5.1: Certificates common fields Field Value Description tbsCertificate Data to be signed Parame... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.6.2 Extension fields for Certificates | The following extension fields defined in IETF RFC 5280 [12] are considered: • Authority key identifier (IETF RFC 5280 [12], section 4.2.1.1): All the certificate except for CI certificate shall contain the extension for authority key identifier. • Subject key identifier (IETF RFC 5280 [12], section 4.2.1.2): All the c... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.2.6.3 Algorithm identifiers and parameters | This clause provides the value to be set in 'AlgorithmIdentifier' structure contained in 'subjectPublicKeyInfo', 'signature', and 'signatureAlgorithm' fields of the certificates for each of cryptographic algorithms used in the present document. For 'subjectPublicKeyInfo' field, the following settings shall apply: • 'Al... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.3 Test Tool SCL network | Router 2 Router 1 TTI Host Domain Network Host Controller SSP Host Domain REE/TEE/ MBM Host Domains TS 103 666-1 scope TS 103 834 scope Test Tool Host Domain TTI front-end Router Network Host Controller SUT TTI Host Figure 5.9: Router abstraction ETSI ETSI TS 103 834-1 V17.0.0 (2022-12) 21 Release 17 As figure 5.9 expo... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.4 TTI platform | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.4.1 TTI valid platform | Figure 5.10 illustrates a TTI valid platform. Other Host Domain (Test Tool) TTI Host Domain TTI Host Other Host AA Control Application AA Control Application Gate TTI Control Application AA Control Service AA Control Service Gate TTI Control Application Gate TTI Control Service TTI Control Service Gate Analyser Parser ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.4.2 Router directives and data | Figure 5.11 illustrates the interaction between TTI services and Router 2, The figure exemplifies the handling of transfer directives and timestamped copies of SCL packets. TTI Host Domain TTI Host ROUTER 2 directives Tunneling of SCL packets Timestamped copy of SCL packets TTI Control Service TTI Control Service Gate ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.5 TTI security perspectives | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.5.1 Identification of security perspectives | Dumping the SCL packets from a host and/or impersonating a host to emulate a host in a TT may lead to security breaches and to disclose sensitive data (see ResearchGate [i.3]). The access to the TT interface shall be enforced with established and secure methods. Thus, the TTI: 1) Reuses the principles of the ETSI TS 10... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.5.2 TTI security requirements | The TTI shall fulfil the following security requirements: • The access to the TTI shall be possible for authenticated accessors only. • The TTI may request confidential data exchange to the TT. • An access control shall allow to grant dumped SCL packets and services per host and per services. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.6 TTI certificates | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.6.1 TTI certification paths | A TTI certification path shall be prepared to consider the following: • The CI issuers of both OEM and TTM which are respectively CIAAS and CIAAA may be different. • No credentials from the test maker (e.g. CERT CIAAA.ECDSA certificate) shall be provisioned into the TTI Host for supporting the accessor authentication w... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.6.2 Certification path verification | The certification path verification shall support the requirement as defined in clause 5.2.5.3 of the present document. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 5.6.3 Certificate policies | Each certificate shall have the appropriate value of the extension for certificate policies. The OIDs used for value of the extension for certificate polices are defined as follows: -- ASN1START id-mb-role OBJECT IDENTIFIER ::= {id-tti role (0)} id-mb-role-ci OBJECT IDENTIFIER ::= { id-mb-role ci (0)} id-mb-role-subord... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6 TTI services | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.1 TTI Accessor Authentication Service | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.1.1 Requirements | The TTI Accessor Authentication Service is the service in the TTI Host responsible of authenticating external entities accessing resources on the TTI Host. The TTI Accessor Authentication Service shall operate similar to the Accessor Authentication Service in the SSP, defined in ETSI TS 103 666-1 [1], clause 6.13. Wher... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.1.2 Test Tool (TT) Accessor Authentication | The TT Accessor Authentication supported by the Accessor Authentication Service within the TTI Host shall support the protocol as defined in ETSI TS 103 666-1 [1], clause 9.4. ETSI ETSI TS 103 834-1 V17.0.0 (2022-12) 27 Release 17 |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.1.3 Access to the TTI Host Services | The access of the TTI Host Services as defined in clause 5.4 of the present document are granted by using the AAS-OP-ACCESS-SERVICE-Service-Command as defined in ETSI TS 103 666-1 [1], clause 6.13.5.6. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2 TTI Control Service | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.1 Overview | This service aims to manage the constraints and the behaviour of the Router Data Extractor interfacing the Router 2. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.2 Administrative operations | The TTI Control Service supports the following administrative operations: • retrieving the capabilities of the TTI Control Service (i.e. TTI-OP-GET-CAPABILITIES-Service-Command); • updating the directives of a TTI Data Service related to the Router Data Extractor in charge to record the SCL packet traffic. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3 TTI Control Service access | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.1 Access rights | The TTI Control Service access rights allow to define the availability of requested operations. -- ASN1START eTTIAccessRight-MBMHostPacketRecordAllowed AccessorRights ::= { eRight-Bit1 } eTTIAccessRight-MBMHostPacketInjectionAllowed AccessorRights ::= { eRight-Bit2 } eTTIAccessRight-MBMHostImpersonationAllowed Accessor... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.2 Directives | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.2.1 Directives transfer | The TTI Control Service shall forward the directives related to rights, as defined in clause 6.2.3.1, to the Router 2 and the SUT host network controller. This rights transfer is implementation dependent. The SUT host network controller shall broadcast the following event concerned by the directives. Table 6.2 defines ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.2.2 EVT_TTI_DIRECTIVES | This event shall be sent by the link service gate of the SUT host network controller to all connected hosts concerned by the TTI directives as defined in clause 6.2.3.1. All recipients of the EVT_TTI_DIRECTIVES shall enforce the directives. This event has the following parameter. -- ASN1START TTI_Directives ::= SEQUENC... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.3 Primitives | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.3.1 TTI-OP-GET-CAPABILITIES-Service-Command | With the command TTI-OP-GET-CAPABILITIES-Service-Command, a TTI Control Service Application requests the TTI Control Service to get granted the capabilities of the TTI Control Service. -- ASN1START TTI-OP-GET-CAPABILITIES-Service-Command ::= [PRIVATE 16] SEQUENCE { } -- ASN1STOP This command has no parameters. If the c... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.3.2 TTI-ADMIN-IMPERSONATE-Service-Command | With the command TTI-ADMIN-IMPERSONNATE-Service-Command, a TTI Control Service Application may impersonate a host. -- ASN1START TTI-ADMIN-IMPERSONATE-Service-Command ::= [PRIVATE 17] SEQUENCE { aFirmwareFamilyID UUID, -- Identifier of firmware family of the host to impersonate aHostDomainID UUID -- Host domain identifi... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3.3.3 TTI-ADMIN-UPDATE-ACL-Service-Command | With the command TTI-ADMIN-UPDATE-ACL-Service-Command, an TTI control application requests the TTI control service to update the access control. The accessor updating the access control shall have the eTTIAccessRight-UpdateACL right on that resource. -- ASN1START TTI-ADMIN-UPDATE-ACL-Service-Command ::= [PRIVATE 18] SE... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.4 Commands | The TTI Control Service gate supports the following commands. -- ASN1START TTI-SERVICE-GATE-Commands ::= [APPLICATION 2] CHOICE { aTTI-OP-GET-CAPABILITIES-Service-Command TTI-OP-GET-CAPABILITIES-Service-Command, aTTI-ADMIN-IMPERSONATE-Service-Command TTI-ADMIN-IMPERSONATE-Service-Command, aTTI-ADMIN-UPDATE-ACL-Service-... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.2.3 Responses | The gate shall support the responses defined as follows. -- ASN1START TTI-SERVICE-GATE-Responses ::= [APPLICATION 1] CHOICE { aTTI-OP-GET-CAPABILITIES-Service-Response TTI-OP-GET-CAPABILITIES-Service-Response, aTTI-ADMIN-IMPERSONATE-Service-Response TTI-ADMIN-IMPERSONATE-Service-Response, aTTI-ADMIN-UPDATE-ACL-Service-... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3 TTI Data Service | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3.1 Overview | This service is in charge to tunnel a SCL packets traffic from/to a TT Host which may impersonate a host as defined in clause 6.3.2.2 of the present document. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3.2 Principles | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3.2.1 SCL packet tunnelling | Figure 6.1 is showing the encapsulation of SCL packets as used to communicate between TT Host and an SCL host B. SCL Header 0 MSG Message Fragment 0 SCL Header 1 H1 Message Fragment 1 H0 Tunneled SCL Packet Figure 6.1: Encapsulation Figure 6.2 illustrates the sending of an SCL packet, including the encapsulation into a... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3.2.2 Host impersonation | The impersonation of a host is performed by the application emulating the impersonated host by using the following procedure: • The TT Host shall initiate the impersonation of a host by using the TTI-ADMIN-IMPERSONNATE-Service- Command command as defined in clause 6.2.3.3.2. • The successful acceptation of the imperson... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3.3 TTI Data Service gate | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.3.3.1 Overview | This service does not support any commands or events. The SCL packet encapsulating another SCL packet shall be configured as a data stream by setting the chaining bit (CB) of the HCP packet header to 0 (see ETSI TS 102 622 [18], clause 5.1). The data acknowledgement mechanism (EVT_ADM_RECEIVED) and the credit-based dat... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4 RDE Data Service | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4.1 Overview | This service is in charge to: • Filter the copied SCL packet flowing within the SCL network associate to the Router 2 (SUT) according to the rights associated to the TT Accessor as defined in clause 6.1.2 of the present document. • Timestamp the taped SCL packets and encapsulate them into an RDE_EVT event. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4.2 RDE Data Service gate | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4.2.1 About the RDE Data Service gate | This service does not support any commands. This gate supports the HCI presentation layer as defined in ETSI TS 102 622 [18], clause 5.2. The data acknowledgement mechanism (EVT_ADM_RECEIVED) and the credit-based data flow control (EVT_ADM_CREDIT) described in ETSI TS 103 666-1 [1], clause 8.5.3 shall apply. |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4.2.2 RDE Data Service gate Events | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4.2.2.1 Overview | The gate supports the following event: Table 6.3: RDE Service gate Events Value Event '10' EVT_RDE |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.4.2.2.2 RDE-Event | With the event RDE-Event, the RDE data service gate notifies the RDE data application gate that a SCL packet has been routed from Router 2. This event has the following parameter. ETSI ETSI TS 103 834-1 V17.0.0 (2022-12) 34 Release 17 Table 6.4: RDE Parameter Description Length Timestamp 8 copied SCL packet N Where: • ... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 6.5 Service identifiers | The provisions of GlobalPlatform VPP - Network Protocol [5], clause 3 shall apply. Table 6.5 defines the URN for the additional gates defined in the present document, other than the ones referenced from GlobalPlatform VPP - Network Protocol [5]. All UUIDs are calculated using the version 5 of the UUID as specified in I... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 7 iSSP primary platform support | |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 7.1 Scope | The iSSP Primary Platform (PP) and its Interface (PPI) are respectively defined in ETSI TS 103 666-2 [2], clauses 7 and 8. The test descriptions related to the PPI are out of the scope of the present document. Nevertheless, the TTI shall support the tooling in charge to test the PPI. The PPI exposes two interfaces: • A... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 7.2 Principle | Figure 7.1 illustrates the concept supporting the test of the PPI from the TT Host. Other Host Domain (Test Tool) TTI Host Domain TTI Host TT Host Impersonated Host Application TTI Application Gate TTI Data Service TTI Data Service Gate SSP Host Domain SSP Host PPI Service PPI Service Gate Router 2 Figure 7.1: PPI serv... |
da99fdbd44a6ad9884f15d3bc00fd195 | 103 834-1 | 7.3 TTI Data Service extension | The TT Data Service as defined in the clause 6.3 of the present document may be extended for supporting the additional events and directives related to [i.6], clause 5.6 in order to monitor: • The signals sent/received by the MAIN process from the MGT service. • The exceptions issued by the MAIN process. This extension... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.