Add files using upload-large-folder tool

marked/Rel-11/22_series/22002/raw.md

@@ -0,0 +1,385 @@
+
+
+
+
+
+
+# Contents
+
+Foreword ..... 4
+
+0 Scope..... 5
+
+0.1 References ..... 5
+
+0.2 Abbreviations ..... 5
+
+1 Framework for defining Circuit Bearer Services ..... 6
+
+2 Bearer Service categories..... 7
+
+3 Bearer Services ..... 7
+
+3.1 General bearer service user data characteristics..... 8
+
+3.1.1 BS 20 (asynchronous services)..... 9
+
+3.1.1.1 BS 20 T (transparent asynchronous services)..... 9
+
+3.1.1.1.1 BS 20 transparent in regular mode for analogue interworking ..... 9
+
+3.1.1.1.2 BS 20 transparent in regular mode for digital interworking ..... 9
+
+3.1.1.2 BS 20 NT (non-transparent asynchronous services)..... 10
+
+3.1.1.2.1 BS 20 non-transparent in regular mode for analogue interworking..... 10
+
+3.1.1.2.2 BS 20 non-transparent in regular mode for digital interworking ..... 10
+
+3.1.1.2.3 BS 20 non-transparent for PIAFS ..... 11
+
+3.1.1.2.4 BS 20 non-transparent for Frame Tunnelling Mode ..... 11
+
+3.1.2 BS 30 (synchronous services) ..... 12
+
+3.1.2.1 BS 30 T (transparent synchronous services)..... 12
+
+3.1.2.1.1 BS 30 transparent in regular mode for analogue interworking ..... 12
+
+3.1.2.1.2 BS 30 transparent in regular mode for digital interworking ..... 12
+
+3.1.2.1.3 BS 30 transparent for Multimedia..... 12
+
+Annex A (informative): ..... Change  
+history ..... 13
+
+# --- 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 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.
+
+# --- 0 Scope
+
+The present document defines a set of Circuit Bearer Services to be provided to PLMN subscribers by a PLMN itself and in connection with other networks. This TS should also be used as a reference for defining the corresponding required mobile network capabilities.
+
+## 0.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] TS 41.004: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] TS 22.001: " Principles of circuit telecommunication services supported by a GSM Public Land Mobile Network (PLMN)".
+- [3] TS 22.004: " General on supplementary services".
+- [4] TS 27.001: " General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+- [5] TS 27.002: " Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities".
+- [6] TS 27.003: " Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
+- [7] TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
+- [8] TS 29.002: " Mobile Application Part (MAP) specification".
+- [9] TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
+- [10] TS 29.010: " Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)".
+- [11] TS 29.011: " Signalling interworking for supplementary services".
+- [12] ITU-T Recommendation V.120: "Support by an ISDN of data terminal equipments with V-series type interface with provision for statistical multiplexing".
+- [13] TR 21.905: "Vocabulary for 3GPP Specifications"
+
+## 0.2 Abbreviations
+
+Abbreviations used in this TS are listed in TS 41.004 [1] and TR 21.905 [13].
+
+# 1 Framework for defining Circuit Bearer Services
+
+Bearer Services are described by attributes, which are intended to be independent. These attributes are described and defined in TS 22.001 [2]. They are grouped into four categories:
+
+- i) Information transfer attributes, which characterize the network capabilities for transferring information from a user access point in a PLMN to a user access point in another network. (Refer to TS 22.001 [2] ).
+- ii) Access attributes, which describe the means for accessing network functions or facilities as seen at the access point in the PLMN (see TS 22.001 [2]).
+- iii) Interworking attributes, which describe properties of the terminating network and its access point. The terminating network may include another PLMN or the originating PLMN.
+- iv) General attributes, which deal with the service in general.
+
+Figure 1 shows the relation between the groups of attributes and their fields of applicability.
+
+![Diagram illustrating the relation between groups of attributes and their fields of applicability. The diagram shows three overlapping circles representing network components: PLMN, Transit Network (note 1), and Terminating Network. The PLMN and Transit Network overlap at an IWF (Interworking Function). The Transit Network and Terminating Network overlap at another IWF. Above the diagram, 'Information Transfer and Access Attributes (note 3)' are indicated by a double-headed arrow spanning the PLMN and IWF areas. Below the diagram, 'Interworking Attributes' are indicated by a double-headed arrow spanning the IWF and Transit Network areas. At the bottom, 'General Attributes (note 2)' are indicated by a long double-headed arrow spanning the entire length from the PLMN to the Terminating Network.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg)
+
+Diagram illustrating the relation between groups of attributes and their fields of applicability. The diagram shows three overlapping circles representing network components: PLMN, Transit Network (note 1), and Terminating Network. The PLMN and Transit Network overlap at an IWF (Interworking Function). The Transit Network and Terminating Network overlap at another IWF. Above the diagram, 'Information Transfer and Access Attributes (note 3)' are indicated by a double-headed arrow spanning the PLMN and IWF areas. Below the diagram, 'Interworking Attributes' are indicated by a double-headed arrow spanning the IWF and Transit Network areas. At the bottom, 'General Attributes (note 2)' are indicated by a long double-headed arrow spanning the entire length from the PLMN to the Terminating Network.
+
+NOTE 1: A transit network may not exist for a Bearer Service.
+
+NOTE 2: Communication may be established from either end.
+
+NOTE 3: The information transfer and access attributes of a Bearer Service relate to a direct peer-to-peer communication of:
+
+- TE to TE;
+- TE to a network gateway (supporting, for example, PSTN interworking); or
+- network gateway to a TE.
+
+**Figure 1: Relation between the groups of attributes and fields of applicability**
+
+The following table lists the individual attributes in each of the four groups. The Bearer Service definitions in this specification are based on the "Minimal Set" of attributes.
+
+**Table 1: List of Bearer Service attributes**
+
+|                                        | Minimal<br>Set |
+|----------------------------------------|----------------|
+| <b>Information Transfer Attributes</b> |                |
+| Information Transfer Mode              | X              |
+| Information Transfer Rate              | X              |
+| Information Transfer Capability        | X              |
+| Establishment of Communication         | X              |
+| Symmetry                               | X              |
+| Communication Configuration            | X              |
+| Data Compression                       |                |
+| <b>Access Attributes</b>               |                |
+| Access Channel and Rate                |                |
+| Signalling Access Protocols            |                |
+| Information Access Protocols           |                |
+| Information Access Structure           | X              |
+| Information Access Rate                | X              |
+| <b>Interworking Attributes</b>         |                |
+| <b>General Attributes</b>              |                |
+| Supplementary Services Provided        |                |
+| Quality of Service                     | X              |
+| Operational and Commercial             |                |
+
+Attributes that are not part of the minimal set provide further technical detail and are required to fully define the use of each Bearer Service.
+
+See specifications [4], [5], [6], [7] for information about the Signalling Access Protocols, Information Access Protocols and related access attributes.
+
+Supplementary services are defined in TS 22.004 [3].
+
+Intercommunication is required with services in the PSTN, ISDN and other PLMNs. The capabilities that describe the Interworking Attributes are described in specifications [8] to [9] and [15].
+
+# 2 Bearer Service categories
+
+All Bearer Service categories provide information transfer between the reference points and allow the use of sub-rate information streams which are rate-adapted.
+
+The Bearer Services can be grouped into the following categories:
+
+- Unrestricted Digital Information (UDI);
+
+Provides the transfer of unrestricted digital information.
+
+- 3,1 kHz (External to the PLMN);
+
+Used to select a "3,1 kHz audio" interworking function at the MSC. This service category is used when interworking with the ISDN or PSTN "3,1 kHz audio" service and includes the capability to select a modem at the interworking function. "External to the PLMN" indicates that the "3,1 kHz audio" service is only used outside of the PLMN, in the ISDN/PSTN. The connection within the PLMN, user access point to the interworking function, is an unrestricted digital connection.
+
+# 3 Bearer Services
+
+This clause provides a list of the existing Bearer Services and indicates the values for each attribute in the minimal set.
+
+The following attributes have the same value for all Bearer Services. Their values are as follows:
+
+|                            |                          |
+|----------------------------|--------------------------|
+| Information Transfer Mode: | "Circuit";               |
+| Information Transfer Rate: | Not applicable (note 1); |
+
+Establishment of Communication: "Demand";  
+ Symmetry: "Bi-directional Symmetric";  
+ Communication Configuration: "Point to point".
+
+NOTE 1: The Information Transfer Rate attribute is not applicable because it depends on the reference point assumed in the PLMN, transit or terminating network.
+
+All asynchronous NT Bearer Services may support data compression to enhance user data throughput.
+
+NT Bearer Services 20 may support V.120 interworking, enabling data terminals connected to an UE to interwork with V.120 [12] terminal adapters on the ISDN as shown in the figure 2 below.
+
+![Figure 2: Model of V.120 Interworking. The diagram shows a sequence of components: Async/Sync Terminal, UE, RAN, MSC, IWF, and V.120 TA. The R reference point is marked at the Async/Sync Terminal. The V.110 interface is shown between the UE and the IWF. The V.120 interface is shown between the IWF and the V.120 TA. The PLMN (Packet Switched Network) is indicated between the R reference point and the IWF. The ISDN (Integrated Services Digital Network) is indicated between the IWF and the V.120 TA.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+Figure 2: Model of V.120 Interworking. The diagram shows a sequence of components: Async/Sync Terminal, UE, RAN, MSC, IWF, and V.120 TA. The R reference point is marked at the Async/Sync Terminal. The V.110 interface is shown between the UE and the IWF. The V.120 interface is shown between the IWF and the V.120 TA. The PLMN (Packet Switched Network) is indicated between the R reference point and the IWF. The ISDN (Integrated Services Digital Network) is indicated between the IWF and the V.120 TA.
+
+Figure 2: Model of V.120 Interworking
+
+Table 2 contains the list of the Bearer Services and the values for the remaining attributes in the minimal set.
+
+Table 2
+
+| Bearer Service Number | Bearer Service Name                                                                                      | Access Structure | Access Rate | Information Transfer Capability | QOS Attribute | Notes |
+|-----------------------|----------------------------------------------------------------------------------------------------------|------------------|-------------|---------------------------------|---------------|-------|
+| 20                    | Asynchronous General Bearer Service                                                                      | Asynch           | note 1      | 3.1 kHz , UDI, RDI              | NT / T        |       |
+| 30                    | Synchronous General Bearer Service                                                                       | Synch            | note 1      | 3.1 kHz , UDI, RDI              | T             |       |
+| Note 1:               | This General Bearer is independent of any nominal rate. It is elaborated in more detail in subclause 3.1 |                  |             |                                 |               |       |
+
+## 3.1 General bearer service user data characteristics
+
+The tables below describe the characteristics of the General Bearer Services. The indicated fixed network user rates are possible, but support of General Bearer Service does not imply support of all rates.
+
+### 3.1.1 BS 20 (asynchronous services)
+
+#### 3.1.1.1 BS 20 T (transparent asynchronous services)
+
+##### 3.1.1.1.1 BS 20 transparent in regular mode for analogue interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS attributes | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|----------------|-----------|---------------|-----------------|-------|
+| 0.3 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 1.2 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 2.4 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 4.8 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 9.6 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 14.4 kbit/s             | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 19.2 kbit/s             | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 28.8 kbit/s             | Asynch           | 3,1 kHz                         | -               | T              | Supported | Supported     | Supported       |       |
+
+##### 3.1.1.1.2 BS 20 transparent in regular mode for digital interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-------|---------------|-----------------|-------|
+| 0.3 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 1.2 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 2.4 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 4.8 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 9.6 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 14.4 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 19.2 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 28.8 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 38.4 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+
+#### 3.1.1.2 BS 20 NT (non-transparent asynchronous services)
+
+##### 3.1.1.2.1 BS 20 non-transparent in regular mode for analogue interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS attributes | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Note   |
+|-------------------------|------------------|---------------------------------|-----------------|----------------|-----------|---------------|-----------------|--------|
+| 0.3 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 1.2 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 2.4 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 4.8 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 9.6 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+| 14.4 kbit/s             | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+| 19.2 kbit/s             | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+| 28.8 kbit/s             | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+|                         | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 1 |
+
+NOTE 1: This is used with high speed modems such as V.90 (56kbit/s). Modem type = 'Autobauding Type 1' is selected. FNUR has no meaning in this case.
+
+NOTE 2: In case of UTRAN and in GERAN Iu mode the FNURs 300, 1200, 2400 and 4800 bit/s towards the fixed network can be provided only with modem type = 'Autobauding Type 1' is selected.
+
+##### 3.1.1.2.2 BS 20 non-transparent in regular mode for digital interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes  |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|--------|
+| 0.3 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 1.2 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 2.4 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 4.8 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 9.6 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 14.4 kbit/s             | Asynch,          | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 19.2 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 28.8 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 38.4 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+
+NOTE 1: In case of UTRAN and in GERAN Iu mode the user rates 300, 1200, 2400 and 4800 bit/s towards the fixed network can be provided only for mobile terminated calls.
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes  |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|--------|
+| 1.2 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 2 |
+| 2.4 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 2 |
+| 4.8 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 2 |
+| 9.6 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 14.4 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 19.2 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 28.8 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 38.4 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 48 kbit/s               | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 56 kbit/s               | Asynch           | UDI                             | V.120           | NT            |           |               |                 |        |
+
+NOTE 1: Requires a new code point in V.120 specification to be defined.
+
+NOTE 2: In case of UTRAN and in GERAN Iu mode the user rates 1200, 2400 and 4800 bit/s toward the fixed network can be provided only for mobile terminated calls.
+
+##### 3.1.1.2.3 BS 20 non-transparent for PIAFS
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|-------|
+| 32 kbit/s               | Asynch           | UDI                             | PIAFS           | NT            | Supported | -             | -               |       |
+| 64 kbit/s               | Asynch           | UDI                             | PIAFS           | NT            | Supported | -             | -               |       |
+
+##### 3.1.1.2.4 BS 20 non-transparent for Frame Tunnelling Mode
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation    | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|--------------------|---------------|-----------|---------------|-----------------|-------|
+| 56kbit/s                | Asynch           | RDI                             | X.31 flag stuffing | NT            | Supported | Supported     | Supported       |       |
+| 64 kbit/s               | Asynch           | UDI                             | X.31 flag stuffing | NT            | Supported | Supported     | Supported       |       |
+
+### 3.1.2 BS 30 (synchronous services)
+
+#### 3.1.2.1 BS 30 T (transparent synchronous services)
+
+##### 3.1.2.1.1 BS 30 transparent in regular mode for analogue interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS attributes | UTRAN     | GERAN Iu mode | GERAN A/Gb | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|----------------|-----------|---------------|------------|-------|
+| 1.2 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 2.4 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 4.8 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 9.6 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 14.4 kbit/s             | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 19.2 kbit/s             | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 28.8 kbit/s             | Synch            | 3,1 kHz                         | -               | T              | Supported | Supported     | Supported  |       |
+
+##### 3.1.2.1.2 BS 30 transparent in regular mode for digital interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|-------|
+| 1.2 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 2.4 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 4.8 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 9.6 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 14.4 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 19.2 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 28.8 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 38.4 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 48 kbit/s               | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 56 kbit/s               | Synch            | UDI                             | V.110           | T             | Supported | Supported     | Supported       |       |
+| 56 kbit/s               | Synch            | RDI                             | -               | T             | Supported | Supported     | Supported       |       |
+| 64 kbit/s               | Synch            | UDI                             | -               | T             | Supported | Supported     | Supported       |       |
+
+##### 3.1.2.1.3 BS 30 transparent for Multimedia
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes  |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|--------|
+| 28.8 kbit/s             | Synch            | 3.1kHz Audio                    | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+| 32.0 kbit/s             | Synch            | UDI                             | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+| 33.6 kbit/s             | Synch            | 3.1kHz Audio                    | H.223 & H.245   | T             | Supported | Supported     | Supported       | Note 1 |
+| 56 kbit/s               | Synch            | RDI                             | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+| 64 kbit/s               | Synch            | UDI                             | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+
+NOTE 1: 33.6kbit/s FNURs is applicable only for UTRAN.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                                                 |        |        |                    |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|-----------------------------------------------------------------------------------------------------------------|--------|--------|--------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                                                 | Old    | New    | WI                 |
+| Jun 1999       |           |           | 02.02  |     |     |       |     | Transferred to 3GPP SA1                                                                                         | 8.0.0  | 3.0.0  |                    |
+| SP-05          | SP-99479  | S1-99608  | 22.002 | 001 |     | R99   | D   | Editorial changes for alignment                                                                                 | 3.0.0  | 3.1.0  |                    |
+| SP-05          | SP-99446  | S1-99659  | 22.002 | 002 |     | R99   | B   | Bearer Services                                                                                                 | 3.0.0  | 3.1.0  |                    |
+| SP-06          | SP-99520  | S1-991008 | 22.002 | 003 |     | R99   | B   | Addition of new general bearer service user data characteristics for 33.6kbit/s modem, FTM and multimedia calls | 3.1.0  | 3.2.0  |                    |
+| SP-06          | SP-99520  | S1-991075 | 22.002 | 004 |     | R99   | C   | 22.002 made only applicable to CS Domain.                                                                       | 3.1.0  | 3.2.0  |                    |
+| SP-07          | SP-000054 | S1-000132 | 22.002 | 005 |     | R99   | F   | Corrections on 3,1 kHz Audio support                                                                            | 3.2.0  | 3.3.0  |                    |
+| SP-08          | SP-000192 | S1-000274 | 22.002 | 006 |     | R99   | F   | Lower User Rates in UMTS for Circuit Switched Data Services                                                     | 3.3.0  | 3.4.0  |                    |
+| SP-09          | SP-000371 | S1-000561 | 22.002 | 007 |     | R99   | F   | 32 kbit/s UDI/RDI multimedia in GSM                                                                             | 3.4.0  | 3.5.0  |                    |
+| SP-09          | SP-000390 | S1-000595 | 22.002 | 008 |     | R4    | C   | Deletion of bearer service BS 30 NT                                                                             | 3.4.0  | 4.0.0  |                    |
+| SP-11          | SP-010039 | S1-010253 | 22.002 | 010 |     | Rel-4 | C   | CR to 22.002 clarification on Circuit Switched Bearer Services in UMTS                                          | 4.0.0  | 4.1.0  | CS Bearers in UMTS |
+| SP-11          | SP-010040 | S1-010254 | 22.002 | 011 |     | Rel-4 | D   | Restructuring of 22.002                                                                                         | 4.0.0  | 4.1.0  | CS Bearers in UMTS |
+| SP-11          | SP-010040 | S1-010266 | 22.002 | 012 |     | Rel-4 | D   | Restructuring of tables in section 3.1                                                                          | 4.0.0  | 4.1.0  | CS Bearers in UMTS |
+| SP-12          | SP-010257 | S1-010357 | 22.002 | 013 |     | Rel-4 | F   | Corrections to erroneous implementation of CRs SP-010039 and SP-010040 to 22.002.                               | 4.1.0  | 4.2.0  | TEI4               |
+| SP-16          | SP-020244 | S1-021076 | 22.002 | 014 |     | Rel-5 | F   | CR to 22.002 Correction of terminology and references                                                           | 4.2.0  | 5.0.0  | TEI5               |
+| SP-26          | SP-040744 | S1-040997 | 22.002 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                                                                     | 5.0.0  | 6.0.0  |                    |
+| SP-36          |           |           | 22.002 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                                                                     | 6.0.0  | 7.0.0  |                    |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                                                                     | 7.0.0  | 8.0.0  |                    |
+| 2009-12        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-9 version (MCC)                                                                                   | 8.0.0  | 9.0.0  |                    |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                                                                  | 9.0.0  | 10.0.0 |                    |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                                                                  | 10.0.0 | 11.0.0 |                    |

marked/Rel-11/22_series/22003/raw.md

@@ -0,0 +1,631 @@
+
+
+
+
+All rights reserved.
+
+# Contents
+
+Foreword .....4
+
+0 Scope.....5
+
+0.1 Normative references .....5
+
+0.2 Abbreviations .....5
+
+1 Framework for describing circuit teleservices supported .....6
+
+2 List of the teleservice attributes .....7
+
+3 List of teleservice categories and individual teleservices .....7
+
+4 Description of individual teleservices.....7
+
+5 Bearer capabilities supporting teleservices.....8
+
+**Annex A (normative): Description of individual Teleservices.....9**
+
+A.1 Individual Teleservices .....9
+
+A.1.1 Telephony.....9
+
+A.1.2 Emergency calls .....11
+
+A.1.3 Short Message Service (SMS).....12
+
+A.1.3.1 Short message service MT/PP .....12
+
+A.1.3.2 Short message service MO/PP.....13
+
+A.1.3.3 Cell Broadcast Service (CBS) .....14
+
+A.1.3.4 Short message service description.....14
+
+A.1.4 Alternate speech/facsimile G3 .....17
+
+A.1.4 Alternate speech/facsimile G3 .....17
+
+A.1.5 Automatic facsimile G3 .....18
+
+A.1.6 Voice Group Call Service .....19
+
+A.1.7 Voice Broadcast Service .....20
+
+Annex B (informative): Change history.....21
+
+# --- 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.
+
+# --- 0 Scope
+
+This Technical Specification (TS) describes and defines a recommended set of Circuit Teleservices to be supported by a PLMN in connection with other networks as a basis for defining the network capabilities required.
+
+## 0.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 TR 21.905: "Vocabulary for 3GPP Specifications"
+- [2] 3GPP TS 22.001: " Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
+- [3] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
+- [4] 3GPP TS 22.004: " General on supplementary services".
+- [5] 3GPP TS42.068 : "Voice Group Call Service (VGCS) - Stage 1".
+- [6] 3GPP TS 42.069 : "Voice Broadcast Service (VBS) - Stage 1".
+- [7] 3GPP TS 23.040: " Technical realization of the Short Message Service (SMS) Point-to-Point (PP)".
+- [8] 3GPP TS 23.041 : " Technical realization of Short Message Service Cell Broadcast (SMSCB)".
+- [9] 3GPP TS 24.008: "Mobile radio interface layer 3 specification".
+- [10] 3GPP TS 27.001 : " General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+- [11] 3GPP TS 27.005: " Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
+- [12] ITU-T Recommendation T.4: "Standardization of group 3 facsimile apparatus for document transmission".
+- [13] ITU-T Recommendation T.30: "Procedures for document facsimile transmission in the general switched telephone network".
+- [14] 3GPP TS 22.101: "Service Principles".
+
+## 0.2 Abbreviations
+
+Abbreviations used in this TS are listed in 3GPP TR 21.905[1].
+
+# --- 1 Framework for describing circuit teleservices supported
+
+Teleservices supported by a PLMN are described by a number of attributes which are intended to be largely independent.
+
+These attributes are described and defined in specification 3GPP TS 22.001 [2].
+
+They are grouped into three categories:
+
+- High layer attributes;
+- Low layer attributes (describing the Bearer capabilities which support the Teleservice).
+  - information transfer attributes;
+  - access attributes.
+- General attributes.
+
+Figure 1 shows the relationship between the different categories of services attributes, and their scope within a Teleservice.
+
+![Diagram showing the relationship between High layer attributes and Low layer attributes across a network path: TE -> PLMN (originating network) -> Possible transit network -> Terminating network -> TE. High layer attributes span the entire path, while Low layer attributes are contained within the PLMN.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg)
+
+The diagram illustrates the scope of service attributes across a network path. The path consists of five components connected in series: a Terminal Equipment (TE) box, a PLMN (originating network) box, a Possible transit network box, a Terminating network box, and another TE box. Above the diagram, a long double-headed arrow labeled 'High layer attributes' spans from the first TE to the second TE. Above the PLMN box, a shorter double-headed arrow labeled 'Low layer attributes (=bearer capability)' spans the width of the PLMN box. Vertical lines connect the first TE to the start of the high layer attribute arrow and the end of the high layer attribute arrow to the second TE.
+
+Diagram showing the relationship between High layer attributes and Low layer attributes across a network path: TE -> PLMN (originating network) -> Possible transit network -> Terminating network -> TE. High layer attributes span the entire path, while Low layer attributes are contained within the PLMN.
+
+NOTE 1: A transit network may not exist.
+
+NOTE 2: Communication may be established from both ends in principle.
+
+**Figure 1: Relationship between the categories of services attributes and their scope within a Teleservice**
+
+# 2 List of the teleservice attributes
+
+Table 1 gives the list of the attributes. For the definitions and possible values of these attributes, see 3GPP TS 22.001 [2].
+
+**Table 1: List of Teleservice attributes**
+
+|                                                                                                         |                                           |                                                                                                  |
+|---------------------------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------|
+| 1. High layer capabilities                                                                              | 1.1 Type of user information              | Dominant Teleservice attribute category<br><br>Secondary attributes<br>" "<br><br>" "<br><br>" " |
+|                                                                                                         | 1.2 Layer 4 protocol functions            |                                                                                                  |
+|                                                                                                         | 1.3 Layer 5 " "                           |                                                                                                  |
+|                                                                                                         | 1.4 Layer 6 " "                           |                                                                                                  |
+|                                                                                                         | 1.5 Layer 7 " "                           |                                                                                                  |
+| 2. Low layer capabilities<br>(describing the Bearer<br>capability which<br>supports the<br>Teleservice) | 2.1 Information transfer                  | Individual services (in the category)                                                            |
+|                                                                                                         | 2.1.1 Information transfer capabilities   |                                                                                                  |
+|                                                                                                         | 2.1.2 Information transfer mode           |                                                                                                  |
+|                                                                                                         | 2.1.3 Information transfer rate           |                                                                                                  |
+|                                                                                                         | 2.1.4 Structure                           |                                                                                                  |
+|                                                                                                         | 2.1.5 Establishment of communication      |                                                                                                  |
+|                                                                                                         | 2.1.6 Communication configuration         |                                                                                                  |
+|                                                                                                         | 2.1.7 Symmetry                            | Qualifying attributes<br>" "<br>" "<br>" "                                                       |
+|                                                                                                         | 2.2 Access (3GPP TS 22.001)               |                                                                                                  |
+|                                                                                                         | 2.2.1 Signalling access                   |                                                                                                  |
+|                                                                                                         | 2.2.2 Information access                  | Further specify the individual services                                                          |
+|                                                                                                         | 2.3 Interworking                          |                                                                                                  |
+|                                                                                                         | 2.3.1 Terminating network type            |                                                                                                  |
+|                                                                                                         | 2.3.2 National/international interworking |                                                                                                  |
+|                                                                                                         | 2.3.3 Interface of terminal equipment     |                                                                                                  |
+| 3. General                                                                                              | 3.1 Supplementary services provided       |                                                                                                  |
+|                                                                                                         | 3.2 Quality of service                    |                                                                                                  |
+|                                                                                                         | 3.3 Operational and commercial            |                                                                                                  |
+
+# 3 List of teleservice categories and individual teleservices
+
+Table 2 presents a list of all Teleservices categories and of individual Teleservices and the associated dominant and secondary attributes.
+
+# 4 Description of individual teleservices
+
+The annex contains a data sheet per Teleservice with all attributes and comments.
+
+# 5 Bearer capabilities supporting teleservices
+
+According to specification 3GPP TS 22.001 [2] the Bearer Capability defines the technical features of a Teleservice as they appear to the user at the customer access point or an appropriate interface of a fixed network. The Bearer Capability is characterized by information transfer, access and interworking attributes. The same set of attributes as for a Bearer Service is used. A Bearer Capability is associated with every Teleservice.
+
+**Table 2: Teleservice categories and Teleservices**
+
+| Dominant attribute       | Category of teleservice |                                  | Individual Teleservice |                                        |
+|--------------------------|-------------------------|----------------------------------|------------------------|----------------------------------------|
+|                          | No                      | Name                             | No                     | Name                                   |
+| Type of user information |                         |                                  |                        |                                        |
+| Speech                   | 1                       | Speech transmission              | 11                     | Telephony                              |
+|                          |                         |                                  | 12                     | Emergency Calls                        |
+| Short message            | 2                       | Short message service            | 21                     | Short message MT/PP                    |
+|                          |                         |                                  | 22                     | Short message MO/PP                    |
+|                          |                         |                                  | 23                     | Cell Broadcast Service                 |
+| Facsimile                | 6                       | Facsimile transmission           | 61                     | Alternate speech and facsimile group 3 |
+|                          |                         |                                  | 62                     | Automatic Facsimile group 3            |
+|                          |                         |                                  |                        | T <sup>1</sup><br>NT <sup>2</sup>      |
+| Speech                   | 9                       | Voice Group service <sup>3</sup> | 91                     | Voice Group Call Service               |
+|                          |                         |                                  | 92                     | Voice Broadcast Service                |
+
+Note 1: The transparent facsimile services apply to GERAN A/Gb mode of operation only.
+
+Note 2: The non-transparent facsimile services apply to UTRAN only.
+
+Note 3: The Voice Group Services, TS 91 and TS 92 apply to GERAN A/Gb mode of operation only.
+
+# Annex A (normative): Description of individual Teleservices
+
+NOTE 1: Within the PLMN the "Information transfer rate" attribute is not indicated.
+
+## A.1 Individual Teleservices
+
+### A.1.1 Telephony
+
+| Teleservice 11, Telephony |     |                                |                                       |                                 |                        |
+|---------------------------|-----|--------------------------------|---------------------------------------|---------------------------------|------------------------|
+| A                         | 1.  | 1.1 Type or user information   | speech                                |                                 |                        |
+| T                         | HLC | 1.2 Layer 4 protocol functions | -                                     |                                 |                        |
+| T                         |     | 1.3 Layer 5 protocol functions | -                                     |                                 |                        |
+| R                         |     | 1.4 Layer 6 protocol functions | -                                     |                                 |                        |
+| I                         |     | 1.5 Layer 7 protocol functions | -                                     |                                 |                        |
+| B                         | 2.  | 2.1                            | 2.1.1 Information transfer capability | speech (digital representation) |                        |
+| U                         | LLC |                                | 2.1.2 Information transfer mode       | circuit                         |                        |
+| T                         |     | Inform                         | 2.1.3 Information transfer rate       | not applicable                  |                        |
+| E                         |     | transfer                       | 2.1.4 Structure                       | not applicable                  |                        |
+| S                         |     |                                | 2.1.5 Establishment of connection     | demand MO MT                    |                        |
+|                           |     |                                | 2.1.6 Communication configuration     | point-to-point                  |                        |
+|                           |     |                                | 2.1.7 Symmetry                        | bidirectional symmetry          |                        |
+|                           |     | 2.2                            | 2.2.1 Signalling access               | manual                          |                        |
+|                           |     | Access                         | 2.2.2 Information access              | rate                            | full rate/half rate    |
+|                           |     | at UE                          | (3GPP TS 22.001)                      | interface                       |                        |
+|                           |     | 2.3                            | 2.3.1 Visible network type            | PSTN/ISDN/ -PLMN                |                        |
+|                           |     | Inter-                         | 2.3.2 National/Internat. interworking | international/national          |                        |
+|                           |     | working                        | 2.3.3 Interface of TE to terminating  | 2 wire, analogue                | 4 wire<br>S (B+B+D) ME |
+|                           | 3.  |                                | 3.1 Supplementary service provided    | 3GPP TS 22.004                  |                        |
+|                           | Gen |                                | 3.2 Quality of service                |                                 |                        |
+
+#### Comments:
+
+This service provides the transmission of speech information and audible signalling tones of the PSTN/ISDN. In the PLMN and the fixed network processing technique appropriate for speech such as analogue transmission, echo cancellation and low bit rate voice encoding may be used. Hence, bit integrity is not assured.
+
+- 1) Transparency for telephone signalling tones is provided.
+- 2) Transparency for voice band facsimile signals is not mandatory. (Appropriate bearer services see 3GPP TS 22.002 [3].)
+- 3) Transparency for end to end speech encryption is not mandatory. If a user needs to apply this technique an appropriate bearer service (3GPP TS 22.002 [3]) can be used.
+- 4) Transmission of DTMF is provided in the mobile to fixed direction (e.g. for controlling voice mail boxes) during any time of an established call.
+- 5) In A/Gb mode of operation (GERAN) speech teleservices may be provided using the Full Rate (full rate, version 1), Enhanced Full Rate (full rate, version 2), Half Rate (half rate, version 1), Adaptive Multirate (AMR) or
+
+Wideband Adaptive Multirate (AMR-WB) speech codecs. The default speech codec to provide speech service in this case is Full Rate.
+
+- 6) In UTRAN operation speech teleservices may be provided using the Adaptive Multirate (AMR) or Wideband Adaptive Multirate (AMR-WB) speech codecs. The default speech codec to provide speech service in this case is AMR.
+- 7) In GERAN Iu mode of operation speech teleservices may be provided using the Adaptive Multirate (AMR) or Wideband Adaptive Multirate (AMR-WB) or Enhanced Full Rate (EFR) speech codecs. Both the Narrow Band AMR codec family (Full Rate AMR and Half Rate AMR) and the EFR codec shall be supported by the UE. The network shall either support at least the AMR or the EFR codec.
+
+### A.1.2 Emergency calls
+
+| Teleservice 12, Emergency calls |     |                                |                                            |                                                                                                                         |
+|---------------------------------|-----|--------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
+| A                               | 1.  | 1.1 Type or user information   |                                            | speech (with or without additional emergency related data)                                                              |
+| T                               | HLC | 1.2 Layer 4 protocol functions |                                            | -                                                                                                                       |
+| T                               |     | 1.3 Layer 5 protocol functions |                                            | -                                                                                                                       |
+| R                               |     | 1.4 Layer 6 protocol functions |                                            | -                                                                                                                       |
+| I                               |     | 1.5 Layer 7 protocol functions |                                            | -                                                                                                                       |
+| B                               | 2.  | 2.1                            | 2.1.1 Information transfer capability      | speech (digital representation and may include emergency related data)                                                  |
+| U                               | LLC |                                | 2.1.2 Information transfer mode            | circuit                                                                                                                 |
+| T                               |     | Inform                         | 2.1.3 Information transfer rate            | not applicable for speech only call                                                                                     |
+| E                               |     | transfer                       | 2.1.4 Structure                            | not applicable                                                                                                          |
+| S                               |     |                                | 2.1.5 Establishment of connection          | demand MO MT                                                                                                            |
+|                                 |     |                                | 2.1.6 Communication configuration          | point-to-point                                                                                                          |
+|                                 |     |                                | 2.1.7 Symmetry                             | bidirectional symmetry (when present the data component may be a symmetric or an asymmetric bidirectional transmission) |
+|                                 |     | 2.2                            | 2.2.1 Signalling access                    | manual                                                                                                                  |
+|                                 |     | Access                         | 2.2.2 Information access                   | rate full rate/half rate                                                                                                |
+|                                 |     | at UE                          | (3GPP TS 22.001)                           | interface                                                                                                               |
+|                                 |     | 2.3                            | 2.3.1 Visible network type                 | PSTN ISDN                                                                                                               |
+|                                 |     | Inter-                         | 2.3.2 National/Internat. interworking      | national                                                                                                                |
+|                                 |     | working                        | 2.3.3 Interface of TE to terminating Ntwk. | 2 wire 4 wire                                                                                                           |
+|                                 | 3.  | 3.1                            | Supplementary service provided             | 3GPP TS 22.004 (see note 3)                                                                                             |
+|                                 | Gen | 3.2                            | Quality of service                         |                                                                                                                         |
+
+#### Comments:
+
+- 1) A standardized access method throughout all PLMNs is mandatory. See 3GPP TS 22.101 [14] for further information on emergency call requirements.
+- 2) It shall be an option of the network operator whether to accept emergency calls coming from user equipment which do not transmit an IMSI or a TMSI.
+- 3) Emergency calls supersede all constraints imposed by supplementary services or user equipment features used for other Tele or Bearer services. The lock state of the UE is overridden by the SOS-procedure.
+- 4) Emergency calls will be routed to the emergency services in accordance with national regulations.
+- 5) In order to help identifying callers in cases of misuse databases in the PLMN may be accessed to retrieve the identity of the calling UE. When applicable, and subject to national regulations, the Public Safety Answering Point (PSAP) may use the related data sent in conjunction with the emergency call and provide this information to the lawful authorities.
+
+### A.1.3 Short Message Service (SMS)
+
+#### A.1.3.1 Short message service MT/PP
+
+| Teleservice 21, Short Message MT point-to-point 1), 2) |     |                                    |                                                              |                                      |
+|--------------------------------------------------------|-----|------------------------------------|--------------------------------------------------------------|--------------------------------------|
+| A                                                      | 1.  | 1.1 Type or user information       |                                                              | short message, $\leq 160$ characters |
+| T                                                      |     | 1.2 Layer 4 protocol functions     |                                                              |                                      |
+| T                                                      |     | 1.3 Layer 5 protocol functions     |                                                              | see 3GPP TS23.040                    |
+| R                                                      |     | 1.4 Layer 6 protocol functions     |                                                              | see 3GPP TS 23.040                   |
+| I                                                      |     | 1.5 Layer 7 protocol functions     |                                                              | see 3GPP TS 23.040                   |
+| B                                                      | 2.  | 2.1<br><br>Inform<br><br>transfer  | 2.1.1 Information transfer capability                        | not applicable                       |
+| U                                                      |     |                                    | 2.1.2 Information transfer mode                              | not applicable                       |
+| T                                                      |     |                                    | 2.1.3 Information transfer rate                              | not applicable                       |
+| E                                                      |     |                                    | 2.1.4 Structure                                              | not applicable                       |
+| S                                                      |     |                                    | 2.1.5 Establishment of connection                            | not applicable                       |
+|                                                        |     |                                    | 2.1.6 Communication configuration                            | not applicable                       |
+|                                                        |     |                                    | 2.1.7 Symmetry                                               | not applicable                       |
+|                                                        |     | 2.2<br>Access<br>at UE             | 2.2.1 Signalling access see 3GPP TS 27.005                   |                                      |
+|                                                        |     |                                    | 2.2.2 Information access                                     | rate not applicable                  |
+|                                                        |     |                                    | (3GPP TS 22.001)                                             | interface                            |
+|                                                        |     | 2.3<br>Inter-<br>working           | 2.3.1 Visible network type not applicable 3)                 |                                      |
+|                                                        |     |                                    | 2.3.2 National/Internat. interworking not applicable 3)      |                                      |
+|                                                        |     |                                    | 2.3.3 Interface of TE to terminating Ntwk. not applicable 3) |                                      |
+|                                                        | 3.  | 3.1 Supplementary service provided |                                                              | 3GPP TS 22.004                       |
+|                                                        | Gen | 3.2 Quality of service             |                                                              |                                      |
+
+##### **Comments:**
+
+- 1) This service provides the transmission of a short message from a message handling system (service centre) to a user equipment. The service centre is functionally separated from the PLMN.
+- 2) After reception an acknowledgement message should be sent back.
+- 3) There is only an interworking between the PLMN and SMS Service Centre (SMS-SC). Connections from the fixed network to the SMS-SC are out of the scope of the 3GPP specifications.
+- 4) The information transfer attributes refer to the connection-oriented services (ISDN, Bluebook Q.931). The Short Message Service is not a connection orientated service, hence the transfer attributes here are not applicable.
+- 5) SMS MT/PP teleservice can be provided via both the CS and PS domains.
+
+#### A.1.3.2 Short message service MO/PP
+
+| Teleservice 22, Short Message MO point-to-point 1), 2) |    |                                |                                            |
+|--------------------------------------------------------|----|--------------------------------|--------------------------------------------|
+| A                                                      | 1. | 1.1 Type or user information   | short message, $\leq 160$ characters       |
+| T                                                      |    | 1.2 Layer 4 protocol functions |                                            |
+| T                                                      |    | 1.3 Layer 5 protocol functions | see 3GPP TS 23.040                         |
+| R                                                      |    | 1.4 Layer 6 protocol functions | see 3GPP TS 23.040                         |
+| I                                                      |    | 1.5 Layer 7 protocol functions | see 3GPP TS 23.040                         |
+| B                                                      | 2. | 2.1                            | 2.1.1 Information transfer capability      |
+| U                                                      |    | Inform                         | not applicable                             |
+| T                                                      |    | transfer                       | 2.1.2 Information transfer mode            |
+| E                                                      |    |                                | not applicable                             |
+| S                                                      |    |                                | 2.1.3 Information transfer rate            |
+|                                                        |    |                                | not applicable                             |
+|                                                        |    |                                | 2.1.4 Structure                            |
+|                                                        |    |                                | not applicable                             |
+|                                                        |    |                                | 2.1.5 Establishment of connection          |
+|                                                        |    |                                | not applicable                             |
+|                                                        |    |                                | 2.1.6 Communication configuration          |
+|                                                        |    |                                | not applicable                             |
+|                                                        |    |                                | 2.1.7 Symmetry                             |
+|                                                        |    |                                | not applicable                             |
+|                                                        |    | 2.2                            | 2.2.1 Signalling access                    |
+|                                                        |    | Access                         | see 3GPP TS 27.005                         |
+|                                                        |    | at UE                          | 2.2.2 Information access                   |
+|                                                        |    |                                | rate                                       |
+|                                                        |    |                                | (3GPP TS 22.001)                           |
+|                                                        |    |                                | interface                                  |
+|                                                        |    | 2.3                            | 2.3.1 Visible network type                 |
+|                                                        |    | Inter-                         | not applicable 3)                          |
+|                                                        |    | working                        | 2.3.2 National/Internat. interworking      |
+|                                                        |    |                                | not applicable 3)                          |
+|                                                        |    |                                | 2.3.3 Interface of TE to terminating Ntwk. |
+|                                                        |    |                                | not applicable 3)                          |
+|                                                        | 3. | 3.1                            | Supplementary service provided             |
+|                                                        |    | Gen                            | 3GPP TS 22.004                             |
+|                                                        |    | 3.2                            | Quality of service                         |
+
+##### Comments:
+
+- 1) This service provides the transmission of a short message from a user equipment to a message handling system (service centre). The service centre is functionally separated from the PLMN.
+- 2) After reception an acknowledgement message is sent back.
+- 3) There is only an interworking between the PLMN and SMS Service Centre (SMS-SC). Connections from the fixed network to the SMS-SC are out of the scope of the 3GPP specifications.
+- 4) The information transfer attributes refer to the connection-oriented services (ISDN, Bluebook Q.931). The Short Message Service is not a connection orientated service, hence the transfer attributes here are not applicable.
+- 5) Information from the following sources at the UE might be transmitted:
+  - a pre-recorded message in a store;
+  - a number from the dialling key pad;
+  - information from an external keyboard or terminal equipment connected to the ME.
+- 6) SMS MO/PP teleservice can be provided via both the CS and PS domains.
+
+#### A.1.3.3 Cell Broadcast Service (CBS)
+
+| Teleservice 23, Cell Broadcast Service |     |                                            |                                        |
+|----------------------------------------|-----|--------------------------------------------|----------------------------------------|
+| A                                      | 1.  | 1.1 Type or user information               | short message, $\leq 93$ characters 4) |
+| T                                      |     | 1.2 Layer 4 protocol functions             |                                        |
+| T                                      |     | 1.3 Layer 5 protocol functions             | see 3GPP TS 23.041                     |
+| R                                      |     | 1.4 Layer 6 protocol functions             | see 3GPP TS 23.041                     |
+| I                                      |     | 1.5 Layer 7 protocol functions             | see 3GPP TS 23.041                     |
+| B                                      | 2.  | 2.1                                        |                                        |
+| U                                      |     | Inform                                     |                                        |
+| T                                      |     | transfer                                   |                                        |
+| E                                      |     | 2.1.1 Information transfer capability      | not applicable                         |
+| S                                      |     | 2.1.2 Information transfer mode            | not applicable                         |
+|                                        |     | 2.1.3 Information transfer rate            | not applicable                         |
+|                                        |     | 2.1.4 Structure                            | not applicable                         |
+|                                        |     | 2.1.5 Establishment of connection          | not applicable                         |
+|                                        |     | 2.1.6 Communication configuration          | not applicable                         |
+|                                        |     | 2.1.7 Symmetry                             |                                        |
+|                                        |     | 2.2                                        |                                        |
+|                                        |     | Access                                     |                                        |
+|                                        |     | at UE                                      |                                        |
+|                                        |     | 2.2.1 Signalling access                    | not applicable                         |
+|                                        |     | 2.2.2 Information access                   | rate not applicable                    |
+|                                        |     | (3GPP TS 22.001)                           | interface not applicable               |
+|                                        |     | 2.3                                        |                                        |
+|                                        |     | Inter-                                     |                                        |
+|                                        |     | working                                    |                                        |
+|                                        |     | 2.3.1 Visible network type                 | 2)                                     |
+|                                        |     | 2.3.2 National/Internat. interworking      | 2)                                     |
+|                                        |     | 2.3.3 Interface of TE to terminating Ntwk. | 2)                                     |
+|                                        | 3.  | 3.1 Supplementary service provided         | 3GPP TS 22.004                         |
+|                                        | Gen | 3.2 Quality of service                     |                                        |
+
+##### Comments:
+
+- 1) This service provides the transmission of a short message from a message handling system to all user equipments in the area of a Base Station. The service centre is functionally separated from the PLMN. There is no acknowledgement message after reception.
+- 2) An interworking only with the Cell-Broadcast Service Centre is foreseen. Connections from the fixed network to the SC are out of the scope of the 3GPP specifications.
+- 3) The information transfer attributes refer to the connection-oriented services (ISDN, Bluebook Q.931). The Short Message Service is not a connection orientated service, hence the transfer attributes here are not applicable.
+- 4) 3GPP TS 23.041 provides up to 15 concatenated "pages" of up to 93 characters each.
+
+#### A.1.3.4 Short message service description
+
+##### Description of:
+
+teleservice 21, "Short message MT/PP";
+
+teleservice 22 "Short message MO/PP"; and
+
+teleservice 23 "Cell Broadcast Service ".
+
+##### 1 Introduction
+
+The purpose of this annex is to describe the short message teleservice.
+
+Three different types of short messages are defined, namely short message MT/PP (Mobile Terminated/Point-to-point), short message MO/PP (Mobile Originated/Point-to-point) and Cell Broadcast Service messages.
+
+##### 2 Definition of the short message service MT/PP and MO/PP
+
+For both mobile originated and mobile terminated services the Service Centre acts as store and forward centre. The Service Centre is functionally separate from the PLMN although this does not preclude an integrated implementation. More than one service centre may be connected to a PLMN. Messages may be input to the service centre from a fixed network customer by means of a suitable telecommunications service either from the fixed network, e.g. speech, telex, facsimile, etc. or from a mobile network customer. The list is not intended to be comprehensive and it is entirely open to the service centre provider what telecommunication services it supports. The service centre shall then reformat the message into that provided by the short message service, for delivery to the user equipment.
+
+For mobile originated SMS messages the SMT formats the message into that used by the SMS service and sends to the service centre (to allow interworking with ERMES also ERMES-format addresses may be sent from the UE to the SC). In general the user may use alphanumeric addresses for more user convenience. In principle the message may be intended for a subscriber on the fixed network or for another mobile subscriber. For the message to another mobile subscriber the service centre should deliver as described in this section.
+
+The message text is limited to a length of 160 characters.
+
+The originator does not need to know the location of the mobile subscriber to whom he wants to send a message. The message is addressed to the recipient's Directory Number.
+
+As a part of the basic service for both MT and MO, an acknowledgement will be provided on a message by message basis to the SC (MT) or UE (MO). This acknowledgement indicates that the PLMN has successfully transferred the message to the UE (MT) or SC (MO).
+
+Optionally, the SC may offer final delivery notification to the originator. In this case, the originator may request to have a notification returned from the SC informing her about the delivery of the Short Message to the recipient. This delivery report indicates whether this particular message has been correctly received at the receiving station or not, to the extent that the SC is able to establish this. It does not indicate whether the message has been read. If the delivery report is negative, i.e. the message has not been successfully delivered to the recipient, it shall include the failure cause.
+
+The delivery report is sent to the originator, if reachable, as soon as the information (positive or negative) is available.
+
+In addition, the SC may use the delivery report capabilities for other purposes, such as intermediate status reports etc.
+
+All point-to-point short messages are either to or from the service centre. A message from one user equipment to another must pass through a service centre. This case is effectively an MO and MT message together. The two transactions are separate, though clearly related.
+
+Point-to-point messages may be sent or received when the UE is engaged on a call (voice or data), or in idle mode. However, messages which overlap the boundary of such a call, or during a handover, may be lost, in which case they will be sent again.
+
+The accounting between the SC and PLMN if applicable is for agreement between those parties.
+
+The originator of a short message may notify the SC of an expiry time after which the message is no longer of value and may be deleted by the SC. During the validity period of the message, the SC shall try to deliver the message. After the expiry date the SC will take no further step to deliver the message, but its status may be kept by the SC to enable the originator to enquire the result. If the originator of the short message does not request any expiry time a standard value, e.g. 24 hours, is used.
+
+The Service Centre may give a short message a priority status. This priority message will be attempted to be delivered irrespective of whether or not the UE has been identified as temporarily absent. Delivery of non-priority messages will not be attempted if the UE has been identified as temporarily absent.
+
+If necessary, the originator may request the SC to perform specific operations on a previously submitted short message, such as provision/cancellation of a report or deletion of the short message.
+
+The recipient of a short message will be informed by the message about the date and time it was submitted to the SC.
+
+If the UE Message Store is full, the Message Store Overflow indicator is activated, and any further messages received will not be accepted. An appropriate specific non-acknowledgement message shall be returned. By help of an optional flow control mechanism further waiting short messages will be transmitted after the UE has memory available again.
+
+##### 3 Reply path
+
+The reply path facility is an enhancement to the point-to-point SMS. In the mobile originated case the mobile user will request his Service Centre to guarantee to forward a single reply to his message back to him (Reply Path).
+
+In the mobile terminated case the recipient of the Short Message will get an indication by the service centre that a reply via this Service centre will be accepted on a subscriptionless basis. The recipient may then submit a reply to this SC (within a period of time defined by the SC operator), which is then forwarded to the submitter of the original message.
+
+No subscription with the Service centre is needed by the replying user. The costs, if any, for the reply path are allocated to the originator.
+
+##### 4 Definition of the Cell Broadcast Service
+
+The cell broadcast service is a Teleservice which enables an Information Provider to submit short messages for broadcasting to a specified area within the PLMN.
+
+The cell broadcast service is characterized by the following aspects:
+
+- No acknowledgement is sent from the UE.
+- The cell broadcast message is sent in a limited area, defined by the originator of the message, by agreement with the PLMN.
+- An identifier is associated with each message. This identifier is received by the UE and used by the short message function of the UE not to store broadcast messages which are not wanted or which have already been received.
+- Generally, cell broadcast messages will be sent continuously, so that all such messages are sent in turn, and then repeated. The cycle time will need to be short enough for important messages to be received by travellers moving through a group of cells.
+- Cell broadcast messages are MT only. The origination of these messages is outside the scope of 3GPP specifications.
+- The maximum length of each cell broadcast message will be 93 characters.
+- Cell broadcast DRX mode is defined to improve the battery life for User equipment. This feature is optional.
+- Reception of CBS messages for a UE is not a requirement if it is connected in the CS domain. It should be possible for a UE to receive messages if it is connected in the PS domain and no data is currently transmitted.
+
+### A.1.4 Alternate speech/facsimile G3
+
+| Teleservice 61, Alternate speech and facsimile group 3 |                   |                                |                                                  |                              |                 |
+|--------------------------------------------------------|-------------------|--------------------------------|--------------------------------------------------|------------------------------|-----------------|
+| A<br>T<br>T<br>R<br>I<br>B<br>U<br>T<br>E<br>S         | HLC               | 1.1 Type or user information   | facsimile/speech                                 |                              |                 |
+|                                                        |                   | 1.2 Layer 4 protocol functions | Procedures according to ITU-T                    |                              |                 |
+|                                                        |                   | 1.3 Layer 5 protocol functions | recommendation T.30/T4.                          |                              |                 |
+|                                                        |                   | 1.4 Layer 6 protocol functions |                                                  |                              |                 |
+|                                                        |                   | 1.5 Layer 7 protocol functions |                                                  |                              |                 |
+| I<br>B<br>U<br>T<br>E<br>S                             | LLC               | 2.1<br><br>Inform<br>transfer  | 2.1.1 Information transfer capability            | alternate speech/group 3 fax |                 |
+|                                                        |                   |                                | 2.1.2 Information transfer mode                  | circuit                      |                 |
+|                                                        |                   |                                | 2.1.3 Information transfer rate                  | up to 14400 bits/s           |                 |
+|                                                        |                   |                                | 2.1.4 Structure                                  | not applicable               |                 |
+|                                                        |                   |                                | 2.1.5 Establishment of connection                | demand (MO MT)               |                 |
+|                                                        |                   |                                | 2.1.6 Communication configuration                | point-to-point               |                 |
+|                                                        |                   |                                | 2.1.7 Symmetry                                   | bidirectional symmetry       |                 |
+|                                                        |                   | 2.2<br><br>Access<br>at UE     | 2.2.1 Signalling access                          | 1.440/450 (GSM 04.08)        |                 |
+|                                                        |                   |                                | 2.2.2 Information access<br><br>(3GPP TS 22.001) | rate                         | fullrate        |
+|                                                        |                   |                                |                                                  | interface                    | 2 wire analogue |
+| I<br>B<br>U<br>T<br>E<br>S                             | Inter-<br>working | 2.3                            | 2.3.1 Visible network type                       | PSTN                         | ISDN PLMN       |
+|                                                        |                   |                                | 2.3.2 National/Internat. interworking            | international/national       |                 |
+|                                                        |                   |                                | 2.3.3 Interface of TE to terminating             | 2 wire, analogue/UE          |                 |
+|                                                        |                   | 3.<br><br>Gen                  | 3.1 Supplementary service provided               | 3GPP TS 22.004               |                 |
+|                                                        |                   |                                | 3.2 Quality of service                           |                              |                 |
+
+#### Comments:
+
+- 1) This Teleservice allows the connection of ITU-T group 3 fax apparatus (send and/or receive) to the user equipments of a PLMN. Facsimile connections may be established to/from group 3 apparatus in the PSTN, ISDN or PLMN.
+- 2) A high quality of service even under bad radio conditions and/or in connection to/from moving vehicles is required.
+- 3) Both speech and fax portions of the call will use a full rate. The fax portion of the call may use multiple full rate channels.
+- 4) Subscription for TS61 includes also subscription for TS62 (refer to 3GPP TS 22.001 [2]). For this reason and in order to allow a user to change between ME supporting TS61 or TS62 both a network and a UE supporting TS61 shall also accept call set-ups for TS62. If a subscriber originates/receives a TS61 call but either the UE or the network do not support TS61 (but supports TS62), then TS61 shall be negotiated to TS62 in accordance to the rules specified in 3GPP TS 27.001 [10]. If the negotiation does not succeed, then the call shall be released.
+
+### A.1.5 Automatic facsimile G3
+
+| Teleservice 62, Alternate facsimile group 3 |          |                                |                                       |           |                               |
+|---------------------------------------------|----------|--------------------------------|---------------------------------------|-----------|-------------------------------|
+| A                                           | 1.       | 1.1 Type or user information   |                                       |           | facsimile                     |
+| T                                           | HLC      | 1.2 Layer 4 protocol functions |                                       |           | Procedures according to ITU-T |
+| T                                           |          | 1.3 Layer 5 protocol functions |                                       |           | recommendation T.30/T4.       |
+| R                                           |          | 1.4 Layer 6 protocol functions |                                       |           |                               |
+| I                                           |          | 1.5 Layer 7 protocol functions |                                       |           |                               |
+| B                                           | 2.       | 2.1                            | 2.1.1 Information transfer capability |           | Facsimile group 3             |
+| U                                           | LLC      |                                | 2.1.2 Information transfer mode       |           | Circuit                       |
+| T                                           | Inform   |                                | 2.1.3 Information transfer rate       |           | up to 14400 bits/s            |
+| E                                           | Transfer |                                | 2.1.4 Structure                       |           | not applicable                |
+| S                                           |          |                                | 2.1.5 Establishment of connection     |           | demand (MO MT)                |
+|                                             |          |                                | 2.1.6 Communication configuration     |           | point-to-point                |
+|                                             |          |                                | 2.1.7 Symmetry                        |           | bidirectional symmetry        |
+|                                             |          | 2.2                            | 2.2.1 Signalling access               |           | 1.440/450 (GSM 04.08)         |
+|                                             | Access   |                                | 2.2.2 Information access              | rate      | Fullrate                      |
+|                                             | At UE    |                                | (3GPP TS 22.001)                      | interface | 2 wire, analogue              |
+|                                             |          | 2.3                            | 2.3.1 Visible network type            | PSTN      | ISDN PLMN                     |
+|                                             | Inter-   |                                | 2.3.2 National/Internat. interworking |           | international/national        |
+|                                             | Working  |                                | 2.3.3 Interface of TE to terminating  |           | 2 wire, analogue/UE           |
+|                                             | 3.       | 3.1                            | Supplementary service provided        |           | 3GPP TS 22.004                |
+|                                             | Gen      | 3.2                            | Quality of service                    |           |                               |
+
+#### Comments:
+
+- 1) This teleservice supports a Facsimile Group 3 Autocalling/Autoanswering mode only.
+- 2) This teleservice allows connection of ITU-T group 3 fax apparatus to and from the user equipments of a PLMN. Facsimile connections may be established to and from group 3 apparatus in the PSTN, ISDN or PLMN.
+- 3) A high quality of service even under bad radio conditions and/or in connection to/from moving vehicles is required.
+- 4) If a Network receives a call set-up for TS61 and if the subscriber in question has a subscription for TS62 only, then the network shall negotiate TS61 to TS62 in accordance to the rules specified in 3GPP TS 27.001 [10]. If the negotiation does not succeed, then the call shall be released. See also item 4) in the description of TS61.
+- 5) This teleservice may use the multislot mechanism of GERAN.
+
+### A.1.6 Voice Group Call Service
+
+| Teleservice 91, Voice Group Call Service |     |                                |                                       |                                 |                     |
+|------------------------------------------|-----|--------------------------------|---------------------------------------|---------------------------------|---------------------|
+| A                                        | 1.  | 1.1 Type or user Information   | speech                                |                                 |                     |
+| T                                        | HLC | 1.2 Layer 4 protocol functions | -                                     |                                 |                     |
+| T                                        |     | 1.3 Layer 5 protocol functions | -                                     |                                 |                     |
+| R                                        |     | 1.4 Layer 6 protocol functions | -                                     |                                 |                     |
+| I                                        |     | 1.5 Layer 7 protocol functions | -                                     |                                 |                     |
+| B                                        | 2.  | 2.1                            | 2.1.1 Information transfer capability | speech (digital representation) |                     |
+| U                                        | LLC | Inform                         | 2.1.2 Information transfer mode       | circuit                         |                     |
+| T                                        |     | transfer                       | 2.1.3 Information transfer rate       | not applicable                  |                     |
+| E                                        |     |                                | 2.1.4 Structure                       | not applicable                  |                     |
+| S                                        |     |                                | 2.1.5 Establishment of connection     | demand MO MT                    |                     |
+|                                          |     |                                | 2.1.6 Communication configuration     | multipoint                      |                     |
+|                                          |     |                                | 2.1.7 Symmetry                        | bidirectional symmetry          |                     |
+|                                          |     | 2.2                            | 2.2.1 Signalling access               | manual                          |                     |
+|                                          |     | Access                         | 2.2.2 Information access              | rate                            | full rate/half rate |
+|                                          |     | at UE                          | (3GPP TS 22.001)                      | interface                       |                     |
+|                                          |     | 2.3                            | 2.3.1 Visible network type            | PSTN/ISDN/ PLMN                 |                     |
+|                                          |     | Inter-                         | 2.3.2 National/Internat. interworking | international/national          |                     |
+|                                          |     | working                        | 2.3.3 Interface of TE to terminating  | 2 wire, analogue                | 4 wire<br>S (B+B+D) |
+|                                          | 3.  | 3.1                            | Supplementary service provided        | 3GPP TS 42.068                  |                     |
+|                                          | Gen | 3.2                            | Quality of service                    |                                 |                     |
+
+#### Comments:
+
+This service provides for speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple mobile service subscribers involved in the VGCS call per cell. A detailed service description is given in 3GPP TS 42.068 [5].
+
+This teleservice shall only be provided via a GERAN A/Gb mode of operation.
+
+### A.1.7 Voice Broadcast Service
+
+| Teleservice 92, Voice Broadcast Service |     |                                    |                                       |                                 |
+|-----------------------------------------|-----|------------------------------------|---------------------------------------|---------------------------------|
+| A                                       | 1.  | 1.1 Type or user Information       | speech                                |                                 |
+| T                                       | HLC | 1.2 Layer 4 protocol functions     | -                                     |                                 |
+| T                                       |     | 1.3 Layer 5 protocol functions     | -                                     |                                 |
+| R                                       |     | 1.4 Layer 6 protocol functions     | -                                     |                                 |
+| I                                       |     | 1.5 Layer 7 protocol functions     | -                                     |                                 |
+| B                                       | 2.  | 2.1                                | 2.1.1 Information transfer capability | speech (digital representation) |
+| U                                       | LLC | Inform                             | 2.1.2 Information transfer mode       | circuit                         |
+| T                                       |     | transfer                           | 2.1.3 Information transfer rate       | not applicable                  |
+| E                                       |     |                                    | 2.1.4 Structure                       | not applicable                  |
+| S                                       |     |                                    | 2.1.5 Establishment of connection     | demand MO MT                    |
+|                                         |     |                                    | 2.1.6 Communication configuration     | broadcast                       |
+|                                         |     |                                    | 2.1.7 Symmetry                        | unidirectional                  |
+|                                         |     | 2.2                                | 2.2.1 Signalling access               | manual                          |
+|                                         |     | Access                             | 2.2.2 Information access              | full rate/half rate             |
+|                                         |     | at UE                              | (3GPP TS 22.001)                      |                                 |
+|                                         |     |                                    | rate                                  |                                 |
+|                                         |     |                                    | interface                             |                                 |
+|                                         |     | 2.3                                | 2.3.1 Visible network type            | PSTN/ISDN/ PLMN                 |
+|                                         |     | Inter-                             | 2.3.2 National/Internat. interworking | international/national          |
+|                                         |     | working                            | 2.3.3 Interface of TE to terminating  | 2 wire, analogue                |
+|                                         |     |                                    |                                       | 4 wire<br>S (B+B+D)             |
+|                                         |     |                                    |                                       | ME                              |
+|                                         | 3.  | 3.1 Supplementary service provided | 3GPP TS 42.069                        |                                 |
+|                                         | Gen | 3.2 Quality of service             |                                       |                                 |
+
+#### Comments:
+
+This service provides for the distribution of speech, generated by a service subscriber, to all or a predefined group service subscribers located in this area. A detailed service description is given in 3GPP TS 42.069 [6].
+
+This teleservice shall only be provided via a GERAN A/Gb mode of operation.
+
+# Annex B (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                  |        |        |         |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|----------------------------------------------------------------------------------|--------|--------|---------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                  | Old    | New    | WI      |
+| Dec 1999       |           |           | 02.03  |     |     |       |     | Transferred to 3GPP SA1                                                          | 8.0.0  | 3.0.0  |         |
+| SA#06          |           |           | 02.03  |     |     |       |     |                                                                                  | 3.0.0  |        |         |
+| SP-06          | SP-99519  | S1-991025 | 22.003 | 001 |     | R99   | D   | Mainly an editorial update for GSM/3GPP use                                      | 3.0.0  | 3.1.0  |         |
+| SP-07          | SP-000069 | S1-000140 | 22.003 | 002 |     | R99   | D   | Editorial modification for change of SMS-CB to CBS and to correct the references | 3.1.0  | 3.2.0  |         |
+| SP-07          | SP-000071 | S1-000162 | 22.003 | 003 |     | R00   | B   | Addition of Wideband AMR                                                         | 3.1.0  | 4.0.0  |         |
+| SP-10          | SP-000687 | S1-000866 | 22.003 | 004 | 1   | Rel-4 | C   | Removal of TS61 and TS62 in NT mode from GSM in Rel-4 and later releases         | 4.0.0  | 4.1.0  | FAX     |
+| SP-12          | SP-010243 | S1-010563 | 22.003 | 007 |     | Rel-4 | A   | Removal of Voice Group Service                                                   | 4.1.0  | 4.2.0  | VGCS    |
+| SP-14          | SP-010672 | S1-011290 | 22.003 | 008 |     | Rel-5 | C   | Clarification of requirements for support of codecs                              | 4.2.0  | 5.0.0  | AMRWB   |
+| SP-15          | SP-020045 | S1-020457 | 22.003 | 010 | -   | Rel-5 | A   | Editorial CR to correct terms and references                                     | 5.0.0  | 5.1.0  | CORRECT |
+| SP-15          | SP-020164 |           | 22.003 | 011 | 1   | Rel-5 | C   | Support of Legacy Transceivers in GERAN                                          | 5.0.0  | 5.1.0  | AMR     |
+| SP-16          | SP-020245 | S1-020889 | 22.003 | 012 |     | Rel-5 | F   | CR to 22.003 Corrections on ASCI and Fax due to GERAN Iu mode                    | 5.1.0  | 5.2.0  | TEI     |
+| SP-26          | SP-040744 | S1-040997 | 22.003 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                                      | 5.2.0  | 6.0.0  |         |
+| SP-34          | -         | -         | 22.003 | -   | -   | Rel-7 | -   | Provision of Rel-7 version as a result of approval of 22.003-0013 for Rel-8      | 6.0.0  | 7.0.0  | -       |
+| SP-34          | SP-060776 | S1-061424 | 22.003 | 013 | -   | Rel-8 | C   | Addition of emergency related data to a TS12 call                                | 6.0.0  | 8.0.0  | EData   |
+| SP-46          | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-9 by MCC                                                          | 8.0.0  | 9.0.0  |         |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                                   | 9.0.0  | 10.0.0 |         |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                                   | 10.0.0 | 11.0.0 |         |

marked/Rel-11/22_series/22004/raw.md

@@ -0,0 +1,731 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                                         |           |
+|---------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                          | 4         |
+| 1 Scope.....                                                                                            | 5         |
+| 1.1 References .....                                                                                    | 5         |
+| 1.2 Abbreviations .....                                                                                 | 6         |
+| 2 General.....                                                                                          | 6         |
+| 2.1 Supplementary service .....                                                                         | 6         |
+| 2.2 Concepts associated with supplementary services .....                                               | 6         |
+| 3 Categories and framework of supplementary services .....                                              | 8         |
+| 3.1 Framework for the description of supplementary services .....                                       | 8         |
+| 3.2 Categories of supplementary services .....                                                          | 9         |
+| 4 Supported supplementary services.....                                                                 | 10        |
+| 4.1 Support of Line identity services .....                                                             | 13        |
+| 4.2 Support of Name identity services .....                                                             | 13        |
+| 5 Use of a password option in relation to supplementary services .....                                  | 14        |
+| 5.1 Definition .....                                                                                    | 14        |
+| 5.2 Description .....                                                                                   | 14        |
+| 5.3 Management - normal procedures and successful outcome.....                                          | 14        |
+| 5.3.1 Provision of password option .....                                                                | 14        |
+| 5.3.2 Withdrawal of the password option.....                                                            | 14        |
+| 5.3.3 Registration of password .....                                                                    | 14        |
+| 5.3.4 Erasure of password .....                                                                         | 14        |
+| 5.3.5 Password checking .....                                                                           | 14        |
+| 5.4 Management - exceptional procedures or unsuccessful outcome .....                                   | 15        |
+| 6 Not used .....                                                                                        | 15        |
+| 7 Processing of supplementary service operations .....                                                  | 15        |
+| 7.1 Processing of operations containing basic service information .....                                 | 15        |
+| 7.2 Processing of operations involving multiple Supplementary Services .....                            | 16        |
+| 7.3 Compatibility Information and Supplementary Services .....                                          | 17        |
+| 8 Format of description .....                                                                           | 17        |
+| <b>Annex A (normative): Applicability of Supplementary Services to Telecommunication Services .....</b> | <b>19</b> |
+| Annex B (informative): Change history .....                                                             | 22        |
+
+# --- Foreword
+
+This Technical Specification (TS) 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 purpose of the present document is to define a recommended set of supplementary services to the Teleservices and Bearer services which will be supported by a PLMN in connection with other networks as a basis for the definition of the network capabilities required.
+
+Supplementary services not covered in 3GPP TS 22.004 cannot be introduced unilaterally in any PLMN if they require modification of the signalling Specifications.
+
+Technical realization of supplementary services is described in 3GPP TS 23.011 [19] and 24.010 [21].
+
+## 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.001: " Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
+- [3] 3GPP TS 22.002: "Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
+- [4] 3GPP TS 22.003: " Teleservices supported by a Public Land Mobile Network (PLMN)".
+- [5] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [6] 3GPP TS 22.067: "Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 1".
+- [7] 3GPP TS 02.081: "Line identification supplementary services - Stage 1".
+- [8] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
+- [9] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1".
+- [10] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services - Stage 1".
+- [11] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1".
+- [12] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1".
+- [13] 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1".
+- [14] 3GPP TS 22.072: "Call Deflection (CD) - Stage 1".
+- [15] 3GPP TS 22.087: "User-to-user signalling (UUS) - Stage 1".
+- [16] 3GPP TS 22.091: "Explicit Call Transfer (ECT) supplementary services - Stage 1".
+- [17] 3GPP TS 22.093: "Call Completion to Busy Subscriber (CCBS) - Stage 1".
+- [18] 3GPP TS 22.096: "Calling Name Presentation (CNAP) - Stage 1".
+- [19] 3GPP TS 23.011: "Technical realization of supplementary services".
+- [20] 3GPP TS 22.135: "Multicall (MC) - Stage 1".
+
+- [21] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification General aspects".
+- [22] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding".
+- [23] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN and the means to describe them".
+- [24] 3GPP TS 22.101: "Service Principles".
+- [25] 3GPP TS 22.105: "Services and service capabilities".
+- [26] 3GPP TS 42.068: "Voice Group Call Service (VGCS) - Stage 1".
+- [27] 3GPP TS 42.069: "Voice Broadcast Service (VBS) - Stage 1".
+
+## 1.2 Abbreviations
+
+For the purposes of the present document the abbreviations and acronyms listed in 3GPP TR 21.905 [1] apply.
+
+# --- 2 General
+
+## 2.1 Supplementary service
+
+A supplementary service modifies or supplements a basic Telecommunication service.
+
+NOTE: Offered supplementary services may be used by subscribers/users at their discretion.
+
+## 2.2 Concepts associated with supplementary services
+
+For the purpose of the present document the following terms are defined:
+
+### **Provision**
+
+An action to make a service available to a subscriber. The provision may be:
+
+- general: where the service is made available to all subscribers (subject to compatibility restrictions enforced) without prior arrangements being made with the service provider;
+- pre-arranged: where the service is made available to an individual subscriber only after the necessary arrangements have been made with the service provider.
+
+### **Withdrawal**
+
+An action taken by the service provider to remove an available service from a subscriber's access. The withdrawal may be:
+
+- general: where the service is removed from all subscribers provided with the service;
+- specific: where the service is removed on an individual basis from subscribers provided with the service.
+
+### **Registration**
+
+The programming by the service provider or subscriber of information to enable subsequent operation of a service. The programming action involves input of specific supplementary information. For certain services the registration procedure may cause activation whilst for others the service may already be in the action phase.
+
+### **Erasure**
+
+The deletion by the service provider, the subscriber or the system of information stored against a particular service by a previous registration(s).
+
+### **Activation**
+
+An action taken by either the service provider, the subscriber or the system to enable a process to run as and when required by the service concerned, resulting in the active phase. Some services can be either "operative" or "quiescent" (not operative) during the active phase according to whether or not the system would be able to invoke or use the service.
+
+### **Deactivation**
+
+An action taken by either the service provider, the subscriber or the system to terminate the process started at the activation.
+
+### **Invocation**
+
+An action to invoke the service required, taken by the subscriber (e.g. pressing a specific button) or automatically by the network or terminal as a result of a particular condition (e.g. calling number identification for each incoming call).
+
+### **Normal operation with successful outcome**
+
+Description of the normal operation of the service, the normal served subscriber's actions and the system response. Decision points, timing and call progress signals would be some of the aspects defined for the service if they can be perceived by the subscriber.
+
+### **Interrogation**
+
+The request by the subscriber to the PLMN to provide information about a specific supplementary service. This information can be requested by a:
+
+- status check;
+
+The following values can be returned by the PLMN:
+
+- not supported;
+- active and operative;
+- active and quiescent;
+- not active.
+
+Not all values are applicable to all supplementary services.
+
+- data check;
+
+This interrogation function compares the data input by the subscriber during an interrogation procedure with the information stored in the PLMN. The PLMN signals an appropriate indication (e.g. "check is positive" or "check is negative").
+
+- data request;
+
+This interrogation function enables the subscriber to obtain confirmation of her input data. The PLMN signals an appropriate indication (e.g. "the forwarded-to number is etc."). The response to a data request may comprise the status of the service (e.g. not active).
+
+### **Exceptional operation or unsuccessful outcome**
+
+Abnormal situations not described in "normal operation with successful outcome". Procedures on time-out, unexpected signalling response and other such events would be defined.
+
+### **Interaction with other supplementary services**
+
+When more than one supplementary service is active, new logical situations, decisions, priorities, etc., may arise. This subclause would identify and define the resolution of such situations as they affect subscriber perception of the service. Special procedures may therefore be required, e.g. to allow, where possible, the simultaneous use of different supplementary services by one mobile subscriber.
+
+### **Interworking considerations**
+
+Identification of subscriber perceptions when a call exits from an ISDN/PLMN to another network or enters an ISDN/PLMN from another network (e.g. PSTN).
+
+### Unstructured SS Operations
+
+These operations are characterized by:
+
+- in the mobile to network direction the transparent transport of MMI strings entered by the user to the network;
+- in the network to mobile direction the transparent transport of text strings that are displayed by the mobile for user information;
+- transparent transfer of data between an application in the MS and a corresponding application in the network.
+
+These operations provide capabilities that can either be used as part of operator specified services, or to facilitate the early introduction of specified services.
+
+NOTE: This Specification does not distinguish between subscriber, user and customer, since all three do not fully cover the textual needs. Generally the term "subscriber" is used, even if this person is not having the subscription.
+
+# 3 Categories and framework of supplementary services
+
+## 3.1 Framework for the description of supplementary services
+
+3GPP TS 22.001 [2] and 3GPP TS 22.101 [24] describe the principles of the Telecommunication services. They also defines the concepts of Telecommunication services and describes their characterization by appropriate attributes. Bearer services and Teleservices, which are offered by a PLMN in connection with other networks, are defined in 3GPP TS 22.002 [3], 3GPP TS 22.105 [25] and 3GPP TS 22.003 [4]. Besides these basic Telecommunication services, their enhancement or modification by supplementary services need also to be offered.
+
+A supplementary service modifies or enhances a basic Telecommunication service and, hence, cannot be offered to a subscriber on a stand alone basis. It must be offered together with or in association with a basic Telecommunication service. The same supplementary service may be offered with a number of different Telecommunication services. For applicability of a Supplementary Service to a Telecommunication service refer to annex A.
+
+Table 3.1/3GPP TS 22.004 (identical to table 1/3GPP TS 22.001 [2] and to table 1 of ITU-T Recommendation I.210 [23]) illustrates the description of Telecommunication services.
+
+**Table 3.1/3GPP TS 22.004: Categorisation of Telecommunication services**
+
+| TELECOMMUNICATION SERVICE |                                               |                   |                                           |
+|---------------------------|-----------------------------------------------|-------------------|-------------------------------------------|
+| BEARER SERVICE            |                                               | TELESERVICE       |                                           |
+| Basic Bearer Service      | Basic Bearer service + supplementary services | Basic Teleservice | Basic Teleservice + supplementary service |
+
+Provision and withdrawal of a supplementary service, with the exception of Closed User Group, shall apply to all basic services the subscriber subscribes to.
+
+Registration, erasure, activation and deactivation of a supplementary service shall apply to one or more group of basic services. The groups of basic services are defined to avoid handling of many basic service codes.
+
+An operation is effective on the basic services, within the basic service group, which have been provisioned and for which the supplementary service is applicable. The fact that a basic service is provisioned but is not supplied by the network shall not lead to reject the request. The request shall be accepted since there is one basic service within the group(s) which is provisioned and for which the supplementary service is applicable. For applicability of a Supplementary Service to a basic service or service group refer to annex A.
+
+The basic service groups are define in table 3.2/3GPP TS 22.004.
+
+**Table 3.2/3GPP TS 22.004: List of basic service groups**
+
+| <b>Basic service group</b> |                                     | <b>Basic service (1) (2)</b> |                                                                       |
+|----------------------------|-------------------------------------|------------------------------|-----------------------------------------------------------------------|
+| <b>number</b>              | <b>name</b>                         | <b>Number (2)</b>            | <b>name</b>                                                           |
+| 1                          | Speech                              | TS 11<br>TS 12               | Telephony<br>Emergency call                                           |
+| 2                          | Short message service               | TS 21<br>TS 22<br>TS 23      | Short message MT/PP<br>Short message MO/PP<br>Short message CB        |
+| 3 - 5                      | Not allocated                       |                              |                                                                       |
+| 6                          | Facsimile services <sup>(3)</sup>   | TS 61<br>TS 62               | Alternate speech and facsimile group 3<br>Automatic facsimile group 3 |
+| 7                          | All Data circuit asynchronous       | BS 20                        | General asynchronous bearer service                                   |
+| 8                          | All Data circuit synchronous        | BS 30                        | General synchronous bearer service                                    |
+| 12                         | Voice group services <sup>(4)</sup> | TS 91<br>TS 92               | Voice Group Call Service<br>Voice Broadcast Service                   |
+
+NOTE 1: Basic services are defined in 3GPP TS 22.002 [3] and 3GPP TS 22.003 [4].  
+NOTE 2: TS: Teleservice BS: Bearer service.  
+NOTE 3: The transparent facsimile services apply to A/Gb mode of GERAN only. The non-transparent facsimile services apply to UTRAN only.  
+NOTE 4: The Voice Group Services, TS 91 and TS 92 apply to A/Gb mode of GERAN only.
+
+## 3.2 Categories of supplementary services
+
+Below follows a list of the possible categories of supplementary services related to provision, withdrawal, registration, erasure, activation, deactivation, invocation and interrogation.
+
+Provision of a supplementary service can be made on a subscription basis, i.e. after pre-arrangement with the service provider, or the supplementary service can be made generally available to all mobile subscribers having access to PLMNs.
+
+Withdrawal of a supplementary service can be as a result of a subscriber's request or for administrative reasons. Both withdrawal actions are performed by the service provider.
+
+Registration of a supplementary service is only applicable to those supplementary services in which specific data is required to enable subsequent operation of the service. This registration can be the result of provision or it can be a subscriber controlled procedure. Registration of a supplementary service may mean simultaneous activation of that service.
+
+Erasure of a supplementary service is only applicable to those supplementary services for which registration is necessary. It can be the result of withdrawal, it can be the result of a new registration overruling, and thus effectively erasing the previous registration, or it can be a subscriber controlled procedure. Erasure of a Supplementary Service may mean simultaneous deactivation of that service.
+
+Activation of a supplementary service can be the result of provision. In some cases the supplementary service is only activated if the conditions in the subscription options are met. A supplementary service can also be activated by means of a procedure controlled either by the mobile subscriber or the service provider. Some supplementary services may also be activated as a result of registration.
+
+Deactivation of a supplementary service can be the result of withdrawal or erasure of the service. In some cases the supplementary service is deactivated if the conditions in the subscription options are not met. A supplementary service can also be deactivated by means of a procedure controlled either by the mobile subscriber or the service provider. A supplementary service can be automatically deactivated at the end of a call if the supplementary service was specifically activated for that call. Finally, a supplementary service may be automatically deactivated by the network as a consequence of activation of another supplementary service if it conflicts with the other activated supplementary service.
+
+Invocation of a supplementary service can take place by means of a subscriber controlled procedure or automatically by the network as a result of a particular condition.
+
+Interrogation of a supplementary service is only applicable for a few supplementary services for which it is useful to get information from the network about the status or relevant data concerning the supplementary service.
+
+# --- 4 Supported supplementary services
+
+Table 4.1/3GPP TS 22.004 gives a list of possible supplementary services implemented in the PLMN, the definitions of which are given in the specifications [6]-[18].
+
+**NOTE:** All supplementary services in this table are implemented in the PLMN. Subscribers can use these supplementary services for calls within the PLMN, but also in interworking situations with the PSTN (if supported) and the ISDN. In interworking situations with CSPDN and PSPDN these supplementary services can only be used during call set up (e.g. call forwarding services). When a call is established between an MS and a PDN, the MS acts as a data network terminal and can consequently only use the supplementary services that are supported by the relevant PDN. The PDN supplementary services are not described in this Specification; they can be found in the relevant PDN Specifications. However, the interworking situations with PDNs still require further study.
+
+It has been identified as a requirement that the man-machine interface in PLMNs regarding supplementary services should be compatible as much as possible with the man-machine interface in the fixed networks as defined in CEPT groups, e.g. the same use of keypad information or function keys.
+
+Table 4.1/ 3GPP TS 22.004 lists the categories for all supported supplementary services. Below the abbreviations used are listed.
+
+### **Registration:**
+
+p = as a result of provision
+
+a = service provider controlled procedure
+
+s = subscriber controlled procedure
+
+- = not applicable
+
+### **Erasure:**
+
+w = as a result of withdrawal
+
+s = subscriber controlled procedure
+
+r = due to new registration
+
+- = not applicable
+
+### **Activation:**
+
+p = as a result of provision
+
+r = as a result of registration
+
+s = subscriber controlled procedure
+
+a = service provider controlled procedure
+
+c = when the conditions in the subscription options are met
+
+- = not applicable
+
+### **Deactivation:**
+
+w = as a result of withdrawal
+
+s = subscriber controlled procedure
+
+a = service provider controlled procedure
+
+e = as a result of erasure
+
+n = when the conditions in the subscr. options are not met
+
+c = at the end of a per call basis activation
+
+- = not applicable
+
+### **Invocation:**
+
+n = automatic invocation by the network as a result of a particular condition
+
+u = user invocation, by means of a control procedure
+
+- = not applicable
+
+### **Interrogation:**
+
+s = status check
+
+dr = data request
+
+- = not applicable
+
+**Table 4.1/ 3GPP TS 22.004: Supported Supplementary Services**
+
+| Supplementary Service                           |               |     |       |     |       |     |      |
+|-------------------------------------------------|---------------|-----|-------|-----|-------|-----|------|
+| Spec/section                                    |               | Reg | Eras  | Act | Deact | Inv | Int  |
+| 22.067                                          | eMLPP         | a/s | w/r   | -   | -     | n   | dr   |
+| 22.072, Call Deflection SS                      |               |     |       |     |       |     |      |
+|                                                 | CD            | -   | -     | p   | w     | u   | -    |
+| 22.081. Number Identif. SS                      |               |     |       |     |       |     |      |
+|                                                 | CLIP          | -   | -     | p   | w     | n   | s    |
+|                                                 | CLIR          | -   | -     | p   | w     | n   | dr   |
+|                                                 | CoLP          | -   | -     | p   | w     | n   | s    |
+|                                                 | CoLR          | -   | -     | p   | w     | n   | s    |
+| 22.082. Call Offering SS                        |               |     |       |     |       |     |      |
+|                                                 | CFU           | a/s | w/r/s | r/s | e/s   | n   | dr   |
+|                                                 | CFB           | a/s | w/r/s | r/s | e/s   | n   | dr   |
+|                                                 | CFNRy         | a/s | w/r/s | r/s | e/s   | n   | dr   |
+|                                                 | CFNRc         | a/s | w/r/s | r/s | e/s   | n   | dr   |
+| 22.083. Call Completion SS                      |               |     |       |     |       |     |      |
+|                                                 | CW            | -   | -     | a/s | a/s   | n   | s    |
+|                                                 | HOLD          | -   | -     | p   | w     | u   | -    |
+| 22.084. Multi Party SS                          |               |     |       |     |       |     |      |
+|                                                 | MPTY          | -   | -     | -   | -     | u   | -    |
+| 22.085. Comm. of Interest SS                    |               |     |       |     |       |     |      |
+|                                                 | CUG           | -   | -     | p   | w     | u/n | -    |
+| 22.087. User-to-User SS                         |               |     |       |     |       |     |      |
+|                                                 | UUS           | -   | -     | s   | c     | u/n | -    |
+| 22.086. Charging SS                             |               |     |       |     |       |     |      |
+|                                                 | AoCI          | -   | -     | p   | w     | n   | -    |
+|                                                 | AoCC          | -   | -     | p   | w     | n   | -    |
+| 22.088. Call Restriction SS                     |               |     |       |     |       |     |      |
+|                                                 | BAOC          | a/s | w/r   | a/s | s/a   | n   | dr   |
+|                                                 | BOIC          | a/s | w/r   | a/s | s/a   | n   | dr   |
+|                                                 | BOIC-exHC     | a/s | w/r   | a/s | s/a   | n   | dr   |
+|                                                 | BAIC          | a/s | w/r   | a/s | s/a   | n   | dr   |
+|                                                 | BAIC-Roam     | a/s | w/r   | a/s | s/a   | n   | dr   |
+|                                                 | ACR           | -   | -     | a/s | s/a   | n   | s    |
+| 22.067                                          | eMLPP         | a/s | w/r/s | -   | -     | u/n | s/dr |
+| 22.091. Call Transfer SS                        |               |     |       |     |       |     |      |
+|                                                 | ECT           | -   | -     | p   | w     | u   | -    |
+| 22.093. Completion of Calls to Busy Subscribers |               |     |       |     |       |     |      |
+|                                                 | CCBS SS       | -   | -     | p   | w     | n   |      |
+|                                                 | CCBS Requests |     |       | s   | s/a/w |     | dr   |
+| 22.096 Name Identification SS                   |               |     |       |     |       |     |      |
+|                                                 | CNAP          | -   | -     | p   | w     | n   | s    |
+| 22.135 Multicall                                |               |     |       |     |       |     |      |
+|                                                 | MC            | a/s | w     | p   | w     | U/n | dr   |
+
+Abbreviations used for the Supplementary Services:
+
+|           |                                                                                        |
+|-----------|----------------------------------------------------------------------------------------|
+| CD        | Call Deflection                                                                        |
+| CLIP      | Calling Line Identification Presentation                                               |
+| CLIR      | Calling Line Identification Restriction                                                |
+| CoLP      | Connected Line Identification Presentation                                             |
+| CoLR      | Connected Line Identification Restriction                                              |
+| CFU       | Call Forwarding Unconditional                                                          |
+| CFB       | Call Forwarding on Mobile Subscriber Busy                                              |
+| CFNRy     | Call Forwarding on No Reply                                                            |
+| CFNRc     | Call Forwarding on Mobile Subscriber Not Reachable                                     |
+| CNAP      | Calling Name Presentation - (CNAP)                                                     |
+| CW        | Call Waiting                                                                           |
+| HOLD      | Call Hold                                                                              |
+| MPTY      | Multi Party Service                                                                    |
+| MC        | Multicall                                                                              |
+| CUG       | Closed User Group                                                                      |
+| AoCI      | Advice of Charge (Information)                                                         |
+| AoCC      | Advice of Charge (Charging)                                                            |
+| UUS       | User-to-user signalling                                                                |
+| BAOC      | Barring of All Outgoing Calls                                                          |
+| BOIC      | Barring of Outgoing International Calls                                                |
+| BOIC-exHC | Barring of Outgoing International Calls except those directed to the Home PLMN Country |
+| BAIC      | Barring of All Incoming Calls                                                          |
+| BIC-Roam  | Barring of Incoming Calls when Roaming Outside the Home PLMN Country                   |
+| ECT       | Explicit Call Transfer                                                                 |
+| eMLPP     | enhanced Multi-Level Precedence and Pre-emption                                        |
+| SPNP      | Support of Private Numbering Plan - (SPNP)                                             |
+| CCBS      | Completion of calls to busy subscribers.- (CCBS)                                       |
+
+## 4.1 Support of Line identity services
+
+A PLMN which supports the CLIP service shall also support the CLIR service. A PLMN which supports CoLP service shall also support the CoLR service.
+
+A PLMN which does not support the CLIR service shall ensure that the line identity of a subscriber shall not be displayed to the called party unless the called party has CLIR override capability. A PLMN which does not support the CoLR service shall ensure that the line identity of a subscriber shall not be displayed to the calling party unless the calling party has CoLR override capability.
+
+## 4.2 Support of Name identity services
+
+(CNAP): A PLMN which supports the CNAP service shall also support the CLIR service.
+
+A PLMN which does not support the CLIR service shall ensure that the name identity of a subscriber shall not be displayed to the called party.
+
+# --- 5 Use of a password option in relation to supplementary services
+
+## 5.1 Definition
+
+Some Supplementary Services (e.g. Call Barring) can be offered to a subscriber with the subscription option of using a password to control the service. When this option is selected every action (related to that Supplementary Service), such as registration, erasure, activation or deactivation is performed by the mobile subscriber with the concurrent entry of the password.
+
+## 5.2 Description
+
+When the subscription option "Control of a Supplementary Service by the subscriber using a password" is provided, password handling is supported by the network.
+
+The password will consist of four digits in the range 0000 to 9999.
+
+## 5.3 Management - normal procedures and successful outcome
+
+### 5.3.1 Provision of password option
+
+Each Supplementary Service for which the control by the subscriber usage of a password is relevant may be offered with the subscription option "Control of the Supplementary Service". The values of this option will be:
+
+- by the subscriber using a password;
+- by the service provider.
+
+NOTE: A service provider needs not to offer this option to its subscribers. However, the support of the password facility is mandatory in the networks for visiting subscribers.
+
+### 5.3.2 Withdrawal of the password option
+
+The password option may be withdrawn for administrative reasons or due to subscription modification.
+
+### 5.3.3 Registration of password
+
+If a mobile subscriber selects at provision time the option of using a password for any given Supplementary Service, the password have to be registered at the same time.
+
+Furthermore, the subscriber can change the password by an appropriate control procedure at any time. The control procedure is described in 3GPP TS 22.030 [5].
+
+### 5.3.4 Erasure of password
+
+A password can be erased in two ways:
+
+- 1) Registration of a new password erases the previous one; or
+- 2) Withdrawal of the password option.
+
+### 5.3.5 Password checking
+
+If the mobile subscriber in an attempt to control a Supplementary Service requiring a password enters a correct password, the corresponding request is then considered by the network.
+
+## 5.4 Management - exceptional procedures or unsuccessful outcome
+
+If the mobile subscriber in an attempt to control a Supplementary Service requiring a password, or in an attempt to register a new password, enters an incorrect password, the corresponding request will be rejected by the network and the subscriber will be notified.
+
+If the mobile subscriber enters incorrect password more than three consecutive times, all control procedures related to the use of the password are made impossible until the service provider instructs the network to again accept password-related requests from this subscriber.
+
+# --- 6 Not used
+
+# 7 Processing of supplementary service operations
+
+## 7.1 Processing of operations containing basic service information
+
+The network shall process a registration/erasure/activation/deactivation request indicating basic service information independent of the previous registration/activation status. As a result the network will process these requests for the indicated basic service information only, whereas other registration/activation status information remains unchanged.
+
+Basic service information received by the network within the above supplementary service operations is in the specifications [6]-[18]. According to this definition the network may receive a combined basic service indication, e.g. for all basic services. As a result the combined basic service indication may be dissolved (note 1). This has to be taken into account when an interrogation procedure is performed.
+
+In case the operation contains a combined basic service indication (e.g. for all bearer services) the interactions specified in the specifications [6]-[18] have to be checked subsequently for each member of the combined service indication. As a result a supplementary service request may be partly rejected due to the interaction requirements (note 2). This has to be taken into account in the acknowledgement to the supplementary service request from the Mobile Station (MS), i.e. the network shall send a notification to the MS that the SS operation request was only partially successful.
+
+NOTE 1: Explanatory example
+
+### **1. Operation:**
+
+Registration of CFU for "all basic services" to number 1.
+
+### **2. Operation:**
+
+Registration of CFU for "Speech" to number 2.
+
+#### **Result:**
+
+Registration status for
+
+"Speech": CFU active to number 2.
+
+All other basic service groups: CFU active to number 1.
+
+NOTE 2: Explanatory example
+
+### **1. Operation:**
+
+Registration of CFB for "Speech" to number 1.
+
+### **2. Operation:**
+
+Activation of BAOC for "Facsimile services".
+
+### **3. Operation:**
+
+Registration of CFU for "all basic services" to number 2.
+
+#### **Result:**
+
+Registration status for
+
+"Speech": CFU active to number 2, CFB "quiescent" to number 1.
+
+"Facsimile services": BAOC Active, CFU rejected.
+
+All other basic service groups: CFU active to number 2.
+
+## 7.2 Processing of operations involving multiple Supplementary Services
+
+Normally, SS operations relate to one single Supplementary Service at a time. The network reaction on such operations are described in the specifications [6]-[18] subclauses x.3 (Normal Procedures), x.4 (Exceptional Procedures) and x.6 (Interaction). Also subclause 7.1 contains information related to this area.
+
+In addition, some groups of Supplementary Services may be controlled collectively, such as Call Forwarding and Barring services. The information contained in such "global" operation (e.g. Forwarded-to-number, Password, Basic Service group(s)) then applies generally to all SS concerned by the operation.
+
+The reaction of the network when receiving such control requests is generally the same as when receiving a number of subsequent single operations to the corresponding Supplementary Services. However, in some cases the action to be taken by the network may be regarded as "exceptional", and therefore the following clarifies the only allowed operations on groups of Supplementary Services:
+
+- If the group "all Call Forwarding services" is subject for a Registration or an Activation request, CFU shall become Active and Operative whilst the conditional CFs (CFC) will become Active and quiescent for the Basic Service groups concerned by the operation. I.e the network behaviour is the same as if the CFCs were Registered/Activated first, followed by Registration/Activation of CFU.
+
+The No Reply Timer may be a part of this general operation.
+
+If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of apply, i.e. the network ignores these parts of the request.
+
+- If the group "all Conditional Call Forwarding services" is subject for a Registration or an Activation request, all CFCs shall become Active and Operative for the Basic Service groups concerned by the operation.
+
+The No Reply Timer may be a part of this general operation.
+
+If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of apply, i.e. the network ignores these parts of the request.
+
+- If the group "all Call Forwarding services" or the group "all Conditional Call Forwarding services" is subject for a Deactivation or an Erasure request, the network shall act as normal, i.e. as if a number of subsequent Deactivations/Erasures were requested. If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of this specification apply, i.e. the network ignores these parts of the request.
+- If any of the groups "all Barring services", "all Outgoing Barring Services" or "all Incoming Barring Services" is subject to a Deactivation request, the network shall act as normal, i.e. as if a number of subsequent Deactivations were requested.
+
+If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of this specification apply, i.e. the network ignores these parts of the request.
+
+- If the user requests Password Registration for any other single or group of Barring Services than "all Barring Services" the request will be denied (as only **one** (common) password for the Barring services per subscriber is allowed).
+- Interrogation of groups of Supplementary Services is not supported.
+
+## 7.3 Compatibility Information and Supplementary Services
+
+Within the Single Numbering Scheme it is possible that an incoming call (e.g. PSTN call) do not have an allocated Bearer Capability Information Element. The network cannot at this stage determine the Basic Service requirement and shall, for Supplementary Service purposes, handle the call based on a "default basic service" for the call. If the subscriber has a subscription to telephony then the network shall use telephony as the "default basic service". If the subscriber does not have
+
+a subscription to telephony the HLR shall choose a Basic Service from the set provisioned to the subscriber as the "default basic service".
+
+When an incoming call is subject to Call Forwarding, no modifications or additions to the original BC-IE information, present or not, received by the PLMN shall be sent with the forwarded call.
+
+# --- 8 Format of description
+
+The supplementary services are described according to the following format:
+
+## 0. GENERAL
+
+## x.1 DEFINITION
+
+## x.2 DESCRIPTION
+
+### x.2.1 Description
+
+### x.2.2 Applicability to telecommunication services
+
+### x.2.3 Terminology
+
+## x.3 NORMAL PROCEDURES WITH SUCCESSFUL OUTCOME
+
+### x.3.1 Provision
+
+### x.3.2 Withdrawal
+
+### x.3.3 Registration
+
+### x.3.4 Erasure
+
+### x.3.5 Activation
+
+### x.3.6 Deactivation
+
+### x.3.7 Invocation
+
+### x.3.8 Normal operation with successful outcome
+
+### x.3.9 Quality of service
+
+### x.3.10 Testing
+
+### x.3.11 Interrogation
+
+### x.3.12 Charging requirements
+
+## x.4 EXCEPTIONAL PROCEDURES OR UNSUCCESSFUL OUTCOME
+
+x.4.1 Exceptional operation or unsuccessful outcome
+
+x.4.2 Registration
+
+x.4.3 Erasure
+
+x.4.4 Activation
+
+x.4.5 Deactivation
+
+x.4.6 Invocation
+
+x.4.7 Testing
+
+x.4.8 Interrogation
+
+x.4.9 Charging requirements
+
+x.4.10 Roaming in non-supporting networks
+
+x.5 ALTERNATE PROCEDURES
+
+x.6.y.z INTERACTIONS WITH OTHER SUPPLEMENTARY SERVICES
+
+x.7 INTERWORKING CONSIDERATIONS
+
+x.8 DYNAMIC DESCRIPTION OF SERVICE
+
+x.9 OUTSTANDING ISSUES
+
+The letter "x" denominates the supplementary service described in clause "x" of the specifications [6]-[18]. The letter "y" denominates the specification (e.g. 3GPP TS 22.0y or 42.0y) in which the supplementary service denominated by the letter "z" is described and which interacts with the supplementary service that is described in clause "x".
+
+Every supplementary service is described according to this format. If a subheading is not included in the text, it means:
+
+- not applicable (e.g. in cases where "registration", "erasure", "activation", etc., do not apply);
+- none identified (e.g. no exceptional procedure for "invocation");
+- no interaction (in cases where no interaction appears between two supplementary services in clause 6).
+
+# --- Annex A (normative): Applicability of Supplementary Services to Telecommunication Services
+
+Table A.1 gives the applicability of Supplementary Services to telecommunication services.
+
+## **Table A.1/3GPP TS 22.004: Applicability of SSs to telecommunication services**
+
+| SS                | Telephony | Emergency Call   | SMS PTP          |                  | SMS-CB | Fax   | cct Data   | GPRS  | Voice Group Services |                   |
+|-------------------|-----------|------------------|------------------|------------------|--------|-------|------------|-------|----------------------|-------------------|
+|                   |           |                  | TS21             | TS22             |        | TS 6x | BS2x, BS3x | BS 70 | TS 91                | TS 92             |
+| eMLPP             | Yes       | Yes <sup>9</sup> |                  |                  |        | Yes   | Yes        |       | Yes                  | Yes               |
+| CD                | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CLIP              | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CLIR              | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| COLP              | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| COLR              | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CFU               | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CFB               | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CFNRy             | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CFNRc             | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| CW <sup>1</sup>   | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| HOLD <sup>2</sup> | Yes       |                  |                  |                  |        |       |            |       |                      |                   |
+| MPTY              | Yes       |                  |                  |                  |        |       |            |       |                      |                   |
+| CUG               | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| AoCI              | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| AoCC              | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| UUS               | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| BAOC              | Yes       |                  | Yes <sup>3</sup> | Yes              |        | Yes   | Yes        |       | Yes <sup>11</sup>    | Yes <sup>11</sup> |
+| BOIC              | Yes       |                  | Yes <sup>3</sup> | Yes              |        | Yes   | Yes        |       |                      |                   |
+| BOIC-exHC         | Yes       |                  | Yes <sup>3</sup> | Yes              |        | Yes   | Yes        |       |                      |                   |
+| BIC               | Yes       |                  | Yes              | Yes <sup>3</sup> |        | Yes   | Yes        |       |                      |                   |
+| BIC-Roam          | Yes       |                  | Yes              | Yes <sup>3</sup> |        | Yes   | Yes        |       |                      |                   |
+| ACR               | Yes       |                  |                  |                  |        | Yes   | Yes        |       |                      |                   |
+| ECT               | Yes       |                  |                  |                  |        |       |            |       |                      |                   |
+| CCBS              | Yes       |                  |                  |                  |        | Yes   | Yes        |       | <sup>10</sup>        | <sup>10</sup>     |
+| SPNP              | Yes       |                  | Yes <sup>5</sup> | Yes <sup>5</sup> |        | Yes   | Yes        |       |                      |                   |
+| CNAP              | Yes       |                  | <sup>8</sup>     | <sup>8</sup>     |        |       |            |       | Yes <sup>3</sup>     | Yes <sup>3</sup>  |
+| MSP               | Yes       |                  | Yes              | Yes              |        | Yes   | Yes        |       |                      |                   |
+| MC                | Yes       | Yes              |                  |                  |        | Yes   | Yes        |       |                      |                   |
+
+- NOTE 1: The applicability of Call Waiting refers to the telecommunication service of the active call and not of the waiting call. The incoming, waiting, call may be of any kind.
+- NOTE 2: If the served mobile subscriber has a call on hold, she may set up another call using the same or a different telecommunication service.
+- NOTE 3: The SS is applicable, but generally will not be invoked.
+- NOTE 4: For the purposes of applicability of supplementary services, the Alternate speech/unrestricted data (BS61) and speech followed by data (BS81) belong to the BS-group of the equivalent data service.
+- NOTE 5: Both the SMS service centre and the mobile destination can be reached by PNP numbers.
+- NOTE 6: Void
+- NOTE 7: Void.
+- NOTE 8: Applicability of SMS PTP to CNAP is for further study.
+- NOTE 9: The network shall apply a specific or the default priority level to emergency calls. There is no possibility to change this priority by the subscriber. Pre-emption of an on-going emergency call is not possible.
+- NOTE 10: The CCBS supplementary service is only applicable for dispatchers. If a new terminating p-t-p call is set up to a dispatcher who is busy because of an active VGCS/VBS call, it should be possible to allow the calling subscriber to apply the CCBS service. If the dispatcher initiates a VGCS/VBS call and the called group/broadcast ID has been active, then the dispatcher should be connected to the ongoing VGCS/VBS call. For VGCS/VBS call to busy dispatcher, the CCBS is not applicable. For a detailed description see 3GPP TS 42.068 [26] and 3GPP TS 42.069 [27].
+- NOTE 11: BAOC is applicable with the exception of high priority voice group calls/voice broadcast calls.
+
+# Annex B (informative): Change history
+
+| Change history |           |           |        |      |     |        |     |                                                                                                 |        |        |           |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|-------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel    | Cat | Subject/Comment                                                                                 | Old    | New    | Work Item |
+| Jun 1999       |           |           | 02.04  |      |     |        |     | Transferred to 3GPP SA1                                                                         | 8.0.0  | 3.0.0  |           |
+| SA#04          |           |           | 22.004 |      |     |        |     |                                                                                                 | 3.0.0  |        |           |
+| SP-05          | SP-99479  | S1-99609  | 22.004 | 0001 |     | R99    | D   | Editorial changes for alignment                                                                 | 3.0.0  | 3.0.1  |           |
+| SP-06          | SP-99518  | S1-991042 | 22.004 | 0002 |     | R99    | F   | Clarification of the applicability of CCBS service to TS91/92                                   | 3.0.1  | 3.1.0  |           |
+| SP-07          | SP-000068 | S1-000154 | 22.004 | 0003 |     | R99    | F   | Introduction of Multicall as Supplementary Service                                              | 3.1.0  | 3.2.0  |           |
+| March 2000     |           |           | 22.004 |      |     |        |     | Editorial: correction to title to replace "release 2000" with "Release 1999"                    | 3.2.0  | 3.2.1  |           |
+| March 2001     | SP-010065 | S1-010258 | 22.004 |      |     | Rel-4  |     | Transferred to 3GPP Release 4                                                                   | 3.2.1  | 4.0.0  |           |
+| SP-15          | SP-020045 | S1-020457 | 22.004 | 0005 | -   | Rel-4  | F   | Editorial CR to correct terms and references                                                    | 4.0.0  | 4.1.0  | CORRECT   |
+| SP-16          | SP-020236 | S1-020985 | 22.004 | 0008 |     | Rel-4  | A   | Correction to Table 3.2 (rel-4)                                                                 | 4.1.0  | 4.2.0  | CORRECT   |
+| SP-16          | SP-020267 | S1-021043 | 22.004 |      |     | Rel-5  |     | Updated from Rel-4 to Rel5                                                                      | 4.2.0  | 5.0.0  |           |
+| SP-24          | SP-040283 | S1-040499 | 22.004 | 0011 | -   | Rel-5  | A   | Modification of table A1 required to remove wrong SS applicabilities to VG Services             | 5.0.0  | 5.1.0  | TEI 5     |
+| SP-26          | SP-040744 | S1-040997 | 22.004 |      |     | Rel-6  |     | Updated from Rel-5 to Rel-6                                                                     | 5.1.0  | 6.0.0  |           |
+| SP-34          | -         | -         | 22.004 | -    | -   | Rel-7  | -   | Provision of Rel-7 version as a result of approval of 22.004-0012 for Rel-8                     | 6.0.0  | 7.0.0  | -         |
+| SP-34          | SP-060771 | S1-061410 | 22.004 | 0012 | -   | Rel-8  | F   | Modification of table A1 required to correct the applicability of the BAOC to VGCS/VBS Services | 6.0.0  | 8.0.0  | TEI8      |
+| SP-46          | -         | -         | -      | -    | -   | -      | -   | Updated to Rel-9 by MCC                                                                         | 8.0.0  | 9.0.0  |           |
+| 2011-03        | -         | -         | -      | -    | -   | -      | -   | Update to Rel-10 version (MCC)                                                                  | 9.0.0  | 10.0.0 |           |
+| SP-52          | SP-110376 | S1-111123 | 22.004 | 0013 | -   | Rel-11 | B   | Addition of Anonymous Call Rejection to 22.004 as a SS                                          | 10.0.0 | 11.0.0 | ACR_CS    |

marked/Rel-11/22_series/22011/raw.md

@@ -0,0 +1,813 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                              |    |
+|----------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                               | 5  |
+| 1 Scope.....                                                                                 | 6  |
+| 1.1 References .....                                                                         | 6  |
+| 1.2 Definitions and abbreviations.....                                                       | 6  |
+| 2 Roaming .....                                                                              | 8  |
+| 2.1 General requirements .....                                                               | 8  |
+| 2.2 International roaming .....                                                              | 8  |
+| 2.3 National roaming.....                                                                    | 8  |
+| 2.4 Roaming in shared networks.....                                                          | 8  |
+| 3 Provisions for providing continuity of service.....                                        | 9  |
+| 3.1 Location registration .....                                                              | 9  |
+| 3.2 Network selection.....                                                                   | 9  |
+| 3.2.1 General .....                                                                          | 9  |
+| 3.2.2 Procedures .....                                                                       | 9  |
+| 3.2.2.1 General.....                                                                         | 9  |
+| 3.2.2.2 At switch-on or recovery from lack of coverage .....                                 | 10 |
+| 3.2.2.3 User reselection.....                                                                | 12 |
+| 3.2.2.4 Mobile Station reactions to indications of service restriction from the network..... | 13 |
+| 3.2.2.4.1 "Permanent" PLMN restriction .....                                                 | 13 |
+| 3.2.2.4.2 "Partial" and "temporary" PLMN restrictions.....                                   | 13 |
+| 3.2.2.4.3 PLMN restrictions for PS services.....                                             | 13 |
+| 3.2.2.5 Periodic network selection attempts .....                                            | 14 |
+| 3.2.2.6 Investigation PLMN Scan.....                                                         | 14 |
+| 3.2.2.7 Void .....                                                                           | 14 |
+| 3.2.2.8 Steering Of Roaming .....                                                            | 14 |
+| 3.2.3 Network selection for Multi-mode terminals with 3GPP Capability .....                  | 15 |
+| 4 Access control.....                                                                        | 16 |
+| 4.1 Purpose .....                                                                            | 16 |
+| 4.2 Allocation.....                                                                          | 16 |
+| 4.3 Operation.....                                                                           | 16 |
+| 4.3.1 Access Class Barring.....                                                              | 16 |
+| 4.3.2 Service Specific Access Control .....                                                  | 17 |
+| 4.3.3 Access Control for CSFB .....                                                          | 17 |
+| 4.3.4 Extended Access Barring .....                                                          | 18 |
+| 4.3.4.1 General.....                                                                         | 18 |
+| 4.3.4.2 Overriding extended access barring.....                                              | 19 |
+| 4.4 Emergency Calls .....                                                                    | 19 |
+| 4.4a Multimedia Priority Service .....                                                       | 19 |
+| 4.5 Control of UE Capabilities.....                                                          | 19 |
+| 5 Support of Localised Service Area (SoLSA).....                                             | 20 |
+| 5.1 Network selection.....                                                                   | 20 |
+| 5.2 The Idle-mode operation .....                                                            | 20 |
+| 5.2.1 Subscriber moving from a normal environment to his localised service area.....         | 20 |
+| 5.2.2 Subscriber moving away from his localised service area to a normal environment. ....   | 21 |
+| 5.2.3 Subscriber staying in his localised service area.....                                  | 21 |
+| 5.3 LSA only access .....                                                                    | 21 |
+| 5.4 Exclusive access.....                                                                    | 21 |
+| 5.5 Preferential access.....                                                                 | 21 |
+| 6 Support of 3GPP - WLAN Interworking .....                                                  | 21 |
+| 6.1 Void.....                                                                                | 22 |
+| 6.2 Void.....                                                                                | 22 |
+| 6.3 Void.....                                                                                | 22 |
+| 7 Administrative restriction of subscribers' access.....                                     | 22 |
+| 7.1 Allowed Location and Routing Area identities access.....                                 | 22 |
+
+7.2 Void.....22  
+8 Support of Home NodeB and Home E-NodeB.....22  
+Annex A (informative): Change history.....23
+
+# --- 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 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 purpose of this TS is to describe the service access procedures as presented to the user.
+
+Definitions and procedures are provided in this TS for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station (UE).
+
+## 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [3] 3GPP TS 23.122: "Non Access Stratum functions related to Mobile Station (MS) in idle mode".
+- [4] ITU-T Recommendation Q.1001: "General aspects of Public Land Mobile Networks".
+- [5] 3GPP TS 22.043: "Support of Localised Service Area (SoLSA). Stage 1".
+- [6] 3GPP TS 22.234: "Requirements on 3GPP system to wireless local area network (WLAN) interworking".
+- [7] 3GPP TS 22.101: "Service aspects; Service principles".
+- [8] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+- [9] 3GPP TS 36.304: "User Equipment (UE) procedures in idle mode"
+- [10] 3GPP TS25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
+- [11] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
+- [12] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
+- [13] 3GPP TS 36.331: "E-UTRA Radio Resource Control (RRC)".
+- [14] 3GPP TS 22.220: "Service requirements for Home NodeBs and Home eNodeBs".
+- [15] 3GPP2 C.S0004-A v6.0: "Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems – Addendum 2"
+- [16] 3GPP TS 22.153: "Multimedia priority service".
+
+## 1.2 Definitions and abbreviations
+
+In addition to those below, abbreviations used in this 3GPP TS are listed in 3GPP TR 21.905 [2].
+
+### **PLMN**
+
+A Public Land Mobile Network (PLMN) is a network established and operated by an Administration or RPOA for the specific purpose of providing land mobile communication services to the public. It provides communication possibilities for mobile users. For communications between mobile and fixed users, interworking with a fixed network is necessary.
+
+A PLMN may provide service in one, or a combination, of frequency bands.
+
+As a rule, a PLMN is limited by the borders of a country. Depending on national regulations there may be more than one PLMN per country.
+
+A relationship exists between each subscriber and his home PLMN (HPLMN). If communications are handled over another PLMN, this PLMN is referred to as the visited PLMN (VPLMN).
+
+### **PLMN Area**
+
+The PLMN area is the geographical area in which a PLMN provides communication services according to the specifications to mobile users. In the PLMN area, the mobile user can set up calls to a user of a terminating network. The terminating network may be a fixed network, the same PLMN, another PLMN or other types of PLMN.
+
+Terminating network users can also set up calls to the PLMN.
+
+The PLMN area is allocated to a PLMN. It is determined by the service and network provider in accordance with any provisions laid down under national law. In general the PLMN area is restricted to one country. It can also be determined differently, depending on the different telecommunication services, or type of UE.
+
+If there are several PLMNs in one country, their PLMN areas may overlap. In border areas, the PLMN areas of different countries may overlap. Administrations will have to take precautions to ensure that cross border coverage is minimized in adjacent countries unless otherwise agreed.
+
+Note 1: ITU-T Recommendation Q.1001 [4] does not contain a definition of the PLMN area.
+
+### **System Area**
+
+The System Area is defined as the group of PLMN areas accessible by UEs.
+
+Interworking of several PLMNs and interworking between PLMNs and fixed network(s) permit public land mobile communication services at international level.
+
+Note 2: The System Area according to [4] Recommendation Q.1001 corresponds to the System Area.
+
+### **Service Area**
+
+The Service Area is defined in the same way as the Service Area according to ITU-T Recommendation Q.1001 [4]. In contrast to the PLMN area it is not based on the coverage of a PLMN. Instead it is based on the area in which a fixed network user can call a mobile user without knowing his location. The Service Area can therefore change when the signalling system is being extended, for example.
+
+### **Regionally Provided Service**
+
+Regionally Provided Service is defined as a service entitlement to only certain geographical part(s) of a PLMN, as controlled by the network operator.
+
+### **Localised Service Area (LSA)**
+
+The localised service area concept shall give the operator a basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber. A LSA consists of a cell or a number of cells within a PLMN. (3GPP TS 22.043 [5]).
+
+### **Tracking Area:**
+
+E-UTRAN utilises Tracking Areas (TA) for UE access control, location registration, paging and mobility management. The TA is independent of Location Areas (LA) and Routing Areas (RA). A TA comprises one or more E-UTRA cells Service requirements for E-UTRAN are specified in 3GPP TS 22.278 [8].
+
+# --- 2 Roaming
+
+## 2.1 General requirements
+
+A UE with a valid IMSI may roam and access service in the area authorized by the entitlement of the subscription.
+
+If a communication has been established, the UE will in principle not suffer an interruption within the PLMN area (provided the entitlement of the subscription allows it). Exceptions are possible if no network resources or radio coverage are available locally.
+
+However, if the UE leaves the PLMN area, an established communication may terminate. If the user then wants to continue, another network providing service has to be selected and a new communication has to be established (see clause 3).
+
+Subject to roaming agreements, a visited network shall be able to prevent incoming roamers from using a particular radio access technology (e.g. when the home network has not implemented this radio access technology).
+
+## 2.2 International roaming
+
+International roaming is a service whereby an UE of a given PLMN is able to obtain service from a PLMN of another country.
+
+The availability of International Roaming is subject to inter-PLMN agreements.
+
+## 2.3 National roaming
+
+National Roaming is a service whereby an UE of a given PLMN is able to obtain service from another PLMN of the same country, anywhere, or on a regional basis.
+
+The availability of National Roaming depends on the home PLMN of the requesting UE and the visited PLMN; it does not depend on subscription arrangements.
+
+## 2.4 Roaming in shared networks
+
+The following requirements are applicable to GERAN, UTRAN and E-UTRAN sharing scenarios:
+
+- Mechanisms shall be specified to enable flexible allocation of visiting roamers among core network operators that have roaming agreements with the same roaming partners. The core network operators shall be able to pre-define their relative share of visiting roamers and distribute the visiting roamers that apply automatic network selection to different core networks connected to the radio access network accordingly.
+- When network sharing exists between different operators and a user roams into the shared network it shall be possible for that user to register with a core network operator (among the network sharing partners) that the user's home operator has a roaming agreement with, even if the operator is not operating a radio access network in that area.
+- The selection of a core network operator among those connected to the shared radio access network can either be manual (i.e. performed by the user after obtaining a list of available core network operators) or automatic (i.e. performed by the UE according to user and operator preferred settings). For further information see subclause 3.2.
+
+# --- 3 Provisions for providing continuity of service
+
+## 3.1 Location registration
+
+PLMNs shall provide a location registration function with the main purpose of providing continuity of service to UEs over the whole system area. The location registration function shall be such as to allow:
+
+- Fixed subscribers to call a UE by only using the directory number of the UE irrespective of where the UE is located in the system area at the time of the call.
+
+- UEs to access the system irrespective of the location of the UE.
+- UEs to identify when a change in location area has taken place in order to initiate automatic location updating procedures.
+
+## 3.2 Network selection
+
+### 3.2.1 General
+
+The UE shall support both manual and automatic network selection mechanisms (modes). The UE shall select the last mode used, as the default mode, at every switch-on.
+
+As an optional feature of the ME, the user shall be able to set a preference in the ME for the mode that shall be used at switch on. If set then the ME shall select this preference rather than the default mode.
+
+Note: By defaulting to the last mode used, e.g. manual network selection, the undesired automatic selection of an adjacent PLMN instead of the desired HPLMN in border areas, can be avoided at switch-on.
+
+The user shall be given the opportunity to change mode at any time.
+
+Except as defined below, the MMI shall be at the discretion of the UE manufacturer.
+
+The UE shall contain display functions by which Available PLMNs and the Selected PLMN can be indicated.
+
+In order not to confuse the user, the same definitions of PLMN names shall be applied consistently both in registered mode and in the list presented to the user when in manual mode.
+
+In shared networks a radio access network can be part of more than one PLMN. This shall be transparent to the user, i.e. the UE shall be able to indicate those PLMNs to the user, and the UE shall support network selection among those PLMNs, as in non-shared networks.
+
+### 3.2.2 Procedures
+
+#### 3.2.2.1 General
+
+In the following procedures the UE selects and attempts registration on PLMNs.
+
+In this TS, the term "PLMN Selection" defines an UE based procedure, whereby candidate PLMNs are chosen, one at a time, for attempted registration.
+
+A User Controlled PLMN Selector data field exists on the USIM to allow the user to indicate a preference for network selection. It shall be possible for the user to update the User Controlled PLMN Selector data field, but it shall not be possible to update this data field over the radio interface, e.g. using SIM Application Toolkit.
+
+It shall be possible to have an Operator Controlled PLMN Selector list and a User Controlled PLMN Selector list stored on the SIM/USIM card. Both PLMN Selector lists may contain a list of preferred PLMNs in priority order. It shall be possible to have an associated Access Technology identifier e.g., E-UTRAN, UTRAN, or GERAN associated with each entry in the PLMN Selector lists.
+
+The UE shall utilise all the information stored in the USIM related to network selection, e.g. HPLMN, Operator controlled PLMN Selector list, User Controlled PLMN Selector list, Forbidden PLMN list.
+
+Note 1: A PLMN in a Selector list, including HPLMN, may have multiple occurrences, with different access technology identifiers.
+
+The UE shall ignore those PLMN + access technology entries in the User Controlled PLMN selector and Operator Controlled PLMN selector lists where the associated Access Technology is not supported by the UE. In the case that there are multiple associated Access Technology identifiers in an entry the UE shall not ignore the entry if it includes any associated Access Technology that is supported by the UE.
+
+It shall be possible to handle cases where one network operator accepts access from access networks with different network IDs. It shall also be possible to indicate to the UE that a group of PLMNs are equivalent to the registered PLMN regarding PLMN selection, cell selection/re-selection and handover.
+
+It shall be possible for the home network operator to identify alternative Network IDs as the HPLMN. It shall be possible for the home network operator to store in the USIM an indication to the UE that a group of PLMNs are treated as the HPLMN regarding PLMN selection. Any PLMN to be declared as an equivalent to the HPLMN shall be present within the EHPLMN list and is called an EHPLMN. The EHPLMN list replaces the HPLMN derived from the IMSI. When the EHPLMN list is present, any PLMN in this list shall be treated as the HPLMN in all the network and cell selection procedures.
+
+If registration on a PLMN is successful, the UE shall indicate this PLMN (the "registered PLMN") and be capable of making and receiving calls on it. The identity of the registered PLMN shall be stored on the SIM/USIM. However, if registration is unsuccessful, the UE shall ensure that there is no registered PLMN stored in the SIM/USIM.
+
+If a registration is unsuccessful because the IMSI is unknown in the home network, or the UE is illegal, then the UE shall not allow any further registration attempts on any network, until the UE is next powered-up or a SIM/USIM is inserted.
+
+If the registration is unsuccessful due to the lack to service entitlement, specific behaviour by the UE may be required, see subclause 3.2.2.4.
+
+To avoid unnecessary registration attempts, lists of forbidden PLMNs, TAs and LAs are maintained in the UE, see subclause 3.2.2.4 and 3GPP TS 23.122 [3].
+
+Registration attempts shall not be made by UEs without a SIM/USIM inserted.
+
+An UE/ME which has not successfully registered shall nevertheless be able to make emergency call attempts on an available PLMN(which supports the emergency call teleservice), without the need for the user to select a PLMN. An available PLMN is determined by radio characteristics (3GPP TS 23.122 [3]).
+
+#### 3.2.2.2 At switch-on or recovery from lack of coverage
+
+At switch on, when in coverage of the last registered PLMN as stored in the SIM/USIM, the UE will attach to that network.
+
+As an option, in automatic selection mode, when no EHPLMN list is present, the UE may select the HPLMN. When the EHPLMN list is present, the UE may select the highest priority EHPLMN among the available EHPLMNs. The operator shall be able to control the UE behaviour by USIM configuration.
+
+As an option, if the UE is in manual network selection mode at switch-on
+
+- if the last registered PLMN is unavailable and no equivalent PLMN is available,
+- and the UE finds it is in coverage of either the HPLMN or an EHPLMN
+
+then the UE should register on the corresponding HPLMN or EHPLMN. The UE remains in manual mode.
+
+If the UE returns to coverage of the PLMN on which it is already registered (as indicated by the registered PLMN stored in the SIM/USIM), the UE shall perform a location update to a new location area if necessary. As an alternative option to this, if the UE is in automatic network selection mode and it finds coverage of the HPLMN or any EHPLMN, the UE may register on the HPLMN (if the EHPLMN list is not present) or the highest priority EHPLMN of the available EHPLMNs (if the EHPLMN list is present) and not return to the last registered PLMN. If the EHPLMN list is present and not empty, it shall be used. The operator shall be able to control by USIM configuration whether an UE that supports this option shall follow this alternative behaviour.
+
+The default behaviour for a UE is to select the last registered PLMN.
+
+If there is no registered PLMN stored in the SIM/USIM, or if this PLMN is unavailable and no equivalent PLMN is available, or the attempted registration fails, the UE shall follow one of the following procedures for network selection:
+
+##### A) Automatic network selection mode
+
+The UE shall select and attempt registration on other PLMNs, if available and allowable, if the location area is not in the list of "forbidden LAs for roaming" and the tracking area is not in the list of "forbidden TAs for roaming" (see 3GPP TS 23.122 [3]), in the following order:
+
+- i) An EHPLMN if the EHPLMN list is present or the HPLMN (derived from the IMSI) if the EHPLMN list is not present for preferred access technologies in the order specified. In the case that there are multiple EHPLMNs present then the highest priority EHPLMN shall be selected. It shall be possible to configure a
+
+voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
+
+- ii) each entry in the "User Controlled PLMN Selector with Access Technology" data field in the SIM/USIM (in priority order). It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
+- iii) each entry in the "Operator Controlled PLMN Selector with Access Technology" data field in the SIM/USIM (in priority order). It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
+- iv) other PLMN/access technology combinations with sufficient received signal quality (see 3GPP TS 23.122 [3]) in random order. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
+- v) all other PLMN/access technology combinations in order of decreasing signal quality. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service.
+
+In the case of a UE operating in UE operation mode A or B, an allowable PLMN is one which is not in the "Forbidden PLMN" data field in the SIM/USIM . This data field may be extended in the ME memory.(see subclause 3.2.2.4). In the case of a UE operating in UE operation mode C, an allowable PLMN is one which is not in the "Forbidden PLMN" data field in the SIM/USIM or in the list of "forbidden PLMNs for GPRS service" in the ME.
+
+If successful registration is achieved, the UE shall indicate the selected PLMN.
+
+If registration cannot be achieved on any PLMN, the UE shall indicate "no service" to the user, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure. When registration cannot be achieved, different (discontinuous) PLMN search schemes may be used in order to minimize the access time while maintaining battery life, e.g. by prioritising the search in favour of BCCH carriers which have a high probability of belonging to an available and allowable PLMN.
+
+##### **B) Manual network selection mode**
+
+The UE shall indicate PLMNs, including "Forbidden PLMNs", which are available. If there are none, this shall also be indicated. The HPLMN of the user may provide on the USIM additional information about the available PLMNs, if this is provided then the UE shall indicate that information to the user. This information, provided as free text may include:
+
+- Preferred partner,
+- roaming agreement status,
+- supported services
+
+Furthermore, the UE may indicate whether the available PLMNs are present on one of the PLMN selector lists (e.g. EHPLMN, User Controlled, Operator Controlled or Forbidden) as well as not being present on any of the lists.
+
+For the purpose of presenting the names of the available PLMNs to the user, the ME shall use the USIM defined names if available or other PLMN naming rules in priority order as defined in 3GPP TS 22.101 [7] (Country/PLMN indication).
+
+Any available PLMNs shall be presented in the following order:
+
+- i) HPLMN (if the EHPLMN list is not present); or if one or more of the EHPLMNs are available then based on an optional data field on the USIM either the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order; if the data field is not present, then only the highest priority available EHPLMN is presented;
+- ii) PLMNs contained in the "User Controlled PLMN Selector" data field in the SIM/USIM (in priority order);
+- iii) PLMNs contained in the "Operator Controlled PLMN Selector" data field in the SIM/USIM (in priority order);
+- iv) other PLMN/access technology combinations with sufficient received signal level (see 3GPP TS 23.122 [3]) in random order;
+
+- v) all other PLMN/access technology combinations in order of decreasing signal strength.
+
+If a PLMN does not support voice services then this shall be indicated to the user.
+
+The user may select the desired PLMN and the UE shall attempt registration on this PLMN. (This may take place at any time during the presentation of PLMNs.)
+
+If the registration cannot be achieved on the selected PLMN, the UE shall indicate "No Service". The user may then select and attempt to register on another or the same PLMN following the above procedure. The UE shall not attempt to register on a PLMN which has not been selected by the user.
+
+Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different PLMN unless:
+
+- i) The new PLMN is declared as an equivalent PLMN by the registered PLMN;
+
+or,
+
+- ii) The user selects automatic mode.
+
+If a PLMN is selected but the UE cannot register on it because registration is rejected with the cause "PLMN not allowed", the UE shall add the PLMN to the "Forbidden PLMN" list (subclause 3.2.2.4.1). The UE shall not re-attempt to register on that network unless the same PLMN is selected again by the user.
+
+If a PLMN is selected but the UE cannot register for PS services on it because registration is rejected with the cause "GPRS services not allowed in this PLMN", the UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network. The PLMN is added to the list "Forbidden PLMN's for GPRS services". The UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network unless the same PLMN is selected again by the user. The reception of the cause "GPRS services not allowed in this PLMN", does not affect the CS service.
+
+For requirements to restrict the access of a UE to one or several specific RATs see section 7.1.
+
+If a PLMN is selected but the UE cannot register on it for other reasons, the UE shall, upon detection of a new LA (not in a forbidden LA list) of the selected PLMN, attempt to register on the PLMN.
+
+If the UE is registered on a PLMN but loses coverage, different (discontinuous) carrier search schemes may be used to minimize the time to find a new valid BCCH carrier and maintain battery life, e.g. by prioritizing the search in favour of BCCH carriers of the registered PLMN.
+
+#### 3.2.2.3 User reselection
+
+At any time, the user may request the UE to initiate reselection and registration onto an alternative available PLMN, according to the following procedures, dependent upon the operating mode.
+
+##### A) Automatic Network Selection Mode
+
+The UE shall follow the procedure defined in clause 3.2.2.2.A) above.
+
+##### B) Manual Network Selection Mode
+
+The procedure of 3.2.2.2 B) is followed.
+
+#### 3.2.2.4 Mobile Station reactions to indications of service restriction from the network
+
+Different types of UE behaviour is required to support, for example, national roaming, regionally provided service and temporary international roaming restrictions. The behaviour to be followed by the UE is indicated by the network.
+
+##### 3.2.2.4.1 "Permanent" PLMN restriction
+
+When a registration attempt by the UE is rejected by a network with an indication of "permanent" PLMN restriction, the PLMN identity shall be written to a list of "Forbidden PLMNs" stored in a data field in the SIM/USIM.
+
+If a successful registration is achieved on a PLMN in the "Forbidden PLMN" list, the PLMN shall be deleted from the list.
+
+When in automatic mode, the UE may indicate any PLMNs which will not be selected due to their presence in the "Forbidden PLMN" list.
+
+If a UE receives an equivalent PLMN list containing a PLMN which is included in the "Forbidden PLMN" list, this PLMN shall be removed from the equivalent PLMN list before this is stored by the UE.
+
+##### 3.2.2.4.2 "Partial" and "temporary" PLMN restrictions
+
+When a registration attempt by the UE is rejected by a network due to a "partial" or a "temporary" PLMN restriction, the UE shall perform one of the following procedures determined by the indication in the location update reject cause sent by the network (see 3GPP TS 23.122 [3]):
+
+- i) The UE shall store the tracking area identity or location area identity in the list of "forbidden TAs or LAs for regional provision of service" respectively and shall enter the limited service state. The UE shall remain in that state until it moves to a cell in a location area where service is allowed.
+- ii) The UE shall store the tracking area identity or the location area identity in the list of "forbidden TAs or LAs for roaming" respectively and shall use one of the following procedures according to the PLMN selection Mode:
+
+A) Automatic network selection mode:
+
+The procedure of 3.2.2.2. A).
+
+B) Manual network selection mode:
+
+The procedure of 3.2.2.2.B).
+
+- iii) The UE shall store the tracking area identity or location area identity in the list of "forbidden TAs or LAs for roaming" respectively and shall search for a suitable cell in the same PLMN.
+
+Note: A suitable cell will belong to a different TA or LA which is not in the "forbidden TAs or LAs for roaming").
+
+##### 3.2.2.4.3 PLMN restrictions for PS services
+
+When a registration attempt for PS services by the UE is rejected by the network with the cause "GPRS services not allowed in this PLMN", the PLMN identity shall be written to a list of "forbidden PLMNs for GPRS service" in the ME. This list is deleted when the UE is switched off or when the SIM/USIM is removed; the maximum number of possible entries in this list is implementation dependent, but must be at least one entry (see 3GPP TS 23.122 [3]).
+
+If a successful registration is achieved on a PLMN in the "forbidden PLMNs for GPRS service" list, the PLMN shall be deleted from the list.
+
+#### 3.2.2.5 Periodic network selection attempts
+
+A UE in Automatic Mode shall make periodic attempts to look for a higher priority PLMN including associated Access Technology of the same country as the currently received PLMN including associated Access Technology. For the ranking of PLMNs the UE shall use the order used in subclause 3.2.2.2. In the case that there is no associated Access Technology identifier, the mobile shall assume that all Access Technologies provided by a PLMN are of equal priority. Moreover, periodic network selection shall not lead to change of access technology within the registered PLMN.
+
+In the case that the UE has stored a list of equivalent PLMNs, the UE shall only select a PLMN if it has a higher priority than all the PLMNs, in the list of equivalent PLMNs, which are of the same country as the currently registered PLMN.
+
+Note: In the context of this 3GPP TS, the term country is to be interpreted not as a political entity but as a single Mobile Country Code (MCC). For example the USA and India have multiple MCC. Such cases are in fact treated as exceptions in the 3GPP specifications. For all other countries, multiple MCCs may be used, however the specifications have not taken this into account and there could be adverse effects such as the UE being unable to detect that multiple MCCs are within the same country.
+
+In the case that there are multiple EHPLMNs available, the UE shall not attempt to select a higher priority EHPLMN when an EHPLMN has already been selected. The priorities of EHPLMNs are only applicable when the UE is on a VPLMN and multiple EHPLMNs are available.
+
+The UE shall only make reselection attempts while in idle mode for circuit services. In case of GPRS terminals, the UE shall only make reselection attempts while in Idle or Stand-by mode.
+
+The interval between attempts shall be stored in the SIM/USIM. Only the service provider shall be able to select for which of the previous situations, periodic network selection shall be attempted and to set the interval, which shall be between 6 minutes and 8 hours, with a step size of 6 minutes. One value shall be designated to indicate that no periodic attempts shall be made.
+
+In the absence of a permitted value in the SIM/USIM, or the SIM/USIM is phase 1 and therefore does not contain the datafield, then a default value of 60 minutes, shall be used by the UE.
+
+Note: Use of values less than 60 minutes may result in excessive ME battery drain.
+
+#### 3.2.2.6 Investigation PLMN Scan
+
+The operator shall be able to control by SIM/USIM configuration whether an UE that is capable shall perform an investigation scan. This investigation scan shall be performed after each successful PLMN selection as well as during limited service state. The investigation scan shall search for a higher prioritised PLMN that does not offer CS voice service. If such a PLMN is available, the user shall be informed. This enables the user to switch to such a PLMN using manual selection if the user so prefers. The investigation scan shall not be performed when no SIM/USIM is inserted.
+
+#### 3.2.2.7 Void
+
+#### 3.2.2.8 Steering Of Roaming
+
+##### Steering to a specific VPLMN
+
+It shall be possible for the HPLMN at any time to direct a UE, that is in automatic mode, to search for a specific VPLMN and, if it is available, move to that VPLMN as soon as possible. This VPLMN shall then be regarded as the highest priority VPLMN as defined by the operator, though any EHPLMN or PLMN on the User Controlled PLMN list shall have higher priority. This process shall be done transparently and without inconvenience to the user.
+
+If the UE is in manual mode, the steering request shall be ignored.
+
+If the UE is registered on a VPLMN that is present on the User Controlled PLMN List, the steering request shall be ignored. PLMNs contained on the User Controlled PLMN List shall have priority over the steered-to-PLMN.
+
+The UE shall attempt to register on the specified VPLMN even if the specified VPLMN is present on a Forbidden List.
+
+This mechanism shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 3GPP specifications.
+
+##### VPLMN Redirection
+
+It shall be possible for the HPLMN to request a UE, that is in automatic mode, to find and register on a different VPLMN from the one it is currently using or trying to register on, if another VPLMN, that is not in a Forbidden List, is available. The original VPLMN shall then be treated as the lowest priority VPLMN and would not be selected by the UE unless it is the only one available to the UE or has been selected in manual mode. This process shall be done transparently and without inconvenience to the user.
+
+If the UE is in manual mode, the redirection request shall be ignored.
+
+If the UE is registered on a VPLMN that is present on the User Controlled PLMN List, the redirection request shall be ignored.
+
+This mechanism shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 3GPP specifications.
+
+### 3.2.3 Network selection for Multi-mode terminals with 3GPP Capability
+
+Different type's of Multi-mode terminals combining different technologies and systems in one terminal can be produced. It is not possible to foresee all possible configurations and provide a detailed technical specification for network and system selection for all possible multi-mode terminal configurations. The following provides the generic requirements for network and system selection for Multi-mode terminals with 3GPP Capability. These requirements are mandatory for a 3GPP capable multi-mode terminal, unless otherwise is explicitly specified elsewhere in the 3GPP Technical Specifications.
+
+- a multi-mode terminal, when in 3GPP mode of operation shall be compliant to the 3GPP specifications, including PLMN selection, cell selection and re-selection, paging reception etc.,
+  - As consequence, the multi-mode terminal when entering 3GPP mode of operation shall act as if it were a 3GPP only UE which had just been switched-on. Similarly, when leaving the 3GPP mode of operation the multimode terminal shall act as if it were a 3GPP only UE which had just been switched-off
+
+When the multimode terminal is in 3GPP mode, the switching between modes in the multi-mode terminal is considered an overlay functionality selecting mode of operation. For the design of the overlay functionality the following requirements shall be fulfilled:
+
+- The overlay functionality shall include a mechanism to avoid ping-pong between systems, e.g., a timer or hysteresis function
+- The overlay functionality shall not include network priority mechanisms, which conflict with the network priority mechanisms specified in 3GPP specifications, e.g., the Periodic network selection attempts scanning within 3GPP based systems for PLMNs of higher priority than the current serving PLMN.
+- Any functionality in the overlay system, such as background scan of other systems, shall not impact the fulfilment of 3GPP protocol requirements (in particular in regards to paging, cell selection, cell re-selection and PLMN selection)
+- As specified in this technical specification, the 3GPP technical specification provides the capability for the user to set their own 3GPP PLMN selection preferences; as well as the user can manually select any 3GPP PLMN. This has been done to ensure a fair competition environment. These principles shall be maintained in the design of the overlay functionality.
+
+# --- 4 Access control
+
+## 4.1 Purpose
+
+Under certain circumstances, it will be desirable to prevent UE users from making access attempts (including emergency call attempts) or responding to pages in specified areas of a PLMN. Such situations may arise during states of emergency, or where 1 of 2 or more co-located PLMNs has failed.
+
+Broadcast messages should be available on a cell by cell basis indicating the class(es) or categories of subscribers barred from network access.
+
+The use of these facilities allows the network operator to prevent overload of the access channel under critical conditions.
+
+It is not intended that access control be used under normal operating conditions.
+
+It should be possible to differentiate access control between CS and PS domains. Details are specified in TS23.122[3] and TS25.304 [10]. Not all RATs need to support this functionality.
+
+## 4.2 Allocation
+
+All UEs are members of one out of ten randomly allocated mobile populations, defined as Access Classes 0 to 9. The population number is stored in the SIM/USIM. In addition, UEs may be members of one or more out of 5 special categories (Access Classes 11 to 15), also held in the SIM/USIM. These are allocated to specific high priority users as follows. (The enumeration is not meant as a priority sequence):
+
+- Class 15 - PLMN Staff;
+- "- 14 - Emergency Services;
+- "- 13 - Public Utilities (e.g. water/gas suppliers);
+- "- 12 - Security Services;
+- "- 11 - For PLMN Use.
+
+## 4.3 Operation
+
+### 4.3.1 Access Class Barring
+
+If the UE is a member of at least one Access Class which corresponds to the permitted classes as signalled over the air interface, and the Access Class is applicable in the serving network, access attempts are allowed. Additionally, in the case of the access network being UTRAN the serving network can indicate that UEs are allowed to respond to paging and perform location registration (see, sec 3.1), even if their access class is not permitted. Otherwise access attempts are not allowed. Also, the serving network can indicate that UEs are restricted to perform location registration, although common access is permitted. If the UE responded to paging it shall follow the normal defined procedures and react as specified to any network command.
+
+Note: The network operator can take the network load into account when allowing UEs access to the network.
+
+Access Classes are applicable as follows:
+
+- Classes 0 - 9 - Home and Visited PLMNs;
+- Classes 11 and 15 - Home PLMN only if the EHPLMN list is not present or any EHPLMN;
+- Classes 12, 13, 14 - Home PLMN and visited PLMNs of home country only. For this purpose the home country is defined as the country of the MCC part of the IMSI.
+
+Any number of these classes may be barred at any one time.
+
+The following is the requirements for enhanced Access control on E-UTRAN.
+
+- The serving network shall be able to broadcast mean durations of access control and barring rates (e.g. percentage value) that commonly applied to Access Classes 0-9 to the UE. The same principle as in UMTS is applied for Access Classes 11-15.
+- E-UTRAN shall be able to support access control based on the type of access attempt (i.e. mobile originating data or mobile originating signalling), in which indications to the UEs are broadcasted to guide the behaviour of UE. E-UTRAN shall be able to form combinations of access control based on the type of access attempt e.g. mobile originating and mobile terminating, mobile originating, or location registration. The 'mean duration of access control' and the barring rate are broadcasted for each type of access attempt (i.e. mobile originating data or mobile originating signalling).
+- The UE determines the barring status with the information provided from the serving network, and perform the access attempt accordingly. The UE draws a uniform random number between 0 and 1 when initiating connection establishment and compares with the current barring rate to determine whether it is barred or not. When the uniform random number is less than the current barring rate and the type of access attempt is indicated allowed, then the access attempt is allowed; otherwise, the access attempt is not allowed. If the access attempt is not allowed, further access attempts of the same type are then barred for a time period that is calculated based on the 'mean duration of access control' provided by the network and the random number drawn by the UE.
+
+### 4.3.2 Service Specific Access Control
+
+Additionally to the above requirements in 4.3.1;
+
+- In E-UTRAN it shall be possible to support a capability called Services Specific Access Control (SSAC) to apply independent access control for telephony services (MMTEL) for mobile originating session requests from idle-mode as following:
+  - EPS shall provide a capability to assign a service probability factor [13] and mean duration of access control for each of MMTEL voice and MMTEL video:
+    - assign a barring rate (percentage) commonly applicable for Access Classes 0-9
+    - assign a flag barring status (barred /unbarred) for each Access Class in the range 11-15.
+    - SSAC shall not apply to Access Class 10.
+    - SSAC can be provided by the VPLMN based on operator policy without accessing the HPLMN.
+
+- SSAC shall provide mechanisms to minimize service availability degradation (i.e. radio resource shortage) due to the mass simultaneous mobile originating session requests and maximize the availability of the wireless access resources for non-barred services.
+- The serving network shall be able to broadcast mean durations of access control, barring rates for Access Classes 0-9, barring status for Access class in the range 11-15 to the UE.
+- The UE determines the barring status with the information provided from the serving network, and perform the access attempt accordingly. The UE draws a uniform random number between 0 and 1 when initiating connection establishment and compares with the current barring rate to determine whether it is barred or not. When the uniform random number is less than the current barring rate and the type of access attempt is indicated allowed, then the access attempt is allowed; otherwise, the access attempt is not allowed. If the access attempt is not allowed, further access attempts of the same type are then barred for a time period that is calculated based on the 'mean duration of access control' provided by the network and the random number drawn by the UE.
+
+### 4.3.3 Access Control for CSFB
+
+Access control for CSFB provides a mechanism to prohibit UEs to access E-UTRAN to perform CSFB. It minimizes service availability degradation (i.e. radio resource shortage, congestion of fallback network) caused by mass simultaneous mobile originating requests for CSFB and increases the availability of the E-UTRAN resources for UEs accessing other services.
+
+When an operator determines that it is appropriate to apply access control for CSFB, the network may broadcast necessary information to provide access control for CSFB for each class to UEs in a specific area. The network shall be able to separately apply access control for CSFB, SSAC and enhanced Access control on E-UTRAN.
+
+The following requirements apply for CSFB to 1xRTT:
+
+- In E-UTRAN, the network may apply access control for mobile originating session requests on CSFB from 1xRTT/E-UTRAN UE. The parameters received by the UE are dealt with in accordance with CDMA2000 procedures in 3GPP2 C.S0004-A: "Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems – Addendum 2" [15].
+
+For CSFB to UTRAN or GERAN, the necessary information in the broadcast to provide access control for CSFB is the same as that specified in Clause 4.3.1. In addition to those requirements the following apply:
+
+- Access control for CSFB shall apply for Access Class 0-9 and Access Class 11-15. It shall not apply for Access Class 10.
+- Access control for CSFB shall be applied for idle mode UE.
+- Access control for CSFB shall apply to all CSFB services.
+- Access control for CSFB may be provided by the VPLMN based on operator policy without accessing the HPLMN.
+- If Access control for CSFB, according to the UE's access class, disallows originating session requests for CSFB then a UE shall not send mobile originating session requests for CSFB.
+- If Access control for CSFB is applied by the UE for a mobile originating session request for CSFB, the UE shall bypass enhanced Access control on E-UTRAN for that session.
+- The criteria on which a UE determines whether Access control for CSFB allows or disallows originating session requests for CSFB are equivalent to those for enhanced Access control on E-UTRAN, as described in clause 4.3.1.
+- If access is not granted for the UE, mobile originating session requests for CSFB shall be restricted for a certain period of time to avoid overload of E-UTRAN due to continuous mobile originating session requests from the same UE. The duration of the period shall be determined using the same operation specified in Clause 4.3.1.
+- In case the network does not provide the Access control for CSFB information, the UE shall be subject to access class barring for Access Classes 0-9 and 11-15 as described in Clause 4.3.1.
+
+### 4.3.4 Extended Access Barring
+
+#### 4.3.4.1 General
+
+Extended Access Barring (EAB) is a mechanism for the operator(s) to control Mobile Originating access attempts from UEs that are configured for EAB in order to prevent overload of the access network and/or the core network. In congestion situations, the operator can restrict access from UEs configured for EAB while permitting access from other UEs. UEs configured for EAB are considered more tolerant to access restrictions than other UEs. When an operator determines that it is appropriate to apply EAB, the network broadcasts necessary information to provide EAB control for UEs in a specific area. The following requirements apply for EAB:
+
+- The UE is configured for EAB by the HPLMN
+- EAB shall be applicable to all 3GPP Radio Access Technologies.
+- EAB shall be applicable regardless of whether the UE is in a Home or a Visited PLMN.
+- A network may broadcast EAB information.
+- EAB information shall define whether EAB applies to UEs within one of the following categories:
+  - a) UEs that are configured for EAB;
+  - b) UEs that are configured for EAB and are neither in their HPLMN nor in a PLMN that is equivalent to it;
+  - c) UEs that are configured for EAB and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN
+- EAB information shall also include extended barring information for Access Classes 0-9.
+- A UE configured for EAB shall use its allocated Access Class(es), as defined in sub-clause 4.2, when evaluating the EAB information that is broadcast by the network, in order to determine if its access to the network is barred.
+- If a UE that is configured for EAB initiates an emergency call or is a member of an Access Class in the range 11-15 and according to clause 4.3.1 that Access Class is permitted by the network, then the UE shall ignore any EAB information that is broadcast by the network.
+- If the network is not broadcasting the EAB information, the UE shall be subject to access barring as described in clause 4.3.1
+- If the EAB information that is broadcast by the network does not bar the UE, the UE shall be subject to access barring as described in clause 4.3.1.
+- In the case of multiple core networks sharing the same access network, the access network shall be able to apply the EAB for the different core networks individually.
+
+#### 4.3.4.2 Overriding extended access barring
+
+Overriding Extended Access Barring is a mechanism for the operator to allow UEs that are configured for EAB to access the network under EAB conditions. The following requirements apply:
+
+- The UE configured with EAB may be configured by the HPLMN with a permission to override EAB.
+- For a UE configured with the permission to override EAB, the user or application (upper layers in UE) may request the UE to activate PDN connection(s) for which EAB does not apply.
+- The UE shall override any EAB restriction information that is broadcast by the network as long as it has an active PDN connection for which EAB does not apply.
+
+## 4.4 Emergency Calls
+
+An additional control bit known as "Access Class 10" is also signalled over the air interface to the UE. This indicates whether or not network access for Emergency Calls is allowed for UEs with access classes 0 to 9 or without an IMSI.
+
+For UEs with access classes 11 to 15, Emergency Calls are not allowed if both "Access class 10" and the relevant Access Class (11 to 15) are barred. Otherwise, Emergency Calls are allowed.
+
+## 4.4a Multimedia Priority Service
+
+Multimedia Priority Service (TS 22.153 [16]) shall be assigned its own unique access class value (i.e., one of the special access classes 11 to 15). The assigned access class value for Multimedia Priority Service is based on regional/national regulatory requirements and operator policy.
+
+## 4.5 Control of UE Capabilities
+
+To protect the user from the effects of a misbehaving UE (e.g. causing additional charges, degraded performance) and to protect the network operator's network capacity, including radio resources and network signalling and processing, means shall be provided for the HPLMN/EHPLMN and the VPLMN to provide an indication to the UE as to which network provided services or functions it is not allowed to use.
+
+The Selective UE Capabilities list, shall be maintained in the UE and the UE shall not request any services indicated as disabled. At registration the HPLMN/EHPLMN or VPLMN may interrogate the status of the list and provide a new list.
+
+The Selective UE Capabilities list shall not be deleted at switch off and will remain valid until a new list is provided by the network. The Selective UE Capabilities list relates to the ME and not to the subscription.
+
+It should be ensured that UEs are not maliciously disabled, including malicious disabling by a VPLMN, or accidentally disabled, or kept disabled, and there shall be a mechanism for restoring disabled UEs in all situations (e.g. in the case that the serving network does not support the control of UE Capabilities).
+
+The UE should use the indications given in the Selective UE Capabilities list to inform the user of the non-availability of services or functions.
+
+There shall be a means for the network to provide an optional customer service number(s) which can be used, by the user, to assist in determining the cause of non-availability of specific services. The specifications should also provide the capability for the network to include an optional text string that will be displayed by the UE.
+
+The UE Capabilities list shall take precedence over subscribed services.
+
+The services to be included in the list are:
+
+- Call Control functions
+- Supplementary Services
+- Emergency Calls (including the (U)SIM-less case and subject to regional regulatory requirements, i.e. emergency calls shall not be disabled in regions where support of them is required)
+- SMS, via CS and PS
+- LCS, via CS and PS
+- GPRS based services
+- MBMS
+- IMS
+
+# --- 5 Support of Localised Service Area (SoLSA)
+
+SoLSA consists of a set of service features that give the operator a basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber. (3GPP TS 22.043 [5]). The following section is only applicable to the support of SoLSA functionality in GERAN.
+
+## 5.1 Network selection
+
+The standard automatic and manual network selection procedures will be used.
+
+Manual network selection may be required when the PLMN providing the users SoLSA service is not the one on which the user is currently registered.
+
+At manual network selection the UE shall provide the means to present the subscribers LSA(s) for each PLMN presented.
+
+## 5.2 The Idle-mode operation
+
+The UE shall always select a valid LSA with the highest priority.
+
+### 5.2.1 Subscriber moving from a normal environment to his localised service area.
+
+The UE shall have the ability to prioritise allowed LSA cells in reselection, making it possible to camp on a LSA cell earlier (the function shall be network controlled).
+
+### 5.2.2 Subscriber moving away from his localised service area to a normal environment.
+
+The UE shall have the ability to prioritise allowed LSA cells in reselection, making it possible to camp on a LSA cell longer (the function shall be network controlled).
+
+### 5.2.3 Subscriber staying in his localised service area
+
+The UE shall have the ability to prioritise allowed LSA cells in reselection by being more persistent (the function shall be network controlled).
+
+Note: Typically in indoor environments there are occasional reflections and "disturbances" due to macro cells, e.g. near the windows. In such a case LSA cells should be favoured even though there is higher field strength available from the outdoor cells.
+
+## 5.3 LSA only access
+
+It shall be possible to allow LSA user to access PLMN only within his LSAs. A LSA user is not allowed to receive and/or originate a call outside the allowed LSA area.
+
+When UE is out of the allowed LSA area it shall be registered in PLMN but indicate subscriber/service specific "out of LSA area" notification. It shall be a network controlled function to prevent terminated or/and originated calls. Emergency calls are however always allowed.
+
+## 5.4 Exclusive access
+
+Access to exclusive access cells is restricted to defined LSA subscribers.
+
+Non-LSA subscriber shall consider exclusive access cells as not suitable, only allowing to camp for emergency calls (limited service state 3GPP TS 23.122 [3]).
+
+## 5.5 Preferential access
+
+As a network controlled function it shall be possible in LSA to allocate resources at call setup and during the active mode to LSA users compared to non-LSA users.
+
+# --- 6 Support of 3GPP - WLAN Interworking
+
+Support of 3GPP-WLAN interworking and network selection is captured in TS 22.234 [6]
+
+6.1 Void
+
+6.2 Void
+
+6.3 Void
+
+# --- 7 Administrative restriction of subscribers' access
+
+## 7.1 Allowed Location and Routing Area identities access
+
+Means shall be standardised for an administrative restriction of subscribers' access without the need of having explicit Tracking/Location/Routing Area identities in the individual subscription profiles.
+
+To achieve this it shall be possible to indicate per subscriber, in subscription data, allowed categories of Tracking/Location/Routing Areas. It shall be possible to use this subscription information to restrict subscribers' access to categories of Tracking/Location/Routing Areas in serving networks accordingly.
+
+As a minimum, at least one of the following categories shall be available:
+
+- a) GERAN
+- b) UTRAN
+- c) E-UTRAN
+
+There might be cases where the visited network has not separated the Location/Routing area categories, in which case the administrative restriction of subscribers' access to only GERAN or UTRAN will not be possible.
+
+This administrative restriction of subscribers' access shall be an optional feature.
+
+7.2 Void
+
+# --- 8 Support of Home NodeB and Home E-NodeB
+
+The service requirements for Home NodeB and Home eNodeB can be found in [14].
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |      |     |       |     |                                                                                                                                                                 |       |       |                          |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|--------------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                                                                                                                 | Old   | New   | Work Item                |
+| Jun 1999       |           |           | 02.04  |      |     |       |     | Transferred to 3GPP SA1                                                                                                                                         | 7.0.0 | 3.0.0 |                          |
+| SA#04          |           |           | 02.04  |      |     |       |     |                                                                                                                                                                 | 3.0.0 |       |                          |
+| SP-05          | SP-99479  | S1-99610  | 22.011 | 0001 |     | R99   | D   | Editorial changes for alignment                                                                                                                                 | 3.0.0 | 3.0.1 |                          |
+| SP-06          | SP-99524  | S1-991032 | 22.011 | 0002 |     | R99   | B   | COMPACT Cell Selection Part 2                                                                                                                                   | 3.0.1 | 3.1.0 |                          |
+| SP-06          | SP-99606  |           | 22.011 | 0003 | 1   | R99   | B   | Network Selection                                                                                                                                               | 3.0.1 | 3.1.0 |                          |
+| SP-06          | SP-99607  |           | 22.011 | 0004 | 1   | R99   | B   | Control of user preference field                                                                                                                                | 3.0.1 | 3.1.0 |                          |
+| SP-07          | SP-000055 | S1-000138 | 22.011 | 0012 |     | R99   | F   | Corrections to 22.011                                                                                                                                           | 3.1.0 | 3.2.0 |                          |
+| SP-07          | SP-000055 | S1-000139 | 22.011 | 0013 |     | R99   | C   | Removal of "Home Environment Specific Network Selection Procedure"                                                                                              | 3.1.0 | 3.2.0 |                          |
+| SP-07          | SP-000071 | S1-000161 | 22.011 | 0014 |     | R00   | B   | Network Selection                                                                                                                                               | 3.1.0 | 4.0.0 |                          |
+| SP-08          | SP-000211 | S1-000335 | 22.011 | 0016 |     | R00   | B   | Reselection attempts of GPRS terminals                                                                                                                          | 4.0.0 | 4.1.0 |                          |
+| SP-09          | SP-000372 | S1-000549 | 22.011 | 0018 |     | R4    | F   | Alignment with 23.122 on selection procedure                                                                                                                    | 4.1.0 | 4.2.0 |                          |
+| SP-11          | SP-010036 | S1-010245 | 22.011 | 0021 |     | Rel-4 | A   | CR to 02.11 on Roaming restrictions for GPRS (Release4)                                                                                                         | 4.2.0 | 4.3.0 | GPRS                     |
+| SP-11          | SP-010151 |           | 22.011 | 0023 |     | Rel-4 | A   | Equivalent handling of PLMNs with different PLMN codes                                                                                                          | 4.2.0 | 4.3.0 | GSM / UMTS inter-working |
+| SP-12          | SP-010244 | S1-010495 | 22.011 | 0025 |     | Rel-4 | A   | Partial PLMN access restriction                                                                                                                                 | 4.3.0 | 4.4.0 |                          |
+| SP-12          | SP-010244 | S1-010514 | 22.011 | 0027 |     | Rel-4 | A   | Periodic Network Selection Attempt improvement                                                                                                                  | 4.3.0 | 4.4.0 |                          |
+| SP-12          | SP-010244 | S1-010517 | 22.011 | 0029 |     | Rel-4 | A   | Default value for background scanning timer                                                                                                                     | 4.3.0 | 4.4.0 |                          |
+| SP-14          | SP-010685 | S1-011341 | 22.011 | 0031 |     | Rel-4 | A   | CR to 22.011 R4 'Interaction between equivalent PLMN list and periodic network selection attempts'                                                              | 4.4.0 | 4.5.0 |                          |
+| SP-14          | SP-010684 | S1-011334 | 22.011 | 0035 |     | Rel-4 | A   | CR to 22.011 R4 'Editorial improvements'                                                                                                                        | 4.4.0 | 4.5.0 |                          |
+| SP-14          | SP-010688 | S1-011336 | 22.011 | 0037 |     | Rel-4 | A   | CR to 22.011 R4 'Clarification on the UE behaviour when receiving a registration rejection'                                                                     | 4.4.0 | 4.5.0 |                          |
+| SP-14          | SP-010687 | S1-011338 | 22.011 | 0039 |     | Rel-4 | A   | CR to 22.011 R4 'Simplification of the procedure for user PLMN reselection'                                                                                     | 4.4.0 | 4.5.0 |                          |
+| SP-14          | SP-010686 | S1-011339 | 22.011 | 0041 |     | Rel-4 | A   | CR to 22.011 R4 'Interaction between "equivalent PLMN" list and "Forbidden PLMN" list'                                                                          | 4.4.0 | 4.5.0 |                          |
+| SP-14          | SP-010757 | ---       | 22.011 | 0042 | 2   | Rel-4 | A   | Interaction between ePLMN and manual mode                                                                                                                       | 4.4.0 | 4.5.0 |                          |
+| SP-15          | SP-010158 | ---       | 22.011 | 0045 | 1   | Rel-4 | A   | CR to 22.011 Rel-4: clarification of the term 'country'<br><br>Note: special dispensation was given by SA #15 to allow some leeway on the position of the note. | 4.5.0 | 4.6.0 |                          |
+| SP-16          | SP-020238 | S1-021058 | 22.011 | 0046 |     | Rel-4 | F   | Editorial corrections on 22.011                                                                                                                                 | 4.6.0 | 4.7.0 | CORRECT                  |
+| SP-16          | SP-020267 | S1-021043 | 22.011 |      |     | Rel-5 |     | Updated from Rel-4 to Rel5                                                                                                                                      | 4.7.0 | 5.0.0 |                          |
+| SP-17          | SP-020547 | S1-021826 | 22.011 | 0049 |     | Rel-5 | A   | CR to 22.011 Rel 5 - correction to periodic PLMN scan                                                                                                           | 5.0.0 | 5.1.0 | TEI4                     |
+| SP-19          | SP-030035 | S1-030236 | 22.011 | 0050 | -   | Rel-6 | B   | Netshare CR to TS 22.011                                                                                                                                        | 5.1.0 | 6.0.0 | NTShar-CR                |
+| SP-20          | SP-030249 | S1-030504 | 22.011 | 0051 |     | Rel-6 | B   | Network Selection requirements for WLAN Interworking                                                                                                            | 6.0.0 | 6.1.0 | WLAN-CR                  |
+| SP-20          | SP-030248 | S1-030532 | 22.011 | 0052 |     | Rel-6 | B   | Network selection in shared networks                                                                                                                            | 6.0.0 | 6.1.0 | NTShar-CR                |
+| SP-22          | SP-030774 | -         | 22.011 | 0053 | 1   | Rel-6 | B   | Administrative restriction of subscribers' access                                                                                                               | 6.1.0 | 6.2.0 | TEI                      |
+| SP-23          | SP-040088 | S1-040200 | 22.011 | 0054 | -   | Rel-6 | C   | Periodic network selection attempts enhancement                                                                                                                 | 6.2.0 | 6.3.0 | TEI                      |
+| SP-23          | SP-040089 | S1-040257 | 22.011 | 0056 | -   | Rel-6 | F   | Priority usage of UICC parameters for I-WLAN                                                                                                                    | 6.2.0 | 6.3.0 | WLAN                     |
+
+| Change history |           |           |        |      |   |       |   |                                                                                                          |       |       |                    |
+|----------------|-----------|-----------|--------|------|---|-------|---|----------------------------------------------------------------------------------------------------------|-------|-------|--------------------|
+| SP-23          | SP-040101 | S1-040260 | 22.011 | 0057 | - | Rel-6 | D | Extraction of redundant WLAN network selection information [- now in WLAN TS22.234]                      | 6.2.0 | 6.3.0 | WLAN               |
+| SP-24          | SP-040287 | S1-040438 | 22.011 | 0058 | - | Rel-6 | F | Behaviour of Single Mode mobiles with regards to the use of access technology in the PLMN selector lists | 6.3.0 | 6.4.0 | TEI6               |
+| SP-24          | SP-040287 | S1-040442 | 22.011 | 0060 | - | Rel-6 | F | Use of access technology in Periodic Network Selection attempts                                          | 6.3.0 | 6.4.0 | TEI6               |
+| SP-24          | SP-040287 | S1-040443 | 22.011 | 0061 | - | Rel-6 | F | Clarification on the use of the RAT during network selection                                             | 6.3.0 | 6.4.0 | TEI6               |
+| SP-24          | SP-040295 | S1-040526 | 22.011 | 0064 | - | Rel-6 | F | Priority usage of UICC parameters for I-WLAN                                                             | 6.3.0 | 6.4.0 | WLAN-CR            |
+| SP-24          | SP-040299 | S1-040445 | 22.011 | 0062 | - | Rel-7 | F | Multimode terminals with 3GPP capability                                                                 | 6.3.0 | 7.0.0 | TEI7               |
+| SP-24          | SP-040298 | S1-040448 | 22.011 | 0063 | - | Rel-7 | B | Support of multiple HPLMN codes                                                                          | 6.3.0 | 7.0.0 | TEI7               |
+| SP-27          | SP-050063 | S1-050233 | 22.011 | 0066 | - | Rel-7 | B | Addition of "Network Control of UE Capabilities"                                                         | 7.0.0 | 7.1.0 | Network Protection |
+| SP-27          | SP-050063 | S1-050245 | 22.011 | 0067 | - | Rel-7 | B | Reinstate CR016 for GPRS Terminal PLMN Reselection                                                       | 7.0.0 | 7.1.0 | TEI-4              |
+| SP-29          | SP-050521 | S1-050903 | 22.011 | 0068 | - | Rel-7 | C | Enhancement of the EHPLMN feature to allow load balancing                                                | 7.1.0 | 7.2.0 | TEI7               |
+| SP-31          | SP-060221 | -         | 22.011 | 0069 | 2 | Rel-7 | C | The Last RPLMN                                                                                           | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-31          | SP-060033 | S1-060330 | 22.011 | 0070 | - | Rel-7 | B | Confirmed Roaming                                                                                        | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-31          | SP-060033 | S1-060331 | 22.011 | 0071 | - | Rel-7 | F | Capability of UE to read USIM information for Network Selection                                          | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-31          | SP-060033 | S1-060332 | 22.011 | 0072 | - | Rel-7 | C | Displaying all available EHPLMNs in Manual Mode                                                          | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-31          | SP-060033 | S1-060333 | 22.011 | 0073 | - | Rel-7 | B | Requirement for presentation of additional information in manual mode                                    | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-31          | SP-060033 | S1-060335 | 22.011 | 0074 | - | Rel-7 | B | Network selection mode at switch-on                                                                      | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-31          | SP-060033 | S1-060352 | 22.011 | 0075 | - | Rel-7 | B | Steering of Roaming                                                                                      | 7.2.0 | 7.3.0 | NSP-CR             |
+| SP-32          | SP-060311 | S1-060630 | 22.011 | 0076 | - | Rel-7 | C | Clarification on confirmed roaming applicability                                                         | 7.3.0 | 7.4.0 | NSP-CR             |
+| SP-32          | SP-060311 | S1-060632 | 22.011 | 0077 | - | Rel-7 | C | Incomplete PLMN list for manual mode information                                                         | 7.3.0 | 7.4.0 | NSP-CR             |
+| SP-32          | SP-060426 | -         | 22.011 | 0078 | 1 | Rel-7 | C | Exception in Manual network selection mode when HPLMN is available at power-on                           | 7.3.0 | 7.4.0 | NSP-CR             |
+| SP-32          | SP-060451 | S1-060649 | 22.011 | 0079 | 3 | Rel-7 | C | Interaction of steering of roaming with User controlled and forbidden PLMN list                          | 7.3.0 | 7.4.0 | NSP-CR             |
+| SP-34          | SP-060762 | S1-061314 | 22.011 | 0080 | - | Rel-7 | F | Additional Information in Manual Mode                                                                    | 7.4.0 | 7.5.0 | NSP-CR             |
+| SP-35          | SP-070119 | S1-070182 | 22.011 | 0081 | 1 | Rel-7 | F | Removal of "Confirmed Roaming" enhancement (section 3.2.2.7)                                             | 7.5.0 | 7.6.0 | NSP-CR             |
+| SP-35          | SP-070119 | S1-070294 | 22.011 | 0083 | 2 | Rel-7 | C | Single EHPLMN Display Name in Manual Mode (CR to 22.011)                                                 | 7.5.0 | 7.6.0 | NSP-CR             |
+| SP-35          | SP-070129 | S1-070285 | 22.011 | 0082 | 2 | Rel-8 | C | Administrative restriction of subscribers' access                                                        | 7.6.0 | 8.0.0 | SAE-R              |
+| SP-36          | SP-070474 |           | 22.011 | 0085 | - | Rel-8 | A | Clarification on User Controlled PLMNs in SoR                                                            | 8.0.0 | 8.1.0 | NSP-CR             |
+| SP-38          | SP-070855 | S1-071842 | 22.011 | 0091 | - | Rel-8 | C | EPS Alignment - References and Definitions                                                               | 8.1.0 | 8.2.0 | AIPN-SAE-R         |
+| SP-38          | SP-070855 | S1-071910 | 22.011 | 0092 | 1 | Rel-8 | C | EPS Alignment - 3.2.2 Procedures                                                                         | 8.1.0 | 8.2.0 | AIPN-SAE           |
+| SP-38          | SP-070855 | S1-071911 | 22.011 | 0093 | 1 | Rel-8 | C | EPS Alignment - 7 Administrative restriction of subscribers/Æ access                                     | 8.1.0 | 8.2.0 | AIPN-SAE           |
+| SP-38          | SP-070855 | S1-071925 | 22.011 | 0099 | 1 | Rel-8 | B | Additional requirement for location registration                                                         | 8.1.0 | 8.2.0 | AIPN-SAE           |
+| SP-38          | SP-070859 | S1-071943 | 22.011 | 0098 | 2 | Rel-8 | F | Correction to EHPLMN terminology and editorials                                                          | 8.1.0 | 8.2.0 | TEI8               |
+| SP-38          | SP-070913 | -         | 22.011 | 0090 | 2 | Rel-8 | A | EHPLMN case added to the optimisation for automatic network selection                                    | 8.1.0 | 8.2.0 | NSP-CR             |
+| SP-38          | SP-070934 | -         | 22.011 | 0095 | 2 | Rel-8 | F | DSAC requirement in UMTS                                                                                 | 8.1.0 | 8.2.0 | TEI8               |
+| SP-38          | SP-070942 | -         | 22.011 | 0094 | 4 | Rel-8 | B | PPAC requirement                                                                                         | 8.1.0 | 8.2.0 | PPACR              |
+
+| Change history |           |            |        |      |    |        |   |                                                                           |        |        |          |
+|----------------|-----------|------------|--------|------|----|--------|---|---------------------------------------------------------------------------|--------|--------|----------|
+| SP-39          | SP-080026 | S1-080155  | 22.011 | 0101 | 1  | Rel-8  | A | EHPLMN recovery lack of coverage                                          | 8.2.0  | 8.3.0  | NSP-CR   |
+| SP-39          | SP-080034 | S1-080351  | 22.011 | 0102 | 2  | Rel-8  | B | HNB/HeNB - Closed Subscriber Group (CSG) definitions for UTRA and E-UTRA  | 8.2.0  | 8.3.0  | HomeNB   |
+| SP-39          | SP-080042 | S1-080326  | 22.011 | 0107 | 1  | Rel-8  | C | basic access control enhancement for EPS                                  | 8.2.0  | 8.3.0  | AIPN-SAE |
+| SP-39          | SP-080041 | S1-080331  | 22.011 | 0108 | 1  | Rel-8  | C | Barring of inbound roamers of previous release networks from E-UTRAN      | 8.2.0  | 8.3.0  | TEI8     |
+| SP-39          | SP-080188 | -          | 22.011 | 0109 | 4  | Rel-8  | B | HNB/HeNB - Closed Subscriber Group (CSG) requirements for UTRA and E-UTRA | 8.2.0  | 8.3.0  | HomeNB   |
+| SP-40          | SP-080301 | S1-080655  | 22.011 | 0114 | 1  | Rel-8  | D | Delete CSGs related access restriction requirements                       | 8.3.0  | 8.4.0  | HomeNB   |
+| SP-40          | SP-080301 | S1-080656  | 22.011 | 0115 | 2  | Rel-8  | F | Introduction of length for HNBID                                          | 8.3.0  | 8.4.0  | HomeNB   |
+| SP-40          | SP-080301 | S1-080767  | 22.011 | 0116 | 3  | Rel-8  | F | HNB/HeNB - Closed Subscriber Group (CSG) requirements for UTRA and E-UTRA | 8.3.0  | 8.4.0  | HomeNB   |
+| SP-40          | SP-080432 | -          | 22.011 | 0117 | 3  | Rel-8  | F | Relation between EPS Services and GPRS Services                           | 8.3.0  | 8.4.0  | SAE      |
+| SP-40          | SP-080301 | S1-080663  | 22.011 | 0118 | -  | Rel-8  | C | Removal of GERAN - E-UTRAN connected mode handover requirement from HeNB  | 8.3.0  | 8.4.0  | HomeNB   |
+| SP-40          | SP-080453 | -          | 22.011 | 0119 | 4  | Rel-8  | C | PPAC restriction to UTRAN                                                 | 8.3.0  | 8.4.0  | PPACR    |
+|                |           |            |        |      |    |        |   | Corrects typos in previous line of history table.                         | 8.4.0  | 8.4.1  |          |
+| SP-41          | SP-080493 | S1-082333  | 22.011 | 0122 | 2  | Rel-8  | F | Correction on definition of length for HNBID                              | 8.4.1  | 8.5.0  | HomeNB   |
+| SP-41          | SP-080493 | S1-082354  | 22.011 | 0120 | 2  | Rel-8  | F | Essential correction to manual CSG selection                              | 8.4.1  | 8.5.0  | HomeNB   |
+| SP-41          | SP-080493 | S1-082389  | 22.011 | 0123 | 2  | Rel-8  | F | Additional HNB/HeNB operator requirements                                 | 8.4.0  | 8.5.0  | HomeNB   |
+| SP-41          | SP-080493 | S1-082393  | 22.011 | 0128 | 2  | Rel-8  | F | Terminology alignment and generalization of requirements                  | 8.4.1  | 8.5.0  | HomeNB   |
+| SP-42          | SP-080771 | S1-083443  | 22.011 | 132  | 2  | Rel-8  | F | Correction to the maximum limit requirement of CSG members                | 8.5.0  | 8.6.0  | HomeNB   |
+| SP-42          | SP-080771 | S1-083250  | 22.011 | 0133 | 1  | Rel-8  | F | HNB/HeNB and pre-release 8 USIM                                           | 8.5.0  | 8.6.0  | HeNB     |
+| SP-42          | SP-080773 | S1-083380  | 22.011 | 0134 | 1  | Rel-8  | F | PPAC CR alignment with CT1                                                | 8.5.0  | 8.6.0  | PPAC     |
+| SP-42          | SP-080771 | S1-084409  | 22.011 | 0137 | 2  | Rel-8  | F | Correction of HNB/HeNB display requirements and manual CSG selection      | 8.5.0  | 8.6.0  | HomeNB   |
+| SP-42          | SP-080874 | S1-084408  | 22.011 | 0139 | 2  | Rel-8  | C | Home network independent support of roamers in CSG                        | 8.5.0  | 8.6.0  | HomeNB   |
+| SP-42          | SP-080771 | S1-084410  | 22.011 | 0140 | 1  | Rel-8  | B | HNB mobility                                                              | 8.5.0  | 8.6.0  | HomeNB   |
+| SP-42          | SP-080785 | S1-084389  | 22.011 | 0136 | 2  | Rel-9  | B | SSAC Services Specific Access Control Requirements                        | 8.6.0  | 9.0.0  | SSACR    |
+| SP-43          | SP-090195 | S1-090161  | 22.011 | 0142 | 1  | Rel-9  | D | Removing the content of chapter 8 and add a reference instead.            | 9.0.0  | 9.1.0  | EHNB     |
+| SP-45          | SP-090669 | -          | 22.011 | 0156 | 1  | Rel-9  | F | Description Alignment of Access Class Barring for E-UTRAN with Stage 3    | 9.1.0  | 9.2.0  | TEI9     |
+| SP-46          | SP-090841 | S1-094330  | 22.011 | 0158 | 1  | Rel-9  | F | Alignment between SSAC and Common AC                                      | 9.2.0  | 9.3.0  | SSAC     |
+| SP-48          | SP-100442 | S1-101221r | 22.011 | 0161 | 4  | Rel-10 | B | Access control for CSFB                                                   | 9.3.0  | 10.0.0 | TEI10    |
+| SP-49          | SP-100580 | S1-102153  |        |      |    |        |   | Clarification on roaming in shared networks                               | 10.0.0 | 10.1.0 | TEI10    |
+|                |           |            | 22.011 | 0166 | -  | Rel-10 | F |                                                                           |        |        |          |
+| SP-49          | SP-100580 | S1-102178  |        |      |    |        |   |                                                                           | 10.0.0 | 10.1.0 | TEI10    |
+|                |           |            | 22.011 | 0163 | 1  | Rel-10 | F | Clarification of ACB for CSFB                                             |        |        |          |
+| SP-49          | SP-100580 | S1-102178  |        |      |    |        |   |                                                                           | 10.0.0 | 10.1.0 | TEI10    |
+|                |           |            | 22.011 | 0163 | 1  | Rel-10 | F | Clarification of ACB for CSFB                                             |        |        |          |
+| SP-50          | SP-100893 | S1-103336  | 22.011 | 0168 | 12 | Rel-10 | B | Access Control for Machine Type Communications                            | 10.1.0 | 10.2.0 | NIMTC    |
+| SP-50          | SP-100805 | S1-103328  | 22.011 | 0171 | -  | Rel-10 | F | Clarification of Access Class Barring for CSFB                            | 10.1.0 | 10.2.0 | TEI10    |
+| -              |           |            |        |      |    |        |   | LTE logo changed into LTE Advanced logo                                   | 10.2.0 | 10.2.1 | -        |
+| SP-51          | SP-110162 | S1-110409  | 22.011 | 0175 | 3  | Rel-10 | F | Clarifications for Extended Access Barring                                | 10.2.1 | 10.3.0 | NIMTC    |
+| SP-52          | SP-110374 | S1-111118  | 22.011 | 0181 | -  | Rel-11 | F | Clarification on applicability of EAB                                     | 10.3.0 | 11.0.0 | SIMTC    |
+
+| Change history |           |           |        |      |   |        |   |                                                                    |        |        |            |
+|----------------|-----------|-----------|--------|------|---|--------|---|--------------------------------------------------------------------|--------|--------|------------|
+| SP-52          | SP-110374 | S1-111376 | 22.011 | 0178 | 2 | Rel-11 | B | Clarification on how EAB is applied in Shared Network              | 10.3.0 | 11.0.0 | SIMTC      |
+| SP-53          | SP-110582 | S1-112243 | 22.011 | 0182 | 2 | Rel-11 | F | Support of countries with multiple MCC values                      | 11.0.0 | 11.1.0 | TEI11      |
+| SP-54          | SP-110813 | S1-113443 | 22.011 | 0186 | 1 | Rel-11 | F | Applicability of Access Class Barring in a FULL-MOCN configuration | 11.1.0 | 11.2.0 | TEI11      |
+| SP-59          | SP-130123 | S1-131287 | 22.011 | 0191 | 2 | Rel-11 | F | Overriding extended access barring                                 | 11.2.0 | 11.3.0 | TEI11      |
+| SP-66          | SP-140747 | S1-144319 | 22.011 | 208  | - | Rel-11 | F | Alignment CR regarding ACB MOCN-support                            | 11.3.0 | 11.4.0 | TEI11      |
+| SP-68          | SP-150270 | S1-151544 | 22.011 | 211  | 2 | Rel-11 | A | Access Class for MPS (Rel-11 Mirror)                               | 11.4.0 | 11.5.0 | ePRIOR-St1 |

marked/Rel-11/22_series/22016/raw.md

@@ -0,0 +1,147 @@
+
+
+
+
+
+
+# Contents
+
+|                                                |   |
+|------------------------------------------------|---|
+| Foreword .....                                 | 4 |
+| 1 Scope.....                                   | 5 |
+| 1.1 References .....                           | 5 |
+| 1.2 Definitions and abbreviations.....         | 5 |
+| 2 General .....                                | 5 |
+| 3 Composition of IMEI .....                    | 6 |
+| 4 Use of the equipment identity register ..... | 6 |
+| 5 Procedure .....                              | 6 |
+| 6 Use of IMEI in case of emergency calls ..... | 6 |
+| 7 MS Software Version Number (SVN).....        | 7 |
+| Annex A (informative): Change history.....     | 8 |
+
+# --- 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 defines the principal purpose and use of International Mobile station Equipment Identities (IMEI).
+
+3GPP TS 23.003 describes the technical manner of numbering, addressing and identification.
+
+## 1.1 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+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 TS 23.003: "Numbering, addressing and identification".
+- [3] ISO/IEC 7812 (1989): "Identification cards - Numbering system and registration procedure for issuer identifiers".
+
+## 1.2 Definitions and abbreviations
+
+In addition to the following, abbreviations used in the present document are listed in 3GPP TS 21.905.
+
+**International Mobile Station Equipment Identity (IMEI)** : An "International Mobile Station Equipment Identity" is a unique number which shall be allocated to each individual mobile station equipment in the PLMN and shall be unconditionally implemented by the MS manufacturer.
+
+# --- 2 General
+
+An MS can only be operated if a valid "International Mobile Subscriber Identity" (IMSI) is present. An IMSI is primarily intended for obtaining information on the use of the PLMN by subscribers for individual charging purposes.
+
+Besides the IMSI, the implementation of IMEI is found necessary in order to obtain knowledge about the presence of specific mobile station equipment in the network, disregarding whatever subscribers are making use of these equipments.
+
+The main objective is to be able to take measures against the use of stolen equipment or against equipment of which the use in the PLMN can not or no longer be tolerated for technical reasons.
+
+The IMEI is incorporated in an UE module which is contained within the UE. The IMEI shall be unique and shall not be changed after the ME's final production process. It shall resist tampering, i.e. manipulation and change, by any means (e.g. physical, electrical and software).
+
+NOTE: This requirement is valid for new GSM MEs type approved after 1st June 2002. However, this requirement is applicable to all 3GPP system compatible UEs from start of production.
+
+The manufacturer implementing the IMEI module in the ME is responsible for ensuring that each IMEI within the allocated range is unique to the ME in which it resides, and is also responsible for keeping detailed records of produced and delivered MEs.
+
+# --- 3 Composition of IMEI
+
+The composition of the IMEI shall be such that each individual mobile station equipment can be separately identified.
+
+Information is contained in the IMEI by which the PLMN, after requesting it, can immediately decide whether or not to accept calls made by means of this equipment.
+
+Secondly, the IMEI shall directly or indirectly contain all information which is necessary for the network operator to make relations through its administrative system to trace the equipment to its origin of production. 3GPP TS 23.003 [2] describes the structure of the IMEI in detail.
+
+The IMEI is complemented by a check digit. The check digit is not part of the digits transmitted at IMEI check occasions, as described below. The Check Digit shall avoid manual transmission errors, e.g. when customers register stolen MEs at the operators customer care desk.
+
+NOTE: The Check Digit is not applied to the Software Version Number.
+
+# --- 4 Use of the equipment identity register
+
+A network operator can make administrative use of the IMEI in the following manner:
+
+Three registers are defined, known as "white lists", "grey lists" and "black lists". The use of such lists is at the operators' discretion.
+
+The **white list** is composed of all **number series** of equipment identities that are permitted for use.
+
+The **black list** contains all equipment identities that belong to equipment that need to be barred.
+
+Besides the black and white list, administrations have the possibility to use a **grey list**. Equipments on the grey list are not barred (unless on the black list or not on the white list), but are tracked by the network (for evaluation or other purposes).
+
+# --- 5 Procedure
+
+It shall be possible to perform the IMEI check at any access attempt, except IMSI detach, and during an established call at any time when a dedicated radio resource is available, in accordance with the security policy of the PLMN operator. It shall also be possible to perform the IMEI check when a UE is IMS registered.
+
+The network shall terminate any access attempt or ongoing call when receiving any of the answers "black-listed" (i.e., on the black list) or "unknown" equipment (i.e., not on the white list) from the EIR. An indication of "illegal ME" shall in these cases be given to the user. Furthermore this is equivalent to an authentication failure hence any call or IMS session establishment or any location updating is forbidden for the MS, it cannot answer to paging, it is just allowed to perform Emergency Calls. Emergency calls must never be terminated as a result of the IMEI check procedure.
+
+# --- 6 Use of IMEI in case of emergency calls
+
+Emergency calls can in some PLMNs be made without having to send the subscriber identity (IMSI) to the network. In this case the misuse of MS equipments after placing invalid emergency calls can be restrained by using the equipment identity.
+
+The network request for the equipment identity is sent to the MS after the emergency call has been set-up. The procedure is the same as for normal call set-up.
+
+# --- 7 MS Software Version Number (SVN)
+
+A Software Version Number (SVN) field shall be provided. This allows the ME manufacturer to identify different software versions of a given mobile.
+
+The SVN is a separate field from the IMEI, although it is associated with the IMEI. When the network requests the IMEI from the MS, it may also request that the SVN is also sent towards the network.
+
+The white list shall use the IMEI, The Black and Grey Lists may also use the SVN.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |            |      |      |       |     |                                                                                               |        |        |                   |
+|----------------|-----------|-----------|------------|------|------|-------|-----|-----------------------------------------------------------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec       | CR   | R ev | Rel   | Cat | Subject/Comment                                                                               | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02 .16 |      |      |       |     | Transferred to 3GPP SA1                                                                       | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.016     |      |      |       |     | Transferred to 3GPP SA1                                                                       |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99611  | 22.016     | 001  |      | R99   | D   | Editorial changes for alignment                                                               | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-06          | SP-99601  | P-99-777  | 22.016     | 002  |      | R99   | F   | Modification of section 2 to enhance IMEI security                                            | 3.0.1  | 3.1.0  |                   |
+| SP-08          | SP-000195 | S1-000441 | 22.016     | 003  | 1    | R99   | F   | IMEI coding                                                                                   | 3.1.0  | 3.2.0  |                   |
+| SP-08          | SP-000194 | S1-000266 | 22.016     | 004  |      | R99   | F   | Modification of section 2 to delete unnecessary information about phases and releases removed | 3.1.0  | 3.2.0  |                   |
+| SP-11          | SP-010065 | S1-010258 | 22.016     |      |      | Rel-4 |     | Transferred to 3GPP Release 4                                                                 | 3.2.0  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.016     | 006  | -    | Rel-4 | F   | Editorial CR to correct terms and                                                             | 4.0.0  | 4.1.0  | CORRECT           |
+| SP-16          | SP-020237 | S1-021149 | 22.016     | 008  |      | Rel-4 | A   | Type approval code                                                                            | 4.0.0  | 4.1.0  | TEI               |
+| SP-16          | SP-020267 | S1-021043 | 22.016     |      |      | Rel-5 |     | Updated from Rel-4 to Rel5                                                                    | 4.1.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.016     |      |      | Rel-6 |     | Updated from Rel-5 to Rel-6                                                                   | 5.0.0  | 6.0.0  |                   |
+| SP-34          | SP-060768 | S1-061444 | 22.016     | 0009 | -    | Rel-7 | F   | IMEI Check and IMS                                                                            | 6.0.0  | 7.0.0  | TEI7              |
+|                |           |           | 22.016     |      |      | Rel-7 |     | Editorial correction to version identity on front cover                                       | 7.0.0  | 7.0.1  |                   |
+| SP-42          | SP-080891 | S1-083445 | 22.016     | 0010 | 1    | Rel-7 | F   | Correction of SVN sending when network requests IMEI                                          | 7.0.1  | 7.1.0  | TEI7              |
+|                |           |           |            |      |      |       |     | Rel-8 version created                                                                         | 7.1.0  | 8.0.0  |                   |
+| SP-45          | SP-090470 | S1-093278 | 22.016     | 0013 | 2    | Rel-9 | A   | Clarify that each IMEI shall be unique                                                        | 8.0.0  | 9.0.0  | TEI9              |
+|                |           |           |            |      |      |       |     | 2010-04: correct history table                                                                | 9.0.0  | 9.0.1  |                   |
+| 2011-03        | -         | -         | -          | -    | -    | -     | -   | Update to Rel-10 version (MCC)                                                                | 9.0.1  | 10.0.0 |                   |
+| 2012-09        |           |           |            |      |      |       |     | Update to Rel-11 version (MCC)                                                                | 10.0.0 | 11.0.0 |                   |

marked/Rel-11/22_series/22032/raw.md

@@ -0,0 +1,156 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                       |          |
+|-------------------------------------------------------|----------|
+| Foreword .....                                        | 4        |
+| 1 Scope.....                                          | 5        |
+| 2 Normative references .....                          | 5        |
+| 3 Definitions and abbreviations .....                 | 5        |
+| 3.1 Definitions.....                                  | 5        |
+| 3.2 Abbreviations .....                               | 5        |
+| 4 Immediate Service Termination (IST).....            | 6        |
+| 4.1 Description .....                                 | 6        |
+| 4.2 Applicability.....                                | 6        |
+| 4.3 Normal procedure.....                             | 6        |
+| 4.4 Exception procedures .....                        | 6        |
+| 5 Security requirements between HPLMN and VPLMN ..... | 6        |
+| <b>Annex A (Informative): Normal procedure .....</b>  | <b>7</b> |
+| Annex B (Informative): Change History.....            | 8        |
+
+# --- 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
+
+This Technical Specification specifies the stage 1 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via Fraud Information Gathering System (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
+
+This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
+
+The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
+
+# --- 2 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 TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this specification the following definitions apply:
+
+**subscriber activities:** subscriber activities that must be terminated. These can be call related events (e.g. call set-up, call termination) or the invocation of call related and call independent supplementary services (e.g. Call Hold, Call Waiting, Call Transfer, Call Forwarding, Unstructured Supplementary Service Data (USSD)).
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following abbreviations apply:
+
+|             |                                    |
+|-------------|------------------------------------|
+| <b>IST</b>  | Immediate Service Termination      |
+| <b>FIGS</b> | Fraud Information Gathering System |
+
+# --- 4 Immediate Service Termination (IST)
+
+## 4.1 Description
+
+It shall be possible for the Home Public Land Mobile Network (HPLMN) to instruct any PLMN to terminate immediately all the activities of a specified HPLMN subscriber.
+
+Immediate Service Termination (IST) is controlled by the HPLMN and can be triggered by the HPLMN only.
+
+A subscriber shall be specified by the International Mobile Subscriber Identity (IMSI).
+
+For subscribers that are marked as subscribed to a CAMEL-based service, IST shall be possible using Customised Application for Mobile network Enhanced Logic (CAMEL).
+
+IST shall also be possible for subscribers who are not marked as subscribed to any CAMEL-based service (see Annex A).
+
+## 4.2 Applicability
+
+This network feature applies to all subscribed Bearer Services and Teleservices of the subscriber, except for emergency calls.
+
+## 4.3 Normal procedure
+
+The HPLMN will normally direct a request for IST for a particular subscriber to the current Visited PLMN (VPLMN) of that subscriber and the PLMN visited by the subscriber immediately prior to visiting the current VPLMN
+
+**NOTE:** In practice, the IST command will be sent to individual Mobile-services Switching Centres (MSCs), and not to "VPLMNs" as a whole (but such detail is for Stage 2 and not Stage 1). IST will therefore be sent to all MSCs in which the subscriber has (or may have) an active call, as logged by the HPLMN. These MSCs may be confined to the current VPLMN or may include MSC(s) in the PLMN visited by the subscriber immediately prior to visiting the current VPLMN (or PLMNs visited even earlier).
+
+The VPLMN shall confirm receipt of the IST command.
+
+The VPLMN shall then terminate all activities of that subscriber in the VPLMN including ongoing calls and forwarded, deflected and transferred calls. The call records of calls terminated by the operation of IST shall contain a field indicating that the call terminated because of the operation of IST.
+
+The VPLMN shall then confirm to the HPLMN that all subscriber activities in that VPLMN have been terminated.
+
+If the specified subscriber has no activities in the VPLMN then the VPLMN shall inform the HPLMN of this.
+
+## 4.4 Exception procedures
+
+If after sending an IST command to a VPLMN, the HPLMN does not receive a positive acknowledgement from the VPLMN indicating receipt and comprehension of the IST command, the HPLMN should assume that the VPLMN does not support IST.
+
+# --- 5 Security requirements between HPLMN and VPLMN
+
+It is expected that there will be a need for authentication and confidentiality of the communication made between PLMNs.
+
+These issues are for study under other work items within the SMG10 work programme.
+
+# --- Annex A (Informative): Normal procedure
+
+IST has been defined to work in co-ordination with existing GSM facilities.
+
+- 1) The HPLMN changes the subscriber's entry in the HLR to prevent the resumption of activity in the HPLMN and VPLMN after IST has terminated all subscriber activity.
+- 2) The HPLMN sends a MAP "Cancel Location" command to the VLR to prevent the resumption of activity by the subscriber within the VPLMN without reference to the HPLMN.
+- 3) The HPLMN sends an IST command to the VPLMN, (possibly a specific MAP message).
+- 4) The VPLMN confirms receipt and comprehension of the command.
+- 5) The VPLMN terminates all activities of the subscriber indicated by the command.
+- 6) The VPLMN confirms to the HPLMN that all subscriber activities have been terminated.
+
+# Annex B (Informative): Change History
+
+| Change history                                                  |        |          |      |     |     |                                                           |                                 |                                 |
+|-----------------------------------------------------------------|--------|----------|------|-----|-----|-----------------------------------------------------------|---------------------------------|---------------------------------|
+| Date                                                            | TSG #  | TSG Doc. | CR   | Rev | Cat | Subject/Comment                                           | Old                             | New                             |
+| <b>Status of GSM 02.32</b>                                      |        |          |      |     |     |                                                           |                                 |                                 |
+|                                                                 |        |          |      |     |     | No Phase 1 version                                        |                                 |                                 |
+| 06-1997                                                         | SMG#22 |          |      |     |     | to SMG#22 for information                                 |                                 | 1.0.0                           |
+| 03-1998                                                         | SMG#25 |          |      |     |     | to SMG#25 for approval                                    | 1.0.0                           | 2.0.0                           |
+| 03-1998                                                         | SMG#25 |          |      |     |     | TS approved by SMG#25. IST is part of Release 98          | 2.0.0                           | 7.0.0                           |
+| 06-1998                                                         | SMG#26 |          | A001 | -   | C   | CR 02.32-A001 (cat C) approved by SMG#26                  | 7.0.0                           | 7.1.0                           |
+| 08-1999                                                         |        |          |      |     |     | R98 publication version                                   | 7.1.0                           | 7.1.1                           |
+| 04-2000                                                         |        |          |      |     |     | R99 publication version                                   | 7.1.1                           | 8.0.0                           |
+| <b>Status of TS 42.032 (Created from TS 02.32 Release 1999)</b> |        |          |      |     |     |                                                           |                                 |                                 |
+| SP-11                                                           | 02.32  |          |      |     |     | Upgrade to 42.032 Release 4 (3GPP numbering)              | <a href="#">02.32</a><br>8.0.0  | <a href="#">42.032</a><br>4.0.0 |
+| <b>Status of TS 22.032 (Created from TS 42.032 Release 4)</b>   |        |          |      |     |     |                                                           |                                 |                                 |
+| 06-2002                                                         | SP-16  |          |      |     |     | Decision to transfer IST to 3GPP system specification set | <a href="#">42.032</a><br>4.0.0 | <a href="#">22.032</a><br>4.0.0 |
+| 06-2002                                                         | SP-16  |          |      |     |     | <a href="#">Upgrade to Rel-5</a>                          | 4.0.0                           | 5.0.0                           |
+| 12-2004                                                         | SP-26  |          |      |     |     | <a href="#">Upgrade to Rel-6</a>                          | 5.0.0                           | 6.0.0                           |
+| 06-2007                                                         | SP-36  |          |      |     |     | <a href="#">Upgrade to Rel-7</a>                          | 6.0.0                           | 7.0.0                           |
+| 12-2008                                                         | SP-42  | --       | --   | --  | --  | <a href="#">Upgrade to Rel-8</a>                          | 7.0.0                           | 8.0.0                           |
+| 12-2009                                                         | SP-46  | -        | -    | -   | -   | <a href="#">Upgrade to Rel-9</a>                          | 8.0.0                           | 9.0.0                           |
+| 2011-03                                                         | -      | -        | -    | -   | -   | <a href="#">Update to Rel-10 version (MCC)</a>            | 9.0.0                           | 10.0.0                          |
+| 2012-09                                                         | -      | -        | -    | -   | -   | <a href="#">Update to Rel-11 version (MCC)</a>            | 10.0.0                          | <b>11.0.0</b>                   |

marked/Rel-11/22_series/22034/raw.md

@@ -0,0 +1,430 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                      |    |
+|--------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                       | 5  |
+| 1 Scope.....                                                                         | 6  |
+| 2 References.....                                                                    | 6  |
+| 3 Abbreviations and definitions .....                                                | 6  |
+| 3.1 Abbreviations .....                                                              | 6  |
+| 3.2 Definitions.....                                                                 | 7  |
+| 4 Description.....                                                                   | 7  |
+| 4.1 General .....                                                                    | 7  |
+| 4.2 Applicability.....                                                               | 7  |
+| 4.3 General Bearer Services.....                                                     | 7  |
+| 4.4 Parameters to be indicated and negotiated.....                                   | 7  |
+| 4.4.1 Call set-up.....                                                               | 7  |
+| 4.4.1.1 T services .....                                                             | 8  |
+| 4.4.1.2 NT services .....                                                            | 8  |
+| 4.4.2 Network initiated modification.....                                            | 8  |
+| 4.4.2.1 T services .....                                                             | 8  |
+| 4.4.2.2 NT services .....                                                            | 9  |
+| 4.4.3 User initiated modification .....                                              | 9  |
+| 4.4.3.1 T services .....                                                             | 9  |
+| 4.4.3.2 NT services .....                                                            | 9  |
+| 4.5 Air Interface Resource Allocation.....                                           | 9  |
+| 4.5.1 Minimum GERAN Air Interface Resource Allocation and Allocation Increment ..... | 9  |
+| 4.5.2 Flexible Air Interface Resource Allocation.....                                | 9  |
+| 4.6 Symmetric and asymmetric connections.....                                        | 9  |
+| 4.6.1 Symmetric connections .....                                                    | 9  |
+| 4.6.2 Asymmetric connections .....                                                   | 9  |
+| 4.6.2.1 Asymmetric air interface connection.....                                     | 9  |
+| 4.6.2.2 Channel coding asymmetry .....                                               | 10 |
+| 4.6.3 Network choice of connection symmetry.....                                     | 10 |
+| 4.7 User Equipment/Mobile Equipment requirements.....                                | 10 |
+| 4.8 Mobility Management.....                                                         | 10 |
+| 4.9 Roaming.....                                                                     | 10 |
+| 4.10 Quality of Service.....                                                         | 11 |
+| 4.10.1 Bit error rate .....                                                          | 11 |
+| 4.10.1.1 GERAN TCH/F Bit Error Rate.....                                             | 11 |
+| 4.10.1.2 Overall GBS Bit Error Rate .....                                            | 11 |
+| 4.10.2 GERAN Radio resource management.....                                          | 11 |
+| 4.10.3 Call set-up delay.....                                                        | 11 |
+| 4.10.4 End-to-end delay .....                                                        | 11 |
+| 4.10.5 Throughput .....                                                              | 11 |
+| 4.10.6 Network planning and interference levels.....                                 | 11 |
+| 4.11 Mapping of FNUR to GERAN TCH/F for T services .....                             | 11 |
+| 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services .....                      | 11 |
+| 4.13 GBS MMI aspects .....                                                           | 12 |
+| 4.14 GBS Subscription aspects .....                                                  | 12 |
+| 4.15 GBS charging aspects.....                                                       | 12 |
+| 4.16 O and M aspects .....                                                           | 12 |
+| 4.17 Multislot security aspects .....                                                | 12 |
+| 5 Exceptional procedures or unsuccessful outcome .....                               | 13 |
+| 6 Interworking requirements.....                                                     | 13 |
+| 6.1 Service interworking .....                                                       | 13 |
+| 6.1.1 Interworking with supplementary services.....                                  | 13 |
+| 6.1.2 Interworking with other services .....                                         | 13 |
+| 6.2 Network interworking .....                                                       | 13 |
+
+Annex A (informative): Change history..................................................................................................14
+
+# --- 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 specifies the Stage 1 description of High Speed Circuit Switched Data (HSCSD). HSCSD is a feature that introduce General Bearer Services and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. Multislot also defines a flexible use of air interface resources which makes efficient and flexible use of higher user rates feasible.
+
+The Multislot mechanism is only applicable to GERAN.
+
+At UTRAN radio access parameters used for GBS user data are specified at TS 23.107.
+
+# --- 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 TS 22.002: "Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
+- [3] 3GPP TS 22.004: "General on supplementary services".
+- [4] 3GPP TS 405.002: " Multiplexing and multiple access on the radio path".
+
+# --- 3 Abbreviations and definitions
+
+## 3.1 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                   |
+|-------|---------------------------------------------------|
+| AIUR  | Air Interface User Rate                           |
+| EDGE  | Enhanced Data rates for GSM Evolution             |
+| FNUR  | Fixed Network User Rate                           |
+| GBS   | General Bearer Services                           |
+| GERAN | GSM/EDGE radio access network                     |
+| HSCSD | High Speed Circuit Switched Data                  |
+| MO    | Mobile Originated                                 |
+| MT    | Mobile Terminated                                 |
+| NT    | Non Transparent                                   |
+| T     | Transparent                                       |
+| UE    | User Equipment (same as MS in GSM specifications) |
+
+Additional abbreviations can be found in TS 22.905 [1].
+
+## 3.2 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Fixed Network User Rate:** user rate between IWF and the fixed network.
+
+**Air Interface User Rate:** user rate between Mobile Termination and IWF. For T services it is the maximum possible AIUR not including padding. For NT services it is the maximum possible AIUR.
+
+**maximum possible GERAN AIUR:** highest possible GERAN AIUR that the multiple TCH/F can provide, e.g. 2 TCH/F using TCH/F9.6 provides a maximum possible AIUR of 19,2 kbit/s.
+
+**padding:** fill bits needed to adapt the maximum possible AIUR supported by a given number of TCH/F with a given channel coding to a FNUR that is lower than the maximum possible AIUR.
+
+# --- 4 Description
+
+## 4.1 General
+
+HSCSD is a feature that introduce General Bearer Services (GBS) and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. HSCSD also defines mechanisms for the use of air interface resources which makes efficient and flexible use of higher user rates feasible. The Multislot mechanism is only applicable to GERAN.
+
+## 4.2 Applicability
+
+GBS shall provide flexible ways of supporting GSM Phase 2, T and NT data services and new data services at the higher rates. Data compression shall be applicable to NT GBS. Supplementary Services applicable to the General Bearer Services are specified at TS 22.004, [3].
+
+## 4.3 General Bearer Services
+
+The General Bearer Services are defined in TS 22.002 [2].
+
+The General Bearer Services (GBS) consist of two Bearer Services, and they are as follows:
+
+- asynchronous;
+- synchronous.
+
+## 4.4 Parameters to be indicated and negotiated
+
+### 4.4.1 Call set-up
+
+The parameters to be indicated, and negotiated, if applicable, during the call set-up shall include:
+
+- FNUR;
+- GERAN Channel coding(s) acceptable (for the call);
+- maximum number of GERAN TCH/F (that the mobile user can accept);
+- wanted AIUR (desired rate that the mobile user wants the network to allocate). The wanted AIUR is applicable to NT services only;
+- indication if the user initiated modification is required, and if so, the network resource needs;
+- channel coding asymmetry indication.
+
+Some of the parameters are only utilised by GERAN. When UTRAN radio access bearer is allocated the values are ignored.
+
+The GERAN channel coding(s) acceptable shall be indicated by the mobile at call set-up and is not negotiable. It indicates the GERAN channel coding(s) that may be chosen by the network for the call.
+
+The maximum number of GERAN TCH/F shall be indicated at call set-up. It enables the mobile user to limit the number of GERAN TCH/F used and thus to control an essential parameter for charging. It sets the upper limit of number of TCH/F that the network may allocate to the mobile.
+
+The wanted AIUR (applicable to NT services only) indicates the AIUR that the mobile user wants and which the network shall try to reach but which it is not allowed to exceed. The exception where the network is allowed to exceed the wanted AIUR is when the network can achieve the GERAN AIUR with a lower number of TCH/F, e.g. wanted
+
+GERAN AIUR indicated by the mobile is 14,4 kbit/s, GERAN channel codings acceptable are both TCH/F9.6 and TCH/F4.8 and maximum number of TCH/F are 3, then the network shall choose 2 x 9,6 over 3 x 4,8 if a channel coding of TCH/F9.6 is available on two TCH/F.
+
+If the user wishes to make use of the user initiated modification procedure, this shall be indicated at the call set-up.
+
+It shall be possible to reserve a different FNUR than the AIUR.
+
+Channel coding asymmetry indication is only applicable to NT calls where the user has indicated acceptance for channel coding(s) based on enhanced modulation. In this case the user may indicate preference for channel coding symmetry, downlink biased channel coding asymmetry, or uplink biased channel coding asymmetry. The channel coding asymmetry indication is only applicable in direction UE to network.
+
+#### 4.4.1.1 T services
+
+The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is not allowed.
+
+The AIUR is always equal to the FNUR.
+
+Fax Group 3 can make use of HSCSD.
+
+The GERAN channel coding selected must be one of the channel coding(s) indicated in the channel coding(s) acceptable parameter, the number of TCH/F selected shall not exceed the maximum number of TCH/F parameter, and the combination of the two shall result in an AIUR that is equal to the FNUR.
+
+#### 4.4.1.2 NT services
+
+The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is allowed.
+
+The wanted AIUR is indicated by the mobile at call set-up.
+
+### 4.4.2 Network initiated modification
+
+#### 4.4.2.1 T services
+
+For transparent calls the radio resource parameters must remain within limits that allow the transparent call to maintain its characteristics of fixed end to end throughput and delay. This means that in GERAN the channel coding and the number of TCH/F used may change during the call as long as a channel coding indicated in the channel coding(s) acceptable parameter is used, the maximum number of TCH/F is not exceeded and the AIUR is kept constant.
+
+#### 4.4.2.2 NT services
+
+For NT calls the network may modify the number of TCH/F and the channel coding used at GERAN and thus also the AIUR during the call as long as the maximum number of TCH/F, and the channel coding(s) acceptable are all respected. The network shall try to reach the wanted GERAN AIUR indicated, as long as the resource situation allows it.
+
+### 4.4.3 User initiated modification
+
+The in-call modification feature shall be supported in case of alternate services.
+
+#### 4.4.3.1 T services
+
+The user initiated modification is not applicable to T services.
+
+#### 4.4.3.2 NT services
+
+The user may indicate a change of the parameters maximum number of GERAN TCH/F, wanted AIUR, and channel coding asymmetry. No other parameters may be modified.
+
+The user initiated modification is only applicable to the data phase of alternate services.
+
+## 4.5 Air Interface Resource Allocation
+
+### 4.5.1 Minimum GERAN Air Interface Resource Allocation and Allocation Increment
+
+Air interface resources shall be allocated to HSCSD calls at TCH/F increments. The minimum air interface resource allocation for HSCSD calls shall be one TCH/F.
+
+### 4.5.2 Flexible Air Interface Resource Allocation
+
+Flexible air interface resource allocation enables:
+
+- the network to allocate dynamically resources related to the air interface usage according to the network operator's strategy, within the limits negotiated at the call set-up or during a user initiated modification.
+
+## 4.6 Symmetric and asymmetric connections
+
+### 4.6.1 Symmetric connections
+
+For symmetric connections, air interface resources are allocated symmetrically.
+
+### 4.6.2 Asymmetric connections
+
+There are two types of asymmetry, asymmetric air interface connection and channel coding asymmetry. Asymmetric air interface connection implies that more time slots are used in the downlink than in the uplink at GERAN. Channel coding asymmetry implies that one channel coding is used in the uplink and another channel coding is used in the downlink at GERAN.
+
+#### 4.6.2.1 Asymmetric air interface connection
+
+The provision of the asymmetric air interface connections allows simple ME (of Type 1, Reference TS 405.002, [4]) to receive at higher AIUR than otherwise would be possible with a symmetric connection.
+
+Asymmetric air interface connections that are a subset of the symmetric HSCSD, and support different user rates at uplink and downlink, shall be provided.
+
+Asymmetric air interface connections are only applicable to the downlink-biased asymmetry, i.e., where the ME is receiving at a higher rate than it is transmitting.
+
+Asymmetric air interface connections shall only be applicable to NT GBS.
+
+#### 4.6.2.2 Channel coding asymmetry
+
+Channel coding asymmetry may be set up by the network in three cases:
+
+- if the UE only supports enhanced modulation in the downlink;
+- if the UE supports enhanced modulation in both links, but the user indicates preference for uplink or downlink biased channel coding asymmetry;
+- if the UE supports enhanced modulation in both links, and the user indicates preference for channel coding symmetry, but the link conditions justifies different channel codings in up- and downlink.
+
+In the case when preference of uplink or downlink biased channel coding asymmetry is indicated by the user, and a asymmetric channel coding connection is set up based on this indication, the network shall always assign a TCH/F14.4 channel at GERAN on the unbiased link.
+
+Channel coding asymmetry shall only be applicable to NT services applying the GERAN channel codings TCH/F14.4, TCH/F28.8 and TCH/F43.2.
+
+In case a symmetric channel coding connection is set up, the link adaptation mechanism may change a symmetric channel coding connection to an asymmetric channel coding connection.
+
+### 4.6.3 Network choice of connection symmetry
+
+When the network has a choice of allocating either a symmetric or an asymmetric air interface connection it shall proceed as follows:
+
+- in the case where the wanted AIUR is smaller than or equal to the AIUR supported symmetrically by the ME, or asymmetric air interface connection is not supported by the network, then a symmetric air interface connection is established;
+- in the case where the wanted AIUR exceeds the AIUR supported symmetrically by the ME, the network shall assign the maximum AIUR supported by the ME in the down-link at GERAN, upper-bounded by the maximum number of TCH/F indicated by the mobile user, and the number of TCH/F supported by the network, maintaining the minimum of one TCH/F.
+
+## 4.7 User Equipment/Mobile Equipment requirements
+
+The general UE capabilities is applicable to HSCSD.
+
+A ME that supports multislot mechanism shall support one or more of the GERAN channel types TCH/F at or above 4,8 kbit/s.
+
+Given that the ME supports a certain GERAN channel coding, the network shall be able to assume that the ME can support this channel coding in any multislot configuration allowed by its multislot class (Reference TS 45.002, [4]).
+
+## 4.8 Mobility Management
+
+HSCSD shall be provided for within the existing supported Mobility Management.
+
+## 4.9 Roaming
+
+Roaming shall be possible.
+
+## 4.10 Quality of Service
+
+### 4.10.1 Bit error rate
+
+#### 4.10.1.1 GERAN TCH/F Bit Error Rate
+
+The bit error rate performance of each TCH/F of a multiple TCH/F HSCSD call shall be the same as that of a single TCH/F data call for the same channel coding.
+
+#### 4.10.1.2 Overall GBS Bit Error Rate
+
+Any increase in the bit error rate caused by the splitting and combining of multiple GERAN TCH/F shall be kept to a minimum.
+
+### 4.10.2 GERAN Radio resource management
+
+The multislot mechanism shall be provided for within the existing Radio Resource management control functions, including the relevant handover types. The handover shall be simultaneous for all air interface timeslots making up the call.
+
+The multislot mechanism shall be provided with full mobility.
+
+### 4.10.3 Call set-up delay
+
+Any increase in call set-up delay of the GBS calls compared to GSM Phase 2 data services shall be kept to a minimum.
+
+### 4.10.4 End-to-end delay
+
+Any increase in end-to-end delay of the GBS calls compared to GSM Phase 2 data services shall be kept to a minimum.
+
+### 4.10.5 Throughput
+
+The throughput for GBS T calls shall remain constant for the duration of the call except for the interruption of transmission at handover.
+
+### 4.10.6 Network planning and interference levels
+
+The impact of multislot mechanism on network planning and interference levels shall be kept to a minimum.
+
+## 4.11 Mapping of FNUR to GERAN TCH/F for T services
+
+For some FNUR padding is required to adapt the maximum possible AIUR to the FNUR.
+
+## 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services
+
+The following table indicates the mapping of AIUR to the number of TCH/F for NT services.
+
+**Table 1: Mapping of AIUR to TCH/F for NT services**
+
+| AIUR        | TCH/F4.8        | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F43.2 |
+|-------------|-----------------|----------|-----------|-----------|-----------|
+| 4,8 kbit/s  | 1               | N/A      | N/A       | N/A       | N/A       |
+| 9,6 kbit/s  | 2               | 1        | N/A       | N/A       | N/A       |
+| 14,4 kbit/s | 3               | N/A      | 1         | N/A       | N/A       |
+| 19,2 kbit/s | 4               | 2        | N/A       | N/A       | N/A       |
+| 28,8 kbit/s | N/A             | 3        | 2         | 1         | N/A       |
+| 38,4 kbit/s | N/A             | 4        | N/A       | N/A       | N/A       |
+| 43,2 kbit/s | N/A             | N/A      | 3         | N/A       | 1         |
+| 57,6 kbit/s | N/A             | N/A      | 4         | 2         | N/A       |
+| N/A         | Not applicable. |          |           |           |           |
+
+For Fixed Network User Rates (FRUR) see TS 22.002 [2].
+
+NOTE: GERAN TCH/F28.8 and GERAN TCH/F43.2 require EDGE capability.
+
+## 4.13 GBS MMI aspects
+
+It shall be possible to configure the parameters negotiated and indicated at GBS call set-up and during user initiated modification.
+
+## 4.14 GBS Subscription aspects
+
+HSCSD is not subscribed to. Users wanting to use multislot mechanism must subscribe to the General Bearer Services.
+
+## 4.15 GBS charging aspects
+
+To allow accurate charging of multislot calls, a record of start and stop timestamps versus the number of TCH/F, for each change in TCH/F allocation, shall be provided.
+
+NOTE: For MO multislot calls, the A party is liable for the use of all the TCH/F in her PLMN.
+
+For MT multislot calls, the B party may have to pay for one or more of the TCH/F in her PLMN.
+
+In case the originating or terminating subscriber is a fixed network subscriber, there should be no additional charge (in respect of the changing allocation of GERAN TCH/F) for the originating or terminating fixed network subscriber.
+
+## 4.16 O and M aspects
+
+For GBS call, there are several new and modified parameters compared to GSM Phase 2 data calls.
+
+For GBS, the air interface resource allocation may change several times during the call (network initiated and user initiated changes). It shall be possible to limit the frequency of changes per call, separately for network initiated and user initiated changes.
+
+Multislot calls can occupy multiple TCH/F. It shall dynamically be possible to limit the maximum number of GERAN TCH/F allowed for GBS calls per cell.
+
+## 4.17 Multislot security aspects
+
+Authentication and ciphering are applicable to multislot calls with no or minimal reduction in the security of the air interface.
+
+# --- 5 Exceptional procedures or unsuccessful outcome
+
+When a GBS call is offered to an entity (either ME or network) unable to support the offered GBS call, it shall be possible, within the limitations of the service, to revert the call:
+
+- to an GBS call the entity can support; or
+- at GERAN to a GSM Phase 2 data service.
+
+# --- 6 Interworking requirements
+
+## 6.1 Service interworking
+
+### 6.1.1 Interworking with supplementary services
+
+Supplementary Services that are applicable to the General Bearer Services can be used (Reference TS 22.004, [3]).
+
+### 6.1.2 Interworking with other services
+
+The simultaneous use of multislot mechanism and SMS MO/PP, and multislot mechanism and SMS MT/PP services shall be possible.
+
+## 6.2 Network interworking
+
+Interworking should be possible to all networks which are covered by GSM Phase 2 bearer services:
+
+- PSTN;
+- ISDN.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                |        |        |           |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|----------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                | Old    | New    | Work Item |
+| SP-04          |           |           | 02.34  |     |     |       |     | Transferred to 3GPP SA1 at ETSI SMG#29                         | 8.1.0  | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99615  | 22.034 | 001 |     | R99   | D   | Editorial changes for alignment                                | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99448  | S1-99706  | 22.034 | 002 |     | R99   | B   | Channel coding asymmetry for ECSD                              | 3.0.0  | 3.1.0  |           |
+| SP-07          | SP-000057 | S1-000052 | 22.034 | 003 |     | R99   | C   | CR on HSCSD changes for 3GPP                                   | 3.1.0  | 3.2.0  |           |
+| April 2000     |           |           |        |     |     |       |     | Editorial correction to title (Release 1999, not Release 2000) | 3.2.0  | 3.2.1  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.004 |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                  | 3.2.1  | 4.0.0  |           |
+| SP-16          | SP-020239 | S1-020890 | 22.034 | 004 |     | Rel-4 | F   | CR to 22.034 Correction of terminology and references          | 4.0.0  | 4.1.0  | Correct   |
+| SP-16          | SP-020267 | S1-021043 | 22.034 |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                     | 4.1.0  | 5.0.0  |           |
+| SP-26          | SP-040744 | S1-040997 | 22.034 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                    | 5.0.0  | 6.0.0  |           |
+| SP-36          |           |           | 22.034 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                    | 6.0.0  | 7.0.0  |           |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                    | 7.0.0  | 8.0.0  |           |
+| SP-46          | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-9 by MCC                                        | 7.0.0  | 9.0.0  |           |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                 | 9.0.0  | 10.0.0 |           |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                 | 10.0.0 | 11.0.0 |           |

marked/Rel-11/22_series/22042/raw.md

@@ -0,0 +1,144 @@
+
+
+
+
+
+
+# Contents
+
+- Foreword .....4
+- 1 Scope.....5
+- 2 References.....5
+- 3 Definitions and abbreviations .....5
+- 4 Description.....6
+- 5 Applicability.....6
+- 6 Normal procedure .....7
+  - 6.1 Transfer of NITZ information .....7
+  - 6.2 Use of NITZ information .....7
+- Annex A (informative): Change history.....8
+
+# --- 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 feature Network Identity and Timezone (NITZ).
+
+This feature provides the means for serving PLMNs to transfer current identity, time, Daylight Saving Time and the local timezone to Mobile Stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the Mobile Equipment (ME) or have changed their name since the ME was sold. Additionally time, Daylight Saving Time and timezone information can be utilised by MEs as desired.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. 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 TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3".
+
+[3] 3GPP TS 23.038: "Alphabets and Languages".
+
+# --- 3 Definitions and abbreviations
+
+In addition to the following definitions, abbreviations used in the present document are listed in 3GPP TR 21.905 [1].
+
+|      |                                                                                                                |
+|------|----------------------------------------------------------------------------------------------------------------|
+| NITZ | The feature Network Identity and Timezone as described in the present document.                                |
+| UCS2 | Universal Character Set 2                                                                                      |
+| UT   | Universal Time                                                                                                 |
+| LTZ  | Local Time Zone, the offset from UT applying in that locality, including any adjustments for summer time, etc. |
+| DST  | Daylight Saving Time. Adjustment for summer time.                                                              |
+
+# --- 4 Description
+
+The feature Network Identities and Timezone shall make it possible for a serving PLMN to transfer its current identity, universal time, DST and LTZ to MSs, and for the MS to store and use this information. Each one of these elements is optional. The feature significantly enhances roaming as it enables the accurate indication of network identities that are either newer than the ME or have changed their name since the ME was manufactured or sold. Additionally time and timezone information can be utilised by MEs as desired.
+
+When using the default character set (see 3GPP TS 23.038 [3]), the serving PLMN shall make both a "short" and a "long" name available to the MS. As an alternative or, in addition, to the default character set, the serving PLMN can make a name available in UCS2. The MS shall be free to choose one of these names depending upon its own characteristics and/or limitations, such as those of its display.
+
+NOTE: Guidance is sought, particularly from non-European operators, as to whether long and short name is required in UCS2 format.
+
+The Network Operator may change the network identity at any time. However the change of network identity need not force immediate transfer of information to the MS.
+
+As a network option, it shall be possible to send universal time (UT) by the network. Time information shall include: Year, Month, Day, Hour, Minute, Second, Timezone and DST. The expected accuracy of the time information is in the order of minutes.
+
+NOTE: Universal time indicates the time at which this information element (see 3GPP TS 24.008 [2]) may have been sent by the network. Thus it can be assumed that the accuracy of the time information when it arrives at the MS is usually within a couple minutes.
+
+The serving PLMN shall make Local Time Zone (LTZ) available to the MS as an offset from Universal Time in units of 15 minutes.
+
+When the LTZ is compensated for DST (summertime), the serving PLMN shall provide a DST parameter to indicate this. The adjustment for DST can be +1h or +2h.
+
+For PLMNs which cover more than one timezone, it is assumed that the Network Operator will arrange for boundaries between subsets of the PLMN service area to be approximately aligned with timezone boundaries. When an MS changes Local Time Zone the PLMN is not required to immediately transfer new time zone information. Similarly the PLMN will transfer the LTZ changes arising from summer/winter adjustments when convenient to the network operator.
+
+The MS will implement the new time zone information at an appropriate time following receipt.
+
+The information passed to MSs supporting the NITZ feature is controlled by the serving PLMN Operator through administrative interaction. The interface necessary to support this administrative interaction is outside the scope of the present document.
+
+# --- 5 Applicability
+
+Network Identity and Timezone is both an optional network feature and an optional MS feature.
+
+The NITZ feature is not intended to replace the existing method of PLMN Indication, nor is it intended to discharge the administration and maintenance of the associated MoU Permanent Document, SE13.
+
+# --- 6 Normal procedure
+
+## 6.1 Transfer of NITZ information
+
+Network name, time, DST and timezone information can be transferred from the serving PLMN to the MS:
+
+- 1) Upon registering on the network.
+- 2) When the MS geographically relocates to a different Local Time Zone.
+- 3) When the network changes its Local Time Zone, e.g. between summer and winter time.
+- 4) When the network changes its identity.
+- 5) At any time during a signalling connection with mobile station.
+
+Transfer of relevant information shall not unduly consume scarce network resources.
+
+## 6.2 Use of NITZ information
+
+Relevant information shall be presented to the MS user at the earliest opportunity.
+
+It is expected that the MS will display the most up to date information transferred to it.
+
+Switching off the MS should not cause the updated name of the network(s) to be deleted.
+
+Removal of the SIM/USIM should not cause the updated name of the network(s) to be deleted.
+
+However, the number of different network identities retained in the ME is a manufacturer issue.
+
+Usage of time information in MS is a ME manufacturer issue. For example, time information can be utilised to time stamp transactions for logging purposes.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |           |     |     |       |     |                                                                |        |        |           |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|----------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                                                | Old    | New    | Work Item |
+| June 1999      |           |           | GSM 02.42 |     |     |       |     | Transferred to 3GPP SA1                                        | 8.0.0  |        |           |
+| SA#04          |           |           | 22.042    |     |     |       |     |                                                                |        | 3.0.0  |           |
+| SA#05          |           |           | 22.042    | 001 |     |       |     | Editorial update of references for GSM/3GPP use.               | 3.0.0  | 3.0.1  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.042    |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                  | 3.0.1  | 4.0.0  |           |
+| SP-15          | SP-020045 | S1-020457 | 22.042    | 003 | -   | Rel-4 | F   | Editorial CR to correct terms and references                   | 4.0.0  | 4.1.0  | TEI       |
+| SP-16          | SP-020267 | S1-021043 | 22.042    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                     | 4.1.0  | 5.0.0  |           |
+| SP-20          | SP-030241 | S1-030378 | 22.042    | 005 | -   | Rel-5 | A   | Alignment of TS 22.042 (NITZ) with implementation in TS 24.008 | 5.0.0  | 5.1.0  | TEI5      |
+| SP-26          | SP-040744 | S1-040997 | 22.042    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                    | 5.1.0  | 6.0.0  |           |
+| SP-36          |           |           | 22.042    |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                    | 6.0.0  | 7.0.0  |           |
+| SP-42          | -         | -         |           |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                    | 7.0.0  | 8.0.0  |           |
+| SP-46          | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-9 by MCC                                        | 8.0.0  | 9.0.0  |           |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                 | 9.0.0  | 10.0.0 |           |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                 | 10.0.0 | 11.0.0 |           |

marked/Rel-11/22_series/22057/raw.md

@@ -0,0 +1,687 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                |           |
+|--------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                 | 4         |
+| 1 Scope.....                                                                   | 5         |
+| 2 References.....                                                              | 5         |
+| 3 Definitions and abbreviations .....                                          | 6         |
+| 3.1 Definitions.....                                                           | 6         |
+| 3.2 Abbreviations .....                                                        | 6         |
+| 4 Description.....                                                             | 7         |
+| 5 Compatibility of MExE UE's and applications .....                            | 7         |
+| 5.1 MExE classmarks.....                                                       | 7         |
+| 5.2 UE MExE classmarks.....                                                    | 7         |
+| 5.3 MExE executables and MExE classmarks.....                                  | 8         |
+| 6 General MExE requirements.....                                               | 8         |
+| 6.1 High level MExE requirements.....                                          | 8         |
+| 6.2 Requirements description from the user's standpoint.....                   | 10        |
+| 6.2.1 User interface configuration management.....                             | 10        |
+| 6.2.2 Service management.....                                                  | 10        |
+| 6.3 Requirements description from the MExE service provider's standpoint ..... | 11        |
+| 6.3.1 Transfer of applications, applets and content.....                       | 11        |
+| 6.3.2 Node types .....                                                         | 11        |
+| 6.3.3 Subscriber data .....                                                    | 11        |
+| 6.3.4 Roaming subscribers .....                                                | 12        |
+| 7 MExE bearer requirements .....                                               | 12        |
+| 8 MExE protocols requirements .....                                            | 12        |
+| 8.1 Optimised Wireless Access.....                                             | 12        |
+| 8.2 Wireless network independence.....                                         | 13        |
+| 8.3 Scaleable and extendible protocols .....                                   | 13        |
+| 8.4 Service independence.....                                                  | 13        |
+| 8.5 Network node type independence .....                                       | 13        |
+| 8.6 Enquiry and notification of MExE capabilities.....                         | 13        |
+| 8.7 UE request of services information.....                                    | 14        |
+| 8.8 Support of transfer protocols.....                                         | 14        |
+| 9 UE application execution environment requirements.....                       | 14        |
+| 9.1 UE platform independence.....                                              | 14        |
+| 9.2 Document mark-up language and other coding formats .....                   | 14        |
+| 9.3 MExE APIs .....                                                            | 14        |
+| 10 Charging requirements.....                                                  | 15        |
+| 11 Security requirements .....                                                 | 15        |
+| 11.1 Security Principles.....                                                  | 16        |
+| 11.2 Security Requirements .....                                               | 16        |
+| 11.3 Security domain classifications.....                                      | 17        |
+| 12 Interworking with other network features.....                               | 17        |
+| 13 Network interworking.....                                                   | 17        |
+| <b>Annex A (informative): Example MExE services .....</b>                      | <b>18</b> |
+| Annex B (informative): Change history.....                                     | 22        |
+
+# --- 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 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
+
+This TS defines the stage one description of the Mobile Execution Environment (MExE). Stage one is an overall service description, primarily from the subscriber's and service providers' points of view, and does not deal with the details of the human interface itself.
+
+This 3GPP TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This 3GPP TS contains the core requirements for a Mobile Execution Environment (MExE) which are sufficient to provide a complete service.
+
+It is highly desirable however, that technical solutions for a Mobile Execution Environment (MExE) should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this 3GPP TS may implement requirements which are considered outside the scope of this 3GPP TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+![Diagram illustrating the scope of the 3GPP TS. A cloud labeled 'MExE Service Environment' is shown. Below it, a box labeled 'UE' contains a smaller box labeled 'MExE'. Two arrows labeled 'Scope of this TS' point from the text 'Scope of this TS' to the 'MExE' box and the 'UE' box.](d980a3f9608055996a07f31788baf827_img.jpg)
+
+The diagram shows a cloud at the top labeled "MExE Service Environment". Below it is a rectangular box labeled "UE" (User Equipment). Inside the "UE" box, at the bottom, is a smaller rectangular box labeled "MExE". To the right of the "UE" box is the text "Scope of this TS". Two arrows originate from this text: one arrow points to the "MExE" box inside the "UE" box, and the other arrow points to the "UE" box itself. This indicates that the scope of the specification covers both the MExE functionality within the UE and the interaction between the UE and the MExE Service Environment.
+
+Diagram illustrating the scope of the 3GPP TS. A cloud labeled 'MExE Service Environment' is shown. Below it, a box labeled 'UE' contains a smaller box labeled 'MExE'. Two arrows labeled 'Scope of this TS' point from the text 'Scope of this TS' to the 'MExE' box and the 'UE' box.
+
+**Figure 1: Scope of this 3GPP TS**
+
+As indicated in Figure 1, the scope of this 3GPP TS encompasses the MExE functionality in the UE, interaction with the MExE service environment. The MExE service environment is not necessarily restricted to the PLMN, and nodes providing MExE services (i.e. MExE servers) may also exist outside the PLMN. Aspects of the support provided by MExE servers within the MExE service environment (such as charging aspects, security level classification etc.) are covered by this specification, but not the MExE servers themselves.
+
+# --- 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".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this 3GPP TS the following definitions apply:
+
+**applet:** a small programme that is intended not to be run on its own, but rather to be embedded inside another application
+
+**application:** MExE information in the form of software, scripts, applications, associated resources (e.g. libraries) and/or data
+
+**content:** data and/or information associated with, or independent of, a particular application which may be presented to or collected from a user
+
+**MExE Classmark:** a MExE Classmark identifies a category of MExE UE supporting MExE functionality with a minimum level of processing, memory, display and interactive capabilities. Several MExE Classmarks may be defined to differentiate between the functionalities offered by different MExE UE's. A MExE executable defined as being of a specific MExE Classmark indicates that it is supportable by a MExE UE of that Classmark.
+
+**MExE server:** a node supporting MExE services in the MExE service environment
+
+**MExE service:** a service enhanced (or made possible) by MExE technology
+
+**MExE service environment:** Depending on the configuration of the PLMN, the operator may be able to offer support to MExE services in various ways. Examples of possible sources are from traditional 3GPP network nodes, IN nodes, operator-specific nodes, operator-franchised nodes and services provider nodes, together with access to nodes external (i.e. vendor-specific) to the PLMN depending on the nature of the MExE service. These nodes are considered to constitute the MExE service environment. The MExE service environment shall support direct MExE UE to MExE UE interaction of MExE services.
+
+**MExE service provider:** an organisation which delivers MExE services to the subscriber. This is normally the PLMN operator, but could be an organisation with MExE responsibility (which may have been delegated by the PLMN operator).
+
+**MExE subscriber:** the owner of a subscription who has entered into an agreement with a MExE service provider for MExE services. Access to MExE services through other types of networks is out of scope of this specification.
+
+**subscriber:** the term subscriber in the context of this 3GPP TS refers to a MExE subscriber
+
+**user:** the user of an MExE UE , who may or may not be the subscriber.
+
+## 3.2 Abbreviations
+
+For the purposes of this 3GPP TS the following abbreviations apply:
+
+|      |                                   |
+|------|-----------------------------------|
+| API  | Application Programming Interface |
+| CS   | Circuit Switched                  |
+| FFS  | For Further Study                 |
+| IN   | Intelligent Network               |
+| ME   | Mobile Equipment                  |
+| MExE | Mobile Execution Environment      |
+| MMI  | Man Machine Interface             |
+| UENO | Network Operator                  |
+| PLMN | Public Land Mobile Network        |
+| SIM  | Subscriber Identity Module        |
+| UE   | User Equipment                    |
+
+|      |                                      |
+|------|--------------------------------------|
+| USIM | Universal Subscriber Identity Module |
+| SP   | Service Provider                     |
+
+Further related abbreviations are given in TR 21.905 [1].
+
+# --- 4 Description
+
+MExE provides a standardised execution environment in an UE, and an ability to negotiate its supported capabilities with a MExE service provider, allowing applications to be developed independently of any UE platform. The UE (consisting of the ME and SIM/USIM) can then be targeted at a range of implementations for MExE from small devices with low bandwidth, limited displays, low processor speeds, limited memory, MMI etc., to sophisticated with a complete MExE execution environment.
+
+The introduction of MExE execution environment into UE's is a significant step forward in their evolution. The ability of UE's to support MExE executables represents an extension of UE's capabilities. In order to allow current and future technologies to exploit and benefit from this, a standardised means of negotiating the UE's and network's capabilities is supported. This negotiation will permit the mutual exchange of capabilities between the UE and the MExE server, and possibly include the service profile of the user and capabilities of the network. The negotiation may take place at service initiation, or on a dynamic basis.
+
+A network can be a transport bearer for the negotiation, interaction and transferring of applications, applets and content with the UE, however it need not necessarily be the provider of the MExE services with which the UE's execution environment is interacting with. The network may also be the intermediary between two UE's which are engaged in a MExE service with each other, with the network effectively supplying the "pipe" and not playing a MExE role in the connection.
+
+Network nodes, nodes external to the network, or even UE's may be the entities which interact with the UE's execution environment.
+
+# --- 5 Compatibility of MExE UE's and applications
+
+## 5.1 MExE classmarks
+
+Given the wide ranging hardware capabilities of MExE UE's, together with the development of MExE executables, a MExE classification shall be supported to determine their respective capability and compatibility. The MExE classification shall apply both to UE's, and MExE executables.
+
+The objective is to:
+
+- classify the capabilities of a MExE UE to support MExE executables; and
+- identify the class of MExE UE on which a MExE executable may be supported.
+
+The concept of a MExE Classmark is introduced to manage the MExE UE and MExE executable classification and compatibility. The MExE Classmark is distinct and unrelated to the existing UE Classmark. The use of MExE Classmarks shall be supported during the capability negotiation between the MExE service provider and the MExE UE.
+
+## 5.2 UE MExE classmarks
+
+A given MExE Classmark shall identify a category of MExE UE supporting MExE functionality with a minimum level of processing, memory, display and interactive capabilities.
+
+Specification of different MExE Classmarks enables use of a variety of technologies to support MExE functionality.
+
+A given MExE Classmark identifies support by a MExE UE for a defined level of MExE functionality. This does not necessarily imply support of other MExE Classmarks. A MExE UE may support multiple MExE Classmarks.
+
+The minimum level of capabilities for each MExE Classmark is beyond the scope of this Stage 1 service description. As UE development evolves and more sophisticated devices (or indeed simpler devices) become available, further UE MExE Classmarks shall be definable to identify UE's capable of supporting improved (or additional) MExE functionality.
+
+A given MExE UE Classmark identifies support by a MExE UE for a defined level of MExE functionality, but does not necessarily imply support of other levels of MExE Classmark. A MExE UE may also support multiple MExE Classmarks.
+
+## 5.3 MExE executables and MExE classmarks
+
+MExE executables will be developed to execute in one or more classes of MExE UE's. In order for MExE executables to be properly supported by a MExE UE, the MExE executable shall identify the minimum functional capabilities required of a MExE UE, as defined by the UE's MExE Classmark.
+
+MExE executables shall be designated by the same classes of MExE UE's on which they may be executed. Examples of the classification of MExE executables are as follows:-
+
+- a MExE executable can be defined as a MExE Classmark 1 application;  
+the application is identified as suitable for execution on MExE Classmark 1 UE's only.
+- a MExE executable can be defined as a MExE Classmark 2 application;  
+the application is identified as suitable for execution on MExE Classmark 2 MS's only.
+- a MExE executable can be defined as a MExE Classmark 1 and Classmark 2 application;  
+the application is identified as suitable for execution on MExE Classmark 1 and Classmark 2 UE's only.
+
+The above example list is neither complete nor exhaustive.
+
+If a MExE executable is capable of being supported by other classes of MExE UE's (with reduced or enhanced capabilities), it is the responsibility of the MExE service provider to re-classify the MExE executable accordingly.
+
+MExE executables defined by a MExE service provider to a given class of MExE UE, shall be supportable by all MExE UE's of that class regardless of MExE UE manufacturer. MExE executables shall operate on differing MExE UE of the same MExE UE class without modification.
+
+It shall be possible for MExE service providers to make the same MExE executables available in the network for different classes of MExE UE. It is desirable that MExE executables are backward compatible within a given technology and for a given UE Classmark; however such backward compatibility is out of scope of this specification.
+
+# --- 6 General MExE requirements
+
+## 6.1 High level MExE requirements
+
+The high level requirements of MExE are as follows:
+
+- the means for MExE service provider specific services to be supported by all UE's of a particular class (i.e. the need for a common set of APIs and development tools), and accessible across a range of networks;
+- provide the user with a more sophisticated user interfaces (e.g. browser-like) with a rich variety of MMI concepts to control and invoke services (i.e. softkeys, icons, voice recognition etc.);
+- the user's and MExE service providers capability to control the "look and feel" of applications and applets;
+- the ability of the user to personalise the user interface;
+- the ability of the user to personalise services and individual media components of a multimedia service;
+- provide support of a wide variety of applications and applets;
+- provide the means for MExE service providers to authenticate MExE subscribers;
+- provide the user access to Internet and Intranet based applications and applets (via both standard Internet and Wireless optimised protocols);
+
+- the means to transfer applications, applets and content automatically or on demand to a MExE UE from a MExE service provider, and upgrade existing applications across the network;
+- the means to support direct MExE UE to MExE UE interaction of MExE services;
+- the need for an inherent security architecture such that both the MExE UE and MExE server sides of a connection are authenticated (possibly by a brokerage server), and have access to a range of encryption and security functions in order to maintain the security and integrity of the network. The MExE service provider shall maintain security of subscribers personal data and network data, with all aspects relating to network security being centred on the SIM/USIM;
+- the ability for the MExE service provider to charge subscribers for MExE service provider provided MExE services, at connect time, when downloading, or on usage;
+- the means for MExE service provider specific applications and applets on the MExE UE to communicate with applications in the MExE service environment using industry standard protocols (e.g. a MExE server etc);
+- the ability to provide information to MExE service providers (e.g. location information of UE for use with location dependent services);
+- the means for MExE service providers and their applications and applets to determine MExE UE capabilities (i.e. MExE Classmark, technology, supported bearers according to network capabilities and network subscription etc.). (This shall be used by MExE servers to adapt application and applet transfer to MExE UE capabilities, and shall be used by applications and applets whilst running to adapt their behaviour to the UE's capabilities.);
+- the opportunity for MExE service providers to apply expertise and software developed for other platforms;
+- provision of APIs and tools to develop MExE services which are applicable for MExE UE;
+- the means for the user to manage (i.e. identify version, delete, modify, save etc.) the applications, applets and content on the MExE UE;
+- the means for the user to control acceptance (i.e. by Security Level, level of trust etc.) of applications, applets and content transferred to the MExE UE. (It shall be possible for the user to finely control a trusted application or applet's access rights on the MExE UE, such as reading/writing/deletion of files stored on the MExE UE);
+- the means for MExE executables to perform some AT command functionality without compromise to security of MExE as defined in clause 8;
+- the means for authentication certificates associated with applications to be managed and stored in the SIM/USIM;
+- the ability for a MExE executable to negotiate the QoS, and the ability to indicate to a MExE executable changes in the QoS;
+- the ability of MExE executables to be notified that handover is about to occur, is occurring or has occurred;
+- the means for MExE UE manufacturers to download and upgrade their existing codec in a MExE UE. A generic mechanism to download other proprietary software into the execution environment of the UE shall be available to the manufacturer. The downloading of platform independent MExE executables, such as streaming audio, that support multimedia capabilities shall also be possible;
+- the means for data to be synchronised between the MExE UE and the MExE service environment;
+- the ability to support IP multimedia services;
+- the ability to discover services offered by the Home Environment, valued added service providers with associated with the Home Environment, and third parties.
+
+Some of the above requirements are subsequently elaborated.
+
+## 6.2 Requirements description from the user's standpoint
+
+MExE provides an improvement in the capabilities of a UE, as well as an extended range of services available to the user from, or via, the network. The user shall have
+
+- user interface configuration management; and
+- service management;
+
+of the services offered to him by MExE.
+
+### 6.2.1 User interface configuration management
+
+User interface configuration management refers to the behaviour of the MExE UE, and the ability of the user to modify the MExE UE to behave in the manner he is accustomed to, or wishes the MExE UE to, present itself to the user. It does not refer to the services which interact with the network, but the way in which the MExE UE interacts with the user.
+
+Users expect MExE UE's to offer an increasing range of capabilities which need not be ubiquitously present on each MExE UE, depending on the technological limitations of the MExE UE. The user shall be able to manage the user interface configuration of the MExE UE. For example, some user's may require a voice-controlled MMI, whilst others may have the need for a specialised presentation on the MExE UE display or preset function keys regardless of the application or applet which is running. Management of the user interface configuration will permit a user to move from MExE UE to MExE UE and exploit the technological capabilities of each class of MExE UE, with the use of varying services downloaded from the network, as required.
+
+The user shall be able to identify (either directly or indirectly) the user interface configuration he wishes to add, modify or delete on his MExE UE, and shall be offered the means of doing this. This management may be performed, for example, by a configuration capability profile.
+
+In taking this action, it shall be possible to determine whether the user interface configuration is already resident on the ME, or whether it requires to be obtained from the SIM/USIM or the network. The modifications which may be requested by the user could result in, for example, differing display characteristics being employed, redefinition of keys, modification of the "look and feel" of the user interface, touch screen facility, extensions to existing functions or the capability to automate some functions.
+
+The control of the "look and feel" of MExE executables to customise their level of functionality and appearance may be possible by the MExE service provider, network operator (where the MExE service provider is not the network operator) and the user. The aspects of the application or applet which may be customisable are determined by the MExE service provider as an integral part of the MExE executable.
+
+The user interface configuration management which is specific to the ME shall be stored on the ME, and user interface configuration management which is generic to ME's may be stored in the network or on the SIM/USIM.
+
+The definition of the user interface configuration management which may be offered to the user is outside the scope of this service description.
+
+### 6.2.2 Service management
+
+MExE shall provide the ability to customise the range of services offered to the subscriber. The subscriber's ability to configure the services available on the MExE UE shall be dynamic, as the range of services required may differ depending on the network, time and location that the user finds himself in. For example, a subscriber may require access to services offering financial support when attending a business meeting, however later in the day he may need access to travel information and booking facilities when re-arranging his travel home.
+
+MExE shall be able to support the handling of individual media components of an IP multimedia service in a user profile, and not necessarily handle all media components of a multimedia session in the same way.
+
+A common address across all PLMN supporting MExE shall be available, from which the user shall be able to request the range of MExE services available he is registered in, if the PLMN supports MExE. The downloading of services may be autonomously controlled by the MExE UE to update existing service access on the MExE UE, or to download new services. The management of these services may be defined by the subscriber directly or under the control of the MExE UE's capabilities organised on the MExE UE (i.e. a user may be particularly interested in unified messaging services, and require the availability of such services to be made available to him).
+
+The user shall be able to determine and manage which MExE executables and content may be transferred to the MExE UE (i.e. in terms of their security level, source of the applications etc.), determine and manage which MExE executables and content are currently resident and usable on the MExE UE (e.g. when roaming some services may not be available to the user), and delete MExE executables and content on the MExE UE.
+
+The definition of the applications, applets and content which may be offered to the user is outside the scope of this specification.
+
+## 6.3 Requirements description from the MExE service provider's standpoint
+
+### 6.3.1 Transfer of applications, applets and content
+
+A common mechanism shall be available to perform the transfer of applications, applets and content between MExE UE's and the MExE service provider.
+
+The common transfer mechanism shall permit applications, applets and content (according to the appropriate MExE Security Level) to be transferred to the MExE UE.
+
+It shall be possible for the MExE service provider to:
+
+- transfer applications, applets and content between the MExE UE and the MExE service provider (which may be initiated by either party);
+- request the version of applications, applets and content on the MExE UE;
+- identify the MExE UE' capabilities;
+- support a request from the MExE UE for information on the (local) services which may be transferred from the network.
+
+Some of these functions may be used by the MExE service provider either individually, or together to automatically update previously transferred services.
+
+### 6.3.2 Node types
+
+The introduction of MExE shall enable an expansion of services available to the user from various network node types.
+
+The MExE UE shall be able to communicate with the various network node types in the MExE service environment, allowing access to intelligent nodes to process service requests from the MExE UE.
+
+Applications in the MExE service environment may interact with, or execute as agents of, an MExE UE application using industry standard protocols. Such interaction does not fall within the scope of MExE, however any MExE UE application that does interact with applications in the MExE service environment must respect the privacy of user data.
+
+### 6.3.3 Subscriber data
+
+Subscription to MExE services shall be logically separate to subscription of network services. A subscriber may have a MExE subscription to multiple MExE service providers. It may also be possible for the subscriber to interrogate such subscription registration (with a suitable means of authorisation), depending on PLMN support.
+
+### 6.3.4 Roaming subscribers
+
+Roaming MExE subscribers shall be able, as far as possible, to access their normal MExE services in their HPLMN.
+
+As usual when roaming, it cannot be ensured that the VPLMN can provide the subscriber access to the same MExE services (e.g. applications, applets and content) as he is accustomed to. However, in the VPLMN additional MExE services may be available, depending on network capabilities. Service continuity when roaming is dependent on the availability of the services in the VPLMN, and is outside the scope of this specification.
+
+The operation of the transferred applications, applets and content may be location dependent, and their behaviour when in a different location is outside the scope of this specification.
+
+The following forms of MExE subscriber roaming are identified:-
+
+- roaming between networks (HPLMN to VPLMN);
+- roaming between visited networks (VPLMN to VPLMN);
+
+- regional roaming within a network (within the HPLMN or VPLMN).
+
+There may be a need to distinguish between the above types of roaming from a MExE services management perspective, as the operation of location dependent MExE services may be affected when the MExE subscriber roams beyond the boundaries of a PLMN or region.
+
+# --- 7 MExE bearer requirements
+
+Bearers available to MExE executables depend on those supported by the MExE UE that are available.
+
+Wherever available, MExE UE applications shall be supported by bearers from 3GPP system and other technologies (e.g. circuit switched, packet switched, high speed data links provided by digital broadcast infrastructure). MExE executables shall be able to use these bearers in an asymmetric fashion.
+
+# --- 8 MExE protocols requirements
+
+In order for MExE to be supported over the network, a set of standardised protocols is required to support interaction between the MExE UE and the MExE service environment.
+
+As this specification is not required to propose a specific technology, it identifies the MExE protocols requirements from the service subscriber's and user's standpoint. The MExE protocols refers to any protocol layer above the 3GPP system bearers, which interfaces between the MExE service environment and the MExE UE.
+
+The functional capabilities, information flows, signalling system protocols and switching functions needed to implement the service described in this Stage 1 specification will be identified by subsequent specifications at the Stage 2 and Stage 3 levels.
+
+The high level MExE protocols requirements are identified in the subsequent subclauses.
+
+## 8.1 Optimised Wireless Access
+
+A primary goal of MExE is to provide access to Internet and Intranet services, the standard Internet applications, security and transport protocols shall be one possible set of MExE protocols which is supported. It is noted that these protocols may not cover all the requirements identified in this specification for all classes of ME's.
+
+A set of application, security and transport protocols optimised for wireless access, and compliant to MExE requirements, shall be specified and form part of the MExE standards.
+
+MExE UE's shall be able to support either or both of these sets of protocols.
+
+## 8.2 Wireless network independence
+
+The upper layers of the MExE protocols shall be independent of the type of underlying wireless network so that applications and applets do not need to take into account the specific nature of networks. In particular, lower layers shall provide a generic access API to network bearers so that application and applet developers do not have to cater for the supported underlying bearers. It shall be possible for applications and applets to request specific bearer services and be notified accordingly if they are not available.
+
+The transport layer of the MExE protocols may however be adapted to support the specific features of the underlying bearers. The MExE protocols shall have the ability to use all the underlying bearer services which the MExE UE is capable of supporting.
+
+## 8.3 Scaleable and extendible protocols
+
+The MExE protocols shall support a scaleable and extendible environment for application and applet development in mobile communication devices. It shall provide a set of generic, non-UE or service-dependent, features. Saleability of the MExE protocols applies to both the MExE UE (e.g. where simple devices do not require the extensive protocols support possibly required by more sophisticated devices) and the network.
+
+The MExE protocols shall support both low bandwidth bearers (e.g. SUE, USSD etc.) as well as medium bandwidth bearers (e.g. anything up to 64kb/s). The introduction of new bearers shall be supported, allowing applications and applets to automatically benefit from their capabilities.
+
+The MExE protocols shall support existing servers and applications and applets, and provide a stable platform for future application development.
+
+## 8.4 Service independence
+
+The MExE protocols shall be independent of the services communicated over the protocols. The modification in the range of services, or addition of new services, offered over the network shall not be restricted by the MExE protocols.
+
+## 8.5 Network node type independence
+
+The MExE protocols shall be independent of the network node type(s) being communicated with over the protocols. The MExE protocols shall support the evolution of network node types in a PLMN.
+
+## 8.6 Enquiry and notification of MExE capabilities
+
+The MExE protocols shall support a generic technology-independent means for the notification by the MExE UE to a MExE server, or enquiry from the MExE server to the MExE UE, of the supported MExE capabilities consisting of:
+
+- MExE Classmark (mandatory, MExE server to MExE UE);  
+the supported class of MExE UE;
+- MExE technology (mandatory, MExE server to MExE UE);  
+the supported types of MExE UE technology to support MExE services;
+- terminal characteristics (optional, MExE UE from MExE server, following MExE server enquiry);  
+further details of the supportable characteristics (i.e. screen size, MMI capabilities, supportable bearer services, toolkits etc. as constrained by the network, terminal, subscription and user preferences).
+
+In existing networks it may not be possible to determine the network capabilities (i.e. supported bearers) and subscription options of the subscriber.
+
+The above notification by the MExE UE or the MExE server are supported at service initiation, dynamically during the provision of such a service, and following a change in the quality of service (i.e. following a handover, change of network, degradation of service, change in quality of service).
+
+The notification mechanism shall flexibly support notification of the MExE UE, and be able to accommodate future evolution of MExE UE equipment.
+
+## 8.7 UE request of services information
+
+The MExE protocols shall support a notification from the PLMN or a request from the MExE UE to the PLMN, for information on the (local) services which may be transferred from the PLMN. The information from the PLMN may take the form of listing the services, or references to a PLMN entity (either internal or external to the PLMN) where the available services may be determined.
+
+## 8.8 Support of transfer protocols
+
+The MExE protocols shall support the capability to transfer new applications and applets to the MExE UE as required. The protocols shall support both user initiated and MExE server initiated transfer of several types of data (content description pages, procedural logic, images, libraries etc.), and be able to indicate the type of data being transferred.
+
+Each specific MExE technology shall support a standardised transfer mechanism for that MExE technology.
+
+# --- 9 UE application execution environment requirements
+
+## 9.1 UE platform independence
+
+In order to support the objectives of MExE, the ME and SIM/USIM is required to have an architecture capable of supporting applications, applets and content in a standardised execution environment, independently of the MExE UE manufacturer.
+
+As this specification is not required to propose a specific technology, it identifies the common platform requirements from the service subscriber's and user's standpoint.
+
+The limitations of small devices may result in the provision of the full application execution environment only being available in sophisticated devices.
+
+The high level execution environment requirements are identified in the subsequent subclauses.
+
+## 9.2 Document mark-up language and other coding formats
+
+In order to cater for a wide variety of ME's with different display and input capabilities, support for both the standard Internet mark-up language and a content description language optimised for small display devices of low bandwidth bearers shall be defined with the MExE specifications. Both languages may be implemented on any MExE UE. Standardised ways of coding content (i.e. images, phonebook, calendar etc.) shall be defined, however the support of such standardised content coding is optional.
+
+In order to facilitate global use of MExE services, a standardised range of character sets for MExE services requires to be defined, and the capabilities of the user and applications to use them.
+
+## 9.3 MExE APIs
+
+MExE APIs may be defined covering aspects (e.g. Network APIs, Non-network API's, Terminal APIs etc.) within a given MExE Classmark of MExE UE (ME and/or SIM/USIM), and the MExE UE shall support a core API to support the execution of MExE executables. The core API is a the minimal set of API that is present on all MExE UE's, providing the MExE execution environment in which applications and applets can execute, and is known as the Core MExE API. The Core MExE API consists of generic and 3GPP specific aspects.
+
+Applications and applets which have been designed to execute in this Core MExE API environment (and the optional MExE APIs subsequently identified), will provide additional functions to the MExE UE.
+
+In addition to the Core MExE API on an MExE UE, standardised MExE API extensions such as Network API (e.g. access to session control services, SUE etc.), Non-network 3GPP-defined services API (e.g. security aspects, SIM/USIM phonebook etc.), Terminal API (e.g. power management, access to alerting function, phonebook, MMI, smartcard access etc.),shall be subsequently defined and may be supported by the MExE UE in order to further exploit the system capabilities.
+
+The standardised MExE API extensions shall include access to mobility information.
+
+# --- 10 Charging requirements
+
+The use of MExE services shall, at MExE service provider determination, be subject to charging.
+
+There are several forms of charging which shall be available to the MExE service provider. It shall be possible for the MExE service provider to charge in the following instances:
+
+- subscription;
+  - the subscriber's registration to use MExE services may be subject to a charge;
+- service transfer;
+  - the transfer of services and/or information to a subscriber's MExE UE may be subject to a charge;
+- service upgrading;
+
+the upgrading of previously transferred services to a subscriber's MExE UE may be subject to a charge (automated upgrading of services may be subject to a different charge);
+
+- service usage;
+
+the usage of transferred services by a subscriber's MExE UE may be subject to a charge (possibly use either internal to, or external to, the MExE UE);
+
+- roaming ;
+
+the usage of MExE services by a subscriber's MExE UE when roaming may be subject to additional charges;
+
+A standardised means of transferring (indicative and/or final) charging information (for the use of MExE services) from the MExE service provider to the MExE UE shall be defined.
+
+The usage of the bearer service may be subject to a charge (i.e. possibly time-based, volume-based, event-based etc.) by the network operator.
+
+Normal service charges may additionally apply when using MExE services and incurring the above charges.
+
+Other charging requirements may be identified in due course.
+
+# --- 11 Security requirements
+
+This clause consists of:
+
+- a sub-clause giving the principles behind security for MExE. These are not requirements as such but the principles behind the requirements;
+- a sub-clause specifying specific requirements that MExE implementations must adhere to;
+- a sub-clause specifying the security domain classifications for MExE executables.
+
+## 11.1 Security Principles
+
+The ME and the data therein are the property of the user. The user is also responsible for the payment of chargeable events involving her UE, and will be seen as the party responsible for any events (whether chargeable or not) involving her UE. Therefore the user shall have full control over all chargeable and non-chargeable events initiated by her UE ("event" includes responses made by the UE to external events, e.g. the acceptance by the UE of an incoming session). This control can be exercised either by the giving of explicit permission at the time of the event or by the giving of implicit permission to the events by the agreement to an event schedule listed clearly in a user profile.
+
+The user shall be able to request the logging of specific network events initiated by MExE UE applications/applets.
+
+The privacy of user data in the UE is of paramount importance.
+
+The SIM/USIM and operator controlled areas within the terminal are the property of the network operator. The network operator shall therefore have full control over access to the SIM/USIM and operator controlled area The operator shall also have full control over data, excluding personal user data, transmitted to or from the SIM/USIM and the operator controlled terminal area and all events initiated by the SIM/USIM or operator controlled area ("event" includes responses made to external events, e.g. the response to a command sent from the ME).
+
+As the user cannot know the capabilities of any MExE executables transferred from a MExE service environment before transfer, the UE MExE environment shall ensure that transferred MExE executables cannot compromise the above principles.
+
+## 11.2 Security Requirements
+
+For MExE executables of security operator, manufacturer and user trusted domains , as defined in clause 11.3, it shall be possible to authenticate the identity of the body that authorised the application, applet or content.
+
+There shall be a secure, unforgeable means for assigning the security domains defined in section 11.3 to the MExE executables transferable from the MExE service environment.
+
+The certification of authorisation associated with MExE executables transferable from the MExE service environment shall be transferred with the certified material.
+
+The MExE UE shall be able to verify the security domain, as defined in section 11.3, of MExE executables transferred from the MExE service environment.
+
+The verification process in the UE itself shall not compromise the security of the functionality and content in the UE
+
+Transferred material that fails verification shall not be installed and shall be deleted by the terminal as soon as possible.
+
+MExE executables that cannot be verified due to the absence of required verification information in the UE, shall be considered as untrusted material, as defined in section 11.3.
+
+The events that MExE executables are given permission by the user to initiate shall be securely recorded in the user profile.
+
+There shall be mechanisms within the MExE UE for ensuring that applications cannot have access to UE functionality and content beyond that allowed by their security domain, as defined in section 11.3.
+
+It shall be possible to for the user to downgrade MExE executables of operator, manufacturer or user trusted domain status to untrusted status, at installation or at any other time.
+
+The MExE UE shall be able to detect if MExE executables transferred from the MExE service environment have been modified since they were assigned a security level.
+
+MExE executables shall not be transferred to a MExE UE without the explicit permission of the UE user immediately prior to transfer or implicit permission via the user profile.
+
+Applications and applets transferred to a MExE UE shall not be able to initiate events without the explicit permission of the UE user immediately prior to event initiation or implicit permission via the user profile.
+
+The user profile data for transfer and event initiation cannot be changed without the explicit agreement of the user.
+
+The user shall be able to abort or suspend any on-going session that has been set up automatically by an application.
+
+The integrity of the SIM or USIM and other security mechanisms shall not be compromised by the introduction of MExE services.
+
+The user shall be able to request the logging of specific network events initiated by MExE UE applications/applets.
+
+MExE UE applications/applets shall not be able to send command RUN GSM ALGORITHM to the SIM.
+
+## 11.3 Security domain classifications
+
+The security domain of MExE executables shall be graded according to the measure of authorisation which they have been designated. The following 3 (the “sandbox” in which untrusted MExE executables runs is not considered to be a domain) domains shall be supported for MExE executables:
+
+- MExE Security Operator Domain (used by the HPLMN operator);
+
+MExE executables designated at this security domain have been authorised by the network operator (i.e. HPLMN),
+
+- MExE Security Manufacturer Domain (system MExE executables);
+
+MExE executables designated at this security domain have been authorised by the MExE UE manufacturer.
+
+- MExE Security User Trusted Domain (trusted applications, applets and content);
+
+MExE executables MExE executables designated at this security domain have been written by user trusted software developers and verified as user trusted domain material (but not with regard to their content) via organisations such as certification authorities.
+
+- MExE Security Untrusted (untrusted applications, applets and content);
+
+Untrusted MExE executables have not been supplied with an associated authorisation, or the authorisation cannot be verified due to the absence of required verification information in the MExE UE.
+
+# --- 12 Interworking with other network features
+
+All services available in the network shall continue to be offered in addition to MExE. This includes the basic services, supplementary services and network features.
+
+It shall be network-determined whether specific MExE services supplement, co-operate with, or supersede the network available services, when a user is subscribed to MExE and has transferred the specific MExE service.
+
+The interworking characteristics of individual MExE services with other network features is outside the scope of this specification.
+
+# --- 13 Network interworking
+
+All services offered in co-operation with other networks shall continue to be offered in combination with MExE. This includes the basic services, supplementary services and network features.
+
+The interworking characteristics of individual MExE services with other networks is outside the scope of this specification.
+
+# Annex A (informative): Example MExE services
+
+## Overview
+
+In addition to the use of standardised network services (e.g. call forwarding, call barring, CCBS, call diversion etc.), MExE provides additional capabilities to control telephony events and manipulate standardised network services in a user-friendly manner.
+
+A MExE handset provides the generic capability to negotiate and interact with services (in the form of applications and content) in servers, other handsets and internet/intranet WebPages etc. Further, MExE provides standardised execution environments to which 3<sup>rd</sup> party software developers may write services to execute directly in the MExE handsets.
+
+MExE provides the user with a more sophisticated user interfaces (e.g. browsers) with a rich variety of MMI concepts to personalise, control and invoke services (e.g.. softkeys, icons, voice recognition etc.). Additionally downloaded services provide users with the capability to control the “look and feel” of services.
+
+MExE also brings security to the support of 3<sup>rd</sup> party services in the wireless handset. With security domains reserved for network operators, handset manufacturers, and third parties , the source and content of downloaded services may be authenticated by the MExE client. The provision of such a security model enables the user to control whether services are installed, configure which functions may be performed by services, and to identify the extent of permissions granted to services. The protection of user data and resources help prevent attacks from potentially fraudulent services.
+
+This annex gives an overview of how new 3<sup>rd</sup> generation services may be supported by MExE handsets, and gives some examples of possible services that may be supported on them. The ability to support some services may depend on the physical handset resources available to the MExE services, the classmark of the MExE client, and handset manufacturers may provide a range of handsets aimed at supporting different types of services.
+
+## Access to MExE services
+
+There are several ways in which these new 3<sup>rd</sup> generation MExE services may be supported, and the following scenarios give an overview of the possible scenarios.
+
+- **services execute on remote servers**
+
+![Diagram illustrating the access to MExE services. A mobile phone labeled 'MExE Client' is connected via a red arrow to a cloud labeled 'Mobile Network'. Inside the cloud, there are two server icons labeled 'Network VAS and MExE Servers'. Another red arrow points from the cloud to a server icon labeled '3rd party VAS and MExE Servers'.](7b8b192e2853ef28d28eff0241ebe86b_img.jpg)
+
+The diagram shows a mobile phone on the left labeled 'MExE Client'. A red arrow points from the phone to a cloud labeled 'Mobile Network'. Inside the cloud, there are two server icons labeled 'Network VAS and MExE Servers'. Another red arrow points from the cloud to a server icon on the right labeled '3rd party VAS and MExE Servers'.
+
+Diagram illustrating the access to MExE services. A mobile phone labeled 'MExE Client' is connected via a red arrow to a cloud labeled 'Mobile Network'. Inside the cloud, there are two server icons labeled 'Network VAS and MExE Servers'. Another red arrow points from the cloud to a server icon labeled '3rd party VAS and MExE Servers'.
+
+The services are provisioned and execute on remote servers, WebPages etc., to which the MExE client establishes a connection. The MExE client uses the services as provided by those remote servers. The MExE client effectively receives content (i.e. secured personal financial information) from the remote application which is presented to the user in the MExE client.
+
+- **application downloaded into the MExE client**
+
+![Diagram illustrating the architecture for an application downloaded into the MExE client.](10781f43062bf3e9601a1e086710556c_img.jpg)
+
+The diagram shows a mobile handset labeled 'MExE Client' on the left. A red arrow points from the handset to a cloud labeled 'Mobile Network', which contains a server icon labeled 'Network VAS and MExE Servers'. Another red arrow points from the 'Network VAS and MExE Servers' to a server icon labeled '3rd party VAS and MExE Servers'. A large blue curved arrow originates from the '3rd party VAS and MExE Servers' and points back to the 'MExE Client', representing the download of an application.
+
+Diagram illustrating the architecture for an application downloaded into the MExE client.
+
+The services are provisioned and execute on remote servers, to which the MExE client establishes a connection. The MExE client downloads an application which acts as a local browser to interact with the remotely provided service. The user interacts with and uses the remote servers via the downloaded application. An example of such a service would be access to an internet/intranet page.
+
+- **service downloaded into the MExE handset**
+
+![Diagram illustrating the architecture for a service downloaded into the MExE handset.](12de9b926df0384ec07702671827c9cd_img.jpg)
+
+This diagram is identical to the one above, showing a mobile handset labeled 'MExE Client' on the left. A red arrow points from the handset to a cloud labeled 'Mobile Network', which contains a server icon labeled 'Network VAS and MExE Servers'. Another red arrow points from the 'Network VAS and MExE Servers' to a server icon labeled '3rd party VAS and MExE Servers'. A large blue curved arrow originates from the '3rd party VAS and MExE Servers' and points back to the 'MExE Client', representing the download of a service.
+
+Diagram illustrating the architecture for a service downloaded into the MExE handset.
+
+The services are available from remote servers, to which the MExE client establishes a connection. The MExE user downloads whichever services he desires from the remote servers, and installs, provisions and configures them on the MExE client. These services execute directly on the handset, without necessarily relying on servers to support the service. An example of such a service would be a game.
+
+- **MExE handset to MExE handset services**
+
+![Diagram illustrating MExE handset to MExE handset services. Two mobile handsets, labeled 'MExE Client', are shown on either side of a central cloud labeled 'Mobile Network'. A thick red arrow points from the left handset to the right handset, passing through the cloud, indicating a direct connection between the two clients.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+Diagram illustrating MExE handset to MExE handset services. Two mobile handsets, labeled 'MExE Client', are shown on either side of a central cloud labeled 'Mobile Network'. A thick red arrow points from the left handset to the right handset, passing through the cloud, indicating a direct connection between the two clients.
+
+MExE handsets may wish to establish connections with each other to provide, receive and use interactive services. This direct MExE client to MExE client interaction of MExE services and any combination of the preceding scenarios may have been used to download services to the MExE client. These services may execute directly on the handset, without necessarily relying on servers to support the service. An example of such a service would be interactive games, sharing of calendar information, etc..
+
+### Example MExE services
+
+Once they have been downloaded, these MExE services may then be configured, personalised and executed on the MExE handset by the user. A MExE handset may support a diverse range of services, providing a dynamic and evolutionary set of facilities to users. The support of this unlimited range of new services, will convert a mobile handset from being a device which simply makes and receives calls and messages, into a multifunctional leisure and business device.
+
+An analogy may be made with a personal computer, where the user can install and configure any type of application that he so chooses, establish multimedia call sessions, and convert the laptop into a multi-faceted device (e.g. slideshow presenter, video box, music jukebox, arcade games machine, protocol analyser, e-mail, messaging and information server etc.). In fact, MExE may simply be considered to be similar to a small computer supporting wireless telecommunications capabilities.
+
+Manufacturers are expected to produce MExE devices with different levels of resources, memory and processing power to exploit the growing number of applications and market niches.
+
+The list of possible services that may be supported by a MExE client is virtually unlimited, and the following are example services that could be supported by a MExE client.
+
+### Applications
+
+Applications may be downloaded and installed on the MExE client to provide a wide range of standalone services.
+
+The user downloads and installs the software into the MExE client, configuring and installing it as required. Examples of such applications are phonebooks, diaries, planners providing similar functionality to current popular handheld PDA devices. Likewise, games may also be downloaded and installed providing similar functionality to current popular handheld games devices and other entertainment and leisure services.
+
+Additionally, interactive working with other devices and servers (i.e. on-line gaming, gambling, messaging etc.) could also be generically supported.
+
+#### Browsers
+
+Applications may be downloaded and installed on the MExE client to support browser functionality already experienced by many users today with personal computers. Examples of this are internet and e-mail browsers.
+
+#### Web browsing
+
+A MExE client can be used by the user as an internet/intranet web browser by downloading and installing a web browser.
+
+Just like the internet browser on a personal computer at home or in the office, the user is able to access the internet/intranet. Similar to accessing the internet via a personal computer, the user is able to surf the web viewing pages, images, animation and download content using standard internet HTTP and HTML protocols. By interaction with the installed web browser, the user is also able to customise his web browser to present the internet/intranet to the user in his accustomed way.
+
+#### E-mail
+
+A user can convert his MExE client into an e-mail handler by downloading and installing an e-mail browser.
+
+Working the same way as an e-mail browser on his desk bound personal computer, the user is able to send and receive messages on the move. As with existing personal computer implementations e-mails with audio, visual and textual attachments may be exchanged with an e-mail server, using the standard e-mail SMTP, POP3 and IMAP4 protocols. Directly supported by the e-mail browser on the MExE client, the user may personalise his e-mail service and manage e-mails on remote e-mail servers.
+
+#### Players
+
+Players are a specialised type of application which the user may install on the MExE client. These players enable content to be presented to the user in a specific manner, depending on the content format. Audio and video players are examples of such specialised applications.
+
+#### Music players
+
+A MExE client may also be used by the user as a portable music player by downloading and installing a music player application.
+
+Once the music player application is installed, the user is then able to download music content using popular music formats available from the internet or third party servers.
+
+Similar to the player applications already available on the internet and personal computers today, the user may be able to play popular music formats like MP3. Further, specialised music content may also be played by downloading and installing the appropriate compliant player.
+
+By downloading and installing a music player, the user is able to obtain functionality from the MExE client similar to current popular handheld music devices.
+
+#### Video players
+
+Similar to the music player, a MExE client may also be used by the user as a portable video player by downloading and installing an appropriate video player application.
+
+Once the video player application is installed, the user is then able to download video content using popular music formats like MPEG4 available from the internet or third party servers.
+
+# Annex B (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                              |        |        |             |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|--------------------------------------------------------------|--------|--------|-------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                              | Old    | New    | Work Item   |
+| Jun 1999       |           |           | 22.057 |     |     | R99   |     | Transferred to 3GPP SA1                                      | 8.0.0  | 3.0.0  |             |
+| SP-05          | SP-99479  | S1-99619  | 22.057 | 001 |     | R99   | D   | Editorial changes for alignment                              | 3.0.0  | 3.0.1  |             |
+| SP-09          | SP-000381 | S1-000626 | 22.057 | 002 |     | R4    | D   | Mobile Execution Environment                                 | 3.0.1  | 4.0.0  |             |
+| SP-09          | SP-000388 | S1-000428 | 22.057 | 004 |     | R4    | D   | MExE Release 2000                                            | 3.0.1  | 4.0.0  |             |
+| SP-09          | SP-000388 | S1-000428 | 22.057 | 005 |     | R4    | B   | MExE Classmark updates                                       | 3.0.1  | 4.0.0  |             |
+| SP-09          | SP-000388 | S1-000628 | 22.057 | 003 |     | R5    | B   | MExE support of multimedia services                          | 3.0.1  | 5.0.0  |             |
+| SP-11          | SP-010043 | S1-010202 | 22.057 | 006 |     | Rel-5 | B   | MeXE service discovery                                       | 5.0.0  | 5.1.0  | MExE-ENHANC |
+| SP-13          | SP-010440 | S1-010629 | 22.057 | 007 |     | Rel-5 | F   | Generic requirements for support of multiple MExE classmarks | 5.1.0  | 5.2.0  | MExE-ENHANC |
+| SP-15          | SP-020045 | S1-020457 | 22.057 | 009 | -   | Rel-5 | A   | Editorial CR to correct terms and references                 | 5.2.0  | 5.3.0  | CORRECT     |
+|                |           |           | 22.057 | -   | -   | Rel-5 |     | Correction to history box                                    | 5.3.0  | 5.3.1  |             |
+| SP-16          | SP-020246 | S1-021057 | 22.057 | 010 |     | Rel-5 | F   | CR to 22.057 on Correction usage of MExE application         | 5.3.0  | 5.4.0  | MExE-ENHANC |
+| SP-26          | SP-040744 | S1-040997 | 22.057 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                  | 5.4.0  | 6.0.0  |             |
+| SP-36          |           |           | 22.057 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                  | 6.0.0  | 7.0.0  |             |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                  | 7.0.0  | 8.0.0  |             |
+| SP-46          | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-9 by MCC                                      | 8.0.0  | 9.0.0  |             |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                               | 9.0.0  | 10.0.0 |             |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-11 by MCC                                     | 10.0.0 | 11.0.0 |             |

marked/Rel-11/22_series/22060/raw.md

@@ -0,0 +1,948 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                     |    |
+|---------------------------------------------------------------------|----|
+| Foreword .....                                                      | 5  |
+| 1 Scope.....                                                        | 6  |
+| 2 References.....                                                   | 6  |
+| 3 Definitions and abbreviations .....                               | 7  |
+| 3.1 Definitions.....                                                | 7  |
+| 3.2 Abbreviations .....                                             | 9  |
+| 4 Main Concepts .....                                               | 10 |
+| 5 Service Requirements .....                                        | 11 |
+| 5.1 GPRS reference model.....                                       | 11 |
+| 5.1.1 Bearer services.....                                          | 11 |
+| 5.1.2 (Void) .....                                                  | 11 |
+| 5.1.3 (Void) .....                                                  | 11 |
+| 5.2 Network Interworking.....                                       | 11 |
+| 5.2.1 Interworking with other data networks and other PLMNs.....    | 12 |
+| 5.2.1.1 QoS when Interworking.....                                  | 12 |
+| 5.2.2 GPRS Numbering Plan.....                                      | 12 |
+| 5.2.3 Addressing and routeing requirements .....                    | 12 |
+| 5.2.3.1 PTP network layer services.....                             | 12 |
+| 5.2.4 Interworking for subscriber roaming.....                      | 12 |
+| 5.3 GPRS service description.....                                   | 12 |
+| 5.3.1 Point-To-Point Connectionless Network Service (PTP-CLNS)..... | 13 |
+| 5.3.2 (Void) .....                                                  | 13 |
+| 5.3.3 Point-To-Multipoint (PTM) service overview .....              | 13 |
+| 5.4 Service interworking .....                                      | 14 |
+| 5.5 Transfer Characteristics.....                                   | 14 |
+| 5.6 Service characteristics.....                                    | 15 |
+| 5.6.1 Subscriber profile .....                                      | 15 |
+| 5.6.2 Quality of Service (QoS).....                                 | 15 |
+| 5.6.2.1 QoS parameter definitions .....                             | 15 |
+| 5.6.2.1.1 Service precedence (priority) .....                       | 15 |
+| 5.6.2.1.2 Reliability.....                                          | 15 |
+| 5.6.2.1.3 Delay .....                                               | 16 |
+| 5.6.2.1.4 Throughput.....                                           | 16 |
+| 5.6.2.2 QoS profile - PTP .....                                     | 17 |
+| 5.6.2.3 Monitor .....                                               | 17 |
+| 5.6.3 Packet size .....                                             | 17 |
+| 6 Operational Requirements.....                                     | 17 |
+| 6.1 GPRS UE Modes of Operation .....                                | 17 |
+| 6.1.1 GPRS UE classes .....                                         | 17 |
+| 6.1.2 UE support for SMS over GPRS.....                             | 19 |
+| 6.2 Subscriber roaming .....                                        | 19 |
+| 6.3 Construction of GPRS subscriber numbers.....                    | 19 |
+| 6.4 Battery life extension .....                                    | 19 |
+| 6.5 Format Of Message User Data .....                               | 19 |
+| 6.6 Charging aspects .....                                          | 20 |
+| 6.6.1 PTP and IP-M charging information .....                       | 20 |
+| 6.6.2 Reverse Charging .....                                        | 20 |
+| 6.7 Security services.....                                          | 20 |
+| 6.8 Message Screening.....                                          | 21 |
+| 6.9 GPRS Operator Determined Barring.....                           | 21 |
+| 7 Normal procedures with successful outcome.....                    | 21 |
+| 7.1 Provision.....                                                  | 21 |
+| 7.2 Withdrawal.....                                                 | 22 |
+| 7.3 GPRS-Attach, GPRS-Detach .....                                  | 22 |
+
+|                        |                                    |    |
+|------------------------|------------------------------------|----|
+| 7.4                    | Registration .....                 | 22 |
+| 7.5                    | Void.....                          | 23 |
+| 7.6                    | Interrogation .....                | 23 |
+| 7.7                    | Activation.....                    | 23 |
+| 7.8                    | De-activation .....                | 23 |
+| 7.9                    | Invocation and operation.....      | 23 |
+| 7.10                   | PIN and Password Management .....  | 24 |
+| 8                      | Exceptional procedures .....       | 24 |
+| 8.1                    | Provision.....                     | 24 |
+| 8.2                    | Withdrawal .....                   | 24 |
+| 8.3                    | Registration .....                 | 24 |
+| 8.4                    | Void.....                          | 24 |
+| 8.5                    | Interrogation .....                | 24 |
+| 8.6                    | Activation.....                    | 25 |
+| 8.7                    | De-activation .....                | 25 |
+| 8.8                    | Invocation and operation.....      | 25 |
+| 8.9                    | PIN and Password management.....   | 25 |
+| 9                      | Addressing .....                   | 25 |
+| 9.1                    | Point to Point services .....      | 25 |
+| 9.2                    | Point to Multipoint services ..... | 25 |
+| 9.3                    | Overview .....                     | 25 |
+| Annex A (informative): | Change history.....                | 26 |
+
+# --- 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
+
+This TS defines the stage one description of the General Packet Radio Service (GPRS). Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. This TS includes information applicable to network operators, service providers and terminal, switch and data base manufacturers.
+
+This TS contains the core requirements for the packet switched networks specified by 3GPP which are sufficient to provide a complete service. It defines a set of bearer services that provide packet mode transmission within the PLMN and interwork with external networks.
+
+The term GPRS shall be used in this document to refer the GPRS service offered via GERAN and UTRAN and the PS Domain of the 3G PLMN.
+
+The GPRS shall not prevent the user's operation of other 3GPP services.
+
+# --- 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 TS 22.001: "Principles of telecommunication services supported by a Public Land Mobile Network (PLMN)".
+- [2] 3GPP TS 24.002: "Public Land Mobile Network (PLMN) access reference configuration".
+- [3] ISO 8348: "Information processing systems - data communications - network service definition".
+- [4] Internet STD 5: RFC 791: Internet protocol, RFC 950: "Internet standard subnetting procedure", RFC 919: "Broadcasting internet datagrams", RFC 922: "Broadcasting internet datagrams in the presence of subnets", RFC 792: "Internet control message protocol", RFC 1112: "Host extensions for IP multicasting" RFC 1122: "Requirements for Internet hosts - communication layers". RFC 1920: "Internet official protocol standards", RFC 1458: "Requirements for multicast protocols", RFC 1301: "Multicast transport protocol".
+- [5] 3GPP TS 22.004: "General on supplementary services".
+- [6] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)".
+- [7] 3GPP TS 42.017 : "Subscriber Identity Modules (SIM) Functional characteristics".
+- [8] 3GPP TS 22.041: "Operator Determined Barring (ODB)".
+- [9] 3GPP TS 27.060: "General Packet Radio Service (GPRS); Mobile Station (MS) supporting GPRS".
+- [10] 3GPP TS 43.055: Dual Transfer Mode; Stage 2"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this 3GPP TS the following definitions apply:
+
+### A
+
+**access delay:** The value of elapsed time between an access request and a successful access (source: ITU-T X.140).
+
+**accuracy:** A performance criterion that describes the degree of correctness with which a function is performed. (The function may or may not be performed with the desired speed.) (source: ITU-T I.350).
+
+### B
+
+**bearer service:** A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces (source: ITU-T I.112).
+
+### C
+
+**conversational service:** An interactive service which provides for bi-directional communication by means of real-time (no store-and-forward) end-to-end information transfer from user to user (source: ITU-T I.113).
+
+### D
+
+**destination user:** Entity to which calls to the General Packet Radio Service (GPRS) are directed.
+
+### F
+
+### G
+
+### I
+
+**interactive service:** A service which provides the means for bi-directional exchange of information between users. Interactive services are divided into three classes of services: conversational services, messaging services and retrieval services (source: ITU-T I.113).
+
+**interface:** The common boundary between two associated systems (source: ITU-T I.112).
+
+### M
+
+**mean bit rate:** A measure of throughput. The average (mean) bit rate available to the user for the given period of time (source: ITU-T I.210).
+
+**messaging service:** An interactive service which offers user-to-user communication between individual users via storage units with store-and-forward, mailbox and/or message handling, (e.g., information editing, processing and conversion) functions (source: ITU-T I.113).
+
+**mobile termination:** The part of the UE which terminates the radio transmission to and from the network and adapts terminal equipment capabilities to those of the radio transmission **multicast service:** A unidirectional PTM service in which a message is transmitted from a single source entity to multiple destinations.
+
+**multipoint:** A value of the service attribute "communication configuration", which denotes that the communication involves more than two network terminations (source: ITU-T I.113).
+
+### N
+
+**network operator:** Entity which provides the network operating elements and resources for the execution of the General Packet Radio Service (GPRS).
+
+**network service data unit (NSDU):** A unit of data passed between the user and the GPRS network across a Network Service Access Point (NSAP).
+
+**network termination:** A functional group on the network side of a user-network interface (source: ITU-T I.112).
+
+### O
+
+### P
+
+**packet:** An information unit identified by a label at layer 3 of the OSI reference model (source: ITU-T I.113). A network protocol data unit (NPDU).
+
+**packet data protocol (PDP):** Any protocol which transmits data as discrete units known as packets, e.g., IP.
+
+**packet transfer mode:** Also known as packet mode. A transfer mode in which the transmission and switching functions are achieved by packet oriented techniques, so as to dynamically share network transmission and switching resources between a multiplicity of connections (source: ITU-T I.113).
+
+**PLMN Operator:** Public Land Mobile Network operator. The entity which offers a GPRS.
+
+**point-to-multipoint (PTM) service:** A service type in which data is sent to "all service subscribers or a pre-defined subset of all subscribers" within an area defined by the Service Requester.
+
+**point-to-point (PTP):** A value of the service attribute "communication configuration", which denotes that the communication involves only two network terminations.
+
+**point-to-point (PTP) service:** A service type in which data is sent from a single network termination to another network termination.
+
+**protocol:** A formal set of procedures that are adopted to ensure communication between two or more functions within the within the same layer of a hierarchy of functions (source: ITU-T I.112).
+
+**protocol data unit (PDU):** In the reference model for OSI, a unit of data specified in an (N)-protocol layer and consisting of (N)-protocol control information and possibly (N)-user data (source: ITU-T X.200 / ISO-IEC 7498-1).
+
+**push service:** service type which delivers information (data/multimedia) initiated from a network (which may be external to the PLMN) to the UE. The service will cause a PDP context to be activated if needed.
+
+### Q
+
+**quality of service:** The collective effect of service performances which determine the degree of satisfaction of a user of the service (ITU-T E.800). The set of performance parameters that can be directly observed and measured at the point at which the service is accessed by the user. There are three criteria by which performance is measured: speed, accuracy and dependability (source: ITU-T I.350).
+
+### R
+
+**reference configuration:** A combination of functional groups and reference points that shows possible network arrangements (source: ITU-T I.112).
+
+**reference point:** A conceptual point at the conjunction of two non-overlapping functional groups (source: ITU-T I.112).
+
+**retrieval service:** An interactive service which provides the capability of accessing information stored in data base centres. The information will be sent to the user on demand only. The information is retrieved on an individual basis, i.e., the time at which an information sequence is to start is under the control of the user (source ITU-T I.113).
+
+### S
+
+**service attribute:** A specified characteristic of a telecommunication service (source: ITU-T I.112).
+
+NOTE: the value(s) assigned to one or more service attributes may be used to distinguish that telecommunications service from others.
+
+**service data unit (SDU):** In the reference model for OSI, an amount of information whose identity is preserved when transferred between peer (N+1)-layer entities and which is not interpreted by the supporting (N)-layer entities (source: ITU-T X.200 / ISO-IEC 7498-1).
+
+**service delay:** The time elapsed from the invocation of the service request, to the corresponding service request indication at the Service Receiver, indicating the arrival of application data.
+
+**service provider:** Entity which offers the General Packet Radio Service (GPRS) for subscription. The network operator may be the service provider.
+
+**service receiver:** The entity which receives the service request indication primitive, containing the SDU.
+
+**service request:** This is defined as being one invocation of the service through a service request primitive.
+
+**service requester:** The entity which requests the initiation of a GPRS operation, through a service request.
+
+**service subscriber:** Entity which subscribes to the General Packet Radio Service (GPRS) service.
+
+**speed:** A performance criterion that describes the time interval required to perform a function or the rate at which the function is performed. (The function may or may not be performed with the desired accuracy.) (source: ITU-T I.350).
+
+### T
+
+**throughput:** A parameter describing service speed. The number of data bits successfully transferred in one direction between specified reference points per unit time (source: ITU-T I.113).
+
+**transit delay:** A parameter describing service speed. The time difference between the instant at which the first bit of a protocol data unit (PDU) crosses one designated boundary (reference point), and the instant at which the last bit of the PDU crosses a second designated boundary (source: ITU-T I.113).
+
+### U
+
+### V
+
+**variable bit rate service:** A type of telecommunication service characterised by a service bit rate specified by statistically expressed parameters which allow the bit rate to vary within defined limits (source: ITU-T I.113).
+
+## 3.2 Abbreviations
+
+For the purposes of this 3GPP TS the following definitions apply:
+
+|       |                                   |
+|-------|-----------------------------------|
+| CLNP  | Connectionless network protocol   |
+| CLNS  | Connectionless network service    |
+| EGPRS | Enhanced GPRS                     |
+| FFS   | For further study                 |
+| GPRS  | General packet radio service      |
+| HSDPA | High Speed Downlink Packet Access |
+| IP    | Internet protocol                 |
+| IP-M  | Internet protocol multicast       |
+| NSDU  | Network service data unit         |
+| PDP   | Packet data protocol              |
+| PDU   | Protocol data unit                |
+| PLMN  | Public land mobile network        |
+| PTM   | Point to multipoint               |
+| PTP   | Point to point                    |
+| QoS   | Quality of service                |
+| SAP   | Service access point              |
+| SVC   | Switched virtual circuit          |
+| SDU   | Service data unit                 |
+| TBD   | To be defined                     |
+| TLLI  | Temporary link level identity     |
+
+# 4 Main Concepts
+
+The GPRS allows the service subscriber to send and receive data in an end-to-end packet transfer mode, without utilizing network resources in circuit switched mode.
+
+GPRS enables the cost effective and efficient use of network resources for packet mode data applications e.g. for applications that exhibit one or more of the following characteristics:
+
+- intermittent, non-periodic (i.e., bursty) data transmissions, where the time between successive transmissions greatly exceeds the average transfer delay;
+- frequent transmissions of small volumes of data, for example transactions consisting of less than 500 octets of data occurring at a rate of up to several transactions per minute;
+- infrequent transmission of larger volumes of data, for example transactions consisting of several kilobytes of data occurring at a rate of up to several transactions per hour.
+
+Within the GPRS, two different bearer service types are defined. These are:
+
+- Point-To-Point (PTP);
+- Point-To-Multipoint (PTM).
+
+Based on standardized network protocols supported by the GPRS bearer services, a GPRS network administration may offer (or support) a set of additional services. This is outside the scope of this specification, however, a number of possible PTP interactive teleservices include:
+
+- retrieval services which provide the capability of accessing information stored in data base centres. The information is sent to the user on demand only. An example of one such service in the Internet's World Wide Web (WWW);
+- messaging services which offer user-to-user communication between individual users via storage units with store-and-forward mailbox, and/or message handling (e.g., information editing, processing and conversion) functions;
+- conversational services which provide bi-directional communication by means of real-time (no store-and-forward) end-to-end information transfer from user to user. An example of such a service is the Internet's Telnet application;
+- tele-action services which are characterized by low data-volume (short) transactions, for example credit card validations, lottery transactions, utility meter readings and electronic monitoring and surveillance systems.
+
+Some examples of teleservices which may be supported by a PTM bearer service include:
+
+- distribution services which are characterized by the unidirectional flow of information from a given point in the network to other (multiple) locations. Examples may include news, weather and traffic reports, as well as product or service advertisements;
+- dispatching services which are characterized by the bi-directional flow of information from a given point in the network (dispatcher) and other (multiple) users. Examples include taxi and public utility fleet services;
+- conferencing services which provide multi-directional communication by means of real-time (no store-and-forward) information transfer between multiple users.
+
+Some examples of teleservices which may be supported by either PTP or PTM bearers include:
+
+- user subscribed services where a priori agreement is made for delivery of data to a user, such as stock quotes, sports results, specific product or service advertisements, and email.
+
+EGPRS is an enhancement of GPRS for GERAN allowing higher data rates on the radio interface. The same set of services provided by GPRS is available in EGPRS.
+
+HSDPA is an enhancement to Packet data services for UTRAN allowing higher data rates on the radio interface downlink. The same set of services provided by GPRS is available with GPRS using HSDPA.
+
+# 5 Service Requirements
+
+## 5.1 GPRS reference model
+
+The GPRS can be described using the simplified reference model in figure 1.
+
+GPRS provides data transfer capabilities between a sending entity and one or more receiving entities. These entities may be an UE or a Terminal Equipment, the latter being attached either to a GPRS network or to an external data network. The base station provides radio channel access for UEs to the GPRS network. User data may be transferred between four types of UEs as described in 3GPP TS22.001 [1] and TS 24.002 [2].
+
+Each PLMN has two access points, the radio interface (labelled Um for GERAN and Uu for UTRAN) used for mobile access and the R reference point used for origination or reception of messages. The R reference point for the UEs is defined in 27.060 [9].
+
+![Figure 1: GPRS simplified reference model diagram](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+The diagram illustrates the GPRS simplified reference model. It features a 'UE' (User Equipment) box on the left connected to a large oval labeled 'GPRS Data Network' via a line labeled 'Um or Uu'. Below the 'GPRS Data Network' oval, a vertical line descends to a 'TE' (Terminal Equipment) box, with a horizontal line labeled 'Gi' intersecting this vertical path. From the bottom of the 'GPRS Data Network' oval, another vertical line descends to a second oval labeled 'External Data Network'. A 'TE' box is connected to this 'External Data Network' oval by a horizontal line.
+
+Figure 1: GPRS simplified reference model diagram
+
+**Figure 1: GPRS simplified reference model**
+
+### 5.1.1 Bearer services
+
+The GPRS bearer services support the capability to transmit data between user-network access points.
+
+### 5.1.2 (Void)
+
+### 5.1.3 (Void)
+
+## 5.2 Network Interworking
+
+Network interworking is required whenever a PLMN and a non-PLMN are involved in the execution of a GPRS Service request.
+
+In general the mobile user of a GPRS network will receive and experience all the services provided by an external data network. In this case the external data network refers to the network that the GPRS PLMN interworks with as determined by the network operator. With this in mind it can be said that a user :-
+
+- 1) will require a universal identity(ies) of the form compatible with the interworked with network(s);
+- 2) and experience access to and provision of all services as offered by the interworked with networks (some reduction of capability may result from unavoidable restrictions due to the complexity of implementation).
+
+### 5.2.1 Interworking with other data networks and other PLMNs
+
+GPRS shall provide means to interwork with external data networks. The GPRS operator may provide an appropriate address to the external data network for the subscriber as part of the GPRS subscription. That address can be either dynamic (e.g. the user's IP address is allocated from a pool of unused IP addresses every time the subscriber activates the access to an IP network) or static (e.g. a certain IP address is permanently allocated to a particular subscriber). In addition, the GPRS network shall be able to notify the server IP address (e.g. the gateway IP address) to the subscriber, when the subscriber activates. When connected with some external data networks, the routeing protocols of these networks may limit the data network addresses that can be allocated. For example, when interworking with IP networks, the IP address for the GPRS subscriber shall belong to that GPRS operator's IP subnetwork that allocates the address. In the case of a simple point to point connection, a GPRS subscriber need not have an associated network address.
+
+The type of interworking between a PLMN and data networks is determined by the network operator.
+
+Interworking with the following types of data networks shall be defined:
+
+- IP networks;
+- other PLMNs, directly or via a transit network.
+
+#### 5.2.1.1 QoS when Interworking
+
+GPRS shall satisfy, within the constraints introduced by the mobile radio environment, the QoS requirements of the interworked-with network.
+
+### 5.2.2 GPRS Numbering Plan
+
+It is required that GPRS UE addresses conform to the numbering plan already defined for 3GPP system.
+
+### 5.2.3 Addressing and routeing requirements
+
+#### 5.2.3.1 PTP network layer services
+
+A GPRS subscriber identified by an IMSI, may have a network layer address(es) temporarily and/or permanently associated with it that conforms to the standard addressing scheme of the respective network layer service used, e.g.:
+
+- IP Version 4 and 6 addresses for Internet CLNS.
+
+In the case of a simple point to point connection, a GPRS subscriber need not have an associated network layer address.
+
+### 5.2.4 Interworking for subscriber roaming
+
+Interworking between different GPRS PLMNs is required in order to support subscriber roaming.
+
+It shall be possible for the VPLMN to provide access to the external data network when the external non-3GPP data network address is dynamically assigned by the VPLMN.
+
+## 5.3 GPRS service description
+
+There are two categories of GPRS services:
+
+- Point to Point (PTP) services,
+- Point to Multipoint (PTM) services.
+
+The PTP service provides a transmission of one or more packets between two users, initiated by a service requester and received by a receiver.
+
+There is one PTP service: - PTP Connectionless Network Service (PTP-CLNS). The PTM service provides a transmission of packets between a service requester and a receiver group.
+
+There is one PTM service:
+
+- IP Multicast (IP-M).
+
+An invocation of the service request by a service requester is possible from the fixed and mobile access points.
+
+Table 1 presents the relationship between service requests and the Service Requester/Receiver.
+
+**Table 1: Relationship of service request and service requester/receiver**
+
+| Service requester/receiver<br>AP = Access Point | Types of service request |           |
+|-------------------------------------------------|--------------------------|-----------|
+|                                                 | PTP-CLNS                 | IP-M      |
+| From fixed AP to mobile AP                      | Supported                | Supported |
+| From mobile AP to mobile AP<br>(see note 1)     | Supported                | Supported |
+| From mobile AP to fixed AP                      | Supported                | Supported |
+
+NOTE 1: It shall be possible to transfer data between two mobiles of the same operator without the use of external data networks.
+
+### 5.3.1 Point-To-Point Connectionless Network Service (PTP-CLNS)
+
+Point-To-Point Connectionless Network Service (PTP-CLNS) is a service in which one (or more) single packet(s) is (are) sent from a single service subscriber "A" to a single destination user "B". Each packet is independent of the preceding and succeeding packet. This service is of the datagram type and is intended to support bursty applications. On the radio interface PTP-CLNS supports the acknowledged transfer mode for reliable delivery.
+
+GPRS provides data communications services consistent with the connectionless network layer service definition ISO 8348 [3]. Specifically, GPRS shall be able to support applications based on the following network layer protocol:
+
+- Internet Protocol (IP);
+  - IP is the network layer protocol of the Internet TCP/IP protocol suite defined by Internet STD 5 [4].
+
+### 5.3.2 (Void)
+
+### 5.3.3 Point-To-Multipoint (PTM) service overview
+
+A PTM service is the transmission of a single message to multiple subscribers. The GPRS PTM services provide the capability for a subscriber to send data to multiple destinations.
+
+There is one PTM service:
+
+- IP Multicast (IP-M), which is a service defined as a part of the IP protocol suite. In IP-M messages are sent between participants of an IP-M group. An IP-M group can be internal to the PLMN or distributed across the Internet. Participation and data transfer in the IP-M service shall be compliant with the Internet protocols. See RFC 1920 [4], RFC 1458 [4], RFC 1301 [4] and RFC 1112 [4]. The Service Receiver of a point-to-multipoint service request shall be able to filter out packets at a network level, through use of the Packet Identities, which are of no interest either because they are for a service for which no subscription is held, or the packet belongs to a sub-group within the offered application service which is of no interest. It is required that the UE-Application resources shall not be utilized for this function.
+
+**Table 2: PTM Service Characteristics**
+
+| <b>Characteristics</b>         | <b>IP-M</b>                                                         |
+|--------------------------------|---------------------------------------------------------------------|
+| Primary addressing mechanism   | specified group of subscribers                                      |
+| Secondary addressing mechanism | no                                                                  |
+| Present subscribers known      | yes, group members shall join the IP-M call to become participants. |
+| Delivery time                  | real time                                                           |
+| Direction of transmission      | multi-directional                                                   |
+| Reliable delivery              | acknowledged as normal IP PTP packets                               |
+| Ciphering                      | yes                                                                 |
+
+## 5.4 Service interworking
+
+It shall be possible for the GPRS PTP services to be utilized as a bearer service for the SMS-MO and SMS-MT services.
+
+## 5.5 Transfer Characteristics
+
+The packet multiplexing mechanisms developed for GPRS shall be independent of a given channel type. It shall be possible to operate GPRS over low and high capacity channels. Table 3 is only applicable to the GPRS part of the connection.
+
+**Table 3: Transfer Characteristics**
+
+| <b>Attributes</b>                  | <b>Supported capabilities</b>                              |
+|------------------------------------|------------------------------------------------------------|
+| Information Transfer Capability    | Unrestricted digital information                           |
+| Information Transfer               | Connection orientated, connectionless                      |
+| Mode                               | Variable bit rate and variable delay                       |
+| Timing end-to-end (b)              | Asynchronous                                               |
+| Information Transfer Rate (c)      | Maximum bit rate.                                          |
+| Information Structure              | - Service data unit integrity<br>- Data sequence integrity |
+| Communication Configuration        | - Point to point<br>- Point to multipoint                  |
+| Establishment of Communication (d) | Demand mobile originated or mobile terminated              |
+| Negotiation                        | - Out of band<br>- In band                                 |
+| Symmetry                           | - Bi-directional<br>- Unidirectional                       |
+| Radio Channel assignment           | Shared, multi-user                                         |
+
+- Traffic type: describing data streams with constant bit rate or variable bit rate characteristics.
+- Timing end-to-end: describing the timing relation between the source and destination of signals.
+- Flexible channels with a maximum bit rate that depends on the type of channel and the number of time slots in GERAN that are used. This capability defines the maximum capability associated with the channel(s). The actual bit rate for a particular user may be any value up to this maximum value.
+- Establishment of communication: may be on demand, reserved or permanent.
+
+## 5.6 Service characteristics
+
+### 5.6.1 Subscriber profile
+
+The subscriber profile holds subscription information about services and other parameters that have been assigned for an agreed contractual period. It includes the following information:
+
+- subscribed services (PTP-CLNS);
+- subscribed QoS profile (service precedence(priority), reliability, delay, throughput).
+
+An invocation of a service by any user with the appropriate subscription profile shall be possible.
+
+It shall be possible to validate a service request against a service subscriber's subscription profile.
+
+### 5.6.2 Quality of Service (QoS)
+
+The mapping of user application QoS parameters to GPRS QoS parameters is an implementation issue and is not part of GPRS specifications.
+
+It shall be possible to respond to local data traffic conditions adaptively. GPRS shall include the functionality to increase or decrease the amount of radio resources allocated to GPRS on a dynamic basis. The criteria used to decide on dynamic changes of the GPRS part of the radio resource should not be specified. Thus, only the necessary procedure, including radio protocol and timers, needed to perform the change of radio resources shall be specified within the ETSI specifications.
+
+Within GPRS the dynamic allocation of the radio resource for bursty or lengthy file transfer applications shall be such that it can be controlled by the network operator.
+
+#### 5.6.2.1 QoS parameter definitions
+
+The defined QoS parameter values, assume the user is at a location with acceptable -coverage and refer to and are valid for normal network operating conditions or, as in the case of the service precedence parameter, regulate how the network shall handle abnormal conditions.
+
+##### 5.6.2.1.1 Service precedence (priority)
+
+The service precedence indicates the relative priority of maintaining the service. For example under abnormal conditions (e.g. network congestion) packets which may be discarded can be identified. The following precedence levels are defined:
+
+- High precedence: Service commitments will be maintained ahead of all other precedence levels.
+- Normal precedence: Service commitments will be maintained ahead of low priority users.
+- Low precedence: Service commitments will be maintained after the high and normal priority commitments have been fulfilled.
+
+##### 5.6.2.1.2 Reliability
+
+The reliability parameter indicates the transmission characteristics that are required by an application. The reliability class defines the probability of loss of, duplication of, mis-sequencing of or corruption of SDUs.
+
+Table 4 lists the three classes of the data reliability.
+
+**Table 4: Reliability classes**
+
+| Reliability class | Lost SDU probability (a) | Duplicate SDU probability | Out of Sequence SDU probability | Corrupt SDU probability (b) | Example of application characteristics.                                                       |
+|-------------------|--------------------------|---------------------------|---------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------|
+| 1                 | $10^{-9}$                | $10^{-9}$                 | $10^{-9}$                       | $10^{-9}$                   | Error sensitive, no error correction capability, limited error tolerance capability.          |
+| 2                 | $10^{-4}$                | $10^{-5}$                 | $10^{-5}$                       | $10^{-6}$                   | Error sensitive, limited error correction capability, good error tolerance capability.        |
+| 3                 | $10^{-2}$                | $10^{-5}$                 | $10^{-5}$                       | $10^{-2}$                   | Not error sensitive, error correction capability and/or very good error tolerance capability. |
+
+- a) To protect against buffer overflow or a protocol malfunction, there is a maximum holding time for each SDU in the GPRS network after which the SDU is discarded. The maximum holding time depends on the protocols used (e.g., TCP/IP).
+- b) Corrupt SDU probability: the probability that a SDU will be delivered to the user with an undetected error.
+
+##### 5.6.2.1.3 Delay
+
+GPRS is not a „store and forward“ service - although data is temporarily stored at network nodes during transmission - thus, any delay incurred is due to technical transmission characteristics (or limitations) of the system and is to be minimised for a particular delay class. The delay parameter thus defines the maximum values for the mean delay and 95-percentile delay to be incurred by the transfer of data through the GPRS network(s). The delay parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s).
+
+This includes the radio channel access delay (on uplink) or radio channel scheduling delay (on downlink), the radio channel transit delay (uplink and/or downlink paths) and the GPRS-network transit delay (multiple hops). It does not include transfer delays in external networks.
+
+Delay is measured between the R or S (for UE) and Gi (for FS) reference points when applied to "UE to fixed station (FS)" or "FS to UE" transmissions.
+
+**Table 5: Delay classes**
+
+| Delay Class      | Delay (maximum values)    |                           |                           |                           |
+|------------------|---------------------------|---------------------------|---------------------------|---------------------------|
+|                  | SDU size: 128 octets      |                           | SDU size: 1024 octets     |                           |
+|                  | Mean Transfer Delay (sec) | 95 percentile Delay (sec) | Mean Transfer Delay (sec) | 95 percentile Delay (sec) |
+| 1. (Predictive)  | < 0.5                     | < 1.5                     | < 2                       | < 7                       |
+| 2. (Predictive)  | < 5                       | < 25                      | < 15                      | < 75                      |
+| 3. (Predictive)  | < 50                      | < 250                     | < 75                      | < 375                     |
+| 4. (Best Effort) | Unspecified               |                           |                           |                           |
+
+The SDUs used to establish communications between network and UE are counted in the averages in the above table if they also contain user data.
+
+##### 5.6.2.1.4 Throughput
+
+The throughput parameter indicates the user data throughput requested by the user.
+
+Throughput is defined by two negotiable parameters:
+
+- Maximum bit rate
+
+- Mean bit rate (includes, for example for "bursty" transmissions, the periods in which no data is transmitted.)
+
+The maximum and mean bit rates can be negotiated to a value up to the Information Transfer Rate value (see table 3).
+
+It shall be possible for the network to re-negotiate the throughput parameters at any time during a session.
+
+#### 5.6.2.2 QoS profile - PTP
+
+The subscriber's QoS profile for the PTP service consists of the following parameters which are negotiated or set to default values:
+
+- service precedence (priority),
+- reliability,
+- delay,
+- user data throughput.
+
+#### 5.6.2.3 Monitor
+
+As an option, the UE may monitor the current QoS level. If this option is implemented, the following information shall be monitored:
+
+- user data throughput;
+- radio channel access delay;
+- round-trip-UE/PLMN delay; and
+- reliability,
+
+The UE shall provide means of communicating this information to the application(s) via the R and S reference points as shown in Figure 2.
+
+### 5.6.3 Packet size
+
+Both PTP and PTM services shall allow the transfer of variable length Network Service Data Units (NSDU).
+
+# --- 6 Operational Requirements
+
+## 6.1 GPRS UE Modes of Operation
+
+### 6.1.1 GPRS UE classes
+
+The purpose of the definition of the GPRS UE Classes is to enable the different needs of the various market segments to be satisfied by a number of UE types with distinct capabilities (e.g., simultaneous use and number of time-slots in GERAN). A means shall be provided to indicate the GERAN multi-slot capability and current configuration to the network when necessary.
+
+Three GPRS UE modes of operation are identified:
+
+NOTE 1: The term simultaneous (attach, traffic, etc.) is the requirement to simultaneously support GPRS services and circuit switched services including SMS.
+
+Class A: The UE is attached to both GPRS and other services. The UE supports simultaneous attach, simultaneous activation, simultaneous monitor, simultaneous invocation and simultaneous traffic. The mobile user can make and/or receive calls/sessions on the two services simultaneously subject to the QoS requirements.
+
+UTRAN will only support Class A mode of operation
+
+In GERAN Class A mode of operation may be achieved using Dual Transfer Mode (DTM) functionality [10]
+
+Class B: The UE is attached to both GPRS and other services, but the UE can only operate one set of services at a time. When the UE is in both idle mode and packet idle mode it should be able to monitor paging channels for both circuit-switched and packet-switched services depending on the mode of network operation.
+
+At least one mode of network operation shall be defined so that when an UE is in both idle mode and packet idle mode it shall be able to respond to paging for both circuit-switched and packet-switched services. A mode of network operation where the network performs the paging for circuit-switched and packet-switched services on different paging channels is also defined. In such case an UE in both idle mode and packet idle mode should either attempt to listen to both paging channels with priority for the circuit-switched service or revert to class-C mode of operation.
+
+If in a mode of network operation the network performs both the paging for circuit-switched and packet-switched services on the same paging channel, then the UE shall respond to paging messages for both services.
+
+There is no requirement for the UE to monitor the packet paging channel when in dedicated mode.
+
+One mode of network operation shall be defined so that when an UE is engaged in packet data transfer, it shall receive paging messages via the packet data channel without degradation of the packet data transfer. Modes of network operation where paging for other services is not done via the packet data channel are also defined. In such cases an UE engaged in packet data transfer may attempt to receive paging messages.
+
+When responding to a paging message for other services, the UE shall establish the connection for that incoming service (i.e., enter dedicated mode) and suspend GPRS activity. GPRS activity is resumed upon return to idle mode.
+
+If paged for an incoming circuit-switched call, the UE shall indicate the presence of the call to the user or user's application, and where possible provide to the user the CLI. It shall be possible for the user (or the user's application) to decide how to proceed with an incoming call (e.g., accept the call, indicate UDUB, or invoke Call Deflection).
+
+It shall be possible for the UE to receive SMS-CB messages if it attached to GPRS but is not engaged in packet data transfer.
+
+Class B is not applicable to UTRAN or GERAN Iu Mode.
+
+NOTE 2: Users should be aware that monitoring paging (in some modes of network operation), responding to paging, alerting of circuit-switched service, or acceptance or establishment of a circuit-switched call during an active GPRS connection may degrade the performance of the established GPRS connection and, in some cases, may cause failures in an application using the GPRS connection (e.g., a file transfer might be aborted due to a timeout of the application protocol).
+
+Class C: The UE is attached to either GPRS or other services. Alternate use only. If both services (GPRS and Circuit Switched) are supported then a Class C UE can make and/or receive calls only from the manually or default selected service, i.e., either GPRS or Circuit Switched service. The status of the service which has not been selected is detached i.e., not reachable. The capability for GPRS-attached class-C UEs to receive and transmit SMS messages is optional.
+
+It shall be possible for the UE to receive SMS-CB messages if it attached to GPRS but is not engaged in packet data transfer.
+
+Class C is not applicable to UTRAN.
+
+An UE may be reconfigured. E.g., a class A UE configured as 1 slot for circuit switched plus 1 slot for GPRS may be reconfigured as a class C configured as 0 slots for circuit switched plus 2 slots for GPRS.
+
+Non-voice only UEs do not have to (but may) support emergency calls.
+
+### 6.1.2 UE support for SMS over GPRS
+
+The network shall support SMS message reception and transmission for GPRS-attached UEs. However, this feature might not be implemented in all networks.
+
+The following requirements are applicable to class A and class B GPRS UEs:
+
+- If the UE preferred method, at power up or later, is sending SMS over GPRS and this fails, either due to a direct failure indication or rejection, or due to the complete lack of a response, then the UE shall switch to sending subsequent SMS's by circuit switched services for an implementation dependent time. After this time the UE may again revert to trying to send SMS's over GPRS.  
+Also, if a different PLMN is selected the UE shall again revert to trying to send SMS's over GPRS.
+- If the SMS attempt fails on both GPRS and circuit switched services, then the user/toolkit is informed.
+
+## 6.2 Subscriber roaming
+
+GPRS shall provide the ability for subscribers to access the service while roaming between networks. This implies the pre-existence of an international signalling mechanism and a service agreement between the different network operators involved.
+
+It shall be possible for GPRS subscribers to remain GPRS attached when moving from one PLMN to another.
+
+HSDPA shall be supported when roaming providing a roaming agreement for the necessary transport/bearer service(s) is currently valid.
+
+## 6.3 Construction of GPRS subscriber numbers
+
+The number of a GPRS subscriber shall be composed such that the PLMN operator can maintain control of the numbering scheme, thereby ensuring subscriber numbering integrity. The ability to allocate a subset of the numbers privately shall be possible.
+
+## 6.4 Battery life extension
+
+The GPRS service shall provide for a means to extend the battery life of an UE, by allowing the UE to reduce current drain; e.g., by using a discontinuous reception (DRX) strategy. The power conservation strategy should allow the UE to remain in a very low current state for a considerable proportion of the time. Moreover, the power conservation strategy should ensure that no messages are lost and that bandwidth is not wasted.
+
+When conserving power through the use of DRX, or other techniques, the UE shall still meet all QoS requirements of selected classes. Some classes of service may necessitate continuous reception (i.e., no DRX capability).
+
+## 6.5 Format Of Message User Data
+
+The user data is to be presented as an octet string between GPRS's access points, and is not interpreted by the PLMN.
+
+## 6.6 Charging aspects
+
+The charging information that the GPRS network collects for each UE shall be standardised. The information that the operator uses to generate a bill to a subscriber is operator specific. Billing aspects, e.g. a regular fee for a fixed period, are outside the scope of this specification.
+
+The HPLMN Operator/Service Provider may be able to charge the GPRS subscriber for all costs incurred including those costs incurred in an external network be it a VPLMN or a data network.
+
+The charging requirements of HSDPA shall be identical to the existing packet data services.
+
+### 6.6.1 PTP and IP-M charging information
+
+The charging information of PTP and IP-M services is collected for the GPRS subscriber. As a minimum the following charging information shall be collected:
+
+- destination and source: The charging information shall describe the destination and source addresses;
+- usage of radio interface: The charging information shall describe the amount of data transmitted in MO and MT directions categorized with QoS and user protocols;
+- usage of the external data networks: The charging information shall describe the amount of data sent/received to/from the external data network;
+- usage of the packet data protocol addresses: The charging information shall describe how long the UE has used the packet data protocol addresses;
+- usage of the general GPRS resources: The charging information shall describe the usage of other GPRS related resources and UE's activity in the GPRS network (e.g. Attach/Detach, mobility management);
+- location of UE: HPLMN, VPLMN, plus optional higher accuracy location information.
+
+### 6.6.2 Reverse Charging
+
+It shall be possible to provide reverse charging as a subscription option. However, reverse charging may not be applicable to certain external data network protocols. It shall be possible, as an option, to allow users to roam from one environment to another, between fixed and mobile, between public and private as well as between different public systems.
+
+## 6.7 Security services
+
+The use of radio communications for transmission to/from subscribers in mobile networks makes them particularly sensitive to:
+
+- 1) misuse of their resources by unauthorized persons using manipulated UEs;
+- 2) eavesdropping on the information being exchanged on the radio path.
+
+Therefore, to protect the system in the two cases mentioned above, the following security features are provided for GPRS:
+
+- UE authentication; i.e., the confirmation by the land-based part of the system that the subscriber identity, transferred by the UE within the identification procedure on the radio path, is the one claimed. The purpose of this authentication is to protect the network against unauthorized use. It also enables the protection of GPRS subscribers by denying intruders the ability to impersonate authorized users;
+- access control; i.e., the network can support restrictions on access by or to different GPRS subscribers, such as restrictions by location, screening lists, and so on;
+- user identity confidentiality; i.e., the property that the user identity on the radio link is not made available or disclosed to unauthorized individuals, entities or processes. The purpose is to provide privacy of identities of the subscribers who are using GPRS radio resources. It allows for the improvement of other security features, e.g., user information confidentiality, and also provides for the protection against tracing the location of a mobile subscriber by listening to the signalling exchanges on the radio path;
+- user information confidentiality; i.e., the property that the user information is not made available or disclosed to unauthorized individuals, entities or processes. The purpose is to provide for confidentiality of user data, i.e., protection of the message part pertaining to layers 3 and above, that passes over the radio path.
+
+Both user identity and user data shall be protected as shown in table 6:
+
+**Table 6: Protection of user identity and user data**
+
+| <b>Service</b> | <b>User Identity Protection</b> | <b>User Data Protection</b> |
+|----------------|---------------------------------|-----------------------------|
+| PTP            | Yes                             | Yes                         |
+| IP-M           | Yes                             | Yes                         |
+
+Security mechanisms available for existing teleservices and bearer services should be used if possible.
+
+## 6.8 Message Screening
+
+The message screening function is concerned with filtering out unauthorized or unwanted messages. Message screening may be used to restrict the types of message or the volume of data which may be transferred across the GPRS network to/from an individual subscriber.
+
+## 6.9 GPRS Operator Determined Barring
+
+GPRS subscribers can request packet oriented services from access points within the HPLMN, or from access points within another GPRS enabled PLMN. Similarly, when roaming, a subscriber may request to be connected to an access point within the HPLMN which requires all of the packets to be sent over an international link, which may attract a higher charge from Service Providers. Therefore, similarly to circuit switched domain, barring capability is required.
+
+The specific requirements for ODB of GPRS can be found in 3GPP TS 22.041 (Operator Determined Barring) [8].
+
+# --- 7 Normal procedures with successful outcome
+
+## 7.1 Provision
+
+The GPRS services shall be provided to the subscriber after prior arrangement with the service provider. The provision of each of the following GPRS services independently or any combination thereof shall be possible:
+
+- 1) Point To Point - Connectionless Network Service (PTP-CLNS);
+- 2) Point To Multipoint (PTM).
+
+It shall be possible to subscribe to GPRS services with or without subscription to other services.
+
+It shall be possible for the network operator to offer GPRS to the Service Provider(s) who may then offer GPRS-based services to the end-user.
+
+GPRS services can be offered to a subscriber with the subscription option of using a password to control the services. A single GPRS-password per subscriber is supported by the network for all GPRS services.
+
+As a subscription option modification of the subscriber's service profile (e.g., registration) shall be possible only in conjunction with the GPRS-password.
+
+The following Quality of Service (QoS) parameters shall be assigned to the subscriber profile upon provision of the GPRS service(s). These parameters may be negotiated or set to default values:
+
+- service precedence (priority),
+- reliability,
+- delay,
+- user data throughput,
+- scheduled repeated transmission.
+
+## 7.2 Withdrawal
+
+The service(s) shall be withdrawn at the subscriber's request or for administrative reasons. Withdrawal shall de-activate the service.
+
+## 7.3 GPRS-Attach, GPRS-Detach
+
+GPRS-Attach is performed when the UE indicates its presence to the PLMN for the purpose of using the GPRS PTP or PTM services. This can be immediately after the UE has been switched on or later as the user decides to use the GPRS services. The UE identifies itself with its identity (IMSI, TLLI). A GPRS-Attach shall be successfully performed only if the subscriber has a valid GPRS subscription. It is assumed that the user will not, under normal circumstances, initiate a GPRS Attach without first ensuring that the data handling capability necessary in the terminating equipment has been activated.
+
+GPRS-Detach is performed when the UE indicates to the PLMN that the UE will no longer be using the GPRS services. The UE identifies itself with its identity (IMSI, TLLI).
+
+## 7.4 Registration
+
+Registration of the service parameters shall enable the subscriber to optimize the actual (dynamic) service profile to the subscriber's present, actual requirements within the limitations of the (static) subscription profile (see subclause 6.1). The result of the registration shall be indicated (i.e. accepted/registered or rejected/not registered). The registered service profile is valid for all GPRS transactions until modified by re-registration or changes to the subscription profile.
+
+As a subscription option registration of the service parameters shall be possible only in conjunction with a GPRS-password.
+
+It shall be possible for the user to activate connections to non-preconfigured external networks by using non-subscribed Access Point Names (APN's).
+
+Table 7 defines which service parameters shall be able to be registered for the different GPRS services. The range of values for the service parameters is specified in subclause 5.6.
+
+**Table 7: Registration of service parameters**
+
+| Service Parameter                | PTP-CLNS | IP-M    |
+|----------------------------------|----------|---------|
+| Service precedence (priority)    | 2,3,4    | 2,3,4   |
+| Reliability                      | 2,4      | 2,4     |
+| Throughput                       | 2, 3, 4  | 2, 3, 4 |
+| Simultaneous use class           | 2        | 2       |
+| Delay                            | 2, 4     | 2, 4    |
+| Security management / encryption | 1        | 1       |
+| Interworking profile<br>(a)      | 2        | 2       |
+| Password Active / De-active      | 2        | 2       |
+|                                  |          |         |
+
+Legend: 1 Network determined.
+
+2 User determined per subscription and registration.
+
+3 User determined per request.
+
+4 Negotiable.
+
+N/A Not applicable.
+
+- a) This is the set of subscription attributes (including a user-ID and/or address valid in the external data network if necessary) adopted by the subscriber when utilizing a particular destination network. A set of subscription attributes is required for each destination network. Multiple user-IDs and/or addresses for each destination network are allowed.
+
+Registration of an identity other than the IMSI (i.e. a user-ID/address in an external data network, e.g. Internet, etc.) is performed to couple this identity to the IMSI for the purpose of accessing (MO and/or MT) the external
+
+data network. Registration of an identity other than the IMSI is subject to valid subscription agreements with the network operator. This also provides an effective operator determined barring of access to external data networks.
+
+Each of the registered interworking profiles can be individually activated and de-activated.
+
+Screening parameters can be assigned to a particular interworking profile as a user protection against unwanted costs and/or data.
+
+## 7.5 Void
+
+## 7.6 Interrogation
+
+The subscriber shall be able to interrogate the status/value of registered service parameters as defined in the current service profile.
+
+## 7.7 Activation
+
+The subscriber shall be able to activate each of the registered interworking profiles independently within the limitations of the subscription profile. As an option the GPRS network may request the activation of a specific interworking profile for a GPRS attached mobile, when an mobile terminated packet or activation request from external data network with user-ID (e.g. MSISDN) packet is received even if a mobile is inactive. This option may be available for one or more PDP. The activation of the inter-working profile(s) may be performed automatically by the UE immediately after GPRS Attach. When an interworking profile is activated a dynamic binding between the 3GPP identity of the UE and the external data network user-ID and/or address is made by the system, and the appropriate service parameters are applied thus establishing a virtual connection between the UE and the GPRS network. Activation of an interworking profile results in a dynamic binding until de-activation is performed.
+
+## 7.8 De-activation
+
+The subscriber shall be able to de-activate the previously activated interworking profiles independently within the limitations of the subscription profile thus releasing the previously established virtual connection. An interworking profile(s) shall be automatically de-activated if the provision for the supporting GPRS service is withdrawn. Interworking profiles are deactivated automatically upon GPRS detach..
+
+De-activation of a particular interworking profile shall abort all presently on-going communication between the UE and the external data network.
+
+## 7.9 Invocation and operation
+
+The GPRS service is invoked upon transmission or reception of GPRS data.
+
+It shall be possible for a UE to be a GPRS service requester and a service receiver. This allows generation and origination of GPRS messages from the mobile termination itself as a standalone GPRS data source. It also allows the mobile termination to provide DCE capabilities for user applications based in terminal equipment outside the mobile termination.
+
+It shall be possible for a subscriber to set-up multiple GPRS communication sessions and maintain these over prolonged periods (e.g. several hours). It shall be possible to establish these connections via more than one external data network. This enables more than one logical data channel to exist to a single mobile termination.
+
+PTP-CLNS and IP-M communications in any combination shall be possible in parallel.
+
+## 7.10 PIN and Password Management
+
+GPRS-Attach shall only be possible after correct subscriber identification has been confirmed by entry of the current PIN if this option is active. Thus only one PIN is required to gain access to either the Circuit Switched Services/SMS or the GPRS Services or both.
+
+GPRS services can be offered to a subscriber with the subscription option of using a password to control the services. One password per subscriber is supported by the network for all GPRS services. The GPRS password shall be the specified password for supplementary services according to 3GPP TS22.004 [5] and TS22.030 [6].
+
+When this option is selected the following actions shall only be performed with the concurrent entry of the password:
+
+- registration, de-registration.
+
+# --- 8 Exceptional procedures
+
+## 8.1 Provision
+
+None.
+
+## 8.2 Withdrawal
+
+None.
+
+## 8.3 Registration
+
+An attempt to register a service or service parameter not available to that subscriber shall result in an indication to the user. The reason shall be indicated:
+
+- the service or service parameter is not supported by the PLMN;
+- the subscriber's present (static) subscription profile prohibits the use of this service or service parameter;
+- parameter is network determined;
+- the entered parameter value is outside the range of that supported by the PLMN.
+
+If, in the case of interworking with an external data network, an attempt is made to set a parameter to a value outside the range of that supported by the interworking to the external data network, it shall be indicated to the user and confirmation required before the parameter value is changed to a value selected by the network.
+
+## 8.4 Void
+
+## 8.5 Interrogation
+
+None.
+
+## 8.6 Activation
+
+An attempt to activate an interworking profile which is already in the active state shall result in an indication to the user, the interworking profile shall remain in the active state.
+
+## 8.7 De-activation
+
+An attempt to de-activate an interworking profile which is already in the de-active state shall result in an indication to the user, the interworking profile shall remain in the de-active state.
+
+## 8.8 Invocation and operation
+
+An attempt to send an MO message with an UE identity which is not valid in the network shall be rejected with an appropriate error status.
+
+An MT message that cannot be delivered due to an invalid UE identity shall be discarded by the network. A message that is received by an incorrect UE shall be discarded by the UE.
+
+## 8.9 PIN and Password management
+
+PIN and password exceptional procedures are as defined in 3GPP TS 42.017 [7] and 22.004 [5].
+
+# 9 Addressing
+
+## 9.1 Point to Point services
+
+A GPRS-PTP subscription is identified by an IMSI.
+
+## 9.2 Point to Multipoint services
+
+For mobile originated PTM communications the IMSI shall be the basis for the access to the network.
+
+## 9.3 Overview
+
+How the identities are used within the different services is described in table 8.
+
+**Table 8: Services and Identities**
+
+| Services | mobile originated |                  | mobile terminated |
+|----------|-------------------|------------------|-------------------|
+|          | calling party     | Called party     |                   |
+| GPRS PTP | IMSI              | Address (note 1) | IMSI              |
+|          |                   |                  |                   |
+|          |                   |                  |                   |
+| IP-M     | IMSI              | Address (note 1) | IMSI              |
+
+NOTE 1: The IMSI or in the case of network interworking refer to subclause 5.2.3.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                                            |        |        |         |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|------------------------------------------------------------------------------------------------------------|--------|--------|---------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                                            | Old    | New    | WI      |
+| Jun 1999       |           |           | 02.60  |     |     |       |     | Transferred to 3GPP SA1                                                                                    | 8.1.0  |        |         |
+| SA#04          |           |           | 22.060 |     |     |       |     | Version 3.0.0 Approved                                                                                     |        | 3.0.0  |         |
+| SP-05          | SP-99440  | S1-99792  | 22.060 | 001 |     | R99   | A   | Class B mode of operation                                                                                  | 3.0.0  | 3.1.0  |         |
+| SP-05          | SP-99441  | S1-99841  | 22.060 | 002 |     | R99   | B   | The function that gives the notification of the server IP address from the GPRS network to the subscriber. | 3.0.0  | 3.1.0  |         |
+| SP-05          | SP-99441  | S1-99802  | 22.060 | 003 |     | R99   | B   | Introduction of Barring for GPRS                                                                           | 3.0.0  | 3.1.0  |         |
+| SP-05          | SP-99479  | S1-99620  | 22.060 | 004 |     | R99   | D   | Editorial changes for alignment                                                                            | 3.0.0  | 3.1.0  |         |
+| SP-05          | SP-99479  | S1-99665  | 22.060 | 005 |     | R99   | D   | Editorial changes for alignment                                                                            | 3.0.0  | 3.1.0  |         |
+| SP-06          | SP-99525  | S1-991010 | 22.060 | 006 |     | R99   | B   | Support of Mobile IP in release 99                                                                         | 3.1.0  | 3.2.0  |         |
+| SP-06          | SP-99525  | S1-991044 | 22.060 | 007 |     | R99   | C   | Deletion of Anonymous Service                                                                              | 3.1.0  | 3.2.0  |         |
+| SP-06          | SP-99525  | S1-991049 | 22.060 | 008 |     | R99   | B   | GPRS & SMS-CB Interworking                                                                                 | 3.1.0  | 3.2.0  |         |
+| SP-07          | SP-000059 | S1-000117 | 22.060 | 009 |     | R99   | F   | Restructuring to improve clarity and align with Stage 2 description for Release 99                         | 3.2.0  | 3.3.0  |         |
+| SP-07          | SP-000060 | S1-000113 | 22.060 | 010 |     | R99   | F   | Support of encryption in GPRS mobile stations                                                              | 3.2.0  | 3.3.0  |         |
+| SP-07          | SP-000071 | S1-000161 | 22.011 | 014 |     | R00   | B   | Network Selection                                                                                          | 3.2.0  | 4.0.0  |         |
+| SP-08          | SP-000197 | S1-000342 | 22.060 | 013 |     | R00   | F   | Deletion of IHOSS (Point to Point Octet Stream Service)                                                    | 4.0.0  | 4.1.0  |         |
+| SP-08          | SP-000197 | S1-000344 | 22.060 | 015 |     | R00   | F   | Removal of X.25 support from Release 99.                                                                   | 4.0.0  | 4.1.0  |         |
+| SP-08          | SP-000197 | S1-000366 | 22.060 | 017 |     | R00   | F   | Clarification of support of registration to external networks                                              | 4.0.0  | 4.1.0  |         |
+| SP-10          | SP-000542 | S1-000782 | 22.060 | 019 |     | Rel-4 | A   | Removal of PTM-G service                                                                                   | 4.1.0  | 4.2.0  | TEI4    |
+| SP-10          | SP-000542 | S1-000842 | 22.060 | 020 |     | Rel-4 | C   | Push Service                                                                                               | 4.1.0  | 4.2.0  | FS-Push |
+| SP-13          | SP-010442 | S1-010898 | 22.060 | 021 | 1   | Rel-5 | B   | Introduction of High Speed Downlink Packet Access                                                          | 4.2.0  | 5.0.0  | HSDPA   |
+| SP-15          | SP-020045 | S1-020463 | 22.060 | 022 |     | Rel-5 | F   | CRs 22.060 rel 5 on change of references                                                                   | 5.0.0  | 5.1.0  | CORRECT |
+| SP-16          | SP-020380 |           | 22.060 | 025 | 1   | Rel-5 | A   | Editorial Corrections to TS 22.060 (Rel-5)                                                                 | 5.1.0  | 5.2.0  | CORRECT |
+| SP-16          | SP-020241 | S1-020989 | 22.060 | 027 |     | Rel-5 | A   | Removal of 'Erasure' from TS22.060 (Rel-5)                                                                 | 5.1.0  | 5.2.0  | CORRECT |
+| SP-19          | SP-030013 | S1-030237 | 22.060 | 030 | -   | Rel-5 | F   | CR to 22.060 on SS SMS transfer over GPRS                                                                  | 5.2.0  | 5.3.0  | TEI5    |
+| SP-19          | SP-030019 | S1-030251 | 22.060 | 028 | -   | Rel-6 | D   | Service Examples                                                                                           | 5.2.0  | 6.0.0  | TEI5    |
+| SP-19          | SP-030019 | S1-030252 | 22.060 | 029 | -   | Rel-6 | C   | Delay Criteria                                                                                             | 5.2.0  | 6.0.0  | TEI5    |
+| SP-36          |           |           | 22.060 |     | -   | Rel-7 |     | Updated from Rel-6 to Rel-7                                                                                | 6.0.0  | 7.0.0  |         |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                                                                | 7.0.0  | 8.0.0  |         |
+| SP-46          | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-9 by MCC                                                                                    | 8.0.0  | 9.0.0  |         |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                                                             | 9.0.0  | 10.0.0 |         |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-11 by MCC                                                                                   | 10.0.0 | 11.0.0 |         |

marked/Rel-11/22_series/22066/raw.md

@@ -0,0 +1,364 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                              |    |
+|--------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                               | 4  |
+| 1 Scope.....                                                                                                 | 5  |
+| 2 References.....                                                                                            | 5  |
+| 3 Definitions and abbreviations .....                                                                        | 6  |
+| 3.1 Definitions.....                                                                                         | 6  |
+| 3.2 Abbreviations .....                                                                                      | 6  |
+| 4 Applicability.....                                                                                         | 7  |
+| 5 Description.....                                                                                           | 7  |
+| 6 Normal procedures with successful outcome.....                                                             | 8  |
+| 7 Exceptional procedures .....                                                                               | 8  |
+| 8 Addressing .....                                                                                           | 8  |
+| 9 Supplementary Services and Service Interworking .....                                                      | 8  |
+| 9.1 Calling line identification presentation (CLIP) .....                                                    | 8  |
+| 9.2 Calling line identification restriction (CLIR).....                                                      | 9  |
+| 9.3 Connected line identification presentation (COLP) .....                                                  | 9  |
+| 9.4 Connected line identification restriction (COLR).....                                                    | 9  |
+| 9.5 Call Forwarding Unconditional (CFU) .....                                                                | 9  |
+| 9.6 Call Forwarding on mobile subscriber Busy (CFB).....                                                     | 9  |
+| 9.7 Call Forwarding on No Reply (CFNRy).....                                                                 | 9  |
+| 9.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) .....                                         | 9  |
+| 9.9 Call Waiting (CW) .....                                                                                  | 9  |
+| 9.10 Call hold (HOLD) .....                                                                                  | 9  |
+| 9.11 Multiparty services (MPTY) .....                                                                        | 9  |
+| 9.12 Closed User Group .....                                                                                 | 9  |
+| 9.13 Advice of Charge services.....                                                                          | 9  |
+| 9.14 Barring of All Outgoing Calls (BAOC) .....                                                              | 10 |
+| 9.15 Barring of Outgoing International Calls (BOIC) .....                                                    | 10 |
+| 9.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)..... | 10 |
+| 9.17 Barring of All Incoming Calls (BAIC) .....                                                              | 10 |
+| 9.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam).....                    | 10 |
+| 9.19 Explicit Call Transfer (ECT).....                                                                       | 10 |
+| 9.20 Completion of Calls to Busy Subscriber (CCBS) .....                                                     | 10 |
+| 9.21 Support of Private Numbering Plan (SPNP) .....                                                          | 10 |
+| 9.22 Multiple Subscriber Profile (MSP) .....                                                                 | 10 |
+| 9.23 enhanced Multi-Level Priority and Pre-emption (eMLPP).....                                              | 10 |
+| 10 Interworking with other network features.....                                                             | 10 |
+| 10.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) .....                                 | 10 |
+| 10.2 Support of Optimal Routing (SOR) .....                                                                  | 11 |
+| 11 Networking interworking.....                                                                              | 11 |
+| 12 Charging aspects .....                                                                                    | 11 |
+| 13 Lawful Interception Issues .....                                                                          | 11 |
+| Annex A: (informative) Change history .....                                                                  | 12 |
+
+# 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
+
+This TS defines the stage one description of the Support of Mobile Number Portability between networks in the same country as well as North America cross-sector portability (i.e., number portability between fixed and 3GPP system). Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself.
+
+Mobile Number Portability (MNP) is applicable only to those telecommunication services identified by an MSISDN.
+
+This specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This specification contains the core requirements for the Support of Mobile Number Portability between network operators in the same country as well as North America cross-sector portability which are sufficient to provide a complete service.
+
+Other cross-sector portability options (e.g. number portability between fixed and mobile networks outside the North American Region) are outside the scope of this technical specification. It is highly desirable however, that technical solutions for MNP should be sufficiently flexible to allow for possible enhancements, e.g. cross-sector number portability, and MNP between analogue and digital mobile networks. Additional functionalities not documented in this specification may implement requirements which are considered outside the scope of this specification. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+Porting between Service Providers (i.e. service provider portability) which does not involve a change of Network Operator is outside the scope of this specification.
+
+The relationship between Service Providers and Network Operators is outside the scope of this specification.
+
+The relationship between a Service Provider and subscriber is outside the scope of this specification. The interface between the User Equipment (UE) and any external applications are outside the scope of this specification. Charging principles are outside the scope of this specification except where explicitly stated in the text.
+
+# --- 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".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this specification the following definitions apply:
+
+**number range owner network:** The network to which the number range containing the ported number has been allocated.
+
+**directory number:** any E.164 dialable number assigned to a wireline or a wireless subscriber. A DN can be a 10-digit number in the context of the North American Numbering Plan (without a country code) or up to 15 digits for an international number(country code included).
+
+**donor network:** The subscription network from which a number is ported in the porting process. This may or may not be the number range owner network.
+
+**mobile number portability:** The ability for a mobile subscriber to change digital mobile subscription network within the same country retaining their original DN(s). Additional regulatory constraints apply in North America.
+
+**network operator:** A PLMN operator.
+
+**North American GSM number portability:** the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within an FCC regulated geographical area within North America
+
+**originating network:** the network where the calling party is located.
+
+**ported number:** Is a MSISDN that has undergone the porting process.
+
+**ported subscriber:** The subscriber of a ported number.
+
+**porting process:** A description of the transfer of a number between network operators.
+
+**recipient network:** The network which receives the number in the porting process. This network becomes the subscription network when the porting process is complete.
+
+**service provider:** An entity which offers service subscriptions to individual subscribers and contracts with a network operator to implement services for a specific DN. A service provider may contract with more than one network operator.
+
+**service provider portability:** The transfer of numbers between two unique Service Providers.
+
+**subscription network:** The network with which the customer's Service Provider has a contract to implement the customer's services for a specific DN.
+
+NOTE: The term "recipient network" is used during the porting process. The recipient network becomes the "subscription network" after the completion of the porting process.
+
+## 3.2 Abbreviations
+
+For the purposes of this specification the following abbreviations apply:
+
+|        |                                             |
+|--------|---------------------------------------------|
+| DN     | Directory Number                            |
+| IMPI   | IP multimedia CN subsystem Private Identity |
+| MMI    | Man Machine Interface                       |
+| MNP    | Mobile Number Portability                   |
+| MSISDN | Mobile Station ISDN number                  |
+| NAGNP  | North American GSM Number Portability       |
+| PLMN   | Public Land Mobile Network                  |
+| SIM    | Subscriber Identity Module                  |
+| USIM   | Universal Subscriber Identity Module        |
+
+Further related abbreviations are given in TR 21.905 [1].
+
+# --- 4 Applicability
+
+Mobile Number Portability cannot be offered to a subscriber as a stand alone service. Mobile Number Portability is applicable to all teleservices (e.g. SMS, voice, fax), IP Multimedia services and bearer services (e.g. data), except for TS12 (emergency call).
+
+The implementation of MNP shall be flexible enough to apply to each DN of a subscriber separately. Where the DNs used in the donor network are ported to different recipient mobile networks then a new IMSI/IMPI (and SIM/USIM/ISIM) will be required for each recipient network. The basic and supplementary services provisioned in the recipient network shall not be dependent on those that were provisioned in the donor network.
+
+# --- 5 Description
+
+Mobile Number Portability (MNP) is the ability for a mobile subscriber to change digital mobile subscription networks within the same country whilst retaining her original DN or DNs. Additional regulatory constraints apply in North America.
+
+North American GSM Number Portability (NAGNP) is the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within an FCC regulated geographical area within North-America.
+
+The IMSI/IMPI shall not be ported, hence the recipient mobile network of the porting process will issue a new IMSI/IMPI for the ported subscription. The porting process may, but need not, include a change in service provider.
+
+The ported subscriber can use exactly the same services as non-ported customers in the same subscription network. That is: whether the DN of a subscriber belongs to a subscription network or is ported to the subscription network shall have no influence on the services offered to the customer by that subscription network.
+
+The services offered by the number range owner network and/or the donor network have no influence on the services offered by the subscription network. When a subscriber ports a DN to a new network then the donor network no longer provides support for the services of the ported number (this includes supplementary and value added services).
+
+NOTE: This also implies that if a service supported in the donor network is not available on the recipient network then number portability mechanisms need not provide that service for the ported subscriber.
+
+A network can be a donor of numbers and a recipient of numbers. A DN can be ported more than once; a ported number can be ported back to its number range owner network. Even after multiple portings, the technical solution shall involve only the number range owner network and recipient network.
+
+The solution for MNP/NAGNP shall have a minimal adverse effect upon the quality of service offered to ported and non-ported subscribers. It may be the case that the quality of service for ported and non-ported subscribers differs slightly (e.g. due to additional call set-up delay).
+
+Any additional delay in call set-up to ported numbers shall be minimised.
+
+The process of porting a number may involve a disruption in service to the customer. The time that no service is available shall be minimised.
+
+The technical implementation of the support of MNP/NAGNP in a network should not impede number availability and efficient use of numbers.
+
+The technical implementation for the support of MNP/NAGNP shall not involve loss of functionality in the number range owner, donor or subscription network.
+
+The technical implementation of MNP/NAGNP shall support optimisation of the use of network and inter-network resources so as to minimise costs associated with transport of traffic and/or appropriate signalling and/or processing activities (e.g. optimal routing).
+
+In addition, for the porting process an efficient and effective way is needed to exchange porting information between all types of network operators.
+
+# --- 6 Normal procedures with successful outcome
+
+Mobile Number Portability is offered to all subscribers of telephone services subject to regulatory requirements.
+
+A porting process is initiated at a subscriber's request on their selected DN(s) with the relevant networks. Initiation of the porting process is an off-line administrative process and cannot be invoked via a specific MMI on the hand-set.
+
+After successful porting the subscriber, is able to use the provisioned telephone services and network specific services of the subscription network as offered to non-ported subscribers on that network. Porting will effectively initiate a new subscription
+
+As part of the porting process, the donor, number range owner and recipient networks shall update their relevant network elements in order to perform the porting. After the porting process is complete, the subscription details related to the ported DN on the donor network shall not be required and can be deleted. Therefore, only the number range owner network and the recipient network are involved in the MNP/NAGNP solution for support of service to the ported subscriber.
+
+The originating network may not be aware of the ported nature of the number; therefore the technical solution shall work even if networks other than the number range owner and recipient have no knowledge of the ported nature of the number.
+
+NOTE: Other networks may be involved to increase the efficiency of call-set-up to ported numbers.
+
+When a ported subscriber takes an additional DN at her subscription network that additional DN should not have to come from the number range owner network(s) of the subscriber's ported numbers.
+
+Where number ranges are assigned to network operators, the number range owner network shall receive the ported number back from the recipient network when the subscriber relinquishes the ported number, i.e. when the ported number ceases to be an active service number.
+
+# --- 7 Exceptional procedures
+
+Service related data (e.g. numbers used in the call-forwarding service, etc.) may not be transferred to the recipient network during the porting process.
+
+# --- 8 Addressing
+
+As a consequence of MNP, the DN of a subscriber may no longer explicitly identify the subscription network of that subscriber.
+
+# --- 9 Supplementary Services and Service Interworking
+
+The support of mobile Number Portability in a network shall not affect the handling of supplementary service for the subscribers, i.e. there shall be no difference in the handling of the supplementary services between ported in and normal subscribers of the same network.
+
+## 9.1 Calling line identification presentation (CLIP)
+
+No impact.
+
+## 9.2 Calling line identification restriction (CLIR)
+
+No impact.
+
+## 9.3 Connected line identification presentation (COLP)
+
+No impact.
+
+## 9.4 Connected line identification restriction (COLR)
+
+No impact.
+
+## 9.5 Call Forwarding Unconditional (CFU)
+
+No impact.
+
+## 9.6 Call Forwarding on mobile subscriber Busy (CFB)
+
+No impact.
+
+## 9.7 Call Forwarding on No Reply (CFNRy)
+
+No impact.
+
+## 9.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
+
+No impact.
+
+## 9.9 Call Waiting (CW)
+
+No impact.
+
+## 9.10 Call hold (HOLD)
+
+No impact.
+
+## 9.11 Multiparty services (MPTY)
+
+No impact.
+
+## 9.12 Closed User Group
+
+No impact.
+
+## 9.13 Advice of Charge services
+
+No impact.
+
+## 9.14 Barring of All Outgoing Calls (BAOC)
+
+No impact.
+
+## 9.15 Barring of Outgoing International Calls (BOIC)
+
+No impact.
+
+## 9.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)
+
+No impact.
+
+## 9.17 Barring of All Incoming Calls (BAIC)
+
+No impact.
+
+## 9.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)
+
+No impact.
+
+## 9.19 Explicit Call Transfer (ECT)
+
+No impact.
+
+## 9.20 Completion of Calls to Busy Subscriber (CCBS)
+
+No impact.
+
+## 9.21 Support of Private Numbering Plan (SPNP)
+
+No impact.
+
+## 9.22 Multiple Subscriber Profile (MSP)
+
+The porting process may apply on a per profile basis.
+
+## 9.23 enhanced Multi-Level Priority and Pre-emption (eMLPP)
+
+No impact.
+
+# --- 10 Interworking with other network features
+
+## 10.1 Customised Applications for Mobile network Enhanced Logic (CAMEL)
+
+No impact.
+
+## 10.2 Support of Optimal Routing (SOR)
+
+No impact.
+
+NOTE: This is a service requirement. However, it may be difficult to find an MNP solution with no impact on Optimal Routing.
+
+# --- 11 Networking interworking
+
+All services offered in co-operation with other types of networks shall still be offered in combination with MNP. This includes the basic services, all supplementary services and all network features.
+
+# --- 12 Charging aspects
+
+Enough information shall be collected to allow different tariffs to be applied to calls and short messages in the following case:
+
+- The calling subscriber is roaming in her home PLMN
+- and
+- The called subscriber is a subscriber of any of the PLMNs in the country of the calling subscriber's home PLMN
+
+In this case the collected information shall allow to distinguish between
+
+- Calls and short messages directed to a called subscriber who subscribes to the calling subscriber's home PLMN
+- Calls and short messages directed to a called subscriber who does not subscribe to the calling subscriber's home PLMN.
+
+Enough information should be collected to allow the involved networks to work out inter-network charging.
+
+# --- 13 Lawful Interception Issues
+
+Lawful interception shall be possible on a ported MSISDN.
+
+# Annex A: (informative) Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                          |        |        |           |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                          | Old    | New    | Work Item |
+| Jun 1999       |           |           | 02.66  |     |     |       |     | Transferred to 3GPP SA1                                                                  | 7.0.0  |        |           |
+| SA#04          |           |           | 22.066 |     |     | R99   |     | Version 3.0.0 Approved                                                                   |        | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99621  | 22.066 | 001 |     | R99   | D   | Editorial changes for alignment to 3GPP                                                  | 3.0.0  | 3.0.1  |           |
+| SP-07          | SP-000061 | S1-000134 | 22.066 | 002 |     | R99   | B   | PCS-1900 Service Provider Number Portability impacts for Mobile Number Portability       | 3.0.1  | 3.1.0  |           |
+| SP-08          | SP-000207 | S1-000434 | 22.066 | 003 |     | R99   | F   | North American Service Provider Number Portability impacts for Mobile Number Portability | 3.1.0  | 3.2.0  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.066 |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                                            | 3.0.1  | 4.0.0  |           |
+| SP-16          | SP-020267 | S1-021043 | 22.066 |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                                               | 4.0.0  | 5.0.0  |           |
+| SP-18          | SP-020655 | S1-021910 | 22.066 | 004 |     | Rel-6 | B   | CR to 22.066 on IMS number portability                                                   | 5.0.0  | 6.0.0  | IMS       |
+| SP-20          | SP-030263 | N4-030451 | 22.066 | 006 | 1   | Rel-6 | A   | Charging Requirements in an MNP environment                                              | 6.0.0  | 6.1.0  | TEI5      |
+| SP-36          |           |           | 22.066 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                                              | 6.1.0  | 7.0.0  |           |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                                              | 7.0.0  | 8.0.0  |           |
+| SP-46          | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-9 by MCC                                                                  | 8.0.0  | 9.0.0  |           |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                                           | 9.0.0  | 10.0.0 |           |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-11 by MCC                                                                 | 10.0.0 | 11.0.0 |           |

marked/Rel-11/22_series/22067/raw.md

@@ -0,0 +1,424 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                     |    |
+|-----------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                      | 4  |
+| 1 Scope.....                                                                                        | 4  |
+| 2 References.....                                                                                   | 4  |
+| 3 Definitions and abbreviations .....                                                               | 5  |
+| 3.1 Definitions.....                                                                                | 5  |
+| 3.2 Abbreviations .....                                                                             | 5  |
+| 4 Description.....                                                                                  | 6  |
+| 4.1 Applicability to telecommunication services .....                                               | 8  |
+| 5 Normal operation with successful outcome .....                                                    | 8  |
+| 5.1 Provision.....                                                                                  | 8  |
+| 5.2 Withdrawal.....                                                                                 | 8  |
+| 5.3 Registration .....                                                                              | 9  |
+| 5.4 Erasure.....                                                                                    | 9  |
+| 5.5 Network related service configuration .....                                                     | 9  |
+| 5.6 Activation.....                                                                                 | 9  |
+| 5.7 Deactivation .....                                                                              | 9  |
+| 5.8 Invocation.....                                                                                 | 9  |
+| 5.9 Normal operation.....                                                                           | 9  |
+| 5.10 Interrogation .....                                                                            | 10 |
+| 5.11 Charging requirements .....                                                                    | 10 |
+| 6 Exceptional procedures or unsuccessful outcome .....                                              | 10 |
+| 7 Alternate procedures .....                                                                        | 10 |
+| 8 Interaction with other supplementary services.....                                                | 10 |
+| 8.1 Calling Line Identification Presentation (CLIP) .....                                           | 10 |
+| 8.2 Calling Line Identification Restriction (CLIR) .....                                            | 10 |
+| 8.3 Connected Line Identification Presentation (COLP) .....                                         | 10 |
+| 8.4 Connected Line Identification Restriction (COLR) .....                                          | 10 |
+| 8.5 Call Forwarding Unconditional (CFU) .....                                                       | 11 |
+| 8.6 Call Forwarding on mobile subscriber busy (CFB) .....                                           | 11 |
+| 8.7 Call Forwarding on No Reply (CFNRy).....                                                        | 11 |
+| 8.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) .....                                | 11 |
+| 8.9 Call Waiting (CW) .....                                                                         | 11 |
+| 8.10 Call Hold.....                                                                                 | 11 |
+| 8.11 Multi-party Service (MPTY).....                                                                | 11 |
+| 8.12 Closed User Group (CUG).....                                                                   | 11 |
+| 8.13 Advice of Charge (AoC) .....                                                                   | 11 |
+| 8.14 Barring of Outgoing Calls (BAOC).....                                                          | 12 |
+| 8.15 Barring of Outgoing International Calls (BOIC) .....                                           | 12 |
+| 8.16 Barring of Outgoing International Calls except those to the Home PLMN country (BOIC-exHC)..... | 12 |
+| 8.17 Barring of All Incoming Calls (BAIC) .....                                                     | 12 |
+| 8.18 Barring of Incoming Calls when Roaming outside the home PLMN country (BIC-Roam).....           | 12 |
+| 8.19 Call Transfer (ECT) .....                                                                      | 12 |
+| 9 Interworking considerations.....                                                                  | 12 |
+| Annex A (informative) : Change history.....                                                         | 13 |
+
+# --- 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.
+
+# --- 1 Scope
+
+The present document specifies the stage 1 description of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP). This service has two parts: precedence and pre-emption. Precedence involves assigning a priority level to a call in combination with fast call set-up. Pre-emption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resources. Pre-emption can also involve the disconnection of an on-going call of lower precedence to accept an incoming call of higher precedence.
+
+The eMLPP service is provided as a network operator's option to a domain of a network. The domain can be the whole network or a subset of the network. The eMLPP service applies to all network resources in the domain that is in common use. The eMLPP service is applicable to all mobile stations in the domain with all or some mobile stations having a respective subscription assigning precedence according to the eMLPP service.
+
+eMLPP is a supplementary service and shall be provided to a subscriber for all basic services subscribed to and for which eMLPP applies.
+
+The service is described from the service subscriber's and user's point of view, in particular:
+
+- the procedure for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other services and features.
+
+The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
+
+The present document is applicable to teleservices 1x and 6x and to all bearer services used in a mobile network if eMLPP is provided. Any interaction with other services and/or networks not dealt with in clauses 8 or 9 are outside the scope of the present document.
+
+# --- 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 TS 22.004: "General on supplementary services".
+- [3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".
+- [5] 3GPP TS 42.068: "Voice Group Call Service (VGCS) - Stage 1".
+- [6] 3GPP TS 42.069: "Voice Broadcast Service (VBS) - Stage 1".
+- [7] 3GPP TS 43.005: "Technical performance objectives".
+- [8] VOID
+- [9] VOID
+- [10] ITU-T Recommendation I.255.3: "ISDN Multi-Level Precedence and Pre-emption (MLPP) stage 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definitions apply:
+
+**called-party pre-emption:** Termination of a call to a particular user when a higher priority call is directed towards that specific user. Called party pre-emption is decided by the User Equipment without interaction of the user.
+
+**calling subscriber:** Service subscriber which invokes the eMLPP service.
+
+**network operator:** Entity which provides the network operating elements and resources for the execution of the enhanced Multi-Level Precedence and Pre-emption service (eMLPP).
+
+**precedence:** Precedence is the priority associated with a call.
+
+**service provider:** Entity which offers the eMLPP service for subscription. The network operator may be the service provider.
+
+**service subscriber:** Mobile subscriber which subscribes to the eMLPP service. In principle, if a network provides eMLPP service, all users are able to subscribe to this service.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply, in addition to those listed in GSM 01.04 and 3GPP TR 21.905 [1]:
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| eMLPP | enhanced Multi-Level Precedence and Pre-emption |
+|-------|-------------------------------------------------|
+
+# --- 4 Description
+
+- a) The enhanced Multi-Level Precedence and Pre-emption service (eMLPP) provides different levels of precedence for call set-up and for call continuity in case of handover.
+
+eMLPP shall be applicable also in case of roaming if supported by the related networks.
+
+The maximum precedence level of a subscriber is set at the subscription time by the service provider, based on the subscriber's need. The subscriber may select a precedence level up to and including the maximum precedence level subscribed to, on a per call basis.
+
+There are at maximum 7 priority levels. The highest level (A) is reserved for network internal use, e.g. for emergency calls or the network related service configurations for specific voice broadcast or voice group call services. The second highest level (B) may be used for network internal use or, optionally, depending on regional requirements, for subscription. These two levels (A and B) may only be used locally, i.e. in the domain of one MSC. The other five priority levels are offered for subscription and may be applied globally, e.g. on inter switch trunks, if supported by all related network elements, and also for interworking with ISDN networks providing the MLPP service.
+
+The seven priority levels are defined as follows:
+
+- A (highest, for network internal use).
+- B (for network internal use or, optionally, for subscription).
+- 0 (for subscription).
+- 1 (for subscription).
+- 2 (for subscription).
+- 3 (for subscription).
+- 4 (lowest, for subscription).
+
+Levels A and B shall be mapped to level 0 for priority treatment outside of the MSC area in which they are applied.
+
+b) Priorities shall be treated in the network as defined for the following call scenarios:
+
+- Mobile originated calls:
+  - The priority level depends on the calling subscriber.
+  - If the user has no eMLPP subscription, the call shall have a default priority level defined in the network.
+  - If the user has an eMLPP subscription, the call shall have the priority level selected by the user at set-up or the priority level predefined by the subscriber as default priority level by registration.
+- Mobile terminated calls:
+  - The priority level depends on the calling party. For this, interworking with the ISDN MLPP (Multi-Level Precedence and Pre-emption) service is required.
+  - If the call is not an ISDN MLPP call, i.e. no priority level is received for the calling party, then the call shall be treated in the terminating mobile network with a default priority level defined in the terminating mobile network, or as an operator option may be treated with the priority level predefined by the called party subscriber as default priority level by registration.
+  - If the call is an ISDN MLPP call, the call shall be treated with the priority level provided by the interfacing network.
+- Mobile-to-mobile calls in case of roaming:
+
+The priority shall be treated for the calling subscriber as for mobile originated calls and for the called subscriber as for mobile terminated calls.
+- Mobile-to-mobile calls in one network:
+
+The priority shall be treated for the calling subscriber as for mobile originated calls and for the called subscriber as for mobile terminated calls.
+- Voice broadcast (VBS) and voice group calls (VGCS):
+
+At the first instances of the voice broadcast or voice group call, when there is only a link between the calling mobile station and the network, the call shall be treated at the defined priority level of this voice broadcast or voice group call if this information is available. If the information is not available the call shall be treated as defined for mobile originated calls. Then, for the set-up of the voice broadcast or voice group call links in the related cells, the call shall have the priority level as defined for this voice broadcast or voice group call in the network.
+
+c) There are three classes of set-up time performance and examples of the call set-up times are:
+
+- class 1 fast set-up 1-2 s;
+- class 2 normal set-up < 5 s;
+- class 3 slow set-up < 10 s.
+
+The achievement of the set-up times depends on technical realizations and network planning. Mechanisms shall be implemented to provide the performance defined by the service provider under normal circumstances (no congestion). They do not include any allowance for user reaction times. The call set-up time is considered to be the time from pressing the "send" button to the point at which the called party, or at least one called party in the case of a multi-party, voice group or voice broadcast call, can receive information.
+
+The class 1 figures depend on the required connection type and service and will have to be considered accordingly. It is assumed that for calls which originate or terminate in external networks, 25 % of the set-up time is spent in these external networks. The procedures assume normal operating conditions apply, e.g. reference loads as defined in 3GPP TS 43.005, the mobile station is in an area of sufficient coverage, the mobile station is not busy, no call redirection is in place, etc.
+
+d) Calls with a high priority requiring a class 1 set-up may not require authentication at call set-up nor confidentiality on the radio link.
+
+e) For precedence calls, the network shall have the possibility to pre-empt on-going calls with lower priority, in ascending order of priority, in case of congestion at set-up on the radio interface or the core network side, respectively, or at handover of the precedence call to a congested cell. In case of necessary pre-emption of another on-going call at set-up, the successful call set-up may exceed the set-up time performance defined under c) but shall be completed as soon as possible.
+
+A call can be pre-empted any time after the precedence level of the call has been established and before call clearing has begun.
+
+Pre-emption shall only be performed to provide precedence for those priority levels which have a pre-emption capability allocated by the network operator. Priority levels with no pre-emption capability allocated shall only have queuing priority.
+
+f) A subscriber shall be able to set her mobile station to automatic answer a call if the incoming call is of or exceeds a defined priority level, respectively.
+
+In case of called mobile subscriber busy, the on-going call shall be pre-empted (or set automatically on call hold by the mobile station in case of telephony and if the subscriber is entitled to call hold services) to accept the incoming call with the priority defined for automatic answering. If the on-going call is a point-to-point call, this function is only possible if the subscriber has a subscription for Call Waiting (CW).
+
+In public networks the capability to pre-empt an on-going TS12 call (emergency call) shall be subject to national regulations.
+
+The definition of the priority level which shall cause automatic answering of an incoming call or pre-emption of another on-going call shall be stored in the mobile station and can be changed by the subscriber.
+
+If a mobile station does not automatically accept an incoming call while being idle and the user does not accept the call, the call may be forwarded to another party if Call Forwarding on No Reply (CFNRy) applies.
+
+If a mobile station does not pre-empt an on-going point-to-point call to accept an incoming call of higher priority, the call is indicated by CW and the user may still accept the incoming call. If the user rejects CW, the call may be forwarded to another party if Call Forwarding on mobile station Busy (CFB) applies.
+
+If the mobile station does not pre-empt an on-going voice broadcast or voice group call to accept an incoming call of higher priority, the call may be forwarded to another party if CFNRy applies.
+
+- g) The network operator can allocate set-up classes and resource pre-emption capabilities to each priority level. Table 1 presents an example for the assignment of priority levels and the corresponding parameters.
+
+**Table 1: Example on eMLPP service composition**
+
+| Priority level | Set-up time | Pre-emption | Examples                          |
+|----------------|-------------|-------------|-----------------------------------|
+| A              | class 1     | yes         | VBS/VGCS emergency applications   |
+| B              | class 2     | yes         | Operators calls                   |
+| 0              | class 2     | yes         | TS12 Emergency calls              |
+| 1              | class 3     | yes         | Premium rate calls                |
+| 2              | class 3     | no          | Standard rate calls               |
+| 3              | class 3     | no          | Default for no eMLPP subscription |
+| 4              | class 3     | no          | Low tariff calls                  |
+
+Network operators which provide the eMLPP service for subscription need to consider the interrelation of the number of subscriptions offered (possibly restricted for particular users), the technical performance and the network planning issues in order to guarantee the service performance for the subscriber.
+
+- h) In case of pre-emption the pre-empted subscriber shall be provided with a suitable indication.
+
+## 4.1 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004.
+
+The effects of the eMLPP service are applicable, potentially, to all subscribers in a network, should a precedence call set-up or handover occur and pre-emption be necessary.
+
+# 5 Normal operation with successful outcome
+
+## 5.1 Provision
+
+A maximum authorized precedence level is provided to a service subscriber after prior arrangements with the service provider. Service subscribers without an eMLPP subscription are assigned to a default priority level (in case of emergency calls, TS12, exceptions shall be possible).
+
+## 5.2 Withdrawal
+
+The maximum authorized precedence level can be changed or the complete eMLPP service withdrawn at the subscriber's request or for administrative reasons.
+
+## 5.3 Registration
+
+The definition of the priority level to be used as default level at mobile originated call establishment shall be registered in the network. This default level will be used if a subscriber has a subscription for a priority level higher than the lowest priority level and has not selected a priority level at call set-up.
+
+Registration can take place either by the service provider or with an appropriate control procedure by the subscriber.
+
+If the subscriber requests a priority level higher than the maximum entitled one then the network shall reject this registration with an appropriate indication to the subscriber.
+
+## 5.4 Erasure
+
+Erasure of a default priority level is done as a result of a new registration overruling, and thus effectively erasing the previous registration.
+
+## 5.5 Network related service configuration
+
+The allocation of eMLPP priority levels to the call set-up classes and the possibility of pre-emption of on-going calls in case of congestion will be arranged by the network operator for a specific composition of the eMLPP service in a network. This is not related to one specific service subscriber.
+
+An example is given in table 1 of clause 4.
+
+## 5.6 Activation
+
+Not applicable.
+
+## 5.7 Deactivation
+
+Not applicable.
+
+## 5.8 Invocation
+
+The eMLPP shall be invoked automatically by the network at call set-up.
+
+The precedence level may be selected by the user on a per call basis. The user may select any precedence level up to and including her maximum authorized precedence level. The maximum authorized precedence level shall be stored on the SIM/USIM and the mobile station shall check that only an authorized level is used for set-up. In addition, it shall be possible to verify in the network the level used at set-up against the maximum authorized level.
+
+If the user has not selected a precedence level at set-up, the network shall apply the subscriber specific default precedence level.
+
+If the user has selected a precedence level higher than the maximum authorized level, the maximum authorized precedence level shall be applied for the call.
+
+## 5.9 Normal operation
+
+At invocation of the eMLPP on a call set-up, the network notes the call priority related to the call and decides on the respective actions to be taken, i.e. on queuing priority, fast call set-up procedures and possibly pre-emption in case of congestion of network resources. In case of pre-emption the network shall release the lowest lower priority call and seize the necessary resources that are required to set-up the higher priority call.
+
+Once set for a call, the precedence level cannot be changed.
+
+In the case of automatic answering of an incoming call with a sufficient priority level, the alerting indication to the calling party may not be provided in order shorten the set-up time. In case of called mobile subscriber busy, the on-going call shall be released if automatic answering applies (or set on call hold in case of a telephony call) to accept an incoming call of higher priority.
+
+When pre-emption applies, at handover to a congested cell, higher priority calls shall replace those of the lowest priority. The pre-empted user shall receive an indication for congestion as defined in 3GPP TS 22.001.
+
+## 5.10 Interrogation
+
+A service subscriber may interrogate the range of priority levels he can use and the default priority level used for mobile originated call establishment.
+
+## 5.11 Charging requirements
+
+The utilized precedence level shall be able to be extracted from the event records if different from the default precedence level.
+
+# --- 6 Exceptional procedures or unsuccessful outcome
+
+When a service subscriber makes a call, he expects the network to automatically invoke the eMLPP service according to her subscription. If the network cannot provide the service for some reason an indication shall be provided to the service subscriber to notify her of the absence or modification of the priority handling.
+
+Exceptional procedures for voice group call and voice broadcast call establishment durations exceeding the specified times are given in 3GPP TS 42.068 [5] and 3GPP TS 42.069 [6], respectively.
+
+# --- 7 Alternate procedures
+
+None identified.
+
+# --- 8 Interaction with other supplementary services
+
+## 8.1 Calling Line Identification Presentation (CLIP)
+
+No interaction.
+
+## 8.2 Calling Line Identification Restriction (CLIR)
+
+No interaction.
+
+## 8.3 Connected Line Identification Presentation (COLP)
+
+No interaction.
+
+## 8.4 Connected Line Identification Restriction (COLR)
+
+No interaction.
+
+## 8.5 Call Forwarding Unconditional (CFU)
+
+The CFU service takes precedence over the eMLPP service. The precedence level of calls shall be preserved during the forwarding process.
+
+No interaction except for voice broadcast and voice group calls (see the respective stage 1 descriptions 3GPP TS 42.069 [6] and 3GPP TS 42.068 [5]).
+
+## 8.6 Call Forwarding on mobile subscriber busy (CFB)
+
+An incoming call with higher priority level shall override CFB in case of CW (see item f of clause 4).
+
+If the mobile station does not pre-empt the on-going call of lower priority and the user rejects the CW, the call may be forwarded to another party if CFB applies.
+
+## 8.7 Call Forwarding on No Reply (CFNRy)
+
+If a mobile station does not automatically accept an incoming call while being idle and the user does not accept the call, the call may be forwarded to another party if CFNRy applies.
+
+## 8.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
+
+No interaction.
+
+## 8.9 Call Waiting (CW)
+
+Pre-emption of on-going point-to-point calls to accept incoming calls of higher priority is only possible if the subscriber has a CW subscription.
+
+The CW indication to the mobile station shall imply the precedence level in order to enable the mobile station to decide on automatic accepting of the waiting call.
+
+## 8.10 Call Hold
+
+A held call may be pre-empted due to lack of network resources. The call is cleared and the pre-empted user shall receive an appropriate indication.
+
+## 8.11 Multi-party Service (MPTY)
+
+eMLPP shall apply to the different call legs of a MPTY as for other calls.
+
+## 8.12 Closed User Group (CUG)
+
+No interaction. eMLPP shall not override CUG restrictions, except high priority calls shall override CUG restrictions as a network option.
+
+## 8.13 Advice of Charge (AoC)
+
+No interactions.
+
+NOTE: Different charge metres for different priorities can be obtained e.g. by variation of the e1 or e2 parameters of the charge advice information according to 3GPP TS 22.024.
+
+## 8.14 Barring of Outgoing Calls (BAOC)
+
+High priority calls shall override BAOC as a network option.
+
+## 8.15 Barring of Outgoing International Calls (BOIC)
+
+High priority calls shall override BOIC as a network option.
+
+## 8.16 Barring of Outgoing International Calls except those to the Home PLMN country (BOIC-exHC)
+
+High priority calls shall override BOIC-exHC as a network option.
+
+## 8.17 Barring of All Incoming Calls (BAIC)
+
+An incoming high priority call shall override BAIC as a network option.
+
+## 8.18 Barring of Incoming Calls when Roaming outside the home PLMN country (BIC-Roam)
+
+See subclause 8.17.
+
+## 8.19 Call Transfer (ECT)
+
+For a normal call transfer, the precedence level of calls is preserved during the transfer process.
+
+# --- 9 Interworking considerations
+
+Interworking of the eMLPP service with other networks shall be provided based on the MLPP service specified in ITU-T Recommendation I.255.3 or a possibly future EN related to MLPP.
+
+For this interworking it shall be considered that:
+
+- precedence levels A and B shall be mapped to precedence level 0 (see clause 4);
+- pre-emption of network resources and on-going calls in the interfacing network will be performed according to the MLPP service, i.e. pre-emption will only affect other MLPP subscribers;
+- other details in the treatment of precedence calls as specified for MLPP which are different to eMLPP.
+
+The precedence level of a call except levels A and B shall not be changed when interworking with networks providing MLPP.
+
+# Annex A (informative) : Change history
+
+| Change history |           |           |               |      |     |        |     |                                                                    |        |        |                   |
+|----------------|-----------|-----------|---------------|------|-----|--------|-----|--------------------------------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec          | CR   | Rev | Rel    | Cat | Subject/Comment                                                    | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02<br>.67 |      |     |        |     | Transferred to 3GPP SA1                                            | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.067        |      |     |        |     | Transferred to 3GPP SA1                                            |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99622  | 22.067        | 0001 |     | R99    | D   | Editorial changes for alignment                                    | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-10          | SP-000543 | S1-000846 | 22.067        | 0002 |     | Rel-4  | B   | Introduces definition of called party pre-emption                  | 3.0.1  | 4.0.0  | ASCI              |
+| SP-15          | SP-020045 | S1-020457 | 22.067        | 0003 |     | Rel-4  | F   | Editorial CR to correct terms and references                       | 4.0.0  | 4.1.0  | Correct           |
+| SP-16          | SP-020267 | S1-021043 | 22.067        |      |     | Rel-5  |     | Updated from Rel-4 to Rel5                                         | 4.1.0  | 5.0.0  |                   |
+| SP-18          | SP-020656 | S1-022377 | 22.067        | 0004 |     | Rel-6  | C   | CR to 22.067 for Priority Service                                  | 5.0.0  | 6.0.0  | PRIOR-FS          |
+| SP-20          | SP-030251 | S1-030381 | 22.067        | 0005 | -   | Rel-6  | F   | Changes to align with 23.067 for Priority Service                  | 6.0.0  | 6.1.0  | PRIOR-FS          |
+| SP-31          | SP-060029 | S1-060199 | 22.067        | 0006 | -   | Rel-7  | F   | EPRT - Correction to priority requirement on setting up group call | 6.1.0  | 7.0.0  | TEI-7             |
+| SP-34          | SP-060772 | S1-061407 | 22.067        | 0007 | -   | Rel-8  | F   | Restriction on pre-emption of TS12 calls in non-public networks    | 7.0.0  | 8.0.0  | TEI8              |
+| SP-46          | -         | -         | -             | -    | -   | -      | -   | Updated to Rel-9 by MCC                                            | 8.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -             | -    | -   | -      | -   | Update to Rel-10 version (MCC)                                     | 9.0.0  | 10.0.0 |                   |
+| SP-53          | SP-110582 | S1-112196 | 22.067        | 0008 | 1   | Rel-11 | F   | Priority at Mobile terminated calls                                | 10.0.0 | 11.0.0 | TEI11             |
+| SP-62          | SP-130592 | S1-135287 | 22.067        | 0009 | 1   | Rel-11 | F   | TS reference corrections                                           | 11.0.0 | 11.1.0 | TEI11             |

marked/Rel-11/22_series/22072/raw.md

@@ -0,0 +1,382 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                                |    |
+|----------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                                 | 5  |
+| 1 Scope.....                                                                                                   | 6  |
+| 2 References.....                                                                                              | 6  |
+| 3 Definitions and Abbreviations .....                                                                          | 6  |
+| 3.1 Definitions.....                                                                                           | 6  |
+| 3.2 Abbreviations .....                                                                                        | 6  |
+| 4 Description.....                                                                                             | 7  |
+| 4.1 General Description.....                                                                                   | 7  |
+| 4.2 Applicability to telecommunication services.....                                                           | 7  |
+| 5 Normal Procedures with successful outcome .....                                                              | 7  |
+| 5.1 Provision.....                                                                                             | 7  |
+| 5.2 Withdrawal.....                                                                                            | 7  |
+| 5.3 Registration .....                                                                                         | 8  |
+| 5.4 Erasure.....                                                                                               | 8  |
+| 5.5 Activation.....                                                                                            | 8  |
+| 5.6 Deactivation .....                                                                                         | 8  |
+| 5.7 Invocation.....                                                                                            | 8  |
+| 5.8 Interrogation .....                                                                                        | 8  |
+| 5.9 Normal Operation.....                                                                                      | 8  |
+| 5.10 Charging requirements .....                                                                               | 9  |
+| 6 Exceptional procedures or unsuccessful outcome .....                                                         | 9  |
+| 6.1 Invocation and operation.....                                                                              | 9  |
+| 7 Interactions with other supplementary services .....                                                         | 10 |
+| 7.1 Calling Line Identification Presentation (CLIP).....                                                       | 10 |
+| 7.2 Calling Line Identification Restriction (CLIR).....                                                        | 10 |
+| 7.3 Connected Line Identification Presentation (COLP) .....                                                    | 10 |
+| 7.4 Connected Line Identification Restriction (COLR).....                                                      | 10 |
+| 7.5 Call Forwarding Unconditional (CFU) .....                                                                  | 10 |
+| 7.6 Call Forwarding on mobile subscriber Busy (CFB).....                                                       | 10 |
+| 7.7 Call Forwarding on No Reply (CFNRy).....                                                                   | 10 |
+| 7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) .....                                           | 10 |
+| 7.9 Call Deflection (CD).....                                                                                  | 10 |
+| 7.10 Call Waiting (CW).....                                                                                    | 11 |
+| 7.11 Call Hold (CH).....                                                                                       | 11 |
+| 7.12 Multi-party (MPTY).....                                                                                   | 11 |
+| 7.13 Closed User Group (CUG).....                                                                              | 11 |
+| 7.14 Advice of Charge (AoC).....                                                                               | 11 |
+| 7.15 Barring of All Outgoing Calls (BAOC).....                                                                 | 11 |
+| 7.16 Barring of all Outgoing International Calls (BOIC) .....                                                  | 11 |
+| 7.17 Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC-exHC)..... | 11 |
+| 7.18 Barring of All Incoming Calls (BAIC) .....                                                                | 11 |
+| 7.19 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam).....                      | 11 |
+| 7.20 Explicit Call Transfer (ECT).....                                                                         | 12 |
+| 7.21 Completion of Calls to Busy Subscriber (CCBS).....                                                        | 12 |
+| 7.22 Support of Private Numbering Plan (SPNP).....                                                             | 12 |
+| 7.23 Multiple Subscriber Profile (MSP) .....                                                                   | 12 |
+
+8 Interactions with Customized Applications for Mobile network Enhanced Logic (CAMEL);..... 12
+
+9 Interworking Considerations..... 12
+
+**Annex A (informative): Deviations to the ISDN service Call Deflection ..... 13**
+
+Annex B (informative): Change history..... 13
+
+# --- 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
+
+Call Deflection (CD) enables the served mobile subscriber to respond to an incoming call offered by the network by requesting redirection of this call to another number specified in the response. The CD supplementary service can only be invoked before the connection is established by the served mobile subscriber, i.e. in response to the offered call, or during the period that the served subscriber is being informed of the call. The served subscriber's ability to originate calls is unaffected by the CD supplementary service.
+
+# --- 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 TS 22.004: "General on supplementary services".
+- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [4] 3GPP TS 22.085: "Closed User Group (CUG) Supplementary Services - Stage 1
+- [5] 3GPP TS 22.078: "CAMEL Phase 3; Stage 1".
+
+# --- 3 Definitions and Abbreviations
+
+## 3.1 Definitions
+
+**served subscriber:** The mobile subscriber to whom the CD supplementary service is provided.
+
+**subscriber A:** The calling subscriber in a call which is subject to diversion. The subscriber A may be a subscriber of any network.
+
+**deflected-to subscriber:** A subscriber to whom the call is redirected as a result of the CD supplementary service. The deflected-to subscriber may be a subscriber of any network.
+
+**(call) forwarding:** A general term applied to any functionality whereby a call is redirected automatically by the network to another user. The forms of forwarding are: unconditional, busy, no reply and not reachable.
+
+**diversion:** A general term which includes all forms of call forwarding and call deflection whereby calls are redirected by the user instead of being answered.
+
+## 3.2 Abbreviations
+
+For the purposes of this TS the following abbreviations apply, in addition, abbreviations used in this TS are listed in TR 21.905 [1].
+
+|    |                 |
+|----|-----------------|
+| CD | Call Deflection |
+|----|-----------------|
+
+# --- 4 Description
+
+## 4.1 General Description
+
+The CD Supplementary Service enables the served mobile subscriber to respond to an incoming call offered by the network by requesting redirection of this call to another number specified in the response. The CD supplementary service can only be invoked before the connection is established by the served mobile subscriber, i.e. in response to the offered call during the period that the served subscriber is being informed of the call. The served subscriber's ability to originate calls is unaffected by the CD supplementary service.
+
+A maximum number of diversions is permitted for each call with an upper limit of five diversions. When counting the number of diversions, all types of diversions are included. As an network operator option the maximum number of diversions shall be in the range of one to five diversions per call. If the limit of successive diversions of a call is already reached an unsuccessful call setup indication is sent backward to the network originating the call.
+
+The invocation of Call Deflection can either be an automatic response from the mobile station to the offered call (use pre-programmed information) or may be the result of an action by the served subscriber. The mobile station related procedures to pre-program and display the deflected-to number is out of the scope of this specification.
+
+If the CD service is provisioned and there is no service violation, the request will be accepted, the connection to the served mobile station will be released (with an appropriate notification) and a call towards the deflection-to subscriber will be established.
+
+## 4.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in TS 22.004 [2].
+
+# --- 5 Normal Procedures with successful outcome
+
+## 5.1 Provision
+
+The supplementary service will be provisioned for all Basic Services subscribed to and to which it is applicable.
+
+The service can be offered with several subscription options. Options apply to all Basic services subscribed to. For each subscription option, only one value can be selected.
+
+| Subscription option:                                                            | Value         |
+|---------------------------------------------------------------------------------|---------------|
+| Calling subscriber receives notification that her call has been deflected       | - Yes<br>- No |
+| MSISDN of the served subscriber can be presented to the deflected-to subscriber | - Yes<br>- No |
+
+## 5.2 Withdrawal
+
+The supplementary service will be withdrawn at the subscriber's request or for service provider reasons.
+
+## 5.3 Registration
+
+Not applicable.
+
+## 5.4 Erasure
+
+Not applicable.
+
+## 5.5 Activation
+
+Within the network the service is activated for the whole subscription period. This supplementary service shall be activated by the service provider as a result of provision.
+
+NOTE: No activation/deactivation procedure is needed at the user-network interface.
+
+## 5.6 Deactivation
+
+This supplementary service shall be deactivated by the service provider as a result of withdrawal.
+
+## 5.7 Invocation
+
+The CD supplementary service shall be invoked by the served mobile subscriber by use of a control procedure as described in TS 22.030 [3].
+
+## 5.8 Interrogation
+
+Not applicable.
+
+## 5.9 Normal Operation
+
+The network offers incoming calls to the served mobile subscriber according to the normal procedure.
+
+The served subscriber can respond to the incoming call offered normally or by invoking the CD supplementary service with an appropriate message. This appropriate message will contain the call deflection request and the deflected-to number. This deflected-to number may be accompanied by a deflected-to subaddress.
+
+Two different cases of the CD invocation can be distinguished:
+
+- The invocation can be either an automatic response from the mobile station to the offered call (using pre-programmed information at the mobile station) or
+- may be the result of an action by the served subscriber.
+
+If the CD supplementary service is invoked and the served mobile subscriber has subscribed to the service, the network performs the call deflection towards the indicated deflected-to number and clears the call to the called (served) mobile subscriber with a positive acknowledgement.
+
+As a subscription option, the served mobile subscriber can request that the subscriber A receives a notification that the call has been deflected.
+
+The deflected-to subscriber shall receive an indication that the CD supplementary service has been invoked on the call, i.e. that call has been deflected. Depending on the value of the served subscribers subscription option, the deflected-to subscriber may also receive the MSISDN of the served subscriber.
+
+When multiple diversions occurs the reason for diversion and the MSISDN given to the deflected-to subscriber should relate to the last diverting subscriber (e.g. the subscriber who has invoked the CD supplementary service).
+
+When calls are diverted once, i.e. due to a single invocation of the CD supplementary service, the following information shall be given to subscriber A based on the value of the served mobile subscriber's subscription option "calling subscriber receives notification that the call has been deflected":
+
+- if the value of the subscription option is "no", then no information shall be sent to subscriber A;
+- if the value of the subscription option is "yes ", then an indication that the call is being deflected shall be sent to subscriber A.
+
+## 5.10 Charging requirements
+
+The deflecting subscriber may be charged for the deflected part of the call.
+
+# --- 6 Exceptional procedures or unsuccessful outcome
+
+## 6.1 Invocation and operation
+
+If a mobile subscriber tries to invoke the CD supplementary service while not subscribed to or the network operator cannot provide the CD supplementary service for some other reasons, an indication shall be provided to the mobile subscriber to notify her with the reason of failure.
+
+Possible causes for rejection include:
+
+- service not subscribed to;
+- deflected-to number invalid;
+- deflected-to number is barred;
+- use of an operator access prefix;
+- insufficient information;
+- deflected-to number is a special service code (see note 1);
+- deflected-to number is served mobile subscriber's number (see note 2);
+- the number of diversions has reached the upper limit;
+- supplementary services incompatibility;
+
+NOTE 1: Network operators may prevent a served subscriber from invoking the CD supplementary service when the number specified for the deflected-to subscriber has special significance, e.g. emergency services, operator services. The identification of such numbers is outside the scope of this standard.
+
+NOTE 2: The network can only check the deflected-to number against the Basic MSISDN of the served subscriber.
+
+If the deflected call cannot be completed to the deflected-to subscriber the network shall clear the call towards the subscriber A and notify the subscriber A of the rejection.
+
+# --- 7 Interactions with other supplementary services
+
+## 7.1 Calling Line Identification Presentation (CLIP)
+
+When a call has been deflected and the deflected-to subscriber has been provided with the CLIP supplementary service, the deflected-to subscriber shall receive the number of the subscriber A unless the CLIR supplementary service is invoked for the subscriber A.
+
+## 7.2 Calling Line Identification Restriction (CLIR)
+
+No impact, i.e. when the CLIR supplementary service is applicable and invoked for subscriber A, her line identity shall not be presented to the deflected-to subscriber unless the deflected-to subscriber has an override category.
+
+## 7.3 Connected Line Identification Presentation (COLP)
+
+If the served (deflecting) subscriber selects the option that the subscriber A is not notified of call deflection, then the subscriber A shall not receive the connected line identity when the call is answered, unless the subscriber A has override capability. Otherwise, no impact.
+
+## 7.4 Connected Line Identification Restriction (COLR)
+
+No impact.
+
+## 7.5 Call Forwarding Unconditional (CFU)
+
+No impact.
+
+## 7.6 Call Forwarding on mobile subscriber Busy (CFB)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+NOTE: If the subscriber is not network determined user busy, then the CD supplementary service or the call forwarding on mobile subscriber busy supplementary service by indicating UDUB can be invoked, depending on the response from the served mobile subscriber.
+
+## 7.7 Call Forwarding on No Reply (CFNRy)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+NOTE: If the network indicates the arrival of an incoming call to the served mobile subscriber, then the CD supplementary service, or the call forwarding on no reply supplementary service can be invoked, depending on the response, or lack of response, from the served mobile subscriber.
+
+## 7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
+
+No impact,
+
+## 7.9 Call Deflection (CD)
+
+Not applicable.
+
+## 7.10 Call Waiting (CW)
+
+When receiving the call waiting indication, the served mobile subscriber can invoke the CD supplementary service.
+
+## 7.11 Call Hold (CH)
+
+No impact
+
+## 7.12 Multi-party (MPTY)
+
+No impact
+
+## 7.13 Closed User Group (CUG)
+
+Same as the interaction between CUG and the call forwarding supplementary services as defined in TS 22.085 [4].
+
+## 7.14 Advice of Charge (AoC)
+
+No impact
+
+NOTE: The Advice of Charge service does not provide any information about the charge of the deflected leg of the call to the deflecting subscriber.
+
+## 7.15 Barring of All Outgoing Calls (BAOC)
+
+If the served subscriber has Barring of all outgoing calls active and operative the invocation of the CD supplementary service shall be rejected.
+
+## 7.16 Barring of all Outgoing International Calls (BOIC)
+
+If the served subscriber has barring of all outgoing international calls active and operative, any invocation of the CD supplementary service to a number not allowed by the barring program shall be rejected.
+
+## 7.17 Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC-exHC)
+
+If the served subscriber has barring of all outgoing international calls except those direct to the HPLMN Country active and operative, any invocation of the CD supplementary service to a number not allowed by the barring program shall be rejected.
+
+## 7.18 Barring of All Incoming Calls (BAIC)
+
+No impact.
+
+## 7.19 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)
+
+No impact
+
+## 7.20 Explicit Call Transfer (ECT)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+NOTE: Where a network supports the option to transfer a call for which the connection has been established, to a user to which the connection has not yet been established, the transferred call can be deflected if this second subscriber invokes the CD supplementary service.
+
+## 7.21 Completion of Calls to Busy Subscriber (CCBS)
+
+A recall resulting from the completion of calls to busy subscribers supplementary service shall not be deflected.
+
+Subscriber A:
+
+If a call to the called subscriber (served CD subscriber) is deflected (by the served CD subscriber) to another subscriber by the CD supplementary service and the deflected-to subscriber is busy, then subscriber A shall not receive any CCBS possible indication.
+
+Served subscriber:
+
+If the called subscriber (served CD subscriber) requests invocation of the CD supplementary service on a terminating call resulting from the completion of calls to busy subscribers supplementary service, then the CCBS call shall be deflected as a normal call.
+
+## 7.22 Support of Private Numbering Plan (SPNP)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. The served subscriber shall be able to enter the deflected-to number according to the selected numbering plan.
+
+## 7.23 Multiple Subscriber Profile (MSP)
+
+If a subscriber is provisioned to both the MSP and the CD service, the CD service shall be provisioned on a per profile basis. If CD is provisioned in the profile used for the incoming call, the served subscriber may invoke the CD supplementary service in the normal way.
+
+# --- 8 Interactions with Customized Applications for Mobile network Enhanced Logic (CAMEL);
+
+The CD supplementary service shall, if invoked, take effect after the invocation of any terminating CAMEL based service. Any deflected call may cause invocation of any mobile originated CAMEL based services.
+
+If the served subscriber is provided with a Translation Information Flag (TIF-CSL, see TS 22.078 [5]) and the VPLMN supports CAMEL phase 2, then when the CD supplementary service is invoked the network shall not check the validity of the deflected-to number and shall not apply the CD interactions with Barring of all Outgoing International Calls (BOIC) and Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC-exHC).
+
+NOTE: This behaviour may be used to deflect a call to a destination violating the BOIC or BOIC-exHC supplementary service. The HPLMN operator should take care to avoid problems that may arise because of this interaction.
+
+# --- 9 Interworking Considerations
+
+Non identified.
+
+# Annex A (informative): Deviations to the ISDN service Call Deflection
+
+- 1) If the call deflection request of a served subscriber is accepted and CD is invoked ISDN gives two network options:
+  - a) The call to the served user is retained until the network receives an indication that the deflected-to user is informed of the call.
+  - b) First the call is removed from the served subscriber and then the connection to the deflected-to subscriber is established.
+
+PLMNs only provide network option b.
+- 2) The service CD does not provide the subscription option "the served user's ISDN number can be presented to the deflected-to user" to the served subscriber.
+- 3) The interaction between CD and CCBS in the PLMN is different from the interaction between CD and CCBS in ISDN. The activation of the CCBS supplementary service will not be offered to the calling subscriber if the original call is deflected to a busy user. In ISDN the CCBS request applies to the original called party.
+- 4) The handling of notifications to subscriber A in case of multiple diversion is not described in the way as ISDN this has been done. It is the intention of this service description to retain the same handling as it is used in present call forwarding implementations.
+
+# Annex B (informative): Change history
+
+| Change history |           |           |           |     |     |       |     |                                 |        |        |                   |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|---------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                 | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.72 |     |     |       |     |                                 | 7.2.0  |        |                   |
+| SA#04          |           |           | 22.072    |     |     | R99   |     | Transferred to 3GPP SA1         |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99626  | 22.072    | 001 |     | R99   | D   | Editorial changes for alignment | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.072    |     |     | Rel-4 |     | Transferred to 3GPP Release 4   | 3.0.1  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.072    |     |     | Rel-5 |     | Updated from Rel-4 to Rel-5     | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.072    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6     | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.072    |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7     | 6.0.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8     | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-9 by MCC         | 8.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)  | 9.0.0  | 10.0.0 |                   |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-11 by MCC        | 10.0.0 | 11.0.0 |                   |

marked/Rel-11/22_series/22081/raw.md

@@ -0,0 +1,642 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                   |    |
+|-------------------------------------------------------------------|----|
+| Foreword .....                                                    | 5  |
+| 0 Scope.....                                                      | 6  |
+| 0.1 References .....                                              | 7  |
+| 0.2 Abbreviations .....                                           | 7  |
+| 1 Calling Line Identification Presentation (CLIP).....            | 7  |
+| 1.1 Definition .....                                              | 7  |
+| 1.2 Description .....                                             | 7  |
+| 1.2.1 Description .....                                           | 7  |
+| 1.2.2 Applicability to telecommunication services .....           | 8  |
+| 1.3 Normal procedures with successful outcome.....                | 8  |
+| 1.3.1 Provision.....                                              | 8  |
+| 1.3.2 Withdrawal .....                                            | 8  |
+| 1.3.5 Activation .....                                            | 8  |
+| 1.3.6 Deactivation.....                                           | 8  |
+| 1.3.7 Invocation .....                                            | 8  |
+| 1.3.8 Normal operation with successful outcome.....               | 8  |
+| 1.3.11 Interrogation .....                                        | 9  |
+| 1.4 Exceptional procedures or unsuccessful outcome.....           | 9  |
+| 1.5 Alternate procedures .....                                    | 9  |
+| 1.6 Interactions with other Supplementary Services.....           | 9  |
+| 1.6.81.2 Calling line identification restriction .....            | 9  |
+| 1.6.82.1 Call forwarding unconditional .....                      | 9  |
+| 1.6.82.2 Call forwarding on mobile subscriber busy .....          | 9  |
+| 1.6.82.3 Call forwarding on no reply.....                         | 9  |
+| 1.6.82.4 Call forwarding on mobile subscriber not reachable ..... | 9  |
+| 1.6.83.1 Call Waiting.....                                        | 9  |
+| 1.6.88.8 Anonymous Call Rejection.....                            | 10 |
+| 1.7 Interworking considerations.....                              | 10 |
+| 2 Calling Line Identification Restriction (CLIR).....             | 10 |
+| 2.1 Definition .....                                              | 10 |
+| 2.2 Description .....                                             | 10 |
+| 2.2.1 Description .....                                           | 10 |
+| 2.2.2 Applicability to telecommunications services.....           | 10 |
+| 2.3 Normal procedures with successful outcome.....                | 10 |
+| 2.3.1 Provision.....                                              | 10 |
+| 2.3.2 Withdrawal .....                                            | 10 |
+| 2.3.5 Activation .....                                            | 10 |
+| 2.3.6 Deactivation.....                                           | 11 |
+| 2.3.7 Invocation .....                                            | 11 |
+| 2.3.8 Normal operation with successful outcome.....               | 11 |
+| 2.3.11 Interrogation .....                                        | 11 |
+| 2.4 Exceptional procedures or unsuccessful outcome.....           | 11 |
+| 2.5 Alternate Procedures .....                                    | 11 |
+| 2.6 Interactions with other Supplementary Services.....           | 12 |
+| 2.6.81.1 Calling line identification presentation.....            | 12 |
+| 2.6.82.1 Call forwarding unconditional .....                      | 12 |
+| 2.6.82.2 Call forwarding on mobile subscriber busy .....          | 12 |
+| 2.6.82.3 Call forwarding on no reply.....                         | 12 |
+| 2.6.82.4 Call forwarding on mobile subscriber not reachable ..... | 12 |
+| 2.7 Interworking considerations.....                              | 12 |
+| 3 Connected Line Identification Presentation (COLP).....          | 12 |
+| 3.1 Definition .....                                              | 12 |
+| 3.2 Description .....                                             | 12 |
+| 3.2.1 Description .....                                           | 12 |
+| 3.2.2 Applicability to telecommunication services .....           | 13 |
+| 3.3 Normal procedure with successful outcome .....                | 13 |
+
+|                        |                                                          |    |
+|------------------------|----------------------------------------------------------|----|
+| 3.3.1                  | Provision.....                                           | 13 |
+| 3.3.2                  | Withdrawal .....                                         | 13 |
+| 3.3.5                  | Activation .....                                         | 13 |
+| 3.3.6                  | Deactivation.....                                        | 13 |
+| 3.3.7                  | Invocation .....                                         | 13 |
+| 3.3.8                  | Normal operation with successful outcome.....            | 13 |
+| 3.3.11                 | Interrogation .....                                      | 13 |
+| 3.4                    | Exceptional procedures or unsuccessful outcome.....      | 14 |
+| 3.5                    | Alternate procedures .....                               | 14 |
+| 3.6                    | Interactions with other Supplementary Services .....     | 14 |
+| 3.6.81.4               | Connected line identification restriction.....           | 14 |
+| 3.6.82.1               | Call forwarding unconditional .....                      | 14 |
+| 3.6.82.2               | Call forwarding on mobile subscriber busy .....          | 14 |
+| 3.6.82.3               | Call forwarding on no reply .....                        | 14 |
+| 3.6.82.4               | Call forwarding on mobile subscriber not reachable ..... | 14 |
+| 3.6.84.1               | Multiparty .....                                         | 14 |
+| 3.7                    | Interworking considerations.....                         | 15 |
+| 4                      | Connected Line Identification Restriction (COLR).....    | 15 |
+| 4.1                    | Definition .....                                         | 15 |
+| 4.2                    | Description .....                                        | 15 |
+| 4.2.1                  | Description .....                                        | 15 |
+| 4.2.2                  | Applicability to telecommunications services.....        | 15 |
+| 4.3                    | Normal procedures with successful outcome.....           | 15 |
+| 4.3.1                  | Provision.....                                           | 15 |
+| 4.3.2                  | Withdrawal .....                                         | 15 |
+| 4.3.5                  | Activation .....                                         | 15 |
+| 4.3.6                  | Deactivation.....                                        | 15 |
+| 4.3.7                  | Invocation .....                                         | 15 |
+| 4.3.8                  | Normal operation with successful outcome.....            | 15 |
+| 4.3.11                 | Interrogation .....                                      | 16 |
+| 4.4                    | Exceptional procedures or unsuccessful outcome.....      | 16 |
+| 4.5                    | Alternate procedures .....                               | 16 |
+| 4.6                    | Interactions with other Supplementary Services .....     | 16 |
+| 4.6.81.3               | Connected line identification presentation .....         | 16 |
+| 4.6.82.1               | Call forwarding unconditional .....                      | 16 |
+| 4.6.82.2               | Call forwarding on mobile subscriber busy .....          | 16 |
+| 4.6.82.3               | Call forwarding on no reply .....                        | 16 |
+| 4.6.82.4               | Call forwarding on mobile subscriber not reachable ..... | 16 |
+| 4.7                    | Interworking consideration .....                         | 16 |
+| Annex A (informative): | Change history.....                                      | 18 |
+
+# --- 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.
+
+# --- 0 Scope
+
+The present document describes the Supplementary Services belonging to the group Line Identification Supplementary Services.
+
+The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in 3GPP TS 22.004.
+
+The group of Line Identification Supplementary Services is divided into the following four Supplementary Services:
+
+- CLIP** - Calling line identification presentation (clause 1);
+- CLIR** - Calling line identification restriction (clause 2);
+- COLP** - Connected line identification presentation (clause 3);
+- COLR** - Connected line identification restriction (clause 4).
+
+**Definition of line identity:** The line identity is made up of a number of information units:
+
+- the subscriber's national ISDN/MSISDN number (MSISDN number is the number stored in the VLR);
+- the country code;
+- optionally, subaddress information. The PLMN cannot be responsible for the content of this subaddress. (For definition of the subaddress see ITU-T Recommendation E.164 [3] subclause 11.2).
+
+In a full ISDN environment, the line identity shall include all the address information necessary to unambiguously identify a subscriber.
+
+The calling line identity is the line identity of the calling party.
+
+The connected line identity is the line identity of the connected party.
+
+If for the line identity of the calling party or the connected party additional line identification is received (additional calling party/connected party number) in a PLMN this additional line identification shall be used for the presentation purpose of the line identification presentation services.
+
+**Definition of Presentation and Screening Indicators:** In addition to or instead of the line identity, the network may give a Presentation Indicator (PI) and/or a Screening Indicator (SI) to the served subscriber. The following information may be given:
+
+- Presentation Indicator showing:
+  - a) presentation allowed, or
+  - b) presentation restricted, or
+  - c) number not available due to interworking;
+
+If Presentation Indicator is set to "Presentation Restricted", then the MS can get additional information on the Cause of no CLI, if provided by the network.
+
+The Cause of no CLI value may be one of the following :
+
+- Unavailable
+- reject by user
+- interaction with other services
+- coin line / pay phone
+- Screening Indicator showing:
+  - a) user provided, verified and passed, or
+
+- b) user provided, not screened, or
+- c) network provided.
+
+If the line identity is that of a PLMN subscriber, then:
+
+the national number and the country code shall always be provided by the network;
+
+the subaddress shall only be included if it is provided by the user (or user equipment);
+
+the screening indicator shall indicate "network provided".
+
+## 0.1 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+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 TS 22.004: General on Supplementary Services".
+- [3] ITU-T Recommendation E.164: "Numbering plan for the ISDN era".
+- [4] 3GPP TS 22.088: "Call Barring (CB) supplementary services – Stage 1".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TR 21.905 [1].
+
+# --- 1 Calling Line Identification Presentation (CLIP)
+
+## 1.1 Definition
+
+The CLIP Supplementary Service provides the called party with the possibility to receive the line identity of the calling party.
+
+## 1.2 Description
+
+### 1.2.1 Description
+
+This Supplementary Service provides for the ability to indicate the line identity of the calling party to the called party.
+
+The network shall deliver the calling line identity to the called party at call set-up time, regardless of the terminal capability to handle the information.
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004 [2].
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.1 Provision
+
+This Supplementary Service is provisioned for all Basic Services subscribed to and to which it is applicable, i.e. not provisioned for any subset of these Basic Services.
+
+#### **Override category within a PLMN**
+
+Override category within an ISDN/PLMN. Depending on national regulations, some networks may define categories of subscribers that have the ability to override the presentation restriction (CLIR, clause 2) and have the calling line identity presented (e.g., the police). The ability to have such override category is a national option.
+
+#### **Override category between a PLMN and a network providing calling line identification restriction**
+
+Override category between ISDN/PLMNs. When a call originates in one ISDN/PLMN and terminates in another ISDN/PLMN and the CLIR Supplementary Service is applied, the rules and regulations of the destination network shall apply. For example, the override category may not be applicable in the originating network but may be applicable in the destination network. In this situation, a call with the CLIR Supplementary Service applied can still be overridden in the destination network.
+
+The override category is only applicable within the HPLMN country.
+
+### 1.3.2 Withdrawal
+
+The CLIP Supplementary Service shall be withdrawn at the customer's request or for administrative reasons.
+
+### 1.3.5 Activation
+
+The CLIP Supplementary Service is activated as a result of provision.
+
+### 1.3.6 Deactivation
+
+The CLIP Supplementary Service is deactivated as a result of withdrawal.
+
+### 1.3.7 Invocation
+
+The network shall automatically invoke the CLIP Supplementary Service in the call set-up phase.
+
+### 1.3.8 Normal operation with successful outcome
+
+A user who has subscribed to the CLIP Supplementary Service and receives a call shall also receive the line identity of the calling party.
+
+**Note:** The decision of whether the user-defined name stored in the handset should take precedence over the line identity of the calling party is a handset implementation issue. However for user experience it may be preferable to display the user-defined name available. In case there are several names associated with the number it is up to the handset implementation to choose which name to display.
+
+In addition to or instead of the calling line identity, the subscriber may be given a Presentation Indicator and/or a Screening Indicator with the relevant information. If provided by the network, the subscriber may also be given some additional information on the Cause of no CLI in case of a presentation restricted.
+
+### 1.3.11 Interrogation
+
+#### **Status check**
+
+The mobile subscriber can request the status of the Supplementary Service and be informed if the service is provided to her.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+If the CLIR Supplementary Service is applicable to the call, then the called PLMN user shall receive an indication that the calling line identity is not available because of restriction.
+
+NOTE: See also subclause 1.3.1 (override category).
+
+In some interworking situations in which the connection is not completely supported by the sufficient signalling capability, then the called PLMN user shall receive an indication that the calling line identity is not available.
+
+For an international call in which the originating network does not provide the calling line identity, then the called PLMN user shall receive an indication that the calling line identity is not available.
+
+## 1.5 Alternate procedures
+
+None identified.
+
+## 1.6 Interactions with other Supplementary Services
+
+#### 1.6.81.2 Calling line identification restriction
+
+The CLIR Supplementary Service shall take precedence over the CLIP Supplementary Service.
+
+The CLIP Supplementary Service can take precedence over the CLIR Supplementary Service when the called user has an override category. The availability of the override category as well as the handling of calling line identity parameters for the override category is a national matter.
+
+#### 1.6.82.1 Call forwarding unconditional
+
+When a call has been forwarded and the forwarded-to user has been provided with the CLIP Supplementary Service, the forwarded-to user shall receive the number of the original calling user, if this calling user has not subscribed to or invoked the CLIR Supplementary Service.
+
+#### 1.6.82.2 Call forwarding on mobile subscriber busy
+
+Same as the interaction with call forwarding unconditional.
+
+#### 1.6.82.3 Call forwarding on no reply
+
+Same as the interaction with call forwarding unconditional.
+
+#### 1.6.82.4 Call forwarding on mobile subscriber not reachable
+
+Same as the interaction with call forwarding unconditional.
+
+#### 1.6.83.1 Call Waiting
+
+If the served mobile subscriber is provisioned with the CLIP service, the notification of an incoming (waiting) call offered to that subscriber shall include the calling line identity, as for a normal call.
+
+#### 1.6.88.8 Anonymous Call Rejection
+
+See 3GPP TS 22.088 [4].
+
+## 1.7 Interworking considerations
+
+According to national network specific rules, the CLIP Supplementary Services need not be applicable, if at least one of the two parties is not an ISDN or PLMN subscriber.
+
+# --- 2 Calling Line Identification Restriction (CLIR)
+
+## 2.1 Definition
+
+The CLIR Supplementary Service enables the calling party to prevent presentation of its line identity to the called party.
+
+## 2.2 Description
+
+### 2.2.1 Description
+
+The CLIR Supplementary Service is a Supplementary Service offered to the calling party to prevent presentation of the calling party's line identity, to the called party. In the case where the called party has an override category, see subclause 2.4.
+
+### 2.2.2 Applicability to telecommunications services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004.
+
+## 2.3 Normal procedures with successful outcome
+
+### 2.3.1 Provision
+
+This Supplementary Service is provisioned for all Basic Services subscribed to and to which it is applicable, i.e. not provisioned for any subset of these Basic Services.
+
+As a service provider option, the CLIR Supplementary Service can be offered with one subscription option permanent (invoked for all relevant calls) or temporary (suppressed by the user on a per call basis).
+
+In temporary mode, the subscriber may subscribe to the default values:
+
+- presentation restricted: or,
+- presentation not restricted.
+
+The option applies to all BS which are provisioned for this SS.
+
+### 2.3.2 Withdrawal
+
+This Supplementary Service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 2.3.5 Activation
+
+The CLIR Supplementary Service shall be activated on provision.
+
+### 2.3.6 Deactivation
+
+The CLIR Supplementary Service shall be deactivated on withdrawal.
+
+### 2.3.7 Invocation
+
+If subscribed to in the permanent mode, then the network shall automatically invoke the CLIR Supplementary Service for each outgoing call.
+
+If subscribed-to in the temporary mode with the default value "presentation restricted", then the network shall automatically invoke the CLIR Supplementary Service for each outgoing call unless CLIR is suppressed by subscriber request at the time of call request.
+
+If subscribed-to in the temporary mode with the default value "presentation not restricted", then the network shall only invoke the CLIR Supplementary Service if requested by subscriber at the time of call request.
+
+### 2.3.8 Normal operation with successful outcome
+
+When the CLIR Supplementary Service is invoked, the originating network shall provide the destination network with a notification that the line identity of the calling party is not allowed to be presented to the called party. The originating network may also provide information on the cause of no CLI.
+
+If the called party subscribes to the CLIP Supplementary Service and the CLIR Supplementary Service has been invoked, then the called party shall receive an indication that the calling line identity is not available due to restriction.
+
+### 2.3.11 Interrogation
+
+#### Data request
+
+The mobile subscriber can request the data of the Supplementary Service.
+
+In response the following information shall be given:
+
+- whether the service is provided or not;
+- if provided which mode is subscribed;
+- if subscribed to the temporary mode, which default value.
+
+## 2.4 Exceptional procedures or unsuccessful outcome
+
+If the subscriber has subscribed to the permanent mode and she tries to suppress the invocation of the CLIR Supplementary Service per MMI command during call set-up (i.e. requests that the CLI is displayed), she shall be notified that the suppression has not been performed and the call set-up shall continue. If the user has not subscribed to CLIR Supplementary Service and she tries to invoke it during call set-up per MMI command (i.e. requests that the CLI is not displayed), the call set-up attempt shall be rejected.
+
+If the called party has a relevant override category (see subclause 1.3.1), the restriction service will be overridden and the calling line identity will be presented to the called party.
+
+## 2.5 Alternate Procedures
+
+A VPLMN which supports the CLIR service shall ensure that the line identity of a subscriber whose HPLMN does not support the CLIR service shall not be displayed to the called party unless the subscriber wishes so or the called party has CLIR override capability.
+
+## 2.6 Interactions with other Supplementary Services
+
+##### 2.6.8.1.1 Calling line identification presentation
+
+See subclause 1.6.8.1.2.
+
+##### 2.6.8.2.1 Call forwarding unconditional
+
+No interaction, i.e. when the CLIR Supplementary Service is applicable and invoked for the original calling subscriber, her line identity shall not be presented to the forwarded-to user unless the forwarded-to user has an override category.
+
+##### 2.6.8.2.2 Call forwarding on mobile subscriber busy
+
+Same as the interaction with call forwarding unconditional.
+
+##### 2.6.8.2.3 Call forwarding on no reply
+
+Same as the interaction with call forwarding unconditional.
+
+##### 2.6.8.2.4 Call forwarding on mobile subscriber not reachable
+
+Same as the interaction with call forwarding unconditional.
+
+## 2.7 Interworking considerations
+
+On calls to or via non-ISDNs, it cannot be assured that a calling line identification restriction indication can be carried to the destination network. As a national option the originating network can restrict any information identifying the calling party from being forwarded to the destination network when the CLIR Supplementary Service is applicable. If a destination network receives a calling line identity without any indication of presentation allowed or restricted, the destination network shall act according to its rules and regulations.
+
+For inter-network calls, when the CLIR Supplementary Service is invoked, the originating network shall provide the destination network with a notification that the line identity of the calling party is not allowed to be presented to the called party. The originating network may also provide information on the cause of no CLI.
+
+NOTE: When the Supplementary Service CLIR is invoked, some network providers may not send the identity of the calling subscriber to other network.
+
+# --- 3 Connected Line Identification Presentation (COLP)
+
+## 3.1 Definition
+
+The Connected Line Identification Presentation (COLP) Supplementary Service provides the calling party with the possibility to receive the line identity of the connected party.
+
+## 3.2 Description
+
+### 3.2.1 Description
+
+This Supplementary Service is not a dialling check but an indication to the calling subscriber of the connected line identity in a full ISDN/PLMN environment, the connected line identity shall include all the information necessary to unambiguously identify the connected party.
+
+The network shall deliver the connected line identity to the calling party regardless of the terminal capability to handle the information.
+
+### 3.2.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004.
+
+## 3.3 Normal procedure with successful outcome
+
+### 3.3.1 Provision
+
+This Supplementary Service is provisioned for all Basic Services subscribed to and to which it is applicable, i.e. not provisioned for any subset of these Basic Services.
+
+#### **Override category within a PLMN**
+
+Override category within an ISDN/PLMN. Depending on national regulations, some networks may define categories of subscribers that have the ability to override the presentation restriction (COLR, clause4) and have the connected line identity presented (e.g., the police). The ability to have such an override category is a national option.
+
+#### **Override category between a PLMN and a network providing connected line identification restriction.**
+
+Override category between ISDNs/PLMNs. When a call originates in one ISDN/PLMN and terminates in another ISDN/PLMN and the COLR Supplementary Service is applied, the rules and regulations of the originating network shall apply.
+
+The override category is only applicable within the HPLMN country.
+
+### 3.3.2 Withdrawal
+
+The COLP Supplementary Service shall be withdrawn at the customer's request or for administrative reasons.
+
+### 3.3.5 Activation
+
+The COLP Supplementary Service is activated as a result of provision.
+
+### 3.3.6 Deactivation
+
+The COLP Supplementary Service is deactivated as a result of withdrawal.
+
+### 3.3.7 Invocation
+
+The network shall automatically invoke the COLP Supplementary Service on each outgoing call made by the served user.
+
+### 3.3.8 Normal operation with successful outcome
+
+The calling subscriber shall at the end of the call set-up phase receive the connected line identity.
+
+In addition to or instead of the connected line identity the subscriber may be given a Presentation Indicator and/or a Screening Indicator with the relevant information.
+
+### 3.3.11 Interrogation
+
+#### Status check
+
+The mobile subscriber can request the status of the Supplementary Service and be informed if the service is provided to her.
+
+## 3.4 Exceptional procedures or unsuccessful outcome
+
+If the COLR Supplementary Service is applicable to the call, the served user shall receive an indication that the connected line identity is not available due to restriction.
+
+NOTE: See also subclause 3.3.1 (override category).
+
+In some interworking situations in which the connection is not completely supported by sufficient signalling capability, the served user shall receive an indication that the connected line identity is not available.
+
+For an international call in which the destination network does not provide the connected line identity, then the served user shall receive an indication that the connected line identity is not available.
+
+## 3.5 Alternate procedures
+
+None identified.
+
+## 3.6 Interactions with other Supplementary Services
+
+#### 3.6.81.4 Connected line identification restriction
+
+The COLR Supplementary Service shall take precedence over the COLP Supplementary Service. The COLP Supplementary Service can take precedence over the COLR Supplementary Service when the served user has an override category. The availability of the override category as well as the handling of connected line identity parameters for the override category is a national option.
+
+#### 3.6.82.1 Call forwarding unconditional
+
+If the served (forwarding) user selects the option that the calling user is not notified of call forwarding, then the calling user shall receive no forwarding notification, and the calling user shall not receive the connected line identity when the call is answered, unless the calling user has override capability. Otherwise, no interaction.
+
+#### 3.6.82.2 Call forwarding on mobile subscriber busy
+
+Same as the interaction with call forwarding unconditional.
+
+#### 3.6.82.3 Call forwarding on no reply
+
+Same as the interaction with call forwarding unconditional.
+
+#### 3.6.82.4 Call forwarding on mobile subscriber not reachable
+
+Same as the interaction with call forwarding unconditional.
+
+#### 3.6.84.1 Multiparty
+
+Multiparty controller: no impact, i.e. neither Supplementary Service shall affect the operation or the other Supplementary Service.
+
+Remote parties: they shall not receive the COLP Supplementary Service information of parties being added to the conference.
+
+## 3.7 Interworking considerations
+
+According to national network specific rules the COLP Supplementary Service need not be applicable, if at least one of the two parties is not an ISDN or PLMN subscriber.
+
+# --- 4 Connected Line Identification Restriction (COLR)
+
+## 4.1 Definition
+
+The COLR Supplementary Service enables the connected party to prevent presentation of its line identity to the calling party.
+
+## 4.2 Description
+
+### 4.2.1 Description
+
+The COLR Supplementary Service is a Supplementary Service offered to the connected party to prevent presentation of the connected line identity, to the calling party. In the case where the calling party has an override category, see subclause 4.4.
+
+### 4.2.2 Applicability to telecommunications services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004.
+
+## 4.3 Normal procedures with successful outcome
+
+### 4.3.1 Provision
+
+This Supplementary Service is provisioned for all Basic Services subscribed to and to which it is applicable, i.e. not provisioned for any subset of these Basic Services.
+
+### 4.3.2 Withdrawal
+
+This Supplementary Service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 4.3.5 Activation
+
+The COLR Supplementary Service shall be activated on provision.
+
+### 4.3.6 Deactivation
+
+The COLR Supplementary Service shall be deactivated on withdrawal.
+
+### 4.3.7 Invocation
+
+The network shall automatically invoke the COLR Supplementary Service for each incoming call at call set-up phase.
+
+### 4.3.8 Normal operation with successful outcome
+
+If the calling party subscribes to the COLP Supplementary Service and the COLR Supplementary Service has been invoked, then the calling party shall receive an indication that the connected line identity is not available due to restriction.
+
+When the COLR Supplementary Service is invoked, the destination network shall provide the originating network with a notification that the line identity of the connected party is not allowed to be presented to the calling party.
+
+### 4.3.11 Interrogation
+
+#### Status check
+
+The mobile subscriber can request the status of the Supplementary Service and be informed if the service is provided to her.
+
+## 4.4 Exceptional procedures or unsuccessful outcome
+
+If the calling party has a relevant override category (see subclause 3.3.1) the restriction service will be overridden and the connected line identity will be presented to the calling party.
+
+## 4.5 Alternate procedures
+
+A VPLMN which supports the COLR service shall ensure that the line identity of a subscriber whose HPLMN does not support the COLR service shall not be displayed to the calling party unless the calling party has COLR override capability.
+
+## 4.6 Interactions with other Supplementary Services
+
+#### 4.6.81.3 Connected line identification presentation
+
+See subclause 3.6.81.4.
+
+#### 4.6.82.1 Call forwarding unconditional
+
+If a forwarded-to user subscribes to the COLR Supplementary Service, then the forwarded-to user's line identity shall not be provided with the notification that the call has been forwarded.
+
+A calling user that subscribes to the COLP Supplementary Service and who has override capability shall not be able to receive the forwarded-to user's line identity as part of the diverting notification information, but can invoke the COLP Supplementary Service with override in order to receive the connected line identity when the call is answered.
+
+#### 4.6.82.2 Call forwarding on mobile subscriber busy
+
+Same as the interaction with call forwarding unconditional.
+
+#### 4.6.82.3 Call forwarding on no reply
+
+Same as the interaction with call forwarding unconditional.
+
+#### 4.6.82.4 Call forwarding on mobile subscriber not reachable
+
+Same as the interaction with call forwarding unconditional.
+
+## 4.7 Interworking consideration
+
+On calls from or via non-ISDNs, it cannot be assured that a connected line restriction indication can be carried to the originating network. As a national option, the destination network can restrict any information identifying the connected party from being returned to the originating network when the COLR Supplementary Service is applicable. If an originating network receives a connected line identity without any indication of presentation allowed or restricted, the originating network shall act according to its rules and regulations.
+
+For inter-network calls, when the COLR Supplementary Service is invoked, the destination network shall provide the originating network with a notification that the line identity of the connected party is not allowed to be presented to the calling party.
+
+NOTE: When the COLR Supplementary Service is invoked, some network providers may not send the identity of the connected customer to other network providers.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |           |      |      |        |     |                                                              |        |        |                   |
+|----------------|-----------|-----------|-----------|------|------|--------|-----|--------------------------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR   | R ev | Rel    | Cat | Subject/Comment                                              | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.81 |      |      |        |     | Transferred to 3GPP SA1                                      | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.081    |      |      | R99    |     | Transferred to 3GPP SA1                                      |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99628  | 22.081    | 001  |      | R99    | D   | Editorial changes for alignment                              | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-06          | SP-99519  | S1-99908  | 22.081    | 002  |      | R99    | D   | Editorial update to TS 22.081 in order to include 3G systems | 3.0.1  | 3.1.0  |                   |
+| SP-08          | SP-000199 | S1-000443 | 22.081    | 003  |      | R99    | B   | Access dependent services (on Cause for no CLI)              | 3.1.0  | 3.2.0  |                   |
+| SP-11          | SP-010065 | S1-010258 | 22.081    |      |      | Rel-4  |     | Transferred to 3GPP Release 4                                | 3.2.0  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.081    | 004  | -    | Rel-4  | F   | Editorial CR to correct terms and references                 | 4.0.0  | 4.1.0  | CORRECT           |
+| SP-16          | SP-020267 | S1-021043 | 22.081    |      |      | Rel-5  |     | Updated from Rel-4 to Rel5                                   | 4.1.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.081    |      |      | Rel-6  |     | Updated from Rel-5 to Rel-6                                  | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.081    |      |      | Rel-7  |     | Updated from Rel-6 to Rel-7                                  | 6.0.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |      |      | Rel-8  |     | Updated from Rel-7 to Rel-8                                  | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -    | -    | -      | -   | Updated to Rel-9 by MCC                                      | 8.0.0  | 9.0.0  |                   |
+| SP-51          | SP-110172 | S1-110405 | 22.081    | 0005 | 1    | Rel-11 | D   | Display of duplicated numbers in the phone book              | 9.0.0  | 11.0.0 | TEI11             |
+| SP-52          | SP-110376 | S1-111433 | 22.081    | 0007 | 1    | Rel-11 | B   | Addition of Anonymous Call Rejection as a SS                 | 11.0.0 | 11.1.0 | ACR_CS            |

marked/Rel-11/22_series/22086/raw.md

@@ -0,0 +1,310 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                |    |
+|--------------------------------------------------------------------------------|----|
+| Foreword .....                                                                 | 4  |
+| 0 Scope.....                                                                   | 5  |
+| 0.1 References .....                                                           | 5  |
+| 0.2 Abbreviations .....                                                        | 5  |
+| 1 Advice Of Charge (Information) (AoCI) .....                                  | 5  |
+| 1.1 Definition .....                                                           | 5  |
+| 1.2 Description .....                                                          | 6  |
+| 1.2.1 Description .....                                                        | 6  |
+| 1.2.2 Applicability to telecommunication services .....                        | 6  |
+| 1.3 Normal procedures with successful outcome.....                             | 6  |
+| 1.3.1 Provision.....                                                           | 6  |
+| 1.3.2 Withdrawal .....                                                         | 6  |
+| 1.3.5 Activation .....                                                         | 6  |
+| 1.3.6 Deactivation.....                                                        | 6  |
+| 1.3.7 Invocation .....                                                         | 6  |
+| 1.3.8 Normal operation with successful outcome.....                            | 6  |
+| 1.4 Exceptional procedures or unsuccessful outcome.....                        | 7  |
+| 1.4.1 Operation in a PLMN that is unable to support AoC .....                  | 7  |
+| 1.4.2 AoC when MS is switched off or out of coverage .....                     | 7  |
+| 1.4.3 Operation with a MS unable to support AoC .....                          | 7  |
+| 1.5 Alternate procedures .....                                                 | 7  |
+| 1.6 Interactions with other supplementary services .....                       | 7  |
+| 1.6.1 SCUDIF .....                                                             | 7  |
+| 1.6.2 Other supplementary services .....                                       | 7  |
+| 1.7 Multicall.....                                                             | 7  |
+| 1.7 Interworking considerations.....                                           | 7  |
+| 2 Advice Of Charge (Charging) (AoCC) .....                                     | 8  |
+| 2.1 Definition .....                                                           | 8  |
+| 2.2 Description .....                                                          | 8  |
+| 2.2.1 Description .....                                                        | 8  |
+| 2.2.2 Applicability to telecommunication services .....                        | 8  |
+| 2.3 Normal procedures with successful outcome.....                             | 8  |
+| 2.3.1 Provision.....                                                           | 8  |
+| 2.3.2 Withdrawal .....                                                         | 8  |
+| 2.3.5 Activation .....                                                         | 8  |
+| 2.3.6 Deactivation.....                                                        | 9  |
+| 2.3.7 Invocation .....                                                         | 9  |
+| 2.3.8 Normal operation with successful outcome.....                            | 9  |
+| 2.4 Exceptional procedures or unsuccessful outcome.....                        | 9  |
+| 2.4.1 Operation in a PLMN that is unable to support the Charging Service ..... | 9  |
+| 2.4.2 Charging when the MS is switched off or out of coverage .....            | 9  |
+| 2.4.3 Operation with a MS unable to support AoC .....                          | 9  |
+| 2.5 Alternate procedures .....                                                 | 9  |
+| 2.6 Interactions with other supplementary services .....                       | 9  |
+| 2.6.1 SCUDIF .....                                                             | 9  |
+| 2.6.2 Other supplementary services .....                                       | 9  |
+| 2.7 Interworking considerations.....                                           | 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.
+
+# --- 0 Scope
+
+The present document describes the supplementary services belonging to the group Charging Supplementary Services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004 [2].
+
+Charging services are the supplementary services associated with charging aspects. The group of supplementary services Charging Supplementary Services comprises two services:
+
+- Advice of Charge (Information) - clause 1;
+- Advice of Charge (Charging) - clause 2.
+
+Advice of Charge (AoC) supplementary services will use the Charge Advice Information described in 22.024 [3].
+
+In principle, the same type of Mobile Station (MS) can be used for both services of Advice of Charge (AoC), except where the application demands special features - e.g. the payment mechanism in a payphone.
+
+Only one of these services may be subscribed to at any one time.
+
+## 0.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] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.004: "General on supplementary services".
+- [3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".
+- [4] 3GPP TS 22.135: "Multicall stage 1".
+- [5] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in TS 21.905 [1].
+
+# --- 1 Advice Of Charge (Information) (AoCI)
+
+## 1.1 Definition
+
+This service permits MS to display an accurate estimate the size of the bill which will eventually be levied in the Home PLMN.
+
+## 1.2 Description
+
+### 1.2.1 Description
+
+This supplementary service provides the MS with the information to produce an estimate of the cost of the service used. Charges are indicated for the call(s) in progress when mobile originated or for the roaming leg only when mobile terminated. Any charges for non-call related transactions, and for certain supplementary services, such as Call Forwarding are not indicated.
+
+The MS will receive at the beginning of each call (and as necessary during the call) a message, the Charge Advice Information. This message contains the elements which together define the rate at which the call is to be charged, time dependence, data dependence and for unit increments - see TS 22.024 [3].
+
+The MS shall still indicate appropriate charges even when roaming, based on Home PLMN units.
+
+Where applicable, the volume charge for Packet data service, in addition to the normal time dependent and incremental charges, shall be indicated.
+
+To indicate the charge per call the Mobile station shall display the units consumed so far during the present call(s) and maintain this value until the MS is switched off or a new call set-up is attempted.
+
+Where required to indicate the total accumulated charge, the MS shall be able to display, and the SIM/USIM shall store in the ACM, the running cumulative unit charge. This value must be stored securely, and all reasonable steps shall be taken to ensure that the written value cannot be interrupted, reset or corrupted (except resetting under control of the unblocking key).
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in TS 22.004 [2].
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.1 Provision
+
+This supplementary service will be provided after prearrangement with the service provider.
+
+### 1.3.2 Withdrawal
+
+This service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 1.3.5 Activation
+
+This supplementary service will be activated by the service provider as a result of provision.
+
+### 1.3.6 Deactivation
+
+This supplementary service will be deactivated by the service provider as a result of withdrawal.
+
+### 1.3.7 Invocation
+
+This supplementary service will be automatically invoked by the network for the use of all applicable telecommunications services.
+
+### 1.3.8 Normal operation with successful outcome
+
+For every applicable usage of telecommunications services, the served MS will be provided with charging information.
+
+The MS shall send to the network a confirmation of receipt of this information.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+### 1.4.1 Operation in a PLMN that is unable to support AoC
+
+Since AoC (Information) is used only to provide an indication to the user, even if the network is unable to support AoC, calls may still be set up as normal, only the AoC indication will not be given. For this reason charges incurred on a network that is unable to support AoC will not be shown on the AoC indicator.
+
+### 1.4.2 AoC when MS is switched off or out of coverage
+
+No AoC information is given by the network.
+
+### 1.4.3 Operation with a MS unable to support AoC
+
+Since AoC (Information) is used only to provide an indication to the user, even if the ME is unable to support AoC, calls may still be set up as normal, only no AoC information will be provided to the user.
+
+## 1.5 Alternate procedures
+
+None identified.
+
+## 1.6 Interactions with other supplementary services
+
+### 1.6.1 SCUDIF
+
+When the MS requires a bearer change, e.g. from Audio to Video or vice versa, the SCUDIF Mode modify procedure is performed as described in TS 23.172 [5]. Depending on the operator's policy, the success of the procedure may trigger a Facility message to convey new values for the CAI parameters. On receipt of new CAI values triggered by a service change based on the SCUDIF supplementary service, the MS shall reset CDUR and continue incrementing the CCM using the new CAI parameters. The MS shall add initial units to the CCM and measure units on a time basis using the new values.
+
+### 1.6.2 Other supplementary services
+
+No interaction.
+
+Invocation of this supplementary service does not prevent use of any other Supplementary Service.
+
+## 8.2 Multicall
+
+See TS 22.135 [4].
+
+## 1.7 Interworking considerations
+
+When interworking with PSPDN, a volume related charge may be incurred, as described in TS 22.024 [3].
+
+# --- 2 Advice Of Charge (Charging) (AoCC)
+
+## 2.1 Definition
+
+This service provides the means by which the MS may indicate the charge that will be made for the use of telecommunication services. It is intended for applications where the user is generally not the subscriber but is known to the subscriber, and where the user pays the subscriber, rather than the Service Provider.
+
+The charge information is based as closely as possible on the charge that will be levied on the subscriber's bill in the Home PLMN. Where this charge cannot be stored in the MS, use of the telecommunications service shall be prevented as described below.
+
+## 2.2 Description
+
+### 2.2.1 Description
+
+This supplementary service provides the MS with the information to produce an estimate of the cost of the service used. Charges are indicated for the call(s) in progress when mobile originated or for the roaming leg only when mobile terminated. Any charges for non-call related transactions, and for certain supplementary services, such as Call Forwarding are not indicated.
+
+The MS will receive at the beginning of each call (and as necessary during the call) a message, the Charge Advice Information. This message contains the elements which together define the rate at which the call is to be charged, time dependence, data dependence and for unit increments - see TS 22.024 [3].
+
+The MS shall still indicate appropriate charges even when roaming, based on Home PLMN units.
+
+Where applicable, the volume charge for Packet data service, in addition to the normal time dependent and incremental charges, shall be indicated.
+
+To indicate the charge per call the Mobile station shall display the units consumed so far during the present call(s) and maintain this value until the MS is switched off or a new call set-up is attempted.
+
+Where required to indicate the total accumulated charge, the MS shall be able to display, and the SIM/USIM shall store in the ACM, the running cumulative unit charge. This value must be stored securely, and all reasonable steps shall be taken to ensure that the written value cannot be interrupted, reset or corrupted (except resetting under control of the unblocking key).
+
+### 2.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in TS 22.004 [2].
+
+## 2.3 Normal procedures with successful outcome
+
+### 2.3.1 Provision
+
+This supplementary service will be provided after pre-arrangement with the service provider.
+
+### 2.3.2 Withdrawal
+
+This service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 2.3.5 Activation
+
+This supplementary service will be activated by the service provider as a result of provision.
+
+### 2.3.6 Deactivation
+
+This supplementary service will be deactivated by the service provider as a result of withdrawal.
+
+### 2.3.7 Invocation
+
+This supplementary service will be automatically invoked by the network for the use of all applicable telecommunications services.
+
+### 2.3.8 Normal operation with successful outcome
+
+For every applicable usage of telecommunication services, the served MS will be provided with charging information.
+
+The MS shall send to the network a confirmation of receipt of this information.
+
+## 2.4 Exceptional procedures or unsuccessful outcome
+
+### 2.4.1 Operation in a PLMN that is unable to support the Charging Service
+
+If the local PLMN is unable to support this service, all chargeable calls shall be prevented. This is determined either by the use of an HLR list of VPLMNs which support the service, or by the HLR interrogating the VPLMN. Prevention is achieved by refusing a Location Update Request to the VPLMN that does not support the service.
+
+### 2.4.2 Charging when the MS is switched off or out of coverage
+
+No AoC information is given by the network.
+
+### 2.4.3 Operation with a MS unable to support AoC
+
+If the MS does not support AoC, no advice of charge information will be provided to the user. Any calls attempted to be set up will be quickly terminated, once the network has failed to receive a positive acknowledgement of receipt of the Charge Advice Information, within a suitable time.
+
+## 2.5 Alternate procedures
+
+None identified.
+
+## 2.6 Interactions with other supplementary services
+
+### 2.6.1 SCUDIF
+
+When the MS requires a bearer change, e.g. from Audio to Video or vice versa, the SCUDIF Mode modify procedure is performed as described in TS 23.172 [5]. Depending on the operator's policy, the success of the procedure may trigger a Facility message to convey new values for the CAI parameters. On receipt of new CAI values triggered by a service change based on the SCUDIF supplementary service, the MS shall reset CDUR and continue incrementing the CCM using the new CAI parameters. The MS shall add initial units to the CCM and measure units on a time basis using the new values.
+
+### 2.6.2 Other supplementary services
+
+No interaction.
+
+Invocation of this supplementary service does not prevent use of any other Supplementary Service, but in certain cases no charging information will be indicated. In this case, the subscriber should not subscribe to those Supplementary Services which need to be charged for, thereby inhibiting their use by another user.
+
+## 2.7 Interworking considerations
+
+When interworking with PSPDN, a volume related charge may be incurred, as described in TS 22.024 [3].
+
+# Annex A (informative): Change history
+
+| Change history |           |           |           |     |     |       |     |                                 |        |        |                   |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|---------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                 | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.86 |     |     |       |     | Transferred to 3GPP SA1         | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.085    |     |     | R99   |     | Transferred to 3GPP SA1         |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99633  | 22.086    | 001 |     | R99   | D   | Editorial changes for alignment | 3.0.0  | 3.1.0  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.085    |     |     | Rel-4 |     | Transferred to 3GPP Release 4   | 3.1.0  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.085    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5      | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.085    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6     | 5.0.0  | 6.0.0  |                   |
+| SP-28          | SP-050212 | S1-050399 | 22.086    | 004 | -   | Rel-6 | A   | AoC for SCUDIF                  | 6.0.0  | 6.1.0  | TEI               |
+| SP-36          |           |           | 22.086    |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7     | 6.1.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8     | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-9 by MCC         | 8.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)  | 9.0.0  | 10.0.0 |                   |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-11 by MCC        | 10.0.0 | 11.0.0 |                   |

marked/Rel-11/22_series/22087/raw.md

@@ -0,0 +1,464 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                  |    |
+|--------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                   | 5  |
+| 1 Scope.....                                                                                     | 6  |
+| 2 References.....                                                                                | 6  |
+| 3 Definitions and Abbreviations .....                                                            | 6  |
+| 3.1 Definitions.....                                                                             | 6  |
+| 3.2 Abbreviations .....                                                                          | 6  |
+| 4 Description.....                                                                               | 7  |
+| 4.1 Description .....                                                                            | 7  |
+| 4.2 Applicability to telecommunication services.....                                             | 7  |
+| 5 Normal procedures with successful outcome.....                                                 | 7  |
+| 5.1 Provision.....                                                                               | 7  |
+| 5.2 Withdrawal.....                                                                              | 7  |
+| 5.3 Registration and Erasure .....                                                               | 8  |
+| 5.4 Activation and Deactivation.....                                                             | 8  |
+| 5.5 Invocation.....                                                                              | 8  |
+| 5.6 Interrogation.....                                                                           | 8  |
+| 5.7 Handling of UUS services.....                                                                | 8  |
+| 5.7.1 Activation .....                                                                           | 8  |
+| 5.7.1.1 Service 1 .....                                                                          | 8  |
+| 5.7.1.2 Service 2 .....                                                                          | 9  |
+| 5.7.1.3 Service 3 .....                                                                          | 9  |
+| 5.7.1.4 "UUS required" request .....                                                             | 9  |
+| 5.7.2 Invocation and operation.....                                                              | 9  |
+| 5.7.2.1 Service 1 .....                                                                          | 10 |
+| 5.7.2.2 Service 2 .....                                                                          | 10 |
+| 5.7.2.3 Service 3 .....                                                                          | 10 |
+| 5.7.2.4 Charging requirements.....                                                               | 10 |
+| 6 Exceptional procedures or unsuccessful outcome .....                                           | 10 |
+| 6.1 Provision and Withdrawal.....                                                                | 10 |
+| 6.2 Registration and Erasure .....                                                               | 10 |
+| 6.3 Handling of UUS services.....                                                                | 10 |
+| 6.3.1 Activation .....                                                                           | 10 |
+| 6.3.2 Invocation.....                                                                            | 11 |
+| 7 Interactions with other supplementary services .....                                           | 11 |
+| 7.1 Call forwarding unconditional .....                                                          | 11 |
+| 7.2 Call forwarding on mobile subscriber busy .....                                              | 11 |
+| 7.3 Call forwarding on no reply .....                                                            | 11 |
+| 7.4 Call forwarding on mobile subscriber not reachable .....                                     | 12 |
+| 7.5 Call waiting .....                                                                           | 12 |
+| 7.6 Call hold.....                                                                               | 12 |
+| 7.7 Completion of calls to busy subscribers.....                                                 | 12 |
+| 7.8 Explicit call transfer .....                                                                 | 12 |
+| 7.9 Multi party service .....                                                                    | 12 |
+| 7.10 Advice of charge .....                                                                      | 12 |
+| 7.11 Barring of outgoing calls.....                                                              | 13 |
+| 7.12 Barring of outgoing international calls.....                                                | 13 |
+| 7.13 Barring of outgoing international calls except those directed to the home PLMN country..... | 13 |
+| 7.14 Barring of incoming calls.....                                                              | 13 |
+| 7.15 Barring of incoming calls when roaming outside the home PLMN country .....                  | 13 |
+| 7.16 Call Deflection .....                                                                       | 13 |
+| 8 Interactions with other network features.....                                                  | 13 |
+| 8.1 Support of Optimal Routeing .....                                                            | 13 |
+| 8.2 Multicall .....                                                                              | 13 |
+
+9 Interworking considerations..... 13
+
+**Annex A (informative): Deviations of the 3GPP UUS supplementary service from the ISDN service ..... 14**
+
+Annex B: Change history ..... 15
+
+# --- 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 User-to-User Signalling (UUS) supplementary service allows a mobile subscriber to send/receive a limited amount of information to/from another PLMN or ISDN subscriber over the signalling channel in association with a call to the other subscriber.
+
+# --- 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 TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.004: "General on supplementary services.
+- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS).
+- [4] 3GPP TS 22.135: "Multicall stage 1".
+
+# --- 3 Definitions and Abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this TS, the following definitions apply:
+
+**User-to-User Information (UUI):** The information transferred by using the UUS supplementary service.
+
+**UUS service:** The UUS services (Service 1, 2 and 3) are components of the UUS supplementary service. If the UUS supplementary service is provided to a subscriber, she can handle the UUS services independently within a call.
+
+**Served subscriber:** The subscriber who has a provision of the UUS supplementary service and who activates the UUS supplementary service. For service 1 and 2 the served subscriber is always the calling subscriber, for service 3 either the calling or the called subscriber can be the served subscriber.
+
+**Remote party:** For service 1 and 2 the remote party is the called party of a call to which the UUS supplementary service is activated by the served subscriber. For service 3 the remote party can be either the called or the calling party of an established call to whom the use of the UUS supplementary service is requested by the served subscriber.
+
+## 3.2 Abbreviations
+
+For the purposes of this TS the following abbreviations apply.
+
+|            |                          |
+|------------|--------------------------|
+| <b>UUS</b> | User-to-User Signalling  |
+| <b>UUI</b> | User-to-User Information |
+
+Further GSM related abbreviations are listed in TS 21.905 [1].
+
+# --- 4 Description
+
+## 4.1 Description
+
+The UUS supplementary service allows the served subscriber to send/receive a limited amount of subscriber generated information to/from another user in association with a call to the user. This information shall be passed transparently (i.e. without modification of contents) through the network. Normally, the network shall not interpret or act upon this information.
+
+The served subscriber can send and receive UUI in different phases of the call depending on the service(s) to which the subscriber subscribes. These services are:
+
+- Service 1: UUI can be sent and received during the origination and termination of a call, with UUI embedded within call control messages. The service 1 can be activated implicit by inserting UUI when set-up a call or explicit with an appropriate procedure.
+- Service 2: UUI can be sent and received after the served subscriber has received an indication that the remote party is being informed of the call and prior to the establishment of the connection. UUI sent by the served subscriber prior to receiving the acceptance of the call by the remote party, may as a network option be delivered to the remote party after the call has been established. The service 2 shall be activated explicitly.
+- Service 3: User-to-user-information can be sent and received only while the connection is established. The service 3 shall be activated explicitly.
+
+Service 1, service 2 and service 3 shall allow the transmission of UUI with the maximum length of 128 octets per message.
+
+## 4.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in TS 22.004 [2].
+
+# --- 5 Normal procedures with successful outcome
+
+## 5.1 Provision
+
+The UUS supplementary service shall be provided to the served subscriber after pre-arrangement with the service provider. The remote party needs no subscription of the UUS supplementary service.
+
+NOTE: The remote party is able to send UUI without provision of the UUS supplementary service when the service is activated against her by the served subscriber.
+
+As a service provider option, one or any combination of the following shall be provided:
+
+- service 1 (implicitly requested and explicitly requested);
+- service 2;
+- service 3.
+
+## 5.2 Withdrawal
+
+The UUS supplementary service and several UUS services shall be withdrawn by the service provider upon the subscriber's request or for service providers reasons.
+
+The supplementary service UUS shall be withdrawn if all UUS services provided to the served subscriber are withdrawn.
+
+## 5.3 Registration and Erasure
+
+not applicable.
+
+## 5.4 Activation and Deactivation
+
+The UUS supplementary service shall be activated by the service provider as a result of provision and deactivated as a result of withdrawal.
+
+## 5.5 Invocation
+
+The UUS supplementary service is invoked if at least one UUS service is activated by the served subscriber.
+
+## 5.6 Interrogation
+
+not applicable.
+
+## 5.7 Handling of UUS services
+
+### 5.7.1 Activation
+
+UUS service is activated when:
+
+- activation is implicitly requested (for service 1); or
+- activation is explicitly requested (for service 1, service 2 and service 3) and is accepted by the remote party.
+
+Depending on the served subscriber subscription to the UUS supplementary service and the provision of the UUS services by the service provider, service 1 implicit, service 1 explicit, service 2 and service 3 can be activated individually or in combination. Service 1 implicit and service 1 explicit cannot be simultaneously active.
+
+Once an UUS service is activated the network shall accept UUI from either subscriber in the call, according to the service that has been activated.
+
+The network shall confirm the explicit activation of a UUS service (service 1, 2 and 3) to the served subscriber. This confirmation shall be preceded by an end-to-end check by the network for service availability.
+
+The network shall interrogate the remote party and check for the availability of the UUS service on the remote party's side. The mobile station shall confirm the requested services if it is able to handle the UUS service. The remote party shall not have the possibility to confirm or reject the request for the UUS service on a per call basis. No response from the remote party shall be taken by the network as a rejection of the request for the UUS service.
+
+NOTE: Nevertheless the remote party may restrict the use of a UUS service by pre-programming of the mobile station to reject incoming UUS activation requests.
+
+The network shall explicitly indicate to the calling mobile subscriber whether or not the requested service has been successfully activated.
+
+#### 5.7.1.1 Service 1
+
+UUS service 1 shall be activated by the calling mobile subscriber when originating a call if UUI transfer is desired in either direction.
+
+Service 1 is automatically deactivated when the call is terminated.
+
+Service 1 can be activated by means of an implicit activation request or an explicit activation request.
+
+##### **Implicit activation:**
+
+Service 1 is implicitly activated when UUI is included when originating a call.
+
+When service 1 is implicitly activated, service 1 is active for the call, i.e. the remote party is not required to send a response to the implicit activation request. However, the remote party can include UUI in the call response.
+
+##### **Explicit activation:**
+
+The UUS service 1 shall be activated explicitly by using of the procedure defined in TS 22.030 [3].
+
+The served mobile subscriber shall be given an explicit response (acceptance or rejection) to an explicit activation request. An explicit activation request can include UUI.
+
+When service 1 is explicitly requested, the remote party can include UUI when accepting the activation request for the UUS supplementary service.
+
+#### 5.7.1.2 Service 2
+
+The UUS service 2 shall be activated by using of the procedure defined in TS 22.030 [3].
+
+Service 2 shall be activated by the served subscriber when originating a call, if UUI transfer is desired in either direction.
+
+Service 2 shall be explicitly requested. The served mobile subscriber shall be given an explicit response (acceptance or rejection) to an explicit activation request.
+
+Service 2 is automatically deactivated when the called subscriber is no longer being informed of the call, i.e. if the call is established or released.
+
+#### 5.7.1.3 Service 3
+
+The served subscriber can explicit request the activation of service 3 when a call is originated or after the connection has been established by using the procedure defined in TS 22.030 [3]. The request for the UUS service 3 shall be accepted from the remote party in order to activate the UUS supplementary service. The served user shall be given an explicit response (acceptance or rejection) to the explicit activation request.
+
+Service 3 is automatically deactivated when the call is no longer established.
+
+#### 5.7.1.4 "UUS required" request
+
+When a call is originated, the calling subscriber can specify whether the requested UUS service(s) is (are) required for the call, i.e. if the call should be completed or not if UUI cannot be passed. If the "UUI-required" indication is given by the subscriber, the call shall not be completed if UUI cannot be passed to the called subscriber. If the "UUI-not-required" indication is given by the subscriber, the call will be completed even if UUI cannot be passed. If service 1 is implicitly requested or if service 3 is requested during the call, it cannot be requested as "UUI-required".
+
+### 5.7.2 Invocation and operation
+
+If activated by the served subscriber a UUS service shall be invoked when UUI is sent by either subscriber to the network.
+
+When a subscriber sends UUI the network shall not confirm its delivery to the subscriber.
+
+For service 2 and 3, when sending a UUI message, the subscriber can indicate that the subscriber will send further UUI associated with this UUI message. This indication shall be given to the receiving subscriber.
+
+When sending a UUI message, the subscriber may indicate the use of particular user protocol associated with the UUI message. This indication shall be given to the receiving subscriber. The identification of, and the use of, user protocols is outside of this standard.
+
+#### 5.7.2.1 Service 1
+
+A PLMN subscriber can transfer UUI when originating a call. When service 1 has been activated, either subscriber can include UUI when accepting, rejecting, or terminating a call.
+
+NOTE: It is possible for a calling subscriber to invoke the UUS service 1 with a call set-up and terminate the call before the connection is established.
+
+#### 5.7.2.2 Service 2
+
+Any time between activation of service 2 and connection is established, either subscriber can transfer up to 2 UUI messages in each direction to the other subscriber involved in the call.
+
+#### 5.7.2.3 Service 3
+
+After service 3 has been activated, either subscriber can transfer UUI to the other subscriber on the call after the connection has been established.
+
+NOTE: The amount of UUI messages that can be transferred with service 3 shall be defined.
+
+#### 5.7.2.4 Charging requirements
+
+The served subscriber shall be charged according to the number of UUI messages transferred in either direction. When charging for UUI the destination (e.g. international calls, diverted calls) of the related call shall not be considered.
+
+It shall be possible to charge for the invocation of the UUS supplementary service even if there are no other call charges.
+
+# --- 6 Exceptional procedures or unsuccessful outcome
+
+## 6.1 Provision and Withdrawal
+
+No exceptional procedures.
+
+## 6.2 Registration and Erasure
+
+not applicable.
+
+## 6.3 Handling of UUS services
+
+### 6.3.1 Activation
+
+If the network cannot accept an implicit request for the activation of UUS service 1, no notification shall be given to the subscriber.
+
+In all other cases, if the network cannot accept a request for the activation of a UUS service, the network shall reject the activation. In addition, the network shall indicate which of service 1, service 2 and/or service 3 have been rejected. For the rejection of the activation request the following reasons may be possible:
+
+- service not subscribed to;
+- necessary signalling connectivity does not exist between sending and receiving subscribers;
+- conflicting situation with other supplementary service (e.g. CUG, incoming call barring);
+- service is already active;
+- network congestion.
+
+### 6.3.2 Invocation
+
+The subscriber may not be able to interpret incoming UUI. In such situations, the user can discard this information without disrupting normal call handling. No specific signalling is provided by the network to accommodate this situation.
+
+Under circumstances of network congestion or failure, the network may discard services 2 and 3 UUI.
+
+# --- 7 Interactions with other supplementary services
+
+## 7.1 Call forwarding unconditional
+
+No impact
+
+NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service.
+
+## 7.2 Call forwarding on mobile subscriber busy
+
+If call forwarding on mobile subscriber busy is invoked as a result of a network determined user busy condition (NDUB) of the called subscriber, any UUI and UUS request accompanies the call set-up request shall be forwarded with the call
+
+If call forwarding on mobile subscriber busy is invoked as a result of an user determined user busy condition (UDUB) the following cases shall be distinguished:
+
+- If the UDUB condition is met before alerting any UUI and UUS request accompanies the call set-up request shall be forwarded with the call.
+- If the UDUB condition is met after alerting the interactions as defined for call forwarding on no reply shall apply.
+
+UUI included in a UDUB request by the forwarding subscriber shall be ignored by the network.
+
+NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service.
+
+## 7.3 Call forwarding on no reply
+
+### Service 1:
+
+If UUS service 1 is implicitly requested to the forwarding subscriber the UUI shall be transferred to the forwarded-to party after the invocation of CFNRy.
+
+If UUS service 1 is explicitly requested with the option "UUS required" to a called subscriber who has CFNRy active and operative and the no-reply condition timer expires, the call shall be released.
+
+If UUS service 1 is explicitly requested with the option "UUS not required" to a called subscriber who has CFNRy active and operative, CFNRy shall be invoked. If the called subscriber has confirmed the UUS service 1 request prior to the invocation of CFNRy, the UUI and the UUS request shall be transferred to the forwarded-to party. Otherwise the UUI and the UUS request shall not be forwarded with the call.
+
+### Service 2:
+
+If UUS service 2 is requested with the option "UUS not required" to a called subscriber who has CFNRy active and operative, CFNRy shall be invoked but no UUS activation request will be given to the forwarded-to subscriber.
+
+If UUS service 2 is requested with the option "UUS required" to a called subscriber who has CFNRy active and operative, CFNRy shall not be invoked.
+
+### Service 3:
+
+Any activation request for UUS service 3 that accompanies the call set-up request shall be forwarded with the call.
+
+NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service.
+
+## 7.4 Call forwarding on mobile subscriber not reachable
+
+No impact
+
+NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service.
+
+## 7.5 Call waiting
+
+UUI for the operation of UUS service 1 included in the call request shall be delivered with the call waiting indication to the called subscriber.
+
+There are no interactions with service 2 and service 3.
+
+## 7.6 Call hold
+
+A subscriber who has invoked the Call Hold supplementary service may send or receive UUI to/from both the active and the held party. If the served subscriber has an active and a held call the mobile station shall indicate which party has sent a received UUI message.
+
+## 7.7 Completion of calls to busy subscribers
+
+Requests for the activation of a UUS service contained in the original call request shall be stored with the request for the invocation of the CCBS supplementary service.
+
+The network shall also store any UUI containing in the original call request and use this stored UUI in the CCBS call.
+
+## 7.8 Explicit call transfer
+
+When calls are transferred as a result of invocation of the explicit call transfer supplementary service, UUS services activated on either of the calls prior to the invocation of the explicit call transfer supplementary service shall be automatically deactivated by the network.
+
+No specific notification shall be sent to the involved subscribers when the UUS services are no longer activated.
+
+The subscribers involved in the transferred call may request the activation of service 3 again, if required.
+
+## 7.9 Multi party service
+
+During a MPTY the MPTY-Manager can send and receive UUI to/from each remote party separately. The mobile station of the multi party manager shall indicate from which remote party a received UUI message was sent.
+
+UUI shall not be transferred between remote parties.
+
+## 7.10 Advice of charge
+
+No impact.
+
+NOTE: The Advice of Charge services may not provide any information concerning charges for the use of the UUS supplementary service.
+
+## 7.11 Barring of outgoing calls
+
+no impact
+
+## 7.12 Barring of outgoing international calls
+
+no impact
+
+## 7.13 Barring of outgoing international calls except those directed to the home PLMN country
+
+no impact
+
+## 7.14 Barring of incoming calls
+
+no impact.
+
+## 7.15 Barring of incoming calls when roaming outside the home PLMN country
+
+no impact.
+
+## 7.16 Call Deflection
+
+If Call Deflection is invoked before alerting the same interactions as for Call forwarding on mobile subscriber busy shall apply.
+
+If Call Deflection is invoked after alerting the same interactions as for Call forwarding on no reply shall apply.
+
+# --- 8 Interactions with other network features
+
+## 8.1 Support of Optimal Routeing
+
+The invocation of Optimal Routeing in case of late call forwarding shall have no impact on the interactions of UUS with the call forwarding supplementary services as defined in section 7.
+
+## 8.2 Multicall
+
+See TS 22.135 [4].
+
+# --- 9 Interworking considerations
+
+The UUS supplementary service can be delivered only when both subscribers' networks provide a means of conveying the UUI.
+
+Some networks may support the transmission of UUI with a maximum length of only 32 octets per message for service 1. In the interworking case only the first 32 octets of UUI with more than 32 octets per message shall be transferred. No notification about the limitation of the UUI shall be given to any subscriber.
+
+# --- Annex A (informative): Deviations of the 3GPP UUS supplementary service from the ISDN service
+
+The ISDN service UUS allows as a network option the transfer of UUI with a maximum length of 32 octets for service 1. This option shall not be supported in PLMNs. However there is the possibility that networks using the phase 1 or phase 2 standard can support the UUS service 1 implicitly requested with 32 octets. These networks shall apply the rules defined in the section 8, Interworking considerations.
+
+In the 3GPP specification some charging requirement are defined. These requirements shall allow network operators to charge their subscribers for the use of and to prevent misuse of the UUS supplementary service.
+
+Because of the different handling of busy states in ISDN the interactions with call forwarding on mobile subscriber busy are different.
+
+The network option to allow forwarding of UUS requests and UUI only if the forwarding subscriber has the subscription of the relevant UUS service is not supported.
+
+The general principle of CCBS to retain all information of the original call set-up and reusing this information for the CCBS call shall also be valid for the UUS supplementary service. Therefore the UUI contained in the original call set-up shall be stored in network and reused in the CCBS call.
+
+# Annex B: Change history
+
+| Change history |           |           |           |     |     |       |     |                                                                          |        |        |                   |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|--------------------------------------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                                                          | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.87 |     |     |       |     | Transferred to 3GPP SA1                                                  | 7.1.0  |        |                   |
+| SA#04          |           |           | 22.087    |     |     | R99   |     | Transferred to 3GPP SA1                                                  |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99634  | 22.087    | 001 |     | R99   | D   | Editorial changes for alignment                                          | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-05          | SP-99450  | S1-99788  | 22.087    | 002 |     | R99   | B   | Multicall (This CR was wrongly marked as 22.086 and should be to 22.087) | 3.0.1  | 3.1.0  | Multicall         |
+| SP-11          | SP-010065 | S1-010258 | 22.087    |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                            | 3.1.0  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.087    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                               | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.087    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                              | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.087    |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                              | 6.0.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                              | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-9 by MCC                                                  | 8.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                           | 9.0.0  | 10.0.0 |                   |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-11 by MCC                                                 | 10.0.0 | 11.0.0 |                   |

marked/Rel-11/22_series/22088/raw.md

@@ -0,0 +1,580 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                   |    |
+|-------------------------------------------------------------------|----|
+| Foreword .....                                                    | 5  |
+| 0 Scope.....                                                      | 6  |
+| 0.1 References .....                                              | 6  |
+| 0.2 Abbreviations .....                                           | 7  |
+| 1 Barring of outgoing calls.....                                  | 7  |
+| 1.1 Definition .....                                              | 7  |
+| 1.2 General description .....                                     | 7  |
+| 1.2.1 Description .....                                           | 7  |
+| 1.2.2 Applicability to telecommunication services .....           | 8  |
+| 1.2.3 Terminology .....                                           | 8  |
+| 1.3 Normal procedures with successful outcome.....                | 8  |
+| 1.3.1 Provision.....                                              | 8  |
+| 1.3.2 Withdrawal .....                                            | 9  |
+| 1.3.3 Registration.....                                           | 9  |
+| 1.3.4 Erasure .....                                               | 9  |
+| 1.3.5 Activation .....                                            | 9  |
+| 1.3.6 Deactivation.....                                           | 10 |
+| 1.3.7 Invocation .....                                            | 10 |
+| 1.3.8 Normal operation with successful outcome.....               | 10 |
+| 1.3.11 Interrogation .....                                        | 10 |
+| 1.4 Exceptional procedures or unsuccessful outcome.....           | 11 |
+| 1.4.1 Provision.....                                              | 11 |
+| 1.4.2 Registration.....                                           | 11 |
+| 1.4.4 Activation .....                                            | 11 |
+| 1.4.5 Deactivation.....                                           | 11 |
+| 1.5 Alternate procedures .....                                    | 11 |
+| 1.6 Interactions with other supplementary services .....          | 12 |
+| 1.6.82.1 Call forwarding unconditional .....                      | 12 |
+| 1.6.82.2 Call forwarding on mobile subscriber busy .....          | 12 |
+| 1.6.82.3 Call forwarding on no reply .....                        | 12 |
+| 1.6.82.4 Call forwarding on mobile subscriber not reachable ..... | 12 |
+| 1.6.83.1 Call waiting.....                                        | 12 |
+| 1.6.83.2 Call hold.....                                           | 12 |
+| 1.6.84 MultiParty service .....                                   | 12 |
+| 1.6.85.1 Closed user group .....                                  | 12 |
+| 1.7 Interworking considerations.....                              | 12 |
+| 2 Barring of incoming calls.....                                  | 12 |
+| 2.1 Definition .....                                              | 12 |
+| 2.2 General description .....                                     | 13 |
+| 2.2.1 Description .....                                           | 13 |
+| 2.2.2 Applicability to telecommunication services .....           | 13 |
+| 2.2.3 Terminology .....                                           | 13 |
+| 2.3 Normal procedures with successful outcome.....                | 13 |
+| 2.3.1 Provision.....                                              | 13 |
+| 2.3.2 Withdrawal .....                                            | 14 |
+| 2.3.3 Registration.....                                           | 14 |
+| 2.3.4 Erasure .....                                               | 14 |
+| 2.3.5 Activation .....                                            | 14 |
+| 2.3.6 Deactivation.....                                           | 15 |
+| 2.3.7 Invocation .....                                            | 15 |
+| 2.3.8 Normal operation with successful outcome.....               | 15 |
+| 2.3.11 Interrogation .....                                        | 15 |
+| 2.4 Exceptional procedures or unsuccessful outcome.....           | 15 |
+| 2.4.2 Registration.....                                           | 15 |
+| 2.4.4 Activation .....                                            | 16 |
+| 2.4.5 Deactivation.....                                           | 16 |
+| 2.5 Alternate procedures .....                                    | 16 |
+
+2.6 Interactions with other supplementary services .....16  
+2.6.82.1 Call forwarding unconditional .....16  
+2.6.82.2 Call forwarding on mobile subscriber busy .....16  
+2.6.82.3 Call forwarding on no reply .....17  
+2.6.82.4 Call forwarding on mobile subscriber not reachable .....17  
+2.6.83.2 Call hold.....17  
+2.6.81.1 Calling Line Identification .....17  
+2.6.84 MultiParty service .....17  
+2.6.85.1 Closed user group .....17  
+2.7 Interworking considerations .....17  
+Annex A (informative): Change history..... 18
+
+# --- 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.
+
+# --- 0 Scope
+
+The present document describes the supplementary services belonging to the group Call Restriction Supplementary Services.
+
+The general aspects - including definitions and recommended provision - of the description of the supplementary services are given in 3GPP TS 22.004 [2].
+
+The Call Restriction supplementary services allow the possibility for a mobile subscriber to have barring of certain categories of outgoing or incoming calls at the mobile subscribers access.
+
+The group of Call Restriction Services includes two supplementary services:
+
+- barring of outgoing calls;
+- barring of incoming calls.
+
+By use of subscription options, the mobile subscriber can at provision time select a set of one or more barring programs to determine the categories of calls to be barred. The following categories are defined:
+
+- all outgoing calls;
+- outgoing international calls;
+- outgoing international calls except those directed to the home PLMN country;
+- all incoming calls;
+- incoming calls when roaming outside the home PLMN country.
+
+NOTE 1: Each category (barring program) is handled as a single supplementary service.
+
+NOTE 2: The call barring program "incoming calls when roaming outside the home PLMN country" is only relevant if as a general rule the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country.
+
+The barring services can be offered to a mobile subscriber with a password option allowing the activation and deactivation by the subscriber. One password per mobile subscriber is supported by the network for all barring services. For the definition of the password, the description of its use and its management, see 3GPP TS 22.004 [2].
+
+## 0.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] 3GPP TS 22.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.004: "General on supplementary services".
+- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
+- [5] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services - Stage 1".
+- [6] 3GPP TS 22.081: "Line Identification supplementary services - Stage 1".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TS 21.905 [1].
+
+# --- 1 Barring of outgoing calls
+
+## 1.1 Definition
+
+This service makes it possible for a mobile subscriber to have barring of certain categories of outgoing calls according to a barring program which is selected from a set of one or more barring programs chosen at provision time and is valid for all outgoing calls, or just those associated with a specific basic service group.
+
+The ability of the served mobile subscriber to receive calls and to set-up emergency calls remains unaffected.
+
+## 1.2 General description
+
+### 1.2.1 Description
+
+The mobile subscriber may determine by subscription of a set of one or more unique barring programs what kind of outgoing calls shall be barred.
+
+The following barring programs are defined:
+
+- 1) Barring of all outgoing calls;
+- 2) Barring of outgoing international calls;
+- 3) Barring of outgoing international calls except those directed to the home PLMN country.
+
+The PLMN will ensure that only one of the barring programs is active per basic service group. The activation of one specific barring program will override an already active one (i.e. the old one will be permanently deactivated).
+
+Description of contents of barring programs:
+
+#### **Barring of all outgoing calls:**
+
+With this barring program there are no outgoing set-up possibilities, except emergency calls.
+
+#### **Barring of outgoing international calls:**
+
+Outgoing call set-up possibilities exist only to subscribers of the PLMN(s) and the fixed network(s) of the country where the mobile subscriber is presently located. So the present PLMN may be the home PLMN or a visited PLMN, respectively the fixed network may be that of the home PLMN country or that of a visited PLMN country.
+
+NOTE 1: This definition implies that mobile subscribers, subscribed to a PLMN in the country in which the served mobile subscriber roams, can be called irrespective where they roam. On the other hand, mobile subscribers, subscribed to any PLMN in another country than the one in which the served mobile subscriber roams, cannot be called even if they roam in the same PLMN area as the served mobile subscriber.
+
+#### **Barring of all outgoing international calls except those directed to the home PLMN country:**
+
+Outgoing call set-up possibilities exist only to subscribers of the PLMN(s) and the fixed network(s) of the country where the mobile subscriber is presently located or to mobile subscribers of the home PLMN country of the served mobile subscriber and to subscribers of the fixed network(s) in the home PLMN country. So the present PLMN may be the home PLMN or a visited PLMN, respectively the fixed network may be that of the home PLMN country or that of a visited PLMN country.
+
+NOTE 2: This definition implies that mobile subscribers, subscribed to a PLMN in the country in which the served mobile subscriber roams or mobile subscribers subscribed to any PLMN in the same country as the served mobile subscriber home PLMN can be called irrespective where they roam. On the other hand, mobile subscribers, subscribed to any PLMN in another country than the one in which the served mobile subscriber roams and not belonging to the same country as the served mobile subscriber, cannot be called even if they roam in the same PLMN area as the served mobile subscriber or if they roam in the home PLMN country of the served mobile subscriber.
+
+In the case of SMS, this barring program shall prevent the subscriber from sending Short Messages using a Service Centre Address that is not part of the subscriber's home PLMN country numbering plan.
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004 [2].
+
+### 1.2.3 Terminology
+
+A barring program defines the subscribed barring condition and will determine the categories of calls to be barred.
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.1 Provision
+
+The supplementary service will be provided after pre-arrangement with the service provider. At provision, subscription options should be selected by the served mobile subscriber.
+
+The service can be offered with two subscription options.
+
+The first subscription option is the definition of the barring condition by a set of one or more barring programs. This subscription option applies to all basic services subscribed. Only one value can be selected for the barring condition.
+
+The second subscription option relates to the control of the call barring supplementary service(s). The subscriber may choose to have the control of the service(s) by use of a password, or may leave the control to the service provider. The value of this subscription option is valid collectively for all basic services and all call barring supplementary services to which the subscriber subscribes to.
+
+Subscription options are summarized below:
+
+| Subscription option         | Value                                                                                                                                                                                                                                                                                                                                                                                 |
+|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Barring condition           | <ul style="list-style-type: none"> <li>- barring program 1</li> <li>- barring program 2</li> <li>- barring program 3</li> <li>- barring program 1 and<br/>barring program 2</li> <li>- barring program 1 and<br/>barring program 3</li> <li>- barring program 2 and<br/>barring program 3</li> <li>- barring program 1 and<br/>barring program 2 and<br/>barring program 3</li> </ul> |
+| Control of barring services | <ul style="list-style-type: none"> <li>- by subscriber using password</li> <li>- by the service provider</li> </ul>                                                                                                                                                                                                                                                                   |
+
+NOTE: A service provider needs not offer the option "control of barring services" to his subscribers. However, the support of the password facility is mandatory in the network for visiting subscribers.
+
+### 1.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 1.3.3 Registration
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the service provider has to register a password at provision time. Furthermore the served mobile subscriber can change the password at any time by an appropriate control procedure which is described in 3GPP TS 22.004 [2].
+
+### 1.3.4 Erasure
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", a password can be erased as described in 3GPP TS 22.004.
+
+### 1.3.5 Activation
+
+Activation takes place with an appropriate control procedure by the subscriber or by the service provider. The activation of barring of outgoing calls does not affect any current communication. Only one barring program may be activated at a time for one basic service group.. The activation of a barring program will deactivate an already active one.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the supplementary service is activated if the subscriber provides the following information to the network:
+
+- password;
+- information as to whether all calls or calls of a specific basic service group should be barred.
+
+NOTE: If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".
+
+- selected barring program.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by service provider", the supplementary service cannot be activated by the subscriber. The activation has to be performed by the service provider.
+
+The activation status attached to different basic service groups can be modified separately.
+
+### 1.3.6 Deactivation
+
+Deactivation takes place by means of an appropriate control procedure by the subscriber, or by the service provider, or finally by activation of a new barring program for the same basic service group.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the supplementary service is deactivated if the subscriber provides the following information to the network:
+
+- password;
+- information as to whether barring of all calls or calls of a specific basic service group should be deactivated.
+
+NOTE: If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".
+
+- selected barring program (i.e. the code for one specific Outgoing Barring program given in 3GPP TS 22.030) or selected barring supplementary service (i.e. the code for Outgoing Barring Service or the code for All Barring Services given in 3GPP TS 22.030).
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by service provider", the supplementary service cannot be deactivated by the subscriber. The deactivation has to be performed by the service provider.
+
+### 1.3.7 Invocation
+
+The supplementary service is automatically invoked by the network upon a request for an outgoing call for a basic service not allowed by an active barring program for the corresponding basic service group. In the case of Short Message, only the Service Centre Address is relevant for the Call Barring service.
+
+### 1.3.8 Normal operation with successful outcome
+
+When barring of outgoing calls is active for a basic service group, each outgoing call set-up to a number not allowed by the barring program related to that basic service group will be refused by the network. In this case the served mobile subscriber will receive an indication that the call is not permitted and has been barred.
+
+When barring of outgoing calls is active, the ability of the served mobile subscriber to receive calls is not affected.
+
+When barring of outgoing calls is active, the ability of the served mobile subscriber to set-up emergency calls is not affected.
+
+### 1.3.11 Interrogation
+
+The subscriber shall by an appropriate control procedure be given the possibility to get a list of all basic service groups for which the given barring program is active (irrespective of whether it is operative or quiescent).
+
+In the situation when a subscriber has activated BOIC-exHC and is roaming in a PLMN not supporting this supplementary service, the local PLMN will return - as an answer to interrogation - the status "not supported".
+
+This information may be translated by the mobile station to inform the user about the replacement of BOIC-exHC with BOIC.
+
+If the served mobile subscriber wants to retrieve information from the local PLMN about the status of BOIC, she has to repeat the interrogation procedure with the supplementary service code for BOIC.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+### 1.4.1 Provision
+
+A PLMN which does not support the barring program "Barring of Outgoing International Calls Except Those Directed to the Home PLMN Country", shall replace this program with "Barring of Outgoing International Calls".
+
+### 1.4.2 Registration
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by service provider", an attempt to register a password will be denied and the served mobile subscriber should receive a notification.
+
+When the served mobile subscriber at provision time has selected the subscription option "control of barring services by the subscriber using password", the handling of incorrect password entry is described in 3GPP TS 22.004 [2].
+
+### 1.4.4 Activation
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by the service provider", an attempt to activate the barring services will be denied and the served mobile subscriber should receive a notification.
+
+When the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using a password", the handling of incorrect password entry is described in 3GPP TS 22.004.
+
+The barring of outgoing calls activation request must specify the basic service group and the selected barring program. If the subscriber does not completely specify for which basic service group (individual basic service group or all basic service groups) barring of outgoing calls is to be activated and the selected barring program, the network will reject the activation request with appropriate cause.
+
+NOTE 1: If no basic service group code is inserted by the user this is interpreted as the group "All Basic Services".
+
+NOTE 2: The group "all basic services" in the context of barring of outgoing calls means all except emergency calls.
+
+### 1.4.5 Deactivation
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the service provider", an attempt to deactivate will be denied and the served mobile subscriber should receive a notification.
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of the barring services by the subscriber using password", the handling of incorrect password entry is described in 3GPP TS 22.004 [2].
+
+The barring of outgoing calls deactivation request must specify the basic service group and the selected barring program (i.e. the code for one specific Outgoing Barring program given in 3GPP TS 22.030) or the selected barring supplementary service (i.e. the code for Outgoing Barring Service or the code for All Barring Services given in 3GPP TS 22.030). If the subscriber does not completely specify for which basic service group (individual basic service group or all basic service groups) barring of outgoing calls is to be deactivated and the selected barring program or supplementary service, the network will reject the deactivation request with appropriate cause.
+
+NOTE: If no basic service group code is inserted by the user this is interpreted as the group "All Basic Services".
+
+## 1.5 Alternate procedures
+
+None identified.
+
+## 1.6 Interactions with other supplementary services
+
+#### 1.6.82.1 Call forwarding unconditional
+
+See 3GPP TS 22.082 [4].
+
+#### 1.6.82.2 Call forwarding on mobile subscriber busy
+
+See 3GPP TS 22.082 [4].
+
+#### 1.6.82.3 Call forwarding on no reply
+
+See 3GPP TS 22.082 [4].
+
+#### 1.6.82.4 Call forwarding on mobile subscriber not reachable
+
+See 3GPP TS 22.082 [4].
+
+#### 1.6.83.1 Call waiting
+
+The activation of barring of outgoing calls at the calling mobile subscriber's side does not affect any currently waiting calls originated by the calling mobile subscriber.
+
+#### 1.6.83.2 Call hold
+
+If barring of outgoing calls is activated after a call hold is invoked on an outgoing call, the held call can be retrieved. Any new outgoing call to a number not allowed by the barring program is barred.
+
+### 1.6.84 MultiParty service
+
+See 3GPP TS 22.084 [5].
+
+#### 1.6.85.1 Closed user group
+
+Barring of outgoing calls takes precedence over the CUG restrictions. The activation of barring of outgoing calls during an outgoing call does not affect any current CUG call.
+
+## 1.7 Interworking considerations
+
+None identified.
+
+# --- 2 Barring of incoming calls
+
+## 2.1 Definition
+
+This service makes it possible for a mobile subscriber to have barring of certain categories of incoming calls according to a barring program which is selected from a set of one or more barring programs chosen at provision time and is valid for all incoming calls, or just those associated with a specific basic service group.
+
+The ability of the served mobile subscriber to set-up outgoing calls remains unaffected.
+
+## 2.2 General description
+
+### 2.2.1 Description
+
+The mobile subscriber may determine by subscription of a set of one or more barring programs what kind of incoming calls shall be barred.
+
+The following barring programs are defined:
+
+- 1) Barring of all incoming calls;
+- 2) Barring of incoming calls when roaming outside the home PLMN country;
+- 3) Anonymous Call Rejection.
+
+The barring programs 2) and 3) may be active simultaneously per basic service group, but can not be active simultaneously with the barring program 1) per basic service group. The PLMN will ensure that exclusive barring programs are not active simultaneously per basic service group. The activation of one specific barring program will override an already active exclusive one (i.e. the old one will be permanently deactivated).
+
+If barring programs 2) and 3) are active simultaneously for a specific basic service group, the barring program 2) shall apply when the called subscriber is roaming outside the home PLMN country.
+
+Description of contents of barring programs:
+
+#### **Barring of all incoming calls:**
+
+With this barring program there will be no set-up of incoming calls to the served subscriber.
+
+#### **Barring of incoming calls when roaming outside the home PLMN country:**
+
+With this barring program, calls which are terminated for the served subscriber will be barred if the subscriber is roaming outside the home PLMN country (i.e. the program is active and operative). The ability to receive calls in the home PLMN country remains unaffected (i.e. the program is active and quiescent).
+
+#### **Anonymous Call Rejection:**
+
+With this barring program, calls which are terminated for the served subscriber will be barred when the CLI presentation is restricted according to CLIR. The calls are barred regardless of the current state (e.g. free or busy) of the served subscriber's access. The calling user will be given an appropriate indication that the call has been rejected due to the application of the ACR supplementary service. Calls which are terminated for the served subscriber without a CLI or when CLI presentation is not available, is allowed, or is restricted by the network shall be allowed.
+
+### 2.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004 [2].
+
+### 2.2.3 Terminology
+
+A barring program defines the subscribed barring condition and will determine the categories of calls to be barred.
+
+## 2.3 Normal procedures with successful outcome
+
+### 2.3.1 Provision
+
+The supplementary service will be provided after pre-arrangement with the service provider. At provision, subscription options should be selected by the served mobile subscriber.
+
+The service can be offered with two subscription options.
+
+The first subscription option is the definition of the barring condition by a set of one or more barring programs. This subscription option applies to all basic services subscribed to. Only one value can be selected for the barring condition.
+
+The second subscription option relates to the control of the call barring supplementary service(s). The subscriber may choose to have the control of the service(s) by use of a password, or may leave the control to the service provider. The value of this subscription option is valid collectively for all basic services and all call barring supplementary services to which the subscriber subscribes to.
+
+Subscription options are summarized below:
+
+| Subscription option         | Value                                                                                                                                                     |
+|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Barring condition           | <ul style="list-style-type: none"> <li>- barring program 1</li> <li>- barring program 2</li> <li>- barring program 1 and<br/>barring program 2</li> </ul> |
+| Control of barring services | <ul style="list-style-type: none"> <li>- by subscriber using password</li> <li>- by the service provider</li> </ul>                                       |
+
+NOTE: A service provider needs not offer the option "control of barring services" to his subscribers. However, the support of the password facility is mandatory in the network for visiting subscribers.
+
+### 2.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 2.3.3 Registration
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the service provider has to register a password at provision time. Furthermore, the served mobile subscriber can change the password at any time by an appropriate control procedure which is described in 3GPP TS 22.004 [2].
+
+### 2.3.4 Erasure
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", a password can be erased as described in 3GPP TS 22.004 [2].
+
+### 2.3.5 Activation
+
+Activation takes place with an appropriate control procedure by the subscriber or by the service provider. The activation of barring of incoming calls does not affect any current communication. Only one barring program may be activated at a time for one basic service group. The activation of the barring program will deactivate an already active one.
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by subscriber using password", the supplementary service is activated if the subscriber provides the following information to the network:
+
+- password;
+- information as to whether all calls or calls of a specific basic service group should be barred.
+
+NOTE: If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".
+
+- selected barring program.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by service provider", the supplementary service cannot be activated by the subscriber. The activation has to be performed by the service provider.
+
+The activation status attached to different basic service groups can be modified separately.
+
+### 2.3.6 Deactivation
+
+Deactivation takes place by means of an appropriate control procedure by the subscriber, or by the service provider, or finally by activation of a new barring program for the same basic service group.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", the supplementary service is deactivated if the subscriber provides the following information to the network:
+
+- password;
+- information as to whether barring of all calls or calls of a specific basic service group should be deactivated.
+
+NOTE: If no Basic Service code is inserted by the user this is interpreted as the group "All Basic Services".
+
+- selected barring program (i.e. the code for one specific Incoming Barring program given in 3GPP TS 22.030) or selected barring supplementary service (i.e. the code for Incoming Barring Service or the code for All Barring Services given in 3GPP TS 22.030).
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by service provider", the supplementary service cannot be deactivated by the subscriber. The deactivation has to be performed by the service provider.
+
+### 2.3.7 Invocation
+
+The supplementary service is automatically invoked by the network upon a request for an incoming call for a basic service not allowed by an active and operative barring program for the corresponding basic service group.
+
+### 2.3.8 Normal operation with successful outcome
+
+When barring of incoming calls is active for a basic service group, each incoming call set-up not allowed by the barring program related to that basic service group will be refused by the network. In this case the calling mobile subscriber will receive an indication that the call is not permitted and has been barred.
+
+When barring of incoming calls is active, the ability of the served mobile subscriber to originate calls is not affected.
+
+### 2.3.11 Interrogation
+
+The subscriber shall by an appropriate control procedure be given the possibility to get a list of all basic service groups for which the given barring program is active (irrespective of whether it is operative or quiescent).
+
+## 2.4 Exceptional procedures or unsuccessful outcome
+
+### 2.4.2 Registration
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by service provider", an attempt to register a password will be denied and the served mobile subscriber should receive a notification.
+
+When the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by subscriber using password", the handling of incorrect password entry is as described in 3GPP TS 22.004 [2].
+
+### 2.4.4 Activation
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the service provider", an attempt to activate the barring services will be denied and the served mobile subscriber should receive a notification.
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the subscriber using password", the handling of incorrect password entry is as described in 3GPP TS 22.004 [2].
+
+The barring of incoming calls activation request must specify the basic service group and the selected barring program. If the subscriber does not completely specify for which basic service (individual basic service group or all basic service groups) barring of incoming calls is to be activated and the selected barring program, the network will reject the activation request with appropriate cause.
+
+NOTE: If no Basic Service group code is inserted by the user this is interpreted as the group "All Basic Services".
+
+### 2.4.5 Deactivation
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the service provider", an attempt to deactivate will be denied and the served mobile subscriber should receive a notification.
+
+If the served mobile subscriber, at provision time, has selected the subscription option "control of barring services by the subscriber using password", the handling of incorrect password entry is as described in 3GPP TS 22.004 [2].
+
+The barring of incoming calls deactivation request must specify the basic service group and the selected barring program (i.e. the code for one specific Incoming Barring program given in 3GPP TS 22.030) or the selected barring supplementary service (i.e. the code for Incoming Barring Service or the code for All Barring Services given in 3GPP TS 22.030). If the subscriber does not completely specify for which basic service group (individual basic service group or all basic service groups) barring of incoming calls is to be deactivated and the selected barring program or supplementary service, the network will reject the deactivation request with appropriate cause.
+
+NOTE: If no Basic Service group code is inserted by the user this is interpreted as the group "All Basic Services".
+
+## 2.5 Alternate procedures
+
+None identified.
+
+## 2.6 Interactions with other supplementary services
+
+#### 2.6.82.1 Call forwarding unconditional
+
+Except for ACR, see 3GPP TS 22.082 [4].
+
+For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding unconditional supplementary service, i.e. , a call which is terminated for the served subscriber when CLI presentation is restricted shall be rejected according to the ACR supplementary service.
+
+#### 2.6.82.2 Call forwarding on mobile subscriber busy
+
+Except for ACR, see 3GPP TS 22.082 [4].
+
+For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding on mobile subscriber busy supplementary service i.e. , a call which is terminated for the served subscriber when CLI is restricted shall be rejected according to the ACR supplementary service.
+
+#### 2.6.82.3 Call forwarding on no reply
+
+Except for ACR , see 3GPP TS 22.082 [4].
+
+For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding on no reply supplementary service, i.e., a call which is terminated for the served subscriber when CLI is restricted shall be rejected according to the ACR supplementary service.
+
+#### 2.6.82.4 Call forwarding on mobile subscriber not reachable
+
+Except for ACR, see 3GPP TS 22.082 [4].
+
+For ACR, if the served (forwarding) user has activated the ACR supplementary service, then the ACR supplementary service shall take precedence over the Call forwarding on mobile subscriber not reachable supplementary service i.e., a call which is terminated for the served subscriber when CLI is restricted shall be rejected according to the ACR supplementary service.
+
+#### 2.6.83.2 Call hold
+
+If barring of incoming calls is activated after a call hold is invoked on an incoming call, the held call can be retrieved. Any new incoming call not allowed by the barring program is barred.
+
+#### 2.6.81.1 Calling Line Identification
+
+If the called user has subscribed to the override category according to the CLIP supplementary service [6], then the CLIP supplementary service shall take precedence over the ACR supplementary service, i.e., a call which is terminated for the served subscriber when CLI is restricted shall be offered to the served subscriber.
+
+### 2.6.84 MultiParty service
+
+See 3GPP TS 22.084 [5].
+
+#### 2.6.85.1 Closed user group
+
+Except for ACR, barring of incoming calls takes precedence over the CUG restrictions. The activation of barring of incoming calls during an incoming call does not affect any current CUG call.
+
+If the called user has activated the ACR supplementary service, then if a closed user group call is offered to a called user belonging to the same closed user group, the closed user group call shall take precedence over the ACR supplementary service. If the called user also has the incoming access capability within the closed user group supplementary service, and if the offered call to the called user is also a non-closed user group call or a closed user group call to which the called party does not belong, the ACR supplementary service shall take precedence over the closed user group supplementary service.
+
+## 2.7 Interworking considerations
+
+None identified.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |           |          |     |        |     |                                              |        |        |                   |
+|----------------|-----------|-----------|-----------|----------|-----|--------|-----|----------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR       | Rev | Rel    | Cat | Subject/Comment                              | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.88 |          |     |        |     | Transferred to 3GPP SA1                      | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.088    |          |     | R99    |     | Transferred to 3GPP SA1                      |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99635  | 22.088    | 001      |     | R99    | D   | Editorial changes for alignment              | 3.0.0  | 3.0.1  | Editorial changes |
+| 22/05/00       |           |           | 22.088    | None     |     | R99    |     | Correction of wrong implementation of CR     | 3.0.1  | 3.0.2  |                   |
+| SP-11          | SP-010065 | S1-010258 | 22.088    |          |     | Rel-4  |     | Transferred to 3GPP Release 4                | 3.0.2  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.088    | 002      | -   | Rel-4  | F   | Editorial CR to correct terms and references | 4.0.0  | 4.1.0  | CORRECT           |
+| SP-16          | SP-020267 | S1-021043 | 22.088    |          |     | Rel-5  |     | Updated from Rel-4 to Rel5                   | 4.1.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.088    |          |     | Rel-6  |     | Updated from Rel-5 to Rel-6                  | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.088    |          |     | Rel-7  |     | Updated from Rel-6 to Rel-7                  | 6.0.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |          |     | Rel-8  |     | Updated from Rel-7 to Rel-8                  | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -        | -   | -      | -   | Updated to Rel-9 by MCC                      | 8.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -        | -   | -      | -   | Update to Rel-10 version (MCC)               | 9.0.0  | 10.0.0 |                   |
+| SP-52          | SP-110376 | S1-111434 | 22.088    | 000<br>3 | 4   | Rel-11 | B   | Addition of Anonymous Call Rejection as a SS | 10.0.0 | 11.0.0 | ACR_CS            |
+| SP-61          | SP-130456 | S1-134178 | 22.088    | 000<br>6 | 4   | Rel-11 | F   | SMSC Usage Restriction in Roaming            | 11.0.0 | 11.1.0 | TEI11             |

marked/Rel-11/22_series/22093/raw.md

@@ -0,0 +1,692 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                              |    |
+|--------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                               | 5  |
+| 1 Scope.....                                                                                                 | 5  |
+| 2 References.....                                                                                            | 6  |
+| 3 Definitions and abbreviations .....                                                                        | 6  |
+| 3.1 Definitions.....                                                                                         | 6  |
+| 3.2 Abbreviations .....                                                                                      | 7  |
+| 4 Description.....                                                                                           | 8  |
+| 4.1 Applicability to telecommunications services.....                                                        | 8  |
+| 5 Normal procedures with successful outcome.....                                                             | 8  |
+| 5.1 Provision.....                                                                                           | 8  |
+| 5.1.1 Subscriber A .....                                                                                     | 8  |
+| 5.1.2 Subscriber B .....                                                                                     | 8  |
+| 5.2 Withdrawal.....                                                                                          | 8  |
+| 5.3 Registration .....                                                                                       | 8  |
+| 5.4 Erasure.....                                                                                             | 8  |
+| 5.5 Activation.....                                                                                          | 9  |
+| 5.6 Deactivation .....                                                                                       | 9  |
+| 5.7 Invocation and operation.....                                                                            | 10 |
+| 5.8 Interrogation .....                                                                                      | 10 |
+| 6 Exceptional procedures or unsuccessful outcome .....                                                       | 10 |
+| 6.1 Registration .....                                                                                       | 10 |
+| 6.2 Erasure.....                                                                                             | 10 |
+| 6.3 Activation.....                                                                                          | 10 |
+| 6.4 Deactivation .....                                                                                       | 11 |
+| 6.5 Invocation and operation.....                                                                            | 11 |
+| 6.5.1 Exceptional situation at destination B's side: .....                                                   | 11 |
+| 6.5.2 Exceptional situation at subscriber A's side: .....                                                    | 13 |
+| 6.5.3 Exceptional situations in the network.....                                                             | 14 |
+| 7 Interaction with other supplementary services.....                                                         | 14 |
+| 7.1 Calling line identification presentation .....                                                           | 14 |
+| 7.2 Calling line identification restriction.....                                                             | 14 |
+| 7.3 Connected line identification presentation.....                                                          | 14 |
+| 7.4 Connected line identification restriction .....                                                          | 14 |
+| 7.5 Call Forwarding Unconditional (CFU) .....                                                                | 14 |
+| 7.6 Call Forwarding on mobile subscriber Busy (CFB).....                                                     | 14 |
+| 7.7 Call Forwarding on No Reply (CFNRy).....                                                                 | 15 |
+| 7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) .....                                         | 15 |
+| 7.9 Call waiting .....                                                                                       | 15 |
+| 7.10 Call hold.....                                                                                          | 15 |
+| 7.11 Multiparty services.....                                                                                | 15 |
+| 7.12 Closed user group.....                                                                                  | 16 |
+| 7.13 Advice of charge services .....                                                                         | 16 |
+| 7.14 Barring of All Outgoing Calls (BAOC).....                                                               | 16 |
+| 7.15 Barring of Outgoing International Calls (BOIC) .....                                                    | 16 |
+| 7.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)..... | 16 |
+| 7.17 Barring of All Incoming Calls (BAIC) .....                                                              | 16 |
+| 7.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam).....                    | 17 |
+| 7.19 Explicit call transfer .....                                                                            | 17 |
+| 7.20 Completion of calls to busy subscriber .....                                                            | 17 |
+| 7.21 Customised Applications for Mobile network Enhanced Logic (CAMEL) .....                                 | 17 |
+| 7.22 Support of Private Numbering Plan (SPNP).....                                                           | 18 |
+
+|                               |                                                                                    |           |
+|-------------------------------|------------------------------------------------------------------------------------|-----------|
+| 8                             | Mobility aspects .....                                                             | 18        |
+| <b>Annex A (informative):</b> | <b>Cross Phase compatibility .....</b>                                             | <b>19</b> |
+| A.1                           | Activation of a CCBS request.....                                                  | 19        |
+| A.2                           | CCBS Recall .....                                                                  | 19        |
+| A.3                           | Interrogation.....                                                                 | 19        |
+| A.4                           | Deactivation .....                                                                 | 19        |
+| <b>Annex B (normative):</b>   | <b>Roaming to non-supporting networks.....</b>                                     | <b>20</b> |
+| B.1                           | Roaming into networks or registering in network entities not supporting CCBS ..... | 20        |
+| B.1.1                         | Subscriber A may register in a non-supporting network or network entity .....      | 20        |
+| B.1.2                         | Destination B may register in a non-supporting network entity .....                | 20        |
+| <b>Annex C (informative):</b> | <b>Change history.....</b>                                                         | <b>21</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+This TS specifies the stage 1 description of Completion of Calls to Busy Subscriber (CCBS) from the subscriber's and user's points of view; in particular:
+
+- the procedures for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other 3GPP supplementary services.
+
+within the 3GPP system.
+
+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 specifies the stage 1 description of Completion of Calls to Busy Subscriber (CCBS) from the subscriber's and user's points of view; in particular:
+
+- the procedures for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other supplementary services;
+
+The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
+
+The charging principles applied to CCBS are outside of the scope of this specification.
+
+Any interactions with other networks not dealt with in the present document are outside the scope of the present document.
+
+# --- 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 TS 22.004: "General on supplementary services".
+- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [4] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [5] 3GPP TS 22.085: "Closed User Group (CUG) Supplementary Services - Stage 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definitions apply:
+
+**CCBS supplementary service:** is a service which enables a calling subscriber A, encountering a NDUB destination B, to have the call completed when the busy destination B becomes idle, without having to make a new call attempt.
+
+**CCBS busy on the A side:** is caused by the following condition:
+
+- while the CCBS recall timer T4 or the CCBS notification timer T10 is running or until the CCBS call is completed or the CCBS call fails.
+
+**CCBS busy on the B side:** is caused by the following conditions:
+
+- while the idle guard timer (T8) is running;
+- while there is CCBS recall pending (i.e. while the CCBS recall timer T9 is running).
+
+Subscriber A and Destination B is indicated as **idle** if there are no active calls, no calls on hold and no call waiting for the subscribers.
+
+Subscriber A and Destination B is indicated as **not reachable** if one of the conditions defined in TS 29.002 [4] apply (e.g. IMSI detach, no paging response, no location information in HLR).
+
+**CCBS recall:** an indication informing subscriber A that destination B is idle.
+
+**CCBS call:** a call set-up from subscriber A to destination B resulting from subscriber A's acceptance of a CCBS recall.
+
+**CCBS request:** A request by subscriber A against an NDUB destination B requesting that subscriber A be automatically informed when destination B becomes idle. The CCBS request shall be held in a CCBS queue pending the correct conditions for the CCBS request to be completed.
+
+**Destination B:** the entity addressed in the original call set up.
+
+**Subscriber A:** the subscriber that originated the call, activated a CCBS request and is uniquely identifiable for CCBS recall.
+
+**Suspended CCBS request:** a CCBS request which cannot be served even if destination B is idle, because subscriber A is CCBS busy, not reachable or is not idle and ignores the CCBS recall.
+
+**Resumed CCBS request:** a CCBS request which was suspended before and has become not suspended as a result of subscriber A becoming idle, not CCBS busy or reachable again.
+
+**Automatic deactivation:** an action by the network resulting in removal of all reference to a CCBS request without informing the subscriber. Automatic deactivation is performed after a successful CCBS procedure or for exceptional situations.
+
+### Timers at the originating side (A):
+
+**CCBS retention timer (T1):** this timer specifies the amount of time that the network retains the call information when the call encounters busy. The value shall be greater than 15 seconds. The upper limit of the CCBS retention timer is a network option.
+
+**CCBS service duration timer (T3):** the maximum time the CCBS request will be active within the network. The value of this period is a network option, in the range of 15 to 45 minutes.
+
+**CCBS recall timer (T4):** the maximum time the network will wait for a subscriber A response to a CCBS recall when subscriber A is idle. The value of this timer is a network option and shall be in the range 20 to 30 seconds.
+
+**CCBS notification timer (T10):** the maximum time the network will wait for a subscriber A response to a CCBS recall when subscriber A is not idle and not CCBS busy. The value of the timer is a network option and shall be in the range 20 to 30 seconds.
+
+**CCBS resume timer (T11):** the timer started as soon as a suspended CCBS request is resumed, making sure only one CCBS request is becoming resumed at a time. Duration of the timer shall allow a CCBS recall resulting from the destination side CCBS queue being processed. The value of the timer is a network option and shall be in the range 20 to 25 seconds.
+
+### Timers at the terminating side (B):
+
+**CCBS service duration timer (T7):** is the timer which specifies the maximum length of time the CCBS request will be held within the network. The value of this period is a network option shall be greater than 45 minutes.
+
+**Destination B idle guard timer (T8):** the time the network will wait after destination B has become idle before initiating a "CCBS recall" to subscriber A. The value of this timer is a network option and shall be in the range 0 to 15 seconds.
+
+NOTE 1: This timer enables destination B to initiate a call before any notification is given to subscriber A that destination B has become idle and prevents destination B to receive incoming calls.
+
+**CCBS recall B timer (T9):** is the timer, which supervises the CCBS recall establishment on the B-side. The value is a network option and shall be in the range of 40 to 55 seconds.
+
+NOTE 2: This timer prevents destination B from receiving other incoming calls than from subscriber A.
+
+NOTE 3: The timer values may vary from one PLMN to another and thus give the subscriber a slightly different perception of the service as she roams between PLMN's.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document the following abbreviations apply:
+
+|      |                                        |
+|------|----------------------------------------|
+| CCBS | Completion of Calls to Busy Subscriber |
+| NDUB | Network Determined User Busy           |
+
+Additional abbreviations may be found in GSM 01.04 [1] and TR 21.905 [6].
+
+# --- 4 Description
+
+When subscriber A encounters a Network Determined User Busy (NDUB) destination B, subscriber A can request the CCBS supplementary service (i.e. activate a CCBS Request against destination B). The network will then monitor the wanted destination B for becoming idle.
+
+When the wanted destination B becomes idle, then the network will wait a short time in order to allow destination B to make an outgoing call. If destination B does not make any outgoing call within this time, then the network shall automatically recall subscriber A.
+
+When subscriber A accepts the CCBS recall, within a defined time, then the network will automatically generate a CCBS call to destination B.
+
+CCBS has to be supported by the originating, as well as by the terminating network.
+
+## 4.1 Applicability to telecommunications services
+
+The applicability of the CCBS supplementary service is defined in TS 22.004 [2].
+
+# --- 5 Normal procedures with successful outcome
+
+## 5.1 Provision
+
+### 5.1.1 Subscriber A
+
+The CCBS supplementary service shall be provided to subscriber A after prior arrangement with the service provider.
+
+This supplementary service is provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BSs.
+
+### 5.1.2 Subscriber B
+
+Subscriber B is the user of destination B and is not provided with the CCBS supplementary service. However, if provided by the network operator/service provider as an option, subscriber B may elect not to be a target of CCBS requests. In this case, the size of her destination B CCBS queue shall be reduced to zero length by the service provider. Only the service provider may subsequently change the destination B CCBS queue length on demand of subscriber B.
+
+## 5.2 Withdrawal
+
+The CCBS supplementary service shall be withdrawn at the customer's request or for administrative reasons. At the same time, all outstanding CCBS requests shall be automatically deactivated.
+
+## 5.3 Registration
+
+Not applicable.
+
+## 5.4 Erasure
+
+Not applicable.
+
+## 5.5 Activation
+
+The CCBS service shall be activated as a result of provisioning.
+
+A CCBS request shall be activated by the mobile subscriber on a per-call basis by a control procedure as described in TS 22.030 [3].
+
+When subscriber A encounters a NDUB destination B, the network shall retain the call information for a period defined by the CCBS retention timer (T1), and inform subscriber A that CCBS is possible when the following set of conditions apply:
+
+- subscriber A has the CCBS supplementary service provisioned;
+- the call failure reason is either "user busy" or "no circuit/channel available";
+- CCBS is available (as determined by network B as described below).
+
+During this time subscriber A can activate the CCBS request.
+
+CCBS is available at network B, when the following set of conditions apply:
+
+- network B supports the CCBS supplementary service;
+
+- destination B is found to be NDUB; and
+- the maximum length of destination B's CCBS queue is greater than zero.
+
+If the network accepts the activation of a CCBS request the network shall register the call information in the original call request, and subscriber A shall be informed that the activation was successful.
+
+When the activation of a CCBS request is accepted the CCBS service duration timers (T3 and T7) are started. The network shall monitor destination B for destination B becoming idle.
+
+Subscriber A can have a limited number of CCBS requests outstanding. This limit is a network option (with a maximum value of 5). The CCBS requests can be to different destination Bs, or can be to the same destination B with different basic service requirements.
+
+Destination B can have a limited number of incoming CCBS requests outstanding. This limit is a network option (with a maximum value of 5). The requests can be from different subscriber As, or can be from the same subscriber A with different basic service requirements.
+
+Having activated a CCBS, subscriber A can originate calls and receive calls as normal.
+
+## 5.6 Deactivation
+
+The CCBS supplementary service shall be deactivated as a result of withdrawal.
+
+A previous CCBS request activation shall be deactivated by the mobile subscriber by a control procedure as described in TS 22.030 [3] or shall be automatically deactivated after a successful CCBS procedure or for exceptional situations as described in subclause 6.4.
+
+Deactivation of a CCBS request shall result in all reference to this CCBS request (entries in A and B queue and timers) being removed from the network.
+
+Subscriber A can send the following deactivation request:
+
+- a) deactivate all outstanding CCBS requests;
+- b) deactivate one specific CCBS request.
+
+Subscriber A shall be informed that the deactivation is successful.
+
+## 5.7 Invocation and operation
+
+The CCBS supplementary service shall be automatically invoked by the network after destination B has become idle.
+
+When destination B is or becomes idle or reachable and there are non-suspended CCBS requests in destination B's CCBS queue, then the network shall start the destination B idle guard timer (T8).
+
+When the destination B idle guard timer (T8) expires and destination B is still idle, the first non-suspended CCBS request shall be processed, provided that an entry in the destination B's CCBS queue is not currently being processed. Entries shall not be processed in parallel. This means that the CCBS recall procedure shall be started towards subscriber A, informing subscriber A that destination B is now idle and the CCBS recall B timer (T9) shall be started.
+
+If subscriber A is idle or not CCBS busy, subscriber A shall be recalled with an indication that it is a CCBS recall and with an indication of which CCBS request it applies to, and the CCBS recall timer (T4) shall be started. Optionally, the ME may use a specific alert (e.g. a tone, different from the one used for normal MT call) for the indication of a CCBS recall.
+
+If subscriber A accepts the recall before the CCBS recall timer (T4) expires, then the network shall initiate the CCBS call to destination B using the call information of the original call set-up (retained in the network). When the network receives an indication that the destination B is being informed of the CCBS call, the corresponding CCBS request shall be considered as completed.
+
+Whilst the destination B idle guard timer (T8) is running, and also whilst awaiting the CCBS call to destination B (whilst CCBS recall B timer (T9) is running), a new incoming call shall not be offered to destination B. For such incoming calls, the called user shall be considered as being NDUB and the calling user shall be informed as for basic call procedures.
+
+The CCBS requests in the destination B CCBS queue shall be processed in the order they are received, although the actual mechanism for processing the CCBS queue is outside the scope of the present document. During the processing of the destination B CCBS queue, CCBS requests which are currently suspended shall be ignored and the next entry in the CCBS queue shall be processed.
+
+If, for any reason, no CCBS call results from the processing of a CCBS request, then provided destination B is still idle, the next CCBS request in the destination B CCBS queue shall be selected for processing. This procedure shall be repeated until the processing of the destination B CCBS queue is complete.
+
+If all of the destination B CCBS queue has been processed and no CCBS call results, then processing is complete.
+
+## 5.8 Interrogation
+
+Subscriber A can request the list of the CCBS requests by a control procedure as described in TS 22.030 [3]. In response to the request subscriber A shall be given a list of the addresses and basic services against which CCBS requests are outstanding.
+
+# --- 6 Exceptional procedures or unsuccessful outcome
+
+## 6.1 Registration
+
+Not applicable.
+
+## 6.2 Erasure
+
+Not applicable.
+
+## 6.3 Activation
+
+If the Mobile Station (MS) does not receive information from the network that CCBS is possible, the activation of a CCBS request shall be rejected.
+
+If the network cannot accept subscriber A's request to activate a CCBS request, the network shall inform subscriber A and give the appropriate reason.
+
+If the request to activate a CCBS request can not be accepted due to special situation regarding CCBS the following indications shall be given to subscriber A:
+
+- a) **short term denial:** The network temporarily cannot accept subscriber A's request to activate a CCBS request. A later attempt to activate a CCBS request for the same destination B may succeed.
+  - The maximum number of CCBS requests permitted against destination B has been reached;
+  - Subscriber A tried to activate a CCBS request against destination B after the CCBS retention timer T1 has expired;
+  - Subscriber A has reached the maximum number of CCBS requests permitted;
+  - if there is an interaction with a supplementary service which temporarily prevents the activation of a CCBS request;
+- b) **long term denial:** The network cannot accept subscriber A's request to activate a CCBS request and a later attempt to activate a CCBS request against the same destination B will also be rejected.
+  - A CCBS request is not allowed against destination B i.e. because the destination B CCBS queue is set to zero;
+
+If subscriber A does not wait for the CCBS recall to a particular destination B, but makes another call to that (busy) destination B and activates another CCBS request then, the following procedures can apply:
+
+- if the two calls are identical, the original CCBS request shall be automatically deactivated and the current CCBS request shall be accepted. The current CCBS request shall be treated as new CCBS request (see subclause 5.5);
+
+NOTE: There will be no restriction how often subscriber A is allowed to activate identical requests like this. If destination B's CCBS queue is limited to a size of one, i.e. only one CCBS request is allowed to be planted against destination B, then if subscriber A re-activates CCBS request before T3 expires then no other subscriber can activate CCBS against destination B.
+
+- if the two calls are not identical, then the network shall treat this as a new CCBS request. (see subclause 5.5).
+
+In order to decide that the two calls are identical, the originating network shall only compare the basic call information, i.e. the basic service requirements, and called subscriber identity.
+
+The originating network shall check for identical CCBS requests.
+
+## 6.4 Deactivation
+
+If there are no CCBS requests outstanding which meet the criteria specified in the deactivation request, the network shall inform subscriber A.
+
+## 6.5 Invocation and operation
+
+If, as a result of processing the entries in the queue, all entries become either suspended or automatically deactivated, no further processing shall take place. If, while destination B is idle, a previously suspended entry is resumed, or a new entry is added to the queue, the network shall process that entry. If destination B becomes idle, the network shall process that entry.
+
+If, while destination B is still idle and no other CCBS call is awaited (CCBS Recall B timer (T9) is not running), a previously suspended entry is resumed or a new entry is added to the destination B CCBS queue, the network shall process that entry as described in subclause 5.7.
+
+### 6.5.1 Exceptional situation at destination B's side:
+
+- a) Destination B makes an outgoing call during the idle guard timer is running.
+
+If destination B makes an outgoing call while the destination B idle guard timer (T8) is running, then invocation of CCBS shall be deferred until destination B becomes idle again.
+
+- b) destination B is NDUB upon arrival of the CCBS call.
+
+If destination B is NDUB upon arrival of the CCBS call, then two network options exist:
+
+- the corresponding CCBS request shall be automatically deactivated. If subscriber A activates a CCBS request again, this activation shall be considered as a new CCBS request; or
+- the original CCBS request shall retain its position in the CCBS queue, and the CCBS service duration timers (T3 and T7) shall not be restarted. If subscriber A attempts to activate a CCBS request again, this shall be treated as an identical request (see subclause 6.3).
+
+NOTE: The option to retain the information of the original CCBS request can only be invoked if both the originating and the destination network support this option. It is the responsibility of networks supporting the option to retain the original CCBS request to provide interworking with those networks that do not.
+
+- c) destination B is not reachable.
+
+The network may determine that destination B is not reachable:
+
+- when the network monitors destination B for destination B becoming idle;
+- while running the destination B idle guard timer (T8).
+
+In each of the above cases, the CCBS request shall remain in the CCBS queue until. When destination B becomes reachable, the network shall process any CCBS requests in the CCBS queue (see subclause 5.7).
+
+If subscriber A accepts the CCBS recall and destination B is not reachable, then the corresponding CCBS request shall be automatically deactivated.
+
+- d) destination B rejects the CCBS call with UDUB.
+
+If destination B rejects the CCBS call using UDUB, the CCBS request shall be automatically deactivated. The network shall not offer subscriber A the opportunity to activate a CCBS request for this call again.
+
+#### e) supplementary service interaction on destination B's side:
+
+If a supplementary service is active and operative on destination B side which prohibits the invocation of the CCBS supplementary service (for details see also Clause 7), then the processing of the B CCBS queue shall be stopped. The outstanding CCBS requests shall remain in destination B CCBS request CCBS queue. If the supplementary service interaction ends the outstanding CCBS requests shall be processed (see subclause 5.7).
+
+#### f) CCBS request becomes suspended while awaiting the CCBS call:
+
+If a CCBS request becomes suspended while being processed, the network shall stop the CCBS recall timer (T9) and process the next non-suspended CCBS request.
+
+#### g) CCBS service duration timer (T7) expires:
+
+If the CCBS service duration timer (T7) expires and the subscriber A has not been informed that destination B is idle for that CCBS request, i.e. the CCBS recall timer (T9) is not running, then the network shall automatically deactivate the CCBS request.
+
+If the CCBS service duration timer (T7) expires after the subscriber A has been informed that destination B is idle for that CCBS request, i.e. the CCBS recall B timer (T9) is running, then the CCBS request shall not be automatically deactivated until the processing of the CCBS request is completed.
+
+#### h) CCBS recall B timer (T9) expires:
+
+If the CCBS recall B timer (T9) expires then the network shall automatically deactivate the CCBS request.
+
+### 6.5.2 Exceptional situation at subscriber A's side:
+
+#### a) non-acceptance or rejection of CCBS recall when subscriber A is found to be idle.
+
+If subscriber A rejects the CCBS recall or the CCBS recall timer (T4) expires, then the CCBS request shall be automatically deactivated.
+
+If subscriber A tries to suspend the CCBS recall then the CCBS request shall be automatically deactivated.
+
+#### b) subscriber A is found to be not idle.
+
+When the destination B's idle guard timer (T8) expires and subscriber A is found to be not idle, the network shall notify subscriber A and start the CCBS notification timer (T10). While the CCBS notification timer (T10) is running, subscriber A may:
+
+- Accept the CCBS recall: The subscriber A has to free up the required resources to set-up the CCBS call, e.g. by releasing the existing calls or put the existing call on hold. The CCBS recall shall then be handled in the same way as when subscriber A is idle (subclause 5.7).
+- Reject the CCBS notification. The network shall automatically deactivate the CCBS request.
+- Ignore the CCBS notification. When the CCBS notification timer (T10) expires, the network shall suspend the CCBS request if T3 is still running. If T10 expires while T3 has already expired, then the CCBS request shall be automatically deactivated.
+- Suspend the CCBS request . The request may later be resumed according to subclause 6.5.2.e.
+
+#### c) subscriber A is found to be CCBS busy.
+
+If subscriber A is CCBS busy when destination B's idle guard timer (T8) expires, the network shall suspend the CCBS request without notifying subscriber A.
+
+#### d) Subscriber A is not reachable.
+
+If it is identified that subscriber A is not reachable when the destination B idle guard timer expires, then the CCBS request shall be suspended until subscriber A becomes reachable again.
+
+- e) If subscriber A becomes idle after being not idle or CCBS busy, or subscriber A becomes reachable again and there are one or more suspended CCBS requests in subscriber A's CCBS queue, this queue shall be processed in the following way:
+
+The first suspended CCBS request shall be resumed. The CCBS resume timer (T11) is started, provided that subscriber A's CCBS queue holds more than one CCBS request;
+
+- If no CCBS recall results from the resume procedure before the CCBS resume timer (T11) expires, processing of subscriber A's CCBS queue shall be continued as described above until no more suspended CCBS requests are left in that queue;
+- If a CCBS recall results from the resume procedure, the CCBS resume timer (T11) is stopped, and the CCBS recall is treated in the normal way as described in subclause 5.7.
+
+- f) CCBS service duration timer (T3) expires:
+
+- If the CCBS service duration timer (T3) expires and the subscriber A has not been informed that destination B is idle for that CCBS request, i.e. the CCBS recall timer (T4) or the CCBS notification timer (T10) are not running then the network shall automatically deactivate the CCBS request.
+- If the CCBS service duration timer (T3) expires and the subscriber A has been informed that destination B is idle, i.e. the CCBS recall timer (T4) or the CCBS notification timer (T10) are running, then the CCBS request shall not be automatically deactivated until the processing of the CCBS request is completed.
+
+- g) CCBS recall timer (T4) expires:
+
+If the CCBS recall timer (T4) expires then the network shall automatically deactivate the CCBS request.
+
+### 6.5.3 Exceptional situations in the network
+
+If the CCBS call fails for any other reason than described in subclauses 6.5.1 and 6.5.2, then subscriber A shall be informed as for the basic call procedures, and the CCBS request shall be automatically deactivated.
+
+# --- 7 Interaction with other supplementary services
+
+## 7.1 Calling line identification presentation
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+## 7.2 Calling line identification restriction
+
+CLIR information from the original call, stored in the network, shall also be automatically included in the CCBS call.
+
+## 7.3 Connected line identification presentation
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+## 7.4 Connected line identification restriction
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+## 7.5 Call Forwarding Unconditional (CFU)
+
+CCBS recalls shall never be forwarded.
+
+If subscriber A places a call to destination B and the call is forwarded to user C by the CFU supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication.
+
+If destination B activates the CFU supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network's queue processing until the CFU supplementary service becomes deactivate or quiescent or until the CCBS duration timers (T3 or T7) expire.
+
+If destination B activates the CFU supplementary service for the relevant Basic Service Group between the expiry of the destination B idle guard timer and the arrival of the CCBS call, the CCBS call shall be forwarded as a normal call.
+
+If the destination network B receives a CCBS request from the originating A network while the CFU supplementary is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial.
+
+## 7.6 Call Forwarding on mobile subscriber Busy (CFB)
+
+CCBS recalls shall never be forwarded.
+
+If subscriber A places a call to destination B and the call is forwarded to user C by the CFB supplementary service and user C is busy, then any subsequent attempt to activate a CCBS request by subscriber A against destination B will be accepted.
+
+If destination B activates the CFB supplementary service after subscriber A has activated a CCBS request, then the processing of destination B's CCBS queue shall be continued.
+
+If destination B which has activated the CFB supplementary service is busy upon arrival of a CCBS call two network provider options exist with regard to the treatment of that CCBS call, i.e.:
+
+- the CCBS call shall be treated according to the exceptional procedures (destination B again busy); or
+- the CCBS call shall be forwarded as a normal call.
+
+## 7.7 Call Forwarding on No Reply (CFNRy)
+
+CCBS recalls shall never be forwarded.
+
+If subscriber A places a call to destination B and the call is forwarded to user C by the CFNRy supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication.
+
+If destination B activates the CFNRy supplementary service after subscriber A has activated a CCBS request, then the processing of destination B's CCBS queue shall be continued.
+
+If destination B activates the call forwarding no reply supplementary service after subscriber A has activated a CCBS request against destination B, then the CCBS call shall be given to destination B at the user's original location. After the no reply timer has expired at destination B the CCBS call shall be forwarded as a normal call.
+
+## 7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
+
+CCBS recalls shall never be forwarded.
+
+If subscriber A places a call to destination B and the call is forwarded to user C by the CFNRc supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication.
+
+If destination B activates the CFNRc supplementary service after subscriber A has activated a CCBS request, then the processing of destination B's queue shall be continued.
+
+If destination B activates the CFNRc supplementary service after subscriber A has activated a CCBS request against destination B and destination B is not reachable upon the arrival of CCBS call then the CCBS call shall be forwarded as a normal call.
+
+## 7.9 Call waiting
+
+If subscriber A has subscribed to the CCBS supplementary service and places a normal call to a destination B that has subscribed to the call waiting supplementary service, and the call waiting indication is given to destination B (i.e. the call is waiting), a subsequent CCBS request activation by subscriber A shall not be allowed.
+
+If the call waiting indication cannot be given at the destination B, subscriber A will receive busy indication and can activate a CCBS request against destination B.
+
+CCBS requests in the destination B CCBS queue shall only be processed if destination B is idle.
+
+A CCBS call shall be treated as a normal call with respect to call waiting, at subscriber B.
+
+## 7.10 Call hold
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+## 7.11 Multiparty services
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+## 7.12 Closed user group
+
+Closed user group information from the original call, stored in the network, shall also be automatically included in the CCBS call.
+
+If subscriber A or destination B roam to a network not supporting CUG the call restriction procedures as described in TS 22.085 [4] shall apply after a CCBS request has been activated.
+
+## 7.13 Advice of charge services
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+If subscriber A has subscribed to Advice of Charge Charging (AoCC) and if ACMmax is reached, or exceeded, and subscriber A is awaiting a CCBS recall notification, then the ME shall be informed of the CCBS recall. Subscriber A shall not be informed of the CCBS recall. The ME shall reject the CCBS recall which shall stop T4 or T10 and the corresponding CCBS request shall be deactivated. Any outstanding CCBS request shall remain in subscriber A's CCBS queue until the CCBS service duration timer (T3 or T7) expires.
+
+## 7.14 Barring of All Outgoing Calls (BAOC)
+
+If the BAOC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred and the CCBS Request shall be automatically deactivated.
+
+## 7.15 Barring of Outgoing International Calls (BOIC)
+
+If the BOIC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred if it is an international call and the CCBS Request shall be automatically deactivated.
+
+## 7.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)
+
+If the BOIC-exHC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred if it is an international call except to the HPLMN country and the CCBS Request shall be automatically deactivated.
+
+## 7.17 Barring of All Incoming Calls (BAIC)
+
+If destination B activates the BAIC supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network's queue processing until the BAIC supplementary service becomes deactivate or until the CCBS duration timers (T3 or T7) expire.
+
+If the BAIC supplementary service is active and operative for the relevant Basic Service Group when the HPLMN B receives an interrogation to route the CCBS call, then the specific CCBS request relating to that CCBS call shall be automatically deactivated.
+
+If the destination network B receives a CCBS request from the originating A network while the BAIC supplementary service is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial.
+
+## 7.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)
+
+If destination B activates the BIC-Roam supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network's queue processing until the BAIC supplementary service becomes deactive or quiescent or until the CCBS duration timers (T3 or T7) expire.
+
+If the BIC-Roam supplementary service becomes active and operative for the relevant Basic Service Group when the HPLMN B receives an interrogation to route the CCBS call, then the specific CCBS request relating to that CCBS call shall be automatically deactivated.
+
+If the destination network B receives a CCBS request from the originating A network while the BIC-Roam supplementary service is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial.
+
+## 7.19 Explicit call transfer
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+## 7.20 Completion of calls to busy subscriber
+
+No impact.
+
+A subscriber can be both a "subscriber A" and a "destination B" simultaneously, i.e. the same subscriber can be both the originator and the target of one or more CCBS requests.
+
+If the subscriber receives a CCBS call while that subscriber is being alerted or is awaiting completion of the CCBS call for which the subscribers is the originator, then the received CCBS call shall be treated as if the subscriber was busy again.
+
+## 7.21 Customised Applications for Mobile network Enhanced Logic (CAMEL)
+
+The CCBS call shall be treated as normal originating call for the purpose of CAMEL based originating services.
+
+If a mobile originating CAMEL based service determines for a CCBS call different called party address than for the initial call, the CCBS call shall be released by the network and the corresponding CCBS request shall be automatically deactivated.
+
+There will be no interaction in case of the called party address is not changed by any CAMEL based terminating service.
+
+In case of a terminating CAMEL based service changing the called party address, then a CCBS request activation shall not be allowed.
+
+At Interrogation the network shall return the same B subscriber address as subscriber A has entered at the time of CCBS request activation.
+
+If the CSE (CAMEL Service Environment) requests a call set-up to an alternative destination after the original call set-up to destination B has encountered a busy condition and this call meets a busy destination, then any subsequent attempt to activate a CCBS request by subscriber A against destination B (the original called party) will be accepted.
+
+If the CSE (CAMEL Service Environment) requests a call set-up to an alternative destination after the original call set-up has failed for other reasons than the busy condition of destination B or was disconnected and this call meets a busy destination, then subscriber A shall not receive any CCBS possible indication..
+
+## 7.22 Support of Private Numbering Plan (SPNP)
+
+A CCBS call shall always be directed to the party originally addressed, regardless of any changes in the B party number after activation of a CCBS request.
+
+At Interrogation, the network shall return the same B subscriber address as subscriber A has entered at the time of the original call.
+
+---
+
+# 8 Mobility aspects
+
+The processing of CCBS requests shall not be affected by the mobility of subscriber A or destination B if either or both of the subscribers is a mobile subscriber.
+
+# --- Annex A (informative): Cross Phase compatibility
+
+Users of existing MSs (Phase 2 and possibly Phase 1) are not prevented from using the CCBS supplementary service.
+
+Existing Phase 1/Phase 2 functional signalling mechanisms and USSD shall be used to offer the service to these MSs. Networks wishing to offer this service to existing MSs are therefore required to support both functional (Phase 1/Phase 2) and stimulus signalling (USSD).
+
+## --- A.1 Activation of a CCBS request
+
+Activation of CCBS requests by existing MSs shall be performed using USSD. The standardised MMI is defined in TS22.030 [3]. The network shall interpret the USSD string as an activation of a CCBS request.
+
+Consequently, networks which do not support USSD will not be able to offer the service to existing MSs which do not support USSD will not be able to activate a CCBS request.
+
+## --- A.2 CCBS Recall
+
+A CCBS Recall to an existing MS shall be handled as a normal mobile terminated call using Phase 1/Phase 2 functional signalling.
+
+## --- A.3 Interrogation
+
+Existing MSs shall use USSD to interrogate the service. The MMI is defined in TS 22.030[3].
+
+## --- A.4 Deactivation
+
+Existing MSs shall use USSD to deactivate the service. The MMI is defined in TS22.030 [3].
+
+# --- Annex B (normative): Roaming to non-supporting networks
+
+## B.1 Roaming into networks or registering in network entities not supporting CCBS
+
+This clause looks at the times when either parties involved in CCBS may roam from a supporting network entity into a non-supporting network or network entity.
+
+Consider the times when neither Subscriber A or Destination B can register in another location area.
+
+Subscriber A cannot register in another location area:
+
+- a) Having received a CCBS Possible indication and while the network is awaiting the initial CCBS Request;
+- b) Having received a CCBS Recall and while the network is awaiting acceptance of the CCBS Recall;
+- c) During the duration of the CCBS Call.
+
+Destination B cannot register in another location area:
+
+- a) During the duration of the CCBS Call;
+
+### B.1.1 Subscriber A may register in a non-supporting network or network entity
+
+Whilst waiting for the CCBS Recall from Destination B
+
+If Subscriber A registers in a non-supporting entity whilst waiting for the CCBS Recall from destination B. The network shall be aware that the CCBS supplementary service is not supported and shall suspend the CCBS Request. The CCBS Request shall remain suspended until either Subscriber A registers in a supporting entity or until the service duration timer T3 expires.
+
+### B.1.2 Destination B may register in a non-supporting network entity
+
+- a) If destination B becomes idle after "CCBS Possible" has been sent and before a "CCBS Request" is received.  
+If destination B is idle and has registered in a non-supporting entity when the CCBS Request arrives then the CCBS Request shall be accepted, but the handling of the destination B CCBS queue shall be frozen until the destination B registers in a supporting entity or until a service duration timer expires.
+- b) While T8 is running.  
+If destination B registers in a non-supporting network entity during T8, then the processing of the destination B CCBS queue shall be stopped until either destination B registers in a supporting network entity or the service duration time expires.
+- c) After T8 expires.  
+If Destination B registers in a non-supporting entity after having sent the CCBS Recall, then error handling will ensure that the entity informs the network that it doesn't support CCBS. However, the CCBS Call shall be allowed to continue. When the non-supporting entity receives the CCBS Call, it will not be able to inform the network that the CCBS has been completed. The only safeguard is that T9 in the network will expire, which will result in automatic deactivation of the CCBS Request from the queue.
+- d) When a CCBS Request is suspended and before it is resumed.  
+If destination B has registered in a non-supporting entity when the CCBS Resume arrives, then the CCBS Resume shall be treated as a CCBS Request and shall be accepted, but the handling of the destination B CCBS queue shall be frozen until destination B registers in a supporting entity or until a service duration timer expires.
+
+# Annex C (informative): Change history
+
+| Change history |           |           |           |     |     |       |     |                                 |        |        |                   |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|---------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                 | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.93 |     |     |       |     | Transferred to 3GPP SA1         | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.093    |     |     | R99   |     | Transferred to 3GPP SA1         |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99638  | 22.093    | 001 |     | R99   | D   | Editorial changes for alignment | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.093    |     |     | Rel-4 |     | Transferred to 3GPP Release 4   | 3.0.1  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.093    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5      | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.093    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6     | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.093    |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7     | 6.0.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8     | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-9 by MCC         | 8.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)  | 9.0.0  | 10.0.0 |                   |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-11 by MCC        | 10.0.0 | 11.0.0 |                   |

marked/Rel-11/22_series/22094/raw.md

@@ -0,0 +1,350 @@
+
+
+
+
+
+
+# Contents
+
+|                                                        |    |
+|--------------------------------------------------------|----|
+| Foreword .....                                         | 4  |
+| 1 Scope.....                                           | 5  |
+| 2 References.....                                      | 5  |
+| 3 Definitions, symbols and abbreviations.....          | 6  |
+| 3.1 Definitions.....                                   | 6  |
+| 3.2 Abbreviations .....                                | 6  |
+| 4 Description.....                                     | 6  |
+| 4.1 Normal Operation.....                              | 7  |
+| 5 Applicability to telecommunication services.....     | 7  |
+| 6 Normal procedures with successful outcome.....       | 7  |
+| 6.1 Provision.....                                     | 7  |
+| 6.2 Withdrawal.....                                    | 8  |
+| 6.3 Registration .....                                 | 8  |
+| 6.4 Erasure.....                                       | 8  |
+| 6.5 Activation.....                                    | 9  |
+| 6.6 Deactivation .....                                 | 9  |
+| 6.7 Invocation.....                                    | 9  |
+| 6.8 Interrogation .....                                | 9  |
+| 7 Exceptional procedures or unsuccessful outcome ..... | 9  |
+| 7.1 Registration .....                                 | 9  |
+| 7.2 Erasure.....                                       | 10 |
+| 7.3 Interrogation .....                                | 10 |
+| 7.4 Invocation.....                                    | 10 |
+| 8 Alternate procedures .....                           | 10 |
+| 9 Charging requirements.....                           | 10 |
+| 10 Interactions with supplementary services .....      | 11 |
+| 10.1 Call Forwarding unconditional.....                | 11 |
+| 11 Interaction with Operator Determined barring.....   | 11 |
+| 12 Interaction with Optimal Routeing .....             | 11 |
+| 13 Interaction with CAMEL .....                        | 11 |
+| 14 Interworking considerations.....                    | 11 |
+| Annex A (informative) : Change history.....            | 12 |
+
+# --- 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 specifies the stage 1 description for the Follow Me feature.
+
+The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a party B in such a way that - under certain conditions - subsequent calls directed to party B will be forwarded to subscriber A.
+
+The feature is described from the service subscriber's and user's point of view, in particular:
+
+- the procedure for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other GSM services and features.
+
+This TS does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
+
+Any interaction with other services and/or networks not dealt with in this specification are outside the scope of this TS.
+
+# --- 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 TS 22.004: "General on supplementary services".
+- [4] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [5] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
+- [6] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1".
+- [7] 3GPP TS 22.041: "Operator Determined Barring (ODB) - Stage 1".
+- [8] 3GPP TS 22.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL); Service definition (Stage 1)".
+- [9] 3GPP TS 22.079: "Support of Optimal Routeing (SOR); Service definition (Stage 1)".
+- [10] 3GPP TS 22.090: " Unstructured Supplementary Service Data (USSD) Stage 1"
+- [11] 3GPP TS 42.031: "Fraud Information Gathering System (FIGS); Service description - Stage 1"
+- [12] 3GPP TS 22.101: "Service Principles".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+**initiating subscriber:** the mobile subscriber which modifies the Follow Me data of the remote party.
+
+**remote party:** Is characterised by a number in E.164 format defined in the numbering plan of a PLMN operator. The Follow Me feature enables the initiating subscriber to modify the Follow Me data associated with this number. In general this number is not assigned to a subscriber. In particular cases the remote party is a subscriber of the PLMN and the number denotes her basic MSISDN.
+
+**FM service supervisor:** Is an initiating subscriber who is allowed to modify the Follow Me data of a remote party who has been registered to another initiating subscriber for the Follow Me application. The FM service supervisor shall be authorised by her network operator.
+
+## 3.2 Abbreviations
+
+For the purposes of this TS the following abbreviations apply, in addition, abbreviations used in this TS are listed in 3GPP TS 21.905 [1].
+
+|    |                   |
+|----|-------------------|
+| FM | Follow Me feature |
+|----|-------------------|
+
+# --- 4 Description
+
+Follow Me enables an initiating mobile subscriber A to have control over the Follow Me data of a remote party B. Initiating Subscriber A shall be able to manipulate the Follow Me data of remote party B such that subsequent calls directed to remote party B are forwarded to initiating subscriber A.
+
+Initiating subscriber A needs to have FM provisioned by her service provider. In case remote party B is a subscriber she needs to have FM provisioned by her service provider too.
+
+The FM service supervisor shall be able to modify the Follow Me data of the remote party who has been registered to another initiating subscriber.
+
+It remains in the responsibility of a FM provisioning service provider to confine
+
+- a.) the range of remote parties for which a FM provisioned subscriber may become initiating subscriber
+- b.) the range of potential initiating subscribers for a remote party.
+
+The mobile subscriber who has been provisioned Follow Me is able to use the following control operations:
+
+|               |                                                                                                   |
+|---------------|---------------------------------------------------------------------------------------------------|
+| Registration  | available to the initiating subscriber                                                            |
+| Interrogation | available to the initiating and remote party in case the remote party corresponds to a subscriber |
+| Erasure       | available to the initiating and remote party in case the remote party corresponds to a subscriber |
+
+(There is no explicit activation or deactivation.)
+
+The FM service supervisor is able to use the following control operations:
+
+|               |                  |
+|---------------|------------------|
+| Interrogation |                  |
+| Erasure       | (forced erasure) |
+
+NOTE 1: The functionality of the Follow Me feature is equivalent to the Call Forwarding Unconditional Supplementary Service (see 3GPP TS 22.082 [5]), controlled by initiating subscriber A and effecting remote party B.
+
+NOTE 2: The Follow Me feature is designed in such a way that the requirements of "functional addressing", which is needed for GSM-Railway operators, can be met. The concept of "functional addressing" enables a subscriber to set up a call to a "function" - e.g. the conductor - on a "train". The Follow Me feature identifies this "function" with the remote party B. Consequently a "functional number" is the equivalent to the number of remote party B (e.g. the MSISDN of a subscriber B). A call to that "functional number" (the conductor on a particular train - to stay with the example) will be forwarded to the MS of the person, who is on duty as a conductor at this time for this train. In the context of the Follow Me feature, this person (the train conductor) constitutes the "initiating subscriber" A, who has registered Follow Me with respect to the remote party B (the "function" train conductor).
+
+## 4.1 Normal Operation
+
+Due to reduced security requirements to the Follow Me feature the service shall not be offered in standard operations of public 3GPP networks. In railway operations it must be enabled by definitive action on the part of the operator.
+
+Fraud Information Gathering System (FIGS) as specified in [11] can be used to protect in CAMEL based inter-working networks.
+
+The Follow Me feature shall be controlled by means of Subscriber Controlled Input using USSD.
+
+# 5 Applicability to telecommunication services
+
+3GPP TS 22.001 describes the principles of the Telecommunication services provided in a PLMN. It also defines the concepts of Telecommunication services and describes their characterization by appropriate attributes. Bearer services and Teleservices, which are offered by a PLMN in connection with other networks, are defined in 3GPP TS 22.002, 3GPP TS 22.003 and 3GPP TS 22.101. A list of basic service groups can be found in 3GPP TS 22.004.
+
+Follow Me is applicable to the following telecommunication services:
+
+**Table 1: Applicability of the Follow Me feature to telecommunication services**
+
+| Feature   | Telephony | Emergency Call | SMS PTP |      | SMS-CB | Fax   | cct Data   |  |  | Voice Group Services |                 |
+|-----------|-----------|----------------|---------|------|--------|-------|------------|--|--|----------------------|-----------------|
+|           | TS11      | TS12           | TS21    | TS22 | TS 23  | TS 6x | BS2x, BS3x |  |  | TS 91                | TS 92           |
+| Follow Me | Yes       |                |         |      |        | Yes   | Yes        |  |  | No <sup>1</sup>      | No <sup>1</sup> |
+
+NOTE 1: The feature is in general not applicable for Voice Group Services. However a dispatcher may be an initiating subscriber or a remote party for the Follow Me feature.
+
+**EDITOR's Note: The applicability of FM to SMS is for further study.**
+
+# 6 Normal procedures with successful outcome
+
+## 6.1 Provision
+
+Follow Me shall be provided after prior arrangement with the service provider. Follow Me will be provisioned for all Basic Services subscribed to and to which it is applicable.
+
+### NOTES:
+
+- A Follow Me provision is required for the initiating subscriber and for the remote party in case the remote party corresponds to a subscriber.
+- If Follow Me is provisioned for a mobile subscriber she may assume the role of an initiating subscriber and/or the role of a remote party.
+- A Follow Me provisioning service provider may confine:
+  - a.) the range of remote parties for which a FM provisioned subscriber may become initiating subscriber
+  - b.) the range of potential initiating subscribers for a remote party.
+  - c.) the range of remote parties for which a FM provisioned subscriber may become FM service supervisor.
+
+NOTE: (Health warning on security) The Follow Me feature is designed in such a way as to meet the security requirements of GSM-Railway operators. If the Follow Me feature is to be used by other operators - in particular if the remote party corresponds to a subscriber - operators are strongly advised to care for additional suitable security mechanisms to protect the remote party from potential harm by misuse of FM. These mechanisms are out of scope of this specification. To support such mechanisms the possibility is foreseen to convey additional operator-specific information in the registration, interrogation and erasure procedures to the PLMN of the remote party. It should however be noted, that this is not a very secure mechanism. Operators should try to use existing security mechanisms where possible
+
+## 6.2 Withdrawal
+
+Follow Me will be withdrawn at the subscriber's request or for administrative reasons.
+
+## 6.3 Registration
+
+Follow Me shall be registered with an appropriate control procedure by the initiating subscriber.
+
+The initiating Subscriber registers the Follow Me feature with respect to a particular remote party.
+
+The initiating subscriber shall provide the following information to the network:
+
+the number of the remote party (e.g. the Basic MSISDN of a subscriber);
+
+The initiating subscriber shall receive an indication if the FM registration request was accepted or rejected by the network.
+
+As an operator's option additional information (such as passwords) for registration may be required from the initiating subscriber. The registration procedure shall transport this information from the initiating subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification.
+
+NOTE 1: The Follow Me feature may, at an instant, be registered to an initiating subscriber with respect to several remote parties. Conversely, a remote party can be registered only to one initiating subscriber at a time.
+
+## 6.4 Erasure
+
+A previous FM registration can be erased in either of the following ways:
+
+- a) The initiating subscriber can specifically erase her previous registration with an appropriate control procedure.
+- b) In case the remote party corresponds to a subscriber the remote party can erase any previous registration with an appropriate control procedure.
+- c) The FM service supervisor can erase any previous registration to any remote party with an appropriate control procedure (forced erasure).
+
+The subscriber who initiates the FM erase request shall be informed of the outcome of the request by the network.
+
+For forced erasure by the FM service supervisor the initiating subscriber whose registration of Follow Me with respect to a remote party has been erased shall be informed of the successful forced erasure by the network.
+
+As an operator's option additional information (such as passwords) for erasure may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification.
+
+## 6.5 Activation
+
+Follow Me is activated by registration.
+
+## 6.6 Deactivation
+
+Follow Me is deactivated by erasure.
+
+## 6.7 Invocation
+
+Follow Me is automatically invoked by the network if it was previously registered. If Follow Me is registered all incoming calls to the remote party will be forwarded to the initiating subscriber by network invocation.
+
+When Follow Me is active and operative and if the remote party is a subscriber, the ability of the remote party to originate calls is not affected.
+
+## 6.8 Interrogation
+
+An initiating subscriber (also the FM service supervisor) shall be able to interrogate the Follow Me data of any remote party, for which she is authorised to become initiating subscriber.
+
+In case the remote party corresponds to a subscriber the remote party shall be able to interrogate her own Follow Me data stored in the network.
+
+The network shall return the basic MSISDN of the initiating subscriber for which the remote party is registered to Follow Me.
+
+As an operator's option additional information (such as passwords) for interrogation may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification.
+
+# --- 7 Exceptional procedures or unsuccessful outcome
+
+## 7.1 Registration
+
+If the system cannot accept a registration request, the initiating subscriber shall receive a notification that Follow Me registration was not successful. Possible causes are:
+
+- insufficient information;
+- feature not provisioned to initiating subscriber;
+- feature not provisioned to remote party (in case the remote party is a subscriber);
+- conflicting situation with supplementary services (e.g. incoming call barring has been activated);
+- remote party already registered to a different initiating subscriber;
+- insufficient authorisation for initiating subscriber or remote party.
+
+## 7.2 Erasure
+
+If the network cannot accept a mobile initiating or remote subscriber's request for erasure, cause will be returned to the subscriber, such as:
+
+- insufficient information;
+- remote party not registered;
+- remote party registered to a different initiating subscriber;
+- insufficient authorisation for initiating subscriber or remote party;
+- feature not provisioned to initiating subscriber;
+
+- feature not provisioned to remote party (in case the remote party is a subscriber).
+
+## 7.3 Interrogation
+
+If the network cannot accept a mobile initiating or remote subscriber's request for interrogation, cause will be returned to the subscriber, such as:
+
+- insufficient information;
+- insufficient authorisation for initiating subscriber or remote party;
+- feature not provisioned to initiating subscriber;
+- feature not provisioned to remote party (in case the remote party is a subscriber).
+
+## 7.4 Invocation
+
+Within a PLMN or different PLMNs the number of tandem forwarding connections (including call forwarding, call deflection, Follow Me) should be limited. The maximum number of tandem forwarding connections should be limited to a value between 1 and 5. This is to prevent infinite looping.
+
+If the limit of successive forwardings of a call has already been reached, an unsuccessful call set up indication is sent backwards.
+
+If the call cannot be completed to the Follow Me destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards.
+
+# --- 8 Alternate procedures
+
+None identified.
+
+# --- 9 Charging requirements
+
+None identified.
+
+# --- 10 Interactions with supplementary services
+
+Interactions of the Follow Me feature with supplementary services may occur only for the remote party.
+
+The interactions of the Follow Me feature with supplementary services other than Call Forwarding Unconditional (CFU) are the same as the interactions of CFU with supplementary services (see 3GPP TS 22.082 [5]).
+
+NOTE: The “served mobile subscriber” in 3GPP TS 22.082 [5] corresponds to the “remote party” in this document. The “forwarded-to subscriber” in 3GPP TS 22.082 [5] corresponds to the “initiating subscriber” in this document
+
+## 10.1 Call Forwarding unconditional
+
+Follow Me and the Call Forwarding Unconditional Supplementary Service are mutually exclusive. That is:
+
+If Follow Me is registered with respect to a remote party, registration or activation of Call forwarding unconditional by the remote party is rejected. The remote party shall be informed of this incompatibility.
+
+If Call forwarding unconditional is registered or active for the remote party, registration of Follow Me is rejected. The initiating subscriber shall be informed of this incompatibility.
+
+# --- 11 Interaction with Operator Determined barring
+
+Same as interaction between Operator Determined barring and call forwarding unconditional as defined in 3GPP TS 22.082.
+
+# --- 12 Interaction with Optimal Routeing
+
+Same as interaction between Optimal Routeing and call forwarding unconditional as defined in 3GPP TS 22.079.
+
+# --- 13 Interaction with CAMEL
+
+Same as interaction between CAMEL and call forwarding unconditional as defined in 3GPP TS 22.078.
+
+# --- 14 Interworking considerations
+
+If a forwarded call due to invocation of Follow Me meets an interworking situation, then an interworking indication should be sent to the calling party. When interworking with non-PLMN or non-ISDN networks, tones and announcements will be required.
+
+NOTE 1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited.
+
+NOTE 2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI.
+
+# Annex A (informative) : Change history
+
+| Change history |                      |           |        |     |     |       |     |                                                                |        |        |           |
+|----------------|----------------------|-----------|--------|-----|-----|-------|-----|----------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.              | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                | Old    | New    | WI        |
+| SP-06          | SP-99517<br>SP99-595 | S1-991015 | 22.094 | 001 |     | R99   | B   | Introduction of the rôle of a " Follow Me service supervisor:" | 3.0.0  | 3.1.0  | Follow-Me |
+| SP-11          | SP-010065            | S1-010258 | 22.094 |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                  | 3.1.0  | 4.0.0  |           |
+| SP-15          | SP-020045            | S1-020457 | 22.094 | 002 | -   | Rel-4 | F   | Editorial CR to correct terms and references                   | 4.0.0  | 4.1.0  | CORRECT   |
+| SP-16          | SP-020267            | S1-021043 | 22.094 |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                     | 4.1.0  | 5.0.0  |           |
+| SP-22          | SP-030699            | S1-031219 | 22.094 | 003 | -   | Rel-6 | B   | Notify of forced erasure to initiating subscriber A            | 5.0.0  | 6.0.0  | TEI6      |
+| SP-36          |                      |           | 22.094 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                    | 6.0.0  | 7.0.0  |           |
+| SP-42          | -                    | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                    | 7.0.0  | 8.0.0  |           |
+| SP-46          | -                    | -         | -      | -   | -   | -     | -   | Updated to Rel-9 by MCC                                        | 8.0.0  | 9.0.0  |           |
+| 2011-03        | -                    | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                 | 9.0.0  | 10.0.0 |           |
+| 2012-09        | -                    | -         | -      | -   | -   | -     | -   | Updated to Rel-11 by MCC                                       | 10.0.0 | 11.0.0 |           |

marked/Rel-11/22_series/22115/raw.md

@@ -0,0 +1,787 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                            |    |
+|--------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                             | 5  |
+| 1 Scope.....                                                                               | 6  |
+| 2 References.....                                                                          | 6  |
+| 3 Definitions and abbreviations .....                                                      | 7  |
+| 3.1 Definitions.....                                                                       | 7  |
+| 3.2 Abbreviations .....                                                                    | 7  |
+| 4 Main Requirements and High Level Principles .....                                        | 7  |
+| 4.1 Cross Phase Compatibility .....                                                        | 9  |
+| 4.2 Charging Entity Relationships .....                                                    | 9  |
+| 4.3 Charging guidelines for IP-Multimedia services .....                                   | 11 |
+| 4.3.1 User Charging Requirements .....                                                     | 11 |
+| 4.3.1.1 Session End Point Configurations .....                                             | 11 |
+| 4.3.1.2 Charging Principles For User Session Components .....                              | 12 |
+| 4.3.1.3 Other Charging Requirements .....                                                  | 13 |
+| 4.3.2 Roaming Charging Requirements .....                                                  | 14 |
+| 4.3.3 Interconnect Charging Requirements .....                                             | 15 |
+| 4.3.4 Conveyance & Usage charging requirements .....                                       | 16 |
+| 4.3.5 Charging 3 <sup>rd</sup> parties .....                                               | 16 |
+| 4.3.6 Advice of Charge (AoC) .....                                                         | 16 |
+| 4.3.7 Service Aware Charging Requirements .....                                            | 17 |
+| 4.4 Additional Charging requirements for prepay services.....                              | 17 |
+| 4.5 QoS and gating based on spending limit.....                                            | 18 |
+| 5 Collection of charging information.....                                                  | 18 |
+| 5.1 Charging information Requirements.....                                                 | 18 |
+| 5.1.1 Information provided by the user .....                                               | 18 |
+| 5.1.2 Information provided by the serving network .....                                    | 19 |
+| 5.1.3 Charged Party .....                                                                  | 20 |
+| 5.1.4 Information provided by the third party accessed by the user.....                    | 20 |
+| 5.2 Special Cases.....                                                                     | 21 |
+| 5.2.1 Long calls and sessions .....                                                        | 21 |
+| 5.2.2 Multimedia calls .....                                                               | 21 |
+| 5.2.3 Service Change .....                                                                 | 21 |
+| 5.2.4 E-Commerce.....                                                                      | 21 |
+| 5.2.5 Volume Based Charging.....                                                           | 21 |
+| 5.2.6 VAS.....                                                                             | 21 |
+| 5.2.7 Usage of IP Multimedia service .....                                                 | 22 |
+| 5.2.8 I- WLAN .....                                                                        | 22 |
+| 5.2.9 Charging for two( and multi)-phases services for IMS networks .....                  | 22 |
+| 5.2.10 CSG charging requirements for UTRAN and E-UTRAN.....                                | 22 |
+| 5.2.11 Inter-UE Transfer charging .....                                                    | 22 |
+| 5.2.12 Selected IP Traffic Offload charging.....                                           | 22 |
+| 6 Transfer of Charging Information.....                                                    | 23 |
+| 6.1 Integrity, Secrecy and Validation of Content and Receipt of Charging Information ..... | 23 |
+| 7 Accounting and Settlement .....                                                          | 23 |
+| 7.1 Delegation of charging authority.....                                                  | 23 |
+| 7.2 Fraud Control .....                                                                    | 23 |
+| 7.2.1 Fraud Control by the Home Environment .....                                          | 23 |
+| 7.2.2 Fraud Control by the Serving Network .....                                           | 24 |
+| 7.3 Cost Control .....                                                                     | 24 |
+| 7.3.1 Cross Phase Compatibility .....                                                      | 24 |
+| 7.4 Inter-network Settlement.....                                                          | 24 |
+| 8 Automatic Roaming Agreements.....                                                        | 24 |
+| 8.1 Routing the Registration Request.....                                                  | 25 |
+| 8.2 Settlement of charges .....                                                            | 25 |
+
+Annex A (informative) : Change history..................................................................................................26
+
+# Foreword
+
+This Technical Specification (TS) 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 Service Aspects of charging and billing of the 3GPP System.
+
+The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The present document will elaborate on the charging requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
+
+# --- 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 TS 22.101: "Service aspects; Service Principles".
+- [2] 3GPP TS 22.066: "Support of Mobile Number Portability (MNP)".
+- [3] 3GPP TS 22.234: "Requirements for 3GPP system to wireless local area network (WLAN) interworking".
+- [4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"
+- [5] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services"
+- [6] ETS 300 178: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information at call set-up time (AOC-S) supplementary service; Service description"
+- [7] ETS 300 179: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information during the call (AOC-D) supplementary service; Service description"
+- [8] ETS 300 180: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information at the end of the call (AOC-E) supplementary service; Service description"
+- [9] TS 183 047: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN IMS Supplementary Services; Advice Of Charge (AOC)"
+- [10] TS 183 058: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); SIP Transfer of IP Multimedia Service Tariff Information;Protocol specification"
+- [11] void
+- [12] 3GPP TS 22.220, "Service requirements for Home NodeBs and Home eNodeBs"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the definitions in [4] are supplemented by the following definitions:
+
+**Prepay service:** A prepay service allows a subscriber to pay in advance for the use of specific services, the prepay account may be updated each time the subscriber uses the services related to that account.
+
+**Real time:** Time, typically in number of seconds, to perform the on-line mechanism used for fraud control and cost control.
+
+**Session:** logical connection between parties involved in a packet switched based communication This term is used for IP connections rather than the term “call” that is normally used for a connection over conventional (circuit switched) systems.
+
+Note: Information about charging is typically collected in Charging Data Records (CDR).
+
+**Local Charging Zone (LCZ):** A logical grouping of a number of cells, where a special tariff applies for a select group of users. A network may have a number of LCZs. A LCZ does not necessarily need to be aligned with an LA or RA, i.e. the border of LCZ may not be the border of an LA or RA.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document the definition of abbreviations in [4] apply.
+
+# --- 4 Main Requirements and High Level Principles
+
+The main new requirements for 3GPP system charging and accounting are:
+
+- to provide charging information for all charges incurred and requiring settlement between the different commercial roles;
+- to allow fraud control by the Home Environment and the Serving network;
+- to allow cost control by the charged party;
+- to provide at the beginning of a chargeable event an indication to the charged party (if involved in the chargeable event) of the charges to be levied for this event;
+- to allow itemised billing for all services charged to each subscription, including voice and data calls, and services offered by home environments;
+- to enable the Home environment to provide a Prepay Service and to enable the serving network to support that Prepay Service for the Home environment's subscribers;
+- to allow interconnect (inter-operator) charging including mobile/fixed operator to mobile/fixed operator (circuit switched & IP), and mobile/fixed operator to IP network provider; and mobile/fixed operator to I-WLAN operator;
+- to allow Network operator to 3<sup>rd</sup> party supplier (e.g. Value Added Service Provider) charging;
+- to provide details required for Customer Care purposes;
+- to support the shared network architecture so that end users can be appropriately charged for their usage of the shared network, and network sharing partners can be allocated their share of the costs of the shared network resources.
+
+The high level principles that will guide the charging requirements are summarised as follows:
+
+- It shall be possible to charge separately for each type of medium used (e.g. voice, video, data) in a session and for each service used (e.g. voice call, streaming video, file download);
+- It shall be possible to charge for different levels of QoS applied for and/or allocated during a session for each type of medium or service used;
+- It shall be possible to charge each “leg” of a session separately. This includes the incoming and outgoing legs and any forwarded/redirected legs. (Note: The legs mentioned here are logical legs, i.e. not necessarily identical to actual signal and traffic flow. Even though tromboning may be avoided by optimal routing, the operator should still be able to charge for the ‘virtual legs’ of the call);
+- It shall be possible to charge unsuccessful calls and sessions (e.g. for billing purposes, to provide the user a full documentation of his call attempts);
+
+- The user can be charged according to the service used irrespective of the technology used to deliver it. (That is, the charge is not derived from whether 2G or 3G is used);
+- The user can be charged according to the technology used to deliver a service. (That is, different charges can be applied on 2G and 3G);
+- It shall be possible to charge a user according to the network resources used. For example, if a large bandwidth is required to use high quality video, the user could be charged accordingly. This is related to charging by QoS;
+- It shall be possible to charge users flexibly for the use of extra resources (in at least the same network) for all legs of the call. For example, if a video component is added to a voice call the use of extra radio resource at both ends of the call could be paid for by each user in the call or totally by the initiating user;
+- It shall be possible to suppress charging for certain types of connection e.g. when a customer receives tones or network announcements or during sessions such as automated pre-pay top-up;
+- It shall be possible to apply different charging based on tariff information provided by a 3<sup>rd</sup> party. This tariff information may change during the use of the service (e.g. based on menu selection in a voice response menu). In this case the requirement applies both for customer-charging and interconnect-charging;
+- It shall be possible for the home network to charge its customers while roaming in the same ways as when they are at home. For example, if duration based charging is used for charging for streaming music in the home network, then it shall be possible to apply the same principle when the user is roaming;
+- It shall be possible for operators to have the option to apply charging mechanisms that are used in GSM/GPRS. For example for duration of a voice call, for the amount of data transmitted (eg for streaming, file download, browsing) and for an event (one-off charge);
+- It shall be possible for a network operator to charge its users for activities while roaming so that the home network will get the capability to raise service charges depending on the roamed to network, e.g. because of inter operator charges for the use of service capabilities within the visited network which will in general depend on the serving network. The ability to supply all the necessary information for all the charging options will depend on the capability of the visited network. For service capabilities which are provided by the home network, however, it is required that the charging information is collected to allow to identify the serving network of the served subscriber;
+- It shall be possible for charging to be applied based on location, presence, push services etc.;
+- The network may provide information to the UE so that the UE is able to notify and indicate to the user the LCZs it is in. This allows the user to decide whether to accept/originate the service depending on the LCZs they are in;
+- It shall be possible to charge using pre-pay, post-pay, advice of charge, 3<sup>rd</sup> party charging techniques;
+- It shall be possible for the home network to apply different tariffs to national calls and short messages established/sent by their subscribers while roaming in their Home PLMN depending on whether or not the called subscriber's Home PLMN equals the calling subscriber's Home PLMN, rather than on the called subscriber's MSISDN;
+
+NOTE: This distinction is necessary only in the case, where the called subscriber's MSISDN may have been ported by Mobile Number Portability.
+
+- For circuit switched interconnection only a capability is required to collect information regarding user rate and user protocol at the interconnection point so that e.g. the identification of CS video telephony at the interconnection point for inter-network accounting purposes becomes possible.
+
+These new requirements and principles will allow users more freedom to obtain service when roaming, whilst providing effective cost and credit control for the Home Environment and User.
+
+## 4.1 Cross Phase Compatibility
+
+Where possible (e.g. services already defined within earlier releases), the charging information collected shall be consistent with the information already provided
+
+It is envisaged that 3GPP system will evolve beyond this Release with the addition of a number of new requirements for
+
+charging and billing, for example with the addition of a number of new requirements for charging and billing; these are noted in the appropriate sections below. The technical standards for each release should be developed in such a way that it is possible and practical to introduce these requirements, ideally in a backward compatible manner.
+
+NOTE: When a change is introduced which affects the 3GPP technical standards, it is said to be 'backward compatible' if existing equipment can continue to operate and perform correctly with equipment that conforms to the new implementation.
+
+## 4.2 Charging Entity Relationships
+
+In the process of introduction of the all-IP technology there will be a mixture of different types of entities using different types of technology.
+
+The diagram below shows the different entities involved in charging and their relationships.
+
+![Diagram illustrating Charging Entity Relationships across different network types.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+The diagram illustrates the charging relationships between various entities, categorized into four horizontal layers:
+
+- "Circuit-switched" Telecommunications Networks non-IP:** Contains 'Fixed Operator' and 'Mobile Operators'. Arrows show 'Interconnect Charging' and 'Roaming Charging' between them and the 'Mobile Network Operator'.
+- IP based Telecommunications Networks:** Contains 'Fixed Operator', 'I-WLAN Operator', 'Mobile Operators', 'Backbone e.g. GRX', and 'Internet'. Arrows show 'Usage Charging', 'Conveyance Charging', 'Roaming Charging', and 'Capacity Charging' between these entities and the 'Mobile Network Operator'.
+- Gateways:** Contains 'Portals'. An arrow shows 'Access Charging' between 'Portals' and the 'Mobile Network Operator'.
+- Content:** Contains 'Applications' and 'Information'. Arrows show 'Supplier Charging' between these entities and the 'Mobile Network Operator'.
+
+The central 'Mobile Network Operator' (yellow oval) is the hub for most charging relationships. It also provides 'Wholesale Charging' to a '3rd Party Service Provider' (green rectangle), which in turn provides 'Retail Charging' to 'User' entities (purple circles).
+
+Diagram illustrating Charging Entity Relationships across different network types.
+
+The types of entities and the relevant type of charging as shown on the diagram are as follows:
+
+- **Users:** retail charged by Mobile Network Operator or 3<sup>rd</sup> Party Service Provider.
+- **3<sup>rd</sup> Party Service Providers:** wholesale charged by Mobile Network Operator.
+- **Other telecommunications operators:** interconnect charging between Mobile Network Operator and non-IP "circuit-switched" Network Operators for call traffic carried; usage charging between Mobile Network Operator and IP-based Network Operators for session traffic carried.
+- **Other mobile operators:** roaming charging between these entities, this may require different mechanisms for IP-based types from the traditional "circuit-switched" types. Also, where mobile operators need to pass traffic to one another, there will be interconnect charging for non-IP "circuit switched" types; usage charging for IP-based types.
+
+- **I-WLAN operators:** where I-WLAN operators need to pass traffic to mobile operators or mobile operators to I-WLAN operators, there may be roaming and usage charging, .
+- **IP backbone carriers:** conveyance charging Mobile Network Operators for traffic carried.
+- **3<sup>rd</sup> Party content & application suppliers:** supplier charging between Mobile Network Operators and Value Added Service Providers for information exchanged.
+- **3<sup>rd</sup> Party Portals:** access charging between Mobile Network Operators and this entity.
+- **Internet:** charge for capacity of connection between Mobile Network Operator and Internet. An Operator pays a provider for a connection based on capacity, e.g. annual charge for a 2Mbit/s “pipe”.
+
+## 4.3 Charging guidelines for IP-Multimedia services
+
+### 4.3.1 User Charging Requirements
+
+This section describes the options required for the charging of end users. The network operator could charge users directly (retail charging) or charge a 3<sup>rd</sup> party service provider (wholesale charging). These requirements can therefore apply to retail and wholesale charging. Note that the word “session” is used to describe the connection between a user and either another user or a service. This term is used for IP connections rather than the term “call” that is normally used for a connection over conventional (circuit switched) systems.
+
+The various ways that users can establish sessions and the main components are described. Also, the required charging options are specified.
+
+#### 4.3.1.1 Session End Point Configurations
+
+A variety of different connection configurations are possible for IP multi-media independently of the components of the session being used. It should be possible to charge for the following types of sessions with the options identified. These charging options should be applicable to each medium separately. Note that not all the charging options need to be used and that some of the options can be used only if the particular party is using the resources of IMS:
+
+The table below lists some example session scenarios and describes some of the possible charging options for each scenario. The table does not list all possible session scenarios nor does it list all possible charging options for the scenarios. Rather, the intent of the table is to emphasize the numerous charging options that shall be supported by an IP Multimedia System due to the complexity of sessions possible. The charging options shall adequately account for all session resources used in order to enable the operators to apply flexible billing policies and to satisfy regional and/or national regulatory policies.
+
+In general, any session shall allow for the following charging options:
+
+- To apply the “Calling Party Pays” charging principle;
+- A 3<sup>rd</sup> party to be charged for all or part of the session;
+- Split charging between any of the parties, including 3<sup>rd</sup> parties;
+- Session setup and session resources to have different charging rules. Different rules would be applied for example, in a scenario where **A** calls an advertising number, say **B**. **B** could be a web-based toy advertisement number, for example. In this scenario, **A** could pay for the initiation fee (session setup), and **B** could pay for the session resource.
+- Any party can add another media to the current session in progress and any of the parties (not necessarily the one(s) being charged for the current session) can be charged for the additional media. For example, **A** calls **B** and **A** is paying for the audio; **B** adds a wireless video image to the call and pays for that portion. The individual resource set-up and usage should be separately identified. This supports the “Calling Party Pays” model;
+- During an active session, media types can change (e.g. audio changed to data) and shall be charged for appropriately. It is thus necessary to be able to detect a change of media during a session so that different rating may be applied.
+
+It should also be noted that during a multi-party session, normally if the charged party drops off the session, all components being charged to that party should drop. But it is foreseeable to support a service option that allows the
+
+charged party to continue to be charged even if they drop off the session. The charging rules should support this option.
+
+| No | CONNECTION                                                                                                                                               | DESCRIPTION                                                                                                                                                                                                                         | CHARGING OPTIONS REQUIRED                                                                                                                                                                                                                                                                                                                                               |
+|----|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1  | <b>A</b> sets up a session to <b>B</b>                                                                                                                   | <b>A</b> simple connection between 2 subscribers or a subscriber and a service (eg voicemail)                                                                                                                                       | <b>A</b> pays for the session set-up to <b>B</b><br><b>A</b> pays for the session resource to <b>B</b><br><b>B</b> pays for the session resource to <b>A</b>                                                                                                                                                                                                            |
+| 2  | <b>A</b> sets up a session to <b>B</b>                                                                                                                   | <b>A</b> simple connection where <b>B</b> is a "toll free" (800) type service                                                                                                                                                       | <b>B</b> pays for the session set-up<br><b>B</b> pays for the session resource<br><b>A</b> pays for part of the session resource (i.e. allowing split charging between <b>A</b> & <b>B</b> )                                                                                                                                                                            |
+| 3  | <b>A</b> requests session with <b>B</b> , <b>B</b> redirects to <b>C</b>                                                                                 | This is redirection. The connection path is not set up to <b>B</b> from <b>A</b> , instead <b>A</b> is told to set up a connection direct to <b>C</b>                                                                               | <b>A</b> pays for the session set-up to <b>B</b><br><b>A</b> pays for the session resource to <b>C</b><br><b>C</b> pays for the session resource to <b>A</b><br><b>A</b> pays for the session resource as though it were to <b>B</b> and <b>B</b> pays for the session resource to <b>C</b> as though it came from <b>B</b>                                             |
+| 4  | <b>A</b> requests session with <b>B</b> , <b>B</b> forwards to <b>C</b>                                                                                  | This is normal forwarding as in GSM. The connection path is <b>A</b> to <b>B</b> 's home network and <b>B</b> 's home network to <b>C</b>                                                                                           | <b>A</b> pays for the session set-up to <b>B</b><br><b>A</b> pays for the session resource as though it were to <b>B</b> and <b>B</b> pays for the session resource to <b>C</b> .                                                                                                                                                                                       |
+| 5  | <b>A</b> sets up sessions with multiple parties (Multi-party)                                                                                            | Connections to multiple parties are initiated by <b>A</b>                                                                                                                                                                           | <b>A</b> pays for the set-up of each session<br><b>A</b> pays for each of the sessions resource to each of the called parties<br>Each of the called parties pays for the session resource to <b>A</b>                                                                                                                                                                   |
+| 6  | <b>A</b> has a multi-party session where the individual parties set up the session to <b>A</b>                                                           | The multiple parties in the session initiate the session to <b>A</b>                                                                                                                                                                | Each party pays for the session set-up to <b>A</b><br><b>A</b> pays for the session resource to the multiple parties<br>The individual parties in the session each pay for the session resource to <b>A</b>                                                                                                                                                             |
+| 7  | <b>A</b> is in a session with <b>B</b> , then puts <b>B</b> on hold to set up a session with <b>C</b> , then returns to <b>B</b> after dropping <b>C</b> | <b>A</b> still has a connection to <b>B</b> while also in a session with <b>C</b> . The session with <b>B</b> continues after the session with <b>C</b> is terminated                                                               | <b>A</b> pays for each of session set-ups to <b>B</b> and <b>C</b><br><b>A</b> pays for the session resource to <b>B</b> & <b>C</b><br><b>B</b> & <b>C</b> pay for the session resource to <b>A</b>                                                                                                                                                                     |
+| 8  | <b>A</b> is in a session with <b>B</b> then answers a session request from <b>C</b> while keeping <b>B</b> on hold                                       | <b>A</b> still has a connection to <b>B</b> while also in a session with <b>C</b> . The session with <b>B</b> continues after the session with <b>C</b> is terminated                                                               | <b>A</b> pays for the session set-up to <b>B</b><br><b>C</b> pays for the session set-up to <b>A</b><br><b>A</b> pays for the session resource to <b>B</b> and <b>C</b><br><b>B</b> & <b>C</b> pay for the session resource to <b>A</b>                                                                                                                                 |
+| 9  | <b>A</b> sets up a session with <b>B</b> who is roaming in another network                                                                               | The connection is made from <b>A</b> to <b>B</b> 's home network and then forwarded to <b>B</b> in the visited network. (Normal GSM mechanism)<br>Alternatively, <b>A</b> is redirected directly to <b>B</b> in the visited network | <b>A</b> pays for the session set-up to <b>B</b><br><b>A</b> pays for the session resource as though it were to <b>B</b> in his home network and <b>B</b> pays for the session resource from his home network to the visited network<br><b>A</b> pays for the session resource to <b>B</b> in the visited network<br><b>B</b> pays for the session resource to <b>A</b> |
+
+#### 4.3.1.2 Charging Principles For User Session Components
+
+A number of different components can comprise a session. These components may be added or dropped from an ongoing session by any participating party. These components should be individually identifiable for charging purposes.
+
+Generally, the party that adds a component should be responsible for the payment for the use of the component. However, it should also be possible to charge all users that need an increase in resource to handle the component. An example is 2 users in an audio session where one of the users upgrades the session to videophone session. Both users could be charged extra for the use of the video component as this requires extra resource at both ends.
+
+Possible components are:
+
+- Voice
+- Audio (real time)
+- Audio (streaming)
+- Video (real-time)
+- Video (streaming)
+- Data (download/upload)
+- Data interactive eg web browsing
+- Messaging (SMS text type)
+- E-mail
+- Data stream (unspecified content) This is where the network operator acts as a “bit-pipe”
+
+It shall be possible to charge for each of these components separately in a session with the options shown in the table below.
+
+It shall be possible for operators to be able to charge for individual components of sessions even if there is no identifiable service. For example a proprietary codec may be used to set up an “end-to-end” speech session where the network operator acts as a “bit-pipe”. In this case, it should be possible for the operator to charge for this differentially. This type of component is called “datastream” in the table below.
+
+It might not be possible to apply some of the charging mechanism and type options described below depending on the capability of the networks used.
+
+| COMPONENT                         | CHARGING MECHANISM OPTIONS                                                             | CHARGING TYPE OPTIONS                                                                                                                   |
+|-----------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Voice                             | Charging principles as described in section 4.3.1.1                                    | Charging by duration of session<br>Charging by QoS requested and/or delivered<br>One-off set-up charge                                  |
+| Real time Audio and Video         | Charging principles as described in section 4.3.1.1                                    | Charging by duration of session<br>Charging by QoS requested and/or delivered<br>One-off set-up charge                                  |
+| Streaming Audio and Video         | Charged to the initiator of the request<br>Charged to the sender of the audio or video | Charging by duration of session<br>Charging by volume of data, optionally QoS-differentiated<br>One-off set-up charge                   |
+| Data (upload or download)         | Charged to the initiator of the request<br>Charged to the sender of the data           | Charging by duration of session<br>Charging by volume of data, optionally QoS-differentiated<br>One-off set-up charge                   |
+| Interactive Data                  | Charged to the initiator of the session                                                | Charging by duration of session<br>Charging by volume of data, optionally QoS-differentiated<br>One-off set-up charge                   |
+| Messaging (SMS text type)         | Charged to the initiator of the message<br>Charged to the recipient of the message     | Charging by event (eg like SMS)<br>Charging by volume of data                                                                           |
+| Unspecified content (data stream) | Charged to the initiator of the session<br>Charged to all parties involved             | Charging by duration of session<br>Charging by volume of data (sent & received), optionally QoS-differentiated<br>One-off set-up charge |
+
+#### 4.3.1.3 Other Charging Requirements
+
+The user will also be charged for additional activities while in a session, for example downloaded applications or information. The table below shows some of these requirements and the priority. [This section will need to be further developed.]
+
+| CHARGING REQUIREMENT                | DESCRIPTION                                                                                                                                                                  |
+|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Downloaded items                    | User is charged for a specific item downloaded eg a music file, video clip, application                                                                                      |
+| Location based services             | User is charged for receiving information on his location (charging based on accuracy as an option). This could be a stand-alone location query or linked to another service |
+| Content accessed or downloaded      | User is charged according to the value of the information. Eg weather information, share price or other financial information                                                |
+| M-Commerce                          | Electronic transactions to 3 <sup>rd</sup> party suppliers of goods & services                                                                                               |
+| Use of portal or other site         | User is charged for any access to a portal or any other site. This could be a one-off charge or based on duration or data volume of the portal or site use                   |
+| APN and associated content          | User is charged for access to a specific APN and for the content associated. Requirements are for further study.                                                             |
+| Actual duration of rendered service | User is charged (e.g. for premium rate services or hotline) based on the actual duration of the rendered service                                                             |
+
+### 4.3.2 Roaming Charging Requirements
+
+It shall be possible for a network operator to charge its users for activities while roaming. It shall be possible for a network operator to charge its users while roaming using the same principles used while on the home network. The ability to supply all the necessary information for all the charging options will depend on the capability of the visited network.
+
+In addition, the network operators have to charge each other for the use of their networks by roaming users. The methods of charging between operators may be different from the methods used to charge the user. For example, a user may be charged by duration for voice sessions made while roaming but the home network may pay the visited network by volume of data used.
+
+Mechanisms used in today's networks may also be applied e.g. Inter-Operator Tariff (IOT).
+
+The table below shows the types of charging principle that networks will require for roaming settlement and a priority for its provision.
+
+| ITEM                           | CHARGING METHOD DESCRIPTION                                                                                                                                                                                                    |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Charging for session use       | Sessions made by users while roaming charged according to the principles described in section 4.3.1.1, above. This includes duration and volume charging                                                                       |
+| Downloaded items               | Items downloaded by the user while roaming from providers associated with the visited network are charged back to the home network for onward charge to the user                                                               |
+| Location based services        | Location information provided by the visited network is charged back to the home network for possible onward charge to the user.                                                                                               |
+| Content accessed or downloaded | Information that is accessed by the user while roaming from providers associated with the visited network is charged according to its value by the visited network back to the home network for onward charge to the user.     |
+| M-Commerce                     | Charging requirements between visited and home networks for M-Commerce transactions made by a roaming user are for further study.                                                                                              |
+| Use of portal or other site    | The visited network may charge the home network for any access by the roaming user to a local portal or any other local site. This could be a one-off charge and/or based on duration or data volume of the portal or site use |
+| APN & associated content       | Charge by visited network to home network for access to a specific APN and for the content associated. Requirements are for further study.                                                                                     |
+
+### 4.3.3 Interconnect Charging Requirements
+
+This clause applies (but is not limited) to the following interconnection scenarios:
+
+- Interworking between two IMS-based networks
+- Interworking between IMS-based networks and PSTN/ISDN
+- Interworking between IMS-based networks and TISPAN NGN supporting PES
+- IMS transit scenario
+
+The following charging requirements principles and guidelines shall apply for IMS when interconnected to other systems:
+
+- Existing, legacy charging principles will need to be retained while there is a requirement to interwork with non-IP based “circuit switched” type of networks
+- All the charging and accounting information shall be collected as closest as possible to the interconnection point (subject to network element performance capabilities).
+- A session or a service instance shall be uniquely identified within a network domain to allow a correct accounting and charging.
+- The identities of the originating network and of the destination network shall be unique and transported at signalling layer. This applies also to transit scenarios.
+- The interconnecting provider(s) will be able to apply Inter Operator Tariff schemes both for offline and online charging.
+- Charging information will be available for recording at both ends of interconnected parties. The charging information shall be sufficient to enable inter operator accounting correlation and inter operator dispute resolution.
+- The real-time transfer of tariff information in interconnection scenarios shall be supported when the serving network supports it, in order to support value added services that are billed by the caller's operator (e.g. Premium rate services 0900 or hotlines).
+
+NOTE: Such services often appear as 3<sup>rd</sup> party services where the tariff information resides in the called network and the caller's operator does not have this information.
+
+- This tariff information must be submitted by the external provider in realtime, so that the caller's operator is capable of
+  - providing AoC (Advice of Charge) information to the caller.
+  - capturing the imported tariff information into charging records.
+
+The service-hosting network shall provide appropriate charging information to the caller's operator in a secure way, independently from the realtime transfer of charging information for AoC purposes.
+
+NOTE: Where required to support offline charging for third party services where the tariff information resides in the called network and the caller's operator needs to bill the end user for that service.
+
+### 4.3.4 Conveyance & Usage charging requirements
+
+It shall be possible for network operators (including mobile, fixed and IP backbone suppliers) to charge each other for the use of resources required to support user sessions. The items to be charged and the principles to be applied are described below.
+
+The methods of charging between operators could be different from the methods used to charge the user. For example, a user may be charged by duration for voice sessions but the mobile network may pay the fixed network or 3<sup>rd</sup> party carrier by volume of data used.
+
+| ITEM               | CHARGING METHOD DESCRIPTION                                                           |
+|--------------------|---------------------------------------------------------------------------------------|
+| Session use        | Charging according to the resources used by duration of session and/or by data volume |
+| Quality of Service | Charging by QoS delivered to and from the other network                               |
+
+### 4.3.5 Charging 3<sup>rd</sup> parties
+
+It shall be possible for network operators and 3<sup>rd</sup> parties to charge each other for the use of their resources. Third parties include content and application providers and portals.
+
+The items that will be charged and the principles are described below:
+
+| ITEM                 | CHARGING METHOD DESCRIPTION                                                                                                                                                |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Content accessed     | The 3 <sup>rd</sup> party charges the end user (via the network operator) for content accessed/downloaded                                                                  |
+| Access to site       | The 3 <sup>rd</sup> party is charged by the network operator for each "hit" by its users                                                                                   |
+| Location information | The 3 <sup>rd</sup> party is charged by the network operator for information on the location of the user. Amount charged could depend on accuracy of location information. |
+| Presence information | The 3 <sup>rd</sup> party is charged by the network operator for presence information about the user.                                                                      |
+| Pushed information   | The 3 <sup>rd</sup> party is charged by the network operator for each message pushed to the user, eg advertisements                                                        |
+
+### 4.3.6 Advice of Charge (AoC)
+
+The Advice of Charge (AoC) supplementary service allows the served user to be informed of MMTel session related charging information.
+
+AoC information may occur as:
+
+- Advice of Charge for Information purposes (AoCI): This supplementary service provides the information to
+
+produce an estimate of the cost of the service used. This means that the displayed value and the cost of the service used (e.g. corresponding bill item) may differ.
+
+- Advice of Charge for Charging purposes (AoCC): This supplementary service provides the means by which the UE may indicate the charge that will be made for the use of MMTel service (i.e. the cost of the service used.)
+
+AoC-information may be sent to the served user at the following phases of communication:
+
+- Charging information at communication set-up time (AOC-S): When the AOC-S supplementary service is activated, the IMS shall provide the user with information about the charging rates at communication establishment. In addition, the IMS may inform the served user at the communication set-up time if a change in charging rates is to take place after the communication set-up.
+- Charging information during the communication (AOC-D): After the AOC-D supplementary service is activated, the IMS shall provide the user with charging information for a communication during the active phase of this communication. The supplied charging information shall be provided as a rate of communication service (e.g. costs per minute) or as a cumulative charge incurred so far for the communication (i.e. charges recorded from the start of the communication and until the moment the charging information is sent to the served user), or as charging units. When the call is released, the network shall send the recorded charges for the communication to the served user.
+- Charging information at the end of the communication (AOC-E): When the AOC-E supplementary service is activated, the network shall provide the served user with charging information indicating the recorded charges for a communication when this communication is released.
+
+Compatibility with existing, legacy AoC principles from both fixed and mobile networks shall be taken into account. This comprises (but is not limited to) the following requirements for AoC as specified in TS 22.086 [5], ETS 300 178 [6], ETS 300 179 [7], ETS 300 180 [8], TS 183 047 [9] and TS 183 058 [10].
+
+AoC shall be also supported for interconnection scenarios.
+
+### 4.3.7 Service Aware Charging Requirements
+
+Service Aware Charging provides the means to perform charging based on identified IMS communication service and the service in use.
+
+To facilitate service aware charging, the system shall support the possibility to identify the IMS communication service and the service in use in the charging and accounting data collection.
+
+To ensure that service aware charging can be provided when roaming, the home network shall have the possibility to provide the unequivocally identified IMS communication service to the visited network.
+
+## 4.4 Additional Charging requirements for prepay services
+
+A prepay service allows a subscriber to pay in advance for the use of specific services, the prepay account will be decreased each time the subscriber uses the services related to that account.
+
+In a multi-service environment like 3GPP system, a subscriber can have different prepay accounts for different kinds of services (e.g. internet access, m-commerce, infotainment, location based services etc.).
+
+In order to guarantee the use of the prepay services, the following general requirements shall be fulfilled:
+
+- The prepay service shall check a subscriber's prepay account for coverage of the requested service charges prior to execution of that service.
+- All charging information related to a specific prepay account shall be prevented to the user when the prepay credit of that account is exhausted or expired.
+- All the ongoing charging information related to a specific prepay account shall be immediately (within a few seconds) interrupted as soon as the prepay credit of that account exhausts or expires.
+- The prepay service shall decrease the prepay account each time the subscriber uses the services related to that account.
+
+It should be possible to support more than one prepay account for a user if needed.
+
+To guarantee a meaningful multi-prepay account concept, at least 2 different prepay accounts should be supported.
+
+## 4.5 QoS and gating based on spending limit
+
+- When the subscriber spending limit has reached a pre-set limit, the system shall be able to trigger a QoS downgrade and/or restrict access to one, several or all IP services based on operator pre-defined thresholds.
+
+NOTE: A spending limit is the usage limit (e.g. monetary, volume, duration) that a subscriber is allowed to consume.
+
+- When the subscriber spending limit (e.g. monetary, volume, duration) has been increased, the system shall be able to modify resources (e.g. QoS, Bandwidth, access) to services accordingly.
+- The home network shall be able to enforce the subscriber spending limits for a roaming subscriber without having dedicated support of the feature in the visited network.
+- Additional signalling load should be minimized.
+
+# --- 5 Collection of charging information
+
+The standard shall support the collection and transfer of charging information in order to facilitate:
+
+- interworking with Release 98 and earlier releases
+- fraud management procedures;
+- unsuccessful calls and sessions documentation (e.g. for billing purposes);
+
+Note: collection of charging information due to error in the signalling flows (e.g. incomplete or erroneous call setup) are not required;
+
+- detailed itemised billing
+- allow for prepay charging
+
+Generally, the charging information collected shall support the high level principles in section 4 (above) and the requirements identified for inter-operator charging as elaborated by the GSM Association. The information listed below is the minimum requirement.
+
+## 5.1 Charging information Requirements
+
+Charging information shall be collected in the Serving Network to record chargeable User or Mobile Station activity and inter-carrier connections. Some of the information is provided by the user, other information is only available in the network element of the serving network.
+
+Depending on the type of charging information some of the data may not be available or might not be required.
+
+### 5.1.1 Information provided by the user
+
+The user's user equipment that is incurring the charge shall provide the following information to the serving network:
+
+- User identity used for authentication;
+- Home environment identity;
+- Terminal Identity and Terminal Class;
+- Destination endpoint identifier for service requested (e.g. B number);
+- Resource requested (e.g. bandwidth, connectionless);
+- QoS parameters (e.g. maximum delay);
+- IP Multimedia capability requested (e.g. media components).
+
+### 5.1.2 Information provided by the serving network
+
+The network serving the user shall provide the following information to the home environment:
+
+- All of the information listed in section above (Information provided by the user);
+- Serving network identity;
+- Recording network element identity;
+- Universal Time (UT) at which the service request was initiated;
+- Universal Time (UT) at which resources were provided for the service;
+- Universal Time (UT) at which the service execution was successfully completed;
+- Universal Time (UT) at which the service execution was unsuccessfully completed;
+- Local time of the serving cell when the service request was initiated for the originating or terminating UE. This could either be explicitly reported, or implicitly reported by providing three pieces of information: the UTC, the time zone offset from UTC, and an indication of daylight savings time;
+- Cause for unsuccessful completion of the service execution. At least the following causes shall be included:
+  - the terminating party does not respond;
+  - communication rejected by the terminating party;
+  - network determined terminating party busy;
+  - network congestion;
+  - terminating party non reachable (out of coverage, switched-off);
+  - destination non reachable (non active address, non-existing address).
+- Resource allocated to the user;
+- Quantity of data transferred both to and from the user;
+- QoS provided to the user;
+- Location of the user in the standard format used for 3GPP location based services (e.g. geographical co-ordinates, Cell ID);
+- Network determined PLMN ID and Cell ID;
+- whether GSM Optimal Routing was applied;
+- If IN or CAMEL services were applied, the service parameters and the actually used destination number and calling party number identification;
+- Time duration covered by this charging information to an accuracy of at least 1 second;
+- Unique identity of the chargeable event which allows the billing system to correlate all charging information belonging to the same chargeable event;
+- Unique charging information identity (unique per network element in a period of about 100 days);
+- IP Multimedia capability provided to the user;
+- VAS information;
+- Identifier of third party accessed by the user;
+- Presence Information;
+- Service Identification (eg voice call, video call, data download etc);
+
+- Supplementary Services used;
+- Prepay account identifier and related information.
+
+### 5.1.3 Charged Party
+
+For subscription related chargeable events the charging information shall indicate the charged party, i.e. normally the calling party. As alternative it should be possible to apply reverse charging or to charge the event to a party not involved in the event itself (e.g. a company as VPN subscriber). It should be possible for multiple leg calls (e.g. forwarded, conference or roamed) to be charged to each party as if each leg was separately initiated. However, in certain types of call, the originating party may wish/be obliged to pay for other legs (e.g. SMS MO may also pay for the MT leg.).
+
+It shall be possible to change the chargeable party at the call set-up.
+
+In case of inter-network chargeable events, the charging information usually does not contain the charged party, but it can be derived from network configuration information contained in the charging event data..
+
+For each party to be charged for a chargeable event or parts of it charging information shall be collected.
+
+### 5.1.4 Information provided by the third party accessed by the user
+
+Supply of Value Added Services, especially in IP based environment, is often made with the aid of third parties typically represented by portals and content/application providers.
+
+To execute an effective charging of these services, the following charging information should be provided by the third party:
+
+- Third party identity;
+- Type of service (information, entertainment, gaming, public utility);
+- Change in the type of service provided to the user;
+- Type of content (picture, videoclip, mp3 file, java file);
+- Universal Time (UT) at which the service request was initiated;
+- If a service change happens, Universal Time (UT) at which the service provision was initiated;
+- Universal Time (UT) at which the service execution was successfully completed;
+- Universal Time (UT) at which the service execution was unsuccessfully completed;
+- Cause for unsuccessful completion of the service execution. At least the following causes shall be included:
+  - the terminating party does not respond;
+  - communication rejected by the terminating party;
+  - network determined terminating party busy;
+  - network congestion;
+  - terminating party non reachable (out of coverage, switched-off);
+  - destination non reachable (non active address, non-existing address).
+- Cause for Abnormal reject of the service;
+- Universal Time (UT) for abnormal reject of the service
+
+## 5.2 Special Cases
+
+### 5.2.1 Long calls and sessions
+
+The advent of packet data services, which can extend for very long periods of time (days, weeks etc), although at low
+
+cost because charges are based on data throughput, may mean that charging information are only output at the end of very long periods. For this reason the serving network shall support the transmission of charging information also during the life of the packet data session, either when some charge value is reached or some duration or some data volume or all three, to allow for both charging settlement and cost control.
+
+### 5.2.2 Multimedia calls
+
+During one call the user may invoke different services like speech, data transmission, video and audio, which may lead to a separate collection of charging information for each service in different network components. In this case, the billing system shall be able to correlate these charging information and to indicate to the user that they belonged to one call.
+
+### 5.2.3 Service Change
+
+Sufficient information about a service change using SCUDIF changing a voice call to a CS multimedia call, or vice versa, shall be collected to enable operators to apply maximum flexibility in charging. This information is collected on top of the data that is already available for the underlying call now subject for the service change.
+
+On a service change using SCUDIF the following information shall be collected on both sides of the call:
+
+- 1) Initiator of the service change (A side or B side)
+- 2) Type of the service change (To speech or to multimedia)
+- 3) For a service change to multimedia: nature of the service change (User or network initiated service change)
+
+### 5.2.4 E-Commerce
+
+The 3GPP system may be used to trade soft goods (e.g. information, video, audio), or hard goods (e.g. books) of high or low value per item between the user and a merchant. It shall be possible for such merchants to charge users directly for services they provide. Electronic payment mechanisms are or shall be made available through other standards (micropayment, credit card payment, etc), and therefore are outside the scope of this specification 3GPP shall not prohibit the use of these mechanisms, and, where possible, shall provide the basic communications transport to allow them to be used effectively.
+
+However, if the serving network acts as merchant of soft goods, it may charge the user directly, collecting the related charging information as described above or using micropayment mechanisms.
+
+### 5.2.5 Volume Based Charging
+
+It shall be possible to charge for the total volume of data/packets sent and received by the user.
+
+### 5.2.6 VAS
+
+It shall be possible to charge the user for Value Added Services offered by the network in terms of access, surfing, queries etc. irrespectively of the volume of data sent or received by the user.
+
+### 5.2.7 Usage of IP Multimedia service
+
+It shall be possible to charge the usage of IP multimedia service independently of the volume of data sent or received by the user. Information on the IP Multimedia capability provided to the user (e.g. voice, mixture of voice and video component, numbers of parties) should be available in the charging information.
+
+### 5.2.8 I- WLAN
+
+I-WLAN charging issues are captured in 3GPP TS 22.234 [3].
+
+### 5.2.9 Charging for two( and multi)-phases services for IMS networks
+
+It shall be possible to charge a service change in case of VAS that foresee different service phases at different tariffs. This applies both at the interconnection between IMS network operators and at the interconnection between IMS network operators and service providers.
+
+This information is collected on top of the data that is already available for the underlying communication now subject for the service change.
+
+### 5.2.10 CSG charging requirements for UTRAN and E-UTRAN
+
+Detailed requirements for CSG access may be found in 3GPP TS 22.220 [12].
+
+Charging related requirements:
+
+- It shall be possible to charge subscribers for consuming network services via a CSG cell based on the following information:
+  - CSG identity of the CSG cell
+  - subscriber membership of the CSG
+  - type of service consumed by the subscriber
+  - addition to and deletion from a CSG
+- An operator shall be able to provide applicable tariffing information when a subscriber is added to a CSG.
+- The network operator shall be able to charge both on-line and off-line for subscribers consuming network services via a CSG cell.
+
+### 5.2.11 Inter-UE Transfer charging
+
+It shall be possible to charge for Inter-UE Transfer (i.e. transfer/replication/sharing) of media components across multiple IMS UEs .
+
+### 5.2.12 Selected IP Traffic Offload charging
+
+The network shall be able to apply volume-base charging to a subscriber regardless of whether the subscriber's traffic has been offloaded from the mobile operator's network as described in 3GPP TS 22.101 [1].
+
+For subscribers' traffic offloaded from the mobile operator network, the network shall be able to apply either online or offline charging.
+
+# --- 6 Transfer of Charging Information
+
+The efficient transfer of charging information between serving networks and from serving networks to home environments requires a standardised interface between these entities. It shall be possible to define different time intervals for the transfer of charging information between serving network and home environment (e.g. when a chargeable event occurs, when a chargeable event is initiated by the user, when a chargeable event terminates, at regular intervals during a chargeable event).
+
+The format of the charging information exchanged (see 5.1) shall be standardised. It shall be possible for the relevant parties to agree minimum and maximum age of charging information transferred between themselves.
+
+## 6.1 Integrity, Secrecy and Validation of Content and Receipt of Charging Information
+
+The transmission mechanism for charging information collected in 5.1 above shall ensure its integrity and secrecy.
+
+A mechanism to validate the source and integrity of the information shall be provided so that:
+
+- the home environment shall be able to validate the source and integrity of the charging information supplied by the serving network;
+- the serving network shall be able to validate the source and integrity of the charging information supplied by the user;
+- the serving network shall have proof that services were provided to a specified user.
+
+# --- 7 Accounting and Settlement
+
+The serving network shall collect and process the charging data generated in its network elements. The record of each individual transaction shall be reported to the home environment at short time intervals in order to allow further processing by the billing system in the Home Environment, provide itemised bills, and to deal with any disputes regarding charges both for users and for other visited networks and home environment.
+
+The standard shall support the transfer of charging data at different intervals as required by the Home Environment (e.g. short time intervals, real time, other regular intervals).
+
+## 7.1 Delegation of charging authority
+
+The registration process allows the home environment to authenticate users before they incur any charges. Once authenticated, the home environment then delegates authority to the serving network operator with which he has a direct commercial relationship to incur charges for services supplied to that user. The direct commercial relationship may be with either the serving network operator if known directly by the home environment or a network operator known to the home environment. This procedure uses each network as trusted third parties in a chain of delegation between entities, thus allowing commercial transactions between entities who have no direct commercial dealings. There shall be an authentication procedure between all entities in the 3GPP system which have a commercial relationship.
+
+In the case of a multimedia telephony, when the HPLMN requests that optimal media routing is not applied, the VPLMN shall disable optimal media routing for all the subscribers of the requesting network.
+
+## 7.2 Fraud Control
+
+A mechanism to control fraud shall be provided by the serving networks and the home environment.
+
+### 7.2.1 Fraud Control by the Home Environment
+
+Charging information shall be collected by the home environment in real time from all serving networks which its users are allowed to use. The billing system in the home environment shall process the information in real time and provide the means to set charge thresholds per time interval upon which some actions may be started, such as informing the customer care centre or even barring the user in the HLR.
+
+It shall be possible for the Home Environment to define different time intervals for the collection and the processing of charging information (e.g. real time, short time, other regular intervals).
+
+### 7.2.2 Fraud Control by the Serving Network
+
+Charging information shall be collected from the network elements and processed in real time. This will allow the serving network to always be aware of the exposure to visitors. A limit for the accumulated charges for all visitors from one home environment or a limit per visitor may be agreed between the home environment and the serving network.
+
+It shall be possible for the Serving Network to define different time intervals for the collection and the processing of charging information (e.g. real time, short time, other regular intervals).
+
+## 7.3 Cost Control
+
+A mechanism shall be standardised providing an indication to the user (if involved in the chargeable event) of the charges to be levied for a chargeable event. This mechanism shall be able to handle all possible charging scenarios, and all service and tariff variants that the home environment and the serving network may offer to the user.
+
+The user shall be able to set in his home environment a limit for the accumulated charges per time interval. Upon exceeding this limit or prior to incurring a charge which would exceed the limit, certain actions may be desired by the user:
+
+- notification to the user, requesting to extend the limit; or
+- Home Environment barring allowing no further originating calls; or
+- Home Environment barring cancelling the roaming permission.
+
+### 7.3.1 Cross Phase Compatibility
+
+For Release 99 the cost control mechanism may be based on Advice of Charge. However the Release 99 standards should not prevent the future implementation of the full Cost Control requirements.
+
+The Release 99 standards should allow these new features to be introduced in a backward compatible manner; specifically terminals conforming to Release 99 standards should continue to support the Release 99 service requirements when operating with future implementations of Advice of Charge in the Home Environment.
+
+## 7.4 Inter-network Settlement
+
+Mechanisms shall also be provided to allow inter-network settlement of charges on a bulk basis. The same mechanisms shall be used between home environments and serving networks. This will allow each of these parties to meter the total input and output of charges and thus determine the payments required on a periodic basis between each of the parties with which they directly interact. The mechanisms used shall allow each of the parties to meter charge flows independently, with the aim of matching the values recorded at both sides of the same interface. The imbalance in charge flow shall be accumulated in short time, such that each entity can be informed when a threshold has been exceeded and determine whether to continue.
+
+# 8 Automatic Roaming Agreements
+
+Support for the requirements in this section is not required in Release 99. However the Release 99 standards should not prevent the future implementation of this requirement in a backward compatible manner (eg a roaming broker enabled Home Environment should inter-operate with a R99 Serving Network).
+
+It is a requirement that users shall be able to obtain service and use chargeable services with networks with whom neither they nor their home environment have any direct commercial agreement. This shall be enabled by interworking via trusted third parties. Each Home Environment shall interwork with one or more serving network operators, with whom they would negotiate a commercial roaming agreement and test the interworking. Any user wishing to use the services of a particular serving network would register with that serving network, that would either directly or indirectly interwork with the home environment. Fraud and cost control mechanisms shall be used to ensure that charges incurred for 3GPP services do not exceed the credit limits set. This can be applied for the user and the other roles involved in commercial dealings. In practice, any serving network shall be capable of operating as a roaming broker.
+
+![Diagram illustrating the Registration and Roaming Process. The diagram shows four entities: User, Servina Network Operator, Roaming Broker, and Home Environment. The process involves four messages: Registration Request (User to Home Environment), Authorisation (Home Environment to Servina Network Operator), Online Signalling Information (Servina Network Operator to Home Environment), and Call Detail Records (Servina Network Operator to Home Environment).](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg)
+
+```
+sequenceDiagram
+    participant User
+    participant SNO as Servina Network Operator
+    participant RB as Roaming Broker
+    participant HE as Home Environment
+    Note left of SNO: Registration Request
+    User->>HE: Registration Request
+    Note right of HE: Authorisation
+    HE-->>SNO: Authorisation
+    Note right of SNO: Online Signalling Information
+    SNO-->>HE: Online Signalling Information
+    Note right of SNO: Call Detail Records
+    SNO-->>HE: Call Detail Records
+```
+
+Diagram illustrating the Registration and Roaming Process. The diagram shows four entities: User, Servina Network Operator, Roaming Broker, and Home Environment. The process involves four messages: Registration Request (User to Home Environment), Authorisation (Home Environment to Servina Network Operator), Online Signalling Information (Servina Network Operator to Home Environment), and Call Detail Records (Servina Network Operator to Home Environment).
+
+Figure 1: Registration and Roaming Process
+
+## 8.1 Routing the Registration Request
+
+The same mechanisms used for routing calls and resolving addresses shall be used to route the subscription identity
+
+back to its Home Environment. The standard shall support a routing identification mechanism to allow a serving network, which does not maintain its own list of all known HE, to determine the appropriate route to reach a given HE. A number of alternative routes may be possible, and ideally the system should be capable of determining the lowest cost to the end user.
+
+Typically, smaller networks will only have a limited number of external connections to other networks or clearing houses, but may not know which one to use for an unknown (new) HE. In this case, the serving network may make a number of inquiries for each route to determine the lowest cost route to handle the call.
+
+## 8.2 Settlement of charges
+
+Settlement of charges incurred by a user shall be on a wholesale basis between the different parties involved in the registration link. By authorising a user to register, or a roaming broker to pass that on, each party is in turn authorising charges up to a maximum credit limit with the adjacent party. Any charges levied can then be paid to the adjacent party on a wholesale basis at the end of a mutually agreed accounting period. Funds are thus passed between each party for the services supplied by the network operator in a serial fashion.
+
+# Annex A (informative) : Change history
+
+| <b>Document information</b> |               |                                                                                                                                    |
+|-----------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Date</b>                 | <b>Status</b> | <b>Comment</b>                                                                                                                     |
+| 27 August 1996              | Version 0.0.1 | SMG 1 WPC output draft for editing purposes only                                                                                   |
+| 3 February 1997             | Version 0.0.3 | Presented to SMG1 WPC meeting, London<br>Incorporated changes agreed at Dec 96 Meeting including charging model and charge enquiry |
+| 20 April 1997               | Version 0.0.4 | Presented to SMG1 WPC meeting in Sophia Antipolis<br>Incorporated text submitted at Feb 97 meeting                                 |
+| 4 June 1997                 | Version 1.0.0 | Proposed Version 1 incorporating changes discussed at SMG1 WPC meeting in Antwerps, June 97                                        |
+| 23 June 1997                | Version 1.0.2 | Incorporated remaining changes discussed at SMG1 WPC meeting in Antwerps, June 97                                                  |
+| 27 Nov 1997                 | Version 1.1.0 | Preparation for SMG1 UMTS Helsinki meeting, incorporating text from reports 22.24 and 22.71                                        |
+| 4 Dec 1997                  | Version 1.2.0 | Incorporated comments from 22.24, 22.71 developed at SMG1 UMTS Meeting in Helsinki                                                 |
+| 26 April 1999               | Version 3.1.0 |                                                                                                                                    |
+| 8 Dec 1997                  | Version 1.2.2 | Format and editorial changes by ETSI Sec for SMG#24                                                                                |
+| 5 November 1998             | Version 1.3.0 | Incorporate changes discussed at SMG1 Rome, including reflecting changes to 22.01 role model.                                      |
+| 12 January 1999             | Version 1.3.1 | Accept Changes and send to editing SMG1 Rome Tdoc 98-0859 Agreed by correspondence. Reviewed by Rapporteur Jan 13, 1999            |
+| 27 January 1999             | Version 2.0.0 | To be presented at SMG#28 for Approval                                                                                             |
+| February 1999               | Version 3.0.0 | Approved at SMG#28                                                                                                                 |
+| March 1999                  | Version 3.0.1 | Reformatted for TSG SA                                                                                                             |
+
+| Change history |           |           |        |      |     |       |     |                                                                                                                                                                                                        |       |       |                                 |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|---------------------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                                                                                                                                                        | Old   | New   | Work Item                       |
+| SMG#28         |           |           | 22.115 |      |     |       |     | Version 3.0.0 Approved                                                                                                                                                                                 |       | 3.0.0 |                                 |
+| SP-03          | SP-99106  | S1-99234  | 22.115 | A001 | 1   | R99   | F   | Clarification of the Charging Service                                                                                                                                                                  | 3.0.0 | 3.1.0 |                                 |
+| SP-05          | SP-99454  | S1-99817  | 22.115 | 002  |     | R99   | D   | clarify the mandatory features supported by the standard                                                                                                                                               | 3.1.0 | 3.2.0 |                                 |
+| SP-05          | SP-99454  | S1-99762  | 22.115 | 003  |     | R99   | B   | Addition of Charging for Volume of Data and some edits                                                                                                                                                 | 3.1.0 | 3.2.0 |                                 |
+| SP-07          | SP-000066 | S1-000171 | 22.115 | 004  |     | R99   | D   | Clarifications to 22.115                                                                                                                                                                               | 3.2.0 | 3.3.0 |                                 |
+| SP-11          | SP-010065 | S1-010258 | 22.115 |      |     | Rel-4 |     | Creation of Release 4                                                                                                                                                                                  | 3.3.0 | 4.0.0 |                                 |
+| SP-11          | SP-010058 | S1-010192 | 22.115 | 005  |     | Rel-5 | B   | Introduction of charging for IPMultimedia and Event Based Charging                                                                                                                                     | 3.3.0 | 5.0.0 | IMS-OAM                         |
+| SP-12          | SP-010260 | S1-010572 | 22.115 | 006  |     | Rel-5 | B   | Introduction of online charging for prepaid services                                                                                                                                                   | 5.0.0 | 5.1.0 | PRPY                            |
+| SP-15          | SP-020053 | S1-020643 | 22.115 | 007  |     | Rel-5 | B   | CR 22.115 Charging and billing<br><br>Some latitude was given by SA #15 to MCC to ensure that section numbering of original sections did not change.                                                   | 5.1.0 | 5.2.0 | OAM-CH                          |
+| SP-19          | SP-030023 | S1-030184 | 22.115 | 008  | -   | Rel-6 | B   | CR to TS 22.115 - Clarification of the charging entity WLAN                                                                                                                                            | 5.2.0 | 6.0.0 | WLAN-CR                         |
+| SP-19          | SP-030035 | S1-030270 | 22.115 | 009  | -   | Rel-6 | B   | Requirements for Network Sharing in Rel-6                                                                                                                                                              | 5.2.0 | 6.0.0 | NTShar-CR                       |
+| SP-20          | SP-030263 | N4-030449 | 22.115 | 013  | 1   | Rel-6 | A   | Charging Requirements in an MNP environment                                                                                                                                                            | 6.0.0 | 6.1.0 | TEI                             |
+| SP-21          | SP-030467 | S1-030764 | 22.115 | 014  | -   | Rel-6 | D   | Alignment of 22.115 with 21.801                                                                                                                                                                        | 6.1.0 | 6.2.0 | TEI-6                           |
+| SP-21          | SP-030467 | S1-030976 | 22.115 | 015  | -   | Rel-6 | B   | CS interconnection requirement for the identification of user data rate and user protocol at the interconnection point for charging purposes                                                           | 6.1.0 | 6.2.0 | TEI-6                           |
+| SP-22          | SP-030701 | S1-031296 | 22.115 | 016  | -   | Rel-6 | F   | CR on 22.115: CS interconnection correction of an improper statement on the requirement for the identification of user data rate and user protocol at the interconnection point e.g. for inter-network | 6.2.0 | 6.3.0 | TEI-6                           |
+| SP-23          | SP-040101 | S1-040259 | 22.115 | 020  | -   | Rel-6 | D   | Extraction of redundant WLAN charging information – now in WLAN TS22.234                                                                                                                               | 6.3.0 | 6.4.0 | WLAN                            |
+| SP-29          | SP-050621 |           | 22.115 | 0021 | 2   | Rel-6 | F   | Clarification of Charging Implications of SCUDIF                                                                                                                                                       | 6.4.0 | 6.5.0 | CS video and voice improvements |
+| SP-30          | SP-050808 | -         | 22.115 | 0022 | 2   | Rel-6 | F   | Clarification of Charging Implications of SCUDIF                                                                                                                                                       | 6.5.0 | 6.6.0 | CS_VSS                          |
+| SP-31          | SP-060203 | -         | 22.115 | 0023 | 3   | Rel-6 | F   | Making charging principles also applicable to prepay services                                                                                                                                          | 6.6.0 | 6.7.0 | TEI6                            |
+| SP-33          | -         | -         | 22.115 | -    | -   | Rel-7 | -   | Produced as a result of the implementation of Rel-8 CR 0024 and 0025 to Rel-6                                                                                                                          | 6.7.0 | 7.0.0 | -                               |
+| SP-33          | SP-060483 | S1-060963 | 22.115 | 0024 | -   | Rel-8 | B   | Local Charging Zone Concept                                                                                                                                                                            | 7.0.0 | 8.0.0 | LCZR                            |
+| SP-33          | SP-060483 | S1-060962 | 22.115 | 0025 | -   | Rel-8 | B   | Local Charging Zone Requirements                                                                                                                                                                       | 7.0.0 | 8.0.0 | LCZR                            |
+| SP-37          | SP-070567 | S1071093  | 22.115 | 30   | 1   | Rel-8 | A   | Correction for incomplete text on Universal Time (UT) at which resources were provided for the service                                                                                                 | 8.0.0 | 8.1.0 | TEI8                            |
+| SP-38          | SP-070845 | S1-071784 | 22.115 | 0036 | 1   | Rel-8 | C   | Inclusion of fixed operator in interconnection charging requirements                                                                                                                                   | 8.1.0 | 8.2.0 | CIMS8-TIS                       |
+| SP-38          | SP-070845 | S1-071785 | 22.115 | 0034 | 2   | Rel-8 | B   | TISPAN charging requirements                                                                                                                                                                           | 8.1.0 | 8.2.0 | CIMS8-TIS                       |
+| SP-38          | SP-070857 | S1-071933 | 22.115 | 0035 | 2   | Rel-8 | B   | Charging Requirements for Unsuccessful sessions and calls                                                                                                                                              | 8.1.0 | 8.2.0 | TEI8                            |
+
+| Change history |           |           |        |      |     |        |     |                                                                                                  |        |        |               |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|--------------------------------------------------------------------------------------------------|--------|--------|---------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel    | Cat | Subject/Comment                                                                                  | Old    | New    | Work Item     |
+| SP-38          | SP-070863 | S1-071929 | 22.115 | 0037 | 3   | Rel-8  | B   | Charging for two-phases services                                                                 | 8.1.0  | 8.2.0  | CHRG2PH       |
+| SP-39          | SP-080031 | S1-080252 | 22.115 | 0038 | 2   | Rel-8  | F   | Advice of Charge (AoC) requirements                                                              | 8.2.0  | 8.3.0  | CIMS8-TIS     |
+| SP-39          | SP-080034 | S1-080332 | 22.115 | 0039 | 3   | Rel-8  | B   | HNB/HeNB - Closed Subscriber Group (CSG) charging for UTRA and E-UTRA                            | 8.2.0  | 8.3.0  | HomeNB        |
+| SP-39          | SP-080192 | -         | 22.115 | 0040 | 2   | Rel-8  | F   | Correction of charging requirement for multi-phase services                                      | 8.2.0  | 8.3.0  | CHRGMPH       |
+| SP-43          | SP-090195 | S1-090332 | 22.115 | 0044 | -   | Rel-9  | B   | HNB/HeNB Charging Requirements                                                                   | 8.3.0  | 9.0.0  | EHNB          |
+| SP-45          | SP-090652 | S1-093360 | 22.115 | 0047 | 1   | Rel-10 | B   | Charging requirements for replication and sharing of multi-media session across multiple IMS UEs | 9.0.0  | 10.0.0 | eIMS_SC C-IDT |
+| SP-46          | SP-090849 | S1-094309 | 22.115 | 0048 | 1   | Rel-10 | B   | Charging aspects for Selected IP Traffic Offload                                                 | 10.0.0 | 10.1.0 | LIPA_SIP TO   |
+| SP-49          | SP-100583 | S1-102391 | 22.115 | 0053 | 2   | Rel-11 | B   | Charging considerations for MMTel when Optimal Media Routing is used                             | 10.1.0 | 11.0.0 | OSCAR         |
+| SP-49          | SP-100584 | S1-102394 | 22.115 | 0054 | 1   | Rel-11 | B   | QoS and gating based on spending limit                                                           | 10.1.0 | 11.0.0 | QoS_SSL       |
+| SP-50          | SP-100800 | S1-103229 | 22.115 | 0055 | 1   | Rel-11 | B   | Clarification of Subscriber Spending Limit                                                       | 11.0.0 | 11.1.0 | QoS_SSL       |
+| SP-50          | SP-100804 | S1-103232 | 22.115 | 0056 | 3   | Rel-11 | B   | Clarification of location requirement                                                            | 11.0.0 | 11.1.0 | NWK-PL2IMS    |
+| -              |           |           |        |      |     |        |     | LTE logo changed into LTE Advanced logo                                                          | 11.1.0 | 11.1.1 | -             |
+| SP-51          | SP-110171 | S1-110325 | 22.115 | 0057 | 2   | Rel-11 | B   | Addition of additional network provided time information for IMS charging                        | 11.1.0 | 11.2.0 | NWK-PL2IMS    |
+| SP-52          | SP-110379 | S1-111067 | 22.115 | 0058 | -   | Rel-11 | B   | Charging clarifications for INIPUI                                                               | 11.2.0 | 11.3.0 | INPUI         |
+| SP-53          | SP-110582 | S1-112398 | 22.115 | 0059 | 2   | Rel-11 | C   | SIPTO Terminology and Charging requirements Update                                               | 11.3.0 | 11.4.0 | TEI11         |
+| SP-54          | SP-110813 | S1-113448 | 22.115 | 0061 | 3   | Rel-11 | B   | Clarification of service based charging                                                          | 11.4.0 | 11.5.0 | TEI11         |
+| SP-57          | SP-120522 | S1-122038 | 22.115 | 0066 | -   | Rel-11 | B   | Removal of INIPUI Charging Requirements from Rel-11                                              | 11.5.0 | 11.6.0 | INIPUI        |

marked/Rel-11/22_series/22153/raw.md

@@ -0,0 +1,236 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Foreword .....                                                             | 4  |
+| Introduction .....                                                         | 4  |
+| 1 Scope.....                                                               | 5  |
+| 2 References.....                                                          | 5  |
+| 3 Definitions and abbreviations .....                                      | 5  |
+| 3.1 Definitions.....                                                       | 5  |
+| 3.2 Abbreviations .....                                                    | 5  |
+| 4 General description .....                                                | 6  |
+| 5 High level requirements .....                                            | 6  |
+| 5.1 General .....                                                          | 6  |
+| 5.2 Priority session treatment in originating network .....                | 6  |
+| 5.3 Priority session progression .....                                     | 6  |
+| 5.4 Priority session treatment in terminating network .....                | 7  |
+| 5.4a Priority Data Bearer Service .....                                    | 7  |
+| 5.5 Priority levels .....                                                  | 7  |
+| 5.6 Invocation on demand .....                                             | 7  |
+| 5.7 Multimedia priority service code/identifier.....                       | 7  |
+| 5.8 Roaming .....                                                          | 8  |
+| 5.9 Handover.....                                                          | 8  |
+| 5.10 Interworking with CS domain .....                                     | 8  |
+| 5.10.1 Mobile origination in the CS domain -> MPS mobile termination ..... | 8  |
+| 5.10.2 MPS mobile origination -> mobile termination to the CS domain ..... | 8  |
+| 5.11 Network Management Functions .....                                    | 8  |
+| 6 MMI aspects.....                                                         | 8  |
+| 7 Security and privacy.....                                                | 8  |
+| 8 Charging aspects .....                                                   | 8  |
+| Annex A (informative): Change history.....                                 | 10 |
+
+# --- 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
+
+The response to emergency situations (e.g., floods, hurricanes, earthquakes, terrorist attacks) depends on the communication capabilities of public networks. In most cases, emergency responders use private radio systems to aid in the logistics of providing critically needed restoration services. However, certain government and emergency management officials and other authorised users have to rely on public network services when the communication capability of the serving network may be impaired, for example due to congestion or partial network infrastructure outages, perhaps due to a direct or indirect result of the emergency situation.
+
+Multimedia Priority Service, supported by the 3GPP system set of services and features, is one element creating the ability to deliver calls or complete sessions of a high priority nature from mobile to mobile networks, mobile to fixed networks, and fixed to mobile networks.
+
+# --- 1 Scope
+
+The present document specifies the service requirements for Multimedia Priority Service (MPS).
+
+The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered within the scope of this document although these interactions may be specified in other standards.
+
+# --- 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 TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TR 22.952: "Priority Service Guide".
+- [3] 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 1".
+- [4] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2".
+- [5] 3GPP TS 24.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Service User:** An individual who has received a priority level assignment from a regional/national authority (i.e., an agency authorised to issue priority assignments) and has a subscription to a mobile network operator that supports the MPS feature.
+
+## 3.2 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].
+
+|            |                             |
+|------------|-----------------------------|
+| <b>MPS</b> | Multimedia Priority Service |
+|------------|-----------------------------|
+
+# --- 4 General description
+
+MPS allows qualified and authorized users to obtain priority access to the next available radio channel on a priority basis before other PLMN users, during situations when PLMN congestion is blocking session establishment attempts. In addition, MPS supports priority sessions on an "end-to-end" priority basis.
+
+MPS is intended to be utilised for Voice, Video, and Data bearer services in the Packet-switched (PS) domain and the IP Multimedia Subsystem (IMS).
+
+# --- 5 High level requirements
+
+## 5.1 General
+
+Upon invocation of MPS, the system shall provide preferential treatment for access and core network resources associated with the session (i.e., signalling and media bearer related resources within a domain and across domains). A Service User is assigned a priority level by a regional/national authority i.e., agency authorised to issue priority levels. Upon MPS invocation the calling Service User's priority level is used to identify the priority to be used for the session being established.
+
+Pre-emption of active sessions shall be subject to regional/national regulatory requirements.
+
+Subject to regional/national regulatory policy, a PLMN should have the capability to retain public access as a fundamental function. Therefore, MPS traffic volumes should be limited (e.g. not to exceed a regional/national specified percentage of any concentrated network resource, such as eNodeB capacity), so as not to compromise this function.
+
+## 5.2 Priority session treatment in originating network
+
+When an MPS session is originated by a Service User, the session shall receive priority treatment (priority access to voice or traffic channels) in the originating PLMN based on the originating Service User priority information (i.e., priority indication and priority level).
+
+When an MPS session is requested by a Service User and the originating network supporting session establishment cannot assign the necessary resources to the MPS session, the MPS session request shall be:
+
+- Queued,
+- Processed for the next available resource in accordance with the calling Service User's priority level and session initiation time.
+
+The network shall support the capability to inform the calling Service User about the status of the MPS session (e.g., tones or signalling messages can be used to indicate that the session request has been queued).
+
+If the queued MPS session times out, then normal session processing applies.
+
+## 5.3 Priority session progression
+
+For an MPS session, a Service User shall receive priority session treatment/progression through the PLMN (s). In case the MPS session traverses or terminates in other networks (e.g., the PSTN), the network providing priority session treatment/progression shall support the capability to indicate to the other network that this is an MPS session.
+
+Note: If there is no agreement on priority handling between networks, the priority does not carry across network boundaries.
+
+## 5.4 Priority session treatment in terminating network
+
+When a terminating network receives an MPS session establishment attempt, the MPS session shall receive priority treatment (priority access to voice or traffic channels) in the terminating PLMN, based on the originating Service User priority information. The priority information of the terminating party is irrelevant.
+
+When the terminating network supporting session establishment cannot assign the necessary resources to the MPS session, the MPS session request shall be:
+
+- Queued,
+- Processed for the next available resource in accordance with the calling Service User's priority level and session arrival time.
+
+The network shall support the capability to inform the calling Service User about the status of the MPS session (e.g., tones or signalling messages can be used to indicate that the session request has been queued).
+
+If the queued MPS session times out, then normal session processing applies.
+
+## 5.4a Priority Data Bearer Service
+
+When a Service User invokes Priority Data Bearer Service for transport of any data packets to and from a Service User, the network should give priority in admission of the Priority Data Bearer and in packet data scheduling in the event of congestion (for new sessions and upgrade to existing sessions), subject to regional/national regulatory policy. Specifically:
+
+- A Priority Data Bearer service session should be given priority for admission over non-Priority Data Bearer sessions during times of congestion;
+- Data packets belonging to a Priority Data Bearer service should not be dropped before data packets belonging to a non-Priority Data Bearer service session, when the network is experiencing congestion, subject to the limitation imposed by public access. Priority Data Bearer session QoS, as required for the type of service invoked (e.g., packet delay), should be maintained throughout the activity of the data session.
+
+## 5.5 Priority levels
+
+The Service User shall be assigned one of "n" user priority levels. The priority levels are defined with 1 being the highest priority level and "n" being the lowest priority level.
+
+Priority levels are a matter of regional/national and operator policies.
+
+In case of interconnecting networks that have different priority levels, mappings between priority levels should be established.
+
+## 5.6 Invocation on demand
+
+MPS priority shall be invoked only when requested by the Service User.
+
+MPS is applied when idle resources required for an origination session request are not available.
+
+If idle resources are available when MPS is requested, the request shall be allowed to proceed as normal, but marked as an MPS request..
+
+An indication of an MPS session should be propagated towards the terminating network regardless of the availability of resources in the originating network.
+
+## 5.7 Multimedia priority service code/identifier
+
+MPS shall be requested by including an MPS code/identifier in the session origination request, or optionally, by using an MPS input string (e.g., an MPS public user identity).
+
+## 5.8 Roaming
+
+MPS shall be supported when the Service User is roaming and the serving (originating and terminating) network(s) supports MPS.
+
+## 5.9 Handover
+
+MPS shall be supported during and after the handover (i.e., sessions shall continue to get priority treatment in the network during and after the handover).
+
+For handover of an MPS call to CS, only the active, or if all calls are on hold, only the most recently active call shall be transferred and receive the priority treatment in CS. Any remaining sessions in PS shall be released.
+
+## 5.10 Interworking with CS domain
+
+### 5.10.1 Mobile origination in the CS domain -> MPS mobile termination
+
+For a Priority Service voice call, as described in [2] and as specified in [3, 4, 5], originated by a Service User in the CS Domain, MPS shall support Mobile Termination of the session in the IMS. The priority level received from the CS domain shall be used in the IMS.
+
+### 5.10.2 MPS mobile origination -> mobile termination to the CS domain
+
+For an MPS voice session originated by a Service User in the IMS, MPS shall support delivery of the voice session to the serving CS Domain. The calling Service User priority level shall be sent to the CS Domain.
+
+## 5.11 Network Management Functions
+
+Based on regional/national requirements and network operator policy, an MPS session shall be exempted from network management controls up to the point where further exemption would cause network instability. Congestion controls, overload controls, and load balancing shall not adversely impact MPS.
+
+# --- 6 MMI aspects
+
+No MMI aspects have been identified specifically for MPS.
+
+# --- 7 Security and privacy
+
+Access to MPS shall be determined based on the subscriber's profile. A level of authorisation in addition to authorisation to use the IMS is required.
+
+Unauthorized access to MPS shall be prevented.
+
+# --- 8 Charging aspects
+
+A network supporting MPS shall be capable of recording the following charging information, in addition to non-MPS information:
+
+- MPS invocation attempt and successful session set-up,
+- Session bearers (originations and/or terminations) on which MPS was used to gain access to resources,
+- Recording of MPS information, e.g., priority level.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |      |     |        |     |                                                                         |        |        |        |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|-------------------------------------------------------------------------|--------|--------|--------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel    | Cat | Subject/Comment                                                         | Old    | New    | WI     |
+| SP-37          | SP-070576 | -         | 22.146 | -    | -   | Rel-8  | -   | Raised to v.2.0.0 by MCC for approval as v.8.0.0                        | 1.3.0  | 2.0.0  | PRIOR  |
+| SP-37          | -         | -         | 22.146 | -    | -   | Rel-8  | -   | Raised to v.8.0.0 by MCC following SA#37 approval                       | 2.0.0  | 8.0.0  | PRIOR  |
+| SP-40          | SP-080305 | S1-080438 | 22.153 | 0004 | -   | Rel-8  | D   | CR to TS 22.153 on applicability of MPS                                 | 8.0.0  | 8.1.0  | PRIOR  |
+| SP-40          | SP-080310 | S1-080727 | 22.153 | 0003 | 1   | Rel-9  | B   | CR to TS 22.153 on an optional service invocation method for MPS        | 8.0.0  | 9.0.0  | ePRIOR |
+| SP-41          | SP-080494 | -         | 22.153 | 0006 | 1   | Rel-9  | A   | Trusted domain support                                                  | 9.0.0  | 9.1.0  | PRIOR  |
+| SP-42          | SP-080778 | S1-084394 | 22.153 | 0007 | 3   | Rel-9  | F   | Correction to priority levels and networks                              | 9.1.0  | 9.2.0  | EPRIOR |
+| SP-42          | SP-080778 | S1-084365 | 22.153 | 0008 | 1   | Rel-9  | C   | Indication of MPS                                                       | 9.1.0  | 9.2.0  | EPRIOR |
+| SP-47          | SP-100188 | S1-100101 | 22.153 | 0011 | -   | Rel-10 | F   | Clarification of MPS Service Aspects - Video and Data Bearer service    | 9.2.0  | 10.0.0 | TEI10  |
+| SP-47          | SP-100188 | S1-100458 | 22.153 | 0012 | 3   | Rel-10 | B   | Priority for data bearer services                                       | 9.2.0  | 10.0.0 | TEI10  |
+| SP-49          | SP-100580 | S1-102180 | 22.153 | 0013 | -   | Rel-10 | B   | Priority for data bearer services                                       | 10.0.0 | 10.1.0 | TEI10  |
+|                |           |           |        |      |     |        |     | Clarifying PS to CS handover requirements for multimedia priority calls |        |        |        |
+| SP-51          | SP-110172 | S1-110182 | 22.153 | 0014 | 2   | Rel-11 | F   |                                                                         | 10.1.0 | 11.0.0 | TEI11  |
+| SP-52          | SP-110376 | S1-111413 | 22.153 | 0016 | 1   | Rel-11 | B   | Priority treatment for Network Management functions                     | 11.0.0 | 11.1.0 | TEI11  |
+| SP-52          | SP-110376 | S1-111414 | 22.153 | 0017 | 1   | Rel-11 | C   | Clarification of Priority Information                                   | 11.0.0 | 11.1.0 | TEI11  |

marked/Rel-11/22_series/22183/raw.md

@@ -0,0 +1,376 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                |    |
+|----------------------------------------------------------------|----|
+| Foreword .....                                                 | 4  |
+| 1 Scope.....                                                   | 5  |
+| 2 References.....                                              | 5  |
+| 3 Definitions, symbols and abbreviations .....                 | 5  |
+| 3.1 Definitions.....                                           | 5  |
+| 3.2 Abbreviations .....                                        | 6  |
+| 4 CRS Service Requirements.....                                | 6  |
+| 4.1 Basic functionality of CRS service .....                   | 6  |
+| 4.1.1 Functionality - IMS domain .....                         | 6  |
+| 4.1.2 Functionality - CS domain.....                           | 7  |
+| 4.2 Normal procedures with successful outcome.....             | 8  |
+| 4.2.1 Provisioning and Withdrawal .....                        | 8  |
+| 4.2.2 Activation and Deactivation and Update.....              | 8  |
+| 4.2.2.1 Activation.....                                        | 8  |
+| 4.2.2.2 Deactivation .....                                     | 8  |
+| 4.2.2.3 Update .....                                           | 8  |
+| 4.2.3 Basic scenarios .....                                    | 8  |
+| 4.2.3.1 Only calling party has activated the CRS service ..... | 8  |
+| 4.2.3.2 Only called party has activated the CRS service .....  | 8  |
+| 4.2.3.3 Both parties have activated the CRS service .....      | 9  |
+| 4.2.4 Interaction with Supplementary Services.....             | 9  |
+| 4.2.4.2 Originating Identification Restriction (OIR) .....     | 9  |
+| 4.2.4.3 Communication Diversion (CDIV) .....                   | 9  |
+| 4.2.4.4 Communication Waiting (CW).....                        | 10 |
+| 4.2.4.5 Explicit Communication Transfer (ECT) .....            | 11 |
+| 4.3 CRS service configuration .....                            | 12 |
+| 4.4 The content of CRS .....                                   | 12 |
+| 4.5 Inter-working CRS .....                                    | 13 |
+| 4.5.1 Inter-working between PLMNs .....                        | 13 |
+| 4.5.2 Inter-working between CS and IMS .....                   | 13 |
+| Annex A (informative): Change history.....                     | 14 |
+
+# --- 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 document specifies the requirements and technical considerations for Customized Ringing Signal (CRS) service in the PS and CS domains, especially additional features for roaming and interoperability support.
+
+This document considers voice and multi-media CRS, so the CRS user may experience favourable songs, multi-media clips or other customized CRS.
+
+This document specifies the CRS filtering service requirements that allow the user to filter the CRS.
+
+# --- 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 TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
+- [3] 3GPP TS 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
+- [4] ETSI TISPAN TR 181 015: "Requirements for Customized Originating and Terminating Multimedia Information Presentation (COMIP/CTMIP) and Customized Originating and Terminating Multimedia Information Filtering (COMIF/CTMIF) Requirements Analysis".
+
+# --- 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] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Ringing Signal:** A Ringing Signal is played to the called party as an incoming communication indication during establishment of a communication.
+
+**Customized Ringing Signal:** A Ringing Signal that is customized by the calling party or the called party. A Customized Ringing Signal (CRS) may e.g. be a picture, a piece of recorded or composed music, greeting words, voice, advertisement or video.
+
+**CRS inter-action:** CRS inter-action is the interaction of the CRS service with other services, e.g. inter-action with Call Forwarding.
+
+**CRS inter-working :** CRS inter-working is the interworking of a CRS service over different domains or subsystems (CS or IMS) as well as between PLMNs.
+
+**CRS content provider:** A service provider that provides a set of Ring Signals for use as CRS for subscribers of the CRS service. A 3GPP operator may be a CRS content provider.
+
+## 3.2 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].
+
+|     |                           |
+|-----|---------------------------|
+| CRS | Customized Ringing Signal |
+|-----|---------------------------|
+
+---
+
+# 4 CRS Service Requirements
+
+## 4.1 Basic functionality of CRS service
+
+The Customized Ringing Signal service (CRS service) is an operator specific service by which an operator enables the subscriber to customize the ringing signal which is played to the called party. The CRS content will be provided to the called party only it's allowed by the called party.
+
+- The service user shall be able to subscribe to the services, activate the services, update the settings, e.g. to change his active CRS.
+- The CRS service shall override the default ringing signal towards the called party provided that media components are compatible..
+- The called party shall be able to experience the CRS set by the called service subscriber.
+- The called party shall be able to experience the CRS set by the calling service subscriber.
+- The operator should have the capability to store multiple CRSs per service subscriber.
+- It should be possible to inform the user about status and changes in his service, e.g. service expiry date or a particular CRS content.
+
+Note: In the CS domain, this information may be provided by existing means such as SMS and web access.
+
+- The operator shall be able to charge for the CRS service and the related contents.
+- It shall be possible for a subscriber to subscribe to CRS that is provided by a third party content provider.
+- CRS service should not negatively affect the conversation between calling and called parties, e.g. no voice /video clipping.
+- If the CRS can't be played for some reason (for example, the CRS system fails, or the CRS content expiry is up, or the called user roams from 3G network to 2G network, or other reasons), the called party shall experience the default ringing signal instead of the CRS.
+- When the multi-media CRS fails to be played in some condition (such as the caller roams from 3G network to 2G network or network congestion occurs), the voice CRS may be played instead if possible.
+
+### 4.1.1 Functionality - IMS domain
+
+The CRS services in IMS domain are defined by:
+
+- For the CRS service, the called party's operator shall be able to configure which CRS should have priority, the one set by the called or calling CRS service subscriber. The called party's operator shall be able to take into account the called CRS service subscriber's preferences. By default, if no preference is set, the CRS set by the called party has priority.
+- When the called party answers the communication the CRS shall stop or continue to play during the conversation, depending on operator or user preferences. By default, if no preference is set, when the called party answers the communication the CRS shall stop.
+- When the calling party is setting up a communication, the calling party shall be able to send an indication to the CRS service which CRS to play to the called party.
+
+- The called party shall have the capability to copy the CRS of the calling party as his own CRS while the CRS is being played. The pre-requisites are that the calling party has enabled CRS sharing, if applicable, for that instance of CRS and that both parties are subscribers to the same HPLMN.
+
+Note 1: A CRS might also be copied offline via e.g. web interface but that functionality does not require standardisation.
+
+Note 2: The expression "to copy the CRS" does not necessarily mean that the CRS is actually copied. It may also mean that a purchase request is being sent to the CRS service provider.
+
+- The CRS service shall be able to send CRS to the called party on per call basis.
+- The CRS service shall send an indication to the multimedia information presentation service which multimedia information to play to the called party (e.g. when the called party is notified about an incoming communication, the CRS subscriber can send an indication to the CRS service which CRS to play to the called party).
+- The CRS subscriber may be able to replace one CRS with another one while it is playing.
+- The CRS subscriber may be able to receive CRS service after communication establishment.
+
+### 4.1.2 Functionality - CS domain
+
+The CRS services in CS domain are defined by:
+
+- For the CRS service, the called party's operator shall be able to configure which CRS should have priority, the one set by the called or calling CRS service subscriber. By default, if no preference is set, the CRS set by the called party has priority.
+- When the called party answers the communication the CRS shall stop.
+- The called party shall have the capability to copy the CRS of the calling party as his own CRS. The pre-requisites are that the calling user has enabled CRS sharing, if applicable, for that instance of CRS and that both parties are subscribers to the same HPLMN and the called party is within the HPLMN.
+
+Note 1: A CRS might also be copied offline via e.g. web interface but that functionality does not require standardisation.
+
+Note 2: The expression "to copy the CRS" does not necessarily mean that the CRS is actually copied. It may also mean that a purchase request is being sent to the CRS service provider.
+
+- During the call setup over the CS domain, the called party UE shall be able to start automatically downloading and streaming CRS content through PS domain. Downloaded CRS content shall not be used for other purposes except CRS service.
+
+## 4.2 Normal procedures with successful outcome
+
+### 4.2.1 Provisioning and Withdrawal
+
+The CRS Service can be provisioned and withdrawn by the operator on a per subscriber basis.
+
+If the CRS service is not provisioned, the called party shall not experience content of CRS, he should experience the default ringing signal.
+
+Note: Procedures for provisioning and withdrawal are out of scope of standardisation.
+
+### 4.2.2 Activation and Deactivation and Update
+
+#### 4.2.2.1 Activation
+
+When a subscriber activates his CRS Service he shall be able to specify which CRS a called user should experience, or use the operator's default setting.
+
+After a subscriber has activated his CRS Service a called user should experience the CRS that was chosen by the subscriber.
+
+#### 4.2.2.2 Deactivation
+
+After a subscriber has deactivated his CRS Service a called user shall experience the default ringing signal.
+
+#### 4.2.2.3 Update
+
+When a subscriber updates his CRS Service, updated CRS should overwrite the existing one.
+
+### 4.2.3 Basic scenarios
+
+#### 4.2.3.1 Only calling party has activated the CRS service
+
+In the following scenarios, contained in table 1, it is assumed that only the calling party (A) has activated his CRS Service. Calling party (A) is calling B. The called party has subscribed and not activated the CRS service.
+
+Note: To activate his CRS means the user has chosen that his CRS should be experienced.
+
+The CRS of A is CRS-A.
+
+**Table 1: Normal Operation Scenarios**
+
+|   | Called party B<br>(condition) | Required behaviour                                                                     |
+|---|-------------------------------|----------------------------------------------------------------------------------------|
+| 1 | B, ringing                    | Depending on B settings, B will experience either CRS-A or the default ringing signal. |
+
+#### 4.2.3.2 Only called party has activated the CRS service
+
+In the following scenario, contained in table 2, it is assumed that only the called party (B) has activated his CRS Service. Calling party (A) is calling B. The calling party has not subscribed and/or activated the CRS service.
+
+The CRS of B is CRS-B.
+
+**Table 2: Normal Operation Scenarios**
+
+|   | Called party B<br>(condition) | Required behaviour                                 |
+|---|-------------------------------|----------------------------------------------------|
+| 1 | B, ringing                    | B experiences CRS-B or the default ringing signal. |
+
+#### 4.2.3.3 Both parties have activated the CRS service
+
+In the following scenarios, contained in table 3, it is assumed that both the calling party (A) and called party (B) have activated the CRS Service. Calling party (A) is calling B.
+
+The CRS of B is CRS-B, the CRS for A is CRS-A.
+
+**Table 3: Normal Operation Scenarios**
+
+|   | <b>Called party B<br/>(condition)</b> | <b>Required behaviour</b>                                                                                                               |
+|---|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B, ringing                            | Depending on B settings, B experiences CRS-A, CRS-B or the default ringing signal.<br>If B has not set preference, B experiences CRS-B. |
+
+### 4.2.4 Interaction with Supplementary Services
+
+#### 4.2.4.1 Originating Identification Presentation (OIP)
+
+No impact. The OIP service is performed independently of the CRS, the CRS will use the information provided by OIP.
+
+The CRS service shall be able to distinguish information provided via service platform and information provided by the network (e.g. public identity sends by the OIP service).
+
+#### 4.2.4.2 Originating Identification Restriction (OIR)
+
+The OIR service takes precedence over the CRS service subscribed by the calling party or by the called party.
+
+#### 4.2.4.3 Communication Diversion (CDIV)
+
+Table 4 describes when the forwarded-to party (C) has not subscribed or activated the CRS service.
+
+**Table 4: Supplementary Service Interaction Scenarios**
+
+|   | <b>Called party B<br/>(condition)</b>                                                        | <b>Forwarded-to-<br/>party<br/>(condition)</b> | <b>Required behaviour</b>                                   |
+|---|----------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------------------------------------------|
+| 1 | B has activated Call Forwarding Unconditional (CFU) to C and A's call is forwarded to C      | C, ringing                                     | C experiences CRS-A or CRS-B or the default ringing signal. |
+| 2 | B has activated Call Forwarding on Busy (CFB) to C, B is busy and A's call is forwarded to C | C, ringing                                     | C experiences CRS-A or CRS-B or the default ringing signal. |
+| 3 | B has activated Call Forwarding on No Reply (CFNRy) to C and A's call is forwarded to C      | C, ringing                                     | C experiences CRS-A or CRS-B or the default ringing signal. |
+| 4 | B has activated Call Forwarding on Not Reachable (CFNRc) to C and A's call is forwarded to C | C, ringing                                     | C experiences CRS-A or CRS-B or the default ringing signal. |
+
+Table 5 describes when the forwarded-to-party (C) has subscribed and activated the CRS service.
+
+The CRS of C is CRS-C.
+
+**Table 5: Supplementary Service Interaction Scenarios**
+
+|   | <b>Called party B<br/>(condition)</b>                                                                                                                           | <b>Forwarded-<br/>to-party<br/>(condition)</b> | <b>Required behaviour</b>                                                                                                                              |
+|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Call Forwarding Unconditional (CFU), Call Forwarding on Busy (CFB) or Call Forwarding on Not Reachable (CFNRc) to C. A's call is forwarded to C | C, ringing                                     | Depending on operator settings, subscriber C will experience the CRS-C or CRS-A or CRS-B or the default ringing signal.                                |
+| 2 | B has activated Call Forwarding on No Reply (CFNRy) to C and A's call is forwarded to C                                                                         | C, ringing                                     | B experiences the standard ringing signal until B's CFNRy timer has expired. Then C experiences CRS-C or CRS-A or CRS-B or the default ringing signal. |
+
+Note: in addition to playing the applicable CRS, related operator settings allow (see [4], 7.1.1):
+
+- Case 1: when CRS-B is played to C, CDIV may also be set to present B's number to the forwarded-to user.
+- Case 2: when CRS-B is played to C, CDIV may also be set to NOT present B's number to the forwarded-to user.
+- Case 3: CRS-A may be provided to C when B's operator has chosen not to send CRS-B.
+
+#### 4.2.4.4 Communication Waiting (CW)
+
+If the called party B has activated the communication waiting service and he is busy, depending on the operator's settings, the called party will experience either the CRS service or the default communication waiting indication.
+
+If B experiences the CRS service, B shall receive appropriate media in order to limit perturbation on the ongoing communication with C (e.g. CRS audio information may be replaced by the default communication waiting tone).
+
+Table 6 describes the situation that only the calling party A has subscribed and activated the CRS service.
+
+**Table 6: Supplementary Service Interaction Scenarios**
+
+|   | <b>Called party B<br/>(condition)</b>  | <b>Required behaviour</b>                                                                                                                                                                   |
+|---|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Communication Waiting, | Depending on operator settings or user preference, B experiences the communication waiting indication or CRS-A whose audio information is replaced by the communication waiting indication. |
+
+Table 7 describes the situation that only the called party B has subscribed and activated the CRS service.
+
+**Table 7: Supplementary Service Interaction Scenarios**
+
+|   | <b>Called party B<br/>(condition)</b>  | <b>Required behaviour</b>                                                                                                                                                                   |
+|---|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Communication Waiting, | Depending on operator settings or user preference, B experiences the communication waiting indication or CRS-B whose audio information is replaced by the communication waiting indication. |
+
+Table 8 describes the situation that both the calling party A and called party B have subscribed and activated the CRS service.
+
+**Table 8: Supplementary Service Interaction Scenarios**
+
+|   | <b>Called party B<br/>(condition)</b>  | <b>Required behaviour</b>                                                                                                                                                                         |
+|---|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Communication Waiting, | Depending on operator settings or user preference, B experiences the communication waiting indication or CRS-A/CRS-B whose audio information is replaced by the communication waiting indication. |
+
+#### 4.2.4.5 Explicit Communication Transfer (ECT)
+
+In case of immediate transfer the called party C shall either experience the CRS from CRS-A or CRS-C depending on operator settings and if A or C has activated the CRS service.
+
+In case of consultative transfer, when A is on hold and B has invoked the ECT service between A and C, C shall either experience the CRS from CRS-B or CRS-C depending on operator settings and if B or C has activated the CRS service. When the communication is established between A and C, C shall either experience the CRS from CRS-A or CRS-C depending on operator settings and if A or C has activated the CRS service.
+
+## 4.3 CRS service configuration
+
+The CRS subscriber should be able to configure the service with a service profile based on the following parameters:
+
+1. CRS content descriptor – Pointing to the right content or combination of contents (e.g. personal prompt plus chosen music/video track)
+2. CRS timing descriptor – Time of day, day of week, specific date and intervals based on each of those parameters.
+3. User (called/calling party) descriptor – user ID (or group ID of users), user presence, user location, CRS user charging mode
+
+Note 1: As location information may be restricted in some instances, the default user location may be set to “unknown”
+
+Note 2: Presence information for a CS user is limited to attached or detached.
+
+The CRS service shall be able to select the appropriate CRS according to the CRS user profile.
+
+A CRS subscriber who has activated his service, shall be able to select and update his settings - e.g. select a different CRS than the current one. It should be possible to charge the subscriber for selection / update of the CRS settings.
+
+A storage mechanism for a user Profile relevant to CRS and/or CRS filtering should be supported.
+
+A user/subscriber and/or CRS service provider should be able to access/manage CRS and/or a CRS filtering User Profile.
+
+A means of managing Access rights for User Profile components and media content should be supported.
+
+The network should provide the capability for the called/forwarded party to reject CRS provided by the calling party according to some rules:
+
+- reject all CRS, unconditionally.
+- reject CRS for unknown parties and accept all known parties,
+- reject CRS for parties identified as with malicious information in a black list and accept all others,
+- prompt the user to accept/reject CRS only for unknown parties and accept CRS all others (default)
+- For IMS CRS, it should be possible to prompt the user to accept or reject CRS for each incoming call (e.g. to present CRS or not).
+
+## 4.4 The content of CRS
+
+The content of CRS can be CRS such as music, voice, text, or video.
+
+The CRS may be composed of music, voice, text, video, which can be provided by the CRS content provider, operator or by the user himself.
+
+The content of the CRS service may be dynamically created, possibly taking into account information available in the network, e.g. calling and/or called user's location and/or presence information.
+
+The dynamic content of CRS service may be stored in the network in order to be experienced again by the called party. This may be requested by the called party, calling party, or service provider. The content may be downloaded to the UE or streamed down to the UE when the CRS is playing.
+
+## 4.5 Inter-working CRS
+
+### 4.5.1 Inter-working between PLMNs
+
+. The CRS service should therefore fulfil the following end user requirements:
+
+- When receiving a communication from another PLMN, the called party shall be able to experience the CRS set by the calling party.
+- When receiving a communication from another PLMN, the called party shall be able to experience the CRS set by the called party.
+- When roaming to another PLMN, the called party shall be able to experience the CRS set by the called party.
+- When roaming to another PLMN, the called party shall be able to experience the CRS set by the calling party.
+- The called party shall be able to experience the CRS set by the calling party who is roaming to another PLMN.
+
+### 4.5.2 Inter-working between CS and IMS
+
+The CS and IMS based CRS services should fulfil the following end user requirements:
+
+- When receiving a communication from another domain (CS or IMS), the called party shall be able to experience the CRS set by the calling party.
+- When receiving a communication from another domain (CS or IMS), the called party shall be able to experience the CRS set by the called party.
+- When receiving a communication from another domain (CS or IMS), the called party should be able to copy the CRS of the calling user as his own CRS. The pre-requisites are that the calling user has enabled CRS sharing, if applicable, for that instance of CRS and that both users are subscribers to the same HPLMN.
+
+The scope of this interoperability may result in a limited service capability.
+
+# --- Annex A (informative): Change history
+
+| Change history |           |           |        |      |     |       |     |                                    |        |        |     |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|------------------------------------|--------|--------|-----|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                    | Old    | New    | WI  |
+| SP-42          | SP-080789 | S1-084326 | 22.183 | -    | -   | Rel-9 | -   | Approved at SA#42                  | 2.0.0  | 9.0.0  | CRS |
+| SP-46          | SP-090838 | S1-094332 | 22.183 | 0001 | 1   | Rel-9 | F   | CRS media components compatibility | 9.0.0  | 9.1.0  | CRS |
+| 2011-03        | -         | -         | -      | -    | -   | -     | -   | Update to Rel-10 version (MCC)     | 9.1.0  | 10.0.0 |     |
+| 2012-09        | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-11 by MCC           | 10.0.0 | 11.0.0 |     |

marked/Rel-11/22_series/22240/raw.md

@@ -0,0 +1,781 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                   |           |
+|-----------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                    | 4         |
+| Introduction .....                                                                | 4         |
+| 1. Scope.....                                                                     | 5         |
+| 2. References.....                                                                | 5         |
+| 3 Definitions and abbreviations .....                                             | 5         |
+| 3.1 Definitions.....                                                              | 5         |
+| 3.2 Abbreviations .....                                                           | 6         |
+| 4 General description .....                                                       | 6         |
+| 4.1 Introduction .....                                                            | 6         |
+| 4.1.1 Intended Usage of the Generic User Profile .....                            | 7         |
+| 4.1.2 Benefits of the 3GPP Generic User Profile for individual stakeholders ..... | 7         |
+| 4.2 Conceptual view of the GUP.....                                               | 8         |
+| 4.3 GUP Data Stores and GUP data Users.....                                       | 9         |
+| 4.4 Synchronisation model.....                                                    | 10        |
+| 4.5 Contents of GUP .....                                                         | 11        |
+| 4.6 The role of Data Description in GUP.....                                      | 12        |
+| 5 Stakeholder requirements.....                                                   | 12        |
+| 5.1 Subscriber Requirements.....                                                  | 13        |
+| 5.1.1 User Requirements .....                                                     | 13        |
+| 5.2 Value Added Service Provider Requirements.....                                | 13        |
+| 5.3 Home Network Operator Requirements.....                                       | 13        |
+| 5.4 Roamed-to Network Operator Requirements.....                                  | 14        |
+| 5.5 Regulatory Requirements.....                                                  | 14        |
+| 6 General Requirements.....                                                       | 14        |
+| 6.1 Network Requirements.....                                                     | 14        |
+| 6.2 UE Requirements .....                                                         | 14        |
+| 6.3 General Service Requirements .....                                            | 15        |
+| 6.4 Management Requirements.....                                                  | 15        |
+| 6.5 Synchronization Requirements .....                                            | 15        |
+| 6.6 Data Description Requirements .....                                           | 16        |
+| 7 Security .....                                                                  | 16        |
+| 8 Privacy and Authorisation.....                                                  | 17        |
+| 8.1 General Requirements .....                                                    | 17        |
+| 8.2 Authorisation Rules.....                                                      | 17        |
+| 9 Charging.....                                                                   | 18        |
+| <b>Annex A (informative): Example 3GPP Generic User Profile use cases .....</b>   | <b>19</b> |
+| <b>Annex B (informative): Additional Information.....</b>                         | <b>21</b> |
+| <b>Annex C (informative): Bibliography .....</b>                                  | <b>24</b> |
+| <b>Annex D (informative): Change history.....</b>                                 | <b>25</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, e.g. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document introduces the requirements and features of a 3GPP Generic User Profile (GUP). The GUP will help overcome some of the challenges associated with the introduction of sophisticated user terminals with widely varying capabilities, hybrid combinations of mobile network domains, the advent of downloadable applications, and the desire of users to customise potentially complex services to individual preferences and needs.
+
+The present document for a Generic User Profile will capture requirements that will allow:
+
+1. A way to express user preferences in a consistent manner.
+2. Effective management, control ownership and protection of GUP data.
+3. Extensibility to cater for future needs and the simple addition of new features.
+
+# --- 1. Scope
+
+The present document defines the stage one description to the 3GPP Generic User Profile (GUP). It specifies requirements to the 3GPP Generic User Profile, seen primarily from the user, home environment, serving network and value added service provider's points of view.
+
+The present document includes information applicable to the home environment, device- and network manufacturers and value added service providers which are sufficient to provide complete support of services in 3GPP networks.
+
+While the 3GPP Generic User Profile may contain components that are out of scope of 3GPP (e.g. for services offered by third parties) the requirements in the present document pertain only to those components that lie within the 3GPP system.
+
+# --- 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 TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 32.140: "Subscription Management Requirements".
+- [3] Open Mobile Alliance (OMA): OMA-RD-Parlay\_Service\_Access-V1\_0-20100427-A.
+- [4] W3C Recommendation "Extensible Markup Language (XML) 1.0 (Fifth Edition)"  
+<http://www.w3.org/TR/2008/REC-xml-20081126/>
+- [5] W3C Recommendation "XML Schemas, Part 1: Structures Second Edition"  
+<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/>
+- [6] W3C Recommendation "XML Schemas, Part 2: Datatypes Second Edition"  
+<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/>
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**3GPP Generic User Profile (GUP):** The 3GPP Generic User Profile is the collection of user related data which affects the way in which an individual user experiences services and which may be accessed in a standardised manner as described in this specification. The Generic User Profile is defined using the W3C XML recommendation [4].
+
+**GUP Component (logical):** A GUP component is logically an individual part of the Generic User Profile.
+
+**GUP Component instance (physical):** a GUP component instance is a physical representation of a GUP component. To one GUP component (logical) correspond one or more component instances, i.e. physical copies. Component instances may be located in the Home Network, in the Value Added Service Provider Environment and/or the User Equipment.
+
+**GUP Data Element:** the indivisible unit of Generic User Profile information.
+
+**GUP Data Model:** The data model describing the data structure, the way the data elements are defined and the relationship to each other.
+
+**Data Description Method:** A method describing how to define the data contained in the Generic User Profile. The description is defined using the W3C XML Schemas recommendations [5], [6].
+
+**Master component instance (aka master instance):** Among the component instances (physical) associated with a GUP component (logical), one of them is tagged with the role of "master instance". The master component instance is responsible for the correct value of the corresponding GUP component.
+
+**Public User Identity:** Identity which is used to communicate with other users.
+
+**User:** for definition see 3GPP TR 21.905 [1]. In addition the present document assumes, that the user has a unique identity in the 3GPP system (IMSI or IMS Private ID) and is associated with one 3GPP subscriber. (Note, that a user may have many addresses though! E.g. the user can have several Public User IDs). The user is not necessarily identical to the 3GPP subscriber.
+
+Further 3GPP system related definitions are given in 3GPP TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                            |
+|-------|--------------------------------------------|
+| GERAN | GSM/EDGE Radio Access Network              |
+| GUP   | 3GPP Generic User Profile                  |
+| IMS   | IP Multimedia Core Network Subsystem       |
+| IMSI  | International Mobile Subscriber Identity   |
+| MVNO  | Mobile Virtual Network Operator            |
+| OSA   | Open Service Access                        |
+| PID   | Private User Identity                      |
+| UE    | User Equipment                             |
+| UTRAN | Universal Terrestrial Radio Access Network |
+| VASP  | Value Added Service Provider               |
+| VHE   | Virtual Home Environment                   |
+| WLAN  | Wireless Local Area Network                |
+
+Further 3GPP system related abbreviations are given in 3GPP TR 21.905 [1].
+
+# --- 4 General description
+
+## 4.1 Introduction
+
+The fact of having several domains within the 3GPP mobile system (e.g. Circuit-Switched, Packet-Switched, IP Multimedia Subsystem) and access technologies (e.g. GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to Users, Services and User Equipment will be increased greatly. This causes difficulties for Users, Subscribers, network Operators and Value added service providers to create, access and manage the user-related data located in different entities.
+
+The objective of specifying the 3GPP Generic User Profile is to provide a means to enable harmonised usage of the user-related information originating from different entities. The specification of the GUP shall also allow extensibility to cater for future developments.
+
+The 3GPP Generic User Profile is the collection of User-related data which affects the way in which an individual user experiences services where a community of entities share this data. The 3GPP Generic User Profile can be stored in the home network environment and/or Value Added Service Provider equipment.
+
+The 3GPP Generic User Profile will be accessed by different stakeholders and managed either by one (centralised) or by different stakeholders (de-centralised) such as the user, subscriber, value added service provider and network operator by a standardised access mechanism. The 3GPP Generic User Profile allows intra-network usage (i.e. data exchange between applications within a mobile operator's network) and inter-network usage (between mobile operator's network and value added service providers) as illustrated in Figure 1.
+
+Note: MVNOs and visited networks are treated as value added service providers in terms of GUP data exchanges with mobile operator's network.
+
+The 3GPP Generic User Profile may be also be used by different applications in a standardised way.
+
+The 3GPP Generic User Profile will help to create and manage the user data in each entity and on the other hand to make it easier to find all user related data as a whole in the home network environment.
+
+Technically the 3GPP Generic User Profile provides an architecture, data description and interface with mechanisms to handle the data.
+
+### 4.1.1 Intended Usage of the Generic User Profile
+
+The intended usage of the 3GPP generic user profile is a critical factor driving its detailed specification, e.g., architecture and data model. In general, user profile data can be shared between different stakeholders to facilitate the following:
+
+- **User preference management:** Enable applications to read and utilize a limited set of user preference information
+- **User service customization:** Enable applications to read and utilize personalized service information, i.e., individual settings for a particular service
+- **Terminal capability management:** Enable applications to access terminal-related capabilities
+- **User Information sharing:** Enable applications to read and utilize application level information, e.g. address book information
+- **Profile key access:** Enable applications to use a unique identity as a key to access profile information, .e.g. any public user identity or an alias.
+
+It is intended that the 3GPP GUP, in particular, will address all of the above. As can be inferred, a user's identity can serve as the unique common key into the profile.
+
+### 4.1.2 Benefits of the 3GPP Generic User Profile for individual stakeholders
+
+The following chapter shows in an exemplary way how stakeholders may benefit from GUP. The examples given are neither exhaustive nor are they meant to be part of, or be implemented by GUP. On the contrary, these functions / use-cases need to be seen distinct from GUP, but capabilities offered through GUP (e.g. a common data description, data access- and synchronisation mechanisms ...) may be utilised to build these functions.
+
+- Subscription Management and Customer Care:  
+Subscription Management [2] benefits from a standardised way to access subscription data of a user. Already today customer care is a noticeable part of an operator's expenses, it will grow to be even more expensive as more services and more terminal types become available for 3GPP system. Unlike the Supplementary services in GSM new services in 3GPP are not standardised. Therefore content and format of subscription data as well as the places (repositories) where subscription data are stored may be different for different new services. GUP specifies the description of- and access of data in a standardised way. This will allow:
+  - **Service providers** as well as Value Added Service providers to use standardised GUP mechanisms for Subscription Management and Customer Care by the operator.
+  - Reduce costs for Subscription Management and Customer Care for the **operator** and/or **service provider** and/or value added service provider since management tools may rely on this standardised mechanism.
+- Subscription Check by third party provided services:  
+Third party provided services may run on application servers outside the 3GPP system. However subscription information may be kept by the home operator. To find out, whether a service is allowed to be invoked by a particular user the service needs to check its subscription. Access to this information can be controlled by means of GUP mechanisms.
+  - Benefit for third party **value added service providers** and for
+  - **Operators**, who want to keep subscription within their domain
+
+#### - Services Interaction:
+
+If personalisation of services possibly effect other services it may be advantageous, that such personalisation is visible to these other services. If a service is designed to permit access to these data through GUP mechanisms:
+
+- the **user or operator** may choose to allow certain services to access certain user data of other services of the user.
+
+#### - Provision of Terminal Capability information:
+
+Services (from the home- or visited network operator or provided by third parties) may need to know what capabilities the terminal, that is currently used by the user, supports. Multiple provisioning protocols are a problem for terminal vendors since the UE has to support all of them. The GUP data will be described in the same way and can therefore be used in different protocols without having to change. GUP mechanisms could provide the basis for retrieval of a user's terminal capabilities.
+
+- Benefit for the **value added service provider**, who can rely on a GUP mechanism to obtain this information.
+
+## 4.2 Conceptual view of the GUP
+
+For each user (characterised by an IMSI or IMS PID) one User Profile exists, which may consist of several 'components'. These components may be distributed in the home network and value added service provider's environment. Within the home network, the components may be distributed in various network nodes. Figure 1 below provides a conceptual overview of GUP and is as such for informative purposes only. Only one master of the component exists, but one or more copies of the master component may exist. The home operator shall be able to copy master components, which are located outside the home network to the home network. Within the home network, functionality exists that is able to locate GUP components, thereby making applications unaware of the actual location of the components. The administration and management of the data associated with this functionality is under the control of the home network. Although GUP does not attempt to provide an actual classification of the data it may contain, one may consider categorisations such as general user information, terminal related information, service specific information, etc. as indicated in clause 4.4.
+
+![Conceptual view of GUP diagram showing Home Network and Value Added Service Provider data components.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates the conceptual view of GUP (Generic User Profile) data distribution between a Home Network and a Value Added Service Provider. A legend at the bottom left indicates that yellow boxes represent 'Component Instance' and orange boxes represent 'Master Component Instance'.
+
+**Home Network:** Contains a cloud labeled 'GUP Data' with the following components:
+
+- General User Information:** Component A (Instance), Component B (Master Instance).
+- Other Data (eg terminal related information):** Component D (Instance), Component E (Master Instance).
+- Service Specific Information:** Component Y (Instance), Component X (Master Instance).
+
+**Value Added Service Provider:** Contains a cloud labeled 'GUP Data' with the following components:
+
+- Component A (Instance).
+- Component Y (Master Instance).
+
+A double-headed green arrow connects the 'GUP Data' cloud in the Home Network to the 'GUP Data' cloud in the Value Added Service Provider, indicating bidirectional data exchange.
+
+Conceptual view of GUP diagram showing Home Network and Value Added Service Provider data components.
+
+Figure 1: Conceptual view of GUP
+
+## 4.3 GUP Data Stores and GUP data Users
+
+This clause describes in general terms where the generic user profile data resides and which entities use that information. A general feature of the user profile is that the different entities are data consumers for a certain subset of the generic user profile and are data suppliers for another part. The 3GPP GUP data are distributed by nature and consequently stored in home network and Value Added Service Provider Equipment.
+
+![Diagram illustrating the scope of 3GPP Generic User Profile. The diagram shows 'GUP Data Users' at the top, which include 'Terminal Application', 'Home Network Application', '3rd Party Application', and 'OAM and subscription Management Application'. These are connected to a central 'Generic User Profile' oval. Below the oval are 'GUP Data Stores', which include 'Home Network' and 'Value Added Service Provider'. The entire structure is enclosed in a large oval.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+
+graph TD
+    subgraph GUP_Data_Users
+        TA([Terminal Application])
+        HNA([Home Network Application])
+        3PA([3rd Party Application])
+        OAMA([OAM and subscription Management Application])
+    end
+    subgraph GUP_Data_Stores
+        HN[Home Network]
+        VASP[Value Added Service Provider]
+    end
+    GUP((Generic User Profile))
+    TA --- GUP
+    HNA --- GUP
+    3PA --- GUP
+    OAMA --- GUP
+    GUP --- HN
+    GUP --- VASP
+    HN --- VASP
+  
+```
+
+Diagram illustrating the scope of 3GPP Generic User Profile. The diagram shows 'GUP Data Users' at the top, which include 'Terminal Application', 'Home Network Application', '3rd Party Application', and 'OAM and subscription Management Application'. These are connected to a central 'Generic User Profile' oval. Below the oval are 'GUP Data Stores', which include 'Home Network' and 'Value Added Service Provider'. The entire structure is enclosed in a large oval.
+
+**Figure 2: Illustration of the scope of 3GPP Generic User Profile**
+
+The Generic User Profile provides a generic mechanism to access and manipulate user related data for suppliers and consumers. Using this mechanism the data can be retrieved and managed in a uniform way. However the data contents itself are not described within the Generic User Profile, but only the data model and a schema shall be defined.
+
+The suppliers and consumers of the data can be divided into the following groups of applications:
+
+- Applications in the home network
+- 3<sup>rd</sup> Party Applications
+- OAM and subscription management applications
+
+Applications in the home network may include those related to call or session handling as well as messaging or web services. Typically fairly high requirements are set on the response time.
+
+3<sup>rd</sup> Party Applications are similar to applications in the home network but they are non-trusted which means that strict security, access and privacy procedures shall be carried out.
+
+OAM activities related to user profile are provisioning and administration of user data by the network operator. These activities are characterised by needs for high throughput and allow longer response time. In order to allow simple and centralized administration it should be transparent to the administrator where the different parts of the user data are stored. As a result, this role needs a single system image on user profile, or, on functional terms, a common data access function. As one alternative the user self-service management may be implemented as part of this function.
+
+## 4.4 Synchronisation model
+
+GUP components instances may be distributed in the home network and value added service provider's environment. The distribution model is shown in Figure 1.
+
+A data consumer can request a copy of a GUP component, i.e. the master instance of the component. This copy may be a **working copy** or a **synchronised copy**.
+
+**Master instance:** the data supplier holds the master instance of a GUP component.
+
+Note: During the lifetime of a component, the role of *master instance* may be played by different component instances (e.g. in the case of failure). But at any point in time, there is always one and only one "master instance". This implementation aspect is beyond the scope of GUP.
+
+A *synchronized copy* of a GUP component is a component instance that is kept synchronized with the master instance.
+
+Synchronization here means that changes made to the master instance will be propagated to the synchronized copy (e.g. update, deletion, etc.) The synchronized copy is held within the data consumer's local store..
+
+A *working copy* of a GUP component is a component instance that corresponds to a copy (or snapshot) of the master instance at a given point in time. The working copy is held within the data consumer's local store. Future changes to the master instance (e.g. update, deletion, etc.) are NOT propagated to the working copy. The working copy remains unaffected by changes of the master instance of the GUP component.
+
+If a GUP component is no longer applicable for a given user, the master instance for this GUP component is deleted and all data stores holding synchronized copies are notified about this deletion.
+
+If the access rights of the component are changed, a proper notification is sent to the owner of the synchronized copy.
+
+## 4.5 Contents of GUP
+
+The present document does not mandate any data to be part of the 3GPP Generic User Profile. However the following kind of data are considered to be useful for inclusion in GUP.
+
+### 1. Authorised and subscribed services information:
+
+These kind of data are generally owned by the home operator and allow management and interrogation of subscription information and would typically consist of:
+
+- authorised services that the subscriber may subscribe to
+- services the subscriber actually has subscribed to
+
+### 2. General user information
+
+Data, owned by the user, which are not specific to individual services, but may be useful for any service. These would be data like
+
+- settings (e.g. name, postal address), preferences (e.g. language)
+- Registered Service Profiles of the user, indicating the currently active Service Profile of the user.
+
+### 3. PLMN specific user information
+
+Data, owned by the home operator, which are not specific to individual services, but may be useful for any service. These typically would be data like
+
+- addresses (e.g. MSISDNs, URLs) of the user.
+- WAP parameters (e.g. standard WAP gateway)
+- GPRS parameters (in UE and HSS)
+- Preferred access technologies (The preferred access technology, second preferred access technology etc. e.g. UTRAN, GERAN, WLAN etc.)
+
+### 4. Privacy control data of the user
+
+Data, owned by the user, which are specific to individual services and which control privacy settings of that service. These could e.g. be
+
+- Privacy settings for standardised services like the Presence service or Push service.
+- Privacy settings of non-standardised services.
+
+### 5. Service specific information of the user:
+
+Data, owned by the user or value added service provider, which are specific to individual services (standardised or non-standardised). These could e.g. be
+
+- Service customisation data of the user.
+- Service authentication- and authorisation data (for “single sign on”) like keys, certificates, passwords...
+
+### 6. Terminal related data
+
+These are data, which relate in particular to the user's terminals (ME and UICC). These could e.g. consist of
+
+- Terminal capabilities of the terminal currently in use (e.g. User Interface capabilities, communication capabilities, available services, service capabilities,...).
+- Data for initial configuration and/or reset of the ME.
+- Backup data for recovery of the ME configuration including service specific data.
+
+### 7. Charging and billing related data
+
+This data consists of information necessary for the user related charging and billing. This data could e.g. consist of:
+
+- The billing policy
+
+Note: The following data categories are not considered to be useful for the 3GPP Generic User Profile:
+
+- Run Time Data.  
+Data that are created during the initiation of the session, call or application execution and if they are only available during the lifetime of such session, call or application execution then they are considered as Run Time data.
+- Historic/Statistic Data.  
+User/system behaviour information (e.g. statistics on the usage preferred web pages; duration, number of calls, error rate).
+
+## 4.6 The role of Data Description in GUP
+
+GUP provides a means of supporting access to data for ranges of services and functions (e.g. MMS, Presence). The support of users' services and personalization data may result in manipulating data in a structured manner, and a standardised way of describing and accessing these data structures, utilizing a Data Description Method based on XML Schema.
+
+As there may be technologies which have impact on the GUP but could not be included in the Data Description Method, the Data Description Method should take this coexistence with other technologies into consideration.
+
+# --- 5 Stakeholder requirements
+
+These requirements are given from the perspective of the key stakeholders.
+
+The stakeholders within the context of GUP are:
+
+- the Subscriber
+
+Note: The subscriber may hold subscriptions for one user (e.g. in the case the subscriber is identical with the user) or several users (e.g. in the case of a company - the subscriber – holding subscriptions for it's employees – the users)
+
+- the User
+
+Note: The user may or may not be identical with the Subscriber.
+
+- the Value Added Service Provider
+
+- the Home Network Operator
+- the Roamed-to Network Operator
+- the Regulator
+
+## 5.1 Subscriber Requirements
+
+For a subscriber's services, that support and are supported by GUP:
+
+- The subscriber shall be able to customise her subscribed services and interrogate customisation settings, subject to limitations by the Home operator and/or value added service provider. The user interface for customisation/interrogation is service specific and out of scope of this specification.
+
+### 5.1.1 User Requirements
+
+For a user's services, that support and are supported by GUP:
+
+- The user shall be able to customise the services , that have been subscribed to her by the subscriber and interrogate customisation settings, subject to limitations by the Home operator and/or value added service provider and/or subscriber. The user interface for customisation/interrogation is service specific and out of scope of this specification.
+
+## 5.2 Value Added Service Provider Requirements
+
+VASP services, i.e. services provided by Value Added Service Providers (VASP), shall – via mechanisms of the GUP – be able to:
+
+- Identify the network, the service and the user in any GUP related operation
+- Check a user's subscription information for the service.
+- Provide access to a user's service specific GUP data stored by the application (according to the access rights set by the user).
+- Access other GUP data of the user subject to limitations of access rights
+
+VASP services – standardised and non-standardised – may be part of the 3GPP system (as operator supplied services in the home-network or in a different 3GPP network) or may reside outside the 3GPP system.
+
+It shall be possible for VASP services outside the 3GPP domain to access GUP only via a secure interface to the 3GPP system.
+
+## 5.3 Home Network Operator Requirements
+
+The home network operator shall, via GUP mechanisms, be able to:
+
+- support On-line Service Registration
+
+Subscriber service registration can be set up by on-line subscription not just by customer care. This will also reduce Customer Relationship Management (CRM) workload.
+
+- access Terminal Capabilities
+
+Terminal capabilities (e.g. software and hardware information, application features, etc) shall be accessible to the network. This information may be used to enable any services within network.
+
+- access Value Added Service Provider Capability Information
+
+Value Added Service Provider capability information (e.g. Compression algorithms, Billing capabilities) should be accessible to the network. This information may be used to provide end-to-end service according to UE, Network and the Value Added Service Provider's capabilities.
+
+## 5.4 Roamed-to Network Operator Requirements
+
+None yet identified.
+
+## 5.5 Regulatory Requirements
+
+None identified in addition to the considerations in clause 8. Privacy and Authorisation.
+
+# --- 6 General Requirements
+
+This clause includes different general technical requirements which are not from the perspective of a particular stakeholder.
+
+## 6.1 Network Requirements
+
+These requirements are collected from the point of view of technical Network infrastructure and Elements:
+
+- The GUP data shall be accessed by standardised GUP interfaces and protocols which use the generic GUP data model to carry the user profile.
+- The GUP Interface shall be independent of the structure and semantics of the data.
+- The GUP access mechanism shall support accessing of the whole profile data or a selected part of it.
+- The GUP access mechanism shall include read, create, modify and delete access. GUP shall provide these access mechanisms to read, create, modify, and delete data of GUP components.
+
+Note: This does not include installation and modification of the structure of GUP components at a specified data store, nor does it imply management of GUP data stores of GUP component instances.
+
+- The GUP data shall be transferred in a standardised way.
+- The GUP interface shall include a standardised way for access control.
+- The GUP interface shall enforce the subscriber privacy.
+- The GUP interface shall enforce the user privacy.
+- The GUP shall not cause significant additional load or delays to the network functions and elements.
+
+## 6.2 UE Requirements
+
+This clause includes different UE specific requirements for the 3GPP GUP.
+
+- GUP shall provide mechanisms to represent UE data as GUP components in the network(e.g. terminal capabilities, user preferences, etc).
+- Network based applications should have “read” access to GUP components representing UE data, irrespective of the connection status of the UE.
+- It shall be possible to back up GUP data to the home network or VASP network and to restore it to a UE, however, the mechanism used is outside the scope of GUP.
+
+## 6.3 General Service Requirements
+
+This clause includes different Service aspects and requirements for the 3GPP Generic User Profile. The following general requirements from the point of view of different Service Applications apply:
+
+- It shall be possible for an application to retrieve the whole user profile or selected parts of it in one transaction.
+- There shall be effective means to retrieve individual GUP data elements with acceptable delay for real-time services.
+
+One typical use case for the latter requirement is a call control application that would take advantage of subscriber's preferences or charging related information.
+
+Third party applications may take advantage of the features specified e.g. for Open Service Access (see OMA Parlay Service Access Requirements [3]) to access GUP data.
+
+The description of GUP data shall be easily extensible for new, proprietary uses without any problems caused for the existing or standard applications.
+
+## 6.4 Management Requirements
+
+This clause includes different technical Management aspects for the 3GPP Generic User Profile based on the needs of e.g. Self-Service Management, Subscription Management, Service Management, Network Element Management, Network Management and Customer Relationship Management.
+
+In 3G networks it is expected that user profile data is not only distributed over different network elements but belongs to different administrative domains. These administrative domains may be closed against external access. However, in order to enable a seamless service experience for the user a controlled transparency to exchange user profile data is needed.
+
+There exist two main cases to be addressed:
+
+### **Domain borders in the home network:**
+
+Already in the network of the subscriber's home network operator there may exist different domains. Potential examples are application of 3<sup>rd</sup> party value added service providers which are loosely coupled with the network provider, e.g. their applications run under the brand of the network operator but their data are stored and maintained apart from the network operator's entities.
+
+### **Domain borders between different network operators:**
+
+This is the well-known roaming scenario where a user is served by another network than his home one. Roaming is already addressed by mobile networks but in the case of 3G networks there is an important additional requirement: The assumed frequent changes of applications induces a need to handle frequent changes of data sources/consumers.
+
+The user profile data access architecture shall enable the transparent and flexible usage of the user profile data. It shall provide transparent access to distributed data fulfilling the needs of the different roles described above. Furthermore, the architecture shall address the fact that parts of the user profile data are potentially located in different administrative domains. Possible means are negotiation capabilities and proxy functionality at the domain borders.
+
+### **Management of GUP data components:**
+
+Making a particular data store available for GUP is not in the scope of GUP and needs to be administered by other means.
+
+The administration (installation and modification) of the structure of GUP components at a specified data store is not in the scope of GUP and needs to be administered by other means.
+
+## 6.5 Synchronization Requirements
+
+To avoid unnecessary duplicated data storage an application should be able to access parts of the user's GUP data.
+
+The following requirements are applicable to the synchronization model:
+
+1. GUP shall offer a mechanism to define *synchronized copies*, i.e. instances that are kept synchronized with the master instance.
+2. GUP shall offer a mechanism to define *working copies*, i.e. instances that do not require any synchronization.
+3. GUP shall make sure that synchronized copies do not conflict with the access right of the corresponding GUP components. For example, if the access rights to some parts of the GUP component change such that the data consumer no longer has access rights, then those parts of the GUP component would no longer be synchronised.
+
+## 6.6 Data Description Requirements
+
+The Generic User Profile is a generic, extensible profile data collection with mechanisms to e.g. create, retrieve, delete and modify the data. GUP shall define a standardised way of data description. This allows for a standardised access and handling of these data, not excluding the possibility of proprietary extensions.
+
+Only part of the data contents are standardised within 3GPP specifications, whereas application specific data is outside the scope of the 3GPP standardisation. This specification does not mandate any 3GPP service specific data to be part of the 3GPP Generic User Profile. However the common data types shall be specified to facilitate the separate work on the service specific definitions (e.g. for the user profile in HSS).
+
+The common data shall contain data types for at least:
+
+- Private IDs (IMSI and IMS Private User Identity)
+- Public IDs (MSISDN and SIP URL)
+- Other address types, that are supported by 3GPP (e.g. e-mail)
+- Service identifications
+- Generic privacy control data
+- Date and time
+- Service Subscription state (e.g. "active", "not subscribed", "dormant" ...)
+
+# --- 7 Security
+
+Secure mechanisms shall be available for the transfer of User Profile data to, from or between authorised entities. Access to User Profile data shall only be permitted in an authorised and secure manner. The secure mechanisms to be applied shall be appropriate to the level of confidentiality of the data, the endpoints of the transfer and the routes that are available for the transfer of the data. The owner of the data, normally the body storing the master copy of the data, shall be responsible for applying the appropriate level of security to the transfer of the data.
+
+The secure mechanisms available shall include the following:
+
+1. Authentication of consumer  
+Before any user data transfer takes place, it shall be possible for the supplier of the data to verify the identity of the consumer.
+2. Authentication of supplier  
+It shall be possible for the consumer of data to identify the supplier.
+3. It is permissible for either the supplier or consumer of data to employ the services of a third party, known to, and trusted by, both in order to provide authentication of identity.
+4. The validity of an authentication of identity shall, if required, be subject to a maximum time limit.
+5. It shall be possible for the supplier of data to render the data to be unreadable by any party not authorised to receive it.
+6. It shall be possible for the consumer of data to detect whether the data have been tampered with during transmission. .
+7. The security mechanisms shall provide verification that the data has been sent by the supplier and received by the consumer (non-repudiation).
+8. It shall be possible for the supplier and/or the consumer to create an audit log of all GUP data transfer transactions of a specified type, provided that this requirement is made known before any transfer takes place
+9. User profile data in general is proprietary data. This data may not be shared with unauthorized entities. *Access control* to the data is required. This access control must also apply to data which is located at legacy systems, currently without own access control functionality.
+
+10. Correct setting of data values in the user profile may be critical for the integrity of certain network services. Therefore, *consistency checks* are needed to minimise the risk.
+11. Transaction security for the change of data should be available in order to ensure the consistent change of data at different locations.
+
+# --- 8 Privacy and Authorisation
+
+This clause describes the requirements for the authorization of access to the user profile data. The Privacy can be provided by the means of authorization mechanism.
+
+## 8.1 General Requirements
+
+It shall be possible for the user to define privacy requirements for components of the 3GPP Generic User Profile to determine access rights.
+
+It is agreed in the subscription agreement between the home network operator and the subscriber how the access and privacy control is carried out e.g. who is able to control different parts of the user profile including the privacy settings. The GUP shall provide means to implement access and privacy control according to the different agreements.
+
+The GUP authorization shall be independent of who has set the privacy rules for each part of the GUP data. A generic mechanism shall be provided to ensure that only such data for which there is a valid authority can be created, read, modified or deleted.
+
+The privacy requirements shall fulfill local privacy regulations. Lawful interception and other regulator requirements may imply that GUP data is delivered to authorities despite the privacy settings.
+
+## 8.2 Authorisation Rules
+
+Authorisation of the requested action (create, read, modify or delete) on the user profile data depends on the following information:
+
+- identification of the requesting application
+- identification of the requesting subscriber (if delivered in the request)
+- identification of the targeted user
+- identification of the targeted user profile data
+
+The disclosure of the user profile data must be considered based on the identification of the application requesting access to the data. The possible identities of the applications will not be standardized but are implementation specific.
+
+Regarding trusted applications involving other subscribers or comparable entities it shall be possible also to check the access rights of the subscriber being served by the application. This requires that the identification of the served subscriber is passed via the GUP mechanism in addition to the application identification. The access is first defined per applications and secondly per served subscriber. The access may be granted also to the public, some group or a list of subscribers.
+
+The identity of targeted user will be based on the 3GPP network identities (Private and Public User Identities). Public User Identities would be normally applied, but especially within the operator domain the Private Identity could be used as well.
+
+The targeted user profile data will be controlled as per the whole user profile and/or per different GUP components and/or per different GUP data elements.
+
+Depending on the service the privacy of the requested GUP data can additionally be managed in the service level e.g. in Presence or IMS group management. The privacy rules for these services are specified in the corresponding 3GPP specifications.
+
+The GUP shall also support the possibility that the privacy of specific GUP data is queried from other privacy control system. Existing privacy solutions should be considered and adopted if applicable (e.g. LCS).
+
+# --- 9 Charging
+
+It shall be possible to support charging for the management, access and synchronization of the 3GPP Generic User Profile. (e.g. for capability negotiation or remote diagnostic information gathering).
+
+Note: There might be legislative restrictions on charging. This is FFS.
+
+# --- Annex A (informative): Example 3GPP Generic User Profile use cases
+
+## 1. Setting up a Subscription for a new customer
+
+- Precondition
+  - A person has just purchased a new device, and requires new subscription data to be initiated in the shop.
+- Actions
+  - Subscription data is input by the shop personnel by means of a Subscription Management application.
+  - Subscription Management application stores the data in Generic User Profile in the Home Network.
+- Post-condition
+  - The user can leave the shop. Her subscription is ready to use.
+
+## 2. Application Access to User Profile Data using OSA (Pull Scenario)
+
+- Precondition
+  - The application is registered with the OSA framework
+  - The application is authorised to access the user profile management Service Control Function and use methods which permit read/write data in user profiles
+- Actions
+  - The application uses OSA to read/write data in the user profile of the user
+  - The network provides the requested data or modifies the data as requested
+- Post-condition
+  - Consistency of the user profile data
+
+## 3. Notification of user subscription to an HE-VASP application using OSA (Push Scenario)
+
+- Precondition
+  - The OSA application from the HE-VASP is registered with the OSA framework
+  - The OSA application is authorized to receive subscription/unsubscription notifications
+  - The OSA application has subscribed to the notification permitting to it to know when new users have subscribed to the service implemented by the OSA application
+- Actions
+  - A new user subscribes to the service implemented by the OSA application
+  - The Home Environment notifies the OSA application about a new subscription and provides it with relevant information (e.g. identity of the user)
+  - Possibly the OSA application provides the home environment with a link (e.g. URL) to a location where the user can customize the service
+- Post-conditions
+
+- The OSA application can now have access to home environment -owned user profile information for this user, provided that it is granted the related access rights
+- The user can customize service data for the service implemented by the OSA application
+
+## **4. Customization of service specific data for a VHE service provided by a HE-VASP**
+
+- Preconditions
+  - The user has a VHE subscription
+  - The user is subscribed to the service provided by the HE-VASP
+  - There is a link from the user Personal Service Environment (PSE) to the HE-VASP for service customization
+  - The user has access to her PSE and has successfully been logged to it
+- Actions
+  - The user accesses her PSE and decides to customize the service provided by the HE-VASP
+  - She transparently access a service customization interface provided by the HE-VASP (possibly via a hyperlink)
+  - She defines/modifies service customization data, which are managed and stored by the HE-VASP
+- Post-condition
+  - Next time she uses the service, new customization data will be used
+
+# --- Annex B (informative): Additional Information
+
+Note: The following use cases are currently not in the scope of 3GPP Generic User Profile Stage 1 but they are still considered to be useful information (e.g. for future work) and therefore included in this Annex.
+
+## 1. Setting up a Subscription for a new customer
+
+- Precondition
+  - A person has just purchased a new device, and requires a new subscription to be initiated in the shop.
+- Actions
+  - The user preferences for services are established.
+  - Information about the terminal capabilities are received from the UE.
+  - User Profile content is created for the Subscriber, and downloaded over the air, via local link or similar
+- Post-condition
+  - The user can leave the shop. Her phone/device is ready to use. Basic settings needed to start and run initial applications ready.
+
+## 2. Initial Service Configuration (Bootstrap)
+
+- Precondition
+  - No settings made, user with a subscription
+- Actions
+  - Settings, partly based on user profile downloaded over the air, via local link or similar
+  - The download initiated by the value added service provider, network operator, 3<sup>rd</sup> party or user
+- User Data
+  - Setting received could include basic connectivity configuration parameters and the user's security policy
+- Post-condition
+  - The user's phone/device ready to use. Basic settings needed to start and run initial applications ready
+
+## 3. Backup/Restore of User Profile Components stored in the UE
+
+- Precondition
+- Backup
+  - The phone is configured, all the user preferences are set.
+  - The settings include user profile parameters such as generic parameters, service personalisation parameters, user's security policy and other user preferences
+- Restore
+  - The phone's initial configuration enables download of configuration and user data at least via local link.
+  - A backup of phone configuration and user preferences is available in the network.
+
+- Actions
+  - The user wishes to backup or restore the current version, or parts of the current user profile to the network, or to another UE.
+  - The backup/restore is performed via local link or remotely towards the network
+  - The backup/restore can be initiated by the user, the value added service provider, 3rd parties or the network operator
+- User Profile Storage
+  - Secure area of the (U)SIM or ME or retained in the network by the value added service provider. User private data is only stored in the network with the user permission.
+
+## 4. Content Negotiation
+
+- Precondition
+  - The user has set her preferences in the UE
+  - Terminal type capability information is stored in "internet"
+- Actions
+  - The user initiates request for content. The request contains:
+    - User preference fetched from the UP
+    - Reference to the capability information is stored in "internet"
+    - Deviating capability information
+  - Returned content selected or tailored according to User preferences and capability information
+
+## 5. Terminal Management – Manual Helpdesk
+
+- Precondition
+  - A user is complaining because her pocket web browser does not work. He calls the helpdesk
+- Actions
+  - The UE capabilities are established by the helpdesk person
+  - A helpdesk person at an operator, value added service provider or enterprise verifies that the correct operating parameters are set on the device of a complaining user
+- Post-condition
+  - The user's is happy. The pocket web browser is running correctly
+
+## 6. Terminal Management – Automated Self Fixing
+
+- Precondition
+  - A software agent on the user's device identifies an error.
+- Actions
+  - It contacts the helpdesk software entity to fix the problem.
+  - The UE capabilities are established by the automated self-fixing solution.
+
+- The self-fixing solution correctly diagnoses the error and provisions a bug fix.
+- Post-condition
+  - The user's device software executes correctly (and is happy)
+
+## 7. Automatic Access Selection based on preferred list
+
+- Precondition
+  - The UE shall be able to support automatic access technologies selection (i.e. without user intervention).
+  - The user has set her preferences in the UE and enabled automatic access technologies selection.
+  - A list of preferred access technologies capabilities information is stored in "internet"
+  - The access technologies are authorized.
+- Actions
+  - The user equipment initiates request for selected access technology. The request contains:
+    - User preferences fetched from the UP
+    - Reference to the access technology capabilities information is stored in "internet"
+  - The preferred access technology is selected.
+- Post-condition
+  - The preferred access technology is selected based on the order of precedence defined in a list of access technologies on the UE. The switch to a less preferred access technology, in case the most preferred is not available, takes place without user intervention.
+
+## 8. Multiple Access Technology Negotiation
+
+- Precondition
+  - The user has set her preferences in the UE and enabled access selection.
+  - Terminal type capability information is stored in "internet"
+  - The access technologies are authorized
+  - The user has access and connection with one ongoing application
+- Actions
+  - The (Multi-mode) terminal initiates request for another access technologies.
+  - The terminal chooses the most appropriate access form based on the UP and/or the sessions in progress demand of service quality.
+  - Returned access form selected according to User preferences and capability information.
+- Post-condition
+  - Change of access technology without interrupting any session(s) to/from that host (context transfer).
+  - The old access connection end.
+  - The user and the terminal are connected via the new access (i.e. WLAN) with the same user identity, without having to re-authenticate.
+
+# --- Annex C (informative): Bibliography
+
+The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information.
+
+3GPP TS 21.133: "3G Security; Security Threats and Requirements".
+
+3GPP TS 22.097: "Multiple Subscriber Profile (MSP) Phase 1; Service description - Stage 1".
+
+3GPP TR 22.121: "The Virtual Home Environment".
+
+# Annex D (informative): Change history
+
+| Change history |           |           |        |      |         |        |     |                                                                                  |        |        |       |
+|----------------|-----------|-----------|--------|------|---------|--------|-----|----------------------------------------------------------------------------------|--------|--------|-------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Re<br>v | Rel    | Cat | Subject/Comment                                                                  | Old    | New    | WI    |
+| SP-19          | SP-030036 |           | 22.240 |      |         | Rel-6  |     | Approved at SA #19                                                               | 2.0.0  | 6.0.0  |       |
+| SP-21          | SP-030469 | S1-030965 | 22.240 | 001  |         | Rel-6  | F   | Clarifications for section 7 of 22.240                                           | 6.0.0  | 6.1.0  | GUP   |
+| SP-22          | SP-030707 | S1-031256 | 22.240 | 002  | -       | Rel-6  | F   | Clarifications on general service requirements and data description requirements | 6.1.0  | 6.2.0  | GUP   |
+| SP-22          | SP-030707 | S1-031257 | 22.240 | 003  | -       | Rel-6  | F   | Clarifications GUP data access and administration                                | 6.1.0  | 6.2.0  | GUP   |
+| SP-22          | SP-030707 | S1-031258 | 22.240 | 004  | -       | Rel-6  | F   | Clarifications on GUP synchronisation                                            | 6.1.0  | 6.2.0  | GUP   |
+| SP-23          | SP-040095 | S1-040202 | 22.240 | 005  | -       | Rel-6  | F   | GUP UE Requirements                                                              | 6.2.0  | 6.3.0  | GUP   |
+| SP-25          | SP-040507 | S1-040683 | 22.240 | 006  | -       | Rel-6  | F   | GUP, UE requirements corrections                                                 | 6.3.0  | 6.4.0  | GUP   |
+| SP-26          | SP-040730 | S1-040989 | 22.240 | 007  | -       | Rel-6  | F   | Removal of erroneous use cases                                                   | 6.4.0  | 6.5.0  | GUP   |
+| SP-42          |           |           |        |      |         | Rel-7  |     | Upgraded to Rel-7 without technical change.                                      | 6.5.0  | 7.0.0  |       |
+| SP-42          |           |           |        |      |         | Rel-7  |     | Upgraded to Rel-8 without technical change.                                      | 7.0.0  | 8.0.0  |       |
+| SP-46          | -         | -         | -      | -    | -       | -      | -   | Updated to Rel-9 by MCC                                                          | 8.0.0  | 9.0.0  |       |
+| SP-49          | SP-100575 | S1-102054 | 22.240 | 0008 | -       | Rel-9  | D   | Removal of references to 3GPP OSA                                                | 9.0.0  | 9.1.0  | TEI9  |
+| 2011-03        | -         | -         | -      | -    | -       | -      | -   | Update to Rel-10 version (MCC)                                                   | 9.1.0  | 10.0.0 |       |
+| 2012-09        | -         | -         | -      | -    | -       | -      | -   | Updated to Rel-11 by MCC                                                         | 10.0.0 | 11.0.0 |       |
+| SP-62          | SP-130592 | S1-135289 | 22.240 | 0009 | 1       | Rel-11 | F   | Correction of external references                                                | 11.0.0 | 11.1.0 | TEI11 |

marked/Rel-11/22_series/22246/raw.md

@@ -0,0 +1,511 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                               |           |
+|---------------------------------------------------------------|-----------|
+| Foreword .....                                                | 4         |
+| Introduction .....                                            | 4         |
+| 1 Scope.....                                                  | 5         |
+| 2 References.....                                             | 5         |
+| 3 Definitions and abbreviations .....                         | 5         |
+| 3.1 Definitions.....                                          | 5         |
+| 3.2 Abbreviations .....                                       | 6         |
+| 4 Classification of MBMS User Services .....                  | 6         |
+| 5 High level requirements .....                               | 7         |
+| 5.0 General .....                                             | 7         |
+| 5.1 Common requirements to broadcast and multicast .....      | 9         |
+| 5.2 Interoperability .....                                    | 10        |
+| 5.2a Pre-Delivery verification.....                           | 10        |
+| 5.3 Delivery verification .....                               | 11        |
+| 6 MBMS User Service requirements .....                        | 11        |
+| 6.1 Charging.....                                             | 11        |
+| 6.2 Security.....                                             | 11        |
+| 6.3 Privacy.....                                              | 11        |
+| 6.4 Quality of service .....                                  | 11        |
+| 6.5 Subscription.....                                         | 12        |
+| 6.6 Availability.....                                         | 12        |
+| <b>Annex A (informative): Use Cases.....</b>                  | <b>13</b> |
+| <b>Annex B (informative): Example service scenarios .....</b> | <b>15</b> |
+| B.1 Text notification service.....                            | 15        |
+| B.2 Local Area Information distribution (Case A).....         | 15        |
+| B.3 Local Area Information distribution (Case B) .....        | 15        |
+| B.4 Multicast distribution .....                              | 15        |
+| B.5 Audio Distribution.....                                   | 16        |
+| B.6 General Content Distribution .....                        | 16        |
+| B.7 Software Download.....                                    | 16        |
+| Annex C (informative): Change history.....                    | 17        |
+
+# --- 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
+
+TS 22.146 [2] specifies the multimedia broadcast and multicast service (MBMS) application independent transport service and includes some guidance on application services and bit rates. The present specification defines MBMS User Services that use the capabilities of MBMS. Service related information is defined in this specification to specify requirements in terms of data rates, quality of service requirements, typical volumes of data etc.
+
+MBMS User Services may be delivered to a user at different bit rates and quality of service depending on radio networks and conditions. This technical specification describes service scenarios for MBMS User Services.
+
+In addition scenarios related to security and charging are described providing information for detailed MBMS User Services security and charging mechanisms to be specified. The service scenarios described in this specification are not exhaustive, it is possible that MBMS may be used for services that are not included in this specification. The present specification describes the minimal requirements for interoperability for MBMS based services. This specification establishes a basis which can also be used for future services.
+
+# --- 1 Scope
+
+The present document describes MBMS User Services that use the capabilities of MBMS. Application scenarios including charging, QoS aspects and related service requirements derived from them are described. These scenarios and service requirements can be used as guidance for the design of codecs and bearers.
+
+# --- 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 TS 22.146: "Multimedia Broadcast/Multicast Service".
+- [3] 3GPP TS 26.140: "Multimedia Messaging Service (MMS): Media formats and Codecs".
+- [4] 3GPP TS 26.134: "Transparent end-to-end Packet-switched Streaming Service (PSS) Protocols and codecs".
+- [5] 3GPP TS 22.240 "Service requirement for the 3GPP Generic User Profile (GUP)".
+- [6] 3GPP TS 22.242: "Digital Rights Management".
+- [7] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) Access Reference Configuration".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the definitions in 3GPP TR 21.905 [1] as well as the following definitions apply.
+
+**Broadcast service area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Local Broadcast Area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Broadcast mode:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Broadcast service:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Broadcast session:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**MBMS transport service:** A MBMS transport service is either a broadcast service or a multicast service as defined in TS 22.146 [2].
+
+**MBMS User Services:** Services that are intended to be delivered to multiple users simultaneously. MBMS User Services use the capabilities of the MBMS application independent transport.
+
+**Media types:** a media type refers to one form of presenting information to a user, e.g. voice or fax.
+
+**Mobile Station (MS):** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast transmission activation:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast service area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Local multicast area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast mode:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast joining:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast session:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multimedia Broadcast/Multicast Service (MBMS):** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast group:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast service:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast subscription:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast Subscription Group:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**User Equipment:** defined in TS 21.905. An occurrence of a User Equipment is an MS for GSM as defined in TS 24.002 [7].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                        |
+|------|----------------------------------------|
+| MBMS | Multimedia Broadcast/Multicast Service |
+| MS   | Mobile Station                         |
+| PSS  | Packet-switched Streaming Service      |
+| UE   | User Equipment                         |
+
+# --- 4 Classification of MBMS User Services
+
+There exist many services and applications that can be provided over the application independent MBMS transport [2]. It is not necessary to standardise specific end user services because the deployment of particular applications and services over the capabilities provided by the 3GPP system is operator specific and outside the scope of standardisation. However, it is possible to classify MBMS User Services according to the method used to distribute these services.
+
+There are four types of MBMS User Service considered within this specification.
+
+### - Streaming services
+
+A continuous data flow providing a stream of continuous media (i.e. audio and video) is a basic MBMS User Service. Like digital video broadcasting, supplementary information of text and/or still images (static media) is also important. For example, if text includes URLs of some content on the Internet, a user can easily access the content without entering the URL for herself. Still images may also be used for banner images that advertise some product or service. These static media need to be synchronized and displayed with audio/video streams.
+
+Note: Streaming in the context of MBMS User Services may not be the same as that described e.g. within PSS [4].
+
+### - File download services
+
+This service delivers binary data (file data) over an MBMS bearer. An MBMS client (i.e. UE) activates an appropriate application, and utilises the delivered data. The most important functionality for this service is reliability. In other words, it is necessary that the user receive all the data sent in order to experience the service.
+
+### - Carousel services
+
+Carousel is a service that combines aspects of both the Streaming and File download services described above. Similar to the streaming service this service includes time synchronisation. However, the target media of this
+
+service is only static media (e.g. text and/or still images). Time synchronization with other media is also required. For example, text objects are delivered and updated from time to time. Still images may also be collated to display low frame-rate video. In common with the download service this service also includes reliability (typically 100% reliability is not always necessary). The benefit of this service is that it is possible over a low bit-rate bearer.
+
+An example of an application utilising the Carousel service is a 'ticker-tape' type service in which the data is provided to the user repetitively and updated at certain times to reflect changing circumstances.
+
+- Television (TV) service
+
+The Television service is an MBMS service consisting of synchronised streaming audio and visual components.
+
+# --- 5 High level requirements
+
+## 5.0 General
+
+MBMS user services are services an operator may provide to subscribers. MBMS user services use the capabilities of MBMS. The operator may provide such services on his own or in collaboration with third party service providers. In addition, an MBMS user service may be provided to the operator's own subscribers and/or to inbound roaming subscribers from other operators.
+
+### MBMS User Services
+
+MBMS user services are based on broadcast- or multicast services, which are defined in TS 22.146 [2].
+
+MBMS user services shall be bearer agnostic to enable access via generic IP access systems.
+
+An MBMS user service may use one or more broadcast- or multicast services at a time within the MBMS service area bound to this user service.
+
+- Note 1: A single broadcast- or multicast service can only have one broadcast- or multicast session at any time within the MBMS service area bound to this user service. A broadcast- or multicast service may consist of multiple successive broadcast- or multicast sessions. (see TS 22.146 [2])
+- Note 2: As part of the same multicast service, it should be possible for the operator to provide the UEs with multiple successive sessions with different quality-of-service for each session. (see TS 22.146 [2])
+
+![Diagram illustrating the mapping of MBMS transport services to MBMS user services over time. The diagram shows four transport services (1-4) and three user services (X, Y, Z). Transport service 1 (multicast) carries a text session for user service X. Transport service 2 (multicast) carries an audio session for user service X. Transport service 3 (multicast) carries text and video sessions for user service Y. Transport service 4 (broadcast) carries an audio session for user service Z. A horizontal arrow at the bottom indicates the progression of time.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates the mapping of MBMS transport services to MBMS user services over time. The horizontal axis represents time, indicated by a large arrow at the bottom labeled "time".
+
+- MBMS transport service 1 (multicast)** carries a **text session** for **MBMS user service X**.
+- MBMS transport service 2 (multicast)** carries an **audio session** for **MBMS user service X**.
+- MBMS transport service 3 (multicast)** carries a **text session** and a **video session** for **MBMS user service Y**.
+- MBMS transport service 4 (broadcast)** carries an **audio session** for **MBMS user service Z**.
+
+Brackets on the right side of the diagram group the transport services with their corresponding user services: X, Y, and Z.
+
+Diagram illustrating the mapping of MBMS transport services to MBMS user services over time. The diagram shows four transport services (1-4) and three user services (X, Y, Z). Transport service 1 (multicast) carries a text session for user service X. Transport service 2 (multicast) carries an audio session for user service X. Transport service 3 (multicast) carries text and video sessions for user service Y. Transport service 4 (broadcast) carries an audio session for user service Z. A horizontal arrow at the bottom indicates the progression of time.
+
+It shall be possible for an MBMS user service to make use of different application independent MBMS transport services at different times or in parallel. The MBMS transport services used may vary for instance in QoS parameters or target broadcast or multicast area.
+
+It shall be possible for one application independent MBMS transport service to be used by more than one MBMS user service at a time.
+
+If an MBMS user service makes use of several application independent MBMS transport services then these may only consist of either broadcast or multicast services, but not of a combination of both.
+
+Note: The combination of broadcast- or multicast services in future releases is FFS
+
+When necessary, within a single MBMS user service, it shall be possible to synchronize the media sessions.
+
+NOTE: For different application independent MBMS transport services to support a single MBMS user service it may be necessary to logically link the transport services to each other, as illustrated in the figure for the audio- and video session of MBMS user service X.
+
+The UTRAN, GERAN and E-UTRAN accesses shall provide protection against normal transmission errors (eg interference not related to cell changes and handovers).
+
+Non 3GPP access system used to transport MBMS user services should provide protection against normal transmission errors (e.g. interference not related to cell changes and handovers).
+
+The BM-SC is responsible for providing protection e.g. FEC, long interleaving and/or point to point repairing the transmission, against errors (eg those caused by cell changes and longer breaks in transmission).
+
+### **Service examples**
+
+MBMS user services may be classified according to the table within Annex A of this specification into several service examples, which are characterized by
+
+- Their predominant broadcast- or multicast service, that constitutes this MBMS user service together with its reliability (QoS) and data transfer rate requirements
+- Media types that are transmitted via this broadcast- or multicast service
+- Type of the service, which implies handling of the distributed media by the UE (e.g. download for subsequent presentation, streaming for instant presentation or carousel downloading)
+- Charging characteristics
+- A potential requirement for point-to-point delivery verification for delivered content.
+
+To express the requirements for standardised service types are one objective of the present specification.
+
+### **Service classes**
+
+MBMS user services may be provided for many purposes to the user and may convey information of various kinds. E.g. some services may be used for traffic information, others for entertainment or for news services. Service classes denote a classification of MBMS user services according to their usage. However, service class values are not in the scope of 3GPP standardisation but may be subject of inter-operator service arrangements.
+
+## **5.1 Common requirements to broadcast and multicast**
+
+The following list describes requirements on an application level:
+
+### **Service classes**
+
+In case of roaming a user shall be able to enjoy services as follows:
+
+- A user shall be able to activate services that are provided locally in the visited network, as allowed by the user's home environment (e.g. local tourist information).
+- A user subscribed to a service class in the HPLMN shall be able to enjoy equivalent services in the same service class as provided by a visited PLMN without explicit subscription in the VPLMN (e.g. weather forecast).
+
+A user subscribed to a service class in the HPLMN shall be able to have access to home contents provided via a visited PLMN without explicit subscription in the VPLMN (e.g. enjoy subscribed service while roaming)
+
+### **Service Interworking**
+
+The user shall be able to manipulate content delivered over MBMS and forward it using other services (e.g. MMS, Speech Call- and IMS signalling, Hyperlinks, ...). Care should be taken in order to fulfil requirements concerning DRM and respective barring and charging capabilities.
+
+When interacting with user profiles, MBMS User Services shall use the mechanisms described in [5] TS 22.240 (Generic User Profile).
+
+#### **Content storage in the UE**
+
+It shall be possible for the UE to store content delivered to it over MBMS and provide it to the user at a later time. Care should be taken in order to fulfil requirements concerning DRM and respective charging capabilities.
+
+### **Data formats and types**
+
+Media types shall be supported independent of specific data types and formats behind..
+
+As a minimum MBMS User Services shall support the following media types:
+
+- Text  
+It shall be possible to embed hyperlinks and to decorate text within content provided by MBMS User Services.
+- Still Images
+
+- Video
+- Speech
+- Mono/Stereo Audio
+
+Data format and data types as being used by other multimedia services shall be supported for interoperability reasons.
+
+Note : It is not intended to constrain MBMS to existing codec technologies. The intention is to maintain consistency with other multimedia services whilst also allowing for adoption of new codec technologies as appropriate.
+
+### **Digital Rights Management**
+
+The MBMS User Service shall be able to control content distribution as defined in 3GPP TS 22.242 [6]. MBMS content providers shall be able to invoke DRM to prevent unauthorized copying and forwarding of content.
+
+### **Notification of required capabilities**
+
+The capabilities (e.g. memory size) required to receive a particular transmission shall be notified in advance by the network or service centre.
+
+### **MBMS Television Service**
+
+It shall be possible for a user to select between different content within the MBMS Television Service.
+
+The MBMS service shall add no more than 1 second when switching between different TV streams to any delay introduced with regards to the coding of the TV stream.
+
+It shall be possible for an operator to configure the MBMS Television service so that the typical switching time, from the end user's perspective, does not exceed 2 seconds.
+
+Handover within the same radio access technology shall be transparent to the user.
+
+Handover between different radio access technologies should be performed without any user perceived interruption.
+
+Note: The quality of the MBMS Television service may change depending on the capabilities of the target network.
+
+## **5.2 Interoperability**
+
+MBMS User Services shall ensure service interoperability with respect to media formats and codecs, at the same time being able to re-use existing multimedia capabilities in the UE as far as possible.
+
+Therefore MBMS User Services shall support a minimum set of media formats and codecs. This minimum set should be aligned with the set of media formats and codecs required for MMS [3] and PSS [4].
+
+## **5.2a Pre-Delivery verification**
+
+It is required that the operator can verify the number of active MBMS users when service commences.
+
+The UE shall provide a secure means to inform the network of the start of services by pre-delivery verification transmitted over a point-to-point connection to the home/visited network. This pre-delivery verification may be relayed to the service provider. The pre-delivery verification shall also support the carriage of bearer specific non-real time information, i.e. previously stored in the UE, to the BM-SC. Such bearer specific information may, for example, include historic C/I measurements for the serving cell.
+
+It should be noted that pre-delivery verification by point-to-point mechanisms partially reduces the resource-efficiency of the underlying broadcast services. Sacrificing resource-efficiency due to requirements of UE reporting may be necessary but should be kept as minimal as possible to minimize congestion.
+
+## **5.3 Delivery verification**
+
+For some MBMS user services it is required that the operator can verify that the content conveyed by the service has been received by the UE.
+
+The UE shall provide a secure means to provide such delivery verification transmitted over a point-to-point connection to the home/visited network. This delivery verification may be relayed to the service provider.
+
+The delivery verification shall also support the carriage of bearer specific non-real time information, i.e. previously stored in the UE, to the BM-SC. Such bearer specific information may, for example, include historic C/I measurements for the serving cell.
+
+It should be noted that delivery verification by point-to-point mechanisms partially reduces the resource-efficiency of the underlying broadcast services. Sacrificing resource-efficiency due to requirements of UE reporting may be necessary but should be kept as minimal as possible to minimize congestion.
+
+# --- 6 MBMS User Service requirements
+
+## 6.1 Charging
+
+The MBMS User Service shall support standardized mechanisms to transfer charging related information.
+
+It shall be possible to charge for MBMS content the user receives while roaming in a VPLMN.
+
+As indicated in Annex A some services will require an indication that MBMS content has been received. Therefore it shall be possible for the UE to provide such an indication.
+
+The MBMS User Service shall support the following charging mechanisms :
+
+- Charging on a subscription basis
+- Charging for keys that allow the user access to the data
+
+## 6.2 Security
+
+The following security aspects shall be taken into account:
+
+Any user modifiable MBMS service data (e.g. storage of deliveries in the UE, data type and format specific behaviours etc) shall only be modified by the authenticated user (see also 4.1.1 above).
+
+## 6.3 Privacy
+
+Third parties and VASP should not be aware about user IDs for MBMS subscriptions unless explicitly allowed by the operator.
+
+## 6.4 Quality of service
+
+It should be possible for the operator to collect statistical data such as lost frames, assigned resources, bit-rates achieved etc.
+
+It shall be possible for the operator to adapt the distribution of a MBMS user service consisting of different MBMS transport services to provide multiple QoS levels according to the QoS resources provided by the access network(s), while maintaining the resource efficiency of the underlying MBMS transport services.
+
+Note: It is necessary that an MBMS user service, consisting of different MBMS transport services providing multiple QoS levels, can be received by all MBMS-capable terminals.
+
+It shall be possible to base the adaptation of the distribution of a MBMS user service to the QoS resources provided by the access network(s) on:
+
+- the QoS resources within the same access network (e.g. UTRAN).
+- the QoS resources provided by different access networks (e.g. UTRAN and GERAN).
+
+It shall be possible to adapt the distribution of an ongoing MBMS user service to persistently changed QoS resource conditions in the access network(s).
+
+Adaptation of the distribution of a MBMS user service to the QoS resources in different access networks or parts of the same access network shall not affect the QoS of the MBMS user service in other access networks or other parts of the same access network.
+
+## 6.5 Subscription
+
+During the lifetime of subscription to a Multicast Service it shall be possible for the user to declare the service preferences. It shall be possible for the network to store the user settings e.g. using GUP.
+
+## 6.6 Availability
+
+The user should be able to receive MBMS user services via generic IP access systems.
+
+Note: The transport of MBMS user services over non 3GPP accesses is out of scope of 3GPP, however if the non 3GPP access system has multicast or broadcast capabilities these should be utilised if possible.
+
+# --- Annex A (informative): Use Cases
+
+| Service Example                                              | Media                                                          | Distribution Scope   | MBMS User Service Classification | Application Bit rate Note 1 | Delivery Verification Required Note 3 | User Charging Note 4          |
+|--------------------------------------------------------------|----------------------------------------------------------------|----------------------|----------------------------------|-----------------------------|---------------------------------------|-------------------------------|
+| Reliable text distribution (eg Local news)                   | Text                                                           | Multicast            | Download                         | Up to 10 kbps               | Yes                                   | Event                         |
+| Unverified text distribution                                 | Text                                                           | Multicast, Broadcast | Carousel, download               | Up to 10 kbps               | No                                    | -                             |
+| Text distribution with still images and/or low quality video | Text, Still images, Video (e.g. 3fps)                          | Multicast, Broadcast | Carousel, download               | Up to 32 kbps               | Service dependent                     | User service dependent Note 2 |
+| Audio streaming                                              | Stereo Audio                                                   | Multicast            | Streaming                        | Up to 48kbps                | Service dependent                     | -                             |
+| Audio streaming                                              | Stereo Audio                                                   | Broadcast            | Streaming                        | Up to 48kbps                | No                                    | -                             |
+| Audio download                                               | Stereo Audio                                                   | Broadcast            | Download                         | Up to 48kbps                | Service dependent                     | -                             |
+| Audio download                                               | Stereo Audio                                                   | Multicast            | Download                         | Up to 48kbps                | Yes                                   | Event                         |
+| Audio distribution with low quality video                    | Stereo Audio, Video (e.g. 3fps)                                | Broadcast            | Streaming                        | Up to 128kbps Note 5        | No                                    | -                             |
+| Audio distribution with low quality video                    | Stereo Audio, Video (e.g. 3fps)                                | Multicast            | Streaming                        | Up to 128kbps Note 5        | Service dependent                     | -                             |
+| Audio distribution with low quality video                    | Stereo Audio, Video (e.g. 3fps)                                | Broadcast            | Download                         | Up to 128kbps Note 5        | Service dependent                     | -                             |
+| Audio distribution with low quality video                    | Stereo Audio, Video (e.g. 3fps)                                | Multicast            | Download                         | Up to 128kbps Note 5        | Yes                                   | Event                         |
+| Video streaming                                              | Video & supplementary data (e.g. text, still images)           | Broadcast            | Streaming                        | Up to 384 kbps Note 5       | No                                    | -                             |
+| Video streaming                                              | Video & supplementary data (e.g. text, still images)           | Multicast            | Streaming                        | Up to 384 kbps Note 5       | Service dependent                     | -                             |
+| Video distribution                                           | Video & supplementary data (e.g. text, still images)           | Broadcast            | Download                         | Up to 384 kbps Note 5       | Service dependent                     | -                             |
+| Video distribution                                           | Video & supplementary data (e.g. text, still images)           | Multicast            | Download                         | Up to 384 kbps Note 5       | Yes                                   | Event                         |
+| General Content Distribution                                 | Video, Audio, File Data (binary data)                          | Broadcast            | Carousel, download               | Up to 384 kbps Note 5       | Service dependent                     | -                             |
+| General Content Distribution                                 | Video, Audio, File Data (binary data)                          | Multicast            | Carousel, download               | Up to 384 kbps Note 5       | Yes                                   | Event                         |
+| Secure data download                                         | File; eg UE type specific and/or application specific software | Multicast            | Carousel, download               | Up to 10kbps                | -                                     | -                             |
+
+### Notes :
+
+1. Bit rate of the user data at the application layer.
+2. If User Charging is Event based then Delivery Verification is required
+3. Delivery Verification relates only to verification itself. Quality assessments may be required in addition.
+4. DRM may be applicable to User Charging.
+5. For GERAN lower bandwidth availability may constrain some applications. In such cases it may be possible to provide the same content via different delivery methods.
+6. The ' - ' mark indicates that no applicable information has been identified.
+
+# --- Annex B (informative): Example service scenarios
+
+This annex provides a non-exhaustive list of potential service scenarios for MBMS User Services.
+
+## B.1 Text notification service
+
+**Media:** Text
+
+**Precondition:** The user is a member of a MBMS Multicast group supplying text alerts.
+
+**Actions:** At an appropriate time an alert is sent to the user's mobile handset using the MBMS Multicast service.
+
+**Post condition:** The user receives the alert using her mobile handset and takes appropriate action.
+
+## B.2 Local Area Information distribution (Case A)
+
+**Media:** Text & Text with low quality video
+
+**Precondition:** The user is a registered with an MBMS Broadcast service providing information to the local area such as local news and weather reports.
+
+**Actions:** Information in the form of text & text with low quality video is distributed to the user's mobile handset by the MBMS Broadcast service. The text may be scrolled on the mobile handset. The information distributed by the MBMS Broadcast Service may be repeated periodically and updated at appropriate intervals.
+
+**Post condition:** The user is aware of events that have taken place within the local area and can view appropriate images.
+
+## B.3 Local Area Information distribution (Case B)
+
+**Media:** Video & Audio
+
+**Precondition:** The user is a registered with an MBMS Broadcast service providing streaming audio and/or visual content related to a local area, such as audio and visual guides to local attractions, traffic reports etc...
+
+**Actions:** Audio and/or visual information is distributed to the user's mobile handset by the MBMS Broadcast service. The user is able experience the content on her mobile device. The user is able to receive the MBMS broadcast service continuously throughout the local area. At some points the user is able to interact with the content of the MBMS Broadcast service in order to access specific information regarding items being presented within the content. The user is able to activate/deactivate reception of the MBMS service at any time.
+
+**Post condition:** The user experiences and interacts with the content provided and is therefore able to obtain information regarding the local area and act accordingly.
+
+## B.4 Multicast distribution
+
+**Media:** Text & Text with still images
+
+**Precondition:** The user is a member if a MBMS multicast group providing personally tailored content such as targeted advertising etc...
+
+**Actions:** Information is provided by the MBMS Multicast service in the form of text & text with still images, to the user's mobile handset based on her subscription to the Multicast group and current location.
+
+**Post condition:** The user receives tailored content and is able to utilize this as appropriate.
+
+## B.5 Audio Distribution
+
+**Media:** Stereo Audio
+
+**Precondition:** The user is registered with an MBMS Broadcast service providing stereo quality streaming audio content.
+
+**Actions:** Audio content is distributed to the user's mobile handset by the MBMS Broadcast service. Whilst listening to the audio content the user is able to interact with the service using the capabilities of the mobile handset (e.g. messaging).
+
+**Post condition:** The user is able to enjoy the stereo quality audio content and interacts with the service as appropriate.
+
+## B.6 General Content Distribution
+
+**Media:** Video, Audio & File Data
+
+**Precondition:** The user is registered with a MBMS Broadcast service providing a variety of content.
+
+**Actions:** Content is periodically distributed to a particular area by the MBMS Broadcast service. When the user activates reception of the MBMS Broadcast service she is able to receive the content being distributed at that time.
+
+**Post condition:** The user is able to receive and enjoy the content being distributed.
+
+## B.7 Software Download
+
+**Media :** File
+
+**Preconditions :** Need to update/download software in UE, the User is subscribed to MBMS User Service, OTA download is supported in UE
+
+**Actions:** The operator compiles a list of affected users and sends them a text message (using MBMS) explaining the problem and that the user should select the MBMS application on their handset. The user sees a message inviting her to activate the Enable Upgrade, selects 'yes' and the software patch transferred by the MBMS User Service, including verification parameters.
+
+**Postcondition :** The software once installed allows the user to view the MMs that she couldn't see before.
+
+# Annex C (informative): Change history
+
+| Change history |           |           |        |      |     |       |     |                                                                                 |        |        |             |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|---------------------------------------------------------------------------------|--------|--------|-------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                                 | Old    | New    | WI          |
+| Jun 2003       |           |           | 22.246 |      |     |       |     | Initial draft presented                                                         | 0.0.0  | 0.1.0  | MBMS        |
+| Aug 2003       |           |           | 22.246 |      |     |       |     | Output from MBMS adhoc Staines                                                  | 0.1.0  | 0.2.0  | MBMS        |
+| Sep 2003       |           |           | 22.246 |      |     |       |     | Approved in SA1 for presentation to SA #21                                      | 0.2.0  | 1.0.0  | MBMS        |
+| Oct 2003       |           |           | 22.246 |      |     | Rel-6 |     | Raised to version 2.0.0 for approval at SA #22                                  | 1.0.0  | 2.0.0  | MBMS        |
+| SP-22          | SP-030708 | S1-031003 | 22.246 |      |     | Rel-6 |     | Approved at SA #22                                                              | 2.0.0  | 6.0.0  | MBMS        |
+| SP-23          | SP-040204 |           | 22.246 | 0001 | 1   | Rel-6 | B   | CR on advertising of capabilities required to receive a particular transmission | 6.0.0  | 6.1.0  | MBMS        |
+| SP-23          | SP-040204 | S1-040226 | 22.246 | 0002 | -   | Rel-6 | F   | Addition of "MBMS transport service" definition                                 | 6.0.0  | 6.1.0  | MBMS        |
+| SP-23          | SP-040204 | S1-040227 | 22.246 | 0003 | -   | Rel-6 | F   | Clarification on delivery verification for MBMS user services                   | 6.0.0  | 6.1.0  | MBMS        |
+| SP-23          | SP-040204 |           | 22.246 | 0004 | 1   | Rel-6 | C   | Using a single MBMS transport service for multiple MBMS user services           | 6.0.0  | 6.1.0  | MBMS        |
+| SP-25          | SP-040505 | S1-040634 | 22.246 | 0005 | -   | Rel-6 | D   | Minor corrections to TS 22.246 (MBMS User Services)                             | 6.1.0  | 6.2.0  | MBMS        |
+| SP-29          | SP-050530 | S1-050887 | 22.246 | 0006 | -   | Rel-7 | C   | Support of enhanced MBMS user services providing multiple QoS levels (2)        | 6.2.0  | 7.0.0  | MBMSE       |
+| SP-29          | SP-050530 | S1-050939 | 22.246 | 0007 | -   | Rel-7 | C   | Support of enhanced MBMS user services providing multiple QoS levels            | 6.2.0  | 7.0.0  | MBMSE       |
+| SP-32          | SP-060308 | S1-060513 | 22.246 | 0009 | -   | Rel-7 | F   | Proposed CR to clarify the requirements for roaming                             | 7.0.0  | 7.1.0  | MBMSE       |
+| SP-32          | SP-060307 | S1-060609 | 22.246 | 0010 | -   | Rel-8 | B   | Requirements on MBMS user service over generic IP accesses                      | 7.1.0  | 8.0.0  | MBMSE       |
+| SP-33          | SP-060466 | S1-060935 | 22.246 | 0011 | -   | Rel-8 | A   | Proposed CR to clarify the requirements for roaming (see CR 0009)               | 8.0.0  | 8.1.0  | MBMSE       |
+| SP-34          | SP-060770 | S1-061433 | 22.246 | 0012 | -   | Rel-8 | B   | Requirements for LTE MBMS Television Service                                    | 8.1.0  | 8.2.0  | LTE         |
+| SP-35          | SP-070131 | S1-070282 | 22.246 | 0015 | 1   | Rel-8 | C   | Requirements for LTE MBMS Television Service                                    | 8.2.0  | 8.3.0  | SAE-R (LTE) |
+| SP-35          | SP-070115 | S1-070181 | 22.246 | 0017 | -   | Rel-8 | A   | Parallel, but regional, MBMS Sessions within one MBMS service.                  | 8.2.0  | 8.3.0  | MBMSE       |
+| SP-36          | SP-070364 | S1-070784 | 22.246 | 0021 | -   | Rel-8 | A   | CR on Service Class Handling                                                    | 8.3.0  | 8.4.0  | MBMS        |
+| SP-39          | SP-080043 | S1-080302 | 22.246 | 0022 | 3   | Rel-8 | B   | Requirement for delivery verification in MBMS                                   | 8.4.0  | 8.5.0  | TEI8        |
+| SP-39          | SP-080043 | S1-080303 | 22.246 | 0023 | 3   | Rel-8 | B   | Requirement for pre-delivery verification in MBMS                               | 8.4.0  | 8.5.0  | TEI8        |
+| SP-46          | SP-090844 | S1-094275 | 22.246 | 0029 | 1   | Rel-9 | F   | Updating to also include E-UTRAN for MBMS                                       | 8.5.0  | 9.0.0  | TEI9        |
+| 2011-03        | -         | -         | -      | -    | -   | -     | -   | Update to Rel-10 version (MCC)                                                  | 9.0.0  | 10.0.0 |             |
+| 2012-09        | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-11 by MCC                                                        | 10.0.0 | 11.0.0 |             |

marked/Rel-11/22_series/22278/raw.md

@@ -0,0 +1,780 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                      |           |
+|------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                       | 5         |
+| Introduction .....                                                                                   | 5         |
+| 1 Scope.....                                                                                         | 6         |
+| 2 References.....                                                                                    | 6         |
+| 3 Definitions and abbreviations .....                                                                | 7         |
+| 3.1 Definitions.....                                                                                 | 7         |
+| 3.2 Abbreviations .....                                                                              | 7         |
+| 4 General description .....                                                                          | 8         |
+| 4.1 Objectives.....                                                                                  | 8         |
+| 5 High-level requirements – user and operational aspects.....                                        | 9         |
+| 5.1 Requirements for Fixed Mobile Interworking .....                                                 | 10        |
+| 5.2 Void.....                                                                                        | 11        |
+| 5.3 Void.....                                                                                        | 11        |
+| 6 Basic capabilities.....                                                                            | 11        |
+| 6.1 Support of IP traffic.....                                                                       | 11        |
+| 6.1.1 Support of increased IP traffic demand .....                                                   | 11        |
+| 6.1.2 Void .....                                                                                     | 11        |
+| 6.1.3 Void.....                                                                                      | 11        |
+| 6.1.4 Support of basic IP connectivity.....                                                          | 11        |
+| 6.1.5 Support of IP multicast service.....                                                           | 11        |
+| 6.2 IP session control .....                                                                         | 11        |
+| 6.3 Quality of Service.....                                                                          | 13        |
+| 6.4 Support of Multicast and Broadcast Services .....                                                | 14        |
+| 6.5 Support of Emergency Calls .....                                                                 | 14        |
+| 7 Multi-access and seamless mobility.....                                                            | 15        |
+| 7.1 Mobility management .....                                                                        | 15        |
+| 7.1.1 Heterogeneous access systems mobility.....                                                     | 15        |
+| 7.1.2 Local breakout .....                                                                           | 15        |
+| 7.1.3 Fixed Access Systems .....                                                                     | 16        |
+| 7.1.4 Service continuity .....                                                                       | 16        |
+| 7.1.4.1 General.....                                                                                 | 16        |
+| 7.1.4.2 Service continuity at domain and RAT change for TS 11, TS 12 and equivalent PS service ..... | 16        |
+| 7.1.4.2A Voice Call Service continuity between 3GPP defined RATs and non 3GPP defined RATs.....      | 17        |
+| 7.1.4.3 Service continuity between E-UTRAN and 3GPP2 accesses on Evolved Packet Core .....           | 17        |
+| 7.1.4.4 Service continuity between 3GPP and WiMAX access on Evolved Packet Core.....                 | 17        |
+| 7.1.5 Access network discovery .....                                                                 | 17        |
+| 7.1.6 Steering of access .....                                                                       | 18        |
+| 7.1.7 CS fallback .....                                                                              | 18        |
+| 7.1.7.1 General.....                                                                                 | 18        |
+| 7.1.7.2 Roaming in a VPLMN not supporting CS fallback.....                                           | 18        |
+| 7.2 IFOM Service requirements.....                                                                   | 19        |
+| 8 Performance requirements for the Evolved Packet System .....                                       | 19        |
+| 9 Security and privacy.....                                                                          | 21        |
+| 9.1 General .....                                                                                    | 21        |
+| 9.2 Security requirements.....                                                                       | 21        |
+| 9.3 Privacy requirements.....                                                                        | 21        |
+| 10 Charging Aspects .....                                                                            | 22        |
+| <b>Annex A (informative): Requirements for further study.....</b>                                    | <b>23</b> |
+| A.1 Management of access networks.....                                                               | 23        |
+| A.2 Use cases for Fixed Mobile Convergence.....                                                      | 23        |
+
+**Annex B (Normative): Evolved Packet System (EPS) applicable specifications..... 25**  
+B.1 EPS Applicable Specifications..... 25  
+**Annex B1 (Informative): Void..... 26**  
+Annex C (informative): Change history..... 27
+
+# --- 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
+
+To ensure competitiveness in a longer time frame an evolution of the overall 3GPP system needs to be considered.
+
+This document compiles requirements to ensure that an Evolved Packet System can cope with the rapid growth in IP data traffic and demanding requirements for new multimedia type of applications in terms of performance and quality, delivered to the user, whilst at the same time enabling cost effective deployment and operation.
+
+The Evolved Packet System is characterised by:
+
+- Reduced latency
+- Higher user data rates equating to broadband performance
+- Improved system capacity and coverage
+- Lower operational costs
+
+# --- 1 Scope
+
+The present document describes the service requirements for the Evolved Packet System. Additional requirements for E-UTRAN are contained in the specifications identified in annex B.
+
+# --- 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 TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
+- [2] 3GPP TS 21.905: "Vocabulary for 3GPP specifications".
+- [3] 3GPP TS 22.258: "Service Requirements for the All-IP Network (AIPN); Stage1".
+- [4] 3GPP TR 25.913: "Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)".
+- [5] 3GPP TS 22.115: "Service aspects; Charging and billing".
+- [6] ETSI TS 102 250-1: "Speech Processing, Transmission and Quality Aspects (STQ); QoS aspects for popular services in GSM and 3G networks: Part 1: Identification of Quality of Service aspects".
+- [7] 3GPP TR 23.882: "3GPP system architecture evolution (SAE): Report on technical options and conclusions".
+- [8] C.S0001-A Introduction to cdma2000 Standards for Spread Spectrum Systems - Release A.
+- [9] C.S0002-A Physical Layer Standard for cdma2000 Spread Spectrum Systems - Release A.
+- [10] C.S0003-A Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems - Release A addendum 2.
+- [11] C.S0004-A Signaling Link Access Control (LAC) Specification for cdma2000 Spread Spectrum Systems -Addendum 2.
+- [12] C.S0005-A Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems - Release A addendum 2.
+- [13] C.S0006-A Analog Signaling Standard for cdma2000 Spread Spectrum Systems - Addendum 2.
+- [14] A.S0007 – A.S0009 Interoperability Specification (IOS) for High Rate Packet Data (HRPD).
+- [15] A.S0011 – A.S0017 Interoperability Specification (IOS) for cdma2000 Access Network Interfaces.
+- [16] X.S0011 cdma2000 Wireless IP Network.
+- [17] C.S0024-A cdma2000 High Rate Packet Data Air Interface Specification.
+- [18] C.S0024-0 cdma2000 High Rate Packet Data Air Interface Specification.
+- [19] Void.
+
+- [20] [WiMAX Forum Mobile System Profile, Release 1.0](#) .
+- [21] 3GPP TS 22.101: "Service Aspects; Service Principles".
+- [22] "Recommendations and Requirements for Networks based on WiMAX Forum Certified™ Products" (WiMAX stage 1)
+- [23] "WiMAX Forum Network Architecture (Stage 2: Architecture Tenets, Reference Model and Reference Points)"
+- [24] "WiMAX Forum Network Architecture (Stage 3: Detailed Protocols and Procedures)"
+- [25] Void.
+- [26] S.R0048-A 3G Mobile Equipment Identifier (MEID)
+- [27] Void.
+- [28] Void.
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [2] and the following apply.
+
+**Evolved Packet System:** is an evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs. The Evolved Packet System comprises the Evolved Packet Core together with the evolved radio access network (E-UTRA and E-UTRAN).
+
+**Service Continuity:** The uninterrupted user experience of a service that is using an active communication (e.g. an ongoing voice call) when a UE undergoes a radio access technology change or a CS/PS domain change without, as far as possible, the user noticing the change.
+
+Note: In particular Service Continuity encompasses the possibility that after a RAT / domain change the user experience is maintained by a different telecommunication service (e.g. tele- or bearer service) than before the RAT / domain change.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [2] and the following apply.
+
+|     |               |
+|-----|---------------|
+| NRT | Non Real Time |
+| RT  | Real Time     |
+
+# --- 4 General description
+
+## 4.1 Objectives
+
+The Evolved Packet System is a higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs. The focus of the Evolved Packet System work is on enhancement of Packet Switched technology to cope with rapid growth in IP traffic.
+
+The objectives of the Evolved Packet System are to:
+
+- Provide higher data rates, lower latency, high level of security and enhanced QoS;
+- Support a variety of different access systems (existing and future), ensuring mobility and service continuity between these access systems;
+- Support access system selection based on a combination of operator policies, user preference and access network conditions;
+- Realise improvements in basic system performance whilst maintaining the negotiated QoS across the whole system;
+- Provide capabilities for co-existence with legacy systems and migration to the Evolved Packet System.
+
+# --- 5 High-level requirements – user and operational aspects
+
+The Evolved Packet System shall be capable of accommodating a variety of different access systems thus providing a multi-access system environment to the user.
+
+The Evolved Packet System shall provide mobility functionality within and across the different access systems.
+
+The Evolved Packet System shall provide capabilities to support the efficient integration of E-UTRAN PS Core Network Nodes and GERAN/UTRAN PS Core Network Nodes.
+
+The Evolved Packet System shall optimize mobility functionality meaning that it shall offer minimal signalling overhead, minimal handover interruption time, secure handover procedure and local breakout.
+
+The Evolved Packet System shall provide capabilities to inter-work with a variety of broadband networks based on IP technologies including those not specified by 3GPP.
+
+The Evolved Packet System shall provide enhanced performance e.g., low communication delay, low connection set-up time and high communication quality.
+
+The Evolved Packet System shall be able to efficiently support a variety of traffic models e.g. user-to-user, user-to-group and traffic models generated by ubiquitous services.
+
+The Evolved Packet System shall provide functionality to support outbound roaming subscribers on other Evolved Packet Systems and legacy networks.
+
+The Evolved Packet System shall provide functionality to support inbound roaming subscribers from other Evolved Packet Systems and legacy networks.
+
+The Evolved Packet System shall be capable of supporting and inter-working with PS services provided on Rel-7 and earlier networks. The Evolved Packet System shall be capable of inter-working with CS services provided on Rel-7 and earlier networks.
+
+The Evolved Packet System shall support service continuity between 3GPP access systems and also between 3GPP access systems and non 3GPP access systems whether the UE supports simultaneous radio transmission or not.
+
+The Evolved Packet System shall be able to accommodate fixed access systems and to inter-work with fixed networks in order to provide service continuity over fixed/mobile converged networks.
+
+The Evolved Packet System service capability set shall include, as a minimum, support for the following categories of services that are likely to be used by the majority of operators:
+
+- Voice
+- Video
+- Messaging
+- Data file exchange
+
+The Evolved Packet System shall provide for efficient usage of system resources, especially of radio resources through both signalling and transport optimization, e.g. overhead, terminal power, radio resources, mobility state, signalling load.
+
+The Evolved Packet System shall support efficient delivery of text-based broadcast messages received from a legacy CBC.
+
+The Evolved Packet System shall support E-UTRAN only operators. The system shall allow these operators to offer national roaming to their subscribers.
+
+The Evolved Packet System shall be capable of uniquely identifying each device that connects via 3GPP access networks and 3GPP2 access networks. For a dual mode device supporting both 3GPP and 3GPP2 access technologies, there shall be a single persistent identifier used to identify the device. This device identifier shall be the same even when the device moves between 3GPP and 3GPP2 access types.
+
+Note: The 3GPP2 device identifier structure is consistent with the IMEI structure [26].
+
+The EPC shall be capable of restricting access of specific 3GPP devices, 3GPP2 devices and dual mode 3GPP/3GPP2 devices.
+
+## 5.1 Requirements for Fixed Mobile Interworking
+
+The Evolved Packet System shall support the following scenarios: a single Operator offering both fixed and mobile access; different Operators collaborating to deliver services across both networks. These scenarios will be supported by interworking between the access networks.
+
+The Evolved Packet System shall support access to services on the mobile network via interworking with a fixed access network for the following scenarios:
+
+- Residential scenarios for operators that own both wireless and wireline access networks
+- Residential scenarios for operators that own wireless access networks only
+- Enterprise scenarios with managed connectivity between mobile operators and enterprise networks
+
+The Evolved Packet System shall be able to support the following functions for interworking between the fixed access in the above scenarios and Evolved Packet Core:
+
+- connectivity,
+- subscriber authentication/authorization,
+- offline charging
+- online charging for traffic routed via the Evolved Packet Core
+- Policy Control and
+- Quality of Service.
+
+The Evolved Packet Core shall support the following for fixed access:
+
+- policy management,
+- authentication for WLAN terminals and fixed devices,
+- charging
+
+The EPS shall be capable to set operator policies to support simultaneous access to PLMN services and traffic offloading to the fixed network.
+
+Interworking shall support the following scenarios:
+
+When traffic is routed via EPC
+
+- When H(e)NB is being used and traffic is offloaded in the local wireline network
+- When WLAN is being used and traffic is offloaded in the local wireline network (i.e. non-seamless WLAN offloading)
+
+Additionally the Evolved Packet System shall be able:
+
+- to minimize QoS and Policy management signalling overhead while interworking between the fixed access and Evolved Packet Core.
+- to route different simultaneously active PDN connections through different accesses while interworking between the fixed access and Evolved Packet Core.
+- to route different IP flows belonging to the same PDN connection through different accesses while interworking between the fixed access and Evolved Packet Core.
+
+The requirements for mobility in chapter 7.1.3 apply also to interworking between the fixed access and Evolved Packet Core.
+
+## 5.2 Void
+
+## 5.3 Void
+
+# --- 6 Basic capabilities
+
+## 6.1 Support of IP traffic
+
+### 6.1.1 Support of increased IP traffic demand
+
+The Evolved Packet System shall be able to provide guaranteed QoS for services and use the resources of the Evolved Packet System with high efficiency i.e. ensure that quality conditions for a particular communication are fulfilled without deterioration between the communicating end-points.
+
+### 6.1.2 Void
+
+### 6.1.3 Void
+
+### 6.1.4 Support of basic IP connectivity
+
+Following registration on the network, the Evolved Packet System shall maintain an IP connectivity with the UE. Following registration it shall be possible for an UE to send and receive IP packets.
+
+### 6.1.5 Support of IP multicast service
+
+The Evolved Packet System shall support IP multicast service.
+
+## 6.2 IP session control
+
+The Evolved Packet System shall provide for session mobility and session adaptation to terminal capabilities, user preferences, subscriber priorities, network conditions and/or other operator-defined criteria. Session adaptation shall be under the control of the operator.
+
+The Evolved Packet System shall support session control for multi-party sessions (e.g. user-to-group) and shall provide a scaleable solution.
+
+In order to support the efficient routing of IP traffic, local breakout (see Section 7.1.2) shall be supported.
+
+The Evolved Packet System shall support a UE having simultaneously more than one active PDN connections exchanging traffic with more than one peer (external network or other UE), when the network policies and user subscription allow it.
+
+If a UE is under the coverage of 3GPP access and one or more non-3GPP accesses, it shall be possible for the UE to communicate using multiple accesses simultaneously.
+
+The Evolved Packet System shall provide the system operator with the means to control the number of simultaneously active PDN connections and combinations thereof to and from a UE.
+
+A single application running on the UE shall not be required to send and receive traffic through multiple PDNs.
+
+## 6.3 Quality of Service
+
+The Evolved Packet System shall have the ability to provide a quality of service equal to or better than the QoS requirements specified for GSM and UMTS. Quality of Service from the customer's perspective is to be considered in phases as specified in ETSI TS 102 250-1[6].
+
+![Figure 2: Phases of service use from customer's point of view. The diagram shows four yellow rectangular boxes arranged horizontally, each containing one of the following text: 'Network Access', 'Service Access', 'Service Retainability', and 'Service Integrity'.](7f17c430b9598e4d748a8041457810b3_img.jpg)
+
+The diagram consists of four yellow rectangular boxes arranged horizontally. Each box contains one of the following text: 'Network Access', 'Service Access', 'Service Retainability', and 'Service Integrity'.
+
+Figure 2: Phases of service use from customer's point of view. The diagram shows four yellow rectangular boxes arranged horizontally, each containing one of the following text: 'Network Access', 'Service Access', 'Service Retainability', and 'Service Integrity'.
+
+**Figure 2: Phases of service use from customer's point of view**
+
+Figure 2 shows the different phases (Quality of Service aspects) during service use from the customer's point of view.
+
+The meaning of these QoS aspects are:
+
+- 1) **Network Access:** The network indication on the display of the mobile is a signal to the customer that he can use the service of this network operator (or any other means to indicate to the user that a network is available).
+- 2) **Service Access:** If the customer wants to use a service, the network operator should provide him as fast as possible access to the service.
+- 3) **Service Integrity:** This describes the Quality of Service during service use.
+- 4) **Service Retainability:** Service Retainability describes the termination of services (in accordance with or against the will of the user).
+
+In particular the Evolved Packet System shall provide for the following:
+
+- There should be no perceptible deterioration of audio quality of a voice call during and following handover between dissimilar CS and PS access networks, and transitions between PS access networks supporting different IP protocol versions.
+- There should be no loss of data, as a result of handovers between dissimilar fixed and mobile access systems, including those that support different versions of the IP protocol.
+- There should be no discernable difference in perceived service quality for users receiving services via unicast and users receiving the same service via multicast.
+- The Evolved Packet System shall support QoS differentiations for unicast bearers.
+- The Evolved Packet System shall support QoS backwards compatibility to earlier 3GPP QoS releases.
+- It shall be possible for the Evolved Packet System to maintain end-to-end QoS without modification when the terminal moves from one access system to a new access system, and the new access system supports the required QoS.
+- It shall be possible for the Evolved Packet System to change QoS, when the terminal moves from one access system to a new access system and the new access system can not provide the same QoS as the old access system or the new access system can provide higher QoS.
+- It shall be possible for the Evolved Packet System to support service continuity for a terminal changing access system and the new access system cannot provide the same QoS as the old one.
+- The Evolved Packet System shall support transport QoS differentiations for multicast bearers.
+- It shall be possible for the Evolved Packet System to maintain QoS within a multicast session without QoS changes for other members of the session when a terminal joins or leaves the multicast session or moves to a new access system.
+- The Evolved Packet System network shall support a minimum of 8 levels of QoS in parallel.
+- The Evolved Packet System network shall support a minimum of 4 parallel RT QoS levels with the appropriate QoS differentiation.
+
+NOTE 1: The requirement for the number of simultaneously supported QoS levels is independent of any MBMS QoS levels.
+
+- Multiple RT services, with similar QoS requirements, shall be served by the same RT QoS level and multiple NRT services, with similar QoS requirements, shall be served by the same NRT QoS level.
+
+The maximum number of parallel RT and NRT services shall not be limited in the Evolved Packet System including the UE. Only the number of parallel RT and NRT QoS levels are limited to the upper value supported by the Evolved Packet System.
+
+- Differentiated handling based on QoS is needed for different traffic types.
+- The Evolved Packet System shall support parallel operation of RT and NRT services per user.
+
+NOTE 2: The different QoS levels provided for RT and NRT services would be differentiated with regards to e.g. maximum end-to-end delay, packet size, packet drop percentage, etc. Bandwidth is not used to define a QoS level.
+
+## 6.4 Support of Multicast and Broadcast Services
+
+The Evolved Packet System shall be able to support Multicast and Broadcast Services which shall be enhanced especially from some aspects, e.g. optimized service provisioning procedures, better performance compared to current MBMS system, and support of multiple access systems.
+
+## 6.5 Support of Emergency Calls
+
+The Evolved Packet System shall support IMS emergency calls applicable to the PS domain, defined in TS 22.101 [21]
+
+# 7 Multi-access and seamless mobility
+
+## 7.1 Mobility management
+
+### 7.1.1 Heterogeneous access systems mobility
+
+![Diagram illustrating heterogeneous access system mobility. A central 'Evolved Packet System' (purple cloud) contains components SC, MM, Policy, and Co AAA. It is connected to PSTN (top left), Internet (top right), 3GPP Legacy System (left), E-UTRA and E-UTRAN (bottom left), and Non 3GPP Access System (bottom right). Arrows indicate bidirectional connections between the central system and each of these external systems, with ellipses indicating additional connections.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+Diagram illustrating heterogeneous access system mobility. A central 'Evolved Packet System' (purple cloud) contains components SC, MM, Policy, and Co AAA. It is connected to PSTN (top left), Internet (top right), 3GPP Legacy System (left), E-UTRA and E-UTRAN (bottom left), and Non 3GPP Access System (bottom right). Arrows indicate bidirectional connections between the central system and each of these external systems, with ellipses indicating additional connections.
+
+**Figure 3: Heterogeneous access system mobility between 3GPP Legacy Systems or E-UTRAN and non 3GPP Access Systems including Fixed Access systems**
+
+The Evolved Packet System shall support mobility between heterogeneous access systems.
+
+The Evolved Packet System shall provide mobility mechanisms to support frequent handovers within and across 3GPP legacy systems or E-UTRAN and non 3GPP access systems in order to avoid service degradation.
+
+The Evolved Packet System shall support mobility mechanisms that accommodates access systems within Rel-7 and earlier.
+
+### 7.1.2 Local breakout
+
+The Evolved Packet System shall allow for local breakout. Local breakout means that for a user which makes mobility within and across one operator-defined network region, routing is optimized such that user plane traffic does not need to leave the current region. An operator may define network regions e.g., according to administrative domains. Local breakout is applicable for user-to-user traffic as well as for 3GPP-operator provided services (including internet access).
+
+Local breakout shall be allowed independently from the access system being used.
+
+Local breakout shall be allowed in both the non-roaming and the roaming case.
+
+The use of local breakout shall be authorised by the HPLMN. If local breakout is not authorised, the user plane traffic shall be handled in the home routed mode.
+
+### 7.1.3 Fixed Access Systems
+
+The Evolved Packet System shall be able to support fixed access systems with very limited or no mobility functionality.
+
+The Evolved Packet System shall be able to support mobility within and across 3GPP and non-3GPP access systems including fixed access systems
+
+### 7.1.4 Service continuity
+
+#### 7.1.4.1 General
+
+Service shall be maintained during and following changes of 3GPP access systems and non 3GPP systems.
+
+Service shall be maintained during and following a change of network in either direction between a Rel-7 and earlier network and an Evolved Packet System.
+
+It shall be possible to support Inter-PLMN handover with seamless service continuity within a 3GPP specified access system (UTRAN, E-UTRAN).
+
+When the access system changes, Multicast and Broadcast services shall be able to continue with their corresponding Multicast and Broadcast services, if the corresponding services are provided in the target access system.
+
+Note: Corresponding Multicast and Broadcast services are the Multicast and Broadcast services in the target access system which is associated to the Multicast and Broadcast services in the source access system, providing similar service experience, e. g. with same content but different bit-rate.
+
+![Diagram illustrating Inter-PLMN handover with seamless service continuity within a 3GPP specified access system. It shows two Evolved PLMNs, Evolved PLMN-A and Evolved PLMN-B, separated by a vertical dashed line. Each PLMN contains a 3GPP core (grey oval) connected to a 3GPP access (orange oval). A large red curved arrow points from the 3GPP access of Evolved PLMN-A to the 3GPP access of Evolved PLMN-B, indicating the handover process.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg)
+
+Diagram illustrating Inter-PLMN handover with seamless service continuity within a 3GPP specified access system. It shows two Evolved PLMNs, Evolved PLMN-A and Evolved PLMN-B, separated by a vertical dashed line. Each PLMN contains a 3GPP core (grey oval) connected to a 3GPP access (orange oval). A large red curved arrow points from the 3GPP access of Evolved PLMN-A to the 3GPP access of Evolved PLMN-B, indicating the handover process.
+
+**Figure 4: Inter-PLMN handover with seamless service continuity within a 3GPP specified access system**
+
+#### 7.1.4.2 Service continuity at domain and RAT change for TS 11, TS 12 and equivalent PS service
+
+It shall be possible to support continuity of an established voice call, i.e. between a TS11, TS12 and an equivalent PS service, when the UE moves between two different domains and RATs. The user experience shall be as far as possible unaffected by the change of domain and RAT. The RAT change procedure executed to enable service continuity for an established voice call shall target an interruption time not higher than 300 ms.
+
+RAT change and domain selection shall be under the control of the registered PLMN. When the UE is roaming, it shall be possible for the VPLMN to take into account any user's HPLMN operator policy.
+
+To support service continuity of an established voice call a UE shall not be required to support simultaneous radio transmission via different 3GPP defined RATs
+
+NOTE: In the case of CS emergency calls (TS12) the service continuity at domain and RAT change can only be performed if IMS emergency calls are supported by the target system.
+
+#### 7.1.4.2A Voice Call Service continuity between 3GPP defined RATs and non 3GPP defined RATs
+
+Continuity of an established voice call, i.e. between a TS11 and an equivalent PS service, when the UE moves between 3GPP defined RATs and non 3GPP defined RATs, shall be supported provided that the non-3GPP defined RATs is connected to the 3GPP system via the Evolved Packet Core.
+
+The user experience shall be as far as possible unaffected by the change of RAT.
+
+#### 7.1.4.3 Service continuity between E-UTRAN and 3GPP2 accesses on Evolved Packet Core
+
+The Evolved Packet System shall support bidirectional service continuity between cdma2000 1xRTT Revision A [8], [9], [10], [11], [12], [13], [14], [15] and E-UTRAN.
+
+NOTE 1: if bi-directional support is not practical, service continuity from E-UTRAN to cdma2000 1xRTT Revision A should have the higher priority.
+
+NOTE 2: The CS component of cdma2000 1xRTT Revision A is not expected to be connected to the Evolved Packet Core.
+
+The Evolved Packet System shall support bidirectional service continuity between cdma2000 HRPD (1xEV-DO) Revision A [17], [14], [15], [16] and E-UTRAN for best effort and real-time applications.
+
+The Evolved Packet System shall support bidirectional service continuity between cdma2000 HRPD (1xEV-DO) Revision 0 [18], [14], [15], [16] and E-UTRAN for best effort applications.
+
+#### 7.1.4.4 Service continuity between 3GPP and WiMAX access on Evolved Packet Core
+
+The Evolved Packet System shall support bidirectional service continuity between Mobile WiMAX [20], [22], [23], [24] and GERAN PS.
+
+The Evolved Packet System shall support bidirectional service continuity between Mobile WiMAX [20], [22], [23], [24] and UTRAN PS.
+
+The Evolved Packet System shall support bidirectional service continuity between Mobile WiMAX [20], [22], [23], [24] and E-UTRAN.
+
+NOTE: The above requirements assume that the service continuity takes place through the Evolved Packet Core.
+
+### 7.1.5 Access network discovery
+
+To avoid unnecessary background scan by the UE and to facilitate service continuity by the UE it shall be possible for the VPLMN and the HPLMN to provide the UE with access network information pertaining to locally supported non-3GPP access technologies, in a resource efficient and secure manner. This mechanism is meant to facilitate changes, including service continuity, between 3GPP access systems and non 3GPP access systems and vice versa. The information may be restricted to the access technologies the UE can use. To reduce battery drain, a UE should minimise the frequency of scanning for different access technologies.
+
+When discovering non-3GPP accesses a UE shall be able to receive information from a non-3GPP access network concerning to which PLMN, or PLMNs, the non-3GPP access network provides access.
+
+Note: The capability to provide such information by a non-3GPP access network is out of scope of 3GPP.
+
+When a UE receives service via a non-3GPP access it shall be possible for the PLMN that provides the non-3GPP access to indicate local availability of 3GPP access to the UE,, in a secure manner, subject to capabilities of the non-3GPP access network.
+
+### 7.1.6 Steering of access
+
+When a UE is accessing the Evolved Packet Core via E-UTRA, the operator of the PLMN that provides the access (registered PLMN or RPLMN for short) may request the UE to use - any or a specific - non-3GPP RAT. Similarly, if a UE is accessing the Evolved Packet Core via a non-3GPP RAT then the RPLMN may want to request the UE to use E-
+
+UTRA. The reason for such steering may be load balancing (for camped- and traffic load balancing), operator policy, private networks/home cells, service based mobility control etc.
+
+The RPLMN shall be able to download on the UE a list of preferred access technologies in priority order. If, while the UE is registered on that PLMN, an access technology with higher priority than the one currently used is detected, the UE shall attempt to use the higher priority access network to access the RPLMN.
+
+The UE shall only perform access technology selection within the RPLMN.
+
+In case the UE is connected to the PLMN via a non-3GPP access, then the PLMN reselection procedures specified for that access technology may be executed.
+
+Note 1: The PLMN operator may provide access to the Evolved Packet Core either through an own access network (E-UTRA or non-3GPP access) or in collaboration with an access network operator that operates a non-3GPP access network.
+
+Note 2: A specific non-3GPP RAT may e.g. be identified by RAT type and the access network name (as advertized by the access network), or a list of access network names.
+
+The HPLMN may also provide the UE with a list of preferred access technologies in priority order for use in the RPLMN. Only one list of preferred access technologies can be active at a time and the list provided by the RPLMN takes precedence over the list provided by the HPLMN. The list of preferred access technologies received from the VPLMN is specific to that VPLMN and PLMNs equivalent to it.
+
+### 7.1.7 CS fallback
+
+#### 7.1.7.1 General
+
+For those services delivered via the HPLMN that the HPLMN only supports in the CS domain (e.g. voice services), when such services are invoked while the UE is configured to use CS Fallback and registered in the E-UTRAN (either in the HPLMN or in a VPLMN), it shall be possible for the EPS to request the UE to perform a change of radio access technology in order to deliver the service over UTRAN or GERAN or 1xRTT.
+
+In the case of an incoming CS service to a UE that is registered for CS services and active in E-UTRAN, the EPS shall transfer the CLI to the UE if available and the calling party has not restricted the presentation, prior to triggering CS fallback. Depending on UE configuration and when the UE is in connected mode, the user or an application on behalf of the user may request to accept or reject CS fallback before performing a change of radio access technology. The default behaviour of the UE is to accept the CS fallback.
+
+#### 7.1.7.2 Roaming in a VPLMN not supporting CS fallback
+
+When a UE that is configured to use CS fallback registers over E-UTRAN in a VPLMN not supporting CS fallback the default behaviour of the UE is to attempt to select a GERAN/UTRAN/1xRTT CS radio access technology in the VPLMN or in a PLMN equivalent to the VPLMN. The default behaviour of the UE is not to autonomously attempt to (re-)select the E-UTRAN for the duration of the time the UE stays in a VPLMN and PLMNs equivalent to the VPLMN.
+
+The default behaviour may be changed based on user preference settings.
+
+The UE may offer the user to perform a PLMN scan and display the list of available PLMNs. The selection of a different PLMN is performed using the manual mode.
+
+## --- 7.2 IFOM Service requirements
+
+Simultaneous active mode of operation is an optional capability for multimode UEs, which support 3GPP and WLAN access. UE supporting simultaneous active mode of operation between one set of technologies may not be capable to support simultaneous active mode of operation between a different technology set (e.g. due to radio interference limitations).
+
+The following requirements apply to the case of UEs with multiple interfaces which will simultaneously connect to 3GPP access and one single WLAN access.
+
+- It shall be possible to provide service continuity when the UE moves from the 3GPP access to WLAN access and vice versa.
+- If the UE is under the coverage of more than one access, including 3GPP and WLAN accesses and communicates using multiple accesses simultaneously, it shall be possible to select one access when a flow is started and re-distribute the flows to/from a UE between accesses while connected.
+- It shall be possible for the operator to enable and control via policies the simultaneous usage of multiple accesses.
+- It shall be possible to distribute IP flows to/from a UE between available accesses based on the characteristics of the flows and the capabilities of the available accesses, subjected to user's preferences and operator's policies.
+- It shall be possible for the operator to define policies for the control of the distribution of IP flows between available accesses. Each policy shall include a list of preferred accesses and whether the policy may be overridden by the user's preferences.
+
+NOTE: The possibility of manual selection or user override is not precluded.
+
+These policies may be defined per APN, per IP flow class under any APN or per IP flow class under a specific APN. The IP flow class identifies a type of service (e.g. IMS voice) or an operator defined aggregation of services.
+
+The policies apply with the following priority order:
+
+1. Policies per IP flow class under a specific APN.
+  2. Policies per IP flow class under any APN.
+  3. Policies per APN.
+- Distribution of flows to/from a UE between available accesses based on the characteristics of the flows and/or the capabilities of the available accesses shall be possible for flows exchanged by both operator controlled (e.g. IMS) and non operator controlled (e.g. web and mail access) applications/services.
+  - It shall be possible to move all the flows to/from a UE out of a certain access in case the UE loses connectivity with that access (e.g. UE moves out of coverage of a WLAN access while maintaining connectivity through the 3GPP access).
+  - Re-distribution of flows to/from a UE between accesses may be triggered by changes to the characteristics of the flows (e.g. QoS requirements) or the capabilities of the available accesses (e.g. due to network congestion, mobility event, or UE discovers a new access) during the connection.
+
+# --- 8 Performance requirements for the Evolved Packet System
+
+The Evolved Packet System comprises the Evolved Packet Core together with the evolved radio access network (E-UTRA and E-UTRAN). A study of the Evolved Packet Core can be found in TS23.882 [7] and the evolved radio access network E-UTRA and E-UTRAN in TR25.913 [4].
+
+The performance objectives for the Evolved Packet System include higher user data rates, reduced latency, improved system capacity and coverage, reduced network complexity and lower operating costs.
+
+The Evolved Packet System shall meet or exceed the following performance criteria:
+
+- a) The radio access network shall be capable of supporting instantaneous peak packet data rates of 100 Mbps on the radio access bearer downlink to the UE and 50 Mbps on the uplink.
+- b) The Evolved Packet System shall be capable of providing lower user and control plane latency when compared to existing 3GPP access networks. The maximum delay should be comparable to that for fixed broadband Internet access technologies. [e.g. less than 5ms in ideal conditions]
+- c) The system shall be capable of supporting large volumes of mixed e.g. voice, data and multimedia traffic. Enhanced load balancing and steering of roaming methods should be used to minimise cell congestion.
+- d) The level of system complexity and mobility management signalling shall be optimised to reduce infrastructure and operating costs. UE power consumption shall also be minimised accordingly.
+- e) For the Evolved Packet System the interruption time during handover of RT and NRT services shall be kept to minimum and shall not exceed the values defined in TR 25.913[4].
+
+# --- 9 Security and privacy
+
+## 9.1 General
+
+The Evolved Packet System shall provide a high level of security and privacy for users and Evolved Packet System operators.
+
+## 9.2 Security requirements
+
+The Evolved Packet System shall provide a high level of security, equivalent or better than Rel-7 3GPP systems.
+
+Any possible lapse in security in one access technology shall not compromise security of other accesses.
+
+The Evolved Packet System should provide protection against threats and attacks including those present in the Internet.
+
+The Evolved Packet System shall support information authenticity between the terminal and Evolved Packet Systems.
+
+The Evolved Packet System shall allow for a network to hide of internal network elements from the UE.
+
+Security policy shall be under the control of the home operator.
+
+The security solution should not interfere with service delivery or 3GPP inter-access handovers in a way that is noticeable to end-users or service providers.
+
+Appropriate traffic protection measures should be provided by the Evolved Packet System.
+
+The Evolved Packet System shall provide appropriate mechanisms to enable lawful intercept.
+
+The Evolved Packet System shall ensure that no unauthorized user can obtain a legitimate IP address that can be used to establish communication or enable malicious attacks on evolved system entities.
+
+Release 99 or later Releases' USIM application on the UICC is required to authenticate a user in an Evolved Packet System and hence allowing the user to get services in the Evolved Packet System according to her/his subscription.
+
+Note: The above requirement is applicable when providing access to the EPC via E-UTRAN.
+
+Once authenticated via a 3GPP or Evolved Packet System, the USIM shall not be required to re-authenticate upon changing between these systems, unless specifically requested by the operator (PLMN).
+
+NOTE: It may be possible to use other applications on the UICC in order to provide authentication on the 3GPP or Evolved Packet System (e.g. for connection to IMS). In addition, in case it is desirable to improve the level of security or to add new security mechanisms for accessing the Evolved Packet System compared to the one provided in Rel-7, a revised/upgraded application on the UICC may be required.
+
+## 9.3 Privacy requirements
+
+The Evolved Packet System shall provide several appropriate levels of user privacy including communication confidentiality, location privacy, and identity protection.
+
+The privacy of the contents, origin, and destination of a particular communication shall be protected from disclosure to unauthorised parties.
+
+The Evolved Packet System shall be able to hide the identities of users from unauthorised third parties.
+
+It shall be possible to provide no disclosure, at any level of granularity, of location, location-related information, e.g. geographic and routing information, or information from which a user's location can be determined, to unauthorised parties, including another party on a communication.
+
+# --- 10 Charging Aspects
+
+The Evolved Packet System shall support various charging models including all those supported by the 3GPP system contained within TS22.115 [5] .
+
+Charging models that shall be supported by the Evolved Packet System include (non-exhaustive list):
+
+- calling party pays
+- charging based on assured QoS
+- charging based on the transport
+- charging based on an event
+- charging based on content
+- charging adjustment (e.g. based on subscription bands)
+- alternate party charging
+
+The Evolved Packet System shall also be able to support introduction of new charging schemes including online and offline schemes, and charging schemes for the multi-access system environment
+
+Charging mechanisms of the Evolved Packet System shall provide (non-exhaustive list):
+
+- Cost effective Control and Charging of IP Flows
+- Perform online charging
+- Support differentiated charging including zero rating of the bearer and event charging
+- Awareness of subscriber identity, time-of-day, roaming status, QoS, Service input etc
+
+# --- Annex A (informative): Requirements for further study
+
+## A.1 Management of access networks
+
+The Evolved Packet System shall be able to allow for self-managing technologies (e.g. Plug-and-Play) for dynamically adding and removing non-3GPP defined access networks. Such self-managing technologies shall take into account the Evolved Packet System and access network policies.
+
+E.g. depending on such policies it shall be possible to for the 3GPP system operator to request encryption of user traffic that is transmitted over the access network.
+
+NOTE 1: The non-3GPP access network needs to have defined interworking with 3GPP.
+
+An example could be a WLAN (operated by some WLAN operator) that can, if needed, automatically be connected to a PLMN to serve as an I-WLAN access. This would enable the PLMN operator to provide additional access resources on a dynamic basis and to provide service to more customers (e.g. at mass events).
+
+NOTE 2: The degree of automation provided for network attachment is yet to be determined, but is intended to simplify (or completely automate) administration procedures.
+
+## A.2 Use cases for Fixed Mobile Convergence
+
+A family has purchased a family subscription plan that is independent of access (e.g. fixed or wireless) and location (e.g. both when at home and away from home). The subscription contains at least the following components:
+
+- Internet access: Operator specific service such as firewall and content filtering (parental control) independent of access for selected devices within the family. The service should be available at home, within the home mobile network and when roaming to a visited mobile network.
+- Voice/Multimedia: QoS and mobility between home WLAN and LTE wide area
+- Charging schemas connected to access type, preference and location
+- Video: Premium Video on Demand Service incl. guaranteed bandwidth and QoS regardless of access network.
+
+### Description
+
+### Use case 1: Internet access with Parental control and personal firewall
+
+The kids leave their house and take a bus to their grandparents' house.
+
+The operator specific services, like parental control and personal firewall, are invoked for specific users and terminals from both fixed network and from mobile network; this allows the kids to get the same service and filtering inside the home, in the bus going to grandparents and at the grandparents. In this use case the grandparents have a separate service provider than the family but the services will still be provided by the service provider where the family has a subscription.
+
+### Use case 2: Voice/Multimedia and Charging
+
+The father travels home after work while talking on the phone with his colleague.
+
+The ongoing Voice/Multimedia call between the father and his colleague is maintained while switching over between LTE Wide area and residential fixed broadband WLAN network. Once the call is switched over to WLAN charging for home-based access is applied. Bandwidth and QoS is maintained for the duration of the call to guarantee the same service delivery.
+
+### Use case 3: Video
+
+The kids in the backseat of the car are watching an Internet TV show on their laptop using LTE while driving home from the grandparent's house.
+
+The TV show is sent from an Internet TV provider. Once home the terminal detects indoor WLAN coverage where the subscriber has a WLAN Residential Gateway connected to his Fixed Broadband network. The user or the terminal automatically may select to switch the IP connection to the wireline broadband connection and enable the user to resume watching the same TV show on the same laptop, possibly with a better quality picture as allowed by the available bandwidth, user-specific policy, network policy and QoS setting.
+
+### **Use case 4: H(e)NB/Femtocell**
+
+A subscriber desires to improve coverage and access speed for their 3GPP device in their home. They purchase and install a small eNodeB (Femtocell AP) device for their home which attaches to the home LAN and establishes a connection back to the subscriber's mobile service provider network. The mobile network provider coordinates with the broadband access provider to deliver proper bandwidth and QoS to support a good QoE for calls and data sessions made within the home that access services from the mobile network. The Femtocell also allows some types of data traffic to be shared with the home LAN, including traffic for Internet applications. Local traffic can be discerned and accounted for differently than traffic that is carried on the mobile network.
+
+### **Use case 5: Application Mobility**
+
+A subscriber is in a multimedia call on their mobile device, and then wishes to change the device they are using to a fixed network attached device (e.g. Set Top Box / TV). The multimedia call is handed over from the mobile network to the fixed network after the subscriber chooses to transfer the multimedia call to a STB / TV. Bandwidth and QoS is maintained for the large screen experience to be meaningful. Accounting and settlement is supported among the application and network service providers, and reflects the changes to the access technology and required bandwidth.
+
+### **Use case 6: Common Quota**
+
+A Common Quota (CQ) can be assigned for both fixed and mobile accesses for a limited time period for a defined set of subscriptions. During each session the network elements monitor the CQ which may be consumed by one or more devices over either the wireless or fixed networks.
+
+When a defined percentage of the CQ and/or all the CQ has been consumed, one or more subscribers in the defined set can be notified of the event (e.g. via SMS and/or email).
+
+When the CQ has been consumed the access to the services is blocked.
+
+### **Use case 7: Video On Demand Service**
+
+Video On Demand (VoD) service is provided to the subscriber via the Set Top Box to the TV or to the PC. A user orders a VoD service interacting with the VoD infrastructure, which sends a resource request to the network. The user may also request mid-session requests triggering the increase/decrease of network resources. The requests will be accepted or rejected according to the available network resources.
+
+### **Use case 8: Broadband Access Wholesale**
+
+In Broadband network the wholesale scenario is quite important as it may be required by the regulation, known as unbundling (access, connectivity and services). For example the operator of the broadband access network lease/sell transport of the connection through its own network from the user to the buyer / leased network. So in the wholesale scenario the renting operator has the end-to-end Service responsibility to the customer and is viewed as the “Retailer” of the service or application. While the leasing network operator has the responsibility for the access network and for the connectivity.
+
+# Annex B (Normative): Evolved Packet System (EPS) applicable specifications
+
+The specifications listed in clause B.1 contain requirements applicable to the Evolved Packet System (EPS).
+
+## B.1 EPS Applicable Specifications
+
+| TS                                                                                                                                                                | Title                                                                                                       |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| 21.905                                                                                                                                                            | Vocabulary for 3GPP Specifications                                                                          |
+| 22.011                                                                                                                                                            | Service accessibility See note                                                                              |
+| 22.016                                                                                                                                                            | International Mobile Equipment Identities (IMEI)                                                            |
+| 22.022                                                                                                                                                            | Personalisation of Mobile Equipment (ME); Mobile functionality specification                                |
+| 22.030                                                                                                                                                            | Man-Machine Interface (MMI) of the User Equipment (UE)                                                      |
+| 22.038                                                                                                                                                            | USIM Application Toolkit (USAT/SAT); Service description; Stage 1                                           |
+| 22.041                                                                                                                                                            | Operator Determined Call Barring                                                                            |
+| 22.042                                                                                                                                                            | Network Identity and Time Zone (NITZ) service description; Stage 1                                          |
+| 22.066                                                                                                                                                            | Support of Mobile Number Portability (MNP); Stage 1                                                         |
+| 22.067                                                                                                                                                            | enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 1                                    |
+| 22.071                                                                                                                                                            | Location Services (LCS); Service description; Stage 1                                                       |
+| 22.078                                                                                                                                                            | Customised Applications for Mobile network Enhanced Logic (CAMEL)                                           |
+| 22.101                                                                                                                                                            | Service Principles                                                                                          |
+| 22.105                                                                                                                                                            | Services and Service Capabilities                                                                           |
+| 22.115                                                                                                                                                            | Charging and Billing                                                                                        |
+| 22.129                                                                                                                                                            | Handover requirements between UTRAN and GERAN or other radio systems                                        |
+| 22.146                                                                                                                                                            | Multimedia Broadcast/Multicast Service (MBMS); Stage 1                                                      |
+| 22.153                                                                                                                                                            | Multimedia priority service                                                                                 |
+| 22.173                                                                                                                                                            | IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 |
+| 22.174                                                                                                                                                            | Push service; Stage 1                                                                                       |
+| 22.182                                                                                                                                                            | Customized Alerting Tones (CAT) Requirements                                                                |
+| 22.226                                                                                                                                                            | Global text telephony (GTT); Stage 1: Service description                                                   |
+| 22.228                                                                                                                                                            | Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1        |
+| 22.233                                                                                                                                                            | Transparent end-to-end packet-switched streaming service; Stage 1                                           |
+| 22.234                                                                                                                                                            | Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking                              |
+| 22.240                                                                                                                                                            | Service requirements for 3GPP Generic User Profile (GUP); Stage 1                                           |
+| 22.242                                                                                                                                                            | Digital Rights Management (DRM); Stage 1                                                                    |
+| 22.246                                                                                                                                                            | Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1                                        |
+| 22.250                                                                                                                                                            | IP Multimedia Subsystem (IMS) Group Management; Stage 1                                                     |
+| 22.259                                                                                                                                                            | Service requirements for Personal Network Management (PNM); Stage 1                                         |
+| 22.279                                                                                                                                                            | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1                          |
+| 22.340                                                                                                                                                            | IP Multimedia Subsystem (IMS) messaging; Stage 1                                                            |
+| Note: In case the UE is connected to the PLMN via a non-3GPP access, then the PLMN (re)selection procedures specified for that access technology may be executed. |                                                                                                             |
+
+# --- Annex B1 (Informative): Void
+
+# Annex C (informative): Change history
+
+| Change history |           |           |        |      |     |       |     |                                                                                                                                                                                       |       |       |          |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                                                                                                                                       | Old   | New   | WI       |
+| SP-35          | SP-070128 | S1-070187 | 22.278 | 0001 | 2   | Rel-8 | F   | Clarification on QoS classes for evolved 3GPP system                                                                                                                                  | 8.0.0 | 8.1.0 | SAE-R    |
+| SP-35          | SP-070127 | S1-070197 | 22.278 | 0002 | -   | Rel-8 | B   | Provision of access network information to the UE                                                                                                                                     | 8.0.0 | 8.1.0 | SAE-R    |
+| SP-36          | SP-070365 | S1-070806 | 22.278 | 0003 | 3   | Rel-8 | B   | Requirement for handovers between LTE and 3GPP2 access networks                                                                                                                       | 8.1.0 | 8.2.0 | SAE-R    |
+| SP-36          | SP-070369 | S1-070556 | 22.278 | 0005 |     | Rel-8 | D   | Editorial correction for performance requirements for evolved 3GPP system                                                                                                             | 8.1.0 | 8.2.0 | SAE-R    |
+| SP-36          | SP-070367 | S1-070807 | 22.278 | 0006 | 1   | Rel-8 | B   | Performance requirements for evolved 3GPP system                                                                                                                                      | 8.1.0 | 8.2.0 | SAE-R    |
+| SP-36          | SP-070370 | S1-070764 | 22.278 | 0008 | 1   | Rel-8 | B   | Requirement for national roaming between LTE-only operators and 2G/3G-only operators                                                                                                  | 8.1.0 | 8.2.0 | SAE-R    |
+| SP-36          | SP-070483 | S1-070805 | 22.278 | 0009 | 5   | Rel-8 | B   | Requirements for service continuity between 3GPP system and WiMAX                                                                                                                     | 8.1.0 | 8.2.0 | SAE-R    |
+| SP-37          | SP-070566 | S1-071324 | 22.278 | 10   | 2   | Rel-8 | D   | Addition of 3GPP reference for the evolved 3GPP packet system (EPS)                                                                                                                   | 8.2.0 | 8.3.0 | SAE-R    |
+| SP-37          | SP-070566 | S1-071096 | 22.278 | 11   | 1   | Rel-8 | B   | Multiple IP session                                                                                                                                                                   | 8.2.0 | 8.3.0 | SAE-R    |
+| SP-37          | SP-070566 | S1-071097 | 22.278 | 12   | 1   | Rel-8 | B   | Voice service continuity between 3GPP RAT and non 3GPP RAT                                                                                                                            | 8.2.0 | 8.3.0 | SAE-R    |
+| SP-37          | SP-070566 | S1-070994 | 22.278 | 13   | 1   | Rel-8 | B   | Alignment of terminology with SA2                                                                                                                                                     | 8.2.0 | 8.3.0 | SAE-R    |
+| SP-37          | SP-070566 | S1-071122 | 22.278 | 14   | 1   | Rel-8 | B   | Access network discovery                                                                                                                                                              | 8.2.0 | 8.3.0 | SAE-R    |
+| SP-38          | SP-070855 | S1-071856 | 22.278 | 0021 | 2   | Rel-8 | C   | Support for efficient delivery of text-based broadcast messages                                                                                                                       | 8.3.0 | 8.4.0 | AIPN-SAE |
+| SP-38          | SP-070855 | S1-071912 | 22.278 | 0022 | 1   | Rel-8 | B   | Emergency Call Support                                                                                                                                                                | 8.3.0 | 8.4.0 | AIPN-SAE |
+| SP-38          | SP-070856 | S1-071913 | 22.278 | 0015 | 3   | Rel-8 | B   | Enhancements to Access network discovery and steering of access                                                                                                                       | 8.3.0 | 8.4.0 | AIPN-SAE |
+| SP-38          | SP-070856 | S1-071915 | 22.278 | 0017 | 1   | Rel-8 | F   | Multi-access MBMS                                                                                                                                                                     | 8.3.0 | 8.4.0 | SAE-R    |
+| SP-38          | SP-070856 | S1-071916 | 22.278 | 0018 | 1   | Rel-8 | B   | QoS change requirement clarification                                                                                                                                                  | 8.3.0 | 8.4.0 | SAE-R    |
+| SP-38          | SP-070929 | -         | 22.278 | 0024 | 2   | Rel-8 | C   | Addition of list of applicable specifications for the EPS and amended scope                                                                                                           | 8.3.0 | 8.4.0 | AIPN-SAE |
+| SP-40          | SP-080306 | S1-080740 | 22.278 | 0028 | 2   | Rel-8 | F   | Clarification of EPS access using pre-Rel-8 USIMs                                                                                                                                     | 8.4.0 | 9.0.0 | AIPN-SAE |
+| SP-40          | SP-080306 | S1-080720 | 22.278 | 0030 | 1   | Rel-8 | F   | WiMAX Forum specification reference in TS 22.278                                                                                                                                      | 8.4.0 | 9.0.0 | AIPN-SAE |
+| SP-40          | -         |           |        |      |     |       |     | Creation of v.9.0.0. Content identical to 8.4.0 + CRs 28r2 and 30r1 (but not including CR 27r1, applicable to Rel-8 only, to remove Features which Stage 3 was not completed on time) | 8.4.0 | 9.0.0 | -        |
+| SP-41          | SP-080495 | S1-082018 | 22.278 | 0037 | -   | Rel-9 | A   | Service continuity (mirror to a Rel-8 CR)                                                                                                                                             | 9.0.0 | 9.1.0 | AIPN-SAE |
+| SP-41          | SP-080639 | -         | 22.278 | 0039 | 3   | Rel-9 | A   | Access Network Discovery and Steering of Access                                                                                                                                       | 9.0.0 | 9.1.0 | AIPN-SAE |
+| SP-41          | SP-080495 | S1-082398 | 22.278 | 0041 | 2   | Rel-9 | A   | Update IP session control and local breakout requirements                                                                                                                             | 9.0.0 | 9.1.0 | AIPN-SAE |
+| SP-41          | SP-080495 | S1-082386 | 22.278 | 0043 | 3   | Rel-9 | A   | <i>Requirement on support of CS Fallback</i>                                                                                                                                          | 9.0.0 | 9.1.0 | AIPN-SAE |
+| SP-41          | SP-080652 | -         | 22.278 | 0043 | 5   | Rel-9 | A   | De-implementation of CR43r3 and implementation of 43r5, as approved during SA#41                                                                                                      | 9.1.0 | 9.1.1 | AIPN-SAE |
+| SP-42          | SP-080774 | S1-083114 | 22.278 | 0045 | -   | Rel-9 | A   | Deletion of redundant reference                                                                                                                                                       | 9.1.1 | 9.2.0 | AIPN-SAE |
+| SP-42          | SP-080783 | S1-083465 | 22.278 | 0049 | 2   | Rel-9 | B   | Terminal Identification of 3GPP and 3GPP2 devices                                                                                                                                     | 9.1.1 | 9.2.0 | TEI9     |
+| SP-42          | SP-080778 | S1-084334 | 22.278 | 0051 | 1   | Rel-9 | B   | Support for Multimedia Priority Service in EPS                                                                                                                                        | 9.1.1 | 9.2.0 | AIPN-SAE |
+
+|       |           |              |        |      |   |        |   |                                                                                             |        |        |          |
+|-------|-----------|--------------|--------|------|---|--------|---|---------------------------------------------------------------------------------------------|--------|--------|----------|
+| SP-42 | SP-080783 | S1-084368    | 22.278 | 0054 | 1 | Rel-9  | C | EPS operational deployment and mobility optimization                                        | 9.1.1  | 9.2.0  | TEI9     |
+| SP-42 | SP-080783 | S1-084069    | 22.278 | 0055 | - | Rel-9  | B | Removal of chapter 6.1.2 and 6.1.3                                                          | 9.1.1  | 9.2.0  | TEI9     |
+| SP-42 | SP-080783 | S1-084425    | 22.278 | 0056 | 3 | Rel-9  | D | Enhanced ANDSF Requirements                                                                 | 9.1.1  | 9.2.0  | TEI9     |
+| SP-42 | SP-080783 | S1-084414    | 22.278 | 0057 | 1 | Rel-9  | C | Basic support for multiaccess                                                               | 9.1.1  | 9.2.0  | TEI9     |
+| SP-42 | SP-080783 | S1-084363    | 22.278 | 0058 | 1 | Rel-9  | B | Adding an appendix with FMC uses cases to 22.278                                            | 9.1.1  | 9.2.0  | TEI9     |
+| SP-44 | SP-090417 | S1-091153rev | 22.278 | 0062 | 2 | Rel-9  | A | Access Technology Selection across PLMNs                                                    | 9.2.0  | 9.3.0  | SAES     |
+| SP-44 | SP-090371 | S1-091169    | 22.278 | 0066 | - | Rel-9  | A | Move sentence about non-3GPP access                                                         | 9.2.0  | 9.3.0  | SAES     |
+| SP-44 | SP-090371 | S1-091352    | 22.278 | 0067 | - | Rel-9  | A | Frequency of Scanning for Different Access Technologies                                     | 9.2.0  | 9.3.0  | SAES     |
+| SP-45 | SP-090476 | S1-093272    | 22.278 | 0060 | 4 | Rel-9  | A | Alignment about accepting/rejecting CSFB                                                    | 9.3.0  | 9.4.0  | AIPN-SAE |
+| SP-46 | SP-090843 | S1-094500    | 22.278 | 0070 | 2 | Rel-9  | F | One active policy ruleset in ANDSF                                                          | 9.4.0  | 9.5.0  | eANDSF   |
+| SP-46 | SP-090904 | -            | 22.278 | 0071 | 7 | Rel-10 | B | Adding of IFOM Requirements                                                                 | 9.5.0  | 10.0.0 | IFOM     |
+| SP-47 | SP-100185 | S1-100236    | 22.278 | 0080 | 5 | Rel-10 | B | Requirements for Fixed Mobile Interworking                                                  | 10.0.0 | 10.1.0 | BBAI     |
+| SP-49 | SP-100575 | S1-102056    | 22.278 | 0089 | - | Rel-10 | A | Removal of references to 3GPP OSA                                                           | 10.1.0 | 10.2.0 | TEI10    |
+| SP-49 | SP-100582 | S1-102032    | 22.278 | 0083 | - | Rel-11 | B | Adding a H(e)NB use case to FMC use cases                                                   | 10.1.0 | 11.0.0 | BBAI     |
+| SP-49 | SP-100582 | S1-102303    | 22.278 | 0084 | 1 | Rel-11 | B | Adding a Application Mobility use case to FMC use cases                                     | 10.1.0 | 11.0.0 | BBAI     |
+| SP-49 | SP-100582 | S1-102307    | 22.278 | 0086 | 1 | Rel-11 | D | Clarifications on FMC use cases                                                             | 10.1.0 | 11.0.0 | BBAI     |
+| SP-49 | SP-100582 | S1-102308    | 22.278 | 0085 | 2 | Rel-11 | B | Adding a Common Quota use case to FMC use cases                                             | 10.1.0 | 11.0.0 | BBAI     |
+| SP-49 | SP-100582 | S1-102309    | 22.278 | 0087 | 2 | Rel-11 | B | New Requirements for Fixed Mobile Convergence scenario                                      | 10.1.0 | 11.0.0 | BBAI     |
+| SP-50 | SP-100802 | S1-103263    | 22.278 | 0090 | 1 | Rel-11 | F | Clarifying the scenarios supported by FMC interworking, including building block II         | 11.0.0 | 11.1.0 | BBAI     |
+| SP-50 | SP-100802 | S1-103266    | 22.278 | 0091 | 2 | Rel-11 | B | New Requirements for Enterprise Interworking scenario                                       | 11.0.0 | 11.1.0 | BBAI     |
+| SP-50 | SP-100802 | S1-103242    | 22.278 | 0093 | 3 | Rel-11 | B | 3GPP EPC based FMC                                                                          | 11.0.0 | 11.1.0 | BBAI     |
+| SP-50 | SP-100802 | S1-103321    | 22.278 | 0095 | 1 | Rel-11 | B | Use cases for BBAI Building Block 3 - Converged scenario                                    | 11.0.0 | 11.1.0 | BBAI     |
+| SP-50 | SP-100802 | S1-103323    | 22.278 | 0097 | - | Rel-11 | B | Evolved Packet Core support for fixed access                                                | 11.0.0 | 11.1.0 | BBAI     |
+| -     |           |              |        |      |   |        |   | LTE logo changed into LTE Advanced logo                                                     | 11.1.0 | 11.1.1 | -        |
+| SP-51 | SP-110165 | S1-110297    | 22.278 | 0094 | 2 | Rel-11 | B | Scenarios for Interworking between Mobile Operators and Application Providers               | 11.1.0 | 11.2.0 | MOSAP    |
+| SP-51 | SP-110165 | S1-110404    | 22.278 | 0098 | 3 | Rel-11 | B | New requirements for MOSAP                                                                  | 11.1.0 | 11.2.0 | MOSAP    |
+| SP-51 | SP-110165 | S1-110302    | 22.278 | 0100 | 2 | Rel-11 | B | Use cases for MOSAP                                                                         | 11.1.0 | 11.2.0 | MOSAP    |
+| SP-51 | SP-110169 | S1-110181    | 22.278 | 0099 | 2 | Rel-11 | B | Fixed Broadband Access Network Requirements for BBAI Building Block 3 - Convergent scenario | 11.1.0 | 11.2.0 | BBAI     |
+| SP-52 | SP-110372 | S1-111223    | 22.278 | 0101 | 2 | Rel-11 | B | User consent-based charging use case for MOSAP                                              | 11.2.0 | 11.3.0 | MOSAP    |
+| SP-52 | SP-110372 | S1-111412    | 22.278 | 0103 | 2 | Rel-11 | B | Non-collaboration requirements for MOSAP                                                    | 11.2.0 | 11.3.0 | MOSAP    |
+| SP-53 | SP-110575 | S1-112357    | 22.278 | 0110 | 3 | Rel-11 | F | MOSAP - Roaming LBO Architecture Correction                                                 | 11.3.0 | 11.4.0 | MOSAP    |
+| SP-56 | SP-120294 | S1-121328    | 22.278 | 0115 | 2 | Rel-11 | F | Removal of MOSAP requirements from Rel-11 Specs                                             | 11.4.0 | 11.5.0 | MOSAP    |
+| SP-57 | SP-120525 | S1-122052    | 22.278 | 0117 | - | Rel-11 | B | Removal of BB III - Fixed Mobile Convergence requirements from Rel-11                       | 11.5.0 | 11.6.0 | BBAI     |

marked/Rel-11/22_series/22279/raw.md

@@ -0,0 +1,438 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                          |    |
+|------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                           | 6  |
+| 1 Scope.....                                                                             | 7  |
+| 2 References.....                                                                        | 7  |
+| 3 Definitions, symbols and abbreviations .....                                           | 7  |
+| 3.1 Definitions.....                                                                     | 7  |
+| 3.2 Abbreviations .....                                                                  | 8  |
+| 4 Introduction to Combinational Service .....                                            | 8  |
+| 5 General requirements .....                                                             | 8  |
+| 6 User experience of combinational services.....                                         | 9  |
+| 7 Service Capability Detection .....                                                     | 9  |
+| 7.1 General .....                                                                        | 9  |
+| 7.2 User privacy .....                                                                   | 9  |
+| 8 IMS service behaviour during a Combinational Service .....                             | 10 |
+| 9 Interaction with supplementary services.....                                           | 10 |
+| 9.1 Line Identification .....                                                            | 10 |
+| 9.1.1 Calling Line Identity Presentation (CLIP) .....                                    | 10 |
+| 9.1.2 Calling Line Identity Restriction (CLIR) .....                                     | 10 |
+| 9.1.3 Connected Line Identification Presentation (COLP).....                             | 11 |
+| 9.1.4 Connected Line Identification Restriction (COLR) .....                             | 11 |
+| 9.2 Name Identification.....                                                             | 11 |
+| 9.2.1 Calling Name Presentation (CNAP).....                                              | 11 |
+| 9.3 Call Forwarding.....                                                                 | 11 |
+| 9.3.1 Call Forwarding Unconditional (CFU) .....                                          | 11 |
+| 9.3.2 Call Forwarding on Busy (CFB) .....                                                | 11 |
+| 9.3.3 Call Forwarding on No Reply (CFNRY) .....                                          | 11 |
+| 9.3.4 Call Forwarding on Not Reachable (CFNRC) .....                                     | 11 |
+| 9.3.5 Call Deflection (CD) .....                                                         | 11 |
+| 9.4 Call Offering .....                                                                  | 12 |
+| 9.4.1 Explicit Call Transfer (ECT).....                                                  | 12 |
+| 9.5 Call Completion .....                                                                | 12 |
+| 9.5.1 Call Waiting (CW) .....                                                            | 12 |
+| 9.5.2 Call Hold (CH) .....                                                               | 12 |
+| 9.5.3 Call Completion to Busy Subscriber (CCBS) .....                                    | 12 |
+| 9.5.4 Multi Call (MC).....                                                               | 12 |
+| 9.6 Multi Party.....                                                                     | 12 |
+| 9.6.1 Multi Party call (MPTY) .....                                                      | 12 |
+| 9.7 Community of Interest .....                                                          | 12 |
+| 9.7.1 Closed User Group (CUG) .....                                                      | 12 |
+| 9.8 Charging.....                                                                        | 13 |
+| 9.8.1 Advice of Charge - Information (AOCI) .....                                        | 13 |
+| 9.8.2 Advice of charge – Charge (AOCC) .....                                             | 13 |
+| 9.9 Additional Info Transfer.....                                                        | 13 |
+| 9.9.1 User-to-User Signalling service 1 (UUS1).....                                      | 13 |
+| 9.9.2 User-to-User Signalling service 2 (UUS2).....                                      | 13 |
+| 9.9.3 User-to-User Signalling service 3 (UUS3).....                                      | 13 |
+| 9.10 Call Barring.....                                                                   | 13 |
+| 9.10.1 Barring of All Outgoing Calls (BAOC) .....                                        | 13 |
+| 9.10.2 Barring of Outgoing International Calls (BOIC).....                               | 13 |
+| 9.10.3 Barring of Outgoing International Calls except to HPLMN country (BOIC-exHc) ..... | 13 |
+| 9.10.4 Barring of All Incoming Calls (BAIC).....                                         | 13 |
+| 9.10.5 Barring of All Incoming Calls when roaming outside HPLMN country (BICROAM).....   | 13 |
+| 9.11 Call Priority .....                                                                 | 14 |
+| 9.11.1 Enhanced Multi Level Pre-emption (EMLPP).....                                     | 14 |
+
+10 Impacts on other services..... 14  
+10.1 Support of Teleservices during a combinational service ..... 14  
+10.2 Support of Location Services during a combinational service..... 14  
+11 Charging aspects for Combinational Service..... 14  
+12 Provisioning ..... 14  
+Annex A (informative): Change history..... 15
+
+# --- 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 specifies service requirements for Combining CS and IMS services using a CS speech or CS multimedia call in association with an IMS session. The IMS session may consist of one or more IMS services.
+
+Requirements for the following capabilities are included:
+
+- Radio capability exchange.
+- Terminal capability exchange.
+- E.164 number exchange.
+- Adding IMS session to an ongoing CS call.
+- Adding a CS call to an ongoing IMS session.
+- Supplementary services as they relate to CSICS.
+
+It is intended that the capabilities defined herein for CSICS shall support interoperability between different operator networks, and roaming.
+
+# --- 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 22.979: "Feasibility study on Combined CS Calls and IMS Sessions".
+- [3] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem".
+- [4] 3GPP TS 22.004: "General on Supplementary Services".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Combinational Service:** A combinational service is created by adding one or more IMS session(s) to a CS call (or vice versa). The CS call and IMS session are established between the same participants.
+
+**Combinational call:** this is the name given to the service in which a circuit switched speech teleservice is enriched by adding an IMS session where both services (IMS session and CS call) are originated in one single UE and are terminated in another single UE.
+
+**Combinational Session:** this is the name given to the service in which an ongoing IMS session between two users is enriched by adding a circuit switched based call. The individual service instances that form the combinational session are originated in a single UE and terminated in another single UE.
+
+**CSICS capable UE:** UE that supports Combinational Service.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply. Additional applicable abbreviations can be found in TR 21.905 [1].
+
+|       |                                            |
+|-------|--------------------------------------------|
+| CSICS | Circuit Switched IMS Combinational Service |
+|-------|--------------------------------------------|
+
+---
+
+# 4 Introduction to Combinational Service
+
+Combinational services are applicable to both UTRAN and GERAN and enables the unidirectional or bi-directional exchange of PS data within the context of an IMS session
+
+A specific subscription for combinational services is not necessary. However, both users A and B shall as a minimum be provisioned with CS telephony (TS11) as well as for accessing the IMS.
+
+The existing address context is reused when the combined service is established, which makes the combined service simple to invoke for the user.
+
+---
+
+# 5 General requirements
+
+In addition to the existing IMS requirements [3], the following general requirements apply for CSICS:
+
+It shall be possible to establish a combinational service between two users within the same PLMN or within different PLMNs.
+
+It shall be possible to establish a combinational service between two users camped on identical or different RATs.
+
+It shall be possible to establish a combinational service when roaming, assuming the visited operator supports GPRS roaming.
+
+The user (A or B party) shall only need to know one address in order to establish the combinational service.
+
+It shall be possible to add an IMS session to a CS speech call, thereby creating a combinational call.
+
+It shall be possible to add a CS speech call to an IMS session, thereby creating a combinational session.
+
+It shall be possible to add an IMS session to a CS Multimedia call, thereby creating a combinational call.
+
+It shall be possible to add a CS Multimedia call to an IMS session, thereby creating a combinational session.
+
+The following two service modes will exist in regards to IMS registration depending on different UE implementations:
+
+- 1) IMS pre established state: the CSICS capable UE performs the IMS registration at switch on.
+- 2) IMS on demand state: the CSICS capable UE performs the IMS registration:
+  - to start the communication, or
+  - to add a IMS session to an existing CS call.
+
+Interoperability between UEs that implement such different approaches shall be enabled.
+
+During a CS call it shall be possible to request establishment of the IMS session whether the invited UE is IMS registered or not. The invited user shall be able to accept or reject the IMS registration request.
+
+A combinational service shall enable both unidirectional and bi-directional exchange of PS data within the context of the IMS session.
+
+---
+
+# 6 User experience of combinational services
+
+When one of the participating users terminates the CS call of a combinational service, the IMS session may continue.
+
+When one of the participating users terminates the IMS session of a combinational service, the CS call may continue.
+
+When the user A sends media to a user B, the user B can accept or reject the media (confirmation from the receiving party is needed) and vice versa.
+
+If media, or parts thereof, accepted by a user cannot be rendered by the UE simultaneously with the CS call, conflicts shall be resolved such that the user is presented with:
+
+- CS speech with preference over IMS speech/audio;
+- IMS video and images with preference over CS video.
+
+It shall be possible to initiate a combinational service with user perceived simultaneous setup of IMS session and CS call. The CS call and IMS session can be established sequentially and on the failure of any of the setups the user may be prompted to decide whether to continue. The terminating user shall be able to accept or reject CS call or IMS session independently.
+
+# --- 7 Service Capability Detection
+
+## 7.1 General
+
+The Service Capability Detection may indicate to the user that the UEs have interoperable CSICS capability and that the access network(s) have the necessary network functionality to carry the combinational service.
+
+The detection of the capabilities of the recipient terminal and the operators' networks shall ensure that information is updated in case of change of terminal.
+
+An operator should have the mechanism to inhibit the capability check, or at least indicate to UE that it should not be performed.
+
+Note: An operator may want to inhibit the capability check for CSICS in order to optimise the usage of radio resources.
+
+It shall be possible for the (CSICS capable) UEs to have the information, prior to initiating a combinational service, regarding the type of capabilities, which are jointly supported by both UEs, without user intervention.
+
+Due to the handover of the participating users to an access network which does not support combinational services, service capability detection may be needed during a CS call to notify the user of the service availability.
+
+## 7.2 User privacy
+
+Participants in a CS call or IMS session may choose not to reveal their identity, even though this may prevent the establishment of a combinational session.
+
+During the service capability detection and exchange of information process, the user's privacy settings shall be respected. The applicable privacy settings are as described in clauses 8 and 9. Additionally, the user shall be able to restrict the information exchanged by the service capability detection application and the user's consent should be requested prior to the exchange of information.
+
+NOTE: The terminal is not normally aware of existing Calling Line Identity Restriction / Connected Line Restriction settings in the network, hence the need for the user to be able to configure the service capability detection application not to reveal such information.
+
+# --- 8 IMS service behaviour during a Combinational Service
+
+There is no standardised supplementary service defined for IMS session, however mechanisms exist (service capabilities) to emulate the behaviour of some of the most common supplementary services that exist in the circuit switched domain. The intention in this clause is NOT to define "supplementary services" for IMS, just to explain the service behaviour during a combinational session for some specific cases as indicated below:
+
+- **IMS session hold:** In an ongoing combinational service, the user may decide to suspend the IMS session. When this service is invoked the user should be able to decide whether the CS call of the combinational service should also be put on hold.
+- **IMS session waiting:** In an ongoing combinational service, the user should be able to receive an alert of an incoming IMS session towards his UE. Subject to the capability of the UE, the user should be provided with the option to switch between the ongoing session and the new incoming one, or accept the new one in parallel with the existing one. The CS call of the combinational service should continue during the alerting of the subscriber and the user may decide to put the CS call on hold when switching to the new IMS session.
+- **IMS session redirect:** It should be possible to add CS call to a redirected IMS session, subject to the capability of the recipient UE.
+- **Identity presentation:** Existing Session Originator Identity Presentation rules apply to IMS session.
+- **Identity restriction:** Existing Session Originator Identity Presentation Suppression rules apply to IMS session, even if this results in the called party being unable to establish a combinational session.
+
+# --- 9 Interaction with supplementary services
+
+The current section lists the supplementary services as specified in 3GPP TS 22.004 [4].
+
+## 9.1 Line Identification
+
+### 9.1.1 Calling Line Identity Presentation (CLIP)
+
+When CLIP is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+If the called party does not subscribe to CLIP or the CLI is not available, then the called party's UE may treat an incoming IMS session as an independent IMS session and the called party may establish an independent IMS session with the calling party.
+
+### 9.1.2 Calling Line Identity Restriction (CLIR)
+
+Existing CLIR rules apply, even if this results in the called party being unable to establish a combinational call.
+
+If a calling party uses CLIR when establishing a CS call, either by subscription or per call basis, and the called party does not have CLIR override, then the called party's UE may treat an incoming IMS session as an independent IMS session and the called party may establish an independent IMS session with the calling party.
+
+If the CLI of the calling party is restricted as a result of CLIR, then the calling party's UE or the network shall ensure that the Public User Identity of the calling party is also restricted when establishing an outgoing IMS session associated with this CS call and when responding to an incoming IMS session associated with this CS call.
+
+### 9.1.3 Connected Line Identification Presentation (COLP)
+
+When COLP is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+If the calling party does not subscribe to COLP or the COL is not available, then the calling party's UE may use the called party number of the CS call, as provided by the UE to the network, to correlate an incoming IMS session with the CS call and to establish an IMS session associated with the CS call.
+
+### 9.1.4 Connected Line Identification Restriction (COLR)
+
+Existing COLR rules apply, even if this results in the calling party being unable to establish a combinational call.
+
+If the called party subscribes to COLR and the calling party does not have COLR override, then the calling party's UE may use the called party number of the CS call, as provided by the UE to the network, to correlate an incoming IMS session with the CS call and to establish an IMS session associated with the CS call.
+
+If the COL of the called party is restricted as a result of COLR, then the called party's UE or the network shall ensure that the Public User Identity of the called party is also restricted when establishing an outgoing IMS session associated with this CS call and when responding to an incoming IMS session associated with this CS call.
+
+## 9.2 Name Identification
+
+### 9.2.1 Calling Name Presentation (CNAP)
+
+When CNAP is used in conjunction with a combinational service, it shall function as specified for CS calls.
+
+## 9.3 Call Forwarding
+
+### 9.3.1 Call Forwarding Unconditional (CFU)
+
+Call forwarding unconditional shall not prevent the calling party or the called party from adding an IMS session to the CS call. Refer to the clause on Line Identification for the usage of the CLI and COL for establishing an IMS session associated with the CS call and for correlating an incoming IMS session with the CS call.
+
+### 9.3.2 Call Forwarding on Busy (CFB)
+
+Refer to CFU.
+
+### 9.3.3 Call Forwarding on No Reply (CFNRY)
+
+Refer to CFU.
+
+### 9.3.4 Call Forwarding on Not Reachable (CFNRC)
+
+Refer to CFU.
+
+### 9.3.5 Call Deflection (CD)
+
+Refer to CFU.
+
+## 9.4 Call Offering
+
+### 9.4.1 Explicit Call Transfer (ECT)
+
+At the moment that the subscriber invokes ECT, she may have an IMS session ongoing with either or both of the CS call parties. The user may keep or terminate these IMS sessions when ECT is invoked. The two CS call parties that are in speech connection after the invocation of ECT, have not exchanged Radio Network and Terminal capabilities with one another. Neither are these two call parties aware of one another's Line Identification. These parties are therefore not capable of initiating IMS sessions, associated with the CS call.
+
+## 9.5 Call Completion
+
+### 9.5.1 Call Waiting (CW)
+
+When a second CS call arrives during an ongoing combinational call, the IMS session of the ongoing combinational call shall not be affected. When the user decides to place the ongoing CS call on hold and accept the second CS call, then the rules as specified for Call Hold apply for the ongoing CS call that is placed on hold. When the incoming, waiting CS call is accepted, the calling party's UE and called party's UE may exchange terminal capability and radio network capability. An IMS session may be established associated with the second CS call, when that CS call is accepted. The IMS session(s) for the second CS call may run concurrently with the IMS session(s) for the CS call that is on hold.
+
+### 9.5.2 Call Hold (CH)
+
+When a user places a CS call on hold, the user may decide to suspend an IMS session associated with that CS call, or to terminate the IMS session. When a held CS call is resumed, an associated IMS session that was suspended when that
+
+CS call was placed on hold, may be resumed. The user may decide whether new IMS sessions may be created for a CS call when that CS call is currently in the held state.
+
+For the second CS call that may be established or accepted when a first CS call is placed on hold, the calling party's UE and called party's UE may exchange terminal capability and radio network capability. An IMS session may be established associated with the second CS call, when that second call is active.
+
+### 9.5.3 Call Completion to Busy Subscriber (CCBS)
+
+Not part of the scope of the present specification.
+
+### 9.5.4 Multi Call (MC)
+
+Not part of the scope of the present specification.
+
+## 9.6 Multi Party
+
+### 9.6.1 Multi Party call (MPTY)
+
+Not part of the scope of the present specification.
+
+## 9.7 Community of Interest
+
+### 9.7.1 Closed User Group (CUG)
+
+No impact. When the establishment of an outgoing CS call or the acceptance of a CS incoming call is barred due to CUG, that shall not affect the calling or called party's ability to establish IMS sessions with the other party. However, these IMS sessions will not be considered "combinational".
+
+## 9.8 Charging
+
+### 9.8.1 Advice of Charge - Information (AOCI)
+
+When AOCI is used in conjunction with a combinational service, it shall function as specified for CS calls and packet data service.
+
+### 9.8.2 Advice of charge – Charge (AOCC)
+
+Refer to AOCI.
+
+## 9.9 Additional Info Transfer
+
+### 9.9.1 User-to-User Signalling service 1 (UUS1)
+
+When UUS1 is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+### 9.9.2 User-to-User Signalling service 2 (UUS2)
+
+When UUS2 is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+### 9.9.3 User-to-User Signalling service 3 (UUS3)
+
+When UUS3 is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+## 9.10 Call Barring
+
+### 9.10.1 Barring of All Outgoing Calls (BAOC)
+
+When the establishment of an outgoing CS call is barred due to BAOC, that shall not affect the calling party's ability to establish IMS sessions with the other party. However, these IMS sessions will not be considered "combinational".
+
+### 9.10.2 Barring of Outgoing International Calls (BOIC)
+
+Refer to BAOC.
+
+### 9.10.3 Barring of Outgoing International Calls except to HPLMN country (BOIC-exHC)
+
+Refer to BAOC.
+
+### 9.10.4 Barring of All Incoming Calls (BAIC)
+
+When the acceptance of an incoming CS call is barred due to BAIC, that shall not affect the called party's ability to establish IMS sessions with the other party. However, these IMS sessions will not be considered "combinational".
+
+### 9.10.5 Barring of All Incoming Calls when roaming outside HPLMN country (BICROAM)
+
+Refer to BAIC.
+
+## 9.11 Call Priority
+
+### 9.11.1 Enhanced Multi Level Precedence Pre-emption (EMLPP)
+
+When a CS call cannot be established due to a lower precedence this shall not affect the user's ability to establish IMS sessions to another party. However, these IMS sessions will not be considered "combinational".
+
+It shall be possible to pre-empt a CS call which is part of a combinational service.
+
+It shall be possible to add a precedence call to an IMS session.
+
+# --- 10 Impacts on other services
+
+## 10.1 Support of Teleservices during a combinational service
+
+It should be possible to send and receive an SMS while engaged in a combinational service.
+
+## 10.2 Support of Location Services during a combinational service
+
+It shall be possible to locate a user engaged in a combinational service.
+
+# --- 11 Charging aspects for Combinational Service
+
+For combinational services, it must be possible to charge as follows:
+
+It shall be possible to provide charging information on the CS call and IMS session for correlation purposes in order to allow off-line charging.
+
+The charging information shall continue to be produced for any remaining multimedia components or the CS call when a multimedia component or the CS call drops during the communication between the two parties.
+
+Note: The below requirement will presumably not be feasible within Rel-7 timeframe, but may be considered in Rel-8.
+
+The home operator should be able to correlate charged media components and CS call in order to introduce dedicated charging schemes, e.g. discounts. This applies to on-line charging as well as off-line charging.
+
+---
+
+# 12 Provisioning
+
+The combinational service should not place additional provisioning requirement on the operator.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |      |     |       |     |                                                                                               |        |        |       |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|-----------------------------------------------------------------------------------------------|--------|--------|-------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                                               | Old    | New    | WI    |
+| 2005-01        |           |           |        |      |     |       |     | First Draft                                                                                   |        | 0.0.0  |       |
+| 2005-04        |           |           |        |      |     |       |     | Output from SA1 #28 Beijing                                                                   | 0.0.0  | 1.0.0  |       |
+| 2005-07        |           |           |        |      |     |       |     | Output from SA1 #29 SWG in Povo de Varzim                                                     | 1.0.0  | 1.1.0  |       |
+| 2005-07        |           |           |        |      |     |       |     | Output from SA #29 plenary                                                                    | 1.1.0  | 2.0.0  |       |
+| SP-29          | SP-050517 |           |        |      |     |       |     | Approved at SA #29                                                                            | 2.0.0  | 7.0.0  |       |
+| SP-30          | SP-050745 | S1-051125 | 22.279 | 0001 | -   | Rel-7 | F   | UE behaviour for simultaneous rendering of CS call and IMS media _ (Action A29-07 from SA#29) | 7.0.0  | 7.1.0  | CSICS |
+| SP-30          | SP-050745 | S1-051148 | 22.279 | 0002 | -   | Rel-7 | F   | CR to TS22.279 for correction of the term                                                     | 7.0.0  | 7.1.0  | CSICS |
+| SP-30          | SP-050745 | S1-051152 | 22.279 | 0003 | -   | Rel-7 | F   | Clarification of supplementary services requirements for CSICS                                | 7.0.0  | 7.1.0  | CSICS |
+| SP-42          | -         | -         |        |      |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                                                   | 7.0.0  | 8.0.0  |       |
+| SP-46          | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-9 by MCC                                                                       | 8.0.0  | 9.0.0  |       |
+| 2011-03        | -         | -         | -      | -    | -   | -     | -   | Update to Rel-10 version (MCC)                                                                | 9.0.0  | 10.0.0 |       |
+| 2012-09        | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-11 by MCC                                                                      | 10.0.0 | 11.0.0 |       |