1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelMobile ExecSer(3GPP TS 22.0TECHNICAL SPECIFICATION122 057 V13.0.0 (2016communications system (Phaelecommunications System (LTE; ecution Environment (MExE); ervice description; Stage 1 .057 version 13.0.0 Release 1316-01) hase 2+); (UMTS); 13) ETSI
2、 ETSI TS 122 057 V13.0.0 (2016-01)13GPP TS 22.057 version 13.0.0 Release 13Reference RTS/TSGS-0122057vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non
3、 lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of
4、the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific ne
5、twork drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the
6、 present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as aut
7、horized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, P
8、LUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Associ
9、ation. ETSI ETSI TS 122 057 V13.0.0 (2016-01)23GPP TS 22.057 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETS
10、I members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ip
11、r.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential
12、to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted a
13、s being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “wil
14、l“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 122 057 V13.0.0 (2016-01)33GPP
15、TS 22.057 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Description . 8g35 Compatibility of MExE UE“s and application
16、s . 8g35.1 MExE classmarks . 8g35.2 UE MExE classmarks . 8g35.3 MExE executables and MExE classmarks . 9g36 General MExE requirements 9g36.1 High level MExE requirements 9g36.2 Requirements description from the users standpoint . 11g36.2.1 User interface configuration management 11g36.2.2 Service ma
17、nagement . 11g36.3 Requirements description from the MExE service provider“s standpoint 12g36.3.1 Transfer of applications, applets and content 12g36.3.2 Node types 12g36.3.3 Subscriber data 12g36.3.4 Roaming subscribers . 13g37 MExE bearer requirements . 13g38 MExE protocols requirements 13g38.1 Op
18、timised Wireless Access 13g38.2 Wireless network independence . 14g38.3 Scaleable and extendible protocols. 14g38.4 Service independence . 14g38.5 Network node type independence 14g38.6 Enquiry and notification of MExE capabilities 14g38.7 UE request of services information 15g38.8 Support of transf
19、er protocols 15g39 UE application execution environment requirements 15g39.1 UE platform independence . 15g39.2 Document mark-up language and other coding formats . 15g39.3 MExE APIs 15g310 Charging requirements . 16g311 Security requirements . 16g311.1 Security Principles 17g311.2 Security Requirem
20、ents . 17g311.3 Security domain classifications 18g312 Interworking with other network features 18g313 Network interworking 18g3Annex A (informative): Example MExE services 19g3ETSI ETSI TS 122 057 V13.0.0 (2016-01)43GPP TS 22.057 version 13.0.0 Release 13Annex B (informative): Change history . 23g3
21、History 24g3ETSI ETSI TS 122 057 V13.0.0 (2016-01)53GPP TS 22.057 version 13.0.0 Release 13Foreword 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
22、TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indica
23、tes TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 122 057 V13.0.0 (2
24、016-01)63GPP TS 22.057 version 13.0.0 Release 131 Scope This TS defines the stage one description of the Mobile Execution Environment (MExE). Stage one is an overall service description, primarily from the subscriber“s and service providers“ points of view, and does not deal with the details of the
25、human interface itself. This 3GPP TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers. This 3GPP TS contains the core requirements for a Mobile Execution Environment (MExE) which are sufficient to provide a complete service. It i
26、s highly desirable however, that technical solutions for a Mobile Execution Environment (MExE) should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this 3GPP TS may implement requirements which are considered outside the scope of this 3GPP
27、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. MExE Service EnvironmentUEMExEScope ofthis TSFigure 1: Scope of this 3GPP TS
28、As indicated in Figure 1, the scope of this 3GPP TS encompasses the MExE functionality in the UE, interaction with the MExE service environment. The MExE service environment is not necessarily restricted to the PLMN, and nodes providing MExE services (i.e. MExE servers) may also exist outside the PL
29、MN. Aspects of the support provided by MExE servers within the MExE service environment (such as charging aspects, security level classification etc.) are covered by this specification, but not the MExE servers themselves. 2 References The following documents contain provisions which, through refere
30、nce in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. ETSI ETSI TS 122 057 V13.0.0 (2016-01)73GPP TS 22.05
31、7 version 13.0.0 Release 13 For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.
32、905: “Vocabulary for 3GPP Specifications“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of this 3GPP TS the following definitions apply: applet: a small programme that is intended not to be run on its own, but rather to be embedded inside another application application: MExE inf
33、ormation in the form of software, scripts, 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 MExE Classmark: a MExE Classmark identifies a ca
34、tegory of MExE UE supporting MExE functionality with a minimum level of processing, memory, display and interactive capabilities. Several MExE Classmarks may be defined to differentiate between the functionalities offered by different MExE UE“s. A MExE executable defined as being of a specific MExE
35、Classmark indicates that it is supportable by a MExE UE of that Classmark. MExE server: a node supporting MExE services in the MExE service environment MExE service: a service enhanced (or made possible) by MExE technology MExE service environment: Depending on the configuration of the PLMN, the ope
36、rator may be able to offer support to MExE services in various ways. Examples of possible sources are from traditional 3GPP network nodes, IN nodes, operator-specific nodes, operator-franchised nodes and services provider nodes, together with access to nodes external (i.e. vendor-specific) to the PL
37、MN depending on the nature of the MExE service. These nodes are considered to constitute the MExE service environment. The MExE service environment shall support direct MExE UE to MExE UE interaction of MExE services. MExE service provider: an organisation which delivers MExE services to the subscri
38、ber. This is normally the PLMN operator, but could be an organisation with MExE responsibility (which may have been delegated by the PLMN operator). MExE subscriber: the owner of a subscription who has entered into an agreement with a MExE service provider for MExE services. Access to MExE services
39、though other types of networks is out of scope of this specification. subscriber: the term subscriber in the context of this 3GPP TS refers to a MExE subscriber user: the user of an MExE UE , who may or may not be the subscriber. 3.2 Abbreviations For the purposes of this 3GPP TS the following abbre
40、viations apply: API Application Programming Interface CS Circuit Switched FFS For Further Study IN Intelligent Network ME Mobile Equipment MExE Mobile Execution Environment MMI Man Machine Interface UENO Network Operator ETSI ETSI TS 122 057 V13.0.0 (2016-01)83GPP TS 22.057 version 13.0.0 Release 13
41、PLMN Public Land Mobile Network SIM Subscriber Identity Module UE User Equipment USIM Universal Subscriber Identity Module SP Service Provider Further related abbreviations are given in TR 21.905 1. 4 Description MExE provides a standardised execution environment in an UE, and an ability to negotiat
42、e its supported capabilities with a MExE service provider, allowing applications to be developed independently of any UE platform. The UE (consisting of the ME and SIM/USIM) can then be targeted at a range of implementations for MExE from small devices with low bandwidth, limited displays, low proce
43、ssor speeds, limited memory, MMI etc., to sophisticated with a complete MExE execution environment. The introduction of MExE execution environment into UE“s is a significant step forward in their evolution. The ability of UE“s to support MExE executables represents an extension of UE“s capabilities.
44、 In order to allow current and future technologies to exploit and benefit from this, a standardised means of negotiating the UE“s and network“s capabilities is supported. This negotiation will permit the mutual exchange of capabilities between the UE and the MExE server, and possibly include the ser
45、vice profile of the user and capabilities of the network. The negotiation may take place at service initiation, or on a dynamic basis. A network can be a transport bearer for the negotiation, interaction and transferring of applications, applets and content with the UE, however it need not necessari
46、ly be the provider of the MExE services with which the UE“s execution environment is interacting with. The network may also be the intermediary between two UE“s which are engaged in a MExE service with each other, with the network effectively supplying the pipe and not playing a MExE role in the con
47、nection. Network nodes, nodes external to the network, or even UE“s may be the entities which interact with the UE“s execution environment. 5 Compatibility of MExE UE“s and applications 5.1 MExE classmarks Given the wide ranging hardware capabilities of MExE UE“s, together with the development of ME
48、xE executables, a MExE classification shall be supported to determine their respective capability and compatibility. The MExE classification shall apply both to UE“s, and MExE executables. The objective is to: - classify the capabilities of a MExE UE to support MExE executables; and - identify the c
49、lass of MExE UE on which a MExE executable may be supported. The concept of a MExE Classmark is introduced to manage the MExE UE and MExE executable classification and compatibility. The MExE Classmark is distinct and unrelated to the existing UE Classmark. The use of MExE Classmarks shall be supported during the capability negotiation between the MExE service provider and the MExE UE. 5.2 UE MExE classmarks A given MExE Classmark shall identify a category of MExE UE supporting MExE functionality with a minimum level of processing, memory, display and interactive
