Add files using upload-large-folder tool

marked/Rel-11/21_series/21111/raw.md

@@ -0,0 +1,500 @@
+
+
+
+
+
+
+# Contents
+
+|                                                              |    |
+|--------------------------------------------------------------|----|
+| Foreword .....                                               | 5  |
+| 1 Scope.....                                                 | 6  |
+| 2 References.....                                            | 6  |
+| 2.1 Normative references .....                               | 6  |
+| 2.2 Void.....                                                | 7  |
+| 3 Definitions, symbols and abbreviations.....                | 7  |
+| 3.1 Definitions.....                                         | 7  |
+| 3.2 Void.....                                                | 7  |
+| 3.3 Abbreviations .....                                      | 7  |
+| 4 General requirements .....                                 | 7  |
+| 5 Security requirements .....                                | 7  |
+| 5.1 File access conditions.....                              | 8  |
+| 5.2 User authentication.....                                 | 8  |
+| 5.3 User data stored in ME.....                              | 8  |
+| 5.4 Authentication .....                                     | 8  |
+| 5.5 Data integrity of signalling elements .....              | 9  |
+| 5.6 User identity confidentiality.....                       | 9  |
+| 5.7 Length of security parameters .....                      | 9  |
+| 6 Logical issues.....                                        | 9  |
+| 6.1 Application selection.....                               | 9  |
+| 6.2 Simultaneous access.....                                 | 9  |
+| 7 Service Requirements .....                                 | 9  |
+| 7.1 Void.....                                                | 9  |
+| 7.2 Data transfer .....                                      | 9  |
+| 7.3 Application execution environment .....                  | 10 |
+| 7.4 Profile exchange.....                                    | 10 |
+| 7.5 Version identification.....                              | 10 |
+| 8 Physical Characteristics .....                             | 10 |
+| 8.1 Void.....                                                | 10 |
+| 8.2 Void.....                                                | 10 |
+| 9 Electrical characteristics and transmission protocols..... | 10 |
+| 9.1 Void.....                                                | 11 |
+| 10 Contents of the Elementary Files.....                     | 11 |
+| 10.1 USIM information storage requirements.....              | 11 |
+| 10.2 Phone Book .....                                        | 11 |
+| 10.2.1 Support of two name fields per entry .....            | 12 |
+| 10.2.2 Support of multiple phone numbers per entry .....     | 12 |
+| 10.2.3 Support of email address .....                        | 12 |
+| 10.2.4 Support of user definable groupings.....              | 12 |
+| 10.2.5 Support of hidden entries.....                        | 12 |
+| 10.2.6 Number of entries .....                               | 12 |
+| 10.2.7 Void.....                                             | 12 |
+| 10.3 Storage of call details .....                           | 12 |
+| 10.4 Void.....                                               | 13 |
+| 11 3G/GSM interworking .....                                 | 13 |
+| 11.1 Void.....                                               | 13 |
+| 11.2 3G subscribers in a GSM network .....                   | 13 |
+| 12 Contact Manager.....                                      | 13 |
+| Annex A (informative): Change history.....                   | 16 |
+
+# --- 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 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 document.
+
+# --- 1 Scope
+
+This document defines the requirements of the USIM (Universal Subscriber Identity Module) and the IC card for 3G (UICC). These are derived from the service and security requirements defined in TS 22.100 [1] and TS 22.101 [2]. The USIM is a 3G application on an IC card. It inter-operates with a 3G terminal and provides access to 3G services. This document is intended to serve as a basis for the detailed specification of the USIM and the UICC, and the interface to the 3G terminal.
+
+# --- 2 References
+
+## 2.1 Normative 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
+
+- [1] 3GPP TS 22.100 v3.x.x: "UMTS phase 1" (Release 99).
+- [2] 3GPP TS 22.101: "Service principles".
+- [3] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics".
+- [4] Void.
+- [5] ETSI TS 101 220: "ETSI Numbering System for AIDs".
+- [6] 3GPP TS 31.111: "USIM Application Toolkit (USAT)".
+- [7] 3GPP TS 33.102: "3G Security: Security Architecture".
+- [8] 3GPP TS 51.011, Rel-4: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
+- [9] Void.
+- [10] Void.
+- [11] ISO/IEC 7816-3: "Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 3: Electronic signals and transmission protocols".
+- [12] ISO/IEC 7816-4: "Identification cards - Integrated circuit cards, Part 4: Organization, security and commands for interchange".
+- [13] Void.
+
+## 2.2 Void ---
+
+# 3 Definitions, symbols and abbreviations ---
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definitions apply:
+
+## 3.2 Void
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                          |
+|------|------------------------------------------|
+| ADN  | Abbreviated Dialling Number              |
+| ATR  | Answer To Reset                          |
+| DF   | Dedicated File                           |
+| EF   | Elementary File                          |
+| ICC  | Integrated Circuit Card                  |
+| IK   | Integrity Key                            |
+| IMSI | International Mobile Subscriber Identity |
+| ME   | Mobile Equipment                         |
+| MF   | Master File                              |
+| PIN  | Personal Identification Number           |
+| PPS  | Protocol and Parameter Selection         |
+| SIM  | Subscriber Identity Module               |
+| USIM | Universal Subscriber Identity Module     |
+
+# --- 4 General requirements
+
+The UICC shall be a removable hardware module. The USIM on a UICC shall contain an identity which unambiguously identifies a subscriber.
+
+For access to 3G services, a UICC containing a valid USIM shall be present at all times, other than for emergency calls.
+
+The specifications shall support the security requirements as defined in 3GPP TS 33.102 [7].
+
+The USIM shall provide storage for subscription and subscriber related information.
+
+The UICC/USIM may also contain applications which use the features defined in the USIM Application Toolkit specification 3GPP TS 31.111 [6].
+
+# --- 5 Security requirements
+
+The USIM shall be used to provide security features. If the UICC is removed from the 3G terminal, the service shall be terminated immediately. The functions of the USIM include authenticating itself to the network and vice versa, authenticating the user and providing additional security functions as defined in 3GPP TS 33.102 [7].
+
+The USIM shall be unambiguously identified.
+
+Means shall be provided to prevent fraudulent use of stolen UICCs.
+
+It shall not be possible to access data intended for USIM internal use, e.g. authentication keys.
+
+Further details of the following requirements are given in 3GPP TS 33.102 [7].
+
+## 5.1 File access conditions
+
+Actions, such as READ, UPDATE on UICC data shall be controlled by access conditions. These shall be satisfied prior to the action being performed.
+
+Since a UICC may contain multiple (3G and non-3G) applications, a flexible method of controlling file access shall be provided.
+
+## 5.2 User authentication
+
+The USIM shall support means to authenticate the user, to provide, for example, protection against the use of stolen cards. For the USIM, authentication shall be performed by the verification of a numeric PIN of four (4) to eight (8) decimal digits.
+
+A function to disable user authentication may exist which may be inhibited by the application provider, in which case the user shall always use the PIN. Otherwise, the user may decide whether or not to make use of the user authentication function. If disabled, the user authentication function remains disabled until the user specifically re-enables it.
+
+Following correct PIN presentation, the ME may perform functions and actions on USIM data, which are protected by the relevant access condition.
+
+If an incorrect PIN is entered, an indication shall be given to the user. After three (3) consecutive incorrect entries the relevant PIN is blocked, i.e. functions and actions on data protected by the access condition shall no longer be possible, even if between attempts the UICC has been removed, the USIM has been deselected or the ME has been switched off. Once a PIN is blocked, further PIN verifications shall be denied.
+
+The USIM shall support a mechanism for unblocking a blocked PIN. Unblocking of a PIN is performed by using the relevant PIN Unblocking Key.
+
+PINs, but not Unblock PINs, shall be changeable by the user following correct entry of either the current PIN or Unblock PIN.
+
+The Unblock PIN shall consist of eight (8) decimal digits and shall not be changeable by the user. If an incorrect Unblock PIN is presented, an indication shall be given to the user. After ten (10) consecutive incorrect entries, the Unblock PIN shall be blocked, even if between attempts the UICC has been removed, the USIM has been deselected or the ME has been switched off. Unblocking of a blocked PIN shall not be possible.
+
+It shall not be possible to read PINs or Unblock PINs.
+
+## 5.3 User data stored in ME
+
+Subject to the exception below, all user related information transferred into the ME during network operations shall be deleted from the ME after removal of the UICC, deselection of the USIM, deactivation of the ME, or following an electrical reset of the UICC. This includes any data that was transferred to the ME by USIM Application Toolkit commands.
+
+User related security codes such as PIN and Unblock PIN may only be stored by the ME during the procedures involving such a code and shall be discarded by the ME immediately after completion of the procedure.
+
+Optionally, an ME may retain some less security-sensitive data at UICC removal, USIM deselection or ME switch-off. Such data are e.g. SMS, ADN/SSC, FDN/SSC, LND. These data, when stored in the ME, shall only be readable/retrievable if the same USIM is reactivated (as determined by the IMSI). If the IMSI is retained in the ME for this purpose, it shall be stored securely and shall not be able to be read out.
+
+## 5.4 Authentication
+
+A means shall be specified to mutually authenticate the USIM and the network by showing knowledge of a secret key K which is shared between and available only to the USIM and in the user's Home Environment. The method is composed of a challenge/response and key establishment protocol combined with a sequence number-based one-pass protocol for network authentication.
+
+## 5.5 Data integrity of signalling elements
+
+Some signalling information elements are considered sensitive and must be integrity protected. An integrity function shall be applied on certain signalling information elements transmitted between the ME and the network.
+
+The 3GPP Integrity Algorithm (UIA) is used with an Integrity Key (IK) to compute a message authentication code for a given message. The setting of IK is triggered by the authentication procedure. IK shall be stored on the USIM.
+
+## 5.6 User identity confidentiality
+
+A mechanism shall be specified to provide user identity confidentiality by means of a temporary identity.
+
+## 5.7 Length of security parameters
+
+In order to allow for enhancements of the security level in 3G, the following requirements shall be covered:
+
+- all security-related parameters for 3G shall be accompanied by a length indicator;
+- the USIM shall support variable-length security parameters.
+
+If the USIM supports the GSM security mechanisms in addition to 3G security, fixed length security parameters according to 3GPP TS 51.011 [8] shall be supported in addition.
+
+# --- 6 Logical issues
+
+## 6.1 Application selection
+
+In a multiapplication environment, a flexible application selection method is required. The application identifier defined in ETSI TS 101 220 [5] should be used for application selection. Direct application selection, including selection by partial DF name and the EF<sub>DIR</sub> concept of ISO/IEC 7816-4 [12] shall be followed. In particular, a mechanism for the ME and the UICC shall be specified in order to allow the user, when the ME is in idle mode, to select and activate one application amongst those which are available and supported by the ME (this will permit the user to choose, for instance, between 2 different USIM applications). At switch on, the last active USIM shall be automatically selected. The last active USIM shall be stored on the UICC. By default if there is no last active USIM defined in the UICC, the user shall be able to select the active USIM amongst those available on the UICC.
+
+## 6.2 Simultaneous access
+
+A mechanism shall be specified for simultaneous access to several files or applications.
+
+# --- 7 Service Requirements
+
+## 7.1 Void
+
+## 7.2 Data transfer
+
+A mechanism allowing highly secure transfer of applications and/or associated data to/from the UICC/USIM shall be specified in line with the requirements in 3GPP TS 22.101 [2]. This requires a secure transfer mechanism.
+
+## 7.3 Application execution environment
+
+An application execution environment may exist on the UICC/USIM which includes functionality defined in 3GPP TS 31.111 [6].
+
+## 7.4 Profile exchange
+
+A mechanism for the ME, the USIM and the network to exchange service capabilities shall be specified. The following exchange of service capabilities may occur:
+
+- ME services capabilities may be provided to the USIM/UICC;
+- USIM/UICC services capabilities may be provided to the ME (and thus potentially to the network);
+- network services capabilities may be provided to the USIM/UICC via the ME.
+
+## 7.5 Version identification
+
+A means for identification of the version of the USIM shall be provided.
+
+# --- 8 Physical Characteristics
+
+The physical characteristics shall be in accordance with the specifications in 3GPP TS 31.101 [3].
+
+## 8.1 Void
+
+## 8.2 Void
+
+# --- 9 Electrical characteristics and transmission protocols
+
+Electronic signals and transmission protocols shall be in accordance with the specifications in 3GPP TS 31.101 [3].
+
+The electrical specifications shall at least cover the 1.8V and 3V voltage ranges as specified in 3GPP TS 31.101 [3]. Lower voltages may be added in the future. 3G terminals shall not support 5V on the ME-UICC interface. Both ME and UICC shall support operational class indication as defined in ISO/IEC 7816-3 [11].
+
+Both ME and UICC shall support at least two voltage classes.
+
+Both UICC and ME shall support PPS as defined in ISO/IEC 7816-3 [11] with at least the values defined in 3GPP TS 31.101 [3].
+
+The ME shall have the capabilities of initiating a warm reset as defined in ISO/IEC 7816-3 [11]. The UICC shall support warm reset as defined in ISO/IEC 7816-3 [11].
+
+NOTE: The warm reset is used during a session when there is a need to restart the USIM due to internal modifications of data caused by user actions or network data downloading.
+
+The UICC may indicate in the ATR to the warm reset that the specific mode is entered automatically, using the parameters that were used prior to the warm reset. In case of a cold reset, the UICC shall enter the negotiable mode.
+
+In addition to the T=0 protocol which is mandatory for the UICC and the ME, the T=1 protocol shall be mandatory for the ME. It is optional for the UICC.
+
+The speed enhancement as specified in 3GPP TS 31.101 [3] shall be supported by both the ME and the UICC.
+
+## 9.1 Void
+
+# --- 10 Contents of the Elementary Files
+
+## 10.1 USIM information storage requirements
+
+The USIM shall contain information elements for 3G network operations. The USIM may contain information elements related to the subscriber, 3G services and home environment or service provider related information.
+
+The UICC shall provide storage capability for the following:
+
+- UICC related information:
+  - IC card identification: a number uniquely identifying the UICC and the card issuer;
+  - Preferred language(s);
+  - Directory of applications.
+
+- USIM related information:
+  - Administrative information: indicates mode of operation of the USIM, e.g. normal, type approval;
+  - USIM service table: indicates which optional services are provided by the USIM;
+  - IMSI;
+  - Language indication;
+  - Location information;
+  - Cipher key (Kc) and cipher key sequence number;
+  - Access control class(es);
+  - Forbidden PLMNs;
+  - Ciphering Key for GPRS;
+  - GPRS location information;
+  - Cell Broadcast related information;
+  - Emergency call codes;
+  - Phone numbers (ADN, FDN, SDN);
+  - Short messages and related parameters;
+  - Capability and Configuration parameters;
+  - Higher Priority PLMN search period;
+  - list of carrier frequencies to be used for cell selection.
+- Information accessible to the USIM and other applications:
+  - ADN.
+
+In addition, the USIM shall manage and provide storage for the following information in accordance with the security requirements of clause 5:
+
+- PIN;
+- PIN enabled/disabled indicator;
+- PIN error counter;
+- Unblock PIN;
+- Unblock PIN error counter;
+- Data integrity keys;
+- Subscriber authentication keys.
+
+## 10.2 Phone Book
+
+A Phone Book entry consists of a record in an ADN file and, optionally, additional records which are placed in different EFs. In the latter case, a mechanism shall be defined to link all records in the same Phone Book entry. These features shall be supported by the ME while their support by the UICC is optional.
+
+### 10.2.1 Support of two name fields per entry
+
+The support of two name fields per entry shall be specified to allow, for example, for two different representations of the same name (for example, in Japanese characters and in Latin characters).
+
+### 10.2.2 Support of multiple phone numbers per entry
+
+The support of multiple phone numbers per entry shall be specified, for example, office, home, fax, mobile or pager. In addition to that, information for identifying those attributes are needed.
+
+### 10.2.3 Support of email address
+
+The support of email addresses linked to Phone Book entries shall be specified. In addition to that, information for identifying these addresses is needed.
+
+### 10.2.4 Support of user definable groupings
+
+The specification shall support the grouping of Phone Book entries into groups defined by the user, for example,
+
+business and private.
+
+### 10.2.5 Support of hidden entries
+
+The specification shall support means of marking Phone Book entries as "hidden".
+
+### 10.2.6 Number of entries
+
+The specification shall support storage of at least 500 entries.
+
+### 10.2.7 Void
+
+## 10.3 Storage of call details
+
+The specification shall support provision of storage for call detail information. The call detail information consists of the following attributes:
+
+- mobile terminated calls:  
+calling party number, date and time, calling party's name and status of call (i.e. answered or missed), duration;
+- mobile originated calls:  
+called party number, date and time, called party's name and duration;
+- accumulated duration of preceding calls, separately for mobile originated and mobile terminated calls.
+
+Call detail attributes are optional. A value to mark them as "undefined" shall be available.
+
+NOTE 1: The calling/called party's name may be available from the Phone Book.
+
+## 10.4 Void ---
+
+# 11 3G/GSM interworking
+
+## 11.1 Void
+
+## 11.2 3G subscribers in a GSM network
+
+3GPP TS 22.101 [2] requires that UMTS shall provide some mechanisms which permit UMTS subscribers to roam easily onto pre-UMTS systems and access the services.
+
+Thus, the specification shall allow the UICC to be used with a dual mode (GSM/ 3G) ME and a GSM ME for the provision of GSM service.
+
+---
+
+# 12 Contact Manager
+
+## 12.1 General
+
+The Contact Manager provides an interface for the management of contact information including rich content without any structural limitations.
+
+There shall be a mechanism for the ME to detect that the UICC containing the Contact Manager has changed. This mechanism may be used by the ME to ask the user whether synchronization of data between the ME and the UICC Contact Manager should occur.
+
+This section defines the functional requirements of the Contact Manager. An ME and a 3GPP application supporting the Contact Manager shall comply with all these requirements.
+
+## 12.2 Security requirements
+
+The Contact Manager may contain personal information. It shall be possible to restrict the access to this information to authorized users or entities (e.g. by binding the access to the verification of the USIM PIN).
+
+### 12.4.3 Interworking with the 3G Phone Book
+
+In case both the ME and the 3GPP application support both the 3G Phone Book (i.e. as defined in section 10.2 of the present document) and the Contact Manager the Contact Manager shall be used. There shall be a mechanism for the 3GPP application to indicate the support of the Contact Manager.
+
+### 12.4.4 Content description
+
+#### 12.4.4.1 Number of contacts
+
+The Contact Manager specification shall not unreasonably restrict the number of contacts.
+
+#### 12.4.4.2 Contact structure
+
+The Contact Manager shall consist of contacts, which are made up of various fields (e.g. phone number, name, photo). A filtering mechanism according to OMA DS Field Filtering shall be supported.
+
+It shall be possible to have several instances of a field in a contact when appropriate (e.g. a contact may have two fax numbers).
+
+An extensible coding scheme shall be defined which allows to describe a contact including all its fields. An existing scheme (e.g. "vcard") shall be used, if appropriate.
+
+A minimum set of field types recognised by the 3GPP application and the ME shall be defined (e.g. name, phone number, URL, Email address, address, sound, pictures, notes).
+
+It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a contact (e.g. photo, logo, video, ring tone, voice tag).
+
+It shall be possible to associate an icon or a label to each contact field type (e.g. associate an icon representing a phone to the number field. "Home address" could be configured as the label of the "mailing address" field type).
+
+It shall be possible to configure the structure and the display order of the contact fields (e.g. first name then Instant Messaging address then number, etc) depending on ME capabilities.
+
+#### 12.4.4.3 Group management
+
+It shall be possible to define new groups (e.g. My Tennis Club).
+
+It shall be possible to pre-define groups (e.g. Friend, Work, Family and VIP).
+
+It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a group (e.g. photo, logo, video, ring tone, icon).
+
+It shall be possible to bind contacts to one or several groups.
+
+#### 12.4.4.4 User Action Management
+
+It shall be possible to configure a list of possible actions that could be proposed to the user when the contact is selected (e.g. Launch Browser, Send SMS, Send MMS, Instant messaging, Make a voice over IP call, Make a video call, Make a conference call, Game player, Send Email).
+
+### 12.4.5 Interface capabilities description
+
+An external and an internal interface to the Contact Manager shall be defined.
+
+The external interface between the Contact Manager and a UICC external entity, i.e. the ME, shall rely on a transport protocol layer that is independent of the physical interface (i.e. the ISO interface and the new high-speed interface).
+
+This is to allow the definition of one solution that can use either the existing ISO interface or the new high-speed interface. The external interface definition shall also ease interfacing the PC applications with the Contact Manager.
+
+Both the ME and the UICC shall be capable of initiating contact information synchronization based on a configurable policy. The internal interface allows other UICC resident applications to access the Contact Manager e.g. through a dedicated API. This enables the creation of additional services utilizing the Contact Manager data and properties. There shall be a mechanism for the user to allow or prevent remote access to the Contact Manager.
+
+The external and internal interface shall provide means to:
+
+- identify Contact Manager capabilities
+- perform the following operations on a contact or a group: create, retrieve, modify, delete, search
+
+In addition the internal interface shall provide mechanisms to:
+
+- register/deregister an UICC resident application to the Contact Manager.
+- allow a resident UICC application to access Contact Manager data and properties based on user permission.
+- allow the Contact Manager to notify events to registered UICC application and to pass event related information when applicable. Events notifying the applications shall include:
+  - contact information is modified locally
+  - contact information is modified remotely
+  - change of contact manager configuration
+
+### 12.4.6 Efficient browsing and searching
+
+The Contact Manager interfaces should allow efficient searching and browsing of the contacts (i.e. the user experience browsing the Contact Manager should be acceptable).
+
+### 12.4.7 Associated services
+
+#### 12.4.7.1 Memory management
+
+It shall be possible to determine the number of stored contacts and the amount of the available and used Contact Manager memory.
+
+# Annex A (informative): Change history
+
+The table below indicates all change requests that have been incorporated into the present document since it was initially approved by 3GPP TSG T and subsequently 3GPP TSG CT.
+
+| Change history |       |             |      |     |     |                                                                                                                                                                         |        |        |
+|----------------|-------|-------------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.    | CR   | Rev | Cat | Subject/Comment                                                                                                                                                         | Old    | New    |
+| 1999-06        | TP-03 | TP-99085    |      |     |     | Draft specification first approved at TSG-T #3                                                                                                                          | 2.0.0  | 3.0.0  |
+| 1999-12        | TP-06 | TP-99255    | 001  |     | D   | References to new specifications and editorial changes                                                                                                                  | 3.0.0  | 3.0.1  |
+| 2000-04        | TP-07 | TP-000017   | 002  |     | F   | Location of the UIA (3GPP integrity algorithm) aligned with 33.102                                                                                                      | 3.0.1  | 3.1.0  |
+| 2000-07        | TP-08 | TP-000097   | 003  |     | F   | Clarification of USIM application selection                                                                                                                             | 3.1.0  | 3.2.0  |
+|                |       | TP-000097   | 004  |     | F   | Alignment with 33.102: removal of Enhanced User Identity Confidentiality (EUIC) from R99                                                                                |        |        |
+| 2000-10        | TP-09 | TP-000150   | 005  |     | F   | Partial AID selection requirements                                                                                                                                      | 3.2.0  | 3.3.0  |
+| 2001-03        | TP-11 | -           | -    |     |     | Issued as version 4.0.0 in order to create a complete set of specifications for release 4. The contents of version 4.0.0 are identical to the contents of version 3.3.0 | 3.3.0  | 4.0.0  |
+| 2002-06        | TP-16 | -           | -    |     |     | Issued as version 5.0.0 in order to create a complete set of specifications for release 5. The contents of version 5.0.0 are identical to the contents of version 4.0.0 | 4.0.0  | 5.0.0  |
+| 2002-09        | TP-17 | TP-020208   | 009  |     | A   | Clarification on the use of the USIM and the SIM                                                                                                                        | 5.0.0  | 5.1.0  |
+| 2004-03        | TP-23 | TP-040023   | 010  |     | C   | Update with respect to the third form factor and removal of an unused reference                                                                                         | 5.1.0  | 6.0.0  |
+| 2004-06        | TP-24 | TP-040100   | 011  |     | D   | Release 6 alignment                                                                                                                                                     | 6.0.0  | 6.1.0  |
+| 2005-06        | CT-28 | CP-050136   | 015  |     | A   | ISO/IEC 7816-Series Revision                                                                                                                                            | 6.1.0  | 6.2.0  |
+| 2006-05        | CT-32 | CP-060349   | 0017 | 1   | F   | Review of TS 21.111, USIM and IC Card Requirements                                                                                                                      | 6.2.0  | 6.3.0  |
+| 2006-09        | CT-33 | action item | -    |     | -   | MCC to raise spec to Rel-7                                                                                                                                              | 6.3.0  | 7.0.0  |
+| 2007-03        | CT-35 | CP-070070   | 0019 | 2   | B   | Requirements for the Enhanced USIM phonebook                                                                                                                            | 7.0.0  | 8.0.0  |
+| 2007-10        |       |             |      |     |     | Editorial correction to cover page                                                                                                                                      | 8.0.0  | 8.0.1  |
+| 2007-12        | CT-38 | CP-070839   | 0020 | 2   | B   | Completion of the requirements for the Enhanced USIM phonebook<br>Renaming of the feature to Contact Manager.<br>Contact Manager moved to a dedicated section           | 8.0.1  | 8.1.0  |
+| 2008-05        | CT-40 | CP-080384   | 0023 | 2   | F   | Update and correct references and pointers to references                                                                                                                | 8.1.0  | 8.2.0  |
+| 2009-12        | CT-46 | CP-091042   | 0025 | 2   | F   | References update                                                                                                                                                       | 8.2.0  | 8.3.0  |
+| 2009-12        | CT-46 | -           | -    | -   | -   | Upgrade of the specification to Rel-9                                                                                                                                   | 8.3.0  | 9.0.0  |
+| 2011-03        | SP-51 | -           | -    | -   | -   | Upgrade of the specification to Rel-10                                                                                                                                  | 9.0.0  | 10.0.0 |
+| 2012-09        | SP-57 | -           | -    | -   | -   | Upgrade of the specification to Rel-11                                                                                                                                  | 10.0.0 | 11.0.0 |
+| 2012-10        |       | -           | -    | -   | -   | Remove hidden text                                                                                                                                                      | 11.0.0 | 11.0.1 |

marked/Rel-11/21_series/21202/raw.md

@@ -0,0 +1,261 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                     |           |
+|-------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                      | 4         |
+| 1 Scope.....                                                                        | 5         |
+| 2 References.....                                                                   | 5         |
+| 3 Definitions, symbols and abbreviations .....                                      | 5         |
+| 3.1 Definitions.....                                                                | 5         |
+| 3.2 Symbols.....                                                                    | 5         |
+| 3.3 Abbreviations .....                                                             | 5         |
+| 4 General.....                                                                      | 5         |
+| 5 Specifications and Reports.....                                                   | 6         |
+| <b>Annex A (informative): (void).....</b>                                           | <b>9</b>  |
+| <b>Annex M (informative): IMS related Specifications and Reports in 3GPP2 .....</b> | <b>10</b> |
+| <b>Annex C (informative): Change history.....</b>                                   | <b>12</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater 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 document.
+
+# --- 1 Scope
+
+The present document identifies the 3GPP Technical Specifications and Technical Reports specifically relating to the Common IP Multimedia Subsystem (IMS) maintained by 3GPP. Standards organizations adopting the Common IP Multimedia Subsystem (IMS) might not need to use all listed specifications.
+
+# --- 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] 3GPP TR 21.900: "Technical specification group working methods"
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
+
+## 3.2 Symbols
+
+(None)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|        |                                                                                        |
+|--------|----------------------------------------------------------------------------------------|
+| NGN    | Next Generation Network                                                                |
+| R1     | Release 1                                                                              |
+| R2     | Release 2                                                                              |
+| TISPAN | Telecommunications and Internet converged Services and Protocols for Advanced Networks |
+
+# --- 4 General
+
+The numbering scheme for specifications is described in 3GPP TR 21.900 [2].
+
+# 5 Specifications and Reports
+
+NOTE 1: The "for publication?" column of the table below indicates whether or not the documents are intended for adoption by the partner Standards Development Organizations as their own publications. Those marked "no" are internal working documents of the 3GPP TSGs.
+
+NOTE 2: "Type" indicates Technical Specification (TS) or Technical Report (TR).
+
+The table below contains all Common IMS specs pertaining to Release 11.
+
+| Type | Number | Title                                                                                                                                | Group | For publication? |
+|------|--------|--------------------------------------------------------------------------------------------------------------------------------------|-------|------------------|
+| TS   | 21.111 | USIM and IC card requirements                                                                                                        | C6    | Yes              |
+| TR   | 21.905 | Vocabulary for 3GPP Specifications                                                                                                   | SP    | Yes              |
+| TS   | 22.030 | Man-Machine Interface (MMI) of the User Equipment (UE)                                                                               | S1    | Yes              |
+| TS   | 22.041 | Operator Determined Barring (ODB)                                                                                                    | S1    | Yes              |
+| TS   | 22.071 | Location Services (LCS); Service description; Stage 1                                                                                | S1    | Yes              |
+| TS   | 22.101 | Service aspects; Service principles                                                                                                  | S1    | Yes              |
+| TS   | 22.105 | Services and service capabilities                                                                                                    | S1    | Yes              |
+| TS   | 22.115 | Service aspects; Charging and billing                                                                                                | S1    | Yes              |
+| TS   | 22.140 | Multimedia Messaging Service (MMS); Stage 1                                                                                          | S1    | Yes              |
+| TS   | 22.141 | Presence service; Stage 1                                                                                                            | S1    | Yes              |
+| TS   | 22.153 | Multimedia priority service                                                                                                          | S1    | Yes              |
+| TS   | 22.173 | IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1                          | S1    | Yes              |
+| TS   | 22.174 | Push Service; Service aspects; Stage 1                                                                                               | S1    | Yes              |
+| TS   | 22.182 | Customized Alerting Tones (CAT) requirements; Stage 1                                                                                | S1    | Yes              |
+| TS   | 22.183 | Customized Ringing Signal (CRS) requirements; Stage 1                                                                                | S1    | Yes              |
+| TS   | 22.228 | Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1                                 | S1    | Yes              |
+| TS   | 22.250 | IP Multimedia Subsystem (IMS) Group Management; Stage 1                                                                              | S1    | Yes              |
+| TS   | 22.279 | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1                                                   | S1    | Yes              |
+| TS   | 22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1                                                                                     | S1    | Yes              |
+| TR   | 22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions                                 | S1    | Yes              |
+| TS   | 23.141 | Presence service; Architecture and functional description                                                                            | S2    | Yes              |
+| TS   | 23.167 | IP Multimedia Subsystem (IMS) emergency sessions                                                                                     | S2    | Yes              |
+| TS   | 23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2                                      | S2    | Yes              |
+| TS   | 23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2                                                                          | C1    | Yes              |
+| TS   | 23.228 | IP Multimedia Subsystem (IMS); Stage 2                                                                                               | S2    | Yes              |
+| TS   | 23.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | C4    | Yes              |
+| TS   | 23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) interface: Procedures descriptions  | C4    | Yes              |
+| TS   | 24.141 | Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3                                                   | C1    | Yes              |
+| TS   | 24.147 | Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3                                                       | C1    | Yes              |
+
+| Type | Number | Title                                                                                                                                                                                   | Group | For publication? |
+|------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------|
+| TS   | 24.173 | IMS Multimedia telephony communication service and supplementary services; Stage 3                                                                                                      | C1    | Yes              |
+| TS   | 24.182 | IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification                                                                                                   | C1    | Yes              |
+| TS   | 24.229 | IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3                                                          | C1    | Yes              |
+| TS   | 24.238 | Session Initiation Protocol (SIP) based user configuration; Stage 3                                                                                                                     | C1    | Yes              |
+| TS   | 24.239 | Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                                     | C1    | Yes              |
+| TS   | 24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3                                                                                                     | C1    | Yes              |
+| TS   | 24.315 | IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3: protocol specification                                                                                        | C1    | Yes              |
+| TS   | 24.341 | Support of SMS over IP networks; Stage 3                                                                                                                                                | C1    | Yes              |
+| TS   | 24.604 | Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                             | C1    | Yes              |
+| TS   | 24.605 | Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                                          | C1    | Yes              |
+| TS   | 24.606 | Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                           | C1    | Yes              |
+| TS   | 24.607 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification             | C1    | Yes              |
+| TS   | 24.608 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification             | C1    | Yes              |
+| TS   | 24.610 | Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                                  | C1    | Yes              |
+| TS   | 24.611 | Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                     | C1    | Yes              |
+| TS   | 24.615 | Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification                                                                                 | C1    | Yes              |
+| TS   | 24.616 | Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                              | C1    | Yes              |
+| TS   | 24.628 | Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                      | C1    | Yes              |
+| TS   | 24.629 | Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification                                                                      | C1    | Yes              |
+| TS   | 24.642 | Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1    | Yes              |
+| TS   | 24.647 | Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem                                                                                                             | C1    | Yes              |
+| TS   | 24.654 | Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification                                                                                    | C1    | Yes              |
+| TR   | 24.930 | Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3     | C1    | Yes              |
+| TS   | 29.162 | Interworking between the IM CN subsystem and IP networks                                                                                                                                | C3    | Yes              |
+| TS   | 29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks                                                                              | C3    | Yes              |
+| TS   | 29.165 | Inter-IMS Network to Network Interface (NNI)                                                                                                                                            | C3    | Yes              |
+| TS   | 29.212 | Policy and Charging Control (PCC); Reference points                                                                                                                                     | C3    | Yes              |
+| TS   | 29.213 | Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping                                                                                             | C3    | Yes              |
+
+| Type | Number | Title                                                                                                                           | Group | For publication? |
+|------|--------|---------------------------------------------------------------------------------------------------------------------------------|-------|------------------|
+| TS   | 29.214 | Policy and charging control over Rx reference point                                                                             | C3    | Yes              |
+| TS   | 29.215 | Policy and Charging Control (PCC) over S9 reference point; Stage 3                                                              | C3    | Yes              |
+| TS   | 29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents                                        | C4    | Yes              |
+| TS   | 29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details                                                           | C4    | Yes              |
+| TS   | 29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3                                                         | C4    | Yes              |
+| TS   | 29.238 | Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3                    | C4    | Yes              |
+| TS   | 29.292 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS) | C3    | Yes              |
+| TS   | 29.311 | Service Level Interworking (SLI) for messaging services                                                                         | C3    | Yes              |
+| TS   | 29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents                                                | C4    | Yes              |
+| TS   | 29.329 | Sh interface based on the Diameter protocol; Protocol details                                                                   | C4    | Yes              |
+| TS   | 29.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3            | C4    | Yes              |
+| TS   | 29.334 | IMS Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3                                   | C4    | Yes              |
+| TS   | 29.658 | SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification                                                | C3    | Yes              |
+| TS   | 31.101 | UICC-terminal interface; Physical and logical characteristics                                                                   | C6    | Yes              |
+| TS   | 31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application                                                | C6    | Yes              |
+| TS   | 31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications                                 | C6    | Yes              |
+| TS   | 31.116 | Remote APDU Structure for (U)SIM Toolkit applications                                                                           | C6    | Yes              |
+| TS   | 31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™                  | C6    | Yes              |
+| TS   | 32.240 | Telecommunication management; Charging management; Charging architecture and principles                                         | S5    | Yes              |
+| TS   | 32.260 | Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging                                       | S5    | Yes              |
+| TS   | 32.299 | Telecommunication management; Charging management; Diameter charging applications                                               | S5    | Yes              |
+| TS   | 33.141 | Presence service; Security                                                                                                      | S3    | Yes              |
+| TS   | 33.203 | 3G security; Access security for IP-based services                                                                              | S3    | Yes              |
+| TS   | 33.210 | 3G security; Network Domain Security (NDS); IP network layer security                                                           | S3    | Yes              |
+
+Tables are based on query " 2003-09-03\_CmnlMS\_specs\_list\_rel-x\_\_21-202" in the [3GPP Specifications Status database](#).
+
+## --- Annex A (informative): (void)
+
+## Annex M (informative): IMS related Specifications and Reports in 3GPP2
+
+The table below shows the 3GPP2 publications relating to core functions of the IP Multimedia Subsystem (IMS) used by the 3GPP2. Also shown in the table is the mapping between the replaced 3GPP2 MMD specifications and the corresponding 3GPP IMS specifications which replace them and the final revision of the document that was published by 3GPP2.
+
+| 3GPP2 Document Number and Revision | 3GPP2 Document Title                                                                 | 3GPP Rel-8 TS/TR                    | 3GPP WG        |
+|------------------------------------|--------------------------------------------------------------------------------------|-------------------------------------|----------------|
+| X.S0013-000-B v1.0                 | Overview                                                                             | TS 23.002                           | S2             |
+| X.S0013-002-B v1.0                 | IP Multimedia Subsystem – Stage 2                                                    | TS 23.228<br>TS 23.228<br>TS 23.002 | S2<br>S2       |
+| X.S0013-003-B v1.0                 | IP Multimedia Session Handling; IP Multimedia Call Model – Stage 2                   | TS 23.218                           | C1             |
+| X.S0013-004-B v1.0                 | IP Multimedia Call Control Protocol Based on SIP and SDP - Stage 3                   | TS 24.229                           | C1             |
+| X.S0013-005-B v1.0                 | IP Multimedia Subsystem Cx Interface Signaling flows and Message Contents            | TS 29.228                           | C4             |
+| X.S0013-006-B v1.0                 | Cx Interface Based on the Diameter Protocol; Protocol Details                        | TS 29.229                           | C4             |
+| X.S0013-007-A v1.0                 | IP Multimedia Subsystem - Charging Architecture                                      | TS 32.240<br>TS 32.260              | S5<br>S5       |
+| X.S0013-008-A v1.0                 | IP Multimedia Subsystem - Offline Accounting Information Flows and Protocol          | TS 32.260<br>TS 32.299              | S5<br>S5       |
+| X.S0013-009-0 v1.0                 | IMS/MMD Call Flow Examples                                                           | TR 24.930                           | C1             |
+| X.S0013-010-B v1.0                 | IP Multimedia Subsystem Sh interface; Signaling flows and message contents – Stage 2 | TS 29.328                           | C4             |
+| X.S0013-011-B v1.0                 | Sh Interface based on Diameter Protocols Protocol Details – Stage 3                  | TS 29.329                           | C4             |
+| X.S0013-012-0 v1.0                 | Service Based Bearer Control – Stage 2                                               | TS 23.203                           | S2             |
+| X.S0013-013-0 v1.0                 | Service Based Bearer Control – Tx Interface Stage 3                                  | TS 29.213<br>TS 29.214              | C3<br>C3       |
+| X.S0013-014-0 v1.0                 | Service Based Bearer Control – Ty Interface Stage 3                                  | TS 29.212<br>TS 29.215              | C3<br>C3       |
+| X.S0013-016-0 v1.0                 | Messaging Service Using the IP Multimedia Subsystem                                  | TS 24.247                           | C1             |
+| X.S0027-000-A v1.0                 | Presence Overview                                                                    | No 3GPP equivalent                  |                |
+| X.S0027-001-0 v1.0                 | Presence Service: Architecture and Functional Description                            | TS 23.141                           | S2             |
+| X.S0027-002-0 v1.0                 | Presence Security                                                                    | TS 33.141                           | S3             |
+| X.S0027-003-0 v1.0                 | Presence Stage 3                                                                     | TS 24.141                           | C1             |
+| X.S0027-004-0 v1.0                 | Network Presence                                                                     | No 3GPP equivalent                  |                |
+| X.S0029-0 v1.0                     | Conferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem                | TS 24.147                           | C1             |
+| X.S0049-0 v1.0                     | All-IP Network Emergency Call Support                                                | TS 23.167<br>TS 24.229              | S2<br>C1       |
+| X.S0055-0 v1.0                     | MMD Supplementary Services                                                           | TS 24.173<br>TS 24.182<br>TS 24.238 | C1<br>C1<br>C1 |
+
+|                |                                                                |                    |    |  |
+|----------------|----------------------------------------------------------------|--------------------|----|--|
+|                |                                                                | TS 24.239          | C1 |  |
+|                |                                                                | TS 24.604          | C1 |  |
+|                |                                                                | TS 24.605          | C1 |  |
+|                |                                                                | TS 24.606          | C1 |  |
+|                |                                                                | TS 24.607          | C1 |  |
+|                |                                                                | TS 24.608          | C1 |  |
+|                |                                                                | TS 24.610          | C1 |  |
+|                |                                                                | TS 24.611          | C1 |  |
+|                |                                                                | TS 24.615          | C1 |  |
+|                |                                                                | TS 24.628          | C1 |  |
+|                |                                                                | TS 24.629          | C1 |  |
+| S.S0086-B v2.0 | IMS Security Framework                                         | TS 33.203          | S3 |  |
+| S.R0058        | IP Multimedia Domain – System Requirements                     | TS 33.210          | S3 |  |
+| S.R0062        | Presence for Wireless Systems – Stage 1 Requirements           | TS 22.228          | S1 |  |
+| S.R0125        | VoIP Supplementary Services Feature Description                | TS 22.141          | S1 |  |
+| X.R0052-0      | All-IP System – MMD Roaming Technical Report                   | TS 22.173          | S1 |  |
+| X.S0042        | Voice Call Continuity between IMS and Circuit Switched Systems | No 3GPP equivalent |    |  |
+| C.S0069        | ISIM Application on UICC for cdma2000 Spread Spectrum Systems  | TS 23.206          | S2 |  |
+|                |                                                                | TS 24.206          | C1 |  |
+|                |                                                                | TS 31.103          | C6 |  |
+
+## Annex C (informative): Change history
+
+| Change history |       |           |    |     |                                                                                                                                                                                          |        |        |
+|----------------|-------|-----------|----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                                                                                                                                                                          | Old    | New    |
+| 2008-05        |       |           |    |     | First draft based on SA1 request to SP-38, refined at SP-39. Spec list based on Specification Manager's whim.                                                                            |        | 0.0.0  |
+| 2008-12        |       |           |    |     | Update based on continuing evolution of Release 8 specs                                                                                                                                  | 0.0.0  | 0.1.0  |
+| 2008-12        | SP-42 | SP-080724 |    |     | Incorporation of comments from TSG CT: removal of §5.1 (substituted by two examples in annex A); indication in list of specs of those which do not progress beyond NGN R2 applicability. | 0.1.0  | 0.2.0  |
+| 2009-01        |       |           |    |     | Update to specs list table resulting from further feedback; Correction to URL of TISPAN spec mapping following revamp of 3GPP web site                                                   | 0.2.0  | 0.3.0  |
+| 2009-03        | CP-43 | CP-090103 |    |     | Presentation for information                                                                                                                                                             | 0.3.0  | 1.0.0  |
+| 2009-03        | SP-43 | SP-090035 |    |     | Presentation to TSG for approval                                                                                                                                                         | 1.0.0  | 1.1.0  |
+| 2009-03        | SP-43 |           |    |     | Approved                                                                                                                                                                                 | 1.1.0  | 8.0.0  |
+| 2009-05        | SP-44 | SP-090463 | 2  | 2   | Annex mapping 3GPP2 specs to 3GPP common IMS specs                                                                                                                                       | 8.0.0  |        |
+|                |       | SP-090464 | 3  |     | Revise scope                                                                                                                                                                             |        | 8.1.0  |
+| 2009-06        | SP-46 | SP-090695 | 4  | 1   | Correction to list of specifications                                                                                                                                                     | 8.1.0  | 8.2.0  |
+| 2010-03        | SP-47 | SP-100012 | 5  |     | Update list of specs                                                                                                                                                                     | 8.2.0  | 8.3.0  |
+|                |       |           | 6  |     | Update list of specs                                                                                                                                                                     | 8.3.0  |        |
+|                |       |           | 7  |     | Removal of information only relevant for earlier Release                                                                                                                                 |        | 9.0.0  |
+| 2010-12        | SP-50 | SP-100871 | 8  | 1   | Clarification of scope to indicate use of complete set of TSs/TRs is not obligatory in all IMS implementations                                                                           | 9.0.0  | 9.1.0  |
+| 2011-03        | SP-51 |           |    |     | Automatic upgrade on Release freeze                                                                                                                                                      | 9.1.0  | 10.0.0 |
+| 2011-06        | SP-52 | SP-110298 | 11 |     | Correction to list of specifications                                                                                                                                                     | 10.0.0 | 10.1.0 |
+| 2012-03        | SP-55 | SP-120114 | 14 | 1   | Changes to list of Specs: common IMS                                                                                                                                                     | 10.1.0 | 10.2.0 |
+| 2013-03        | SP-59 | SP-130155 | 15 |     | Update to list of specs                                                                                                                                                                  | 10.2.0 | 10.3.0 |
+| 2013-03        | SP-59 | SP-130155 | 16 |     | Update to list of specs                                                                                                                                                                  | 10.3.0 | 11.0.0 |
+| 2014-06        |       |           |    |     | Minor editorial                                                                                                                                                                          | 11.0.0 | 11.0.1 |

marked/Rel-11/21_series/21801/raw.md

@@ -0,0 +1,105 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                            |   |
+|--------------------------------------------|---|
+| Foreword .....                             | 3 |
+| 1 Scope.....                               | 4 |
+| 2 References.....                          | 4 |
+| 3 Void.....                                | 4 |
+| 4 Drafting rules for Release 11 .....      | 4 |
+| Annex K (informative): Change history..... | 5 |
+
+---
+
+# Foreword
+
+This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP) Secretariat on behalf of the 3GPP Technical Specification Groups (TSGs).
+
+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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater 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 document.
+
+The present document is based ISO/IEC Directives. Most clauses of the ISO/IEC document have been retained, while some clauses have been modified or deleted. Additional material has been inserted.
+
+Items concerning word-processor specific layout and formatting matters when using the Microsoft Word for Windows® based skeleton documents and templates are shown with shaded background. Boiler plate text (i.e. text which shall be directly used in 3GPP specifications) is represented by *italic* characters.
+
+# --- 1 Scope
+
+The present document specifies rules for the structure and drafting of documents intended to become a 3GPP Technical Specification or Technical Report. These rules are intended to ensure that such documents are drafted in as uniform a manner as is practicable, irrespective of the technical content.
+
+The present document is based on the ISO/IEC Directives, Part 3, but is a self-contained document that will be maintained as such.
+
+These drafting rules complement the 3GPP Working Procedures.
+
+# --- 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] Void
+- [2] Void
+- [3] Void
+- [4] 3GPP TR 21.801 Release 12: "Specification drafting rules"
+
+# --- 3 Void
+
+# 4 Drafting rules for Release 11
+
+The drafting rules for Release 11 3GPP Technical Specifications and Technical Reports are identical to the rules for the next higher Release of TR 21.801 [4].
+
+# Annex K (informative): Change history
+
+| Change history |           |         |       |         |             |                                                                                 |
+|----------------|-----------|---------|-------|---------|-------------|---------------------------------------------------------------------------------|
+| TSG SA #       | TDoc      | Version | CR    | <Phase> | New Version | Subject/Comment                                                                 |
+| 05-2000        |           |         | -     |         | 0.0.0       | First draft, internal to MCC.                                                   |
+| 06-2000        |           | 0.0.0   | -     |         | 1.0.0       | Editorial clean up                                                              |
+| SP-08          | SP-000278 | 1.0.0   | -     |         | 1.0.1       | Presentation to SA#8                                                            |
+| SP-08          |           | 1.0.1   |       | Rel-4   | 4.0.0       | Approved (Rel-4)                                                                |
+| SP-11          | SP-010193 | 4.0.0   | 001   | Rel-4   | 4.1.0       | Automatic numbering of references                                               |
+| SP-11          | SP-010213 | 4.0.0   | 002r1 | Rel-4   | 4.1.0       | Clarification on use of automatically numbered figures, tables, etc.            |
+| SP-13          | SP-010482 | 4.1.0   | 003   | Rel-4   | 4.2.0       | Corrections of invalid clause reference                                         |
+| SP-15          | SP-020105 | 4.2.0   | 004   | Rel-4   | 4.3.0       | Correction of invalid table number, annex H.                                    |
+| SP-16          |           | 4.3.0   |       | Rel-5   | 5.0.0       | Upgrade to Rel-5.                                                               |
+|                |           | 5.0.0   |       | Rel-5   | 5.0.1       | 2002-07-19: Correct cover page.                                                 |
+|                |           | 5.0.1   |       | Rel-5   | 5.0.2       | 2003-05-15: Correct cover page.                                                 |
+| SP-23          |           | 5.0.2   |       | Rel-6   | 6.0.0       | Upgrade without change to Release 6                                             |
+| SP-28          | SP-050401 | 6.0.0   | 009   | Rel-7   | 7.0.0       | The use of 'void'                                                               |
+| SP-29          | SP-050535 | 7.0.0   | 013   | Rel-7   |             | Introduction of MS Visio                                                        |
+|                |           |         | 014r1 |         | 7.1.0       | Specification of versions of permitted software packages                        |
+| SP-30          | SP-050689 | 7.1.0   | 015   | Rel-7   | 7.2.0       | Inclusion of version identity for Visio                                         |
+| SP-34          | SP-060914 | 7.2.0   | 017   | Rel-7   |             | Alignment of section 6.6.4.2 and annex I in respect of figure format.           |
+| SP-37          | SP-070527 | 7.3.0   | 018   | Rel-8   |             | Upgrade to Rel-8, allowing for more recent versions of application file formats |
+| SP-39          | SP-080078 | 8.0.0   | 020   | Rel-8   |             | Correction of illegal text                                                      |
+|                |           |         | 021   |         | 8.1.0       | Elimination of IPR provisions                                                   |
+| SP-46          |           | 8.1.0   |       |         | 9.0.0       | Upgrade to Rel-9, no technical change                                           |
+| SP-48          | SP-100365 | 9.0.0   | 024r4 | Rel-10  |             | References to Figures and Tables                                                |
+|                | SP-100422 |         | 026r1 |         | 10.0.0      | Clarification on usage of "may", "may not", "can" and "cannot"                  |
+| SP-49          | SP100655  | 10.0.0  | 028r3 | Rel-10  |             | Supported file formats                                                          |
+|                |           |         | 029r3 |         |             | Rules on referencing unpublished documents                                      |
+|                | SP-100629 |         | 030   |         | 10.1.0      | Clarification on the use of References                                          |
+|                |           | 10.1.0  |       | Rel-10  |             | Editorial correction to previous meeting's entry in this history table.         |
+|                |           | 10.1.1  |       | Rel-10  | 10.1.2      | Editorial correction to table H.3                                               |
+| SP-55          | SP-120112 | 10.1.2  | 031r1 | Rel-11  | 11.0.0      | Clarification on treatment of void clauses                                      |
+| SP-56          | SP-120317 | 11.0.0  | 033   | Rel-11  | 11.1.0      | Page breaks before annexes                                                      |
+| SP-57          | SP-120610 | 11.1.0  | 034r1 | Rel-11  | 11.2.0      | TS and TR titles                                                                |
+| SP-61          | SP-130365 | 11.2.0  | 037   | Rel-11  |             | Eliminate contents of Rel-11 and substitute with pointer to Rel-12              |
+|                |           |         |       |         | 11.3.0      |                                                                                 |

marked/Rel-11/21_series/21900/raw.md

@@ -0,0 +1,107 @@
+
+
+
+
+
+
+# Contents
+
+Foreword ..... 4
+
+Introduction ..... 4
+
+1 Scope..... 5
+
+1A References..... 5
+
+Annex A: Change history..... 6
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater 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 document.
+
+# --- Introduction
+
+In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports) under responsibility of the Technical Specification Groups (TSG) of the 3<sup>rd</sup> Generation Partnership Project (3GPP), clear, manageable and efficient mechanisms are necessary to handle version control, change control, document updating, distribution and management.
+
+The provisions for this Release are identical with those for the latest Release of TR 21.900 [1].
+
+# --- 1 Scope
+
+This document outlines the working methods to be used by the 3GPP Technical Specification Groups and their Working Groups and their Sub-Groups, and by the 3GPP Support Team in relation to document management, i.e. handling of specifications, updating procedures, Change Request procedures, version control mechanisms, specifications status information etc. It complements the rules and procedures defined for 3GPP. This document does not stipulate the details of the internal working of the TSG Sub-Groups. From the Technical Specification Group point of view, a task and responsibility is given to a Working Group directly answering to the Technical Specification Group. In practice, the work/task may be carried out in a subgroup of that Working Group.
+
+# --- 1A 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.900 Release 12: "Technical Specification Group working methods".
+
+# Annex A: Change history
+
+| Change history |         |           |           |             |                                                                                                                                                                                                            |
+|----------------|---------|-----------|-----------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TSG SA#        | Version | CR        | Tdoc SA   | New Version | Subject/Comment                                                                                                                                                                                            |
+| SP-04          | 3.0.0   | 001       | SP-99288  | 3.1.0       | Alignment with TSG SA decisions made at TSG#3. Deletion of Strategic/non strategic CR references. Change of PT to Support Team, editorial corrections.                                                     |
+|                |         | 002       | SP-99289  |             | Harmonisation of the use of software for 3GPP documents in order to minimise the errors due to software conversion problems and to allow efficient interchange of electronic files for electronic working. |
+| SP-05          | 3.1.0   | 003       | SP-99428  | 3.2.0       | Addition of new text related to electronic working practices.                                                                                                                                              |
+| SP-08          | 3.2.0   | 005       | SP-000279 | 3.3.0       | Clarification and editorial corrections to provisions covering the management of specifications and Work Items.                                                                                            |
+| SP-09          | 3.3.0   | 007 r1    | SP-000402 | 3.4.0       | Role of rapporteur for both Specifications and Work Items.                                                                                                                                                 |
+|                |         | 008 r2    | SP-000492 |             | Clarification of CR categories.                                                                                                                                                                            |
+|                |         | 010       | SP-000461 |             | Clarification of CR categories for a frozen 3GPP release.                                                                                                                                                  |
+|                |         | editorial |           |             | Change of "Release 2000" into "Release 4", addition of "Release 5".                                                                                                                                        |
+| SP-10          | 3.4.0   | 011 r1    | SP-000693 | 3.5.0       | Release numbers appearing in CR cover sheets                                                                                                                                                               |
+|                | 3.4.0   | 012 r1    | SP-000693 |             | Clarification of the "freezing" of specifications                                                                                                                                                          |
+|                | 3.4.0   | 013 r2    | SP-000693 |             | Release mechanisms                                                                                                                                                                                         |
+| SP-11          | 3.5.0   | 014 r1    | SP-010178 | 3.6.0       | Inclusion of GSM spec numbering scheme                                                                                                                                                                     |
+|                | 3.6.0   | -         | -         | 4.0.0       | Upgrade to Rel-4.                                                                                                                                                                                          |
+| SP-16          | 4.0.0   | -         | -         | 5.0.0       | Upgrade to Rel-5.                                                                                                                                                                                          |
+| 2002-09-17     | 5.0.0   | -         | -         | 5.0.1       | Editorial correction to front cover (change title to read Release 5 instead of Release 4)                                                                                                                  |
+| SP-21          | 5.0.1   | 015       | SP-030499 | 6.0.0       | Addition of stage 1-2-3 specification structure description                                                                                                                                                |
+| SP-22          | 6.0.0   | 019       | SP-030575 | 6.1.0       | Corrects references                                                                                                                                                                                        |
+| SP-23          | 6.1.0   | -         | -         | 6.1.1       | Corrects Release shown on cover page                                                                                                                                                                       |
+| SP-24          | 6.1.1   | 020       | SP-040310 | 6.2.0       | Release planning: target date setting                                                                                                                                                                      |
+|                |         | -         | -         |             | Editorial: Correction of second clause 6.0.2 to 6.0.3.                                                                                                                                                     |
+| SP-25          | 6.2.0   | 021 r3    | SP-040705 | 6.3.0       | Introduction of "Early Implementation" process                                                                                                                                                             |
+|                |         | 024       | SP-040706 |             | Improved tracking of Work Item status                                                                                                                                                                      |
+| SP-26          | 6.3.0   | 025       | SP-040824 | 7.0.0       | Editorial clarification of version numbering system, upgrade to Rel-7                                                                                                                                      |
+| SP-28          | 7.0.0   |           |           | 7.0.1       | Editorial corrections to harmonize use of capitalization plus a typographical error                                                                                                                        |
+| SP-29          | 7.0.1   | 028       | SP-050537 | 7.1.0       | Introduction of the concept of "study item"                                                                                                                                                                |
+| SP-32          | 7.1.0   | 029       | SP-060403 | 7.2.0       | Inclusion of "study item" in definition of "work item"                                                                                                                                                     |
+|                |         | 030       |           |             | Change "short" to "long" WG abbreviations                                                                                                                                                                  |
+|                |         | 031 r1    |           |             | Correct references to obsolete TSG.                                                                                                                                                                        |
+|                |         | 032       |           |             | Registration of code points with external bodies                                                                                                                                                           |
+| SP-37          | 7.2.0   | 034 r2    | SP-070703 | 8.0.0       | Alignment of working methods with alignment CR practice agreed in TSG SA #36                                                                                                                               |
+| SP-38          | 8.0.0   | 035       | SP-070900 | 8.1.0       | Addition of 36.-series to Specs series table                                                                                                                                                               |
+|                | 8.1.0   |           |           | 8.1.1       | Correct typo in previous entry in history table                                                                                                                                                            |
+| SP-39          | 8.1.1   | 036 r2    | SP-080079 | 8.2.0       | Clarification of version nomenclature                                                                                                                                                                      |
+| SP-42          | 8.2.0   | 037 r3    | SP-080897 | 8.3.0       | Determination of freeze dates for stages of a Release. (Correction recommended by OP ad hoc group on improvements.)                                                                                        |
+|                |         | 038 r1    | SP-080721 |             | Cross-TSG work coordination. (Correction recommended by OP ad hoc group on improvements.)                                                                                                                  |
+|                |         | 039 r2    |           |             | Introduction of concept of "exception sheets" for late-running work items                                                                                                                                  |
+| SP-46          | 8.3.0   |           |           | 9.0.0       | Upgrade without technical change to Rel-9                                                                                                                                                                  |
+| SP-51          | 9.0.0   |           |           | 10.0.0      | Upgrade without technical change to Rel-10                                                                                                                                                                 |
+| SP-54          | 10.0.0  | 045       | SP-110802 | 11.0.0      | The use of Category A CRs                                                                                                                                                                                  |
+|                | 11.0.0  |           |           | 11.0.1      | 2013-06: Corrects cased of letter "i" shown against value 18 in table 5.                                                                                                                                   |
+| SP-65          | 11.0.1  | 047       | SP-140445 | 11.1.0      | Correction to implementation of CR0045                                                                                                                                                                     |
+|                |         | 043r2     | SP-140446 |             | Encourage allocation of CR number at first sight                                                                                                                                                           |
+
+| <b>Change history</b> |                |             |           |            |            |                                                                   |                    |
+|-----------------------|----------------|-------------|-----------|------------|------------|-------------------------------------------------------------------|--------------------|
+| <b>Date</b>           | <b>Meeting</b> | <b>TDoc</b> | <b>CR</b> | <b>Rev</b> | <b>Cat</b> | <b>Subject/Comment</b>                                            | <b>New version</b> |
+| 2016-03               | SA#71          | SP-160182   | 0050      |            | F          | Eliminate contents of Rel-11 and substitute with pinter to Rel-12 | 11.2.0             |

marked/Rel-11/24_series/24002/raw.md

@@ -0,0 +1,310 @@
+
+
+
+
+
+
+# Contents
+
+|                                            |    |
+|--------------------------------------------|----|
+| Foreword .....                             | 4  |
+| 1 Scope.....                               | 5  |
+| 1.1 References .....                       | 5  |
+| 1.2 Abbreviations .....                    | 6  |
+| 2 General definitions.....                 | 6  |
+| 2.1 Reference Configurations.....          | 7  |
+| 2.2 Functional Groups .....                | 7  |
+| 2.3 Reference Points.....                  | 7  |
+| 2.4 Interface Points.....                  | 7  |
+| 2.5 Terminal Definitions .....             | 7  |
+| 3 Reference Configuration .....            | 8  |
+| 3.0 General .....                          | 8  |
+| 3.1 Mobile Termination (MT).....           | 9  |
+| 3.2 Void.....                              | 10 |
+| 4 Physical Realisation .....               | 10 |
+| Annex A (informative): Change history..... | 11 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater 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 document.
+
+# --- 1 Scope
+
+The present document describes the reference configuration for access to a PLMN.
+
+A user accesses a PLMN via a number of interfaces, including the MS-BS (in A/Gb mode and GERAN Iu mode), UE-UTRAN (in UTRAN Iu mode) and UE-E-UTRAN interface. The purpose of this document is to indicate the possible access arrangements that may be used in conjunction with the MS-BS (in A/Gb mode and GERAN Iu mode), UE-UTRAN (in UTRAN Iu mode) and UE-E - UTRAN interface.
+
+## 1.1 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] Void.
+- [2] Void.
+- [3] Void.
+- [4] Void.
+- [5] Void.
+- [6] Void.
+- [7] Void.
+- [8] Void.
+- [9] Void.
+- [10] Void.
+- [11] Void.
+- [12] Void.
+- [13] Void.
+- [14] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface".
+- [15] Void.
+- [16] Void.
+- [17] Void.
+- [18] Void.
+- [19] Void.
+- [20] Void.
+- [21] Void.
+
+- [22] Void.
+- [23] Void.
+- [24] Void.
+- [25] Void.
+- [26] Void.
+- [27] Void.
+- [28] Void.
+- [29] Void.
+- [30] Void.
+- [31] Void.
+- [32] Void.
+- [33] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+- [34] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities".
+- [35] 3GPP TS 27.003: "Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
+- [36] Void.
+- [37] Void.
+- [38] Void.
+- [39] 3GPP TR 21.905: " Vocabulary for 3GPP Specifications ".
+- [40] Void.
+- [41] 3GPP TS 25.322: "Radio Link Control (RLC) Protocol Specification".
+- [42] ITU-T Recommendation V.24 (1996):"List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)".
+- [43] ITU-T Recommendation V.28 (1993): "Electrical characteristics for unbalanced double-current interchange circuits".
+- [44] Infrared Data Association IrDA: "IrPHY Physical layer signalling standard".
+- [45] Personal Computer Memory Card Association: "PCMCIA 2.1 or PC-Card 3.0 electrical specification or later revisions".
+- [46] Void.
+
+## 1.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TR 21.905 [39].
+
+# --- 2 General definitions
+
+The following definitions 2.1-2.3 are based on those used for ISDN.
+
+## 2.1 Reference Configurations
+
+Reference Configurations are conceptual configurations useful in identifying access arrangements to a network. Two concepts are used in defining reference configurations:
+
+reference points and functional groups.
+
+## 2.2 Functional Groups
+
+Functional Groups are sets of functions which may be needed in network access arrangements. In a particular access arrangement, specific functions in a functional group may or may not be present. Specific functions in a functional group may be performed in one or more pieces of equipment.
+
+## 2.3 Reference Points
+
+Reference Points are the conceptual points dividing functional groups. In a specific access arrangement, a reference point may correspond to a physical interface between pieces of equipment, or there may not be any physical interface corresponding to the reference point.
+
+## 2.4 Interface Points
+
+Interface Points are reference points within a PLMN at which a 3GPP specified interface is always identified.
+
+## 2.5 Terminal Definitions
+
+The term 'mobile station' ( MS ) in the present document is synonymous with the term 'user equipment' ( UE ) in 3G terminology as defined in 3GPP TR 21.905 [39].
+
+The term 'TE2' in the present document is synonymous with the term 'TE' in 3G terminology as defined in 3GPP TR 21.905 [39].
+
+The term 'MT2' in the present document is synonymous with the term 'MT' in 3G terminology as defined in 3GPP TR 21.905 [39].
+
+# 3 Reference Configuration
+
+## 3.0 General
+
+The reference configuration for PLMN (in A/Gb mode and GERAN Iu mode) access interfaces is shown in figure 1.
+
+![Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode). The diagram shows two Mobile Stations (MS) connected to a Base Station/Mobile Switching Center (BSS/MSC). The top MS contains a Mobile Terminal (MT0) connected directly to the BSS/MSC. The bottom MS contains a Terminal Equipment (TE2) connected to a Terminal Adaptor (TA), which is then connected to an MT2, which in turn connects to the BSS/MSC. Reference points R and Um are indicated by vertical dashed lines with cross-ticks. A legend defines the symbols: a cross-tick for a reference point, TE2 for a V-type terminal, TA for a Terminal Adaptor, GERAN for GSM/EDGE Radio Access Network, and CN for Core Network.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg)
+
++ : reference point.  
+ TE2: V -type terminal.  
+ TA: Terminal Adaptor.  
+ GERAN: GSM/EDGE Radio Access Network.  
+ CN: Core Network.
+
+Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode). The diagram shows two Mobile Stations (MS) connected to a Base Station/Mobile Switching Center (BSS/MSC). The top MS contains a Mobile Terminal (MT0) connected directly to the BSS/MSC. The bottom MS contains a Terminal Equipment (TE2) connected to a Terminal Adaptor (TA), which is then connected to an MT2, which in turn connects to the BSS/MSC. Reference points R and Um are indicated by vertical dashed lines with cross-ticks. A legend defines the symbols: a cross-tick for a reference point, TE2 for a V-type terminal, TA for a Terminal Adaptor, GERAN for GSM/EDGE Radio Access Network, and CN for Core Network.
+
+**Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode)**
+
+There are two types of MT:
+
+- MT0 includes functions belonging to the functional group MT, with support of no terminal interfaces.
+- MT2 includes functions belonging to the functional group MT, and with an interface that complies with the 3GPP TS 27.00z series Terminal Adaptation Function specifications [33], [34], [35]. Accordingly, the interchange circuit mapping at the MT2 to TE interface shall comply with the ITU-T V.24 [42] recommendation; while the physical implementation shall conform either to the ITU-T V.28 [43], or to the IrDA IrPHY Physical signalling standard specification [44], or to the PCMCIA 2.1 [45], or to the PC-Card 3.0 [45], electrical specification or to later revisions.
+
+The MT plus any TE constitutes the Mobile Station, MS.
+
+The terminal equipment functional groups TE2 and TA are conceptually the same functional groups as those in the ISDN.
+
+The reference configuration for PLMN (Iu mode) access interfaces is shown in figure 2.
+
+![Figure 2: PLMN Access Reference Configuration (UTRAN lu mode or E-UTRAN). The diagram shows the internal components of a User Equipment (UE) and its interfaces. The UE contains a Mobile Equipment (ME), which in turn contains a Mobile Termination (MT) and a Terminal Adaptor (TA). The ME is connected to a TE (Terminal Equipment) via the Cc reference point. The TE is connected to a USIM via the R reference point. The MT is connected to the UTRAN or E-UTRAN/CN via the Uu reference point. The TA is shown as a dashed box within the MT.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+Figure 2: PLMN Access Reference Configuration (UTRAN lu mode or E-UTRAN). The diagram shows the internal components of a User Equipment (UE) and its interfaces. The UE contains a Mobile Equipment (ME), which in turn contains a Mobile Termination (MT) and a Terminal Adaptor (TA). The ME is connected to a TE (Terminal Equipment) via the Cc reference point. The TE is connected to a USIM via the R reference point. The MT is connected to the UTRAN or E-UTRAN/CN via the Uu reference point. The TA is shown as a dashed box within the MT.
+
++ : reference point.  
+ TA: Terminal Adaptor.  
+ MT: Mobile Termination.  
+ ME: Mobile Equipment.  
+ UE: User Equipment  
+ UTRAN: UMTS Radio Access Network.  
+ E-UTRAN: Evolved UMTS Radio Access Network.  
+ CN: Core Network.
+
+**Figure 2: PLMN Access Reference Configuration (UTRAN lu mode or E-UTRAN)**
+
+There is no reference point identified for the TA Function. The TA Function is considered as a part of the Mobile Termination and with an interface that complies with the 3GPP TS 27.00z series Terminal Adaptation Function specifications [33], [34], [35].
+
+## 3.1 Mobile Termination (MT)
+
+The MT performs the following functions, which performs the following functions:
+
+- radio transmission termination;
+- radio transmission channel management;
+- terminal capabilities, including presentation of a man-machine interface to a user;
+- speech encoding/decoding;
+- error protection for all information sent across the radio path. This includes FEC (forward error correction) and, for signalling and user data (except for transparent data services), ARQ (automatic request for retransmission);
+- flow control of signalling and mapping of user signalling to/from PLMN access signalling;
+- flow control of user data (except for transparent data services) and mapping of flow control for asynchronous transparent data services;
+- rate adaptation of user data (see 3GPP TS 44.021[14]) and data formatting for the transmission SAP (3GPP TS 25.322 [41]);
+- multiple terminal support;
+- mobility management.
+
+## 3.2 Void
+
+# 4 Physical Realisation
+
+In a PLMN, the reference point Um/Uu is an interface point, i.e. it is always implemented as a physical interface (according to 3GPP Technical Specifications in the 44, 45, 24, 25 and 36 series). The R reference point may be optionally implemented as physical interface. The implementation of interfaces at this reference point is according to 3GPP TS 27.001 [33], 3GPP TS 27.002 [34] and 3GPP TS 27.003 [35].
+
+Figure 3 gives examples of configurations illustrating combinations of physical interfaces at the R reference point. The examples shown are not exhaustive, but only serve to illustrate possible implementations of the respective functional blocks.
+
+Example (a) of figure 3 illustrates a fully integrated MS including data terminal functions within the mobile station equipment.
+
+Example (c) of figure 3 illustrates the connection of a TE2 by an ITU-T V series interface according to 3GPP TS 27.002 [34] and 3GPP TS 27.003 [35].
+
+Example (d) of figure 3 illustrates the connection of a MT2 PCMCIA card to a TE2 by a PCMCIA 2.1 interface according to 3GPP TS 27.002 [34] and 3GPP TS 27.003 [35].
+
+Example (f) of figure 3 illustrates the connection of a speech only MS.
+
+![Figure 3: Examples of physical implementations. The diagram shows six examples (a-f) of physical implementations at the R reference point. Each example shows a Mobile Station (MS) or Terminal (TE2) connected to a Base Station. (a) shows a Mobile Data Terminal [MT0] connected to a Base Station. (b) is labeled 'void'. (c) shows a V DTE [TE2] connected to an MT2, which is connected to a Base Station. (d) shows a V.24 and PCMCIA 2.1 DTE [TE2] connected to an MT2, which is connected to a Base Station. (e) is labeled 'void'. (f) shows a Speech-only MS [MT0] connected to a Base Station.](b10763be31553f31cbb795653b731a43_img.jpg)
+
+(a)
+
+```
+
++-----+
+| Mobile Data Terminal [MT0] |
++-----+
+-----//-----
++-----+
+| Base Station |
++-----+
+  
+```
+
+(b) void
+
+(c)
+
+```
+
++-----+
+| V DTE [TE2] |
++-----+
+-----//-----
++-----+
+| MT2 |
++-----+
+-----//-----
++-----+
+| Base Station |
++-----+
+  
+```
+
+(d)
+
+```
+
++-----+
+| V.24 and PCMCIA 2.1 DTE [TE2] |
++-----+
+-----//-----
++-----+
+| MT2 |
++-----+
+-----//-----
++-----+
+| Base Station |
++-----+
+  
+```
+
+(e) void
+
+(f)
+
+```
+
++-----+
+| Speech-only MS [MT0] |
++-----+
+-----//-----
++-----+
+| Base Station |
++-----+
+  
+```
+
+Figure 3: Examples of physical implementations. The diagram shows six examples (a-f) of physical implementations at the R reference point. Each example shows a Mobile Station (MS) or Terminal (TE2) connected to a Base Station. (a) shows a Mobile Data Terminal [MT0] connected to a Base Station. (b) is labeled 'void'. (c) shows a V DTE [TE2] connected to an MT2, which is connected to a Base Station. (d) shows a V.24 and PCMCIA 2.1 DTE [TE2] connected to an MT2, which is connected to a Base Station. (e) is labeled 'void'. (f) shows a Speech-only MS [MT0] connected to a Base Station.
+
+**Figure 3: Examples of physical implementations**
+
+# Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                           |        |        |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                           | Old    | New    |
+| 30.3.2000      | CN#7  | -         | -    | -   | Transferred to 3GPP for R99 (from GSM 04.02 v7.0.0).                                                      |        | 3.0.0  |
+| 12-2000        | NP-10 | NP-000673 | 001  | 2   | CR 24.002 on Adaptations for UMTS                                                                         | 3.0.0  | 3.1.0  |
+| 03-2001        | NP-11 |           |      |     | TSG CN#11 decided to issue RELEASE 4 of the specification 3GPP TS 24.002                                  | 3.1.0  | 4.0.0  |
+| 06-2002        | NP-16 |           |      |     | CN#16 decided to issue this TS also for Release 5. Additionally MCC made editorial and reference updates. | 4.0.0  | 5.0.0  |
+| 03-2003        | NP-19 | NP-030044 | 003  | 1   | Removal of the S reference point within the MS                                                            | 5.0.0  | 5.1.0  |
+| 06-2003        |       |           |      |     | Corrected the coverpage and some formatting,- MCC editorial.                                              | 5.1.0  | 5.1.1  |
+| 12-2004        | NP-26 |           |      |     | Rel-6 published after CN#26                                                                               | 5.1.1  | 6.0.0  |
+|                |       |           |      |     | Upgraded to Rel-7 by MCC                                                                                  | 6.0.0  | 7.0.0  |
+|                |       |           |      |     | Upgraded to Rel-8 by MCC                                                                                  | 7.0.0  | 8.0.0  |
+| 03-2009        | CP-43 | CP-090243 | 0004 | 4   | Inclusion of LTE in scope                                                                                 | 8.0.0  | 8.1.0  |
+| 03-2009        | CP-43 | CP-090159 | 0005 |     | Removal of unused references                                                                              | 8.0.0  | 8.1.0  |
+| 12-2009        | CP-46 |           |      |     | Upgraded to Rel-9 by MCC                                                                                  | 8.1.0  | 9.0.0  |
+| 03-2011        | CP-51 |           |      |     | Upgraded to Rel-10 by MCC                                                                                 | 9.0.0  | 10.0.0 |
+| 09-2012        | CP-57 |           |      |     | Upgraded to Rel-11 by MCC                                                                                 | 10.0.0 | 11.0.0 |