hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.1.6.2.3 Power source of type Independent | The power source of type independent defined in ETSI TS 103 666-3 [3], clause 6.2.2.3 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.1.6.3 Power consumption | The power consumption defined in ETSI TS 103 666-3 [3], clause 6.2.3 shall apply. ETSI ETSI TS 103 666-4 V17.0.0 (2022-04) 12 Release 17 |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.1.7 Cryptographic functions | The provisions of ETSI TS 103 666-2 [2], clause 7.1.7 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.1.8 Clock | The eSSP Type 2 shall support a clock as defined in ETSI TS 103 666-3 [3], clause 6.3. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.1.9 Secure CPU | The characteristics of the CPUs (e.g. endianness) are implementation dependent and outside the scope of the present document. The CPU(s) shall be based at least on a 32-bit architecture. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.1.10 Random Number Generator | The provisions of ETSI TS 103 666-2 [2], clause 7.1.11 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.2 Low-level Operating System | The provisions of ETSI TS 103 666-2 [2], clause 7.2 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.3 Services | The provisions of ETSI TS 103 666-2 [2], clause 7.3 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.4 Minimum level of interoperability | The provisions of ETSI TS 103 666-2 [2], clause 7.4 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.5 Primary Platform identification | The eSSP Type 2 shall be identified with an identifier based on the definition in ETSI TS 103 666-2 [2], clause 7.5 with the following exceptions: • SSP Type identifies the type of SSP and is coded as follows: Base-32 character Value Description F '00101' Embedded SSP Type 2 (eSSP Type 2) |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.6 Provisioning of Primary Platform software | The provisions of GlobalPlatform VPP - Concepts and Interfaces [6], clause 5.7 REQ85 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 6.7 Part Number Identifier | The provisions of ETSI TS 103 666-2 [2], clause 7.7 shall apply. ETSI ETSI TS 103 666-4 V17.0.0 (2022-04) 13 Release 17 |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 7 Primary Platform Interface | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 7.1 Kernel functions ABI/API | The provisions of ETSI TS 103 666-2 [2], clause 8.1 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 7.2 Communication service interface | The provisions of ETSI TS 103 666-2 [2], clause 8.2 shall apply with the exception listed below: • One of the end points of any dynamic pipe may be out the SSP host domain. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 7.3 Secondary Platform Bundle management service interface | The provisions of ETSI TS 103 666-2 [2], clause 8.3 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8 Secondary Platform Bundle | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.1 Introduction | The Secondary Platform Bundle refers to either the data container or the runtime instance of the container. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.2 States | The provisions of ETSI TS 103 666-2 [2], clause 9.2 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.3 Secondary Platform Bundle container format | The provisions of ETSI TS 103 666-2 [2], clause 9.3 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4 Secondary Platform | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.1 High-level OS | The provisions of ETSI TS 103 666-2 [2], clause 9.4.1 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.2 Execution framework | The provisions of ETSI TS 103 666-2 [2], clause 9.4.2 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.3 UICC platform as a Secondary Platform | The provisions of ETSI TS 103 666-2 [2], clause 9.4.3 shall apply. ETSI ETSI TS 103 666-4 V17.0.0 (2022-04) 14 Release 17 |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.4 Capability exchange | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.4.1 Overall description | The capability exchange procedure is used to inform the eSSP Type 2 of the capabilities of the terminal and for the terminal to retrieve the capabilities of the eSSP Type 2. The capability exchange for eSSP Type 2 supporting SCL as defined in ETSI TS 103 666-1 [1], clause 6.4.2 apply with modifications provided below. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.4.2 Capabilities of the terminal | The data field sent by the terminal to the eSSP Type 2 contains the data structure defined in ETSI TS 103 666-3 [3], clause 6.4.2.2. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.4.3 Capabilities of the eSSP Type 2 | The provisions of ETSI TS 103 666-3 [3], clause 6.4.2.3 shall apply with the following exception: • SSPClass field shall have the eSSPClass-Embedded-Type2 (2) value. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.4.5 Identifiers of Secondary Platform Bundle | The provisions of ETSI TS 103 666-2 [2], clause 9.4.5 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.5 SSP Application | The provisions of ETSI TS 103 666-2 [2], clause 9.5 and subclauses shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.6 Lifecycle management of Secondary Platform Bundles | The provisions of ETSI TS 103 666-2 [2], clause 9.6 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.7 Secondary Platform Bundle family identifier | The provisions of ETSI TS 103 666-2 [2], clause 9.7 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 8.8 eSSP Type 2 suspension | If the eSSP Type 2 indicates it supports the suspension mechanism as defined in clause 8.4.4.3, the provisions defined in ETSI TS 103 666-1 [1], clause 6.9 shall apply with the modifications listed below: • The suspension of the SSP should only be used if, in addition to the Secondary Platform Bundle Loader, only one S... |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9 Communication interface | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.1 eSSP Type 2 initialization | The eSSP Type 2 interface session defined in ETSI TS 103 666-1 [1], clause 6.4.1 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2 Low level protocol layers | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1 Physical layer | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1.1 Overview | The provisions of ETSI TS 103 666-3 [3], clause 7.1 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1.2 Reset | The eSSP Type 2 description in ETSI TS 103 666-3 [3], clause 7.2 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1.3 SPI interface | The eSSP Type 2 may support an SPI interface, in that case the clauses ETSI TS 103 666-3 [3], clause 7.4 and subclauses shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1.4 I2C interface | The eSSP Type 2 may support an I2C interface, in that case the clauses ETSI TS 103 666-3 [3], clause 7.5 and subclauses shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1.5 SWP interface | The eSSP Type 2 may support an SWP interface, in that case the clauses ETSI TS 103 666-3 [3], clause 7.6 and subclauses shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.1.6 USB interface | The eSSP Type 2 may support an USB interface, in that case the clauses ETSI TS 103 666-3 [3], clause 7.7 and subclauses shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.2.2 Link layer | The provisions of ETSI TS 103 666-1 [1], clause 8.3.1 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.3 SSP Common Layer | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.3.1 introduction | The eSSP Type 2 shall support the SCL protocol, therefore the provisions defined in ETSI TS 103 666-1 [1], clause 8 and subclauses shall apply, with the exception listed below: • The SCL network controller host and SCL router need not to share the same security perimeter of the eSSP Type 2, i.e. the SCL network control... |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.3.2 eSSP Type 2 with only one SCL interface | If the eSSP Type 2 has only one SCL interface, this interface should convey packets to multiple SCL hosts outside the SSP host domain, as illustrated in ETSI TS 103 666-3 [3], clause B.1. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.3.3 eSSP Type 2 with multiple SCL interfaces | If the eSSP Type 2 has multiples SCL interfaces, all these interfaces should belong to the same SCL network. Furthermore, the eSSP Type 2 should implement the SCL router and SCL network controller host, as illustrated in ETSI TS 103 666-3 [3], clause B.2. SCL hosts of an host domain should be accessible only through on... |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 9.4 Communication layers above SCL | The definition and usage of protocols layers above the SCL (e.g. ISO 7816 [9] APDUs) are defined in ETSI TS 103 666-1 [1], clause 10. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 10 Certification | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 10.1 Introduction | The eSSP Type 2 shall be able to support a certification by composition of a Secondary Platform Bundle from the Primary Platform certification. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 10.2 Primary Platform certification | |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 10.2.1 Overview | The provisions of GlobalPlatform VPP - Concepts and Interfaces [6], clause 4 shall apply. The certification of the Primary Platform shall include the Loader Package 2, as defined in BSI-CC-PP-0084-2014 [10]. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 10.2.2 Security Capabilities | The provisions of ETSI TS 103 666-2 [2], clause 11.2.2 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 10.3 Secondary Platform Bundle certification | The provisions of ETSI TS 103 666-2 [2], clause 11.3 shall apply. |
461da97da84f800f057e7f3a64bc260d | 103 666-4 | 11 eSPP Type 2 ecosystem and interfaces | The provisions of ETSI TS 103 666-2 [2], clause 12 and subclauses shall apply. ETSI ETSI TS 103 666-4 V17.0.0 (2022-04) 17 Release 17 Annex A (normative): Additions for Telecom Secondary Platform Bundles The provisions of ETSI TS 103 666-2 [2], Annex A shall apply. ETSI ETSI TS 103 666-4 V17.0.0 (2022-04) 18 Release 17... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for core elements for network independent access to emergency services (NG112) as defined in standards listed in clause 2.1 of the present document. |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 2 References | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 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... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 3 Definition of terms, symbols and abbreviations | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [i.1], ISO/IEC 9646-2 [i.2] and ETSI ETS 300 406 [i.3] apply. ETSI ETSI TS 103 650-2 V1.2.1 (2022-08) 6 |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 3.2 Symbols | Void. |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AML Advanced Mobile Location ASP Abstract Services Primitives ATM Abstract Test Method ATS Abstract Test Suite BCF Border Control Function ECRF Emergency Call Routing Function ESRP Emergency Service Routing Proxy IP Internet Protocol IUT Imple... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4 Abstract Test Method (ATM) | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4.1 Test Configuration | The test configurations as defined in ETSI TS 103 650-1 [1], clause 5, shall apply. |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4.2 Test architecture | The present document implements the general TTCN-3 test architecture as shown in figure 1. In single-component testcases, the MTC communicates with SUT over a port. In multi-component testcases, the MTC is used to synchronize the different PTCs. The PTCs communicate with the SUT over ports. The Upper tester entity in t... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4.3 Ports and ASPs (Abstract Services Primitives) | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4.3.1 Introduction | Two ports are used by the NG112 test suite: • The httpPort, of type HttpPort • The SIPP port of type SipPort |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4.3.2 Primitives on httpPort | One type of primitives is used in the httpPort: • HttpMessage type which can be either a Request message or a Response message |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 4.3.3 Primitives on SIP | Several types of primitives are used in the SIP: • Request type, which is a generic SIP request message type • REGISTER_Request type, which is a REGISTER SIP request message type • INVITE_Request type, which is an INVITE SIP request message type • OPTIONS_Request type, which is an OPTIONS SIP request message type • INF... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 5 Untestable Test Purposes | Not applicable. |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6 ATS conventions | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.2 Testing conventions | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.2.1 Testing states | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in the base standard, the function f_poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.3 Naming conventions | |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.3.1 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 1) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; • prefixes... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.3.2 NG112 specific TTCN-3 naming conventions | Next to such general naming conventions, table 2 shows specific naming conventions that apply to the NG112 TTCN-3 test suite. The <ng112_entityt> tag indicates the NG 112 entity: LIS, ESRP, ECRF, PSAP or BCF. Table 2: NG112 specific TTCN-3 naming conventions Language element Naming convention Identifier Module containi... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.3.3 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. ETSI ETSI TS 103 650-2 V1.2.1 (2022-08) 10 • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Th... |
ab56e77b0ac73f756eb286197358b4a4 | 103 650-2 | 6.3.4 Test Case (TC) identifier | The test case naming convention shall follow the same naming convention as defined in ETSI TS 103 650-1 [1], clause 7.1.2. EXAMPLE: TP identifier: TP_ESRP_FIND_SERVICE_BV_01 TC identifier: TC_ESRP_FIND_SERVICE_BV_01 ETSI ETSI TS 103 650-2 V1.2.1 (2022-08) 11 Annex A (normative): TTCN-3 modules A.1 Online TTCN-3 modules... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 1 Scope | The present document defines a PP for Consumer Mobile Device (CMD), which is typically a user-customizable device utilizing an operating system, supporting installation and maintenance of applications, with wireless internet connectivity, high computation power and rich user interface, such as smartphones or tablets, u... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 2 References | |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 3 Definition of terms, symbols and abbreviations | |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: ad network: technology platform used to match the sale of ads to be displayed to users between publishers and advertisers atomic update: update process in which the result will either be a completely successful update or the update process will be com... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 3.2 Symbols | Void. |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3G (mobile) Partnership Project ADP Application Distribution Platform AES Advanced Encryption Standard API Application Program Interface App Application CC Common Criteria CEM Common Evaluation Methodology CMD Consumer Mobile Device DEK D... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 4 TOE Definition | |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 4.1 TOE Overview | The TOE described by the present document is a subset of a CMD as shown in figure 1. The CMD includes hardware, an operating system and apps. Apps are categorized as preloaded and downloaded apps. Examples of a CMD include smart phone, tablet and other device with similar capabilities. Users can customize their CMDs (m... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 4.2 Usage and Major Security Features | The TOE is a subset of a CMD with wireless connectivity, high computation power and rich user interface. A user can customize the device by downloading apps and changing settings. A user can perform a wide range of actions with the TOE, such as make phone and video calls, perform various productivity tasks, play games,... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 4.4 Base-PP reference | Base-PP Title ETSI TS 103 732-1: "Consumer Mobile Device; Part 1: Base Protection Profile" Base-PP Version 2.1.2 Base-PP Date November 16, 2023 |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 4.5 Conformance Claim | The present document: • claims conformance to CC V3.1 Release 5 [1], [2], [3] and the CC and CEM addenda [18]; • is CC Part 2 [2] extended and CC Part 3 [3] extended; • does not claim conformance to any other PP; • conforms to the package EAL2 augmented with ALC_DVS_EXT.1 & ALC_FLR.3. ETSI ETSI TS 103 732-1 V2.1.2 (202... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 5 Security Problem Definition | |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 5.1 Assets and interfaces of the TOE | Assets to be protected: • User data assets stored in the TOE and in transit to the Trustworthy Remote Service, such as: - user files: photos, videos, etc.; - user location: location information, location record, etc.; - non-TOE account information; - user communication: communication records, address books, emails, SMS... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 5.2 Threat agents and threats | The following threat Agents are defined for the TOE (note that one entity may be multiple threat agents simultaneously): • TA.LOCAL: a threat agent in the general vicinity of a TOE when it is used, and therefore has access to the local wireless interface. • TA.REMOTE: a threat agent with access to the wide-area interfa... |
908b1db2923c9d5b9336bc07e544e666 | 103 732-1 | 5.3 Organizational Security Policies | P.DATA_CLASSIFICATION - The TOE manufacturer classifies groups of user data assets into at least three different classes, according to policies such as the potential harm that may result to the user if the user data asset were inappropriately accessed, used, or disclosed: • Low: user data assets to which unauthorized a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.