hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 3.4.2 Logical operators | For the purposes of the present document, the following C-language mathematical symbols apply: || Logical OR ETSI ETSI TS 103 466 V1.1.1 (2016-10) 11 |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 3.4.3 Relational operators | For the purposes of the present document, the following C-language mathematical symbols apply: > Greater than ≥ Greater than or equal to < Less than ≤ Less than or equal to == Equal to != Not equal to |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 3.4.4 Assignment | For the purposes of the present document, the following C-language mathematical symbols apply: = Assignment operator |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 3.4.5 Mnemonics | The following mnemonics are defined to describe the different data types used in the coded DAB audio bit-stream: bslbf Bit string, left bit first, where "left" is the order in which bit strings are written in the present document. Bit strings are written as a string of 1 s and 0 s within single quote marks, e.g. "1000 ... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 3.4.6 Method of describing bit stream syntax | The bit stream described in clause 5 is the bit stream that exists in the DAB-receiver at the interface between channel decoder and audio decoder. The bit stream is described using the "C" software language which is used to program the processor which assembles the programme audio and associated data for channel coding... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 3.5 Convention | Unless otherwise stated, the following notation, regarding the order of bits within each step of processing is used: • in figures, the bit shown in the left hand position is considered to be first; • in tables, the bit shown in the left hand position is considered to be first; • in byte fields, the Most Significant bit... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 4 Introduction | The DAB system standard [1] allows audio (programme) services to be carried using either DAB audio or DAB+ audio. The present document defines the way that audio (programme) services are carried when using DAB audio (MPEG layer II audio coding). Two sampling rates are permitted for DAB audio coding, 48 kHz and 24 kHz. ... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5 DAB audio coding | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.1 Introduction | An overview of the principal functions of the audio coding scheme is shown in the simplified block diagram of the DAB audio encoder (see figure 1). The main characteristics of the audio coding system, like audio modes, bit rates and audio frame length are given in clause A.2, whereas the characteristics of the input au... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2 Audio encoding | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.0 General | The source encoder for the DAB system is the MPEG Audio Layer II (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) encoder with restrictions on some parameters and some additional protection against transmission errors. In the ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4] International Standards only the encoded audio bit st... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.1 Analysis sub-band filter | An analysis sub-band filter should be used to split the broadband audio signal with sampling frequency fs into 32 equally spaced sub-bands, each with a sampling frequency of fs/32. This filter, called a poly-phase analysis filter bank, is critically sampled (i.e. there are as many samples in the sub-band domain as ther... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.2 Scale Factor calculation | In each sub-band, 36 samples shall be grouped for processing. Before quantization, the output samples of the filter bank should be normalized. The calculation of the Scale Factor (ScF) for each sub-band shall be performed every 12 sub-band samples. The maximum of the absolute value of these 12 samples shall be determin... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.3 Coding of Scale Factors | This clause is partly of informative, and partly of normative nature. The index "iscf" in table 1 is represented by 6 bits, MSb first. The ScF of a certain sub-band shall be transmitted only if a non-zero number of bits has been allocated to this sub-band. A DAB audio frame corresponds to 36 sub-band samples and theref... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.4 Coding of Scale Factor Selection Information | The ScFSI shall be coded by an unsigned two bit binary word, MSb first, which is also to be found in the table 3, showing the Scale Factor transmission patterns. Only the ScFSI for the sub-bands which will have a non-zero bit allocation shall be transmitted. ETSI ETSI TS 103 466 V1.1.1 (2016-10) 18 |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.5 Psychoacoustic model | A psychoacoustic model should calculate a just-noticeable noise-level for each sub-band in the filter bank. This noise level should be used in the bit allocation procedure to determine the actual quantizer for each sub-band. The final output of the model is a Signal-to-Mask Ratio (SMR) for each sub-band. For a high cod... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.6 Bit allocation | A bit allocation procedure shall be applied. Different strategies for allocating the bits to the sub-band samples of the individual sub-bands are possible. A reference model of the bit allocation procedure is described in clause C.3. The principle used in this allocation procedure is minimization of the total noise-to-... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.7 Bit allocation coding | In order to increase the coding efficiency, only a limited number of possible quantizations are permitted. Both the number and the quantizations may be different from one sub-band (denoted as "sb" in tables 5 to 7) to another. Only the index with word length "nbal" given in tables 5 to 7, which depends on the bit rate ... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.8 Quantization and coding of sub-band samples | A quantization process of the sub-band samples shall be applied. The following description of this process is informative, but the coding of the sub-band samples has to follow normative rules. Each of the 12 consecutive sub-band samples, which are grouped together for the scaling process, should be normalized by dividi... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.2.9 Formatting of the audio bit stream | The frame formatter of the audio encoder shall take the bit allocation, ScFSI, ScF and the quantized sub-band samples together with header information and a few code words used for error detection to format the MPEG Audio Layer II (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) bit stream. It shall further divide this bi... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3 Semantics of the audio bit stream | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1 MPEG Audio Layer II bit stream | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1.1 Audio sequence | The DAB audio coding system uses the MPEG Audio Layer II (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) format. A graphic representation of an audio frame in MPEG Audio Layer II (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) format is given in the upper part of figure 4. Audio_frame: part of the bit stream that is decoda... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1.2 Audio frame | header: part of the bit stream containing synchronization and state information. error_check: part of the bit stream containing information for error detection of significant audio side information. audio_data: part of the bit stream containing information on the audio samples. ancillary_data: part of the bit stream th... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1.3 Audio frame header | The first 32 bit (four bytes) are header information. syncword: the bit string "1111 1111 1111". ID (Identifier): this 1-bit flag shall identify the audio coding algorithm, as follows: 0: ISO/IEC 13818-3 [4] or MPEG-2 Audio extension to lower sampling frequencies; 1: ISO/IEC 11172-3 [2]. Layer: this 2-bit field shall i... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1.4 Error check | crc_check: a 16 bit parity check word used for error detection of the most error-sensitive part of the audio information within the encoded audio bit stream. This information includes the third and fourth bytes of the MPEG Audio (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) header, bit allocation and Scale Factor Selec... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1.5 Audio data | allocation[ch][sb]: contains information concerning the quantizers used for the samples in sub-band sb in channel ch, whether the information on three consecutive samples of a granule has been grouped to one code, and on the number of bits used to code the samples. The meaning and length of this field depends on the nu... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.1.6 Ancillary data | ancillary_bit: user definable. The number of ancillary bits (no_of_ancillary_bits) equals the available number of bits in an audio frame minus the number of bits actually used for header, error check and audio data. The no_of_ancillary_bits corresponds to the distance between the end of the audio data in an MPEG Audio ... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2 DAB audio bit stream | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.0 Introduction | The DAB system uses the MPEG Audio Layer II (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) format with additional specific information, necessary for the DAB application. The field for this additional specific information is defined in DAB to contain the DAB fields Extended Programme Associated Data (X-PAD), Audio Scale... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.1 DAB audio sequence | A detailed graphic representation of the content and the structure of a DAB audio frame is given in figures 5 and 6. DAB_audio_frame: part of the bit stream that is decodable by itself. Besides the information for 1 152 audio samples, it contains all specific DAB audio information (see also definition given in clause 5... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.2 DAB audio frame | DAB_audio_frame_header: part of the bit stream (the first 32 bits) containing relevant state information for the DAB audio decoder. error_check: see definition given in clause 5.3.1.2. 2 Bit 6 Bit 3 sub-band samples are corresponding to 96 audio PCM samples Gr0 Gr11 00 01 10 11 F- PA D SCF CRC stuff S cale F actors SCF... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.3 DAB audio frame header | The DAB audio frame header is identical to the MPEG Audio (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) header. See definitions given in clause 5.3.1.3 for the semantic meaning of the following parameters: • bitrate_index; • sampling_frequency; • padding_bit; • private_bit; • mode; • mode_extension; • copyright; • orig... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.4 Error check | See definitions given in clause 5.3.1.4. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.5 Audio data | See definitions given in clause 5.3.1.5. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.6 Audio stuffing bits | The total number of bits available for audio_data per DAB audio frame for a sampling frequency of 48 kHz equals (bit_rate × 0,024) minus bits used by DAB_audio_frame_header(), error_check(), x_prog_ass_data(), scf_error_check(), and f_prog_ass_data(), and in the case of 24 kHz sampling frequency, this number equals (bi... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.7 Extended Programme Associated Data (X-PAD) | x-pad_byte[i]: ith byte of X-PAD. A variable number of bytes, no_of_x-pad_bytes is used for X-PAD, i.e. the length of this field is variable in multiples of bytes. The actual value is given in [1] clause 7.4. ETSI ETSI TS 103 466 V1.1.1 (2016-10) 30 |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.8 Scale Factor Error Check (ScF-CRC) | scf-crc_check[i]: ith word used for Cyclic Redundancy Check (CRC) words, each protecting the Scale Factors of a group of sub-bands of the following DAB audio frame. The actual number of CRC words, no_of_scf_error_checks depends upon the bit-rate and audio mode (see clause B.3). In the case of ISO/IEC 11172-3 [2], eithe... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.3.2.9 Fixed Programme Associated Data (F-PAD) | f-pad_byte[i]: ith byte of F-PAD. A fixed number of two bytes for Fixed Programme Associated Data (F-PAD), comprising the last two bytes of the DAB audio frame, is used. ETSI ETSI TS 103 466 V1.1.1 (2016-10) 31 Figure 6: DAB audio frame structure bit allocation DAB audio frame header Scale Factors CRC SCFSI X-PAD SCF C... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4 Audio bit stream syntax | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.0 Introduction | The details of the audio frame can be found in this clause, which describes the MPEG Audio Layer II bit stream syntax (clause 5.4.1), and the DAB audio bit stream syntax (clause 5.4.2). Apart from the audio stuffing bits, there is no difference in the ISO/IEC 11172-3 [2] Layer II bit stream syntax for 48 kHz sampling f... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1 ISO/IEC 11172-3 and ISO/IEC 13818-3 Layer II bit stream syntax | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1.0 General | This syntax is valid at the output of an MPEG Audio (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) Layer II audio encoder and at the input of an MPEG Audio (ISO/IEC 11172-3 [2] and ISO/IEC 13818-3 [4]) Layer II decoder. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1.1 Audio sequence | Syntax No. of bits Mnemonic audio sequence() { while (nextbits()==syncword) { frame() } } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1.2 Audio frame | Syntax No. of bits Mnemonic frame() { header() error_check() audio_data() ancillary_data() } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 7.3.1.3 Header | Syntax No. of bits Mnemonic header() { syncword 12 bslbf ID 1 bslbf layer 2 bslbf protection_bit 1 bslbf bitrate_index 4 bslbf sampling_frequency 2 bslbf padding_bit 1 bslbf private_bit 1 bslbf mode 2 bslbf mode_extension 2 bslbf copyright 1 bslbf original/copy 1 bslbf emphasis 2 bslbf } ETSI ETSI TS 103 466 V1.1.1 (20... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1.4 Error check | Syntax No. of bits Mnemonic error_check() { if (protection_bit==0) crc_check 16 rpchof } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1.5 Audio data | Syntax No. of bits Mnemonic audio_data() { for (sb=0; sb<bound; sb++) for (ch=0; ch<nch; ch++) allocation[ch][sb] 2...4 uimsbf for (sb=bound; sb<sblimit; sb++) { allocation[0][sb] 2...4 uimsbf allocation[1][sb]=allocation|0]|sb] } for (sb=0; sb<sblimit; sb++) for (ch=0; ch<nch; ch++) if (allocation[ch][sb]!=0) scfsi[ch... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.1.6 Ancillary data | Syntax No. of bits Mnemonic ancillary_data() { if ((layer == 1) || (layer == 2)) for (b=0; b<no_of_ancillary_bits; b++) ancillary_bit 1 bslbf } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2 DAB audio bit stream syntax | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.0 General | This syntax is valid at the output of the DAB audio encoder and at the input of the DAB audio decoder. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.1 DAB audio sequence | Syntax No. of bits Mnemonic dab_audio sequence() { while true { dab_audio_frame() } } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.2 DAB audio frame | Syntax No. of bits Mnemonic dab_audio_frame() { dab_audio_frame_header() error_check() audio_data() audio_stuffing_bits() x_prog_ass_data() scf_error_check() f_prog_ass_data() } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.3 DAB audio frame header | The DAB audio frame header is defined identically to the header defined in clause 5.4.1.3. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.4 Error check | See clause 5.4.1.4. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.5 Audio data | See clause 5.4.1.5. ETSI ETSI TS 103 466 V1.1.1 (2016-10) 35 |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.6 Audio stuffing bits | In the case of 48 kHz sampling frequency, i.e. ISO/IEC 11172-3 [2] Layer II, the following syntax is valid. Syntax No. of bits Mnemonic audio_stuffing_bits() { while (bitsum < (bit_rate * 0,024 - no_of_x-pad_bytes * 8 - 2* 8 - no_of_scf_error_checks * 8)) { stuff_bit 1 bslbf bitsum++ } } In the case of 24 kHz sampling ... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.7 Extended Programme Associated Data | Syntax No. of bits Mnemonic x_prog_ass_data() { for (i=0; i<no_of_x-pad_bytes; i++) x-pad_byte(i) 8 bslbf } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.8 Scale factor error check | Syntax No. of bits Mnemonic scf_error_check() { for (i=no_of_scf_error_checks-1; i≥0; i--) scf-crc_check(i) 8 rpchof } |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.4.2.9 Fixed Programme Associated Data | Syntax No. of bits Mnemonic f_prog_ass_data() { for (i=0; i<2; i++) f-pad_byte(i) 8 bslbf } ETSI ETSI TS 103 466 V1.1.1 (2016-10) 36 |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.5 Programme Associated Data (PAD) | |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.5.1 Coding | The coding of the F-PAD and X-PAD are described in [1] clause 7.4. |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.5.2 Transport | Each DAB audio frame contains a number of bytes which may carry Programme Associated Data (PAD). PAD is information which is synchronous to the audio and its contents may be intimately related to the audio. The PAD bytes in successive audio frames constitute the PAD channel. The functions provided by PAD are given in c... |
75b50e2cbde107ac7a189dd27bd62bc2 | 103 466 | 5.5.3 Dynamic Range Control data | The DRC data can be used in the receiver to set the gain of a variable gain amplifier. The DRC data shall be coded as follows: b7 - b2 DRC signal; 0 0 0 0 0 0: 0 dB; 0 0 0 0 0 1: +0,25 dB; 0 0 0 0 1 0: +0,50 dB; ↓ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ : continuous steps of +0,25 dB; ¯ ¯ ¯ ¯ ¯ ¯ 1 1 1 1 1 1: +15,75 dB. When DRC is used... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 1 Scope | The present document defines the use cases and requirements for the definition of the interfaces and protocols for interfacing with a secure element. This secure element is called Smart Secure Platform (SSP). |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 2 References | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 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... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 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... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 3 Definition of terms, symbols and abbreviations | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 102 216 [i.2] and the following apply: Certificate Issuer (CI): root CA which issues digital certificates to the certified entities in the SSP ecosystem custodian: organization that defines family identifier specific requirements (e.g. trusted CIs, pr... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 3.2 Symbols | Void. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 102 216 [i.2] and the following apply: CI Certificate Issuer eSSP embedded SSP HPSIM Hosting Party Subscription Identity Module iNVM internal Non-Volatile Memory iSSP integrated SSP LBA Local Bundle Assistant LPWA Low Power Wide Area M2M Machi... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 4 Abstract (informative) | The present document describes the use case and requirements for the definition of a new secure element and its interfaces, superseding the interfaces currently defined for a UICC. By defining these interfaces, a new type of secure element will be defined called a Smart Secure Platform (SSP). The present document aims ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 5 SSP concept description | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 5.1 Introduction | The SSP is a secure 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 intended app... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 5.2 Core features | A key element of the SSP is a logical interface allowing the support of different types of application protocols such as the ones used in the internet world (e.g. HTTP(S)), but also protocols used for secure elements such as banking cards or UICCs. This logical interface is able to transport these application protocols... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 5.3 Security | A set of security features such as secure channel protocols, access control and secure storage needs to be defined. SSP class definitions will reference the required security features. A certification scheme targeting the different classes of SSP may also be defined. These certification schemes will help the secure app... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 5.4 Electrical characteristics and physical interfaces | 5.4.1 Unlinking electrical characteristics of the SSP from its physical interfaces A secure element according to ETSI TS 102 221 [2] with an additional interface according to ETSI TS 102 613 [4] or ETSI TS 102 600 [i.4] lacks a clear separation of electrical characteristics which belong to the secure element (e.g. powe... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 5.4.2 Operational stages | During device operation an SSP will not be used continuously in the same manner. There will be stages when the SSP performs high performance tasks like bulk encryption or key generation followed by stages where the SSP remains responsive to incoming service requests. Depending on the device which embeds the SSP it may ... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6 Background (informative) | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.1 Overview of the use cases | A range of use cases is identified in this clause to derive requirements for the specification of the SSP. Use cases are provided as a means to understand and add context to the overall requirements. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2 Use Case 1 - Embedded secure element | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2.1 Overview | An embedded secure element is a dedicated hardware component that is not intended to be removed from or replaced in the terminal. One example for an embedded secure element is an embedded UICC (eUICC). Such an embedded secure element is normally soldered into the terminal and is therefore an integral part of the termin... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2.2 Sub use cases | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2.2.1 Use case 1.1 - Embedded secure element, electrical interface | Using an electrical interface already used in the terminal would avoid implementing a specific power supply for the embedded secure element and would make the power management in the terminal much easier and more efficient. ETSI ETSI TS 103 465 V16.6.0 (2022-01) 17 Release 16 |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2.2.2 Use case 1.2 - Embedded secure element, physical interface | Using an interface already available in the terminal would make the implementation inside the terminal more efficient as existing interfaces like e.g. I2C or SPI can be re-used and there is no need to develop a specific interface for communicating with an embedded secure element. The Serial Peripheral Interface (SPI) i... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2.2.4 Use case 1.4 - Embedded secure element, protocol interface | The existing UICC protocols couple the electrical interface and higher-layer functionality. In order to enable an appropriate decoupling of these components, the protocols would permit SSP power management while allowing different transports to be used, and the other use cases to be supported. The protocols would be de... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.2.3 Interaction with existing features | Although for the above use cases it may be beneficial to re-use existing electrical and protocol interfaces, while it may for other use cases be beneficial to have a standardized interface defined. One of such use case is a removable SSP. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3 Use case 2 - Securing IoT devices | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3.1 Overview | IoT devices are a special class of devices which are usually very constrained in terms of cost and power supply. But IoT devices are also the source of potential high risk for end user privacy and security. IoT devices are usually comprised of three main parts: • Sensors. • Processing and management. • Remote connectio... |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3.2 Sub use cases | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3.2.1 Use case 2.1 - Management of IoT devices | The SSP will have the role of processing all the information contained into an IoT device in addition to provide secure authentication to be used to connect to a wireless network and to be used to securely connect to a remote service backend. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3.2.2 Use case 2.2 - Constrained terminals for M2M | Several use cases in the M2M area are requiring very power efficient terminals and procedures. Such terminals may only be active very infrequently, e.g. once a week, and only transmit a small amount of data. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3.2.3 Use case 2.3 - General power efficiency | In the light of the general need to save energy wherever possible it is also necessary to optimize the power consumption of small devices like an SSP. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.3.3 Interaction with existing features | None. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4 Use case 3 - Storage of large data | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.1 Overview | Several use cases may require the SSP to store large amounts of data, possibly in one file and in an unstructured way. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.2 Sub use cases | |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.2.1 Use case 3.1 - Storage of large configuration data | In 3GPP, more and more configuration parameters need to be stored in the device. Also the complexity of these parameters is increasing. |
05e2f811f51a7b0fbe3a5345af7d66c0 | 103 465 | 6.4.2.2 Use case 3.2 - Storage of identification data | Applications making use of biometric security require to store biometric information (e.g. voice, facial, fingerprint) in a secure way. Such biometric data may require a big amount of data. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.