hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.2.3 Use case 3.3 - Storage of user data | The SSP may be used to store user data that is considered by the user as relevant to be protected (e.g. documents, pictures, videos). |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.2.4 Use case 3.4 - Storage of emails | The SSP may be used to securely store emails. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.3 Interaction with existing features (informative) | None. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 19 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5 Use case 4 - Security token/HSM | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.1 Overview | The SSP can be used to provide security services for various applications as described below. It will be the provider of security and cryptographic applications such as: • Signature generation/verification. • Bulk encryption/decryption. • Hardware root of trust. • Secure boot. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.2 Sub use cases | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.2.1 Use case 4.1 - Security for VPN | The SSP acts as a security token to provide employees access to the VPN of their company. The data traffic over the VPN tunnel may be encrypted/decrypted online by the SSP. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.2.2 Use case 4.2 - Security token for email | The SSP can be used as a security token to protect access to emails. The emails may also be stored securely in the SSP (see clause 6.4.2.4). |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.2.3 Use case 4.3 - Security token for network elements | Wide area networks, including cellular networks, make more and more usage of small distributed network equipment in order to provide more flexibility in the network deployment but also in order to improve performance by reducing the distance between the end user and this network equipment. In order to secure all these ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.2.4 Use case 4.4 - Secure boot | The security capability service could be centralized and managed by the SSP. During booting, the SSP could provide integrity protection to ensure that the signed image can be loaded, but prevent unauthorized third-party code from running on different processors or chips. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.5.3 Interaction with existing features | FFS. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.6 Use case 5 - Multiple applications | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.6.1 Overview | The SSP may support multiple applications for example, multiple network access applications, multiple security token applications or combinations thereof. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 20 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.6.2 Sub use cases | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.6.2.1 Use case 5.1 - Multiple applications active at the same time | An SSP supports several applications. One of them is a network access application e.g. a USIM, and in addition an ID application, e.g. a driver's license. When the driver's license application is being activated, e.g. during a control by the police, it needs to be activated in parallel to the still activated NAA and da... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.6.2.2 Use case 5.2 - Multiple applications from independent stakeholders | An SSP supports multiple applications. Those applications may belong to different stakeholders. For example an NAA may belong to an MNO, a payment application may belong to a payment institution, while a secure key storage may belong to a service provide who manages the device in which the SSP is embedded. For easy dep... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.6.3 Interaction with existing features | It needs to be clarified if also several NAAs can be active at the same time. Potential interferences between applications should be avoided. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.7 Use case 6 - Optimization for LPWA IoT | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.7.1 Overview | Low Power Wide Area (LPWA) wireless technology is a generic term for a group of technologies including NB-IoT, Cat-M, even 5G massive IoT technology, etc. Such LPWA technologies differentiate themselves from other technologies in terms of: • Wide area coverage. • Low cost. • Long battery life. • Low data throughput. It... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.8.1 Overview | The 3GPP next generation mobile communication system, also called 5G, is requiring to store the network access credentials in a tamper resistant secure hardware component. The processing of the credentials with the authentication algorithm is required to be performed inside the tamper resistant secure hardware componen... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.8.2 Sub use cases | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.8.2.1 Use case 7.1 - Storage and processing of network access credentials | The next generation system requires the storage of credentials and identities (human and machine) in the UE. Subscription (human and machine) credentials and identities allow the network operator to authenticate its subscribers. Subscription authentication is needed to identify the origin and destination of the communi... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.8.2.2 Use case 7.2 - Interworking with non-3GPP systems | The 5G network is required to interwork with various non-3GPP systems. These include fixed line access, satellite access, WLAN access, etc. For authentication between the UE and the 5G network over a non 3GPP access the authentication methods defined in ETSI TS 133 501 [10] are 5G AKA or EAP AKA. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.8.3 Interaction with existing features | The 5G system is supposed to interwork with existing 3GPP networks, e.g. in Phase 1 of 5G it is the interworking of the new radio technology with the existing LTE network core, EPC. This includes the authentication but also existing services that are supported by the existing UICC and the 3GPP applications (SIM, USIM, ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.9 Use case 8 - IMEI protection | One issue identified by several governments is the high number of stolen mobile devices. The current mechanism of blacklisting stolen devices does not really solve the issue, as the mechanism relies on the equipment identifier (IMEI) which is not tamper resistant. Studies in the US have shown that it may take only seve... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.10 Use case 9 - Integrated secure element | An integrated secure element can be a secure element integrated in a larger hardware platform. One example is a system on chip that integrates modem, processing and security functionalities where the integrated secure element is part of such a SoC. The SoC is normally soldered into the terminal and is therefore an inte... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.1 Introduction | 3GPP has identified several features that require an evolution of the current UICC functionalities to support new or existing 3GPP features. The SSP is intended to be an alternative for the current UICC, which is already an agreed option in ETSI TS 133 501 [10] and thus needs to support the features required by 3GPP. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2 Existing features | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.1 Introduction | The following sections describe existing features in 3GPP that make use of the UICC applications defined in 3GPP (USIM, ISIM, HPSIM, etc.) and impose technical requirements that may not be optimally supported by the existing UICC as the platform. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.2 File Storage | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.2.1 Introduction | In recent 3GPP releases, the number of configuration files for new 3GPP features that need to be stored in the UICC has consistently increased. In many of these cases, a complex and large XML schema is defined in 3GPP to provision the configuration into the device with OMA-DM. Due to existing requirements to have the p... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.2.2 Examples from 3GPP specifications | 6.11.2.2.2.1 Configuration Parameters for MCPTT The parameters stored in the USIM follow the specification of the management object for the ME as defined in ETSI TS 124 383 [i.5]. The structure of the management object is, depending on the required services, complex and may therefore contain a large amount of data. The... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.3 Internet of Things | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.3.1 Power efficiency | 6.11.2.3.1.1 Introduction In the recent years, power consumption of the UE has become a very important aspect due to the rise of several IoT use cases that require that the device remains active for long periods of time, without the possibility to re-charge it. The overall power consumption is obviously composed by the... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.3.2 Hardware flexibility | For many use cases in IoT, devices may be optimized in size, functionality and according to the specific needs of the IoT application they are intended for. Some devices may be very small, e.g. simple sensors and may have specific requirements related to size and power consumption. For such devices it would be benefici... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.3.3 Electrical Interface and protocols | In several use cases for IoT it may also be beneficial for a device to not have to implement the current ISO interface to a UICC but rather rely on interfaces and protocols already in use inside the device. Examples of such interfaces are I2C or SPI. Additional aspects to consider are: • Number of wires. • Transmission... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.4 Toolkit | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.4.1 User-related applications | 6.11.2.4.1.1 Interaction with user authentication Issues found when using the USAT command on which user authentication is needed: no mean to retrieve the user authentication status. For instance ENVELOPE (ProSe report) requires user authentication. The same issue is identified for second level applications. 6.11.2.4.1... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.4.2 System applications | 6.11.2.4.2.1 Proactive commands In the ME-UICC interface defined in the existing platform, the UICC plays a slave role in the communication with the ME in a way that the UICC cannot initiate by itself the communication with the ME in the case a command from the UICC to the ME is requested to be sent. To enable this cas... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.2.5 Concurrent operation of applications | The existing platform supports multiple applications on different channels, with the limitation of one command at a time. This may result in the interface to the card being blocked by one of these applications, potentially causing disruption in the operation of 3GPP applications. For instance, some non-telecommunicatio... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3 Possible new features | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3.0 General | 3GPP also considered additional use cases, describing new features that are not specified in 3GPP but may be considered during the definition of a new secure platform. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 27 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3.1 Storage of data | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3.1.1 The ability to provide the ME with storage space | With such feature the new secure platform could provide a possibility for a device to store specific data, for example, sensitive information inside the new secure platform. This would require an efficient mechanism to transfer data in a fast, efficient and secure way. Such a mechanism needs to ensure that only the aut... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3.1.2 The ability to provide the new secure platform with storage space in the ME | Such a feature would enable the new secure platform to make use of memory available in the ME. This can be data that is encrypted and therefore stored in a secure way or data that is not sensitive. Such a feature could allow new use cases which are currently not possible due to the resource limitations in current UICCs... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3.2 Extensibility of functionality | An update of part of or the whole Secure Platform functionality may be triggered by the need to extend the set of supported features. This includes: • Extension of the supported command set. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.11.3.3 Multiple application environment | Multiple applications may be hosted by the Secure Platform and may be active at the same moment in some deployments. Multiple non-telecommunication applications may be communicating at the same moment. Another case is when a network authentication is processed at the same moment as an over-the-air update is performed. ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.12 Use Case 11 - SSP remote management | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.12.1 Overview | The SSP can be used to provide a security service on a wide range of devices via an SPB provided by the Service Provider. Besides the local management functions defined for the end user, in some cases, the Service Provider and/or the subscriber needs to have the capability to remotely manage an SPB. Dependent on the ty... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.12.2 Telecommunication industry use cases | In the telecommunication industry, there are several use cases where the remote management (e.g. remotely install, delete, enable, disable) of telecom SPB can be useful or even required, such as in M2M services, devices in enterprise environment or even consumer usage. The different usages have been identified for othe... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.13 Use Case 12 - Discovery service | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.13.1 Overview | The SSP Discovery Service (SSP DS) is one of the methods for the SSP device to obtain the information (e.g. the address of an SPBM and a matching identifier) which is used by the LBA to initiate the download of an SPB or a remote management command. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.14 Use Case 13 - SSP device change | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.14.1 Overview | An end user subscribes to a service with a service provider, and installs an SPB in his or her device. After some time the end user gets a new device and wants to use the same services attached to the SPB with the new device. This can be achieved by remote provisioning of the new device with an SPB providing the same s... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7 SSP Classes overview | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.1 Introduction | As the SSP covers a wide set of use cases, requirements for the SSP are split into requirements that are applicable to all types of SSPs and requirements that are specific to a particular SSP class. This clause provides an overview on the currently defined SSP classes. Those are iSSP, eSSP and rSSP as defined below. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.2 iSSP: integrated SSP | An iSSP is integrated into a System on Chip (SoC), so it does not have a standardized form factor. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.3 eSSP: embedded SSP | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.3.0 General | An eSSP is implemented as a discrete tamper resistant hardware component, that is embedded, non-removable and may have a standardized form factor. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.3.1 eSSP: Type 1 | An eSSP Type 1 is an eSSP which supports the SCL and which may support different electrical interfaces. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 29 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.3.2 eSSP: Type 2 | An eSSP Type 2 inherits the eSSP Type 1 functionalities and, in addition, supports the primary/secondary platform architecture. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 7.4 rSSP: removable SSP | An rSSP is implemented as a discrete tamper resistant hardware component. This component is removable and shall have a standardized form factor. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8 Requirements applicable for all SSP classes | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.1 General | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.1.0 Introduction | This clause defines the applicability of requirements: Mandatory requirements in general section: Any product, regardless of its class, shall support these features to be compliant with the SSP technical specification. Optional requirements in general section: The support of the respective features by a dedicated produ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.1.1 General - mandatory requirements | Identifier Requirement REQ-15-SSP-8.1.1-01 The SSP shall be optimized for power efficiency. REQ-15-SSP-8.1.1-02 There shall be an option for the SSP to operate in different power modes (e.g. IDLE, SUSPENDED, OPERATIONAL). REQ-15-SSP-8.1.1-03 The timing behaviour when switching between power modes shall be clearly defin... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.1.2 General - optional requirements | Identifier Requirement REQ-15-SSP-8.1.2-01 There shall be an optional mechanism to negotiate the transmission rate between the terminal and the SSP. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.1.3 General - use case specific requirements | Identifier Requirement REQ-15-SSP-8.1.3-01 (3GPP) The SSP shall provide a mechanism for the secure platform for 3GPP applications to initiate a proactive session with the ME. REQ-15-SSP-8.1.3-02 (3GPP) The SSP shall provide a mechanism for rich user interface for applications on the secure platform. REQ-15-SSP-8.1.3-03... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2 Application and file structure | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.1 SSP applications | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.1.1 SSP applications - mandatory requirements | Identifier Requirement REQ-15-SSP-8.2.1.1-01 The activation and the usage of an SSP application shall be protected by access conditions as defined in clause 8.2.3. REQ-15-SSP-8.2.1.1-02 The SSP shall provide a mechanism allowing to list the SSP application(s) available in the SSP. REQ-16-SSP-8.2.1.1-03 It shall be poss... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.1.2 SSP applications - optional requirements | Identifier Requirement REQ-15-SSP-8.2.1.2-01 There shall be an option for the SSP to support concurrent SSP applications. REQ-15-SSP-8.2.1.2-02 There shall be an option for the SSP to support multiple active SSP applications. REQ-15-SSP-8.2.1.2-03 There shall be an option for the SSP to support SSP applications using t... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.1.3 SSP applications - use case specific requirements | Identifier Requirement REQ-15-SSP-8.2.1.3-01 CAT commands and protocols transported via SCL shall support payloads larger than 255 bytes. REQ-15-SSP-8.2.1.3-02 Proactive commands transported via SCL shall be supported without the need for proactive polling. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.2 File system | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.2.1 File system - mandatory requirements | None. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.2.2 File system - optional requirements | Identifier Requirement REQ-15-SSP-8.2.2.2-01 Support of file systems as described in this clause is optional for the SSP. REQ-15-SSP-8.2.2.2-02 The SSP file system shall be able to handle large files (100 MB or larger). REQ-15-SSP-8.2.2.2-03 The SSP shall provide an option for supporting UICC file system as defined in ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.2.3 File system - class dependent requirements | None. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.2.4 File system - use case specific requirements | Identifier Requirement REQ-15-SSP-8.2.2.4-01 (3GPP) The SSP shall support efficient access to large and complex configuration data in the sense that an ME does not need to read the complete content if only a part of the configuration data needs to be read at a time. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 32 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.3 SSP application and file system access conditions | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.3.1 SSP application and file system access conditions - mandatory requirements | Identifier Requirement REQ-15-SSP-8.2.3.1-01 The SSP shall provide an access condition mechanism based on end user verification. REQ-15-SSP-8.2.3.1-02 Access to the SSP applications and file system from a remote entity shall use a strong authentication and authorization mechanism. REQ-16-SSP-8.2.3.1-03 The SSP shall su... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.3.2 SSP application and file system access conditions - optional requirements | Identifier Requirement REQ-15-SSP-8.2.3.2-01 The end user verification mechanisms may include PIN code verification. REQ-15-SSP-8.2.3.2-02 The end user verification mechanisms may include biometric. REQ-15-SSP-8.2.3.2-03 The SSP shall provide an option for supporting application and file system access conditions as def... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.4 Terminal support for SSP applications | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.4.1 Terminal support for SSP applications - mandatory requirements | Identifier Requirement REQ-15-SSP-8.2.4.1-01 The terminal that supports IP shall support a mechanism to relay IP network connections from SSP applications. REQ-15-SSP-8.2.4.1-02 The mechanism as described in REQ-15-SSP-8.2.4.1-01 shall be able to use currently available IP network connection in the terminal. REQ-15-SSP... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.2.4.2 Terminal support for SSP applications - optional requirements | Identifier Requirement REQ-15-SSP-8.2.4.2-01 There shall be an option for the SSP application to provide IP network connection parameters such as an APN to the terminal (see note). NOTE: The IP network connection parameters shall only be used for the SSP application requesting the connection and shall not affect the ot... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3 Protocols | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.1 Protocols - mandatory requirements | None. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 33 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.2 Protocols - optional requirements | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.2.1 SCL network layer requirements | Identifier Requirement REQ-15-SSP-8.3.2.1-01 The SSP should support the SCL network layer as defined in the present document. REQ-15-SSP-8.3.2.1-02 The SCL network layer shall provide a means to address a targeted SSP application without additional application selection mechanisms (e.g. SELECT AID). REQ-15-SSP-8.3.2.1-... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.2.2 SCL Transport layer requirements | Identifier Requirement REQ-15-SSP-8.3.2.2-01 The SSP may support the SCL transport layer as defined in the present document. REQ-15-SSP-8.3.2.2-02 The SCL transport layer shall be independent of all the underlying layers (network, physical and link layers). REQ-15-SSP-8.3.2.2-03 The SCL transport layer shall be indepen... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.2.3 SCL session layer requirements | Identifier Requirement REQ-15-SSP-8.3.2.3-01 The SSP may support the SCL session layer as defined in the present document. REQ-15-SSP-8.3.2.3-02 The SCL session layer shall provide an optional means to manage (open, close) a session to a targeted application hosted by the SSP. REQ-15-SSP-8.3.2.3-03 The SCL session laye... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.2.4 Presentation layer requirements | Identifier Requirement REQ-15-SSP-8.3.2.4-01 The SSP may support the presentation layer as defined in the present document. REQ-15-SSP-8.3.2.4-02 The presentation layer may be application specific or generic as defined in the present document. REQ-15-SSP-8.3.2.4-03 The generic presentation layer shall provide a means t... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.2.5 Common underlying protocol stack requirements | Identifier Requirement REQ-15-SSP-8.3.2.5-01 The SSP shall provide a means for managing the SCL underlying data flow control. REQ-15-SSP-8.3.2.5-02 The SSP shall provide a means for getting the MTU of the SCL underlying protocols. REQ-15-SSP-8.3.2.5-03 The SSP shall provide an optional means for controlling (e.g. activ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.3 Protocols - class dependent requirements | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.3.3.1 Protocols - requirements for SPI | Identifier Requirement REQ-15-SSP-8.3.3.1-01 The SSP shall support the SPI interface if required by the corresponding SSP class. REQ-15-SSP-8.3.3.1-02 The SSP may represent the SPI slave or master. REQ-15-SSP-8.3.3.1-03 Once defined the layers "1. Physical", "2.Data Link", "3.Network", "4.Transport" shall comply with t... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.4 Electrical and physical Interface | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.4.1 Electrical and physical Interface - mandatory requirements | Identifier Requirement REQ-15-SSP-8.4.1-01 The SSP shall support a mechanism to suspend and resume. REQ-15-SSP-8.4.1-02 The electrical and physical interface shall be independent from the form factor. REQ-15-SSP-8.4.1-03 Electrical characteristics of the SSP which are not directly linked to a physical interface (e.g. c... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.4.2 Electrical and physical Interface - class dependent requirements | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.4.2.1 Electrical and physical Interface requirements | Identifier Requirement REQ-15-SSP-8.4.2.1-01 There shall be an option for the SSP to support the ISO/IEC 7816 [1] electrical and physical interface as defined in ISO/IEC 7816-3 [7]. REQ-15-SSP-8.4.2.1-02 There shall be an option for the SSP to support the SPI electrical and physical interface. REQ-15-SSP-8.4.2.1-03 The... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.4.2.2 Electrical and physical Interface: SPI requirements | Identifier Requirement REQ-15-SSP-8.4.2.2-01 The electrical parameters of the SPI interface shall be clearly defined (e.g. signalling levels, slew rates, input & output driver characteristics). REQ-15-SSP-8.4.2.2-02 The timing parameters of the SPI interface shall be clearly defined (e.g. clock rates, bit lengths, sign... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 8.4.2.3 Electrical and physical Interface: I2C requirements | Identifier Requirement REQ-15-SSP-8.4.2.3-01 The I2C interface shall support I2C master mode. REQ-15-SSP-8.4.2.3-02 The I2C interface shall support I2C slave mode. REQ-15-SSP-8.4.2.3-03 The I2C interface shall support I2C multi-master mode. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.