hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
2b997f793085bd3d48236a874636bb22
|
122 140
|
5 General Requirements
|
..............................................................................................................................7
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
5.1 Multimedia message management
|
..................................................................................................................... 7
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
5.2 Multimedia message delivery and submission
|
................................................................................................... 9
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
5.3 Notification and Acknowledgement
|
.................................................................................................................. 9
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
5.4 Addressing
|
......................................................................................................................................................... 9
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
6 Profile
|
......................................................................................................................................................9
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
7 Security
|
..................................................................................................................................................10
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
8 Charging
|
.................................................................................................................................................10
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
9 External Interface
|
...................................................................................................................................10
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
10 Interworking
|
...........................................................................................................................................10 Annex A (informative): Change history...............................................................................................11 ETSI ETSI TS 122 140 V3.1.0 (2000-06) 4 3G TS 22.140 version 3.1.0 Release 1999 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 TR, 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 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. Introduction SMS has been very successful in the GSM second generation system, as all mobiles have supported the application level and it is possible to send to any GSM handset without the need to check for individual support. This easy to use service for non realtime text transmission between GSM users shall be succeeded to in third generation mobile systems by a non real-time Multimedia Message Service, MMS. The MMS will allow users to send and receive messages exploiting the whole array of media types available today e.g. text, images, audio, video while also making it possible to support new content types as they become popular. 3GPP shall not standardise new services themselves, but instead uses the standardised set of service capabilities features on which the new services will be built. Multimedia technology a rapidly developing allowing new capabilities, such as multimedia messages, games, presentations and services that are now considered to be a part of every day life. Multimedia consists of one or more media elements (such as text, voice, image and video), and it is the combination of these media elements in a ordered synchronised manner that creates a multimedia presentation. A non-realtime multimedia message as observed by the user is a combination of one or more different media elements in a multimedia presentation, that can be transferred between users without the requirement for the need to be transferred in realtime. The non-real-time multimedia messaging service shall be capable of supporting current and future multimedia messaging services, and exploit the advances being made in the world multimedia community, with additional mobile requirements. ETSI ETSI TS 122 140 V3.1.0 (2000-06) 5 3G TS 22.140 version 3.1.0 Release 1999 1 Scope This Technical Specification defines the stage one description of the non real-time Multimedia Messaging Service, MMS. Stage one is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber's and service providers' points of view. This TS includes information applicable to network operators, service providers, terminal and network manufacturers. This TS contains the core requirements for the Multimedia Messaging Service, which are sufficient to provide a complete service. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. Such 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. This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:- - multiple media elements per single message - negotiate different terminal and network MM capabilities - notification and acknowledgement of MM related events (e.g. delivery, deletion, ...) - handling of undeliverable MM - flexible charging The above list is not exhaustive. Thus the MMS enables a unified application which integrates the composition, storage, access, and delivery of different kinds of media, e.g. text, voice, image or video in combination with additional mobile requirements. 2 References The following documents contain provisions which, through reference 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. - For a non-specific reference, the latest version applies. [1] 3G TS 22.101 (V3.6.0 onwards): "Service Principles" [2] 3G TS 22.121 (V3.0.0 onwards): "The Virtual home Environment" [3] 3G TS 21.133 (V3.0.0 onwards): "3G Security; Security Threats and Requirements" [4] 3G TS 22.975 (V3.0.0 onwards): "Advanced Addressing" ETSI ETSI TS 122 140 V3.1.0 (2000-06) 6 3G TS 22.140 version 3.1.0 Release 1999 3 Definitions and abbreviations 3.1 Definitions Recipient : the recipient is the entity to which a MM has been sent. Sender : the sender is the entity that sent a MM. User : the user is the MM sender or the MM recipient. message element : a message element is a part of a MM consisting of only one media type. multimedia message : a multimedia message is a message composed of one or more message elements. multimedia message service : A multimedia message service allows transfer of multimedia messages between users without the requirement for the multimedia messages to be transferred in real-time. media types: a media type refers to one form of presenting information to a user, e.g. voice or fax.media formats: within one media type different media formats are applicable for the media presentation, e.g. a picture can be GIF or JPEG format. network : for the purposes of supporting multimedia messaging, the term network shall be considered to include the mobile operator's network and any functionality which may exist outside the mobile operator's network (i.e.fixed, internet and multimedia technologies etc.), and the support provided by that functionality for multimedia messaging. service capabilities features : see Reference [2]. 3.2 Abbreviations For the purposes of this document the following abbreviations apply: MM Multimedia Message MMS Multimedia Message Service SMS Short Message Service 4 High level Requirements The following list gives the high level requirements of the MMS. These are requirements which are independent of the user's perception of the service:- - Forward compatible multimedia messaging Multimedia messaging mechanisms shall provide the capability to support current and evolving multimedia messaging by re-using existing standards as far as possible and proposing extensions (as necessary) to existing standards (i.e. the multimedia messaging service shall support the evolution of multimedia messaging technologies). - Consistent messaging Regardless of the message type / format, MMS shall be capable of supporting integration of all types of messaging (e.g. fax, SMS, Multimedia , voicemail, e-mail etc.) in a consistent manner. - Interoperability The MMS shall support a minimum set of functionality to ensure interoperability. (e.g. deletion of MM, identified standardised message notification, message media types and message content formats) ETSI ETSI TS 122 140 V3.1.0 (2000-06) 7 3G TS 22.140 version 3.1.0 Release 1999 5 General Requirements Network operators have many differing requirements, and MMS shall be supported in the network in a manner which allows network operators to consider different configurations depending on their network and commercial requirements. Thus, an identified set of functionalities and formats shall be standardised to ensure interoperability across networks and terminals to support MMS. However, some network operators may wish to design and configure networks in different ways, and the subsequent requirements are identified to allow flexibility in how the MMS functionality is supported. For example in some networks the network operators may wish to implement the MMS functionality within the core network, whereas other may wish to place the MMS functionality on the periphery of the core network (e.g. a centralised network model instead of a distributed architecture). Further, some network operators may wish to support a limited set of MMS functionality, while others may require extensive and elaborate MMS support according to their business models (e.g. basic MMS instead of advanced MMS). Interoperability shall always be maintained within this flexible architecture. The following sub-clauses use the term "The MMS shall be able to support a request for …" and similar phrases to allow network operators to consider these different network models and business requirements, to permit flexible architectures and ensure MMS interoperability. The following sub-clauses use the term "This requirement shall be supported at the application layer in the terminal (and/or the network), and will not be further elaborated." and similar phrases to identify those service requirements that shall be supported by MMS but do not require standardisation. The criterion for identifying these types of requirements is as follows: If the requirement corresponds to an interaction and/or command between the terminal and the network applications from the same Service Provider (e.g. between the recipient's terminal resident messaging application and the recipient's network resident application. The same applies for the sender), then this requirement shall be supported by MMS but does not require standardisation. The following general requirements shall be supported via the use of service capability features. 5.1 Multimedia message management - Terminal-sensitive MM management The MMS shall be able to support the capability for the terminal and network to take account of the capability of the user's terminal (e.g. deliver a MM / notification in a manner compatible with the terminals capability). - User status-sensitive MM Management The MMS shall be able to support the capability for the terminal and network to take account of the availability, changes of the state of availability of the user (e.g. store messages if the recipient is not available). - MMS Control by the operator The MMS shall be able to support a request from the operator to enable/disable MM delivery and submission. This requirement shall be supported at the application layer in the network, and will not be further elaborated. - MMS Control by the user The MMS shall be able to support a request from the user to enable/disable MM delivery and submission. This requirement shall be supported at the application layer in the terminal, and will not be further elaborated. - Personalise multimedia messaging The MMS shall be able to support a request by the user to manage the Service Preferences of his User Service Profile (e.g. customise his MM environment within the capabilities of the terminal, network and MM application. This could be unconditional or conditional e.g. depending on roaming conditions or operator restrictions). - MM creation ETSI ETSI TS 122 140 V3.1.0 (2000-06) 8 3G TS 22.140 version 3.1.0 Release 1999 The MMS shall be able to support the request to create a MM by the user or an application. This requirement shall be supported at the application layer in the terminal, and will not be further elaborated. - Multiple Media Multimedia messages may be composed of either a single medium (e.g. voice) or multi-media (e.g. Voice and video). The MMS shall be able to support a request for media synchronisation / sequencing. - Media Type Conversion The MMS shall be able to support a request to convert between media types (e.g. Fax to image). This requirement shall be supported at the application layer in the network, and will not be further elaborated. - Media Format Conversion The MMS shall be able to support a request by the user or the application to convert between MM media formats (e.g. JPEG to GIF). This requirement shall be supported at the application layer in the terminal and/or in the network, and will not be further elaborated. - Message forwarding The MMS shall be able to support a request to forward multimedia messages or multimedia message elements without having to first download the MM to the terminal. This requirement shall be supported at the application layer in the network, and will not be further elaborated - Storage of Multi-Media Messages The MMS shall be able to support a request for multimedia messages or message elements to be stored until delivered to the recipient's terminal, until they expire, or until they are deleted by the user (unless configured differently). The MMS shall be able to support a request to store and manage all MMs in a network based repository rather than on the mobile terminal. This requirement shall be supported at the application layer in the network, and will not be further elaborated. Note: There is no requirement for the MMS to be responsible for the processing/presentation of the MM message, after it has been delivered to the terminal. - Prioritisation of Messages The MMS shall be able to support a request for MM prioritisation subject to the capabilities of the network (e.g. the sender of the MM may request to prioritise the importance of the multimedia messages). - Screening of Messages The MMS shall be able to support a request for MM screening subject to the capabilities of the network (e.g. automatically delete "junk mail" without delivery to the recipient's terminal) This requirement shall be supported at the application layer in the network, and will not be further elaborated. - Validity Period The MMS shall be able to support a request to define validity periods for message delivery (e.g. if a message can not be delivered within a certain time it will be deleted). ETSI ETSI TS 122 140 V3.1.0 (2000-06) 9 3G TS 22.140 version 3.1.0 Release 1999 5.2 Multimedia message delivery and submission - Submission mechanism The MMS shall support multimedia messages or messages elements to be submitted to the recipient's terminal. - Push Mechanism The MMS shall be able to support a request for multimedia messages or messages elements to be automatically delivered to the recipient's terminal. - Pull Mechanism The MMS shall be able to support a request for multimedia messages or messages elements to be delivered to the recipient's terminal on request by the recipient. - Concurrency The MMS shall be able to support MM delivery to and from the user's terminal not be restricted during other active services (subject to the capabilities of the terminal and the network). 5.3 Notification and Acknowledgement The MMS shall be able to support a request to send generic notification and acknowledgement capability to inform the user in an appropriate manner of MMS events. Examples may include:- - notify the recipient about received messages (including a description of the message, e.g. content, size, type). - acknowledge the sender about successful or failed MM or storage of a MM. - acknowledge the sender about successful or failed MM submission - acknowledge the sender about successful or failed MM delivery to the recipient terminal. - acknowledge the sender about successful or failed MM deletion. - acknowledge the sender, upon request, about the status of a submitted MM (i.e. delivered / not delivered). 5.4 Addressing The MMS shall support different addressing formats to identify the sender and recipient as specified in 22.975 [4] where applicable. It shall be possible to submit one message to multiple recipients. 6 Profile The MMS shall be able to support the ability to create, update, store, transfer, interrogate, manage and retrieve a user's multimedia messaging profiles. The multimedia messaging profiles shall allow a user to configure and personalise his multimedia messaging environment with the multimedia messaging profiles (e.g. which media types and notifications that shall be delivered to the recipient , such as voice only or text only). The multimedia messaging profiles shall form part of the user's virtual home environment. ETSI ETSI TS 122 140 V3.1.0 (2000-06) 10 3G TS 22.140 version 3.1.0 Release 1999 7 Security The user shall be able to use and access MM in a secure manner. It shall be possible for the contents of MMs to be read only by the intended recipient(s). A recipient shall be informed of the reliability of the identity of the sender in case the sender has authorised his identity to be transmitted. The integrity of MMs during transit shall be assured to extent of the network capabilities. The MMS shall be intrinsically resistant to attempts of malicious or fraudulent use. The "Security Threats and Requirements" specified in 22.133 [3] shall not be compromised. 8 Charging The MMS shall be able to support various charging mechanisms. The following charging characteristics may be considered:- - message types, length, storage time in the network, etc - delivering time, upload / download method, - MM-sender / -recipient - number of messages sent - number of messages received. - roaming conditions - location conditions 9 External Interface The support of xternal interfaces for controlling and delivering MM between the terminal and an external device e.g. portable computer is left for future releases. The standard shall permit interworking with other or existing messaging technologies, messaging services, intelligent network services and supplementary services, either located within or outside a mobile network. ETSI ETSI TS 122 140 V3.1.0 (2000-06) 11 3G TS 22.140 version 3.1.0 Release 1999 Annex A (informative): Change history V. 0.0.1 June 1999 First Draft (Presented at TSG-T-WG2 SWG3 14th – 16th June 99) V. 0.0.2 June 1999 Interim Draft for SWG3 discussion V. 0.0.3 July 1999 Draft version to be submitted to TSG-SA-WG1, 5th – 9th July 99 V. 0.0.4 July 1999 2nd draft for submission to TSG-SA-WG1, 5th – 9th July 1999 V. 0.1.0 July 1999 Version to be submitted to TSG-SA-WG1, 5th – 9th July 99 V. 0.2.0 September 1999 Presented at TSG-T-WG2#5 6th – 9th September 99 V. 0.2.2 September 1999 Version after post TSG-T-WG2#5 discussion / Presentation to S1 V. 0.3.0 September 1999 Version after TSG-SA-WG1 MMS ad-hoc V 0.3.1 September 1999 "3G" and "UMTS" removed to indicate availability to 2G systems Proposed version 1.0.0 Version sent to SA for information V 1.1.0 November 1999 Version after TSG-SA-WG1 MMS AdHoc #2 V 1.2.0 November 1999 Version to be submitted to S1#6 for R`99 approval V 2.0.0 December 1999 Version to be submitted to SA #6 for R`99 approval V 3.0.0 December 1999 Approved at SA #6 for R`99 Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New SP-08 SP-000208 S1-000424 22.140 002 R99 F R99 alignment to stage 2 3.0.0 3.1.0 12 ETSI ETSI TS 122 140 V3.1.0 (2000-06) 3G TS 22.140 version 3.1.0 Release 1999 History Document history V3.0.0 January 2000 Publication V3.1.0 June 2000 Publication
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
2 References
|
................................................................................................................................................6
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
3.2 Abbreviations
|
..................................................................................................................................................... 7
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
4 Description
|
...............................................................................................................................................7 5 Compatibility of MExE MS’s and applications.......................................................................................7
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
5.1 MExE classmarks
|
.............................................................................................................................................. 7
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
5.2 MS MExE classmarks
|
........................................................................................................................................ 8
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
5.3 Application and applet MExE classmarks
|
......................................................................................................... 8
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6 General MExE requirements
|
...................................................................................................................9
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.1 High level MExE requirements
|
......................................................................................................................... 9
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.2 Requirements description from the user's standpoint
|
....................................................................................... 10
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.2.1 User interface configuration management
|
.................................................................................................. 10
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.2.2 Service management
|
.................................................................................................................................. 11 6.3 Requirements description from the MExE service provider’s standpoint........................................................ 11
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.3.1 Transfer of applications, applets and content
|
............................................................................................. 11
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.3.2 Node types
|
.................................................................................................................................................. 11
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.3.3 Subscriber data
|
........................................................................................................................................... 12
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
6.3.4 Roaming subscribers
|
.................................................................................................................................. 12
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
7 MExE bearer requirements
|
....................................................................................................................12
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8 MExE protocols requirements
|
...............................................................................................................12
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.1 Optimised Wireless Access
|
.............................................................................................................................. 13
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.2 Wireless network independence
|
...................................................................................................................... 13
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.3 Scaleable and extendible protocols
|
.................................................................................................................. 13
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.4 Service independence
|
...................................................................................................................................... 13
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.5 Network node type independence
|
.................................................................................................................... 13
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.6 Enquiry and notification of MExE capabilities
|
................................................................................................ 14
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.7 MS request of services information
|
................................................................................................................. 14
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
8.8 Support of transfer protocols
|
........................................................................................................................... 14
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
9 MS application execution environment requirements
|
...........................................................................14
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
9.1 MS platform independence
|
.............................................................................................................................. 14
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
9.2 Document mark-up language and other coding formats
|
.................................................................................. 15
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
9.3 MExE APIs
|
...................................................................................................................................................... 15
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
10 Charging requirements
|
...........................................................................................................................15
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
11 Security requirements
|
............................................................................................................................16
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
11.1 Security Principles
|
........................................................................................................................................... 16
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
11.2 Security Requirements
|
..................................................................................................................................... 16
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
11.3 Security domain classifications
|
........................................................................................................................ 17
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
12 Interworking with other network features
|
..............................................................................................17
|
2f5de03f4dbc68455da6cfc5bff397eb
|
122 057
|
13 Network interworking
|
............................................................................................................................18 Annex A: Change history ..............................................................................................................................19 History..............................................................................................................................................................20 (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 4 3G TS 22.057 version 3.0.1 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; (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 5 3G TS 22.057 version 3.0.1 1 Scope This TS defines the stage one description of the Mobile Station Application 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 human interface itself. This TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers. This TS contains the core requirements for a Mobile Station Application Execution Environment (MExE) which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a Mobile Station Application Execution Environment (MExE) 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. MExE Service Environment MS MExE Scope of this TS Figure 1: Scope of this TS As indicated in Figure 1, the scope of this TS encompasses the MExE functionality in the MS, 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 PLMN. 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. MExE requirements are considered to be applicable to both GSM and UMTS systems. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 6 3G TS 22.057 version 3.0.1 2 References The following documents contain provisions which, through reference 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. • For a non-specific reference, the latest version applies. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: “Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms”. [2] TR 21.905: "Vocabulary for 3GPP Specifications". 3 Definitions and abbreviations 3.1 Definitions For the purposes of this 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 information 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 category of MExE MS 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 MSs. A MExE application or applet defined as being of a specific MExE Classmark indicates that it is supportable by a MExE MS 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 operator may be able to offer support to MExE services in various ways. Examples of possible sources are from traditional GSM 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 PLMN 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 MS to MExE MS interaction of MExE services. MExE service provider: an organisation which delivers MExE services to the subscriber. 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 though other types of networks is out of scope of this specification. subscriber: the term subscriber in the context of this TS refers to a MExE subscriber user: the user of an MExE MS , who may or may not be the subscriber. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 7 3G TS 22.057 version 3.0.1 3.2 Abbreviations For the purposes of this TS the following abbreviations apply: API Application Programming Interface CS Circuit Switched FFS For Further Study 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 SIM Subscriber Identity Module USIM Universal Subscriber Identity Module SP Service Provider Further related abbreviations are given in GSM 01.04 [1] and TR 21.905 [2]. 4 Description MExE provides a standardised execution environment in an MS, and an ability to negotiate its supported capabilities with a MExE service provider, allowing applications to be developed independently of any MS platform. The MS (consisting of the ME and SIM/USIM) can then be targetted at a range of implementations for MExE from small devices with low bandwidth, limited displays, low processor speeds, limited memory, MMI etc., to sophisticated with a complete MExE execution environment. The introduction of MExE execution environment into MSs is a significant step forward in their evolution. The ability of MSs to support MExE applications represents an extension of MSs’ capabilities. In order to allow current and future technologies to exploit and benefit from this, a standardised means of negotiating the MSs’ and network’s capabilities is supported. This negotiation will permit the mutual exchange of capabilities between the MS and the MExE server, and possibly include the service 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 MS, however it need not necessarily be the provider of the MExE services with which the MS’s execution environment is interacting with. The network may also be the intermediary between two MSs which are engaged in a MExE service with each other, with the network effectively supplying the “pipe” and not playing a MExE rôle in the connection. Network nodes, nodes external to the network, or even MSs may be the entities which interacts with the MS’s execution environment. 5 Compatibility of MExE MS’s and applications 5.1 MExE classmarks Given the wide ranging hardware capabilities of MExE MSs, together with the development of MExE applications and applets, a MExE classification shall be supported to determine their respective capability and compatibility. The MExE classification shall apply both to MSs and applications and applets. The objective is to: - classify the capabilities of a MExE MS to support MExE applications and applets; and - identify the class of MExE MS on which a MExE application and applet may be supported. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 8 3G TS 22.057 version 3.0.1 The concept of a MExE Classmark is introduced to manage the MExE MS and MExE application and applet classification and compatibility. The MExE Classmark is distinct and unrelated to the existing MS Classmark. The use of MExE Classmarks shall be supported during the capability negotiation between the MExE service provider and the MExE MS. 5.2 MS MExE classmarks A given MExE Classmark shall identify a category of MExE MS supporting MExE functionality with a minimum level of processing, memory, display and interactive capabilities. Small devices may be considered to be MExE Classmark 1 devices, and contemporary sophisticated devices may be considered to be MExE Classmark 2 devices. The minimum level of capabilities for each MExE Classmark is beyond the scope of this Stage 1 service description. As MS development evolves and more sophisticated devices (or indeed simpler devices) become available, further MS MExE Classmarks shall be definable to identify MS’s capable of supporting improved (or additional) MExE functionality. A given MExE MS Classmark identifies support by a MExE MS for a defined level of MExE functionality, but does not necessairly imply support of other levels of MExE Classmark. A MExE MS may also support multiple MExE Classmarks. 5.3 Application and applet MExE classmarks MExE applications and applets will be developed to execute in one or more classes of MExE MS’s. In order for MExE applications and applets to be properly supported by a MExE MS, the application and applet shall identify the minimum functional capabilities required of a MExE MS, as defined by the MS’s MExE Classmark. MExE applications and applets shall be designated by the same classes of MExE MS’s on which they may be executed. Examples of the classification of MExE applications and applets are as follows:- - MExE Application “A” is defined as a MExE Classmark 1 application; the application is identified as suitable for execution on MExE Classmark 1 MS’s only. - MExE Application “B” is defined as a MExE Classmark 1 and Classmark 2 application; the application is identified as suitable for execution on MExE Classmark 1 and Classmark 2 MS’s only. - MExE Application “C” is defined as a MExE Classmark 2 and Classmark 3 application; the application is identified as suitable for execution on MExE Classmark 2 and Classmark 3 MS’s only. - MExE Application “D” is defined as a MExE Classmark 1, Classmark 2 and Classmark 3 application; the application is identified as suitable for execution on MExE Classmark 1, Classmark 2 and Classmark 3 MS’s. If a MExE application or applet is capable of being supported by other classes of MExE MS’s (with reduced or enhanced capabilities), it is the responsibility of the MExE service provider to re-classify the MExE application or applet accordingly. MExE applications and applets defined by a MExE service provider to a given class of MExE MS, shall be supportable by all MExE MS’s of that class regardless of MExE MS manufacturer. MExE applications and applets shall operate on differing MExE MS of the same MExE MS class without modification. It shall be possible for MExE service providers to make the same MExE applications and applets available in the network for different classes of MExE MS. It is desirable that applications and applets are backward compatible within a given technology and for a given MS Classmark; however such backward compatibility is out of scope of this specification. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 9 3G TS 22.057 version 3.0.1 6 General MExE requirements 6.1 High level MExE requirements The high level requirements of MExE are as follows: - the means for MExE service provider specific services to be supported by all mobiles of a particular class (i.e. the need for a common set of APIs and development tools), and accessible across a range of networks; - provide the user with a more sophisticated user interfaces (e.g. browser-like) with a rich variety of MMI concepts to control and invoke services (i.e. softkeys, icons, voice recognition etc.); - the user’s and MExE service providers capability to control the “look and feel” of applications and applets; - the ability of the user to personalise the user interface; - the ability of the user to personalise services; - provide support of a wide variety of applications and applets; - provide the means for MExE service providers to authenticate MExE subscribers; - provide the user access to Internet and Intranet based applications and applets (via both standard Internet and Wireless optimised protocols); - the means to transfer applications, applets and content automatically or on demand to a MExE MS from a MExE service provider, and upgrade existing applications across the network; - the means to support direct MExE MS to MExE MS interaction of MExE services; - the need for an inherent security architecture such that both the MExE MS and MExE server sides of a connection are authenticated (possibly by a brokerage server), and have access to a range of encryption and security functions in order to maintain the security and integrity of the network. The MExE service provider shall maintain security of subscribers personal data and network data, with all aspects relating to network security being centred on the SIM/USIM; - the ability for the MExE service provider to charge subscribers for MExE service provider provided MExE services, at connect time, when downloading, or on usage; - the means for MExE service provider specific applications and applets on the MExE MS to communicate with applications in the MExE service environment using industry standard protocols (e.g. a MExE server etc); - the ability to provide information to MExE service providers (e.g. location information of MS’ for use with location dependent services); - the means for MExE service providers and their applications and applets to determine MExE MS capabilities (i.e. MExE Classmark, technology, supported bearers according to network capabilities and network subscription etc.). (This shall be used by MExE servers to adapt application and applet transfer to MExE MS capabilities, and shall be used by applications and applets whilst running to adapt their behaviour to the MS’s capabilities.); - the opportunity for MExE service providers to apply expertise and software developed for other platforms; - provision of APIs and tools to develop MExE services which are applicable for MExE MS’; - the means for the user to manage (i.e. identify version, delete, modify, save etc.) the applications, applets and content on the MExE MS; - the means for the user to control acceptance (i.e. by Security Level, level of trust etc.) of applications, applets and content transferred to the MExE MS. (It shall be possible for the user to finely control a trusted application or applet’s access rights on the MExE MS, such as reading/writing/deletion of files stored on the MExE MS); - the means for MExE applications to perform some AT command functionality without compromise to security of MExE as defined in clause 8; (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 10 3G TS 22.057 version 3.0.1 - the means for authentication certificates associated with applications to be managed and stored in the SIM/USIM; - the ability for a MExE application to negotiate the QoS, and the ability to indicate to a MExE application changes in the QoS; - the ability of MExE applications to be notified that handover is about to occur, is occuring or has occurred; - the means for MExE MS manufacturers to download and upgrade their existing codec in a MExE MS. A generic mechanism to download other proprietary software into the execution environment of the MS shall be available to the manufacturer. The downloading of platform independent MExE applications, such as streaming audio, that support multimedia capabilities shall also be possible; - the means for data to be synchronised between the MExE MS and the MExE service environment. Some of the above requirements are subsequently elaborated. 6.2 Requirements description from the user's standpoint MExE provides an improvement in the capabilities of an MS, as well as an extended range of services available to the user from, or via, the network. The user shall have - user interface configuration management; and - service management; of the services offered to him by MExE. 6.2.1 User interface configuration management User interface configuration management refers to the behaviour of the MExE MS, and the ability of the user to modify the MExE MS to behave in the manner he is accustomed to, or wishes the MExE MS to, present itself to the user. It does not refer to the services which interact with the network, but the way in which the MExE MS interacts with the user. Users expect MExE MSs to offer an increasing range of capabilities which need not be ubiquitously present on each MExE MS, depending on the technological limitations of the MExE MS. The user shall be able to manage the user interface configuration of the MExE MS. For example, some user’s may require a voice-controlled MMI, whilst others may have the need for a specialised presentation on the MExE MS display or preset function keys regardless of the application or applet which is running. Management of the user interface configuration will permit a user to move from MExE MS to MExE MS and exploit the technological capabilities of each class of MExE MS, with the use of varying services downloaded from the network, as required. The user shall be able to identify (either directly or indirectly) the user interface configuration he wishes to add, modify or delete on his MExE MS, and shall be offered the means of doing this. This management may be performed, for example, by a configuration capability profile. In taking this action, it shall be possible to determine whether the user interface configuration is already resident on the ME, or whether it requires to be obtained from the SIM/USIM or the network. The modifications which may be requested by the user could result in, for example, differing display characteristics being employed, redefinition of keys, modification of the “look and feel” of the user interface, touch screen facility, extensions to existing functions or the capability to automate some functions. The control of the “look and feel” of MExE applications and applets to customise their level of functionality and appearance may be possible by the MExE service provider, network operator (where the MExE service provider is not the network operator) and the user. The aspects of the application or applet which may be customisable are determined by the MExE service provider as an integral part of the MExE application or applet. The user interface configuration management which is specific to the ME shall be stored on the ME, and user interface configuration management which is generic to ME’s may be stored in the network or on the SIM/USIM. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 11 3G TS 22.057 version 3.0.1 The definition of the user interface configuration management which may be offered to the user is outside the scope of this service description. 6.2.2 Service management MExE shall provide the ability to customise the range of services offered to the subscriber. The subscriber’s ability to configure the services available on the MExE MS shall be dynamic, as the range of services required may differ depending on the network, time and location that the user finds himself in. For example, a subscriber may require access to services offering financial support when attending a business meeting, however later in the day he may need access to travel information and booking facilities when re-arranging his travel home. A common address across all PLMN supporting MExE shall be available, from which the user shall be able to request the range of MExE services available he is registered in, if the PLMN supports MExE. The downloading of services may be autonomously controlled by the MExE MS to update existing service access on the mobile, or to download new services. The management of these services may be defined by the subscriber directly or under the control of the MExE MS’s capabilities organised on the MExE MS (i.e. a user may be particularly interested in unified messaging services, and require the availability of such services to be made available to him). The user shall be able to determine and manage which MExE applications, applets and content may be transferred to the MExE MS (i.e. in terms of their security level, source of the applications etc.), determine and manage which MExE applications, applets and content are currently resident and usable on the MExE MS (e.g. when roaming some services may not be available to the user), and delete MExE applications, applets and content on the MExE MS. The definition of the applications, applets and content which may be offered to the user is outside the scope of this specification. 6.3 Requirements description from the MExE service provider’s standpoint 6.3.1 Transfer of applications, applets and content A common mechanism shall be available to perform the transfer of applications, applets and content between MExE MSs’ and the MExE service provider. The common transfer mechanism shall permit applications, applets and content (according to the appropirate MExE Sercurity Level) to be transferred to the MExE MS. It shall be possible for the MExE service provider to: - transfer applications, applets and content between the MExE MS and the MExE service provider (which may be initiated by either party); - request the version of applications, applets and content on the MExE MS; - identify the MExE MS’ capabilities; - support a request from the MExE MS for information on the (local) services which may be transferred from the network. Some of these functions may be used by the MExE service provider either individually, or together to automatically update previously transferred services. 6.3.2 Node types The introduction of MExE shall enable an expansion of services available to the user from various network node types. The MExE MS shall be able to communicate with the various network node types in the MExE service environment, allowing access to intelligent nodes to process service requests from the MExE MS. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 12 3G TS 22.057 version 3.0.1 Applications in the MExE service environment may interact with, or execute as agents of, an MExE MS application using industry standard protocols. Such interaction does not fall within the scope of MExE, however any MExE MS application that does interact with applications in the MExE service environment must respect the privacy of user data. 6.3.3 Subscriber data Subscription to MExE services shall be logically separate to subscription of network services. A subscriber may have a MExE subscription to multiple MExE service providers. It may also be possible for the subscriber to interrogate such subscription registration (with a suitable means of authorisation), depending on PLMN support. 6.3.4 Roaming subscribers Roaming MExE subscribers shall be able, as far as possible, to access their normal MExE services in their HPLMN. As usual when roaming, it cannot be ensured that the VPLMN can provide the subscriber access to the same MExE services (e.g. applications, applets and content) as he is accustomed to. However, in the VPLMN additional MExE services may be available, depending on network capabilities. Service continuity when roaming is dependent on the availability of the services in the VPLMN, and is outside the scope of this specification. The operation of the transferred applications, applets and content may be location dependent, and their behaviour when in an different location is outside the scope of this specification. The following forms of MExE subscriber roaming are identified:- - roaming between networks (HPLMN ↔ VPLMN); - roaming between visited networks (VPLMN ↔ VPLMN); - regional roaming within a network (within the HPLMN or VPLMN). There may be a need to distinguish between the above types of roaming from a MExE services management perspective, as the operation of location dependent MExE services may be affected when the MExE subscriber roams beyond the boundaries of a PLMN or region. 7 MExE bearer requirements Bearers available to MExE applications depend on those supported by the MExE MS that are available. Wherever available, MExE MS applications shall be supported by bearers from GSM, UMTS and other technologies (e.g. high speed data links provided by digital broadcast infrastructure). MExE applications shall be able to use these bearers in an asymmetric fashion. 8 MExE protocols requirements In order for MExE to be supported over the network, a set of standardised protocols is required to support interaction between the MExE MS and the MExE service environment. As this specification is not required to propose a specific technology, it identifies the MExE protocols requirements from the service subscriber's and user's standpoint. The MExE protocols refers to any protocol layer above the GSM/UMTS bearers, which interfaces between the MExE service environment and the MExE MS. The functional capabilities, information flows, signalling system protocols and switching functions needed to implement the service described in this Stage 1 specification will be identified by subsequent specifications at the Stage 2 and Stage 3 levels. The high level MExE protocols requirements are identified in the subsequent subclauses. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 13 3G TS 22.057 version 3.0.1 8.1 Optimised Wireless Access A primary goal of MExE is to provide access to Internet and Intranet services, the standard Internet applications, security and transport protocols shall be one possible set of MExE protocols which is supported. It is noted that these protocols may not cover all the requirements identified in this specification for all classes of ME’s. A set of application, security and transport protocols optimised for wireless access, and compliant to MExE requirements, shall be specified and form part of the MExE standards. MExE MS’s shall be able to support either or both of these sets of protocols. 8.2 Wireless network independence The upper layers of the MExE protocols shall be independent of the type of underlying wireless network so that applications and applets do not need to take into account the specific nature of networks. In particular, lower layers shall provide a generic access API to network bearers so that application and applet developers do not have to cater for the supported underlying bearers. It shall be possible for applications and applets to request specific bearer services and be notified accordingly if they are not available. The transport layer of the MExE protocols may however be adapted to support the specific features of the underlying bearers. The MExE protocols shall have the ability to use all the underlying bearer services which the MExE MS is capable of supporting. 8.3 Scaleable and extendible protocols The MExE protocols shall support a scaleable and extendible environment for application and applet development in mobile communication devices. It shall provide a set of generic, non-MS or service-dependent, features. Scaleability of the MExE protocols applies to both the MExE MS (e.g. where simple devices do not require the extensive protocols support possibly required by more sophisticated devices) and the network. The MExE protocols shall support both low bandwidth bearers (e.g. SMS, USSD etc.) as well as medium bandwidth bearers (e.g. anything up to 64kb/s, HSCSD, UMTS). The introduction of new bearers shall be supported, allowing applications and applets to automatically benefit from their capabilities. The MExE protocols shall support existing servers and applications and applets, and provide a stable platform for future application development. 8.4 Service independence The MExE protocols shall be independent of the services communicated over the protocols. The modification in the range of services, or addition of new services, offered over the network shall not be restricted by the MExE protocols. 8.5 Network node type independence The MExE protocols shall be independent of the network node type(s) being communicated with over the protocols. The MExE protocols shall support the evolution of network node types in a PLMN. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 14 3G TS 22.057 version 3.0.1 8.6 Enquiry and notification of MExE capabilities The MExE protocols shall support a generic technology-independent means for the notification by the MExE MS to a MExE server, or enquiry from the MExE server to the MExE MS, of the supported MExE capabilities consisting of: - MExE Classmark (mandatory, MExE server ↔ MExE MS); the supported class of MExE MS; - MExE technology (mandatory, MExE server ↔ MExE MS); the supported types of MExE MS technology to support MExE services; - terminal characteristics (optional, MExE MS ¡ MExE server, following MExE server enquiry); further details of the supportable characterstics (i.e. screen size, MMI capabilities, supportable bearer services, toolkits etc. as constrained by the network, terminal, subscription and user preferences). In existing networks it may not be possible to determine the network capabilities (i.e. supported bearers) and subscription options of the subscriber. The above notification by the MExE MS or the MExE server are supported at service initiation, dynamically during the provision of such a service, and following a change in the quality of service (i.e. following a handover, change of network, degradation of service, change in quality of service). The notification mechanism shall flexibly support notification of the MExE MS, and be able to accommodate future evolution of MExE MS equipment. 8.7 MS request of services information The MExE protocols shall support a notification from the PLMN or a request from the MExE MS to the PLMN, for information on the (local) services which may be transferred from the PLMN. The information from the PLMN may take the form of listing the services, or references to a PLMN entity (either internal or external to the PLMN) where the available services may be determined. 8.8 Support of transfer protocols The MExE protocols shall support the capability to transfer new applications and applets to the MExE MS as required. The protocols shall support both user initiated and MExE server initiated transfer of several types of data (content description pages, procedural logic, images, libraries etc.), and be able to indicate the type of data being transferred. Each specific MExE technology shall be support a a standardised transfer mechanism for that MExE technology. 9 MS application execution environment requirements 9.1 MS platform independence In order to support the objectives of MExE, the ME and SIM/USIM is required to have an architecture capable of supporting applications, applets and content in a standardised execution environment, independently of the MExE MS manufacturer. As this specification is not required to propose a specific technology, it identifies the common platform requirements from the service subscriber's and user's standpoint. The limitations of small devices may result in the provision of the full application execution environment only being available in sophisticated devices. The high level execution environment requirements are identified in the subsequent subclauses. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 15 3G TS 22.057 version 3.0.1 9.2 Document mark-up language and other coding formats In order to cater for a wide variety of ME’s with different display and input capabilities, support for both the standard Internet mark-up language and a content description language optimised for small display devices of low bandwith bearers shall be defined with the MExE specifications. Both languages may be implemented on any MExE MS. Standardised ways of coding content (i.e. images, phonebook, calendar etc.) shall be defined, however the support of such standardised content coding is optional. In order to facilitate global use of MExE services, a standardised range of character sets for MExE services requires to be defined, and the capabilities of the user and applications to use them. 9.3 MExE APIs MExE APIs may be defined covering aspects (e.g. Network APIs, Non-network API’s, Terminal APIs etc.) within a given MExE Classmark of MExE MS (ME an/or SIM/USIM), and the MExE MS shall support a core API to support the execution of MExE applications and applets. The core API is a the minimal set of API that is present on all MExE MS’s, providing the MExE execution environment in which applications and applets can execute, and is known as the Core MExE API. The Core MExE API consists of generic and GSM/UMTS specific aspects. Applications and applets which have been designed to execute in this Core MExE API environment (and the optional MExE APIs subsequently identified), will provide additional functions to the MExE MS. In addition to the Core MExE API on an MExE MS, standardised MExE API extensions such as Network API (e.g. access to call control services, SMS etc.), Non-network GSM/UMTS-defined services API (e.g. security aspects, SIM/USIM phonebook etc.), Terminal API (e.g. power management, access to alerting function, phonebook, MMI, smartcard access etc.),shall be subsequently defined and may be supported by the MExE MS in order to further exploit the system capabilities. The standardised MExE API extensions shall include access to mobility information. 10 Charging requirements The use of MExE services shall, at MExE service provider determination, be subject to charging. There are several forms of charging which shall be available to the MExE service provider. It shall be possible for the MExE service provider to charge in the following instances: - subscription; the subscriber’s registration to use MExE services may be subject to a charge; - service transfer; the transfer of services and/or information to a subscriber’s MExE MS may be subject to a charge; - service upgrading; the upgrading of previously transferred services to a subscriber’s MExE MS may be subject to a charge (automated upgrading of services may be subject to a different charge); - service usage; the usage of transferred services by a subscriber’s MExE MS may be subject to a charge (possibly use either internal to, or external to, the MExE MS); - roaming ; the usage of MExE services by a subscriber’s MExE MS when roaming may be subject to additional charges; A standardised means of transferring (indicative and/or final) charging information (for the use of MExE services) from the MExE service provider to the MExE MS shall be defined. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 16 3G TS 22.057 version 3.0.1 The usage of the bearer service may be subject to a charge (i.e. possibly time-based, volume-based, event-based etc.) by the network operator. Normal service charges may additionally apply when using MExE services and incurring the above charges. Other charging requirements may be identified in due course. 11 Security requirements This clause consists of: - a sub-clause giving the principles behind security for MExE. These are not requirements as such but the principles behind the requirements; - a sub-clause specifying specific requirements that MExE implementations must adhere to; - a sub-clause specifying the security domain classifications for MExE executables. 11.1 Security Principles The ME and the data therein are the property of the user. The user is also responsible for the payment of chargeable events involving her MS, and will be seen as the party responsible for any events (whether chargeable or not) involving her MS. Therefore the user shall have full control over all chargeable and non-chargeable events initiated by her MS (“event” includes responses made by the MS to external events, e.g. the acceptance by the MS of an incoming call). This control can be exercised either by the giving of explicit permission at the time of the event or by the giving of implicit permission to the events by the agreement to an event schedule listed clearly in a user profile. The user shall be able to request the logging of specific network events initiated by MExE MS applications/applets. The privacy of user data in the MS is of paramount importance. The SIM/USIM and operator controlled areas within the terminal are the property of the network operator. The network operator shall therefore have full control over access to the SIM/USIM and operator controlled area The operator shall also have full control over data, excluding personal user data, transmitted to or from the SIM/USIM and the operator controlled terminal area and all events initiated by the SIM/USIM or operator controlled area (“event” includes responses made to external events, e.g. the response to a command sent from the ME). As the user cannot know the capabilities of any MExE executables transferred from a MExE service environment before transfer, the MS MExE environment shall ensure that transferred MExE executables cannot compromise the above principles. 11.2 Security Requirements For MExE executables of security operator, manufacturer and user trusted domains , as defined in clause 11.3, it shall be possible to authenticate the identity of the body that authorised the application, applet or content. There shall be a secure, unforgable means for assigning the security domains defined in section 11.3 to the MExE executables transferable from the MExE service environment. The certification of authorisation associated with MExE executables transferable from the MExE service environment shall be transferred with the certified material. The MExE MS shall be able to verify the security domain, as defined in section 11.3, of MExE executables transferred from the MExE service environment. The verification process in the MS itself shall not compromise the security of the functionality and content in the MS Transferred material that fails verification shall not be installed and shall be deleted by the terminal as soon as possible. MExE executables that cannot be verified due to the absence of required verification information in the MS, shall be considered as untrusted material, as defined in section 11.3. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 17 3G TS 22.057 version 3.0.1 The events that MExE executables are given permission by the user to initiate shall be securely recorded in the user profile. There shall be mechanisms within the MExE MS for ensuring that applications cannot have access to MS functionality and content beyond that allowed by their security domain, as defined in section 11.3. It shall be possible to for the user to downgrade MExE executables of operator, manufacturer or user trusted domain status to untrusted status, at installation or at any other time. The MExE MS shall be able to detect if MExE executables transferred from the MExE service environment have been modified since they were assigned a security level. MExE executables shall not be transferred to a MExE MS without the explicit permission of the MS user immediately prior to transfer or implicit permission via the user profile. Applications and applets transferred to a MExE MS shall not be able to initiate events without the explicit permission of the MS user immediately prior to event initiation or implicit permission via the user profile. The user profile data for transfer and event initiation cannot be changed without the explicit agreement of the user. The user shall be able to abort or suspend any on-going call that has been set up automatically by an application. The integrity of the SIM or USIM and other security mechanisms shall not be compromised by the introduction of MExE services. The user shall be able to request the logging of specific network events initiated by MExE MS applications/applets. MExE MS applications/applets shall not be able to send command RUN GSM ALGORITHM to the SIM. 11.3 Security domain classifications The security domain of MExE executables shall be graded according to the measure of authorisation which they have been designated. The following 3 (the “sandbox” in which untrusted MExE executables runs is not considered to be a domain) domains shall be supported for MExE executables: - MExE Security Operator Domain (used by the HPLMN operator); MExE executables designated at this security domain have been authorised by the network operator (i.e. HPLMN), - MExE Security Manufacturer Domain (system MExE executables); MExE executables designated at this security domain have been authorised by the MExE MS manufacturer. - MExE Security User Trusted Domain (trusted applications, applets and content); MExE executables MExE executables designated at this security domain have been written by user trusted software developers and verified as user trusted domain material (but not with regard to their content) via organisations such as certification authorities. - MExE Security Untrusted (untrusted applications, applets and content); Untrusted MExE executables have not been supplied with an associated authorisation, or the authorisation cannot be verified due to the absence of required verification information in the MExE MS. 12 Interworking with other network features All services available in the network shall continue to be offered in addition to MExE. This includes the basic services, supplementary services and network features. It shall be network-determined whether specific MExE services supplement, co-operate with, or supersede the network available services, when a user is subscribed to MExE and has transferred the specific MExE service. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 18 3G TS 22.057 version 3.0.1 The interworking characteristics of individual MExE services with other network features is outside the scope of this specification. All services offered in co-operation with other networks shall continue to be offered in combination with MExE. This includes the basic services, supplementary services and network features. The interworking characteristics of individual MExE services with other networks is outside the scope of this specification. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.057 V3.0.1 (1999-10) 19 3G TS 22.057 version 3.0.1 Annex A: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.57 8.0.0 Transferred to 3GPP SA1 SA#04 22.057 3.0.0 SA#05 22.057 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.057 version 3.0.1 Release 1999) ETSI TS 122 057 V3.0.1 (2000-01) ETSI 20 ETSI ETSI TS 122 057 V3.0.1 (2000-01) (3G TS 22.057 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
1 Scope
|
........................................................................................................................................................5
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
2 References
|
................................................................................................................................................5
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
3 Definitions and abbreviations
|
..................................................................................................................5
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
4 Description
|
...............................................................................................................................................6
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
5 Applicability
|
............................................................................................................................................6
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
6 Normal procedure
|
....................................................................................................................................7
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
6.1 Transfer of NITZ information
|
............................................................................................................................ 7
|
2e5659653c00d88b9b88a5e524b3b03c
|
122 042
|
6.2 Use of NITZ information
|
................................................................................................................................... 7 Annex A: Change history ................................................................................................................................8 History................................................................................................................................................................9 (3G TS 22.042 version 3.0.1 Release 1999) ETSI TS 122 042 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.042 V3.0.1 (1999-10) 4 3G TS 22.042 version 3.0.1 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; (3G TS 22.042 version 3.0.1 Release 1999) ETSI TS 122 042 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.042 V3.0.1 (1999-10) 5 3G TS 22.042 version 3.0.1 1 Scope The present document describes the feature Network Identity and Timezone (NITZ). This feature provides the means for serving PLMNs to transfer current identity, time, Daylight Saving Time and the local timezone to Mobile Stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the Mobile Equipment (ME) or have changed their name since the ME was sold. Additionally time, Daylight Saving Time and timezone information can be utilised by MEs as desired. 2 References The following documents contain provisions which, through reference 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. • For a non-specific reference, the latest version applies. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TR 21.905: "Vocabulary for 3GPP Specifications". [3] TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3". [4] TS 23.038: "Alphabets and Languages". 3 Definitions and abbreviations In addition to the following definitions, abbreviations used in the present document are listed in GSM 01.04 [1] and TR 21.905 [2]. NITZ The feature Network Identity and Timezone as described in the present document. UCS2 Universal Character Set 2 UT Universal Time LTZ Local Time Zone, the offset from UT applying in that locality, including any adjustments for summer time, etc. DST Daylight Saving Time. Adjustment for summer time. (3G TS 22.042 version 3.0.1 Release 1999) ETSI TS 122 042 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.042 V3.0.1 (1999-10) 6 3G TS 22.042 version 3.0.1 4 Description The feature Network Identities and Timezone shall make it possible for a serving PLMN to transfer its current identity, universal time, DST and LTZ to MSs, and for the MS to store and use this information. Each one of these elements is optional. The feature significantly enhances roaming as itenables the accurate indication of network identities that are either newer than the ME or have changed their name since the ME was manufactured or sold. Additionally time and timezone information can be utilised by MEs as desired. When using the default character set (see TS 23.038 [4]), the serving PLMN shall make both a "short" and a "long" name available to the MS. As an alternative or, in addition, to the default character set, the serving PLMN can make a name available in UCS2. The MS shall be free to choose one of these names depending upon its own characteristics and/or limitations, such as those of its display. NOTE: Guidance is sought, particularly from non-European operators, as to whether long and short name is required in UCS2 format. The Network Operator may change the network identity at any time. However the change of network identity need not force immediate transfer of information to the MS. As a network option, it shall be possible to send universal time (UT) by the network. Time information shall include: Year, Month, Day, Hour, Minute, Second, Timezone and DST. The expected accuracy of the time information is in the order of minutes. NOTE: Universal time indicates the time at which this information element (see TS 24.008 [3]) may have been sent by the network. Thus it can be assumed that the accuracy of the time information when it arrives at the MS is usually within a couple minutes. The serving PLMN shall make Local Time Zone (LTZ) available to the MS as an offset from Universal Time in units of 15 minutes. When the LTZ is compensated for DST (summertime), the serving PLMN shall provide a DST parameter to indicate this. The adjustment for DST can be +1h or +2h. For PLMNs which cover more than one timezone, it is assumed that the Network Operator will arrange for boundaries between subsets of the PLMN service area to be approximately aligned with timezone boundaries. When an MS changes Local Time Zone the PLMN is not required to immediately transfer new time zone information. Similarly the PLMN will transfer the LTZ changes arising from summer/winter adjustments when convenient to the network operator. The MS will implement the new time zone information at an appropriate time following receipt. The information passed to MSs supporting the NITZ feature is controlled by the serving PLMN Operator through administrative interaction. The interface necessary to support this administrative interaction is outside the scope of the present document. 5 Applicability Network Identity and Timezone is both an optional network feature and an optional MS feature. The NITZ feature is not intended to replace the existing method of PLMN Indication, nor is it intended to discharge the administration and maintenance of the associated MoU Permanent Document, SE13. (3G TS 22.042 version 3.0.1 Release 1999) ETSI TS 122 042 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.042 V3.0.1 (1999-10) 7 3G TS 22.042 version 3.0.1 6 Normal procedure 6.1 Transfer of NITZ information Network name, time, DST and timezone information can be transferred from the serving PLMN to the MS: 1) Upon registering on the network. 2) When the MS geographically relocates to a different Local Time Zone. 3) When the network changes its Local Time Zone, e.g. between summer and winter time. 4) When the network changes its identity. 5) At any time during a signalling connection with mobile station. Transfer of relevant information shall not unduly consume scarce network resources. Relevant information shall be presented to the MS user at the earliest opportunity. It is expected that the MS will display the most up to date information transferred to it. Switching off the MS should not cause the updated name of the network(s) to be deleted. Removal of the SIM should not cause the updated name of the network(s) to be deleted. However, the number of different network identities retained in the ME is a manufacturer issue. Usage of time information in MS is a ME manufacturer issue. For example, time information can be utilised to time stamp transactions for logging purposes. (3G TS 22.042 version 3.0.1 Release 1999) ETSI TS 122 042 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.042 V3.0.1 (1999-10) 8 3G TS 22.042 version 3.0.1 Annex A: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.42 8.0.0 Transferred to 3GPP SA1 SA#04 22.042 3.0.0 SA#05 22.042 3.0.0 001 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.042 version 3.0.1 Release 1999) ETSI TS 122 042 V3.0.1 (2000-01) ETSI 9 ETSI ETSI TS 122 042 V3.0.1 (2000-01) (3G TS 22.042 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
1 Scope
|
........................................................................................................................................................6
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
2 References
|
................................................................................................................................................6
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
3 Abbreviations and definitions
|
..................................................................................................................6
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
3.1 Abbreviations
|
.......................................................................................................................................................... 6
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
3.2 Definitions
|
............................................................................................................................................................... 7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4 Description
|
...............................................................................................................................................7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.1 General
|
.................................................................................................................................................................... 7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.2 Applicability
|
............................................................................................................................................................ 7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.3 General Bearer Services
|
.......................................................................................................................................... 7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4 Parameters to be indicated and negotiated
|
............................................................................................................... 7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.1 Call set-up
|
.......................................................................................................................................................... 7
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.1.1 T services
|
........................................................................................................................................................... 8
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.1.2 NT services
|
........................................................................................................................................................ 8
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.2 Network initiated modification
|
.......................................................................................................................... 8
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.2.1 T services
|
........................................................................................................................................................... 8
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.2.2 NT services
|
........................................................................................................................................................ 8
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.3 User initiated modification
|
................................................................................................................................ 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.3.1 T services
|
........................................................................................................................................................... 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.4.3.2 NT services
|
........................................................................................................................................................ 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.5 Air Interface Resource Allocation
|
........................................................................................................................... 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.5.1 Minimum GERAN Air Interface Resource Allocation a
|
nd Allocation Increment ............................................ 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.5.2 Flexible Air Interface Resource Allocation
|
....................................................................................................... 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.6 Symmetric and asymmetric connections
|
................................................................................................................. 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.6.1 Symmetric connections
|
...................................................................................................................................... 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.6.2 Asymmetric connections
|
.................................................................................................................................... 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.6.2.1 Asymmetric air interface connection
|
................................................................................................................. 9
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.6.2.2 Channel coding asymmetry
|
.............................................................................................................................. 10
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.6.3 Network choice of connection symmetry
|
........................................................................................................ 10 4.7 User Equipment/Mobile Equipment requirements ................................................................................................ 10
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.8 Mobility Management
|
........................................................................................................................................... 10
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.9 Roaming
|
................................................................................................................................................................ 10
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10 Quality of Service
|
............................................................................................................................................ 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.1 Bit error rate
|
..................................................................................................................................................... 11 4.10.1.1 GERAN TCH/F Bit Error Rate .................................................................................................................. 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.1.2 Overall GBS Bit Error Rate
|
....................................................................................................................... 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.2 GERAN Radio resource management
|
............................................................................................................. 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.3 Call set-up delay
|
.............................................................................................................................................. 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.4 End-to-end delay
|
.............................................................................................................................................. 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.5 Throughput
|
...................................................................................................................................................... 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.10.6 Network planning and interference levels
|
....................................................................................................... 11 4.11 Mapping of FNUR to GERAN TCH/F for T services ..................................................................................... 11 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services .................................................................... 11
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.13 GBS MMI aspects
|
............................................................................................................................................ 12
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.14 GBS Subscription aspects
|
................................................................................................................................ 12
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.15 GBS charging aspects
|
...................................................................................................................................... 12
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.16 O and M aspects
|
............................................................................................................................................... 12
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
4.17 Multislot security aspects
|
................................................................................................................................. 12
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
5 Exceptional procedures or unsuccessful outcome
|
.................................................................................13
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.