ETSI TS 131 213 V15.1.0 (2020-01)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Test specification for (U)SIM;
Application Programming Interface (API) for Java Card™
(3GPP TS 31.213 version 15.1.0 Release 15)


3GPP TS 31.213 version 15.1.0 Release 15 1 ETSI TS 131 213 V15.1.0 (2020-01)

Reference
RTS/TSGC-0631213vf10
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 2 ETSI TS 131 213 V15.1.0 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 3 ETSI TS 131 213 V15.1.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Test environment . 9
4.1 Applicability . 9
4.2 Test environment description . 9
4.3 Tests format . 10
4.3.1 Test area reference . 10
4.3.1.1 Conformance requirements . 10
4.3.1.2 Test area files . 11
4.3.1.3 Test procedure . 11
4.3.1.4 Test coverage . 11
4.4 Initial conditions . 11
4.5 Package name . 11
4.6 AID coding . 12
4.7 Test equipment . 13
4.7.1 Test tool . 13
4.7.2 Interfaces and classes use . 13
4.7.3 Util package . 13
4.7.4 Java Software Development kit version . 13
5 Test plan . 13
5.1 Package uicc.usim.access package . 13
5.1.1 Interface SIMConstants . 13
5.1.2 Interface USIMConstants . 13
5.2 Package uicc.usim.toolkit package . 14
5.2.1 Interface ToolkitConstants . 14
5.2.2 Interface USATEnvelopeHandler . 14
5.2.2.1 Method getSecuredDataLength . 14
5.2.2.2 Method getSecuredDataOffset . 18
5.2.2.3 Method getShortMessageLength . 22
5.2.2.4 Method getShortMessageOffset . 25
5.2.2.5 Method getTPUDLOffset . 29
5.2.2.6 Method getUserDataLength . 31
5.2.2.7 Method getItemIdentifier . 34
5.2.2.8 Method getChannelIdentifier . 35
5.2.2.9 Method getChannelStatus . 38
5.2.2.10 Method getSize . 40
5.2.2.11 Method getTag . 41
5.2.2.12 Method compareValue . 42
5.2.2.13 Method copy . 44
5.2.2.14 Method copyValue . 46
5.2.2.15 Method findAndCompareValue(byte tag, byte[] compareBuffer, short compareOffset) . 49
5.2.2.16 Method findAndCompareValue(byte tag, byte occurrence, short valueOffset, byte[]
compareBuffer, short compareOffset, short compareLength) . 51
5.2.2.17 Method findAndCopyValue(byte tag, byte[] dstBuffer, short dstOffset) . 54
5.2.2.18 Method findAndCopyValue(byte tag, byte occurrence, short valueOffset, byte[] dstBuffer, short
dstOffset, short dstLength) . 56
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 4 ETSI TS 131 213 V15.1.0 (2020-01)
5.2.2.19 Method findTLV . 59
5.2.2.20 Method getCapacity . 61
5.2.2.21 Method getLength . 62
5.2.2.22 Method getValueByte . 63
5.2.2.23 Method getValueLength . 64
5.2.2.24 Method getValueShort . 65
5.2.3 Interface USATTerminalProfile . 66
5.2.4 Class USATEnvelopeHandlerSystem . 66
5.2.4.1 Method getTheHandler . 66
5.2.5 Interface ToolkitRegistry . 67
5.2.5.1 Method clearEvent . 67
5.2.5.2 Method isEventSet . 69
5.2.5.3 Method setEvent . 70
5.2.5.4 Method setEventList . 73
5.3 (U)SAT Framework . 77
5.3.1 Minimum handler availability. 77
5.3.1.1 ProactiveHandler . 77
5.3.1.2 ProactiveResponseHandler . 82
5.3.1.3 EnvelopeHandler . 92
5.3.1.4 EnvelopeResponseHandler . 95
5.3.1.5 USATEnvelopeHandler . 102
5.3.1.6 Applet triggering with ongoing proactive session . 104
5.3.2 Handler integrity . 110
5.3.2.1 ProactiveResponseHandler . 110
5.3.2.2 EnvelopeHandler . 111
5.3.2.3 USATEnvelopeHandler . 122
5.3.3 Exception handling . 136
5.3.3.1 General Behaviour . 136
5.3.3.2 Interaction with Multiple Triggering . 138
5.3.4 Applet triggering . 139
5.3.4.1 EVENT_FORMATTED_SMS_PP_ENV . 139
5.3.4.2 EVENT_UNFORMATTED_SMS_PP_ENV . 141
5.3.4.3 EVENT_FORMATTED_SMS_PP_UPD . 143
5.3.4.4 EVENT_UNFORMATTED_SMS_PP_UPD . 145
5.3.4.5 EVENT_FORMATTED_SMS_CB . 148
5.3.4.6 EVENT_UNFORMATTED_SMS_CB . 149
5.3.4.7 EVENT_FORMATTED_USSD . 150
5.3.4.8 EVENT_UNFORMATTED_USSD . 152
5.3.5 Envelope response posting . 153
5.3.5.1 EVENT_MO_SHORT_MESSAGE_CONTROL_BY_SIM . 153
5.3.6 Toolkit installation . 155
5.3.6.1 Minimum security level . 155
5.3.6.2 TAR. 157
5.3.6.3 Access domain . 161
5.3.7 Other parts transferred to (U)SAT framework from API . 162
5.3.7.1 A handler is a temporary JCRE Entry Point object . 162
5.3.8 Framework security management . 163
5.3.8.1 Input data . 164
5.3.8.2 Output data . 172
5.3.9 Concatenated SMS . 174
5.3.9.1 Concatenation processing . 174
5.3.9.2 Test area files . 174
5.3.9.3 Test coverage . 175
5.3.9.4 Test procedure . 175
5.3.10 Cell Broadcast Service . 176
5.3.10.1 Multiple message reassembling . 176
5.3.10.2 Test area files . 177
5.3.10.3 Test coverage . 177
5.3.11 Concatenated USSD . 178
5.3.11.1 Concatenation processing . 178
5.3.11.2 Test area files . 178
5.3.11.3 Test coverage . 178
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 5 ETSI TS 131 213 V15.1.0 (2020-01)
5.3.11.4 Test procedure . 178
Annex A (normative): Class, methods and USATFramework tests acronyms. 180
A.1 Toolkit part . 180
A.1.1 USATEnvelopeHandler interface . 180
A.1.2 USATEnvelopeHandlerSystem method . 180
A.1. 3 ToolkitRegistry methods . 181
A.2 Acronyms for USATFramework tests . 181
A.2.1 Minimum handler availability . 181
A.2.2 Handler integrity . 181
A.2.3 Applet triggering . 181
A.2.4 Exception handling . 181
A.2.5 Envelope response posting . 182
A.2.6 Toolkit installation . 182
A.2.7 Other parts transferred from API to CAT RE . 182
A.2.8 Framework security . 182
A.2.9 Concatenated SMS . 182
A.2.10 Cell Broadcast Service . 182
Annex B (normative): Global prepersonalization . 183
Annex C (normative): Test file description . 184
Annex D (normative): uicc.usim.test.util package, (U)SIM interfaces and testing script
example . 185
Annex E (normative): Test Area files . 186
Annex F (informative): Change history . 187
History . 188

ETSI
3GPP TS 31.213 version 15.1.0 Release 15 6 ETSI TS 131 213 V15.1.0 (2020-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 7 ETSI TS 131 213 V15.1.0 (2020-01)
1 Scope
The present document covers the minimum characteristics considered necessary in order to provide compliance to
TS 31.130 [2].
The present document describes the technical characteristics and methods of test for testing the (U)SIM API for Java
TM
Card (TS 31.130 [2]) implemented in the (U)SIM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test suite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] ETSI TS 101 220: "Integrated Circuit Cards (ICC); ETSI numbering system for
telecommunication; Application providers (AID)".
[2] 3GPP TS 31 130 Release 6: "(U)SIM API for Java Card™"
[3] Void.
[4] 3GPP TS 31.102: "Characteristics of the USIM Application".
[5] 3GPP TS 51.011 Release 4: "Specification of the Subscriber Identity Module- Mobile Equipment
(SIM – ME) interface".
[6] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[7] Void.
[8] 3GPP TS 31.111: "USIM Application Toolkit (USAT)".
[9] Void.
[10] 3GPP TS 31.115: "Secured packet structure for the (U)SIM Toolkit applications".
[11] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 8 ETSI TS 131 213 V15.1.0 (2020-01)
[12] Sun Microsystems Java Card™ Specification: "Java Card™ 2.2.1 Application Programming
Interface".
[13] Sun Microsystems Java Card™ Specification: "Java Card™ 2.2.1 Runtime Environment (JCRE)
Specification".
[14] Sun Microsystems Java Card™ Specification: "Java Card™ 2.2.1 Virtual Machine Specification".
SUN Java Card™ Specifications can be downloaded at http://java.sun.com/products/javacard
[15] ETSI TS 102 268 V6.1.0: "Test specification for UICC Application Programming Interface for
Java Card (TM) ".
[16] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [16] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [16].
applet installation parameters: values for applet installation parameters
Conformance Requirement Reference (CRR): description of the expected card behaviour according to TS 31.130 [2]
expected state: state in which the (U)SIM is supposed to be after the execution of the test procedure applied on the
relevant initial conditions
security parameters: minimum security requirements defined for the applet installation process
test area: set of Test Cases applicable to a specific part (class method, CAT RE behaviour, etc) of the TS 31.130 [2].
test case: elementary test that checks for compliance with one or more Conformance Requirement References
test procedure: sequence of actions/commands to perform all the test cases defined in a test area
test source file: java file containing methods that will load and install test applet in the card, execute and verify the test
results, and restore the Default Initial Conditions on the (U)SIM (when possible).
test toolkit applet: applet designed to test a specific functionality of the USIM API (TS 31.130 [2])
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [16] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [16].
AID Application IDentifier
APDU Application Protocol Data Unit
API Application Programming Interface
CAT RE Card Application Toolkit Runtime Environment
CRR Conformance requirements Reference
CRRC Conformance requirement Reference Context Error
CRRN Conformance requirement Reference Normal
CRRP Conformance requirement Reference Parameter Error
FFS For Further Study
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 9 ETSI TS 131 213 V15.1.0 (2020-01)
4 Test environment
This clause specifies requirements that shall be met and the testing rules that shall be followed during the test
procedure.
4.1 Applicability
The tests defined in the present document shall be performed taking into account the services supported by the card as
specified in the EF file.
SST
The test defined in the present document are applicable to cards implementing TS 31.130 [2] unless otherwise stated.
The tests defined in the present document require that the card support the concatenation process with 2 concatenated
SMS.
4.2 Test environment description
The general architecture for the test environment is:
Scope of the Test Suite.
Elements of the Test Suite
Conversion
ETSI TS 102 241 102 221 and
UICC File Other Toolkit Applet
parameters
and Java Card™
31 130 based
System Applications (e.g. Toolkit
Applications
Server not based on Service, Remote
(e.g. SIM Applet
102 221 and
Management
or USIM Applet)
Test
31 130
Applications,
TERMINAL
Toolkit
ADF File system Browser
Applet
Server Applications)
Converter
Applet
TM uicc.usim. uicc.usim.
Java Card uicc.toolkit uicc.system
.cap uicc.access
access toolkit
package packages package package
package
package
Applet
TM
Java Card Runtime Environment
installation
Loader
(U)SATFramework USAT EvelopeHandler
parameter
CAT Runtime Environment
Test
Triggering
Toolkit
Source
Toolkit
Entity
Handlers Registry
APDU
APDU
I/O
Output
test
result
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 10 ETSI TS 131 213 V15.1.0 (2020-01)
4.3 Tests format
4.3.1 Test area reference
Each test area is referenced as follows:
For API testing:
API Testing: 'API_[package name]_[classname]_[methodname]' where
package name:
uicc.usim.access package: '1'
uicc.usim.toolkit package: '2'
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.
For Framework testing:
FWK: framework testing
Chapter name:
xxx: 3 letters for each chapter
See annex F for full chapter acronyms list
Subchapter name
yyyy: : 4 letters for each subchapter
See annex F for full subchapter acronyms list
4.3.1.1 Conformance requirements
The conformance requirements are expressed in the following way:
- Method prototype as listed in TS 31.130 [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 incorrect parameter limit values, each referenced as a Conformance
Requirement Reference Parameter Error (CRRP).
- Context error:
- Contains errors due to the context the method is used in, each referenced as a Conformance Requirement
Reference Context Error (CRRC).
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 11 ETSI TS 131 213 V15.1.0 (2020-01)
4.3.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 common interfaces defined in Annex D.
The Cap File format is described in Java Card™ Virtual Machine Specification [4].
Test files can be run in any order.
All files from the same test area are located in the same subfolder.
4.3.1.3 Test procedure
Each test procedure contains a table to indicate the expected responses form the API and/or the APDU level as follows:

Test Case
Id Description API/(U)SAT Framework APDU Expectation
Expectation
Test Case detailed description API and/or (U)SAT Framework Expected response at APDU
expected behaviour. level.
4.3.1.4 Test coverage
The table above each test procedure indicates the correspondence between the Conformance Requirements Reference
(CRR) and the different test cases.
4.4 Initial conditions
The Initial Conditions are a set of general prerequisites for the (U)SIM prior to the execution of testing. For each test
procedure described in the present document, the following rules apply to the Initial Conditions:
- unless otherwise stated, the file system and the files' content shall fulfil the requirements described in annex B;
- unless otherwise stated, before installing the applet(s) relevant to the current test procedure, all packages specific
to other test procedures shall not be present.
When both statements apply, a test procedure is said to be in the "Default Initial Conditions" state.
4.5 Package name
Java packages integrating this Test Suite shall follow this naming convention:
uicc.usim.test.access.[Test Area Reference]: Java Card packages containing Test Area References for the
TS 31.130 [2] uicc.access package.
uicc.usim.test.toolkit.[Test Area Reference]: Java Card packages containing Test Area References for the
TS 31.130 [2] uicc.toolkit package.
uicc.usim.test.usatframework.[Test Area Reference]: Java Card packages containing Test Area References for the
TS 31.130 [2] USAT Framework.
uicc.usim.test.util: for the Test util package defined in this Test Suite.
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 12 ETSI TS 131 213 V15.1.0 (2020-01)
where the Test Area Reference is written in lower case.
EXAMPLE: The package ./uicc.usim.test.access.[Test Area Reference] creates the following directory
structure ./uiccusim//test/access/[Test Area Reference]/Api_1_._[1.n].*, where
'Api_1_._[1.n].*' are the different test applets Java source files used in [Test Area Reference].
4.6 AID coding
The AID coding for the Test Packages, Applet classes and Applets shall be as specified in ETSI TS 101 220 [5]. In
addition, the following TAR and Application Provider specific data values are defined for use within the present
document:
AID coding
Byte 1 Byte 12 Byte 13 Byte 14 Byte 15 Byte 16

Application Provider specific data

TAR
Specified in ETSI TS 101 220 [5]

TAR coding (3 bytes/ 24 bits):

b1 b4 b5 b8 b9 b12 b13 b16 b17 b24

Applet instance number
Applet class number
Package number
RFU
Test Part Identifier
Applet instance number, Applet Class number, Package number:
For package AID, package number shall start from 0 and class and instance numbers shall be 0.
For class AID, package number is the number of the class package, class number shall start from 1 and instance
shall be 0.
For instance AID, package and class number are the number of class and package of which instance belongs, and
instance number shall start from 1.
Test part Identifier (bits b1-b4):
- 0000 reserved (as TAR= '00.00.00' is reserved for Issuer Security Domain)
- 0010 API uicc.usim.toolkit
- 0101 USAT Framework
- 1110 USIM ADF
- 1111 uicc.util
- other values are RFU
Application Provider specific data (1 byte):
- '00' for Package
- '01' for Applet class
- '02' for Applet Instance
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 13 ETSI TS 131 213 V15.1.0 (2020-01)
EXAMPLE: The AID of Package uicc.usim.util is 'A0 00 00 00  87 10 05 FF  FF FF FF 89  F0 00 00 00'.
4.7 Test equipment
These clauses recommend a minimum specification for each of the items of test equipment referenced in the tests.
4.7.1 Test tool
This test tool shall meet the following requirements:
- be able to send and receive APDU command to the USIM;
- the result of I/O commands must be presented at the application layer;
- be able to provide results of the tests;
- shall send and/or compare all data specified in test file.
4.7.2 Interfaces and classes use
The USIM test tool extends the UICC test tool defined in ETSI TS 102 268 [15]. Then The USIM test tool cannot be
run without having implemented the UICC test tool.
The USIM test tool shall use some interfaces and classes, defined in Annex D. They define the only allowed methods to
write the test sources.
Interfaces and classes are defined as follow:
- USimToolkitService defines methods to manage toolkit commands,
- USimAPITestService defines methods to send envelopes defined in TS 31.111 [8],
- USimAPITestCardService defines the static method to get a reference of the class implementing all interfaces.
4.7.3 Util package
Annex D includes java source code of TestToolkitApplet abstract class of the uicc.usim.util package. Each test applet
shall extend this abstract class in order to retrieve test results when selecting it.
4.7.4 Java Software Development kit version
Java software development kit (SDK) version supported by Java Card 2.2.1 specifications ([12], [13], [14]) is 1.4.1.
5 Test plan
The test plan is divided according to the (U)SIM API specification, that way the tests will follow the class hierarchy for
the uicc.usim.toolkit and uicc.usim.access package; for the SIM Toolkit framework this test plan describes the different
points that will be tested with the present test specification.
5.1 Package uicc.usim.access package
5.1.1 Interface SIMConstants
The constants in Java are resolved at compilation time, therefore a runtime test is not useful. No test of constants will be
performed.
5.1.2 Interface USIMConstants
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 14 ETSI TS 131 213 V15.1.0 (2020-01)
The constants in Java are resolved at compilation time, therefore a runtime test is not useful. No test of constants will be
performed.
5.2 Package uicc.usim.toolkit package
5.2.1 Interface ToolkitConstants
The constants in Java are resolved at compilation time, therefore a runtime test is not useful. No test of constants will be
performed.
5.2.2 Interface USATEnvelopeHandler
5.2.2.1 Method getSecuredDataLength
Test Area Reference: Api_2_Ueh_Gsdl
5.2.2.1.1 Conformance requirement
The method with following header shall be compliant to its definition in the API.
public short getSecuredDataLength()
throws uicc.toolkit.ToolkitException

5.2.2.1.1.1 Normal execution
- CRRN1: The method shall return the length of the Secured Data from the Command Packet in the SMS TPDU
(simple or concatenated) or Cell Broadcast Page Comprehension TLV contained in the Envelope handler.
- CRRN2: The length is from the first SMS TPDU TLV, USSD String TLV or Cell Broadcast Page
Comprehension TLV.
- CRRN3: The length should not include padding bytes.
- CRRN4: The method can be used if the event is EVENT_FORMATTED_SMS_PP_ENV and if the SMS TP UD
is formatted according to TS 31.115 [10] Single or Concatenated Short Message.
- CRRN5: The method can be used if the event is EVENT_FORMATTED_SMS_PP_UPD and if the SMS TP UD
is formatted according to TS 31.115 [10] Single or Concatenated Short Message.
- CRRN6: The method can be used if the event is EVENT_FORMATTED_SMS_CB and if the Cell Broadcast
Page is formatted according to TS 31.115 [10].
- CRRN7: The method can be used if the event is EVENT_FORMATTED_USSD and if the USSD String id is
formatted according to TS31.115 [10]
- CRRN8: If the method is successful and if the event is EVENT_FORMATTED_SMS_PP_ENV, the selected
TLV should be the SMS TPDU TLV.
- CRRN9: If the method is successful and if the event is EVENT_FORMATTED_SMS_PP_UPD, the selected
TLV should be the SMS TPDU TLV.
- CRRN10: If the method is successful and if the event is EVENT_FORMATTED_SMS_CB, the selected TLV
should be the Cell Broadcast Page TLV.
- CRRN11: If the method is successful and if the event is EVENT_FORMATTED_USSD, the selected TLV
should be the USSD String TLV.
5.2.2.1.1.2 Parameter errors
No requirements.
ETSI
3GPP TS 31.213 version 15.1.0 Release 15 15 ETSI TS 131 213 V15.1.0 (2020-01)
5.2.2.1.1.3 Context errors
- CRRC1: The method shall throw ToolkitException.UNAVAILABLE_ELEMENT in case of unavailable SMS
TPDU TLV, USSD Strin
...