ARIB STD-T64-C.S0035-B v2.0
CDMA Card Application Toolkit
(CCAT)
Refer to "Industrial Property Rights (IPR)" in the preface of ARIB STD-T64 for Related Industrial
Property Rights. Refer to "Notice" in the preface of ARIB STD-T64 for Copyrights
1
Original Specification
2
This standard, ARIB STD-T64-C.S0035-B v2.0, was prepared by 3GPP2-WG of Association of
3
Radio Industries and Businesses (ARIB) based upon the 3GPP2 specification, C.S0035-B v2.0.
4
5
6
Modification to the original specification
None.
7
8
Notes
9
None.
10
3GPP2 C.S0035-B v2.0
May 2014
CDMA Card Application Toolkit (CCAT)
© 2014 3GPP2
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may
copyright and issue documents or standards publications in individual Organizational Partner's name based on this
document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at
[email protected]. Requests to reproduce individual Organizational Partner's documents should be directed to
that Organizational Partner. See www.3gpp2.org for more information.
3GPP2 C.S0035-B v2.0
REVISION HISTORY
Revision
Description of Changes
Date
C.S0035-0 v1.0
Initial Release
October 2002
C.S0035-A v1.0
First Revision
March 2005
C.S0035-A v2.0
Second Version of First Revision
August 2007
C.S0035-A v3.0
Third Version of First Revision
August 2012
C.S0035-B v1.0
Second Revision
December 2013
C.S0035-B v2.0
Second Version of Second Revision
May 2014
3GPP2 C.S0035-B v2.0
1
CONTENTS
2
1 GENERAL ...................................................................................................................... 1
3
1.1 Scope ....................................................................................................................... 1
4
1.2 Document Conventions ............................................................................................ 1
5
2 References ..................................................................................................................... 3
6
2.1 Normative References ............................................................................................... 3
7
2.2 Informative References ............................................................................................. 4
8
3 Terms ............................................................................................................................ 5
9
4 Overview of CCAT........................................................................................................... 7
10
4.1 Profile Download ...................................................................................................... 7
11
4.2 Proactive UICC ......................................................................................................... 7
12
4.3 Data download to UICC ............................................................................................ 7
13
4.4 Menu selection ......................................................................................................... 7
14
4.5 Call control by network access application ................................................................ 7
15
4.6 MO Short Message Control by UICC .......................................................................... 7
16
4.7 Event download ........................................................................................................ 7
17
4.8 Security ................................................................................................................... 7
18
4.9 Multiple card ............................................................................................................ 7
19
4.10 Timer Expiration .................................................................................................... 7
20
4.11 Bearer Independent Protocol ................................................................................... 8
21
4.12 Description of the access technology indicator mechanism ...................................... 8
22
4.13 Tag allocation guidelines......................................................................................... 8
23
5 Profile download............................................................................................................. 9
24
5.1 Procedure................................................................................................................. 9
25
5.2 Structure and coding of TERMINAL PROFILE ............................................................ 9
26
5.3 Definition of display parameters in Profile download ................................................ 10
27
6 Proactive UICC ............................................................................................................. 11
28
6.1 Introduction ........................................................................................................... 11
29
6.2 Identification of ME support ................................................................................... 11
30
6.3 General procedure .................................................................................................. 11
31
6.4 Proactive UICC commands and procedures ............................................................. 11
32
6.4.1 DISPLAY TEXT ................................................................................................. 11
i
3GPP2 C.S0035-B v2.0
1
6.4.2 GET INKEY ....................................................................................................... 11
2
6.4.3 GET INPUT ....................................................................................................... 11
3
6.4.4 MORE TIME ..................................................................................................... 11
4
6.4.5 PLAY TONE ...................................................................................................... 11
5
6.4.6 POLL INTERVAL ............................................................................................... 11
6
6.4.7 REFRESH ......................................................................................................... 11
7
6.4.8 SET UP MENU .................................................................................................. 11
8
6.4.9 SELECT ITEM .................................................................................................. 11
9
6.4.10 SEND SHORT MESSAGE ................................................................................ 12
10
6.4.11 Reserved ......................................................................................................... 13
11
6.4.12 SEND USSD ................................................................................................... 13
12
6.4.13 SET UP CALL .................................................................................................. 13
13
6.4.14 POLLING OFF ................................................................................................. 13
14
6.4.15 PROVIDE LOCAL INFORMATION .................................................................... 13
15
6.4.16 SET UP EVENT LIST ....................................................................................... 14
16
6.4.17 PERFORM CARD APDU .................................................................................. 14
17
6.4.18 POWER OFF CARD ......................................................................................... 14
18
6.4.19 POWER ON CARD........................................................................................... 14
19
6.4.20 GET READER STATUS .................................................................................... 14
20
6.4.21 TIMER MANAGEMENT .................................................................................... 14
21
6.4.22 SET UP IDLE MODE TEXT .............................................................................. 14
22
6.4.23 RUN AT COMMAND ........................................................................................ 14
23
6.4.24 SEND DTMF ................................................................................................... 14
24
6.4.25 LANGUAGE NOTIFICATION ............................................................................ 14
25
6.4.26 LAUNCH BROWSER ....................................................................................... 14
26
6.4.27 OPEN CHANNEL ............................................................................................. 14
27
6.4.28 CLOSE CHANNEL ........................................................................................... 14
28
6.4.29 RECEIVE DATA .............................................................................................. 14
29
6.4.30 SEND DATA.................................................................................................... 15
30
6.4.31 GET CHANNEL STATUS .................................................................................. 15
31
6.4.32 SERVICE SEARCH .......................................................................................... 15
32
6.4.33 GET SERVICE INFORMATION ......................................................................... 15
ii
3GPP2 C.S0035-B v2.0
1
6.4.34 DECLARE SERVICE ........................................................................................ 15
2
6.5 Common elements in proactive UICC commands ..................................................... 15
3
6.6 Structure of proactive UICC commands .................................................................. 15
4
6.6.1 DISPLAY TEXT ................................................................................................. 15
5
6.6.2 GET INKEY ....................................................................................................... 15
6
6.6.3 GET INPUT ....................................................................................................... 15
7
6.6.4 MORE TIME ..................................................................................................... 15
8
6.6.5 PLAY TONE ...................................................................................................... 15
9
6.6.6 POLL INTERVAL ............................................................................................... 15
10
6.6.7 SET-UP MENU .................................................................................................. 15
11
6.6.8 SELECT ITEM .................................................................................................. 16
12
6.6.9 SEND SHORT MESSAGE .................................................................................. 16
13
6.6.10 Reserved ......................................................................................................... 16
14
6.6.11 SEND USSD ................................................................................................... 16
15
6.6.12 SET UP CALL .................................................................................................. 16
16
6.6.13 REFRESH ....................................................................................................... 16
17
6.6.14 POLLING OFF ................................................................................................. 16
18
6.6.15 PROVIDE LOCAL INFORMATION .................................................................... 16
19
6.6.16 SET UP EVENT LIST ....................................................................................... 16
20
6.6.17 PERFORM CARD APDU .................................................................................. 16
21
6.6.18 POWER OFF CARD ......................................................................................... 16
22
6.6.19 POWER ON CARD........................................................................................... 16
23
6.6.20 GET READER STATUS .................................................................................... 16
24
6.6.21 TIMER MANAGEMENT .................................................................................... 16
25
6.6.22 SET UP IDLE MODE TEXT .............................................................................. 17
26
6.6.23 RUN AT COMMAND ........................................................................................ 17
27
6.6.24 SEND DTMF COMMAND ................................................................................. 17
28
6.6.25 LANGUAGE NOTIFICATION ............................................................................ 17
29
6.6.26 LAUNCH BROWSER ....................................................................................... 17
30
6.6.27 OPEN CHANNEL ............................................................................................. 17
31
6.6.28 CLOSE CHANNEL ........................................................................................... 17
32
6.6.29 RECEIVE DATA .............................................................................................. 17
iii
3GPP2 C.S0035-B v2.0
1
6.6.30 SEND DATA.................................................................................................... 17
2
6.6.31 GET CHANNEL STATUS .................................................................................. 17
3
6.6.32 SERVICE SEARCH .......................................................................................... 17
4
6.6.33 GET SERVICE INFORMATION ......................................................................... 17
5
6.6.34 DECLARE SERVICE ........................................................................................ 17
6
6.7 Command results ................................................................................................... 18
7
6.8 Structure of TERMINAL RESPONSE ........................................................................ 18
8
6.8.1 Command details .............................................................................................. 18
9
6.8.2 Device identities ............................................................................................... 18
10
6.8.3 Result .............................................................................................................. 18
11
6.8.4 Duration .......................................................................................................... 18
12
6.8.5 Text string ........................................................................................................ 18
13
6.8.6 Item identifier ................................................................................................... 18
14
6.8.7 Local information .............................................................................................. 18
15
6.8.8 Call control requested action ............................................................................. 18
16
6.8.9 Result data object 2 .......................................................................................... 18
17
6.8.10 Card reader status .......................................................................................... 18
18
6.8.11 Card ATR ........................................................................................................ 18
19
6.8.12 R-APDU .......................................................................................................... 19
20
6.8.13 Timer identifier ............................................................................................... 19
21
6.8.14 Timer value .................................................................................................... 19
22
6.8.15 AT Response ................................................................................................... 19
23
6.8.16 Text string 2 ................................................................................................... 19
24
6.8.17 Channel data .................................................................................................. 19
25
6.8.18 Channel status ............................................................................................... 19
26
6.8.19 Channel data length ....................................................................................... 19
27
6.8.20 Bearer description .......................................................................................... 19
28
6.8.21 Buffer size ...................................................................................................... 19
29
6.8.22 Total Display Duration .................................................................................... 19
30
6.8.23 Service Availability .......................................................................................... 19
31
6.8.24 Service Record ................................................................................................ 19
32
6.9 Proactive UICC session and ME display interaction ................................................. 19
iv
3GPP2 C.S0035-B v2.0
1
6.10 Handling of unknown, unforeseen and erroneous messages .................................. 20
2
6.11 Proactive commands versus possible terminal response ........................................ 20
3
7 ENVELOPE Commands ................................................................................................ 21
4
7.1 Data Download to UICC .......................................................................................... 21
5
7.1.1 SMS-PP Data Download .................................................................................... 21
6
7.1.1.1 Procedure ................................................................................................... 21
7
7.1.1.2 Structure of ENVELOPE (SMS-PP Data Download) ....................................... 22
8
7.1.2 Cell Broadcast Data Download .......................................................................... 23
9
7.1.2.1 Structure of ENVELOPE (CELL BROADCAST DOWNLOAD) .......................... 23
10
7.2 Menu Selection....................................................................................................... 23
11
7.3 Call Control ............................................................................................................ 23
12
7.3.1 Call Control by UICC ........................................................................................ 23
13
7.3.1.1 Procedure for mobile originated calls ........................................................... 23
14
7.3.1.2 Procedure for USSD .................................................................................... 24
15
7.3.1.3 Indication to be given to the user ................................................................. 24
16
7.3.1.4 Interaction with Fixed Dialling Number (FDN) .............................................. 24
17
7.3.1.5 Support of Barred Dialling Number (BDN) service ........................................ 24
18
7.3.1.6 Structure of ENVELOPE (CALL CONTROL) .................................................. 24
19
7.3.1.7 MO Short Message Control by UICC ............................................................ 25
20
7.3.1.8 Description ................................................................................................. 25
21
7.3.1.9 Structure of ENVELOPE (MO SHORT MESSAGE CONTROL) ........................ 25
22
7.3.1.10 Indication to be given to the user ............................................................... 27
23
7.3.1.11 Interaction with Fixed Dialing Number (FDN) ............................................. 27
24
7.4 Timer Expiration .................................................................................................... 27
25
7.5 Event download ...................................................................................................... 27
26
7.6 USSD Data Download ............................................................................................. 28
27
8 SIMPLE-TLV generic data objects ................................................................................. 29
28
8.1 Address .................................................................................................................. 29
29
8.2 Alpha identifier....................................................................................................... 29
30
8.3 Sub-Address .......................................................................................................... 29
31
8.4 Capability Configuration Parameters ....................................................................... 29
32
8.5 Reserved ................................................................................................................ 29
v
3GPP2 C.S0035-B v2.0
1
8.6 Command details ................................................................................................... 29
2
8.7 Device identities ..................................................................................................... 29
3
8.8 Duration ................................................................................................................ 29
4
8.9 Item ....................................................................................................................... 29
5
8.10 Item identifier ....................................................................................................... 29
6
8.11 Response length ................................................................................................... 29
7
8.12 Result .................................................................................................................. 30
8
8.13 Reserved .............................................................................................................. 30
9
8.14 Reserved .............................................................................................................. 30
10
8.15 Text string ............................................................................................................ 30
11
8.16 Tone..................................................................................................................... 30
12
8.17 USSD string ......................................................................................................... 30
13
8.18 File List ................................................................................................................ 30
14
8.19 Location Information ............................................................................................ 31
15
8.20 Reserved .............................................................................................................. 35
16
8.21 Help Request ........................................................................................................ 35
17
8.22 Network Measurement Results.............................................................................. 35
18
8.23 Default Text ......................................................................................................... 35
19
8.24 Items Next Action Indicator ................................................................................... 35
20
8.25 Event list.............................................................................................................. 35
21
8.26 Cause .................................................................................................................. 35
22
8.27 Location Status .................................................................................................... 35
23
8.28 Transaction Identifier ........................................................................................... 36
24
8.29 Reserved .............................................................................................................. 36
25
8.30 Call control requested action ................................................................................ 36
26
8.31 Icon Identifier ....................................................................................................... 36
27
8.32 Item Icon Identifier list ......................................................................................... 36
28
8.33 Card reader status ............................................................................................... 36
29
8.34 Card ATR ............................................................................................................. 36
30
8.35 C-APDU ............................................................................................................... 37
31
8.36 R-APDU ............................................................................................................... 37
32
8.37 Timer identifier ..................................................................................................... 37
vi
3GPP2 C.S0035-B v2.0
1
8.38 Timer value .......................................................................................................... 37
2
8.39 Date-Time ............................................................................................................ 37
3
8.40 AT Command ....................................................................................................... 37
4
8.41 AT Response ........................................................................................................ 37
5
8.42 Reserved .............................................................................................................. 37
6
8.43 Immediate response.............................................................................................. 37
7
8.44 DTMF string ......................................................................................................... 37
8
8.45 Language ............................................................................................................. 37
9
8.46 Reserved .............................................................................................................. 37
10
8.47 Browser Identity ................................................................................................... 37
11
8.48 URL ..................................................................................................................... 38
12
8.49 Bearer .................................................................................................................. 38
13
8.50 Provisioning File Reference ................................................................................... 38
14
8.51 Browser Termination Cause .................................................................................. 38
15
8.52 Bearer description ................................................................................................ 38
16
8.53 Channel data ....................................................................................................... 38
17
8.54 Channel data length ............................................................................................. 38
18
8.55 Buffer size ............................................................................................................ 38
19
8.56 Channel status ..................................................................................................... 38
20
8.57 Card reader identifier ........................................................................................... 38
21
8.58 Other Address ...................................................................................................... 38
22
8.59 UICC/ME interface transport level ........................................................................ 38
23
8.60 AID ...................................................................................................................... 39
24
8.61 Access Technology ................................................................................................ 39
25
8.62 Display parameters .............................................................................................. 39
26
8.63 Service Record ...................................................................................................... 39
27
8.64 Device Filter ......................................................................................................... 39
28
8.65 Service Search ...................................................................................................... 39
29
8.66 Attribute Information ............................................................................................ 39
30
8.67 Service Availability ............................................................................................... 39
31
8.68 Remote Entity Address ......................................................................................... 39
32
8.69 ESN ..................................................................................................................... 39
vii
3GPP2 C.S0035-B v2.0
1
8.70 Network access name ........................................................................................... 40
2
8.71 CDMA SMS TPDU................................................................................................. 40
3
8.72 Text Attribute ....................................................................................................... 40
4
8.73 Item Text Attribute List ......................................................................................... 40
5
8.74 Reserved .............................................................................................................. 40
6
8.75 Network Search Mode ........................................................................................... 40
7
8.76 Battery State ........................................................................................................ 41
8
8.77 Browsing Status ................................................................................................... 41
9
8.78 Frame Layout ....................................................................................................... 41
10
8.79 Frame Information ............................................................................................... 41
11
8.80 Frame Identifier .................................................................................................... 41
12
8.81 MEID ................................................................................................................... 41
13
8.82 Multimedia Message Reference ............................................................................. 41
14
8.83 Multimedia Message Identifier .............................................................................. 41
15
8.84 Multimedia Message Transfer Status .................................................................... 41
16
8.85 MM Content Identifier........................................................................................... 41
17
8.86 Multimedia Message Notification ........................................................................... 42
18
8.87 Last Envelope ....................................................................................................... 42
19
8.88 Registry Application Data ..................................................................................... 42
20
8.89 Activate Descriptor ............................................................................................... 42
21
8.90 Broadcast Network Information ............................................................................ 42
22
8.91 Contactless state request ...................................................................................... 42
23
8.92 Contactless functionality state .............................................................................. 42
24
8.93 Extended registry application data ........................................................................ 42
25
9 Tag values ................................................................................................................... 43
26
9.1 BER-TLV tags in ME to UICC direction ................................................................... 43
27
9.2 BER-TLV tags in UICC TO ME direction .................................................................. 43
28
9.3 COMPREHENSION-TLV tags in both directions ....................................................... 43
29
9.4 Type of Command and Next Action Indicator ........................................................... 43
30
9.5 3GPP2 Tag Values .................................................................................................. 44
31
10 Allowed Type of command and Device identity combinations ....................................... 45
32
11 Security requirements ................................................................................................ 46
viii
3GPP2 C.S0035-B v2.0
1
12 CDMA2000 Specific Simple TLV Data Objects ............................................................. 47
ix
3GPP2 C.S0035-B v2.0
FOREWORD
1
2
3
4
5
6
7
8
9
10
11
12
This foreword is not part of this document.
This document contains the requirements for CDMA Card Application Toolkit (CCAT). It
2
extends the Card Application Toolkit [1] 1 to enable operation in cdma2000® . CCAT is a set of
commands and procedures for use during the network operation phase of CDMA, in addition to
those defined in [13]. Specifying the interface is to ensure interoperability between a UICC (RUIM or CSIM) and an ME independently of the respective manufacturers and operators. CCAT
will allow Service Providers to offer unique services to their subscribers by placing applications
they have designed (or third party applications) on the UICC that would function on any
particular manufacturer’s ME that supports the Toolkit features.
These requirements are expressed as additions to current release of [1]. The composite CCAT
specification is comprised of [1] and this ancillary document.
13
14
1
[ ] indicates the corresponding document to be cross referenced
2
cdma2000® is the trademark for the technical nomenclature for certain specifications and standards
of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication),
cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the
United States.
x
3GPP2 C.S0035-B v2.0
1
1 GENERAL
2
1.1 Scope
3
4
5
6
7
8
9
10
The present document defines the interface between the UICC and the Mobile Equipment (ME),
and mandatory ME procedures, specifically for CDMA Card Application Toolkit (CCAT).
As stated in [1], the UICC refers to an ICC that supports a Network Access Application. All
references to UICC in [1] shall be interpreted as a card holding a network access application,
i.e. an R-UIM or CSIM, in this document.
The present document refers in its majority to [1], which describes the generic aspects of
application toolkits within the UICC. CCAT is a set of commands and procedures for use during
the network operation phase of CDMA, in addition to those defined in [13].
12
Specifying the interface is needed to ensure interoperability between a UICC and an ME
independently of the respective manufacturers and operators.
13
The present document defines for CDMA technology:
11
14
-
The commands;
15
-
The application protocol;
16
-
The mandatory requirements on the UICC and ME for each procedure.
17
18
19
20
21
22
23
24
25
26
27
CCAT will allow Service Providers to offer unique services to their subscribers by placing
applications they have designed (or third party applications) on the UICC that would function
on any particular manufacturer’s ME that supports the Toolkit features.
These requirements are expressed as additions to current release of [1]. The composite CCAT
specification is comprised of [1] and this ancillary document.
The present document does not specify any aspects related to the administrative management
phase. Any internal technical realizations of either the UICC or the ME are only specified where
these reflect over the interface. The present document does not specify any of the security
algorithms, which may be used.
Within the context of the present document, the term "terminal" used in [1] refers to the Mobile
Equipment (ME).
29
Within the context of the present document, the term "NAA" used in [1] refers to the CDMA
Card Application Toolkit (CCAT).
30
1.2 Document Conventions
28
31
32
33
34
35
36
“Shall” and “shall not” identify requirements to be followed strictly to conform to this document
and from which no deviation is permitted. “Should” and “should not” indicate that one of
several possibilities is recommended as particularly suitable, without mentioning or excluding
others, that a certain course of action is preferred but not necessarily required, or that (in the
negative form) a certain possibility or course of action is discouraged but not prohibited. “May”
and “need not” indicate a course of action permissible within the limits of the document. “Can”
1
3GPP2 C.S0035-B v2.0
1
2
and “cannot” are used for statements of possibility and capability, whether material, physical
or causal.
2
3GPP2 C.S0035-B v2.0
1
2 REFERENCES
2
2.1 Normative References
7
The following standards are referenced in this text. At the time of publication, the editions
indicated were valid. All standards are subject to revision and parties to agreements based on
this standard are encouraged to investigate the possibility of applying the most recent editions
of the standards indicated below. ANSI and TIA maintain registers of currently valid national
standards published by them.
8
1.
ETSI TS 102 223, Smart Cards; Card Application Toolkit.
9
2.
ANSI/INCITS 4-1986(R 1997), Information Processing – Coded Character Sets – 7-bit
American National Standard Code for Information Interchange (7-bit ASCII), 1986.
3.
C.S0015-B v2.0, Short Message Service (SMS) for Wideband Spread Spectrum SystemsRelease B, 2005.
13
4.
Void.
14
5.
3GPP TS 22.001, Principles of circuit telecommunication services supported by a Public
Land Mobile Network (PLMN).
6.
ITU-T T.50, International reference alphabet (IRA) (Formerly International Alphabet n5 or
IA5) information technology – 7bit Coded Characters Set for Information Interchange 1992.
7.
ETSI TS 102 221, Smart Cards; UICC – ME Interface; Physical and Logical Characteristics,
Release 9, 2010.
20
8.
3GPP2 X.S0004-E. Mobile Application Part (MAP). 2010.
21
9.
Reserved.
22
10.
ITU-T Recommendation E.212, Identification Plan for Land Mobile Stations, 2008.
23
11.
ETSI TS 123 038, Digital Cellular Telecommunications System (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); Alphabets and Language-Specific Information,
3GPP TS 23.038 Release 10, 2011.
12.
ETSI TS 122 016, International Mobile Equipment Identities (IMEI), 3GPP TS 22.016
Release 10, 2011.
28
13.
C.S0023-D v1.0, Removable User Identity Module for Spread Spectrum Systems, 2009.
29
14.
Void.
30
15.
3GPP2 C.S0074-0, UICC-Terminal interface Physical and Logical characteristics for
cdma2000 Spread Spectrum Systems, 2005.
16.
ETSI TS 101 220 Smart Cards; ETSI numbering system for telecommunication application
providers.
34
17.
C.S0024-B v3.0, cdma2000 High Rate Packet Data Air Interface Specification, 2009.
35
18.
3GPP2 C.S0005-E v3.0, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread
Spectrum Systems, 2011.
19.
3GPP TS 51.014 v4.5.0, Specification of the SIM Application Toolkit for the Subscriber
Identity Module – Mobile Equipment (SIM – ME) interface, 2004.
39
20.
3GPP TS 31.111, Universal Subscriber Identity Module (USIM) Application Toolkit (USAT).
40
21.
3GPP2 C.S0065-B v2.0. cdma2000 Application on UICC for Spread Spectrum Systems,
2011.
22.
3GPP2 X.S0057, E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects.
3
4
5
6
10
11
12
15
16
17
18
19
24
25
26
27
31
32
33
36
37
38
41
42
3
3GPP2 C.S0035-B v2.0
1
23.
2
3GPP2 C.S0105-0 v1.0. Unstructured Supplementary Service Data (USSD) Service Options
for Spread Spectrum Systems: Service Options 78 and 79. 2012.
3
2.2 Informative References
4
i1
3GPP2 C.S0001-E v3.0, Introduction to cdma2000 Standards for Spread Spectrum
Systems, 2011.
i2
3GPP2 C.S0002-E v3.0, Physical Layer Standard for cdma2000 Spread Spectrum Systems,
2011.
i3
3GPP2 C.S0003-E v3.0, Medium Access Control (MAC) Standard for cdma2000 Spread
Spectrum Systems, 2011.
i4
3GPP2 C.S0004-E v3.0, Signaling Link Access Control (LAC) Standard for cdma2000
Spread Spectrum Systems, 2011.
12
i5
Replaced by normative reference 18.
13
i6
3GPP2 C.S0006-D v2.0, Analog Signaling Standard for cdma2000 Spread Spectrum
Systems, 2005.
i7
TIA/EIA/IS-95-B, Mobile Station – Base Station Compatibility Standard for Wideband
Spread Spectrum Cellular Standards, December 1998.
i8
C.R1001-H, Administration of Parameter Value Assignments for cdma2000 Spread
Spectrum Standards, July 2011.
i9
3GPP2 S.R0048-A v4.0, 3G Mobile Equipment Identifier (MEID) - Stage 1, November,
2005.
i10
Replaced by normative reference 22.
5
6
7
8
9
10
11
14
15
16
17
18
19
20
21
22
4
3GPP2 C.S0035-B v2.0
1
2
3
4
3 TERMS
Base Station. A fixed station used for communicating with mobile stations. Depending upon
the context, the term base station may refer to a cell, a sector within a cell, a MSC, an OTAF or
other part of the wireless system. (See also MSC and OTAF).
6
Card Application Toolkit. A set of generic commands and procedures for use by the ICC,
irrespective of the access technology of the network.
7
CAT. See Card Application Toolkit.
8
CCAT. See CDMA Card Application Toolkit.
5
10
CDMA Card Application Toolkit. A set of commands and procedures for use during the
network operation phase of CDMA.
11
CSIM. cdma2000 Subscriber Identity Module.
12
ECC. Emergency Call Code from EFECC.
13
eHRPD. Evolved HRPD.
9
15
Global Emergency Call Indicator (GECO). Used by the Mobile Station to identify an
Emergency Call as specified in [18].
16
ICC. Integrated Circuit(s) Card.
17
IMEI. International Mobile Equipment Identity.
18
IMSI. See International Mobile Subscriber Identity.
14
19
20
International Mobile Equipment Identity. A method of identifying a mobile equipment in the
land mobile service as specified in [10].
22
International Mobile Subscriber Identity. A method of identifying a subscriber in the land
mobile service as specified in [12].
23
M/O. Mandatory / Optional.
24
MCC. Mobile Country Code.
25
ME. Mobile Equipment.
26
MEID. Mobile Equipment Identifier.
27
Min. Minimum.
28
MNC. Mobile Network Code.
29
MSC. Mobile Switching Center.
30
MT. Mobile terminated.
21
32
Network Identification. A number that uniquely identifies a network within a wireless system.
See also System Identification.
33
NID. See Network Identification.
34
NITZ. Network Identity and Time Zone.
31
5
3GPP2 C.S0035-B v2.0
1
OTAF. See Over-the-Air Provisioning Function.
2
OTASP. See Over-the-Air Service Provisioning.
3
4
Over-the-Air Provisioning Function. A configuration of network equipment that controls
OTASP functionality messaging protocols.
6
Over-the-Air Service Provisioning. A process of provisioning mobile station operational
parameters over the air interface.
7
RFU. Reserved for Future Use.
8
R-UIM. Removable User Identity Module.
9
SID. See System Identification.
5
12
Simple TLV. A data object that consists of a tag of length one byte, a length indicator, which
gives the number of bytes in the value field and a value part of variable length. (Called
Comprehension TLV in [1]).
13
SMS. Short Message Service.
14
SMS-MO. Short Message Service Mobile Originated.
15
SMS-MT. Short Message Service Mobile Terminated.
16
SW1/SW2. Status Word 1/Status Word 2.
17
System Identification. A number uniquely identifying a wireless system.
10
11
19
Terminal Response. This function is used to transfer from the ME to the UICC the response to
a previously fetched proactive command.
20
TLV. Tag Length Value.
21
TPDU. See Transfer Protocol Data Unit.
18
22
23
24
25
Transfer Protocol Data Unit. Command and response format used for communication
between the ME and UICC.
UICC. Within the scope of this document, an ICC supporting at least one network access
application, i.e. an R-UIM or CSIM. USSD. Unstructured Supplementary Service Data [23].
6
3GPP2 C.S0035-B v2.0
1
2
3
4
4 OVERVIEW OF CCAT
The CCAT provides mechanisms, which allow applications, existing in the UICC, to interact
and operate with any ME, which supports the specific mechanism(s), required by the
application.
6
The following mechanisms have been defined. These mechanisms are dependent upon the
commands and protocols relevant to CCAT in [7].
7
4.1 Profile Download
8
See [1].
9
4.2 Proactive UICC
5
10
See [1]. Also, sending a USSD string [20].
11
4.3 Data download to UICC
12
See [1].
13
4.4 Menu selection
14
See [1].
15
4.5 Call control by network access application
16
See [1]. This also applies to USSD operations [20].
17
4.6 MO Short Message Control by UICC
18
See [20].
19
4.7 Event download
20
See [1].
21
4.8 Security
22
See [1].
23
4.9 Multiple card
24
See [1].
25
4.10 Timer Expiration
26
See [1].
7
3GPP2 C.S0035-B v2.0
1
4.11 Bearer Independent Protocol
2
See [1].
3
4.12 Description of the access technology indicator mechanism
4
See [1].
5
4.13 Tag allocation guidelines
6
See [1].
8
3GPP2 C.S0035-B v2.0
1
5 PROFILE DOWNLOAD
2
5.1 Procedure
3
4
5
6
The profile download instruction is sent by the ME to the UICC as part of the UICC
initialization procedure. This procedure is specified as TERMINAL PROFILE in [7]. The profile
sent by the ME shall state the facilities relevant to CCAT that are supported by the ME.
See additional details for TERMINAL PROFILE in [1].
7
5.2 Structure and coding of TERMINAL PROFILE
8
Direction: ME to UICC.
9
The command header is the one specified for TERMINAL PROFILE in [7].
10
Command parameters/data:
11
Description
Clause
M/O/C
Length
-
M
lgth
Profile
12
Profile:
-
13
Contents:
 The list of CCAT facilities that are supported by the ME.
14
-
15
Coding (1 bit is used to code each facility):
16
 bit = 1: facility supported by ME.
17
 bit = 0: facility not supported by ME.
18
19
20
21
22
23
24
This section lists only CDMA specific bytes (e.g. Twentieth Byte) of the TERMINAL PROFILE.
All other bytes of the TERMINAL PROFILE can be found in [1].
The following bits listed as “Reserved for 3GPP” in some versions of [1] are in use by this
document with the following meanings taken from [20]:



Byte 1, bit 7 – Call Control is supported.
Byte 4, bit 4: Proactive UICC: SEND USSD.
Byte 23, bit 8: USSD Data download and application mode.
25
26
Twentieth byte (Reserved for 3GPP2 C.S0035 CCAT):
b8 b7 b6 b5 b4 b3 b2 b1
SEND CDMA SMS
CDMA SMS-PP data download
CDMA SMS BROADCAST data download
CDMA USSD support (Note 1)
CDMA MO SMS Control support (Note 2)
RFU
9
3GPP2 C.S0035-B v2.0
1
2
3
4
5
6
7
8
Notes:
1. This bit indicates that the USSD control bits (Byte 1 bit 7, Byte 4 bit 4 and Byte 23 bit
8) should be considered when the ME is operating in a CDMA mode (Access Technology
‘05’, ‘06’, ‘07’ or ‘09’). Otherwise they should be treated as if they were set to ‘0’ in a
CDMA mode.
2. This bit indicates that Mobile Originated SMS Control is supported when the ME is
operating in a CDMA mode (Access Technology ‘05’, ‘06’, ‘07’ or ‘09’). This bit is
independent of byte 2, bit 4, which indicates support for other technologies.
9
10
11
Response parameters/data:
-
None.
12
5.3 Definition of display parameters in Profile download
13
See [1].
10
3GPP2 C.S0035-B v2.0
1
6 PROACTIVE UICC
2
6.1 Introduction
3
See [1]. The list of commands also includes SEND USSD from [20].
4
6.2 Identification of ME support
5
See [1].
6
6.3 General procedure
7
See [1].
8
6.4 Proactive UICC commands and procedures
9
6.4.1 DISPLAY TEXT
10
See [1].
11
6.4.2 GET INKEY
12
See [1].
13
6.4.3 GET INPUT
14
See [1].
15
6.4.4 MORE TIME
16
See [1].
17
6.4.5 PLAY TONE
18
See [1].
19
NOTE:
Some supervisory tones are optional for mobile equipment (see [5]).
20
6.4.6 POLL INTERVAL
21
See [1].
22
6.4.7 REFRESH
23
See [1].
24
6.4.8 SET UP MENU
25
See [1].
26
6.4.9 SELECT ITEM
27
See [1].
11
3GPP2 C.S0035-B v2.0
1
6.4.10 SEND SHORT MESSAGE
2
Two types are defined:
3
-
A short message to be sent to the network in an SMS Submit Message where the
user data can be passed transparently, without packing by the ME;
-
A short message to be sent to the network in an SMS Submit Message where the
user data needs to be packed by the ME.
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Where packing by the ME is not required, the CDMA SMS TPDU shall be coded as defined in
[3]. The Command details data object shall indicate, “Packing is not required”.
Where packing by the ME is required, the UICC shall use the “7-bit ASCII” coding as defined in
[2], “IA5” coding as defined in [6] or the “GSM 7-bit default alphabet” as defined in [11]. The
UICC shall place the user data into 8-bit octets with bit 8 set to ‘0’. NUM_FIELDS provided by
the UICC shall state the number of characters in the text string. The Command details data
object shall indicate, “Packing is required”. The ME shall pack the user data into 7 bit fields as
described in section 6.2.1 of [11] and reconstruct the TPDU before submitting the message to
the network. The MSG_ENCODING shall not be changed and the ME shall not interpret the
message encoding as indicating the receipt of 7 bit fields from the UICC.
Optionally, the UICC may include in this command an alpha identifier. The use of this alpha
identifier by the ME is described below.
-
If the alpha identifier is provided by the UICC and is not a null data object, the ME
shall use it to inform the user. This is also an indication that the ME should not
give any other information to the user on the fact that the ME is sending a short
message. If an icon is provided by the UICC, the icon indicated in the command
may be used by the ME to inform the user, in addition to or instead of the alpha
identifier, as indicated with the icon qualifier.
-
If the alpha identifier is provided by the UICC and is a null data object (i.e. length =
‘00’ and no value part), this is an indication that the ME should not give any
information to the user on the fact that the ME is sending a short message.
-
If the alpha identifier is not provided by the UICC, the ME may give information to
the user concerning what is happening.
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
A terminal of type ND shall ignore any alpha identifier provided together with this command.
The terminal shall respond with “command performed successfully” upon successful
completion of the command. A terminal of type ND shall also ignore any icon provided together
with this command. The terminal shall respond with “command performed successfully but
requested icon could not be displayed” upon successful completion of the command.
If the ME is capable of SMS-MO, then it shall send the data as a CDMA SMS TPDU to the
destination address including the Bearer Reply Option.
If the ME receives an SMS Acknowledgment Message [3] from the network, it shall give the
result to the UICC using TERMINAL RESPONSE indicating successful or unsuccessful
transmission of the Short Message. The ME should not give any information to the user at the
reception of the SMS Acknowledgement Message.
12
3GPP2 C.S0035-B v2.0
4
If the network fails to acknowledge receipt of the CDMA SMS TPDU, after a timeout the ME
shall inform the UICC using TERMINAL RESPONSE (Network currently unable to process
command – No specific cause can be given). The ME should not give any information to the
user in the case of a timeout.
5
6.4.11 Reserved
6
6.4.12 SEND USSD
1
2
3
7
8
9
10
11
12
See section 6.4.12 of [20].
6.4.13 SET UP CALL
This command is issued by a UICC to request that the ME set up a call. The procedure is
defined in section 6.4.13 of [1], except when stated otherwise in the present document.
It is possible for the UICC to request the ME to set up an emergency call by supplying any ECC
in EFECC or “112”.
15
If the ME supports EFCSIM_ST Service n27 (Outgoing Call Information (OCI)), it shall not store the
call set-up details (called party number and associated parameters) sent by the UICC in this
command in EFOCI.
16
6.4.14 POLLING OFF
17
See [1].
18
6.4.15 PROVIDE LOCAL INFORMATION
13
14
19
20
This command requests the ME to send current local information to the UICC. At present, this
information is restricted to:
21
-
Location information;
22
-
The ESN or MEID of the ME;
23
-
The current date, time and time zone;
24
-
The current ME language setting;
25
-
The current access technology.
26
27
28
29
30
31
32
33
The ME shall return the requested local information, as stored in the ME, within a TERMINAL
RESPONSE.
When location information has been requested and is not available, the ME shall return the
result “terminal currently unable to process command - no service” and shall not return the
data requested.
The ME shall return the current date and time as set by the user or by the network. If
available, the ME shall also return the time zone from the network. If the time zone information
is not available, the ME shall return ‘FF’ for this element.
13
3GPP2 C.S0035-B v2.0
1
6.4.16 SET UP EVENT LIST
2
See [1].
3
6.4.17 PERFORM CARD APDU
4
See [1].
5
6.4.18 POWER OFF CARD
6
See [1].
7
6.4.19 POWER ON CARD
8
See [1].
9
6.4.20 GET READER STATUS
10
See [1].
11
6.4.21 TIMER MANAGEMENT
12
See [1].
13
6.4.22 SET UP IDLE MODE TEXT
14
See [1].
15
6.4.23 RUN AT COMMAND
16
See [1].
17
6.4.24 SEND DTMF
18
See [1].
19
6.4.25 LANGUAGE NOTIFICATION
20
See [1].
21
6.4.26 LAUNCH BROWSER
22
See [1].
23
6.4.27 OPEN CHANNEL
24
See [1].
25
6.4.28 CLOSE CHANNEL
26
See [1].
27
6.4.29 RECEIVE DATA
28
See [1].
14
3GPP2 C.S0035-B v2.0
1
6.4.30 SEND DATA
2
See [1].
3
6.4.31 GET CHANNEL STATUS
4
See [1].
5
6.4.32 SERVICE SEARCH
6
See [1].
7
6.4.33 GET SERVICE INFORMATION
8
See [1].
9
6.4.34 DECLARE SERVICE
10
See [1].
11
6.5 Common elements in proactive UICC commands
12
See [1].
13
6.6 Structure of proactive UICC commands
14
The general structure of proactive UICC commands using TLV objects is described in annex C.
15
6.6.1 DISPLAY TEXT
16
See [1].
17
6.6.2 GET INKEY
18
See [1].
19
6.6.3 GET INPUT
20
See [1].
21
6.6.4 MORE TIME
22
See [1].
23
6.6.5 PLAY TONE
24
See [1].
25
6.6.6 POLL INTERVAL
26
See [1].
27
6.6.7 SET-UP MENU
28
See [1].
15
3GPP2 C.S0035-B v2.0
1
6.6.8 SELECT ITEM
2
See [1].
3
6.6.9 SEND SHORT MESSAGE
4
See [1].
5
6.6.10 Reserved
6
6.6.11 SEND USSD
7
This command is defined in [20].
8
6.6.12 SET UP CALL
9
This command is defined in [1].
10
6.6.13 REFRESH
11
See [1].
12
6.6.14 POLLING OFF
13
See [1].
14
6.6.15 PROVIDE LOCAL INFORMATION
15
See [1].
16
6.6.16 SET UP EVENT LIST
17
See [1].
18
6.6.17 PERFORM CARD APDU
19
See [1].
20
6.6.18 POWER OFF CARD
21
See [1].
22
6.6.19 POWER ON CARD
23
See [1].
24
6.6.20 GET READER STATUS
25
See [1].
26
6.6.21 TIMER MANAGEMENT
27
See [1].
16
3GPP2 C.S0035-B v2.0
1
6.6.22 SET UP IDLE MODE TEXT
2
See [1].
3
6.6.23 RUN AT COMMAND
4
See [1].
5
6.6.24 SEND DTMF COMMAND
6
See [1].
7
6.6.25 LANGUAGE NOTIFICATION
8
See [1].
9
6.6.26 LAUNCH BROWSER
10
See [1].
11
6.6.27 OPEN CHANNEL
12
See [1].
13
6.6.28 CLOSE CHANNEL
14
See [1].
15
6.6.29 RECEIVE DATA
16
See [1].
17
6.6.30 SEND DATA
18
See [1].
19
6.6.31 GET CHANNEL STATUS
20
See [1].
21
6.6.32 SERVICE SEARCH
22
See [1].
23
6.6.33 GET SERVICE INFORMATION
24
See [1].
25
6.6.34 DECLARE SERVICE
26
See [1].
17
3GPP2 C.S0035-B v2.0
1
6.7 Command results
3
See [1]. In addition, the temporary problem, “ME currently busy on USSD operation”, and the
permanent problem, “USSD Return Error”, are included from [20].
4
6.8 Structure of TERMINAL RESPONSE
5
See [1]. Also see [20] for structure of TERMINAL RESPONSE related to SEND USSD.
6
6.8.1 Command details
7
See [1].
8
6.8.2 Device identities
9
See [1].
2
10
6.8.3 Result
11
See [1].
12
6.8.4 Duration
13
See [1].
14
6.8.5 Text string
15
See [1]. Also see [20] for use with a SEND USSD command.
16
6.8.6 Item identifier
17
See [1].
18
6.8.7 Local information
19
See [1].
20
6.8.8 Call control requested action
21
See [1]. Also see [20] for use with a SEND USSD command.
22
6.8.9 Result data object 2
23
See [1]. Also see [20] for use with a SEND USSD command.
24
6.8.10 Card reader status
25
See [1].
26
6.8.11 Card ATR
27
See [1].
18
3GPP2 C.S0035-B v2.0
1
6.8.12 R-APDU
2
See [1].
3
6.8.13 Timer identifier
4
See [1].
5
6.8.14 Timer value
6
See [1].
7
6.8.15 AT Response
8
See [1].
9
6.8.16 Text string 2
10
See [1]. Also see [20] for use with a SEND USSD command.
11
6.8.17 Channel data
12
See [1].
13
6.8.18 Channel status
14
See [1].
15
6.8.19 Channel data length
16
See [1].
17
6.8.20 Bearer description
18
See [1].
19
6.8.21 Buffer size
20
See [1].
21
6.8.22 Total Display Duration
22
See [1].
23
6.8.23 Service Availability
24
See [1].
25
6.8.24 Service Record
26
See [1].
27
6.9 Proactive UICC session and ME display interaction
28
See [1].
19
3GPP2 C.S0035-B v2.0
1
6.10 Handling of unknown, unforeseen and erroneous messages
2
See [1].
3
6.11 Proactive commands versus possible terminal response
4
See [1].
5
6
Also see [20] for TERMINAL RESPONSE values associated with SEND USSD Proactive
Command.
20
3GPP2 C.S0035-B v2.0
1
7 ENVELOPE COMMANDS
2
7.1 Data Download to UICC
3
7.1.1 SMS-PP Data Download
4
7.1.1.1 Procedure
5
6
7
When the ME receives a Short Message with Teleservice Identifier [3] set to 4103 (“Card
Application Toolkit Protocol Teleservice (CATPT)” [8]) then the ME shall follow the procedure
below.
10
If the ME does not support CCAT or the service “Data Download via SMS-PP” is neither
allocated nor activated in EFCST nor available in EFCSIM_ST, then the ME shall store the message
in EFSMS under DFCDMA.
11
Otherwise:
8
9
-
The ME shall pass the message transparently to the UICC using the ENVELOPE
(SMS-PP Data Download) command as defined in section 7.1.1.2.
14
-
The ME shall not display the message, or alert the user of a short message waiting.
15
-
The ME shall wait for a response from the UICC.
16
-
If the UICC responds with ’93 00’ the ME may retry the command (otherwise it will
respond with a cause code value as described below in Table 1).
-
Otherwise, when the ME receives a response from the UICC it shall send an SMS
User Acknowledgement message3 to the network with the User Data and User
Response Code fields included as described below:
12
13
17
18
19
20
o
21
22
23
24
3
If the Status Words received from the UICC indicate that the ME should use
GET RESPONSE to retrieve response data (i.e. ‘61 XX’, ‘62 XX’, ‘63 XX’ [20],
‘9E XX’ or ‘9F XX’ [19]), then this response data shall be placed in the CHARi
octets of the User Data field. Otherwise the User Data field shall be omitted.
An SMS User Acknowledgment Message is an “SMS Point-to-Point” message with the
Teleservice Identifier set to CATPT and the Bearer Data containing a Message Identifier field
containing a MESSAGE_TYPE of ‘0101’ (User Acknowledgment).[3]
21
3GPP2 C.S0035-B v2.0
o
1
2
3
If one of the following Status Word pairs is received from the UICC the
specified SMS_CauseCode value [8] shall be placed in the User Response
Code field:
4
Status Words
SMS_CauseCode value [8]
‘93 00’ [19]
“Destination Busy”
‘9E XX’ [19]
‘62 XX’
“Other Terminal problem”
‘63 XX’
o
5
6
If the ME receives any other Status Words from the UICC the User Response
Code shall be omitted.
7
7.1.1.2 Structure of ENVELOPE (SMS-PP Data Download)
8
Direction: ME to UICC
9
The command header is specified in [7].
10
Command parameters/data.
11
Description
SMS-PP download tag
Section
7.2 of [16]
M/O
M
Min
Y
Length
1
-
M
Y
1 or 2
8.7 of [1]
M
Y
A
8.71
M
Y
B
Length (A+B)
Device identities
CDMA SMS TPDU
13
Device identities: the ME shall set the device identities to:
 Source:
Network;
14

12
15
16
17
18
-
Destination:
UICC.
Response parameters/data.
If the Status Words received from the UICC (e.g. ’61 XX’, ’62 XX’, ’63 XX’ [1] or ‘9F XX’ [19])
indicate that the ME should use GET RESPONSE to retrieve response data then the following
data is returned:
19
Byte(s)
1-X
(X≤128)
20
21
Description
UICC Acknowledgment
Length
X
The Card Acknowledgment parameter is used as the CHARi octets of the User Data parameter
in the SMS User Acknowledgment message by the ME.
22
3GPP2 C.S0035-B v2.0
1
2
3
4
7.1.2 Cell Broadcast Data Download
If the ME receives a Broadcast SMS message with the Service Category of 0x0020 (Card
Application Toolkit Protocol Teleservice (CATPT)) then the ME shall follow the procedure below:

If the service “Data Download via SMS Broadcast” is not allocated and activated in
EFCST and not available in EFCSIM_ST then the ME shall discard the message.
Otherwise the ME shall pass the message transparently to the UICC using the
ENVELOPE (Cell Broadcast Download) command defined below and shall not display
the message or otherwise alert the user of a short message waiting.
5
6

7
8
10
The ME shall identify new Broadcast SMS messages by their message identifier and service
category.
11
7.1.2.1 Structure of ENVELOPE (CELL BROADCAST DOWNLOAD)
12
Direction: ME to UICC.
13
The command header is specified in [7].
14
Command parameters/data:
9
15
Description
Cell Broadcast download tag (‘D2’)
Length (A+B)
Device identities
CDMA SMS TPDU
M/O
M
Min
Y
Length
1
-
M
Y
1 or 2
8.7 of [1]
M
Y
A
8.71
M
Y
B
17
Device identities: the ME shall set the device identities to:
 source:
Network;
18
 destination:
16
-
Section
3.1 of [16]
UICC.
19
Response parameters/data: None for this type of ENVELOPE command.
20
7.2 Menu Selection
21
See [1].
22
7.3 Call Control
23
7.3.1 Call Control by UICC
24
7.3.1.1 Procedure for mobile originated calls
25
This procedure is defined in [1] with the following exception:
-
If the ENVELOPE (CALL CONTROL) response contains an Address parameter
containing the digits “112” or a number stored in EFECC, the ME shall initiate an
emergency call.
29
-
Supplementary services (other than USSD) are not supported.
30
-
The service “call control” in the USIM Service Table should be interpreted as R-UIM
service n28 (Call Control) or CSIM service n13 (Call Control for Voice Services).
26
27
28
31
23
3GPP2 C.S0035-B v2.0
2
The ME shall follow the call set-up procedure defined in [18] or the USSD operation procedure
defined in [23].
3
7.3.1.2 ReservedProcedure for USSD
4
See section 7.3.1.2 of [20], except that:
5
-
Supplementary Service (SS) operations other than USSD are not supported.
6
-
The service “call control” in the USIM Service Table should be interpreted as R-UIM service
n28 (Call Control) or CSIM service n13 (Call Control for Voice Services).
1
7
8
10
The ME shall follow the call set-up procedure defined in [18] or the USSD operation procedure
defined in [23].
11
7.3.1.3 Indication to be given to the user
12
See [1]
13
7.3.1.4 Interaction with Fixed Dialling Number (FDN)
14
See [1]
15
7.3.1.5 Support of Barred Dialling Number (BDN) service
16
See [1]
17
7.3.1.6 Structure of ENVELOPE (CALL CONTROL)
18
This command is defined in [120]. except that the Command parameters/data table is:
9
Description
Clause
M/O/C
Min
Length
Call control tag
9.1
M
Y
1
Length (A+B+C+D)
Device identities
Address or USSD string
-
M
Y
1 or 2
8.7
M
Y
A
8.1 or 8.17
M
Y
B
Subaddress
8.3
O
N
C
Location information
8.19
M
N
D
19
21
Location information: This data object contains the identification (MCC, IMSI_11_12, SID, NID
etc. as defined in section 8.19) of the current serving cell of the ME.
22
Also, the Response parameters/data table is as follows:
20
Description
Clause
M/O/C
Min
Call control result
-
M
Y
1
Length (A+B+C)
-
M
Y
1 or 2
Address or USSD string
Length
8.1, 8.17
O
N
A
Subaddress
8.3
O
N
B
Alpha identifier
8.2
O
N
C
23
24
-
Supplementary services (other than USSD) are not supported.
25
-
Parameters related to PDP context activation or EPS PDN connection activation
including any comments related to such context activation shall be ignored.
26
24
3GPP2 C.S0035-B v2.0
1
-
Parameters related to Capability configuration and BC repeat indicator shall be ignored.
2
-
The service “call control” in the USIM Service Table should be interpreted as R-UIM
service n28 (Call Control) or CSIM service n13 (Call Control for Voice Services).
3
4
7.3.1.7 MO Short Message Control by UICC
5
7.3.1.8 Description
7
If the service "MO Short Message Control" is available in the R-UIM or CSIM Service Table (see
[13] and [21]), then the ME shall follow the procedure below:
8
-
for all MO short message attempts (even those resulting from a SEND SM proactive UICC
command), the ME shall first pass the destination mobile’s Destination Address to the
UICC, using the ENVELOPE (MO SHORT MESSAGE CONTROL) command defined below.
The ME shall also pass to the UICC in the ENVELOPE (MO SHORT MESSAGE CONTROL)
command the current serving cell;
-
if the UICC responds with '90 00', the ME shall send the short message with the addresses
unchanged;
-
if the UICC responds with any other status code indicating an error, the ME shall not send
the short message;
-
if the UICC responds with '93 00', the ME shall not send the short message and may retry
the command;
-
if the UICC provides response data, then the response data from the UICC shall indicate to
the ME whether to send the short message as proposed, not send the short message or
send a short message using the data supplied by the UICC. It is mandatory for the ME to
perform the MO short message request in accordance with the data from the UICC.
6
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
The ME shall then follow the MO Short Message procedure defined in [3].
27
In the case where the initial MO short message request results from a proactive command
SEND SHORT MESSAGE, if the MO short message control result is "not allowed", the ME shall
inform the UICC using TERMINAL RESPONSE, "interaction with call control by UICC or MO
short message control by UICC, action not allowed".
28
7.3.1.9 Structure of ENVELOPE (MO SHORT MESSAGE CONTROL)
29
Direction: ME to UICC.
30
The command header is specified in [7].
24
25
26
25
3GPP2 C.S0035-B v2.0
1
2
Command parameters/data.
Description
MO Short Message control tag
Length
Annex E
Annex P
Annex A
Clause
M/O/C
Min
9.1
M
Y
Annex
- B AnnexMC
Annex D
Y
Device identities
Annex F
Annex
8.7 G
Address 1
Annex H
Annex
8.1 I AnnexMJ
Address 2
Annex L
Annex
8.1 M AnnexMN Annex
Y O
Location Information
M
Length
1
1 or 2
Y
Annex
Y K
Annex
8.19 Q AnnexCR Annex
Y S
3
4
5
Device identities:
The ME shall set the device identities to:
6

source: ME;
7

destination: UICC.
8
9
10
11
12
13
14
15
16
17
18
Address 1:
Contains the address of the MC to which the ME is proposing to send the short message.
Address 2:
Contains the Destination Address to which the ME is proposing to send the short message.
Location Information:
Include for all 3GPP2 Access Technologies to identify the current serving cell.
Response parameters/data.
It is permissible for the UICC to provide no response data, by responding with SW1/SW2 = '90
00'. If the UICC does not provide any response data, then this shall have the same meaning as
"allowed, no modification".
Description
Annex T
Clause
M/O/C
Min
Length
MO short message control result
-
M
Y
1
Length
-
M
Y
1 or 2
Address 1
8.1
C
N
Address 2
8.1
C
N
Alpha identifier
8.2
O
N
19
20
MO Short Message control result:
21
Contents:
23
The command that the UICC gives to the ME concerning whether to allow, bar or modify the
proposed short message;
24
Coding:
22
26
3GPP2 C.S0035-B v2.0
1
-
'00' = Allowed, no modification;
2
-
'01' = Not allowed;
3
-
'02' = Allowed with modifications.
4
Address 1:
Shall be included if and only if the “MO Short Message control result” is set to “Allowed
with modifications”.
5
6
7
Address 2:
Shall be included if and only if the “MO Short Message control result” is set to “Allowed
with modifications”.
8
9
10
Alpha identifier:
This data object is only required if the UICC requests a particular indication to be given to
the user. The handling of this data object by the ME is described in clause 7.3.2.3.
11
12
13
7.3.1.10 Indication to be given to the user
17
The UICC may optionally include an alpha-identifier in the response data to the ENVELOPE
(MO SHORT MESSAGE CONTROL) message, in order to inform the user at the time the
response is received by the ME. The use of this alpha identifier by the ME is identical to the
one described in clause 7.3.1.3 relative to call control by UICC.
18
7.3.1.11 Interaction with Fixed Dialing Number (FDN)
14
15
16
19
20
21
22
It is permissible for the Fixed Dialing Number service to be enabled (see [13] and [21]) at the
same time as MO Short Message Control is available (in the R-UIM or CSIM Service Table). If
FDN is enabled, the ME shall follow the procedure for Call Control (see clause 7.3.1.4), where
the number in the procedure refers to the SMS destination address.
23
24
7.4 Timer Expiration
25
See [1].
26
7.5 Event download
27
See [1].
28
Regarding all the call events, the following equivalences shall apply:
29
-
for MT Call Event, the Transaction Identifier contains the CON_REF when the call control
instance is instantiated in the message that triggers MT call setup as defined in [18]
(possible message:
Service Connect Message, General Handoff Direction Message,
Universal Handoff Direction Message or Call Assignment Message);
-
for Call Connected Event, the Transaction Identifier contains the CON_REF in the
Connected Order message that triggers the call connection as defined in [18] (possible
message: Service Connect Message, General Handoff Direction Message, Universal Handoff
Direction Message or Call Assignment Message)].
30
31
32
33
34
35
36
27
3GPP2 C.S0035-B v2.0
1
2
-
for Call Disconnected Event, the Transaction Identifier contains a list of all CON_REFs that
refer to the calls being disconnected whose call control instances are terminated.
4
Where events occur and the UICC responds with '93 00', the ME shall retry to deliver the event
download messages to the UICC.
5
7.6 USSD Data Download
6
See [20].
3
28
3GPP2 C.S0035-B v2.0
1
8 SIMPLE-TLV GENERIC DATA OBJECTS
3
The coding of these TLV objects is as described in [1], except when stated otherwise in the
present document.
4
8.1 Address
2
6
See [1]. In addition, the values of TON and NPI when the Dialling number string is null (zero
length) are, respectively, ‘000’ and ‘0000’.
7
8.2 Alpha identifier
8
See [1].
9
8.3 Sub-Address
5
10
See [1].
11
8.4 Capability Configuration Parameters
13
Cards operating according to this specification shall not use this parameter. If a command is
received with this parameter, this parameter shall be ignored.
14
8.5 Reserved
15
8.6 Command details
16
See [1].
17
8.7 Device identities
18
See [1].
19
8.8 Duration
20
See [1].
21
8.9 Item
22
See [1].
23
8.10 Item identifier
24
See [1].
25
8.11 Response length
26
See [1].
12
29
3GPP2 C.S0035-B v2.0
1
8.12 Result
5
See [1], except that result codes ‘14’, ‘37’ and ‘39’ have the meanings from [20]. Also, the
"additional information" for "ME currently unable to process command" can be 08 = "ME
currently busy on USSD transaction" (section 8.12.2 of [20]). Also, section 8.12.7 of [20] should
be supported.
6
8.13 Reserved
7
8.14 Reserved
8
8.15 Text string
9
See [1].
2
3
4
10
8.16 Tone
11
See [1].
12
8.17 USSD string
13
See section 8.17 of [20].
14
8.18 File List
15
See [1].
30
3GPP2 C.S0035-B v2.0
1
2
3
8.19 Location Information
The following data structure applies when the current Access Technology is ‘06’ (cdma2000 1x),
‘07’ (cdma2000 HRPD) or ‘09’ (eHRPD):
4
Byte(s)
1
Description
Location information tag (‘13’ or ‘93’ [16])
2
Length
1
Length = ‘0F’, ‘13’, ‘2A’ or ‘2E’
1
MCC (Note 1)
2
IMSI_11_12 (Note 1)
1
6–7
SID (Note 1)
2
8–9
NID (Note 1)
2
10 – 11
BASE_ID (Note 1)
2
12 – 14
BASE_LAT (Note 1)
3
15 – 17
BASE_LONG (Note 1)
3
18 – 20
Height (Note 2)
3
Horizontal Uncertainty (Note 2)
1
HRPD Country Code (Note 3)
2
3–4
5
21
A – A+1
A+2 – A+17
Sector ID (Note 3)
16
A+18 – A+20
CDMA Channel (Note 3)
3
A+21 – A+26
Latitude and Longitude (Note 3)
6
5
6
7
8
Notes:
1.
2.
9
10
11
12
13
14
15
3.
If not available use ‘FF’ bytes as filler.
If both Height and Horizontal Uncertainty are unavailable all bytes marked with
this note shall be omitted. If only one parameter is unavailable use ‘FF’ bytes as
filler.
Do not include these bytes if the current Access Technology is ‘06’. If current
Access Technology is ‘07’ or ‘09’ and the information for a parameter is not
available use ‘FF’ bytes as filler. The value of A is either 18 if bytes associated
with Note 2 are not included or 22 if they are included.
Bytes 3 – 4 (MCC):
b8 b7 B6 b5 b4 b3 b2 b1
LSB of MCC [18]
MCC bits in ascending order
16
b8 b7 b6 b5 b4 b3 b2 b1
Next MSB of MCC
MSB of MCC
RFU
17
31
3GPP2 C.S0035-B v2.0
1
Byte 5 (IMSI_11_12):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of IMSI_11_12 [18]
Middle bits of IMSI_11_12 in ascending order
MSB of IMSI_11_12
RFU
2
3
Bytes 6 – 7 (SID):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of SID [18]
SID bits in ascending order
4
b8 b7 b6 b5 b4 b3 b2 b1
SID bits in ascending order
MSB of SID
RFU
5
6
Bytes 8 – 9 (NID):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of NID [18]
NID bits in ascending order
7
b8 b7 b6 b5 b4 b3 b2 b1
NID bits in ascending order
MSB of NID
8
9
Bytes 10 – 11 (BASE_ID):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of BASE_ID [18]
BASE_ID bits in ascending order
10
b8 B7 b6 b5 b4 b3 b2 b1
BASE_ID bits in ascending order
MSB of BASE_ID
11
12
Bytes 12 – 14 (Base Station Latitude):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of BASE_LAT [18]
BASE_LAT bits in ascending order
13
b8 b7 b6 b5 b4 b3 b2 b1
BASE_LAT bits in ascending order
14
32
3GPP2 C.S0035-B v2.0
b8 b7 b6 b5 b4 b3 b2 b1
BASE_LAT bits in ascending order
MSB of BASE_LAT
RFU
1
2
Bytes 15 – 17 (Base Station Longitude):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of BASE_LONG [18]
BASE_LONG bits in ascending order
3
b8 b7 b6 b5 b4 b3 b2 b1
BASE_LONG bits in ascending order
4
b8 b7 b6 b5 b4 b3 b2 b1
BASE_LONG bits in ascending order
MSB of BASE_LONG
RFU
5
Bytes 18 – 20 (Height):
b8 b7 b6 b5 b4 b3 b2 b1
LOC_UNC_V [18]
RFU
6
b8 b7 b6 b5 b4 b3 b2 b1
LSB of HEIGHT [18]
7
b8 b7 b6 b5 b4 b3 b2 b1
MSB of HEIGHT
RFU
8
Byte 21 (Horizontal Uncertainty):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of LOC_UNC_H [18]
MSB of LOC_UNC_H
RFU
9
Bytes A – A+1 (HRPD Country Code):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of CountryCode [17]
10
b8 b7 b6 b5 b4 b3 b2 b1
MSB of CountryCode
RFU
33
3GPP2 C.S0035-B v2.0
1
Bytes A+2 – A+17 (Sector ID):
b1
b128
2
LSB of SectorID (Byte 1) [17]
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
Byte 9
Byte 10
Byte 11
Byte 12
Byte 13
Byte 14
Byte 15
MSB of SectorID (Byte 16)
Bytes A+18 – A+20 (CDMA Channel):
b8 b7 b6 b5 b4 b3 b2 b1
SystemType of ReverseCDMAChannel [17]
3
b8 b7 b6 b5 b4 b3 b2 b1
ReverseBandClass of ReverseCDMAChannel
Bit 1 (LSB) of ReverseChannelNumber of
ReverseCDMAChannel
4
b8 b7 b6 b5 b4 b3 b2 b1
Bit 11 (MSB) of ReverseChannelNumber of
ReverseCDMAChannel
5
Bytes A+21 – A+26 (HRPD Latitude and Longitude):
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Latitude (Byte 1) [17]
6
b8 b7 b6 b5 b4 b3 b2 b1
Byte 2 of Latitude
7
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Latitude (Byte 3)
RFU
8
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Longitude (Byte 1) [17]
9
34
3GPP2 C.S0035-B v2.0
b8 b7 b6 b5 b4 b3 b2 b1
Byte 2 of Longitude
1
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Longitude (Byte 3)
RFU
2
3
8.20 Reserved
4
8.21 Help Request
5
See [1].
6
8.22 Network Measurement Results
7
RFU.
8
8.23 Default Text
9
See [1].
10
8.24 Items Next Action Indicator
11
See [1].
12
8.25 Event list
13
See [1].
14
8.26 Cause
15
See [1].
18
There are no cause values defined in current [18] which can be used as Cause data object as
defined in [1] for the Call Disconnected event so this data object is reserved for future use and
should not be included in the Call Disconnected event download.
19
8.27 Location Status
20
See [1], except that “Limited Service” is not supported.
16
17
35
3GPP2 C.S0035-B v2.0
1
8.28 Transaction Identifier
Byte(s)
Description
Length
1
Transaction identifier tag (‘1C’ or ‘9C’ [16])
2
Length (X) of bytes following
1
Transaction identifier list
X
3 to X+2
1
2
3
4
-
Transaction identifier list:
Contents:
-
5
6
7
8
9
A list of transaction identifiers, of variable length. Each byte in the list defines a
transaction identifier and the transaction identifier is equivalent to CON_REF as
defined in [18]. Each transaction identifier shall not appear more than once within
the list;
Coding:
10
-
Length of bytes following: if CON_REF is not present in the corresponding messages
as defined in 7.5 (for example, if P_REV_IN_USE is less than 7, there is no CON_REF
defined, and for some cases, CON_REF is not included in messages even in higher
P_REV_IN_USE), the length shall be 0 and the Transaction Identifier list field shall
be omitted.
-
Each byte in the transaction identifier list shall contain the value of a CON_REF in
signalling messages as defined in [18].
11
12
13
14
15
16
17
8.29 Reserved
18
8.30 Call control requested action
19
See [1].
20
8.31 Icon Identifier
21
See [1].
22
8.32 Item Icon Identifier list
23
See [1].
24
8.33 Card reader status
25
See [1].
26
8.34 Card ATR
27
See [1].
36
3GPP2 C.S0035-B v2.0
1
8.35 C-APDU
2
See [1].
3
8.36 R-APDU
4
See [1].
5
8.37 Timer identifier
6
See [1].
7
8.38 Timer value
8
See [1].
9
8.39 Date-Time
10
See [1].
11
8.40 AT Command
12
See [1].
13
8.41 AT Response
14
See [1].
15
8.42 Reserved
16
8.43 Immediate response
17
See [1].
18
8.44 DTMF string
19
See [1].
20
8.45 Language
21
See [1].
22
8.46 Reserved
23
8.47 Browser Identity
24
See [1].
37
3GPP2 C.S0035-B v2.0
1
8.48 URL
2
See [1].
3
8.49 Bearer
4
See [1]. Additionally, bearer ‘02’ = USSD is also allowed.
5
8.50 Provisioning File Reference
6
See [1].
7
8.51 Browser Termination Cause
8
See [1].
9
8.52 Bearer description
10
See [1].
11
8.53 Channel data
12
See [1].
13
8.54 Channel data length
14
See [1].
15
8.55 Buffer size
16
See [1].
17
8.56 Channel status
18
See [1].
19
8.57 Card reader identifier
20
See [1].
21
8.58 Other Address
22
See [1].
23
8.59 UICC/ME interface transport level
24
See [1].
38
3GPP2 C.S0035-B v2.0
1
8.60 AID
2
See [1].
3
8.61 Access Technology
4
See [1].
5
8.62 Display parameters
6
See [1].
7
8.63 Service Record
8
See [1].
9
8.64 Device Filter
10
See [1].
11
8.65 Service Search
12
See [1].
13
8.66 Attribute Information
14
See [1].
15
8.67 Service Availability
16
See [1].
17
8.68 Remote Entity Address
18
See [1].
19
8.69 ESN
20
Byte(s)
Description
Length
1
See section 9.5 (3GPP2 Tag Values)
1
2
Length = ‘04’
1
3 to 6
ESN_ME
4
The ESN_ME is coded as the ElectronicSerialNumber parameter in [8].
39
3GPP2 C.S0035-B v2.0
1
8.70 Network access name
2
An APN, as defined in [22].
3
8.71 CDMA SMS TPDU
Byte(s)
Description
Length
1
See section 9.5 (3GPP2 Tag Values)
1
2 to (Y-1)+2
Length (X)
Y
(Y-1)+3 to
(Y-1)+X+2
CDMA SMS TPDU
X
4
5
The CDMA SMS TPDU is formatted as described in [3].
6
A CDMA SMS TPDU will have the following structure:
7
Byte(s)
(Y-1)+3
Description
SMS_MSG_TYPE
Length
1
One or more occurrences of the following segment:
(Y-1)+4
PARAMETER_ID
1
(Y-1)+5
PARAMETER_LEN (Z)
1
(Y-1)+6 to
(Y-1)+Z+5
Parameter Data
Z
11
Note that the definition of CDMA SMS TPDU does allow multiple occurrences of the segment,
which consists of “PARAMETER_ID”, “PARAMETER_LEN” and “Parameter Data” as described in
[3]. The number of repetitions of the aforementioned segment is determined by the Length and
PARAMETER_LEN of each segment.
12
8.72 Text Attribute
13
See [1].
14
8.73 Item Text Attribute List
15
See [1].
16
8.74 Reserved
17
8.75 Network Search Mode
18
See [1].
8
9
10
40
3GPP2 C.S0035-B v2.0
1
8.76 Battery State
2
See [1].
3
8.77 Browsing Status
4
See [1].
5
8.78 Frame Layout
6
See [1].
7
8.79 Frame Information
8
See [1].
9
8.80 Frame Identifier
10
See [1].
11
8.81 MEID
12
Byte(s)
Description
Length
1
See Section 9.5 (3GPP2 Tag Values)
1
2
Length = ‘08’
1
3 to 9
MEID_ME
7
10
RFU
1
The MEID is encoded as 14 BCD digits, without the check digit [i9].
13
8.82 Multimedia Message Reference
14
See [1].
15
8.83 Multimedia Message Identifier
16
See [1].
17
8.84 Multimedia Message Transfer Status
18
See [1].
19
8.85 MM Content Identifier
20
See [1].
41
3GPP2 C.S0035-B v2.0
1
8.86 Multimedia Message Notification
2
See [1].
3
8.87 Last Envelope
4
See [1].
5
8.88 Registry Application Data
6
See [1].
7
8.89 Activate Descriptor
8
See [1].
9
8.90 Broadcast Network Information
10
See [1].
11
8.91 Contactless state request
12
See [1].
13
8.92 Contactless functionality state
14
See [1].
15
8.93 Extended registry application data
16
See [1].
42
3GPP2 C.S0035-B v2.0
1
9 TAG VALUES
3
This clause specifies the tag values used to identify the BER-TLV and SIMPLE-TLV data objects
used in the present document, in addition to those defined in section 7.2 of [16].
4
9.1 BER-TLV tags in ME to UICC direction
5
See section 7.2 of [16] and section 9.1 of [20].
6
9.2 BER-TLV tags in UICC TO ME direction
7
See section 7.2 of [16] and section 9.2 of [20].
8
9.3 COMPREHENSION-TLV tags in both directions
9
See section 7.2 of [16] and section 9.3 of [20].
2
10
9.4 Type of Command and Next Action Indicator
11
See [1] and SEND USSD from section 9.4 of [20].
12
43
3GPP2 C.S0035-B v2.0
1
2
3
4
9.5 3GPP2 Tag Values
The value of the tag associated with a particular parameter may vary depending on the
command it is contained within. The meaning of a tag value may vary depending on the
command it is contained within.
Comprehension TLV Tag
Value4
CCAT Data Object
Command
‘46’/’C6’
ESN
TERMINAL RESPONSE (Provide
Local Information)
CDMA-SMS TPDU
SEND SHORT MESSAGE
CDMA-SMS TPDU
ENVELOPE (SMS-PP-DOWNLOAD)
CDMA-SMS TPDU
ENVELOPE (CELL BROADCAST
DOWNLOAD)
3GPP2 Tag 37 ‘61’/’E1’
Reserved
n/a
3GPP2 Tag 48 ‘6D’/’ED’
MEID
TERMINAL RESPONSE (Provide
Local Information)
Name
3GPP2 Tag
15
3GPP2 Tag 26 ‘48’/’C8’
5
6
4 Comprehension-TLV tags are 7 bits in length. Bit 8 (CR) can be ‘1’ or ‘0’. [16]
5 This is referred to as “ESN tag” in some versions of [16].
6 This is referred to as “CDMA-SMS-TPDU tag” in some versions of [16].
7 This is referred to as “Emergency Call tag” in some versions of [16].
8 This is referred to as “MEID tag” in some versions of [16].
44
3GPP2 C.S0035-B v2.0
1
2
3
4
10 ALLOWED TYPE OF COMMAND AND DEVICE IDENTITY
COMBINATIONS
See [1]. In addition, “MO SHORT MESSAGE CONTROL” and “SEND USSD” are defined in
section 10 of [20].
45
3GPP2 C.S0035-B v2.0
1
11 SECURITY REQUIREMENTS
2
Void.
3
46
3GPP2 C.S0035-B v2.0
1
12 CDMA2000 SPECIFIC SIMPLE TLV DATA OBJECTS
2
Void.
47
3GPP2 C.S0035-B v2.0
2
ANNEX A (NORMATIVE): SUPPORT OF CCAT BY MOBILE
EQUIPMENT
3
See Annex A of [1]. The definition of class ‘p’ is included from Annex A of [20].
1
4
5
6
Support of CCAT is optional for Mobile Equipment. However, if an ME states conformance with
a CCAT release, it is mandatory for the ME to support all functions of that release. Optionally,
the letter classes defined in [1] may be used.
7
48
3GPP2 C.S0035-B v2.0
2
ANNEX B (INFORMATIVE): EXAMPLE OF DISPLAY TEXT
PROACTIVE UICC COMMAND
3
See [1].
1
49
3GPP2 C.S0035-B v2.0
1
ANNEX C (NORMATIVE): STRUCTURE OF CCAT COMMUNICATIONS
2
See [1].
50
3GPP2 C.S0035-B v2.0
2
ANNEX D (INFORMATIVE): ME DISPLAY IN PROACTIVE UICC
SESSION
3
See [1].
1
51
3GPP2 C.S0035-B v2.0
2
ANNEX E (INFORMATIVE): HELP INFORMATION FEATURE
PROCESSING
3
See [1].
1
52
3GPP2 C.S0035-B v2.0
1
ANNEX F
2
See [1].
(INFORMATIVE): MONITORING OF EVENTS
53
3GPP2 C.S0035-B v2.0
2
ANNEX G (NORMATIVE): SUPPORT OF MULTIPLE CARD
OPERATION
3
See [1].
1
54
3GPP2 C.S0035-B v2.0
2
ANNEX H (INFORMATIVE): MULTIPLE CARD PROACTIVE
COMMAND EXAMPLES
3
See [1].
1
55
3GPP2 C.S0035-B v2.0
1
ANNEX I
RESERVED.
56
3GPP2 C.S0035-B v2.0
1
ANNEX J (INFORMATIVE): WAP TERMINOLOGY
2
See [1].
57
3GPP2 C.S0035-B v2.0
2
ANNEX K (INFORMATIVE): USE OF CCAT BEARER INDEPENDENT
PROTOCOL FOR LOCAL LINKS BLUETOOTH CASE
3
See [1].
1
58
3GPP2 C.S0035-B v2.0
1
ANNEX L
2
3
(INFORMATIVE): BLUETOOTH SERVICE DISCOVERY
PROTOCOL
See [1].
59
3GPP2 C.S0035-B v2.0
2
ANNEX M (INFORMATIVE): USE OF CCAT BEARER INDEPENDENT
PROTOCOL FOR LOCAL LINKS, SERVER CASE
3
See [1].
1
60
3GPP2 C.S0035-B v2.0
2
ANNEX N (INFORMATIVE): USSD INFORMATION FLOW BETWEEN
THE NETWORK, THE ME AND THE UICC
3
See Annex N of [20].
1
61
3GPP2 C.S0035-B v2.0
1
2
ANNEX O (INFORMATIVE): CARD APPLICATION TOOLKIT
PROTOCOL TELESERVICE (CATPT)
4
The Card Application Toolkit Protocol Teleservice (CATPT) allows certain short messages to be
routed to the UICC for processing by CCAT, including short message responses.
5
The Teleservice ID for CATPT is 4103 [8] and the broadcast Service Category is 0x0020 [3].
3
6
7
8
9
10
The Short Message Service protocol messages used by CCAT are the “SMS Deliver Message” (to
the MS) and the “SMS Submit Message” (from the MS) [3]. The “SMS Deliver Message” or the
“SMS Submit Message” may be an SMS User Acknowledgment message.
If the ME receives an SMS Point-to-Point “SMS Deliver Message” with the CATPT Teleservice ID
it uses procedure 7.1.1 (SMS-PP Data Download).
12
When the ME receives an SMS Broadcast “SMS Deliver Message” with the Service Category for
CATPT it uses procedure 7.1.2 (Cell Broadcast Data Download).
13
The ME may initiate an SMS with CATPT by setting the Teleservice ID to CATPT (4103).
11
62
3GPP2 C.S0035-B v2.0
2
ANNEX P (NORMATIVE): SUPPORT OF USAT BY TERMINALS WITH
REDUCED FEATURE CAPABILITIES
3
See Annex P of [20].
1
4
63
3GPP2 C.S0035-B v2.0
1
2
3
4
5
ANNEX Q (INFORMATIVE): MULTIPLE RADIO ACCESS
TECHNOLOGY SUPPORT
The following data objects are defined to have a format that is “defined by the different access
technologies” in [1]. To aid in the interpretation of these data objects, they are listed below with
the recommended treatment.
6
Data Object
Treatment
Address TON (Type of number)
values
None. No values yet defined as access technology specific.
Address NPI values
Numbering plan indicator
None. No values yet defined as access technology specific.
Capability configuration
parameters
None. Redacted from this specification.
Location information
Length of ‘0F’, ‘13’, ‘2A’ or ‘2E’ indicates the definition from
this specification is included.
Network measurement results
None. RFU in this specification.
BC repeat indicator
None. Reserved in this specification.
Bearer description
None. The Bearer Type value could discriminate between
different formats of Bearer Parameters if necessary.
Network Access Name
None. All types are text strings and should be self-identifying
with a prefix.
MM Content Identifier
None. Multimedia messages are actually coded according to
defined access-technology-independent standards.
7
64