hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.2.2 Si1 response header | The ASN1 structure of all Si1 responses contains the Si1ResponseHeader defined as follows: -- ASN1START Si1ExecutionStatus ::= ENUMERATED { eSi1ExecutionStatus-Executed-Success (0), eSi1ExecutionStatus-Failed (1), eSi1ExecutionStatus-Executed-WithWarning (2) } Si1ResponseHeader ::= SEQUENCE { aFunctionExecutionStatus S... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.3 Si1 error codes | This clause describes the error codes used to indicate an error over the Si1 interface. Table 12.5 gives the applicability matrix according to the Si1 function. ETSI ETSI TS 103 666-2 V17.1.0 (2024-12) 63 Release 17 -- ASN1START Si1ErrorCode::= ENUMERATED { eSpbIdUnknown (0), -- the Secondary Platform Bundle identifier... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.4 Si1.SelectSpb | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.4.1 Command | The "Si1.SelectSpb" function shall be used by the service provider during the Secondary Platform Bundle selection as defined in clause 12.3.2.2. The service provider shall use the "Si1.SelectSpbm" function to select a Secondary Platform Bundle that matches the terminal and the SSP capabilities. The body part of the HTT... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.4.2 Procedure | Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. • If the Secondary Platform Bundle identifier (spbId) was provided as input data: - return an error with the code eSpbIdNotAvailable if the spbId is not available; - return an error with the code eSpbI... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.4.3 Response | The body part of the HTTP POST response for the "Si1.SelectSpb" function shall contain Si1SelectSpbResponse defined as follows: -- ASN1START Si1SelectSpbResponse ::= SEQUENCE { aSi1ResponseHeader Si1ResponseHeader, -- Header of the response aSi1SelectSpbResult CHOICE { aSi1SelectSpbOk Si1SelectSpbOk, aSi1SelectSpbError... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.5 Si1.CreateSPReference | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.5.1 Command | The "Si1.CreateSPReference" function shall be used by the service provider during the procedure of creation of a service provider reference as defined in clause 12.3.2.3. The service provider may use the "Si1.CreateSPReference" function to create a reference shared between the service provider and the SPB Manager. This... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.5.2 Procedure | Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. • Return an error with the code eTaskTypeUnknown if the Si1TaskType is not eSi1TaskType-DownloadSPB. • Return an error with the code eTaskNotAllowed if the function caller is not allowed to use... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.5.3 Response | The body part of the HTTP POST response for the "Si1.CreateSPReference" function shall contain Si1CreateSPReferenceResponse defined as follows: -- ASN1START Si1CreateSPReferenceResponse ::= SEQUENCE { aSi1ResponseHeader Si1ResponseHeader, -- Header of the response aSi1CreateSPReferenceResult CHOICE { aSi1CreateSPRefere... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.6 Si1.FinalizePreparation | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.6.1 Command | The "Si1.FinalizePreparation" function shall be used by the service provider to finalize the preparing procedure as defined in clause 12.3.2.2. If the selection of the Secondary Platform Bundle procedure, as defined in clause 12.3.2.2 has been executed after the creation of the CodeM procedure, as defined in clause 12.... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.6.2 Procedure | Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. • Verify the CodeM provided as input data. • Return an error with the code eCodeMUnknown if the CodeM is unknown to the SPB Manager. • Return an error with the code eCodeMNotAllowed if the Co... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.6.3 Response | The body part of the HTTP POST response for the "Si1.finalizePreparation" function shall contain Si1FinalizePreparationResponse defined as follows: -- ASN1START Si1FinalizePreparationResponse ::= SEQUENCE { aSi1ResponseHeader Si1ResponseHeader, -- Header of the response aSi1FinalizePreparationResult CHOICE { aSi1Finali... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.7 Si1.CancelPreparation | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.7.1 Command | The "Si1.CancelPreparation" function shall be used by the service provider to cancel a pending preparation procedure as defined in clause 12.3.2. The body part of the HTTP POST request for the "Si1.CancelPreparation" function command shall contain Si1CancelPreparationCommand defined as follows: -- ASN1START Si1CancelPr... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.7.2 Procedure | Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. • Return an error with the code eCodeMUnknown if a CodeM is provided as input data and is unknown to the SPB Manager. • Return an error with the code eCodeMNotAllowed if the bound SPB image dow... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.7.3 Response | The body part of the HTTP POST response for the "Si1.CancelPreparation" function shall contain Si1CancelPreparationResponse defined as follows: -- ASN1START Si1CancelPreparationResponse ::= SEQUENCE { aSi1ResponseHeader Si1ResponseHeader, -- Header of the response aSi1CancelPreparationResult CHOICE { aSi1CancelPreparat... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.8 Si1.HandleNotification | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.8.1 Command | The "Si1.HandleNotification" function shall be used by the SPB Manager to send any notifications as agreed with the service provider owning the pending related task. The agreement of the notifications to send is outside the scope of the present document. The body part of the HTTP POST request for the "Si1.HandleNotific... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.3.8.2 Procedure | Table 12.6 indicates which parameters shall be present depending on aNotificationEvent. Table 12.6: Si1 notification parameters aNotificationEvent aNotificationReceiverId aNotificationCallId aCodeM aSpbId aSpbType aPpIdentifier aTimeStamp aNotificationEvent aNotificationEventStatus eNotificationStatus-Eligibility • • •... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4 Si2 interface | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.1 Overview | The Si2 interface is used between the LBA and SPB Manager to provide a transport of the bound Secondary Platform Bundle image and the management commands on the Secondary Platform Bundles installed in the iSSP. The binding of the Si2 interface shall be performed over Hypertext Transfer Protocol version 2 (HTTP/2) as de... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.2 Si2.GetSpbmCertificate | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.2.1 Command | The "Si2.GetSpbmCertificate" function shall be used by the LBA during the capability negotiation procedure as defined in clause 12.3.3.1. The LBA shall use the "Si2.GetSpbmCertificate" function to provide the SPB Manager with the public SSP information (SspInfoPublic) as defined in clause 12.6.2.2.2 and terminal inform... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.2.2 Procedure | On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 1) Perform eligibility check based on Annex C as follows: a) The SPB Manager shall verify that the aSpblSpecVerInfo contained in the aSspInfoPublic and aLbaSpecVerInfo contained in aTerminalInfo are supported by itself. If a version is no... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.2.3 Response | The body part of the HTTP POST response for the "Si2.GetSpbmCertificate" function shall contain Si2GetSpbmCertificateResponse defined as follows: -- ASN1START Si2GetSpbmCertificateResponse ::= CHOICE { aSi2GetSpbmCertificateOk Si2GetSpbmCertificateOk, aSi2GetSpbmCertificateError Si2GetSpbmCertificateErrorCode } Si2GetS... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.3 Si2.GetBoundSpbImage | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.3.1 Command | The "Si2.GetBoundSpbImage" function shall be used by the LBA during the download procedure as defined in clause 12.3.3. The LBA shall use "Si2.GetBoundSpbImage" function to provide the SPB Manager with SSP credential (SspCredential) as defined in clause 12.6.2.4 and terminal information (TerminalInfo) as defined in cla... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.3.2 Procedure | On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: a) E... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.3.3 Response | The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" shall contain Si2GetBoundSpbImageResponse defined as follows: -- ASN1START Si2GetBoundSpbImageResponse ::= CHOICE { aSi2GetBoundSpbImageOk Si2GetBoundSpbImageOk, aSi2GetBoundSpbImageError Si2GetBoundSpbImageError } Si2GetBoundSpbImageOk ::= CHOICE { ... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.4 Si2.HandleNotification | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.4.1 Command | The "Si2.HandleNotification" function shall be used by the LBA to send any notification about the result of the Secondary Platform Bundle management to the SPB Manager. The body part of the HTTP POST request for the "Si2.HandleNotification" function command shall contain Si2HandleNotificationCommand defined as follows:... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.4.2 Procedure | On reception of Si2HandleNotificationCommand, the SPB Manager shall respond to the LBA to notify a successful reception of the notification. The response may contain a family identifier-specific notification response or a custodian- specific notification response. ETSI ETSI TS 103 666-2 V17.1.0 (2024-12) 80 Release 17 |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.4.4.3 Response | The body part of the HTTP POST response for the "Si2.HandleNotification" function shall contain Si2HandleNotificationResponse defined as follows: -- ASN1START Si2HandleNotificationResponse ::= SEQUENCE { aFamilySpecificNotificationResponseContainer FamilySpecificNotificationResponse OPTIONAL } FamilySpecificNotificatio... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5 Si3 interface | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.1 Overview | The Si3 interface is used between the LBA and the Secondary Platform Bundle Loader. The LBA shall use the Si3 interface to transfer a bound Secondary Platform Bundle image and management commands to the Secondary Platform Bundle Loader. The OFL agent host in the LBA and the OFL service hosted in the Secondary Platform ... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.2 Registries | The OFL service Gate in the Secondary Platform Bundle Loader shall support the registry entries defined in clause 7.3.1.2. |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.3 Commands | The OFL service Gate in the Secondary Platform Bundle Loader shall support the commands defined in clause 7.3.1.3. |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.4 Responses | The OFL service Gate in the Secondary Platform Bundle Loader shall support the reponses defined in clause 7.3.1.4. |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5 Functions | |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.1 Si3.GetSspInfo | The "Si3.GetSspInfo" function shall be used by the LBA during the capability negotiation procedure as defined in clause 12.3.3.1. The LBA shall use the "Si3.GetSspInfo" function to retrieve aSspInfoPublic from the Secondary Platform Bundle Loader. The "Si3.GetSspInfo" function command shall be GET_SSP_INFO. ETSI ETSI T... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.2 Si3.SetSpbmCredential | The "Si3.SetSpbmCredential" function shall be used by the LBA during the bound SPB image download procedure as defined in clause 12.3.3.2. The LBA shall use "Si3.SetSpbmCredential" function to deliver aSpbmCredential to the Secondary Platform Bundle Loader. The "Si3.SetSpbmCredential" function command shall be ANY_SET_... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.3 Si3.LoadBoundSpbInfo | The "Si3.LoadBoundSpbInfo" function shall be used by the LBA during the installation procedure as defined in clause 12.3.4. The LBA shall use the "Si3.LoadBoundSpbInfo" function to provide the Secondary Platform Bundle Loader with the aDoOperateParameter contained in the bound SPB image received from the SPB Manager as... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.4 Si3.LoadBoundSpbSds | The "Si3.LoadBoundSpbSds" function shall be used by the LBA during the installation procedure as defined in clause 12.3.4. The LBA shall use the "Si3.LoadBoundSpbSds" function to provide the Secondary Platform Bundle Loader with an element of aChangeSegmentParameter contained in the bound SPB image received from the SP... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.5 Si3.LoadBoundSpbSeg | The "Si3.LoadBoundSpbSeg" function shall be used by the LBA during the installation procedure as defined in clause 12.3.4. The LBA shall use the "Si3.LoadBoundSpbSeg" function to provide the Secondary Platform Bundle Loader with an element of aLoadSegmentParameter contained in the bound SPB image received from the SPB ... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.6 Si3.GetSspCredential | The "Si3.GetSspCredential" function shall be used by the LBA during the bound SPB image download procedure as defined in clause 12.3.3.2. The LBA shall use the "Si3.GetSspCredential" function to retrieve aSspCredential from the Secondary Platform Bundle Loader. The "Si3.GetSspCredential" function command shall be ANY_G... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.7 Si3.EnableSpb | The "Si3.EnableSpb" function shall be used by the LBA for the procedure to enable a Secondary Platform Bundle as defined in clause 12.4.1. The LBA shall use the "Si3.EnableSpb" function to provide the Secondary Platform Bundle Loader with the Secondary Platform Bundle identifier to enable. The "Si3.EnableSpb" function ... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.8 Si3.DisableSpb | The "Si3.DisableSpb" function shall be used by the LBA for the procedure to disable a Secondary Platform Bundle as defined in clause 12.4.2. The LBA shall use the "Si3.DisableSpb" function to provide the Secondary Platform Bundle Loader with the Secondary Platform Bundle identifier to disable. The "Si3.DisableSpb" func... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.9 Si3.DeleteSpb | The "Si3.DeleteSpb" function shall be used by the LBA for the procedure to delete a Secondary Platform Bundle as defined in clause 12.4.3. The LBA shall use the "Si3.DeleteSpb" function to provide the Secondary Platform Bundle Loader with the Secondary Platform Bundle identifier to delete. The "Si3.DeleteSpb" function ... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.10 Si3.GetSpbMetadata | The "Si3.GetSpbMetadata" function shall be used by the LBA to retrieve the SPB metadata of a Secondary Platform Bundle container installed in the iSSP. The "Si3.GetSpbMetadata" function command shall be GET_SPB_METADATA. The parameter of GET_SPB_METADATA command is a Secondary Platform Bundle identifier. The Secondary ... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.11 Si3.UpdateSpbState | The "Si3.UpdateSpbState" function shall be used by the LBA during the SPB state retrieving procedure as defined in clause 12.4.5. The LBA shall use "Si3.UpdatetSpbState" function to request the Secondary Platform Bundle Loader to update the value of SPB_ID registry. The "Si3.UpdateSpbState" function command shall be AN... |
a44d7bc2e2c4c46338f6b44c5203bab5 | 103 666-2 | 12.6.5.5.12 Si3.GetSpbState | The "Si3.GetSpbState" function shall be used by the LBA during the SPB state retrieving procedure as defined in clause 12.4.5. ETSI ETSI TS 103 666-2 V17.1.0 (2024-12) 87 Release 17 The "Si3.GetSpbState" function command shall be ANY_GET_PARAMETER command defined in ETSI TS 103 666-1 [3], clause 8.5.4 which allows the ... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 1 Scope | The present document provides the C-ITS Multi-Channel Operations functional architectural of the C-ITS architecture including the definition of requirements to the MCO entities, MCO mechanisms, MCO interfaces and MCO related application requirements. |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 2 References | |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 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 ... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 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... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 3 Definition of terms, symbols and abbreviations | |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 3.1 Terms | For the purposes of the present document, the following terms apply: access layer instance: fully parametrized (service channel, technology, TX power, etc.) transceiver entity in the access layer access layer instance ID: unique identifier for an access layer instance access layer instance group: set of access layer in... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 3.2 Symbols | Void. |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: A-PDU Application-Protocol Data Unit AF_SAP Application-Facilities Service Access Point ALI Access Layer Instance AliID Access layer instance Identifier AliGroupID Access Layer Instance Group Identifier NOTE: The abbreviations AliID and AliGro... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 4 Overview | Cooperative-Intelligent Transport Systems (C-ITS) applications require the exchange of information between C-ITS stations (C-ITS-Ss), see ETSI TR 103 439 [i.1], therefore they need to provide their information to the lower layers for dissemination to other C-ITS-Ss. In C-ITS Release 1 the number of use cases to be supp... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 5 MCO architecture | |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 5.1 Introduction | The C-ITS MCO architecture is depicted in Figure 1. MCO is a cross layer functionality realized by entities at different layers. The MCO functionalities are C-ITS station internal functionalities. In fact it can be recognized that at all layers functionalities involved in the MCO process exist: at the Application layer... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 5.2 Facilities Layer MCO functionalities | The Facilities layer MCO functionalities are all part of the MCO_FAC, which is realized by a set of entities located at the Facilities layer. MCO_FAC manages the dissemination of messages to lower layers when triggered by applications with their Message Generating Services (MGSs). MCO_FAC interacts with the Message Tri... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 5.3 Networking & Transport Layer MCO functionalities | The Networking & Transport layer MCO functionalities are all part of the MCO_NET service. MCO_NET has interfaces with the GN Core, GN ALI group handlers, and the Facilities and Access layer functionalities. At the Networking & Transport Layer there is an entity called GN Core and entities called GN Access Layer Instanc... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 5.4 Access layer MCO functionalities | The access layer of an MCO capable C-ITS-S will operate a set of more than one transceiver simultaneously. Such set of transceivers may be capable of implementing different access layer technologies (e.g. ITS-G5, LTE-V2X, etc.), each of which may be parameterized to allow adaptation to the requirements of the applicati... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 6 MCO Mechanisms | |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 6.1 Introduction | To facilitate an MCO approach that takes into account the application requirements and support their fulfilment through various channels and technologies independently, two specific mechanisms are defined. The first mechanism involves the Applications and Facilities layer through the definition of Functional Configurat... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 6.2 The Functional Configuration mechanism | In principle, for each message to be disseminated, communication configurations could be selected flexible for any specific use case by use case or application by application. In Release 1 the dissemination configurations are statically defined, CAS for example makes use of a fixed channel and fixed priority level. In ... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 6.3 The Access Layer Instance mechanism | Although the applications may provide several dissemination possibilities to the MHE by suggesting FCPs, the MHE at the Facilities layer shall decide which Access Layer Instance (ALI) is to be used. As identified in clause 5.4, the "Access Layer Instance" (ALI) represents a specific access layer instantiation of a tran... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 7 MCO application requirements | |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 7.1 Introduction | C-ITS applications are expected to provide end user services with well-defined Quality of Services. QoS is very important since many of these end-user services are safety related and therefore a service degradation would not be acceptable. In this regard MCO plays a key role since it will be up to the MCO functionaliti... |
4845f58f855d91abaca39bacf5ad450d | 103 697 | 7.2 MCO related application requirements | In order to make sure MCO will operate in the most efficient way so as to guarantee the required QoS, the application shall fulfil the following requirements: REQ_APP_001: A Release 2 application being an extension of the same already deployed Release 1 application, shall provide the Release 1 functionalities in such a... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 1 Scope | The present document is part of a series of documents that specify the technical solution for the Smart Secure Platform (SSP), according to the requirements listed in ETSI TS 103 465 [i.2]. The present document contains generic technical solutions for different aspects of SSP functionality. It does not specify any spec... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 2 References | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-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... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-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... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 102 216 [i.1] and the following apply: access control: metadata defining access rights of an accessor or a group of accessors NOTE: It is an element of the access control list. access control list: list of access controls attached to the resource acce... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 3.2 Symbols | Void. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Accessor Authentication Application AAS Accessor Authentication Service ACL Access Control List AID Application IDentifier APDU Application Protocol Data Unit ASN.1 Abstract Syntax Notation One ATR Answer To Reset C-APDU Command - APDU CA ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 3.4 Coding conventions | All bytes specified as RFU shall be set to '00' and all bits specified as RFU shall be set to 0, and their values shall be ignored. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4 Introduction | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4.1 Background | The present document defines a secure element which is modular and allows for different combinations of form factors, physical and electrical interfaces, transport layers, file system and security requirements based on the targeted use-case. This secure element is called Smart Secure Platform (SSP). This platform is de... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4.2 Document layout | The present document specifies: • the definition and overview of an SSP; • the possible physical interface(s) between the terminal and the SSP; • the possible transport protocol(s) used between the terminal and the SSP; • the core features and characteristics of an SSP, including security requirements; • various SSP cl... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4.3 References to UICC | The present document contains several references to UICC specifications such as ETSI TS 102 221 [1] and ETSI TS 102 223 [6]. In these cases, the word "UICC" shall be replaced with "SSP" as needed. Similarly, the word "card" used in ISO/IEC 7816-3 [3] and ISO/IEC 7816-4 [4] shall be replaced with "SSP" as needed. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4.4 ASN.1 syntax | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4.4.1 Introduction | The description of some data objects in the present document is based on ASN.1 specified in Recommendation ITU-T X.680 [15] and encoded in TLV structures using Distinguished Encoding Rule (DER) encoding as specified in Recommendation ITU-T X.690 [16]. This provides a flexible description of those data objects. The comp... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 4.4.2 Start of ASN.1 | The complete ASN.1 code is provided for reference in Annex L. -- ASN1START SSPDefinitions { itu-t (0) identified-organization (4) etsi (0) smart-secure-platform (3666) part1 (1) } DEFINITIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN EXPORTS ALL; /* Imports */ IMPORTS ESSPCapabilities -- SSPSpecificCapabilities fo... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5 SSP architecture | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5.1 Overview | The SSP is a secure element platform intended for use in a number of use cases which may have very different requirements. For that reason, the SSP is designed to be a modular platform offering a core set of features as well as a number of options that need to be selected at the time of implementation based on the inte... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5.2 SSP software architecture | SSP Applications are programs running in the SSP. Examples for SSP Applications are: • applications based on a file system and commands, e.g. as defined in ISO/IEC 7816-4 [4]; • applications running in standardized runtime environment, e.g. as defined in ETSI TS 102 241 [12]; • applications running as native applicatio... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5.3 SSP hardware architecture | A typical SSP consists of a processing unit, security components, I/O ports and memory (volatile and non-volatile). Figure 5.2 shows a typical SSP. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 21 Release 17 Figure 5.2: Typical SSP hardware architecture |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5.4 Protocol stacks | The physical interface(s) between the SSP and the device might be selected from a range of options. The SSP may have multiple physical interfaces. The data link layer used over the physical interface might also be selected from a range of options. The SSP should provide means for controlling (e.g. activating, deactivat... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5.5 Execution frameworks | The optional or mandatory support of specific execution frameworks is defined for each specific SSP class. The SSP may support an execution framework as defined for the UICC according to ETSI TS 102 241 [12] based on the Java Card™ Platform [9], [10] and [11]. The definition of additional Execution Frameworks for the S... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 5.6 Bundle Interoperability | SSP Secondary Platform Bundles are generated for a specific Primary Platform and are in general not binary interoperable with other Primary Platforms. If an SPB created for one Primary Platform is intended to be loaded onto an SSP with another Primary Platform which is different in hardware or software, even if only in... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6 SSP characteristics | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.1 Form factors | The overall definition of the SSP is independent of the form factor, unless specified differently for a particular SSP class. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2 Power | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2.1 Power mode | The following power modes are defined: • OPERATIONAL: when the SSP performs an internal process or processes incoming data from any of its interfaces. This mode also includes the transmission of data from and to the terminal. • SUSPENDED: the SSP does not consume any power, with the ability to resume the logical state ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.