hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.1 Introduction | The Cable Network provides data services using the (Euro) DOCSIS™ [5] architecture. The diagram given by figure 2 illustrates the reference model as specified for a Cable Network. Figure 2: Cable Network Reference model for Lawful Interception In this model, a Mediation System interacts with LEA and with the cable serv... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.2 INI1 | The protocol used for INI1a is not specified and dependant on the MD equipment. The INI1a between the LI Adminstration and LI MD is assumed to be integrated within the Mediation Device. ETSI ETSI TS 102 836-2 V1.1.1 (2009-11) 11 The administrative information relating to the target to be intercepted is exchanged betwee... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.2.1 Dynamically assigned IP-addresses | The auhorized cable operator personel must ensure that information related to MAC-addresses behind the cable modem that do not have to be tapped (i.e. MAC-addresses of eMTAs, etc.) is available to the MD. Dynamic IP-addresses assigned to these MAC-addresses must be excluded from the TAP. In the case that the target is ... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.2.2 DHCPv4 requirements on CMTS | To identify in the DHCPv4 messages that are intercepted by the relay agent from the CMTS from behind which cable modem the DHCP message originates DHCP option 82 sub-option remote-id needs to be used. This field is added to intercepted DHCP messages by the CMTS and contains the MAC-address of the cable modem from behin... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.2.3 DHCPv6 requirements on CMTS | To identify in the DHCPv6 messages that are intercepted by the relay agent from the CMTS from behind which cable modem the DHCP message originates the CM MAC ADDRESS option defined in [CANN-DHCP-Req] needs to be used. This field is added to intercepted DHCP messages by the CMTS and contains the MAC-address of the cable... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.2.4 Non-dynamically assigned IP-addresses | For cable operators that use IP-addresses that are not dynamically assigned by a DHCP-server from the operator (this can be a single IP-address or an IP-subnet behind a cable modem), the MD needs to get to know the IP-addresses that need to be tapped through other means. (out-of-scope). Those IP-addresses are provision... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.3 INI2b | The Provisioing Function sends all events related to an IP data session that is under intercept to the MD. Internal interface INI2b carries Intercept Related Information (IRI) from the Provisioning Function relating to the communication session that is under intercept to the MD. If dynamically assigned IP-addresses are... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.4 INI3 - Call Content (CC) of Communication Interface | Internal interface INI3 carries Call Content (CC) of Communication information related to the intercept from the CMTS to the mediation function, consistent with PacketCable™ PC ESP [7], section 5. This clause describes the mechanism for delivery of call content, via (CC) Connections from the cable operators network LI ... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.4.1 Call Content Connection Identifier | The CCC-Identifier is a 32-bit quantity, and is used to identify the intercept order to the Law Enforcement Agency. A data session typically consists of two separate packet streams, each corresponding to a direction of the communication. Both are delivered to the demarcation point with the same CCC-Identifier. The part... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.4.2 Original IP Header | This is the IP header [10] as sent by the endpoint. Contained in this IP header is the IP Source Address (SA) and IP Destination Address (DA), that identify the internet addresses of the source and destination of the packet. |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.4.3 Original other header | The packets can be of any IP-protocol (TCP, UDP, etc.) The original headers are maintained in the CCC sent to the MD. ETSI ETSI TS 102 836-2 V1.1.1 (2009-11) 14 |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6.4.5 Original Payload | The payload field is the bit-sequence as sent by the endpoint identified in the Source Address and Source Port. 6.5 SBCF (SNMP based Configuration Function) Based on SNMPv3, with the use of the IP intercept and IP TAP MIB. An intercept and tap mib specifies mibs for tapping content at IP Layer and configuraing the deli... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7 LI Cable Broadband IP Network Architecture | The cable broadband IP network architecture given by PacketCable™ maps to the LI reference model as given in figure 3. Figure 3: Cable Network Architecture for LI The Provisioning Function provides the IRI. In an actual implementation of there may be more than one element of Provisioning Functions and MDs within a Cabl... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7.1 Dimensioning and Capacity | The LI solution shall be scaled to accommodate the level of interception service that's proportionate with the subscriber base with minimum requirements defined by national legislation, e.g number of LEA's supported by the network provider with delivery to a number of LEMF's and a number of simultaneous interception or... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7.2 Elements of Cable Broadband IP Network | LI Monitoring / LEMD Function: The LI Monitoring / Law Enforcement Monitoring function is the system used by the LEA for the receiving of the HI-2 and/or HI-3 information streams. This system requirements are out of sciope of the current document and assumed to be already available. LI Administration: The LI administra... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7.3 Functional Description | The reference model RFC 3924 [13] is assumed as given in clause 5 with the elements of an LI Mediation Device (MD) and an LI Administrative Function located at the Cable Operators premises. The DHCP server or DHCP wiretap must support the LI INI1b and INI2 as described by the current document. The DHCP server or DHCP s... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7.3.1 LI Process: Interception of provisioning messaging | The functional model for interception of provisioning messaging is given by figure 4. LEA IP network HFC LI Monitor Target DHCP CMTS Prov Function HI2 HI1 INI1c INI2b INI1a MD LI Admin Figure 4: Interception of Provisioning messaging All signalling will be intercepted at the DHCP server or DHCP server wiretap, concentr... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7.3.2 LI Process: interception of IP data | The functional model for interception of IP data is given by figure 6. LEA IP network HFC LI Monitor Target User data CMTS HI3 HI1 INI1a MD LI Admin INI3 Duplicated IP stream SBCF Figure 6: Interception of IP data Interception shall be at the the IAP of the CMTS as given by figure 6. Call content traffic to and from th... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 7 Security | The SNMP3 (VACM and USM MIBs) configuration must be such that only authorised personal can modify and view the MIBs used for LI. Security requirements for LI are given by TR 102 661 [i.1]. ETSI ETSI TS 102 836-2 V1.1.1 (2009-11) 20 Annex A (informative): Requirements listed in Council Resolution of 17 January 1995 The ... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 1 Scope | The present document specifies the internal network interfaces to enable the Lawful Interception (LI) of IP telephony services over cable operators broadband IP Networks. The current document describes the LI functional elements and interfaces for both the NCS based and SIP protocol signalling architectures within a Pa... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 1.1 Requirements notation | If the present document is implemented, the key words "MUST" and "SHALL" as well as "REQUIRED" are to be interpreted as indicating a mandatory aspect of the present document. The keywords indicating a certain level of significance of a particular requirement that are used throughout the present document are summarized ... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Council Resolution of 17 January 1995 on the lawful i... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] PacketCable 1.5 Security Specification, PKT-SP-S... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 3 Definitions and abbreviations | |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: cable modem: layer two termination device that terminates the customer end of the J.112 connection hair-pin call: call that is targeted to a customer on the cable network that has forwarding enabled to a line which is on a different ne... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Access Provider CC Call Content CCC Communication Call Content CMTS Cable Modem Termination System CRD Call Related Details DA Destination Address EM Event Message GW Gateway HFC Hybrid Fiber Coax HI Handover Interface IAP Intercept Access ... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 4 Requirements | European cable operators are required to have the capability of intercepting messages passed over their networks system in any form. This capability should be covert, not affect the operation of the system in any discernible way or be detectable by the end user. Therefore, a European implementation for a Cable Broadban... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 5 Overview | The overall interception framework is extended from the model described in clause 5.2 of ES 201 158 as given by [16] and from the architecture identified in clause 5 of TS 101 671 as given by [3]. NW O/AP /SvP’s adm inistration function IRI m ediation function CC m ediation function Network Internal Functions IIF INI i... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 6 Internal Cable Network Interfaces | |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 6.1 Introduction | The Cable Network IP Telephony services is based on the PacketCable™ reference architecture and deploys signalling based on the NCS architecture described by TS 101 909-4 [5] and SIP architecture as given by RFC 3261 [6]. Figure 2 illustrates the reference model as specified for a Cable Network. Figure 2: Cable Network... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 6.2 INI1 | The protocol used for INI1a is not specified and dependant on the MD equipment. The INI1a between the LI Administration and LI MD is assumed to be integrated within the Mediation Device. ETSI ETSI TS 102 836-1 V1.1.1 (2009-11) 12 The administrative information relating to the target to be intercepted is exchanged betwe... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 6.3 INI2a | The SD sends all events related to a communication session that is under intercept to the MD. Internal interface INI2a carries Intercept Related Information (IRI) from the SD relating to the communication session that is under intercept to the MD. Based on the IRI the MD will invoke the SBCF to trigger delivery of the ... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 6.4 INI3 - Call Content (CC) of Communication Interface | Timestamp is an option for the CMTS, the MD must be able to be configured for both with and without timestamp. Clarify behaviour of MD in case of the two options. Internal interface INI3 carries Call Content (CC) of Communication information related to the intercept from the CMTS or MG to the mediation function, consis... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 6.4.1 Call Content Connection Identifier | The CCC-Identifier is a 32-bit quantity, and is used to identify the intercept order to the Law Enforcement Agency. A conversation in the PacketCable network typically consists of two separate packet streams, each corresponding to a direction of the communication. Both are delivered to the demarcation point with the sa... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 7 LI Cable Broadband IP Network Architecture | The cable broadband IP network architecture given by PacketCable™ maps to the LI reference model as given by figure 3. Figure 3: Cable Network Architecture for LI The SD provides the IRI . In an actual implementation of there may be more than one elements of SD and MDs within a Cable Network Architecture. The SD provid... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 7.1 Dimensioning and Capacity | The LI solution shall be scaled to accommodate the level of interception service that's proportionate with the subscriber base with minimum requirements defined by national legislation, e.g. number of LEA's supported by the network provider with delivery to a number of LEMF's and a number of simultaneous interception o... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 7.2 Elements of Cable Broadband IP Network | LI Monitoring / LEMD Function: The LI Monitoring / Law Enforcement Monitoring function is the system used by the LEA for the receiving of the HI-2 and/or HI-3 information streams. This system requirements are out of scope of the current document and assumed to be already available. LI Administration: The LI administrat... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 7.3 Functional Description | The reference model RFC 3924 [18] is assumed as given in clause 5 with the elements of an LI Mediation Device (MD) and an LI Administrative Function located at the Cable Operators premises. The SD must support the LI INI1b and INI2a as described by the present document. The SD receives over INI1b information relating t... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 7.3.3 LI Process: interception of off-net calls | The functional model for interception of IP Telephony off-net calls is given by figure 8. LEA IP network PSTN LI Monitor MG HI3 HI1 INI1a MD LI Admin INI2a INI1b SD HFC CMTS RTP SBCF SBCF INI3 INI3 Target Figure 8: Interception of off-net voice calls Interception shall be at the IAP of the CMTS or MG, in the same way a... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 7.3.4 Details: interception of hairpin calls | The functional model for interception of IP Telephony hairpin calls is given in figure 10. LEA IP network PSTN LI Monitor Forwarded number MG HI3 HI1 INI1a MD LI Admin INI2a INI1b SD SBCF INI3 MGCP HFC CMTS Target (with forwarding) Figure 10: Interception of hairpin voice calls Interception shall be at the IAP of the M... |
6f9663186dfddd397d2d7f053819b62d | 102 836-1 | 8 Security | The SNMP3 (VACM and USM MIBs) configuration must be such that only authorised personal can modify and view the MIBs used for LI. Security requirements for LI are given by TR 102 661 [i.4]. ETSI ETSI TS 102 836-1 V1.1.1 (2009-11) 25 Annex A (informative): Requirements listed in Council Resolution of 17 January 1995 The ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 1 Scope | The present document covers the minimum characteristics considered necessary in order to provide compliance to TS 102 588 [2]. It describes the technical characteristics and methods for testing the SCWS API for Java CardTM (TS 102 588 [2]) implemented in a UICC platform. It specifies the following parts: • test applica... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 2 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 reference document (including any amendments) applies. • In the case of a reference ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [2] ETSI TS 102 588: "Smart Cards; Application... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 102 600: "Smart Cards; UICC-Terminal interface; Characteristics of the USB interface". [i.2] HttpClient project. NOTE: Available at http://hc.... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 3 Definitions and abbreviations | |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: applet installation parameters: values for applet installation parameters Conformance Requirement Reference (CRR): description of the expected SCWS behaviour according to TS 102 588 [2] expected state: state in which the UICC is suppos... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AID Application IDentifier API Application Programming Interface BIP Bearer Independent Protocol according to TS 102 223 [11] CAT Card Application Toolkit CRR Conformance Requirements Reference CRRC Conformance Requirement Reference Context Er... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4 Applicability | |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.1 Applicability of the present document | This present test specification applies to UICCs containing a SCWS invocation API according to TS 102 588 [2]. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.2 Applicability of the individual test cases | Table A.1 lists the optional features for which the supplier of the implementation states the support. |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.3 Applicability to different Releases | The applicability to different releases specified in table B.1 of the present document shall apply, unless otherwise specified. ETSI ETSI TS 102 835 V8.1.0 (2012-03) 12 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.4 Definitions | |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.4.1 Format of table of the table of optional features | The columns in table A.1 have the following meaning. Column Meaning Option: The optional feature supported or not by the implementation. Status: See clause 4.4.3 'Status and Notations' Support: The support columns shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/I... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.4.2 Format of the applicability table | The applicability of every test in table B.1 is formally expressed by the use of Boolean expression defined in the following clause. The columns in table B.1 have the following meaning. Column Meaning Test case: The "Test case" column gives a reference to the test case number(s) detailed in the present document and req... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.5 Table of optional features | Table A.1: Options Item Option Status Support Mnemonic 1 ScwsExtension.doGet() M doGet 2 ScwsExtension.doPost() M doPost 3 ScwsExtension.doHead() M doHead 4 ScwsExtension.doPut() M doPut 5 ScwsExtension.doDelete() M doDelete 6 ScwsExtension.doOptions() O doOptions 7 ScwsExtension.doTrace() O doTrace ETSI ETSI TS 102 83... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 4.6 Applicability table | Table B.1: Applicability of tests Test case Description Release Rel-7 Rel-8 Class ScwsExtensionRegistry |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.1.1 Method register | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.1.2 Method deregister | Rel-7 M M Class ScwsExtensionService |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.1 Method doDelete | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.2 Method doGet | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.3 Method doHead | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.4 Method doOptions | Rel-7 C001 C001 |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.5 Method doPost | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.6 Method doPut | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.3.7 Method doTrace | Rel-7 C002 C002 Interface HttpRequest |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.1 Method findAndCopyKeywordValue | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.2 Method findAndCopyKeywordValue | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.3 Method getContentLength | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.4 Method getContentType | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.5 Method getRequestHttpVersion | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.6 Method readContent | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.4.7 Method readContentType | Rel-7 M M Interface HttpResponse |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.1 Method appendContent | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.2 Method appendHeaderVariable(byte[] data, short offset, short length) | Rel-7 M M 6.1.5.3 Method appendHeaderVariable (byte[] name, short nameOffset, short nameLength, byte[] value, short valueOffset, short valueLength) Rel-7 M M 6.1.5.4 Method appendHeaderVariable (short headerKeywordNameId, byte[] value, short valueOffset, short valueLength) Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.5 Method enableChunkMode | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.6 Method finalizeHeader | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.7 Method flush | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.8 Method getRemainingResponseBufferSize | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.9 Method reset | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.10 Method sendError | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.11 Method setContentType | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.1.5.12 Method writeStatusCode | Rel-7 M M SCWS Runtime Environment: Applet state |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.1 Invokation of applets not in state selectable | Rel-7 M M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.1.2 Registration remains valid if applet is not in selectable state | Rel-7 M M SCWS Runtime Environment: Exception handling |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.3.1 No exception shall be propagated as HTTP error to the terminal | Rel-7 M M SCWS Runtime Environment: Response Header Management |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.4.1 Send status code indicating success | Rel-7 M M SCWS Runtime Environment: Availability of ProactiveHandler / ProactiveResponseHandler |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.1 Incoming Http request | Rel-8 N/A M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.2 Available for complete Http response | Rel-8 N/A M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.3 Availability of ProactiveResponseHandler | Rel-8 N/A M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.4 Triggering through the ToolkitInterface | Rel-8 N/A M |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 6.2.5.5 Presence of CAT_TP multiplexing application | Rel-8 N/A C003 C001: IF (doOptions supported) THEN M ELSE N/A. C002: IF (doTrace supported) THEN M ELSE N/A. C003: IF (CAT Multiplexing application present) THEN M ELSE N/A. ETSI ETSI TS 102 835 V8.1.0 (2012-03) 15 (Release 8) |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5 Test environment | This clause specifies requirements that shall be met and the testing rules that shall be followed during the test procedure. The test cases described in the present document shall be performed independently of the interface used between the UICC and the terminal. In particular, any test case shall have the same result ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5.1 Test environment description | The general architecture for the test environment is: Figure 5.1 TERMINAL Test Procedure exchange APDU cmd response Java CardTM Runtime Environment TS 102 241 [12] and Java Card™ Scope of the Test Suite. Elements of the Test Suite Converter Loader APDU I/O APDU Test SCWS applet APDU cmd TS 102 221 [13] based Applicatio... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5.2 Tests format | |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5.2.1 Test area reference | Each test area is referenced as follows: For API Testing: 'API_[package name]_[class name]_[method name]' where • package name: uicc.scws: '1'. • class name: yyy: 3 letters for each class. See annex A for full classes acronyms list. • method name: zzzz[input parameters]: See annex A for full methods name acronyms list.... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5.2.1.1 Conformance requirements | The conformance requirements are expressed in the following way: • Method prototype as listed in TS 102 588 [2]. • Normal execution: - Contains normal execution and correct parameters limit values, each referenced as a Conformance Requirement Reference Normal (CRRN). • Parameters error: - Contains parameter errors and ... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5.2.1.2 Test area files | The files included in the Test Area use the following naming convention: • Test Source: Test_[Test Area Reference].java • Test Applet: [Test Area Reference]_[Test applet number].java • Cap File: [Test Area Reference].cap The applet numbers start from '1'. The test source shall use the common interfaces defined in annex... |
30401c8bcab7a085b1db3be5a9b7a40b | 102 835 | 5.2.1.3 Test procedure | Each test procedure contains a table to indicate the expected responses form the API and/or the HTTP level as follows. Test Case Id Description API/SCWS Framework Expectation APDU/HTTP Expectation Test Case detailed description API and/or SCWS Framework expected behaviour. Expected response at HTTP level. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.