`(cid:48)(cid:72)(cid:72)(cid:87)(cid:76)(cid:81)(cid:74)(cid:3)(cid:6)(cid:24)(cid:15)(cid:3)(cid:46)(cid:92)(cid:82)(cid:81)(cid:74)(cid:77)(cid:88)(cid:15)(cid:3)(cid:46)(cid:82)(cid:85)(cid:72)(cid:68)(cid:15)(cid:3)(cid:20)(cid:20)(cid:16)(cid:20)(cid:22)(cid:3)(cid:50)(cid:70)(cid:87)(cid:82)(cid:69)(cid:72)(cid:85)(cid:3)(cid:20)(cid:28)(cid:28)(cid:28)
`
`3G TS 22.038 V2.0.0 (1999-10)
`
`Technical Specification
`
`(cid:22)(cid:85)(cid:71)(cid:3)(cid:42)(cid:72)(cid:81)(cid:72)(cid:85)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:51)(cid:68)(cid:85)(cid:87)(cid:81)(cid:72)(cid:85)(cid:86)(cid:75)(cid:76)(cid:83)(cid:3)(cid:51)(cid:85)(cid:82)(cid:77)(cid:72)(cid:70)(cid:87)(cid:30)
`(cid:55)(cid:72)(cid:70)(cid:75)(cid:81)(cid:76)(cid:70)(cid:68)(cid:79)(cid:3)(cid:54)(cid:83)(cid:72)(cid:70)(cid:76)(cid:73)(cid:76)(cid:70)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:42)(cid:85)(cid:82)(cid:88)(cid:83)(cid:3)(cid:54)(cid:72)(cid:85)(cid:89)(cid:76)(cid:70)(cid:72)(cid:86)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:54)(cid:92)(cid:86)(cid:87)(cid:72)(cid:80)(cid:3)(cid:36)(cid:86)(cid:83)(cid:72)(cid:70)(cid:87)(cid:86)(cid:30)
`(cid:54)(cid:44)(cid:48)(cid:3)(cid:36)(cid:83)(cid:83)(cid:79)(cid:76)(cid:70)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:55)(cid:82)(cid:82)(cid:79)(cid:78)(cid:76)(cid:87)(cid:3)(cid:11)(cid:54)(cid:36)(cid:55)(cid:12)(cid:30)(cid:3)(cid:54)(cid:72)(cid:85)(cid:89)(cid:76)(cid:70)(cid:72)(cid:3)(cid:71)(cid:72)(cid:86)(cid:70)(cid:85)(cid:76)(cid:83)(cid:87)(cid:76)(cid:82)(cid:81)(cid:30)
`(cid:54)(cid:87)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)
`(cid:11)(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:12)
`
`The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
`The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this
`Specification.
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
`
`M2M0007868
`
`1
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:21)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`Reference
`DTS/TSGSA-0122034U
`
`Keywords
`3GPP, SA
`
`3GPP
`
`Postal address
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`http://www.3gpp.org
`
`3GPP
`
`M2M0007869
`
`2
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:22)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`Contents
`
`Foreword............................................................................................................................................................ 5
`1
`Scope ....................................................................................................................................................... 6
`2
`References ............................................................................................................................................... 6
`2.1
`Normative references ......................................................................................................................................... 7
`3
`Definitions and abbreviations.................................................................................................................. 7
`3.1
`Definitions.......................................................................................................................................................... 7
`3.2
`Abbreviations..................................................................................................................................................... 8
`4
`Description .............................................................................................................................................. 8
`5
`High level SAT requirements.................................................................................................................. 8
`6
`SAT/ME interface requirements.............................................................................................................. 9
`6.1
`SAT APIs........................................................................................................................................................... 9
`6.2
`SAT proactive capability ................................................................................................................................... 9
`7
`SAT User Interface requirements.......................................................................................................... 11
`7.1
`Data presentation requirements (e.g. Display) ................................................................................................. 11
`7.2
`Data acquisition requirements (e.g. Keypad) ................................................................................................... 11
`7.3
`Access requirements (e.g. Menu)..................................................................................................................... 11
`7.4
`Menu capability ............................................................................................................................................... 11
`7.4.1
`Set up capability ......................................................................................................................................... 11
`7.4.2
`Selection capability .................................................................................................................................... 11
`7.5
`Soft-key capability ........................................................................................................................................... 11
`7.6
`User control of the SAT execution environment.............................................................................................. 11
`8
`Network interface requirements ............................................................................................................ 12
`8.1
`SAT SIM/Network interaction......................................................................................................................... 12
`8.2
`Communication control capability ................................................................................................................... 12
`8.3
`Service Interworking requirements .................................................................................................................. 12
`9
`SAT bearer requirements....................................................................................................................... 13
`10
`Charging requirements .......................................................................................................................... 13
`11
`Security requirements............................................................................................................................ 13
`11.1
`Secure Environment requirements ................................................................................................................... 14
`12
`Traceability requirements...................................................................................................................... 14
`13
`Roaming................................................................................................................................................. 14
`14
`Interaction with supplementary services ............................................................................................... 14
`14.1
`General............................................................................................................................................................. 14
`14.2
`Line Identification............................................................................................................................................ 15
`14.2.1
`Calling Line Identification Presentation (CLIP)......................................................................................... 15
`14.2.2
`Calling Line Identification Restriction (CLIR)........................................................................................... 15
`14.2.3
`Connected Line Identification Presentation (COLP).................................................................................. 15
`14.2.4
`Connected Line Identification Restriction (COLR).................................................................................... 15
`14.3
`Call Forwarding ............................................................................................................................................... 15
`14.3.1
`Call Forwarding Unconditional (CFU)....................................................................................................... 15
`14.3.2
`Call Forwarding Busy (CFB) ..................................................................................................................... 15
`14.3.3
`Call Forwarding on No Reply (CFNRy)..................................................................................................... 15
`14.3.4
`Call Forwarding on Not Reachable (CFNRc)............................................................................................. 15
`14.4
`Call Completion............................................................................................................................................... 15
`14.4.1
`Call Hold (CH)........................................................................................................................................... 15
`14.4.2
`Call Waiting (CW) ..................................................................................................................................... 15
`14.5
`Multi Party (MPTY) ........................................................................................................................................ 15
`
`3GPP
`
`M2M0007870
`
`3
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:23)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`Closed User Group (CUG)............................................................................................................................... 16
`14.6
`Advice of Charge (AoC) .................................................................................................................................. 16
`14.7
`Call Barring...................................................................................................................................................... 16
`14.8
`Barring of all outgoing calls ....................................................................................................................... 16
`14.8.1
`Barring of outgoing international calls....................................................................................................... 16
`14.8.2
`Mobile originated calls ......................................................................................................................... 16
`14.8.2.1
`Forwarded Calls.................................................................................................................................... 16
`14.8.2.2
`Barring of outgoing international calls except those directed to the HPLMN country............................... 16
`14.8.3
`Barring of all incoming calls ...................................................................................................................... 16
`14.8.4
`Barring of incoming calls when roaming.................................................................................................... 16
`14.8.5
`Explicit Call Transfer (ECT)............................................................................................................................ 16
`14.9
`Completion of Call to Busy Subscriber (CCBS).............................................................................................. 16
`14.10
`Multiple Subscriber Profile (MSP) .................................................................................................................. 16
`14.11
`Interaction with network features.......................................................................................................... 17
`15
`Interactions with Operator Determined Barring (ODB)................................................................................... 17
`15.1
`Barring of all outgoing calls ....................................................................................................................... 17
`15.1.1
`Barring of all outgoing international calls .................................................................................................. 17
`15.1.2
`Barring of all outgoing international calls except those directed to the home PLMN country................... 17
`15.1.3
`Barring of outgoing calls when roaming outside the home PLMN country................................................ 17
`15.1.4
`Barring of outgoing premium rate calls...................................................................................................... 17
`15.1.5
`Barring of incoming calls ........................................................................................................................... 17
`15.1.6
`Barring of incoming calls when roaming outside the home PLMN country............................................... 17
`15.1.7
`Operator Specific Barring .......................................................................................................................... 17
`15.1.8
`Barring of Supplementary Services Management....................................................................................... 17
`15.1.9
`Interactions with Optimal Routing (OR).......................................................................................................... 17
`15.2
`Interactions with MExE ................................................................................................................................... 18
`15.3
`Interactions with CAMEL................................................................................................................................ 18
`15.4
`Compatibility of SAT MS’s and applications ....................................................................................... 18
`16
`SAT Classification ........................................................................................................................................... 18
`16.1
`ME/SIM operation ........................................................................................................................................... 18
`16.2
`ME/SIM capability information exchange ....................................................................................................... 19
`16.3
`ME and SIM compatibility............................................................................................................................... 19
`16.4
`Management Control Category requirements................................................................................................... 19
`16.5
`Mandatory. ................................................................................................................................................. 19
`16.5.1
`Conditional................................................................................................................................................. 19
`16.5.2
`Cross Phase compatibility with future Phases of SAT.......................................................................... 19
`17
`Document History............................................................................................................................................ 20
`
`3GPP
`
`M2M0007871
`
`4
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:24)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`Foreword
`This Technical Specification has been produced by the 3GPP.
`
`The contents of the present document are subject to continuing work within the TSG and may change following formal
`TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying
`change of release date and an increase in version number as follows:
`
`Version 3.y.z
`
`where:
`
`x the first digit:
`
`1 presented to TSG for information;
`
`2 presented to TSG for approval;
`
`3 Indicates TSG approved document under change control.
`
`y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
`etc.
`
`z
`
`the third digit is incremented when editorial only changes have been incorporated in the specification;
`
`3GPP
`
`M2M0007872
`
`5
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:25)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`Scope
`1
`This ETSI Technical Specification defines the stage one description of the SIM application Toolkit (SAT). Stage one is
`an overall service description, primarily from the subscriber’s and serving environment's points of view, and does not
`deal with the details of the human interface itself.
`
`This TS includes information applicable to network operators, serving environments and terminal, switch and database
`manufacturers.
`
`This TS contains the core requirements for a SIM application Toolkit (SAT) which are sufficient to provide a complete
`service.
`
`It is highly desirable however, that technical solutions for a SIM application Toolkit (SAT) should be sufficiently
`flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement
`requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide
`basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise
`conformance to the core requirements of the service.
`
`(cid:42)(cid:54)(cid:48)(cid:3)(cid:51)(cid:47)(cid:48)(cid:49)
`
`(cid:54)(cid:70)(cid:82)(cid:83)(cid:72)(cid:3)(cid:82)(cid:73)
`(cid:87)(cid:75)(cid:76)(cid:86)(cid:3)(cid:55)(cid:54)
`
`(cid:48)(cid:40)
`
`(cid:42)(cid:54)(cid:48)
`(cid:54)(cid:36)(cid:55)
`(cid:54)(cid:44)(cid:48)
`
`(cid:54)(cid:36)(cid:55)(cid:3)(cid:54)(cid:72)(cid:85)(cid:89)(cid:72)(cid:85)(cid:11)(cid:86)(cid:12)
`
`(cid:41)(cid:76)(cid:74)(cid:88)(cid:85)(cid:72)(cid:3)(cid:20)(cid:29)(cid:3)(cid:54)(cid:70)(cid:82)(cid:83)(cid:72)(cid:3)(cid:82)(cid:73)(cid:3)(cid:87)(cid:75)(cid:76)(cid:86)(cid:3)(cid:55)(cid:54)
`
`As indicated in Figure 1, the scope of this TS encompasses the SAT functionality in the MS (comprising SIM and ME)
`and the interaction with the PLMN environment. The SAT Server is not necessarily a separate entity as shown in the
`figure; nodes providing SAT services may also exist within the PLMN. The functionalities of the SAT servers (such as
`charging aspects, security level classification etc.) are not covered by this specification.
`
`SAT requirements are considered to be applicable to both GSM and UMTS systems.
`
`Note:
`
`The present document covers description for SIM only. The document needs to be
`updated to make it applicable to 3GPP.
`
`References
`2
`References may be made to:
`
`3GPP
`
`M2M0007873
`
`6
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:26)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
`which case, subsequent revisions to the referenced document do not apply; or
`
`b) all versions up to and including the identified version (identified by "up to and including" before the version
`identity); or
`
`c) all versions subsequent to and including the identified version (identified by "onwards" following the version
`identity); or
`
`d) publications without mention of a specific version, in which case the latest version applies.
`
`A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
`number.
`
`2.1
`[1]
`
`Normative references
`GSM 01.04 (ETR 350): Digital cellular telecommunications system (Phase 2+); Abbreviations and
`acronyms
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`GSM 02.48: Security mechanisms for the SIM Application Toolkit; Stage 1
`
`GSM 03.48: Security mechanisms for the SIM Application Toolkit; Stage 2
`
`GSM 11.11: Specification of the Subscriber Identity Module - Mobile Equipment interface
`
`GSM 11.14: Specification of the SIM Application Toolkit for the Subscriber Identity Module -
`Mobile Equipment interface.
`
`GSM 02.19: Subscriber Identity Module Application Programming Interface (SIM API)
`
`TR 21.905: "Vocabulary for 3GPP Specifications"
`
`3
`
`Definitions and abbreviations
`
`Definitions
`3.1
`For the purposes of this TS the following definitions apply:
`
`applet: a small program that is intended not to be run on its own, but rather to be embedded inside another application
`
`application: SAT information in the form of software, applications, associated resources (e.g. libraries) and/or data
`
`content: data and/or information associated with, or independent of, a particular application which may be presented to
`or collected from a user
`
`SAT service: a service enhanced (or made possible) by SAT technology
`
`SAT execution environment: the SAT execution environment provides the mechanisms to operate single or multiple
`SAT-applications
`
`SAT serving environment: an entity which delivers SAT services to the subscriber. This is normally the PLMN
`operator, but could be an entity with SAT responsibility (which may have been delegated by the PLMN operator)
`
`SAT subscriber: the owner of a PLMN subscription who has entered into an agreement with a SAT serving
`environment for SAT services. Access to SAT services though other types of networks is out of scope of this
`specification
`
`SAT server: a node supporting SAT services in the SAT service environment
`
`3GPP
`
`M2M0007874
`
`7
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:27)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`user: the user of a SAT MS , who may or may not be the subscriber
`
`Abbreviations
`3.2
`For the purposes of this TS the following abbreviations apply:
`API
`Application Programming Interface
`CAMEL
`Customized Applications for Mobile network Enhanced Logic
`CS
`Circuit Switched
`CSE
`CAMEL Service Environment
`IN
`Intelligent Network
`ME
`Mobile Equipment
`MExE
`Mobile Station (Application) Execution Environment
`MMI
`Man Machine Interface
`MS
`Mobile Station
`NO
`Network Operator
`PLMN
`Public Land Mobile Network
`SAT
`SIM Application Toolkit
`SCI
`Subscriber Controlled Input
`SIM
`Subscriber Identity Module
`Further abbreviations are given in GSM 01.04 [1] and TS 21.905 [7].
`
`Description
`4
`SAT provides a standardised execution environment for applications stored on the SIM card and the ability to utilize
`certain functions of the supporting mobile equipment. SAT provides mechanisms which allow applications, existing in
`the SIM, to interact and operate with any ME which supports the specified mechanism(s) thus ensuring interoperability
`between a SIM and an ME, independent of the respective manufacturers and operators. A transport mechanism is
`provided enabling applications to be down-loaded and/or updated.
`
`A significant aspect of SAT is the highly secure environment provided by the SIM card. This is further enhanced by the
`fact that the subscriber and the issuer of the SIM and also the SAT applications have a "trusted relationship" (e.g. the
`subscriber trusts the issuer of the card to charge correctly for the resources used). This allows certain features, such as
`call control, to be implemented with a degree of freedom which would not be acceptable in a "non-trusted relationship".
`
`The introduction of the SAT execution environment into MSs (i.e. ME+SIM) is a significant step forward in their
`evolution. The ability of MSs to support SAT represents an extension of the MS's and PLMN capabilities. In order to
`allow current and future technologies to exploit and benefit from this, a standardized means of exchanging the MEs’ and
`SIMs capability profiles is supported.
`
`This Technical Specification defines an enhancement of the SIM/ME interface for GSM Phase 2+ and future systems.
`
`High level SAT requirements
`5
`The high level requirements of SAT are as follows:-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`provide the user with additional user interface functionalities to control and invoke services (e.g. menus, icons,
`etc.)
`
`to provide means for the user to personalize applications by means of parameters, if such parameters are made
`available by the application
`
`provide support of a wide variety of applications
`
`provide the means for SAT to interact with the user via the input and output devices of the ME
`
`the means to transfer applications automatically or on demand to the SIM from a SAT server, and upgrade
`existing applications via the PLMN
`
`3GPP
`
`M2M0007875
`
`8
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:28)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`the means to transfer content automatically or on demand to or from the SIM from or to a SAT server
`
`the means to transfer content directly from one SAT application to a second MS with a SAT application via the
`PLMN
`
`the need for an inherent security architecture such that it shall be possible for both the SAT and SAT server sides
`of a connection to be authenticated (possibly implicitly by the use of digital signature or ciphering). The SAT
`server shall maintain security of subscribers personal data and PLMN data
`
`it shall be possible to charge subscribers for the use of PLMN or third party SAT services
`
`the means for SAT applications on the SIM to communicate with other PLMN nodes
`
`the means for the ME and SIM to exchange SAT capability information
`
`provision of SAT API(s) to facilitate the development and downloading of SAT applications
`
`- Categorisation of applications in either "Mandatory" or "Conditional" shall allow application management. For
`conditional-applications the means for the user to manage (i.e. identify version, delete, modify, save etc.) the
`applications and content on the SAT MS shall be possible. Modification of the application by the user is,
`however, explicitly not allowed
`
`-
`
`-
`
`-
`
`-
`
`-
`
`It shall be possible for the user to deactivate the SIM application environment
`
`the means for the network operator to provide and manage the SAT execution environment resources and also to
`provide and manage (i.e. identify version, activate, de-activate, delete, modify, download etc.) those services of
`the management control class "mandatory"
`
`the means to trace (e.g. for billing and customer care purposes) the source of origin of a particular
`communication activity
`
`the means for the SAT application to fully control the display of all actions and network-responses related to the
`operation of the application. Optionally under user control the ME may display the individual actions/responses
`
`the means for the SAT application to control the PLMN services/supplementary services via the standardized
`MMI. Only the originator (i.e. either user or SAT application) of the action shall directly receive the
`results/responses of that action (e.g. network response to an SCI). Optionally under user control the ME may
`display the individual actions/responses.
`
`Some of the above requirements are subsequently elaborated.
`
`6
`
`SAT/ME interface requirements
`
`SAT APIs
`6.1
`The SAT-API is defined in GSM 02.19 [6].
`
`The SAT API for the GSM SIM card shall allow application programmers easy access to the functions and data
`described in GSM 11.11 [4] and GSM 11.14 [5], such that SIM based services can be developed and loaded onto SIMs
`(independent of the SIM manufacturer), quickly and, if necessary, remotely, after the card has been issued. The SAT
`API shall support pro-active functions as described in GSM 11.14 [5] and transport functions as described in GSM
`11.11 [4].
`
`SAT proactive capability
`6.2
`The SAT proactive capability is a mechanism whereby the SIM can request specific actions to be taken by the ME by
`issuing "proactive commands" thus establishing and maintaining an interactive dialogue with the user and/or
`communicating with the network..
`
`3GPP
`
`M2M0007876
`
`9
`
`M2M
`Ex. 2013
`
`
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:89)(cid:72)(cid:85)(cid:86)(cid:76)(cid:82)(cid:81)(cid:3)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)
`
`(cid:20)(cid:19)
`
`(cid:22)(cid:42)(cid:3)(cid:55)(cid:54)(cid:3)(cid:21)(cid:21)(cid:17)(cid:19)(cid:22)(cid:27)(cid:3)(cid:57)(cid:21)(cid:17)(cid:19)(cid:17)(cid:19)(cid:3)(cid:11)(cid:20)(cid:28)(cid:28)(cid:28)(cid:16)(cid:20)(cid:19)(cid:12)
`
`The ME shall inform the SIM of the success or otherwise of each command issued to it by the SIM, and also indicate the
`command details and if applicable add more specific information.
`
`The proactive command set allows the SAT to instruct the ME to:
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`display text supplied by the SIM on the ME's display, with an indication of priority (normal or high), and a
`defined action (user activity or timeout) to terminate the text display.
`
`display a text string and obtain the response in the form of a single user keystroke