ARIB STD-T64-C.S0035-B v2.0. CDMA Card Application Toolkit

Transcription

1 ARIB STD-T-C.S00-B v.0 CDMA Card Application Toolkit (CCAT) Refer to "Industrial Property Rights (IPR)" in the preface of ARIB STD-T for Related Industrial Property Rights. Refer to "Notice" in the preface of ARIB STD-T for Copyrights

2 Original Specification This standard, ARIB STD-T-C.S00-B v.0, was prepared by GPP-WG of Association of Radio Industries and Businesses (ARIB) based upon the GPP specification, C.S00-B v.0. Modification to the original specification None. Notes None. 0

3 GPP C.S00-B v.0 May 0 CDMA Card Application Toolkit (CCAT) 0 GPP GPP 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 GPP Secretariat at secretariat@gpp.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

4 GPP C.S00-B v.0 REVISION HISTORY Revision Description of Changes Date C.S00-0 v.0 Initial Release October 00 C.S00-A v.0 First Revision March 00 C.S00-A v.0 Second Version of First Revision August 00 C.S00-A v.0 Third Version of First Revision August 0 C.S00-B v.0 Second Revision December 0 C.S00-B v.0 Second Version of Second Revision May 0

5 GPP C.S00-B v CONTENTS GENERAL.... Scope.... Document Conventions... References.... Normative References.... Informative References... Terms... Overview of CCAT.... Profile Download.... Proactive UICC.... Data download to UICC.... Menu selection.... Call control by network access application.... MO Short Message Control by UICC.... Event download.... Security.... Multiple card....0 Timer Expiration.... Bearer Independent Protocol.... Description of the access technology indicator mechanism.... Tag allocation guidelines... Profile download.... Procedure.... Structure and coding of TERMINAL PROFILE.... Definition of display parameters in Profile download... 0 Proactive UICC.... Introduction.... Identification of ME support.... General procedure.... Proactive UICC commands and procedures..... DISPLAY TEXT... i

6 GPP C.S00-B v GET INKEY..... GET INPUT..... MORE TIME..... PLAY TONE..... POLL INTERVAL..... REFRESH..... SET UP MENU..... SELECT ITEM SEND SHORT MESSAGE..... Reserved..... SEND USSD..... SET UP CALL..... POLLING OFF..... PROVIDE LOCAL INFORMATION..... SET UP EVENT LIST..... PERFORM CARD APDU..... POWER OFF CARD..... POWER ON CARD GET READER STATUS..... TIMER MANAGEMENT..... SET UP IDLE MODE TEXT..... RUN AT COMMAND..... SEND DTMF..... LANGUAGE NOTIFICATION..... LAUNCH BROWSER..... OPEN CHANNEL..... CLOSE CHANNEL..... RECEIVE DATA SEND DATA..... GET CHANNEL STATUS..... SERVICE SEARCH..... GET SERVICE INFORMATION... ii

7 GPP C.S00-B v DECLARE SERVICE.... Common elements in proactive UICC commands.... Structure of proactive UICC commands..... DISPLAY TEXT..... GET INKEY..... GET INPUT..... MORE TIME..... PLAY TONE..... POLL INTERVAL..... SET-UP MENU..... SELECT ITEM..... SEND SHORT MESSAGE Reserved..... SEND USSD..... SET UP CALL..... REFRESH..... POLLING OFF..... PROVIDE LOCAL INFORMATION..... SET UP EVENT LIST..... PERFORM CARD APDU..... POWER OFF CARD..... POWER ON CARD GET READER STATUS..... TIMER MANAGEMENT..... SET UP IDLE MODE TEXT..... RUN AT COMMAND..... SEND DTMF COMMAND..... LANGUAGE NOTIFICATION..... LAUNCH BROWSER..... OPEN CHANNEL..... CLOSE CHANNEL..... RECEIVE DATA... iii

8 GPP C.S00-B v SEND DATA..... GET CHANNEL STATUS..... SERVICE SEARCH..... GET SERVICE INFORMATION..... DECLARE SERVICE.... Command results.... Structure of TERMINAL RESPONSE..... Command details..... Device identities..... Result..... Duration..... Text string..... Item identifier..... Local information..... Call control requested action..... Result data object Card reader status..... Card ATR..... R-APDU..... Timer identifier..... Timer value..... AT Response..... Text string..... Channel data..... Channel status..... Channel data length Bearer description..... Buffer size..... Total Display Duration..... Service Availability..... Service Record.... Proactive UICC session and ME display interaction... iv

9 GPP C.S00-B v Handling of unknown, unforeseen and erroneous messages Proactive commands versus possible terminal response... 0 ENVELOPE Commands.... Data Download to UICC..... SMS-PP Data Download Procedure Structure of ENVELOPE (SMS-PP Data Download)..... Cell Broadcast Data Download Structure of ENVELOPE (CELL BROADCAST DOWNLOAD).... Menu Selection.... Call Control..... Call Control by UICC Procedure for mobile originated calls Procedure for USSD Indication to be given to the user Interaction with Fixed Dialling Number (FDN) Support of Barred Dialling Number (BDN) service Structure of ENVELOPE (CALL CONTROL) MO Short Message Control by UICC Description Structure of ENVELOPE (MO SHORT MESSAGE CONTROL) Indication to be given to the user Interaction with Fixed Dialing Number (FDN).... Timer Expiration.... Event download.... USSD Data Download... SIMPLE-TLV generic data objects.... Address.... Alpha identifier.... Sub-Address.... Capability Configuration Parameters.... Reserved... v

10 GPP C.S00-B v Command details.... Device identities.... Duration.... Item....0 Item identifier.... Response length.... Result Reserved Reserved Text string Tone USSD string File List Location Information....0 Reserved.... Help Request.... Network Measurement Results.... Default Text.... Items Next Action Indicator.... Event list.... Cause.... Location Status.... Transaction Identifier.... Reserved....0 Call control requested action.... Icon Identifier.... Item Icon Identifier list.... Card reader status.... Card ATR.... C-APDU.... R-APDU.... Timer identifier... vi

11 GPP C.S00-B v Timer value.... Date-Time....0 AT Command.... AT Response.... Reserved.... Immediate response.... DTMF string.... Language.... Reserved.... Browser Identity.... URL.... Bearer....0 Provisioning File Reference.... Browser Termination Cause.... Bearer description.... Channel data.... Channel data length.... Buffer size.... Channel status.... Card reader identifier.... Other Address.... UICC/ME interface transport level....0 AID.... Access Technology.... Display parameters.... Service Record.... Device Filter.... Service Search.... Attribute Information.... Service Availability.... Remote Entity Address.... ESN... vii

12 GPP C.S00-B v Network access name CDMA SMS TPDU Text Attribute Item Text Attribute List Reserved Network Search Mode Battery State.... Browsing Status.... Frame Layout.... Frame Information....0 Frame Identifier.... MEID.... Multimedia Message Reference.... Multimedia Message Identifier.... Multimedia Message Transfer Status.... MM Content Identifier.... Multimedia Message Notification.... Last Envelope.... Registry Application Data.... Activate Descriptor....0 Broadcast Network Information.... Contactless state request.... Contactless functionality state.... Extended registry application data... Tag values.... BER-TLV tags in ME to UICC direction.... BER-TLV tags in UICC TO ME direction.... COMPREHENSION-TLV tags in both directions.... Type of Command and Next Action Indicator.... GPP Tag Values... 0 Allowed Type of command and Device identity combinations... Security requirements... viii

13 GPP C.S00-B v.0 CDMA000 Specific Simple TLV Data Objects... ix

14 GPP C.S00-B v.0 0 FOREWORD This foreword is not part of this document. This document contains the requirements for CDMA Card Application Toolkit (CCAT). It extends the Card Application Toolkit [] to enable operation in cdma000. CCAT is a set of commands and procedures for use during the network operation phase of CDMA, in addition to those defined in []. Specifying the interface is to ensure interoperability between a UICC (R- UIM 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 []. The composite CCAT specification is comprised of [] and this ancillary document. [ ] indicates the corresponding document to be cross referenced cdma000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of GPP. Geographically (and as of the date of publication), cdma000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. x

15 GPP C.S00-B v GENERAL. Scope 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 [], the UICC refers to an ICC that supports a Network Access Application. All references to UICC in [] 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 [], 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 []. Specifying the interface is needed to ensure interoperability between a UICC and an ME independently of the respective manufacturers and operators. The present document defines for CDMA technology: - The commands; - The application protocol; - The mandatory requirements on the UICC and ME for each procedure. 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 []. The composite CCAT specification is comprised of [] 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 [] refers to the Mobile Equipment (ME). Within the context of the present document, the term "NAA" used in [] refers to the CDMA Card Application Toolkit (CCAT).. Document Conventions 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

16 GPP C.S00-B v.0 and cannot are used for statements of possibility and capability, whether material, physical or causal.

17 GPP C.S00-B v REFERENCES. Normative References 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.. ETSI TS 0, Smart Cards; Card Application Toolkit.. ANSI/INCITS -(R ), Information Processing Coded Character Sets -bit American National Standard Code for Information Interchange (-bit ASCII),.. C.S00-B v.0, Short Message Service (SMS) for Wideband Spread Spectrum Systems- Release B, 00.. Void.. GPP TS.00, Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN).. ITU-T T.0, International reference alphabet (IRA) (Formerly International Alphabet n or IA) information technology bit Coded Characters Set for Information Interchange.. ETSI TS 0, Smart Cards; UICC ME Interface; Physical and Logical Characteristics, Release, 00.. GPP X.S000-E. Mobile Application Part (MAP) Reserved. 0. ITU-T Recommendation E., Identification Plan for Land Mobile Stations, 00.. ETSI TS 0, Digital Cellular Telecommunications System (Phase +) (GSM); Universal Mobile Telecommunications System (UMTS); Alphabets and Language-Specific Information, GPP TS.0 Release 0, 0.. ETSI TS 0, International Mobile Equipment Identities (IMEI), GPP TS.0 Release 0, 0.. C.S00-D v.0, Removable User Identity Module for Spread Spectrum Systems, 00.. Void.. GPP C.S00-0, UICC-Terminal interface Physical and Logical characteristics for cdma000 Spread Spectrum Systems, 00.. ETSI TS 0 0 Smart Cards; ETSI numbering system for telecommunication application providers.. C.S00-B v.0, cdma000 High Rate Packet Data Air Interface Specification, 00.. GPP C.S000-E v.0, Upper Layer (Layer ) Signaling Standard for cdma000 Spread Spectrum Systems, 0.. GPP TS.0 v..0, Specification of the SIM Application Toolkit for the Subscriber Identity Module Mobile Equipment (SIM ME) interface, GPP TS., Universal Subscriber Identity Module (USIM) Application Toolkit (USAT).. GPP C.S00-B v.0. cdma000 Application on UICC for Spread Spectrum Systems, 0.. GPP X.S00, E-UTRAN - ehrpd Connectivity and Interworking: Core Network Aspects.

18 GPP C.S00-B v.0. GPP C.S00-0 v.0. Unstructured Supplementary Service Data (USSD) Service Options for Spread Spectrum Systems: Service Options and. 0.. Informative References 0 i i i i GPP C.S000-E v.0, Introduction to cdma000 Standards for Spread Spectrum Systems, 0. GPP C.S000-E v.0, Physical Layer Standard for cdma000 Spread Spectrum Systems, 0. GPP C.S000-E v.0, Medium Access Control (MAC) Standard for cdma000 Spread Spectrum Systems, 0. GPP C.S000-E v.0, Signaling Link Access Control (LAC) Standard for cdma000 Spread Spectrum Systems, 0. i Replaced by normative reference. 0 i i i i GPP C.S000-D v.0, Analog Signaling Standard for cdma000 Spread Spectrum Systems, 00. TIA/EIA/IS--B, Mobile Station Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Standards, December. C.R00-H, Administration of Parameter Value Assignments for cdma000 Spread Spectrum Standards, July 0. GPP S.R00-A v.0, G Mobile Equipment Identifier (MEID) - Stage, November, 00. i0 Replaced by normative reference.

19 GPP C.S00-B v 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). Card Application Toolkit. A set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. CAT. See Card Application Toolkit. CCAT. See CDMA Card Application Toolkit. CDMA Card Application Toolkit. A set of commands and procedures for use during the network operation phase of CDMA. CSIM. cdma000 Subscriber Identity Module. ECC. Emergency Call Code from EF ECC. ehrpd. Evolved HRPD. Global Emergency Call Indicator (GECO). Used by the Mobile Station to identify an Emergency Call as specified in []. ICC. Integrated Circuit(s) Card. IMEI. International Mobile Equipment Identity. IMSI. See International Mobile Subscriber Identity. International Mobile Equipment Identity. A method of identifying a mobile equipment in the land mobile service as specified in [0]. International Mobile Subscriber Identity. A method of identifying a subscriber in the land mobile service as specified in []. M/O. Mandatory / Optional. MCC. Mobile Country Code. ME. Mobile Equipment. MEID. Mobile Equipment Identifier. Min. Minimum. MNC. Mobile Network Code. MSC. Mobile Switching Center. MT. Mobile terminated. Network Identification. A number that uniquely identifies a network within a wireless system. See also System Identification. NID. See Network Identification. NITZ. Network Identity and Time Zone.

20 GPP C.S00-B v OTAF. See Over-the-Air Provisioning Function. OTASP. See Over-the-Air Service Provisioning. Over-the-Air Provisioning Function. A configuration of network equipment that controls OTASP functionality messaging protocols. Over-the-Air Service Provisioning. A process of provisioning mobile station operational parameters over the air interface. RFU. Reserved for Future Use. R-UIM. Removable User Identity Module. SID. See System Identification. 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 []). SMS. Short Message Service. SMS-MO. Short Message Service Mobile Originated. SMS-MT. Short Message Service Mobile Terminated. SW/SW. Status Word /Status Word. System Identification. A number uniquely identifying a wireless system. Terminal Response. This function is used to transfer from the ME to the UICC the response to a previously fetched proactive command. TLV. Tag Length Value. TPDU. See Transfer Protocol Data Unit. 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 [].

21 GPP C.S00-B v 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. The following mechanisms have been defined. These mechanisms are dependent upon the commands and protocols relevant to CCAT in [].. Profile Download. Proactive UICC Also, sending a USSD string [0].. Data download to UICC. Menu selection. Call control by network access application This also applies to USSD operations [0].. MO Short Message Control by UICC See [0].. Event download. Security. Multiple card.0 Timer Expiration

22 GPP C.S00-B v.0. Bearer Independent Protocol. Description of the access technology indicator mechanism. Tag allocation guidelines

23 GPP C.S00-B v.0 0 PROFILE DOWNLOAD. Procedure 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 []. 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 [].. Structure and coding of TERMINAL PROFILE Direction: ME to UICC. The command header is the one specified for TERMINAL PROFILE in []. Command parameters/data: Description Clause M/O/C Length Profile - M lgth 0 Profile: - Contents: The list of CCAT facilities that are supported by the ME. - Coding ( bit is used to code each facility): bit = : facility supported by ME. bit = 0: facility not supported by ME. 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 []. The following bits listed as Reserved for GPP in some versions of [] are in use by this document with the following meanings taken from [0]: Byte, bit Call Control is supported. Byte, bit : Proactive UICC: SEND USSD. Byte, bit : USSD Data download and application mode. Twentieth byte (Reserved for GPP C.S00 CCAT): b b b b b b b b SEND CDMA SMS CDMA SMS-PP data download CDMA SMS BROADCAST data download CDMA USSD support (Note ) CDMA MO SMS Control support (Note ) RFU

24 GPP C.S00-B v.0 Notes:. This bit indicates that the USSD control bits (Byte bit, Byte bit and Byte bit ) should be considered when the ME is operating in a CDMA mode (Access Technology 0, 0, 0 or 0 ). Otherwise they should be treated as if they were set to 0 in a CDMA mode.. This bit indicates that Mobile Originated SMS Control is supported when the ME is operating in a CDMA mode (Access Technology 0, 0, 0 or 0 ). This bit is independent of byte, bit, which indicates support for other technologies. 0 Response parameters/data: - None.. Definition of display parameters in Profile download 0

25 GPP C.S00-B v PROACTIVE UICC. Introduction The list of commands also includes SEND USSD from [0].. Identification of ME support. General procedure. Proactive UICC commands and procedures.. DISPLAY TEXT.. GET INKEY.. GET INPUT.. MORE TIME.. PLAY TONE NOTE: Some supervisory tones are optional for mobile equipment (see [])... POLL INTERVAL.. REFRESH.. SET UP MENU.. SELECT ITEM

26 GPP C.S00-B v SEND SHORT MESSAGE Two types are defined: - 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. Where packing by the ME is not required, the CDMA SMS TPDU shall be coded as defined in []. The Command details data object shall indicate, Packing is not required. Where packing by the ME is required, the UICC shall use the -bit ASCII coding as defined in [], IA coding as defined in [] or the GSM -bit default alphabet as defined in []. The UICC shall place the user data into -bit octets with bit 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 bit fields as described in section.. of [] 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 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. 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 [] 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.

27 GPP C.S00-B v 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... Reserved.. SEND USSD See section.. of [0]... 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.. of [], 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 EF ECC or. If the ME supports EF CSIM_ST Service n (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 EF OCI... POLLING OFF.. PROVIDE LOCAL INFORMATION This command requests the ME to send current local information to the UICC. At present, this information is restricted to: - Location information; - The ESN or MEID of the ME; - The current date, time and time zone; - The current ME language setting; - The current access technology. 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.

28 GPP C.S00-B v SET UP EVENT LIST.. PERFORM CARD APDU.. POWER OFF CARD.. POWER ON CARD..0 GET READER STATUS.. TIMER MANAGEMENT.. SET UP IDLE MODE TEXT.. RUN AT COMMAND.. SEND DTMF.. LANGUAGE NOTIFICATION.. LAUNCH BROWSER.. OPEN CHANNEL.. CLOSE CHANNEL.. RECEIVE DATA

29 GPP C.S00-B v SEND DATA.. GET CHANNEL STATUS.. SERVICE SEARCH.. GET SERVICE INFORMATION.. DECLARE SERVICE. Common elements in proactive UICC commands. Structure of proactive UICC commands The general structure of proactive UICC commands using TLV objects is described in annex C... DISPLAY TEXT.. GET INKEY.. GET INPUT.. MORE TIME.. PLAY TONE.. POLL INTERVAL.. SET-UP MENU

30 GPP C.S00-B v SELECT ITEM.. SEND SHORT MESSAGE..0 Reserved.. SEND USSD This command is defined in [0]... SET UP CALL This command is defined in []... REFRESH.. POLLING OFF.. PROVIDE LOCAL INFORMATION.. SET UP EVENT LIST.. PERFORM CARD APDU.. POWER OFF CARD.. POWER ON CARD..0 GET READER STATUS.. TIMER MANAGEMENT

31 GPP C.S00-B v SET UP IDLE MODE TEXT.. RUN AT COMMAND.. SEND DTMF COMMAND.. LANGUAGE NOTIFICATION.. LAUNCH BROWSER.. OPEN CHANNEL.. CLOSE CHANNEL.. RECEIVE DATA..0 SEND DATA.. GET CHANNEL STATUS.. SERVICE SEARCH.. GET SERVICE INFORMATION.. DECLARE SERVICE

32 GPP C.S00-B v Command results In addition, the temporary problem, ME currently busy on USSD operation, and the permanent problem, USSD Return Error, are included from [0].. Structure of TERMINAL RESPONSE Also see [0] for structure of TERMINAL RESPONSE related to SEND USSD... Command details.. Device identities.. Result.. Duration.. Text string Also see [0] for use with a SEND USSD command... Item identifier.. Local information.. Call control requested action Also see [0] for use with a SEND USSD command... Result data object Also see [0] for use with a SEND USSD command...0 Card reader status.. Card ATR

33 GPP C.S00-B v R-APDU.. Timer identifier.. Timer value.. AT Response.. Text string Also see [0] for use with a SEND USSD command... Channel data.. Channel status.. Channel data length..0 Bearer description.. Buffer size.. Total Display Duration.. Service Availability.. Service Record. Proactive UICC session and ME display interaction

34 GPP C.S00-B v.0.0 Handling of unknown, unforeseen and erroneous messages. Proactive commands versus possible terminal response Also see [0] for TERMINAL RESPONSE values associated with SEND USSD Proactive Command. 0

35 GPP C.S00-B v ENVELOPE COMMANDS. Data Download to UICC.. SMS-PP Data Download... Procedure When the ME receives a Short Message with Teleservice Identifier [] set to 0 ( Card Application Toolkit Protocol Teleservice (CATPT) []) then the ME shall follow the procedure below. If the ME does not support CCAT or the service Data Download via SMS-PP is neither allocated nor activated in EF CST nor available in EF CSIM_ST, then the ME shall store the message in EF SMS under DFCDMA. Otherwise: - The ME shall pass the message transparently to the UICC using the ENVELOPE (SMS-PP Data Download) command as defined in section... - The ME shall not display the message, or alert the user of a short message waiting. - The ME shall wait for a response from the UICC. - If the UICC responds with 00 the ME may retry the command (otherwise it will respond with a cause code value as described below in Table ). - Otherwise, when the ME receives a response from the UICC it shall send an SMS User Acknowledgement message to the network with the User Data and User Response Code fields included as described below: o If the Status Words received from the UICC indicate that the ME should use GET RESPONSE to retrieve response data (i.e. XX, XX, XX [0], E XX or F XX []), 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 00 (User Acknowledgment).[]

36 GPP C.S00-B v.0 o If one of the following Status Word pairs is received from the UICC the specified SMS_CauseCode value [] shall be placed in the User Response Code field: Status Words SMS_CauseCode value [] 00 [] Destination Busy E XX [] XX Other Terminal problem XX 0 o If the ME receives any other Status Words from the UICC the User Response Code shall be omitted.... Structure of ENVELOPE (SMS-PP Data Download) Direction: ME to UICC The command header is specified in []. Command parameters/data. Description Section M/O Min Length SMS-PP download tag. of [] M Y Length (A+B) - M Y or Device identities. of [] M Y A CDMA SMS TPDU. M Y B - Device identities: the ME shall set the device identities to: Source: Network; Destination: UICC. Response parameters/data. If the Status Words received from the UICC (e.g. XX, XX, XX [] or F XX []) indicate that the ME should use GET RESPONSE to retrieve response data then the following data is returned: Byte(s) Description Length -X (X ) UICC Acknowledgment X 0 The Card Acknowledgment parameter is used as the CHARi octets of the User Data parameter in the SMS User Acknowledgment message by the ME.

37 GPP C.S00-B v.0.. Cell Broadcast Data Download If the ME receives a Broadcast SMS message with the Service Category of 0x000 (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 EF CST and not available in EF CSIM_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. 0 The ME shall identify new Broadcast SMS messages by their message identifier and service category.... Structure of ENVELOPE (CELL BROADCAST DOWNLOAD) Direction: ME to UICC. The command header is specified in []. Command parameters/data: Description Section M/O Min Length Cell Broadcast download tag ( D ). of [] M Y Length (A+B) - M Y or Device identities. of [] M Y A CDMA SMS TPDU. M Y B - Device identities: the ME shall set the device identities to: source: Network; destination: UICC. 0 0 Response parameters/data: None for this type of ENVELOPE command.. Menu Selection. Call Control.. Call Control by UICC... Procedure for mobile originated calls This procedure is defined in [] with the following exception: - If the ENVELOPE (CALL CONTROL) response contains an Address parameter containing the digits or a number stored in EF ECC, the ME shall initiate an emergency call. - Supplementary services (other than USSD) are not supported. - The service call control in the USIM Service Table should be interpreted as R-UIM service n (Call Control) or CSIM service n (Call Control for Voice Services).

38 GPP C.S00-B v.0 The ME shall follow the call set-up procedure defined in [] or the USSD operation procedure defined in [].... ReservedProcedure for USSD See section... of [0], except that: - Supplementary Service (SS) operations other than USSD are not supported. - The service call control in the USIM Service Table should be interpreted as R-UIM service n (Call Control) or CSIM service n (Call Control for Voice Services). 0 The ME shall follow the call set-up procedure defined in [] or the USSD operation procedure defined in [].... Indication to be given to the user See []... Interaction with Fixed Dialling Number (FDN) See []... Support of Barred Dialling Number (BDN) service See []... Structure of ENVELOPE (CALL CONTROL) This command is defined in [0]. except that the Command parameters/data table is: Description Clause M/O/C Min Length Call control tag. M Y Length (A+B+C+D) - M Y or Device identities. M Y A Address or USSD string. or. M Y B Subaddress. O N C Location information. M N D 0 Location information: This data object contains the identification (MCC, IMSI, SID, NID etc. as defined in section.) of the current serving cell of the ME. Also, the Response parameters/data table is as follows: Description Clause M/O/C Min Length Call control result - M Y Length (A+B+C) - M Y or Address or USSD string.,. O N A Subaddress. O N B pha identifier. O N C - Supplementary services (other than USSD) are not supported. - Parameters related to PDP context activation or EPS PDN connection activation including any comments related to such context activation shall be ignored.

39 GPP C.S00-B v Parameters related to Capability configuration and BC repeat indicator shall be ignored. - The service call control in the USIM Service Table should be interpreted as R-UIM service n (Call Control) or CSIM service n (Call Control for Voice Services).... MO Short Message Control by UICC... Description If the service "MO Short Message Control" is available in the R-UIM or CSIM Service Table (see [] and []), then the ME shall follow the procedure below: - 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 '0 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 ' 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. The ME shall then follow the MO Short Message procedure defined in []. 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".... Structure of ENVELOPE (MO SHORT MESSAGE CONTROL) Direction: ME to UICC. The command header is specified in [].

40 GPP C.S00-B v.0 Command parameters/data. Description Clause M/O/C Min Length MO Short Message control tag. M Y Length A - M Y or Device identities. M Y Address. M Y K Address. M Y O Location Information. C Y Device identities: The ME shall set the device identities to: source: ME; destination: UICC. 0 Address : Contains the address of the MC to which the ME is proposing to send the short message. Address : Contains the Destination Address to which the ME is proposing to send the short message. Location Information: Include for all GPP 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 SW/SW = '0 00'. If the UICC does not provide any response data, then this shall have the same meaning as "allowed, no modification". Description Clause M/O/C Min Length MO short message control result - M Y Length - M Y or Address. C N Address. C N Alpha identifier. O N 0 MO Short Message control result: Contents: The command that the UICC gives to the ME concerning whether to allow, bar or modify the proposed short message; Coding:

41 GPP C.S00-B v '00' = Allowed, no modification; - '0' = Not allowed; - '0' = Allowed with modifications. Address : Shall be included if and only if the MO Short Message control result is set to Allowed with modifications. Address : Shall be included if and only if the MO Short Message control result is set to Allowed with modifications. 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 Indication to be given to the user 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... relative to call control by UICC.... Interaction with Fixed Dialing Number (FDN) It is permissible for the Fixed Dialing Number service to be enabled (see [] and []) 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...), where the number in the procedure refers to the SMS destination address. 0. Timer Expiration. Event download Regarding all the call events, the following equivalences shall apply: - 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 [] (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 [] (possible message: Service Connect Message, General Handoff Direction Message, Universal Handoff Direction Message or Call Assignment Message)].

42 GPP C.S00-B v.0 - 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. Where events occur and the UICC responds with ' 00', the ME shall retry to deliver the event download messages to the UICC.. USSD Data Download See [0].

43 GPP C.S00-B v.0 SIMPLE-TLV GENERIC DATA OBJECTS The coding of these TLV objects is as described in [], except when stated otherwise in the present document.. Address In addition, the values of TON and NPI when the Dialling number string is null (zero length) are, respectively, 000 and Alpha identifier. Sub-Address 0. Capability Configuration Parameters Cards operating according to this specification shall not use this parameter. If a command is received with this parameter, this parameter shall be ignored.. Reserved. Command details. Device identities. Duration 0. Item.0 Item identifier. Response length

44 GPP C.S00-B v.0 0. Result See [], except that result codes, and have the meanings from [0]. Also, the "additional information" for "ME currently unable to process command" can be 0 = "ME currently busy on USSD transaction" (section.. of [0]). Also, section.. of [0] should be supported.. Reserved. Reserved. Text string. Tone. USSD string See section. of [0].. File List 0

45 GPP C.S00-B v.0. Location Information The following data structure applies when the current Access Technology is 0 (cdma000 x), 0 (cdma000 HRPD) or 0 (ehrpd): Byte(s) Description Length Location information tag ( or []) Length = 0F,, A or E MCC (Note ) IMSI (Note ) SID (Note ) NID (Note ) 0 BASE_ID (Note ) BASE_LAT (Note ) BASE_LONG (Note ) 0 Height (Note ) Horizontal Uncertainty (Note ) A A+ HRPD Country Code (Note ) A+ A+ Sector ID (Note ) A+ A+0 CDMA Channel (Note ) A+ A+ Latitude and Longitude (Note ) 0 Notes:. 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 0. If current Access Technology is 0 or 0 and the information for a parameter is not available use FF bytes as filler. The value of A is either if bytes associated with Note are not included or if they are included. Bytes (MCC): b b B b b b b b b b b b b b b b LSB of MCC [] MCC bits in ascending order Next MSB of MCC MSB of MCC RFU

46 GPP C.S00-B v.0 Byte (IMSI ): b b b b b b b b LSB of IMSI [] Middle bits of IMSI in ascending order MSB of IMSI RFU Bytes (SID): b b b b b b b b b b b b b b b b LSB of SID [] SID bits in ascending order SID bits in ascending order MSB of SID RFU 0 Bytes (NID): b b b b b b b b b b b b b b b b Bytes 0 (BASE_ID): b b b b b b b b b B b b b b b b LSB of NID [] NID bits in ascending order NID bits in ascending order MSB of NID LSB of BASE_ID [] BASE_ID bits in ascending order BASE_ID bits in ascending order MSB of BASE_ID Bytes (Base Station Latitude): b b b b b b b b b b b b b b b b LSB of BASE_LAT [] BASE_LAT bits in ascending order BASE_LAT bits in ascending order

47 GPP C.S00-B v.0 b b b b b b b b BASE_LAT bits in ascending order MSB of BASE_LAT RFU Bytes (Base Station Longitude): b b b b b b b b b b b b b b b b b b b b b b b b LSB of BASE_LONG [] BASE_LONG bits in ascending order BASE_LONG bits in ascending order BASE_LONG bits in ascending order MSB of BASE_LONG RFU Bytes 0 (Height): b b b b b b b b LOC_UNC_V [] RFU b b b b b b b b LSB of HEIGHT [] b b b b b b b b MSB of HEIGHT RFU Byte (Horizontal Uncertainty): b b b b b b b b LSB of LOC_UNC_H [] MSB of LOC_UNC_H RFU 0 Bytes A A+ (HRPD Country Code): b b b b b b b b b b b b b b b b LSB of CountryCode [] MSB of CountryCode RFU

48 GPP C.S00-B v.0 Bytes A+ A+ (Sector ID): b LSB of SectorID (Byte ) [] Byte Byte Byte Byte Byte Byte Byte Byte Byte 0 Byte Byte Byte Byte Byte b MSB of SectorID (Byte ) Bytes A+ A+0 (CDMA Channel): b b b b b b b b b b b b b b b b b b b b b b b b Bytes A+ A+ (HRPD Latitude and Longitude): b b b b b b b b b b b b b b b b b b b b b b b b SystemType of ReverseCDMAChannel [] ReverseBandClass of ReverseCDMAChannel Bit (LSB) of ReverseChannelNumber of ReverseCDMAChannel Bit (MSB) of ReverseChannelNumber of ReverseCDMAChannel LSB of Latitude (Byte ) [] Byte of Latitude MSB of Latitude (Byte ) RFU b b b b b b b b LSB of Longitude (Byte ) []

49 GPP C.S00-B v.0 b b b b b b b b b b b b b b b b Byte of Longitude MSB of Longitude (Byte ) RFU.0 Reserved. Help Request. Network Measurement Results RFU.. Default Text 0. Items Next Action Indicator. Event list. Cause There are no cause values defined in current [] which can be used as Cause data object as defined in [] 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.. Location Status 0 See [], except that Limited Service is not supported.

50 GPP C.S00-B v.0. Transaction Identifier Byte(s) Description Length Transaction identifier tag ( C or C []) Length (X) of bytes following to X+ Transaction identifier list X Transaction identifier list: Contents: - 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 []. Each transaction identifier shall not appear more than once within the list; Coding: - Length of bytes following: if CON_REF is not present in the corresponding messages as defined in. (for example, if P_REV_IN_USE is less than, 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 [].. Reserved.0 Call control requested action. Icon Identifier. Item Icon Identifier list. Card reader status. Card ATR

51 GPP C.S00-B v C-APDU. R-APDU. Timer identifier. Timer value. Date-Time.0 AT Command. AT Response. Reserved. Immediate response. DTMF string. Language. Reserved. Browser Identity

52 GPP C.S00-B v URL. Bearer Additionally, bearer 0 = USSD is also allowed..0 Provisioning File Reference. Browser Termination Cause. Bearer description. Channel data. Channel data length. Buffer size. Channel status. Card reader identifier. Other Address. UICC/ME interface transport level

53 GPP C.S00-B v AID. Access Technology. Display parameters. Service Record. Device Filter. Service Search. Attribute Information. Service Availability. Remote Entity Address. ESN Byte(s) Description Length See section. (GPP Tag Values) Length = 0 to ESN_ME 0 The ESN_ME is coded as the ElectronicSerialNumber parameter in [].

54 GPP C.S00-B v.0.0 Network access name An APN, as defined in [].. CDMA SMS TPDU Byte(s) Description Length See section. (GPP Tag Values) to (Y-)+ Length (X) Y (Y-)+ to (Y-)+X+ CDMA SMS TPDU X The CDMA SMS TPDU is formatted as described in []. A CDMA SMS TPDU will have the following structure: Byte(s) Description Length (Y-)+ SMS_MSG_TYPE One or more occurrences of the following segment: (Y-)+ PARAMETER_ID (Y-)+ PARAMETER_LEN (Z) (Y-)+ to (Y-)+Z+ Parameter Data Z 0 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 []. The number of repetitions of the aforementioned segment is determined by the Length and PARAMETER_LEN of each segment.. Text Attribute. Item Text Attribute List. Reserved. Network Search Mode 0

55 GPP C.S00-B v.0 0. Battery State. Browsing Status. Frame Layout. Frame Information.0 Frame Identifier. MEID Byte(s) Description Length See Section. (GPP Tag Values) Length = 0 to MEID_ME 0 RFU 0 The MEID is encoded as BCD digits, without the check digit [i].. Multimedia Message Reference. Multimedia Message Identifier. Multimedia Message Transfer Status. MM Content Identifier

56 GPP C.S00-B v.0 0. Multimedia Message Notification. Last Envelope. Registry Application Data. Activate Descriptor.0 Broadcast Network Information. Contactless state request. Contactless functionality state. Extended registry application data

57 GPP C.S00-B v.0 TAG VALUES 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. of [].. BER-TLV tags in ME to UICC direction See section. of [] and section. of [0].. BER-TLV tags in UICC TO ME direction See section. of [] and section. of [0].. COMPREHENSION-TLV tags in both directions 0 See section. of [] and section. of [0].. Type of Command and Next Action Indicator See [] and SEND USSD from section. of [0].

58 GPP C.S00-B v.0. GPP 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 Name Value CCAT Data Object Command GPP Tag / C ESN TERMINAL RESPONSE (Provide Local Information) GPP Tag / C CDMA-SMS TPDU SEND SHORT MESSAGE CDMA-SMS TPDU CDMA-SMS TPDU GPP Tag / E Reserved n/a ENVELOPE (SMS-PP-DOWNLOAD) ENVELOPE (CELL BROADCAST DOWNLOAD) GPP Tag D / ED MEID TERMINAL RESPONSE (Provide Local Information) Comprehension-TLV tags are bits in length. Bit (CR) can be or 0. [] This is referred to as ESN tag in some versions of []. This is referred to as CDMA-SMS-TPDU tag in some versions of []. This is referred to as Emergency Call tag in some versions of []. This is referred to as MEID tag in some versions of [].

59 GPP C.S00-B v.0 0 ALLOWED TYPE OF COMMAND AND DEVICE IDENTITY COMBINATIONS In addition, MO SHORT MESSAGE CONTROL and SEND USSD are defined in section 0 of [0].

60 GPP C.S00-B v.0 SECURITY REQUIREMENTS Void.

61 GPP C.S00-B v.0 CDMA000 SPECIFIC SIMPLE TLV DATA OBJECTS Void.

62 GPP C.S00-B v.0 ANNEX A (NORMATIVE): SUPPORT OF CCAT BY MOBILE EQUIPMENT See Annex A of []. The definition of class p is included from Annex A of [0]. 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 [] may be used.