CDMA Card Application Toolkit (CCAT)

Transcription

1 GPP C.S00-A Version.0 August 00 CDMA Card Application Toolkit (CCAT) GPP 00 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.

2

3 This page is intentionally left blank i

4 0 0 0 CONTENTS GENERAL Terms... - Scope... - Reserved... - Overview of CCAT Profile Download Proactive UICC Data download to UICC Menu selection Call control by network access application Reserved Event download Security Multiple card 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... - Proactive UICC Introduction Identification of ME support General procedure Proactive UICC commands and procedures DISPLAY TEXT GET INKEY GET INPUT MORE TIME... - ii

5 PLAY TONE POLL INTERVAL REFRESH SET UP MENU SELECT ITEM SEND SHORT MESSAGE Reserved Reserved 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 DECLARE SERVICE Common elements in proactive UICC commands Structure of proactive UICC commands... - iii

6 DISPLAY TEXT GET INKEY GET INPUT MORE TIME PLAY TONE POLL INTERVAL SET-UP MENU SELECT ITEM SEND SHORT MESSAGE Reserved Reserved 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 SEND DATA GET CHANNEL STATUS SERVICE SEARCH...- iv

7 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 Handling of unknown, unforeseen and erroneous messages...-. Proactive commands versus possible terminal response...- ENVELOPE Commands... - v

8 Data Download to R-UIM SMS-PP data download Procedure Structure of ENVELOPE (SMS-PP DOWNLOAD) Cell Broadcast data download... - Procedure... - Structure of ENVELOPE (CELL BROADCAST DOWNLOAD) Menu Selection Call Control Timer Expiration Event download... - SIMPLE-TLV data objects Address Alpha identifier Sub-Address Capability Configuration Parameters Reserved Command details Device identities Duration Item Item identifier Response length Result Reserved Reserved Text string Tone Reserved File List Location Information Reserved...-0 vi

9 Help Request Network Measurement Results Default Text Items Next Action Indicator Event list Cause Location status Transaction identifier...-. Reserved Call control requested action...-. Icon Identifier...-. Item Icon Identifier list...-. Card reader status...-. Card ATR...-. C-APDU...-. R-APDU...-. Timer identifier...-. Timer value...-. Date-Time AT Command...-. AT Response...-. Reserved...-. Immediate response...-. DTMF string...-. Language...-. Reserved...-. Browser Identity...-. URL...-. Bearer Provisioning File Reference...-. Browser Termination Cause...-. Bearer description...- vii

10 Channel data...-. Channel data length...-. Buffer size...-. Channel status...-. Card reader identifier...-. Other Address...-. UICC/ME interface transport level AID...-. Access Technology...-. Display parameters...-. Service Record...-. Device Filter...-. Service Search...-. Attribute Information...-. Service Availability...-. Remote Entity Address...-. ESN Network access name...-. CDMA SMS TPDU...-. Text Attribute...-. Item Text Attribute List...-. Reserved...-. Network Search Mode...-. Battery State...-. Browsing Status...-. Emergency Call...- Tag values BER-TLV tags in ME to UICC direction BER-TLV tags in UICC TO ME direction SIMPLE-TLV tags in both directions Type of Command and Next Action Indicator Allowed Type of command and Device identity combinations...0- viii

11 0 Security requirements...- ANNEX A (NORMATIVE): Support of CCAT by Mobile Equipment...- ANNEX B (INFORMATIVE): Example of DISPLAY TEXT Proactive UICC Command...- ANNEX C (NORMATIVE): Structure of CCAT communications...- ANNEX D (INFORMATIVE): ME display in proactive UICC session...- ANNEX E (INFORMATIVE): Help information feature processing...- ANNEX F (INFORMATIVE): Monitoring of events...- ANNEX G (NORMATIVE): Support of Multiple Card Operation...- ANNEX H (INFORMATIVE): Multiple Card proactive command examples...- ANNEX I (INFORMATIVE): Bearer independent protocol proactive command using CDMA packet data parameters...- ANNEX J (INFORMATIVE): WAP Terminology...- ANNEX K (INFORMATIVE): Use of CCAT Bearer independent protocol for local links Bluetooth case...- ANNEX L (INFORMATIVE): Bluetooth Service Discovery protocol...- ANNEX M (INFORMATIVE): Use of CCAT Bearer independent protocol for local links, server case...- ix

12 FOREWORD 0 This document contains the requirements for CDMA Card Application Toolkit (CCAT). It extends the Card Application Toolkit [] to enable operation in [//]. 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 an R-UIM 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 R-UIM that would function on any particular manufacture 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. 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, e.g. an R-UIM, in this document. The term R-UIM is used in the present document in a generic way to specifically refer to an ICC holding a CDMA network access application. [ ] indicates the corresponding document to be cross referenced x

13 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, Release.. ANSI/INCITS -(R ), Information Processing Coded Character Sets -bit American National Standard Code for Information Interchange (-bit ASCII),.. C.S00-B, Short Message Service (SMS) for Wideband Spread Spectrum Systems- Release B, 00.. IETF RFC, The PPP Compression Control Protocol (CCP), June.. 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.. ANSI/TIA/EIA--E, Cellular Radio Telecommunication Intersystem Operations.. Reserved. 0. ITU-T Recommendation E., Identification Plan for Land Mobile Stations,.. ETSI TS 0, Digital Cellular Telecommunications System (Phase +) (GSM); Universal Mobile Telecommunications System (UMTS); Alphabets and Language-Specific Information, GPP TS.0 Release.. ETSI TS.0, International Mobile Equipment Identities (IMEI), GPP TS.0 Release.. C.S00-B, Removable User Identity Module for Spread Spectrum Systems- Release B, 00.. C.S00-0-A, Data Service Options for Spread Spectrum Systems: Service Option and, 00.. GPP C.S00-0, UICC-Terminal interface Physical and Logical characteristics for cdma000 Spread Spectrum Systems, December 00 Deleted: Standard Informative References. GPP C.S000-D, Introduction to cdma000 Standards for Spread Spectrum Systems, March 00. xi

14 0. GPP C.S000-D, Physical Layer Standard for cdma000 Spread Spectrum Systems, March 00.. GPP C.S000-D, Medium Access Control (MAC) Standard for cdma000 Spread Spectrum Systems, March 00.. GPP C.S000-D, Signaling Link Access Control (LAC) Standard for cdma000 Spread Spectrum Systems, March GPP C.S000-D, Upper Layer (Layer ) Signaling Standard for cdma000 Spread Spectrum Systems, March 00.. GPP C.S000-D, Analog Signaling Standard for cdma000 Spread Spectrum Systems, March 00.. TIA/EIA/IS--B, Mobile Station Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Standards, December.. C.R00-D, Administration of Parameter Value Assignments for cdma000 Spread Spectrum Standards- release D, 00. Deleted: TIA/EIA xii

15 Formatted: Justified, Right: 0 pt GENERAL. 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. Global Emergency Call Indicator. Used by the Mobile Station to identify an Emergency Call as specified in [0]. 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. 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. OTAF. See Over-the-Air Provisioning Function. OTASP. See Over-the-Air Service Provisioning. -

16 0 0 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 R-UIM. UICC. Within the scope of this document, an ICC supporting at least one network access application, e.g. an R-UIM. -

17 Formatted: Justified, Right: 0 pt 0 0 SCOPE The present document defines the interface between the R-UIM 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, e.g. an R-UIM, in this document. In the present document, the term R-UIM is used in a generic way to specifically refer to an ICC holding a CDMA network access application. 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 an R-UIM 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 R-UIM 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 R-UIM 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 R-UIM 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). Deleted: ETSI TS 0 -

18 RESERVED 0 OVERVIEW OF CCAT The CCAT provides mechanisms, which allow applications, existing in the R-UIM, 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 Deleted: ETSI TS 0. Proactive UICC A proactive R-UIM provides a mechanism whereby the R-UIM can initiate actions to be taken by the ME.. Data download to UICC. Menu selection. Call control by network access application 0. Reserved. Event download. Security. Multiple card.0 Timer Expiration -

19 Formatted: Justified, Right: 0 pt. Bearer Independent Protocol. Description of the access technology indicator mechanism. Tag allocation guidelines PROFILE DOWNLOAD 0. Procedure The profile download instruction is sent by the ME to the R-UIM as part of the R-UIM 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 []. Deleted: ETSI TS 0. Structure and coding of TERMINAL PROFILE Direction: ME to R-UIM. The command header is the one specified for TERMINAL PROFILE in []. Command parameters/data: Description Clause M/O/C Length Profile - M lgth Profile: - Contents: The list of CCAT facilities that are supported by the ME. 0 - Coding ( bit is used to code each facility): bit = : facility supported by ME. bit = 0: facility not supported by ME. NOTE: several bits may need to be set to for the support of the same facility. This is because of backward compatibility with SAT: several options existed in SAT for a given facility, and they are mandatory in CCAT when this facility is supported. 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 []. Twentieth byte (Proactive R-UIM): -

20 b b b b b b b b SEND CDMA SMS CDMA SMS-PP data download CDMA SMS BROADCAST data download RFU Response parameters/data: - None.. Definition of display parameters in Profile download PROACTIVE UICC. Introduction. Identification of ME support 0. General procedure. Proactive UICC commands and procedures.. DISPLAY TEXT.. GET INKEY.. GET INPUT 0.. MORE TIME.. PLAY TONE NOTE: Some supervisory tones are optional for mobile equipment (see []). Deleted: GPP TS.00.. POLL INTERVAL -

21 Formatted: Justified, Right: 0 pt REFRESH.. SET UP MENU.. SELECT ITEM..0 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; - A short message to be sent to the network in an SMS-SUBMIT message where the text 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 text length given by the R-UIM shall state the number of characters in the text string. The command details shall indicate, Packing is not required. Where packing by the ME is required, the R-UIM shall use the -bit ASCII as defined in [], IA as defined in [] or GSM -bit default alphabet packed into -bit octets as defined in []. The text length given by the R-UIM shall state the number of characters in the text string. The ME shall pack the text string before submitting the message to the network. The command details shall indicate, Packing is required. Optionally, the R-UIM 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 R-UIM 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 R-UIM, 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 R-UIM 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 R-UIM, the ME may give information to the user concerning what is happening. If the ME is capable of SMS-MO, then it shall send the data as a Short Message TPDU to the destination address. The ME shall give the result to the R-UIM using TERMINAL RESPONSE (indicating successful or unsuccessful transmission of the Short Message) after receiving an SMS Acknowledgement Message from the network. If an alpha identifier was provided by the -

22 R-UIM, the ME should not give any information to the user at the reception of SMS Acknowledgement Message. If the network unsuccessfully receives the Short Message TPDU, the ME shall inform the R- UIM using TERMINAL RESPONSE (network currently unable to process command). If a null alpha identifier was provided by the R-UIM, the ME should not give any information to the user at the unsuccessful network reception... Reserved.. Reserved SET UP CALL This command is issued by the R-UIM to request a call set up. The procedure is defined in [], except when stated otherwise in the present document. The R-UIM may request the use of an automatic redial mechanism according to [] It is possible for the R-UIM to request the ME to set up an emergency call by supplying an Emergency Call object (see.). Upon receiving this Emergency Call object, the ME shall set the global emergency call indicator if the indicator is supported by the ME. If the command from the R-UIM card contains an Emergency Call object, then the ME shall follow the procedure below: - if the R-UIM supplies an Address object with a data, this shall result in an emergency call if possible using the number supplied by the R-UIM card; - if the R-UIM supplies a null data object (i.e. length = '00' and no value part) as the Address object, this shall result in an emergency call. If a number is needed for setting up the emergency call, then the first entry in the EF ECC list shall be used. If the EF ECC list is empty then the ME informs the R-UIM using TERMINAL RESPONSE (Command beyond ME s capabilities). The operation is aborted. - if the UICC supplies a number stored in EF ECC, this shall not result in setting the global emergency call indicator even if the indicator is supported by the ME. If the R-UIM supplies as number without an Emergency Call object, this shall not result an emergency call; If the R-UIM supplies a number stored in EF ECC without an Emergency Call object, this shall not result in an emergency call; Upon receiving this command, the ME shall decide if it is able to execute the command. One example is given below, but the list is not exhaustive: - if the command is rejected because the ME is busy on another call, the ME informs the R-UIM using TERMINAL RESPONSE (ME unable to process command - currently busy on call);.. POLLING OFF Deleted: GPP TS.00 -

23 Formatted: Justified, Right: 0 pt PROVIDE LOCAL INFORMATION This command requests the ME to send current local information to the R-UIM. At present, this information is restricted to: - Location information: the mobile country code (MCC), th and th digits of IMSI (IMSI ), system identification (SID), network identification (NID), base station identification (BASE_ID), longitude (BASE_LONG) and latitude (BASE_LAT) of the current base station; - 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. Note, this information may not reflect the BASE_ID, BASE_LONG and BASE_LAT of the serving base station. - When location information has been requested and no service is currently available, the ME shall return the data requested in the TERMINAL RESPONSE with the result ME currently unable to process command - no service. - When location information has been requested and the ME is on limited service (e.g. emergency calls only), the ME shall return the data requested in the TERMINAL RESPONSE with the result Limited Service. The ME shall return the current date and time as set by the user. 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... SET UP EVENT LIST.. PERFORM CARD APDU.. POWER OFF CARD.. POWER ON CARD..0 GET READER STATUS -

24 0 0.. TIMER MANAGEMENT.. SET UP IDLE MODE TEXT.. RUN AT COMMAND.. SEND DTMF.. LANGUAGE NOTIFICATION.. LAUNCH BROWSER.. OPEN CHANNEL.. CLOSE CHANNEL.. RECEIVE DATA..0 SEND DATA.. GET CHANNEL STATUS.. SERVICE SEARCH.. GET SERVICE INFORMATION.. DECLARE SERVICE -

25 Formatted: Justified, Right: 0 pt 0 0. Common elements in proactive UICC commands. Structure of proactive UICC commands The general structure of proactive R-UIM commands using TLV objects is described in annex C... DISPLAY TEXT.. GET INKEY.. GET INPUT.. MORE TIME.. PLAY TONE.. POLL INTERVAL.. SET-UP MENU.. SELECT ITEM.. SEND SHORT MESSAGE..0 Reserved.. Reserved.. SET UP CALL -

26 0 Description Clause M/O/C Min Length Proactive UICC command Tag. M Y Length - M Y or (A+B+C+D+E+F+G+H+I+J+K+L+M+N) Command details. M Y A Device identities. M Y B Alpha identifier (user confirmation phase). O N C Address. M Y D Capability configuration parameters. O N E Subaddress. O N F Duration. O N G Icon identifier (user confirmation phase). O N H Alpha identifier (call set up phase). O N I Icon identifier (call set up phase). O N J Text Attribute (user confirmation phase). C N K Text Attribute (call set up phase). C N L Emergency Call. O N N If the capability configuration parameters are not present, the ME shall assume the call is a speech call. If the subaddress is not present, the ME shall not provide a called party subaddress to the network. If the duration is not present, the R-UIM imposes no restrictions on the ME of the maximum duration of redials. The Text Attribute (user confirmation phase) applies to the Alpha Identifier (user confirmation phase). The Text Attribute (call set up phase) applies to the Alpha identifier (call set up call phase). One Text Attribute may be present, only if at least one Alpha Identifier is present. Both Text Attributes may be present only if both Alpha Identifiers are present. If only one Text Attribute data object is present, it shall apply to the first or unique alpha identifier present in the command. If the R-UIM is requesting an emergency call set up, then the Emergency Call shall be provided. Formatted: Portuguese (Brazil) Formatted: Not Highlight.. REFRESH.. POLLING OFF 0.. PROVIDE LOCAL INFORMATION.. SET UP EVENT LIST -0

27 Formatted: Justified, Right: 0 pt 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 COMMAND.. LANGUAGE NOTIFICATION.. LAUNCH BROWSER.. OPEN CHANNEL.. CLOSE CHANNEL.. RECEIVE DATA..0 SEND DATA -

28 0 0.. GET CHANNEL STATUS.. SERVICE SEARCH.. GET SERVICE INFORMATION.. DECLARE SERVICE. Command results Once the ME has made its attempt to execute a proactive command from the R-UIM, the ME shall inform the R-UIM of the success or otherwise of that command, by using TERMINAL RESPONSE. This procedure is defined in [].. Structure of TERMINAL RESPONSE.. Command details.. Device identities.. Result.. Duration.. Text string.. Item identifier.. Local information -

29 Formatted: Justified, Right: 0 pt Call control requested action.. Result data object..0 Card reader status.. Card ATR.. R-APDU.. Timer identifier.. Timer value.. AT Response.. Text string.. Channel data.. Channel status.. Channel data length..0 Bearer description.. Buffer size -

30 0.. Total Display Duration.. Service Availability.. Service Record. Proactive UICC session and ME display interaction.0 Handling of unknown, unforeseen and erroneous messages. Proactive commands versus possible terminal response -

31 Formatted: Justified, Right: 0 pt ENVELOPE COMMANDS. Data Download to R-UIM.. SMS-PP data download... Procedure If the service data download via SMS-PP is allocated and activated in the CDMA Service Table, then the ME shall follow the procedure below: - When the ME receives a Short Message with: Teleservice Identifier = Card Application Toolkit Protocol Teleservice (CATPT) then the ME shall pass the message transparently to the R-UIM using the ENVELOPE (SMS-PP DATA DOWNLOAD) command as defined below: - The ME shall not display the message, or alert the user of a short message waiting. - The ME shall wait for an acknowledgement from the R-UIM. - If the R-UIM responds with 0 00, the ME shall acknowledge the receipt of the short message to the network using an SMS User Acknowledgement message. - If the R-UIM responds with 00, the ME shall either retry the command or send back an SMS User Acknowledgement message to the network according to [] with the User Response Code value indicating Destination busy as defined in the SMS_CauseCode table of []. - If the R-UIM responds with F XX, the ME shall use the GET RESPONSE command to retrieve the response data. The ME shall include the response data received from the R-UIM in the User Data field of the SMS User Acknowledgement message that it will send back to the network according to []. - If the ME has indicated in ME PROFILE that it supports the status word E XX and if the R-UIM responds with E XX, the ME shall use the GET RESPONSE command to get the response data. The ME shall include the response data received from the R-UIM in the User Data field of the SMS User Acknowledgement message that it will send back to the network according to []. The value of the User Response Code of the SMS User Acknowledgement Message shall be Other Terminal problem as defined in the SMS_CauseCode table of []. - If the service data download via SMS-PP is neither allocated nor activated in the CDMA Service Table and the ME receives a SMS Point-to-Point Message with Teleservice_ID = CATPT, then the ME shall store the message in EF SMS under DF CDMA. MEs not supporting CCAT shall store SMS Point-to-Point Messages in EF SMS under DF CDMA, as if they were normal short messages. -

32 ... Structure of ENVELOPE (SMS-PP DOWNLOAD) Direction: ME to R-UIM The command header is specified in []. Command parameters/data. Description Section M/O Min Length SMS-PP DATA 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: R-UIM. Response parameters/data. 0 It is permissible for the R-UIM not to provide response data. If the R-UIM responds with 0 00 then no response parameter shall be available, otherwise the R-UIM shall respond with F XX or E XX and the following data is returned: Byte(s) Description Length -X (X ) R-UIM Acknowledgement X.. Cell Broadcast data download 0 If the service "data download via SMS CB" is allocated and activated in the CDMA Service Table, then the ME shall follow the procedure below: - When the ME receives a Short Message with: Teleservice Identifier = Card Application Toolkit Protocol Teleservice (CATPT) Procedure If the service "data download via Broadcast SMS" is allocated and activated in the CDMA Service Table, then the ME shall follow the procedure below: -

33 Formatted: Justified, Right: 0 pt 0 - When the ME receives a new Broadcast SMS message, the ME shall check the Service Category of the Broadcast SMS message. - If the Service Category is CATPT, the ME shall pass the message transparently to the R-UIM using the ENVELOPE (BROADCAST SMS DATA DOWNLOAD) command defined below. - The ME shall not display the message, or alert the user of a short message waiting. - If the Service Category is not CATPT, then the ME shall determine if the message should be displayed, by following the procedures in []. The ME shall identify new Broadcast SMS messages by their message identifier and service category. Structure of ENVELOPE (CELL BROADCAST DOWNLOAD) Direction: ME to R-UIM. The command header is specified in []. Command parameters/data: Description Section M/O Min Length BROADCAST SMS DATA 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. 0 Response parameters/data: None for this type of ENVELOPE command.. Menu Selection. Call Control.. Call Control by R-UIM... Procedure for mobile originated calls If the service "call control" is available in the "Service Table", then the ME shall follow the procedure described in [] with the additional rules listed here: -

34 If the user dials "" or an emergency call code stored in EF ECC or in the ME, the ME shall set the global emergency call indicator to if supported, instead of passing the call set-up details to the UICC; - If the R-UIM supplies as number without an Emergency Call object, this shall not result an emergency call; - If the R-UIM supplies a number stored in EF ECC without an Emergency Call object, this shall not result in an emergency call; - If the response from the R-UIM card contains an Emergency Call object, then the ME shall follow the procedure below: if the R-UIM supplies an Address object with data, this shall result in an emergency call if possible using the number supplied by the R-UIM card; if the R-UIM supplies a null data object (i.e. length = '00' and no value part) as the Address object, this shall result in an emergency call. If a number is needed for setting up the emergency call, then the first entry in the EF ECC list shall be used. If the EF ECC list is empty then the ME shall not perform the call set-up, and the operation is aborted. In the case where the initial call set-up request results from a proactive command SET UP CALL: - If the R-UIM supplies an Emergency Call object inside the SET UP CALL proactive command, then the ME shall set up an emergency call instead of passing the call set-up details to the R-UIM (the ME shall set the global emergency call indicator if the indicator is supported by the ME); - If the response from the R-UIM card contains an Emergency Call object, then the ME shall follow the procedure below: if the R-UIM supplies an Address object with data, this shall result in an emergency call if possible using the number supplied by the R-UIM card; if the R-UIM supplies a null data object (i.e. length = '00' and no value part) as the Address object, this shall result in an emergency call. If a number is needed for setting up the emergency call, then the first entry in the EF ECC list shall be used. If the EF ECC list is empty then the ME informs the R-UIM using TERMINAL RESPONSE (Command beyond ME s capabilities). The operation is aborted.... Reserved... 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) -

35 Formatted: Justified, Right: 0 pt Direction: ME to UICC. The command header is specified in []. Command parameters/data: Response parameters/data: It is permissible for the R-UIM to provide no response data, by responding with SW/SW = '0 00'. If the R-UIM does not provide any response data, then this shall have the same meaning as "allowed, no modification". Description Clause M/O/C Min Length Call control result - M Y Length (A+B+C+D+E+F+G) - M Y or Address. O N A Capability configuration parameters. O N B Subaddress. O N C Alpha identifier. O N D BC repeat indicator. C N E Capability configuration parameters. O N F Emergency Call. O N G 0. Timer Expiration. Event download 0 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 [0] (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 [0] (possible message: Service Connect Message, General Handoff Direction Message, Universal Handoff Direction Message or Call Assignment Message)]. - 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. -

36 SIMPLE-TLV DATA OBJECTS The coding of the TLV objects is as described in [], except when stated otherwise in the present document.. Address. Alpha identifier 0. Sub-Address. Capability Configuration Parameters Deleted: Reserved 0 0 Byte(s) Description Length Capability configuration parameters tag to (Y-)+ Length (X) Y (Y-)+ to (Y-)+X+ CDMA Capability configuration parameters X CDMA Capability configuration parameters: CDMA SO list. Each SO is a -bit number as specified in []. The SOs listed in CDMA capability configuration parameters should be ordered according to the preference of SOs, i.e., the most preferred SO should be listed as the first SO in the list, and rest is listed in the descending order of preference. CCAT application using SETUP UP CALL command should list all the SOs the application can use for a specific call type (voice or data, SMS or OTA etc) in CDMA Capability configuration parameters so ME can negotiate one of SOs listed with network. If ME receives the CCAT setup call command, with capability configuration parameters Tag included, ME shall use the first service options listed in the CDMA Capability Configuration Parameters as the service option field in CDMA origination message as defined in [0]. ME can put the remaining SO listed in CDMA Capability Configuration Parameters as Alternative SO fields in origination message. If ME receives response message from the network indicating that one of the SO in the CCP is accepted by network, ME shall proceed to establish the call and send terminal response to R-UIM indicating the success of the call setup command. Otherwise, if ME receives the response message from network indicating another SO outside of the CCP list is proposed or receives the response message indicating the origination is rejected, ME shall send the terminal response to R-UIM indicating the failure of the call setup command If the first SO in CCP is not supported by ME, ME can select one it supported from the CCP and use it as the SO field in origination message. -

37 Formatted: Justified, Right: 0 pt 0 0. Reserved. Command details. Device identities. Duration. Item.0 Item identifier. Response length. Result. Reserved. Reserved. Text string Content and coding is defined [].. Tone. Reserved. File List -

38 . Location Information Byte(s) Description Length Location information tag Length = 0F MCC IMSI SID NID 0 BASE_ID BASE_LAT BASE_LONG Bytes : 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 Byte : b B b b b b b b LSB of IMSI Middle bits of IMSI in ascending order MSB of IMSI RFU 0 Bytes : b B b b b b b b LSB of SID SID bits in ascending order -

39 Formatted: Justified, Right: 0 pt b B b b b b b b SID bits in ascending order MSB of SID RFU Bytes : Bytes 0 : 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 b B b b b b b b b B b b b b b b LSB of BASE_ID BASE_ID bits in ascending order BASE_ID bits in ascending order MSB of BASE_ID 0 Bytes : 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_LAT BASE_LAT bits in ascending order BASE_LAT bits in ascending order BASE_LAT bits in ascending order MSB of BASE_LAT RFU -

40 Bytes : 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.0 Reserved. Help Request. Network Measurement Results RFU. 0. Default Text. Items Next Action Indicator. Event list. Cause Deleted: Reserved 0 Byte(s) Description Length Cause tag Length (X) of bytes following. X=0, or X 0. to X+ Cause X There is no cause values defined in current [0] 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

41 Formatted: Justified, Right: 0 pt. Transaction identifier Deleted: Byte(s)... [] 0 Byte(s) Description Length Transaction identifier tag 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 [0]. 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.. Reserved - Each byte in the transaction identifier list shall contain the value of CON_REF in signalling messages as defined in [0]. 0.0 Call control requested action. Icon Identifier. Item Icon Identifier list. Card reader status. Card ATR 0. C-APDU -

42 0 0. R-APDU. Timer identifier. Timer value. Date-Time.0 AT Command. AT Response. Reserved. Immediate response. DTMF string. Language. Reserved. Browser Identity. URL. Bearer.0 Provisioning File Reference -

43 Formatted: Justified, Right: 0 pt. Browser Termination Cause. Bearer description Byte(s) Description Length Bearer description tag Length Bearer type PPP Payload Compression CCP Option to (+X) QOS BLOB X - Bearer Type coding: in addition to the values defined in [], the following are defined: '0' = NA; '0' = NA; '0' = GPP packet data service Bearer parameters coding: Contents: parameters describing the Quality of Service (QoS) and the type of PPP Payload Compression CCP Option. The PPP Payload Compression CCP Option is coded as specified in []. The QoS BLOB coded as specified in []. To use the default set of QOS parameters for GPP packet data service, the parameters should not include a QOS BLOB in the BEARER description parameters. To propose any non-default parameters, the BEARER description parameters shall include a QOS BLOB, as specified in [] and set the parameters in the QOS BLOB using the values defined in []. When requesting assured mode packet data service, the R-UIM shall omit any QOS parameter for which it requests and can accept best effort service rather than a specific level of service.. Channel data. Channel data length. Buffer size -

44 0 0. 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 -

45 Formatted: Justified, Right: 0 pt.0 Network access name. CDMA SMS TPDU Byte(s) Description Length CDMA SMS TPDU tag to (Y-)+ (Y-)+ to (Y-)+X+ Length (X) CDMA SMS TPDU Y 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 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. Battery State -

46 . Browsing Status. Emergency Call Byte(s) Description Length Emergency Call tag Length (always 0x00) -

47 Formatted: Justified, Right: 0 pt 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 [].. BER-TLV tags in ME to UICC direction In addition to the values defined in [], the following are defined: Description Length of tag Value SMS-PP download tag D' SMS Broadcast download tag 'D' 0. BER-TLV tags in UICC TO ME direction See [] and no additional tag is defined for CDMA.. SIMPLE-TLV tags in both directions In addition to the values defined in [], the following is defined: Description Length of tag Tag value, bits - (Range: '0' - 'E') Tag (CR and Tag value) CDMA SMS-TPDU '' '' or 'C'. Type of Command and Next Action Indicator See [] and no additional type of command is defined for CDMA. -

48

49 0 ALLOWED TYPE OF COMMAND AND DEVICE IDENTITY COMBINATIONS 0-

50 SECURITY REQUIREMENTS The security requirements of the R-UIM shall follow the definitions specified in Section of []. -

51 ANNEX A (NORMATIVE): Support of CCAT by Mobile Equipment See Annex A of []. 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. Deleted: ETSI TS 0. -

52 ANNEX B (INFORMATIVE): Example of DISPLAY TEXT Proactive UICC Command -

53 ANNEX C (NORMATIVE): Structure of CCAT communications -

54 ANNEX D (INFORMATIVE): ME display in proactive UICC session -

55 ANNEX E (INFORMATIVE): Help information feature processing -

56 ANNEX F (INFORMATIVE): Monitoring of events -

57 ANNEX G (NORMATIVE): Support of Multiple Card Operation -

58 ANNEX H (INFORMATIVE): Multiple Card proactive command examples -

59 ANNEX I (INFORMATIVE): Bearer independent protocol proactive command using CDMA packet data parameters. This annex applies if class "e" is supported. For the others bearers, see []. ICC Terminal BS OPEN CHANNEL OPEN CHANNEL (immediate) Bearer description(ppp Payload Compression, QoS BLOB), Buffer size, Network Access Name, UICC/Terminal interface transport level (UDP, port p), data destination address) Origination (packet data service option) Channel Assignment Service Request (QoS BLOB) Service Connect (QoS BLOB) Service Connect Completion LCP Negotiation Terminal Response (Channel identifier, link established, no further information, buffer size) ENVELOPE (Channel status event: Channel identifier, link established) IPCP Negotiation (exchange user profile corresponding to Network Access Identifier) CCP Negotiation (PPP Payload Compression) CLOSE CHANNEL CLOSE CHANNEL(Channel identifier) Terminal Response(OK) Release Release -

60 RECEIVE DATA ENVELOPE (Data available) Data (one complete SDU received) RECEIVE DATA (Channel Data length) Terminal Response(Channel Data Length, Data<=Length) RECEIVE DATA (Channel Data length) Terminal Response(Channel Data Length, Data<=Length) RECEIVE DATA (Channel Data length) Terminal Response(Channel Data Length = 0, Data<=Length) SEND DATA 'Stored in Tx Buffer' SEND DATA (Store, Data) Terminal Response(Channel Data length) SEND DATA (Store, Data) Terminal Response(Channel Data length) SEND DATA (Immediate, Data) Terminal Response(Channel Data length = 0) Data GET CHANNEL STATUS GET CHANNEL STATUS Terminal Response (Channel status) Channel available -0

61 ANNEX J (INFORMATIVE): WAP Terminology -

62 ANNEX K (INFORMATIVE): Use of CCAT Bearer independent protocol for local links Bluetooth case -

63 ANNEX L (INFORMATIVE): Bluetooth Service Discovery protocol -

64 ANNEX M (INFORMATIVE): Use of CCAT Bearer independent protocol for local links, server case -

65 Page -: [] Deleted Praveen //00 ::00 AM Byte(s) Description Length Transaction identifier tag 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. The transaction identifier shall be the Transaction Identifier in the call setup message from the network. Coding: Each byte in the transaction identifier list is a single byte between '0' and 'FF'. Each transaction identifier shall not appear more than once within the list.