Add files using upload-large-folder tool

marked/Rel-13/22_series/22001/raw.md

@@ -0,0 +1,868 @@
+
+
+# 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; ~~3GPP TS 22.001 V13.0.0 (2016-01)~~ ~~Principles of circuit telecommunication services supported~~ *Technical Specification* **by a Public Land Mobile Network (PLMN)** **(Release 13)**
+
+![3GPP logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+---
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font with a red signal icon below the 'G'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, service
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                       |    |
+|-------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                        | 5  |
+| 0 Scope.....                                                                                          | 6  |
+| 0.1 References .....                                                                                  | 6  |
+| 0.2 Abbreviations .....                                                                               | 6  |
+| 1 Framework for the description of telecommunication services .....                                   | 7  |
+| 1.1 The attribute method of characterization of circuit telecommunication services .....              | 7  |
+| 2 Description of circuit telecommunication services by the attribute method.....                      | 7  |
+| 2.1 General .....                                                                                     | 7  |
+| 2.2 Categorisation of telecommunication services.....                                                 | 7  |
+| 3 Characterization of circuit telecommunication services .....                                        | 7  |
+| 3.1 General .....                                                                                     | 7  |
+| 3.2 Bearer services .....                                                                             | 8  |
+| 3.3 Teleservices.....                                                                                 | 8  |
+| 4 Provision of telecommunication services .....                                                       | 8  |
+| 4.1 Subscription checking for Basic Services.....                                                     | 9  |
+| 4.2 Subscription checking for Supplementary Services.....                                             | 10 |
+| <b>Annex A (normative): List of definition of attributes and values used for bearer services...11</b> |    |
+| A.1 Information transfer attributes .....                                                             | 11 |
+| A.1.1 Information transfer capability .....                                                           | 11 |
+| A.1.2 Information transfer mode.....                                                                  | 11 |
+| A.1.3 Information transfer rate.....                                                                  | 11 |
+| A.1.4 Structure .....                                                                                 | 11 |
+| A.1.5 Establishment of communication .....                                                            | 12 |
+| A.1.6 Communication configuration.....                                                                | 12 |
+| A.1.7 Symmetry .....                                                                                  | 12 |
+| A.1.8 Data compression.....                                                                           | 13 |
+| A.2 Attributes describing the access at the user equipment.....                                       | 13 |
+| A.2.1 Signalling access .....                                                                         | 13 |
+| A.2.2 Information access.....                                                                         | 13 |
+| A.2.2.1 Rate.....                                                                                     | 13 |
+| A.2.2.2 Interface .....                                                                               | 13 |
+| A.3 Interworking attribute .....                                                                      | 14 |
+| A.3.1 Type of terminating network.....                                                                | 14 |
+| A.3.2 Terminal to terminating network interface.....                                                  | 14 |
+| A.4 General attributes .....                                                                          | 14 |
+| A.4.1 Supplementary services provided.....                                                            | 14 |
+| A.4.2 Quality of service .....                                                                        | 14 |
+| A.4.3 Commercial and operational .....                                                                | 15 |
+| A.4.4 Service interworking .....                                                                      | 15 |
+| <b>Annex B (normative): List of definitions of attributes and values used for teleservices.....16</b> |    |
+| B.1 High layer attributes.....                                                                        | 16 |
+| B.1.1 Type of user information.....                                                                   | 16 |
+| B.1.2 Layer 4 protocol functions .....                                                                | 16 |
+| B.1.3 Layer 5 protocol functions .....                                                                | 16 |
+| B.1.4 Layer 6 protocol functions .....                                                                | 16 |
+| B.1.5 Layer 7 protocol functions .....                                                                | 16 |
+
+B.2 Low layer attribute (bearer capabilities) ..... 16
+
+B.3 General attributes ..... 16
+
+**Annex C (normative): Definition of "busy" in a PLMN ..... 17**
+
+C.1 Scope..... 17
+
+C.2 Network Determined User Busy (NDUB) condition..... 17
+
+C.3 User Determined User Busy (UDUB) condition ..... 17
+
+C.4 Mobile subscriber busy ..... 17
+
+**Annex D (normative): Call set-up procedures ..... 18**
+
+D.1 Scope..... 18
+
+D.2 Mobile Originated Call Set-up..... 18
+
+D.2.1 Called Party Address..... 18
+
+D.2.2 Calling/Called Party Sub-address..... 18
+
+D.2.3 Type of Number ..... 18
+
+D.2.4 Number Plan Indicator ..... 18
+
+D.2.5 Bearer Capability..... 19
+
+D.2.6 Calling Line Indication Restriction Override..... 19
+
+D.2.7 Action of the Network on Call Set-up..... 19
+
+D.3 Mobile Terminated Call Set-up..... 19
+
+D.3.1 Bearer Type ..... 19
+
+D.3.2 Response of the UE ..... 20
+
+D.3.3 Description of Call Re-establishment ..... 20
+
+**Annex E (normative): Automatic calling repeat call attempt restrictions ..... 21**
+
+**Annex F(informative): Procedures for call progress indications ..... 23**
+
+F.1 General..... 23
+
+F.2 Supervisory tones ..... 23
+
+F.2.1 General ..... 23
+
+F.2.2 Method ..... 23
+
+F.2.3 Standard tones ..... 23
+
+F.2.4 Applicability..... 24
+
+F.2.5 Comfort tones..... 24
+
+F.3 Recorded announcements ..... 25
+
+F.4 Application of call control cause information elements to supervisory tones ..... 26
+
+Annex G (informative): Change history..... 27
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document defines the telecommunication services supported by a GSM PLMN within the digital cellular telecommunications system (Phase 2+).
+
+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 covers the definition of the circuit telecommunication services supported by a PLMN. The purpose of the present document is to provide a method for the characterization and the description of these telecommunication services.
+
+TS 22.101 describes overall service principles of a PLMN.
+
+## 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 TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] ITU-T Recommendation I.221: "Common specific characteristics of services".
+- [3] ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic reference model: The basic model".
+- [4] 3GPP TS 22.101: "Service Principles".
+- [5] 3GPP TS 22.002: "Bearer services supported by a PLMN".
+- [6] 3GPP TS 22.003: "Teleservices supported by a PLMN".
+- [7] 3GPP TS 22.004: "General on Supplementary Services".
+- [8] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+- [9] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User equipment (MS)".
+- [10] 3GPP TS 22.081: "Line Identification Supplementary Services; Stage 1".
+- [11] 3GPP TS 22.135: "Multicall; Stage 1".
+- [12] 3GPP TS 24.008: " Mobile radio interface layer 3 specification".
+- [13] 3GPP TS 22.011: "Service accessibility".
+- [14] 3GPP TS 23.003: "Numbering, addressing and identification".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TR 21.905 [1].
+
+# 1 Framework for the description of telecommunication services
+
+## 1.1 The attribute method of characterization of circuit telecommunication services
+
+This characterization is made by using a set of attributes. A telecommunication service attribute is a specific characteristic of that service whose values distinguish it from other telecommunication services. Particular values are assigned to each attribute when a given telecommunication service is described and defined.
+
+A list of definitions of attributes and values used for bearer services and teleservices is contained in, respectively, annex A and annex B.
+
+# 2 Description of circuit telecommunication services by the attribute method
+
+## 2.1 General
+
+Telecommunication services are described by attributes which define service characteristics as they apply at a given reference point where the customer accesses the service. The description of a telecommunication service by the method of attributes is composed of:
+
+- technical attributes as seen by the customer; and
+- other attributes associated with the service provision, e.g. operational and commercial attributes.
+
+## 2.2 Categorisation of telecommunication services
+
+The concepts introduced in the present document are illustrated in table 1.
+
+**Table 1: Categorisation of telecommunication services**
+
+| <b>TELECOMMUNICATION SERVICES</b> |                                               |                    |                                           |
+|-----------------------------------|-----------------------------------------------|--------------------|-------------------------------------------|
+| <b>BEARER SERVICE</b>             |                                               | <b>TELESERVICE</b> |                                           |
+| Basic Bearer Service              | Basic Bearer service + supplementary services | Basic Teleservice  | Basic Teleservice + supplementary service |
+
+# 3 Characterization of circuit telecommunication services
+
+## 3.1 General
+
+A telecommunication service supported by a PLMN is characterized and described by service attributes.
+
+There are two groups of service attributes applicable to user information flow:
+
+- low layer attributes;
+- high layer attributes.
+
+Bearer services are characterized only by low layer attributes. Teleservices are characterized by both low layer attributes and high layer attributes.
+
+The basic characteristics of a telecommunication service are described by the basic service attributes.
+
+The additional characteristics associated with a supplementary service which modify or supplement a basic telecommunication service are described in Specification 3GPP TS 22.004 [7].
+
+## 3.2 Bearer services
+
+Bearer services are characterized by a set of low layer attributes in Specification 3GPP TS 22.002[5]. These attributes are classified into four categories:
+
+- information transfer attributes;
+- access attributes;
+- interworking attributes;
+- general attributes, including operational and commercial attributes.
+
+The bearer capability defines the technical features of a bearer service as they appear to the user at the appropriate access point. For the time being, the bearer capability is characterized by information transfer, access and interworking attributes. A bearer capability is associated with every bearer service.
+
+## 3.3 Teleservices
+
+Circuit teleservices provide the full capacity for communication by means of terminals and network functions and possibly functions provided by dedicated centres.
+
+Circuit teleservices are specified in 3GPP TS 22.003 [6]. Teleservices are characterized by a set of low layer attributes, a set of high layer attributes and operational and commercial attributes.
+
+Low layer attributes are those used to characterize the bearer capability. High layer attributes are used in Specification 3GPP TS 22.003 [6] to describe high layer (i.e. layer 4-7) information transfer related characteristics. They refer to functions and protocols of layers 4-7 in the ITU-T Recommendation X.200 framework which are concerned with the transfer, storage and processing of user messages (provided by a subscriber's terminal, a retrieval centre or a network service centre).
+
+Therefore, not all attributes can be applied directly at the user to terminal interface as they represent two kinds of features, the bearer capability and the terminal features, that are not directly perceived by the user.
+
+# --- 4 Provision of telecommunication services
+
+Specifications 3GPP TS 22.101[4] and 3GPP TS 22.011 [13] define some aspects of the provisions of telecommunication services by a 3GPP system.
+
+The provision of telecommunication services implies:
+
+- subscription of basic services and possibly subscription to supplementary services;
+- registration into a service directory;
+- compatibility between terminals;
+- interworking capabilities (see 3GPP TS 29 series of specifications).
+
+The user's subscription to a Basic or Supplementary service is normally verified by the network prior to completion of Call Establishment and/or Supplementary Service operation. This subscription checking shall be performed in accordance with the following subclauses.
+
+## 4.1 Subscription checking for Basic Services
+
+### General
+
+Subscription checking is the function/process to ascertaining whether a subscriber has the authorization to use the particular Basic Service deduced from the call set-up parameters. It is the responsibility of the HPLMN to transfer, to
+
+the VPLMN, only the subscription data corresponding to those services a given subscriber is entitled to use in that VPLMN.
+
+For mobile originated calls, subscription checking is performed in the VLR, whilst for mobile terminated calls it is performed in either the HLR or the VLR (determined as described below). The prerequisite for executing the subscription check is a successful deduction of a Basic Service from the Compatibility Information contained in the call set up, i.e. Bearer Capability Information Element and, in some cases, also the Low Layer and High Layer Compatibility Information elements.
+
+For mobile originated calls an UE shall indicate the requested service by appropriate compatibility information elements according to 3GPP TS 27.001 [8]. This information is mapped to an individual Basic Service code (i.e. the MAP representation) by the MSC in order to be compared with the subscriber data available in the VLR.
+
+An equivalent process is required in the HLR for mobile terminated calls, where the caller's requested service is indicated to the HLR (by the ISDN) by exhaustive compatibility information consisting of ISDN Bearer Capability Information Elements and in some cases - depending on the service requested - also of Low Layer and High layer Compatibility information elements. In case the compatibility information is not exhaustive, e.g. when the call is originated/transited by a PSTN, no Basic Service can be deduced and subscription checking cannot be performed in the "normal" way. Instead, rules for the Single and Multi Numbering Schemes apply.
+
+In the Multi Numbering Scheme the Basic Service can be deduced by information stored in the HLR against the called number and hence an implicit subscription check is performed. In the Single Numbering Scheme, the Basic Service cannot be deduced until the UE has responded to the set up and therefore the HLR cannot perform subscription check. Instead, the VLR/MSC will perform the subscription check or calls are passed "unfiltered" (as regards subscription check), at the network operators' discretion.
+
+### **Bearer Services**
+
+3GPP TS 22.002 [5] lists the Bearer Services, each of them with a specific "BS number". Single services defined independent of the fixed network user rate are called General Bearer Services. These distinct [numbered] services may individually be provided to a subscriber. Whichever the subscription arrangements are, all PLMNs (MSCs, VLRs and HLRs) shall be able to allow - as regards subscription checking - the use of individually subscribed-to Basic Services, within the range of services supported by the PLMN. That is, whenever it is possible to deduce the Basic Service from a call set up, subscription check shall be performed at the granularity of that particular Basic Service or the group to which it belongs.
+
+### **TeleServices**
+
+3GPP TS 22.003 [6] lists the TeleServices, each of them with a specific "TS number". These may be provided to subscribers individually or combined, to the operators' discretion, however TS 12 (Emergency calls) and TS 23 (CBS) are not subscribable. But, as for Bearer Services, networks shall be able to handle subscription checking at the granularity of individual TeleServices.
+
+Table 2 summarizes the basis on which a successful subscription checking will result. It also describes on which basis Supplementary Service handling for a given call set-up should be performed.
+
+Table 2
+
+| Set Up                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Subscription Check                  | SS handling |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------|
+| BS 20                                                                                                                                                                                                                                                                                                                                                                                                                                                               | BS 20                               | BS Group 2x |
+| BS 30                                                                                                                                                                                                                                                                                                                                                                                                                                                               | BS 30                               | BS Group 3x |
+| TS 11                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 11, TS Group 1x or TS Group All  | TS Group 1x |
+| TS 12                                                                                                                                                                                                                                                                                                                                                                                                                                                               | N.A.                                |             |
+| TS 21                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 21, TS Group 2x or TS Group All  | TS Group 2x |
+| TS 22                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 22, TS Group 2x or TS Group All  | TS Group 2x |
+| TS 23                                                                                                                                                                                                                                                                                                                                                                                                                                                               | N.A.                                |             |
+| TS 61                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 61, TS Group 6x or TS Group All  | TS Group 6x |
+| TS 62                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 61, 62, Group 6x or TS Group All | TS Group 6x |
+| TS 91                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 91, TS Group 9x or TS Group All  | TS Group 9x |
+| TS 92                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TS 92, TS Group 9x or TS Group All  | TS Group 9x |
+| Legend: <ul style="list-style-type: none"> <li>- set-up: The Basic Service which is set up for the call;</li> <li>- subscription check: Required VLR or HLR data for successful subscription check;</li> <li>- SS handling: Against which VLR or HLR data SS handling should be performed. For example; a call set-up indicating BS61 and Asynchronous mode should be treated for SS purposes in accordance with the SS-data stored against BS group 2x.</li> </ul> |                                     |             |
+
+When TS61 is requested in a call set-up and the subscription check for TS61 is negative, but a subscription check for TS62 is positive, then the call shall proceed according to the TS 22.003 [6] and TS 27.001 [8]. If a subscription check for both TS61 and TS62 is negative, then the call shall be released.
+
+## 4.2 Subscription checking for Supplementary Services
+
+This is described in 3GPP TS 22.004 [7].
+
+# --- Annex A (normative): List of definition of attributes and values used for bearer services
+
+## A.1 Information transfer attributes
+
+### A.1.1 Information transfer capability
+
+This attribute describes the capability associated with the transfer of different types of information through a PLMN and another network or through a PLMN.
+
+Values:
+
+- unrestricted digital information;  
+transfer of information sequence of bits at its specified bit rate without alteration; this implies bit sequence independence, digit sequence integrity and bit integrity.
+- speech;  
+digital representation of speech information and audible signalling tones of the PSTN coded according to the encoding rule defined in the 3GPP TS 26 series of specifications.
+- 3,1 kHz Ex PLMN;  
+unrestricted digital information transfer within the PLMN and 3.1 kHz audio restricted within the ISDN.
+- group 3 Fax;  
+transfer of Group 3 Fax information.
+
+### A.1.2 Information transfer mode
+
+This attribute describes the operational mode of transferring (transportation and switching) through a PLMN.
+
+Values:
+
+- circuit.
+
+### A.1.3 Information transfer rate
+
+This attribute describes the bit rate (circuit mode). It refers to the transfer of digital information between two access points or reference points.
+
+Values:
+
+- appropriate bit rate, throughput rate.
+
+### A.1.4 Structure
+
+This attribute refers to the capability of the PLMN and if involved other networks to deliver information to the destination access point or reference point in a structure.
+
+Note: This attribute has not been utilised in 3GPP TS 22.002 [5] or 3GPP TS 22.003 [6].
+
+Values:
+
+- not applicable.
+
+### A.1.5 Establishment of communication
+
+This attribute associated with a telecommunication service describes the mode of establishment used to establish and a given communication.
+
+In every telecommunication service communication may be between users within the PLMN or between a user in the PLMN and a user in another network.
+
+Values:
+
+- demand Mobile Originated (MO) only;
+- demand Mobile Terminated (MT) only;
+- demand Mobile Originated or Terminated (MO, MT).
+
+### A.1.6 Communication configuration
+
+This attribute describes the spatial arrangement for transferring information between two or more access points. It completes the structure associated to a telecommunication services as it associates the relationship between the access points involved and the flow of information between these access points.
+
+Values:
+
+- point-to-point communication;  
+this value applies when there are only two access points.
+- multipoint communication;  
+this value applies when more than two access points (1) are provided by the service. The exact characteristics of the information flows must be specified separately based on functions provided by the PLMN.
+
+NOTE 1: The number of access points can be undefined.
+
+- broadcast communication;  
+this value applies when more than two access points (2) are provided by the service. The information flows are from a unique point (source) to the others (destination) in only one direction.
+
+NOTE 2: The number of destination access points can be undefined.
+
+### A.1.7 Symmetry
+
+This attribute describes the relationship of information flow between two (or more) access points or reference points involved in a communication.
+
+It characterizes the structure associated to a communication service.
+
+Values:
+
+- unidirectional;  
+this value applies when the information flow is provided only in one direction.
+- bidirectional symmetric;  
+this value applies when the information flow characteristics provided by the service are the same between two (or more) access points or reference points in the forward and backward directions.
+- bidirectional asymmetric;  
+this value applies when the information flow characteristics provided by the service are different in the two directions.
+
+### A.1.8 Data compression
+
+This attribute indicates whether use of a data compression function is desired (and accepted) between an MT and IWF.
+
+Values:
+
+- use of data compression requested/not requested;
+- use of data compression accepted/not accepted.
+
+## --- A.2 Attributes describing the access at the user equipment
+
+### A.2.1 Signalling access
+
+This attribute characterized the protocol on the signalling channel at a given access point or reference point Values:
+
+- manual;
+- appropriate V-series protocol;
+- appropriate X-series protocol;
+- I-series stack of signalling protocols.
+
+### A.2.2 Information access
+
+#### A.2.2.1 Rate
+
+This attribute describes either the bit rate (circuit mode including transparent access to a PSPDN) or variable bit rate (packet mode) used to transfer the user information at a given access point or reference.
+
+Values:
+
+- appropriate bit rate;
+- variable bit rate.
+
+#### A.2.2.2 Interface
+
+This attribute describes the interface according to the protocol used to transfer user information at a given access point or reference.
+
+Values:
+
+- appropriate V-series DTE/DCE interface;
+- appropriate X-series interface;
+- S interface;
+- analogue 4-Wire interface.
+
+## --- A.3 Interworking attribute
+
+### A.3.1 Type of terminating network
+
+Communication can be established between a UE in a PLMN (originating network) and a terminal in a network (terminating network) including the same PLMN or another PLMN. The attribute designates the terminating network.
+
+NOTE 1: The terms "originating" and "terminating" do not indicate the direction of communication establishment.
+
+NOTE 2: This attribute does not reflect whether there is none, one or several transit networks between the originating and terminating networks.
+
+Values:
+
+- PSTN;
+- ISDN;
+- PSPDN;
+
+- PDN;
+- PLMN;
+- direct access networks.
+
+### A.3.2 Terminal to terminating network interface
+
+This attribute describes the interface between a terminal equipment and the terminating network.
+
+Values:
+
+- appropriate V-series (DTE/DCE) interface;
+- appropriate X-series interface;
+- analogue 2 resp. 4 wire interface;
+- S interface (D+B+B).
+
+## --- A.4 General attributes
+
+### A.4.1 Supplementary services provided
+
+This attribute refers to the supplementary services to a given telecommunication service.
+
+Values:
+
+- appropriate supplementary services.
+
+### A.4.2 Quality of service
+
+The Bearer Services use the Quality of Service attribute to indicate one of the following values:
+
+- transparent;  
+service characterized by constant throughput, constant transit delay and variable error rate.
+- non-transparent;  
+service characterized by an improved error rate with variable transit delay and throughput.
+
+### A.4.3 Commercial and operational
+
+### A.4.4 Service interworking
+
+# --- Annex B (normative): List of definitions of attributes and values used for teleservices
+
+## B.1 High layer attributes
+
+### B.1.1 Type of user information
+
+This attribute describes the type of information which the communication offered to the user by the teleservice is based on.
+
+Values:
+
+- speech;
+- short message;
+- facsimile.
+
+### B.1.2 Layer 4 protocol functions
+
+### B.1.3 Layer 5 protocol functions
+
+### B.1.4 Layer 6 protocol functions
+
+### B.1.5 Layer 7 protocol functions
+
+## --- B.2 Low layer attribute (bearer capabilities)
+
+The low layer attributes describe the bearer capabilities which support the teleservice. These low layer attributes and their values are the same as presented in Annex A: List of definitions of attributes and values used for bearer services.
+
+## --- B.3 General attributes
+
+The general attributes are the same as presented in annex A: List of definitions and values used for bearer services.
+
+# --- Annex C (normative): Definition of "busy" in a PLMN
+
+## C.1 Scope
+
+This annex describes the conditions under which a given mobile subscriber (station) is considered as "busy". In general, this occurs whenever the resources associated with that UE (and needed to successfully complete the call) exist but are not available for that call. The description is based on the busy definition in the ISDN (CCITT Recommendation I.221).
+
+In addition, the operation of some Supplementary Services occurs when certain of these resources are busy. Therefore, these "resources busy" are also described herein.
+
+This annex does not cover the cases, when network resources not associated with a given destination are unavailable, or when such resources are out-of-service or otherwise non-functional.
+
+## --- C.2 Network Determined User Busy (NDUB) condition
+
+This condition occurs, when a call is about to be offered, if the information (i.e. traffic) channel is busy and the maximum number of total calls has been reached (see note).
+
+This condition also occurs, when a call is about to be offered and an already on-going call attempt (incoming or outgoing) is in the establishing phase, i.e. not yet active.
+
+When NDUB condition occurs, the PLMN will clear the call and indicate "busy" back towards the calling subscriber (see also clause 4).
+
+NOTE: The value of the maximum number of calls is 1 for the basic call. When the supplementary service "Call Waiting" is applicable the value is  $n+1$  where  $n$  is the maximum number of calls that can be waiting.
+
+3GPP TS 22.135 [11] defines NDUB for Multicall environment.
+
+## --- C.3 User Determined User Busy (UDUB) condition
+
+This condition occurs when a call is offered to a user equipment and the UE responds "user busy" because the subscribers resources (terminal or person using them) are busy. Then the PLMN will clear the call with the indication "busy" back towards the calling subscriber (see also clause 4).
+
+## --- C.4 Mobile subscriber busy
+
+A mobile subscriber is considered to be busy if either a "Network Determined User Busy" or a "User Determined User Busy" condition occurs.
+
+Some supplementary services (e.g. Call Forwarding on Busy) may cause the call not to be cleared when a busy condition occurs.
+
+# --- Annex D (normative): Call set-up procedures
+
+## D.1 Scope
+
+This annex specifies the service requirements for call set-up, both Mobile originated and mobile terminated, in a network, including the establishment of radio contact.
+
+## --- D.2 Mobile Originated Call Set-up
+
+When an UE wishes to start a call and there is no existing radio connection, it requests a signalling channel. When such a signalling channel has been allocated to the UE, the UE can transfer the call set-up information.
+
+A traffic channel may be allocated at any time before the network informs the UE that the remote user has answered.
+
+For a call to be set up, certain information needs to be sent by the UE to the network, defining the call. This information may be provided as default by the MS, it may be derived from the SIM/USIM or be entered by the user either directly into the UE or from a DTE by using the DTE/DCE Interface.
+
+The following information is sent. Where necessary, default values will generally be inserted by the UE if not directly specified by the user. The Teleservice Emergency Calls are set up using a special procedure not using the fields described in this clause (except for the Bearer Capability).
+
+### D.2.1 Called Party Address
+
+This is the address of the called party, generally as defined in 3GPP TS 23.003 [14], using the TON/NPI specified below
+
+### D.2.2 Calling/Called Party Sub-address
+
+This is the sub-address of the calling/called party, as defined in 3GPP TS 23.003 [14], in order to provide interworking with ISDN. This is described in more detail in ETS 300 059. Support and use of these fields are optional.
+
+### D.2.3 Type of Number
+
+This indicates the format of the called party address. The selection procedure is given in 3GPP TS 22.030 [9]. The following Types of Number are commonly used:
+
+- International Format;
+- Open Format ("Unknown");
+
+### D.2.4 Number Plan Indicator
+
+This indicates the number plan of the called party address. Either of the following number plans may be the "default", depending on the contents of the Called Party Address (see 3GPP TS 22.030 [9]):
+
+- ISDN/Telephony E.164;
+- unknown.
+
+Alternatively, one of these number plans may be specified if appropriate:
+
+- data network X.121;
+- telex network F.69;
+- National Numbering Plan;
+- Private Numbering Plan.
+
+### D.2.5 Bearer Capability
+
+This is used to define the type of call to be set up (telephony, data, rate etc.) For most applications, the UE will use a set of default conditions, generally on the assumption of a telephony call, unless otherwise set. These may be overridden by the user (or DTE via the DTE/DCE Interface) if desired except for the determination of the channel mode (full or half rate, speech codec conversion).
+
+The UE shall indicate to the network its channel mode capability in terms of the data channels and the speech codec versions supported.
+
+The network decides which mode to use on the basis of the requested bearer or teleservice, the available network resources and the channel mode capability of the UE:
+
+- for the "alternate" and "followed-by" services, the same principle applies (with the exception of TS61, where a Full Rate or an Enhanced Full Rate channel shall be provided);
+- for the full set of parameters and values, refer to 3GPP TS 24.008 [12];
+- for data services see the 3GPP TS 27 series.
+
+Lower Layer Compatibility and Higher Layer Compatibility Information Elements may also be included.
+
+### D.2.6 Calling Line Indication Restriction Override
+
+If the user wishes to override the calling line identification restriction, he may indicate this on a per-call basis as described in 3GPP TS 22.030 [9] and 3GPP TS 22.081 [10].
+
+### D.2.7 Action of the Network on Call Set-up
+
+On receipt of the call set-up message, the network shall attempt to connect the call. However, if insufficient information has been provided by the UE to indicate the exact Bearer Capability requirements (e.g. due to missing or optional values or for rate adaptation for data), the network may insert the missing information, if this is possible, and the call set-up shall proceed using the new information. If the call set-up is unsuccessful, the network shall notify the UE of the cause.
+
+## --- D.3 Mobile Terminated Call Set-up
+
+Using the procedures described in 3GPP TS 22.011, the network knows the location area where the UE is positioned. If the UE is not already in two way radio communication with the network, the network pages the MS. Upon receiving its page message, the UE establishes communication with the selected cell. The network then allocates a channel which is used for signalling and sends call set-up information to the UE.
+
+A traffic channel may be allocated at any instant until just after the call is answered by the UE.
+
+The network indicates to the UE that it wishes to offer the UE a call. This notification includes the proposed bearer capability information, where available (see subclause D.2.5).
+
+### D.3.1 Bearer Type
+
+If the calling party specifies the required bearer capability this shall be used for the call set-up attempt. If the calling party does not specify the required bearer capability (e.g. because the call originated in the PSTN), the network shall attempt to determine the bearer capability to be used as described below.
+
+The network may use a multi-numbering scheme to define the bearer capability by the MSISDN. In a multi-numbering scheme several MSISDNs are associated with one IMSI. Each MSISDN is used for a different bearer capability. If the network uses a multi-numbering scheme and the calling party has not specified the required bearer capability then the network shall use the bearer capability associated with the called party MSISDN.
+
+The network may use a single-numbering scheme, in which one MSISDN is associated with each IMSI. If the network uses a single-numbering scheme and the calling party has not specified the required service then the network shall omit the bearer capability information.
+
+### D.3.2 Response of the UE
+
+On receipt of the call set-up request from the network, the UE shall check that it is able to support the type of call requested and that it is not User Determined User Busy (see annex C). The UE then alerts the user.
+
+If the UE is unable to support the type of call requested, or the information is incomplete, the UE shall, if possible and not restricted by requirements in other ETSs, reply to the network proposing an alternative set of parameters, indicating those that are different from those proposed by the network. The network then either accepts this new proposal or terminates the call attempt.
+
+### D.3.3 Description of Call Re-establishment
+
+Call re-establishment allows the user equipment to attempt to reconnect a call following the loss of radio coverage between the UE and the network while a call is in progress. Call re-establishment may be initiated by the UE when it detects this situation, if supported in the network.
+
+Call re-establishment is mandatory in the ME and optional in the network.
+
+# --- Annex E (normative): Automatic calling repeat call attempt restrictions
+
+Call set up attempts referred to in this annex are assumed to be initiated from peripheral equipment or automatically from the MT itself.
+
+A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in 3GPP TS 24.008 [13]).
+
+These reasons are classified in three major categories:
+
+- 1) "Busy destination":
+  - cause number 17 User busy.
+- 2) "Unobtainable destination - temporary":
+  - cause number 18 No user responding;
+  - 19 User alerting, no answer;
+  - 27 Destination out of order;
+  - 34 No circuit/channel available;
+  - 41 Temporary failure;
+  - 42 Switching Equipment congestion;
+  - 44 Requested circuit/channel not available;
+  - 47 Resources unavailable, unspecified.
+- 3) "Unobtainable destination - permanent/long term":
+  - cause number 1 Unassigned (unallocated) number;
+  - 3 No route to destination;
+  - 22 Number changed;
+  - 28 Invalid number format (uncompleted number);
+  - 38 Network out of order.
+
+NOTE 1: Optionally, it is allowed to implement cause number 27 in Category 3, instead of Category 2, as this is desirable already in Phase 1.
+
+The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this number n is reached, the associated B number shall be blacklisted by the MT until a manual re-set at the MT is performed in respect of that B number. When a repeat attempt to anyone B number fails, or is blacklisted, this does not prevent calls being made to other B numbers.
+
+**For the categories 1 and 2 above, n shall be 10; for category 3, n shall be 1.**
+
+| <b>call attempts</b> | <b>Minimum duration between Call attempt</b> |
+|----------------------|----------------------------------------------|
+| Initial call attempt | -                                            |
+| 1st repeat attempt   | 5 sec                                        |
+| 2nd repeat attempt   | 1 min                                        |
+| 3rd repeat attempt   | 1 min                                        |
+| 4th repeat attempt   | 1 min                                        |
+| 5th repeat attempt   | 3 min                                        |
+| nth repeat attempt   | 3 min                                        |
+
+The number of B numbers that can be held in the blacklist is at the manufacturers discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers.
+
+When automatic calling apparatus is connected to an MT1 or MT2, or where an MTO is capable of auto-calling, then the MT shall process the call requests in accordance with the sequence of repeat attempts defined above, i.e. requests for repeat attempts with less than the minimum allowed duration between them shall be rejected by the MT.
+
+A successful call attempt to a number which has been subject to the call restrictions shown above (i.e. an unsuccessful call set up attempt has previously occurred) shall reset the "counter" for that number.
+
+The "counter" for an unsuccessfully attempted B number shall be maintained in 24 hours or until the MT is switched off.
+
+The automatic calling repeat call attempt restrictions apply to speech and data services.
+
+NOTE 2: The restrictions only apply to unsuccessful Call Control activity, not to Radio Resource Management or to Mobility Management, so multiple attempts at radio channel access are not limited by this mechanism.
+
+# --- Annex F(informative): Procedures for call progress indications
+
+## F.1 General
+
+Indications of call progress, such as ringing, engaged, unobtainable, and no radio channel, may in principle be verbal message, tones, displayed text or graphical symbols. Which combination of these applies may depend on the message, the UE and selection by the user or PLMN operator. However, verbal announcements will generally be reserved for situations which are peculiar to a mobile network, where users may be unfamiliar with any tone chosen to indicate conditions such as "call diversion" or "subscriber not available".
+
+It may also be desirable to add comfort indications (e.g. tones, noise, music, clicks) while a call is being connected, since silence may cause an unfamiliar user to believe that nothing is happening.
+
+Generally, on data calls, and on the data part of alternate speech/data or speech-followed-by-data calls, PLMN generated network tones and announcements should be muted.
+
+## --- F.2 Supervisory tones
+
+### F.2.1 General
+
+Supervisory Tones, indicating primarily ringing, engaged and unobtainable numbers, may be generated by both the PLMN and PSTN.
+
+Except for ring tone, all tones indicating call progress to a user shall be generated in the UE, on the basis of signals from the network where available, and are according to the standard defined in the present document.
+
+Tones sent to a caller to a UE will be generated in the network, generally local to the caller, and will be to the standard of his local exchange, except for mobile to mobile calls, where the tones will be generated in the calling UE. For mobile terminated calls, the ring tone will be generated in the called MSC (except OACSU).
+
+### F.2.2 Method
+
+In the interests of early release of the traffic channel on failure to succeed in setting up a (mobile originated) call, where possible supervisory tones should be indicated over signalling channels. The UE will then generate the required tones. However, if the network generates an in-band announcement this will be indicated to the UE. In this case the UE shall connect the user to the announcement until instructed to release the call, either by the user or by the network. An alternate procedure may apply for UE able to generate appropriate announcements internally.
+
+The ring tone will be sent over the traffic channel, since this channel must be available for traffic immediately it is answered (exception: Off Air Call Set Up). The Ring Tone is therefore generated by the PLMN or PSTN supporting the called phone.
+
+On failed mobile terminated call attempts, the called MSC will either signal to the caller, if this is possible, or else will generate the required supervisory tones.
+
+"Alert" is not a supervisory tone. The indication is signalled, and the UE may generate any form of indication to the user that the UE is being called.
+
+### F.2.3 Standard tones
+
+UE generated tones will be generally in accordance with CEPT, ANSI T1.607, or Japan recommendations, where appropriate, and are listed in table 1. Any network originated tones will be according to PLMN or PSTN choice.
+
+### F.2.4 Applicability
+
+This method will apply in all cases where signalling is capable of indicating the supervisory tone required. However, for connection to certain fixed networks where this signalling is not possible, fixed network tones will be carried over the traffic channel.
+
+User equipment may employ any suitable technique to indicate supervisory information. However, if tones are employed, they shall be in accordance with the present document. The use of these tones in the MSC is preferred.
+
+NOTE 1: The tones and/or announcement to the calling party should not be provided if the Information transfer capability is set to UDI.
+
+NOTE 2: For a call with information transfer capability set to 3.1 kHz, the use of tones and/or announcement may cause the expiry of an awaiting answer timer in a modem or fax machine.
+
+### F.2.5 Comfort tones
+
+If desired by the PLMN operator, the network may optionally introduce "comfort tones" while the call is being connected, during what would otherwise be silence. This would be overridden by indication of a supervisory tone, an announcement or by traffic. PLMNs may offer this feature optionally to incoming or outgoing callers.
+
+The "comfort tones" may take the form of tones, clicks, noise, music or any other suitable form, provided that they cannot be confused with other indications that might be expected.
+
+This feature is intended to indicate to the user that his call is progressing, to prevent him terminating the call prematurely.
+
+Table 1: Supervisory tones in UEs
+
+| Tone                                                                                                                                                                                                                            |                                                                           | Frequency                                                                                                                                                                                                                                                             |                              |          | Tolerance               |          | Type                                             |                                                 |                                |       |  |  |  |  |  |  |  |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------|-------------------------|----------|--------------------------------------------------|-------------------------------------------------|--------------------------------|-------|--|--|--|--|--|--|--|
+|                                                                                                                                                                                                                                 |                                                                           | CEPT                                                                                                                                                                                                                                                                  | ANSI                         | Japan    | CEPT                    | ANSI     | Japan                                            | CEPT                                            | ANSI                           | Japan |  |  |  |  |  |  |  |
+| 1                                                                                                                                                                                                                               | Dial tone (optional)                                                      | 425 Hz                                                                                                                                                                                                                                                                | 350 Hz added to 440 Hz       | 400 Hz   | 15 Hz                   | 20Hz     | Continuous                                       | Continuous                                      | Continuous                     |       |  |  |  |  |  |  |  |
+| 2 *                                                                                                                                                                                                                             | Subscriber Busy (Called Number)                                           | 425 Hz                                                                                                                                                                                                                                                                | 480 Hz added to 620 Hz       | 400 Hz   | 15 Hz                   | 20Hz     | Tone on 500ms<br>Silence 500ms                   | Tone on 500ms<br>Silence 500ms                  | Tone on 500ms<br>Silence 500ms |       |  |  |  |  |  |  |  |
+| 3 *                                                                                                                                                                                                                             | Congestion                                                                | 425 Hz                                                                                                                                                                                                                                                                | 480 Hz added to 620 Hz       | Optional | 15 Hz                   | Optional | Tone on 200ms<br>Silence 200ms                   | Tone on 250ms<br>Silence 250ms                  | Optional                       |       |  |  |  |  |  |  |  |
+| 4                                                                                                                                                                                                                               | Radio Path Acknowledgement (Mobile Originated only) (optional)            | 425 Hz                                                                                                                                                                                                                                                                | 425 Hz                       | 400 Hz   | 15 Hz                   | 20 Hz    | Single tone 200ms                                | Single tone 200ms                               | Tone on 1 Sec<br>Silence 2 Sec |       |  |  |  |  |  |  |  |
+| 5                                                                                                                                                                                                                               | {Radio Path Not Available<br>{Call Dropped – Mobile originated only       | 425 Hz                                                                                                                                                                                                                                                                | 425 Hz                       | Optional | 15 Hz                   | Optional | 200ms}<br>On/off 200ms}<br>for 3 burst           | 200ms}<br>On/off 200ms}<br>for 3 burst          | Optional                       |       |  |  |  |  |  |  |  |
+| 6 *                                                                                                                                                                                                                             | Error/Special Information} Number Unobtainable } Authentication Failure } | 950 Hz<br>1400 Hz<br>1800 Hz                                                                                                                                                                                                                                          | 950 Hz<br>1400 Hz<br>1800 Hz | Optional | 50 Hz<br>50 Hz<br>50 Hz | Optional | {Triple Tone<br>{Tones on 330ms<br>{Silence 1.0s | Triple Tone<br>{Tones on 330ms<br>{Silence 1.0s | Optional                       |       |  |  |  |  |  |  |  |
+| 7                                                                                                                                                                                                                               | Call Waiting Tone (CEPT)                                                  | 425 Hz (tolerance 15 Hz), on for 200 ms, off for 600 ms on for 200 ms, off for 3 s, on for 200 ms, off for 600 ms on for 200 ms. This tone is superimposed on the audio traffic received by the called user. Alternate tones are <i>acceptable</i> but not preferred. |                              |          |                         |          |                                                  |                                                 |                                |       |  |  |  |  |  |  |  |
+| 7                                                                                                                                                                                                                               | Call Waiting Tone (ANSI)                                                  | 440 Hz, on for 300 ms, 9,7 s off followed by (440 Hz, on for 100 ms off for 100 ms, on for 100 ms, 9,7s off and repeated as necessary) This tone is superimposed on the audio traffic received by the called user.                                                    |                              |          |                         |          |                                                  |                                                 |                                |       |  |  |  |  |  |  |  |
+| 7                                                                                                                                                                                                                               | Call Waiting Tone (Japan)                                                 | Optional                                                                                                                                                                                                                                                              |                              |          |                         |          |                                                  |                                                 |                                |       |  |  |  |  |  |  |  |
+| Definition of these and other tones, together with advice on announcements, may be found in CEPT T/CS 20-15 and in T/SF 23.                                                                                                     |                                                                           |                                                                                                                                                                                                                                                                       |                              |          |                         |          |                                                  |                                                 |                                |       |  |  |  |  |  |  |  |
+| NOTE: *: The duration of these tones is an implementation option. However, in each case, the UE should be returned immediately to the idle state, and will be able to originate/receive calls, which will override these tones. |                                                                           |                                                                                                                                                                                                                                                                       |                              |          |                         |          |                                                  |                                                 |                                |       |  |  |  |  |  |  |  |
+| Ringing Tone (Alternative National options permitted)                                                                                                                                                                           |                                                                           | 425Hz                                                                                                                                                                                                                                                                 | 440 Hz added to 480 Hz       | Optional | 15 Hz                   | Optional | Tone on 1 s<br>Silence 4 s                       | Tone on 2 s<br>Silence 4 s                      | Optional                       |       |  |  |  |  |  |  |  |
+| For application of Call Control Cause Information Elements to these tones, see F.4.                                                                                                                                             |                                                                           |                                                                                                                                                                                                                                                                       |                              |          |                         |          |                                                  |                                                 |                                |       |  |  |  |  |  |  |  |
+
+## F.3 Recorded announcements
+
+In present networks, both fixed and cellular, the language of recorded announcements and displayed information is invariably that of the country of origin. However, this is generally undesirable in a multi-lingual environment such as is encountered on a global network with international roaming. It is therefore probably desirable to minimise the number of such announcements.
+
+Advanced UEs may be designed which have the ability to generate announcements in the form desired by the user, e.g. in the language preferred by the user. In this case, it becomes necessary to block any verbal announcements sent from the network towards the UE, to avoid clashes with those generated by the UE. The UE may be allowed to block in-band announcements in case appropriate announcements according to the Cause Information Elements (F.3) can be generated. The default setting of the UE shall be "non blocking", which could be set by MMI command to "blocking".
+
+Announcements generated by the PLMN and sent to callers to that PLMN will generally be in the language of the PLMN. However, on some fixed networks it will be possible for the message to be signalled back to the caller's local exchange, which will then generate the announcement in its local language.
+
+## --- F.4 Application of call control cause information elements to supervisory tones
+
+The Cause Information Elements are listed and defined in 3GPP TS 24.008 [12]. This annex lists these elements and indicates which supervisory tone should be generated in response. It should be noted that some conditions (e.g. radio path not available, dropped call) may be deduced by the UE, rather than signalled explicitly over the air interface. All causes not listed below should result in the generation of tone 6. In case of multiple calls a tone should only be generated if it does not disturb an ongoing active call. "-" indicates no tone required.
+
+| Cause<br>CC |                                         | Tone<br>(see table 1) |
+|-------------|-----------------------------------------|-----------------------|
+| 16          | Normal Clearing                         | 1                     |
+| 17          | User Busy                               | 2                     |
+| 22          | Number Changed                          | -                     |
+| 30          | Response to STATUS ENQUIRY              | -                     |
+| 31          | Normal, unspecified                     | -                     |
+| 34          | No circuit/channel available            | 3                     |
+| 41          | Temporary Failure                       | 3                     |
+| 42          | Switching Equipment Congestion          | 3                     |
+| 44          | Requested circuit/channel not available | 3                     |
+| 49          | Quality of Service Unavailable          | 3                     |
+| 58          | Bearer Capability not available         | 3                     |
+
+# Annex G (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                  |        |        |         |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|------------------------------------------------------------------|--------|--------|---------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                  | Old    | New    | WI      |
+| Dec 1999       |           |           | 02.01  |     |     |       |     | Transferred to 3GPP SA1                                          | 8.1.0  | 3.0.0  |         |
+| SP-06          | SP-99519  | S1-991076 | 22.001 | 001 |     | R99   | D   | Mainly an editorial update for GSM/3GPP use                      | 3.0.0  | 3.1.0  |         |
+| SP-07          | SP-000069 | S1-000124 | 22.001 | 002 |     | R99   | D   | Editorial modification for change of SMS-CB to CBS               | 3.1.1  | 3.2.0  |         |
+| SP-07          | SP-000053 | S1-000133 | 22.001 | 003 |     | R99   | C   | Procedure for call progress indications                          | 3.1.1  | 3.2.0  |         |
+| SP-09          | SP-000389 | S1-000642 | 22.001 | 004 |     | R4    | B   | CR on TS22.001 for Bearer Modification without pre-notification  | 3.2.0  | 4.0.0  |         |
+| SP-10          | SP-000539 | S1-000772 | 22.001 | 005 |     | Rel-4 | B   | Subscription Check                                               | 4.0.0  | 4.1.0  | BMWPN   |
+|                |           |           |        |     |     |       |     | Accepting change bars introduced at SP-10                        | 4.1.0  | 4.1.1  |         |
+| SP-12          | SP-010264 | S1-010540 | 22.001 | 006 |     | Rel-4 | F   | Removal Bearer modification without pre-modification from 22.001 | 4.1.1  | 4.2.0  | BMWPN   |
+| SP-15          | SP-020045 | S1-020457 | 22.001 | 007 | -   | Rel-4 | F   | Editorial CR to correct terms and references                     | 4.2.0  | 4.3.0  | CORRECT |
+| SP-16          | SP-020267 | S1-021043 | 22.001 |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                       | 4.3.0  | 5.0.0  |         |
+| SP-26          | SP-040744 | S1-040997 | 22.001 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                      | 5.0.0  | 6.0.0  |         |
+| SP-36          |           |           | 22.001 |     |     | 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 |         |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                   | 11.0.0 | 12.0.0 |         |
+| 2015-12        |           |           |        |     |     |       |     | Update to Rel-13 version (MCC)                                   | 12.0.0 | 13.0.0 |         |

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

@@ -0,0 +1,412 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) (Release 13)** ---
+
+![3GPP logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font. The '3' is bold and black, the 'G' is black, the 'P' is black, and the 'P' is black. Below the 'G' and 'P' is a red signal icon consisting of three curved lines.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, circuit mode, bearer
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 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, a double-headed arrow labeled 'Information Transfer and Access Attributes (note 3)' spans the PLMN and IWF areas. Below the diagram, a double-headed arrow labeled 'Interworking Attributes' spans the IWF and Transit Network areas. At the bottom, a long double-headed arrow labeled 'General Attributes (note 2)' spans the entire length from the start of the PLMN to the end of the Terminating Network.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg)
+
+Diagram illustrating the relation between groups of attributes and 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, a double-headed arrow labeled 'Information Transfer and Access Attributes (note 3)' spans the PLMN and IWF areas. Below the diagram, a double-headed arrow labeled 'Interworking Attributes' spans the IWF and Transit Network areas. At the bottom, a long double-headed arrow labeled 'General Attributes (note 2)' spans the entire length from the start of the PLMN to the end of 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 path is indicated between the UE and the IWF. The V.120 path is indicated 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 path is indicated between the UE and the IWF. The V.120 path is indicated 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 |                    |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                                                                  | 11.0.0 | 12.0.0 |                    |
+| 2015-12        |           |           |        |     |     |       |     | Update to Rel-13 version (MCC)                                                                                  | 12.0.0 | 13.0.0 |                    |

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

@@ -0,0 +1,674 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Circuit Teleservices supported by a Public Land Mobile Network (PLMN) (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a small "TM" symbol. Above the "lte" text are three green curved lines representing signal waves.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. Below the "P" is a small red signal icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>TM</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP<sup>TM</sup> system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+GSM, UMTS, circuit mode, service  
+All rights reserved.
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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. A long double-headed arrow labeled 'High layer attributes' spans from the first TE to the last TE. A shorter double-headed arrow labeled 'Low layer attributes (=bearer capability)' is positioned above the PLMN box, indicating its specific scope.
+
+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 |
+|                                                                                             | 1.2 Layer 4 protocol functions            |                                         |
+|                                                                                             | 1.3 Layer 5 " "                           | Secondary attributes                    |
+|                                                                                             | 1.4 Layer 6 " "                           | " "                                     |
+|                                                                                             | 1.5 Layer 7 " "                           | " "                                     |
+| 2. Low layer capabilities (describing the Bearer capability which supports the Teleservice) | 2.1 Information transfer                  | " "                                     |
+|                                                                                             | 2.1.1 Information transfer capabilities   | " "                                     |
+|                                                                                             | 2.1.2 Information transfer mode           | " "                                     |
+|                                                                                             | 2.1.3 Information transfer rate           | Individual services (in the category)   |
+|                                                                                             | 2.1.4 Structure                           |                                         |
+|                                                                                             | 2.1.5 Establishment of communication      |                                         |
+|                                                                                             | 2.1.6 Communication configuration         |                                         |
+|                                                                                             | 2.1.7 Symmetry                            |                                         |
+|                                                                                             | 2.2 Access (3GPP TS 22.001)               | Qualifying attributes                   |
+|                                                                                             | 2.2.1 Signalling access                   | " "                                     |
+|                                                                                             | 2.2.2 Information access                  | " "                                     |
+|                                                                                             | 2.3 Interworking                          | " "                                     |
+|                                                                                             | 2.3.1 Terminating network type            | " "                                     |
+|                                                                                             | 2.3.2 National/international interworking | Further specify the individual services |
+|                                                                                             | 2.3.3 Interface of terminal equipment     |                                         |
+|                                                                                             | 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 trans-mission             | 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 trans - mission        | 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<br>T<br>T<br>R<br>I<br>B<br>U<br>T<br>E<br>S         | 1.             | 1.1 Type or user information       |                                              | short message, $\leq 160$ characters                                                                                                                                                                                                                                                                                                             |      |
+|                                                        |                | 1.2 Layer 4 protocol functions     |                                              |                                                                                                                                                                                                                                                                                                                                                  |      |
+|                                                        |                | 1.3 Layer 5 protocol functions     |                                              | see 3GPP TS23.040                                                                                                                                                                                                                                                                                                                                |      |
+|                                                        |                | 1.4 Layer 6 protocol functions     |                                              | see 3GPP TS 23.040                                                                                                                                                                                                                                                                                                                               |      |
+|                                                        |                | 1.5 Layer 7 protocol functions     |                                              | see 3GPP TS 23.040                                                                                                                                                                                                                                                                                                                               |      |
+|                                                        | 2.             | 2.1<br><br>Inform<br><br>transfer  | 2.1.1 Information transfer capability        | not applicable                                                                                                                                                                                                                                                                                                                                   |      |
+|                                                        |                |                                    | 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                               | not applicable                                                                                                                                                                                                                                                                                                                                   |      |
+|                                                        |                | 2.2<br>Access<br>at UE             | 2.2.1 Signalling access                      | see 3GPP TS 27.005                                                                                                                                                                                                                                                                                                                               |      |
+|                                                        |                |                                    | 2.2.2 Information access<br>(3GPP TS 22.001) | <table border="1" style="width:100%; border-collapse: collapse;"> <tr><td style="border:none; border-right: 1px solid black; border-bottom: 1px solid black;">rate</td><td style="border:none; border-bottom: 1px solid black;">not applicable</td></tr> <tr><td style="border:none;">interface</td><td style="border:none;"></td></tr> </table> | rate |
+| rate                                                   | not applicable |                                    |                                              |                                                                                                                                                                                                                                                                                                                                                  |      |
+| 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                                        |                                      |
+| 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                             | not applicable                       |
+|                                                        |     | 2.2                                        |                                      |
+|                                                        |     | Access                                     |                                      |
+|                                                        |     | at UE                                      |                                      |
+|                                                        |     | 2.2.1 Signalling access                    | see 3GPP TS 27.005                   |
+|                                                        |     | 2.2.2 Information access                   | rate                                 |
+|                                                        |     | (3GPP TS 22.001)                           | interface                            |
+|                                                        |     | 2.3                                        |                                      |
+|                                                        |     | Inter-                                     |                                      |
+|                                                        |     | 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 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<br>T<br>T<br>R<br>I<br>B<br>U<br>T<br>E<br>S | 1.  | 1.1 Type or user information                           |                                       | short message, $\leq 93$ characters 4)     |                |
+|                                                |     | 1.2 Layer 4 protocol functions                         |                                       |                                            |                |
+|                                                |     | 1.3 Layer 5 protocol functions                         |                                       | see 3GPP TS 23.041                         |                |
+|                                                |     | 1.4 Layer 6 protocol functions                         |                                       | see 3GPP TS 23.041                         |                |
+|                                                |     | 1.5 Layer 7 protocol functions                         |                                       | see 3GPP TS 23.041                         |                |
+|                                                | 2.  | 2.1<br><br>Inform<br><br>transfer                      | 2.1.1 Information transfer capability | not applicable                             |                |
+|                                                |     |                                                        | 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<br><br>Access<br><br>at UE<br><br>(3GPP TS 22.001) | 2.2.1 Signalling access               | not applicable                             |                |
+|                                                |     |                                                        | 2.2.2 Information access              | rate                                       | not applicable |
+|                                                |     |                                                        |                                       | interface                                  | not applicable |
+|                                                |     |                                                        | 2.3<br><br>Inter-<br><br>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)             |
+|                                                | Gen | 3.                                                     | 3.1 Supplementary service provided    |                                            | 3GPP TS 22.004 |
+|                                                |     |                                                        | 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>(3GPP TS 22.001) | rate                         | fullrate        |
+|                                                        |                   |                                |                                              | interface                    | 2 wire analogue |
+| A<br>T<br>T<br>R<br>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<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                     |                                       |                        |
+|                                                |                   | 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 |                               |                                       |                        |
+| B<br>U<br>T<br>E<br>S                          | LLC               | Inform<br>Transfer             | 2.1                           | 2.1.1 Information transfer capability | Facsimile group 3      |
+|                                                |                   |                                |                               | 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 |
+|                                                |                   | Access<br>At UE                | 2.2                           | 2.2.1 Signalling access               | 1.440/450 (GSM 04.08)  |
+|                                                |                   |                                |                               | 2.2.2 Information access              | rate Fullrate          |
+|                                                |                   |                                |                               | (3GPP TS 22.001) interface            | 2 wire, analogue       |
+| 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.                             |                               | 3.1 Supplementary service provided    | 3GPP TS 22.004         |
+|                                                |                   |                                |                               | 3.2 Quality of service                |                        |
+|                                                |                   | Gen                            |                               |                                       |                        |
+
+##### 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) ME |
+|                                          | 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              | 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.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 |         |
+| 2014-09        |           |           |        |     |     |       |     | Update to Rel-12 version (MCC)                                                   | 11.0.0 | 12.0.0 |         |
+| 2015-01        |           |           |        |     |     |       |     | Update to Rel-13 version (MCC)                                                   | 12.0.0 | 13.0.0 |         |

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

@@ -0,0 +1,785 @@
+
+
+# **3GPP TS 22.004 V13.0.0 (2016-01)** **Technical Specification Group Services and System Aspects** **General on supplementary services** **(Release 13)**
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font with a small "TM" symbol. Above the "e" is the text "Advanced Pro" in a smaller font. To the left of the text is a green signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo. It features the letters "3GPP" in a stylized, bold font. The "P" has a small signal icon (three curved lines) at its base. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+GSM, UMTS, supplementary service
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- 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    |
+| 2014-10        | -         | -         | -      | -    | -   | -      | -   | Update to Rel-12 version (MCC)                                                                  | 11.0.0 | 12.0.0 |           |
+| 2015-12        |           |           |        |      |     |        |     | Update to Rel-12 version (MCC)                                                                  | 12.0.0 | 13.0.0 |           |

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

@@ -0,0 +1,202 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **3GPP TS 22.016 (2016-01)** **International Mobile station Equipment Identities (IMEI)** *Technical Specification* **(Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller font. To the left of the text is a green signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon consisting of three curved lines of increasing height. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+GSM, UMTS, LTE, addressing
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |                   |
+| 2014-10        | -         | -         | -          | -    | -    | -     | -   | Update to Rel-12 version (MCC)                                                                | 11.0.0 | 12.0.0 |                   |
+| 2015-12        |           |           |            |      |      |       |     | Update to Rel-13 version (MCC)                                                                | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22022/raw.md

@@ -0,0 +1,725 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Personalisation of Mobile Equipment (ME); Mobile functionality specification (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a green signal icon consisting of three curved lines of increasing height. A small "TM" trademark symbol is located to the bottom right of the "e".
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top. Below the "P" is a red signal icon consisting of three curved lines of increasing height. To the right of the "P" is a small "TM" trademark symbol. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>TM</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP<sup>TM</sup> system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+GSM, UMTS, terminal
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                             |           |
+|-------------------------------------------------------------|-----------|
+| Foreword .....                                              | 5         |
+| 1 Scope.....                                                | 6         |
+| 2 References.....                                           | 6         |
+| 3 Definitions and abbreviations .....                       | 7         |
+| 3.1 Abbreviations .....                                     | 7         |
+| 3.2 Definitions.....                                        | 7         |
+| 4 General description .....                                 | 8         |
+| 5 Network personalisation .....                             | 9         |
+| 5.1 Network personalisation.....                            | 9         |
+| 5.1.1 Operation of network personalised ME.....             | 9         |
+| 5.1.2 Network personalisation cycle .....                   | 9         |
+| 5.1.2.1 Personalisation cycle.....                          | 9         |
+| 5.1.2.2 De-personalisation cycle.....                       | 10        |
+| 5.2 Network subset personalisation.....                     | 10        |
+| 5.2.1 Operation of Network subset personalised ME.....      | 10        |
+| 5.2.2 Network subset personalisation cycle .....            | 11        |
+| 5.2.2.1 Personalisation Cycle.....                          | 11        |
+| 5.2.2.2 De-personalisation cycle.....                       | 11        |
+| 6 SP personalisation.....                                   | 12        |
+| 6.1 Operation of SP personalised MEs.....                   | 12        |
+| 6.2 SP personalisation cycle.....                           | 12        |
+| 6.2.1 Personalisation cycle .....                           | 12        |
+| 6.2.2 De-personalisation cycle .....                        | 13        |
+| 7 Corporate personalisation .....                           | 13        |
+| 7.1 Operation of corporate personalised MEs.....            | 13        |
+| 7.2 Corporate personalisation cycle .....                   | 14        |
+| 7.2.1 Personalisation cycle .....                           | 14        |
+| 7.2.2 De-personalisation cycle .....                        | 14        |
+| 8 SIM/USIM personalisation .....                            | 15        |
+| 8.1 Operation of SIM/USIM personalised ME .....             | 15        |
+| 8.2 SIM/USIM personalisation cycle.....                     | 15        |
+| 8.2.1 Personalisation cycle .....                           | 15        |
+| 8.2.2 De-personalisation cycle .....                        | 16        |
+| 9 Over the air de-personalisation cycle.....                | 16        |
+| 10 Disable Personalisation.....                             | 17        |
+| 11 Manufacturer personalisation and de-personalisation..... | 17        |
+| 12 Automatic personalisation.....                           | 18        |
+| 13 Personalisation Cycle Restrictions.....                  | 18        |
+| 14 Security .....                                           | 18        |
+| <b>Annex A (normative): Technical information.....</b>      | <b>20</b> |
+| A.1 GID1 and GID2 files.....                                | 20        |
+| A.2 Emergency calls only mode .....                         | 20        |
+| A.3 Co-operative Network List.....                          | 21        |
+| A.4 Over-the-air de-personalisation.....                    | 21        |
+| Annex B (informative): Change history.....                  | 23        |
+
+# --- 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 provides functional specifications of five features to personalise Mobile Equipment (ME) for GSM and 3G systems. These features are called:
+
+- Network personalisation;
+- Network subset personalisation;
+- Service Provider (SP) personalisation;
+- Corporate personalisation;
+- SIM/USIM personalisation (SIM for GSM systems or USIM for 3G systems).
+
+The present document specifies requirements for MEs which provide these personalisation features.
+
+# --- 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.011: "Service accessibility".
+- [3] 3GPP TS 23.003: " Numbering, addressing and identification".
+- [4] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
+- [5] 3GPP TS 23.038: "Alphabets and language-specific information".
+- [6] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Point-to-Point (PP)".
+- [7] GSM 11.11: "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
+- [8] GSM 11.14: "Digital cellular telecommunications system (Phase 2+); Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
+- [9] 3GPP TS 31.102: "Characteristics of the USIM application".
+- [10] 3GPP TS 31.111: "USIM Application Tool Kit".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                          |
+|------|------------------------------------------|
+| CCK  | Corporate Control Key                    |
+| CNL  | Co-operative Network List                |
+| GID1 | Group Identifier (level 1)               |
+| GID2 | Group Identifier (level 2)               |
+| EF   | Elementary File                          |
+| IMEI | International Mobile Equipment Identity  |
+| IMSI | International Mobile Subscriber Identity |
+| MCC  | Mobile Country Code                      |
+| ME   | Mobile Equipment                         |
+| MS   | GSM Mobile Station (ME + SIM)            |
+| MNC  | Mobile Network Code                      |
+| NCK  | Network Control Key                      |
+| NSCK | Network Subset Control Key               |
+| PCK  | Personalisation Control Key              |
+| SIM  | Subscriber Identity Module               |
+| SMS  | Short Message Service                    |
+| SP   | Service Provider                         |
+| SPCK | Service Provider Control Key             |
+| TMSI | Temporary Mobile Subscriber Identity     |
+| UE   | 3G User Equipment (ME + USIM)            |
+| USIM | User Services Identity Module            |
+
+Further GSM abbreviations are given in TS 21.905 [1].
+
+## 3.2 Definitions
+
+For the purposes of the present document, the following definitions apply:
+
+**corporate personalisation:** Allows a corporate customer to personalise MEs that he provides for his employees or customers use so that they can only be used with the company's own SIM/USIMs.
+
+**de-personalisation:** Is the process of deactivating the personalisation so that the ME ceases to carry out the verification checks.
+
+**network personalisation:** Allows the network operator to personalise a ME so that it can only be used with that particular network operator's SIM/USIMs
+
+**network subset personalisation:** A refinement of network personalisation, which allows network operators to limit the usage of a ME to a subset of SIM/USIMs
+
+**normal mode of operation:** Is the mode of operation into which the ME would have gone if it had no personalisation checks to process.
+
+**personalisation:** Is the process of storing information in the ME and activating the procedures which verify this information against the corresponding information stored in the SIM/USIM whenever the ME is powered up or a SIM/USIM is inserted, in order to limit the SIM/USIMs with which the ME will operate.
+
+**SIM/USIM personalisation:** Enables a user to personalise a ME so that it may only be used with particular SIM/USIM(s).
+
+**SP personalisation:** Allows the service provider to personalise a ME so that it can only be used with that particular service provider's SIM/USIMs.
+
+**user:** Normally refers to the person performing the personalisation or de-personalisation operations and may represent a network operator, service provider, manufacturer of the user/owner of the handset, depending on the context.
+
+**network code:** MCC and MNC.
+
+**network subset code:** digits 6 and 7 of the IMSI.
+
+**SP code:** code which when combined with the network code refers to a unique SP. The code is provided in the GID1 file on the SIM/USIM (see Annex A.1.) and is correspondingly stored on the ME.
+
+**Corporate code:** code which when combined with the network and SP codes refers to a unique Corporate. The code is provided in the GID2 file on the SIM/USIM (see Annex A.1.) and is correspondingly stored on the ME.
+
+**SIM/USIM code:** code which when combined with the network and NS codes refers to a unique SIM/USIM. The code is provided by the digits 8 to 15 of the IMSI
+
+**network code group:** same as network code
+
+**network subset code group:** combination of a network subset code and the associated network code.
+
+**SP code group:** combination of the SP code and the associated network code.
+
+**Corporate code group:** combination of the Corporate code and the associated SP and network codes.
+
+**SIM/USIM code group:** combination of the SIM/USIM code and the associated network subset and network codes (it is equivalent to the IMSI).
+
+**Personalisation entity:** Network, network subset, SP, Corporate or SIM/USIM to which the ME is personalised
+
+# 4 General description
+
+The personalisation features work by storing information in the ME which limits the IMs with which it will operate, and by checking this information against the SIM/USIM whenever the ME is powered up or a SIM/USIM is inserted. If a check fails, the ME enters the "limited service state" in which only emergency calls can be attempted (see annex A.2).
+
+There are five personalisation categories of varying granularity; network, network subset, SP, corporate and SIM/USIM. The personalisation categories are independent in so far as each category can be activated or de-activated regardless of the status of the others. Each category has a separate personalisation indicator to show whether it is active or not. The ME can be personalised to one network, one network subset, one SP, one Corporate, one SIM/USIM or any combination thereof. The ME may optionally be personalised to multiple networks, network subsets, SPs, Corporates, IMs or any combinations thereof.
+
+The codes used for each personalisation category are shown in Table 1. Some categories require several codes (e.g. SP and network for SP personalisation) and each combination of codes relating to a particular entity (network, SP etc.) is referred to as a code group. To personalise to multiple entities, multiple code groups are stored in the ME. For each activated personalisation category, the ME retrieves the relevant codes from the SIM/USIM and checks the retrieved code group against the (list of) code group(s) stored in the ME. If a match is found with any of the code groups stored in the ME, the check is passed for that category. If checks for all active categories are passed, then the MS goes into normal operation.
+
+**Table 1: Codes used by each personalisation category**
+
+| Code                     | Network (MCC, MNC) | Network Subset (IMSI digits 6 and 7) | SP | Corporate | SIM/USIM (IMSI digits 8 to 15) |
+|--------------------------|--------------------|--------------------------------------|----|-----------|--------------------------------|
+| Personalisation category |                    |                                      |    |           |                                |
+| Network                  | ✓                  |                                      |    |           |                                |
+| Network subset           | ✓                  | ✓                                    |    |           |                                |
+| SP                       | ✓                  |                                      | ✓  |           |                                |
+| Corporate                | ✓                  |                                      | ✓  | ✓         |                                |
+| SIM/USIM                 | ✓                  | ✓                                    |    |           | ✓                              |
+
+Precautions must be taken to ensure that when more than one personalisation category is to be activated or when the ME is to be personalised to more than one entity of a personalisation category, the new codes are not in conflict with any existing valid codes. To avoid such conflicts, checks are carried out by the ME during the personalisation cycle, as described in clause 13.
+
+As an optional ME feature, the status (activated or not) of each personalisation category and the values of the relevant codes may be read by the user.
+
+# 5 Network personalisation
+
+## 5.1 Network personalisation
+
+Network personalisation allows a ME to be personalised to a particular network, for example to prevent the use of stolen MEs on other networks. The ME may optionally be personalised to more than one network.
+
+The ME is network personalised by storing the code (MCC+MNC) (see TS 23.003 [3]) of the relevant network(s) in the ME and setting a network personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the International Mobile Subscriber Identity (IMSI) is read from the SIM/USIM and the embedded network code (MCC+MNC) checked against that stored in the ME. If the values differ, the MS shall go into emergency calls only mode as defined in annex A.2.
+
+The network personalisation feature is controlled by a Network Control Key, (NCK) which has to be entered into the ME in order to network de-personalise it.
+
+In order to support the network personalisation feature the ME shall have storage for the network personalisation indicator, the network code(s) and the NCK.
+
+### 5.1.1 Operation of network personalised ME
+
+The network personalisation check described below is performed whenever a SIM/USIM is inserted or the ME is powered up with a SIM/USIM already in place.
+
+The personalisation check is as follows. When more than one personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks:
+
+- a) **check whether the ME is network personalised:** The ME checks its network personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the MS goes into the normal mode of operation, omitting the remaining steps of the check;
+- b) **check the network code(s):** The ME reads the IMSI from the SIM/USIM, extracts the network code from it and checks it against the (list of) value(s) stored on the ME.
+
+If no match is found in b), the ME may display an appropriate message, (e.g., "Incorrect SIM" or "Incorrect USIM") and shall go into the emergency calls only mode as defined in annex A.2. If a match is found, the MS goes into the normal mode of operation.
+
+### 5.1.2 Network personalisation cycle
+
+#### 5.1.2.1 Personalisation cycle
+
+The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the network personalisation indicator is set to "off". Access to the personalisation process shall be restricted in order to prevent unauthorised, accidental or unwanted personalisation. Other restrictions are described in clause 13. The personalisation process results in the NCK being set, the network personalisation indicator being set to "on" and the storage in the ME of the network code(s) to which the ME is being personalised.
+
+The network personalisation process is as follows:
+
+- a) The network code(s) are entered into the ME. This may be accomplished by one of the following means:
+  - for the case of a single network code, the ME reads the IMSI from the SIM/USIM and extracts the network code;
+  - the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the list of network code(s) associated with network personalisation;
+  - keypad entry;
+  - a manufacturer defined process.
+
+- b) The ME carries out the pre-personalisation checks contained in clause 13. If they all pass, the network code(s) are stored in the ME. If any fail, the personalisation process shall be terminated.
+- c) The NCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.
+- d) The network personalisation indicator is set to "on".
+
+#### 5.1.2.2 De-personalisation cycle
+
+To de-personalise the ME, the correct NCK shall be entered. It is optional whether or not a SIM/USIM is inserted in the ME. If a SIM/USIM is inserted, then de-personalisation shall be offered whether or not the network personalisation check passes or fails.
+
+Network subset de-personalisation shall be possible by keypad entry. If there is no keypad, then an alternative ME-based solution shall be provided. Other de-personalisation methods may also be provided such as a network initiated process whereby the control key is sent to the MS over-the-air (see clause 9).
+
+The network de-personalisation process is as follows:
+
+- a) the NCK is entered into the ME;
+- b) if the entered NCK is the same as the one stored in the ME the network personalisation indicator is set to "off".
+
+If the entered and stored NCK values differ, the de-personalisation process shall be stopped. The ME remains personalised and the stored network code(s) and NCK shall be left unchanged.
+
+## 5.2 Network subset personalisation
+
+Network subset personalisation is a refinement of network personalisation, which allows network operators to limit the usage of a ME to a well defined subset of IMs; e.g. where the ME is the property of a third party.
+
+The ME is network subset personalised by storing the network code and the Network Subset Code (digits 6 and 7 of the IMSI) as an identification of the network subset and setting an network subset personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the MS is powered up with a SIM/USIM already in place, the network subset code group is read from the SIM/USIM and checked against the stored values in the ME. If no match is found, the ME shall go into emergency calls only mode, as defined in annex A.2.
+
+The network subset personalisation feature is controlled by a Network Subset Control Key (NSCK) which has to be entered into the ME in order to network subset de-personalise it.
+
+In order to support the network subset personalisation feature, the ME shall have storage for the network subset personalisation indicator, the network subset code group(s) and the NSCK.
+
+### 5.2.1 Operation of Network subset personalised ME
+
+The Network subset personalisation check described below is performed whenever a SIM/USIM is inserted or the ME is powered up with a SIM/USIM already in place.
+
+The personalisation check is as follows. When more than one personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks.
+
+- a) **check whether the ME is network subset personalised:** The ME checks its network subset personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the ME goes into the normal mode of operation, omitting the remaining steps of the check;
+- b) **check network subset code group:** The ME reads the network subset code group from the SIM/USIM and checks it against the (list of) stored value(s) on the ME;
+
+If no match is found in b) the ME may display an appropriate message, (e.g. "Insert correct SIM") and shall go into emergency calls only mode, as defined in annex A.2. Otherwise the ME goes into the normal mode of operation.
+
+### 5.2.2 Network subset personalisation cycle
+
+#### 5.2.2.1 Personalisation Cycle
+
+The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the network subset personalisation indicator is set to "off". Access to the personalisation process shall be restricted in order to prevent unauthorised, accidental or unwanted personalisation. Other restrictions are described in clause 13. The personalisation process results in the NSCK being set, the network subset personalisation indicator being set to "on" and the storage in the ME of the (list of) network subset code group(s) which identify the specific network subset(s) to which the ME is being personalised.
+
+The network subset personalisation process is as follows:
+
+- a) The network subset code group(s) is (are) entered into the ME. This may be accomplished by one of the following means:
+  - for the case of a single network code group, the ME reads the IMSI from the SIM/USIM and extracts the network and network subset codes;
+  - the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the list of network subset code group(s);
+  - keypad entry;
+  - a manufacturer defined process.
+- b) The ME carries out the pre-personalisation checks contained in clause 13, on the new codes entered into the ME. If they all pass, the network subset code group(s) is (are) stored in the ME. If any fail, the personalisation process shall be terminated.
+- c) The NSCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.
+- d) The network subset personalisation indicator is set to "on".
+
+#### 5.2.2.2 De-personalisation cycle
+
+To de-personalise the ME the correct NSCK shall be entered. It is optional whether or not a SIM/USIM is inserted. If a SIM/USIM is inserted, then de-personalisation shall be offered whether or not the network subset personalisation check passes or fails.
+
+Network subset de-personalisation shall be possible by keypad entry. If there is no keypad, then an alternative ME-based solution shall be provided. Other de-personalisation methods may also be provided such as a network initiated process whereby the control key is sent to the MS over-the-air (see clause 9).
+
+The network subset de-personalisation process is as follows:
+
+- a) the NSCK is entered into the ME;
+- b) if the entered NSCK is the same as the one stored in the ME the network subset personalisation indicator is set to "off".
+
+If the entered and stored NSCK values differ, the de-personalisation process shall be stopped and the ME remain personalised. The stored network and network subset codes and the NSCK are left unchanged.
+
+# --- 6 SP personalisation
+
+Service provider or SP personalisation is a feature which allows a service provider to associate a ME with the SP. This feature only works with IMs which support the GID1 file. For the purpose of SP personalisation the GID1 file is programmed with an SP code that identifies the service provider.
+
+The ME is SP personalised by storing the SP code group(s) and setting a SP personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the SP code group is
+
+read from the SIM/USIM and checked against those stored in the ME. If no match is found the ME shall go into emergency calls only mode as defined in annex A.2.
+
+The SP personalisation feature is controlled by a Service Provider Control Key, (SPCK) which has to be entered into the ME in order to SP de-personalise it.
+
+In order to support the SP personalisation feature the ME shall have storage for the SP personalisation indicator, the (list of) SP code group(s) and the SPCK.
+
+## 6.1 Operation of SP personalised MEs
+
+The personalisation check described below is performed whenever a SIM/USIM is inserted or the ME is powered up with a SIM/USIM already in place.
+
+The personalisation check is as follows. When more than one personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks:
+
+- a) **check whether the ME is SP personalised:** The ME checks the SP personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the ME goes into its normal mode of operation;
+- b) **check whether the SIM/USIM supports GID1:** The ME checks that the SIM/USIM supports the GID1 file;
+- c) **check the SP code group:** The ME reads the SP code group from the SIM/USIM and checks it against the (list of) stored value(s) on the ME;
+
+If b) fails or no match is found in c), the ME may display an appropriate message (e.g. "insert correct SIM") and shall go into emergency calls only mode, as defined in annex A.2. Otherwise, the ME goes into the normal mode of operation.
+
+## 6.2 SP personalisation cycle
+
+### 6.2.1 Personalisation cycle
+
+The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the SP personalisation indicator is set to "off". Access to the personalisation process shall be restricted in order to prevent unauthorised, accidental or unwanted personalisation. Other restrictions are described in clause 13. The personalisation process results in the SPCK being set, the SP personalisation indicator being set to "on" and the storage in the ME of the (list of) SP code group(s) to which the ME is being personalised.
+
+The SP personalisation process is as follows:
+
+- a) The SP code group(s) is (are) entered into the ME. This may be accomplished by one of the following means:
+  - the ME checks that the SIM/USIM supports the GID1 file, if not the SP personalisation process is aborted with an appropriate error message. The ME reads the SP code group from the SIM/USIM. If the SP code is set to the default value (see annex A.1) then the personalisation process shall be aborted with an appropriate error message. Otherwise the SP code group is entered into the ME.
+  - the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the (list of) SP code group(s);
+  - keypad entry;
+  - a manufacturer defined process.
+- b) The ME carries out the pre-personalisation checks contained in clause 13 on the new codes entered into the ME. If they all pass, the SP code group(s) is (are) stored in the ME. If any fail, the personalisation process shall be terminated.
+- c) The SPCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process.
+- e) The SP personalisation indicator is set to "on".
+
+### 6.2.2 De-personalisation cycle
+
+To de-personalise the ME, the correct SPCK shall be entered. It is optional whether or not a SIM/USIM is inserted in the ME. If a SIM/USIM is inserted, then de-personalisation shall be offered whether or not the SP personalisation check passes or fails.
+
+SP de-personalisation shall be possible by keypad entry. If there is no keypad, then an alternative ME-based solution shall be provided. Other de-personalisation methods may also be provided such as a network initiated process whereby the control key is sent to the MS over-the-air (see clause 9).
+
+The SP de-personalisation process is as follows:
+
+- a) the SPCK is entered into the ME;
+- b) if the entered SPCK is the same as the one stored in the ME, the SP personalisation indicator is set to "off".
+
+If the entered and stored SPCK values differ, the de-personalisation process shall be stopped and the ME remains SP personalised. The stored network and SP codes and SPCK shall be left unchanged.
+
+# --- 7 Corporate personalisation
+
+Corporate personalisation is a refinement of SP personalisation which allows companies to prevent the use of MEs they provide for their employees or customers with other IMs without that corporate personalisation.
+
+This feature only works with IMs which support both the GID1 and GID2 files. For the purpose of corporate personalisation the GID1 file is programmed at pre-personalisation with an SP code that identifies the service provider and the GID2 file is programmed by the service provider or corporate customer with a code that identifies the corporate customer.
+
+The ME is corporate personalised by storing the corporate code group(s) and setting a corporate personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the corporate code group is read from the SIM/USIM and checked against those stored in the ME. If there is no match the ME shall go into emergency calls only mode, as defined in annex A.2.
+
+The corporate personalisation feature is controlled by a Corporate Control Key (CCK), which has to be entered into the ME in order to de-personalise it.
+
+In order to support the corporate personalisation feature the ME shall have storage for the corporate personalisation indicator, a (list of) corporate code group(s) and the CCK.
+
+## 7.1 Operation of corporate personalised MEs
+
+The personalisation check described below is performed whenever a SIM/USIM is inserted or the ME is powered up with a SIM/USIM already in place.
+
+The personalisation check is as follows. When more than one personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks:
+
+- a) **check whether the ME is corporate personalised:** The ME checks the corporate personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the ME goes into its normal mode of operation;
+- b) **check whether the SIM/USIM supports GID1 and GID2:** The ME checks that the SIM/USIM supports the GID1 and GID2 files;
+- c) **check the corporate code group:** The ME reads the corporate code group from the SIM/USIM and checks it against the (list of) stored value(s) on the ME;
+
+If b) fails, or no match is found in c), the ME may display an appropriate message (e.g. "Insert correct SIM") and shall go into emergency calls only mode, as defined in annex A.2. Otherwise, the ME goes into the normal mode of operation.
+
+## 7.2 Corporate personalisation cycle
+
+### 7.2.1 Personalisation cycle
+
+The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the corporate personalisation indicator is set to "off". Access to the personalisation process shall be restricted in order to prevent unauthorised, accidental or unwanted personalisation. Other restrictions are described in clause 13. The personalisation process results in the CCK being set, the corporate personalisation indicator being set to "on" and the storage in the ME of a (list of) corporate group(s) codes to which the ME is being personalised.
+
+The corporate personalisation process is as follows:
+
+- a) The corporate code group(s) is (are) entered into the ME. This may be accomplished by one of the following means:
+  - the ME checks that the SIM/USIM supports the GID1 and GID2 files, if not the corporate personalisation process shall be aborted with an appropriate error message;  
+the ME reads the corporate code group(s) from the SIM/USIM. If either the SP code or the corporate code is set to the default value (see Annex A.1), then the corporate personalisation process shall be aborted with an appropriate error message. Otherwise the corporate code group is entered into the ME;
+  - the ME reads the Co-operative Network List (CNL) from the SIM/USIM and extracts the (list of) Corporate code group(s);
+  - keypad entry;
+  - a manufacturer defined process.
+- b) The ME carries out the pre-personalisation checks contained in clause 13 on the new codes entered into the ME. If they all pass, the corporate code group(s) are stored in the ME. If any fail, the personalisation process shall be terminated.
+- c) The CCK is stored in the ME. This may be entered via the keypad by the user or by a manufacturer defined process;
+- d) The corporate personalisation indicator is set to "on".
+
+### 7.2.2 De-personalisation cycle
+
+To de-personalise the ME the correct CCK shall be entered. It is optional whether or not a SIM/USIM is inserted in the ME. If a SIM/USIM is inserted, then de-personalisation shall be offered whether or not the corporate personalisation check passes or fails.
+
+The corporate de-personalisation shall be possible by keypad entry. If there is no keypad, then an alternative ME-based solution shall be provided. Other de-personalisation methods may also be provided such as a network initiated process whereby the control key is sent to the MS over-the-air (see clause 9).
+
+The corporate de-personalisation process is as follows:
+
+- a) the CCK is entered into the ME;
+- b) if the entered CCK is the same as the one stored in the ME, the corporate personalisation indicator is set to "off".
+
+If the entered and stored CCK values differ the de-personalisation process shall be stopped and the ME remains corporate personalised. The stored network operator, SP and corporate codes and CCK are left unchanged
+
+# --- 8 SIM/USIM personalisation
+
+SIM/USIM personalisation is an anti-theft feature. When a ME is SIM/USIM personalised to a particular SIM it will refuse to operate with any other SIM/USIM. Hence, if the ME is stolen the thief will not be able to use it with another SIM/USIM (see note). While this does not stop the ME being stolen it should make it less attractive to the thief.
+
+NOTE: If the ME and the SIM/USIM to which it has been personalised are stolen together the ME would become unusable once the SIM/USIM is reported stolen and is disconnected.
+
+The ME is SIM/USIM personalised by storing the SIM/USIM code group (which is equivalent to the IMSI) of the relevant SIM/USIM in the ME and setting the SIM/USIM personalisation indicator in the ME to "on". Whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the SIM/USIM code group (IMSI) is read from the SIM/USIM and checked against the SIM/USIM code group(s) stored in the ME. If there is no match the ME shall go into emergency calls only mode as described in annex A.2.
+
+The SIM/USIM personalisation feature is controlled by a Personalisation Control Key (PCK). This key is selected by the user at SIM/USIM personalisation and shall be entered into the ME to SIM/USIM de-personalise the ME.
+
+In order to support the SIM/USIM personalisation feature the ME should have storage for the SIM/USIM personalisation indicator, a (list of) SIM/USIM code group(s) and the PCK.
+
+Multiple instances of SIM/USIM personalisation can be supported, i.e. whenever a SIM/USIM is inserted, or the ME is powered up with a SIM/USIM already in place, the IMSI is read from the SIM/USIM and checked against a list of SIM/USIM code groups stored in the ME.
+
+## 8.1 Operation of SIM/USIM personalised ME
+
+The SIM/USIM personalisation check described below is performed whenever a SIM/USIM is inserted or the ME is powered up with a SIM/USIM already in place.
+
+The personalisation check is as follows. When more than one personalisation is active in the ME, normal mode of operation includes performing any outstanding personalisation checks:
+
+- a) **check whether the ME is SIM/USIM personalised:** The ME checks its SIM/USIM personalisation indicator, if it is set to "off" the personalisation check shall be stopped and the ME goes into the normal mode of operation, omitting the remaining steps of the check;
+- b) **read IMSI:** The ME reads the IMSI from the SIM/USIM;
+- c) **SIM/USIM personalisation check:** The ME checks the read IMSI against the (list of) SIM/USIM code group(s) stored in the ME. If no match is found, the ME shall display an appropriate message (e.g. "Insert correct SIM" or "Insert correct USIM") and shall go into emergency calls only mode as described in annex A.2. Otherwise, the ME goes into the normal mode of operation.
+
+## 8.2 SIM/USIM personalisation cycle
+
+### 8.2.1 Personalisation cycle
+
+The process of personalisation can only be carried out on a currently unpersonalised ME, i.e., if the SIM/USIM personalisation indicator is set to "off". Access to the personalisation process shall be restricted in order to prevent unauthorised, accidental or unwanted personalisation. Other restrictions are described in clause 13. The personalisation process results in the PCK being set, the SIM/USIM personalisation indicator being set to "on" and the storage in the ME of a (list of) SIM/USIM code group(s) to which the ME is being personalised.
+
+The SIM/USIM personalisation process is as follows:
+
+- a) the SIM/USIM code group(s) is (are) entered into the ME. This may be accomplished by one of the following means :
+  - the ME reads the SIM/USIM code group (IMSI) from the SIM/USIM and stores it;
+  - a manufacturer defined process.
+- b) the ME carries out the pre-personalisation checks contained in clause 13. If they all pass, the SIM/USIM code group(s) is(are) stored in the ME. If any fail, the personalisation process shall be terminated;
+- c) to personalise the ME to more than one SIM/USIM and if the reading of the IMSI from the SIM/USIM is used to enter the SIM/USIM code group in the ME, the procedures given in a) and b) shall be repeated;
+
+- d) the PCK is then stored in the ME. A single value of PCK shall be used for both single and multiple SIM/USIM personalisation;
+- e) the SIM/USIM personalisation indicator is set to "on".
+
+### 8.2.2 De-personalisation cycle
+
+To de-personalise the ME, the correct PCK shall be entered. It is optional whether or not a SIM/USIM is inserted in the ME. If a SIM/USIM is inserted, then de-personalisation shall be offered whether or not the SIM/USIM personalisation check passes or fails.
+
+SIM/USIM de-personalisation shall be provided by keypad entry. Other de-personalisation methods may also be provided.
+
+The SIM/USIM de-personalisation process is as follows:
+
+- a) the user enters the PCK in the ME;
+- b) if the entered PCK is the same as the one stored in the ME, the SIM/USIM personalisation indicator is set to "off".
+
+If the entered and stored PCK values differ, the de-personalisation process shall be stopped and the ME remain personalised. The stored IMSI and PCK are left unchanged.
+
+# --- 9 Over the air de-personalisation cycle
+
+As an optional ME feature, the ME may be de-personalised over-the-air (OTA) by the network. The network, network subset, SP and corporate categories may be de-personalised in this way. More than one category may be de-personalised at the same time. The process results in the relevant personalisation indicator(s) being set to "off". The ME must be registered on a network.
+
+Two OTA methods are defined both of which use MT SMS-PP messages. With the first method, the IMEI of the ME to be de-personalised and the Control Key(s) of the personalisation categories to be de-personalised are sent directly to the ME. The ME performs checks on both the IMEI and the key values and the outcome of the attempted de-personalisation(s) is acknowledged to the network.
+
+With the second method, the keys of the personalisation categories to be de-personalised are sent to the ME via the SIM/USIM. The IMEI is not included and the de-personalisation process only checks the keys. The outcome of the attempted de-personalisation(s) is acknowledged to the network.
+
+The network de-personalises the ME by one of the following methods:
+
+### (i) SMS-PP, ME-specific:
+
+- a) A point-to-point SMS message is sent by the network to the MS or UE, the message being marked as being destined for the ME only and for the purposes of ME de-personalisation (see TS 23.040 [6]). The User Data of the SMS contains the de-personalisation key(s) and the IMEI (see annex A.4). If the ME supports the feature, then it shall not display the data on the ME.
+- b) The ME compares the values of the IMEI and the key(s) sent by the network with the corresponding values stored in the ME. If they are the same, the relevant personalisation indicator(s) is (are) set to "off".
+
+If the IMEI values differ, the personalisation status of all categories shall be left unchanged.
+
+If any key values differ, the corresponding personalisation status shall be left unchanged.
+
+- c) The MS or UE sends a SMS acknowledgement to the network indicating the result of the attempted de-personalisation process (see annex A.4).
+
+### (ii) SMS-PP Data Download:
+
+- a) A SMS message is sent by the network to the IM updating the EF<sub>DCK</sub>. In the GSM system, it is done by using the SMS-PP SIM Data Download of the SIM Tool Kit (see GSM 11.14 [8]). In the 3G system, it is done by using the SMS-PP Data Download of the USIM Toolkit (see TS 31.111 [10]).
+
+- b) The SIM/USIM causes the ME to send an SMS acknowledgement to the network, as a result of the terminal response to the ENVELOPE command.
+- c) The SIM/USIM shall issue a REFRESH command to instruct the ME to perform an initialisation procedure. During the initialisation procedure the ME reads the de-personalisation key field(s) from EF<sub>DCK</sub> stored in the SIM/USIM after performing all personalisation checks.
+- d) For each control key in EF<sub>DCK</sub> which is empty (set to default), the corresponding personalisation status shall be left unchanged.
+- e) For each control key in the EF<sub>DCK</sub> which is not the same as the corresponding stored key, the personalisation status shall be left unchanged.
+- f) For each control key in EF<sub>DCK</sub> which is the same as the one stored in the ME, the corresponding personalisation indicator is set to "off".
+- g) All the keys in the EF<sub>DCK</sub> are reset to the default value by the ME.
+
+# --- 10 Disable Personalisation
+
+There shall be a means to disable the personalisation at each level individually such that the ME shall operate with any (i.e. all) SIM/USIM at that level.
+
+The process of disable-personalisation can only be carried out on a currently unpersonalised ME, i.e., if the personalisation indicator for that level is set to "off". It results in the personalisation indicator remaining set to "off". When a particular level is disabled in this manner there shall be a means to make it impossible to change this status i.e. the disable becomes irreversible thus eliminating the need for key-administration.
+
+# --- 11 Manufacturer personalisation and de-personalisation
+
+Manufacturers may enter into private arrangements to personalise MEs before delivery or at other times. They may also have the capability to de-personalise/reset MEs for example, when a ME needs repairing, when the relevant control key has been forgotten or lost or if the ME has been blocked as a result of excessive failed attempts at de-personalisation.
+
+In all cases, secure arrangements shall be followed with the transfer and handling of the critical data such as the IMSI and the associated control keys.
+
+In common with the normal de-personalisation processes, the manufacturer controlled processes should be secure and be key or password controlled.
+
+# --- 12 Automatic personalisation
+
+ME manufacturers may offer alternative means of personalizing the ME such as adding functionality to the ME so that it automatically personalises itself to the first IM inserted in it, using one or more of the five personalisation levels described in clauses 5 to 8. In the case of SP and corporate personalisation, this is subject to the SIM/USIM supporting GID1 and GID2 (as required) and the contents of those files being non-default.
+
+# --- 13 Personalisation Cycle Restrictions
+
+Security mechanisms shall be implemented to ensure that additions or changes to any personalisation category shall only be made by persons authorised to do so for that category (see Section 14).
+
+During the Personalisation cycle of a category, before any changes are made to the existing personalisation data, it shall be checked that :
+
+- the category to be personalised is not currently activated;
+- the new codes to be stored are a subset of the existing codes.
+
+(e.g. for a ME which is already network-personalised with the network code N1 and that is to be personalised for the SP category, N1-SP1 can be added but N2-SP2 cannot be added).
+
+NOTE 1: If no personalisation category are active, then no checks are necessary.
+
+NOTE 2: If the entities of an active personalisation category are to be modified, then this shall only be possible if the personalisation category is first de-personalised by means of the appropriate Control Key.
+
+NOTE 3: After each personalisation cycle, the number of SIM/USIMs with which the ME can operate decreases. If further personalisation cycles of specific personalisation categories are to be prevented, the disable-personalisation feature can be used (see clause 10).
+
+# --- 14 Security
+
+This clause lists a number of security requirements which should be satisfied if the personalisation features are to be effective. The requirements are not arranged in any particular order.
+
+- a) The control keys shall be decimal strings with an appropriate number of digits for the level of personalisation. PCK should be at least 6 digits, and the remaining control keys at least 8 digits in length. The maximum length for any control key is 16 digits.
+- b) Where more than one of the personalisation features are in use, distinct control keys should be used for the different features.
+- c) The NCK, NSCK, SPCK and CCK should be randomly selected or pseudo-randomly generated and differ from ME to ME.
+- d) The PCK should be randomly selected for each ME. In particular, subscribers should be strongly encouraged not to use obvious values such as part of the dialling number.
+- e) It should be impractical to read or recover any of the control keys from the ME.
+- f) It should be impractical to alter or delete the values of the personalisation indicators, the control keys, the stored IMSI or the stored network operator, SP and corporate codes, other than by the defined personalisation and de-personalisation processes, without completely disabling the ME from working with any SIM/USIM. (Possible methods that might be used by criminals to alter or delete the values include freezing, baking, exposure to magnetic fields or UV light.)
+- g) For each de-personalisation procedure, there shall be a mechanism to prevent unauthorised attempts to de-personalise the ME. These may include blocking the ME if the number of failed attempts to de-personalise the ME exceeds a certain limit, or alternatively introducing an increasing delay after each successive failed de-personalisation attempt. Other mechanisms may be also be used.
+- h) The SIM/USIM personalisation feature will only succeed in discouraging thieves if they know or suspect that the ME is SIM/USIM personalised. Therefore, unless and until SIM/USIM personalised MEs become the norm, it is desirable that the ME should advertise the fact that it is SIM/USIM personalised.
+- i) Manufacturers should not de-personalise a ME for a user unless they have obtained the appropriate level of approval, e.g., from the network operator for network personalisation, from the service provider for service provider personalisation, etc.
+- j) ME manufacturers should ensure that the personalisation processes (except for SIM/USIM personalisation) are protected against unauthorised, accidental or malicious operation.
+
+# --- Annex A (normative): Technical information
+
+## A.1 GID1 and GID2 files
+
+The GID1 and GID2 elementary files on the SIM are specified in GSM 11.11 (ETS 300 977) [7].
+
+The GID1 and GID2 elementary files on the USIM are specified in TS 31.102 [9].
+
+For the purposes of this TS, a SIM/USIM is said to support one of these two files if it is marked as both allocated and activated in the SIM/USIM service table.
+
+The SP and corporate codes are stored in byte 1 of the appropriate files.
+
+If byte 1 contains a hexadecimal value between "00" and "FE" inclusive, then this represents the SP/corporate code in the GID1/GID2 files respectively. For the purpose of these personalisation features, the ME shall ignore the contents of any other bytes of the file.
+
+The value "FF" is the default value to be used in byte 1 when no meaningful SP/corporate code is represented in the GID1/GID2 files respectively. This value shall not be allocated as an SP/corporate code.
+
+Note that network operators would normally allocate SP codes for its service providers and SPs would normally allocate corporate codes for its corporate customers.
+
+## --- A.2 Emergency calls only mode
+
+The expression "emergency calls only mode" is used in this TS to describe the state the MS (combined ME and SIM) or US (combined ME and USIM) enters when a personalisation check fails. In this mode, the state of the MS/UE is equivalent to the "limited service state" (see TS 23.122) [4]. Although the personalisation has failed, the ME will be able to access the TMSI and IMSI from the SIM/USIM, and therefore any emergency call request shall use these as the MS/UE identity.
+
+Set up of emergency calls remains as usual dependent on the status of Access Class 10 being broadcast in the cell (see TS 22.011) [2].
+
+## A.3 Co-operative Network List
+
+The Co-operative Network List is specified in GSM 11.11 (ETS 300 977) [7].
+
+For the purposes of this TS, a SIM is said to support this feature if it is marked as both allocated and activated in the SIM service table.
+
+The value "FF" is the default value to be used when no meaningful code is represented. This value shall not be allocated as a code value.
+
+## A.4 Over-the-air de-personalisation
+
+- a) The ME-specific de-personalisation SMS messages sent by the network to de-personalise the ME shall be coded according to TS 23.040 [6]. If length of every key does not exceed 8 digits, the TP-UD field shall be coded as follows:
+
+| Character | Description                                                |
+|-----------|------------------------------------------------------------|
+| 1 - 40    | Operator specific text padded with spaces to character 40. |
+| 41 - 48   | Network control key                                        |
+| 49 - 56   | Network subset control key                                 |
+| 57 - 64   | SP control key                                             |
+| 65 - 72   | Corporate control key                                      |
+| 73 - 88   | IMEI                                                       |
+
+If length of one or more keys exceed 8 digits the message in TP-UD field shall be extended with additional 32 digits as follows:
+
+|         |                                      |
+|---------|--------------------------------------|
+| 89-96   | Network control key extension        |
+| 97-104  | Network subset control key extension |
+| 105-112 | SP control key extension             |
+| 113-120 | Corporate control key extension      |
+
+The key shall be divided into main and extension fields as follows:
+
+- If key length is equal to or less than 8 digits, the key value shall be coded to the main field as specified above, and the corresponding extension field shall be encoded as "FFFFFFFF".
+- If key length is more than 8 digits, the 8 most significant digits shall be coded to the main field and the remaining digits shall be coded to the extension field. If the length of the key is less than 16 digits, then extension field shall be populated from the beginning of the extension field, and each of the remaining digits shall be encoded as "F".
+
+NOTE: If the key value is "12345678901234", then the main field value will contain the string "12345678" and the extension field "901234FF".
+
+If an ME receives a key value with "F" padding, it shall ignore the "F" padding characters and only use the received key part.
+
+As the IMEI is 15 digits long (see TS 23.003 [3]), the sixteenth digit present here is ignored by the ME during the de-personalization procedure and should be set to zero.
+
+For the IMEI and each control key, the most significant digit is coded first in the string, e.g. character 41 is the most significant digit of NCK.
+
+All characters are coded according to the default alphabet described in TS 23.038 [5].
+
+The string "FFFFFFFF" shall be used in place of a key to indicate that de-personalisation of that category is not required.
+
+- b) The acknowledgement to the ME De-personalisation Short Message shall be a SMS-DELIVER-REPORT for RP-ACK as described in TS 23.040 [6] with the TP-User-Data coded according to the default alphabet described in TS 23.038 [5] as below:
+
+| Character | Description                           |
+|-----------|---------------------------------------|
+| 1-16      | IMEI of ME                            |
+| 17        | Network personalisation status        |
+| 18        | Network subset personalisation status |
+| 19        | SP personalisation status             |
+| 20        | Corporate personalisation status      |
+
+As the IMEI is 15 digits long (see TS 23.003 [3]), the sixteenth digit present here is ignored by the network during the de-personalization procedure and should be set to zero.
+
+Status codes shall indicate the resulting status of each personalisation category as below.
+
+| Status code | Description                  |
+|-------------|------------------------------|
+| 0           | Currently not personalised   |
+| 1           | Permanently not personalised |
+| 2           | Personalised                 |
+| 3           | IMEI mismatch                |
+| Other       | RFU                          |
+
+If the IMEI of the ME does not match the IMEI included in the De-personalisation Short Message, then the status of all the personalisation categories shall be coded "IMEI mismatch".
+
+- c) The format for the control keys stored on the SIM is specified in GSM 11.11 [8]. The format for the control keys stored on the USIM is specified in TS 31.102 [9].
+
+For the purposes of this TS, a SIM/USIM is said to support this feature if it is marked as both allocated and activated in the SIM/USIM service table.
+
+The value "FF" is the default value to be used when no meaningful value for a key is represented. This value shall not be allocated as a key value.
+
+# Annex B (informative): Change history
+
+| Change history |           |     |     |       |     |                                                                                                 |        |        |      |
+|----------------|-----------|-----|-----|-------|-----|-------------------------------------------------------------------------------------------------|--------|--------|------|
+| TSG SA#        | SA Doc.   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                                 | Old    | New    | WI   |
+| SP-16          | SP-020339 | 004 | -   | Rel-4 | A   | IMEI format for de-personalisation over the air                                                 | 4.0.0  | 4.1.0  | SEC1 |
+| SP-17          | -         | -   | -   | -     | -   | Upgrade to Release 5                                                                            | 4.1.0  | 5.0.0  | -    |
+| SP-26          | -         | -   | -   | -     | -   | Upgrade to Release 6                                                                            | 5.0.0  | 6.0.0  | -    |
+| SP-36          | -         | -   | -   | -     | -   | Upgrade to Release 7                                                                            | 6.0.0  | 7.0.0  | -    |
+| SP-39          | SP-080194 | 005 | 3   | Rel-7 | F   | Control key length increase in OTA de-personalisation message                                   | 7.0.0  | 7.1.0  | TEI7 |
+| SP-40          | SP-080419 | 006 | 1   | Rel-7 | F   | Completion of sentence concerning control key length increase in OTA de-personalisation message | 7.1.0  | 7.2.0  | TEI7 |
+| SP-42          | -         | -   | -   | -     | -   | Upgrade to Release 8                                                                            | 7.0.0  | 8.0.0  | -    |
+| SP-46          | -         | -   | -   | -     | -   | Upgrade to Release 9                                                                            | 8.0.0  | 9.0.0  | -    |
+| SP-48          | SP-100397 | 008 | -   | Rel-9 | A   | Correction of Reference                                                                         | 9.0.0  | 9.1.0  | TEI8 |
+| 2011-03        | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                                                  | 9.1.0  | 10.0.0 |      |
+| 2012-09        | -         | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                                                  | 10.0.0 | 11.0.0 |      |
+| 2014-10        | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                                                  | 11.0.0 | 12.0.0 |      |
+| 2015-12        |           |     |     |       |     | Update to Rel-13 version (MCC)                                                                  | 12.0.0 | 13.0.0 |      |

marked/Rel-13/22_series/22024/raw.md

@@ -0,0 +1,438 @@
+
+
+## **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **3GPP TS 22.024 v9.0 (2010-01)** **Description of Charge Advice Information (CAI)** *Technical Specification* **(Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a small "TM" symbol. Above the "e" and "Advanced Pro" text is a green signal strength icon consisting of four curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top. Below the "P" is a red signal strength icon consisting of three curved lines of increasing height. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, charging
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                         |    |
+|---------------------------------------------------------|----|
+| Foreword .....                                          | 4  |
+| 1 Scope.....                                            | 5  |
+| 1.1 References .....                                    | 5  |
+| 1.2 Definitions and abbreviations.....                  | 5  |
+| 2 Introduction.....                                     | 6  |
+| 3 Charge Advice Information .....                       | 7  |
+| 4 Functional operation in MS.....                       | 8  |
+| 4.1 Handling of the CAI elements.....                   | 8  |
+| 4.2 Handling of call meters .....                       | 9  |
+| 4.2.1 The Current Call Meter (CCM).....                 | 9  |
+| 4.2.2 The Accumulated Call Meter (ACM).....             | 9  |
+| 4.2.3 The ACM Maximum Value (ACMmax).....               | 10 |
+| 4.2.4 The Price per Unit and Currency Table (PUCT)..... | 10 |
+| 4.3 Special processing.....                             | 10 |
+| 4.4 Interactions with SCUDIF supplementary service..... | 11 |
+| 5 Functional operation in PLMN .....                    | 11 |
+| 5.1 Outgoing calls .....                                | 11 |
+| 5.2 Incoming calls .....                                | 11 |
+| 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.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The charging supplementary service is described in TS 22.086 [2]. These services are designed to supply to a mobile user sufficient information to allow a real-time estimate to be made of the bill which will eventually be levied in the home PLMN on the Mobile Station (MS) subscriber.
+
+In the case of certain MS uses, for example a mobile payphone, this estimate could be subject to further processing (e.g. to present the charges in currency, rather than units, this may include an additional mark up). This additional processing is not described in this document in order to avoid constraining the evolution of the MS product in this area.
+
+This document gives an overall view of how this supplementary service shall operate both in the PLMN and within the MS. Text given in this document is required to define functionality and is not intended to constrain implementation.
+
+## 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.086: "Advice of Charge (AoC) Supplementary Services - Stage 1".
+
+[3] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2".
+
+## 1.2 Definitions and abbreviations
+
+In addition to the following, abbreviations used in the present document are listed in TS 21.905 [1].
+
+### **Mark up (MU):**
+
+An increase over the basic charge e.g. to provide extra revenue or to cover additional costs.
+
+### **Service Provider (SP):**
+
+The organization through which the subscriber obtains PLMN services. This may be the network operator or possibly a separate body.
+
+### **Home Units (HU):**
+
+The published basic telecommunication unit as published by the HPLMN. This has a published value expressed in the currency of the Home country.
+
+### **Local PLMN (LPLMN):**
+
+The LPLMN is the HPLMN or VPLMN depending on the location of the MS at the time and is the PLMN with which the MS is interworking via the radio interface.
+
+### **Local Units (LU):**
+
+The published basic telecommunication unit as published by the LPLMN. This has a published value expressed in the currency of the local country.
+
+### **Price per Unit and Currency Table (PUCT):**
+
+The PUCT is the value of the Home unit in a currency chosen by the subscriber. The PUCT is stored in the SIM. The value of the PUCT can be set by the subscriber and may exceed the value published by the HPLMN. The PUCT value does not have any impact on the charges raised by the HPLMN.
+
+### **Current Call Meter (CCM):**
+
+The accumulated charge as computed by the MS, expressed in terms of Home units.
+
+### **Accumulated Call Meter (ACM):**
+
+The accumulated charge for both the current call and all preceding calls as computed by the MS, expressed in terms of Home units. The ACM is stored in the SIM/USIM.
+
+### **ACM Maximum value (ACMmax):**
+
+The ACMmax sets the upper limit for the ACM. The ACMmax is stored in the SIM/USIM. The value of the ACMmax can be set by the subscriber.
+
+### **Charging point (CHP):**
+
+The time at which charging commences i.e. at the point when the called party answers or the equivalent.
+
+### **End of charge point (CEND):**
+
+The time at which the calling, or called, party stops charging by the termination of the call or by an equivalent procedure invoked by the network or by failure of the radio path.
+
+### **Advice of Charge (AOC):**
+
+The charge as computed by the MS, expressed in terms of Home Units.
+
+### **Segment:**
+
+A charging element as defined by ITU-T, in octets (up to 64).
+
+# --- 2 Introduction
+
+The principle of this service is that the MS shall be capable of indicating the cost of a call in home units as a basic service. This is the Advice of Charge (AOC).
+
+The ability for the MS to perform further processing on AOC is not precluded. If the subscriber wishes, the MS shall indicate the value of CCM, ACM, ACMmax in the currency she has indicated using the PUCT.
+
+At the charging point, the MS is informed of the charging rate.
+
+The MS shall then use its independent internal clock to time the call from the charging point to the end of call i.e. the chargeable duration (CDUR) is measured by the MS. In the case of multiple calls this applies separately for each call (see subclause 4.3 l). The time taken attempting to perform call reestablishment is not included in CDUR (see subclause 4.3 m).
+
+By using the calculations described in clause 4, the MS shall be able to derive the number of home units used.
+
+Due to the independence of the calculated value, an exact one-to-one relation with the bill cannot be guaranteed. This discrepancy is due to the short delays in signalling between the MS and the network, e.g. transmission of charging point and end of call signals.
+
+In deriving the present document the following principles are assumed:
+
+- i) For mobile originated calls, the mobile user pays for the connection to the dialled number, as per the published tariff of the Local PLMN, plus a mark-up defined by the HPLMN to cover additional administration costs, when roaming.
+
+It is assumed that the MS subscriber will **not** be charged for the forwarded leg if the dialled number has set call forwarding. If additional charging is required for this forwarded leg, then it is assumed that such charging will be applied only to the called party. This follows current telecommunications practice.
+
+- ii) For mobile terminated calls, any charge set for incoming calls is that based on the tariff as published by the HPLMN.
+
+The tariff as published for the roaming extension charges is assumed to be time and date invariant. For the avoidance of doubt, this assumption does not preclude routine tariff changes.
+
+- iii) Charge rates for calls originating within a PLMN vary depending upon, for example, location, destination, service, time of day, type of day and any mark ups.
+
+- iv) The units indicated in the advice of charge are always given in terms of Home units, the value of which is defined and published by the HPLMN, regardless of the PLMN in which they were incurred or the call direction or the type of call including supplementary service and data calls.
+
+# 3 Charge Advice Information
+
+The MS is supplied with the necessary Charge Advice Information (CAI) at the charging point on a per call basis, in a signalling message over the radio interface.
+
+The MS uses the CAI elements to compute the AOC value for the relevant call. Thus the signalling CAI not only provides charging information, but indicates the charging point and hence initiates the timing of the chargeable duration.
+
+The information sent to the MS from the MSC consists of seven elements as follows:
+
+**Table 1: Information elements**
+
+| Element | Dimensions | Description             | MIN | MAX   | RES  |
+|---------|------------|-------------------------|-----|-------|------|
+| e1      | u/i        | Units per interval      | 0   | 819.1 | 0.1  |
+| e2      | t/i        | Seconds/time interval   | 0   | 819.1 | 0.1  |
+| e3      | -          | Scaling Factor          | 0   | 81.91 | 0.01 |
+| e4      | u          | Unit increment          | 0   | 819.1 | 0.1  |
+| e5      | u/d        | Units per data interval | 0   | 819.1 | 0.1  |
+| e6      | seg/d      | Segments/data interval  | 0   | 8191  | 1    |
+| e7      | t/i        | Initial secs/t interval | 0   | 819.1 | 0.1  |
+
+where:
+
+u = units; t = time; i = interval; seg = segments; d = data interval.
+
+The CAI Message need only contain those elements required for the particular situation. If elements are missing from the initial CAI message of a call, they shall be treated as zero.
+
+## Element e1 -
+
+This element defines the number of units incremented per interval. It is set in terms of LPLMN units/interval to a resolution as defined in the table above under RES.
+
+## Element e2 -
+
+This element defines the time interval for unitization, and is specified in seconds, to a resolution as defined in the table above under RES.
+
+## Element e3 -
+
+This element defines the scaling factor to convert from LPLMN units to HPLMN units. It is a dimensionless multiplier given to a resolution as defined in the table above under RES.
+
+## Element e4 -
+
+This element defines the number of units to be incremented on receipt of the message containing the CAI elements. It is specified in units of the LPLMN to a resolution as defined in the table above under RES.
+
+## Element e5 -
+
+This element defines the number of units incremented per data interval. It is set in terms of HPLMN units/interval, to a resolution as defined in the table above under RES.
+
+## **Element e6 -**
+
+This element defines the data usage interval for unitization, and is specified in segments (SEG), to a resolution as defined in the table above under RES., for Dedicated Access to the PSPDN (whether directly or via Dedicated PAD). It does not apply to circuit switched access to modems or PADs, (except Dedicated PAD's) or MS to MS calls.
+
+## **Element e7 -**
+
+This element defines the initial time interval for unitization, and is specified in seconds, to a resolution as defined in the table above under RES.
+
+# 4 Functional operation in MS
+
+Simple operation in the MS is described by the equation:-
+
+$$\begin{aligned} \text{AoC} &= e3 * \{ e4 + e1 * \text{INT}(\text{CDUR}/(e7,e2)) + e5 * \text{INT}(\text{SEG}/e6) \} \\ &= \text{scaling} * \{ \text{constant} + \text{time related} + \text{data related} \} \end{aligned}$$
+
+where:
+
+AoC is the Advice of Charge in home units.
+
+CDUR is the Chargeable DURATION as measured by the MS.
+
+SEG is the SEGment count as counted by the MS.
+
+INT(v) is the function to take the INTEGER value of v.
+
+\* indicates multiply operator.
+
+e7,e2 indicate first e7 then e2 selected as described below.
+
+## 4.1 Handling of the CAI elements
+
+For the detailed mechanisms, the conditions given under subclause 4.3 (Special Processing) must be observed. The following therefore describes the process for a simple single call scenario, for either an incoming or outgoing call for the MS in any PLMN, including HPLMN:-
+
+On receipt of the CAI message, charging computation commences.
+
+### **INITIAL/FIXED CHARGE:**
+
+Element e4\*e3 defines the number of HPLMN units to be incremented in the Current Call Meter (CCM, see below) on receipt of the CAI message.
+
+### **INITIAL TIME RELATED CHARGE:**
+
+On first receipt of the CAI message, timing commences immediately and MS timer CDUR is incremented, from zero, with a precision of at least 0.1 seconds. When CDUR reaches e7 (see special processing for the case where e7 is equal to zero) i.e. a full interval has been timed, then e1\*e3 HPLMN units are added to the CCM. CDUR is then reset to zero to allow timing of the next interval to commence based on CAI element e2. Element e7 is not used further, unless it is updated via a new CAI message.
+
+### **TIME RELATED CHARGE:**
+
+On expiry of the interval defined by e7; e2 is applied and timing re-commences immediately. MS timer CDUR is incremented, from zero, with a precision of at least 0.1 seconds. When CDUR reaches e2 i.e. a full interval has been timed, then e1\*e3 HPLMN units are added to the CCM. CDUR is then reset to zero to allow timing of the next interval to commence, based on e2.
+
+### **DATA RELATED CHARGE:**
+
+On first receipt of non-zero element e6, data segment counting commences immediately and MS counter SEG is incremented, from zero, by unity for each segment transferred. When SEG reaches e6 i.e. a full data interval has been counted, then  $e5 \cdot e3$  HPLMN units are added to the CCM. SEG is then reset to zero to allow counting of the next data interval to commence.
+
+- NOTE 1: Elements e1, e7 and e2 have no effect on the initial charge or fixed charges applied i.e. are independent of e4.
+- NOTE 2: It should be noted that e1 in conjunction with e2 increases charging range compared to a regime based on e2 only. (i.e. e1 fixed at unity). This benefit is secondary to the support of call charging for roamers, which is the main function of e1.
+- NOTE 3: e1 improves the precision for high cost calls, where the interval, as defined by e2, may need to be excessively small, e.g. long haul international calls or INMARSAT. i.e. e1 can be increased instead of reducing e2, with some loss of accuracy of correlation with the actual bill.
+- NOTE 4: Element e5, for data usage charging, is equivalent to e1 (time related charging) and provides similar benefits for the support of data usage charges for roamers and high cost data calls.
+- NOTE 5: Rules for handling of CAI elements in the case of multiple calls are given in subclause 4.3 I.
+
+## **4.2 Handling of call meters**
+
+Two meters are defined.
+
+### **4.2.1 The Current Call Meter (CCM)**
+
+This is required to accumulate the charging units generated by the current call and is capable of advising:
+
+- a) The current charge due for the call(s) in progress.
+- b) At the end of the call(s), the charge equivalent to the current call record in an itemized bill.
+
+The CCM shall hold the value of the last call AOC, until the initiation of an outgoing call or acceptance of an incoming call, at which point it shall be reset to zero, regardless of the success of the initiation/acceptance attempt. This information is deleted when the MS is switched off or the SIM/USIM is removed.
+
+The CCM is essential for the correct functioning of AOC, see subclauses 4.1 and 4.3, and is a component of the Mobile Equipment. The charging computation shall cease immediately on termination of a call, as indicated by the user or the network, or on failure of the call.
+
+For multiple calls, CCM will advise the total charge of all the calls made and/or received during occupation of a traffic channel.
+
+### **4.2.2 The Accumulated Call Meter (ACM)**
+
+The Accumulated Call Meter accumulates the total units for both the current call and all preceding calls. The ACM is a function contained within the SIM/USIM. It is optional, but is essential for certain applications.
+
+For security reasons, the SIM/USIM only allows the value of the ACM to be incremented, not decremented. Resetting of the ACM shall only be possible after presentation of PIN2.
+
+If the ACMmax (see subclause 4.2.3) is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user (i.e. those calls that have a non-zero AoC associated with them), shall be terminated by the ME once the chargeable interval determined by the CAI has elapsed. The ACM will be updated with the new value, which may be greater than the ACMmax value. The reason why the call has terminated shall be given to the user by means of an appropriate indication given to the user.
+
+If the ACMmax is valid and the ACM is equal to or greater than the value of ACMmax, then no outgoing calls can be placed, except Emergency calls.
+
+If the ACMmax is valid and the ACM is equal to or greater than the value of ACMmax, and an incoming call is received and subsequently a non-zero CAI is received for that call, then the call shall be terminated by the ME with an appropriate indication given to the user.
+
+### 4.2.3 The ACM Maximum Value (ACMmax)
+
+This is the value that the subscriber can set, to limit the units which may be consumed by a user. The MS may provide for the means to set or update the ACMmax, using PIN2. The ACMmax is not valid if set to zero.
+
+NOTE: The network operator should make clear to the subscriber that the ACMmax must not be set to a value close to the maximum value possible in the encoding of ACMmax. The network operators should provide guidance as to what the maximum value for the ACMmax may be.
+
+### 4.2.4 The Price per Unit and Currency Table (PUCT)
+
+This is intended to enable the MS to calculate the cost of a call in a currency chosen by the subscriber. The subscriber may set the value of the home unit in the PUCT differently to the value of the unit published by the HPLMN in order to cover extra cost. An indication of the currency in use is part of the PUCT.
+
+## 4.3 Special processing
+
+- a) If e7 is zero or not sent in the CAI message, e2 applies and e7 is not used.
+- b) If e2 or e6 are set to zero, the relevant INT function shall handle the singularity by returning zero, thus disabling the relevant unitization process (call or data part).
+- c) On receipt of a subsequent e4, the MS shall transfer the value of  $e4 * e3$  to the CCM, by addition of  $e4 * e3$  to the current contents of the CCM.
+- d) When CDUR reaches e2 (or e7 as appropriate),  $e1 * e3$  is added to the CCM and CDUR is reset to zero, except when conditions given in (a) and (b) above, apply.
+- e) On receipt of new e1, e2 or e7 during a call, these new values are held in abeyance, until the value of the associated MS timer CDUR has reached the current e2 or e7 value as appropriate, and the processing as described in special processing item d) above has been completed. The new e1, e2 and/or e7 are then brought into operation. e7 is applied followed by e2, conditions a) and b) above determining the detailed processing.
+
+Any update of e1, e2 and/or e7 during the time before CDUR is reset, shall supersede any values already held in abeyance.
+
+If CDUR is not actively timing (i.e. due to e2 being zero, e7 being zero or the processing of e7 has been completed), then a new value of e2 and/or e7 is applied immediately as per a normal new call.
+
+- f) When SEG reaches e6,  $e5 * e3$  is added to the CCM and SEG is reset to zero, except where e6 is zero, where condition (b) above applies.
+- g) On receipt of a new e5 or e6 during the call, these new elements are held in abeyance, until the value of the associated MS counter SEG has reached the old e6 value, and the processing as described in special processing item (f) above has been completed. The resulting zero SEG and new e5 and e6 are then brought into operation.
+
+Any update of e5 or e6 during the time before SEG is reset, shall supersede any values already held in abeyance.
+
+If the old value of e6 was zero, then the new value of e5 and e6 is applied immediately.
+
+- h) The ACM shall be incremented when the CCM is incremented or once every 5 seconds, which ever is the longer period. Although the CCM is maintained with an accuracy of three places of decimals, the ACM shall be incremented and stored as integer units (i.e. no decimal places). The ACM shall be incremented by the difference between the present value of the CCM (rounded up) and the value of the CCM (rounded up) at the previous ACM incrementation.
+- i) A zero value for any of the CAI elements is valid and dealt with as described above.
+- j) Free calls should be implemented by sending a CAI message with appropriate zero elements.
+
+- k) On receipt of any CAI message from the network, provided the MS supports AoC, the MS it shall confirm receipt of the CAI message. An MS not supporting AoC as defined in TS 22.24 and TS 22.086 [2] shall not confirm receipt of the message.
+- l) During multiple calls the network shall send, and the MS shall receive, CAI elements for each call separately. The CCM shall record the sum of all the charges for the services being used currently.
+- m) If the MS detects a radio link failure the MS shall suspend CDUR. If a subsequent call reestablishment is successful, CDUR shall be resumed when call reestablishment is complete.
+
+## 4.4 Interactions with SCUDIF supplementary service
+
+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 [3]. 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 as stated in subclause 4.3 of this specification. The MS shall add initial units to the CCM and measure units on a time basis using the new values.
+
+# --- 5 Functional operation in PLMN
+
+For applicable calls, the PLMN shall send the CAI message to the MS immediately the called party answers. The PLMN derives the values of the elements to be sent in the CAI message in the following way:
+
+## 5.1 Outgoing calls
+
+The local PLMN, be it the HPLMN or the VPLMN, always sets values of e1, e2, e4, e5, e6 and e7 in terms of units of the LPLMN and according to its own tariff structure.
+
+Element e3 is set according to variables of the LPLMN and the relevant HPLMN. If the LPLMN is the HPLMN (i.e. the MS is in its Home PLMN) then e3 shall be simplified to unity.
+
+There shall be only one value of e3 for a given combination of HPLMN and VPLMN. This value may be simply loaded into the VMSC of the LPLMN using the Man Machine Interface commands, since it is not expected to vary frequently and is independent of the type of outgoing call.
+
+## 5.2 Incoming calls
+
+For incoming calls the HPLMN determines the tariff and this tariff is dependent on the LPLMN of the MS. Therefore all the CAI elements are set according to the HPLMN tariff as a function of LPLMN.
+
+In the case of the LPLMN being the HPLMN these elements may be set to zero assuming the HPLMN does not charge for incoming calls.
+
+For roaming (i.e. where the LPLMN is not the HPLMN), in order to charge for incoming calls, the VPLMN must be provided with specific CAI values as defined by each HPLMN (e1i through e7i inclusive). This may be achieved by loading the offered HPLMN derived values via the VPLMN MMI.
+
+Each VPLMN will require a set of 7 values per HPLMN with which the VPLMN has a roaming agreement i.e.:
+
+e1i(h), e2i(h), e3(h), e4i(h), e5i(h), e6i(h) and e7i(h).
+
+These are derived by:
+
+$$e1i(h)=e1H(h)/e3(h);$$
+
+$$e4i(h)=e4H(h)/e3(h);$$
+
+$$e5i(h)=e5H(h)/e3(h);$$
+
+where :
+
+- h represents the 'h'th HPLMN with a roaming relationship with the VPLMN;
+- i indicates the CAI element as determined by the 'h'th HPLMN, for the charging of incoming calls;  
+the same value of e3 is used for both incoming and outgoing calls;  
+exH(h) represents the value of the element x, given in terms of HPLMN units;  
+exi(h) represents the value of the element x as handled by the VPLMN.
+
+# 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.24 |     |     |       |     | Transferred to 3GPP SA1         | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.024    |     |     |       |     | Transferred to 3GPP SA1         |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99613  | 22.024    | 001 |     | R99   | D   | Editorial changes for alignment | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.024    |     |     | Rel-4 |     | Transferred to 3GPP Release 4   | 3.0.1  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.024    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5      | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.024    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6     | 5.0.0  | 6.0.0  |                   |
+| SP-28          | SP-050211 | S1-050397 | 22.024    | 003 | -   | Rel-6 | A   | AoC for SCUDIF                  | 6.0.0  | 6.1.0  | TEI               |
+| SP-36          |           |           | 22.024    |     |     | 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         | 7.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)  | 9.1.0  | 10.0.0 |                   |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-11 version (MCC)  | 10.0.0 | 11.0.0 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)  | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-13 version (MCC)  | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22030/raw.md

@@ -0,0 +1,1020 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **3GPP TS 22.030 V13.0.0 (2016-01)** **Man-Machine Interface (MMI) of the User Equipment (UE)** **Technical Specification** **(Release 13)**
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font with a small "TM" symbol. Above the "e" is the text "Advanced Pro" in a smaller font. To the left of the text is a green signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, which consists of the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top. Below the "P" is a red signal icon with three curved lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>TM</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP<sup>TM</sup> system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+UMTS, GSM, MMI, terminal
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles – Sophia Antipolis  
+Valbonne – FRANCE  
+Tel. : +33 4 92 94 42 00 Fax : +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                                                                                   |    |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                                                                                    | 5  |
+| 1 Scope.....                                                                                                                                                      | 6  |
+| 2 References.....                                                                                                                                                 | 6  |
+| 3 Definitions and abbreviations .....                                                                                                                             | 7  |
+| 3.1 Definitions.....                                                                                                                                              | 7  |
+| 3.2 Abbreviations .....                                                                                                                                           | 7  |
+| 4 General.....                                                                                                                                                    | 7  |
+| 4.1 Basic philosophy.....                                                                                                                                         | 7  |
+| 5 Physical user input features.....                                                                                                                               | 8  |
+| 5.1 General .....                                                                                                                                                 | 8  |
+| 5.2 MMI related to UE features .....                                                                                                                              | 8  |
+| 6 Procedures.....                                                                                                                                                 | 9  |
+| 6.1 General .....                                                                                                                                                 | 9  |
+| 6.2 UE access .....                                                                                                                                               | 9  |
+| 6.3 Definition of functions .....                                                                                                                                 | 9  |
+| 6.4 Call Control.....                                                                                                                                             | 10 |
+| 6.4.1 General .....                                                                                                                                               | 10 |
+| 6.4.2 Voice calls .....                                                                                                                                           | 10 |
+| 6.4.2.1 Mobile originated calls .....                                                                                                                             | 10 |
+| 6.4.2.2 Emergency calls.....                                                                                                                                      | 10 |
+| 6.4.2.3 Mobile terminated calls .....                                                                                                                             | 10 |
+| 6.5 Supplementary Services Control.....                                                                                                                           | 10 |
+| 6.5.1 General .....                                                                                                                                               | 10 |
+| 6.5.2 Structure of the MMI.....                                                                                                                                   | 11 |
+| 6.5.3 Handling of supplementary services .....                                                                                                                    | 12 |
+| 6.5.3.1 Handling of defined supplementary services.....                                                                                                           | 12 |
+| 6.5.3.2 Handling of not-implemented supplementary services .....                                                                                                  | 12 |
+| 6.5.4 Registration of new password .....                                                                                                                          | 15 |
+| 6.5.5 Handling of supplementary services within a call.....                                                                                                       | 15 |
+| 6.5.5.1 Call Deflection, Call Waiting, Call Hold, MultiParty Services, Explicit Call Transfer and Completion of Calls to Busy Subscriber general principles ..... | 15 |
+| 6.5.5.2 Call Waiting (CW).....                                                                                                                                    | 16 |
+| 6.5.5.3 Call hold.....                                                                                                                                            | 16 |
+| 6.5.5.4 MultiParty .....                                                                                                                                          | 17 |
+| 6.5.5.5 Explicit Call Transfer.....                                                                                                                               | 17 |
+| 6.5.5.6 Special case.....                                                                                                                                         | 17 |
+| 6.5.5.7 Call Deflection.....                                                                                                                                      | 17 |
+| 6.5.5.8 Completion of calls to busy subscribers .....                                                                                                             | 17 |
+| 6.5.6 Other handling of supplementary services .....                                                                                                              | 18 |
+| 6.5.6.1 Multiple Subscriber Profile.....                                                                                                                          | 18 |
+| 6.5.6.1.1 Registering an alternative profile .....                                                                                                                | 18 |
+| 6.5.6.1.2 Selecting an alternative profile on a per call basis .....                                                                                              | 18 |
+| 6.5.6.2 Calling Line Identification Presentation (CLIP).....                                                                                                      | 18 |
+| 6.6.6.2.1 Presentation of Information.....                                                                                                                        | 18 |
+| 6.5.6.3 Follow Me (FM) .....                                                                                                                                      | 18 |
+| 6.6 SIM/USIM interfaces .....                                                                                                                                     | 18 |
+| 6.6.1 Entry of PIN and PIN2 .....                                                                                                                                 | 18 |
+| 6.6.2 Change of PIN or PIN2 .....                                                                                                                                 | 19 |
+| 6.6.3 Unblocking of PIN or PIN2.....                                                                                                                              | 19 |
+| 6.6.4 Reading the abbreviated dialling code.....                                                                                                                  | 19 |
+| 6.6.5 Status information - return codes .....                                                                                                                     | 19 |
+| 6.7 Presentation of IMEI .....                                                                                                                                    | 20 |
+| 6.8 In Case of Emergency access procedure.....                                                                                                                    | 20 |
+| 6.9 Presentation of e-marking .....                                                                                                                               | 20 |
+
+**Annex A (normative):** UE access mealy graph .....21
+
+**Annex B (normative):** Codes for defined Supplementary Services .....23
+
+**Annex C (normative):** Codes for Tele- and bearer services.....26
+
+**Annex D (informative):** Change history.....28
+
+# --- 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 requirements for and gives guidelines on the MMI on the User Equipment (UE). This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information.
+
+Some clauses of the present document include the requirements that are applicable only to UE connected to CS Domain. See 3GPP TS 22.101 [18]; for overall service principles and 3GPP TS 22.001 [19] for Circuit telecommunication 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 TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.004: "General on supplementary services".
+- [3] 3GPP TS 22.011: "Service accessibility".
+- [4] 3GPP TS 22.016: "International Mobile station Equipment Identities (IMEI)".
+- [5] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services – Stage 1".
+- [6] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services – Stage 1".
+- [7] 3GPP TS 22.090: "Stage 1 description of Unstructured Supplementary Service Data (USSD)".
+- [8] 3GPP TS 23.038: "Alphabets and language".
+- [9] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols – Stage 3".
+- [10] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding".
+- [11] 3GPP TS 29.002 : "Mobile Application Part (MAP)".
+- [12] 3GPP TS 22.081: "Line Identification Supplementary Services – Stage 1".
+- [13] ITU-T Recommendation E.164: "Numbering plan for the ISDN era".
+- [14] ITU-T Recommendation E.121: "Pictograms and symbols to assist users of the telephone service".
+- [15] 3GPP TS 22.072: "Call Deflection; Stage 1".
+- [16] 3GPP TS 22.091: "Explicit Call Transfer Supplementary Service; Stage 1".
+- [17] 3GPP TS 22.093: "Call Completion to Busy Subscriber (CCBS); Stage 1".
+- [18] 3GPP TS 22.101: "Service principles".
+- [19] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
+
+- [20] 3GPP TS 22.094: "Follow Me Service description – Stage 1".
+- [21] 3GPP TS 22.135: "Multicall supplementary service Stage 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definition applies:
+
+**Directory Number:** A string consisting of one or more of the characters from the set {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, \*, #, a, b, c} associated with a nature of address indicator and number plan indicator. When using the public MMI for the control of supplementary services however, \* and # cannot be part of any SC or SI field.
+
+NOTE 1: No such restriction on the SC and SI fields exists when using other (e.g. menu-driven) MMI for the control of supplementary services.
+
+NOTE 2: When using the public MMI, certain limitations on the use of one and two digit directory numbers may apply. The use of other MMI can remove these restrictions.
+
+NOTE 3: This definition is not intended to require the support of all these characters in the MMI itself.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations listed in 3GPP TR 21.905 [18] apply.
+
+# --- 4 General
+
+## 4.1 Basic philosophy
+
+The basic idea behind the present document is that it should give a minimum level of requirements, with emphasis on items which are seen as important from a usage point of view. This means, that the requirements are mainly dealing with standardized control procedures of access to services i.e. call establishment, invocation of supplementary services and so on.
+
+The requirements on the physical layout of input and output features are kept to a minimum to allow for differentiated types of Ues and to ease the introduction of future developments in the area of MMI. The standardized control procedures describe the sequence of real actions to be taken by the users. However, since the requirements on the physical input features are minimal the control procedures may differ between Ues depending on the solution of the manufacturers. The "bridge" between these requirements is however that the same logical actions have to be taken by the user. That is, the user has to provide the same information for the call control and signalling no matter what the method is. This is also valid if an automatic device is used for carrying out the same actions. The logical procedures are therefore defined and standardized in the present document.
+
+Optionally, the user may set the ME to disable some or all of the MMI functions defined in the present document. This setting shall only apply when the same SIM/USIM is in use otherwise the ME shall enable the standard MMI.
+
+# --- 5 Physical user input features
+
+## 5.1 General
+
+This clause gives the requirements or guidelines for the MMI of the input related UE features. Basic requirements on these features are given in 3GPP TS 22.101 [18].
+
+## 5.2 MMI related to UE features
+
+### \* Country/PLMN selection:
+
+The method is manufacturer optional.
+
+### \* International Access Function ("+" key):
+
+and
+
+### \* Keypad:
+
+The physical means of entering the characters 0-9, +, \* and # (i.e. the SELECT function) may be keypad, voice input device, DTE or other, but there must be means to enter this information.
+
+The relationship on the keypad between the numbers and letters (where used) is important when mnemonic dialling may be used. The following relationship is therefore preferred though optional.
+
+|   |     |   |      |
+|---|-----|---|------|
+| 1 |     | 6 | MNO  |
+| 2 | ABC | 7 | PQRS |
+| 3 | DEF | 8 | TUV  |
+| 4 | GHI | 9 | WXYZ |
+| 5 | JKL | 0 |      |
+
+### \* ACCEPT, SEND and END functions:
+
+The physical means to perform these functions may be keypad, voice input device, DTE or other, but there must be means to perform these functions. ACCEPT and SEND may use the same means.
+
+### \* Setting of called Number Fields (Type of Number), use of the "+" key function:
+
+Users may enter a called number in two formats, called here International or Open. The Type of Number (TON) may be set to other values if required, but the procedure for this is not defined here.
+
+### "International format":
+
+This is entered by starting with a "+" followed by country code, even for national calls. This method is preferred for roaming and international calls, and highly desirable for storage of short codes or for call-forwarding.
+
+This sets the TON to "International" - see 3GPP TS 24.008 [9].
+
+#### "Open format":
+
+This is when the "+" is not entered, and the number is entered in the normal way for that network. The number may require a prefix or escape code as normal, for example for entering the international access code or national access code (often "0").
+
+This sets the TON to "Unknown" - see 3GPP TS 24.008 [9]. (This is **not** the "National" case, which does not permit prefix or escape digits).
+
+Care should be taken with this format, since the dialled number will only be correct in a given network, and may be wrong when roaming. Caution must be applied when using stored numbers or call-forwarding.
+
+### \* Setting of Called Number Fields (Number Plan Indicator):
+
+The default Number Plan Identification (NPI) shall be ITU-T E.164 [13] if all the digits are in the range 0-9 and the NPI shall be "unknown" if other number information is included. However, if the user selects (or has selected) a particular NPI (procedure not defined) then that NPI shall be used.
+
+### \* Entry of Bearer Capability Information Elements (BCIE):
+
+This is required in order to indicate information such as whether it is a voice or data call, facsimile, synchronous or asynchronous etc. The method for entering this information is of mobile manufacturer's option. For those User Equipment offering only telephony (and emergency calls), the default BCIE shall be for telephony (or emergency call). For User Equipment supporting non-voice services, there shall be means to set the BCIE
+
+required, by reading the appropriate field in the SIM/USIM and possibly otherwise. This field may be associated with or independent of the called number.
+
+# --- 6 Procedures
+
+## 6.1 General
+
+This clause defines the MMI of the service access procedures, and supplementary service control procedures. These procedures are defined as logical procedures and in general no mandatory methods are specified. In order to make the descriptions continuous and clear requirements in 3GPP TS 22.101 [18] have been included or are referenced. The mapping between the MMI procedures and the call control entity is specified in 3GPP TS 24.008 [9].
+
+## 6.2 UE access
+
+The UE access procedure is comprised of the initial actions the user has to take before calls can be established or received. This procedure includes e.g. insertion of subscriber-card and entering the PIN-code.
+
+As there exist different types of UE and as requirements in other 3GPP specifications allow different options the UE access procedure may differ between User Equipment. The method for describing the UE access procedures is by using a Mealy-graph, see annex A.
+
+The graph shows the UE access for simple UE e.g. hand-held and they may be different for more complex stations. It should also be noted that the exact sequences of events are not described, these may be chosen by the manufacturers.
+
+## 6.3 Definition of functions
+
+The following functions are applicable and mandatory for the logical procedures for Mobile originated and terminated calls and for the control of Supplementary Services:
+
+- ACCEPT: Acceptance of a mobile terminated call.
+- SELECT: Entry of information.
+- SEND: Transmission of the entered information to the network.
+- INDICATION: Call progress indications. Other indications may be given in addition throughout the procedure.
+- END: Termination of or disconnection from the call. The execution of the END-function may be caused by either party involved in the call by e.g. termination, loss of coverage, invalidation of payment.
+
+## 6.4 Call Control
+
+### 6.4.1 General
+
+Voice calls to and from a User Equipment shall be controlled in accordance with the procedures described below. "Data calls" are expected to be controlled in a similar way but are not here specified.
+
+### 6.4.2 Voice calls
+
+The voice call is either a normal telephony call or an emergency call.
+
+#### 6.4.2.1 Mobile originated calls
+
+The following sequence of functions shall be used:
+
+- SELECT: Entry of called address information.
+- SEND: Transmission of the called address.
+- INDICATION: Call progress indications.
+- END: Termination of the call.
+
+#### 6.4.2.2 Emergency calls
+
+With User Equipment supporting Telephony, it shall be possible to place an emergency call as specified in 3GPP TS 22.101 [18].
+
+#### 6.4.2.3 Mobile terminated calls
+
+The following sequence of functions shall be used:
+
+- INDICATION: Alert to the user that she is being called.
+- ACCEPT: Acceptance of the incoming call by the user.
+- INDICATION: Call progress indications.
+- END: Termination of the call.
+
+User Determined User Busy (UDUB): If, on being alerted by an incoming call, the called user enters "0 SEND", this shall set UDUB for that call, which shall either invoke call forwarding on busy, if active and operative, or else present BUSY to the calling party.
+
+## 6.5 Supplementary Services Control
+
+### 6.5.1 General
+
+The supplementary services shall be controlled in accordance with the procedures described below. All User Equipment with MMI shall be able to be controlled in this way, to minimize the confusion of users using different types of User Equipment (quite likely, due to the use of the SIM IC card or UICC) and to permit the introduction by a PLMN operator of new supplementary services, not defined at the time of the design of a User Equipment. These procedures are based on those recommended by ETSI/HF and ITU-T Recommendation E.131.
+
+The specified MMI shall be supported by the L3 signalling between the UE and the MSC, see 3GPP TS 24.080 [10].
+
+In addition to these specified MMI procedures the UE may be equipped with additional enhanced MMI procedures (e.g. dedicated keys, menu procedures...), left to the discretion of the manufacturer. These procedures shall also be converted in accordance with 3GPP TS 24.080 [10].
+
+### 6.5.2 Structure of the MMI
+
+The following sequence of functions shall be used for the control of Supplementary Services:
+
+- SELECT: Entry of the procedure information (may be a digit or a sequence of characters).
+- SEND: Transmission of the information to the network.
+- INDICATION: Call progress indications.
+
+The UE shall support the MMI procedure specified as:
+
+- Activation : \*SC\*SI#
+- Deactivation : #SC\*SI#
+- Interrogation : \*#SC\*SI#
+- Registration : \*SC\*SI# and \*\*SC\*SI#
+- Erasure : ##SC\*SI#
+
+This structure consists of the following parts:
+
+- Service Code, SC( 2 or 3 digits);
+- Supplementary Information, SI (variable length).
+
+The procedure always starts with \*, #, \*\*, ## or \*# and is finished by #. Each part within the procedure is separated by \*.
+
+The service code uniquely specifies the Supplementary Service, either as a defined Supplementary Service or as a spare service code. All spare service codes shall be reserved for future use.
+
+The UE shall determine from the context whether, an entry of a single \*, activation or registration was intended.
+
+For example, a call forwarding request with a single \* would be interpreted as registration if containing a forwarded-to number, or an activation if not.
+
+The supplementary information (SI) may comprise e.g. a PIN code or Directory Number. Where a particular service request does not require any SI, "\*SI" is not entered, e.g. Activation becomes \*SC#SEND. Where further supplementary information is required this is again entered as \*SI, e.g. \*SC\*SIA\*SIB#SEND. SIB may be used to specify the tele or bearer service expressed as a Basic Service Group to which this supplementary service request applies, SIC may be used to specify the value of the "No Reply Condition Timer".
+
+Use of SIA, SIB, SIC for a particular procedure is optional. The procedure to be adopted where these are not all used is as follows:
+
+\*SI# shall be entered in any of the following formats:
+
+\* SIA \* SIB \* SIC #
+
+\* SIA \* SIB #
+
+\* SIA \* \* SIC #
+
+\* SIA #
+
+\* \* SIB \* SIC #
+
+\* \* SIB #
+
+\* \* \* SIC #
+
+#
+
+The denotation of the Supplementary Information and the order of entry are specified in annex B. Supplementary Information Codes for the Teleservices and Bearer Services are given in annex C.
+
+The following procedures shall be used for application of supplementary services to the call set-up procedure:
+
+\*SCn\*SI#DN SEND;
+
+where SC is the service code defined in annex B and \*SI is an optional field which may be applicable to service SC. The "n" is a single digit used to indicate the numbering plan, profile, priority, etc. according to the service being applied. For simplicity of presentation, the leading \* is shown on the assumption that the action is to activate (switch on) the required service. However, for a deactivation (or switch off), this would become:
+
+#SCn\*SI#DN SEND;
+
+It is assumed that the \*# (interrogation) will not apply to call set-up.
+
+Where more than one supplementary service is applicable to the call set-up, these shall be concatenated with any applicable supplementary information immediately following the applicable service code.
+
+For example, if SCn and SI refer to one applicable supplementary service and scn and si to another, then the generic procedure becomes:
+
+\*SCn\*SI#scn\*si#DN SEND.
+
+NOTE: The order of entry of SC and sc is a user option, provided that any supplementary information follows immediately after the relevant SC.
+
+Where SI is not applicable according to the definition of the supplementary service, then \*SI is omitted. Where its use is optional, but not selected for a particular call set-up, it may be omitted or entered as an extra \* if this is necessary to avoid ambiguity of interpretation.
+
+NOTE: By using the # as a separator, most cases are expected to be unambiguous.
+
+### 6.5.3 Handling of supplementary services
+
+#### 6.5.3.1 Handling of defined supplementary services
+
+The MMI procedure for the defined Supplementary Services (see 3GPP TS 22.004 [2]) shall be converted to the mobile radio interface Layer 3, as specified in 3GPP TS 24.080 [10]. An appropriate message should be given/displayed to the user in accordance with the "return result/error" from the network.
+
+The service codes for the defined Supplementary Services are given in annex B.
+
+#### 6.5.3.2 Handling of not-implemented supplementary services
+
+The UE shall act in accordance with figure 3.5.3.2 when digits are entered to the UE to determine whether to interpret these as call set-up requests or supplementary service control procedures etc. This may involve a mechanism, referred to as Unstructured SS Data, which allows the support of SS services which are not implemented by means of the specified functional signalling. See also 3GPP TS 22.090 [7].
+
+![Flowchart for input string processing in a mobile station (MS).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+```
+graph TD; Start[Idle or 'in call'] --> Input[Input string]; Input --> D1{Input string is standard GSM SS procedure support by MS}; D1 -- Yes --> Action1[MS shall perform the requested procedure]; D1 -- No --> D2{Input string is SIM control procedure}; D2 -- Yes --> Action1; D2 -- No --> D3{Input String is MS manufacturer defined procedure (2)}; D3 -- Yes --> Action1; D3 -- No --> D4{Input string is #-string (3)}; D4 -- Yes --> Action1; D4 -- No --> D5{Input string is short string (4)}; D5 -- Yes --> D6{MS is in a call (1)}; D5 -- No --> D7{Input string is call set-up string (5)}; D6 -- Yes --> Action1; D6 -- No --> D8{Input string is 2 digit starting with a "1"}; D8 -- Yes --> Action2[Input shall be sent as a call set-up request]; D8 -- No --> Action1; D7 -- Yes --> Action2; D7 -- No --> D9{Is USSD supported by the MS?}; D9 -- Yes --> Action3[MS shall interpret this as USSD and send transparently towards the network]; D9 -- No --> Action4[Other meaning or error]; Action2 --> Action1;
+```
+
+The flowchart describes the processing of an input string in a mobile station (MS). It begins with the state 'Idle or 'in call'' and proceeds to 'Input string'. A series of decision diamonds evaluate the input string against various criteria: 'Input string is standard GSM SS procedure support by MS', 'Input string is SIM control procedure', 'Input String is MS manufacturer defined procedure (2)', 'Input string is #-string (3)', 'Input string is short string (4)', and 'Input string is call set-up string (5)'. If any of these are 'Yes', the MS performs the requested procedure. If 'Input string is short string (4)' is 'Yes', it checks if 'MS is in a call (1)'. If 'Yes', it performs the requested procedure; if 'No', it checks if the 'Input string is 2 digit starting with a "1"'. If 'Yes', it sends it as a call set-up request; if 'No', it performs the requested procedure. If 'Input string is call set-up string (5)' is 'Yes', it sends it as a call set-up request. If none of the above criteria are met, it checks if 'USSD supported by the MS?'. If 'Yes', it interprets it as USSD and sends it transparently towards the network. Otherwise, it results in 'Other meaning or error'.
+
+Flowchart for input string processing in a mobile station (MS).
+
+Figure 3.5.3.2
+
+The following definitions are applicable to the interpretation of figure 3.5.3.2:
+
+##### 1) In a call:
+
+A UE is "in a call" from the time that signalling related to the establishment or attempted establishment of a MO or MT call commences and before the call or call attempt ends, and (if applicable) the ME has stopped generating tones related to this call to the user.
+
+##### 2) UE manufacturer defined procedure:
+
+The term "UE manufacturer defined procedure" shall not include the following two cases:
+
+###### (i) input which can be interpreted as being of the following form, whether or not in a call:
+
+CX [string]# followed by SEND;
+
+where
+
+string is any combination of numeric digits, \*, #;
+
+and
+
+C comprises 1, 2 or 3 digits from the set (\*,#);
+
+and
+
+X comprises 1, 2 or 3 numeric digits or the fourth numeric digit is non-zero;
+
+###### (ii) input of the following form in a call (as defined above):
+
+"Entry of 1 or 2 characters defined in the 3GPP TS 23.038 [8] Default Alphabet followed by SEND".
+
+##### 3) #-string:
+
+Input of the form.
+
+"Entry of any characters defined in the 3GPP TS 23.038 [8] Default Alphabet (up to the maximum defined in 3GPP TS 24.080 [10]), followed by #SEND".
+
+##### 4) Short string:
+
+"Entry of 1 or 2 characters defined in the 3GPP TS 23.038 [8] Default Alphabet followed by SEND".
+
+##### 5) Call setup string:
+
+MMI input in accordance with the call set-up procedures as defined in 3GPP TS 24.008 [9] and terminated by SEND.
+
+If the network has initiated an operation which explicitly (in the signalling) requires a response from the user, then the user shall be able to enter a response in the form of any string of characters followed by SEND. The mobile shall also provide an MMI command to terminate the dialogue with a NULL response.
+
+The use of END shall release all calls in progress (see also subclause 3.5.5.2), terminate any outstanding unstructured SS operations, and release any connection used for unstructured SS operations.
+
+### 6.5.4 Registration of new password
+
+The following procedure permits the user to change the password relating to use of Supplementary Services. The only control procedure supported is Registration of a new password, which replaces any previous password for the same service. The password may not be Erased or Interrogated.
+
+Procedure:
+
+\* 03 \* ZZ \* OLD\_PASSWORD \* NEW\_PASSWORD \* NEW\_PASSWORD #
+
+The UE shall also support the alternative procedure:
+
+\*\* 03 \* ZZ \* OLD\_PASSWORD \* NEW\_PASSWORD \* NEW\_PASSWORD #
+
+where, for Barring Services, ZZ = 330;
+
+for a common password for all appropriate services, delete the ZZ, entering:
+
+\* 03 \*\* OLD\_PASSWORD \* NEW\_PASSWORD \* NEW\_PASSWORD #
+
+The UE shall also support the alternative procedure:
+
+\*\* 03 \*\* OLD\_PASSWORD \* NEW\_PASSWORD \* NEW\_PASSWORD #
+
+The UE will then indicate to the user whether the new password request has been successful or not. If the new password request is rejected (e.g. due to entry of incorrect old password) the old password remains unchanged, until it is successfully changed by correctly repeating the procedure. Refer to 3GPP TS 22.004 [2] regarding repeated entry of incorrect password.
+
+NOTE: The procedures shall be followed by SEND as described in subclause 3.5.2.
+
+### 6.5.5 Handling of supplementary services within a call
+
+#### 6.5.5.1 Call Deflection, Call Waiting, Call Hold, MultiParty Services, Explicit Call Transfer and Completion of Calls to Busy Subscriber general principles
+
+During a call, the following general procedures shall be available, where applicable, for the subscriber to control the operation of:
+
+- Call Deflection;
+- Call Waiting;
+- Call Hold;
+- MultiParty Services;
+- Explicit Call Transfer;
+- Completion of Calls to Busy Subscriber,
+
+including their interactions. It should be noted that not all control procedures described in 3GPP TS 22.072 [15], 3GPP TS 22.083 [5], 3GPP TS 22.084 [6], 22.091 [16], and 22.093 [17] are specified in this subclause.
+
+Procedures:
+
+|                              |   |                                                                                        |
+|------------------------------|---|----------------------------------------------------------------------------------------|
+| Entering 0 followed by SEND  | - | Releases all held calls or sets User Determined User Busy (UDUB) for a waiting call.   |
+| Entering 1 followed by SEND  | - | Releases all active calls (if any exist) and accepts the other (held or waiting) call. |
+| Entering 1X followed by SEND | - | Releases a specific active call X.                                                     |
+
+|                                                  |   |                                                                                                                           |
+|--------------------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------|
+| Entering 2 followed by SEND                      | - | Places all active calls (if any exist) on hold and accepts the other (held or waiting) call.                              |
+| Entering 2X followed by SEND                     | - | Places all active calls on hold except call X with which communication shall be supported.                                |
+| Entering 3 followed by SEND                      | - | Adds a held call to the conversation.                                                                                     |
+| Entering 4 followed by SEND                      | - | Connects the two calls and disconnects the subscriber from both calls (ECT).                                              |
+| Entering 4 * "Directory Number" followed by SEND | - | Redirect an incoming or a waiting call to the specified followed by SEND directory number.                                |
+| Entering 5 followed by SEND                      | - | Activates the Completion of Calls to Busy Subscriber Request.                                                             |
+| Entering "Directory Number" followed by SEND     | - | Places all active calls (if any exist) on hold and sets up a followed by SEND new call to the specified Directory Number. |
+| Entering END followed by SEND                    | - | Releases the subscriber from all calls (except a possible waiting call).                                                  |
+
+"X" is the numbering (starting with 1) of the call given by the sequence of setting up or receiving the calls (active, held or waiting) as seen by the served subscriber. Calls hold their number until they are released. New calls take the lowest available number.
+
+Where both a held and a waiting call exist, the above procedures shall apply to the waiting call (i.e. not to the held call) in conflicting situation.
+
+#### 6.5.5.2 Call Waiting (CW)
+
+During a call, provided this service is active for the called party, if a second call attempts to make contact, a "call waiting" indication will be presented to the called party.
+
+To clear the current call and accept the waiting call, enter 1 followed by SEND, within the time out period. Alternatively, either party in the existing, active, call may release that call. The call waiting indication then becomes an "alert", and the call may be accepted as a normal call within the time-out period.
+
+To hold the current call and accept the waiting call, enter 2 followed by SEND, within the time out period.
+
+To ignore the waiting call, take no action.
+
+To set User Determined User Busy (UDUB) for the waiting call, enter 0 followed by SEND, within the time out period.
+
+To redirect the waiting call to another destination, enter 4 \* "Directory Number" followed by SEND, within the time out period.
+
+#### 6.5.5.3 Call hold
+
+During a call, the initial call may be held while another call is made by entering the second directory number followed by SEND.
+
+To shuttle between the two calls enter 2 followed by SEND irrespective of whether the second call was acquired using the Call Hold or acceptance of Call Waiting procedures.
+
+If no waiting call exists, by entering 0 followed by SEND the held call is cleared.
+
+To clear an active call and return to the held call enter 1 followed by SEND. This is only possible if no waiting call exists.
+
+#### 6.5.5.4 MultiParty
+
+Having established calls to these two parties with one call active and the other on hold, enter 3 followed by SEND for a multiparty conversation.
+
+To add another remote party, the same procedure applies. Another call is established and either this call or the existing multiparty call is placed on hold. Entering 3 followed by SEND brings all these parties together in an enlarged multiparty call.
+
+To choose one party for a private communication, putting the rest of the multiparty on hold, enter 2X followed by SEND, where X defines the call with which communication shall be supported.
+
+To return to the multiparty, with the previously active call placed on hold, enter 2 followed by SEND.
+
+To release a specific party enter 1X followed by SEND, where X is defined as above.
+
+If the served mobile subscriber enters END, all calls including the multiparty are released. The multiparty is terminated.
+
+#### 6.5.5.5 Explicit Call Transfer
+
+Having established calls to these two parties with one call active and the other on hold, enter 4 followed by SEND to transfer the calls.
+
+If a subscriber has one active, one held and one waiting call, and by entering 4 SEND the active and held call are connected, after the successful completion of the transfer, the served subscriber shall be offered the normal notification that there is a new waiting call, as for a normal terminating call.
+
+#### 6.5.5.6 Special case
+
+Provided both Call Hold and Call Waiting is active, it is possible to have one active and one held call and then a third call attempting to make contact. In this case, to clear the active call and accepting the waiting call (the held call not affected) enter 1 followed by SEND (If entering 2 followed by SEND the call state shall not be affected).
+
+Alternatively, either party in the active call may release that call. The held call will remain held. Within the time-out period the waiting call may then be accepted by entering 2 followed by SEND. It shall also be allowed to accept the waiting call by entering 1 followed by SEND.
+
+As an additional alternative, the (controlling) subscriber B may enter END, in which case the active and the held calls are released. The call waiting indication then becomes an "alert" and the previously waiting call may be accepted as a normal call within the time-out period.
+
+#### 6.5.5.7 Call Deflection
+
+If informed about an incoming call this call may be redirected to another destination by entering 4 \* "Directory Number" followed by SEND.
+
+#### 6.5.5.8 Completion of calls to busy subscribers
+
+In a situation where a calling party A encounters busy or congestion on the B side, the network may offer the possibility to apply the CCBS supplementary service. If subscriber A, after being notified that CCBS is possible and during the period where the retention timer is running (minimum 15 seconds), enters 5 followed by SEND, this shall be interpreted as CCBS activation. Entering of 5 SEND by subscriber A in any other situation as described above shall not be interpreted as CCBS activation.
+
+### 6.5.6 Other handling of supplementary services
+
+#### 6.5.6.1 Multiple Subscriber Profile
+
+##### 6.5.6.1.1 Registering an alternative profile
+
+An alternative profile is registered by entering the profile ID of the new profile, as illustrated:
+
+\* 59n # SEND
+
+Where n is the identity of the profile desired.
+
+An indication is given to the user showing whether this procedure was successful.
+
+The ID of the registered profile and other provisioned profiles may be determined by interrogation on entering \*#59# SEND
+
+The profile so registered shall be used for all further UE originated activities and CISS operations unless another profile is selected, or an alternative profile is registered.
+
+##### 6.5.6.1.2 Selecting an alternative profile on a per call basis
+
+An alternative profile to the registered profile is selected by entering the profile ID of the new profile along with the desired Directory Number, as illustrated:
+
+DN \*59n# SEND
+
+Where n is the identity of the profile desired
+
+Continued processing of the call shall implicitly indicate that the selection was successful, there shall be no explicit indication given to the user concerning successful execution this selection procedure.
+
+It is assumed that \*# (i.e. interrogation) will not apply to call set-up.
+
+#### 6.5.6.2 Calling Line Identification Presentation (CLIP)
+
+The CLIP Supplementary Service is defined in 3GPP TS 22.081[12]
+
+##### 6.6.6.2.1 Presentation of Information
+
+If CLIP has been provisioned for the subscriber and the UE is capable of displaying the line identification then for each MT call the UE should either:
+
+display the calling line identity; or
+
+display the reason why the line identity is not available as indicated by the Presentation Indicator.
+
+#### 6.5.6.3 Follow Me (FM)
+
+The Follow Me Feature is defined in 3GPP TS 22.094 [20]. FM control procedures make use of USSD.
+
+## 6.6 SIM/USIM interfaces
+
+### 6.6.1 Entry of PIN and PIN2
+
+After insertion of the IC card while the UE is switched on, or when the UE is switched on while the IC card is inserted, or when the UE is switched on in the case of a plug-in SIM/USIM, an indication shall be given to the user that the PIN needs to be entered, unless the PIN is not applicable.
+
+If the user wishes to perform a function protected by PIN2, an indication shall be given to the user that PIN2 needs to be entered.
+
+When the user enters the PIN or PIN2, each entered digit should not be displayed to the user for longer than one second.
+
+### 6.6.2 Change of PIN or PIN2
+
+The following procedure permits the user to change the PIN or PIN2 in the SIM/USIM:
+
+PIN: \*\*04\*OLD\_PIN\*NEW\_PIN\*NEW\_PIN#
+
+PIN2: \*\*042\*OLD\_PIN2\*NEW\_PIN2\*NEW\_PIN2#
+
+Note that the SEND function is not used in these procedures.
+
+An indication is given to the user showing whether this procedure was successful.
+
+### 6.6.3 Unblocking of PIN or PIN2
+
+The following procedure permits the user to unblock the PIN or PIN2:
+
+PIN: \*\*05\*PIN\_UNBLOCKING\_KEY\*NEW\_PIN\*NEW\_PIN#
+
+PIN2: \*\*052\*PIN2\_UNBLOCKING\_KEY\*NEW\_PIN2\*NEW\_PIN2#
+
+Note that the SEND function is not used in these procedures.
+
+The new PIN or PIN2 must be entered whether or not it is intended to change the PIN or PIN2. An indication is given to the user showing whether this procedure was successful.
+
+### 6.6.4 Reading the abbreviated dialling code
+
+An abbreviated dialling code shall be able to be read using the following procedure:
+
+N(N)(N)#
+
+Alternative additional procedures are also permitted.
+
+### 6.6.5 Status information - return codes
+
+The SIM/USIM gives status information, as responses to instructions. Some of the possible return codes are deeply related to the user's actions and should therefore be indicated to her.
+
+It is mandatory to give the user the appropriate indication (respectively) when the following codes appear:
+
+description;
+
+Memory Problem (eg. Update impossible);
+
+Access conditions not fulfilled (eg. secret code verify rejected);
+
+Unsuccessful CHV verification, no attempt left (eg. Secret code locked);
+
+Technical problem with no diagnostic given. However, if this code is returned by the SIM/USIM in response to an ENVELOPE (SMS-PP DOWNLOAD) or ENVELOPE (CELL BROADCAST DOWNLOAD) or similar message, then no indication shall be given to the user, since in this case the code is not related to a user action.
+
+The status information indication can be a dedicated lamp, text-string or others, as long as it is unambiguously made available to the user via the MMI.
+
+As regards all other codes, it is left to the manufacturers' discretion whether and how the user shall be informed.
+
+## 6.7 Presentation of IMEI
+
+The following procedure shall instruct the ME to display its IMEI:
+
+\*#06#
+
+The procedure shall be accepted and performed with and without an inserted SIM/USIM. The ME shall then display the 14 digits of the IMEI (not including the spare digit), the Check Digit and optionally the Software Version Number as defined in 3GPP TS 22.016 [4] (as a single string, in that order).
+
+## 6.8 In Case of Emergency access procedure
+
+The In Case of Emergency (ICE) information is specified in TS 22.101[18]. This clause defines the MMI of the In Case of Emergency access procedures.
+
+The default setting is that the In Case of Emergency access procedure shall operate whether or not the SIM PIN is locked and whether or not the handset is locked. It shall be possible for the subscriber to change the default setting to prevent accessibility to the ICE information. The unlocking of In Case of Emergency shall occur when a star key is pressed three times (\*\*\*) in the WAIT state, provided that a star key is on the keypad.
+
+The mealy-graph for the In Case of Emergency access procedure is shown in Figure A.2.
+
+**Editor's Note:** Access of ICE information for the voice-only device and DTE is FFS.
+
+## 6.9 Presentation of e-marking
+
+The ME may display the electronic marking (e-marking). If the ME supports the e-marking and if the ME supports Physical user input features (see section 5), the following procedure shall instruct the ME to display its e-marking:
+
+\*#07#
+
+The procedure shall be accepted and performed with and without an inserted SIM/USIM. The e-marking may include, at the option of the manufacturer, regulatory-mandated marking information, regulatory restrictions of use if required and other relevant marking information. The regulatory marking should follow the format given by the regulation(s).
+
+# Annex A (normative): UE access mealy graph
+
+![Mealy-graph for the UE access procedure. State 1 (MS - OFF) is the initial state. State 2 (WAIT) is the central state. States 3 (Enter-card), 4 (Enter-PIN), and 6 (Enter-PLMN) are dotted states. State 5 (Failure - Treatment) is a failure state. State 7 (Serv -AV) is the service state. Transitions: 1 to 2 on 'ON'; 2 to 3 on 'REQ', 3 to 2 on 'ICC'; 2 to 4 on 'REQ', 4 to 2 on 'Complete'; 2 to 5 on 'Failure', 5 to 2 on 'LOCKER'; 2 to 6 on 'REQ', 6 to 2 on 'Entered'; 2 to 7 on 'OK', 7 to 2 on 'Conditional'.](a3472689858b068ef469213682965325_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> 1 : MS - OFF
+    1 --> 2 : ON
+    2 --> 3 : REQ
+    3 --> 2 : ICC
+    2 --> 4 : REQ
+    4 --> 2 : Complete
+    2 --> 5 : Failure
+    5 --> 2 : LOCKER
+    2 --> 6 : REQ
+    6 --> 2 : Entered
+    2 --> 7 : OK
+    7 --> 2 : Conditional
+    state 1 as "1 MS - OFF"
+    state 2 as "2 WAIT"
+    state 3 as "3 Enter-card"
+    state 4 as "4 Enter-PIN"
+    state 5 as "5 Failure - Treatment"
+    state 6 as "6 Enter-PLMN"
+    state 7 as "7 Serv -AV"
+    classDef dotted stroke-dasharray: 5 5;
+    class 3, 4, 6 dotted;
+  
+```
+
+Mealy-graph for the UE access procedure. State 1 (MS - OFF) is the initial state. State 2 (WAIT) is the central state. States 3 (Enter-card), 4 (Enter-PIN), and 6 (Enter-PLMN) are dotted states. State 5 (Failure - Treatment) is a failure state. State 7 (Serv -AV) is the service state. Transitions: 1 to 2 on 'ON'; 2 to 3 on 'REQ', 3 to 2 on 'ICC'; 2 to 4 on 'REQ', 4 to 2 on 'Complete'; 2 to 5 on 'Failure', 5 to 2 on 'LOCKER'; 2 to 6 on 'REQ', 6 to 2 on 'Entered'; 2 to 7 on 'OK', 7 to 2 on 'Conditional'.
+
+Figure A.1: Mealy-graph for the UE access procedure
+
+![Mealy-graph for the In Case of Emergency access procedure. State 2 (Wait) and State 8 (ICE) are shown. Transition from 2 to 8 is labeled 'ICE unlock (***)'. Transition from 8 to 2 is labeled '"End" key'.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg)
+
+```
+
+stateDiagram-v2
+    2 --> 8 : ICE unlock (***)
+    8 --> 2 : "End" key
+    state 2 as "2 Wait"
+    state 8 as "8 ICE"
+  
+```
+
+Mealy-graph for the In Case of Emergency access procedure. State 2 (Wait) and State 8 (ICE) are shown. Transition from 2 to 8 is labeled 'ICE unlock (\*\*\*)'. Transition from 8 to 2 is labeled '"End" key'.
+
+Figure A.2: Mealy-graph for the In Case of Emergency access procedure
+
+Assumptions and requirements:
+
+- 1) Emergency calls shall be possible in all states, except in state 1.
+- 2) Power-off should cause transition to state 1 from all other states.
+- 3) The actions to be taken in state 5 is not defined.
+- 4) Realization of the dotted states (3, 4 and 6) depends upon the network requirements and the type of UE.
+
+## Description of the states of the UE access procedure
+
+- 1) UE-OFF: The UE is in OFF-condition. This means that the equipment is not active as an UE in a PLMN.
+- 2) WAIT: Waiting for the completion of the UE access conditions, which are related to the type of UE and to the PLMN, where in the UE is roaming (e.g. location updating).
+- 3) ENTER CARD: Request for entering of the subscriber card, (e.g. when no built in SIM module is available).
+- 4) ENTER PIN: Request for entering of the correct PIN.
+- 5) FAILURE TREATMENT: Waiting for removal the actual failure condition.
+- 6) ENTER PLMN: Request for selection of PLMN.
+- 7) SERV-AV: The UE is in a ready state. PLMN services are available to the user.
+- 8) In Case of Emergency (ICE) When a star key is pressed three times (\*\*\*), the UE is unlocked and ICE information is available unless the subscriber has decided to prevent the display of the ICE information. If the UE has been locked in the previous state, then only the ICE information is available.
+
+## Description of the transitions between UE access states
+
+- ON: The equipment becomes active as an UE in a PLMN.
+- REQ: A request for user activity.
+- IOC: Insertion of a subscriber card with SIM/USIM-module.
+- COMPLETE: The PIN has been entered.
+- ENTERED: A PLMN choice has been done.
+- FAILURE: A failure condition has occurred in any other state during the UE access procedures.
+- CONDITIONAL: One of the conditions the UE is waiting for in WAIT state has been lost. The UE goes back to the WAIT state.
+- "DONE": The UE access failure condition has been corrected.
+- OK: All the conditions the UE is waiting for in the WAIT state are accomplished.
+- ICE unlock When a star key is pressed three times (\*\*\*), the UE enters the In Case of Emergency (ICE) state unless the subscriber has decided to prevent the display of the ICE information.
+- "End" key The UE goes back to the WAIT state.
+
+# Annex B (normative): Codes for defined Supplementary Services
+
+**Table B.1: Input information for handling of defined Supplementary Services**
+
+|        | Supplementary Service                                                                                                                           | Service Code      | SIA | SIB         | SIC |
+|--------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----|-------------|-----|
+| 22.067 | eMLPP                                                                                                                                           | 75 and 75n        |     | where n=0-4 |     |
+| 22.072 | CD                                                                                                                                              | 66                |     |             |     |
+| 22.081 | CLIP                                                                                                                                            | 30                | -   | -           | -   |
+|        | CLIR                                                                                                                                            | 31                | -   | -           | -   |
+|        | COLP                                                                                                                                            | 76                | -   | -           | -   |
+|        | COLR                                                                                                                                            | 77                | -   | -           | -   |
+|        | In temporary mode, to suppress CLIR for a single call, enter:<br>" * 31 # <called number> SEND "                                                |                   |     |             |     |
+|        | In temporary mode, to invoke CLIR for a single call enter:<br>" # 31 # <called number> SEND "                                                   |                   |     |             |     |
+| 22.082 | CFU                                                                                                                                             | 21                | DN  | BS          | -   |
+|        | CF Busy                                                                                                                                         | 67                | DN  | BS          | -   |
+|        | CF No Reply                                                                                                                                     | 61                | DN  | BS          | T   |
+|        | CF Not Reachable                                                                                                                                | 62                | DN  | BS          | -   |
+|        | all CF                                                                                                                                          | 002               | DN  | BS          | T   |
+|        | all conditional CF                                                                                                                              | 004               | DN  | BS          | T   |
+| 22.083 | WAIT                                                                                                                                            | 43                | BS  | -           | -   |
+|        | HOLD                                                                                                                                            | see section 4.5.5 |     |             |     |
+| 22.084 | MPTY                                                                                                                                            | see section 4.5.5 |     |             |     |
+| 22.087 | UUS Service 1                                                                                                                                   | 361               | R   | -           | -   |
+|        | UUS Service 2                                                                                                                                   | 362               | R   | -           | -   |
+|        | UUS Service 3                                                                                                                                   | 363               | R   | -           | -   |
+|        | all UUS Services                                                                                                                                | 360               | R   | -           | -   |
+|        | If UUS shall be activated when originating a call, enter:<br>" * 36X * R # <called number> SEND"<br>(X is indicating the requested UUS service) |                   |     |             |     |
+
+**Table B.1 (concluded): Input information for handling of defined Supplementary Services**
+
+| Supplementary Service | Service Code | SIA              | SIB                                 | SIC |
+|-----------------------|--------------|------------------|-------------------------------------|-----|
+| <b>22.088</b>         |              |                  |                                     |     |
+| BAOC                  | 33           | PW               | BS                                  | -   |
+| BAOIC                 | 331          | PW               | BS                                  | -   |
+| BAOIC exc home        | 332          | PW               | BS                                  | -   |
+| BAIC                  | 35           | PW               | BS                                  | -   |
+| BAIC roaming          | 351          | PW               | BS                                  | -   |
+| all Barring Serv.     | 330          | PW               | BS                                  | -   |
+| Outg. Barr. Serv.     | 333          | PW               | BS                                  |     |
+| Inc. Barr. Serv.      | 353          | PW               | BS                                  |     |
+| <b>22.091</b>         |              |                  |                                     |     |
+| ECT                   | 96           |                  | see section 4.5.5                   |     |
+| <b>22.093</b>         |              |                  |                                     |     |
+| CCBS                  | 37           | n<br>where n=1-5 | See Section 4.5.5                   |     |
+| <b>22.094</b>         |              |                  |                                     |     |
+| FM                    | 214          |                  | See Section 6.5.6.3                 |     |
+| <b>22.096</b>         |              |                  |                                     |     |
+| CNAP                  | 300          | -                | -                                   | -   |
+| <b>22.097</b>         |              |                  |                                     |     |
+| MSP                   | 59n          | PW               | where n=1-4                         |     |
+| <b>22.135</b>         |              |                  |                                     |     |
+| MC                    | 88           |                  | Nbr_user<br>Where Nbr_user=1-Nbr_SB |     |
+
+DN = Directory Number;
+
+PW = Password (see subclause 4.5.4);
+
+BS = Basic Service Group (if required) – see annex C;
+
+T = No Reply Condition Timer (5-30 seconds);
+
+R = UUS required option.
+
+SI required Y = Yes;
+
+N = No;
+
+- = Not applicable.
+
+Nbr\_user = maximum number of simultaneous CS bearers as defined by the within the limits given by Nbr\_SB.
+
+Nbr\_SB = maximum number of simultaneous CS bearers defined by Multicall subscription.
+
+The value for Nbr\_SB shall in the range from 2 up to 7.
+
+Details about Nbr\_user and Nbr\_SB specified in 3GPP TS22.135 Multicall. [21]
+
+### **"UUS required" option**
+
+For the "UUS required" option two values are defined:
+
+R = 0        UUS not required;  
+R = 1        UUS required.
+
+NOTE: If the "UUS required" option is requested for a call, the call will only be established if the requested UUS capabilities are available.
+
+If the "UUS required" option is not contained in an activation request UUS shall be activated without the UUS required option.
+
+# Annex C (normative): Codes for Tele- and bearer services
+
+Tele- and Bearer Service Supplementary Information codes (SIb).
+
+Alternate and speech/data services are included with the equivalent data service.
+
+## Basic Service
+
+| group number (Note 1) | Telecommunication Service         | MMI Service Code |
+|-----------------------|-----------------------------------|------------------|
+| 1 to 12               | All tele and bearer services      | no code required |
+|                       | Teleservices                      |                  |
+| 1 to 6, 12            | All teleservices                  | 10               |
+| 1                     | Telephony                         | 11               |
+| 2 to 6                | All data teleservices             | 12               |
+| 6                     | Facsimile services                | 13               |
+| 2                     | Short Message Services            | 16               |
+| 1, 3 to 6, 12         | All teleservices except SMS       | 19               |
+| 12                    | Voice group services              |                  |
+|                       | Voice Group Call Service (VGCS)   | 17               |
+|                       | Voice Broadcast Service (VBS)     | 18               |
+|                       | Bearer Service                    |                  |
+| 7 to 11               | All bearer services               | 20               |
+| 7                     | All async services                | 21               |
+| 8                     | All sync services                 | 22               |
+| 8                     | All data circuit sync             | 24               |
+| 7                     | All data circuit async            | 25               |
+| 13                    | All GPRS bearer services (Note 2) | 99               |
+| 1,8                   | Telephony and All sync services   | 26               |
+
+Note 1: See 3GPP TS 22.004 [2] for definition of Basic Service groups.
+
+Note 2: "All GPRS bearer services" are not included in "All tele and bearer services" and "All bearer services".
+
+The grouping implies that if e.g. code 25 is used, the Supplementary Service procedure concerned applies to all Asynchronous Data Circuit mode Bearer Services subscribed to.
+
+## **Tele- and Bearer Service Supplementary Information Codes (SIb) for services not defined by 3GPP**
+
+| <b>Code as defined in<br/>3GPP TS 29.002 [11]</b> | <b>Telecommunication Service</b>  | <b>MMI Service<br/>Code</b> |
+|---------------------------------------------------|-----------------------------------|-----------------------------|
+| <b>PLMN specific teleservices:</b>                |                                   |                             |
+| 11010000                                          | All PLMN specific teleservices    | 50                          |
+| 11010001                                          | PLMN specific teleservice 1       | 51                          |
+| 11010010                                          | PLMN specific teleservice 2       | 52                          |
+| 11010011                                          | PLMN specific teleservice 3       | 53                          |
+| 11010100                                          | PLMN specific teleservice 4       | 54                          |
+| 11010101                                          | PLMN specific teleservice 5       | 55                          |
+| 11010110                                          | PLMN specific teleservice 6       | 56                          |
+| 11010111                                          | PLMN specific teleservice 7       | 57                          |
+| 11011000                                          | PLMN specific teleservice 8       | 58                          |
+| 11011001                                          | PLMN specific teleservice 9       | 59                          |
+| 11011010                                          | PLMN specific teleservice 10      | 60                          |
+| 11011011                                          | PLMN specific teleservice 11      | 61                          |
+| 11011100                                          | PLMN specific teleservice 12      | 62                          |
+| 11011101                                          | PLMN specific teleservice 13      | 63                          |
+| 11011110                                          | PLMN specific teleservice 14      | 64                          |
+| 11011111                                          | PLMN specific teleservice 15      | 65                          |
+| <b>PLMN specific bearer services:</b>             |                                   |                             |
+| 11010000                                          | All PLMN specific bearer services | 70                          |
+| 11010001                                          | PLMN specific bearer service 1    | 71                          |
+| 11010010                                          | PLMN specific bearer service 2    | 72                          |
+| 11010011                                          | PLMN specific bearer service 3    | 73                          |
+| 11010100                                          | PLMN specific bearer service 4    | 74                          |
+| 11010101                                          | PLMN specific bearer service 5    | 75                          |
+| 11010110                                          | PLMN specific bearer service 6    | 76                          |
+| 11010111                                          | PLMN specific bearer service 7    | 77                          |
+| 11011000                                          | PLMN specific bearer service 8    | 78                          |
+| 11011001                                          | PLMN specific bearer service 9    | 79                          |
+| 11011010                                          | PLMN specific bearer service 10   | 80                          |
+| 11011011                                          | PLMN specific bearer service 11   | 81                          |
+| 11011100                                          | PLMN specific bearer service 12   | 82                          |
+| 11011101                                          | PLMN specific bearer service 13   | 83                          |
+| 11011110                                          | PLMN specific bearer service 14   | 84                          |
+| 11011111                                          | PLMN specific bearer service 15   | 85                          |
+
+# Annex D (informative): Change history
+
+| Change history |           |           |        |      |      |        |     |                                                             |        |        |           |
+|----------------|-----------|-----------|--------|------|------|--------|-----|-------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | R ev | Rel    | Cat | Subject/Comment                                             | Old    | New    | Work Item |
+| Jun 1999       |           |           | 02.30  |      |      |        |     | Transferred to 3GPP SA1                                     | 7.1.0  | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99614  | 22.030 | 001  |      | R99    | D   | Editorial changes for alignment                             | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99447  | S1-99744  | 22.030 | 002  |      | R99    | C   | Data services streamlining                                  | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99447  | S1-99664  | 22.030 | 003  |      | R99    | C   | Support for Anonymous Call Rejection                        | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99439  | S1-99847  | 22.030 | 004  |      | R99    | F   | Indication to user in case of an error during Data Download | 3.0.0  | 3.1.0  |           |
+| SP-06          | SP-99519  | S1-991029 | 22.030 | 006  |      | R99    | C   | Mainly an editorial update for GSM/3GPP use.                | 3.1.0  | 3.2.0  |           |
+| SP-07          | SP-000056 | S1-000166 | 22.030 | 007  |      | R99    | B   | Introduction of Service Code 214 for "Follow Me"            | 3.2.0  | 3.3.0  |           |
+| SP-07          | SP-000056 | S1-000172 | 22.030 | 008  |      | R99    | B   | MMI(Man-Machine interface) of Multicall                     | 3.2.0  | 3.3.0  |           |
+| SP-09          | SP-000376 | S1-000501 | 22.030 | 009  |      | R99    | F   | Codes for defined Supplementary Services                    | 3.3.0  | 3.4.0  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.030 |      |      | Rel-4  |     | Transferred to 3GPP Release 4                               | 3.4.0  | 4.0.0  |           |
+| SP-15          | SP-020045 | S1-020457 | 22.030 | 010  | -    | Rel-4  | F   | Editorial CR to correct terms and references                | 4.0.0  | 4.1.0  | CORRECT   |
+| SP-16          | SP-020267 | S1-021043 | 22.030 |      |      | Rel-5  |     | Updated from Rel-4 to Rel5                                  | 4.1.0  | 5.0.0  |           |
+| SP-23          | SP-040097 | S1-040239 | 22.030 |      |      |        |     | Rel-6 created as a byproduct of Rel-7 CR 011.               | 5.0.0  | 6.0.0  |           |
+| SP-23          | SP-040097 | S1-040239 | 22.030 | 011  | -    | Rel-7  | B   | Add a MMI Service Code of UE                                | 5.0.0  | 7.0.0  | CS_VSS    |
+|                |           |           |        |      |      |        |     | 2005-07: Change "Release 5" to "Release 7" on title page.   | 7.0.0  | 7.0.1  |           |
+| SP-39          | SP-080036 | S1-080320 | 22.030 | 0013 | 2    | Rel-8  | B   | ICE: CR to TS 22.030                                        | 7.0.1  | 8.0.0  | ICE       |
+| SP-40          | SP-080302 | S1-080706 | 22.030 | 0014 | -    | Rel-8  | F   | Correction of ICE access procedure                          | 8.0.0  | 8.1.0  | ICE       |
+| SP-46          | -         | -         | -      | -    | -    | -      | -   | Updated to Rel-9 by MCC                                     | 8.1.0  | 9.0.0  |           |
+| 2011-03        | -         | -         | -      | -    | -    | -      | -   | Update to Rel-10 version (MCC)                              | 9.0.0  | 10.0.0 |           |
+| SP-57          | SP-120534 | S1-122440 | 22.030 | 0015 | 2    | Rel-12 | B   | Adding the presentation of e-marking                        | 10.0.0 | 12.0.0 | TEI12     |
+| SP-60          | SP-130196 | S1-133018 | 22.030 | 0018 | 1    | Rel-12 | C   | Displaying of PIN and PIN2 entry to the user                | 12.0.0 | 12.1.0 | TEI12     |
+| -              | -         | -         | -      | -    | -    | -      | -   | Correction of a problem with figure 3.5.3.2                 | 12.1.0 | 12.1.1 | -         |
+| -              | -         | -         | -      | -    | -    | -      | -   | Correction of a problem with figure A.1                     | 12.1.1 | 12.1.2 | -         |
+| SP-70          |           |           |        |      |      |        |     | Upgrade to Rel-13 version (MCC)                             | 12.1.2 | 13.0.0 |           |

marked/Rel-13/22_series/22031/raw.md

@@ -0,0 +1,373 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.031 V13.0.0 (2016-01) ~~Fraud Information Gathering System (FIGS);~~ *Technical Specification* **Service description; Stage 1 (Release 13)****
+
+![Advanced Pro LTE logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for Advanced Pro LTE. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the left of the text is a green signal icon consisting of four curved lines of increasing height.
+
+Advanced Pro LTE logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, which consists of the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. The "P" and "P" are also connected at the top by a single horizontal line. Below the "G" and the first "P" is a red signal icon consisting of three curved lines of increasing height.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+UMTS, GSM, Security, Stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                     |           |
+|-------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                      | 4         |
+| 1 Scope.....                                                                        | 5         |
+| 2 Normative references .....                                                        | 5         |
+| 3 Definitions and abbreviations .....                                               | 5         |
+| 3.1 Definitions.....                                                                | 5         |
+| 3.2 Abbreviations.....                                                              | 6         |
+| 4 Fraud Information Gathering System high level requirements.....                   | 6         |
+| 4.1 Description.....                                                                | 6         |
+| 4.2 Applicability .....                                                             | 6         |
+| 4.3 Normal Procedure .....                                                          | 6         |
+| 5 Service conditions .....                                                          | 7         |
+| 5.1 Control of monitoring of subscriber activities .....                            | 7         |
+| 5.2 Number of calls monitored by a VPLMN.....                                       | 7         |
+| 5.3 Interworking with non-supporting networks .....                                 | 7         |
+| 5.4 Information Delivery Time .....                                                 | 8         |
+| 6 Monitored activity .....                                                          | 8         |
+| 7 Interface between HPLMN and FDS .....                                             | 8         |
+| 8 Security Requirements between HPLMN and VPLMN .....                               | 8         |
+| <b>Annex A (normative): Information transferred by the VPLMN .....</b>              | <b>9</b>  |
+| <b>Annex B (normative): Message flow in FIGS monitoring, normal procedure .....</b> | <b>11</b> |
+| Annex C (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 Technical Specification specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
+
+This specification enables service providers/ network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
+
+HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
+
+# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+
+[2] 3GPP TS 42.033: "Digital cellular telecommunications system (Phase 2+); Lawful Interception - stage 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this specification the following definitions apply:
+
+**A subscriber:** The calling mobile subscriber.
+
+**B subscriber:** The mobile subscriber originally called by the A subscriber.
+
+**C subscriber:** The subscriber to whom the B subscriber has requested that calls be forwarded. The C subscriber may be fixed or mobile.
+
+**call:** both connection-oriented and connectionless services/events.
+
+**call information:** information about a call.
+
+**call reference:** a reference number for a call that shall remain constant throughout the duration of that call and that shall be unique to that call and the switch on which the call was made for a period of at least one week.
+
+**home network:** The home PLMN including non-GSM elements such as the Fraud Detection System (FDS), customer service systems and billing.
+
+**monitored activities:** subscriber activities that shall be reported to the HPLMN. 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).
+
+## 3.2 Abbreviations
+
+Abbreviations used in this specification are also listed in GSM 01.04.
+
+For the purposes of this specification the following abbreviations apply:
+
+|      |                                    |
+|------|------------------------------------|
+| FIGS | Fraud Information Gathering System |
+| FDS  | Fraud Detection System             |
+| IST  | Immediate Service Termination      |
+| MO   | Mobile Originated                  |
+| MT   | Mobile Terminated                  |
+| CGI  | Cell Global Identifier             |
+
+# --- 4 Fraud Information Gathering System high level requirements
+
+## 4.1 Description
+
+It shall be possible for the HPLMN to request the VPLMN to supply certain information about a subscriber from the time the subscriber registers in that VPLMN to the time the last of the monitored activities is finished in that VPLMN, which can be after the subscriber's de-registration from the VPLMN. The information received by the HPLMN shall be passed to the relevant network or service providers and used to instruct the VPLMN to act in an appropriate way.
+
+Fraud information gathering is controlled by the HPLMN and can be activated and deactivated by the HPLMN only.
+
+The information is received in the HPLMN and is forwarded to fraud detection and control systems. Such systems are out of the scope of this standard.
+
+The subscriber is specified by the IMSI or MSISDN.
+
+## 4.2 Applicability
+
+This network feature applies to all subscribed Bearer Services and Teleservices and supplementary services of the subscriber. It is not possible to apply FIGS independently to individual Services.
+
+The HPLMN shall be able to specify whether it would like call information on MO calls, MT calls, or both.
+
+## 4.3 Normal Procedure
+
+The HPLMN shall be able to request a VPLMN to monitor a subscriber.
+
+See Annex A for the definition of the information to be sent for each call event.
+
+If the VPLMN cannot monitor the subscriber, it shall indicate this as a response to the FIGS request.
+
+The FDS will process this information and may then limit the activities of the subscriber using ODB or terminate the subscriber activities using IST, or may allow the subscriber to proceed.
+
+When the home network no longer wishes the subscriber to be monitored by the VPLMN it requests the VPLMN to stop monitoring the activities of the subscriber.
+
+Figure B.1 shows the sequence of FIGS messages passed during a normal case.
+
+# --- 5 Service conditions
+
+## 5.1 Control of monitoring of subscriber activities
+
+The HPLMN can request a VPLMN to begin monitoring the activities of a subscriber when the subscriber has registers on that VPLMN or at any time after registration. If the VPLMN is able to monitor a subscriber as requested it shall send a confirmation of monitoring message to the HPLMN.
+
+The HPLMN does not need to know the status of the target subscriber before initiation or subsequent termination of fraud information gathering.
+
+Fraud information cannot be switched on or off by the subscriber or other (unauthorised) party.
+
+Subscribers upon which fraud information gathering has been set shall not be able by interrogating the network to determine that they are subject to fraud information gathering.
+
+Subscribers upon which fraud information gathering has been set shall not be able, for example by significant changes to normal call set up times, speech quality or general transmission characteristics, to determine that they are subject to fraud information gathering.
+
+If the VPLMN receives a request to monitor the activities of a subscriber and an activity to be monitored is already ongoing it is not necessary for the VPLMN to send information on this particular activity to the HPLMN.
+
+If the VPLMN receives a request to cease monitoring the activities of a subscriber and an activity is already ongoing and being monitored, the VPLMN shall immediately cease sending information on this activity to the HPLMN.
+
+## 5.2 Number of calls monitored by a VPLMN
+
+If the VPLMN has to monitor the activities of a large number of subscribers for FIGS this may degrade the performance of the VPLMN. Each VPLMN (in reality, each network entity involved in FIGS monitoring) will therefore have a maximum number of subscribers that it can monitor.
+
+If the number of monitored subscribers has reached this upper limit the VPLMN shall reject requests for monitoring of subscribers from HPLMNs until the number of monitored subscribers decreases below the limit.
+
+Each VPLMN may have a limit per HPLMN on the number of subscribers from that HPLMN that it will monitor. When an HPLMN has requested a VPLMN to monitor a number of subscribers equal to the limit for that HPLMN, the VPLMN can refuse any subsequent requests for FIGS monitoring from that PLMN, until the number of monitored subscribers drops below the limit. The principles behind the setting of these limits are outside the scope of this specification.
+
+In order to minimise the number of subscribers that a VPLMN has to monitor, the HPLMN should ideally limit itself to requesting information about subscriber's monitored activities in:
+
+- the current VPLMN;
+- the last previously served VPLMN.
+
+## 5.3 Interworking with non-supporting networks
+
+If the HPLMN does not receive a positive acknowledgement to the request for FIGS monitoring sent to a VPLMN, it shall assume that the VPLMN does not support FIGS. The HPLMN may then act as appropriate (e.g. put appropriate ODB categories in place).
+
+## 5.4 Information Delivery Time
+
+The need for up to date information is a critical part of any fraud information system. The sooner data is transferred to the HPLMN, the sooner fraud can be stopped. Therefore the prescribed information shall be transferred from the VPLMN network to the HPLMN within two minutes of the occurrence of a FIGS-monitored event, if real time implementations of FIGS are used.
+
+The information should be transferred from the VPLMN to the HPLMN over appropriate communication links.
+
+# --- 6 Monitored activity
+
+The authorised party can request the VPLMN to monitor both call activity and supplementary services.
+
+The monitoring of call activity shall take the form of transmission of call information from the VPLMN to the HPLMN, at the start and end of all calls. For long calls, the VPLMN shall also send partial call information a certain time (e.g. 15 minutes) after the call has begun.
+
+Call information shall be sent to the HPLMN by the VPLMN on the invocation of all supplementary services, e.g.:
+
+- call deflection;
+- call forwarding;
+- call hold;
+- Multi Party (MPTY);
+- Explicit Call Transfer (ECT).
+
+The HPLMN can decide to prevent future invocation of the same or all supplementary services using ODB. The decision mechanism is out of the scope of this specification.
+
+# --- 7 Interface between HPLMN and FDS
+
+Information gathered by the HPLMN may be transferred to Non-GSM systems, e.g. an FDS. These systems will decide if the monitored activity is fraudulent and will advise the home network to take appropriate action, e.g. send an IST command to the VPLMN, change the subscriber's ODB categories.
+
+The contents of call information messages to be transferred on this interface shall be specified but not the transfer mechanism. This is in line with the approach used for the X-interface as specified in 3GPP TS 42.033. The message formats are defined in annex A.
+
+The system needs the ability to handle the volume of information returned to the home network.
+
+# --- 8 Security Requirements between HPLMN and VPLMN
+
+It is expected that there will be a need for authentication, data integrity and confidentiality of the communication made between PLMNs.
+
+These issues are for study under other work items within the SMG 10 work programme.
+
+# Annex A (normative): Information transferred by the VPLMN
+
+The reports generated by the VPLMN shall take the form of "call information" records for each monitored subscriber. The content of the call information will depend on the type of event (call start, end etc.). To simplify matters, there will be one format for both MO and MT calls with an MO/MT indicator within the call information to distinguish between the two.
+
+A partial call information will be sent to the HPLMN when there is an mid-call invocation of a supplementary service and when a call in progress has exceeded a defined duration.
+
+Justification is given for the content of the call information message.
+
+**Table A.1: Call information content**
+
+| Information           |
+|-----------------------|
+| Dialled digits        |
+| A subscriber          |
+| B subscriber          |
+| C subscriber          |
+| CGI                   |
+| IMSI                  |
+| IMEI                  |
+| Call Start Time/Date  |
+| Call Duration         |
+| Call Reference        |
+| MO/MT indicator       |
+| Visited MSC address   |
+| Type of SS event      |
+| Type of Basic Service |
+
+The **Dialled digits** are required as these are an important indicator in deciding if a call is fraudulent or not - certain call destinations are more likely to be called fraudulently than others.
+
+**A subscriber** can be used to identify the subscriber
+
+**B, C subscriber** are relevant as some call destinations are more subject to fraud than others.
+
+Cell Global Identifier (**CGI**) is relevant as some cells in a PLMN are more subject to fraud than others.
+
+The **IMSI** is used to reference the subscriber.
+
+The **IMEI** can be used to check if a stolen handset has been used.
+
+The **Call Start Time/Date** is required so that the call duration can be calculated (if the call end time and not call duration is given at call conclusion) and because the call start time can also be an important indicator of fraudulence.
+
+The **Call Duration** gives the duration of the call at the sending of the partial call information - call duration can be an important indicator of fraudulence. If call end is sent instead, the duration can be calculated using the call start and end times.
+
+The **Call Reference** is used to reference a particular call.
+
+The **MO/MT indicator** is required because call charging is different for MO and MT calls.
+
+The **Visited MSC address** gives the PLMN on which the call was made.
+
+The **Type of SS event** record is sent if the "call" start is actually the invocation of a supplementary service, e.g. ECT. The Type of SS event is required as this can help to indicate if the mobile is being fraudulently used or not.
+
+The **Type of Basic Service** indicates whether a teleservice or bearer service is being used and which sort of teleservice or bearer service is being used and is sent if the event is a call and not a supplementary service. The Type of Basic Service is required as this can help to indicate if the mobile station is being fraudulently used or not.
+
+## --- Annex B (normative): Message flow in FIGS monitoring, normal procedure
+
+![Sequence diagram showing message flow between HPLMN and VPLMN for FIGS monitoring.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+```
+sequenceDiagram
+    participant HPLMN
+    participant VPLMN
+    Note right of VPLMN: Request for FIGS monitoring
+    VPLMN->>HPLMN: Positive Acknowledgement
+    Note right of VPLMN: FIGS Data
+    VPLMN->>HPLMN: FIGS Data
+    Note right of VPLMN: FIGS Data
+    VPLMN->>HPLMN: FIGS Data
+    Note right of VPLMN: Request to stop FIGS monitoring
+    VPLMN->>HPLMN:
+```
+
+The diagram illustrates the message flow between HPLMN and VPLMN for FIGS monitoring. It consists of two vertical lifelines. The sequence of messages is as follows: 1. A message labeled 'Request for FIGS monitoring' is sent from VPLMN to HPLMN. 2. A message labeled 'Positive Acknowledgement' is sent from HPLMN to VPLMN. 3. A message labeled 'FIGS Data' is sent from VPLMN to HPLMN. 4. Another message labeled 'FIGS Data' is sent from VPLMN to HPLMN. 5. A third message labeled 'FIGS Data' is sent from VPLMN to HPLMN. 6. A message labeled 'Request to stop FIGS monitoring' is sent from VPLMN to HPLMN.
+
+Sequence diagram showing message flow between HPLMN and VPLMN for FIGS monitoring.
+
+Figure B.1: Message flow in FIGS monitoring, normal procedure
+
+## Annex C (informative): Change history
+
+| <b>Change history GSM 02.31</b>      |              |                 |           |            |                                                                                                                                            |                  |                  |
+|--------------------------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|
+| <b>Date</b>                          | <b>TSG #</b> | <b>TSG Doc.</b> | <b>CR</b> | <b>Rev</b> | <b>Subject/Comment</b>                                                                                                                     | <b>Old</b>       | <b>New</b>       |
+|                                      |              |                 |           |            | No Phase 1 version                                                                                                                         |                  |                  |
+| 06-1997                              | SMG#22       |                 |           |            | To SMG#22 for information                                                                                                                  |                  | 1.0.0            |
+| 10-1997                              | SMG#23       |                 |           |            | To SMG#23 for approval                                                                                                                     |                  | 2.0.0            |
+| 10-1997                              | SMG#23       |                 |           |            | TS approved by SMG#23                                                                                                                      | 2.0.0            | 5.0.0            |
+| 03-1998                              | SMG#25       |                 |           |            | The specification was converted to version 7.0.0 because the work item is related to Release 98; <b>version 5.0.0 withdrawn.</b> (SMG#25)  | 5.0.0            | 7.0.0            |
+| 06-1998                              | SMG#26       |                 | A001      | 1          | CR 02.31-A001r1 (correction) approved by SMG#26                                                                                            | 7.0.0            | 7.1.0            |
+| 08-1999                              |              |                 |           |            | Publication version                                                                                                                        | 7.1.0            | 7.1.1            |
+| 04-2000                              |              |                 |           |            | Release 1999 publication version                                                                                                           | 7.1.1            | 8.0.0            |
+| 06-2001                              |              |                 |           |            | ETSI Publication                                                                                                                           | 8.0.0            | 8.0.1            |
+| <b>Change history 3GPP TS 42.031</b> |              |                 |           |            |                                                                                                                                            |                  |                  |
+| <b>Date</b>                          | <b>TSG #</b> | <b>TSG Doc.</b> | <b>CR</b> | <b>Rev</b> | <b>Subject/Comment</b>                                                                                                                     | <b>Old</b>       | <b>New</b>       |
+| 03-2001                              | SA#11        |                 |           |            | Upgrade to Release 4 (3GPP numbering)                                                                                                      | 02.31<br>V8.0.0  | 42.031<br>V4.0.0 |
+| 06-2002                              | SA#16        |                 |           |            | Upgrade to Release 5                                                                                                                       | 4.0.0            | 5.0.0            |
+| <b>Change history 3GPP TS 22.031</b> |              |                 |           |            |                                                                                                                                            |                  |                  |
+| <b>Date</b>                          | <b>TSG #</b> | <b>TSG Doc.</b> | <b>CR</b> | <b>Rev</b> | <b>Subject/Comment</b>                                                                                                                     | <b>Old</b>       | <b>New</b>       |
+| 12-2002                              | SA#18        |                 |           |            | Agreed to convert to 3GPP/GSM joint numbering scheme.<br><b>42.031 WITHDRAWN.</b><br><b>Technically equivalent to 42.031 version 5.0.0</b> | 42.031<br>v5.0.0 | 22.031<br>v5.0.0 |
+| 12-2004                              | SA#26        | -               | -         | -          | <a href="#">Upgrade to Release 6</a>                                                                                                       | 5.0.0            | 6.0.0            |
+| 06-2007                              | SA#36        | -               | -         | -          | <a href="#">Upgrade to Release 7</a>                                                                                                       | 6.0.0            | 7.0.0            |
+| 12-2008                              | SA#42        | -               | -         | -          | <a href="#">Upgrade to Release 8</a>                                                                                                       | 7.0.0            | 8.0.0            |
+| 12-2009                              | SA#46        | -               | -         | -          | <a href="#">Upgrade to Release 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           | 11.0.0           |
+| 2014-09                              | -            | -               | -         | -          | <a href="#">Update to Rel-12 version (MCC)</a>                                                                                             | 11.0.0           | 12.0.0           |
+| 2015-12                              |              |                 |           |            | <a href="#">Update to Rel-13 version (MCC)</a>                                                                                             | 12.0.0           | 13.0.0           |

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

@@ -0,0 +1,210 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** 3GPP TS 22.032 V13.0.0 (2016-01) --- **Immediate Service Termination (IST);** *Technical Specification* **Service description; Stage 1** **(Release 13)**
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font with a small "TM" symbol. Above the "e" is the text "Advanced Pro" in a smaller font. To the left of the text is a green signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold font. Below the "P" is a small red signal icon consisting of three curved lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+ This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.  
+ Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+GSM, UMTS, IST, Security, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- 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)              | <b>02.32</b><br>8.0.0  | <b>42.032</b><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 | <b>42.032</b><br>4.0.0 | <b>22.032</b><br>4.0.0 |
+| 06-2002                                                         | SP-16  |          |      |     |     | Upgrade to Rel-5                                          | 4.0.0                  | 5.0.0                  |
+| 12-2004                                                         | SP-26  |          |      |     |     | Upgrade to Rel-6                                          | 5.0.0                  | 6.0.0                  |
+| 06-2007                                                         | SP-36  |          |      |     |     | Upgrade to Rel-7                                          | 6.0.0                  | 7.0.0                  |
+| 12-2008                                                         | SP-42  | --       | --   | --  | --  | Upgrade to Rel-8                                          | 7.0.0                  | 8.0.0                  |
+| 12-2009                                                         | SP-46  | -        | -    | -   | -   | Upgrade to Rel-9                                          | 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                 |
+| 2014-09                                                         | -      | -        | -    | -   | -   | Update to Rel-12 version (MCC)                            | 11.0.0                 | 12.0.0                 |
+| 2015-12                                                         |        |          |      |     |     | Update to Rel-13 version (MCC)                            | 12.0.0                 | 13.0.0                 |

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

@@ -0,0 +1,489 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; High Speed Circuit Switched Data (HSCSD);** ---
+
+**3GPP TS 22.034 V13.0.0 (2016-01)**
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font. The '3' is bold and black, the 'G' is black, the 'P' is black, and the 'P' is black. There is a small red signal icon below the 'G'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+## Keywords
+
+---
+
+GSM, UMTS, data, circuit mode
+
+## **3GPP**
+
+## Postal address
+
+## --- 3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |           |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                 | 11.0.0 | 12.0.0 |           |
+| 2015-12        |           |           |        |     |     |       |     | Update to Rel-12 version (MCC)                                 | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22038/raw.md

@@ -0,0 +1,792 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.038 (5) SIM Application Toolkit (USAT); Service description; *Technical Specification* Stage 1 (Release 13)** ---
+
+![Advanced Pro LTE logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for Advanced Pro LTE. It features the word "Advanced" in a small font above the word "Pro" in a red font, both positioned above the letters "lte" in a large, bold, black font. A green signal icon is located above the word "Advanced". A small "TM" symbol is at the bottom right of the "lte" text.
+
+Advanced Pro LTE logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, black font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+UMTS, GSM, Card, SIM, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                    |    |
+|--------------------------------------------------------------------|----|
+| Foreword .....                                                     | 5  |
+| 1 Scope.....                                                       | 6  |
+| 2 References.....                                                  | 6  |
+| 2.1 Normative references .....                                     | 7  |
+| 3 Definitions and abbreviations .....                              | 7  |
+| 3.1 Definitions.....                                               | 7  |
+| 3.2 Abbreviations .....                                            | 8  |
+| 4 Description.....                                                 | 8  |
+| 5 High level USAT requirements.....                                | 9  |
+| 6 SAT/USAT/ME interface requirements.....                          | 10 |
+| 6.1 (U)SAT APIs.....                                               | 10 |
+| 6.2 USAT proactive capability.....                                 | 10 |
+| 6.3 ME Capability for support of bearer independent protocol ..... | 11 |
+| 6.4 ME equipped with positioning features .....                    | 12 |
+| 7 USAT User Interface requirements.....                            | 12 |
+| 7.1 Data presentation requirements (e.g. Display).....             | 12 |
+| 7.2 Data acquisition requirements (e.g. Keypad).....               | 12 |
+| 7.3 Access requirements (e.g. Menu).....                           | 12 |
+| 7.4 Menu capability.....                                           | 12 |
+| 7.4.1 Set up capability .....                                      | 12 |
+| 7.4.2 Selection capability .....                                   | 13 |
+| 7.5 Soft-key capability .....                                      | 13 |
+| 7.6 User control of the SAT/USAT execution environment.....        | 13 |
+| 7.7 MMS presentation requirements .....                            | 13 |
+| 8 Network interface requirements.....                              | 13 |
+| 8.1 USAT/Network interaction .....                                 | 13 |
+| 8.2 Communication control capability .....                         | 13 |
+| 8.3 Service Interworking requirements .....                        | 14 |
+| 9 USAT data exchange capabilities requirements .....               | 14 |
+| 9.1 Data exchange capabilities supported .....                     | 14 |
+| 10 Charging requirements.....                                      | 14 |
+| 11 Security requirements .....                                     | 15 |
+| 11.1 Secure Environment requirements .....                         | 15 |
+| 12 Emergency calls .....                                           | 15 |
+| 13 Roaming .....                                                   | 15 |
+| 14 Interaction with supplementary services.....                    | 16 |
+| 14.1 General .....                                                 | 16 |
+| 14.2 Line Identification .....                                     | 16 |
+| 14.2.1 Calling Line Identification Presentation (CLIP) .....       | 16 |
+| 14.2.2 Calling Line Identification Restriction (CLIR) .....        | 16 |
+| 14.2.3 Connected Line Identification Presentation (COLP).....      | 16 |
+| 14.2.4 Connected Line Identification Restriction (COLR) .....      | 16 |
+| 14.3 Call Forwarding.....                                          | 16 |
+| 14.3.1 Call Forwarding Unconditional (CFU) .....                   | 16 |
+| 14.3.2 Call Forwarding Busy (CFB) .....                            | 16 |
+| 14.3.3 Call Forwarding on No Reply (CFNRy) .....                   | 16 |
+| 14.3.4 Call Forwarding on Not Reachable (CFNRc) .....              | 16 |
+| 14.4 Call Completion .....                                         | 16 |
+| 14.4.1 Call Hold (CH) .....                                        | 16 |
+| 14.4.2 Call Waiting (CW) .....                                     | 17 |
+
+|                        |                                                                                                  |    |
+|------------------------|--------------------------------------------------------------------------------------------------|----|
+| 14.5                   | Multi Party (MPTY).....                                                                          | 17 |
+| 14.6                   | Closed User Group (CUG).....                                                                     | 17 |
+| 14.7                   | Advice of Charge (AoC).....                                                                      | 17 |
+| 14.8                   | Call Barring.....                                                                                | 17 |
+| 14.8.1                 | Barring of all outgoing calls.....                                                               | 17 |
+| 14.8.2                 | Barring of outgoing international calls.....                                                     | 17 |
+| 14.8.2.1               | Mobile originated calls .....                                                                    | 17 |
+| 14.8.2.2               | Forwarded Calls.....                                                                             | 17 |
+| 14.8.3                 | Barring of outgoing international calls except those directed to the HPLMN country .....         | 17 |
+| 14.8.4                 | Barring of all incoming calls .....                                                              | 17 |
+| 14.8.5                 | Barring of incoming calls when roaming .....                                                     | 17 |
+| 14.9                   | Explicit Call Transfer (ECT).....                                                                | 17 |
+| 14.10                  | Completion of Call to Busy Subscriber (CCBS).....                                                | 18 |
+| 14.11                  | Multiple Subscriber Profile (MSP) .....                                                          | 18 |
+| 15                     | Interaction with network features .....                                                          | 18 |
+| 15.1                   | Interactions with Operator Determined Barring (ODB) .....                                        | 18 |
+| 15.1.1                 | Barring of all outgoing calls .....                                                              | 18 |
+| 15.1.2                 | Barring of all outgoing international calls.....                                                 | 18 |
+| 15.1.3                 | Barring of all outgoing international calls except those directed to the home PLMN country ..... | 18 |
+| 15.1.4                 | Barring of outgoing calls when roaming outside the home PLMN country .....                       | 18 |
+| 15.1.5                 | Barring of outgoing premium rate calls.....                                                      | 18 |
+| 15.1.6                 | Barring of incoming calls .....                                                                  | 18 |
+| 15.1.7                 | Barring of incoming calls when roaming outside the home PLMN country .....                       | 18 |
+| 15.1.8                 | Operator Specific Barring.....                                                                   | 18 |
+| 15.1.9                 | Barring of Supplementary Services Management.....                                                | 19 |
+| 15.2                   | Interactions with Optimal Routing (OR).....                                                      | 19 |
+| 15.3                   | Interactions with MExE .....                                                                     | 19 |
+| 15.4                   | Interactions with CAMEL.....                                                                     | 19 |
+| 16                     | Compatibility of USAT ME's and applications.....                                                 | 19 |
+| 16.1                   | USAT Classification .....                                                                        | 19 |
+| 16.2                   | ME/USIM operation.....                                                                           | 20 |
+| 16.3                   | ME/UICC capability information exchange .....                                                    | 20 |
+| 16.4                   | ME and compatibility.....                                                                        | 20 |
+| 16.5                   | Void.....                                                                                        | 20 |
+| 17                     | Void.....                                                                                        | 20 |
+| Annex A (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.
+
+# 1 Scope
+
+This 3GPP Technical Specification defines the stage one description of the USIM application Toolkit (USAT). Stage one is an overall service description, primarily from the subscriber's and serving environment's points of view, and does not deal with the details of the human interface itself.
+
+This TS includes information applicable to network operators, serving environments and terminal, switch and database manufacturers.
+
+This TS contains the core requirements for a USIM application Toolkit (USAT) which are sufficient to provide a complete service.
+
+It is highly desirable however, that technical solutions for a USIM application Toolkit (USAT) are sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+![Diagram illustrating the scope of this TS. It shows a Mobile Equipment (ME) connected to a PLMN cloud, which is further connected to a SAT/USAT Server(s) cloud. The ME is shown with a SIM/USIM card, which is divided into GSM/UMTS and SAT/USAT sections. Arrows indicate the flow of communication between the ME, the PLMN, and the SAT/USAT Server(s). A label 'Scope of this TS' points to the ME and the PLMN connection.](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg)
+
+The diagram illustrates the scope of the specification. On the left, a rectangular box labeled 'ME' (Mobile Equipment) is shown. Below it, a SIM/USIM card is depicted, divided into two sections: 'GSM/UMTS' and 'SAT/USAT'. Double-headed arrows connect the ME to both sections of the SIM/USIM. To the right, a cloud labeled 'PLMN' is connected to the ME by a double-headed arrow. Another cloud labeled 'SAT/USAT Server(s)' is connected to the PLMN cloud. A label 'Scope of this TS' has an arrow pointing to the connection between the ME and the PLMN cloud.
+
+Diagram illustrating the scope of this TS. It shows a Mobile Equipment (ME) connected to a PLMN cloud, which is further connected to a SAT/USAT Server(s) cloud. The ME is shown with a SIM/USIM card, which is divided into GSM/UMTS and SAT/USAT sections. Arrows indicate the flow of communication between the ME, the PLMN, and the SAT/USAT Server(s). A label 'Scope of this TS' points to the ME and the PLMN connection.
+
+**Figure 1: Scope of this TS**
+
+As indicated in Figure 1, the scope of this TS encompasses the USAT functionality in the UE (comprising USIM and ME) and the interaction with the PLMN environment. The USAT Server is not necessarily a separate entity as shown in the figure; nodes providing USAT services may also exist within the PLMN. The functionalities of the USAT servers (such as charging aspects, security level classification etc.) are not covered by this specification.
+
+The requirements are considered to be applicable to both GSM and UMTS systems.
+
+# 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*.
+
+## 2.1 Normative references
+
+- [1] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics".
+- [2] Void.
+- [3] Void.
+- [4] 3GPP TS 51.011: "Specification of the Subscriber Identity Module, Mobile Equipment (SIM - ME) interface" Release 4.
+- [5] Void.
+- [6] Void.
+- [7] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [8] Void.
+- [9] Void.
+- [10] Void.
+- [11] Void.
+- [12] Void.
+- [13] Void.
+- [14] 3GPP TS 31.111: "USIM Application Toolkit (USAT)".
+- [15] 3GPP TS 31.102: "Characteristics of the USIM Application".
+- [16] 3GPP TS 22.140: "Multimedia Messaging Service (MMS); Stage 1".
+- [17] 3GPP TS 51.014: "Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface" Release 4.
+- [18] ETSI TS 102 240: "UICC Application Programming Interface and Loader Requirements; Service description" Release 6.
+- [19] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1"..
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this TS the following definitions apply:
+
+**applet:** a small program that is intended not to be run on its own, but rather to be embedded inside another application.
+
+**application:** USAT information in the form of software, applications, associated resources (e.g. libraries) and/or data.
+
+**bearer independent protocol:** Mechanism at the interface between the USIM and the ME which provide access to the data bearers supported by the ME.
+
+**buffer:** A dedicated memory used to temporarily store data to be sent and/or retrieved.
+
+**content:** data and/or information associated with, or independent of, a particular application which may be presented to or collected from a user.
+
+**data channel:** allow the USIM and the network to exchange data using a selected data exchange capability.
+
+**link:** radio resource.
+
+**USAT service:** a service enhanced (or made possible) by USAT technology.
+
+**USAT execution environment:** the USAT execution environment provides the mechanisms to operate single or multiple USAT-applications.
+
+**USAT serving environment:** an entity which delivers USAT services to the subscriber. This is normally the PLMN operator, but could be an entity with USAT responsibility (which may have been delegated by the PLMN operator).
+
+**USAT subscriber:** the owner of a PLMN subscription who has entered into an agreement with a USAT serving environment for USAT services. Access to USAT services through other types of networks is out of scope of this specification.
+
+**USAT server:** a node supporting USAT services in the USAT service environment.
+
+**user:** the user of a USAT UE, who may or may not be the subscriber.
+
+**(U)SIM:** SIM and/or USIM.
+
+## 3.2 Abbreviations
+
+For the purposes of this TS the following abbreviations apply:
+
+|       |                                                           |
+|-------|-----------------------------------------------------------|
+| API   | Application Programming Interface                         |
+| CAMEL | Customized Applications for Mobile network Enhanced Logic |
+| CS    | Circuit Switched                                          |
+| CSE   | CAMEL Service Environment                                 |
+| IN    | Intelligent Network                                       |
+| ME    | Mobile Equipment                                          |
+| MExE  | Mobile Execution Environment                              |
+| MMI   | Man Machine Interface                                     |
+| NO    | Network Operator                                          |
+| PLMN  | Public Land Mobile Network                                |
+| SAT   | SIM Application Toolkit                                   |
+| SCI   | Subscriber Controlled Input                               |
+| SIM   | Subscriber Identity Module                                |
+| UE    | User Equipment                                            |
+| USAT  | USIM Application Toolkit                                  |
+| USIM  | Universal Subscriber Identity Module                      |
+
+Further abbreviations are given in TS 21.905 [7].
+
+# --- 4 Description
+
+USAT provides a standardised execution environment for applications stored on the UICC and the ability to utilize certain functions of the supporting mobile equipment. USAT provides mechanisms which allow applications, existing in the UICC, to interact and operate with any ME which supports the specified mechanism(s) thus ensuring interoperability between a UICC and an ME, independent of the respective manufacturers and operators. A transport mechanism is provided enabling applications to be down-loaded and/or updated.
+
+A significant aspect of USAT is the highly secure environment provided by the UICC. This is further enhanced by the fact that the subscriber and the issuer of the UICC and also the USAT applications have a "trusted relationship" (e.g. the subscriber trusts the issuer of the UICC to charge correctly for the resources used). This allows certain features, such as call control, to be implemented with a degree of freedom which would not be acceptable in a "non-trusted relationship".
+
+The introduction of the USAT execution environment into UEs (i.e. ME+USIM) is a significant step forward in their evolution. The ability of UEs to support USAT represents an extension of the UE's and PLMN capabilities. In order to allow current and future technologies to exploit and benefit from this, a standardized means of exchanging the MEs' and USIMs' capability profiles is supported.
+
+This Technical Specification defines an enhancement of the USIM/ME interface.
+
+# --- 5 High level USAT requirements
+
+The requirements described in the present document apply independently of the UICC/ME interfaces described in TS 31.101 [1]. However, this may imply different technical implementations of these requirements depending on the used interface (e.g. ISO or HSP), in order to optimize the USAT implementation.
+
+The high level requirements of USAT are as follows:-
+
+- provide the user with additional user interface functionalities to control and invoke services (e.g. menus, icons, etc.) ;
+- to provide means for the user to personalize applications by means of parameters, if such parameters are made available by the application;
+- provide support of a wide variety of applications;
+- provide the means for USAT to interact with the user via the input and output devices of the ME;
+- the means to transfer applications automatically or on demand to the USIM from a USAT server, and upgrade existing applications via the PLMN;
+- the means to transfer content automatically or on demand to or from the USIM from or to a USAT server;
+- the means to transfer content directly from one USAT application to a second UE with a USAT application via the PLMN;
+- the need for an inherent security architecture such that it shall be possible for both the USAT and USAT server sides of a connection to be authenticated (possibly implicitly by the use of digital signature or ciphering). The USAT server shall maintain security of subscribers' personal data and PLMN data;
+- it shall be possible to charge subscribers for the use of PLMN or third party USAT services;
+- the means for USAT applications on the USIM to communicate with other PLMN nodes;
+- the means for the ME and USIM to exchange USAT capability information;
+- provision of USAT API(s) to facilitate the development and downloading of USAT applications;
+- It may be possible for the user to activate and deactivate the USIM/SIM application execution environment; in this case the ME shall initiate a new USIM session.- the means for the network operator to provide and manage the USAT execution environment resources and also to provide and manage (i.e. identify version, activate, deactivate, delete, modify, download etc.) the applications;
+- the means for the USAT application to fully control the display of all actions and network-responses related to the operation of the application. Optionally under user control the ME may display the individual actions/responses;
+- the means for the USAT application to control the PLMN services/supplementary services and IP multimedia services via the standardized MMI. Only the originator (i.e. either user or USAT application) of the action shall directly receive the results/responses of that action (e.g. network response to an SCI). Optionally under user control the ME may display the individual actions/responses.
+- provide the user with additional user interface functionality to control and invoke IP multimedia services
+
+Some of the above requirements are subsequently elaborated.
+
+# --- 6 SAT/USAT/ME interface requirements
+
+## 6.1 (U)SAT APIs
+
+The (U)SIM-API is defined in ETSI TS 102 240 [18]. This API is valid for (U)SAT and is referred to in this TS as (U)SAT API.
+
+The (U)SAT API for the UICC shall allow application programmers easy access to the functions and data described in 3GPP TS 51.011 [4], TS 31.101 [1], TS 31.102 [15], TS 51.014 [17], TS 31.111 [14], such that (U)SIM based services can be developed and loaded onto UICCs (independent of the UICC manufacturer), quickly and, if necessary, remotely, after the card has been issued. The (U)SAT API shall support pro-active functions as described in 3GPP TS 51.014 [17] and TS 31.111 [14], and transport functions as described in 3GPP TS 51.011 [4] and TS 31.102 [15].
+
+## 6.2 USAT proactive capability
+
+The USAT proactive capability is a mechanism whereby the UICC can request specific actions to be taken by the ME by issuing "proactive commands" thus establishing and maintaining an interactive dialogue with the user and/or communicating with the network or an external device.
+
+An ME may have a variety of configurations, for example, it may consist of a modem connected to an external display. The USAT proactive capability requirements are applicable to the ME as a whole without regard to any particular configuration.
+
+The ME shall inform the UICC of the success or otherwise of each command issued to it by the UICC, and also indicate the command details and if applicable add more specific information.
+
+The proactive command set allows the USAT to instruct the ME to:
+
+- 1 display text supplied by the USAT on the ME's display, with an indication of priority (normal or high), and a defined action (user activity or timeout) to terminate the text display.
+- 2 display a text string and obtain the response in the form of a single user keystroke or a string of keys entered by the user and pass the response to the UICC. If the response is designated as private by the UICC the ME shall not display the users response on the screen.
+- 3 set up a voice call to an address with a specific priority as indicated by the UICC with all parameters indicated by the UICC.
+- 4 set up a data call to an address with specific bearer capability and priority, all parameters are indicated by the UICC.
+- 5 set up and manage a data channel (using CSD, Packet service bearer (e.g.: GPRS, UTRAN packet service, HSDPA, ...), SMS, USSD or I-WLAN) between the UICC and an address using information provided by the UICC. It shall be possible for the USAT application to provide the ME with the network connectivity parameters to be used (e.g. PDP context parameters) to establish IP connectivity between a USAT application and a remote entity.
+- 6 send data through a previously set up data channel. The UICC informs the ME if the data is to be sent immediately.
+- 7 retrieve data from the ME that has previously been received via a data channel set up using (5) above. The UICC informs the ME as to how much data it expects to retrieve.
+- 8 send a short message to the network. The short message text is supplied by the UICC to the ME in either packed or unpacked SMS 7-bit alphabet, or UCS2 alphabet.
+- 9 send a SS control, SS MMI string or USSD string, indicating which alphabet is used where applicable.
+- 10 play a tone in the appropriate audio device.
+- 11 negotiate, within reasonable tolerances, a periodic "polling" of the USIM Toolkit.
+- 12 refresh the image (if applicable) of the USIM data contained in the ME memory, either entirely, or partially, or instruct the ME to re-initialize completely.
+- 13 set up an event list in the ME such that the UICC is informed by the ME when an indicated event has occurred.
+- 14 set up an additional menu in the ME, by issuing the ME with a menu list, and allow indication back to the UICC of the user selected menu item.
+- 15 provide requested information from the ME to the UICC, for example the MCC, MNC and IMEI.
+
+- 16 communicate bi-directionally with an auxiliary device, e.g. a second card reader.
+- 17 set up, refresh and interrogate several timers, and inform the UICC when these expire, within reasonable tolerances.
+- 18 display additional MMI information such as display information or tones with commands that employ network resources, with an indication to the ME as to the required level of ME generated MMI as a result of the interaction with the network.
+- 19 allow the ME to display help information with the commands, by providing the associated text, related to the user action (e.g. menu selection).
+- 20 Provide indication from the ME to the USAT when a key on the MMI has been pressed in a "menu" (response to prompt) or and event (independent action) methods, with key identification. This indication shall be done in a secure manner.
+- 21 send a MM to the network, using a data channel as (5) above. The MM content is supplied by the ME or the UICC.
+- 22 start an ME-based application that the USAT application knows about. For example USAT applications have the ability to launch a micro-browser if provided by the ME as already described in this document (see Interactions with MExE), or may ask the ME to initiate a data synchronisation process.
+
+Note: addressing of ME applications and other relevant parameters if needed, shall be properly defined by the corresponding USAT specifications.
+
+- 23 Provide location information from the ME to the UICC (e.g. GPS, A-GPS, Galileo, etc) if the ME is equipped with a positioning feature.
+- 24 Provide a list of the CSG identities available application for selection together with the corresponding HNB Names from the ME to the UICC applications, if available to the ME.
+- 25 Inform the UICC applications when selecting and leaving a CSG cell and to provide the corresponding CSG identity and HNB Name, if HNB Name is available.
+
+Unless otherwise stated the following shall apply:
+
+- The format of text to be displayed is designated by the UICC and is either SMS default alphabet (packed or unpacked) or UCS2 alphabet.
+- The format of the response from the ME is designated by the UICC and is either keypad digit (0-9, \*, #, +), SMS default alphabet characters or UCS2 alphabet characters.
+
+## 6.3 ME Capability for support of bearer independent protocol
+
+The ME supporting bearer independent protocol shall provide to the USIM a common interface for any type of data bearer. This interface is in addition to dedicated commands (e.g. SMS, SS and USSD) for USAT application to exchange data with entities outside the UICC.
+
+The communication is initiated by the UICC. The ME negotiates with the UICC and the addressed entity to establish the optimum channel considering the UICC request, the network and ME capabilities.
+
+The ME is responsible for maintaining and restoring the link should there be a link error.
+
+## 6.4 ME equipped with positioning features
+
+It shall be possible for the UICC to request the current location information from the ME for USAT applications if the ME is equipped with a positioning feature capable of operating in autonomous, MS Assisted or MS Based modes (e.g. GPS, A-GPS, Galileo, etc).
+
+It shall be possible for the UICC to detect the presence of a positioning feature in the Terminal Profile if the ME is equipped with a positioning feature.
+
+The ME shall inform the UICC if the location feature is disabled when the UICC requests the ME to send the location information.
+
+The ME shall inform the UICC if the location information retrieval is not possible (e.g. due to lack of GPS coverage) when the UICC requests the ME to send the location information.
+
+The UICC request for location information shall be treated in accordance with the principles defined in TS 22.071 [19].
+
+# --- 7 USAT User Interface requirements
+
+## 7.1 Data presentation requirements (e.g. Display)
+
+In order to be able to create and operate applications with a homogeneous display(s) USAT shall fully control the display of all actions and all network-responses concerned with the operation of the application. USAT shall, upon completion/closure of the application, return full control to the ME.
+
+The display of information shall be either in the form of text (i.e. alphanumeric characters) or in graphical form or both.
+
+Optionally under user control the ME may display the individual actions/network responses.
+
+## 7.2 Data acquisition requirements (e.g. Keypad)
+
+In order to be able to create and operate applications with a homogeneous user interface USAT shall fully control the function associated with the user input for example via the keypad of the ME. Exceptions to this are keys which are "dedicated ME keys" such as the ON/OFF key. USAT shall, upon completion/closure of the application, return full control to the ME.
+
+## 7.3 Access requirements (e.g. Menu)
+
+A simple, powerful method for the user to access and interact with certain USAT applications shall be provided.
+
+It shall be possible for the USAT-Application to set up a user interface (e.g. menu, icons) via the capabilities provided by the ME to allow the user to interact with a USAT application using, for example, the display and keypad.
+
+## 7.4 Menu capability
+
+### 7.4.1 Set up capability
+
+The menu set up capability is a mechanism whereby the menu items (menu entries/structure etc.) required by the USAT is indicated to the ME by means of a proactive command. The menu set up capability is not directly available to the user. As an option this may include "help information" items.
+
+### 7.4.2 Selection capability
+
+The menu selection capability is a mechanism whereby the menu item selected by the user is indicated to the USAT by the ME via the UICC-ME interface. As an option this may include "help information" items.
+
+## 7.5 Soft-key capability
+
+The soft-key allocation capability is a mechanism whereby the UICC indicates to the ME the text to be displayed and the USAT function which is to be assigned to a ME soft-key.
+
+## 7.6 User control of the SAT/USAT execution environment
+
+The user may be able to control the USAT execution environment via the ME in accordance with the following cases:
+
+- i) the USAT execution environment is enabled/disabled
+- ii) the USAT execution environment is not allowed to make automatic calls
+- iii) the USAT execution environment is allowed to make automatic calls but only with user confirmation
+- iv) the USAT execution environment is allowed to make automatic calls without user confirmation.
+
+In addition it shall be possible for the user to independently enable/disable the AT command feature.
+
+Note that for ease of reading the term "automatic call" is used but this shall be taken to mean any network interaction initiated by USAT including SMS, USSD etc. but excluding user initiated interactions modified by USAT.
+
+The user shall be notified by the ME if service access is prevented as the result of partially disabling the USAT execution environment. It shall be possible to enable the USAT execution environment if service access has been prevented.
+
+## 7.7 MMS presentation requirements
+
+The USAT shall be able to request the ME to present to the user a Multimedia Message (i.e. via the MMS user agent in the ME) stored in the UICC (see TS 22.140 [16]).
+
+# --- 8 Network interface requirements
+
+## 8.1 USAT/Network interaction
+
+USAT/Network interaction is required such that the USAT and the network can bi-directionally exchange data through the ME, employing any of the transport mechanisms defined in the section "USAT data exchange capabilities requirements".
+
+## 8.2 Communication control capability
+
+The communication control capability is a mechanism whereby the use of communication resources is either initiated by the USAT application or modified by the USAT application subsequent to a user action. If supported by the ME, the ME shall, at the time of the user initiated communication request, inform the UICC of the current cell location identity. The UICC shall indicate to the ME if the presentation of information (display, tones etc.) shall be restricted to the explicit presentation of USAT supplied information or if it is required to present standard PLMN information (e.g. network responses) in addition to the USAT supplied information.
+
+It shall be possible for the UICC:
+
+- to initiate and terminate a (UICC initiated) communication request with or without explicit confirmation by the user
+- to allow, bar or modify a communication request initiated by the user
+- to replace a user initiated communication request by another communication request (e.g. replace call request by an SS action etc.).
+
+It shall be possible for the SAT/USAT serving environment to enable/disable the communication control capability. As an option, dependant on the subscribers subscription and the application, the user may enable/disable the communication control capability via a SAT/USAT serving environment and/or under the control of the Network Operator. The user shall be notified by the ME in case network service is lost as the result of disabling the communication control capability.
+
+The communication control capability applies to all mobile originated requests independent of the applicable data exchange capability. Explicitly it applies to voice calls, IMS based communications and to all services listed in the section "USAT data exchange capabilities requirements" (e.g. SMS, supplementary service, circuit switched connection, packet switched connection, etc.).
+
+## 8.3 Service Interworking requirements
+
+The USAT application shall be able to use all PLMN services and supplementary services (SS) including those functions available to the user via the standardized MMI (e.g. 2 SEND for Call Hold). Only the originator (i.e. either user or USAT application) of the action shall directly receive the results/responses of that action (e.g. network response to an SCI). Optionally under user control the ME may display the individual actions/responses.
+
+# 9 USAT data exchange capabilities requirements
+
+## 9.1 Data exchange capabilities supported
+
+USAT shall support the transmission (mobile originated) and the reception (mobile terminated) of data by means of one of the following data exchange capabilities, either using dedicated commands or managed by the ME (using the Bearer Independent Protocol) ;
+
+| <b>Data exchange capability</b>            |
+|--------------------------------------------|
+| SMS                                        |
+| CSD                                        |
+| Packet service bearer                      |
+| SS (MO only)                               |
+| USSD (MO only)                             |
+| Cell Broadcast (MT only)                   |
+| SMS via GPRS                               |
+| I-WLAN                                     |
+| Local Bearer (Bluetooth, IrDA, RS232, USB) |
+
+# 10 Charging requirements
+
+It shall be possible to charge the subscriber for the use of USAT applications.
+
+It shall be possible to charge for the following activities:-
+
+- subscription:  
+the subscriber's registration to use USAT services
+- application transfer (download):  
+the transfer of applications and/or information to a subscriber's USAT UE
+- application upgrading (download):  
+the upgrading of previously transferred applications to a subscriber's USAT UE
+- application use:  
+the use of applications by a subscriber's USAT UE
+- content:  
+the provision of content within a USAT application
+- roaming:  
+the use of USAT applications by a subscriber when roaming
+- transport:  
+the use of a transport/bearer service (e.g. SMS)
+
+# 11 Security requirements
+
+The integrity of the USIM and existing security mechanisms shall not be compromised with the introduction of USAT services.
+
+The security of the PLMN, the USIM and the USAT applications shall not be able to be compromised by an external execution environment.
+
+Applications running within an external execution environment are considered "non-trusted" until a secure authentication and identification procedure has been successfully performed. MExE is considered to be an external execution environment. MExE is not covered by this specification.
+
+Applications designed using the features in this specification may require additional methods to provide additional data confidentiality, data integrity, and data sender validation, or any subset thereof.
+
+## 11.1 Secure Environment requirements
+
+A major aspect of the UICC is the security provided by the chip technology combined with the encryption and challenge/response procedures. The enhancement of the UICC by USAT shall not reduce nor endanger the current security. In addition, the USAT environment shall maintain (or improve) the same high levels of security. Adequate (future) measures shall be taken to ensure the fulfilment of this requirement also with future advances in technologies/services (either network-centric and/or UE-centric).
+
+# --- 12 Emergency calls
+
+The SAT/USAT shall be able to instruct the ME to set up an emergency call to the default emergency call centre. All other call set up requests shall proceed as a normal call set up, and the dialled digits offered by the SAT/USAT shall not be altered.
+
+# --- 13 Roaming
+
+Provided a roaming agreement for the necessary transport/bearer service(s) (e.g. SMS, GPRS) is currently valid, the USAT execution environment shall be supported when roaming.
+
+# --- 14 Interaction with supplementary services
+
+## 14.1 General
+
+This subclause defines the interaction between PLMN supplementary services and the USAT feature. PLMN supplementary services shall not have any knowledge of USAT based services.
+
+## 14.2 Line Identification
+
+### 14.2.1 Calling Line Identification Presentation (CLIP)
+
+No interaction.
+
+### 14.2.2 Calling Line Identification Restriction (CLIR)
+
+No interaction.
+
+### 14.2.3 Connected Line Identification Presentation (COLP)
+
+### 14.2.4 Connected Line Identification Restriction (COLR)
+
+No interaction.
+
+## 14.3 Call Forwarding
+
+### 14.3.1 Call Forwarding Unconditional (CFU)
+
+USAT shall be able to modify the forwarded to number entered by the user and displayed, upon interrogation, to the user.
+
+### 14.3.2 Call Forwarding Busy (CFB)
+
+USAT shall be able to modify the forwarded to number entered by the user and displayed, upon interrogation, to the user.
+
+### 14.3.3 Call Forwarding on No Reply (CFNRy)
+
+USAT shall be able to modify the forwarded to number entered by the user and displayed, upon interrogation, to the user.
+
+### 14.3.4 Call Forwarding on Not Reachable (CFNRc)
+
+USAT shall be able to modify the forwarded to number entered by the user and displayed, upon interrogation, to the user.
+
+## 14.4 Call Completion
+
+### 14.4.1 Call Hold (CH)
+
+No interaction.
+
+### 14.4.2 Call Waiting (CW)
+
+No interaction.
+
+## 14.5 Multi Party (MPTY)
+
+USAT shall be able to modify the called number entered by the user.
+
+## 14.6 Closed User Group (CUG)
+
+No interaction.
+
+## 14.7 Advice of Charge (AoC)
+
+No interaction.
+
+## 14.8 Call Barring
+
+### 14.8.1 Barring of all outgoing calls
+
+No interaction.
+
+### 14.8.2 Barring of outgoing international calls
+
+#### 14.8.2.1 Mobile originated calls
+
+No interaction.
+
+#### 14.8.2.2 Forwarded Calls
+
+No interaction.
+
+### 14.8.3 Barring of outgoing international calls except those directed to the HPLMN country
+
+No interaction.
+
+### 14.8.4 Barring of all incoming calls
+
+No interaction.
+
+### 14.8.5 Barring of incoming calls when roaming
+
+No interaction.
+
+## 14.9 Explicit Call Transfer (ECT)
+
+USAT shall be able to modify the transfer number entered by the user.
+
+## 14.10 Completion of Call to Busy Subscriber (CCBS)
+
+USAT shall be able to modify the number displayed to the user.
+
+## 14.11 Multiple Subscriber Profile (MSP)
+
+No interaction.
+
+# --- 15 Interaction with network features
+
+All services available in the network shall continue to be offered and remain applicable in addition to USAT. This includes the basic services, supplementary services and network features.
+
+## 15.1 Interactions with Operator Determined Barring (ODB)
+
+### 15.1.1 Barring of all outgoing calls
+
+No interaction.
+
+### 15.1.2 Barring of all outgoing international calls
+
+No interaction.
+
+### 15.1.3 Barring of all outgoing international calls except those directed to the home PLMN country
+
+No interaction.
+
+### 15.1.4 Barring of outgoing calls when roaming outside the home PLMN country
+
+No interaction.
+
+### 15.1.5 Barring of outgoing premium rate calls
+
+No interaction.
+
+### 15.1.6 Barring of incoming calls
+
+No interaction.
+
+### 15.1.7 Barring of incoming calls when roaming outside the home PLMN country
+
+No interaction.
+
+### 15.1.8 Operator Specific Barring
+
+No interaction.
+
+### 15.1.9 Barring of Supplementary Services Management
+
+No interaction.
+
+## 15.2 Interactions with Optimal Routing (OR)
+
+No interaction.
+
+## 15.3 Interactions with MExE
+
+The SAT/USAT applications have the the ability to launch a micro-browser (on a given URL and a given bearer) if provided by the ME.
+
+## 15.4 Interactions with CAMEL
+
+No interaction.
+
+# --- 16 Compatibility of USAT ME's and applications
+
+## 16.1 USAT Classification
+
+Given the wide ranging hardware capabilities of UICCs and MEs, together with the development of USAT applications and applets, a USAT classification shall be supported to determine their respective capability and compatibility. The USAT classification shall apply both to UICCs, MEs and applications and applets.
+
+The objective is to:-
+
+- classify the requirements of a USAT UICC/applications and
+- identify the commands and features supported by the ME
+
+The development and maintenance of the USAT specification is done in accordance to the ETSI/3GPP release procedures. . I.e. annual releases of the specifications are done providing support for new commands and enhancements of existing commands. The annual Release may both contain commands that are mandatory for that Release and commands that are optional.
+
+The classification of the optional commands and features in a given Release may be done with the concept of “Letter Classes”. A Letter Class identifies a subset of functionality of the Release, which will provide the user, USAT serving environment and application writer with a consistent set of commands and features.
+
+The concept of a USAT Letter Classes is introduced to help identify the ME, and the UICC /USAT application compatibility within a given Release. The USAT Letter Class is distinct and unrelated to the existing PLMN UE Classmark. The USAT Letter Classes are not used during capability negotiations, but are intended to assist in designing applications by provision of a means for an application designer to identify which combinations of USAT features are supported by the MEs. Capability negotiations between the UICC and the ME are performed at the feature level, independent of the USAT Letter Class.
+
+In addition to classifying the ME as conforming to a specific Release and if applicable one or several Letter Classes within the release, an ME manufacturers declaration shall be provided. This shall indicate in detail the commands and features supported by the ME. Any conformance testing shall be performed in accordance to this declaration.
+
+The support of a given Letter Class doesn't require the support of another Letter Class.
+
+USAT applications will be developed to execute on USAT UE's in one or more classifications. In order for USAT applications to be properly supported by a USAT UE, the application shall be designated by the same classification of USAT UE's on which they are intended to be executed.
+
+## 16.2 ME/USIM operation
+
+In the case of an ME not supporting SAT/USAT or not supporting a certain SAT/USAT feature the following shall apply:
+
+- the USIM shall control (i.e. allow or prevent) the access to the network.  
+This allows the USIM to prevent the use of a subscription (which may rely on the support of USAT features for correct operation) in an uncontrolled manner.
+- if access to a PLMN is not prevented the ME shall support the non-USAT PLMN features without restriction.
+
+## 16.3 ME/UICC capability information exchange
+
+If supported, the UICC and the ME shall exchange USAT capabilities when the card session is initiated.
+
+This exchange of information is important since the UICC then knows what the ME is capable of, and the UICC can thus adapt the service made available to the user accordingly. If the UICC does not receive any ME capability information it shall assume that the ME does not support USAT.
+
+A UICC that supports USAT shall not attempt to invoke USAT functions in the ME if the ME has not indicated USAT support.
+
+An ME that supports USAT shall not attempt to invoke USAT functions in the UICC if the UICC has not indicated that USAT is supported and is active.
+
+## 16.4 ME and compatibility
+
+For compatibility testing the ME manufacturers shall provide a declaration of the Release and if applicable the Letter Class(es) supported by the ME including the detail of all commands and features supported by the ME. It can be envisaged that ME implementations will exist that are compliant to a given release and which support commands and features from later releases.
+
+## 16.5 Void ---
+
+# 17 Void
+
+# Annex A (informative): Change history
+
+| Document history |         |                                                                                                                                      |
+|------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------|
+| Date             | Version | Comment                                                                                                                              |
+| June 98          | 0.0.0   | Initial draft based on MExE stage 1.                                                                                                 |
+| June 98          | 0.1.0   | Output of SMG1/SMG9 joint ad hoc                                                                                                     |
+| August 98        | 0.2.0   | Updated by editor reflecting discussion at joint ad hoc in June.                                                                     |
+| August 98        | 0.3.0   | Output of SMG1/SMG9 joint ad hoc meeting                                                                                             |
+| November 98      | 0.4.0   | Output of SMG1/SMG9 joint ad hoc meeting                                                                                             |
+| January 99       | 0.5.0   | Output of SMG1/SMG9 joint ad hoc meeting                                                                                             |
+| January 99       | 0.5.1   | Improved output of SMG1/SMG9 joint ad hoc meeting, submitted to SMG1 for information, with recommendation to raise to Version 1.0.0. |
+| March 99         | 1.0.0   | Raised to Version 1.0.0 by SMG1 Plenary                                                                                              |
+| May 99           | 1.0.1   | Draft changes, interim output of SMG1/SMG9 ad hoc meeting.                                                                           |
+| May 99           | 1.1.0   | Output of SMG1/SMG9 joint ad hoc meeting                                                                                             |
+| May 99           | 1.1.1   | Minor editorial changes only. Output of SMG1/SMG9 joint ad hoc meeting                                                               |
+| June 99          | 1.1.2   | Spelling and editorial corrections, changes agreed to by email after the 5 <sup>th</sup> ad hoc                                      |
+| September 99     | 1.3.0   | New version after S1 meeting                                                                                                         |
+| September 99     | 1.3.1   | Final version for approval at TSG-SA Korea                                                                                           |
+| October 99       | 2.0.0   | Editorial clean-up for version 2.0.0                                                                                                 |
+
+| Change history |           |           |        |     |     |       |     |                                                                    |       |       |                  |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|--------------------------------------------------------------------|-------|-------|------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                    | Old   | New   | WI               |
+| SA#05          | SP99-434  |           |        |     |     |       |     | Version 3.0.0 Approved                                             |       | 3.0.0 |                  |
+| SMG#30         | SP99-434  |           |        |     |     |       |     | Version 3.0.0 Approved                                             |       | 3.0.0 |                  |
+| SP-07          | SP-000058 | S1-000120 | 22.038 | 001 |     | R99   | D   | USIM/SIM Application Toolkit, Service Description, Stage 1         | 3.0.0 | 3.1.0 |                  |
+| SP-07          | SP-000152 |           | 22.038 | 002 | 1   | R99   | B   | Addition requirements for bearer independent data transfer feature | 3.0.0 | 3.1.0 |                  |
+| SP-08          | SP-000196 | S1-000432 | 22.038 | 003 |     | R99   | F   | Deletion of note to non-existent TS                                | 3.1.0 | 3.2.0 |                  |
+| SP-09          | SP-000381 | S1-000637 | 22.038 | 005 |     | R4    | D   | Change of MExE name                                                | 3.2.0 | 4.0.0 |                  |
+| SP-09          | SP-000382 | S1-000629 | 22.038 | 004 |     | R5    | B   | Release 2000 features                                              | 3.2.0 | 5.0.0 |                  |
+| SP-10          | SP-000541 | S1-000862 | 22.038 | 007 |     | Rel-5 | B   | LS on USAT local link mechanism and impact on TS 22.038            | 5.0.0 | 5.1.0 | USAT1-<br>LocLnk |
+| SP-12          | SP-010261 | S1-010419 | 22.038 | 008 |     | Rel-5 | B   | Indication of Key identification                                   | 5.1.0 | 5.2.0 | USAT1            |
+| SP-20          | SP-030238 | S1-030466 | 22.038 | 011 |     | Rel-5 | A   | Clean up of USAT requirements                                      | 5.2.0 | 5.3.0 | TEI              |
+| SP-20          | SP-030355 |           | 22.038 | 013 | 2   | Rel-6 | B   | MMS support on the card                                            | 5.2.0 | 6.0.0 | MMS-R6           |
+| SP-21          | SP-030461 | S1-030887 | 22.038 | 014 |     | Rel-6 | B   | MMS support by the USIM Application Toolkit                        | 6.0.0 | 6.1.0 | MMS-R6           |
+
+|         |           |               |        |      |   |        |   |                                                                                                                           |        |        |         |
+|---------|-----------|---------------|--------|------|---|--------|---|---------------------------------------------------------------------------------------------------------------------------|--------|--------|---------|
+| SP-22   | SP-030772 | -             | 22.038 | 016  | 1 | Rel-6  | F | Change of the term "bearer" to "data exchange capability" and removal of implementation dependent statements in TS 22.038 | 6.1.0  | 6.2.0  | TEI     |
+| SP-22   | SP-030688 | S1-031336     | 22.038 | 018  | - | Rel-6  | A | Enable Cell Broadcast Bearer for USAT application while connected to UTRAN networks                                       | 6.1.0  | 6.2.0  | TEI5    |
+| SP-22   | SP-030685 | S1-031322     | 22.038 | 022  | - | Rel-6  | A | CR to align TS 22.038 with the T3 specifications TS 11.14 and TS 31.111                                                   | 6.1.0  | 6.2.0  | EMC1-CS |
+| SP-22   | SP-030696 | S1-031220     | 22.038 | 015  | - | Rel-7  | B | Interaction between ME and USAT applications                                                                              | 6.1.0  | 7.0.0  | USAT1   |
+| SP-25   | SP-040679 | -             | 22.038 | 023  | 1 | Rel-7  | A | Enhance the USAT MMS presentation                                                                                         | 7.0.0  | 7.1.0  | UEMMS   |
+| SP-26   | SP-040734 | S1-040985     | 22.038 | 025  | - | Rel-7  | B | Extension of the USAT bearers                                                                                             | 7.1.0  | 7.2.0  | WLAN    |
+| SP-27   | SP-050057 | S1-050247     | 22.038 | 027  | - | Rel-7  | A | References corrections                                                                                                    | 7.2.0  | 7.3.0  | TEI-7   |
+| SP-28   | SP-050220 | S1-050479     | 22.038 | 028  | - | Rel-7  | F | Correction of WLAN into I-WLAN                                                                                            | 7.3.0  | 7.4.0  | WLAN    |
+| SP-29   | SP-050606 |               | 22.038 | 0030 | 1 | Rel-7  | A | Addition of UTRAN packet service as a data bearer for the UICC                                                            | 7.4.0  | 7.5.0  | TEI-7   |
+| SP-39   | SP-080043 | S1-080277     | 22.038 | 0032 | 3 | Rel-8  | C | Extension of Toolkit communication control to IMS                                                                         | 7.5.0  | 8.0.0  | TEI8    |
+| SP-39   | SP-080043 | S1-080311     | 22.038 | 0033 | 4 | Rel-8  | B | Availability of Location information in the UICC                                                                          | 7.5.0  | 8.0.0  | TEI8    |
+| SP-39   | SP-080043 | S1-080305     | 22.038 | 0035 | 4 | Rel-8  | B | Toolkit over HSP                                                                                                          | 7.5.0  | 8.0.0  | TEI8    |
+| -       | -         | -             | -      |      |   |        |   | Some revision marks appearing in v.8.0.0 have been accepted                                                               | 8.0.0  | 8.0.1  |         |
+| SP-43   | SP-090215 | S1-090288 rev | 22.038 | 0036 | 5 | Rel-9  | B | Discovery of surrounding home (e)NodeB by UICC                                                                            | 8.0.1  | 9.0.0  | EHNB    |
+| SP-50   | SP-100805 | S1-103325     | 22.038 | 0037 | 1 | Rel-10 | F | Correction of USAT requirements                                                                                           | 9.0.0  | 10.0.0 | TEI10   |
+| 2011-03 |           |               |        |      |   |        |   | Update to Rel-10 version (MCC)                                                                                            | 10.0.0 | 10.0.1 |         |
+| 2012-09 | -         | -             | -      | -    | - | -      | - | Update to Rel-11 version (MCC)                                                                                            | 10.0.1 | 11.0.0 |         |
+| 2014-10 | -         | -             | -      | -    | - | -      | - | Update to Rel-12 version (MCC)                                                                                            | 11.0.0 | 12.0.0 |         |
+| 2015-12 |           |               |        |      |   |        |   | Update to Rel-13 version (MCC)                                                                                            | 12.0.0 | 13.0.0 |         |

marked/Rel-13/22_series/22041/raw.md

@@ -0,0 +1,409 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Operator Determined Barring (ODB) (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a small "TM" symbol. Above the "lte" text are three green curved lines representing signal waves.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left of the "G". The "P" and "P" are connected at the top by a single horizontal line. Below the "G" is a small red signal wave icon. To the right of the "P" is a small "TM" symbol.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+## **Keywords**
+
+GSM, UMTS, call barring, supplementary service,  
+stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles – Sophia Antipolis  
+Valbonne – FRANCE  
+Tel. : +33 4 92 94 42 00 Fax : +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                     |    |
+|-----------------------------------------------------|----|
+| Foreword .....                                      | 4  |
+| 1 Scope.....                                        | 5  |
+| 1.1 References.....                                 | 5  |
+| 1.2 Definitions and abbreviations.....              | 5  |
+| 2 Description.....                                  | 5  |
+| 3 Applicability to Basic Services (BS) .....        | 6  |
+| 4 Applicability to Supplementary Services (SS)..... | 6  |
+| 5 Normal procedure .....                            | 7  |
+| 5.1 Circuit Oriented Services .....                 | 7  |
+| 5.2 Packet Oriented Services.....                   | 9  |
+| 5.3 Interworking WLAN .....                         | 9  |
+| 5.4 IMS Oriented Services .....                     | 9  |
+| 5.4.1 IMS Multimedia Telephony Services.....        | 9  |
+| 6 Exceptional procedures .....                      | 11 |
+| 7 Alternate procedures .....                        | 11 |
+| 8 Interworking considerations.....                  | 11 |
+| Annex A (informative): Change history.....          | 12 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of 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 network feature Operator Determined Barring (ODB).
+
+This allows the network operator or service provider to regulate, by means of an exceptional procedure, access by the subscribers to services (both Circuit and Packet Oriented), by the barring of certain categories of outgoing or incoming calls/Packet Oriented Services or of roaming. ODB shall take effect immediately and shall terminate ongoing calls and bar future calls/Packet Oriented Services.
+
+The purpose of this network feature is to be able to limit the service provider's financial exposure to new subscribers, or to those who have not promptly paid their bills. It may only be applied to the service provider's own subscribers.
+
+## --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] TS 22.088: " Call Barring (CB) supplementary services – Stage 1".
+- [3] ITU-T Recommendation E.164 : "Numbering plan for the ISDN era".
+- [4] TS 22.082: " Call Forwarding (CF) supplementary services – Stage 1".
+- [5] TR 21.905: "Vocabulary for 3GPP Specifications".
+- [6] 3GPP TS 22.234: "Requirements for 3GPP system to wireless local area network (WLAN) interworking".
+
+## 1.2 Definitions and abbreviations
+
+In addition to the following definitions, abbreviations used in the present document are listed in GSM 01.04 [1] and TR 21.905 [5].
+
+**Premium rate call:** A telecommunications network, possibly but not necessarily a PLMN, may make available certain services, for which the tariff is comparable to, or may exceed, International Call rates. Examples of such premium rate services might be information and entertainment services. The exact definition of what constitutes a premium rate call is the responsibility of the VPLMN operator, possibly subject to inter-operator agreements.
+
+# --- 2 Description
+
+Application of Operator Determined Barring is controlled by the Service Provider, by administrative interaction with the HLR; this interface is not standardized.
+
+With the exception of the barring of roaming, the HLR affects Operator Determined Barring in a similar manner to Service Provider – activated use of the Call Barring Supplementary service. Consequently, the VLR and MSC also execute the relevant Barring Conditions in similar manners. It is noted that there is no password usage. Roaming is barred by the HLR when the MS is in a PLMN other than the Home PLMN or not in the Home PLMN Country as applicable.
+
+In addition to ensuring the barring integrity for future calls, the HLR, and consequently the MSC and VLR, shall provide means to terminate the calls of a user that have been established prior to the application of the ODB service and which are still ongoing.
+
+# --- 3 Applicability to Basic Services (BS)
+
+This network feature is applied to all Teleservices and Bearer Services except as noted below. The Operator Determined Barring feature shall not be applied to Teleservice-Emergency Call. It is not possible to apply Operator Determined Barring independently to individual Basic Services.
+
+# --- 4 Applicability to Supplementary Services (SS)
+
+Operator Determined Barring is a network feature and hence applies to Supplementary Service aspects of subscriptions.
+
+Operator Determined Barring is applied independently from Supplementary Services. Nevertheless the following interactions occur:
+
+## **Call Barring:**
+
+Calls will be denied if either Operator Determined Barring or Subscriber Controlled Barring determine that the call should be barred.
+
+If a call is barred due to both Operator Determined Barring and Subscriber Controlled Barring, then the message or notification returned towards the caller will be the same as if the barring was due solely to Operator Determined Barring (see Section 5).
+
+There is no other interaction.
+
+## **Call Forwarding:**
+
+If a call forwarding programme is in contravention of an Operator Determined Barring Category, when the latter is activated, then the activation shall result in making call forwarding quiescent. If the subscriber attempts to activate a new call forwarding programme in contravention of an Operator Determined Barring Category, then the activation shall be denied, and the subscriber informed of the denial. There is no other interaction.
+
+## **Closed User Group:**
+
+CUG restrictions must be met in addition to Operator Determined Barring restrictions for a call to proceed.
+
+If a call is barred due to both Operator Determined Barring and CUG restrictions, then the message or notification returned towards the caller will be the same as if the barring was due solely to Operator Determined Barring (see Section 5).
+
+There is no other interaction.
+
+## **Call Transfer:**
+
+If the subscriber attempts to invoke a call transfer in contravention of an Operator Determined Barring category, then the invocation shall be denied, and the subscriber informed of the denial. There is no other interaction.
+
+## **Multi-Party, Advice of Charge, CLIP, CLIR, COLP, COLR, Call Wait, Call Hold:**
+
+There is no interaction.
+
+## **Call Completion to Busy Subscriber, User to User Signalling, Malicious Call Identification, Mobile Access Hunting:**
+
+For further study.
+
+The application of a Barring of Roaming category (see subclauses 3.1 and 3.2 below) will, if the Mobile Station is roaming appropriately, prevent the Mobile Subscriber from undertaking any form of Supplementary Service management.
+
+# --- 5 Normal procedure
+
+## 5.1 Circuit Oriented Services
+
+As described in the following categories, the Service Provider may at any time activate this feature and this shall terminate any relevant calls in progress, including forwarded calls, and bar future calls covered by the barring category:
+
+Independently, one of:
+
+- 1.1 Barring outgoing calls;
+- or: 1.2 Barring outgoing international calls;
+- or: 1.3 Barring outgoing international calls except those directed to the home PLMN country;
+- or: 1.4 Barring of outgoing calls when roaming outside the home PLMN country;
+- or: 1.5 Barring of outgoing inter-zonal calls;
+- or: 1.6 Barring of outgoing inter-zonal calls except those directed to the home PLMN country;
+- or: 1.7 Barring of outgoing international calls except those directed to the home PLMN country AND barring of outgoing inter-zonal calls.
+
+And/or one of:
+
+- 2.1 Barring incoming calls;
+- or: 2.2 Barring incoming calls when roaming outside the home PLMN country;
+- or: 2.3 Barring incoming calls when roaming outside the zone of the home PLMN country.
+
+And/or one of:
+
+- 3.1 Barring of Roaming outside the home PLMN;
+- or: 3.2 Barring of Roaming outside the home PLMN country.
+
+And/or one or more of:
+
+- 4.1 Barring of outgoing Premium Rate Calls (Information);
+- 4.2 Barring of outgoing Premium Rate Calls (Entertainment);
+- 4.3 Barring of outgoing Premium Rate Calls (Information) when roaming outside the home PLMN country;
+- 4.4 Barring of outgoing Premium Rate Calls (Entertainment) when roaming outside the home PLMN country.
+
+And/or one or more of:
+
+- 5.1 When registered in the HPLMN, Operator Specific Barring (Type 1);
+- or: 5.2 When registered in the HPLMN, Operator Specific Barring (Type 2);
+- or: 5.3 When registered in the HPLMN, Operator Specific Barring (Type 3);
+- or: 5.4 When registered in the HPLMN, Operator Specific Barring (Type 4).
+
+And/or
+
+- 6.1 Barring of Supplementary Services Management, which prevents user control of any supplementary service (registration, erasure, activation, deactivation, user invocation, interrogation, password registration and
+
+mobile initiated USSD). However, this does not prevent invocation by other action – e.g. an existing call forwarding or barring state will remain.
+
+And/or one of:
+
+- 7.1 Barring of registration of any call forwarded-to number;
+- or: 7.2 Barring of registration of any international call forwarded-to number;
+- or: 7.3 Barring or registration of any international call forwarded-to number except to a number within the HPLMN country;
+- or: 7.4 Barring of registration of any inter-zone call forwarded-to number.
+- Or: 7.5 Barring of registration of any inter-zone call forwarded-to number except to a number within the HPLMN country;
+
+Note: The definition of an international call is based on the equivalent definition of an international call in TS 22.088 [2]. The principles for deciding whether a forwarded-to number is international or inter-zonal are the same as those given in TS 22.082 [4] to determine the interactions between call forwarding and call barring.
+
+And/or one of:
+
+- 8.1 Barring of invocation of call transfer;
+- or: 8.2 Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber; i.e. the call is either an outgoing call or an incoming call when the served subscriber roams outside the HPLMN;
+- or: 8.3 Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country;
+- or: 8.4 Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN.
+
+And/or:
+
+- 9 Barring of invocation of call transfer where both calls are calls charged to the served subscriber, i.e. both calls are either outgoing calls or incoming calls when the served subscriber roams outside the HPLMN;
+
+and/or:
+
+- 10 Barring of further invocation of call transfer if there is already one ongoing transferred call for the served subscriber in the serving MSC/VLR.
+
+"User invocation", as it relates to ODB, consists of the following action:
+
+- invocation of the call hold supplementary service.
+
+"Zone" is as based on the first digit of their international dialing code as defined in ITU-T Recommendation E.164 [3].
+
+Note: For the purposes of this TS, zone 3 and zone 4 are treated as one zone.
+
+Note: If control of Supplementary Services Management is barred, then the control of call forward will be barred as a consequence, so explicit barring of call forward activation is not necessary.
+
+If a mobile subscriber attempts to use a mobile initiated service which is barred as described above (categories 1, 4, 5, 6, 7, 8, 9, and 10), an appropriate message shall be returned to the Mobile Station or alternatively (categories 1, 4, and 5), if located in the HPLMN, the mobile subscriber can be automatically connected to a destination address determined by the HPLMN operator. It is necessary for the message to indicate that the barring is due to Operator Determined Barring. It is not necessary to indicate the categories which are barred. For ongoing, or transferred calls, that are terminated due to ODB, the network operator may give an appropriate indication to the barred party.
+
+A notification (announcement or ITU-T#7 cause value) may be returned to callers attempting to call a mobile subscriber who is appropriately barred incoming calls. It is not necessary to indicate to the called mobile station that an incoming call has been barred.
+
+Only the HPLMN Operator can activate, change or deactivate application of this network feature.
+
+In order to provide this feature securely when a subscriber roams to another network, the visited network needs to support the feature to ensure that the roaming subscriber cannot use a service which has been barred to him.
+
+## 5.2 Packet Oriented Services
+
+Packet Oriented Services, particularly data services, are different in nature to Circuit Oriented Services, and therefore have different requirements for Operator Determined Barring.
+
+As described in the following categories, the Service Provider may at any time activate this feature and this shall terminate any relevant services in progress, and bar future requests for service covered by the barring category:
+
+- It shall be possible to bar subscribers completely from the Packet Oriented Services.
+- Network shall be able to allow a subscriber to access some specific APNs while barring the subscriber from the other Packet Oriented Services.
+- It shall be possible to bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN.
+- It shall be possible to bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN.
+
+The term 'access point' is used to indicate the GGSN or part of the GGSN that is specified by a particular APN.
+
+## 5.3 Interworking WLAN
+
+Aspects of ODB related to interworking WLAN are addressed in TS 22.234 [6].
+
+## 5.4 IMS Oriented Services
+
+### 5.4.1 IMS Multimedia Telephony Services
+
+As described in the following categories, the Service Provider may at any time activate this feature and this shall terminate any relevant communications in progress, including diverted communications, and bar future communications covered by the barring category:
+
+Independently, one of:
+
+- 1.1 Barring outgoing communication;
+- or: 1.2 Barring outgoing international communications;
+- or: 1.3 Barring outgoing international communications except those directed to the home PLMN country;
+- or: 1.4 Barring of outgoing communications when roaming outside the home PLMN country;
+
+and/or one of:
+
+- 2.1 Barring incoming communications;
+- or: 2.2 Barring incoming communications when roaming outside the home PLMN country;
+
+and/or one of:
+
+- 3.1 Barring of Roaming outside the home PLMN;
+- or: 3.2 Barring of Roaming outside the home PLMN country.
+
+and/or one or more of:
+
+4.1 Barring of outgoing Premium Rate Communications (Information) for E.164 international premium numbers and for premium numbers located within the home PLMN;
+
+4.2 Barring of outgoing Premium Rate Communications (Entertainment) for E.164 international premium numbers and for premium numbers located within the home PLMN;
+
+Note 1: outgoing communications to non E.164 international premium numbers located outside the home PLMN are barred at interconnection between networks based on bilateral agreements.
+
+and/or one or more of:
+
+5.1 When registered in the HPLMN, Operator Specific Barring (Type 1);
+
+or: 5.2 When registered in the HPLMN, Operator Specific Barring (Type 2);
+
+or: 5.3 When registered in the HPLMN, Operator Specific Barring (Type 3);
+
+or: 5.4 When registered in the HPLMN, Operator Specific Barring (Type 4).
+
+and/or
+
+6 Barring of Supplementary Services Management, which prevents user control of any supplementary service (registration, erasure, activation, deactivation, user invocation, interrogation and password registration). However, this does not prevent invocation by other action - e.g. an existing communication diversion or barring state will remain.
+
+and/or one of:
+
+7.1 Barring of registration of any communication diverted-to address;
+
+or: 7.2 Barring of registration of any international communication diverted-to address;
+
+or: 7.3 Barring of registration of any international communication diverted-to address except to an address within the HPLMN country;
+
+and/or one of:
+
+8.1 Barring of invocation of communication transfer;
+
+or: 8.2 Barring of invocation of communication transfer where at least one of the two communications is a communication charged to the served subscriber; i.e. the communication is either an outgoing communication or an incoming communication when the served subscriber roams outside the HPLMN;
+
+or: 8.3 Barring of invocation of communication transfer where at least one of the two communications is a communication charged to the served subscriber at international rates, i.e. the communication is either an outgoing international communication or an incoming communication when the served subscriber roams outside the HPLMN country;
+
+and/or:
+
+9 Barring of invocation of communication transfer where both communications are communications charged to the served subscriber, i.e. both communications are either outgoing communications or incoming communications when the served subscriber roams outside the HPLMN;
+
+and/or:
+
+10 Barring of further invocation of communication transfer if there is already one ongoing transferred communication for the served subscriber.
+
+If a mobile subscriber attempts to use a mobile initiated service which is barred as described above (categories 1, 4, 5, 6, 7, 8, 9 and 10), an appropriate message shall be returned to the Mobile Station or alternatively (categories 1, 4 and 5), if located in the HPLMN, the mobile subscriber can be automatically connected to a destination address determined by the HPLMN operator. It is necessary for the message to indicate that the barring is due to Operator Determined Barring. It is not necessary to indicate the categories which are barred. For ongoing, or transferred communications, that are terminated due to ODB, the network operator may give an appropriate indication to the barred party.
+
+A notification (announcement or appropriate SIP response) may be returned to callers attempting to communicate with a mobile subscriber who is appropriately barred for incoming communications. No indication is provided to the called mobile station that an incoming communication has been barred.
+
+Only the HPLMN Operator can activate, change or deactivate application of this network feature.
+
+# --- 6 Exceptional procedures
+
+If a VPLMN does not support an operator determined barring category which an HPLMN requests it to apply, the VPLMN shall notify the HPLMN. The HPLMN may then request the VPLMN to apply a substitute operator determined barring category, or take any other action required by the HPLMN operator.
+
+# --- 7 Alternate procedures
+
+None identified.
+
+# --- 8 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.41 |      |     |        |     | Transferred to 3GPP SA1                                                              | 7.0.0  |        |              |
+| SA#04          |           |           | 22.041    |      |     |        |     | Transferred to 3GPP SA1                                                              |        | 3.0.0  |              |
+| SP-05          | SP-99479  | S1-99616  | 22.041    | 001  |     | R99    | D   | Editorial changes for alignment                                                      | 3.0.0  | 3.1.0  |              |
+| SP-05          | SP-99441  | S1-99850  | 22.041    | 002  |     | R99    | B   | Addition of explicit requirements for Packet Oriented Services                       | 3.0.0  | 3.1.0  |              |
+| SP-10          | SP-000532 | S1-000852 | 22.041    | 003  |     | R99    | F   | Operator Determined Barring of Packet Oriented Services                              | 3.1.0  | 3.2.0  |              |
+| SP-10          | SP-000532 | S1-000853 | 22.041    | 004  |     | Rel-4  | B   | Operator Determined Barring of Packet Oriented Services                              | 3.2.0  | 4.0.0  | TEI4         |
+| SP-11          | SP-010041 | S1-010019 | 22.041    | 006  |     | Rel-4  | F   | Corrections of the ODB categories for Packet Oriented Services                       | 4.0.0  | 4.1.0  | ODB Enh.     |
+| SP-11          | SP-010042 | S1-010174 | 22.041    | 008  |     | Rel-4  | A   | CR on Operator Determined Barring – Zonal Barring to 3GPP TSG SA WG1                 | 4.0.0  | 4.1.0  | TEI          |
+| SP-16          | SP-020267 | S1-021043 | 22.041    |      |     | Rel-5  |     | Updated from Rel-4 to Rel5                                                           | 4.1.0  | 5.0.0  |              |
+| SP-20          | SP-030327 | S1-030490 | 22.041    | 009  | 1   | Rel-6  | B   | ODB in WLAN – Requirement                                                            | 5.0.0  | 6.0.0  | ODB, WLAN-CR |
+| SP-21          | SP-030464 | S1-030901 | 22.041    | 011  | -   | Rel-6  | B   | ODB in VPLMN for WLAN user                                                           | 6.0.0  | 6.1.0  | ODB          |
+| SP-21          | SP-030464 | S1-030915 | 22.041    | 010  | -   | Rel-6  | C   | WLAN access point terminology clarified                                              | 6.0.0  | 6.1.0  | ODB          |
+| SP-23          | SP-040101 | S1-040261 | 22.041    | 012  | -   | Rel-6  | D   | Extraction of redundant WLAN related ODB text – now in WLAN TS22.234                 | 6.1.0  | 6.2.0  | WLAN         |
+| SP-35          | SP-070118 | S1-070251 | 22.041    | -    | -   | Rel-7  | B   | Raised to version 7.0.0 as a result of approval of CR 0014r1 for Rel-8               | 6.2.0  | 7.0.0  | -            |
+| SP-35          | SP-070118 | S1-070251 | 22.041    | 0014 | 1   | Rel-8  | B   | ODB for IMS                                                                          | 7.0.0  | 8.0.0  | MTSI-REQ     |
+| SP-36          | SP-070353 | S1-070800 | 22.041    | 0015 | 2   | Rel-8  | B   | Selective application of ODB to International & Premium Rate Services whilst roaming | 8.0.0  | 8.1.0  | TEI-8        |
+| SP-46          | -         | -         | -         | -    | -   | -      | -   | Updated to Rel-9 by MCC                                                              | 8.1.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 |              |
+| SP-58          | SP-120869 | S1-124362 | 22.041    | 0016 | 2   | Rel-11 | B   | Addition of APN to the condition of the ODB judgment                                 | 11.0.0 | 11.1.0 | TEI11        |
+| SP-59          | SP-130123 | S1-131295 | 22.041    | 0017 | 1   | Rel-11 | F   | Barring of Premium Rate Numbers                                                      | 11.1.0 | 11.2.0 | TEI11        |
+| SP-61          | SP-130411 | S1-134130 | 22.041    | 0018 | 1   | Rel-11 | A   | Removal of IMS Operator Determined Barring Outgoing Premium Rate requirements        | 11.2.0 | 11.3.0 | TEI8         |
+| 2014-10        | -         | -         | -         | -    | -   | -      | -   | Update to Rel-12 version (MCC)                                                       | 11.3.0 | 12.0.0 |              |
+| 2015-12        |           |           |           |      |     |        |     | Update to Rel-13 version (MCC)                                                       | 12.0.0 | 13.0.0 |              |

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

@@ -0,0 +1,200 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.042 V13.0.0 (2016-01) Network Identity and Time Zone (NITZ); Service description; *Technical Specification* Stage 1 (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a small "TM" symbol. Above the "Advanced Pro" text are three green curved lines representing signal waves.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. Below the "P" is a small red signal wave icon. Below the main logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, addressing, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |           |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                 | 11.0.0 | 12.0.0 |           |
+| 2015-12        |           |           |           |     |     |       |     | Update to Rel-13 version (MCC)                                 | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22053/raw.md

@@ -0,0 +1,301 @@
+
+
+# Keywords GSM, UMTS, stage 1 3GPP TS 22.053 V13.0.0 (2015-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **Tandem Free Operation (TFO);** **Service Description;**
+
+![GSM logo: GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+GSM logo: GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS
+
+Postal address  
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association  
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                                                       |          |
+|---------------------------------------------------------------------------------------|----------|
+| Foreword .....                                                                        | 4        |
+| 1 Scope.....                                                                          | 5        |
+| 2 References.....                                                                     | 5        |
+| 3 Definitions and abbreviations .....                                                 | 5        |
+| 3.1 Definitions.....                                                                  | 5        |
+| 3.2 Abbreviations .....                                                               | 6        |
+| 4 Description.....                                                                    | 6        |
+| 4.1 Applicability of TFO to Basic Services .....                                      | 6        |
+| 4.2 Support in Mobile Stations (MS) .....                                             | 6        |
+| 4.3 Parameters to be indicated and negotiated.....                                    | 6        |
+| 4.4 Provision of Service .....                                                        | 6        |
+| 4.4.1 Location Independence.....                                                      | 6        |
+| 4.4.2 Provision of service within and between networks .....                          | 6        |
+| 4.4.3 Subscription and Billing Information .....                                      | 7        |
+| 4.5 Quality of Service (QoS).....                                                     | 7        |
+| 4.5.1 Impact on Speech Quality .....                                                  | 7        |
+| 5 Interaction with supplementary services.....                                        | 7        |
+| 5.1 General .....                                                                     | 7        |
+| 5.2 Explicit Call Transfer (ECT).....                                                 | 7        |
+| 5.3 Call wait/Call hold .....                                                         | 8        |
+| 5.4 Multiparty.....                                                                   | 8        |
+| 5.5 Service Announcements.....                                                        | 8        |
+| 6 Interaction with Alternate and Followed by services.....                            | 8        |
+| 7 Interaction with other speech services .....                                        | 8        |
+| 8 Interaction with DTMF .....                                                         | 8        |
+| 9 Interaction with Lawful Intercept .....                                             | 8        |
+| <b>Annex A (informative): Limitations of initial in-band TFO implementations.....</b> | <b>9</b> |
+| Annex B (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.
+
+# --- 1 Scope
+
+The present document specifies the stage 1 description for the Tandem Free Operation (TFO) feature which provides the capability to avoid tandeming speech codecs in mobile to mobile speech calls. The primary aim is to realise improvements in speech quality. The TFO mode of operation could also be used to reduce inter-Mobile services Switching Center (MSC) transmission bandwidth requirements.
+
+In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+
+# --- 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] ITU-T Recommendations I.130 (1988): "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
+
+[2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+
+# --- 3 Definitions and abbreviations
+
+GSM 01.04 [2] provides a list of abbreviations and acronyms used in GSM specifications.
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Tandem Free Operation (TFO):** avoidance of tandeming speech codecs in mobile to mobile speech calls
+
+**TFO call:** mobile to mobile call where TFO has been applied
+
+**Normal call or operation:** call where TFO has not been applied
+
+**Negotiation phase:** phase during which the applicability of TFO is assessed through the exchange of information such as the capabilities of the respective transcoders and the types of speech codecs being used
+
+**A party:** user originating the call
+
+**B party:** user receiving the call (unless the call is forwarded)
+
+For simplicity the term MS is also used when UE is meant for 3G systems. The same is valid for TRAU and TC analogously.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                  |
+|------|----------------------------------|
+| ASCI | Advanced Speech Call Items       |
+| MSC  | Mobile services Switching Centre |
+| PLMN | Public Land Mobile Network       |
+
+# --- 4 Description
+
+The TFO feature avoids the tandeming of speech codecs that occurs in mobile to mobile speech calls.
+
+## 4.1 Applicability of TFO to Basic Services
+
+TFO shall be applicable to all mobile to mobile speech calls where both parties use the same GSM speech coding standard. TFO shall be supported for all of the GSM speech coding standards (i.e. Full Rate, Half Rate and Enhanced Full Rate). It would also be desirable to extend the TFO approach to realise quality enhancements when different speech codec standards are in use, e.g. by handing over one of the links to provide common codec types and then applying TFO.
+
+## 4.2 Support in Mobile Stations (MS)
+
+TFO shall not require any modifications to existing or future mobile stations. There shall be no additional user intervention required to enable or invoke the feature. Correspondingly, it shall not be possible for a user to disable the feature.
+
+## 4.3 Parameters to be indicated and negotiated
+
+The speech codec standards used on each party shall be indicated and negotiated, if applicable.
+
+## 4.4 Provision of Service
+
+### 4.4.1 Location Independence
+
+TFO shall be capable of being applied for mobile to mobile calls regardless of the serving networks of the A or B parties. Thus, the A and B parties may be registered on different PLMNs or on the same network.
+
+### 4.4.2 Provision of service within and between networks
+
+Provision of the TFO feature shall be determined by the network operator on a network (or sub-network) wide basis, where equipment to support the feature has been deployed. It shall not be necessary for the service capability to be rolled out throughout an entire network before being made operational.
+
+TFO between networks shall be applied if appropriate between supporting (sub) networks.
+
+In the case where a TFO call is handed over between two parts of a network, but the new part is not provisioned with TFO, the call shall revert to normal operation.
+
+In the case where a normal call is handed over between two parts of a network, and the new part is provisioned with TFO, the call will switch to TFO if appropriate.
+
+NOTE: TFO operation will normally require that the coded speech is transmitted transparently (i.e. without errors) between the relevant transcoders (e.g. by bit-stealing).
+
+### 4.4.3 Subscription and Billing Information
+
+This feature shall not be provisioned on a per-subscriber basis and no record of the application of TFO is necessary for billing purposes.
+
+## 4.5 Quality of Service (QoS)
+
+### 4.5.1 Impact on Speech Quality
+
+The speech quality and timing requirements depend on the phase of the call and are defined in table 1. In all cases the duration and degradation should be minimised.
+
+The timing requirements for the application and removal of TFO are derived from the typical user's perception of the feature in the context of typical call set-up times together with handover operation. There is a much stricter requirement on the time taken to revert to normal operation than to apply TFO because when TFO is enabled only on one side of a call, the speech will be unintelligible. Likewise, failures in the transmission of the coded speech without (significant) errors (e.g. due to routing via an ADPCM link) should be detected rapidly as the speech quality may also be seriously degraded.
+
+**Table 1: TFO speech quality and timing requirements**
+
+| Call phase                                             | Reference condition (note 1) | Maximum degradation          | Speed of operation               |
+|--------------------------------------------------------|------------------------------|------------------------------|----------------------------------|
+| TFO negotiation following call set-up                  | normal transcoding stages    | "no perceptible degradation" | 2 sec (note 2)<br>7 sec (note 3) |
+| TFO negotiation following TFO interruption or handover | normal transcoding stages    | "no perceptible degradation" | 7 sec (notes 4 and 5)            |
+| transition from normal operation to TFO                | normal transcoding stages    | "no annoying artefacts"      |                                  |
+| return from TFO to normal operation                    | TFO transcoding stages       | "no annoying artefacts"      | 160 ms                           |
+| continuous TFO                                         | TFO transcoding stages       | "no degradation"             |                                  |
+| continuous normal operation                            | normal transcoding stages    | "no degradation"             |                                  |
+
+NOTE 1: All reference conditions are defined as error free with no bit-stealing and with no transmission delay between the TRAUs "normal transcoding stages" refers to the speech codec(s) selected prior to TFO.  
+NOTE 2: Objective for time taken to establish TFO after call set-up.  
+NOTE 3: Maximum time allowed for TFO negotiation after call set-up.  
+NOTE 4: Objective for time taken to establish TFO after re-establishment of transparent PCM link.  
+NOTE 5: Once TFO has been successfully established during a call, an unlimited number of negotiation attempts may be made after any subsequent interruptions of TFO.
+
+NOTE: The timing limits and the quality degradations specified in table 1 are to some extent inter-dependent.
+
+# 5 Interaction with supplementary services
+
+## 5.1 General
+
+This clause defines the interactions between supplementary services and TFO.
+
+Neither TFO nor attempted TFO establishment shall interfere with the provision or invocation of any supplementary services.
+
+## 5.2 Explicit Call Transfer (ECT)
+
+Following call transfer, the new call route is evaluated and TFO applied if possible, otherwise normal operation applies.
+
+## 5.3 Call wait/Call hold
+
+Following the establishment of another call, the new call route shall be evaluated and TFO applied if possible, otherwise normal operation applies.
+
+## 5.4 Multiparty
+
+Where more than two parties are involved in a call, TFO may not be applicable. As a result, when a two-party TFO call is extended to multi-party, all the links shall revert to normal operation.
+
+## 5.5 Service Announcements
+
+TFO shall not disrupt the provision of call progress or similar speech announcements to the user which originate in any of the networks routing a call.
+
+# --- 6 Interaction with Alternate and Followed by services
+
+There shall be no impact on data transmission due to TFO or attempted TFO establishment.
+
+# --- 7 Interaction with other speech services
+
+There is no requirement for TFO in ASCI services.
+
+# --- 8 Interaction with DTMF
+
+DTMF transmission performance during TFO shall be no worse than during normal operation.
+
+# --- 9 Interaction with Lawful Intercept
+
+In the case where lawful intercept is required in a TFO call, the intercept shall not cause any degradation in the speech quality received by the A and B parties.
+
+# --- Annex A (informative): Limitations of initial in-band TFO implementations
+
+This annex highlights the limitations of the applicability of the in-band TFO solutions, some of these limitations could be overcome, however they imply modifications of equipments that are not in the scope of the specifications.
+
+When analogue lines are used TFO either in-band or out-of-band can not apply.
+
+The main limitation of TFO in-band is the digital transparency of the PCM links behind the MSCs that cannot be guaranteed in all the configurations of Mobile-to-Mobile calls.
+
+When digital lines are used the non-transparency is mainly due to the use of In Path Equipments (IPE). These IPEs consist mainly in Echo Cancellers and DCMEs.
+
+The Network Echo Cancellers intend to remove the echo due to the unbalanced hybrids present in the PSTN when going from four wires to two wires in the subscriber local loops. These IPEs are useful in the mobile-to-PSTN calls. These Echo Cancellers should not be used in mobile-to-mobile calls since both terminals are digital. The enabling and disabling of these equipments are properly managed in some countries and not in other countries. Therefore TFO can apply to inter-PLMN calls in the countries where the network echo cancellers are properly configured. The main issue is that there's no easy internationally recognised way to identify mobile-to-mobile calls. They are usually correctly configured for Mobile-to-Mobile calls within a PLMN.
+
+Another limitation that should apply to a very small number of mobile-to\_mobile calls is the use of A/ $\mu$  Laws converters in some international calls.
+
+In some networks Acoustical Echo Cancellers are used. It would be preferable to keep them enabled in Tandem Free calls. This implies that this be taken into account by the Acoustical Echo Cancellers.
+
+The DCMEs they are mainly used in the long distance calls although some operators use them in their PLMN. The only known way to disable the DCMEs is to ask for a transparent 64 kbit/s UDI connection. This option is not reasonable since such connections are more expensive than the speech calls and would imply modifications in the MSCs. Therefore when a DCME is used in-band TFO cannot be established.
+
+In order to get TFO working for the vast majority of the Mobile-to-Mobile calls it is desirable that the IPEs be modified in order to allow the in-band TFO cross them without modification.
+
+TFO implies that compatible speech codec configurations are being used in both MSs. In-band TFO can be established only after the call set-up has been made and thus there can be different speech codecs used in the MSs. The TFO standard shall include ways to solving the codec mismatch otherwise in-band TFO won't apply to these Mobile-to-Mobile calls.
+
+# Annex B (informative): Change history
+
+| SMG# | SPEC  | CR   | VERS  | NEW_VERS | PHASE | SUBJECT                                                                                                       |
+|------|-------|------|-------|----------|-------|---------------------------------------------------------------------------------------------------------------|
+| s23  | 02.53 | new  | 2.0.0 | 5.0.0    | R97   | Tandem Free Operation Stage 1                                                                                 |
+| s24  | 02.53 | A001 | 5.0.0 | 5.1.0    | R97   | CR to GSM 02.53 Modifications to Annex A (informative):<br>Limitations of initial in-band TFO implementations |
+| s25  | 02.53 | new  | 5.1.0 | 7.0.0    | R98   | Version change as part of Release 1998                                                                        |
+| s29  | 02.53 |      | 7.0.0 | 7.0.1    | R98   | Publication of version 7.0.1                                                                                  |
+|      | 02.53 |      | 7.0.1 |          | R99   | Version 8.0.0                                                                                                 |
+
+  
+
+| Change history |         |           |     |     |                         |        |        |  |
+|----------------|---------|-----------|-----|-----|-------------------------|--------|--------|--|
+| Date           | TSG SA# | TSG Doc.  | CR  | Rev | Subject/Comment         | Old    | New    |  |
+| 2001-03        | 11      | SP-010098 | 002 |     | Extension of TFO to AMR | 8.0.0  | 4.0.0  |  |
+| 2001-09        |         |           |     |     | Clean-up                | 4.0.0  | 4.0.1  |  |
+| 2002-06        | 16      |           |     |     | Version for Release 5   | 4.0.1  | 5.0.0  |  |
+| 2004-12        |         |           |     |     | Version for Release 6   | 5.0.0  | 6.0.0  |  |
+| 2007-06        | 36      |           |     |     | Version for Release 7   | 6.0.0  | 7.0.0  |  |
+| 2008-12        | 42      |           |     |     | Version for Release 8   | 7.0.0  | 8.0.0  |  |
+| 2009-12        | 46      |           |     |     | Version for Release 9   | 8.0.0  | 9.0.0  |  |
+| 2011-03        | 51      |           |     |     | Version for Release 10  | 9.0.0  | 10.0.0 |  |
+| 2012-09        | 57      |           |     |     | Version for Release 11  | 10.0.0 | 11.0.0 |  |
+| 2014-09        | 65      |           |     |     | Version for Release 12  | 11.0.0 | 12.0.0 |  |
+| 2015-12        | 70      |           |     |     | Version for Release 13  | 12.0.0 | 13.0.0 |  |
+

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

@@ -0,0 +1,743 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mobile Execution Environment (MExE); Service description, Stage 1 (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the right of the "e" is a green signal icon consisting of three curved lines. A small "TM" symbol is located to the bottom right of the "e".
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected by a horizontal line. Below the "P" is a red signal icon consisting of three curved lines. A small "TM" symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 rectangle represents a 'UE' (User Equipment) with a sub-section labeled 'MExE'. Two arrows originate from the text 'Scope of this TS'. One arrow points to the 'MExE' sub-section of the 'UE'. The other arrow points to the 'MExE Service Environment' cloud.](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg)
+
+The diagram shows a cloud at the top labeled "MExE Service Environment". Below it is a rectangle representing a "UE" (User Equipment). Inside the UE rectangle, the top part is labeled "UE" and the bottom part is labeled "MExE". To the right of the UE, the text "Scope of this TS" has two arrows pointing from it: one arrow points to the "MExE" sub-section of the UE, and the other arrow points to the "MExE Service Environment" cloud.
+
+Diagram illustrating the scope of the 3GPP TS. A cloud labeled 'MExE Service Environment' is shown. Below it, a rectangle represents a 'UE' (User Equipment) with a sub-section labeled 'MExE'. Two arrows originate from the text 'Scope of this TS'. One arrow points to the 'MExE' sub-section of the 'UE'. The other arrow points to the 'MExE Service Environment' cloud.
+
+**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'.](cf4ac1058c52bc3ca37737740afb7f2c_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.](523ab7b925beb555f88b2e1e1336974f_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 this server to another server icon on the right 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.](e636d7ccca0ad14c6b95201404324823_img.jpg)
+
+This diagram is identical to the one above, showing a mobile handset ('MExE Client') connected via red arrows to 'Network VAS and MExE Servers' within a 'Mobile Network' cloud, which are further connected to '3rd party VAS and MExE Servers'. A large blue curved arrow points from the third party servers back to the handset, 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.](a3472689858b068ef469213682965325_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 |             |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                               | 11.0.0 | 12.0.0 |             |
+| 2015-12        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-13 version (MCC)                               | 12.0.0 | 13.0.0 |             |

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

@@ -0,0 +1,996 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 1 (Release 13)** ---
+
+![3GPP logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font. The '3' is bold and black, the 'G' is black, the 'P' is black, and the 'P' is black. There is a small red signal icon below the 'G'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, GPRS, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 routing 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 routing 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 mode       | Connection orientated, connectionless                      |
+|                                    | Traffic type (a)      | Variable bit rate and variable delay                       |
+| Mode                               | 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 |         |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                                                             | 11.0.0 | 12.0.0 |         |
+| 2015-12        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-13 version (MCC)                                                                             | 12.0.0 | 13.0.0 |         |

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

@@ -0,0 +1,423 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of Mobile Number Portability (MNP); Service description; Stage 1 (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the right of the "e" is a small "TM" symbol. Above the "lte" text are three green curved lines representing signal waves.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a red curved line. A small "TM" symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>TM</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP<sup>TM</sup> system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+## Keywords
+
+LTE, GSM, UMTS, addressing, portability,  
+supplementary service, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- 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 |           |
+| 2014-10        | -         | -         | -      | -   | -   | -      | -   | Update to Rel-12 version (MCC)                                                           | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -         | -         | -      | -   | -   | Rel-13 | -   | Updated to Rel-13 by MCC                                                                 | 12.0.0 | 13.0.0 |           |

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

@@ -0,0 +1,480 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1 (Release 13)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "e" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above the "ADVANCED" text are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the bottom right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top. The "P" and "P" are connected at the top. Below the second "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+GSM, UMTS, emergency, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 .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             |
+| 2014-10        | -         | -         | -          | -    | -   | -      | -   | Update to Rel-12 version (MCC)                                     | 11.1.0 | 12.0.0 | -                 |
+| 2015-12        | -         | -         | -          | -    | -   | Rel-13 | -   | Update to Rel-13 version (MCC)                                     | 12.0.0 | 13.0.0 | -                 |

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

@@ -0,0 +1,440 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects (2016-12)** **3GPP TS 22.072** **Call Deflection (CD) service description; Stage 1** **Technical Specification** **(Release 13)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a trademark symbol (TM). Above the "e" is the word "ADVANCED" in a smaller, uppercase font. To the left of the text is a red signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized, bold, black font with a trademark symbol (TM). Below the "P" is a red signal icon consisting of three curved lines of increasing height.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+## Keywords
+
+LTE, GSM, UMTS, CF, supplementary service,  
+stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -      | -   | Update to Rel-12 version (MCC)  | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | Rel-13 | -   | Update to Rel-13 version (MCC)  | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22076/raw.md

@@ -0,0 +1,302 @@
+
+
+# Keywords GSM, UMTS, codec, stage 1, LTE 3GPP TS 22.076 V13.0.0 (2015-12)
+
+*Technical Specification*
+
+## <sup>3GPP</sup> **3rd Generation Partnership Project;** ~~Postal address~~ **Technical Specification Group Services and System Aspects;** **Noise Suppression for the AMR Codec;** ~~3GPP support office address~~ **Service description;**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE Advanced Pro logo
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo
+
+# Copyright Notification
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.  
+The present document has been developed within the 3rd Generation Partnership Project (3GPP) and may be further elaborated for the purposes of 3GPP.
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
+
+GSM and the GSM logo are registered and approved by the GSM Association.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                                     |    |
+|---------------------------------------------------------------------|----|
+| Foreword .....                                                      | 4  |
+| 1 Scope.....                                                        | 5  |
+| 2 References.....                                                   | 5  |
+| 3 Definitions and abbreviations .....                               | 5  |
+| 4 Description.....                                                  | 5  |
+| 4.1 Applicability of Noise Suppression to Basic Services.....       | 5  |
+| 4.2 Support in Mobile Stations (MS) .....                           | 6  |
+| 4.3 Support in the Network .....                                    | 6  |
+| 4.4 Parameters to be indicated and negotiated.....                  | 6  |
+| 4.5 Provision of Service .....                                      | 6  |
+| 4.5.1 Location Independence.....                                    | 6  |
+| 4.5.2 Provision of service within and between networks .....        | 6  |
+| 4.5.3 Subscription and Billing Information .....                    | 6  |
+| 4.6 Quality of Service (QoS).....                                   | 6  |
+| 4.6.1 Impact on Speech Quality .....                                | 6  |
+| 4.6.1.1 Initial Convergence Time .....                              | 6  |
+| 4.6.1.2 No Degradation in Clean Speech.....                         | 7  |
+| 4.6.1.3 No Artefacts in Residual Noise .....                        | 7  |
+| 4.6.1.4 No Speech Clipping and no Reduction in Intelligibility..... | 7  |
+| 4.6.1.5 Quality Impact compared to AMR .....                        | 7  |
+| 4.6.2 Impact on Speech Path Delay.....                              | 7  |
+| 4.7 Impact on Complexity.....                                       | 7  |
+| 4.8 Impact on Channel Activity .....                                | 8  |
+| 5 Interaction with supplementary services.....                      | 8  |
+| 5.1 General .....                                                   | 8  |
+| 5.2 Explicit Call Transfer (ECT).....                               | 8  |
+| 5.3 Call wait/Call hold. ....                                       | 8  |
+| 5.4 Multiparty.....                                                 | 8  |
+| 5.5 Service Announcements.....                                      | 9  |
+| 6 Interaction with Alternate and Followed by services.....          | 9  |
+| 7 Interaction with other speech services .....                      | 9  |
+| 8 Interaction with DTMF and other signalling tones.....             | 9  |
+| 9 Interaction with Lawful Intercept .....                           | 9  |
+| 10 Interaction with TFO.....                                        | 9  |
+| Annex A (informative): Change Request 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.
+
+# --- 1 Scope
+
+The present document specifies the stage 1 description for the Noise Suppression feature for the AMR codec which enhances the input speech signal corrupted by acoustic noise. In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+
+# --- 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] ITU-T Recommendations I.130 (1988): "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
+- [2] GSM 01.04 (ETR 350): "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [3] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system".
+
+# --- 3 Definitions and abbreviations
+
+GSM 01.04 [2] (ETR 350) provides a list of abbreviations and acronyms used in GSM specifications.
+
+# --- 4 Description
+
+Noise Suppression for the AMR codec is an optional feature designed to enhance speech quality in a range of environments where there is significant (acoustic) background noise. The noise suppression function is a preprocessing module that is used to improve the signal to noise ratio of a speech signal prior to voice coding. In so doing it may use functions and/or data from the AMR speech encoding function. It shall be possible to implement AMR Noise Suppression in the mobile station (operating on the uplink speech signal). The possibility to implement AMR Noise Suppression in the network (operating on the downlink speech signal) is for further study. The noise suppression specification shall be comprised of bit exact fixed point C code. Test vectors shall be defined to verify operation.
+
+The AMR Speech decoder C-code should not be altered by the Noise Suppression.
+
+It shall be possible for the network to disable the operation of the example noise suppression algorithm defined by this feature, whether that operation is operational in the network, the mobile station, or both locations.
+
+## 4.1 Applicability of Noise Suppression to Basic Services.
+
+This feature shall be applicable (as an option) to all speech calls where the narrowband AMR codec is utilised. Operation of noise suppression for wideband AMR is for further study.
+
+## 4.2 Support in Mobile Stations (MS)
+
+Support of the Noise Suppression feature shall require modifications to future mobile stations. Provision of the feature in AMR-capable mobile stations is a manufacturer dependent option.
+
+Use of the feature in the network during a call should not place any requirements on its use within the MS. Similarly, use of the feature by the MS during a call shall not place any requirements on its use in the network.
+
+The network shall be able to enable or disable this example optional noise suppression function both at call set-up and in call [Signalling between network and mobile to allow this control is under study in SMG2 WPA].
+
+## 4.3 Support in the Network
+
+Provision of the feature in the network should be an option.
+
+Use of the feature in the network during a call should not place any requirements on its use within the MS. Similarly, use of the feature by the MS during a call should not place any requirements on its use in the network.
+
+The network should be able to enable or disable this example optional noise suppression function both at call set-up and in call.
+
+## 4.4 Parameters to be indicated and negotiated
+
+[TBD]
+
+## 4.5 Provision of Service
+
+### 4.5.1 Location Independence
+
+The Noise suppression feature shall be location independent.
+
+### 4.5.2 Provision of service within and between networks
+
+Provision of the feature is the same whether or not the call is wholly contained within a network or between networks.
+
+### 4.5.3 Subscription and Billing Information
+
+This feature shall not be provisioned on a per-subscriber basis and no record of the application of Noise Suppression is necessary for billing purposes.
+
+## 4.6 Quality of Service (QoS)
+
+### 4.6.1 Impact on Speech Quality
+
+The following performance requirements are stated under the assumption that the noise suppressor is tested as an integral part of the AMR speech codec with the speech codec operating at the following rates [TBD]. The performance requirements must be met for all these stated speech codec rates.
+
+#### 4.6.1.1 Initial Convergence Time
+
+The initial convergence time shall be a maximum of T seconds with T equal to 2s. The definition of this time interval shall be understood strictly in accordance with its means of use in subjective listening experiments. Its use shall be defined by a process whereby the first T seconds of each sample processed through the AMR speech codec with and without noise suppression active, is deleted before presentation to listeners. It is assumed that this process does not reduce intelligibility, or introduce clipping or similar effects into the resultant speech plus noise material.
+
+To test the subjective effect of initial convergence, there will be a subset of subjective testing defined where this initial period of T seconds is not removed from the processed samples. These tests should be representative of the full range of noise conditions.
+
+#### 4.6.1.2 No Degradation in Clean Speech
+
+The noise suppression function must not have a statistically significant distorting effect on clean speech, in comparison with the performance of the AMR codec without noise suppression applied. This requirement also applies to the case where tandeming of the standardised example noise suppression function occurs for mobile to mobile calls, in which case the reference condition is the tandem condition without noise suppression activated.
+
+This requirement also applies when VAD/DTX is active.
+
+#### 4.6.1.3 No Artefacts in Residual Noise
+
+The noise suppression function must not introduce any subjectively objectionable artefacts in the residual noise. This requirement also applies to the case where tandeming of the standardised example noise suppression function occurs for mobile to mobile calls, in which case the reference condition is the tandem condition without noise suppression activated.
+
+This requirement also applies when VAD/DTX is active.
+
+#### 4.6.1.4 No Speech Clipping and no Reduction in Intelligibility
+
+The noise suppression function should introduce no subjectively objectionable degradation such as clipping or distortion in the speech, and no reduction in intelligibility. This requirement also applies to the case where tandeming of the standardised example noise suppression function occurs for mobile to mobile calls, in which case the reference condition is the tandem condition without noise suppression activated.
+
+This requirement also applies when VAD/DTX is active.
+
+#### 4.6.1.5 Quality Impact compared to AMR
+
+The AMR speech codec with noise suppression activated must produce an output in noisy speech which is preferred amongst test listeners with statistical significance, compared to the case where noise suppression is not used. This requirement also applies to the case where tandeming of the standardised example noise suppression function occurs for mobile to mobile calls, in which case the reference condition is the tandem condition without noise suppression activated.
+
+This requirement also applies when VAD/DTX is active.
+
+### 4.6.2 Impact on Speech Path Delay
+
+The one way algorithmic delay due to the activation of AMR noise suppression shall be no more than 7 ms in excess of the delay inserted by the AMR speech codec.
+
+In handsfree case, this delay is part of the 39ms delay specified in GSM 03.50 [3].
+
+## 4.7 Impact on Complexity
+
+Table 4.1 defines complexity limits for AMR noise suppression.
+
+**Table 4.1 Complexity Requirements for AMR Noise Suppression**
+
+| Quantity                                 | Complexity Limit (Upper Bound)                                                                                                                                                                                                           |
+|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Number of weighted operations per second | 5 WMOPS                                                                                                                                                                                                                                  |
+| Scratch pad RAM                          | Re-use AMR speech encoder scratch pad RAM (or in the case of implementation which does not reside in the same device as the speech encoder, the available scratch pad RAM should be the same as that defined for the AMR speech encoder) |
+| Static RAM                               | 1,5 kwords                                                                                                                                                                                                                               |
+| Data ROM                                 | 1 kword                                                                                                                                                                                                                                  |
+| Program ROM                              | 2000 basic ETSI operations                                                                                                                                                                                                               |
+
+## 4.8 Impact on Channel Activity
+
+The AMR speech codec with noise suppression activated should not significantly increase channel activity when used in conjunction with DTX.
+
+Channel activity increase will be measured thanks to the Voice Activity factor (VAF), defined as follows.
+
+Let  $x$  be the VAF measured by the AMR VAD as an averaged value on all clean speech signals.
+
+Let  $y$  be the VAF measured by the AMR VAD without AMR NS active as an averaged value on all clean speech + noise signals (where the applicable clean speech signal is the speech signal used in the measure of  $x$ ).
+
+Let  $w$  be the VAF measured by the AMR VAD with AMR NS active as an averaged value on all clean speech + noise signals (where the applicable clean speech signal is the speech signal used in the measure of  $x$ ).  $w$  is required to be less than the maximum of  $y$  and  $x$ . Any case where  $w$  is greater than  $y$  should be further investigated.
+
+For real word signals,  $w$  is required not to be significantly greater than  $y$ . Any case where  $w$  is greater than  $y$  should be further investigated.
+
+These requirements shall apply to all standardized AMR VADs.  $(w,x,y)$  are determined using all VADs, and the requirements are checked relatively to each AMR VAD independently.
+
+# --- 5 Interaction with supplementary services
+
+## 5.1 General
+
+This clause defines the interactions between GSM supplementary services and the Noise Suppression Feature.
+
+The application of Noise Suppression shall not interfere with the provision or invocation of any supplementary services.
+
+## 5.2 Explicit Call Transfer (ECT)
+
+No adverse interaction. If the new party is a mobile station with support for the Noise Suppression feature, the noise suppression feature shall be invoked.
+
+## 5.3 Call wait/Call hold.
+
+No interaction.
+
+## 5.4 Multiparty
+
+No interaction.
+
+## 5.5 Service Announcements
+
+No interaction.
+
+# --- 6 Interaction with Alternate and Followed by services
+
+There shall be no impact on data transmission due the Noise Suppression Feature.
+
+# --- 7 Interaction with other speech services
+
+There is no requirement for Noise Suppression in ASCI services.
+
+# --- 8 Interaction with DTMF and other signalling tones
+
+DTMF and other signalling tones transmission performance during the application of Noise Suppression shall be no worse than the case where Noise Suppression is turned off.
+
+# --- 9 Interaction with Lawful Intercept
+
+In the case where lawful intercept is required in a call where Noise Suppression is activated, the Noise Suppression shall not cause any degradation in the speech quality received by the A and B parties.
+
+# --- 10 Interaction with TFO
+
+No interaction.
+
+# --- Annex A (informative): Change Request History
+
+| SMG#                  | Tdoc SMG | Spec     | CR | Cat | PH                              | Vers | New Vers | Subject                   |
+|-----------------------|----------|----------|----|-----|---------------------------------|------|----------|---------------------------|
+| 29                    | P-99-425 | 02.76    |    |     | 2+                              |      | 8.0.0    | New version 8.0.0 for R99 |
+| <b>Change history</b> |          |          |    |     |                                 |      |          |                           |
+| Date                  | TSG #    | TSG Doc. | CR | Rev | Subject/Comment                 |      | Old      | New                       |
+| 2001-03               | 11       |          |    |     | New version 4.0.0 for Release 4 |      | 8.0.0    | 4.0.0                     |
+| 2001-08               |          |          |    |     | Clean-up                        |      | 4.0.0    | 4.0.1                     |
+| 2002-06               | 16       |          |    |     | Version 5.0.0 for Release 5     |      | 4.0.1    | 5.0.0                     |
+| 2004-12               | 26       |          |    |     | Version 6.0.0 for Release 6     |      | 5.0.0    | 6.0.0                     |
+| 2007-06               | 36       |          |    |     | Version 7.0.0 for Release 7     |      | 6.0.0    | 7.0.0                     |
+| 2008-12               | 42       |          |    |     | Version 8.0.0 for Release 8     |      | 7.0.0    | 8.0.0                     |
+| 2009-12               | 46       |          |    |     | Version 9.0.0 for Release 9     |      | 8.0.0    | 9.0.0                     |
+| 2011-03               | 51       |          |    |     | Version 10.0.0 for Release 10   |      | 9.0.0    | 10.0.0                    |
+| 2012-09               | 57       |          |    |     | Version 11.0.0 for Release 11   |      | 10.0.0   | 11.0.0                    |
+| 2014-09               | 65       |          |    |     | Version 12.0.0 for Release 12   |      | 11.0.0   | 12.0.0                    |
+| 2015-12               | 70       |          |    |     | Version 13.0.0 for Release 13   |      | 12.0.0   | 13.0.0                    |
+

marked/Rel-13/22_series/22079/raw.md

@@ -0,0 +1,483 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of Optimal Routeing (SOR); Service definition; Stage 1 (Release 13)**
+
+![3GPP logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+---
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font with a red signal icon below the 'G'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, addressing, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                        |    |
+|----------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                         | 4  |
+| 1 Scope.....                                                                           | 5  |
+| 2 References.....                                                                      | 5  |
+| 3 Definitions and abbreviations .....                                                  | 5  |
+| 4 Description of Optimal Routing.....                                                  | 6  |
+| 5 Functional requirements.....                                                         | 6  |
+| 5.1 General .....                                                                      | 6  |
+| 5.2 Normal operation.....                                                              | 6  |
+| 5.2.1 A is a fixed subscriber or a mobile subscriber who may not benefit from OR ..... | 7  |
+| 5.2.2 A is a mobile subscriber who may benefit from OR .....                           | 8  |
+| 5.2.2.1 Description of the call routing .....                                          | 8  |
+| 5.2.2.2 Call scenarios handled in OR Phase 1 .....                                     | 9  |
+| 5.3 Exceptional procedures or unsuccessful outcome.....                                | 13 |
+| 5.3.1 Non-support of SOR in the VPLMN of the caller.....                               | 13 |
+| 5.3.2 Non-support of SOR in the HPLMN of the B subscriber .....                        | 13 |
+| 5.3.3 Non support of SOR in the VPLMN of the B subscriber.....                         | 13 |
+| 5.3.4 Calls to special mobile network numbers.....                                     | 13 |
+| 6 Interactions of Optimal Routing with Supplementary Services.....                     | 14 |
+| 6.1 Call Forwarding.....                                                               | 14 |
+| 6.2 Call Barring .....                                                                 | 14 |
+| 6.3 Call Transfer.....                                                                 | 14 |
+| 6.4 Call Deflection .....                                                              | 14 |
+| 6.5 Advice of Charge .....                                                             | 14 |
+| 7 Interactions of Optimal Routing with Operator Determined Barring (ODB).....          | 14 |
+| 8 Interactions of Optimal Routing with CAMEL .....                                     | 14 |
+| Annex A: 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
+
+This Stage 1 description of the first phase of Support of Optimal Routing (SOR):
+
+- compiles the basic service requirements for SOR;
+- describes the interactions for Supplementary Services (SS) in order to cater for SOR;
+- refers to modifications to network features required by SOR.
+
+This specification does not address the following:
+
+- There is no need for optimisation of the routing of calls originally directed to a fixed network subscriber, because the physical address of a fixed network terminating line cannot differ from its logical address.
+- SOR in non-PLMNs is not a subject of this TS, but might be possible by bilateral arrangement between PLMN operators and those non-PLMN operators.
+
+The purpose of SOR is to reduce the number of unnecessary inter-PLMN call legs.
+
+The first phase of SOR applies to:
+
+- OR for the benefit of the B party i.e. Mobile terminated calls with late call forwarding to the home or visited country (scenarios 1 and 2),  
+and optionally;
+- OR for the benefit of the A party, e.g. Mobile to mobile calls where both mobile subscribers are in the same country (scenarios 3 to 10).
+
+The complete set of scenarios included in the phase 1 of OR is presented in the paragraph for normal procedures. All other scenarios are excluded from Phase 1 of OR.
+
+Note that Optimal Routing is applicable to national roaming situations, that is to calls directed to a mobile subscriber roaming in her home country, but registered in a PLMN different from her HPLMN.
+
+All further call scenarios, including multiple call forwarding, are left to subsequent phases of SOR. Subsequent phases of SOR shall be backwards compatible with this first phase.
+
+# --- 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
+
+**Administrative PLMN:** The complete set of all functional entities normally regarded as a single PLMN.
+
+**Basic OR :** Routeing of a call by the direct route when no forwarding occurs.
+
+**Direct route:** A call uses the direct route if it is routed from the serving network of the original calling party to the serving network of the ultimate called party without any intermediate PLMN.
+
+**HPLMN route:** A call uses the HPLMN route if the destination is deduced from the MSISDN of the called party. This forces the call to be routed via the HPLMN of the called party.
+
+**HPLMN leg:** The HPLMN leg is that part of the HPLMN route from the IPLMN to the HPLMN of the called party.
+
+**IPLMN:** An IPLMN is a PLMN which interrogates the HPLMN of a called party in order to determine the whereabouts of that party.
+
+**Early Call Forwarding :** Early Call Forwarding is Call Forwarding performed from the IPLMN before the call has been extended to the VPLMN of the forwarding subscriber (i.e. Call Forwarding Unconditional and Conditional Call Forwarding on Not Reachable known at the IPLMN before extension of the call)
+
+**Functional PLMN:** For the purposes of this description the Administrative PLMN is divided into functional PLMNs that represent different aspects of the Optimal Routeing functionality.
+
+**Late Call Forwarding:** Late Call Forwarding is Call Forwarding performed after the call has been extended to the VPLMN of the forwarding subscriber (i.e. Conditional Call Forwarding on Busy, Conditional Call Forwarding on No Reply and Conditional Call Forwarding on Not Reachable detected in the VPLMN of the forwarding subscriber). Late Call Forwarding may be invoked in the IPLMN or in the VPLMN of the forwarding subscriber.
+
+**Special mobile network number:** For the purposes of this description special mobile network numbers are numbers belonging logically to a PLMN but not to a mobile subscriber. Examples are the customer service number or value added service numbers.
+
+Abbreviations are given in TR 21.905 [1].
+
+# --- 4 Description of Optimal Routing
+
+Support of Optimal Routing (SOR) is a network feature which enables the calls directed to a mobile subscriber to be routed directly to the mobile subscriber's actual location, or to her forwarded-to destination (instead of via the HPLMN or in the case of Late Call Forwarding via the VPLMN).
+
+The IPLMN handling the call shall decide whether or not to optimise the routing of the call taking into account information provided by the called mobile subscriber's HPLMN. For given subscribers, as a network option, the HPLMN may permit or deny OR on a per call basis.
+
+# --- 5 Functional requirements
+
+## 5.1 General
+
+SOR shall be provided for all circuit switched Telecommunication Services, except emergency calls, Dedicated PAD and Dedicated Packet Access (GPRS is for further study).
+
+The network feature shall be applied automatically for all calls except for those calls for which the HPLMN of the called party denies the optimal routing.
+
+## 5.2 Normal operation
+
+In the first phase of SOR, the routes of calls will be optimised for the cases of OR being performed within a country or towards the country where the call would have been routed normally.
+
+Under all other circumstances, the basic call routing is applied:
+
+- If the IPLMN detects that basic OR cannot be applied, the IPLMN routes the call according to the dialled number.
+- If the IPLMN detects that OR for Late Call Forwarding cannot be applied, the Call Forwarding will be performed in the VPLMN of the forwarding subscriber.
+
+If the serving network of the ultimate destination supports SOR, the serving network of the caller shall be able to indicate to the network visited by the ultimate destination that the call has been optimally routed and to indicate the originating PLMN of the optimally routed leg.
+
+The complete set of scenarios included in phase 1 of SOR is described below.
+
+The notation used for the scenario diagrams is defined in figure 1.
+
+![Figure 1: Notation used in scenario diagrams. The diagram defines symbols for traffic routes, call attempts, and PLMN types. A solid arrow represents a 'Traffic route'. A solid arrow with a cross (X) represents a 'Traffic route of basic GSM routeing, not used for OR'. A solid arrow represents a 'Call Attempt'. A dashed arrow represents 'Output of call record information'. A dashed arrow represents 'Interrogation'. An oval represents a 'Functional PLMN (e.g. IPLMN, VPLMN-B)'. A double oval represents an 'Administrative PLMN, which may include two functional PLMNs'.](d793cf7c174b89eb024d132f00679787_img.jpg)
+
+Figure 1: Notation used in scenario diagrams. The diagram defines symbols for traffic routes, call attempts, and PLMN types. A solid arrow represents a 'Traffic route'. A solid arrow with a cross (X) represents a 'Traffic route of basic GSM routeing, not used for OR'. A solid arrow represents a 'Call Attempt'. A dashed arrow represents 'Output of call record information'. A dashed arrow represents 'Interrogation'. An oval represents a 'Functional PLMN (e.g. IPLMN, VPLMN-B)'. A double oval represents an 'Administrative PLMN, which may include two functional PLMNs'.
+
+Figure 1: Notation used in scenario diagrams
+
+If one of those scenarios occurs, SOR shall be invoked.
+
+The assumptions taken are the following :
+
+- A subscriber A sets up a call to a mobile subscriber B, who may have forwarded her calls to a subscriber C.
+- The C subscriber may be either a fixed subscriber or a mobile subscriber.
+
+If C is a mobile subscriber, the location of C taken into account in the following paragraphs is the location of HPLMN-C.
+
+### 5.2.1 A is a fixed subscriber or a mobile subscriber who may not benefit from OR
+
+As the originating network does not have the ability to interrogate the HPLMN of the B subscriber, the normal call handling is applied.
+
+Once the HPLMN of the B subscriber has the control of the call, the call may be optimised in the case of a forwarded call towards a party located in the Home Country of the B subscriber or in the country visited by the B subscriber.
+
+- NOTE:
+- A may be in any country.
+  - In the two following cases, the IPLMN is HPLMN-B.
+
+![Scenario 1: OR for Late Call Forwarding, C is in the same country as HPLMN-B. The diagram shows three countries: Country X, Country Y, and Country Z. In Country X, subscriber A initiates a call. The call route goes to Country Y, where it enters the IPLMN. From the IPLMN, the call is forwarded to subscriber C, who is also in Country Y. A 'Call record: Call forwarding record OR flag' is generated at the IPLMN. The HPLMN-B is also in Country Y and is connected to the IPLMN. In Country Z, there is a VPLMN-B. Arrows with a cross (X) indicate that traffic routes from the IPLMN to the VPLMN-B are not used for OR. Arrows without a cross indicate the call attempt and the output of call record information.](06da11ab76cacc38bbcd714e437797ea_img.jpg)
+
+Scenario 1: OR for Late Call Forwarding, C is in the same country as HPLMN-B. The diagram shows three countries: Country X, Country Y, and Country Z. In Country X, subscriber A initiates a call. The call route goes to Country Y, where it enters the IPLMN. From the IPLMN, the call is forwarded to subscriber C, who is also in Country Y. A 'Call record: Call forwarding record OR flag' is generated at the IPLMN. The HPLMN-B is also in Country Y and is connected to the IPLMN. In Country Z, there is a VPLMN-B. Arrows with a cross (X) indicate that traffic routes from the IPLMN to the VPLMN-B are not used for OR. Arrows without a cross indicate the call attempt and the output of call record information.
+
+Scenario 1: OR for Late Call Forwarding, C is in the same country as HPLMN-B
+
+NOTE: Call records shown in the figure are only for information
+
+![Diagram illustrating a call routing scenario across three countries: Country X, Country Y, and Country Z. In Country X, subscriber A initiates a call. The call is routed to Country Y, where it passes through the IPLMN (Interworking PLMN). The IPLMN is connected to the HPLMN-B (Home PLMN of B) and the VPLMN-B (Visited PLMN of B). A call record is generated at the IPLMN, containing information about the call forwarding record and the OR flag. The call is then routed to Country Z, where it is received by the VPLMN-B. A call record is also generated at the VPLMN-B. The call is then routed to the destination C.](35a7554182eb055209552843f341a1ae_img.jpg)
+
+The diagram shows a call routing process across three countries: Country X, Country Y, and Country Z. In Country X, subscriber A initiates a call. The call is routed to Country Y, where it passes through the IPLMN (Interworking PLMN). The IPLMN is connected to the HPLMN-B (Home PLMN of B) and the VPLMN-B (Visited PLMN of B). A call record is generated at the IPLMN, containing information about the call forwarding record and the OR flag. The call is then routed to Country Z, where it is received by the VPLMN-B. A call record is also generated at the VPLMN-B. The call is then routed to the destination C.
+
+Diagram illustrating a call routing scenario across three countries: Country X, Country Y, and Country Z. In Country X, subscriber A initiates a call. The call is routed to Country Y, where it passes through the IPLMN (Interworking PLMN). The IPLMN is connected to the HPLMN-B (Home PLMN of B) and the VPLMN-B (Visited PLMN of B). A call record is generated at the IPLMN, containing information about the call forwarding record and the OR flag. The call is then routed to Country Z, where it is received by the VPLMN-B. A call record is also generated at the VPLMN-B. The call is then routed to the destination C.
+
+#### Scenario 2: OR for Late Call Forwarding, C is in the same country as VPLMN-B
+
+NOTE: Call records shown in the figure are only for information
+
+### 5.2.2 A is a mobile subscriber who may benefit from OR
+
+#### 5.2.2.1 Description of the call routing
+
+If A sets up a call to B, then the originating PLMN shall interrogate the HPLMN of the mobile subscriber B in order to know how to route the call.
+
+If B is registered in the same country as A, then the call shall be routed directly to B as described below.
+
+If B has activated a Call Forward to a destination located in the Home Country of B or in the country where A is registered and this leads to the invocation of Early Call Forwarding, then the call shall be routed directly from A to the forwarded-to-party.
+
+In any other cases, the call shall be routed to the mobile subscriber B via HPLMN(B).
+
+If the call cannot be completed, the originating PLMN shall receive an indication of the reason of the failure of the call completion.
+
+Thereafter, if the mobile subscriber B has activated a Conditional Call Forward to a destination located in her Home Country or to a destination in the country where A is registered and this leads to the invocation of Late Call Forwarding, then the originating PLMN shall route the call directly to the forwarded-to-party.
+
+The remaining leg of the call from the intermediate point to the ultimate destination may be optimally routed.
+
+#### 5.2.2.2 Call scenarios handled in OR Phase 1
+
+In the following scenarios, the IPLMN is VPLMN-A.
+
+##### 1) The call from the A subscriber to the B subscriber is completed (Basic OR)
+
+- B is located in the same country as A
+
+![Diagram for Scenario 3: BASIC OR, B in the same country as A. The diagram shows a call flow between Country X and Country Y. In Country X, a call originates from subscriber A to VPLMN-A. VPLMN-A sends an MO call record and routes the call to IPLMN. IPLMN routes the call to HPLMN-B in Country Y (step 3). HPLMN-B routes the call to VPLMN-B (step 4). VPLMN-B sends an MT call record and delivers the call to subscriber B (step 6). There are crossed-out arrows indicating alternative or rejected paths.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates the call flow for Scenario 3. Subscriber A in Country X initiates a call to VPLMN-A (step 1). VPLMN-A generates an MO call record (Dialled nmb, real destination, OR flag) and routes the call to IPLMN (step 2). IPLMN routes the call to HPLMN-B in Country Y (step 3). HPLMN-B routes the call to VPLMN-B (step 4). VPLMN-B generates an MT call record (OR flag) and delivers the call to subscriber B (step 6). Crossed-out arrows indicate that the call is not routed directly from IPLMN to VPLMN-B, nor from HPLMN-B to VPLMN-B.
+
+Diagram for Scenario 3: BASIC OR, B in the same country as A. The diagram shows a call flow between Country X and Country Y. In Country X, a call originates from subscriber A to VPLMN-A. VPLMN-A sends an MO call record and routes the call to IPLMN. IPLMN routes the call to HPLMN-B in Country Y (step 3). HPLMN-B routes the call to VPLMN-B (step 4). VPLMN-B sends an MT call record and delivers the call to subscriber B (step 6). There are crossed-out arrows indicating alternative or rejected paths.
+
+###### Scenario 3: BASIC OR, B in the same country as A
+
+NOTE: Call records shown in the figure are only for information
+
+b) B is located in her Home Country (Network usage optimization)
+
+![Diagram for Scenario 4: BASIC OR, B in her home country. The diagram shows a call flow between Country X and Country Y. In Country X, a call originates from subscriber A to VPLMN-A. VPLMN-A sends an MO call record and routes the call to IPLMN. IPLMN routes the call to HPLMN-B in Country Y (step 3). HPLMN-B routes the call to VPLMN-B (step 4). VPLMN-B generates an MT call record and delivers the call to subscriber B (step 6). There are crossed-out arrows indicating alternative or rejected paths.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+The diagram illustrates the call flow for Scenario 4. Subscriber A in Country X initiates a call to VPLMN-A (step 1). VPLMN-A generates an MO call record (Dialled nmb, real destination, OR flag) and routes the call to IPLMN (step 2). IPLMN routes the call to HPLMN-B in Country Y (step 3). HPLMN-B routes the call to VPLMN-B (step 4). VPLMN-B generates an MT call record (OR flag) and delivers the call to subscriber B (step 6). Crossed-out arrows indicate that the call is not routed directly from IPLMN to VPLMN-B, nor from HPLMN-B to VPLMN-B.
+
+Diagram for Scenario 4: BASIC OR, B in her home country. The diagram shows a call flow between Country X and Country Y. In Country X, a call originates from subscriber A to VPLMN-A. VPLMN-A sends an MO call record and routes the call to IPLMN. IPLMN routes the call to HPLMN-B in Country Y (step 3). HPLMN-B routes the call to VPLMN-B (step 4). VPLMN-B generates an MT call record and delivers the call to subscriber B (step 6). There are crossed-out arrows indicating alternative or rejected paths.
+
+###### Scenario 4: BASIC OR, B in her home country
+
+NOTE: Call records shown in the figure are only for information
+
+2) The call set up by the subscriber A is being forwarded to a C party
+
+2.1) Early Call Forward
+
+NOTE: for the two following scenarios, the location of B is not relevant.
+
+- a) the C party is in the same country as the A subscriber, but different from HPLMN B country.
+
+![Diagram for Scenario 5: Early CF, C in the same country as A. It shows a call flow from subscriber A in Country X (VPLMN-A) through IPLMN to HPLMN-B in Country Y, then being forwarded to C in Country X. Call records are generated at the subscriber and the forwarding node.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates a call flow for Scenario 5. Subscriber A in Country X (VPLMN-A) initiates a call (1) to the IPLMN (2). The IPLMN routes the call to HPLMN-B in Country Y (3). HPLMN-B then forwards the call to C in Country X (4). A call record is generated at the subscriber (MO record: Dialled nmb, real destination, OR flag) and at the forwarding node (Call forwarding record: OR flag). The call is rejected at the HPLMN-B node (5).
+
+Diagram for Scenario 5: Early CF, C in the same country as A. It shows a call flow from subscriber A in Country X (VPLMN-A) through IPLMN to HPLMN-B in Country Y, then being forwarded to C in Country X. Call records are generated at the subscriber and the forwarding node.
+
+**Scenario 5: Early CF, C in the same country as A**
+
+NOTE: Call records shown in the figure are only for information.
+
+- b) the C party is in the same country as HPLMN-B
+
+![Diagram for Scenario 6: Early CF, C in the same country as HPLMN-B. It shows a call flow from subscriber A in Country X (VPLMN-A) through IPLMN to HPLMN-B in Country Y, then being forwarded to C in Country Y. Call records are generated at the subscriber and the forwarding node.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+The diagram illustrates a call flow for Scenario 6. Subscriber A in Country X (VPLMN-A) initiates a call (1) to the IPLMN (2). The IPLMN routes the call to HPLMN-B in Country Y (3). HPLMN-B then forwards the call to C in Country Y (4). A call record is generated at the subscriber (MO record: Dialled nmb, real destination, OR flag) and at the forwarding node (Call forwarding record: OR flag). The call is rejected at the HPLMN-B node (5).
+
+Diagram for Scenario 6: Early CF, C in the same country as HPLMN-B. It shows a call flow from subscriber A in Country X (VPLMN-A) through IPLMN to HPLMN-B in Country Y, then being forwarded to C in Country Y. Call records are generated at the subscriber and the forwarding node.
+
+**Scenario 6: Early CF, C in the same country as HPLMN-B**
+
+NOTE: Call records shown in the figure are only for information
+
+##### 2.2) Late Call Forward
+
+- a) B and C are in the same country as A
+
+![Diagram for Scenario 7 showing call forwarding from Country X to Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call flow and record generation. Arrows 3, 4, and 5 are marked with an 'X'.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+The diagram illustrates Scenario 7: BASIC OR + OR for Late Call Forwarding. Country X contains two nodes: IPLMN and VPLMN-A. Country Y contains two nodes: HPLMN-B and VPLMN-B. The call flow is as follows:
+ 
+
+- Arrow 1: From point A to VPLMN-A. A call record box below it contains: "Call record: MO record (Dialled nmb, real destination, OR flag)".
+- Arrow 2: From VPLMN-A to IPLMN.
+- Arrow 3: From IPLMN to HPLMN-B. This arrow is marked with an 'X'.
+- Arrow 4: From HPLMN-B to IPLMN. This arrow is marked with an 'X'.
+- Arrow 5: From IPLMN to VPLMN-B. This arrow is marked with an 'X'.
+- Arrow 6: From VPLMN-A to point C. This arrow is marked with an 'X'.
+- Arrow 7: From IPLMN to a call record box containing: "Call record: Call forwarding record (OR flag)".
+
+Diagram for Scenario 7 showing call forwarding from Country X to Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call flow and record generation. Arrows 3, 4, and 5 are marked with an 'X'.
+
+**Scenario 7: BASIC OR + OR for Late Call Forwarding, B in the same country as A, C in the same country as A**
+
+NOTE: Call records shown in the figure are only for information
+
+- b) B is in the same country as A and C is in the same country as HPLMN-B
+
+![Diagram for Scenario 8 showing call forwarding from Country X to Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call flow and record generation. Arrows 3, 4, 5, and 6 are marked with an 'X'.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+The diagram illustrates Scenario 8: BASIC OR + OR for Late Call Forwarding. Country X contains two nodes: IPLMN and VPLMN-A. Country Y contains two nodes: HPLMN-B and VPLMN-B. The call flow is as follows:
+ 
+
+- Arrow 1: From point A to VPLMN-A. A call record box below it contains: "Call record: MO record (Dialled nmb, real destination, OR flag)".
+- Arrow 2: From VPLMN-A to IPLMN.
+- Arrow 3: From IPLMN to HPLMN-B. This arrow is marked with an 'X'.
+- Arrow 4: From HPLMN-B to IPLMN. This arrow is marked with an 'X'.
+- Arrow 5: From IPLMN to VPLMN-B. This arrow is marked with an 'X'.
+- Arrow 6: From IPLMN to point C. This arrow is marked with an 'X'.
+- Arrow 7: From IPLMN to a call record box containing: "Call record: Call forwarding record (OR flag)".
+
+Diagram for Scenario 8 showing call forwarding from Country X to Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call flow and record generation. Arrows 3, 4, 5, and 6 are marked with an 'X'.
+
+**Scenario 8: BASIC OR + OR for Late Call Forwarding, B in the same country as A, C in the same country as HPLMN-B**
+
+NOTE: Call records shown in the figure are only for information
+
+- c) B is in her home country and C is in the same country as A
+
+![Diagram for Scenario 9 showing call flow between Country X and Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call path from A to C, with call records generated at VPLMN-A and IPLMN.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+The diagram illustrates a call flow scenario between Country X and Country Y. In Country X, there are two network nodes: IPLMN and VPLMN-A. In Country Y, there are two network nodes: HPLMN-B and VPLMN-B. A call originates at point A (VPLMN-A) and is destined for point C (VPLMN-B). The call path is as follows: 1. From A to VPLMN-A; 2. From VPLMN-A to IPLMN; 3. From IPLMN to HPLMN-B; 4. From HPLMN-B to VPLMN-B (marked with a red 'X'); 5. From VPLMN-B to IPLMN; 6. From IPLMN to C. Call records are generated at VPLMN-A (MO record) and IPLMN (Call forwarding record).
+
+**Country X**        **Country Y**
+
+**Call record:**  
+Call forwarding record  
+(OR flag)
+
+**Call record:**  
+MO record  
+(Dialled nmb, real destination, OR flag)
+
+Diagram for Scenario 9 showing call flow between Country X and Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call path from A to C, with call records generated at VPLMN-A and IPLMN.
+
+###### **Scenario 9: BASIC OR + OR for Late Call Forwarding, B in the same country as HPLMN-B, C in the same country as A**
+
+NOTE: Call records shown in the figure are only for information
+
+d) B and C are in the country of HPLMN-B
+
+![Diagram for Scenario 10 showing call flow between Country X and Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call path from A to C, with call records generated at VPLMN-A and IPLMN. This diagram is identical to the one for Scenario 9.](853f59c89931a666c07903b31d098277_img.jpg)
+
+This diagram is identical to the one for Scenario 9, illustrating the same call flow and call record generation between Country X and Country Y.
+
+**Country X**        **Country Y**
+
+**Call record:**  
+Call forwarding record  
+(OR flag)
+
+**Call record:**  
+MO record  
+(Dialled nmb, real destination, OR flag)
+
+Diagram for Scenario 10 showing call flow between Country X and Country Y. Country X contains IPLMN and VPLMN-A. Country Y contains HPLMN-B and VPLMN-B. Arrows 1-6 show the call path from A to C, with call records generated at VPLMN-A and IPLMN. This diagram is identical to the one for Scenario 9.
+
+###### **Scenario 10: BASIC OR + OR for Late Conditional Call Forwarding, B in the same country as HPLMN-B, C in the same country as HPLMN-B**
+
+NOTE: Call records shown in the figure are only for information.
+
+## 5.3 Exceptional procedures or unsuccessful outcome
+
+### 5.3.1 Non-support of SOR in the VPLMN of the caller
+
+If subscriber A roams into a network not supporting OR, she may not benefit from OR and only scenario 1 and scenario 2 of SOR are supported.
+
+### 5.3.2 Non-support of SOR in the HPLMN of the B subscriber
+
+If the HPLMN of the called party does not support SOR, SOR cannot be invoked and the route of the call as far as the called party's VPLMN cannot be optimised (the call would normally be routed via the HPLMN of the called party).
+
+The same procedure shall be followed if the HPLMN operator denies OR on a subscriber basis.
+
+### 5.3.3 Non support of SOR in the VPLMN of the B subscriber
+
+If a subscriber whose HPLMN supports SOR registers in a VPLMN which does not support SOR, only the cases of Early Forwarded calls may be optimised.
+
+### 5.3.4 Calls to special mobile network numbers
+
+If the called number is a special mobile network number of the HPLMN, the HPLMN has to guarantee that the call terminates at its correct destination. This can be achieved by denying OR for this call by sending an appropriate error cause or by implementing a special handling.
+
+# --- 6 Interactions of Optimal Routing with Supplementary Services
+
+No Interaction unless it is stated differently below.
+
+## 6.1 Call Forwarding
+
+Interactions between SOR and Call Forwarding are dealt with in clause 5.0.
+
+## 6.2 Call Barring
+
+Outgoing Call Barring services are applied according to the dialled number.
+
+Barring of Incoming calls when Roaming outside the HPLMN country will prevent calls to a mobile subscriber who has roamed outside her HPLMN country even if OR would result in no chargeable roaming leg.
+
+The existing interactions between Call Forwardings and Call Barrings are not changed by the introduction of OR.
+
+## 6.3 Call Transfer
+
+A transferred call is considered as a set of two separate calls which may be separately optimally routed.
+
+Optimal Routing shall not be invoked as a result of the invocation of Call Transfer.
+
+## 6.4 Call Deflection
+
+A deflected call is considered as a late forwarded call and as such may be optimally routed.
+
+## 6.5 Advice of Charge
+
+Depending on call scenarios, AoC may not work properly.
+
+# --- 7 Interactions of Optimal Routing with Operator Determined Barring (ODB)
+
+The principles for the interaction between operator determined barring and SOR are the same as those for the interaction between Supplementary Service Call Barring and SOR.
+
+# --- 8 Interactions of Optimal Routing with CAMEL
+
+If CAMEL has to be applied to the Mobile Originating part of the call and if CAMEL modifies the destination of the call, the OR applies to any destination introduced by CAMEL.
+
+If CAMEL has to be applied to the Mobile Terminating part of the call or a forwarding leg, the modified destination is treated for optimal routing in the same way as a forwarded-to number.
+
+If Barring services are also applicable to the call then they have to be handled first together with CAMEL before SOR is applied.
+
+# Annex A: Change history
+
+| Change history |           |           |           |     |     |       |     |                                 |        |        |                   |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|---------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                 | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.79 |     |     |       |     | Transferred to 3GPP SA1         | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.079    |     |     | R99   |     | Transferred to 3GPP SA1         |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99627  | 22.079    | 001 |     | R99   | D   | Editorial changes for alignment | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.079    |     |     | Rel-4 |     | Transferred to 3GPP Release 4   | 3.0.1  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.079    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5      | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.079    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6     | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.079    |     |     | 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)  | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC        | 12.0.0 | 13.0.0 |                   |

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

@@ -0,0 +1,705 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Line identification Supplementary Services;**
+
+**3GPP TS 22.081 V13.0.0 (2015-12)**
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "4DVANCED" in a smaller, uppercase sans-serif font. Above the "4" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, CLIP, CLIR, COLP, COLR,  
+supplementary service, stage 1
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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            |
+| 2014-10        | -         | -         | -         | -    | -    | -      | -   | Update to Rel-12 version (MCC)                               | 11.1.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -    | -    | -      | -   | Updated to Rel-13 by MCC                                     | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22082/raw.md

@@ -0,0 +1,1413 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **3GPP TS 22.082 (2016-12)** **Call Forwarding (CF) Supplementary Services; Stage 1** *Technical Specification* **(Release 13)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in bold lowercase letters with a red signal icon above the "e", and the word "ADVANCED" in smaller uppercase letters to the right. A trademark symbol (TM) is at the bottom right.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized font with a red signal icon below the "P", and the text "A GLOBAL INITIATIVE" in smaller uppercase letters below the logo. A trademark symbol (TM) is at the bottom right.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, CF, supplementary service,  
+stage 1
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                       |    |
+|-------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                        | 6  |
+| 0 Scope.....                                                                                          | 6  |
+| 0.1 References.....                                                                                   | 7  |
+| 0.2 Definitions and abbreviations.....                                                                | 8  |
+| 1 Call Forwarding Unconditional .....                                                                 | 8  |
+| 1.1 Definition .....                                                                                  | 8  |
+| 1.2 Description .....                                                                                 | 8  |
+| 1.2.1 Description .....                                                                               | 8  |
+| 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 .....                                                                                | 8  |
+| 1.3.3 Registration.....                                                                               | 9  |
+| 1.3.4 Erasure .....                                                                                   | 9  |
+| 1.3.5 Activation .....                                                                                | 9  |
+| 1.3.6 Deactivation.....                                                                               | 9  |
+| 1.3.7 Invocation .....                                                                                | 10 |
+| 1.3.8 Normal operation with successful outcome.....                                                   | 10 |
+| 1.3.11 Interrogation .....                                                                            | 10 |
+| 1.3.12 Charging requirements .....                                                                    | 10 |
+| 1.4 Exceptional procedures or unsuccessful outcome.....                                               | 11 |
+| 1.4.2 Registration.....                                                                               | 11 |
+| 1.4.3 Erasure .....                                                                                   | 11 |
+| 1.4.4 Activation .....                                                                                | 11 |
+| 1.4.5 Deactivation.....                                                                               | 11 |
+| 1.4.6 Invocation .....                                                                                | 12 |
+| 1.5 Alternate procedures .....                                                                        | 12 |
+| 1.6 Interactions with other supplementary services .....                                              | 12 |
+| 1.6.81.1 Calling line identification presentation.....                                                | 12 |
+| 1.6.81.2 Calling line identification restriction .....                                                | 12 |
+| 1.6.81.3 Connected line identification presentation .....                                             | 12 |
+| 1.6.81.4 Connected line identification restriction.....                                               | 12 |
+| 1.6.82.2 Call forwarding on mobile subscriber busy .....                                              | 12 |
+| 1.6.82.3 Call forwarding on no reply.....                                                             | 13 |
+| 1.6.82.4 Call forwarding on mobile subscriber not reachable .....                                     | 13 |
+| 1.6.83.1 Call waiting.....                                                                            | 13 |
+| 1.6.84.1 Multi party .....                                                                            | 13 |
+| 1.6.85.1 Closed user group .....                                                                      | 13 |
+| 1.6.86.1 Advice of charge.....                                                                        | 13 |
+| 1.6.88.1 Barring of all outgoing calls .....                                                          | 13 |
+| 1.6.88.2 Barring of outgoing international calls .....                                                | 13 |
+| 1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country ..... | 13 |
+| 1.6.88.6 Barring of all incoming calls .....                                                          | 14 |
+| 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country.....                    | 14 |
+| 1.6.88.8 Anonymous Call Rejection.....                                                                | 14 |
+| 1.7 Interworking considerations.....                                                                  | 14 |
+| 2 Call Forwarding on Mobile Subscriber Busy .....                                                     | 14 |
+| 2.1 Definition .....                                                                                  | 14 |
+| 2.2 Description .....                                                                                 | 15 |
+| 2.2.1 Description .....                                                                               | 15 |
+| 2.2.2 Applicability to telecommunication services .....                                               | 15 |
+| 2.2.3 Terminology .....                                                                               | 15 |
+| 2.3 Normal procedures with successful outcome.....                                                    | 15 |
+| 2.3.1 Provision.....                                                                                  | 15 |
+| 2.3.2 Withdrawal .....                                                                                | 15 |
+| 2.3.3 Registration.....                                                                               | 15 |
+
+|          |                                                                                              |    |
+|----------|----------------------------------------------------------------------------------------------|----|
+| 2.3.4    | Erasure .....                                                                                | 16 |
+| 2.3.5    | Activation .....                                                                             | 16 |
+| 2.3.6    | Deactivation.....                                                                            | 16 |
+| 2.3.7    | Invocation .....                                                                             | 17 |
+| 2.3.8    | Normal operation with successful outcome.....                                                | 17 |
+| 2.3.11   | Interrogation .....                                                                          | 17 |
+| 2.3.12   | Charging requirements .....                                                                  | 17 |
+| 2.4      | Exceptional procedures or unsuccessful outcome.....                                          | 17 |
+| 2.4.2    | Registration.....                                                                            | 17 |
+| 2.4.3    | Erasure .....                                                                                | 18 |
+| 2.4.4    | Activation .....                                                                             | 18 |
+| 2.4.5    | Deactivation.....                                                                            | 18 |
+| 2.4.6    | Invocation .....                                                                             | 18 |
+| 2.5      | Alternate Procedures .....                                                                   | 19 |
+| 2.6      | Interactions with other supplementary services .....                                         | 19 |
+| 2.6.81.1 | Calling line identification presentation.....                                                | 19 |
+| 2.6.81.2 | Calling line identification restriction .....                                                | 19 |
+| 2.6.81.3 | Connected line identification presentation .....                                             | 19 |
+| 2.6.81.4 | Connected line identification restriction.....                                               | 19 |
+| 2.6.82.1 | Call forwarding unconditional .....                                                          | 19 |
+| 2.6.83.1 | Call waiting.....                                                                            | 19 |
+| 2.6.84.1 | Multi party .....                                                                            | 19 |
+| 2.6.85.1 | Closed user group .....                                                                      | 19 |
+| 2.6.86.1 | Advice of charge .....                                                                       | 19 |
+| 2.6.88.1 | Barring of all outgoing calls .....                                                          | 19 |
+| 2.6.88.2 | Barring of outgoing international calls .....                                                | 19 |
+| 2.6.88.4 | Barring of outgoing international calls except those directed to the home PLMN country ..... | 20 |
+| 2.6.88.6 | Barring of all incoming calls .....                                                          | 20 |
+| 2.6.88.7 | Barring of incoming calls when roaming outside the home PLMN country.....                    | 20 |
+| 2.6.88.8 | Anonymous Call Rejection.....                                                                | 21 |
+| 2.7      | Interworking considerations.....                                                             | 21 |
+| 3        | Call Forwarding on No Reply.....                                                             | 21 |
+| 3.1      | Definition .....                                                                             | 21 |
+| 3.2      | Description .....                                                                            | 21 |
+| 3.2.1    | Description .....                                                                            | 21 |
+| 3.2.2    | Applicability to telecommunication services .....                                            | 21 |
+| 3.2.3    | Terminology .....                                                                            | 21 |
+| 3.3      | Normal procedures with successful outcome.....                                               | 22 |
+| 3.3.1    | Provision.....                                                                               | 22 |
+| 3.3.2    | Withdrawal .....                                                                             | 22 |
+| 3.3.3    | Registration.....                                                                            | 22 |
+| 3.3.4    | Erasure .....                                                                                | 22 |
+| 3.3.5    | Activation .....                                                                             | 23 |
+| 3.3.6    | Deactivation.....                                                                            | 23 |
+| 3.3.7    | Invocation .....                                                                             | 23 |
+| 3.3.8    | Normal operation with successful outcome.....                                                | 23 |
+| 3.3.11   | Interrogation .....                                                                          | 24 |
+| 3.3.12   | Charging requirements .....                                                                  | 24 |
+| 3.4      | Exceptional procedures or unsuccessful outcome.....                                          | 24 |
+| 3.4.2    | Registration.....                                                                            | 24 |
+| 3.4.3    | Erasure .....                                                                                | 25 |
+| 3.4.4    | Activation .....                                                                             | 25 |
+| 3.4.5    | Deactivation.....                                                                            | 25 |
+| 3.4.6    | Invocation .....                                                                             | 25 |
+| 3.5      | Alternate procedures .....                                                                   | 25 |
+| 3.6      | Interactions with other supplementary services .....                                         | 26 |
+| 3.6.81.1 | Calling line identification presentation.....                                                | 26 |
+| 3.6.81.2 | Calling line identification restriction .....                                                | 26 |
+| 3.6.81.3 | Connected line identification presentation .....                                             | 26 |
+| 3.6.81.4 | Connected line identification restriction.....                                               | 26 |
+| 3.6.82.1 | Call forwarding unconditional .....                                                          | 26 |
+
+|                        |                                                                                              |    |
+|------------------------|----------------------------------------------------------------------------------------------|----|
+| 3.6.83.1               | Call waiting.....                                                                            | 26 |
+| 3.6.84.1               | Multi party .....                                                                            | 26 |
+| 3.6.85.1               | Closed user group .....                                                                      | 26 |
+| 3.6.86.1               | Advice of charge.....                                                                        | 26 |
+| 3.6.88.1               | Barring of all outgoing calls .....                                                          | 26 |
+| 3.6.88.2               | Barring of outgoing international calls .....                                                | 26 |
+| 3.6.88.4               | Barring of outgoing international calls except those directed to the home PLMN country ..... | 26 |
+| 3.6.88.6               | Barring of all incoming calls .....                                                          | 26 |
+| 3.6.88.7               | Barring of incoming calls when roaming outside the home PLMN country.....                    | 27 |
+| 3.6.88.8               | Anonymous Call Rejection.....                                                                | 27 |
+| 3.7                    | Interworking considerations.....                                                             | 27 |
+| 4                      | Call Forwarding on Mobile Subscriber Not Reachable .....                                     | 27 |
+| 4.1                    | Definition .....                                                                             | 27 |
+| 4.2                    | Description .....                                                                            | 27 |
+| 4.2.1                  | Description .....                                                                            | 27 |
+| 4.2.2                  | Applicability to telecommunication services .....                                            | 27 |
+| 4.2.3                  | Terminology .....                                                                            | 27 |
+| 4.3                    | Normal procedures with successful outcome.....                                               | 28 |
+| 4.3.1                  | Provision.....                                                                               | 28 |
+| 4.3.2                  | Withdrawal .....                                                                             | 28 |
+| 4.3.3                  | Registration.....                                                                            | 28 |
+| 4.3.4                  | Erasure .....                                                                                | 28 |
+| 4.3.5                  | Activation .....                                                                             | 29 |
+| 4.3.6                  | Deactivation.....                                                                            | 29 |
+| 4.3.7                  | Invocation .....                                                                             | 29 |
+| 4.3.8                  | Normal operation with successful outcome.....                                                | 29 |
+| 4.3.11                 | Interrogation .....                                                                          | 30 |
+| 4.3.12                 | Charging requirements .....                                                                  | 30 |
+| 4.4                    | Exceptional procedures or unsuccessful outcome.....                                          | 30 |
+| 4.4.2                  | Registration.....                                                                            | 30 |
+| 4.4.3                  | Erasure .....                                                                                | 30 |
+| 4.4.4                  | Activation .....                                                                             | 31 |
+| 4.4.5                  | Deactivation.....                                                                            | 31 |
+| 4.4.6                  | Invocation .....                                                                             | 31 |
+| 4.5                    | Alternate procedures .....                                                                   | 31 |
+| 4.6                    | Interactions with other supplementary services .....                                         | 31 |
+| 4.6.81.1               | Calling line identification presentation.....                                                | 31 |
+| 4.6.81.2               | Calling line identification restriction .....                                                | 31 |
+| 4.6.81.3               | Connected line identification presentation .....                                             | 31 |
+| 4.6.81.4               | Connected line identification restriction.....                                               | 32 |
+| 4.6.82.1               | Call forwarding unconditional .....                                                          | 32 |
+| 4.6.83.1               | Call waiting.....                                                                            | 32 |
+| 4.6.84.1               | Multi party .....                                                                            | 32 |
+| 4.6.85.1               | Closed user group .....                                                                      | 32 |
+| 4.6.86.1               | Advice of charge.....                                                                        | 32 |
+| 4.6.88.1               | Barring of all outgoing calls .....                                                          | 32 |
+| 4.6.88.2               | Barring of outgoing international calls .....                                                | 32 |
+| 4.6.88.4               | Barring of outgoing international calls except those directed to the home PLMN country ..... | 32 |
+| 4.6.88.6               | Barring of all incoming calls .....                                                          | 32 |
+| 4.6.88.7               | Barring of incoming calls when roaming outside the home PLMN country.....                    | 32 |
+| 4.6.88.8               | Anonymous Call Rejection.....                                                                | 32 |
+| 4.7                    | Interworking considerations.....                                                             | 33 |
+| Annex A (informative): | Change history.....                                                                          | 34 |
+
+# --- 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 specification describes the supplementary services belonging to the group CALL OFFERING SUPPLEMENTARY SERVICES.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in specification 3TS 22.004.
+
+The group of supplementary services CALL OFFERING SUPPLEMENTARY SERVICES is divided into four different supplementary services:
+
+- Call forwarding unconditional (section 1);
+- Call forwarding on mobile subscriber busy (section 2);
+- Call forwarding on no reply (section 3);
+- Call forwarding on mobile subscriber not reachable (section 4).
+
+## **Indication of active Call forwarding supplementary service.**
+
+An indication that a Call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made. There will be one indication for Unconditional call forwarding and another common indication for the Conditional call forwarding services.
+
+## **Note on the use of the forwarded-to number at registration.**
+
+If the forwarded-to number is a number in the HPLMN country, it may be entered by the served mobile subscriber in three different formats, independent of her actual location, according to the schemes:
+
+- 1) National (significant) number.
+- 2) National (trunk) prefix plus national (significant) number.
+- 3) International prefix\*, country code, national (significant) number.
+
+Scheme 3) Storage of numbers in this format is mandatory for all PLMN operators.
+
+If the forwarded-to number is a number in a country other than the HPLMN country, it shall be entered by the served mobile subscriber, independent of her actual location, according to the following scheme:
+
+- International prefix (NOTE), country code, national (significant) number.
+
+NOTE: The MMI for entering of international prefix is defined in 22.030.
+
+The maximum forwarded-to number length is 28 digits.
+
+## **Principles for interaction with the Barring of Outgoing Calls supplementary services.**
+
+Numbers allowed to call according to the Barring of Outgoing call service condition are allowed as forwarded-to numbers for the served mobile subscriber.
+
+Numbers not allowed to call according to the Barring of Outgoing call service condition are not allowed as forwarded-to numbers for the served mobile subscriber.
+
+For Unconditional Call Forwarding the forwarded leg is treated as an outgoing call from the HPLMN country.
+
+For the Conditional Call Forwarding services the forwarded leg is treated as an outgoing call from the LPLMN (HPLMN or VPLMN) country.
+
+## **Principles for interaction with the Barring of Incoming Calls supplementary services.**
+
+When Barring of all incoming calls is active for the served mobile subscriber - no Call forwarding services are allowed for her.
+
+When Barring of all incoming calls when roaming outside the HPLMN country is active and operative - i.e. the served mobile subscriber is roaming outside the HPLMN country, the Conditional Call Forwarding services are not allowed.
+
+## **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 TR 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.081: Line identification supplementary services - Stage 1".
+- [5] 3GPP TS22.083Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1".
+- [6] 3GPP TS 22.084MultiParty (MPTY) supplementary services - Stage 1".
+- [7] 3GPP TS 22.085Closed User Group (CUG) supplementary services - Stage 1".
+- [8] 3GPP TS 22.086: Advice of charge (AoC) supplementary services - Stage 1".
+- [9] 3GPP TS 22.088: “Call Barring (CB) supplementary services – Stage 1”.
+
+## **0.2 Definitions and abbreviations**
+
+Abbreviations used in this specification are listed in TR 22.905 [1].
+
+# --- 1 Call Forwarding Unconditional
+
+## 1.1 Definition
+
+This service permits a called mobile subscriber to have the network send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber's directory number to another directory number. The ability of the served mobile subscriber to originate calls is unaffected. If this service is activated, calls are forwarded no matter what the condition of the termination.
+
+## 1.2 Description
+
+### 1.2.1 Description
+
+The served mobile subscriber can request a different forwarded-to number for each Basic service group containing a basic service to which she has subscribed.
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004.
+
+### 1.2.3 Terminology
+
+A served mobile subscriber is a mobile subscriber of a particular PLMN access who is requesting that calls to her number be forwarded. This subscriber may also be referred to as the forwarding subscriber or the called subscriber.
+
+A forwarded-to subscriber is a subscriber to whom the call shall be forwarded.
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.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 options                                                            | Value     |
+|---------------------------------------------------------------------------------|-----------|
+| Calling subscriber receives notification the call has been forwarded            | No<br>Yes |
+| MSISDN of the served subscriber can be presented to the forwarded-to subscriber | No<br>Yes |
+
+### 1.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 1.3.3 Registration
+
+The following information has to be registered in the network:
+
+- 1) the forwarded-to number, which may be accompanied by a forwarded-to sub-address;
+- 2) information as to whether all calls or all calls of one (or several) specific Basic service groups should be forwarded.
+
+If no Basic Service code is inserted by the user this is interpreted as All Basic Services.
+
+Registration can take place either by the service provider or with an appropriate control procedure by the subscriber.
+
+Verification, where possible, of the forwarded-to number should be accomplished before accepting the call forwarding request. This verification is done by a simple check of the forwarded-to number to see if the number is within the allowed number range.
+
+When the mobile subscriber so registers call forwarding unconditional, the network will return notification of acceptance or rejection of the request. This notification will include the forwarded-to number to which call forwarding unconditional is registered.
+
+### 1.3.4 Erasure
+
+A previous registration can be erased in either of three ways:
+
+Firstly, the subscriber can specifically erase a previous registration with an appropriate control procedure.
+
+Secondly, the subscriber can register information for call forwarding unconditional for the specific Basic service group to another directory number, thus causing the previous registration of call forwarding unconditional to be overridden.
+
+Thirdly, all information is erased as a result of withdrawal of the service.
+
+### 1.3.5 Activation
+
+The user shall be allowed to activate Call Forwarding Unconditional (CFU) by e.g. using the MMI command described in 3GPP TS 22.030. This activation request may include information of which Basic Service Group(s) it shall apply to. If no such information is included the Activation request applies to all Basic Service Groups.
+
+When receiving an activation request the network shall activate CFU for the Basic Service Groups comprised in the BS group information given by the user against which a CFU forwarded-to-number is registered. The Activation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+When CFU is activated for Basic Service Group (Voice – MMI service code 11; Fax – MMI service code 13; Data – MMI service code 12) as defined in 3GPP TS 22.030 [3], a notification shall be sent to the user. Subsequently, when the UE is in idle mode, an indication may be given to the user to show that CFU for Basic Service Group Voice – MMI service code 11 is active.
+
+The supplementary service is also activated for a Basic service group as a result of Registration for that Basic service group.
+
+### 1.3.6 Deactivation
+
+An active CFU can be deactivated in either of two ways;
+
+- The user may deactivate CFU by means of an appropriate control procedure (e.g. as described in 3GPP TS 22.030). A deactivation request may contain information of which Basic Service Group(s) it shall apply to. If no such information is included the Deactivation request applies to all Basic Service Groups.
+
+When receiving a deactivation request the network shall deactivate CFU for the Basic Service Group(s) comprised in the BS group information given by the user against which a CFU forwarded-to-number is registered. However, the registered information shall not be erased. The Deactivation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+Even if there is no data stored against a particular Basic Service group comprised in a deactivation request, the request shall be accepted by the network for the other Basic Service group(s) included in the information given by the user.
+
+- The service is deactivated as a result of Erasure.
+
+In the former case, and also in the latter if Erasure is user controlled, the user shall receive a notification of whether her request was accepted or rejected in accordance with the rules set out in 3GPP TS 22.004.
+
+### 1.3.7 Invocation
+
+If the supplementary service is activated for a Basic service incoming calls for the specified Basic service will be forwarded by network invocation.
+
+### 1.3.8 Normal operation with successful outcome
+
+When call forwarding unconditional is active and operative, incoming calls for the specified Basic Service(s) will be forwarded without being offered to the served mobile subscriber.
+
+The forwarded-to subscriber will receive an indication that the call has been forwarded with the cause. The cause, when available, will be the appropriate forwarding condition. Depending on the value of the served subscribers subscription option, the forwarded-to subscriber may also receive the MSISDN of the served subscriber.
+
+When multiple forwarding occurs the reason for forwarding and the MSISDN given to the forwarded-to subscriber should relate to the last forwarding subscriber in the chain.
+
+When call forwarding unconditional is active and operative, the ability of the served mobile subscriber to originate calls is not affected. However, an indication that the call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made.
+
+As a subscription option, the served mobile subscriber can request that the calling subscriber receives a notification that the call has been forwarded.
+
+NOTE: In case the notification is implemented using intermediate tones or announcements, the tones and/or announcements to the calling party should not be provided if the information transfer capability is set to UDI.
+
+### 1.3.11 Interrogation
+
+#### Data request
+
+The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information:
+
+- in response to a general data request the served mobile subscriber should be given a list of all Basic service groups to which call forwarding unconditional is registered, including information whether or not it is active and operative, and the associated forwarded-to numbers;
+- in response to a specific request concerning one particular Basic service group, the served mobile subscriber should be informed whether or not call forwarding unconditional is registered, including information whether or not it is active and operative for that Basic service group. If CFU is registered, the associated forwarded-to number shall be given.
+
+### 1.3.12 Charging requirements
+
+The forwarding subscriber may be charged for the forwarded part of the call.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+### 1.4.2 Registration
+
+If the system cannot accept a registration request, the served mobile subscriber should receive a notification that call forwarding unconditional registration was not successful. Possible causes are:
+
+- service not subscribed to;
+- forwarded-to number is invalid directory number;
+- use of an operator access prefix;
+- insufficient information;
+- forwarded-to number is a special service code (e.g. police);
+- forwarded-to number is the directory number of the mobile subscriber herself;
+- conflicting situation with other supplementary services (e.g. incoming call barring has been activated);
+- no basic service provisioned within the basic service group(s).
+
+The network is not required to validate information related to the forwarded-to number.
+
+### 1.4.3 Erasure
+
+If the network cannot accept a mobile subscriber's request for erasure, cause will be returned to the subscriber, such as:
+
+- insufficient information;
+- inconsistent with registration.
+
+If the subscriber does not completely specify which call forwarding unconditional request is to be erased, the network will reject the erasure request with appropriate cause.
+
+If no Basic Service Code is inserted by the user, CF will be erased from all Basic Services.
+
+### 1.4.4 Activation
+
+If there is no CFU forwarded-to-number registered against a Basic Service group, the activation request for that Basic Service group shall be denied.
+
+Examples of causes for a not accepted activation request:
+
+- service not provisioned;
+- conflicting situation with other supplementary services;
+- service not registered.
+
+### 1.4.5 Deactivation
+
+If the network cannot accept a deactivation request, an appropriate cause will be returned to the user, e.g. Service not Active.
+
+### 1.4.6 Invocation
+
+Within a PLMN or different PLMNs the number of tandem forwarding connections 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 forwarded call cannot be completed to the forwarded-to destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards.
+
+NOTE: Call forwarding unconditional applies only to the Basic services subscribed to. Calls to a directory number requesting a Basic service which is not subscribed to will never be forwarded.
+
+## 1.5 Alternate procedures
+
+None identified.
+
+## 1.6 Interactions with other supplementary services
+
+### 1.6.81.1 Calling line identification presentation
+
+See 3GPP TS 22.081.
+
+### 1.6.81.2 Calling line identification restriction
+
+See 3GPP TS 22.081.
+
+### 1.6.81.3 Connected line identification presentation
+
+See 3GPP TS 22.02.81.
+
+### 1.6.81.4 Connected line identification restriction
+
+See 3GPP TS 22.02.81.
+
+### 1.6.82.2 Call forwarding on mobile subscriber busy
+
+If Call forwarding unconditional is active, activation of Call forwarding on mobile subscriber busy is rejected. The served mobile subscriber shall be informed of this supplementary service incompatibility.
+
+If Call forwarding on mobile subscriber busy is active, activation of Call forwarding unconditional will be accepted. Call forwarding on mobile subscriber busy will be quiescent during the active period of Call forwarding unconditional. If Call forwarding unconditional is subsequently deactivated, Call forwarding on mobile subscriber busy becomes operative again (unless the interaction with another supplementary service requests that it remains quiescent).
+
+If Call forwarding unconditional is active for one particular basic service, activation of Call forwarding on mobile subscriber busy for all basic services is rejected. The served mobile subscriber shall be informed of this supplementary service incompatibility.
+
+If Call forwarding on mobile subscriber busy is active for one particular basic service, activation of Call forwarding unconditional for all basic services will be accepted. Call forwarding on mobile subscriber busy will be quiescent during the active period of Call forwarding unconditional. If Call forwarding unconditional is subsequently deactivated, Call forwarding on mobile subscriber busy becomes operative again (unless the interaction with another supplementary service requests that it remains quiescent).
+
+#### 1.6.82.3 Call forwarding on no reply
+
+Same as interaction between Call forwarding unconditional and Call forwarding on mobile subscriber busy.
+
+#### 1.6.82.4 Call forwarding on mobile subscriber not reachable
+
+Same as interaction between Call forwarding unconditional and Call forwarding on mobile subscriber busy.
+
+#### 1.6.83.1 Call waiting
+
+See 3GPP TS 22.083.
+
+#### 1.6.84.1 Multi party
+
+See 3GPP TS 22.084.
+
+#### 1.6.85.1 Closed user group
+
+See 3GPP TS 22.085.
+
+#### 1.6.86.1 Advice of charge
+
+See 3GPP TS 22.086.
+
+#### 1.6.88.1 Barring of all outgoing calls
+
+Served mobile subscriber:
+
+- If barring of all outgoing calls is active, the registration and/or activation of call forwarding unconditional is denied. The mobile subscriber requesting for this call forwarding service shall be informed of this supplementary service incompatibility.
+- If Call forwarding unconditional is active, activation of Barring of all outgoing calls is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+
+#### 1.6.88.2 Barring of outgoing international calls
+
+Served mobile subscriber:
+
+- If barring of outgoing international calls is active, the registration of an international forwarded-to number (from the home PLMN country) for call forwarding unconditional, as well as the activation of call forwarding unconditional to such a forwarded-to number, is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Call forwarding unconditional is active to an international forwarded-to number (from the HPLMN country), activation of Barring of outgoing international calls is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+
+#### 1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country
+
+Same as interaction between Call forwarding unconditional and Barring of outgoing international calls.
+
+#### 1.6.88.6 Barring of all incoming calls
+
+Calling subscriber: No interaction
+
+Served mobile subscriber:
+
+- If barring of all incoming calls is active, the registration and/or activation of call forwarding unconditional is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Call forwarding unconditional is active, activation of Barring of all incoming calls is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+
+Forwarded-to subscriber: Calls forwarded to a subscriber having Barring of all incoming calls active, will be denied as any other incoming call to that subscriber.
+
+#### 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country
+
+Served mobile subscriber:
+
+- If Barring of Incoming Calls when Roaming Outside the HPLMN Country is active, registration and/or activation of Call Forwarding Unconditional is permitted and Barring of Incoming Calls when Roaming Outside the HPLMN Country becomes quiescent.
+- If Call Forwarding Unconditional is active, activation of Barring of Incoming Calls when Roaming Outside the HPLMN Country is not permitted. The mobile subscriber shall be informed of this supplementary service incompatibility.
+
+Forwarded to subscriber: Calls forwarded to a subscriber having Barring of incoming calls when roaming outside the HPLMN country active and operative, will be denied as any other incoming call to that subscriber.
+
+#### 1.6.88.8 Anonymous Call Rejection
+
+See 3GPP TS 22.088 [9].
+
+## 1.7 Interworking considerations
+
+If the forwarded-to number is not a PLMN- or ISDN-number, then an interworking situation is said to exist.
+
+If a forwarded call 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.
+
+NOTE1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited.
+
+NOTE2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI.
+
+# 2 Call Forwarding on Mobile Subscriber Busy
+
+## 2.1 Definition
+
+This service permits a called mobile subscriber to have the network send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber's directory number and which meet mobile subscriber busy to another directory number. The ability of the served mobile subscriber to originate calls is unaffected. If this service is activated, a call is forwarded only if the call meets mobile subscriber busy.
+
+## 2.2 Description
+
+### 2.2.1 Description
+
+The served mobile subscriber can request a different forwarded-to number for each Basic service group containing a basic service to which she has subscribed.
+
+### 2.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004.
+
+### 2.2.3 Terminology
+
+A served mobile subscriber is a mobile subscriber of a particular PLMN access who is requesting that calls to her number be forwarded. This subscriber may also be referred to as the forwarding subscriber or the called subscriber.
+
+A forwarded-to subscriber is a subscriber to whom the call shall be forwarded.
+
+## 2.3 Normal procedures with successful outcome
+
+### 2.3.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 options are summarized below:
+
+| <u>Subscription options</u>                                                     | <u>Value</u>  |
+|---------------------------------------------------------------------------------|---------------|
+| Forwarding subscriber receives notification that the call has been forwarded    | - No<br>- Yes |
+| Calling subscriber receives notification that the call has been forwarded       | - No<br>- Yes |
+| MSISDN of the served subscriber can be presented to the forwarded-to subscriber | - No<br>- Yes |
+
+In case of User Determined User Busy (UDUB) a notification towards the forwarding subscriber will not be given.
+
+### 2.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 2.3.3 Registration
+
+The following information has to be registered in the network:
+
+- 1) the forwarded-to number, which may be accompanied by a forwarded-to sub-address;
+- 2) information as to whether all calls or all calls of one (or several) specific Basic service group(s) should be forwarded.
+
+If no Basic Service Code is inserted by the user this is interpreted as All Basic Services.
+
+Registration can take place either by the service provider or with an appropriate control procedure by the subscriber. Verification, where possible, of the forwarded-to number should be accomplished before accepting the call forwarding request. This verification is done by a simple check of the forwarded-to number to see if the number is within the allowed number range.
+
+When the mobile subscriber so registers call forwarding on mobile subscriber busy, the network will return notification of acceptance or rejection of the request. This notification will include the forwarded-to number to which call forwarding on mobile subscriber busy is registered.
+
+### 2.3.4 Erasure
+
+A previous registration can be erased in either of three ways:
+
+Firstly, the subscriber can specifically erase a previous registration with an appropriate control procedure.
+
+Secondly, the subscriber can register information for call forwarding on mobile subscriber busy for the specific Basic service group to another directory number, thus causing the previous registration of call forwarding on mobile subscriber busy to be overridden.
+
+Thirdly, all information is erased as a result of withdrawal of the service.
+
+### 2.3.5 Activation
+
+The user shall be allowed to activate Call Forwarding on Busy (CFB) by e.g. using the MMI command described in 3GPP TS 22.030. This activation request may include information of which Basic Service Group(s) it shall apply to. If no such information is included, the Activation request applies to all Basic Service Groups.
+
+When receiving an activation request the network shall activate CFB for the Basic Service Groups comprised in the BS group information given by the user against which a CFB forwarded-to-number is registered. The Activation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+The user shall receive a notification that CFB has been activated.
+
+The supplementary service is also activated for a Basic service group as a result of registration for that Basic service group.
+
+### 2.3.6 Deactivation
+
+An active CFB can be deactivated in either of two ways:
+
+- The user may deactivate CFB by means of an appropriate control procedure (e.g. as described in 3GPP TS 22.030). A deactivation request may contain information of which Basic Service Group(s) it shall apply to. If no such information is included, the Deactivation request applies to all Basic Service Groups.
+
+When receiving a deactivation request the network shall deactivate CFB for the Basic Service Groups comprised in the BS group information given by the user against which a CFB forwarded-to-number is registered. However, the registered information shall not be erased. The Deactivation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+Even if there is no data stored against a particular Basic Service group comprised in a deactivation request, the request shall be accepted by the network for the other Basic Service group(s) included in the information given by the user.
+
+- The service is deactivated as a result of Erasure.
+
+In the former case, and also in the latter if Erasure is user controlled, the user shall receive a notification of whether her request was accepted or rejected in accordance with the rules set out in 3GPP TS 22.004.
+
+### 2.3.7 Invocation
+
+If the supplementary service is activated for a Basic service incoming calls for the specified Basic service that meet mobile subscriber busy will be forwarded by network invocation.
+
+### 2.3.8 Normal operation with successful outcome
+
+When call forwarding on mobile subscriber busy is active and operative, incoming calls for the specified Basic Service(s) that meet mobile subscriber busy with the condition UDUB (User Determined User Busy) will be forwarded. Incoming calls for the specified basic service(s) that meet mobile subscriber busy with the condition NDUB (Network Determined User Busy) will be forwarded without being offered to the served mobile subscriber.
+
+When an incoming call is forwarded on mobile subscriber busy with the condition NDUB the served mobile subscriber can, as a subscription option, receive notification.
+
+The forwarded-to subscriber will receive an indication that the call has been forwarded with the cause. The cause, when available, will be the appropriate forwarding condition. Depending on the value of the served subscribers subscription option, the forwarded-to subscriber may also receive the MSISDN of the served subscriber.
+
+When multiple forwarding occurs the reason for forwarding and the MSISDN given to the forwarded-to subscriber should relate to the last forwarding subscriber in the chain.
+
+When call forwarding on mobile subscriber busy is active and operative, the ability of the served mobile subscriber to originate calls is not affected. However, an indication that the call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made.
+
+As a subscription option, the served mobile subscriber can request that the calling subscriber receives a notification that the call has been forwarded.
+
+NOTE: In case the notification is implemented using intermediate tones or announcements, the tones and/or announcements to the calling party should not be provided if the information transfer capability is set to UDI.
+
+### 2.3.11 Interrogation
+
+#### Data request
+
+The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information:
+
+- in response to a general data request the served mobile subscriber should be given a list of all Basic service groups to which call forwarding on mobile subscriber busy is registered, including information whether it is active and if so, whether it is operative or quiescent, and the associated forwarded-to numbers;
+- in response to a specific request concerning one particular Basic service group, the served mobile subscriber should be informed whether or not call forwarding on mobile subscriber busy is registered, including information whether it is active and if so, whether it is operative or quiescent for that Basic service group. If CFB is registered, the associated forwarded-to number shall be given.
+
+### 2.3.12 Charging requirements
+
+The forwarding subscriber may be charged for the forwarded part of the call.
+
+## 2.4 Exceptional procedures or unsuccessful outcome
+
+### 2.4.2 Registration
+
+If the system cannot accept a registration request, the served mobile subscriber should receive a notification that call forwarding on mobile subscriber busy registration was not successful. Possible causes are:
+
+- service not subscribed to;
+
+- forwarded-to number is invalid directory number;
+- use of an operator access prefix;
+- insufficient information;
+- forwarded-to number is a special service code (e.g. police);
+- forwarded-to number is the directory number of the mobile subscriber herself;
+- conflicting situation with other supplementary services (e.g. incoming call barring has been activated);
+- no basic service provisioned within the basic service groups.
+
+The network is not required to validate information related to the forwarded-to number.
+
+### 2.4.3 Erasure
+
+If the network cannot accept a mobile subscriber's request for erasure, cause will be returned to the subscriber, such as:
+
+- insufficient information;
+- inconsistent with registration.
+
+If the subscriber does not completely specify which call forwarding on mobile subscriber busy request is to be erased, the network will reject the erasure request with appropriate cause.
+
+If no Basic Service Code is inserted by the user, CF will be erased from all Basic Services.
+
+### 2.4.4 Activation
+
+If there is no CFB forwarded-to-number registered against a Basic Service group, the activation request for that Basic Service group shall be denied.
+
+Examples of causes for a not accepted activation request:
+
+- service not provisioned;
+- conflicting situation with other supplementary services;
+- service not registered.
+
+### 2.4.5 Deactivation
+
+If the network cannot accept a deactivation request, an appropriate cause will be returned to the user, e.g. Service not Active.
+
+### 2.4.6 Invocation
+
+Within a PLMN or different PLMNs the number of tandem forwarding connections 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 forwarded call cannot be completed to the forwarded-to destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards.
+
+NOTE: Call forwarding on mobile subscriber busy applies only to the Basic services subscribed to. Calls to a directory number requesting a Basic service which is not subscribed to will never be forwarded.
+
+## 2.5 Alternate Procedures
+
+None identified.
+
+## 2.6 Interactions with other supplementary services
+
+### 2.6.81.1 Calling line identification presentation
+
+See 3GPP TS 22.081.
+
+### 2.6.81.2 Calling line identification restriction
+
+See 3GPP TS 22.081.
+
+#### 2.6.81.3 Connected line identification presentation
+
+See 3GPP TS 22.081.
+
+#### 2.6.81.4 Connected line identification restriction
+
+See 3GPP TS 22.081.
+
+#### 2.6.82.1 Call forwarding unconditional
+
+See section 1.6.82.2.
+
+#### 2.6.83.1 Call waiting
+
+See 3GPP TS 22.083.
+
+#### 2.6.84.1 Multi party
+
+See 3GPP TS 22.084.
+
+#### 2.6.85.1 Closed user group
+
+See 3GPP TS 22.085.
+
+#### 2.6.86.1 Advice of charge
+
+See 3GPP TS 22.086.
+
+#### 2.6.88.1 Barring of all outgoing calls
+
+Same as the interaction between call forwarding unconditional and barring of all outgoing calls.
+
+#### 2.6.88.2 Barring of outgoing international calls
+
+Served mobile subscriber:
+
+- If barring of outgoing international calls is active, the registration of an international forwarded-to number (from the visited PLMN country) for call forwarding on mobile subscriber busy, as well as the activation of call forwarding on mobile subscriber busy to such a forwarded-to number, is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Call forwarding on mobile subscriber busy is active to an international forwarded-to number (from the local PLMN country), activation of Barring of outgoing international calls is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Barring of outgoing international calls and Call forwarding on mobile subscriber busy are simultaneously active (i.e. the forwarded-to number is a local number seen from the local PLMN country), Call forwarding on mobile subscriber busy will be made quiescent by the network as soon as the mobile subscriber updates in another PLMN country.
+- If barring of outgoing international calls is subsequently deactivated, or if the mobile subscriber updates in a PLMN where the forwarded-to number is not considered as an international number, call forwarding on mobile subscriber busy is automatically made operative (unless the interaction with another supplementary service requests that it remains quiescent).
+
+#### 2.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country
+
+Served mobile subscriber:
+
+- If Barring of outgoing international calls except those directed to the home PLMN country is active, the registration of an international forwarded-to number (from the local PLMN country) except to the HPLMN country, as well as the activation of call forwarding on mobile subscriber busy to such a forwarded-to number, is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Call forwarding on mobile subscriber busy is active to an international forwarded-to number (from the local PLMN country) except to the HPLMN country, activation of Barring of outgoing international calls except those directed to the home PLMN country is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Barring of outgoing international calls except those directed to the home PLMN country and Call forwarding on mobile subscriber busy are simultaneously active (i.e. the forwarded-to number is a local number seen from the local PLMN country or a number in the HPLMN country), Call forwarding on mobile subscriber busy will be made quiescent as soon as the mobile subscriber is updated in another PLMN country if the forwarded-to number is not a number in the HPLMN country.
+- If Barring of outgoing international calls except those directed to the home PLMN country is subsequently deactivated, or if the mobile subscriber updates in a PLMN where the forwarded-to number is not barred, Call forwarding on mobile subscriber busy is automatically made operative (unless the interaction with another supplementary service requests that it remains quiescent).
+
+#### 2.6.88.6 Barring of all incoming calls
+
+Same as the interaction between call forwarding unconditional and barring of all incoming calls.
+
+#### 2.6.88.7 Barring of incoming calls when roaming outside the home PLMN country
+
+Served mobile subscriber:
+
+- If Barring of incoming calls when roaming outside the home PLMN country is active and operative (i.e. the mobile subscriber is roaming outside the home PLMN country) then the registration and/or activation of Call forwarding on mobile subscriber busy is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If Barring of incoming calls when roaming outside the home PLMN country is active and quiescent (i.e. the mobile subscriber is in the home PLMN country), then the registration and/or activation of Call forwarding on mobile subscriber busy is not denied.
+- If Barring of incoming calls when roaming outside the home PLMN country becomes operative after Call forwarding on mobile subscriber busy has been registered and/or activated, Call forwarding on mobile subscriber busy is made quiescent.
+- If Barring of incoming calls when roaming outside the home PLMN country subsequently becomes quiescent, Call forwarding on mobile subscriber busy is automatically made operative (unless the interaction with another supplementary service requests that it remains quiescent).
+- If Call forwarding on mobile subscriber busy is active and operative and the mobile subscriber is roaming outside the home PLMN country, activation of Barring of incoming calls when roaming outside the HPLMN country is denied. The mobile subscriber shall be informed of this supplementary service incompatibility.
+- If call forwarding on mobile subscriber busy is active and quiescent and the mobile subscriber is roaming in the home PLMN country, activation of Barring of incoming calls when roaming outside the HPLMN country is not denied.
+
+Forwarded to subscriber: Calls forwarded to a subscriber having Barring of incoming calls when roaming outside the HPLMN country active and operative, will be denied as any other incoming call to that subscriber.
+
+#### 2.6.88.8 Anonymous Call Rejection
+
+See 3GPP TS 22.088 [9].
+
+## 2.7 Interworking considerations
+
+If the forwarded-to number is not a PLMN- or ISDN-number, then an interworking situation is said to exist.
+
+If a forwarded call 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.
+
+NOTE1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited.
+
+NOTE2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI.
+
+# 3 Call Forwarding on No Reply
+
+## 3.1 Definition
+
+This service permits a called mobile subscriber to have the network send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber's directory number and which meet no reply to another directory number. The ability of the served mobile subscriber to originate calls is unaffected. If this service is activated, a call is forwarded only if the call meets no reply.
+
+## 3.2 Description
+
+### 3.2.1 Description
+
+The served mobile subscriber can request a different forwarded-to number for each Basic service group containing a basic service to which she has subscribed.
+
+### 3.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004.
+
+### 3.2.3 Terminology
+
+A served mobile subscriber is a mobile subscriber of a particular PLMN access who is requesting that calls to her number be forwarded. This subscriber may also be referred to as the forwarding subscriber or the called subscriber.
+
+A forwarded-to subscriber is a subscriber to whom the call shall be forwarded.
+
+## 3.3 Normal procedures with successful outcome
+
+### 3.3.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 options are summarized below:
+
+| <u>Subscription options</u>                                                  | <u>Value</u>  |
+|------------------------------------------------------------------------------|---------------|
+| Forwarding subscriber receives notification that the call has been forwarded | - No<br>- Yes |
+| Calling subscriber receives notification that the call has been forwarded    | - No<br>- Yes |
+| MSISDN of the served subscriber can be                                       | - No          |
+
+presented to the forwarded-to subscriber
+
+- Yes
+
+### 3.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 3.3.3 Registration
+
+The following information has to be registered in the network:
+
+- 1) the forwarded-to number, which may be accompanied by a forwarded-to sub-address;
+- 2) information as to whether all calls or all calls of one (or several) specific Basic service group(s) should be forwarded;
+
+If no Basic Service Code is inserted by the user this is interpreted as All Basic Services.
+
+- 3) the duration of the no reply condition timer.
+
+Registration can take place either by the service provider or with an appropriate control procedure by the subscriber. If the duration of the no reply condition timer is not registered by the mobile subscriber then the previous value set by the mobile subscriber applies. If no previous value exists, a default value set by the service provider applies. The value is in between 5 and 30 seconds, in steps of 5 seconds.
+
+Verification, where possible, of the forwarded-to number should be accomplished before accepting the call forwarding request. This verification is done by a simple check of the forwarded-to number to see if the number is within the allowed number range.
+
+When the mobile subscriber registers call forwarding on no reply, the network will return notification of acceptance or rejection of the request. This notification will include the forwarded-to number to which call forwarding on no reply is registered and the duration of the no reply condition timer.
+
+### 3.3.4 Erasure
+
+A previous registration can be erased in either of three ways:
+
+Firstly, the subscriber can specifically erase a previous registration with an appropriate control procedure.
+
+Secondly, the subscriber can register information for call forwarding on no reply for the specific Basic service group to another directory number, thus causing the previous registration of call forwarding on no reply to be overridden.
+
+Thirdly, all information is erased as a result of withdrawal of the service.
+
+### 3.3.5 Activation
+
+The user shall be allowed to activate Call Forwarding on No Reply (CFNRy) by e.g. using the MMI command described in 3GPP TS 22.030. This activation request may include information of which Basic Service Group(s) it shall apply to. If no such information is included, the Activation request applies to all Basic Service Groups.
+
+When receiving an activation request the network shall activate CFNRy for the Basic Service Groups comprised in the BS group information given by the user against which a CFNRy forwarded-to-number is registered. The Activation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+The user shall receive a notification that CFNRy has been activated.
+
+The supplementary service is also activated for a Basic service group as a result of Registration for that Basic service group.
+
+### 3.3.6 Deactivation
+
+An active CFNRy can be deactivated in either of two ways:
+
+- The user may deactivate CFNRy by means of an appropriate control procedure (e.g. as described in 3GPP TS 22.030). A deactivation request may contain information of which Basic Service Group(s) it shall apply to. If no such information is included the Deactivation request applies to all Basic Service Groups.
+
+When receiving a deactivation request the network shall deactivate CFNRy for the Basic Service Groups comprised in the BS group information given by the user against which a CFNRy forwarded-to-number is registered. However, the registered information shall not be erased. The Deactivation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+Even if there is no data stored against a particular Basic Service group comprised in a deactivation request, the request shall be accepted by the network for the other Basic Service groups included in the information given by the user.
+
+- The service is deactivated as a result of Erasure.
+
+In the former case, and also in the latter if Erasure is user controlled, the user shall receive a notification of whether her request was accepted or rejected in accordance with the rules set out in 3GPP TS 22.004.
+
+### 3.3.7 Invocation
+
+If the supplementary service is activated for a Basic service incoming calls for the specified Basic service that are not answered within the period defined by the no reply condition timer, will be forwarded by network invocation.
+
+### 3.3.8 Normal operation with successful outcome
+
+When call forwarding on no reply is active and operative, incoming calls for the specified Basic Service(s) that are not answered within the period defined by the no reply condition timer, will be forwarded without being offered to the served mobile subscriber.
+
+When an incoming call is forwarded on no reply the served mobile subscriber can, as a subscription option, receive notification (but will not be able to answer the incoming call).
+
+The forwarded-to subscriber will receive an indication that the call has been forwarded with the cause. The cause, when available, will be the appropriate forwarding condition. Depending on the value of the served subscribers subscription option, the forwarded-to subscriber may also receive the MSISDN of the served subscriber.
+
+When multiple forwarding occurs the reason for forwarding and the MSISDN given to the forwarded-to subscriber should relate to the last forwarding subscriber in the chain.
+
+When call forwarding on no reply is active and operative, the ability of the served mobile subscriber to originate calls is not affected. However, an indication that the call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made.
+
+As a subscription option, the served mobile subscriber can request that the calling subscriber receives a notification that the call has been forwarded.
+
+NOTE: In case the notification is implemented using intermediate tones or announcements, the tones and/or announcements to the calling party should not be provided if the information transfer capability is set to UDI.
+
+### 3.3.11 Interrogation
+
+#### Data request
+
+The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information:
+
+- in response to a general data request the served mobile subscriber should be given a list of all Basic service groups to which call forwarding on no reply is registered, including information whether it is active and if so, whether it is operative or quiescent, the associated forwarded-to numbers and the duration of the no reply timer;
+- in response to a specific request concerning one particular Basic service group, the served mobile subscriber should be informed whether or not call forwarding on no reply is registered, including information whether it is active and if so, whether it is operative or quiescent for that Basic service group. If CFNRy is registered, the associated forwarded-to number and the duration of the no reply timer shall be given.
+
+### 3.3.12 Charging requirements
+
+The forwarding subscriber may be charged for the forwarded part of the call.
+
+## 3.4 Exceptional procedures or unsuccessful outcome
+
+### 3.4.2 Registration
+
+If the system cannot accept a registration request, the served mobile subscriber should receive a notification that call forwarding on no reply registration was not successful. Possible causes are:
+
+- service not subscribed to;
+- forwarded-to number is invalid directory number;
+- use of an operator access prefix;
+- insufficient information;
+- forwarded-to number is a special service code (e.g. police);
+- forwarded-to number is the directory number of the mobile subscriber herself;
+- conflicting situation with other supplementary services (e.g. incoming call barring has been activated);
+- no basic service provisioned within the basic service group(s).
+
+The network is not required to validate information related to the forwarded-to number.
+
+### 3.4.3 Erasure
+
+If the network cannot accept a mobile subscriber's request for erasure, cause will be returned to the subscriber, such as:
+
+- insufficient information;
+- inconsistent with registration.
+
+If the subscriber does not completely specify which call forwarding on no reply request is to be erased, the network will reject the erasure request with appropriate cause.
+
+If no Basic Service Code is inserted by the user, CF will be erased from all Basic Services.
+
+### 3.4.4 Activation
+
+If there is no CFNRy forwarded-to-number registered against a Basic Service group, the activation request for that Basic Service group shall be denied. However, if there is CFNRy forwarded-to-numbers stored against other Basic Service groups contained in the same activation request, these will be activated.
+
+Examples of causes for a not accepted activation request:
+
+- service not provisioned;
+- conflicting situation with other supplementary services;
+- service not registered.
+
+### 3.4.5 Deactivation
+
+If the network cannot accept a deactivation request, an appropriate cause will be returned to the user, e.g. Service not Active.
+
+### 3.4.6 Invocation
+
+Within a PLMN or different PLMNs the number of tandem forwarding connections 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 is reached and an attempt is made to forward the call an additional time, then the forwarded call shall be treated as in the following paragraph.
+
+If the forwarded call cannot be completed to the forwarded-to destination, then the network will clear the call towards the calling user with an indication that the call cannot be completed. This indication shall not include information that the call has been forwarded.
+
+NOTE 1: The alerting of the forwarding user shall have ceased on invocation of the CFNRy Service.
+
+NOTE 2: The alerting of the calling subscriber should, if possible, not cease on invocation of CFNRy.
+
+NOTE 3: Call forwarding on no reply applies only to the Basic services subscribed to. Calls to a directory number requesting a Basic service which is not subscribed to will never be forwarded.
+
+## 3.5 Alternate procedures
+
+None identified.
+
+## 3.6 Interactions with other supplementary services
+
+### 3.6.81.1 Calling line identification presentation
+
+See 3GPP TS 22.081.
+
+### 3.6.81.2 Calling line identification restriction
+
+See 3GPP TS 22.081.
+
+#### 3.6.81.3 Connected line identification presentation
+
+See 3GPP TS 22.081.
+
+#### 3.6.81.4 Connected line identification restriction
+
+See 3GPP TS 22.081.
+
+#### 3.6.82.1 Call forwarding unconditional
+
+See section 1.6.82.3.
+
+#### 3.6.83.1 Call waiting
+
+See 3GPP TS 22.083.
+
+#### 3.6.84.1 Multi party
+
+See 3GPP TS 22.084.
+
+#### 3.6.85.1 Closed user group
+
+See 3GPP TS 22.085.
+
+#### 3.6.86.1 Advice of charge
+
+See 3GPP TS 22.086.
+
+#### 3.6.88.1 Barring of all outgoing calls
+
+Same as the interaction between call forwarding unconditional and barring of all outgoing calls.
+
+#### 3.6.88.2 Barring of outgoing international calls
+
+Same as the interaction between call forwarding on mobile subscriber busy and barring of outgoing international calls.
+
+#### 3.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country
+
+Same as the interaction between call forwarding on mobile subscriber busy and barring of outgoing international calls except those directed to the home PLMN country.
+
+#### 3.6.88.6 Barring of all incoming calls
+
+Same as the interaction between call forwarding unconditional and barring of all incoming calls.
+
+#### 3.6.88.7 Barring of incoming calls when roaming outside the home PLMN country
+
+Same as the interaction between call forwarding on mobile subscriber busy and barring of incoming calls when roaming outside the home PLMN country.
+
+#### 3.6.88.8 Anonymous Call Rejection
+
+See 3GPP TS 22.088 [9].
+
+## 3.7 Interworking considerations
+
+If the forwarded-to number is not a PLMN- or ISDN-number, then an interworking situation is said to exist.
+
+If a forwarded call 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.
+
+NOTE1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited.
+
+NOTE2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI.
+
+# --- 4 Call Forwarding on Mobile Subscriber Not Reachable
+
+## 4.1 Definition
+
+This service permits a called mobile subscriber to have the network send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber's directory number, but which is not reachable, to another directory number. The ability of the served mobile subscriber to originate calls is principally unaffected, but practically it is affected if the mobile subscriber is de-registered, if there is radio congestion or if the mobile subscriber for example is being out of radio coverage. If this service is activated, a call is forwarded only if the mobile subscriber is not reachable.
+
+## 4.2 Description
+
+### 4.2.1 Description
+
+The served mobile subscriber can request a different forwarded-to number for each Basic service group containing a basic service to which he has subscribed.
+
+### 4.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004.
+
+### 4.2.3 Terminology
+
+A served mobile subscriber is a mobile subscriber of a particular PLMN access who is requesting that calls to his number be forwarded. This subscriber may also be referred to as the forwarding subscriber or the called subscriber. A forwarded-to subscriber is a subscriber to whom the call shall be forwarded.
+
+## 4.3 Normal procedures with successful outcome
+
+### 4.3.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 service subscribed to. For each subscription option only one value can be selected.
+
+| <u>Subscription options</u>                                                     | <u>Value</u>  |
+|---------------------------------------------------------------------------------|---------------|
+| Calling subscriber receives notification that the call has been forwarded       | - No<br>- Yes |
+| MSISDN of the served subscriber can be presented to the forwarded-to subscriber | - No<br>- Yes |
+
+### 4.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 4.3.3 Registration
+
+The following information has to be registered in the network:
+
+- 1) the forwarded-to number, which may be accompanied by a forwarded-to sub-address;
+- 2) information as to whether all calls or all calls of one (or several) specific Basic service group(s) should be forwarded.
+
+If no Basic Service Code is inserted by the user this is interpreted as All Basic Services.
+
+Registration can take place either by the service provider or with an appropriate control procedure by the subscriber.
+
+Verification, where possible, of the forwarded-to number should be accomplished before accepting the call forwarding request. This verification is done by a simple check of the forwarded to number to see if the number is within the allowed number range.
+
+When the mobile subscriber registers call forwarding on mobile subscriber not reachable the network will return notification of acceptance or rejection of the request. This notification will include the forwarded-to number to which call forwarding on mobile subscriber not reachable is registered.
+
+### 4.3.4 Erasure
+
+A previous registration can be erased in either of three ways:
+
+Firstly, the subscriber can specifically erase a previous registration with an appropriate control procedure.
+
+Secondly, the subscriber can register information for call forwarding on mobile subscriber not reachable for the specific Basic service group to another directory number, thus causing the previous registration of call forwarding on mobile subscriber not reachable to be overridden.
+
+Thirdly, all information is erased as a result of withdrawal of the service.
+
+### 4.3.5 Activation
+
+The user shall be allowed to activate Call Forwarding on mobile not Reachable (CFNRc) by e.g. using the MMI command described in 3GPP TS 22.030. This activation request may include information of which Basic Service Group(s) it shall apply to. If no such information is included the Activation applies to all Basic Service Groups against which CFNRc data (forwarded-to-number) is registered.
+
+When receiving an activation request the network shall activate CFNRc for the Basic Service Groups comprised in the BS group information given by the user and against which a CFNRc forwarded-to-number is registered. The Activation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+The user shall receive a notification that CFNRc has been activated.
+
+The supplementary service is also activated for a Basic service group as a result of registration for that Basic service group.
+
+### 4.3.6 Deactivation
+
+An active CFNRc can be deactivated in either of two ways:
+
+- The user may deactivate CFNRc by means of an appropriate control procedure (e.g. as described in 3GPP TS 22.030). An explicit deactivation request may contain information of which Basic Service Group(s) it shall apply to. If no such information is included the Deactivation applies to all Basic Service Groups.
+
+When receiving a deactivation request the network shall deactivate CFNRc for the Basic Service Groups comprised in the BS group information given by the user and against which a CFNRc forwarded-to-number is registered. However, the registered information shall not be erased. The Deactivation(s) shall be in accordance with the rules set out in 3GPP TS 22.004.
+
+Even if there is no data stored against a particular Basic Service group comprised in deactivation request, the request shall be accepted by the network for the other Basic Service groups included in the information given by the user.
+
+- The service is deactivated as a result of Erasure.
+
+In the former case, and also in the latter if Erasure is user controlled, the user shall receive a notification of whether her request was accepted or rejected in accordance with the rules set out in 3GPP TS 22.004.
+
+### 4.3.7 Invocation
+
+If the supplementary service is activated for a Basic service incoming calls for the specified Basic service when the mobile subscriber is not reachable, will be forwarded by network invocation.
+
+### 4.3.8 Normal operation with successful outcome
+
+When call forwarding on mobile subscriber not reachable is active and operative, all incoming calls for the specified Basic Service(s) when the mobile subscriber is not reachable, will be forwarded without being offered to the served mobile subscriber.
+
+The forwarded-to subscriber will receive an indication that the call has been forwarded with the cause. The cause, when available, will be the appropriate forwarding condition. Depending on the value of the served subscribers subscription option, the forwarded-to subscriber may also receive the MSISDN of the served subscriber.
+
+When multiple forwarding occurs the reason for forwarding and the MSISDN given to the forwarded-to subscriber should relate to the last forwarding subscriber in the chain.
+
+When call forwarding on mobile subscriber not reachable is active and operative, the ability of the served mobile subscriber to originate calls is principally not affected, but practically it is affected if the mobile subscriber is de-registered, on radio congestion or on no paging response. However, an indication that the call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made.
+
+As a subscription option, the served mobile subscriber can request that the calling subscriber receives a notification that the call has been forwarded.
+
+NOTE: In case the notification is implemented using intermediate tones or announcements, the tones and/or announcements to the calling party should not be provided if the information transfer capability is set to UDI.
+
+### 4.3.11 Interrogation
+
+#### Data request
+
+The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information:
+
+- in response to a general data request the served mobile subscriber should be given a list of all Basic service groups to which call forwarding on mobile subscriber not reachable is registered, including information whether it is active and if so, whether it is operative or quiescent, and the associated forwarded-to numbers;
+- in response to a specific request concerning one particular Basic service group, the served mobile subscriber should be informed whether or not call forwarding on mobile subscriber not reachable is registered, including information whether it is active and if so, whether it is operative or quiescent for that Basic service group. If CFNRc is registered, the associated forwarded-to number shall be given.
+
+### 4.3.12 Charging requirements
+
+The forwarding subscriber may be charged for the forwarded part of the call.
+
+## 4.4 Exceptional procedures or unsuccessful outcome
+
+### 4.4.2 Registration
+
+If the system cannot accept a registration request, the served mobile subscriber should receive a notification that call forwarding on mobile subscriber not reachable registration was not successful. Possible causes are:
+
+- service not subscribed to;
+- forwarded-to number is invalid directory number;
+- use of an operator access prefix;
+- insufficient information;
+- forwarded-to number is a special service code (e.g. police);
+- forwarded-to number is the directory number of the mobile subscriber herself;
+- conflicting situation with other supplementary services (e.g. incoming call barring has been activated);
+- no basic service provisioned within the basic service group(s).
+
+The network is not required to validate information related to the forwarded-to number.
+
+### 4.4.3 Erasure
+
+If the network cannot accept a mobile subscriber's request for erasure, cause will be returned to the subscriber, such as:
+
+- insufficient information;
+- inconsistent with registration.
+
+If the subscriber does not completely specify which call forwarding on mobile subscriber not reachable request is to be erased, the network will reject the erasure request with appropriate cause.
+
+If no Basic Service Code is inserted by the user, CF will be erased from all Basic Services.
+
+### 4.4.4 Activation
+
+If there is no CFNRc forwarded-to-number registered against a Basic Service group, the activation request for that Basic Service group shall be denied.
+
+Examples of causes for a not accepted activation request:
+
+- service not provisioned;
+- conflicting situation with other supplementary services;
+- service not registered.
+
+### 4.4.5 Deactivation
+
+If the network cannot accept a deactivation request, an appropriate cause will be returned to the user, e.g. Service not Active.
+
+### 4.4.6 Invocation
+
+Within a PLMN or different PLMNs the number of tandem forwarding connections 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 forwarded call cannot be completed to the forwarded-to destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards.
+
+NOTE: Call forwarding on mobile subscriber not reachable applies only to the Basic services subscribed to. Calls to a directory number requesting a Basic service which is not subscribed to will never be forwarded.
+
+## 4.5 Alternate procedures
+
+None identified.
+
+## 4.6 Interactions with other supplementary services
+
+### 4.6.81.1 Calling line identification presentation
+
+See 3GPP TS 02.081.
+
+### 4.6.81.2 Calling line identification restriction
+
+See 3GPP TS 02.081.
+
+#### 4.6.81.3 Connected line identification presentation
+
+See 3GPP TS 02.081.
+
+#### 4.6.81.4 Connected line identification restriction
+
+See 3GPP TS 02.081.
+
+#### 4.6.82.1 Call forwarding unconditional
+
+See section 1.6.82.4.
+
+#### 4.6.83.1 Call waiting
+
+See 3GPP TS 22.083.
+
+#### **4.6.84.1 Multi party**
+
+See 3GPP TS 22.084.
+
+#### **4.6.85.1 Closed user group**
+
+See 3GPP TS 22.085.
+
+#### **4.6.86.1 Advice of charge**
+
+See 3GPP TS 22.086.
+
+#### **4.6.88.1 Barring of all outgoing calls**
+
+Same as the interaction between call forwarding unconditional and barring of all outgoing calls.
+
+#### **4.6.88.2 Barring of outgoing international calls**
+
+Same as the interaction between call forwarding on mobile subscriber busy and barring of outgoing international calls.
+
+#### **4.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country**
+
+Same as the interaction between call forwarding on mobile subscriber busy and barring of outgoing international calls except those directed to the home PLMN country.
+
+#### **4.6.88.6 Barring of all incoming calls**
+
+Same as the interaction between call forwarding unconditional and barring of all incoming calls.
+
+#### **4.6.88.7 Barring of incoming calls when roaming outside the home PLMN country**
+
+Same as the interaction between call forwarding on mobile subscriber busy and barring of incoming calls when roaming outside the home PLMN country.
+
+#### **4.6.88.8 Anonymous Call Rejection**
+
+See 3GPP TS 22.088 [9].
+
+## **4.7 Interworking considerations**
+
+If the forwarded-to number is not a PLMN- or ISDN-number, then an interworking situation is said to exist.
+
+If a forwarded call 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                |
+| Jun 1999       |           |           | 02.82  |          |     |        |     | Transferred to 3GPP SA1                      | 8.0.0  |        |                   |
+| SA#04          |           |           | 22.082 |          |     |        |     |                                              |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99629  | 22.082 | 001      |     | R99    | D   | Editorial changes for alignment              | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010052 | S1-010073 | 22.082 | 002      |     | Rel-4  | B   | Notification of active CFU                   | 3.0.1  | 4.0.0  | CPHS              |
+| SP-12          | SP-010259 | S1-010438 | 22.082 | 003      |     | Rel-4  | C   | Clarification of CPHS CFU Indication         | 4.0.0  | 4.1.0  | UICC1-CPHS        |
+| SP-15          | SP-020045 | S1-020457 | 22.082 | 004      | -   | Rel-4  | F   | Editorial CR to correct terms and references | 4.1.0  | 4.2.0  | CORRECT           |
+| SP-16          | SP-020267 | S1-021043 | 22.082 |          |     | Rel-5  |     | Updated from Rel-4 to Rel5                   | 4.2.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.082 |          |     | Rel-6  |     | Updated from Rel-5 to Rel-6                  | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.082 |          |     | 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-111407 | 22.082 | 000<br>5 | -   | Rel-11 | B   | Addition of Anonymous Call Rejection as a SS | 10.0.0 | 11.0.0 | ACR_CS            |
+| 2014-10        | -         | -         | -      | -        | -   | -      | -   | Update to Rel-12 version (MCC)               | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -      | -        | -   | -      | -   | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22083/raw.md

@@ -0,0 +1,525 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.083 V13.0.0 (2015-12) Call Waiting (CW) and Call Holding (HOLD); Supplementary Services, Stage 1 Technical Specification (Release 13)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above "ADVANCED" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, CW, supplementary service,  
+stage 1
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                  |    |
+|--------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                   | 5  |
+| 0 Scope.....                                                                                     | 6  |
+| 0.1 References .....                                                                             | 6  |
+| 0.2 Abbreviations .....                                                                          | 6  |
+| 1 Call Waiting (CW).....                                                                         | 6  |
+| 1.1 Definition .....                                                                             | 6  |
+| 1.2 Description .....                                                                            | 7  |
+| 1.2.1 Description .....                                                                          | 7  |
+| 1.2.2 Applicability to telecommunication services .....                                          | 7  |
+| 1.2.3 Terminology .....                                                                          | 7  |
+| 1.3 Normal procedures with successful outcome.....                                               | 7  |
+| 1.3.1 Provision.....                                                                             | 7  |
+| 1.3.2 Withdrawal .....                                                                           | 7  |
+| 1.3.5 Activation .....                                                                           | 7  |
+| 1.3.6 Deactivation.....                                                                          | 8  |
+| 1.3.7 Invocation .....                                                                           | 8  |
+| 1.3.8 Normal operation with successful outcome.....                                              | 8  |
+| 1.3.8.1 Incoming call from C .....                                                               | 8  |
+| 1.3.8.2 Terminating call by A or B .....                                                         | 8  |
+| 1.3.11 Interrogation .....                                                                       | 8  |
+| 1.4 Exceptional procedures or unsuccessful outcome.....                                          | 8  |
+| 1.4.1 Incoming call from subscriber C ignored by subscriber B.....                               | 8  |
+| 1.4.2 Incoming call from subscriber C is indicated as UDUB by subscriber B (or terminal B) ..... | 9  |
+| 1.4.3 Release by subscriber C within the specified period.....                                   | 9  |
+| 1.4.4 Incoming call from subscriber C is rejected by subscriber B.....                           | 9  |
+| 1.5 Alternate procedures .....                                                                   | 9  |
+| 1.6 Interactions with other Supplementary Services.....                                          | 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.83.2 Call hold.....                                                                          | 9  |
+| 1.6.81.1 Calling line identification presentation.....                                           | 9  |
+| 1.6.84.2 MultiParty .....                                                                        | 10 |
+| 1.6.88.6 Barring of all incoming calls .....                                                     | 10 |
+| 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country.....               | 10 |
+| 1.7 Interactions with other services.....                                                        | 10 |
+| 1.7.1 Multicall .....                                                                            | 10 |
+| 1.8 Interworking considerations.....                                                             | 10 |
+| 2 Call hold.....                                                                                 | 10 |
+| 2.1 Definition .....                                                                             | 10 |
+| 2.2 Description .....                                                                            | 10 |
+| 2.2.1 Description .....                                                                          | 10 |
+| 2.2.2 Applicability to telecommunication services .....                                          | 11 |
+| 2.3 Normal procedures with successful outcome.....                                               | 11 |
+| 2.3.1 Provision.....                                                                             | 11 |
+| 2.3.2 Withdrawal .....                                                                           | 11 |
+| 2.3.5 Activation .....                                                                           | 11 |
+| 2.3.6 Deactivation.....                                                                          | 11 |
+| 2.3.7 Invocation .....                                                                           | 11 |
+| 2.3.8 Normal operation with successful outcome.....                                              | 11 |
+| 2.4 Exceptional procedures or unsuccessful outcome.....                                          | 13 |
+| 2.4.1 Exceptional operation or unsuccessful outcome .....                                        | 13 |
+| 2.4.6 Invocation .....                                                                           | 13 |
+| 2.5 Alternate procedures .....                                                                   | 13 |
+| 2.6 Interactions with other Supplementary Services.....                                          | 13 |
+| 2.6.83.1 Call waiting.....                                                                       | 13 |
+| 2.6.84.2 MultiParty .....                                                                        | 13 |
+
+2.7 Interactions with other services.....13  
+2.7.1 Multicall .....13  
+2.8 Interworking considerations.....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.
+
+# --- 0 Scope
+
+The present document describes the Supplementary Services belonging to the group Call Completion Supplementary Services.
+
+The general aspects, including definitions and recommended provision, of the description of Supplementary Services are given in specification TS 22.004 [2].
+
+The group of Call Completion Supplementary Services is divided into the following two Supplementary Services:
+
+- Call waiting (clause 1);
+- Call hold (clause 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 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.081: "Line identification Supplementary Services - Stage 1".
+- [5] 3GPP TS 22.084: "Digital cellular telecommunication system; MultiParty (MPTY) Supplementary Services - Stage 1".
+- [6] 3GPP TS 22.135: "Multicall Stage 1".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in TR 21.905 [1].
+
+# --- 1 Call Waiting (CW)
+
+## 1.1 Definition
+
+The Call Waiting Service permits a mobile subscriber to be notified of an incoming call (as per basic call procedures) whilst the traffic channel is not available for the incoming call and the mobile subscriber is engaged in an active or held call. Subsequently, the subscriber can either accept, reject, or ignore the incoming call.
+
+## 1.2 Description
+
+### 1.2.1 Description
+
+This service operates when the traffic channel at the controlling subscriber B is not available and B is engaged in an active or held call.
+
+When a third party (calling subscriber C) attempts to connect to that termination, the controlling subscriber B is given an appropriate indication of the waiting call. A notification that the call is waiting will be sent back towards the calling subscriber C.
+
+The maximum number of waiting calls at one time per mobile access is one. This means that no further calls are offered to the subscriber while a call is waiting.
+
+NOTE: As a network option this maximum number of waiting calls may be greater than one. This is considered as a possible future enhancement.
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service to the ongoing call is defined in TS 22.004 [2]. The incoming, waiting, call may be of any kind.
+
+### 1.2.3 Terminology
+
+#### **(Controlling) subscriber B**
+
+This is the subscriber who is provided by the network with the Call Waiting Service and who reacts to the Call Waiting.
+
+#### **Subscriber C**
+
+This is the subscriber who has originated a call to B which causes the Call Waiting Service to be invoked.
+
+#### **Subscriber A**
+
+This represents a subscriber who is engaged in a call with B, being either the calling or the called party.
+
+##### **T2; No answer time out**
+
+The duration of this time out is the time the network will wait for a response from subscriber B, to the offered call from subscriber C. The value of the timer is between 0.5 and 2 minutes at the service providers discretion.
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.1 Provision
+
+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 BS.
+
+### 1.3.2 Withdrawal
+
+Withdrawal will be at the request of the subscriber or for administrative reasons.
+
+### 1.3.5 Activation
+
+This Supplementary Service will be activated either collectively for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as specified in TS 22.030 [3], or by the service provider. The controlling subscriber shall be informed by the network of the success or otherwise of her action.
+
+### 1.3.6 Deactivation
+
+The service will be deactivated either collectively for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as specified in TS 22.030 [3], or by the service provider. The controlling subscriber shall be informed by the network of the success or otherwise of her action.
+
+### 1.3.7 Invocation
+
+This service is invoked by the network on arrival of an incoming call if the service is active and the controlling subscriber B's traffic channel is not available, B is engaged in an active or held call and there is no other call currently waiting.
+
+### 1.3.8 Normal operation with successful outcome
+
+#### 1.3.8.1 Incoming call from C
+
+When an incoming call from subscriber C arrives, the served mobile subscriber is connected to - at least - one call (active or held) and a NDUB (Network Determined User Busy) condition does not exist, then the CW service shall be invoked and the call shall be offered to subscriber B with an appropriate indication, e.g. with a "Call Waiting Tone".
+
+If a response to the offered call is received from the mobile termination at B, then the subscriber C shall be given an indication (e.g. ringing tone) that the called subscriber is being informed of the incoming call and, if possible, that call waiting is in operation.
+
+#### 1.3.8.2 Terminating call by A or B
+
+If either subscriber A or subscriber B requests that the call is terminated, then this call shall be terminated as for basic call (see TS 22.030 [3] for more information). Subscriber B shall then be given the normal notification that there is a new call to her, as for a normal terminating call. The network shall continue to indicate; e.g. ringing tone towards subscriber C as for a normal call. B can then accept the call from C before the expiry of T2.
+
+Subscriber B can also free resources by using the Call Hold Supplementary Service. Subscriber B shall then be able to accept the waiting call from subscriber C before the expiry of T2.
+
+Alternatively, subscriber B may specifically request release or hold of the connection to A and accept the waiting call as one action (see TS 22.030 [3]). In this case, the network connects subscriber B to subscriber C with no further notifications to either subscriber. This must be done before the expiry of T2.
+
+### 1.3.11 Interrogation
+
+#### Status check
+
+The controlling subscriber may interrogate the network by the use of a control procedure, as specified in TS 22.030 [3]. The network shall respond with an appropriate indication telling the subscriber whether the service is supported in this network and, if so, provide a list of all Basic Service groups to which the Call waiting Supplementary Service is active.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+### 1.4.1 Incoming call from subscriber C ignored by subscriber B
+
+If no response is received by the network from controlling subscriber B before the expiry of T2, then the network shall inform the controlling subscriber B that the call is no longer waiting. Subscriber C shall then be given a no reply indication, unless e.g. Call Forwarding applies. The call waiting service is then made available for a subsequent incoming call.
+
+### 1.4.2 Incoming call from subscriber C is indicated as UDUB by subscriber B (or terminal B)
+
+If the waiting call is indicated as UDUB by B before the expiry of T2 the subscriber C shall be given a busy indication, unless e.g. Call Forwarding applies. The call waiting service is then made available for a subsequent incoming call.
+
+### 1.4.3 Release by subscriber C within the specified period
+
+If calling subscriber C terminates the call attempt to subscriber B before the expiry of T2, the call attempt from C shall be terminated, as for basic call, and subscriber B shall be notified.
+
+### 1.4.4 Incoming call from subscriber C is rejected by subscriber B
+
+If the waiting call is explicitly rejected by B before the expiry of T2, the subscriber C shall be given a reject indication. The call waiting service is then made available for a subsequent incoming call.
+
+## 1.5 Alternate procedures
+
+None identified.
+
+## 1.6 Interactions with other Supplementary Services
+
+#### 1.6.82.1 Call forwarding unconditional
+
+If call forwarding unconditional has been activated, it takes precedence over call waiting. Call forwarding unconditional can be activated while a call is waiting without changing the state of the waiting call.
+
+#### 1.6.82.2 Call forwarding on mobile subscriber busy
+
+No impact, i.e. neither Supplementary Service shall affect the operation of the other Supplementary Service.
+
+The following text clarifies the situation: If user B is NDUB (Network Determined User Busy), Call Forwarding shall take place, and the call is not offered to B. If B is not NDUB, the call shall be offered to B, and if the UDUB (User DUB) condition occurs, then the Call Forwarding shall take place.
+
+#### 1.6.82.3 Call forwarding on no reply
+
+If the CFNRy is active and operative for the called subscriber then a waiting call shall still be offered as described in subclause 1.3.8.1 (call waiting indication). If no response is received to this call before the expiry of the No Reply Condition timer, then the call forwarding on no reply service becomes invoked and the call is forwarded as per that call forwarding on no reply service description.
+
+#### 1.6.83.2 Call hold
+
+The served user may use the Call Hold service to answer subsequently a waiting call from C.
+
+If the served mobile subscriber has an active call and a call on hold the network can still offer an incoming call with the waiting indication i.e. the NDUB condition is not used the normal way (n=2 not 1).
+
+NOTE: Although the call is offered to the subscriber, she cannot accept the call as long as she has one active call and one call on hold.
+
+If the served mobile subscriber has a call on hold and no active call, an incoming call is offered as a waiting call.
+
+#### 1.6.81.1 Calling line identification presentation
+
+See TS 22.081 [4]
+
+#### 1.6.84.2 MultiParty
+
+See TS 22.084 [5] .
+
+#### 1.6.88.6 Barring of all incoming calls
+
+Invocation of Barring of Incoming Calls takes precedence over invocation of Call Waiting.
+
+Call waiting cannot be activated if barring of incoming calls is activated. The mobile subscriber requesting for call waiting shall be informed of this Supplementary Service incompatibility. The activation of barring of incoming calls does not affect any currently waiting calls.
+
+#### 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country
+
+When active and operative, same as interaction with Barring of All Incoming Calls.
+
+## 1.7 Interactions with other services
+
+### 1.7.1 Multicall
+
+See TS 22.135 [6].
+
+## 1.8 Interworking considerations
+
+Calls originating from outside the ISDN/PLMN can undergo call waiting at B.
+
+A special in-band indication may be provided to the calling subscriber instead of the normal indication.
+
+# --- 2 Call hold
+
+## 2.1 Definition
+
+The call hold service allows a served mobile subscriber, who is provisioned with this Supplementary Service, to interrupt communication on an existing active call and then subsequently, if desired, re-establish communication. The traffic channel remains assigned to the mobile subscriber after the communication is interrupted to allow the origination or possible termination of other calls.
+
+## 2.2 Description
+
+### 2.2.1 Description
+
+When the call hold service is invoked, communication is interrupted on the traffic channel and the traffic channel is released from the existing call. The traffic channel is reserved for the served mobile subscriber invoking the call hold service. The served mobile subscriber can only have one call on hold at a time.
+
+One traffic channel should be reserved for the served mobile subscriber as long as the subscriber has one call on hold and is currently not connected to any other call, i.e. the network should not reserve more than one traffic channel for a mobile station.
+
+If the served mobile subscriber has a call on hold and is not connected to an active call, she can:
+
+- 1) Retrieve the held call.
+- 2) Set up another call.
+- 3) Disconnect the held call.
+
+If the served mobile subscriber has a call on hold and is not connected to an active call she can not receive a call, except when using the Call Waiting Supplementary Service. For additional information, see subclause 2.6.83.1 (Interaction with Call Waiting Supplementary Service).
+
+If the served mobile subscriber is connected to an active call and has another call on hold, she can:
+
+- 1) Alternate from one call to the other.
+- 2) Disconnect the active call.
+- 3) Disconnect the held call.
+- 4) Disconnect both calls.
+
+If the served mobile subscriber is connected to an active call and has another call on hold, she can not receive a call. For additional information, see subclause 2.6.83.1 (Interaction with Call Waiting Supplementary Service).
+
+### 2.2.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in TS 22.004 [2].
+
+NOTE: If the served mobile subscriber has a call on hold she may set up another call using a different telecommunications service.
+
+## 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 to any subset of these BS.
+
+### 2.3.2 Withdrawal
+
+The service will be withdrawn at the subscriber's request or for administrative reasons.
+
+### 2.3.5 Activation
+
+The Supplementary Service will be activated by the service provider as a result of provision.
+
+### 2.3.6 Deactivation
+
+The Supplementary Service will be deactivated by the service provider as a result of withdrawal.
+
+### 2.3.7 Invocation
+
+Call hold will be invoked by the served mobile subscriber by use of a control procedure as described in TS 22.030 [3].
+
+### 2.3.8 Normal operation with successful outcome
+
+#### Hold request
+
+The served mobile subscriber indicates to the network that communication on the interface is to be interrupted. A call may be placed on hold:
+
+- on the served calling subscriber's interface by her at any time after the call has been answered and before call clearing has begun.
+- on the served called subscriber's interface by her at any time after the call has been answered and before call clearing has begun.
+
+The communication on the connection is then interrupted An acknowledgement shall be given to the served mobile subscriber, and the traffic channel is now available for other uses. A notification shall be sent towards the held party indicating that the call has been placed on hold.
+
+#### Disconnect
+
+If at any time a call is in the held state, either party may disconnect from that call.
+
+#### Unidirectionality
+
+Assume that subscriber A and B are connected to a call and both have subscribed to the call hold services. The call hold service is unidirectional, so it is possible for:
+
+- 1) only party A to have party B on hold;
+
+For party A the call is on hold, for the held party B the call is active.
+
+- 2) only party B to have party A on hold;
+
+For party B the call is on hold, for the held party A the call is active; or
+
+- 3) each party to have the other on hold.
+
+For party A and party B the call is on hold.
+
+#### Handling of call hold service within a call
+
+The served mobile subscriber may control the call hold service by use of the control procedures as described in TS 22.030 [3].
+
+If the served mobile subscriber has a call on hold and is not connected to an active call, she can:
+
+- 1) Retrieve the held call.
+
+A notification shall be send towards the previously held party that the call has been retrieved.
+
+- 2) Set up another call.
+
+Results in the served mobile subscriber being engaged in that new call and still holding the other call.
+
+- 3) Disconnect the held call (as for basic call).
+
+If the served mobile subscriber is connected to an active call and has another call on hold, she can:
+
+- 1) Alternate from one call to the other.
+
+Results in the previously active call being held and the previously held call becoming active. Privacy is provided between the two calls. A notification shall be sent towards the previously held party that the call has been retrieved and another notification shall be sent towards the party being put on hold.
+
+- 2) Disconnect the active call.
+
+Results in the traffic channel being available for the served mobile subscriber and the other call being still on hold. The served mobile subscriber shall be notified that she has a call on hold. The disconnected party shall be notified as for a basic call.
+
+NOTE: The notification about the held call towards the served mobile subscriber is given by the MS, not by the network.
+
+- 3) Disconnect the held call.
+
+The disconnected party shall be notified as for a basic call.
+
+- 4) Disconnect both calls (as for basic call).
+
+If the served mobile subscriber is connected to an active call and has another call on hold, and the active call is disconnected by the other party; then the served mobile subscriber shall be notified that she has a call on hold.
+
+NOTE: The notification about the held call towards the served mobile subscriber is given by the MS, not by the network.
+
+## 2.4 Exceptional procedures or unsuccessful outcome
+
+### 2.4.1 Exceptional operation or unsuccessful outcome
+
+If the network cannot retrieve a previously held call, the mobile subscriber will be informed of the reason of the failure. (For example, the call may be in the process of being cleared). The call state is not affected.
+
+If the network cannot alternate between two calls, the mobile subscriber will be informed of the reason for the failure. The call states are not affected.
+
+### 2.4.6 Invocation
+
+#### Hold
+
+If a mobile subscriber tries to invoke the hold service while not subscribed to the service or for some other reason, the service provider cannot provide the hold service, an indication will be provided to the mobile subscriber with the reason of failure. The call state is not affected.
+
+## 2.5 Alternate procedures
+
+None identified.
+
+## 2.6 Interactions with other Supplementary Services
+
+#### 2.6.83.1 Call waiting
+
+See subclause 1.6.83.2.
+
+#### 2.6.84.2 MultiParty
+
+See TS 22.084 [5]
+
+## 2.7 Interactions with other services
+
+### 2.7.1 Multicall
+
+See TS 22.135 [6].
+
+## 2.8 Interworking considerations
+
+The operation of this Supplementary Service is not affected by the nature of the far end of the connection.
+
+NOTE: In some networks the indication to the distant user about the held or retrieve state of the call may not be supported.
+
+# 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.83 |     |     |       |     | Transferred to 3GPP SA1                      | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.083    |     |     | R99   |     | Transferred to 3GPP SA1                      |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99630  | 22.083    | 001 |     | R99   | D   | Editorial changes for alignment              | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-05          | SP-99449  | S1-99854  | 22.083    | 002 |     | R99   | B   | Multicall                                    | 3.0.0  | 3.1.0  | Multicall         |
+| SP-11          | SP-010065 | S1-010258 | 22.083    |     |     | Rel-4 |     | Transferred to 3GPP Release 4                | 3.1.0  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.083    | 003 | -   | Rel-4 | F   | Editorial CR to correct terms and references | 4.0.0  | 4.1.0  | CORRECT           |
+| SP-16          | SP-020267 | S1-021043 | 22.083    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                   | 4.1.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.083    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                  | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.083    |     |     | 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)               | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22084/raw.md

@@ -0,0 +1,453 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **3GPP TS 22.084 (2016-12)** **MultiParty (MPTY) supplementary service; Stage 1** *Technical Specification* **(Release 13)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a trademark symbol (TM). Above the "e" is the word "ADVANCED" in a smaller, uppercase font. To the left of the text is a red signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized, bold font. The "3" is black, and the "G" and "P" are black with a red signal icon (three curved lines) integrated into the bottom of the "P". A trademark symbol (TM) is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, MPTY,  
+supplementary service, stage 1
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                       |    |
+|-------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                        | 4  |
+| 0 Scope.....                                                                                          | 5  |
+| 0.1 References .....                                                                                  | 5  |
+| 0.2 Abbreviations .....                                                                               | 5  |
+| 1 MultiParty Service (MPTY).....                                                                      | 5  |
+| 1.1 Definition .....                                                                                  | 5  |
+| 1.2 Description .....                                                                                 | 5  |
+| 1.2.1 Description .....                                                                               | 5  |
+| 1.2.1.1 Indication about multiParty status .....                                                      | 6  |
+| 1.2.2 Applicability to telecommunication services .....                                               | 6  |
+| 1.2.3 Terminology .....                                                                               | 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.....                                                   | 7  |
+| 1.3.8.1 Beginning the multiParty call .....                                                           | 7  |
+| 1.3.8.2 Managing an active multiParty call .....                                                      | 7  |
+| 1.3.8.3 Managing a held multiParty call.....                                                          | 8  |
+| 1.3.8.4 Managing a single call and a MPTY .....                                                       | 8  |
+| 1.3.8.4.1 Single active call .....                                                                    | 8  |
+| 1.3.8.4.2 Active MPTY and held call.....                                                              | 8  |
+| 1.3.8.5 Remote parties in a Multi-Party Call .....                                                    | 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.3 Connected line identification presentation .....                                             | 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 .....                                                            | 10 |
+| 1.6.82.4 Call Forwarding on mobile subscriber not reachable .....                                     | 10 |
+| 1.6.83.1 Call waiting.....                                                                            | 10 |
+| 1.6.83.2 Call hold.....                                                                               | 10 |
+| 1.6.84.1 Multi-party service.....                                                                     | 10 |
+| 1.6.85.1 Closed user group .....                                                                      | 10 |
+| 1.6.88.1 Barring of all outgoing calls .....                                                          | 10 |
+| 1.6.88.2 Barring of outgoing international calls .....                                                | 10 |
+| 1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country ..... | 11 |
+| 1.6.88.6 Barring of incoming calls .....                                                              | 11 |
+| 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country.....                    | 11 |
+| 1.7 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.
+
+# --- 0 Scope
+
+The present document describes the Supplementary Services belonging to the group MultiParty Supplementary Services.
+
+The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004.
+
+The group of Supplementary Services MultiParty Supplementary Services consists of one Supplementary Service:
+
+- MultiParty service (Clause 1).
+
+## 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.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [4] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1".
+- [5] 3GPP TS 22.085 "Closed User Group (CUG) Supplementary Services - Stage 1".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in TS 21.905.
+
+# --- 1 MultiParty Service (MPTY)
+
+## 1.1 Definition
+
+This Supplementary Service provides a mobile subscriber with the ability to have a multi-connection call, i.e. a simultaneous communication with more than one party.
+
+## 1.2 Description
+
+### 1.2.1 Description
+
+A precondition for the multi-party service is that the served mobile subscriber is in control of one active call and one call on hold, both calls having been answered. In this situation the served mobile subscriber can request the network to begin the multiParty service.
+
+Once a multiParty call is active, remote parties may be added, disconnected or separated (i.e. removed from the multiParty call but remain connected to the served mobile subscriber).
+
+The maximum number of remote parties is 5.
+
+#### 1.2.1.1 Indication about multiParty status
+
+Notification shall be sent towards the served mobile subscriber and all the remote parties in a multiParty call at the invocation of this Supplementary Service. In addition, a notification shall always be sent towards all remote parties (i.e. not towards the served mobile subscriber) every time a new party is added to the multiParty call. Notifications shall also be sent to remote parties when they are put on hold and when they are retrieved in accordance with normal Call Hold procedures.
+
+In the case where a previously private communication is added again to the multiParty call, a notification shall be sent towards all remote parties.
+
+NOTE: During an interim period of time, some networks might not support the sending of the notifications to the remote parties.
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in TS 22.004.
+
+### 1.2.3 Terminology
+
+#### **Served Mobile Subscriber**
+
+During the invocation and active phase, the service is under the control of the served mobile subscriber, i.e. the one who has subscribed to the service.
+
+#### **Remote Party**
+
+Any participant in the multiParty call who is not the served mobile subscriber.
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.1 Provision
+
+This Supplementary Service is provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not to any subset of these BS.
+
+The provision of the Call Hold Supplementary Service is also required.
+
+### 1.3.2 Withdrawal
+
+Withdrawal of the service is made by the service provider upon request by the subscriber or for service provider reasons.
+
+### 1.3.5 Activation
+
+The Supplementary Service shall be activated by the service provider as a result of provision.
+
+### 1.3.6 Deactivation
+
+The Supplementary Service shall be deactivated by the service provider as a result of withdrawal.
+
+### 1.3.7 Invocation
+
+Multi-Party service will be invoked by the served mobile subscriber by use of a control procedure, as defined in TS 22.030.
+
+### 1.3.8 Normal operation with successful outcome
+
+Only the served mobile subscriber shall be able to add remote parties to the multiParty call.
+
+#### 1.3.8.1 Beginning the multiParty call
+
+When the served mobile subscriber invokes multiParty service from the precondition defined in Section 1.2.1, the network joins the active call and the call on hold together into a multiParty call in which the served mobile subscriber and the remote parties can all communicate with one another.
+
+#### 1.3.8.2 Managing an active multiParty call
+
+During an active multiParty call, the served mobile subscriber shall be able to:
+
+- (i) Add another remote party, to which a private communication has been established using the same procedures as in Section 1.3.8.1, if the number of remote parties does not then exceed the maximum number allowed, which results in an active multiParty call.  
+  
+A "MPTY invoke" notification shall be sent towards all remote parties.  
+  
+A Retrieve notification (according to TS 22.083) shall be sent towards all previously held remote parties.
+- (ii) Put the connection to multiParty call on hold, i.e. place her connection to the multiParty call on hold (and typically later retrieve it). The served mobile subscriber may make an enquiry call (e.g. to a potential new remote party) or process a Call Waiting request from this state. While the multiParty call is on hold the remaining remote parties in the multiParty call can have communication with each other.
+
+As a result of this scenario, the enquiry call or the accepted waiting call can be added to the multiParty call or released. If the call is released by the served mobile subscriber or by the remote party, the served mobile subscriber is in control of a held multiParty call.
+
+A Hold notification (according to TS 22.083) shall be sent towards all remote parties.
+
+- (iii) Separate a remote party:
+
+Explicitly choose one remote party to have a private communication with. This results in that remote party being removed from the multiParty call which is placed on hold, and the conversation between the served mobile subscriber and the designated remote party being a normal active call (see NOTE 1). The remaining remote parties may have communication with each other in this state.
+
+As a result of this scenario the private communication can be added again to the multiParty call or released. If the private call is released by the served mobile subscriber or by the remote party, the served mobile subscriber is in control of a held multiParty call.
+
+A Hold notification (according to TS 22.083) shall be sent towards all remote parties, except the designated remote party to which a private communication was established.
+
+- (iv) Terminate the entire multiParty call. When the served mobile subscriber releases, this is interpreted as a request for termination of the entire multiParty call even if there are calls on hold.
+
+No further notification shall be sent.
+
+- (v) Disconnect a remote party:
+
+Explicitly release the remote parties one at a time basis (see NOTE 1). In the case when no remote parties remain, the multiParty call is terminated.
+
+NOTE 1: If the served mobile subscriber has a private communication with one of the remote parties and this remote party disconnects or is disconnected a notification is sent towards the served mobile subscriber that she has a multiParty call on hold.
+
+The notification about the held multiparty call towards the served mobile subscriber is given by the MS, not by the network.
+
+#### 1.3.8.3 Managing a held multiParty call
+
+During a held multiParty call the served mobile subscriber shall be able to:
+
+- 1) Retrieve the held multiParty call, which results in an active multiParty call.
+
+- 2) Initiate a new call.
+- 3) Process a Call Waiting request.
+- 4) Disconnect the held multiParty call. All calls belonging to the multiParty call shall be released.
+- 5) Disconnect a single remote party.
+
+During a held multiParty call the served mobile subscriber shall NOT be able to:
+
+Retrieve a single remote party.
+
+#### 1.3.8.4 Managing a single call and a MPTY
+
+##### 1.3.8.4.1 Single active call
+
+If the served mobile subscriber is connected to a single active call (regardless whether it is a private communication or a new initiated call) and has a MPTY on hold, she is able to:
+
+- 1) Disconnect the single active call.
+- 2) Disconnect the held MPTY.
+- 3) Disconnect both. All calls, even if they are on hold, shall be released.
+- 4) Join the single active call and the held MPTY together.  
+This would result in an active MPTY, except if the number of remote parties exceeds the number allowed.  
+  
+A "MPTY invoke" notification shall be sent towards all remote parties.  
+  
+A Retrieve notification (according to TS 22.083) shall be sent towards the previously held remote party.
+- 5) Alternate between both calls.
+
+##### 1.3.8.4.2 Active MPTY and held call
+
+If the served mobile subscriber is connected to a active MPTY and has a single call on hold, she is able to:
+
+- 1) Disconnect the active MPTY.
+- 2) Disconnect the single held call.
+- 3) Disconnect both. All calls, even if they are on hold, shall be released.
+- 4) Join the single held call and the active MPTY together. This would result in an active MPTY, except if the number of remote parties exceeds the number allowed.  
+  
+A "MPTY invoke" notification shall be sent towards all remote parties.  
+  
+A Retrieve notification (according to TS 22.083) shall be sent towards all previously held remote parties.
+- 5) Alternate between both calls.
+
+If the served mobile subscriber is connected to a active Multi Party call and has a single call on hold, a request for establishing a private communication will be rejected by the network. (Because this would lead to an active call and two calls on hold, which is not supported according to the Call Hold Supplementary Service).
+
+An indication will be given to the served mobile subscriber with the reason for failure.
+
+#### 1.3.8.5 Remote parties in a Multi-Party Call
+
+Any of the remote parties shall be able to:
+
+- a) Put her connection to the multiParty call on hold (and typically later retrieve it). The requirements of the Call Hold service then apply;
+
+- b) Release from the multiParty call.
+
+If a remote party releases and no remote party then remains, the requirements of the normal call release procedures then apply.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+If a served mobile subscriber attempts to invoke multiParty service and the network cannot accept that request, the request will be rejected and an indication will be given to the served mobile subscriber with a reason for denial. Some possible reasons for rejection are:
+
+- service not subscribed;
+- resources cannot be allocated;
+- conflicting situation with other Supplementary Services;
+- calls are not in appropriate state (e.g. one or more calls are not answered or are in the process of being cleared);
+- service not supported by the LPLMN.
+
+If the service provider cannot satisfy the request to add a further remote party (e.g. if the multiParty call has been cleared or if the maximum number of remote parties allowed has already been reached) the served mobile subscriber shall receive an indication that the request is denied, with the reason for failure.
+
+If the radio path of the served mobile subscriber is lost permanently for any reason, the multiParty call shall be released.
+
+## 1.5 Alternate procedures
+
+None identified.
+
+## 1.6 Interactions with other Supplementary Services
+
+#### 1.6.81.3 Connected line identification presentation
+
+Remote parties in an existing multiParty call who have subscribed to connected line number identification presentation will not receive a new remote party's number whenever a served mobile subscriber adds a new remote party to the multiParty call.
+
+#### 1.6.82.1 Call forwarding unconditional
+
+No interaction, the following text shall give a clarification.
+
+Calling subscriber: If a calling subscriber attempts to establish a multiParty call to a subscriber with call forwarding unconditional active and operative, the forwarded-to subscriber will be alerted and can be added to the conference.
+
+Forwarded-to subscriber: A forwarded-to subscriber can establish a multiParty call using an existing forwarded call as one of the multiParty connections.
+
+#### 1.6.82.2 Call forwarding on mobile subscriber Busy
+
+No interaction, the following text shall give a clarification.
+
+Calling subscriber: If a calling subscriber attempts to establish a multiParty call to a subscriber with call forwarding on mobile subscriber busy active and operative, and the forwarding condition is met, the forwarded-to subscriber will be alerted and can be added to the conference.
+
+Forwarded-to subscriber: A forwarded-to subscriber can establish a multiParty call using an existing forwarded call as one of the multiParty connections.
+
+#### 1.6.82.3 Call forwarding on no reply
+
+Same as the interaction between call forwarding on mobile subscriber busy and multiParty call.
+
+#### **1.6.82.4 Call Forwarding on mobile subscriber not reachable**
+
+Same as the interaction between call forwarding on mobile subscriber busy and multiParty call.
+
+#### **1.6.83.1 Call waiting**
+
+No interaction. The following text is included for clarification:
+
+A user who is active on a multiParty call, either as the served mobile subscriber or as remote party, may receive an indication of a waiting call, provided that the maximum number of calls at the mobile equipment will not be exceeded.
+
+After the multiParty call has been put on hold by this user, the waiting call may be accepted by the user.
+
+#### **1.6.83.2 Call hold**
+
+Any party involved in an active multiParty call (i.e. the served mobile subscriber or a remote party) may place the connection to the multiParty call on hold and later retrieve it.
+
+#### **1.6.84.1 Multi-party service**
+
+It shall be possible for any remote party in a multiParty call to alternate between two different multiParty calls.
+
+Served Mobile Subscriber:
+
+The served mobile subscriber cannot control more than one multiParty call at a time.
+
+It shall not be possible to invoke multiParty service if either or both of the initial calls are active parts of one or two other multiParty calls.
+
+Multi-Party Call controlled by one of the remote parties:
+
+The network will not be required to prevent that a leg to one of the other remote parties can be part of another multiParty call controlled by that remote party.
+
+#### **1.6.85.1 Closed user group**
+
+See TS 22.085.
+
+#### **1.6.88.1 Barring of all outgoing calls**
+
+If barring of all outgoing calls is activated after a multiParty call is invoked, any outgoing calls in progress within that multiParty call will not be barred. Any new outgoing call is barred.
+
+#### **1.6.88.2 Barring of outgoing international calls**
+
+Same as interworking between barring of all outgoing calls and multiParty service.
+
+#### **1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country**
+
+Same as interaction between barring of all outgoing calls and multiParty service.
+
+#### **1.6.88.6 Barring of incoming calls**
+
+If barring of incoming calls is activated after a multiParty call is invoked, any incoming calls in progress within that multiParty call will not be barred. Any new incoming call is barred.
+
+#### **1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country**
+
+If barring of incoming calls when roaming outside the home PLMN country is made active and operative after a multiParty call is invoked, any incoming calls in progress within that multiParty call will not be barred. Any new incoming call is barred.
+
+## 1.7 Interworking considerations
+
+Interworking with non-PLMN/ISDN:
+
+If a remote party is neither a PLMN nor an ISDN subscriber, it is possible that she is not notified.
+
+Mapping of notifications:
+
+Direction ISDN to PLMN:
+
+3PTY and CONF shall be mapped onto MPTY.
+
+Direction PLMN to ISDN:
+
+MPTY shall be mapped onto CONF.
+
+# 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.84 |     |     |       |     | Transferred to 3GPP SA1                      | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.084    |     |     | R99   |     | Transferred to 3GPP SA1                      |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99631  | 22.084    | 001 |     | R99   | D   | Editorial changes for alignment              | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.084    |     |     | Rel-4 |     | Transferred to 3GPP Release 4                | 3.0.1  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.084    | 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.084    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                   | 4.1.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.084    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                  | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.084    |     |     | 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)               | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22085/raw.md

@@ -0,0 +1,538 @@
+
+
+# **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **3GPP TS 22.085 (2016-12)** **Closed User Group (CUG) supplementary services; Stage 1** *Technical Specification* **(Release 13)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a red signal icon above the "l". The word "ADVANCED" is written in a smaller, uppercase font to the right of the "e". A trademark symbol (TM) is located at the bottom right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top, and the "P" has a red signal icon below it. A trademark symbol (TM) is located at the bottom right of the "P". Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, uppercase font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, CUG, supplementary service,  
+stage 1
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                        |           |
+|--------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                         | 4         |
+| 0 Scope.....                                                                                           | 5         |
+| 0.1 References .....                                                                                   | 5         |
+| 0.2 Abbreviations .....                                                                                | 5         |
+| 1 Closed User Group (CUG).....                                                                         | 5         |
+| 1.1 Definition .....                                                                                   | 5         |
+| 1.2 Description .....                                                                                  | 6         |
+| 1.2.1 Service description .....                                                                        | 6         |
+| 1.2.2 Applicability to telecommunication services .....                                                | 6         |
+| 1.2.3 Definitions .....                                                                                | 6         |
+| 1.3 Normal procedures with successful outcome.....                                                     | 6         |
+| 1.3.1 Provision.....                                                                                   | 6         |
+| 1.3.2 Withdrawal .....                                                                                 | 7         |
+| 1.3.5 Activation .....                                                                                 | 7         |
+| 1.3.6 Deactivation.....                                                                                | 7         |
+| 1.3.7 Invocation .....                                                                                 | 7         |
+| 1.3.8 Normal operation with successful outcome.....                                                    | 7         |
+| 1.3.8.1 Mobile originating calls .....                                                                 | 8         |
+| 1.3.8.1.1 A user with no preferential CUG and no OA capability .....                                   | 8         |
+| 1.3.8.1.2 A user with a preferential CUG but no OA capability.....                                     | 8         |
+| 1.3.8.1.3 A user with the OA capability but no preferential CUG.....                                   | 8         |
+| 1.3.8.1.4 A user with a preferential CUG and the OA capability .....                                   | 8         |
+| 1.3.8.1.5 A user not subscribing to the CUG Supplementary Service .....                                | 9         |
+| 1.3.8.2 Mobile terminating calls .....                                                                 | 9         |
+| 1.3.8.2.1 CUG call with no OA indication.....                                                          | 9         |
+| 1.3.8.2.2 CUG call with OA indication.....                                                             | 9         |
+| 1.3.8.2.3 Normal call.....                                                                             | 9         |
+| 1.4 Exceptional procedures or unsuccessful outcome.....                                                | 9         |
+| 1.4.1 Exceptional operation or unsuccessful outcome .....                                              | 9         |
+| 1.4.10 Roaming into networks not supporting CUG .....                                                  | 9         |
+| 1.5 Alternate procedures .....                                                                         | 10        |
+| 1.6 Interactions with other Supplementary Services.....                                                | 10        |
+| 1.6.82.1 Call forwarding unconditional .....                                                           | 10        |
+| 1.6.82.2 Call forwarding on mobile subscriber busy .....                                               | 11        |
+| 1.6.82.3 Call forwarding on no reply.....                                                              | 11        |
+| 1.6.82.4 Call forwarding on mobile subscriber not reachable .....                                      | 11        |
+| 1.6.83.1 Call waiting.....                                                                             | 11        |
+| 1.6.84.1 Multi-party service.....                                                                      | 11        |
+| 1.6.88 Call restriction Supplementary Services .....                                                   | 11        |
+| 1.7 Interworking considerations.....                                                                   | 11        |
+| <b>Annex 1 (normative): General subscription options (Per Subscriber) .....</b>                        | <b>13</b> |
+| <b>Annex 2 (normative): Originating PLMN actions on call requests on the calling user's side .....</b> | <b>14</b> |
+| <b>Annex 3 (normative): Terminating PLMN actions.....</b>                                              | <b>15</b> |
+| <b>Annex 4 (normative): CUG interaction with the call forwarding Supplementary Services ..</b>         | <b>16</b> |
+| <b>Annex 5 (informative): Change history.....</b>                                                      | <b>17</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 0 Scope
+
+The present document describes the Supplementary Services belonging to the group Community Of Interest Supplementary Services.
+
+The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004.
+
+The group of Community Of Interest Supplementary Services includes one Supplementary Service:
+
+- Closed user group (clause 1).
+
+## 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 23.003: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification".
+- [4] ITU-T Recommendation X.121: "International numbering plan for public data networks".
+- [5] ITU-T Recommendation X.180: "Administrative arrangements for closed user groups (CUGs)".
+- [6] 3GPP TS 22.088: "Call Barring (CB) supplementary services – Stage 1".
+
+## 0.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TS 21.905 [1].
+
+# --- 1 Closed User Group (CUG)
+
+## 1.1 Definition
+
+The Closed User Group (CUG) Supplementary Service enables subscribers, connected to a PLMN and possibly also other networks, to form closed user groups (CUGs) to and from which access is restricted. A specific user may be a member of one or more CUGs. Members of a specific CUG can communicate among each other but not, in general, with users outside the group.
+
+The ability to set up emergency calls remains unaffected.
+
+## 1.2 Description
+
+### 1.2.1 Service description
+
+An ISDN/MSISDN number shall identify each member of a CUG.
+
+A CUG shall be defined for one or more basic service groups.
+
+CUG members can have additional capabilities that allow them to originate calls outside the group, and/or to receive calls from outside the group. CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG, or from receiving calls from other members of the CUG.
+
+CUG shall remain unaffected when members roam to PLMNs supporting CUG. Roaming subscribers must have the same CUG facilities on the roamed-to PLMN as on the Home PLMN.
+
+When roaming to networks not supporting CUG, the CUG restrictions must be enforced. (However, where possible, the CUG facilities should be supported, see subclause 1.4.10.)
+
+Each individual subscriber may be a member of a maximum of 10 CUGs.
+
+### 1.2.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004 [2].
+
+### 1.2.3 Definitions
+
+**MSISDN:** A number conforming to the numbering plan and structure specified in 3GPP TS 23.003.
+
+**CUG member:** A user who has subscribed to the CUG Supplementary Service and is one of the users in the group formed by a particular CUG.
+
+**CUG index:** A value assigned by the network to identify a CUG.
+
+**CUG Interlock Code (IC):** Is used by the network (not by the MS) to identify CUG membership.
+
+**preferential CUG:** A preferential CUG, which can be specified for each basic service group, is the nominated default CUG to be used when no explicit CUG index is received by the network.
+
+**suppress preferential CUG:** A user action to prohibit the use of the preferential CUG, on a per call basis.
+
+**Incoming Access (IA):** An arrangement which allows a member of a CUG to receive calls from outside the CUG.
+
+**Outgoing Access (OA):** An arrangement which allows a member of a CUG to place calls outside the CUG.
+
+**suppress OA:** A user action to prohibit the use of the OA subscription option, on a per call basis.
+
+**Incoming Calls Barred Within A CUG (ICB):** An access restriction that prevents a CUG member from receiving calls from other members of that group.
+
+**Outgoing Calls Barred Within A CUG (OCB):** An access restriction that prevents a CUG member from placing calls to other members of that group.
+
+**CUG calls:** A CUG call is a call which is restricted to a pre-defined group of users.
+
+## 1.3 Normal procedures with successful outcome
+
+### 1.3.1 Provision
+
+The CUG Supplementary Service shall be provided after prior arrangement with the service provider. At provision subscription options should be selected by the served mobile subscriber.
+
+A user may be a member of several CUGs. The service provider defines the number of CUGs, up to the maximum stated in subclause 1.2.1, which can be allocated to an individual subscriber.
+
+The user shall choose one of the following subscription options for each basic service group applied to the CUG Supplementary Service. This subscription option may be provisioned on a per basic service group basis or for all basic services:
+
+- CUG calls only;
+- CUG with incoming access, i.e. can also receive calls, which are not subject to CUG restrictions;
+- CUG with outgoing access, i.e. can also make calls, which are not subject to CUG restrictions;
+
+- CUG with incoming and outgoing access, i.e. can also make and receive calls, which are not subject to CUG restrictions.
+
+A user may subscribe to one of two additional restrictions applying for each particular CUG:
+
+- incoming calls barred within a CUG;
+- outgoing calls barred within a CUG.
+
+The network shall provide a subscription option in order to enable the user to specify a preferential CUG, for each basic service group included in at least one of the CUG(s). The user can request that no preferential CUG exists, or that a particular one of her CUGs (or the only one if a single CUG applies) is used as a preferential CUG for the particular basic service group.
+
+If a user has the subscription option outgoing calls barred within a CUG, it is not allowed to specify that particular CUG as a preferential CUG.
+
+The subscription options are shown in Annex 1.
+
+The CUG indices shall be allocated by prior arrangement with the service provider.
+
+The choice of preferential CUG(s) shall be alterable only by service provider action upon request by the served user.
+
+### 1.3.2 Withdrawal
+
+Withdrawal of the CUG Supplementary Service, membership of one or more CUGs, will be by the action of the service provider, at the request of the subscriber or CUG management, or for administrative reasons.
+
+### 1.3.5 Activation
+
+The CUG Supplementary Service will be activated by the service provider as a result of provision.
+
+### 1.3.6 Deactivation
+
+The CUG Supplementary Service will be deactivated by the service provider as a result of withdrawal.
+
+### 1.3.7 Invocation
+
+Normal call setup procedures shall apply to calls with the CUG Supplementary Service.
+
+### 1.3.8 Normal operation with successful outcome
+
+A user having neither the restriction of incoming calls barred within a CUG, nor the restriction of outgoing calls barred within a CUG can make calls to, and receive calls from, members of those CUGs of which the user is a member.
+
+Upon receipt of a call setup attempt to or from a CUG subscriber the network shall check its validity in conjunction with the access capabilities subscribed to.
+
+On successful validation of a CUG call setup attempt the network shall attempt to establish the call to the required destination.
+
+#### 1.3.8.1 Mobile originating calls
+
+When originating a call, the calling user may specify a CUG index to indicate that service to a particular CUG is required. If no CUG index is given then the preferential CUG (if specified) is used by the network.
+
+The Outgoing Access (OA) capability allows CUG subscribers to make outgoing calls, which are not subject to CUG restrictions.
+
+If a user, subscribing to the CUG Supplementary Service, originates a call and enters a request for suppression of both a preferential CUG and of the OA capability but does not enter a CUG index, the call shall be rejected.
+
+If a user, subscribing to the CUG Supplementary Service and having the OA capability, originates a call and enters a CUG index (without suppressing the OA capability), while having the restriction of outgoing calls barred within that CUG, the call shall be established without any CUG information i.e. as a normal call.
+
+The originating PLMN actions are illustrated in annex 2.
+
+As a network option, the network may signal towards the calling user the CUG index in use for the current call, if this can be determined by the network.
+
+##### **1.3.8.1.1 A user with no preferential CUG and no OA capability**
+
+If a user, subscribing to the CUG Supplementary Service, who has no preferential CUG and no OA capability, originates a call and enters a CUG index (and possibly requests suppression of a preferential CUG and/or the OA capability) the call shall be established using the CUG index provided. If no CUG index is entered the call shall be rejected.
+
+##### **1.3.8.1.2 A user with a preferential CUG but no OA capability**
+
+If a user, subscribing to the CUG Supplementary Service, who has a preferential CUG but no OA capability, originates a call and enters no CUG information (or if she only requests suppression of the OA capability), the call shall be established using the preferential CUG. If she enters a CUG index (and possibly a request for suppression of the preferential CUG and/or the OA capability), the call shall be established using the CUG index provided. If she enters only a request for suppression of the preferential CUG, i.e. no CUG index, the call shall be rejected.
+
+##### **1.3.8.1.3 A user with the OA capability but no preferential CUG**
+
+If a user, subscribing to the CUG Supplementary Service, who has the OA capability but no preferential CUG, originates a call and enters no CUG information (or if she only requests suppression of a preferential CUG), the call shall be established without any CUG information being sent, i.e. this is set up as a normal call. If she enters a CUG index (and possibly a request for suppression of a preferential CUG), the call shall be established using the CUG index provided and with an indication of OA allowed. If she enters both a CUG index and a request for suppression of the OA capability (and possibly a request for suppression of a preferential CUG), the call shall be established using the CUG index provided. If she enters only a request for suppression of the OA capability, i.e. no CUG index, the call shall be rejected.
+
+##### **1.3.8.1.4 A user with a preferential CUG and the OA capability**
+
+If a user, subscribing to the CUG Supplementary Service, who has a preferential CUG and the OA capability, originates a call without any CUG information, the call shall be established using the preferential CUG and with an indication of OA allowed. If she enters a CUG index (and possibly a request for suppression of the preferential CUG), the call shall be established using the CUG index provided and with an indication of OA allowed. If she enters only a request for suppression of the OA capability, the call shall be established using the preferential CUG. If she enters only a request for suppression of the preferential CUG, i.e. no CUG index, the call shall be established without any CUG information i.e. this is set up as a normal call. If she enters both a CUG index and a request for suppression of the OA capability (and possibly a request for suppression of the preferential CUG), the call shall be established using the CUG index provided.
+
+##### **1.3.8.1.5 A user not subscribing to the CUG Supplementary Service**
+
+If a user, not subscribing to the CUG Supplementary Service, originates a call and enters CUG information the call shall be set up as a normal call.
+
+#### **1.3.8.2 Mobile terminating calls**
+
+If a user, with or without the IA capability, receives a CUG call and the calling user is a member of the same CUG, the incoming CUG call shall be indicated as such, towards the called Mobile Station, with the appropriate CUG index.
+
+If a user with the IA capability receives a call from a user who has not subscribed to the CUG Supplementary service, or from a user who is a member from another CUG and who is using the OA capability, the call is offered to the user as a normal incoming call.
+
+The terminating PLMN actions are illustrated in annex 3.
+
+##### **1.3.8.2.1 CUG call with no OA indication**
+
+For a call where an interlock code is received, but not an indication of OA allowed, the following applies:
+
+If there is a match with any of the called user's CUGs, and if she does not have incoming calls barred within this CUG, the call shall be offered as a CUG call. In all other cases the call shall be rejected.
+
+##### 1.3.8.2.2 CUG call with OA indication
+
+For a call where both an interlock code and an indication of OA allowed is received, the following applies:
+
+If there is a match with any of the called user's CUGs, and if she does not have incoming calls barred within this CUG, the call shall be offered as a CUG call.
+
+If the above condition does not apply, and if she has incoming access allowed, the call shall be offered as a normal call.
+
+If the called subscriber does not subscribe to the CUG Supplementary Service, the call shall be offered as a normal call.
+
+In all other cases, the call shall be rejected.
+
+##### 1.3.8.2.3 Normal call
+
+When a normal call is received, i.e. a call without any CUG information, the following shall apply:
+
+If the called subscriber subscribes to the CUG Supplementary Service and has incoming access allowed, or if she is a normal non-CUG subscriber, the call shall be offered as a normal call. In all other cases, the call shall be rejected.
+
+## 1.4 Exceptional procedures or unsuccessful outcome
+
+### 1.4.1 Exceptional operation or unsuccessful outcome
+
+Upon receipt of a call setup attempt to or from a CUG subscriber, the network shall check its validity in conjunction with the access capabilities subscribed to. If an invalid request is received or the checks cannot be performed, then the network shall reject the call and return an appropriate indication to the calling user.
+
+The network shall prohibit a user with incoming calls barred within a CUG from receiving CUG calls from members of the same CUG.
+
+The network shall prohibit a user with outgoing calls barred within a CUG from making CUG calls within that CUG.
+
+### 1.4.10 Roaming into networks not supporting CUG
+
+The HPLMN shall control handling of roaming, when a CUG subscriber is roaming into a network not supporting CUG, without relying on extra functionality in network entities not supporting CUG.
+
+For subscribers roaming in a PLMN not supporting CUG the following apply:
+
+- 1) In the case of basic service groups not subject to CUG restrictions, incoming and outgoing calls shall be allowed as normal.
+- 2) In the case of basic service groups subject to CUG restrictions and without incoming access, incoming calls shall not be allowed.
+- 3) In the case of basic service groups subject to CUG restrictions and without outgoing access, outgoing calls shall not be allowed.
+- 4) Normal incoming calls are allowed for basic service groups subject to CUG restrictions and for which the called user has incoming access allowed.
+- 5) Outgoing calls are allowed for basic service groups subject to CUG restrictions and for which the user has outgoing access allowed.
+
+## 1.5 Alternate procedures
+
+None identified
+
+## 1.6 Interactions with other Supplementary Services
+
+#### 1.6.82.1 Call forwarding unconditional
+
+CUG restrictions shall be met between the calling user and the forwarding user. In addition, the call must not be forwarded if the CUG restrictions of the forwarding mobile subscriber forbid her to make a call attempt of the same type to the forwarded-to user. The parameters of the CUG requested by the calling user shall be used for the forwarding call, and by this means CUG restrictions shall be met between the calling user and the forwarded-to user, except for the cases stated in section b) below.
+
+Annex 4 shows under what circumstances a call shall be allowed to be forwarded.
+
+- a) CUG call with no OA indication.
+
+For calls received with an IC, but no indication of OA allowed, the following is valid:
+
+If the forwarding subscriber subscribes to the CUG Supplementary Service, and if she does not have outgoing calls barred within the CUG, the call shall be forwarded with the same IC as received from the A-party. In all other cases, the call shall be rejected.
+
+- b) CUG call with an indication of OA allowed.
+
+For calls received with an IC and an indication of OA allowed, the following is valid:
+
+If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is a match with any of her CUGs, and if she does not have OA allowed, and if she does not have outgoing calls barred within the CUG, then the call shall be forwarded with the same IC as received from the A-party (the indication of OA allowed shall in this case NOT be forwarded).
+
+If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is a match with any of her CUGs, and if she does have OA allowed, and if she does not have outgoing calls barred within the CUG, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed. If this forwarding subscriber has outgoing calls barred within the CUG, then the call shall be forwarded as a normal call (the CUG information shall in this case NOT be forwarded).
+
+If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is no match with any of her CUGs, but if she has IA allowed and OA allowed, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed (in this case the subscription option "Intra-CUG restrictions" is not relevant).
+
+If the forwarding subscriber does not subscribe to the CUG Supplementary Service, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed.
+
+In all other cases, the call shall be rejected.
+
+- c) Normal call.
+
+For normal calls received the following is valid:
+
+If the forwarding subscriber subscribes to the CUG Supplementary Service, and if she does have OA allowed, then the call shall be forwarded without any CUG data. (In this case the subscription option "Intra-CUG restrictions" is not relevant.)
+
+If the forwarding subscriber does not subscribe to the CUG Supplementary Service, then the call shall be forwarded (without any CUG data).
+
+In all other cases, the call shall be rejected.
+
+#### 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
+
+No interaction. If the incoming (waiting) call is a CUG call it shall be indicated as such.
+
+#### 1.6.84.1 Multi-party service
+
+No interaction. Multi-party calls shall be set up taking into account the CUG relationships between the controlling party and each of the remote parties. The CUG restrictions need not to be checked between remote parties.
+
+### 1.6.88 Call restriction Supplementary Services
+
+Except for ACR, the following is valid:
+
+- The call restriction Supplementary Services, when active and operative, takes precedence over the CUG restrictions.
+- The activation of a call restriction Supplementary Service does not affect any current CUG call.
+
+For ACR, see 3GPP TS 22.088 [6].
+
+## 1.7 Interworking considerations
+
+If, due to an interworking situation, signalling in the network is not able to carry the information required to provide the service, the network shall terminate the attempt and return an appropriate indication to the calling user. However, a CUG call with an OA indication shall in this case continue to be established as a normal call.
+
+The rejection of CUG calls cannot be technically guaranteed in all network interconnection cases, and can only be ensured by inter-connect agreement.
+
+Management of CUG spanning over multiple networks:
+
+A CUG may span over several networks. In this case the responsibility for the management of this CUG is in one of these networks.
+
+- NOTE: One mechanism exists for CUGs spanning over data networks only, having X.121 as the numbering plan (see ITU-T Recommendation X.180 (1988)), "Administrative arrangements for international closed user groups".
+
+# --- Annex 1 (normative): General subscription options (Per Subscriber)
+
+| <b>Subscription Option</b>                     | <b>Values Available</b>                                                                                                                                         |
+|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Subscription to CUGs                           | List of one or more CUG indices to the maximum stated in subclause 1.2.1.                                                                                       |
+| Intra CUG restrictions (for each CUG)          | <ul style="list-style-type: none"> <li>- None designated</li> <li>- Incoming calls barred within a CUG</li> <li>- Outgoing calls barred within a CUG</li> </ul> |
+| Applicability to Basic Services (for each CUG) | <ul style="list-style-type: none"> <li>- List of one or more Basic Service groups</li> <li>- All Basic Services</li> </ul>                                      |
+
+Per basic service group subscription options
+
+| <b>Subscription Option</b>      | <b>Values Available</b>                                                                                                                                           |
+|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Preferential CUG                | <ul style="list-style-type: none"> <li>- None designated (NOTE)</li> <li>- CUG index</li> </ul>                                                                   |
+| Type of inter CUG accessibility | <ul style="list-style-type: none"> <li>- None designated</li> <li>- Outgoing access</li> <li>- Incoming access</li> <li>- Outgoing and Incoming access</li> </ul> |
+
+# Annex 2 (normative): Originating PLMN actions on call requests on the calling user's side
+
+| Calling user's subscription                  | Information from the calling user                      |                                                          |                               |                                                        |                                                              |
+|----------------------------------------------|--------------------------------------------------------|----------------------------------------------------------|-------------------------------|--------------------------------------------------------|--------------------------------------------------------------|
+|                                              | No CUG info                                            | CUG index or CUG index and suppress pref. CUG            | Suppress OA                   | Suppress pref. CUG                                     | CUG index and suppress OA or CUG index and suppress pref CUG |
+| -<br>-<br>-                                  |                                                        |                                                          |                               |                                                        |                                                              |
+| User without preferential CUG and without OA | Reject call                                            | Establish call using CUG index provided                  | Reject call                   | Reject call                                            | Establish call using CUG index provided                      |
+| User with preferential CUG but without OA    | Establish call using pref CUG                          | Establish call using CUG index provided                  | Establish call using pref CUG | Reject call                                            | Establish call using CUG index provided                      |
+| User without preferential CUG but with OA    | Establish call without any CUG info i.e. a normal call | Establish call using CUG index provided and OA indicator | Reject call                   | Establish call without any CUG info i.e. a normal call | Establish call using CUG index provided                      |
+| User with preferential CUG and with OA       | Establish call using pref CUG and OA indicator         | Establish call using CUG index provided and OA indicator | Establish call using pref CUG | Establish call without any CUG info i.e. a normal call | Establish call using CUG index provided                      |
+| User without the CUG SS                      | Normal call                                            | Normal call                                              | Normal call                   | Normal call                                            | Normal call                                                  |
+
+NOTE 1: If a CUG user enters a non-allocated CUG index the call shall be rejected.
+
+NOTE 2: If a user, subscribing to the CUG Supplementary Service and having the OA capability, originates a call and enters a CUG index (without suppressing the OA capability), while having the restriction of outgoing calls barred within that CUG, the call shall be established without any CUG information i.e. as a normal call.
+
+# Annex 3 (normative): Terminating PLMN actions
+
+This table shows the type of call request sent to the destination user or that a rejection indication is returned to the calling user, as a result of the CUG checks on the destination network side.
+
+Network actions on call requests on the called user's side
+
+| Type of CUG indication<br>from the network | M<br>or<br>NM | CUG attributes of the forwarding user for requested basic service group |          |             |             | forwarding user is a non CUG user |  |
+|--------------------------------------------|---------------|-------------------------------------------------------------------------|----------|-------------|-------------|-----------------------------------|--|
+|                                            |               | IA not allowed                                                          |          | IA allowed  |             |                                   |  |
+|                                            |               | not icb                                                                 | icb      | not icb     | icb         |                                   |  |
+| CUG call with no OA indication             | M             | CUG call                                                                | rejected | CUG call    | rejected    | rejected                          |  |
+|                                            | NM            | rejected                                                                |          | rejected    |             |                                   |  |
+| CUG call with OA indication                | M             | CUG call                                                                | rejected | CUG call    | normal call | normal call                       |  |
+|                                            | NM            | rejected                                                                |          | normal call |             |                                   |  |
+| Normal call                                | --            | rejected                                                                |          | normal call |             | normal call                       |  |
+
+M: match with any of the called subscriber's CUGs for the requested basic service group.
+
+NM: no match with any of the called subscriber's CUGs for the requested basic service group.
+
+# Annex 4 (normative): CUG interaction with the call forwarding Supplementary Services
+
+This table shows under what circumstances a call shall be allowed to be forwarded.
+
+| Type of CUG indication<br>from the network | M<br>or<br>NM<br>1) | CUG attributes of the forwarding user for requested basic service group |          |            |          | forwarding user is a non CUG user |  |
+|--------------------------------------------|---------------------|-------------------------------------------------------------------------|----------|------------|----------|-----------------------------------|--|
+|                                            |                     | OA not allowed                                                          |          | OA allowed |          |                                   |  |
+|                                            |                     | not ocb                                                                 | ocb      | not ocb    | ocb      |                                   |  |
+| CUG call with no OA indication             | M                   | CF                                                                      | rejected | CF         | rejected | rejected                          |  |
+|                                            | NM                  | rejected                                                                |          | rejected   |          |                                   |  |
+| CUG call with OA indication                | M                   | CFm 2)                                                                  | rejected | CF         | CFn      | CF                                |  |
+|                                            | NM                  | rejected                                                                |          | CF 3)      |          |                                   |  |
+| Normal call                                | --                  | rejected                                                                |          | CF 3)      |          | CF                                |  |
+
+Abbreviations:
+
+CF: Forward call using the calling subscriber's parameters
+
+CFm: Forward call using modified calling subscriber's parameters
+
+CFn: The call is forwarded as a normal call.
+
+NOTE 1: M: match with any of the called subscriber's CUGs for the requested basic service group.
+
+NM: no match with any of the called subscriber's CUGs for the requested basic service group.
+
+NOTE 2: Only the interlock code is sent from the forwarding subscriber towards the forwarded to subscriber.
+
+NOTE 3: The subscription option outgoing calls barred within a CUG (ocb), is not relevant in this case.
+
+# Annex 5 (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.85 |      |      |        |     | Transferred to 3GPP SA1                      | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.085    |      |      | R99    |     | Transferred to 3GPP SA1                      |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99632  | 22.085    | 001  |      | R99    | D   | Editorial changes for alignment              | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-06          | SP-99519  | S1-99999  | 22.085    | 002  |      | R99    | D   | Editorial update for GSM/3GPP use.           | 3.0.1  | 3.1.0  |                   |
+| SP-11          | SP-010065 | S1-010258 | 22.085    |      |      | Rel-4  |     | Transferred to 3GPP Release 4                | 3.1.0  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.085    | 003  | -    | Rel-4  | F   | Editorial CR to correct terms and references | 4.0.0  | 4.1.0  | CORRECT           |
+| SP-16          | SP-020267 | S1-021043 | 22.085    |      |      | Rel-5  |     | Updated from Rel-4 to Rel5                   | 4.1.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-36          |           |           | 22.085    |      |      | 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-111408 | 22.085    | 0004 | -    | Rel-11 | B   | Addition of Anonymous Call Rejection as a SS | 10.0.0 | 11.0.0 | ACR_CS            |
+| 2014-10        | -         | -         | -         | -    | -    | -      | -   | Update to Rel-12 version (MCC)               | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -    | -    | -      | -   | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |                   |

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

@@ -0,0 +1,373 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Advice of Charge (AoC) supplementary services;**
+
+**3GPP TS 22.086 V13.0.0 (2015-12)**
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above the "a" and "n" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The logo for 3GPP. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, AOC, supplementary service,  
+stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)  | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC        | 12.0.0 | 13.0.0 |                   |

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

@@ -0,0 +1,521 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.087 User-to-User Signalling (UUS); Service description; Technical Specification Stage 1 (Release 13)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above the "a" in "ADVANCED" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the right of the "e" in "lte".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, UUS, supplementary service,  
+stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                           | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC                                                 | 12.0.0 | 13.0.0 |                   |

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

@@ -0,0 +1,643 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.088 V13.0.0 (2015-12) Call Barring (CB) supplementary services** ---
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a "TM" symbol. Above the "e" is the word "ADVANCED" in a smaller, uppercase font. To the right of the "e" are three red curved lines representing signal waves. Below the main text is a faint reflection of the logo.
+
+LTE Advanced logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top. Below the "P" is a small red signal wave icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, uppercase font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, call barring,  
+supplementary service, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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             |
+| 2014-10        | -         | -         | -         | -        | -   | -      | -   | Update to Rel-12 version (MCC)               | 11.1.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -        | -   | -      | -   | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22090/raw.md

@@ -0,0 +1,324 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Unstructured Supplementary Service Data (USSD); Stage 1 *Technical Specification* (Release 13)**
+
+![LTE Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above "ADVANCED" are three red curved lines representing signal waves. A small "TM" trademark symbol is to the right of "lte".
+
+LTE Advanced logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the top. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is to the right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, USSD,  
+supplementary service, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Foreword .....                                                             | 4  |
+| 1 Scope.....                                                               | 4  |
+| 2 References.....                                                          | 4  |
+| 3 Abbreviations .....                                                      | 5  |
+| 4 Description.....                                                         | 5  |
+| 5 USSD operations – MMI mode .....                                         | 5  |
+| 5.1 Mobile initiated USSD operations .....                                 | 5  |
+| 5.1.1 Initiating action at the User Equipment (UE).....                    | 5  |
+| 5.1.2 Action at the network .....                                          | 5  |
+| 5.1.3 Mobile initiated USSD cross phase compatibility.....                 | 6  |
+| 5.1.4 Allocation of service codes (to be noted by network operators) ..... | 6  |
+| 5.2 Network initiated USSD operation .....                                 | 7  |
+| 5.2.1 Initiating actions in the network.....                               | 7  |
+| 5.2.2 Actions at the UE.....                                               | 7  |
+| 5.3 Network aspects of USSD operation.....                                 | 7  |
+| 6 USSD operations – application mode .....                                 | 8  |
+| 6.1 General .....                                                          | 8  |
+| 6.2 Mobile initiated transfer.....                                         | 8  |
+| 6.2.1 Initiating action at the UE.....                                     | 8  |
+| 6.2.2 Action in the network .....                                          | 8  |
+| 6.3 Network initiated transfer.....                                        | 8  |
+| 6.3.1 Initiating action in the network.....                                | 8  |
+| 6.3.2 Action at the UE .....                                               | 8  |
+| 6.4 External addressing .....                                              | 8  |
+| 6.5 Charging aspects .....                                                 | 8  |
+| 6.6 Compatibility aspects .....                                            | 9  |
+| 6.6.1 Mobile initiated transfer .....                                      | 9  |
+| 6.6.2 Network initiated transfer.....                                      | 9  |
+| 6.7 Interaction with other services .....                                  | 9  |
+| 6.8 Security.....                                                          | 9  |
+| 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.
+
+# --- 1 Scope
+
+The present document defines the stage 1 description of Unstructured Supplementary Service Data (USSD) for use in one or a number of Public Land Mobile Networks (PLMNs).
+
+# --- 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 23.038: "Alphabets and language-specific information".
+- [5] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the abbreviations listed in TS 21.905 [1] apply.
+
+# --- 4 Description
+
+There are two modes of USSD: MMI-mode and application mode. MMI-mode USSD is for the transparent transport of MMI strings entered by the user to the network and for the transparent transport of text strings from the network that are displayed by the mobile for user information.
+
+Application mode USSD is for the transparent transport of data between the network and the UE. Application mode USSD is intended to be used by applications in the network and their peer applications in the UE.
+
+The communication over the radio interface takes place on the signalling channels using short dialogues with peak data throughput rate capabilities of up to approximately 600 bits/s outside of a call and 1 000 bits/s during a call.
+
+# --- 5 USSD operations – MMI mode
+
+## 5.1 Mobile initiated USSD operations
+
+### 5.1.1 Initiating action at the User Equipment (UE)
+
+If the user enters an MMI string that, according to TS 22.030 [3], should be treated as USSD, the UE shall send this string to the network using the appropriate operation from TS 24.080 [5].
+
+The mobile initiated operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the user.
+
+The UE may initiate an USSD operation either during a call or out of call.
+
+### 5.1.2 Action at the network
+
+A network supporting USSD shall examine the alphabet indicator. If the serving network does not recognize the alphabet indicated in the mobile initiated USSD operation, it shall send the operation to the HLR.
+
+On recognition of the alphabet, the network shall examine the contents of the string, and take appropriate action, according to the following rules, depending of the format of the message.
+
+- Case a) 1, 2 or 3 digits from the set (\*, #) followed by 1X(Y), where X=any number 0-4, Y=any number 0-9, then, optionally "\*" followed by any number of any characters", and concluding with # SEND:
+
+This case is reserved for HPLMN use. When a serving network receives such a message from a visiting subscriber, it shall pass the USSD message directly to the HPLMN. If it receives it from a home subscriber, it is up to the network to decide whether to treat it locally or to pass it to the HLR.
+
+- Case b) 1, 2 or 3 digits from the set (\*, #) followed by 1X(Y), where X=any number 5-9, Y=any number 0-9, then, optionally "\*" followed by any number of any characters", and concluding with # SEND:
+
+This case is reserved for VPLMN use. It is up to the VPLMN to decide how to treat it.
+
+- Case c) 7(Y) SEND, where Y=any number 0-9:
+
+This case is reserved for HPLMN use. When a serving network receives such a message from a visiting subscriber, it shall pass the USSD message directly to the HPLMN. If it receives it from a home subscriber, it is up to the network to decide whether to treat it locally or to pass it to the HLR.
+
+- Case d) All other formats:
+
+The visited network examines the message. If it is able, it acts upon it. Failing that, it passes the message to the HLR.
+
+If the HLR does not support the alphabet indicated, it shall inform the UE.
+
+The network shall terminate the mobile initiated operation by responding to the request from the mobile with either an error signal, or a text string indicating the outcome of the operation. The response string uses the characters available in the selected alphabet as defined in TS 23.038 [4]. If no indication to the user is required, the response string may be empty.
+
+The response to the mobile initiated USSD operation shall contain alphabet and language indicators. The selection of values for these indicators is a matter for the network operator.
+
+### 5.1.3 Mobile initiated USSD cross phase compatibility
+
+In situations of incompatibility the mobile initiated USSD operation will be rejected by a non-supporting network and the attempt will fail. In this situation, if it is possible to encode the content of the USSD message in the IA5 alphabet, the UE shall attempt the operation again using the IA5 format without the alphabet and language indicators.
+
+This procedure is not applicable if an operation failure is due to alphabet support problems, services not supported or network failure problems.
+
+### 5.1.4 Allocation of service codes (to be noted by network operators)
+
+Service codes for use in control of Supplementary Services are standardized by international agreement, so must not be used by PLMNs unless authorized, except for those codes allocated for PLMN use.
+
+If the message is of the format:
+
+1, 2 or 3 digits from the set (\*, #), followed by
+
+NN(N), where N=0-9,
+
+optionally followed by "\* and any number of any characters",
+
+and terminating in # SEND:
+
+then NN(N) is known as the service code. Only codes specified in TS 22.030 [3] and those defined in cases a) and b) above may be used. All other values are reserved.
+
+Similarly, if the message is of the format:
+
+X(Y) SEND, where X=0-6 or 8-9 and Y=0-9:
+
+the codes X(Y) are standardized. Only codes specified in TS 22.030 [3] subclause 4.5.5 may be used. All other values are reserved.
+
+## 5.2 Network initiated USSD operation
+
+### 5.2.1 Initiating actions in the network
+
+At any stage while the UE is registered with a network, the network may send an unstructured string to the UE. This string contains operator determined information that is relevant to the user. If the network is unable to successfully reach the UE, then an error shall be returned to the node that originated the operation.
+
+The network initiated USSD operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the network operator.
+
+### 5.2.2 Actions at the UE
+
+If the UE is unable to process the network initiated USSD operation (e.g. the feature is not supported or the user is engaged in another MMI activity) then an error indication shall be returned to the node that originated the operation. If the alphabet indicated by the network is not supported by the UE, the UE shall inform the network.
+
+The network may explicitly indicate to the UE that a response from the user is required. In this case, the next string entered by the user shall be used as the response and this string is not interpreted according to normal MMI procedures stated in TS 22.030 [3]. An MMI command shall be provided to allow the user to terminate the dialogue with a null response. The response string uses the characters available in the selected alphabet as defined in TS 23.038 [4]. The response is sent to the node that originated the operation. If the network does not indicate that a response is required, then the normal MMI procedures on the UE continue to apply.
+
+The UE shall include alphabet and language indicators in the response to the network (if any).
+
+## 5.3 Network aspects of USSD operation
+
+Applications that use USSD operations may be located in either the HPLMN or a roamed to VPLMN.
+
+Network applications using USSD operations may:
+
+- use several USSD operations (possibly a mixture of mobile initiated and network initiated) in combination as part of a dialogue with the user. Linkage between separate operations as part of a dialogue is only implemented locally in the network application and does not lead to any special mode of operation in the UE. The network initiated request for a response from the user and the corresponding response is a single operation;
+- act on calls in progress, or place new calls, as part of the service the application provides.
+
+Release of the connection used for an unstructured dialogue is normally the responsibility of the network and may be carried out at the request of the application using the USSD operations. The user may also initiate connection release through an MMI procedure.
+
+# --- 6 USSD operations – application mode
+
+## 6.1 General
+
+USSD supports communication between an application (handler) in the UE and a corresponding application (handler) in the network by enabling transparent transfer of binary data between the network and the UE. The applications may use USSD either during a call or out of call.
+
+Application-level addressing is out of scope of the present document.
+
+## 6.2 Mobile initiated transfer
+
+### 6.2.1 Initiating action at the UE
+
+If the UE wishes to send data to the network, it can do so using USSD. It shall be possible for the UE to send data to nodes in the VPLMN and in the HPLMN, i.e. MSC, VLR, HLR, MExE servers, CSEs and proxy servers.
+
+### 6.2.2 Action in the network
+
+The serving network shall pass the received message to its destination node. If the VPLMN cannot route the message to the destination it shall forward the message to the HPLMN.
+
+## 6.3 Network initiated transfer
+
+### 6.3.1 Initiating action in the network
+
+If a node in the network wishes to send data to an UE, it can do so using USSD.
+
+If the network is unable successfully to reach the UE, then an error shall be returned to the node that originated the operation.
+
+### 6.3.2 Action at the UE
+
+The UE shall pass the message to the ME, to the SIM/USIM or to the TE as indicated in the message.
+
+## 6.4 External addressing
+
+The USSD dialogue exists inside the PLMN. However, it shall be possible to transport the address of an external node in the USSD message. The address format must be standardised and support at least E.164 and IP addresses.
+
+When addressing of an UE from an external node the address shall be an MSISDN number. The return address shall be present and in the same format the UE uses to address an external node.
+
+The mechanism for communication between the PLMN and the external node is out of scope of the present document.
+
+## 6.5 Charging aspects
+
+It shall be possible to charge for the use of application mode USSD based on e.g. the destination node.
+
+Charging for the use of an application is out of scope of the present document.
+
+## 6.6 Compatibility aspects
+
+### 6.6.1 Mobile initiated transfer
+
+If the network does not support application mode USSD, the mobile initiated operation will be rejected and the attempt will fail. The UE shall not attempt automatic fall back to phase 1 USSD or to MMI mode USSD in case of incompatibility. Application-level recovery is outside the scope of the present document.
+
+If the network is unable to identify the destination node, it shall forward the message to the HLR.
+
+### 6.6.2 Network initiated transfer
+
+If the UE is unable to process the network initiated USSD operation, then an error indication shall be returned to the node that originated the operation.
+
+## 6.7 Interaction with other services
+
+The user or the network operator shall be able to prevent the use of application mode USSD during calls. The use of USSD in parallel with a circuit switched call may have a negative impact on the quality of the speech or data transmission.
+
+## 6.8 Security
+
+Application-level security is out of scope of the present document.
+
+# 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.90  |      |     |       |     | Transferred to 3GPP SA1                  | 8.0.0  |        |           |
+| SA#04          |           |           | 22.090 |      |     | R99   |     |                                          |        | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99636  | 22.090 | 0001 |     | R99   | D   | Editorial changes for alignment for 3GPP | 3.0.0  | 3.0.1  |           |
+| SP-07          | SP-000063 | S1-000048 | 22.090 | 0002 |     | R99   | C   | UCS2 character set for MMI mode          | 3.0.1  | 3.1.0  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.090 |      |     | Rel-4 |     | Transferred to 3GPP Release 4            | 3.1.0  | 4.0.0  |           |
+| SP-16          | SP-020267 | S1-021043 | 22.090 |      |     | Rel-5 |     | Updated from Rel-4 to Rel5               | 4.0.0  | 5.0.0  |           |
+| SP-26          | SP-040744 | S1-040997 | 22.090 |      |     | Rel-6 |     | Updated from Rel-5 to Rel-6              | 5.0.0  | 6.0.0  |           |
+| SP-32          | SP-060445 | -         | 22.090 | 0003 | 2   | Rel-7 | F   | USSD – Corrections                       | 6.0.0  | 7.0.0  | TEI7      |
+| 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 |           |
+| 2014-10        | -         | -         | -      | -    | -   | -     | -   | Update to Rel-12 version (MCC)           | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-13 by MCC                 | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22091/raw.md

@@ -0,0 +1,487 @@
+
+
+# 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; ~~Explicit Call Transfer (ECT) supplementary service; Stage 1~~ *Technical Specification* **(Release 13)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a trademark symbol, and the word "ADVANCED" in a smaller, uppercase font above the "e". Above the text is a red signal strength icon consisting of four curved bars.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized, bold font with a trademark symbol. Below the "P" is a red signal strength icon consisting of three curved bars.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+## Keywords
+
+LTE, UMTS, GSM, supplementary service, ECT,  
+stage 1
+
+### **3GPP**
+
+### Postal address ---
+
+### 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet ---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                                                                                 |    |
+|-----------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                                  | 5  |
+| 1 Scope.....                                                                                                    | 6  |
+| 2 References.....                                                                                               | 6  |
+| 3 Definitions and abbreviations .....                                                                           | 6  |
+| 3.1 Definitions.....                                                                                            | 6  |
+| 3.2 Abbreviations .....                                                                                         | 7  |
+| 4 Description.....                                                                                              | 7  |
+| 4.1 Applicability to telecommunication services.....                                                            | 7  |
+| 5 Normal operation with successful outcome .....                                                                | 7  |
+| 5.1 Provision.....                                                                                              | 7  |
+| 5.2 Withdrawal.....                                                                                             | 7  |
+| 5.3 Registration .....                                                                                          | 7  |
+| 5.4 Erasure.....                                                                                                | 7  |
+| 5.5 Activation.....                                                                                             | 7  |
+| 5.6 Deactivation .....                                                                                          | 8  |
+| 5.7 Invocation.....                                                                                             | 8  |
+| 5.8 Normal operation.....                                                                                       | 8  |
+| 5.9 Interrogation .....                                                                                         | 8  |
+| 5.10 Charging requirements .....                                                                                | 9  |
+| 6 Exception procedures or unsuccessful outcome .....                                                            | 9  |
+| 7 Alternate procedures .....                                                                                    | 9  |
+| 8 Interaction with other supplementary services.....                                                            | 9  |
+| 8.1 Calling Line Identification Presentation (CLIP) .....                                                       | 9  |
+| 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) .....                                                                   | 10 |
+| 8.6 Call Forwarding on mobile subscriber Busy (CFB).....                                                        | 10 |
+| 8.7 Call Forwarding on No Reply (CFNRy).....                                                                    | 10 |
+| 8.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) .....                                            | 11 |
+| 8.9 Call Waiting (CW) .....                                                                                     | 11 |
+| 8.10 Call Hold (HOLD) .....                                                                                     | 11 |
+| 8.11 Multi-party (MPTY) service .....                                                                           | 11 |
+| 8.12 Closed User Group (CUG).....                                                                               | 11 |
+| 8.13 Advice of Charge (AoC) .....                                                                               | 11 |
+| 8.14 Barring of All Outgoing Calls (BAOC) .....                                                                 | 12 |
+| 8.15 Barring of all Outgoing International Calls (BOIC) .....                                                   | 12 |
+| 8.16 Barring of all Outgoing International Calls except those direct 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 (CT).....                                                                                    | 12 |
+
+9 Interworking considerations..... 12
+
+**Annex A (informative): Deviations of PLMN ECT to the ISDN specifications of ECT ..... 13**
+
+A.1 Subclause 4.1 Applicability to telecommunication services..... 13
+
+A.2 Subclause 5.8 Normal operation ..... 13
+
+A.3 Subclause 6 Exception procedures or unsuccessful outcome ..... 13
+
+A.4 Subclause 8.6 and 8.7..... 13
+
+A.5 Annexes..... 13
+
+**Annex B (normative): Cross Phase compatibility ..... 14**
+
+Annex C (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 the stage 1 description of Explicit Call Transfer (ECT) from the service 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 Technical Specifications.
+
+The charging principles applied to ECT are established in the present document in terms of the charging information required to be collected. Any subsequent charging implications are outside of the scope of the present document.
+
+Any interactions with other networks not dealt with in Clause 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 TS 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] 3GPP TS 22.030: " Man-Machine Interface (MMI) of the Mobile Station (MS)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definitions apply.
+
+**Alerting state:** the remote subscriber is being informed of the call (i.e. the connection has not yet been established for that call).
+
+**Answered state:** the connection has been established on the call to the remote subscriber.
+
+**Subscriber A:** is the served mobile subscriber, the one who has subscribed to, and invokes the Explicit Call Transfer supplementary service.
+
+**Subscriber B:** is the other party in one of subscribers A's calls. By convention, in the present document it is considered that the connection has been established on this call.
+
+**Subscriber C:** is the other party in another of subscribers A's calls.
+
+**Subscriber D:** is the forwarded-to subscriber of call forwarded by subscriber C.
+
+NOTE: Each of subscriber B, C and D can be a mobile or a fixed subscriber, and each of them is referred to as "remote party".
+
+**Successful invocation:** The ECT supplementary service is successfully invoked if the outcome of all checks (e.g. subscription, states of calls, resources) performed by the network on the received ECT request from the served subscriber are successful.
+
+## 3.2 Abbreviations
+
+All abbreviations used within the present document are given in 3GPP TS 21.905 [1].
+
+# --- 4 Description
+
+The ECT supplementary service enables the served mobile subscriber (subscriber A) who has two calls , each of which can be an incoming or outgoing call, to connect the other parties in the two calls and release the served mobile subscribers own connection.
+
+Prior to transfer, the connection shall have been established on the call between subscriber A and subscriber B. On the call between subscriber A and subscriber C, either the connection shall have been established prior to transfer, or, as a network option, transfer can occur while subscriber C is being informed of the call (i.e. the connection has not yet been established.)
+
+## 4.1 Applicability to telecommunication services
+
+This service is applicable to telephony (TS:11) only.
+
+# --- 5 Normal operation with successful outcome
+
+## 5.1 Provision
+
+The supplementary service shall be provided after pre-arrangement with the service provider.
+
+The provision of the Call Hold (HOLD) supplementary service is also required.
+
+## 5.2 Withdrawal
+
+The supplementary service shall be withdrawn at the subscriber request or for service provider reasons.
+
+## 5.3 Registration
+
+Not applicable.
+
+## 5.4 Erasure
+
+Not applicable.
+
+## 5.5 Activation
+
+The supplementary service shall be activated by the service provider as a result of provision.
+
+## 5.6 Deactivation
+
+The supplementary service shall be deactivated by the service provider as a result of withdrawal.
+
+## 5.7 Invocation
+
+ECT shall be invoked by the served mobile subscriber by use of a control procedure as described in TS 22.030 [2].
+
+## 5.8 Normal operation
+
+The served mobile subscriber (subscriber A) who has two calls (one with subscriber B and one with subscriber C), each of which can be an incoming call or an outgoing call, can request the invocation of the ECT supplementary service with respect to the two calls.
+
+The connection shall have been established on one of the calls (referred to as the call between subscriber A and subscriber B).
+
+The ECT supplementary service can be invoked after the connection has been established on the call between subscriber A and subscriber C, and in addition, as a network option, after subscriber C has been informed of the call (i.e. an outgoing call from subscriber A to subscriber C, where the connection has not yet been established).
+
+On successful invocation of the ECT supplementary service, the two calls between subscriber A and subscriber B and between subscriber A and subscriber C respectively shall be removed from subscriber A's access (i.e. the traffic channel and the signalling channel towards subscriber A will be released) and shall be transformed into a normal call between subscriber B and subscriber C where the state of the previously held party is changed to active without a subscriber action.
+
+The previously held party will be informed in the normal way of the retrieve procedure.
+
+If the network option above is supported, then if subscriber C is being informed of the call from subscriber A at the time of transfer, the call shall remain in this state at subscriber C (as a network option the ringing tone will be given to subscriber B), and when the connection is established by subscriber C, subscriber C shall be connected to subscriber B.
+
+Subscriber A will no longer have any control of the on-going call between B and C.
+
+The network shall inform (if possible) subscriber B and subscriber C of the occasion that call transfer has happened including the state (connection established, or user being informed of the call) of the call to the other subscriber.
+
+If the network option above is supported, then after connection is established on a call which was transferred whilst subscriber C was being informed of that call, subscriber B shall be informed that the connection has been established on the call to subscriber C.
+
+The line identity of subscriber B shall be indicated to subscriber C as specified in subclauses 8.1 through 8.4.
+
+The line identity of subscriber C shall be indicated to subscriber B as specified in subclauses 8.1 through 8.4, either:
+
+- at the time of transfer, if the connection had been established between subscriber A and subscriber C; or
+- when subscriber B is informed that the connection has been established to subscriber C, if this occurs after transfer.
+
+## 5.9 Interrogation
+
+Not applicable.
+
+## 5.10 Charging requirements
+
+The charging principles applicable prior to the served mobile subscribers invocation of ECT, shall also apply after the ECT supplementary service is successfully invoked, i.e. the same charging information will continue to be collected after invocation as before. The charging information for both calls shall contain an indication of successful invocation of ECT.
+
+NOTE: There is no additional charging requirement on the interchange signalling capabilities.
+
+# --- 6 Exception procedures or unsuccessful outcome
+
+If a mobile subscriber tries to invoke the call transfer service while not subscribed to or the network cannot provide ECT supplementary service for some other reason, an indication shall be provided to the mobile subscriber to notify the mobile subscriber with the reason of failure.
+
+The call state is not affected and the established connection shall remain in the state prior to the request.
+
+In the case where:
+
+- the two calls are incompatible with the ECT request, i.e. either one of them or both are not belonging to the service TS:11 (telephony);
+- if the network option is not supported and the call state is not compatible with the request, e.g. one call is not answered
+
+the request shall be rejected by the network and the subscriber shall be notified with the reason.
+
+The call state is not affected and the established connection shall remain in the state prior to the request.
+
+The request for the ECT supplementary service shall be rejected if, as a network option, the network can determine that the resulting connection would contain no subscriber who is able to terminate the call.
+
+NOTE: It may not be possible to decide if the resulting connection would have such a subscriber, e.g. when interworking between different versions of signalling systems occurs. In such cases, as a network option, the request for the ECT supplementary service may be accepted, or rejected. If the request for the ECT supplementary service is accepted in this case, the network may employ other means to control this situation (e.g. time supervision). The procedures for this are outside the scope of the present document.
+
+# --- 7 Alternate procedures
+
+For further study.
+
+# --- 8 Interaction with other supplementary services
+
+## 8.1 Calling Line Identification Presentation (CLIP)
+
+If subscriber A originated the call between subscribers A and B, and subscriber B subscribes to CLIP, subscriber C's identity shall be presented to subscriber B, subject to subscriber C's line identification restrictions (see subclauses 8.2 and 8.4). If the connection has been established on the call between subscribers A and C before ECT is invoked, subscriber C's identity shall be presented when ECT is invoked. If the connection is established on the call between subscribers A and C after ECT is invoked, subscriber C's identity shall be presented when the connection on that call is established.
+
+If subscriber A originated the call between subscribers A and C, and subscriber C subscribes to CLIP, subscriber B's identity shall be presented to subscriber C, subject to subscriber B's line identification restrictions (see subclauses 8.2 and 8.4) when ECT is invoked.
+
+## 8.2 Calling Line Identification Restriction (CLIR)
+
+If subscriber B originated the call between subscribers A and B, and subscriber B subscribes to CLIR, presentation of subscriber B's identity to subscriber C shall be controlled by that subscription. Subscriber B's serving network may also provide information on the cause of no CLI.
+
+If subscriber C originated the call between subscribers A and C, and subscriber C subscribes to CLIR, presentation of subscriber C's identity to subscriber B shall be controlled by that subscription. Subscriber C's serving network may also provide information on the cause of no CLI.
+
+## 8.3 Connected Line Identification Presentation (COLP)
+
+If subscriber B originated the call between subscribers A and B, and subscriber B subscribes to COLP, subscriber C's identity shall be presented to subscriber B, subject to subscriber C's line identification restrictions (see subclauses 8.2 and 8.4). If the connection has been established on the call between subscribers A and C before ECT is invoked, subscriber C's identity shall be presented when ECT is invoked. If the connection is established on the call between subscribers A and C after ECT is invoked, subscriber C's identity shall be presented when the connection on that call is established.
+
+If subscriber C originated the call between subscribers A and C, and subscriber C subscribes to COLP, subscriber B's identity shall be presented to subscriber C, subject to subscriber B's line identification restrictions (see subclauses 8.2 and 8.4) when ECT is invoked.
+
+## 8.4 Connected Line Identification Restriction (COLR)
+
+If subscriber A originated the call between subscribers A and B, and subscriber B subscribes to COLR, presentation of subscriber B's identity to subscriber C shall be controlled by that subscription.
+
+If subscriber A originated the call between subscribers A and C, and subscriber C subscribes to COLR, presentation of subscriber C's identity to subscriber B shall be controlled by that subscription.
+
+## 8.5 Call Forwarding Unconditional (CFU)
+
+No impact.
+
+## 8.6 Call Forwarding on mobile subscriber Busy (CFB)
+
+Where a network supports the option to transfer a call for which the connection has been established to a subscriber C to which the connection has not yet been established, the transferred call will be forwarded to a forwarded-to subscriber D if the CFB condition at subscriber C (i.e. UDUB) applies.
+
+For a call that is forwarded due to CFB after ECT is invoked, the sending of line identities to subscriber B and forwarded-to subscriber D respectively shall correspond to what is specified for the B and C subscribers in subclauses 8.1 through 8.4, i.e. replacing 'subscriber C' with 'the forwarded-to subscriber D' in the text.
+
+## 8.7 Call Forwarding on No Reply (CFNRy)
+
+The CFNRy timer at C is not restarted after the transfer has taken place.
+
+Where a network supports the option to transfer a call for which the connection has been established to a subscriber C to which the connection has not yet been established, the transferred call will be forwarded to a forwarded-to subscriber D if the call forwarding no reply timer expires.
+
+For a call that is forwarded due to CFNRy after ECT is invoked, the sending of line identities to subscriber B and forwarded-to subscriber D respectively shall correspond to what is specified for the B and C subscribers in subclauses 8.1 through 8.4, i.e. replacing 'subscriber C' with 'the forwarded-to subscriber D' in the text.
+
+## 8.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
+
+No impact.
+
+## 8.9 Call Waiting (CW)
+
+No impact, any party may receive a CW indication before, during or after the calls are transferred.
+
+NOTE: After execution of ECT the served subscribers access is free for receiving calls without a CW indication.
+
+If subscriber A has one active, one held and one waiting call, then once ECT of the held and active calls has been successfully completed, subscriber A shall be offered the normal notification that there is a new call, as for a normal terminating call.
+
+If the call to subscriber C meets the waiting state at C, the subscriber B shall be informed after successful transfer about the waiting status at subscriber C.
+
+## 8.10 Call Hold (HOLD)
+
+No impact, if either subscriber B or C have put their call to the served subscriber A on hold prior to the transfer, the resulting transferred call shall remain on hold by that subscriber. In this case the remote parties shall not be informed of the held state on the call.
+
+## 8.11 Multi-party (MPTY) service
+
+A served mobile subscriber who has invoked MPTY supplementary service is not allowed to invoke the ECT supplementary service.
+
+This is due to the fact that the MPTY functionality can not be subject to call transfer at all.
+
+Any of the remote parties is allowed to invoke ECT.
+
+## 8.12 Closed User Group (CUG)
+
+The two calls shall use the same closed user group for the transfer to be successful.
+
+NOTE: Closed user group restrictions between subscribers will have been checked when the first call is established. Similarly, closed user group restrictions between subscribers will have been checked when established the second call.
+
+## 8.13 Advice of Charge (AoC)
+
+Served mobile subscriber:
+
+- if call transfer is successfully accepted by the network, subscriber A will be disconnected, and therefore AoC processing at subscribers A Mobile Station will be stopped;
+- for the combination AoC charging level and ECT, it is strongly recommended not to subscribe to both supplementary services at the same time.
+
+Remote mobile subscriber:
+
+- any AoC service at the remote sides will continue to calculate the charging information according to the original call.
+
+## 8.14 Barring of All Outgoing Calls (BAOC)
+
+No impact.
+
+## 8.15 Barring of all Outgoing International Calls (BOIC)
+
+No impact.
+
+NOTE: If transfer occurs successfully at subscriber A, the barring programs at the remote subscribers cannot be checked again.
+
+## 8.16 Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC-exHC)
+
+No impact.
+
+NOTE: If transfer occurs successfully at subscriber A, the barring programs at the remote subscribers cannot be checked again.
+
+## 8.17 Barring of All Incoming Calls (BAIC)
+
+No impact.
+
+## 8.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)
+
+No impact.
+
+## 8.19 Call Transfer (CT)
+
+No impact.
+
+The ECT supplementary service can be invoked simultaneously by the users on a call for which the connection has been established, but this is not regarded as a normal situation. The network will not be required to prevent this occurring, but likewise cannot guarantee that the indications supplied to the users involved will be sensible to those users. There can be more than one indication generated due to multiple invocations of the ECT supplementary service and the arrival of such indications is dependent on the timing of their invocation by the users involved in the call. The network shall transfer these indications when they are generated.
+
+Therefore, both mobile subscribers (subscriber A and subscriber B) in a normal call, who have each subscribed to the ECT supplementary service, can simultaneous transfer the call. That is, if subscriber A and subscriber B are involved in a call on which the connection has been established, subscriber A can transfer the call to user C and subscriber B can transfer the call to user D.
+
+NOTE: Mechanisms which prevent the ECT supplementary service from resulting in a connection which contains no subscriber able to terminate the call may result in rejection of simultaneous requests to invoke the ECT supplementary service by the subscribers involved in the call.
+
+# --- 9 Interworking considerations
+
+The operation of this supplementary service is not affected by the nature of the far end of the connections.
+
+NOTE: In some networks the indication to the remote parties about the invocation of ECT may not be supported.
+
+## --- Annex A (informative): Deviations of PLMN ECT to the ISDN specifications of ECT
+
+### A.1 Subclause 4.1 Applicability to telecommunication services
+
+This service is applicable to Telephony (TS:11) only.
+
+**NA1 states:** applicable to all circuit switched basic telecommunication services.
+
+### --- A.2 Subclause 5.8 Normal operation
+
+The NOTE describing the Call Hold scenario is not included in the 3GPP stage 1 specifications.
+
+In 3GPP specifications there a explicit explanation that the previously held party shall be informed of the retrieve procedure.
+
+**NA1:** there is no explicit description of this procedure.
+
+In 3GPP specifications there is no explicit exchange of the subaddress of the remote parties after the successful transfer defined.
+
+**NA1 states:** After the successful transfer of the call, the subscriber B and subscriber C can deliver if supplied their subaddress to the other subscriber.
+
+### --- A.3 Subclause 6 Exception procedures or unsuccessful outcome
+
+In the case where:
+
+- the two calls are incompatible with ECT (either one of them or both are not Telephony service);
+- the call state is not compatible with the request, e.g. one call is not answered;
+- etc. (for further study).
+
+the request will be rejected by the network and the subscriber will be notified of the cause.
+
+**NA1 states:** It is the responsibility of the served user to ensure that the two calls are compatible.
+
+### --- A.4 Subclause 8.6 and 8.7
+
+**NA1:** There is no special definition of the impact of the interaction between CFB and CFNRy and ECT on the line identification supplementary services.
+
+## --- A.5 Annexes
+
+Annex A is missing in the ISDN specification.
+
+## --- Annex B (normative): Cross Phase compatibility
+
+As a operator option it is possible to support also the invocation of ECT by using Unstructured Supplementary Service Data (USSD).
+
+The USSD string used should be the same as the standardised MMI code (4 SEND) for ECT.
+
+The network shall send an indication towards the user if ECT was invoked successfully or unsuccessfully, though the mechanism for this indication is not specified.
+
+If a remote party uses a non-ECT mobile station they may not receive the ECT notification.
+
+## Annex C (informative): Change history
+
+| Change history |           |           |           |     |     |       |     |                                      |        |        |           |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|--------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                      | Old    | New    | Work Item |
+| Jun 1999       |           |           | GSM 02.91 |     |     |       |     | Transferred to 3GPP SA1              | 7.0.0  |        |           |
+| SA#04          |           |           | 22.091    |     |     | R99   |     |                                      |        | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99637  | 22.091    | 001 |     | R99   | D   | Editorial changes for alignment      | 3.0.0  | 3.0.1  |           |
+| SP-09          | SP-000377 | S1-000587 | 22.091    | 002 |     | R99   | F   | CR on CLI presentation modifications | 3.0.1  | 3.1.0  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.091    |     |     | Rel-4 |     | Transferred to 3GPP Release 4        | 3.1.0  | 4.0.0  |           |
+| SP-16          | SP-020267 | S1-021043 | 22.091    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5           | 4.0.0  | 5.0.0  |           |
+| SP-26          | SP-040744 | S1-040997 | 22.091    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6          | 5.0.0  | 6.0.0  |           |
+| SP-36          |           |           | 22.091    |     |     | 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 |           |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)       | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC             | 12.0.0 | 13.0.0 |           |

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

@@ -0,0 +1,749 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1 (Release 13)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced. It features the word "lte" in a bold, black, lowercase sans-serif font. Above the "t" is the word "4DVANCED" in a smaller, italicized, black sans-serif font. Above the "4" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, black, hand-drawn font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, CCBS,  
+supplementary service, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)  | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC        | 12.0.0 | 13.0.0 |                   |

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

@@ -0,0 +1,413 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.094 V13.0.0 (2015-12) Follow Me Service description;** ---
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font, with a small "TM" trademark symbol to its right. Above the "e" in "lte" is the word "4DVANCED" in a smaller, uppercase sans-serif font. Above the "4" in "4DVANCED" are three red curved lines representing signal waves. Below the "lte" text is a faint, mirrored reflection of the logo.
+
+LTE Advanced logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for the 3rd Generation Partnership Project (3GPP). It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal icon consisting of three curved lines. To the right of the "P" is a small "TM" trademark symbol.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, follow me,  
+supplementary service, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 |           |
+| 2014-10        | -                    | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                 | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -                    | -         | -      | -   | -   | -     | -   | Updated to Rel-13 by MCC                                       | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22096/raw.md

@@ -0,0 +1,364 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.096 V13.0.0 (2015-12) Name identification supplementary services;** ---
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above "ADVANCED" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for the 3rd Generation Partnership Project (3GPP). It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>TM</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP<sup>TM</sup> system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, GSM, UMTS, CNAP,  
+supplementary service, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                       |    |
+|-----------------------------------------------------------------------|----|
+| Foreword .....                                                        | 4  |
+| 1 Scope.....                                                          | 5  |
+| 2 References.....                                                     | 5  |
+| 3 Definitions and abbreviations .....                                 | 5  |
+| 3.1 Definitions.....                                                  | 5  |
+| 3.2 Abbreviations .....                                               | 6  |
+| 4 Calling Name Presentation (CNAP) .....                              | 6  |
+| 4.1 Definition .....                                                  | 6  |
+| 4.2 Description .....                                                 | 6  |
+| 4.2.1 Description .....                                               | 6  |
+| 4.2.2 Applicability to telecommunication services .....               | 6  |
+| 4.3 Normal procedures with successful outcome.....                    | 6  |
+| 4.3.1 Provision.....                                                  | 6  |
+| 4.3.2 Withdrawal .....                                                | 7  |
+| 4.3.3 Registration.....                                               | 7  |
+| 4.3.4 Erasure.....                                                    | 7  |
+| 4.3.5 Activation .....                                                | 7  |
+| 4.3.6 Deactivation.....                                               | 7  |
+| 4.3.7 Invocation .....                                                | 7  |
+| 4.3.8 Normal operation with successful outcome.....                   | 7  |
+| 4.3.9 Interrogation .....                                             | 7  |
+| 4.4 Exceptional procedures or unsuccessful outcome.....               | 8  |
+| 4.5 Alternate procedures .....                                        | 8  |
+| 4.6 Interactions with other supplementary services .....              | 8  |
+| 4.6.1 Calling Line Identification Presentation (CLIP) .....           | 8  |
+| 4.6.2 Calling Line Identification Restriction (CLIR) .....            | 8  |
+| 4.6.3 Call Forwarding Unconditional (CFU) .....                       | 8  |
+| 4.6.4 Call Forwarding on mobile subscriber Busy (CFB).....            | 8  |
+| 4.6.4.1 Network Determined User Busy (NDUB).....                      | 8  |
+| 4.6.4.2 User Determined User Busy (UDUB) .....                        | 9  |
+| 4.6.5 Call Forwarding on No Reply (CFNRy) .....                       | 9  |
+| 4.6.6 Call Forwarding on mobile subscriber Not Reachable (CFNRc)..... | 9  |
+| 4.6.7 Call Waiting (CW) .....                                         | 9  |
+| 4.6.9 Explicit Call Transfer (ECT).....                               | 9  |
+| 4.6.10 Support of Private Numbering Plan (SPNP) .....                 | 9  |
+| 4.6.11 Completion of Calls to Busy Subscriber (CCBS) .....            | 9  |
+| 4.6.12 enhanced Multi-Level Precedence and Pre-emption (eMLPP) .....  | 9  |
+| 4.7 Service functions for roamers .....                               | 9  |
+| 4.8 Interworking considerations.....                                  | 9  |
+| 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.
+
+# --- 1 Scope
+
+The present document describes the supplementary services belonging to the group Name Identification supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004 [2].
+
+The group of Name Identification supplementary services is divided into the following supplementary services:
+
+CNAP                                              Calling Name Presentation (clause 4).
+
+# --- 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.081: "Line Identification Supplementary Services - Stage 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definitions apply:
+
+### **Definition of name identity:**
+
+The name identity is made up of the following information unit:
+
+- The name of the mobile subscriber for the purpose of calling name presentation - up to 80 characters of information associated with a specific calling party.
+
+The calling name identity is the name identity of the calling party.
+
+### **Definition of Presentation Indicator:**
+
+In addition to or instead of the name identity, the network may give a Presentation Indicator (PI) to the called mobile subscriber of the CNAP service. The following information may be given:
+
+- Presentation Indicator (PI) showing:
+  - a) presentation restricted, or
+  - b) name unavailable.
+
+The name identity of a PLMN subscriber shall always be provided by the network.
+
+**Calling Party:** The calling party is the originating party.
+
+**Called Party:** The called party is the terminating party. The CNAP service is provided to the called party.
+
+**Calling Name Information:** The calling name information of the calling party includes either the calling name identity or an indication of privacy or unavailability.
+
+## 3.2 Abbreviations
+
+In addition to the following abbreviations used in the present document, abbreviations are listed in TS 21.905 [1].
+
+|      |                           |
+|------|---------------------------|
+| CNAP | Calling Name Presentation |
+|------|---------------------------|
+
+# --- 4 Calling Name Presentation (CNAP)
+
+## 4.1 Definition
+
+The CNAP supplementary service enables the called party to receive the calling name information of the calling party.
+
+## 4.2 Description
+
+### 4.2.1 Description
+
+This supplementary service provides for the ability to indicate the name information of the calling party to the called party at call set-up time for all incoming calls.
+
+The calling party takes no action to activate, initiate, or in any manner provide Calling Name Identification Presentation. However, the delivery of the calling name to the called party may be affected by other services subscribed to by the calling party. For example, if the calling party has subscribed to Calling Line Identification Restriction (CLIR), then the calling line identity as well as the calling name identity shall not be presented to the called party.
+
+### 4.2.2 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in TS 22.004 [2].
+
+CNAP is applicable to all telecommunication services except Short Message service. (for further study)
+
+## 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.
+
+This service shall be provided after pre-arrangement with the service provider. It may be provided on a subscription basis or be generally available.
+
+The override category controlling the name information is separate from the override category for the line identity information. It is left to the CNAP service provider to ensure that no discrepancy between these two override categories occurs. The handling of override category within a PLMN or between PLMNs shall follow the rules applying to the override category of the line identification services TS 22.081 [3].
+
+### 4.3.2 Withdrawal
+
+The CNAP supplementary service shall be withdrawn at the customer's request or for administrative reasons.
+
+### 4.3.3 Registration
+
+Not applicable.
+
+### 4.3.4 Erasure
+
+Not applicable.
+
+### 4.3.5 Activation
+
+The CNAP supplementary service is activated as a result of provision.
+
+### 4.3.6 Deactivation
+
+The CNAP supplementary service is deactivated as a result of withdrawal.
+
+### 4.3.7 Invocation
+
+The network shall automatically invoke the CNAP supplementary service in the call set-up phase to the terminating CNAP subscriber.
+
+CNAP is invoked when the Calling Name Information associated with an incoming call is available and can be presented to the called party which has subscribed to CNAP.
+
+### 4.3.8 Normal operation with successful outcome
+
+A user who has subscribed to the CNAP supplementary service and receives a call shall also receive the calling name information of the calling party, if available.
+
+The calling party takes no action to activate, initiate, or in any manner provide the calling name identity.
+
+When the CNAP service is subscribed and activated, the destination network provides the called subscriber with calling name information at call set-up on all incoming calls or during an active call for that particular call.
+
+In addition to, or instead of, the calling name identity, the subscriber may be given a presentation indicator with the relevant information.
+
+### 4.3.9 Interrogation
+
+#### Status check
+
+The mobile subscriber can, by the appropriate control procedure, request from the network the status of this supplementary service. Upon receiving an interrogation request, the network shall send the status of this supplementary service to the subscriber.
+
+The information sent to the subscriber shall indicate whether the service is provided to her.
+
+The information sent in response to the interrogation of this supplementary service shall not imply the status of any other supplementary service.
+
+## 4.4 Exceptional procedures or unsuccessful outcome
+
+If the name identity for a specific caller is not available, then the CNAP subscriber shall be sent an indication that the name is unavailable.
+
+If the network has been unable to determine the appropriate name information within a predefined time, then the CNAP subscriber shall be sent an indication that the name is unavailable. The predefined time is a network dependent value such that the called user may receive the name in a timely manner prior to answer.
+
+If the calling name information is not available due to a system problem, such as signalling inter-working, then a standard error treatment shall be provided, which may be a visual display to the subscriber indicating the name is unavailable.
+
+## 4.5 Alternate procedures
+
+The decision of whether the user-defined name stored in the handset should take precedence over the calling name identity provided by the network is a handset implementation issue.
+
+## 4.6 Interactions with other supplementary services
+
+Only those supplementary services for which CNAP has any interactions are detailed in this clause. For all other supplementary services not mentioned in this clause no interactions were identified.
+
+### 4.6.1 Calling Line Identification Presentation (CLIP)
+
+No interaction.
+
+### 4.6.2 Calling Line Identification Restriction (CLIR)
+
+The CLIR supplementary service shall take precedence over the CNAP supplementary service, unless the called user has an override category. In this latter case, it is assumed that the override category for name information has been set so that the name information is presented to the called user.
+
+The Calling Line Identification Restriction (CLIR) information shall be used to restrict the delivery of the calling name to the called subscriber. That is, if the calling party has activated CLIR then instead of the calling name, a privacy indication shall be provided to the called subscriber, which may be a visual display indicating “private” (or Restricted) name. This method of restricting calling name shall not restrict the use or implementation of other calling name restriction methods when the calling party is a fixed subscriber. These methods used by fixed subscribers are outside the scope of this specification.
+
+### 4.6.3 Call Forwarding Unconditional (CFU)
+
+For an incoming call to a subscriber with both CNAP and Call Forwarding Unconditional activated, the calling party name information shall not be displayed at the forwarding subscribers terminal.
+
+When a call has been forwarded and the forwarded-to user has been provided with the CNAP supplementary service, the forwarded-to user shall receive the name of the original calling party, if the calling party has not subscribed to or invoked the CLIR supplementary service.
+
+### 4.6.4 Call Forwarding on mobile subscriber Busy (CFB)
+
+#### 4.6.4.1 Network Determined User Busy (NDUB)
+
+Same as the interaction with call forwarding unconditional.
+
+#### 4.6.4.2 User Determined User Busy (UDUB)
+
+Same as interaction with call forwarding no reply.
+
+### 4.6.5 Call Forwarding on No Reply (CFNRy)
+
+For an incoming call to a subscriber with both CNAP and Call Forwarding on No Reply activated, the calling party name information shall be displayed by the predefined time while the call is alerting.
+
+### 4.6.6 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
+
+Same as the interaction with call forwarding unconditional.
+
+### 4.6.7 Call Waiting (CW)
+
+If the served mobile subscriber is provisioned with the CNAP service, the calling party name information shall be displayed to the subscriber at the notification of an incoming (waiting) call as for a normal incoming call.
+
+### 4.6.9 Explicit Call Transfer (ECT)
+
+For Further Study.
+
+### 4.6.10 Support of Private Numbering Plan (SPNP)
+
+The public number corresponding to the used PNP number is used to obtain the calling name information for delivery to the called party's terminal.
+
+### 4.6.11 Completion of Calls to Busy Subscriber (CCBS)
+
+No interaction.
+
+### 4.6.12 enhanced Multi-Level Precedence and Pre-emption (eMLPP)
+
+No interaction.
+
+## 4.7 Service functions for roamers
+
+CNAP should be available to a roaming subscriber. However, the serving system may elect to not offer the CNAP service to any subscriber.
+
+## 4.8 Interworking considerations
+
+According to national network specific rules, the CNAP supplementary services need not be applicable, if at least one of the two parties is not an ISDN or PLMN subscriber.
+
+# 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.96 |     |     |       |     | Transferred to 3GPP SA1         | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.096    |     |     |       |     | Transferred to 3GPP SA1         |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99639  | 22.096    | 001 |     | R99   | D   | Editorial changes for alignment | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.096    |     |     | Rel-4 |     | Transferred to 3GPP Release 4   | 3.0.1  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.096    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5      | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.096    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6     | 5.0.0  | 6.0.0  |                   |
+| SP-36          |           |           | 22.096    |     |     | 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 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)  | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-13 by MCC        | 12.0.0 | 13.0.0 |                   |

marked/Rel-13/22_series/22097/raw.md

@@ -0,0 +1,447 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1 (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the right of the "e" is a small "TM" symbol. Above the "lte" text are three green curved lines representing signal waves.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left of the "G". The "P" and "P" are connected at the top by a single horizontal line. Below the "G" is a small red signal wave icon. To the right of the "P" is a small "TM" symbol.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, UMTS, GSM, supplementary service, MSP,  
+stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                  |    |
+|----------------------------------------------------------------------------------|----|
+| Foreword .....                                                                   | 5  |
+| 1 Scope.....                                                                     | 6  |
+| 2 References.....                                                                | 6  |
+| 3 Definitions and abbreviations .....                                            | 6  |
+| 3.1 Definitions.....                                                             | 6  |
+| 3.2 Abbreviations .....                                                          | 7  |
+| 4 Description.....                                                               | 7  |
+| 4.1 Applicability to telecommunication services .....                            | 7  |
+| 5 Functional requirements.....                                                   | 7  |
+| 5.1 Handling of the MSP Service.....                                             | 7  |
+| 5.1.1 Provision.....                                                             | 7  |
+| 5.1.2 Withdrawal .....                                                           | 7  |
+| 5.1.3 Activation .....                                                           | 7  |
+| 5.1.4 Deactivation.....                                                          | 7  |
+| 5.1.5 Invocation .....                                                           | 8  |
+| 5.2 Handling of the Profile .....                                                | 8  |
+| 5.2.1 Provision.....                                                             | 8  |
+| 5.2.2 Withdrawal .....                                                           | 8  |
+| 5.2.3 Registration.....                                                          | 8  |
+| 5.2.4 Selection .....                                                            | 8  |
+| 5.2.5 Erasure .....                                                              | 8  |
+| 5.2.6 Interrogation .....                                                        | 8  |
+| 5.3 Normal operation with successful outcome .....                               | 9  |
+| 5.3.1 Mobile Originating Calls.....                                              | 9  |
+| 5.3.2 Mobile Terminating Calls.....                                              | 9  |
+| 5.3.3 Mobile Originating Call Independent Supplementary Service Activities ..... | 9  |
+| 5.3.4 Call Related Supplementary Service Activities.....                         | 9  |
+| 5.4 Exceptional procedures or unsuccessful outcome.....                          | 9  |
+| 5.4.1 Roaming into networks not supporting MSP .....                             | 9  |
+| 5.4.2 Registration or Selection of a profile that is already registered .....    | 9  |
+| 5.4.3 Registration or Selection of a non-provisioned profile .....               | 9  |
+| 5.4.4 Registration or Selection attempts where MSP is not provisioned .....      | 10 |
+| 6 Interaction with supplementary services.....                                   | 10 |
+| 6.1 Line Identification Services .....                                           | 10 |
+| 6.2 Call Hold (HOLD) .....                                                       | 10 |
+| 6.3 Call Waiting (CW) .....                                                      | 10 |
+| 6.4 Call Forwarding.....                                                         | 10 |
+| 6.5 Multi Party Service (MPTY).....                                              | 10 |
+| 6.6 Closed User Group (CUG).....                                                 | 10 |
+| 6.7 Advice of Charge (AoC).....                                                  | 10 |
+| 6.8 Call Barring .....                                                           | 11 |
+| 6.9 Explicit Call Transfer (ECT).....                                            | 11 |
+| 6.10 CCBS.....                                                                   | 11 |
+| 6.11 eMLPP.....                                                                  | 11 |
+| 6.12 Multicall .....                                                             | 11 |
+| 7 Interaction with other services .....                                          | 11 |
+| 7.1 The Multi-Numbering Scheme.....                                              | 11 |
+| 7.2 The Short Message Service.....                                               | 11 |
+| 7.3 Interactions with CAMEL.....                                                 | 12 |
+| 7.4 Interactions with OR .....                                                   | 12 |
+| 7.5 Operator Determined Barring.....                                             | 12 |
+| 7.6 Roaming restrictions .....                                                   | 12 |
+
+8 Cross-Phase Compatibility.....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.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document gives an overall view of how this service shall operate both in the PLMN and within the Mobile Station (MS). This TS defines functionality and is not intended to constrain implementation.
+
+# --- 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 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 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".
+- [5] 3GPP TS 22.135: "Multicall".
+- [6] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) ".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this TS the following definitions apply:
+
+**Subscriber:** The user who is provisioned with the MSP service
+
+**Profile:** A profile consists of a set of telecommunications services for the subscriber. In the case of the single numbering scheme there is a unique MSISDN associated with each profile. In the multi-numbering scheme there is the ability to have a unique MSISDN associated with each basic service in each profile.
+
+**Service Provider (SP):** The organisation through which the subscriber obtains PLMN telecommunication services. This may be the network operator or possibly a separate body.
+
+**Profile Identification (Profile ID):** The profile IDs allow unambiguous identification of each profile. This will allow the subscriber to select the preferred profile for outgoing calls and for subscriber actions. For terminating calls the profile ID shall be part of the notification of the profile.
+
+**Registered Profile:** The registered profile is that registered by/for the subscriber
+
+**Selected Profile:** For mobile originated calls and short messages this is the registered profile unless the subscriber explicitly selects an alternative profile. For mobile terminating activities, this is the profile associated with the MSISDN addressed.
+
+**Mobile Terminating Activities:** These include mobile terminating calls, short messages (SMS MT) and Call Independent Supplementary Services (e.g. NI-USSD).
+
+**Default Profile:** Profile to be used when roaming to non-supporting network
+
+## 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].
+
+|     |                             |
+|-----|-----------------------------|
+| MSP | Multiple Subscriber Profile |
+|-----|-----------------------------|
+
+---
+
+# 4 Description
+
+Multiple Subscriber Profile is an optional service to enable mobile subscribers to have several profiles associated with a single IMSI, with each profile being a subscription option. Each profile may be used for mobile originated and mobile terminated calls.
+
+Up to four different profiles can be provisioned against a subscriber using the MSP feature. This will allow the subscriber to separate her telecommunication service needs into different identities (e.g. business and home).
+
+The charges accrued for services shall be associated with the appropriate profile, allowing separate charging for each profile.
+
+A supporting visited network shall indicate [on the billing record] for charging purposes the profile used.
+
+## 4.1 Applicability to telecommunication services
+
+The applicability of this supplementary service is defined in 3GPP TS 22.004 [2].
+
+---
+
+# 5 Functional requirements
+
+## 5.1 Handling of the MSP Service
+
+This clause describes the normal procedures for the handling of the MSP service.
+
+### 5.1.1 Provision
+
+The MSP service shall be provided after prior arrangement with the service provider. If the MSP service is provisioned for the subscriber at the first time the subscriber shall also be provisioned with at least two profiles.
+
+### 5.1.2 Withdrawal
+
+Withdrawal of the MSP service shall be done by either the service provider at the subscriber's request or for administrative reasons. The MSP service shall be withdrawn when there is only one profile remaining.
+
+### 5.1.3 Activation
+
+The MSP service is activated by the service provider as a result of provision.
+
+### 5.1.4 Deactivation
+
+The MSP service is deactivated by the service provider as a result of withdrawal.
+
+### 5.1.5 Invocation
+
+The MSP service is invoked by mobile originated and mobile terminating calls.
+
+## 5.2 Handling of the Profile
+
+This subclause describes the normal procedures for selecting the registered profile for mobile originated calls, short messages and call independent supplementary service related activities. For mobile terminating activities the profile is selected automatically by association with the MSISDN addressed.
+
+### 5.2.1 Provision
+
+The provision of profiles (up to a maximum of four) is provided by prior arrangement with the service provider. The subscriber may select any provisioned profile on a per call basis or register one of them. The subscriber will nominate one of their provisioned profiles as the default profile to be used when roaming to non-supporting networks. The subscriber may subsequently nominate an alternative default (i.e. roaming) profile, nevertheless the default profile can only be changed by the service provider.
+
+### 5.2.2 Withdrawal
+
+The Service Provider shall be able to withdraw profiles. The registered profile shall never be withdrawn, and consequently if the registered profile needs to be withdrawn the service provider shall first register the subscriber onto another profile.
+
+### 5.2.3 Registration
+
+Registration is the procedure by which information is written to the network to allocate a particular profile to be used for all outgoing calls and supplementary service related activities. Registration to a profile shall take place either by the service provider or with an appropriate control procedure by the subscriber as defined in 3GPP TS 22.030 [3]. At all times only one profile shall be registered. The network shall indicate to the user whether an attempt to register a profile has been successful or not.
+
+### 5.2.4 Selection
+
+The profile to be used for mobile originated calls is selected either implicitly or explicitly:
+
+- Implicit selection occurs if the served subscriber does not indicate a profile ID when initiating a call or short message. In this case the selected profile is the registered profile.
+- Explicit selection occurs if the served subscriber does indicate a profile ID when initiating a call or short message.
+
+The control procedure used to select the profile is as defined in 3GPP TS 22.030 [3].
+
+For mobile terminating activities, the profile is selected according to the MSISDN addressed.
+
+### 5.2.5 Erasure
+
+A previous registration can be erased in the following ways:
+
+- the subscriber can register to another profile which causes the previous registration to be overridden;
+- the registered profile is erased as a result of withdrawal of the MSP service.
+
+### 5.2.6 Interrogation
+
+The subscriber shall be able to interrogate which profile is the registered profile and all other available profile IDs, with an appropriate control procedure as defined in 3GPP TS 22.030 [3].
+
+## 5.3 Normal operation with successful outcome
+
+### 5.3.1 Mobile Originating Calls
+
+Mobile originating calls shall be handled according to the selected profile. This shall be the registered profile unless an alternative is explicitly selected by the subscriber. Profiles are registered and selected according to control procedures in 3GPP TS 22.030 [3].
+
+Any activity that is normally chargeable shall be identified against the selected profile.
+
+### 5.3.2 Mobile Terminating Calls
+
+The MSISDN addressed shall be used to determine the profile to be used. If there are any active supplementary services, which are applicable to the telecommunication service within the profile, then those supplementary services
+
+shall apply. For example, if the MS is busy in a call, further incoming call attempts shall be rejected or busy, even if they were on a different profile. This shall not prevent the normal operation of Call Waiting or Call Forwarding if appropriate.
+
+The serving network shall indicate the profile towards the mobile station done by changing the alerting pattern.
+
+Any activity that is normally chargeable shall be identified against the profile used for the mobile terminating activity.
+
+### 5.3.3 Mobile Originating Call Independent Supplementary Service Activities
+
+The activity shall be handled according to the registered profile.
+
+### 5.3.4 Call Related Supplementary Service Activities
+
+The handling of call related supplementary service activities is described in clause 7.
+
+## 5.4 Exceptional procedures or unsuccessful outcome
+
+### 5.4.1 Roaming into networks not supporting MSP
+
+The default profile shall be used for outgoing traffic when the subscriber roams to a non-supporting network.
+
+Incoming calls and short messages to all profiles will still be received.
+
+### 5.4.2 Registration or Selection of a profile that is already registered
+
+If there is an attempt to register a profile that is already the registered profile, the registration shall continue uninterrupted and the user shall not be informed.
+
+If there is an attempt to select a profile that is already the registered profile, the selection shall continue uninterrupted and the user shall not be informed.
+
+### 5.4.3 Registration or Selection of a non-provisioned profile
+
+If there is an attempt to register a profile that has not been provisioned, the registration attempt shall fail and the user shall be informed. The registered profile shall remain unchanged.
+
+If there is an attempt to select a profile that has not been provisioned the selection and associated call activity shall fail. The user shall be informed. The registered profile shall remain unchanged.
+
+### 5.4.4 Registration or Selection attempts where MSP is not provisioned
+
+If there is an attempt by a subscriber who does not have MSP provisioned to register a profile, the registration attempt shall fail and subscriber shall be informed.
+
+If there is an attempt by a subscriber who does not have MSP provisioned to select a profile, the selection attempt shall fail and subscriber shall be informed.
+
+# --- 6 Interaction with supplementary services
+
+The profile used when a supplementary service is invoked will be subject to the charging principles and invocation requirements relevant to that supplementary service. The service provider may decide which profiles to charge for the service provision.
+
+## 6.1 Line Identification Services
+
+The profile in use for the incoming or outgoing call shall be used for the line identification services.
+
+The Line Identification services will be provisioned on a per subscriber basis. If provisioned, the Line Identification services shall apply over all profiles.
+
+## 6.2 Call Hold (HOLD)
+
+The HOLD service can only be invoked if the profile for that active call has the HOLD service provisioned.
+
+## 6.3 Call Waiting (CW)
+
+CW for an incoming call can only be invoked if the profile for the ongoing call has the CW service provisioned and active although the incoming call may be on any profile.
+
+## 6.4 Call Forwarding
+
+Call Forwarding will be available to the subscriber per-profile. An operator specific control procedure may be used by the subscriber to control the call forwarding service.
+
+The subscriber shall be able to forward calls to from one profile to another profile.
+
+## 6.5 Multi Party Service (MPTY)
+
+The MPTY service can only be invoked or an MPTY call controlled or extended if MPTY is provisioned for the served subscriber for each profile(s) associated with the MPTY call leg(s).
+
+## 6.6 Closed User Group (CUG)
+
+An MO call shall be treated according to the rules of the CUG service if CUG is provisioned for the selected profile. An MT call shall be treated according to the rules of the CUG service if CUG is provisioned for the profile defined by the called MSISDN.
+
+## 6.7 Advice of Charge (AoC)
+
+If subscribed to, AoCI or AoCC shall be applicable to the selected profile. Each profile shall have a separate meter (ACM) and a separate upper limit (ACMmax) when AoCC is subscribed. There shall be an overall meter for all profiles, with its own upper limit for AoCC if subscribed. For normal operation both the individual meter applicable to the selected profile and the overall meter shall be incremented.
+
+When roaming to a non-supporting network, only the overall meter shall be incremented.
+
+## 6.8 Call Barring
+
+Call Barring will be available to the subscriber per-profile. An operator specific control procedure may be used by the subscriber to control the call barring service.
+
+## 6.9 Explicit Call Transfer (ECT)
+
+ECT can only be invoked if the service is provisioned for each profile which governs a call leg to be joined by the ECT service.
+
+## 6.10 CCBS
+
+The CCBS service shall be provisioned per profile. The option not to be a target of CCBS requests shall also apply per profile. When the subscriber is informed of a CCBS recall, the profile in use when the CCBS request was activated shall be used for the CCBS call. If the subscriber activates a CCBS call request on a profile that is not the default profile and subsequently moves to a network not supporting MSP Phase 2, then if the CCBS recall matures, the corresponding CCBS request shall be suspended until the subscriber next registers on a network supporting MSP Phase 2.
+
+The limit to the number of outstanding CCBS requests that can be activated by the subscriber shall apply regardless of the number of profiles.
+
+The limit to the number of outstanding CCBS requests that can be activated against the subscriber shall apply regardless of the number of profiles.
+
+## 6.11 eMLPP
+
+eMLPP shall be provisioned per subscriber.
+
+## 6.12 Multicall
+
+The multicall supplementary service shall be provisioned on a per subscriber basis. If provisioned, Nbr\_SN, Nbr\_SB, and Nbr\_user shall apply over all profiles. (See 3GPP TS 22.135 [5] "3.1 Definitions" for detailed information)
+
+# --- 7 Interaction with other services
+
+## 7.1 The Multi-Numbering Scheme
+
+Each profile may employ the single-numbering scheme or the multi-numbering scheme. The multi-numbering scheme is described in 3GPP TS 22.001 [6]. For each of the profile(s) defined above, it shall be possible for the subscriber to be allocated different MSISDNs for different basic services.
+
+## 7.2 The Short Message Service
+
+The Short Message Service is described in 3GPP TS 23.040 [4]. It will not be possible to indicate the profile used for the MT case. All MO short messages will be sent from the default profile.
+
+MO short messages can be sent from (and charged to) the registered profile or an explicitly selected profile.
+
+Whilst roaming in a network not supporting MSP Phase 2, all MO short messages will be sent from and charged to the default profile.
+
+## 7.3 Interactions with CAMEL
+
+CAMEL based services can be provisioned either per subscriber or per profile depending on the operator specific implementation in the CSE.
+
+For call independent supplementary service procedures for CAMEL based services, information to identify the registered profile shall be passed to the CAMEL server.
+
+## 7.4 Interactions with OR
+
+No interaction
+
+NOTE: It is a HPLMN option to allow or deny OR of forwarded calls where the HPLMN recognises that the IPLMN does not support MSP. This is due to the requirement to include an indication of the profile ID in call detail records which may be raised in the IPLMN and sent to the HPLMN.
+
+## 7.5 Operator Determined Barring
+
+ODB shall apply either per subscriber or per profile.
+
+## 7.6 Roaming restrictions
+
+These will apply on a per subscriber basis.
+
+# --- 8 Cross-Phase Compatibility
+
+The default profile will be sent to the visited network and can be addressed by non-supporting networks.
+
+Mobile terminated calls to a non-supporting MS shall still be accepted but the indication of profile may not be supported.
+
+# 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       |           |           | GSM<br>02.97 |     |     |       |     | Transferred to 3GPP SA1                      | 7.1.0  |        |           |
+| SA#04          |           |           | 22.097       |     |     | R99   |     | Transferred to 3GPP SA1                      |        | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99640  | 22.097       | 001 |     | R99   | D   | Editorial changes for alignment              | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99451  | S1-99842  | 22.097       | 002 |     | R99   | B   | MSP Phase2                                   | 3.0.0  | 3.1.0  |           |
+| SP-09          | SP-000375 | S1-000584 | 22.097       | 003 |     | R99   | F   | Interaction with Multicall                   | 3.1.0  | 3.2.0  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.097       |     |     | Rel-4 |     | Transferred to 3GPP Release 4                | 3.2.0  | 4.0.0  |           |
+| SP-15          | SP-020045 | S1-020457 | 22.097       | 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.097       |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                   | 4.1.0  | 5.0.0  |           |
+| SP-26          | SP-040744 | S1-040997 | 22.097       |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                  | 5.0.0  | 6.0.0  |           |
+| SP-36          |           |           | 22.097       |     |     | 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 |           |
+| 2014-10        | -         | -         | -            | -   | -   | -     | -   | Update to Rel-12 version (MCC)               | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -         | -         | -            | -   | -   | -     | -   | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22129/raw.md

@@ -0,0 +1,699 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.129 V13.0.0 (2015-12) Handover requirements between UTRAN and GERAN or other radio systems (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the right of the "e" is a green signal icon consisting of three curved lines. A small "TM" symbol is located to the bottom right of the "e".
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo. It consists of the letters "3GPP" in a stylized, black, handwritten font. The "G" has a red signal icon consisting of three curved lines below it. A small "TM" symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+UMTS, GSM, handover
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                     |    |
+|-------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                      | 5  |
+| 1 Scope.....                                                                        | 6  |
+| 1.1 Situations in which Service Requirements apply.....                             | 6  |
+| 2 References.....                                                                   | 7  |
+| 3 Definitions and Abbreviations .....                                               | 7  |
+| 3.1 Definitions.....                                                                | 7  |
+| 3.2 Abbreviations .....                                                             | 8  |
+| 4 General Principles governing service continuity .....                             | 8  |
+| 4.1 Service Continuity Scenarios .....                                              | 8  |
+| 4.2 Service Continuity requirements.....                                            | 8  |
+| 4.2.1 Service continuity for CS .....                                               | 8  |
+| 4.2.2 Service continuity for GPRS .....                                             | 9  |
+| 4.2.3 Service continuity for IM Services.....                                       | 9  |
+| 4.3 General Operational Considerations .....                                        | 9  |
+| 4.3.1 Coverage environment.....                                                     | 9  |
+| 4.3.2 Inter PLMN Handover Issues .....                                              | 9  |
+| 4.3.3 Charging and Network Management.....                                          | 10 |
+| 4.3.4 Cost and efficiency .....                                                     | 10 |
+| 4.3.5 Security.....                                                                 | 10 |
+| 4.4 Performance Requirements .....                                                  | 10 |
+| 4.4.1 Temporary degradation of service caused by handover .....                     | 10 |
+| 5 Requirements for Handover .....                                                   | 10 |
+| 5.1 Handover due to UE Movement.....                                                | 10 |
+| 5.2 Handover due to negotiated service requirement.....                             | 11 |
+| 5.3 Handover between Radio Access Modes.....                                        | 11 |
+| 5.4 Cell capacity.....                                                              | 11 |
+| 5.5 Handover of a Multicall .....                                                   | 11 |
+| 5.6 Access Rights .....                                                             | 11 |
+| 5.7 Handover for shared networks .....                                              | 11 |
+| 6 Requirements for Handover from UTRAN to GERAN.....                                | 12 |
+| 6.1 Operational Requirements.....                                                   | 12 |
+| 6.1.2 GERAN bands .....                                                             | 12 |
+| 6.2 Performance Requirements .....                                                  | 12 |
+| 6.2.1 Detection Time of Potential GERAN Handover Candidates .....                   | 12 |
+| 6.2.2 Number of GERAN handover candidates to detect.....                            | 12 |
+| 6.2.3 Probability of Connection Loss .....                                          | 12 |
+| 6.3 Specific Requirements for Individual Services from UTRAN to GERAN .....         | 13 |
+| 6.3.1 Speech.....                                                                   | 13 |
+| 6.3.2 Short Message Service .....                                                   | 13 |
+| 6.3.3 Cell Broadcast .....                                                          | 13 |
+| 6.3.4 USSD .....                                                                    | 13 |
+| 6.3.5 Facsimile.....                                                                | 13 |
+| 6.3.6 Data Bearer Services .....                                                    | 13 |
+| 6.3.6.1 Circuit Switched Data.....                                                  | 13 |
+| 6.3.6.2 Packet Switched Data .....                                                  | 13 |
+| 6.3.7 Supplementary Services .....                                                  | 13 |
+| 6.4 Requirements on multiple bearer services handover from UTRAN to GERAN .....     | 13 |
+| 7 Requirements for Handover from GERAN to UTRAN.....                                | 14 |
+| 7.1 Operational Requirements.....                                                   | 14 |
+| 7.1.2 GERAN bands .....                                                             | 14 |
+| 7.2 Performance Requirements .....                                                  | 14 |
+| 7.3 Specific Requirements for Individual Service Handover from GERAN to UTRAN ..... | 14 |
+| 7.3.1 Speech.....                                                                   | 14 |
+| 7.3.2 Short Message Service .....                                                   | 14 |
+| 7.3.3 Cell Broadcast .....                                                          | 14 |
+
+|                               |                                                                             |           |
+|-------------------------------|-----------------------------------------------------------------------------|-----------|
+| 7.3.4                         | USSD .....                                                                  | 14        |
+| 7.3.5                         | Facsimile.....                                                              | 15        |
+| 7.3.6                         | Data Bearer Services .....                                                  | 15        |
+| 7.3.6.1                       | Circuit Switched Data .....                                                 | 15        |
+| 7.3.6.2                       | Packet Switched Data .....                                                  | 15        |
+| 7.3.7                         | Supplementary services .....                                                | 15        |
+| 7.4                           | Requirements on multiple bearer services handover from GERAN to UTRAN ..... | 15        |
+| 8                             | Cross Phase Compatibility for this release .....                            | 15        |
+| 8.1                           | Compatibility with Existing Specifications.....                             | 15        |
+| 8.2                           | Compatibility with Future 3GPP specifications.....                          | 15        |
+| 8.2.1                         | Requirements for Service Capabilities .....                                 | 16        |
+| 8.2.2                         | Inter PLMN Handover Issues.....                                             | 16        |
+| 8.2.3                         | Handover between Environments.....                                          | 16        |
+| 8.3                           | Support of Multicall with Simultaneous Voice Calls.....                     | 16        |
+| <b>Annex A (informative):</b> | <b>Illustration of elements in inter-PLMN handover .....</b>                | <b>17</b> |
+| <b>Annex B (informative):</b> | <b>Open Points on Inter-Operator Handover.....</b>                          | <b>18</b> |
+| B.2                           | Selection of Target Cells for Handover .....                                | 18        |
+| B.3                           | Network Information Exchange.....                                           | 18        |
+| B.4                           | Service Requirements .....                                                  | 18        |
+| B.5                           | Billing, Accounting and Charging Requirements .....                         | 18        |
+| <b>Annex C (informative):</b> | <b>Change history.....</b>                                                  | <b>19</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the specification;
+
+# --- 1 Scope
+
+The scope of this document includes service requirements for handover maintaining continuity of service to a wireless terminal as it moves between the radio coverage area, or "cells", associated with different base station sites. This functionality is called "handover". Handover can also occur due to change of radio resource providing a service without necessarily any change of the base stations involved. In particular, when the radio resources providing a service change from one of the UTRA radio access modes to the other (UTRA-FDD and UTRA-TDD), this is regarded as handover. Particular emphasis has been placed on the description of requirements for service continuity within UTRAN and between UTRAN and GERAN.
+
+It is a key requirement to allow for dual or multi-mode terminals to handover traffic from UTRAN to GERAN and vice versa. This document describes the service requirements for intra- and inter- system handover.
+
+The following subject areas are within the scope of these service requirements:
+
+- User perceived performance that may be influenced by handover;
+- Operational requirements relating to handover;
+- Security requirements.
+
+The requirements set forth in this document are service requirements, in that they fulfil the following:
+
+- The requirements are independent of the implementation of the UTRAN;
+- The extent to which the requirements are met are in principle verifiable using observables that are not internal to the UTRAN.
+
+## 1.1 Situations in which Service Requirements apply
+
+The service requirements in this document are as far as possible independent of the implementation. They therefore apply to situations where handover would occur regardless of how the radio access network is implemented. Situations envisaged are:
+
+- Handover within UTRAN due to change of radio resource caused by UE movement between areas covered by different transmitters;
+- Handover within UTRAN due to change of UTRA radio access mode;
+- Handover due to change of radio system.
+
+It is possible that handover (i.e. change of radio resource) will occur in other situations, for example the technical implementation of the UTRAN may necessitate it or O&M procedures initiated by the operator may force it. Requirements for these situations are not within the scope of this document, with the exception of two remarks:
+
+- Where the technical implementation of the UTRAN necessitates handover as a matter of normal operation (i.e. not related to the above situations), then services shall in no way be degraded or adversely affected;
+- The service requirements for handover occurring in situations such as O&M activity are outside the scope of this 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.278: "Service requirements for the Evolved Packet System (EPS)"
+
+# --- 3 Definitions and Abbreviations
+
+## 3.1 Definitions
+
+In addition to the following, abbreviations used in the present document are listed in TR 21.905 [1].
+
+For the purposes of the present document, the following definitions apply:
+
+**Connection mode (for a bearer service):** characterises the type of association between two endpoints as required by the bearer service for the transfer of information. A bearer service is either connection-oriented or connectionless. In a connection oriented mode, a logical association called *connection* needs to be established between the source and the destination entities before information can be exchanged between them. Connection oriented bearer services lifetime is the period of time between the establishment and the release of the connection.
+
+**Connectionless (for a bearer service):** In a connectionless bearer, no connection is established beforehand between the source and the destination entities; the source and destination network addresses need to be specified in each message. Transferred information cannot be guaranteed of ordered delivery. Connectionless bearer services lifetime is reduced to the transport of one message.
+
+**GERAN coverage:** an area where mobile cellular services are provided by a GERAN in accordance with GERAN specifications.
+
+**UTRAN coverage:** an area where mobile cellular services are provided by a UTRAN in accordance with UTRAN specifications.
+
+**Multi mode terminal:** UE that can obtain service from at least one UTRA radio access mode, and one or more different systems such as GERAN bands or possibly other radio systems such IMT-2000 family members.
+
+**Handover:** The process in which the radio access network changes the radio transmitters or radio access mode or radio system used to provide the bearer services, while maintaining a defined bearer service QoS.
+
+**Intra PLMN handover:** Handover within the same network, i.e. having the same MCC-MNC regardless of radio access system. Note: this includes the case of UTRAN  $\leftrightarrow$  GERAN handover where MCC-MNC are the same in both cases.
+
+**Inter PLMN handover:** Handover between different PLMNs, i.e. having different MCC-MNC.
+
+**Inter system handover:** Handover between networks using different radio systems , e.g. UTRAN – GERAN.
+
+**UTRA Radio access mode:** the selected UTRA radio access mode i.e. UTRA-FDD; UTRA-TDD.
+
+**Radio system:** the selected 2<sup>nd</sup> or 3<sup>rd</sup> generation radio access technology.
+
+**Service Continuity:** The means for maintaining active services during changes in the coverage areas or their characteristics without, as far as possible, the user noticing. Note that Service Continuity can be achieved by handover, cell re-selection or other mechanisms.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|    |                |
+|----|----------------|
+| UE | User equipment |
+|----|----------------|
+
+# 4 General Principles governing service continuity
+
+## 4.0 General Principles for service continuity
+
+The general principles for service continuity described in this specification refer to service continuity within the UTRAN, within the GERAN and between the UTRAN and GERAN. As a principle, the requirements on service continuity characteristics should be according to the target network on which the service is maintained.
+
+Service requirements for seamless mobility between multiple heterogeneous access systems beyond only UTRAN and GERAN are contained within TS 22.278 [2].
+
+## 4.1 Service Continuity Scenarios
+
+Service continuity shall support the following scenarios:
+
+1. Continuity of active CS services when moving within UTRAN, within GERAN and between UTRAN and GERAN coverage areas.
+2. Continuity of active GPRS sessions when moving within UTRAN, within GERAN and between UTRAN and GERAN coverage areas.
+3. Continuity of active IM Services when moving within UTRAN, within GERAN and between UTRAN and GERAN coverage areas (that support those IM services).
+
+Service continuity is not applicable for any call or session using resources specific to the source domain that cannot be maintained using resources in the target domain.
+
+## 4.2 Service Continuity requirements
+
+For all scenarios, the specifications shall cover both service continuity within the same PLMN (intra-PLMN) and between PLMNs (inter-PLMN), including the case where the PLMNs involved are operated by different network operators.
+
+It shall be possible for a user to roam between the different parts of a shared network without requiring any user intervention. The user experience while roaming in a shared network shall be comparable to the user experience while roaming in a non-shared network.
+
+### 4.2.1 Service continuity for CS
+
+The scenario numbers in this table refer to the scenarios in section 4.1.
+
+|                  |       | To CS services   |                  |
+|------------------|-------|------------------|------------------|
+|                  |       | UTRAN            | GERAN            |
+| From CS services | UTRAN | Yes - Scenario 1 | Yes - Scenario 1 |
+|                  | GERAN | Yes - Scenario 1 | Yes - Scenario 1 |
+
+### 4.2.2 Service continuity for GPRS
+
+Service continuity of GPRS sessions (conversation, streaming, interactive and background) is required within the GERAN, within the UTRAN, and between the UTRAN and GERAN (scenario 2 in section 4.1 above).
+
+Note: Service continuity for conversational, streaming and interactive GPRS sessions is not applicable to and from GERAN Release 4 or earlier, due to the lack of support for the conversational, streaming and interactive GPRS within GERAN Release 4 or earlier. In these cases, although the QoS required may not be available in the target, the bearer shall be maintained as long as possible. If the QoS supported by GERAN is not acceptable, the user/application may terminate the session.
+
+### 4.2.3 Service continuity for IM Services
+
+Service continuity of IM services is required within the GERAN, within the UTRAN, and between the UTRAN and GERAN (scenario 3 in section 4.1 above).
+
+Note: Service continuity of IM Services is not applicable to and from GERAN Release 4 or earlier as the IM Services service classes are not supported by GERAN Release 4 or earlier. In these cases, although the QoS required may not be available in the target, the bearer shall be maintained as long as possible. If the QoS supported by GERAN is not acceptable, the user/application may terminate the session.
+
+## 4.3 General Operational Considerations
+
+### 4.3.1 Coverage environment
+
+Mechanisms defined to support service continuity between different radio systems or radio access modes should effectively cope with a number of coverage scenarios:
+
+- Limited coverage in a 'sea' of coverage provided by another radio system or radio access mode, or vice versa;
+- Selective operation at a geographical boundary, with extensive UTRAN coverage on one side and extensive coverage from another radio system on the other side;
+- Geographically co-located areas of UTRAN coverage and another radio system.
+
+However the specifications should impose no restrictions or assumptions on how an operator might deploy or operate the network in both GERAN and UTRAN.
+
+### 4.3.2 Inter PLMN Handover Issues
+
+Handovers to support service continuity between PLMNs should remain an optional feature to implement. It is envisaged that handover would take place due to changing radio conditions caused e.g. by movement of the terminal causing it to leave the coverage area of a PLMN.
+
+The following networks may be involved with an inter-PLMN handover procedure. These concepts are illustrated in Annex A:
+
+- The user's *home network*, i.e. the operator where the user's subscription may be found;
+- The user's *visited network* where the subscriber user is currently registered, i.e. the network where the subscriber user has performed the last successful update location procedure. As long as the subscriber user is roaming within the home network, home and visited network are identical;
+- The user's *serving network* covering the cell that serves the subscriber. After successful completion of the update location update procedure, the serving network is identical with the visited network. After an inter-PLMN handover, the visited network is different from the serving network until a location update procedure has been successfully completed (except the case that the subscriber returns into the visited network);
+- The *target network* covering candidate target cell(s) for inter-PLMN handover. The target network has overlapping radio coverage with the serving network but not necessarily with the visited network.
+
+The minimum requirements for inter-PLMN HO are:
+
+- Continuity of an *active call* across the handover procedure, where this would be possible for intra-PLMN handover;
+- The decision whether the handover request is accepted must be taken by the target network.
+
+### 4.3.3 Charging and Network Management
+
+Means shall be standardised which allow charging records to record the time of handover in the case of inter-PLMN operator handover. Charging records must be able to reflect the level of UTRA radio access, operation mode and network type after handover.
+
+A capability to provide network management information relating to frequency of occurrence and type of handover
+
+should be defined.
+
+### 4.3.4 Cost and efficiency
+
+The UTRAN specifications shall facilitate the cost-effective implementation both on the network and on the terminal side, of multi mode operation between GERAN and UTRAN. Impacts on networks based on earlier releases shall be minimised. Such handover shall not require user intervention.
+
+### 4.3.5 Security
+
+Security requirements should embody the principle that handover shall not compromise the security of the network providing the new radio resources; the (possibly different) network providing the original radio resources; and the UE. The security mechanisms should also cater for appropriate authentication processes and meet the requirements of national administrations in terms of lawful interception.
+
+## 4.4 Performance Requirements
+
+### 4.4.1 Temporary degradation of service caused by handover
+
+During intra UTRAN handover or handover from UTRAN to GERAN, degradation of service shall be no greater than during intra GERAN handover.
+
+The duration of the discontinuity experienced by PS and CS real time services should be shorter than that in the handover of CS speech calls over GERAN.
+
+# --- 5 Requirements for Handover
+
+## 5.1 Handover due to UE Movement
+
+It should be possible to provide a technical implementation of handover such that there is no measurable impact on the quality of any service when handover due to UE movement occurs. This does not imply that all handovers will achieve this ideal. However, the specifications shall define at least one UTRA radio access mode in which this is possible given the following:
+
+- UE speed stays within limits for given service;
+- UE stays constantly within UTRA coverage of a single UTRAN.
+
+When there is handover to a new cell with different radio conditions and if a PS sessions is unable to maintain the required quality of service, the QoS of the sessions may be modified to lower quality to continue communication.
+
+## 5.2 Handover due to negotiated service requirement
+
+In order to allow the connection with the negotiated bearer- or teleservice to be established, means shall be defined, which makes it possible for the core network, to recommend to access network to handover the UE to another RAT better suited to support the desired bearer- or teleservice.
+
+## 5.3 Handover between Radio Access Modes
+
+The specifications shall permit a technical implementation of handover between radio access modes, although there may be a temporary degradation of QoS on bearer services at the time of handover.
+
+## 5.4 Cell capacity
+
+Consideration must be given services such as multimedia, which may involve use of multiple bearers. Due for example to cell loading, it may happen that a target cell cannot support the combination of bearer services provided by the current serving cell. Although all bearer services may not be handed over, the handover to another cell should not be precluded.
+
+## 5.5 Handover of a Multicall
+
+The handover event can trigger changes to individual calls in any multicall scenario.
+
+It shall be possible to handover all the calls in a multicall configuration. If the target system is UTRAN and the target cell is not able to accommodate all the calls in a multicall configuration, then the calls that are handed over are selected according to operator preferences. If the target system is GERAN, then the call that is handed over shall be selected in following order:
+
+- i The call of teleservice emergency call ;
+- ii The call of teleservice telephony;
+- iii The call of any other type according to operator preferences.
+
+Calls that cannot be handed over will be released.
+
+A change in the availability of suitable radio resources may also occur for other reasons in addition to handover.
+
+## 5.6 Access Rights
+
+It shall be possible to prevent handover to cells to which the UE does not have access rights. In this case, a handover to allowed cells shall be attempted. For this release this requirement only applies for UTRAN to UTRAN and UTRAN to GERAN handover in both A/Gb and Iu mode.
+
+## 5.7 Handover for shared networks
+
+Handover shall be supported within a shared network and between a shared network and a non-shared network.
+
+The requirements that apply to inter PLMN handover between non-shared networks shall equally apply to inter PLMN handover between shared networks as well as between a shared and a non-shared network.
+
+The network shall be able to make the decision on the most appropriate candidate for handover based on any combination of the following information:
+
+- type of subscription (e.g. prepay / postpay)
+- home network of the subscriber
+- access rights
+- connected core network
+
+NOTE: Access rights describe which of the candidates for handover a subscriber is allowed to access. The access rights are granted by the home PLMN on a subscriber by subscriber basis.
+
+# --- 6 Requirements for Handover from UTRAN to GERAN
+
+## 6.1 Operational Requirements
+
+### 6.1.2 GERAN bands
+
+The standard shall support handover to any combination of GERAN bands supported by the specifications.
+
+## 6.2 Performance Requirements
+
+The following service principles apply to performance requirements:
+
+- When the UE performs handover to GERAN then the service requirements of GERAN that relate to handover between different cells in different location areas is taken as the benchmark. It is not the intention to set more stringent service requirements for UTRAN to GERAN handover than are already commonly accepted for handover within GERAN.
+
+### 6.2.1 Detection Time of Potential GERAN Handover Candidates
+
+Means shall be defined which allow the UE to achieve as good detection time performance as the GERAN benchmark: i.e. to behave in such a way as to detect potential handover candidates as quickly as a mobile performing an intra GERAN handover is required to do so.
+
+### 6.2.2 Number of GERAN handover candidates to detect
+
+Means shall be available which allow UE to detect an equal number of GERAN handover candidates relative to the GERAN benchmark, i.e. to behave in such a way as to detect as many potential handover candidates as a mobile performing an intra GERAN handover is required to do so.
+
+### 6.2.3 Probability of Connection Loss
+
+The service requirement is that it should be possible to hand over to GERAN from UTRAN with a probability of connection loss that fulfils the corresponding service requirement for intra GERAN handover.
+
+## 6.3 Specific Requirements for Individual Services from UTRAN to GERAN
+
+### 6.3.1 Speech
+
+Handover of a CS Speech teleservice (TS11) from UTRAN to GERAN is required. This requirement also applies to emergency calls (TS12):
+
+- Any call based on the default UTRAN speech codec (AMR) shall be mapped to the FR GSM speech codec. In the case the terminal and the GERAN network support AMR and /or EFR and/or HR, it shall be the operators choice to define the appropriate mapping.
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for speech handover.
+
+### 6.3.2 Short Message Service
+
+There are no requirements related to handover for short message service.
+
+### 6.3.3 Cell Broadcast
+
+There are no requirements related to handover for cell broadcast.
+
+### 6.3.4 USSD
+
+The technical specifications shall provide means to ensure that any handover that occurs during a USSD interaction need no more affect the service than intra-GERAN handover.
+
+### 6.3.5 Facsimile
+
+It is not required that a facsimile transmission that is active between UE and network at the time of handover from UTRAN to GERAN completes successfully.
+
+### 6.3.6 Data Bearer Services
+
+#### 6.3.6.1 Circuit Switched Data
+
+Specifications shall be defined to permit the possibility of handover of a UTRAN data bearer service to GERAN
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for data bearer service handover.
+
+#### 6.3.6.2 Packet Switched Data
+
+It is required to handover a user PS context between GERAN and UTRAN. Independently of the used air interface, the user shall stay connected to an external network (internet, intranet).
+
+### 6.3.7 Supplementary Services
+
+Control and use of Supplementary Services should not be effected by a handover to GERAN.
+
+## 6.4 Requirements on multiple bearer services handover from UTRAN to GERAN
+
+Consideration must be given to services that may involve multiple bearer services. The mapping between UTRAN bearer services and GERAN bearer services will depend upon many factors such as data rate, delay constraints, error rate etc. In the event certain UTRAN bearer services cannot be handed over to GERAN, the handover of some of the bearers to maintain the service should not be precluded.
+
+In the case where user equipped with a dual mode terminal is in UTRAN coverage and has multiple PDP contexts activated (for instance to support multimedia) then it is preferable to handover one PDP context, rather than dropping all of them.
+
+As a first priority only the PDP contexts which have an associated QoS that can be supported by the GERAN should be candidates for handover.
+
+If there are still multiple PDP contexts as "handover candidates" then it shall be an operator choice which PDP context will be maintained. When roaming this decision shall be taken by the serving network. The operator may choose to either;
+
+- a) Drop all of the PDP contexts.
+- b) Choose one based upon criteria such as duration, amount of traffic transferred, etc.
+
+In case of UTRAN to GERAN handover of a **Multicall** only one call can be handed over.
+
+# --- 7 Requirements for Handover from GERAN to UTRAN
+
+## 7.1 Operational Requirements
+
+### 7.1.2 GERAN bands
+
+The standard shall support handover from any combination of GERAN bands supported by the GERAN specifications.
+
+## 7.2 Performance Requirements
+
+During handover from GERAN to UTRAN, temporary degradations shall be no greater than for intra-GERAN handovers.
+
+## 7.3 Specific Requirements for Individual Service Handover from GERAN to UTRAN
+
+### 7.3.1 Speech
+
+AMR, EFR, FR and HR calls shall be mapped to the default UTRAN speech codec.
+
+### 7.3.2 Short Message Service
+
+There are no requirements related to handover for short message service.
+
+### 7.3.3 Cell Broadcast
+
+There are no requirements related to handover for cell broadcast.
+
+### 7.3.4 USSD
+
+The technical specifications shall provide means to ensure that any handover that occurs during a USSD interaction need no more affect the service than intra-GERAN handover.
+
+### 7.3.5 Facsimile
+
+It is not required that a facsimile transmission that is active between UE and network at the time of handover from GERAN to UTRAN completes successfully.
+
+### 7.3.6 Data Bearer Services
+
+#### 7.3.6.1 Circuit Switched Data
+
+Specifications shall be defined to permit the possibility of handover of a data bearer from GERAN to UTRAN.
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for circuit switched data handover.
+
+#### 7.3.6.2 Packet Switched Data
+
+It is required to handover a user context between GERAN and UTRAN. Independently of the used radio interface, the user shall stay connected to an external network (internet, intranet). Any change in the QoS shall be seen at the service access points as a network initiated renegotiation of QoS. If the supported QoS is not acceptable, the UE/user may terminate the connection/context.
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for packet switched data handover.
+
+### 7.3.7 Supplementary services
+
+Control and use of Supplementary Services should not be effected by a handover to UTRAN.
+
+## 7.4 Requirements on multiple bearer services handover from GERAN to UTRAN
+
+Consideration must be given to services that may involve the use of multiple bearer services. For example Class A GPRS terminals will be capable of simultaneously supporting more than one data bearer services. Means shall be defined to allow handover of several data bearer services from GERAN to UTRAN
+
+# --- 8 Cross Phase Compatibility for this release
+
+This section details the cross phase compatibility requirements relating to the service requirements in this document.
+
+Note: When a change is introduced which affects the 3GPP technical specifications, 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.
+
+## 8.1 Compatibility with Existing Specifications
+
+Where the service and operational requirements in this document relate to a GERAN, compatibility is required with systems conforming to the R99 or later GERAN specifications.
+
+## 8.2 Compatibility with Future 3GPP specifications
+
+The specifications that define the technical implementation of this release should be developed in such a way that it is
+
+practical to add the requirements in this section in a backward compatible manner.
+
+### 8.2.1 Requirements for Service Capabilities
+
+3GPP standardises service capabilities, not services. As part of the service capabilities it is envisaged that applications may wish to respond to events related to handover that either has occurred, is about to occur or could potentially occur. The service capabilities described in this section should be available at least to UE hosted applications.
+
+The following list of uses is provided as an example and is not intended to be exhaustive:
+
+- An application may wish to accept or reject offered QoS;
+- An application may wish to cope to the effect that handover has on a service, for example facsimile retransmission;
+- An application may wish to preferentially choose radio resources.
+
+It is therefore required that the service capability set available to an application be able to provide an indication that handover has occurred or could occur with information about the type of handover and radio resources involved. The service capabilities should support QoS negotiation.
+
+### 8.2.2 Inter PLMN Handover Issues
+
+The minimum requirements for inter-PLMN HO are:
+
+- The ability to check with the home network whether the user is permitted to handover from the visited network to a target network.
+- Invocation of the handover procedure only occurs if the target network provides the radio channel type required for the respective call;
+- The avoidance of "network hopping", i.e. successive handover procedures between neighbouring networks for the same call;
+- The possibility of user notification of inter-PLMN HO (e.g. possible tariff change) when it occurs.
+
+### 8.2.3 Handover between Environments
+
+UMTS is expected to provide coverage in a number of environments including fixed and mobile as described in the table below. The technical specifications should not preclude the possibility of implementing these requirements in a backward compatible manner.
+
+| From \ To            | Terrestrial Cellular | Fixed/Cordless | Satellite |
+|----------------------|----------------------|----------------|-----------|
+| Terrestrial Cellular | Yes (R99)            | Yes            | Yes       |
+| Fixed/Cordless       | Yes                  | Yes            | Yes       |
+| Satellite            | Yes                  | Yes            | No        |
+
+## 8.3 Support of Multicall with Simultaneous Voice Calls
+
+In the case where Multicall is used to support multiple voice calls a handover must be attempted for each bearer that is in use. In the case where not all bearers can be supported by the destination network the related voice calls shall be automatically put on hold. After the handover is completed, the subscriber shall be able to retrieve any held voice call by invoking the Call Hold service.
+
+This requirement is dependent on the user subscribing to Call Hold.
+
+This is only required if there is more than one simultaneous speech call and this is therefore not required for this release.
+
+# Annex A (informative): Illustration of elements in inter-PLMN handover
+
+Figure 1 illustrates the above definitions taking an example of European GSM networks. The subscriber's home network is France. The visited network where the subscriber is registered in a VLR is Germany. The signalling connection between HLR and VLR is indicated by dotted lines. The calls for the subscriber are controlled by the MSC collocated to the VLR where the subscriber is registered. This MSC is called "*anchor MSC*".
+
+Handover to a different MSC may occur if the cell serving the subscriber after handover is not controlled by the anchor MSC. This MSC is called the "*serving MSC*". Even after the call has been handed over to a different MSC, the call control function remains in the anchor MSC. The signalling connection and circuit switched connection established between anchor MSC and serving MSC are indicated by a solid line.
+
+When the French subscriber registered in a German network roams near the border to the Netherlands, inter-PLMN handover may occur. In this case a Dutch network is the *target network*. After handover, the anchor MSC located in a German network continues to control the call. The German network remains the *visited network* where the subscriber is registered. The subscriber's location information stored in the HLR remains unchanged. The signalling and circuit switched connections between the anchor MSC and the previously serving MSC in the German network will be released when the User Equipment (UE) is served by a cell within a Dutch network. The Dutch network becomes the *serving network*. From the Dutch network the subscriber may be handed over to a Belgian network.
+
+![Diagram illustrating inter-PLMN handover elements across France, Germany, Netherlands, Belgium, and Luxembourg.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg)
+
+The diagram shows a map of Western Europe with France, Germany, Netherlands, Belgium, and Luxembourg. A mobile station (UE) is shown in the top left. In France (home network), there is an HLR (cylinder) and a Gateway MSC (yellow box). In Germany (visited network), there is an MSC (yellow box) and a VLR (yellow box) connected by a solid line. A dotted line connects the HLR in France to the VLR in Germany. In the Netherlands (target network), there is an MSC (pink box). In Belgium, there is another MSC (pink box). Solid lines represent circuit-switched connections between the Gateway MSC in France, the MSC in Germany, and the MSC in the Netherlands. Dotted lines represent signalling connections between the HLR in France and the various MSCs and VLRs.
+
+Diagram illustrating inter-PLMN handover elements across France, Germany, Netherlands, Belgium, and Luxembourg.
+
+Fig. 1: Example for Inter-PLMN handover
+
+Figure 1: Example for inter-PLMN handover
+
+# --- Annex B (informative): Open Points on Inter-Operator Handover
+
+The requirements outlined below are likely to need further elaboration, although these may be outside the scope of service requirements.
+
+## --- B.2 Selection of Target Cells for Handover
+
+A mechanism is envisaged to support the selection of the target cell for handover. The target cell may be part of the serving network or part of another network.
+
+## --- B.3 Network Information Exchange
+
+A mechanism is envisaged to support the exchange of network information between different operators. Two categories of network information are identified:
+
+- static information, for example, neighbour cell lists, interconnecting traffic and signalling links, etc.;
+- dynamic information, for example real-time signalling information related to target cell selection, etc.
+
+## --- B.4 Service Requirements
+
+FFS.
+
+[There is a need to identify which services can be maintained during handover and the interactions of services across network boundaries]
+
+## --- B.5 Billing, Accounting and Charging Requirements
+
+FFS.
+
+# Annex C (informative): Change history
+
+| Document history |               |                                                                                                                                                            |
+|------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <Version>        | <Date>        | <Milestone>                                                                                                                                                |
+| 0.0.1            | 29 Oct 98     | First Draft for tdoc                                                                                                                                       |
+| 0.0.2            | 5 Jan 98      | Evolved from tdoc 3 then 7 of SMG 1 handover ad hoc                                                                                                        |
+| 0.0.3            | 6 Jan 98      | evolved from tdoc 20 of SMG1 handover ad hoc                                                                                                               |
+| 0.0.4            | 7 Jan 98      | evolved from tdoc 35 of SMG1 handover adhoc                                                                                                                |
+| 0.0.5            | 8 Jan 98      | Evolved from tdoc 45 of SMG1 handover adhoc                                                                                                                |
+| 1.0.0            | 27 January    | To be presented as version 1.0.0 to SMG#28 for Approval                                                                                                    |
+| 1.1.0            | 5 Mar 99      | - new requirement for inter-operator handover, as demanded by SMG<br>- removes text on security requirements by referencing 33.21<br>- editorial revisions |
+| 1.2.0            | 22 Mar 99     | 1 Initial draft for email handover ad hoc 22-27 Mar.<br>-                                                                                                  |
+| 1.3.0            | 24 Mar 99     | Clarify inter-operator handover requiremetn                                                                                                                |
+| 1.4.0            | 26 Mar 99     | Proposed as draft version 2.0.0                                                                                                                            |
+| 2.0.0            | 12 Apr 99     | Draft version 2.0.0                                                                                                                                        |
+| 2.0.1            | 12 Apr 99     | Editorially equivalent 2.0.0, with editorial comments removed                                                                                              |
+| 2.0.2            | 16 April 99   | Editorial review                                                                                                                                           |
+| 3.0.0            |               |                                                                                                                                                            |
+| 3.1.0            | October 1999  | Inclusion of CRs at SA#5                                                                                                                                   |
+| 3.2.0            | December 1999 | Inclusion of CRs at SA#6                                                                                                                                   |
+| 3.3.0            | June 2000     | Inclusion of CRs at SA#8                                                                                                                                   |
+| 4.0.0            | October 2000  | Inclusion of CRs at SA#9                                                                                                                                   |
+| 4.1.0            | January 2001  | Inclusion of CRs at SA#10                                                                                                                                  |
+| 4.2.0            | March 2001    | Inclusion of CRs at SA#11                                                                                                                                  |
+
+| Change history |          |          |        |     |     |     |     |                                        |       |       |    |
+|----------------|----------|----------|--------|-----|-----|-----|-----|----------------------------------------|-------|-------|----|
+| TSG SA#        | SA Doc.  | SA1 Doc  | Spec   | CR  | Rev | Rel | Cat | Subject/Comment                        | Old   | New   | WI |
+|                |          |          |        |     |     |     |     |                                        |       |       |    |
+| SP-05          | SP-99436 | S1-99500 | 22.129 | 002 |     | R99 | F   | SMS handover requirement clarification | 3.0.0 | 3.1.0 |    |
+| SP-05          | SP-99436 | S1-99516 | 22.129 | 003 |     | R99 | D   | Removal of out-of-date appendix        | 3.0.0 | 3.1.0 |    |
+
+| Change history |           |           |        |      |     |       |     |                                                                                                                    |        |        |           |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|--------------------------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                                                                    | Old    | New    | WI        |
+| SP-05          | SP-99436  | S1-99533  | 22.129 | 004  |     | R99   | D   | Editorial improvements of definitions and alignment of terminology                                                 | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99436  | S1-99540  | 22.129 | 005  |     | R99   | C   | To elucidate 1-1 handover principle for R99                                                                        | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99436  | S1-99541  | 22.129 | 006  |     | R99   | D   | Clarification of the scope of mandatory requirements                                                               | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99483  | S1-99565  | 22.129 | 007  | 1   | R99   | C   | Removes all non-R99 requirements, by changing them into Cross phase compatibility requirements which apply to R99. | 3.0.0  | 3.1.0  |           |
+| SP-06          | SP-99553  | S1-99877  | 22.129 | 008  |     | R99   | D   | Editorial CR to 22.129                                                                                             | 3.1.0  | 3.2.0  |           |
+| SP-06          | SP-99523  | S1-991019 | 22.129 | 009  |     | R99   | D   | 3G/2G handover in the PS Domain                                                                                    | 3.1.0  | 3.2.0  |           |
+| SP-06          | SP-99523  | S1-991066 | 22.129 | 010  |     | R99   | B   | Handover of a Multicall                                                                                            | 3.1.0  | 3.2.0  |           |
+| SP-06          | SP-99521  | S1-99868  | 22.129 | 011  |     | R99   | C   | Performance requirements for real time services and requirements for handover between UMTS and GPRS                | 3.1.0  | 3.2.0  |           |
+| SP-08          | SP-000205 | S1-000349 | 22.129 | 012  |     | R99   | F   | Alignment of handover requirements for Multicall                                                                   | 3.2.0  | 3.3.0  |           |
+| SP-09          | SP-000426 | S1-000574 | 22.129 | 013  |     | R99   | F   | Removal of requirements for SoLSA support                                                                          | 3.3.0  | 3.4.0  |           |
+| SP-09          | SP-000389 | S1-000613 | 22.129 | 014  |     | R4    | B   | Bearer Modification without pre-notification                                                                       | 3.3.0  | 4.0.0  |           |
+| SP-10          | SP-000534 | S1-000863 | 22.129 | 015  |     | R99   | F   | Handover requirements                                                                                              | 3.4.0  | 3.5.0  |           |
+| SP-10          | SP-000534 | S1-000864 | 22.129 | 016  |     | Rel-4 | A   | Handover requirements                                                                                              | 4.0.0  | 4.1.0  | TEI4      |
+| SP-11          | SP-010061 | S1-010251 | 22.129 | 017  |     | Rel-4 | D   | Editorial CR to correct references to releases                                                                     | 4.1.0  | 4.2.0  | CORRECT   |
+| SP-12          | SP-010264 | S1-010553 | 22.129 | 018  |     | Rel-4 | F   | Bearer modification without pre-modification                                                                       | 4.2.0  | 4.3.0  | BMWPN     |
+| SP-12          | SP-010245 | S1-010353 | 22.129 | 019  |     | Rel-4 | F   | Inter PLMN handover                                                                                                | 4.2.0  | 4.3.0  | Handover  |
+| SP-13          | SP-010434 | S1-010859 | 22.129 | 020  | 1   | Rel-5 | B   | Release 5 IMS Service Continuity Requirements                                                                      | 4.3.0  | 5.0.0  | IMS       |
+| SP-14          | SP-010670 | 1289      | 22.129 | 025  |     | Rel-5 | A   | Multicall handover requirements                                                                                    | 5.0.0  | 5.1.0  |           |
+| SP-16          | SP-020250 | S1-021093 | 22.129 | 026  |     | Rel-5 | F   | CR to TS 22.129 on access rights in connected mode                                                                 | 5.1.0  | 5.2.0  | TEI       |
+| SP-19          | SP-030035 | S1-030271 | 22.129 | 027  | -   | Rel-6 | B   | Netshare CR to TS 22.129 on Requirements for Network Sharing in Rel-6                                              | 5.2.0  | 6.0.0  | NTShar-CR |
+| SP-22          | SP-030704 | S1-031300 | 22.129 | 028  | 4   | Rel-6 | B   | Service based handover/assignment                                                                                  | 6.0.0  | 6.1.0  | TEI       |
+| SP-31          | -         | -         | 22.129 | -    | -   | Rel-7 |     | Rel-7 created as a result of applying CR 0029 from SA #31 to Rel-6 in order to create Rel-8                        | 6.1.0  | 7.0.0  | -         |
+| SP-31          | SP-060208 | -         | 22.129 | 0029 | 1   | Rel-8 | F   | Introduction of reference to the AIPN Stage 1 in TS 22.129                                                         | 6.1.0  | 8.0.0  | AIPN      |
+| SP-38          | SP-070855 | S1-071839 | 22.129 | 0030 | 1   | Rel-8 | B   | Introduction of reference to EPS Stage 1 in TS 22.129                                                              | 8.0.0  | 8.1.0  | AIPN-SAE  |
+| SP-46          | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-9 by MCC                                                                                            | 8.1.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 |           |
+| 2014-10        | -         | -         | -      | -    | -   | -     | -   | Update to Rel-12 version (MCC)                                                                                     | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-13 by MCC                                                                                           | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22135/raw.md

@@ -0,0 +1,630 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multicall; Service description; 3GPP TS 22.133 V13.0.0 (2015-12)** ---
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced Pro logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller, red, sans-serif font. Above the text "Advanced Pro" are three green curved lines representing signal waves. A small "TM" trademark symbol is located to the bottom right of the "e".
+
+LTE Advanced Pro logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo. It consists of the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the top by a single horizontal line. Below the "P" is a small red graphic of three curved lines, similar to the signal waves in the LTE logo. A small "TM" trademark symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+## **Keywords**
+
+LTE, UMTS, multicall, supplementary service;  
+stage 1
+
+## **3GPP**
+
+## **Postal address** ---
+
+## **3GPP support office address** ---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## **Internet** ---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                                                               |    |
+|-----------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                | 5  |
+| 1 Scope.....                                                                                  | 6  |
+| 2 References.....                                                                             | 6  |
+| 3 Definitions, symbols and abbreviations.....                                                 | 6  |
+| 3.1 Definitions.....                                                                          | 6  |
+| 4 Description.....                                                                            | 7  |
+| 4.1 Description of multicall.....                                                             | 7  |
+| 4.2 Applicability to telecommunication services.....                                          | 7  |
+| 5 Functional requirements.....                                                                | 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 Call related procedures.....                                                              | 8  |
+| 5.9.1 Terminating CS call.....                                                                | 8  |
+| 5.9.2 Originating CS call.....                                                                | 9  |
+| 5.10 Charging requirements.....                                                               | 9  |
+| 6 Exceptional procedures or unsuccessful outcome .....                                        | 9  |
+| 6.1 Exceptional operation or unsuccessful outcome .....                                       | 9  |
+| 6.2 Registration .....                                                                        | 9  |
+| 6.3 Erasure.....                                                                              | 9  |
+| 6.4 Activation.....                                                                           | 10 |
+| 6.5 Deactivation .....                                                                        | 10 |
+| 6.6 Invocation.....                                                                           | 10 |
+| 6.7 Interrogation.....                                                                        | 10 |
+| 6.8 Roaming in non-supporting networks.....                                                   | 10 |
+| 7 Interaction with other services .....                                                       | 10 |
+| 7.1 Line Identification.....                                                                  | 10 |
+| 7.1.1 Calling Line Identification Presentation (CLIP) .....                                   | 10 |
+| 7.1.2 Calling Line Identification Restriction (CLIR) .....                                    | 10 |
+| 7.1.3 Connected Line Identification Presentation (COLP).....                                  | 10 |
+| 7.1.4 Connected Line Identification Restriction (COLR) .....                                  | 10 |
+| 7.2 Call Forwarding.....                                                                      | 11 |
+| 7.2.1 Call Forwarding Unconditional (CFU) .....                                               | 11 |
+| 7.2.2 Call Forwarding on Busy (CFB) .....                                                     | 11 |
+| 7.2.3 Call Forwarding on No Reply (CFNRy) .....                                               | 11 |
+| 7.2.4 Call Forwarding on Not Reachable (CFNRc) .....                                          | 11 |
+| 7.3 Call Completion.....                                                                      | 11 |
+| 7.3.1 Call Hold (CH) .....                                                                    | 11 |
+| 7.3.2 Call Waiting (CW) .....                                                                 | 11 |
+| 7.4 Multi Party (MPTY).....                                                                   | 12 |
+| 7.5 Closed User Group (CUG).....                                                              | 12 |
+| 7.6 Advice of Charge (AoC).....                                                               | 12 |
+| 7.7 Call Barring.....                                                                         | 12 |
+| 7.7.1 Barring of all outgoing calls .....                                                     | 12 |
+| 7.7.2 Barring of outgoing international calls.....                                            | 12 |
+| 7.7.3 Barring of outgoing international calls except those directed to the HPLMN country..... | 12 |
+| 7.7.4 Barring of all incoming calls .....                                                     | 12 |
+| 7.7.5 Barring of incoming calls when roaming .....                                            | 12 |
+| 7.8 Explicit Call Transfer (ECT).....                                                         | 12 |
+
+|                               |                                                                       |           |
+|-------------------------------|-----------------------------------------------------------------------|-----------|
+| 7.9                           | Completion of Call to Busy Subscriber (CCBS).....                     | 13        |
+| 7.10                          | Multiple Subscriber Profile (MSP) .....                               | 13        |
+| 7.11                          | Calling Name Presentation (CNAP) .....                                | 13        |
+| 7.12                          | User-to-User Signalling (UUS).....                                    | 13        |
+| 7.13                          | enhanced Multi-Level Precedence and Pre-emption service (eMLPP) ..... | 13        |
+| 7.14                          | Call Deflection (CD).....                                             | 13        |
+| 8                             | Interaction with other network features and services.....             | 13        |
+| 8.1                           | CAMEL.....                                                            | 13        |
+| 8.2                           | IST .....                                                             | 13        |
+| 8.3                           | ODB .....                                                             | 13        |
+| 8.4                           | Emergency Calls .....                                                 | 13        |
+| <b>Annex A (normative):</b>   | <b>Busy definition .....</b>                                          | <b>15</b> |
+| <b>Annex B (informative):</b> | <b>Cross Phase Compatibility .....</b>                                | <b>16</b> |
+| B.1                           | Compatibility With Existing Standards .....                           | 16        |
+| B.2                           | Compatibility With Future Releases.....                               | 16        |
+| B.2.1                         | Multicall configuration.....                                          | 16        |
+| B.2.2                         | Several simultaneous speech calls / bearers.....                      | 17        |
+| B.2.3                         | CCBS.....                                                             | 17        |
+| <b>Annex C (informative):</b> | <b>Change history.....</b>                                            | <b>18</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document presents describes Multicall supplementary service.
+
+The general aspects, including definitions and recommended provision, of the description of the 3GPP Supplementary Services are given in 3GPP TS 22.004.
+
+# --- 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 circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
+- [2] 3GPP TS 22.004: "General on Supplementary Services".
+- [3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".
+- [4] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [5] 3GPP TS 22.100: "UMTS Phase 1 Release 99".
+- [6] 3GPP TS 22.129: "Handover Requirement between UTRAN and GERAN or other Radio Systems".
+- [7] 3GPP TS 22.097: "Multiple Subscriber Profile (MSP) ".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+**CS Call:** Circuit switched call. A call routed through CS domain. CS call can be for example a speech call, fax call or data call. One call shall only use one bearer at the time
+
+**Multiparty:** Supplementary Service for speech conference service
+
+**N<sub>cs\_MO</sub>:** maximum number of simultaneous mobile originating CS calls. The value of The Value of N<sub>cs\_MO</sub> is 7. If N<sub>cs\_MO</sub> has been reached, no more MO calls can be set-up
+
+**N<sub>cs\_MT</sub>:** Maximum number of simultaneous mobile terminating CS calls. The value of N<sub>cs\_MT</sub> is 7. If N<sub>cs\_MT</sub> has been reached, additional MT call attempts shall fail without any indication to the called subscriber
+
+**N<sub>br</sub>:** Maximum number of simultaneous CS bearers. The value of N<sub>br</sub> is the smallest value within the N<sub>br\_User</sub>, N<sub>br\_UE</sub>, and N<sub>br\_SN</sub>
+
+**N<sub>br\_User</sub>:** Maximum number of simultaneous CS bearers allowed, as defined by the user within the limits given by N<sub>br\_SB</sub>
+
+**N<sub>br\_SB</sub>:** Maximum number of simultaneous CS bearers allowed, defined by the service provider in the Multicall subscription
+
+**N<sub>br\_UE</sub>:** Maximum number of simultaneous CS bearers supported by the UE
+
+$N_{br\_SN}$ : Maximum number of simultaneous CS bearers supported by the serving network
+
+---
+
+# 4 Description
+
+## 4.1 Description of multicall
+
+The Multicall supplementary service enables a mobile subscriber to have several simultaneous CS calls, each call using its own dedicated bearer.
+
+Only one CS bearer can used for speech at any one times.
+
+A speech call is one of TS11 (Telephony), TS12 (Emergency Calls), and TS61 (Alternate speech/fax). If the bearer capability information is not available, e.g. the call is originated/transited by a PSTN, the basic service cannot be deduced and the network shall, for multicall purposes, handle the call as telephony.
+
+A held call shall be regarded as using the bearer used while the call was active.
+
+NOTE: The 3GPP protocol architecture allows several parallel CS calls, the limitation being that there is only one traffic channel in GERAN, which the different CS calls share. This is facilitated by e.g. the Call Waiting, Call Hold, Call Transfer and Multiparty Supplementary Services. Call configurations related to supplementary services are not considered as Multicall. See clause 7 for interaction.
+
+It shall be possible for each CS call to use a dedicated bearer of independent traffic and performance characteristics. It shall be possible to release each active CS call independently of any other CS call.
+
+## 4.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004.
+
+---
+
+# 5 Functional requirements
+
+## 5.1 Provision
+
+Multicall is provided by prior arrangement with the service provider.
+
+Multicall shall be provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not to any subset of these BS.
+
+When the Multicall supplementary service is provisioned the maximum number of simultaneous CS bearers available to the subscriber ( $N_{br\_SB}$ ) shall be defined as part of the subscription. The value for  $N_{br\_SB}$  shall in the range from 2 up to 7.
+
+## 5.2 Withdrawal
+
+It shall be possible to withdraw the Multicall supplementary service subscription on request of the subscriber or for administrative reasons.
+
+## 5.3 Registration
+
+The user shall be able to modify the maximum number of CS bearers available ( $N_{br\_User}$ ) within the limitations set by the service provider. ( $N_{br\_SB}$ ).
+
+If the subscriber attempts to register a value for  $N_{br\_User}$  that is higher than the value of  $N_{br\_SB}$ , the request shall be rejected and the subscriber shall be informed on the unsuccessful outcome on the request.
+
+## 5.4 Erasure
+
+Data related to the Multicall supplementary service shall be erased by the service provider as a result of withdrawal.
+
+## 5.5 Activation
+
+The Multicall supplementary service shall be activated by the service provider as a result of provision.
+
+## 5.6 Deactivation
+
+The Multicall supplementary service shall be deactivated by the service provider as a result of withdrawal.
+
+## 5.7 Invocation
+
+The Multicall supplementary service shall be invoked by the system when at least one call is in progress and another call with a dedicated bearer is to be set up. The Multicall service applies to mobile originating and mobile terminating calls.
+
+## 5.8 Interrogation
+
+The user shall be able to interrogate the network for the values of  $N_{br\_User}$ ,  $N_{br\_SB}$  and  $N_{br\_SN}$ .
+
+## 5.9 Call related procedures
+
+### 5.9.1 Terminating CS call
+
+The indication of a terminating CS call to the mobile terminal will be done by the Multicall supplementary service until either the maximum number of bearer ( $N_{br}$ ) or the maximum number of CS mobile terminating calls ( $N_{cs\_MT}$ ) has been reached.
+
+If the maximum number of terminating calls ( $N_{cs\_MT}$ ) has been reached, and additional terminating call shall be reject without any indication to the subscriber.
+
+If the maximum number of bearers ( $N_{br}$ ) has been reached an additional terminating call will be only indicated to the user if the user has the Call Waiting supplementary service active, see chapter 7.4.2 for interactions with Call Waiting.
+
+If  $N_{br}$  and  $N_{cs\_MT}$  havenot been reached, a terminating call is indicated to the user and she may react in the following way:
+
+- a) Accept the terminating call:
+  - The user/user applications shall have the possibility to allocate a new bearer for the terminating call.
+  - If the user has the Call Hold SS active, the user shall have the possibility to reuse/share an already established bearer (e.g. release existing calls or put an speech on hold and accept the terminating call).
+- b) Rejecting the terminating call:
+  - If the user rejects the terminating call the call shall be released in a normal way.
+- c) Ignore the incoming call:
+  - If the user ignores the indication of the terminating call (i.e. neither accepts nor rejects it ), the normal call handling shall apply, e.g. after the Alerting Timer expires the call will be released.
+
+If there is a terminating speech call attempt and an ongoing speech call (active or held), the terminating call shall not be indicated to user by the Multicall service. The Call waiting call SS shall be invoked if applicable, see chapter 7.4.2 for interactions with Call Waiting SS.
+
+The user can have possibility to reuse/share a bearer only when she is provisioned for Call Hold SS. See subclause 7.4.1 for interaction with Call Hold SS.
+
+### 5.9.2 Originating CS call
+
+If neither  $N_{br}$  nor  $N_{cs\_MO}$  have not been reached and the user wants to establish a new originating CS call she may act in the following way:
+
+- a) allocate a new bearer for the originating call;
+- b) reuse/share an already established bearer (e.g. to put an speech on hold and set-up a new call).
+
+The user can have possibility to reuse/share a bearer only when she is provisioned for Call Hold SS. See subclause 7.4.1 for interaction with Call Hold SS. The mobile terminal shall not originate a speech call requesting a new bearer when there is already an active speech call.
+
+## 5.10 Charging requirements
+
+Each of the calls using a dedicated bearer shall be charged individually.
+
+Allocation of a dedicated bearer shall be visible in the charging data.
+
+# --- 6 Exceptional procedures or unsuccessful outcome
+
+## 6.1 Exceptional operation or unsuccessful outcome
+
+The number of simultaneous CS bearers supported by the system may vary in different regions. For instance, after handover the number of simultaneous bearers available to the served subscriber may be lower than the number of already established bearers. Such events shall trigger changes to individual calls in any multicall scenario.
+
+The handover requirements for multicall are specified in 3GPP TS 22.129 [6].
+
+## 6.2 Registration
+
+If the system cannot accept a registration request, the served mobile subscriber shall receive a notification that Multicall registration was not successful. Possible causes are:
+
+- service not subscribed to;
+- $N_{br\_User} > N_{br\_SB}$ ;
+- insufficient information.
+
+## 6.3 Erasure
+
+No exceptional operation identified.
+
+## 6.4 Activation
+
+No exceptional operation identified.
+
+## 6.5 Deactivation
+
+No exceptional operation identified.
+
+## 6.6 Invocation
+
+If the served subscriber attempts to set up a new call with a dedicated bearer while the maximum number of bearers available to the subscriber ( $N_{br}$ ) has been reached, the call attempt shall be rejected by normal procedures, indicating that no more bearers are available.
+
+## 6.7 Interrogation
+
+When a mobile subscriber who is not provided with the Multicall supplementary service interrogates the service data of the Multicall supplementary service, she shall be notified that she is not subscribed to the service.
+
+## 6.8 Roaming in non-supporting networks
+
+Roaming into networks not supporting the Multicall supplementary service shall be possible. The served subscriber will not have any access to the Multicall supplementary service and the system should behave accordingly.
+
+When the served subscriber performs any procedure related to Multicall service as described in the clauses above while roaming in a non-supporting network, she shall be notified that the service is not available.
+
+# --- 7 Interaction with other services
+
+## 7.1 Line Identification
+
+### 7.1.1 Calling Line Identification Presentation (CLIP)
+
+No impact, i.e. CLIP shall be provided with all calls.
+
+### 7.1.2 Calling Line Identification Restriction (CLIR)
+
+No impact, i.e. CLIR shall be provided with all calls.
+
+### 7.1.3 Connected Line Identification Presentation (COLP)
+
+No impact, i.e. COLP shall be provided with all calls.
+
+### 7.1.4 Connected Line Identification Restriction (COLR)
+
+No impact, i.e. COLR shall be provided with all calls.
+
+## 7.2 Call Forwarding
+
+### 7.2.1 Call Forwarding Unconditional (CFU)
+
+No impact.
+
+### 7.2.2 Call Forwarding on Busy (CFB)
+
+No impact.
+
+NOTE: CFB shall be invoked when the network detects a NDUB condition. The maximum number of bearers available to the subscriber ( $N_{br}$ ) affects the NDUB condition. For the NDUB definition specific for Multicall, see annex A.
+
+This means that for the case of  $N_{br} = 1$ , the system behaviour shall be the same as for a subscriber who is not provided with the Multicall service.
+
+### 7.2.3 Call Forwarding on No Reply (CFNRy)
+
+No impact.
+
+### 7.2.4 Call Forwarding on Not Reachable (CFNRc)
+
+No impact.
+
+## 7.3 Call Completion
+
+### 7.3.1 Call Hold (CH)
+
+No impact, i.e. it shall be possible to put an established speech call on hold.
+
+Irrespective of whether the maximum number of CS bearers ( $N_{br}$ ) is reached or not, and a terminating call is indicated to the user, she shall be able to accept the terminating call by applying the Call Hold service to an active speech call. By that she makes the bearer of the held call available to the new call.
+
+NOTE 1: This means that for the case of  $N_{br} = 1$ , the system behaviour shall be the same as for a subscriber who is not provided with the Multicall service.
+
+NOTE 2: There is no change to the maximum number of held calls allowed for the Multicall supplementary service. The maximum number of held calls is still 1 per a subscriber.
+
+### 7.3.2 Call Waiting (CW)
+
+When the subscriber has at least one ongoing call and a new terminating call is speech; then Call Waiting shall be invoked if:
+
+- 1) there is an active speech call and Call Waiting is active and operative for speech or;
+- 2) there is a held speech call, with no active call on the same bearer, and Call Waiting is active and operative for speech or;
+- 3) there is a held speech call, with an active non-speech call on the same bearer, and Call Waiting is active and operative for that non-speech basic service or;
+- 4) there are no speech calls (including a call on hold), the maximum number of bearers ( $N_{br}$ ) has been reached and Call Waiting is active and operative for at least one of the basic services currently in use.
+
+When the subscriber has at least one ongoing call and a new terminating call is not speech; then Call Waiting shall be invoked if the maximum number of bearers ( $N_{br}$ ) has been reached and Call Waiting is active and operative for at least one of the basic services currently in use.
+
+NOTE: There is no change to the maximum number of waiting calls allowed for the Multicall service. The maximum number of waiting calls is still 1 per a subscriber.
+
+## 7.4 Multi Party (MPTY)
+
+No Impact.
+
+The number of MPTY member may be limited by  $N_{cs\_MO}$ ,  $N_{cs\_MT}$  and  $N_{cs}$ .
+
+## 7.5 Closed User Group (CUG)
+
+No impact.
+
+## 7.6 Advice of Charge (AoC)
+
+The subscriber shall receive the AoC indication individually for each CS call.
+
+For the AoCC service, the ACM (Accumulated Call Meter as defined in TS 22.024) shall reckon the sum of the charge generated by all simultaneous CS calls.
+
+## 7.7 Call Barring
+
+No impact.
+
+### 7.7.1 Barring of all outgoing calls
+
+No impact.
+
+### 7.7.2 Barring of outgoing international calls
+
+No impact.
+
+### 7.7.3 Barring of outgoing international calls except those directed to the HPLMN country
+
+No impact.
+
+### 7.7.4 Barring of all incoming calls
+
+No impact.
+
+### 7.7.5 Barring of incoming calls when roaming
+
+No impact.
+
+## 7.8 Explicit Call Transfer (ECT)
+
+No impact.
+
+## 7.9 Completion of Call to Busy Subscriber (CCBS)
+
+The definition of the IDLE state of subscriber A and destination B is not modified, i.e. a subscriber is considered to be IDLE when all the bearers (calls) for her have been released.
+
+A subscriber to whom CCBS can be invoked shall be regarded as NDUB under the specific NDUB condition for Multicall (See Annex A).
+
+## 7.10 Multiple Subscriber Profile (MSP)
+
+No impact. The Multicall supplementary service shall be provisioned on a per subscriber basis. Nbr\_SN, Nbr\_SB, and Nbr\_user shall apply over all profiles.
+
+## 7.11 Calling Name Presentation (CNAP)
+
+No impact.
+
+## 7.12 User-to-User Signalling (UUS)
+
+No Impact
+
+## 7.13 enhanced Multi-Level Precedence and Pre-emption service (eMLPP)
+
+No impact.
+
+## 7.14 Call Deflection (CD)
+
+No impact.
+
+# --- 8 Interaction with other network features and services
+
+## 8.1 CAMEL
+
+No impact.
+
+## 8.2 IST
+
+No impact.
+
+## 8.3 ODB
+
+No impact.
+
+## 8.4 Emergency Calls
+
+The network shall handle emergency call at first priority. When a user originates an emergency call, the network shall behave as follows:
+
+- The network, which supports Multicall, shall accept the emergency call within the serving network capability regardless of Multicall subscription limitation to the user.
+- The MS shall ensure that an emergency call setup request is acceptable to a serving network which does not support multicall, if necessary by releasing one or more existing call.
+
+# --- Annex A (normative): Busy definition
+
+NDUB (Network Determined User Busy) occurs when:
+
+1. The maximum number of mobile terminating calls ( $N_{cs\_MT}$ ) has been reached (NOTE 1).
+2. The maximum number of bearers ( $N_{br}$ ) has been reached and the maximum number of waiting calls has been reached (NOTE 2, NOTE3).
+
+NOTE 1: This can occur even if bearers are still available, e.g. when the MS is engaged in MPTY SS. If the maximum number of mobile terminating calls ( $N_{cs\_MT}$ ) has been reached, the Call Waiting SS cannot be invoked.
+
+NOTE 2: If Call Waiting is provisioned and activated, and when the maximum number of bearers has been reached the Call Waiting SS can be invoked. This case is not regarded as NDUB. See subclause 7.3.2 for interaction with Call Waiting SS.
+
+NOTE 3: According to the speech bearer number limitation, the incoming speech call shall be regarded as encountering NDUB when the MS is engaged in a speech call (including a held call) and Call Waiting SS is not provisioned and activated for the user, irrespective of the further availability of bearers for the user. For the condition under which Call Waiting SS shall be invoked in this case, see subclause 7.3.2.
+
+For User Determined User Busy (UDUB) condition see TS 22.001 Annex C.
+
+# Annex B (informative): Cross Phase Compatibility
+
+This section details the cross phase compatibility requirements relating to the service requirements in this document.
+
+NOTE: When a change is introduced which affects the 3GPP specifications, 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.
+
+## B.1 Compatibility With Existing Standards
+
+Where the service and operational requirements in this document relate to core network functionality, compatibility is required.
+
+Multicall mechanisms are not applicable for GERAN.
+
+## B.2 Compatibility With Future Releases
+
+It is envisaged that 3GPP standards will evolve in future releases, for example with the addition of new service requirements. The standards which define the technical implementation should be developed in such a way that it is practical to add the requirements in this section in a backward compatible manner.
+
+Following chapters include requirements that are foreseen for future release.
+
+### B.2.1 Multicall configuration
+
+When having one active CS call and one held call on the same bearer. It shall be possible to create a new CS bearer and to move one of the calls to the new bearer, resulting both calls being active within the limits set by the operator/user and within the capability of the terminal. See figure 2: Split of bearer.
+
+When having two calls (multicall) on the separate bearers. It shall be possible to join both calls to one of the two bearers, put the one of the calls to hold and to release unused CS bearer. It shall be possible to select which call to put on hold. See figure 2: Combination of bearers. *(Note: there is no clear end-user service requirement for this feature at time being).*
+
+NOTE: Due to that only speech calls can be put on hold, so one of the two active Cs calls has to be a speech call.
+
+![Figure 2: Illustration for split of bearer and combination of bearers. The diagram shows two states: 'Call Hold SS' and 'Multicall'. In 'Call Hold SS', 'Active CALL1' and 'Hold CALL2' are connected to a single 'BEARER'. In 'Multicall', 'CALL1' and 'CALL2' are connected to 'BEARER1' and 'BEARER2' respectively. Arrows labeled 'Split' and 'Combine' show the transition between these states.](57f8e374b0e99c488f68c46b713ffc64_img.jpg)
+
+```
+
+graph LR
+    subgraph CallHoldSS [Call Hold SS]
+        CALL1((Active CALL1)) --- BEARER((BEARER))
+        CALL2((Hold CALL2)) --- BEARER
+    end
+    subgraph Multicall [Multicall]
+        CALL1_2((CALL1)) --- BEARER1((BEARER1))
+        CALL2_2((CALL2)) --- BEARER2((BEARER2))
+    end
+    CallHoldSS -- Split --> Multicall
+    Multicall -- Combine --> CallHoldSS
+  
+```
+
+Figure 2: Illustration for split of bearer and combination of bearers. The diagram shows two states: 'Call Hold SS' and 'Multicall'. In 'Call Hold SS', 'Active CALL1' and 'Hold CALL2' are connected to a single 'BEARER'. In 'Multicall', 'CALL1' and 'CALL2' are connected to 'BEARER1' and 'BEARER2' respectively. Arrows labeled 'Split' and 'Combine' show the transition between these states.
+
+Figure 2: Illustration for split of bearer and combination of bearers
+
+### B.2.2 Several simultaneous speech calls / bearers
+
+A Key requirements for multicall is to allow several simultaneous CS calls with dedicated bearers. The most important usage scenario is to allow several CS data bearers to be bind at application level resulting to higher than 64kbits/s data rates. Another important feature is to allow simultaneous speech and data calls.
+
+It's been proposed that the multicall feature could be introduced in a phased manner; meaning that in the first phase, i.e. 3GPP release 99 does only support one active speech call at a time. However, Call control should not prohibit a complete set of multiple speech bearer services in future releases and UTRAN shall be designed in a flexible way to
+
+support multiple speech bearers. The specific NDUB definition for speech call shall be removed when multiple speech call is supported. At this release , Supplementary Services Call Waiting, Multiparty and Call Hold are used to offer simultaneous speech calls to user.
+
+N<sub>cs</sub> may be extended in further releases.
+
+If multiple simultaneous speech calls are supported in the future then the Call Hold service may be used to reconfigure the number of bearers supporting speech calls if required during handover. e.g. in the case of handover to GERAN where only one speech call can be active at a time. This requirement is dependent on the user subscribing to Call Hold.
+
+### B.2.3 CCBS
+
+At this release CCBS no enhancements for CCBS is required.
+
+In the future releases the definition of IDLE state of subscriber A and destination B should be modified in away that the IDLE state is reach even if there are active CS calls but the maximum limit of CS calls is not reached.
+
+# Annex C (informative): Change history
+
+| Date          | Version | Comment                                                                                                                                                                                                                                                                                                                       |
+|---------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 19 Mar. 1999  | 0.0.1   | First draft by the editor (Tommi Kokkola / Nokia)                                                                                                                                                                                                                                                                             |
+| 30 Mar. 1999  | 0.1.0   | Output from S1 Multicall ad hoc                                                                                                                                                                                                                                                                                               |
+| 6 Apr. 1999   | 0.1.0   | Minor modifications by the editor. Proposed version 1.0.0                                                                                                                                                                                                                                                                     |
+| 19 Apr. 1999  | 1.0.0   | For information to 3GPP TSG SA#3                                                                                                                                                                                                                                                                                              |
+| 10. Jun. 1999 | 1.1.0   | Draft from editor for the email meeting.                                                                                                                                                                                                                                                                                      |
+| 18. Jun. 1999 | 1.1.1   | Draft during the email meeting.                                                                                                                                                                                                                                                                                               |
+| 24. Jun. 1999 | 1.2.0   | Result of email discussions. For some issues status still unstable.                                                                                                                                                                                                                                                           |
+| 1. Jul. 1999  | 1.2.1   | Comments from TSGN & TSGS Multimedia and Multicall joint meeting included. (Revisions included from version 1.1.0)                                                                                                                                                                                                            |
+| 8. Jul. 1999  | 1.3.0   | Results from S1 Plenary. Drafting continues at S1_Multicall mailing lists.<br>Contributions expected on:<br>-Busy, Idle, Active states<br>-Busy definition<br>-Supplementary service interactions incl. related CR to appropriate SS when needed. (Specifically 02.83 need to be studied.)<br>- all topics marked with FFS... |
+| 28. Sep. 1999 | 1.4.0   | Output from S1 Multicall ad hoc, Germany.                                                                                                                                                                                                                                                                                     |
+| 1.Oct. 1999   | 1.6.0   | Proposed version 2.0.0                                                                                                                                                                                                                                                                                                        |
+| 10. Oct 1999  | 2.0.0   | Version 2.0.0                                                                                                                                                                                                                                                                                                                 |
+
+| Change history |           |           |        |     |     |     |     |                                                                                    |       |       |           |
+|----------------|-----------|-----------|--------|-----|-----|-----|-----|------------------------------------------------------------------------------------|-------|-------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel | Cat | Subject/Comment                                                                    | Old   | New   | Work Item |
+| SP-05          | SP99-433  |           | 22.135 |     |     |     |     | Version 3.0.0 approved                                                             |       | 3.0.0 |           |
+| SP-06          | SP-99523  | S1-991020 | 22.135 | 001 |     | R99 | D   | Transfer of Handover chapter to 22.129                                             | 3.0.0 | 3.1.0 |           |
+| SP-06          | SP-99523  | S1-991065 | 22.135 | 002 |     | R99 | D   | Clarification on handling of multiple bearers                                      | 3.0.0 | 3.1.0 |           |
+| SP-06          | SP-99554  | S1-99963  | 22.135 | 003 |     | R99 | C   | Registration, Interrogation and Restriction of Packet Domain                       | 3.0.0 | 3.1.0 |           |
+| SP-07          | SP-000068 | S1-000168 | 22.135 | 004 |     | R99 | F   | Clarification of requirement for Multicall                                         | 3.1.0 | 3.2.0 |           |
+| SP-08          | SP-000205 | S1-000349 | 22.129 | 012 |     | R99 | F   | Alignment of handover requirements for Multicall                                   | 3.2.0 | 3.3.0 |           |
+| SP-09          | SP-000375 | S1-000585 | 22.135 | 006 |     | R99 | F   | Interaction with MSP                                                               | 3.3.0 | 3.4.0 |           |
+| SP-09          | SP-000406 | S1-000656 | 22.135 | 007 |     | R99 | F   | Removal of the Requirement on Network to Tear Down Calls to Accept EC in Multicall | 3.3.0 | 3.4.0 |           |
+| SP-09          | SP-000406 | S1-000657 | 22.135 | 008 |     | R99 | F   | Addition of Ncs_MT limitation to number of MPTY members                            | 3.3.0 | 3.4.0 |           |
+
+|         |           |           |        |     |   |       |   |                                              |        |        |         |
+|---------|-----------|-----------|--------|-----|---|-------|---|----------------------------------------------|--------|--------|---------|
+| SP-11   | SP-010065 | S1-010258 | 22.135 |     |   | Rel-4 |   | Transferred to 3GPP Release 4                | 3.4.0  | 4.0.0  |         |
+| SP-15   | SP-020045 | S1-020457 | 22.135 | 009 | - | Rel-4 | F | Editorial CR to correct terms and references | 4.0.0  | 4.1.0  | CORRECT |
+| SP-16   | SP-020267 | S1-021043 | 22.135 |     |   | Rel-5 |   | Updated from Rel-4 to Rel5                   | 4.1.0  | 5.0.0  |         |
+| SP-26   | SP-040744 | S1-040997 | 22.135 |     |   | Rel-6 |   | Updated from Rel-5 to Rel-6                  | 5.0.0  | 6.0.0  |         |
+| SP-36   |           |           | 22.135 |     |   | 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 |         |
+| 2014-10 | -         | -         | -      | -   | - | -     | - | Update to Rel-12 version (MCC)               | 11.0.0 | 12.0.0 |         |
+| 2015-12 | -         | -         | -      | -   | - | -     | - | Updated to Rel-13 by MCC                     | 12.0.0 | 13.0.0 |         |

marked/Rel-13/22_series/22140/raw.md

@@ -0,0 +1,718 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Messaging Service (MMS);**
+
+**3GPP TS 22.140 V13.0.0 (2015-12)**
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font with a "TM" symbol. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the left of the text is a green signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo. It features the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned above the "G". The "P" has a small red signal icon (three curved lines) at its base. A "TM" symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>TM</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP<sup>TM</sup> system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+Keywords  
+LTE, UMTS, MMS, multimedia, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+Foreword .....4
+
+Introduction .....4
+
+1 Scope.....5
+
+2 References.....5
+
+3 Definitions and abbreviations .....6
+
+3.1 Definitions.....6
+
+3.2 Abbreviations .....6
+
+4 High level Requirements.....6
+
+5 General Requirements.....7
+
+5.1 Multimedia message management .....8
+
+5.2 Multimedia message delivery and submission.....10
+
+5.2.1 MM delivery to and submission from a VASP .....12
+
+5.3 Notification and Acknowledgement.....12
+
+5.4 Addressing.....13
+
+5.5 Management and Control of a Network Based Repository.....13
+
+5.6 Error Messages.....13
+
+5.6.1 Prepaid Errors .....13
+
+5.7 MMS client interaction with UICC.....13
+
+6 User Profile .....14
+
+7 Security .....14
+
+8 Charging.....14
+
+9 External Interface.....15
+
+10 Interworking.....15
+
+11 Roaming .....15
+
+12 Support of Operator Specific Services.....15
+
+12.1 Service Interaction.....16
+
+12.1.1 VASP Services .....16
+
+Annex A (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
+
+SMS has been very successful in the GSM second generation system, as all mobiles have supported the application level and it is possible to send to any GSM handset without the need to check for individual support. This easy to use service for non realtime text transmission between GSM users shall be succeeded to in third generation mobile systems by a non real-time Multimedia Message Service, MMS. The MMS will allow users to send and receive messages exploiting the whole array of media types available today e.g. text, images, audio, video while also making it possible to support new content types as they become popular.
+
+3GPP shall not standardise new services themselves, but instead uses the standardised set of service capabilities features on which the new services will be built.
+
+Multimedia technology is rapidly developing new capabilities, such as multimedia messages, games, presentations and services that are now considered to be a part of everyday life. Multimedia consists of one or more media elements (such as text, voice, image and video), and it is the combination of these media elements in an ordered synchronised manner that creates a multimedia presentation.
+
+A non-realtime multimedia message as observed by the user is a combination of one or more different media elements in a multimedia presentation, that can be transferred between users without the requirement for the need to be transferred in realtime. The non-real-time multimedia messaging service shall be capable of supporting current and future multimedia messaging services, and exploit the advances being made in the world multimedia community, with additional mobile requirements.
+
+# --- 1 Scope
+
+This Technical Specification defines the stage one description of the non real-time Multimedia Messaging Service, MMS. Stage one is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber's and service providers' points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the Multimedia Messaging Service, which are sufficient to provide a complete service.
+
+This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:
+
+- multiple media elements per single message
+- individual handling of message elements
+- different delivery methods for each message element
+- negotiate different terminal and network MM capabilities
+- notification and acknowledgement of MM related events (e.g. delivery, deletion, ...)
+- handling of undeliverable MM
+- personalised MMS configuration
+- flexible charging
+
+The above list is not exhaustive.
+
+Thus the MMS enables a unified application which integrates the composition, storage, access, and delivery of different kinds of media, e.g. text, voice, image or video in combination with additional mobile requirements.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. 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 Principles".
+- [2] Void
+- [3] 3GPP TS 21.133: "3G Security; Security Threats and Requirements".
+- [4] ITU-T E.164 (1997): "The International Public Telecommunications Numbering Plan".
+- [5] IETF; STD 0011 (RFC 2822): "Internet Message Format", URL:  
+<http://www.ietf.org/rfc/rfc2822.txt>.
+- [6] 3GPP TS 21.905: "Vocabulary".
+- [7] 3GPP TS 31.102 "Characteristics of the USIM Application".
+
+- [8] 3GPP TS 51.011 (Rel-4): "Specification of the Subscriber Identity Module – Mobile Equipment (SIM-ME) interface".
+- [9] 3GPP TS 22.242 "Digital Rights Management (DRM); Stage 1".
+- [10] 3GPP TS 22.240 "Stage 1 Service Requirement for the 3GPP Generic User Profile (GUP)" .
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+**Recipient :** the recipient is the entity to which a MM has been sent.
+
+**Sender:** the sender is the entity that sent a MM.
+
+**User:** the user is the MM sender or the MM recipient.
+
+**message element:** a message element is a part of a MM consisting of only one media type.
+
+**multimedia message:** a multimedia message is a message composed of one or more message elements.
+
+**multimedia message service:** A multimedia message service allows transfer of multimedia messages between users without the requirement for the multimedia messages to be transferred in real-time.
+
+**media types:** a media type refers to one form of presenting information to a user, e.g. voice or fax.
+
+**media formats:** within one media type different media formats are applicable for the media presentation, e.g. a picture can be GIF or JPEG format.
+
+**network:** for the purposes of supporting multimedia messaging, the term network shall be considered to include the mobile operator's network and any functionality which may exist outside the mobile operator's network (i.e. fixed, internet and multimedia technologies etc.), and the support provided by that functionality for multimedia messaging.
+
+**Operator Specific Service:** network-based and operator administered function being able to perform additional, operator defined, MMS services based on MMS capabilities for address translation and charging.
+
+**Value Added Service Provider:** provides services other than basic telecommunications service for which additional charges may be incurred.
+
+**Short code:** A string of alphanumeric characters which addresses a specific service of a Value Added Service Provider.
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+|      |                               |
+|------|-------------------------------|
+| MM   | Multimedia Message            |
+| MMS  | Multimedia Message Service    |
+| SMS  | Short Message Service         |
+| VASP | Value Added Services Provider |
+
+# --- 4 High level Requirements
+
+The following list gives the high level requirements of the MMS. These are requirements which are independent of the user's perception of the service:
+
+- **Forward compatible multimedia messaging**
+
+Multimedia messaging mechanisms shall provide the capability to support current and evolving multimedia messaging by re-using existing standards as far as possible and proposing extensions (as necessary) to existing standards (i.e. the multimedia messaging service shall support the evolution of multimedia messaging technologies).
+
+### - **Consistent messaging**
+
+Regardless of the message type / format, MMS shall be capable of supporting integration of all types of messaging (e.g. fax, SMS, Multimedia , voicemail, e-mail etc.) in a consistent manner.
+
+### - **Universal messaging access**
+
+Within the capabilities of networks and terminals, the user shall be able to experience consistent access to the MMS regardless of the access point.
+
+For example the user should be capable of accessing her multimedia messages through a number of different access points, which should include 3GPP systems, fixed networks, the Internet, etc.
+
+### - **Interoperability**
+
+The MMS shall support a minimum set of functionality and message formats to ensure interoperability (e.g. deletion of MM, identified standardised message notification, message media types and message content formats).
+
+The MMS shall provide a minimum set of supported formats to ensure full interoperability between different terminals and networks from the very beginning of service provisioning (e.g. JPEG for pictures, MP3 for audio, MPEG for motion pictures, etc.).
+
+The MMS shall support version management by indicating a version number in the MM for interoperability purpose.
+
+# --- 5 General Requirements
+
+Network operators have many differing requirements, and MMS shall be supported in the network in a manner which allows network operators to consider different configurations depending on their network and commercial requirements. Thus, an identified set of functionalities and formats shall be standardised to ensure interoperability across networks and terminals to support MMS.
+
+However, some network operators may wish to design and configure networks in different ways, and the subsequent requirements are identified to allow flexibility in how the MMS functionality is supported. For example in some networks the network operators may wish to implement the MMS functionality within the core network, whereas other may wish to place the MMS functionality on the periphery of the core network (e.g. a centralised network model instead of a distributed architecture). Further, some network operators may wish to support a limited set of MMS functionality, while others may require extensive and elaborate MMS support according to their business models (e.g. basic MMS instead of advanced MMS). Interoperability shall always be maintained within this flexible architecture.
+
+The following sub-clauses use the term "*The MMS shall be able to support a request for ...*" and similar phrases to allow network operators to consider these different network models and business requirements, to permit flexible architectures and ensure MMS interoperability.
+
+The following sub-clauses use the term "*This requirement shall be supported at the application layer in the terminal (and/or the network), and will not be further elaborated.*" and similar phrases to identify those service requirements that shall be supported by MMS but do not require standardisation.
+
+The criterion for identifying these types of requirements is as follows:
+
+If the requirement corresponds to an interaction and/or command between the terminal and the network applications from the same Service Provider (e.g. between the recipient's terminal resident messaging application and the recipient's network resident application. The same applies for the sender), then this requirement shall be supported by MMS but does not require standardisation.
+
+The following general requirements shall be supported.
+
+## 5.1 Multimedia message management
+
+### - **Terminal-sensitive MM management**
+
+The MMS shall be able to support the capability for the terminal and network to take account of the capability of the user's terminal (e.g. deliver a MM / notification in a manner compatible with the terminals capability).
+
+### - **Terminal status-sensitive MM Management**
+
+The MMS shall be able to support the capability of the network to take account of the availability, changes of the state of availability of the terminal (e.g. store messages if the recipient is not available).
+
+### - **MMS Control by the operator**
+
+The MMS shall be able to support a request from the operator to enable/disable MM delivery and submission.
+
+### - **MMS Control by the user**
+
+The MMS shall be able to support a request from the user to enable/disable MM delivery and submission.
+
+This requirement shall be supported at the application layer in the terminal, and will not be further elaborated.
+
+### - **Storage of MMS parameters**
+
+The USIM shall be able to store the following types of MMS related data:
+
+- i) a number of sets of issuer configuration information to allow access to MMS services.
+
+At least one of these sets of configuration information should be stored on the USIM by the issuer of the USIM.
+
+The first issuer configuration information set is denoted as the default configuration set.
+
+This configuration information shall only be configurable by the issuer of the USIM.
+
+- ii) a number of sets of user configuration information to allow access to MMS services.
+
+If more than one set of configuration information is present, it shall be possible for the user to select which set is used. If the user has not selected any of the configuration information sets, then the default set in the active USIM is used.
+
+- iii) MMS notifications
+
+- iv) MMS user preferences
+
+A terminal using a USIM [7] or a SIM [8] with these MMS parameters, shall by default use them and the related preferred bearer, to access to the MMS services.
+
+NOTE 1: Terminal support of SIM and USIM in general is specified in 3GPP TS 22.101[1].
+
+### - **Personalise multimedia messaging**
+
+The MMS shall be able to support a request by the user to manage the Service Preferences of his User Service Profile related to this MMS [6](e.g. customise his MM environment within the capabilities of the terminal, network and MM application. This could be unconditional or conditional e.g. depending on roaming conditions or operator restrictions).
+
+### - **MM creation**
+
+The MMS shall be able to support the request to create a MM by the user or an application.
+
+This requirement shall be supported at the application layer in the terminal, and will not be further elaborated.
+
+### - **MM Time Stamping**
+
+The MMS shall be able to support the request to include a reliable time value in an MM, a notification and an acknowledgement as appropriate.
+
+### - **Multiple Media**
+
+Multimedia messages may be composed of either a single medium (e.g. voice) or multi-media (e.g. Voice and video). The MMS shall be able to support a request for media synchronisation / sequencing.
+
+### - **Media Type Conversion**
+
+The MMS shall be able to support a request to convert between media types (e.g. Fax to image). The MMS shall be able to support an indication from a VASP that VASP originated content of an MM should not be converted or changed by the MMS service provider before it is delivered to the recipient.
+
+This requirement shall be supported at the application layer in the network, and will not be further elaborated.
+
+### - **Media Format Conversion**
+
+The MMS shall be able to support a request by the user or the application to convert between MM media formats (e.g. JPEG to GIF).
+
+This requirement shall be supported at the application layer in the terminal and/or in the network, and will not be further elaborated.
+
+### - **Message forwarding**
+
+The MMS shall be able to support a request to forward multimedia messages or multimedia message elements without having to first download the MM to the terminal. The MMS shall provide a mechanism to prevent an MM forwarding loop (e.g. MMs are setup to be automatically forwarded from User A to B, then from B to C and from C back to A. Users A, B, and C are unaware that they have setup this undesirable situation).
+
+### - **Storage of Multi-Media Messages**
+
+The MMS shall be able to support a request for multimedia messages or message elements to be stored until delivered to the recipient's terminal, until they expire, or until they are deleted by the user (unless configured differently). The MMS shall be able to support a request to store and manage all MMs in a network based repository rather than on the mobile terminal.
+
+When the USIM supports MMs storage, it shall be possible for the MMS client to store and retrieve MMs or elements of MMs in the USIM.
+
+NOTE 2: There is no requirement for the MMS to be responsible for the processing/presentation of the MM message, after it has been delivered to the terminal.
+
+### - **Prioritisation of Messages**
+
+The MMS shall be able to support a request for MM prioritisation. The prioritisation is passed to the recipient(s) of the message as an indication of the importance the sender places on the message. MM prioritisation is not acted upon by the network.
+
+### - **Message qualification**
+
+The MMS shall be able to support a request for MM qualification (e.g. subject) for the purpose of advanced user experience and awareness.
+
+### - **Screening of Messages**
+
+The MMS shall be able to support a request for MM screening subject to the capabilities of the network (e.g. automatically delete "junk mail", anonymous messages without delivery to the recipient's terminal).
+
+This requirement shall be supported at the application layer in the terminal and/or in the network, and will not be further elaborated.
+
+### - **Validity Period**
+
+The MMS shall be able to support a request by the originator of a message to define validity periods (earliest and latest desired time) for message delivery (e.g. if a message can not be delivered within a certain time it will be automatically deleted). The MMS service provider shall be able to set the MAXIMUM allowable validity period for any message.
+
+### - **Multimedia Message Processing by a VASP**
+
+The MMS shall be able to support a request for messages to be processed by a VASP. An example of such processing may be where an MM is sent to a VASP before delivery to the recipient so that the VASP can add multimedia element(s) to the original message.
+
+### - **Replacing MM**
+
+The MMS shall be able to support a request by a VASP to replace a previously sent MM from the VASP with a second newer MM.
+
+### - **Cancellation of MM**
+
+The MMS shall be able to support a request by a VASP to delete a MM that had previously been sent from the VASP but not yet delivered to the terminal.
+
+### - **Hyperlinks in MM**
+
+It shall be possible to embed a hyperlink in a MM.
+
+The following guidelines on editing, presenting and following of hyperlinks should be followed:
+
+- There should be no restriction to the position in the MM where a hyperlink can be added.
+- It should be possible to clearly recognise the presence of a hyperlink.
+
+NOTE 3: It is preferable to display the title of a hyperlink rather than the complete address. (URI)
+
+- Presence of a hyperlink in an MM should not impact the presentation of the MM (i.e. due to immediate following or storage of the link)
+- The recipient of an MM should be able to follow a hyperlink.
+
+The hyperlink should not be followed automatically by default (explicit user interaction should be required)
+
+### - **Digital Rights Management**
+
+The MMS shall be able to support controlling the distribution of controlled content as defined in 3GPP TS 22.242 [9]. MMS Content Providers shall be able to invoke DRM to prevent unauthorized copying and forwarding of controlled content through the MMS.
+
+## 5.2 Multimedia message delivery and submission
+
+### - **Submission mechanism**
+
+The MMS shall support multimedia messages or messages elements to be submitted from the sender's UE.
+
+### - **Push Mechanism**
+
+The MMS shall be able to support a request for multimedia messages or messages elements to be automatically delivered to the recipient's UE.
+
+### - **Pull Mechanism**
+
+The MMS shall be able to support a request for multimedia messages or messages elements to be delivered to the recipient's UE on request by the recipient.
+
+NOTE 1: Push and pull delivery mechanisms could be identical; the criteria which decide on the type of mechanism (push / pull) are either described in the User Services Profile or out of the scope of this specification.
+
+### - **Concurrency**
+
+The MMS shall be able to support MM delivery to and from the user's terminal not be restricted during other active services (subject to the capabilities of the terminal and the network).
+
+### - **Streaming**
+
+The MMS shall be able to support streaming for MM delivery from the MMS system to the terminal.
+
+Support for streaming for MM upload from the terminal to the MMS system will be considered for future releases.
+
+#### - **Preferred Bearer**
+
+It shall be possible to define a list of precedence for bearers in the configuration information sets for delivery and submission of MM (e.g. GPRS, CSD). By default, the terminal shall be able to support automatic bearer selection (i.e. without user intervention) based on the order of precedence defined in the configuration information sets on the USIM[7] or SIM [8]. The user shall be able to enable or disable automatic bearer selection. When disabled, manual bearer selection shall be available from the list of bearers.
+
+### - **Conditional delivery mechanism**
+
+It shall be possible for the user to define in the User Profile a set of conditions that determine which delivery mechanism should be used for the delivery of a MM.
+
+Such conditions should include:
+
+- Roaming status of the recipient (e.g. inside or outside the home network)
+- Identity of the MM originator
+- Time of day (of the recipient's home network)
+- Upper limit to the MM size
+
+The notification message indicating an MMS awaiting delivery shall relay the information of the user's preferred delivery mechanism, if such information is made available by the user profile in the network, to the UE. If a mismatch is identified between the delivery mechanism configured in the UE and the delivery mechanism indicated in the notification message, it shall be possible for the user to select either the delivery mechanism configured in the UE or the delivery mechanism indicated in the notification message.
+
+Furthermore, the terminal may also display a warning prior to the download of a message depending on some terminal parameters such as:
+
+- Available storage capacity
+- Remaining battery life
+- Available bearers
+
+For example, the user may elect to have all MMs downloaded automatically when in the home network, be able to manually select whether to download a MM or not when roaming.
+
+It shall be possible for the network operator to program a default set of rules for the delivery mechanism in the User profile. Such rules can be overridden by the user.
+
+NOTE 2: The way the user profile is accessed and modified is not subject of standardisation.
+
+- MM intended for applications other than the default MMS client on the UE
+
+The MMS shall support MMs that are not intended for presentation but used to originate and deliver information to applications residing on the UE other than the default MMS client.
+
+NOTE 3: The intended application can present the MM contents.
+
+When an application sends a MM not intended for presentation, it shall be possible to uniquely identify that originating application and the target application on the recipient UE as well as the instance of the application if more than one instance can be active. The originating application may reside on a UE or within the network.
+
+The message payload shall not be modified by the MMS.
+
+If the MM is originated by the subscriber's home environment, it shall be possible to protect the MM from accidental deletion by the user.
+
+### 5.2.1 MM delivery to and submission from a VASP
+
+#### - **VASP submission mechanism**
+
+The MMS shall support multimedia messages or messages elements to be submitted from a VASP.
+
+#### - **VASP delivery mechanism**
+
+The MMS shall be able to support multimedia messages or messages elements to be delivered to a VASP.
+
+#### - **VASP mass distribution**
+
+The MMS shall be able to support a request from a VASP for mass distribution of MMs to recipients.
+
+#### - **Additional VASP data**
+
+The MMS shall be able to convey additional data associated with an MM from a VASP to the MMS service provider and vice versa.
+
+Note: A possible use case for this could be the option to send additional charging information from the VASP to the MMS service provider. However the data itself is not specified for this release.
+
+## 5.3 Notification and Acknowledgement
+
+The MMS shall be able to support a request to send generic notification and acknowledgement capability to inform the user in an appropriate manner of MMS events. Examples may include:
+
+- notify the recipient about received messages (including a description of the message, e.g. content, size, type).
+- notify the recipient about actions taken by the MMS, (e.g. due to profile settings like automatic MM forwarding, deletion, etc.).
+- acknowledge the sender about successful or failed MM or storage of a MM.
+- acknowledge the sender about successful or failed MM submission.
+- acknowledge the sender, including a VASP, about successful or failed MM delivery to the recipient terminal (subject to the recipient permitting such an acknowledgement).
+- acknowledge the sender, including a VASP, about the MM being read/handled at the recipient terminal (subject to the recipient permitting such an acknowledgement).
+- acknowledge the sender, including a VASP, about successful or failed MM deletion.
+- acknowledge the sender, including a VASP, upon request, about the status of a submitted MM (i.e. delivered / not delivered).
+- acknowledge a VASP, upon request, about the status of a mass distributed MM. A mass MM status report might be an aggregated report on the status of individual messages for all recipients on the distribution list of a specific mass distributed MM.
+- acknowledge a VASP, upon request, about the status of previously submitted MMs, after a VASP had sent the MMs being queried.
+
+## 5.4 Addressing
+
+The MMS shall support different addressing formats to identify the sender and recipient. It shall be possible to submit one message to multiple recipients.
+
+The MMS shall support the capability for both MSISDN [4] and e-mail addressing schemes [5] to be used, and the user may use either form of addressing to send a message.
+
+The MMS shall be able to support the request to hide the sender's address from the recipient.
+
+The MMS shall support a distribution list for mass distribution of MMs from a VASP. The MMS shall support the ability for a VASP to have the distribution list modified by the MMS service provider for this release.
+
+The MMS may support short code addresses to address Value Added Services. If supported, and routing of messages to a MMS VASP service based on a short code address is enabled, the MMS shall be able to translate the short code address to a routable address to be used in the transport layer, e.g. a URI.
+
+## 5.5 Management and Control of a Network Based Repository
+
+Network based repository is optional. If supported, MMS shall be able to support following functionalities:-
+
+- The MMS shall allow an MMS service provider to configure MMS in such a way that one, several or all incoming MMs of a particular user be stored persistently in a network based repository
+- The MMS shall allow an MMS service provider to configure MMS in such a way that one, several or all submitted MMs of a particular user be stored persistently in a network based repository
+- The MMS shall be able to support a request from a sender to persistently store a sent MM in a network based repository at the time of sending
+- The MMS shall be able to support a request from a user to persistently store a MM for which he received a notification in a network based repository
+- The MMS shall be able to support a request from a user to upload one or more MMs into a network based repository for persistent storage
+- The MMS shall be able to support a request from a user to retrieve one or more MMs that are stored in a network based repository
+- The MMS shall be able to support a request from a user to delete one or more MMs that are stored in a network based repository
+- The MMS shall be able to support a request from a user to forward one or more MMs that are stored in a network based repository to another destination without being delivered first to that user.
+- The MMS shall be able to support a request from a user to view the list of MMs and MM related attributes, such as sender, recipient, subject and date/time, in a network based repository
+
+## 5.6 Error Messages
+
+It shall be possible for the operator to configure the content of the error message delivered to the MMS client.
+
+### 5.6.1 Prepaid Errors
+
+The MMS shall notify a prepaid user when message submission was unsuccessful due to lack of credit in the prepaid account, explicitly stating this situation.
+
+## 5.7 MMS client interaction with UICC
+
+It shall be possible for an MMS client in the ME to interact with a UICC to manage (e.g. send, receive and present) MMS messages stored on the UICC, in accordance with the requirements in this specification. It shall be possible to indicate to the UE that an MM needs to receive special treatment. When a MM has been marked with this indication, means shall be provided to protect the MM from accidental deletion e.g. by asking for additional confirmation to the user. The use of this indication shall be under the control of the HPLMN.
+
+# --- 6 User Profile
+
+The MMS shall be able to support the ability to create, update, store, transfer, interrogate, manage and retrieve a user's multimedia messaging profiles.
+
+The multimedia messaging profiles shall allow a user to configure and personalise his multimedia messaging environment with the multimedia messaging profiles (e.g. which media types and notifications that shall be delivered to the recipient, such as voice only or text only).
+
+The user profile shall allow the user to create and manipulate a list of users, identified by their addresses, from which the user does not want to receive messages. This list is called "user-level blacklist". It shall be possible for the user to add, remove and edit addresses in the user-level blacklist.
+
+Note: User-level blacklist differs from ODB blacklist. Users can decide from whom they do not want to receive messages by adding the corresponding address to the user profile.
+
+If the MMS supports a network based repository of MMs, it shall be possible for the users to configure where incoming MMs will be stored.
+
+The multimedia messaging profiles shall form part of the user's virtual home environment.
+
+MMS information in the user profile when stored in the UA or the network shall be accessed in a standardised manner. The MMS should accomplish this using mechanisms described in the 3GPP Generic User Profile 3GPP TS 22.240 [10] whenever possible.
+
+# --- 7 Security
+
+The user shall be able to use and access MM in a secure manner. It shall be possible for the contents of MMs to be read only by the intended recipient(s). A recipient shall be informed of the reliability of the identity of the sender in case the sender has authorised his identity to be transmitted.
+
+The integrity of MMs during transit shall be assured to extent of the network capabilities.
+
+The MMS shall be intrinsically resistant to attempts of malicious or fraudulent use.
+
+An MMS service provider shall be able to authenticate a VASP connected to it and shall be able to be authenticated by a VASP connected to it. The MMS service provider shall be able to authorise the VASP to use various MM services. The MMS shall support encryption of the transport layer between an MMS service provider and a VASP.
+
+Note: Key management is outside the scope of this release of this standard.
+
+The "Security Threats and Requirements" specified in 21.133 [3] shall not be compromised.
+
+# --- 8 Charging
+
+The MMS shall be able to support various charging models, including:
+
+- Sender pays;
+- both Sender and Recipient pay their respective charges for message delivery;
+- Recipient pays for receipt of messages from a VASP when there is a commercial agreement between the Recipient and the VASP;
+- Sender pays for reply message on a per message basis.
+- The third party who has a commercial agreement with the VASP (and possibly additional agreement with the operator and/or recipient) is charged for the delivery of the message to the recipient.
+
+The MMS shall be able to support various charging mechanisms. The following charging characteristics may be considered:
+
+- message types, length, storage time in the network, etc,
+- delivering time, upload / download method,
+- MM-sender / -recipient,
+- number of messages sent,
+- number of messages received,
+- roaming conditions,
+- location conditions,
+- Indication of charging,
+
+The MMS indicates to the recipient prior to the recipient downloading a multi media message whether the sender has paid or the recipient is expected to pay for the message.
+
+- Prepaid subscriptions.
+- Bearer of the message
+
+The MMS shall support a standardized interface to transfer CDRs and other charging related information between the MMS system and the billing system for prepaid and postpaid billing solutions.
+
+# --- 9 External Interface
+
+External interfaces for controlling and delivering MM between the terminal and an external device e.g. portable computer should be supported.
+
+# --- 10 Interworking
+
+The standard shall permit interworking with other or existing messaging technologies, messaging services, intelligent network services and supplementary services, either located within or outside a mobile network.
+
+In the case of a VASP, such interworking shall include capability negotiation between the VASP and the MMS service provider. Such capability negotiation shall include service version information as a minimum for this release.
+
+# --- 11 Roaming
+
+Roaming between network operators shall be supported.
+
+# --- 12 Support of Operator Specific Services
+
+The MMS may support operator specific services. Thereby network operators shall be able to provide additional MMS services dealing with enhanced addressing and charging.
+
+If supported, the interaction between the MMS and Operator Specific Service shall happen immediately after multimedia message submission time or immediately before multimedia message delivery time, or both.
+
+Multimedia Messages sent or delivered from/to users shall be subject to operator specific services handling if:
+
+- the user is provisioned with operator specific services in the MMS user profile. The user may be provisioned independently for operator specific services applicable for submission and delivery of multimedia messages. Provisioning of Operator Specific Services for MMS is under control of the HPLMN operator.
+
+- the MMS determines based on a pre-analysis of the recipient's address(es) found in a submitted multimedia message that an Operator Specific Service needs to be invoked. The definition of the addresses invoking MMS Operator Specific Services is under control of the HPLMN operator(s) of the originating and terminating subscribers.
+
+If the Operator Specific Services needs to be invoked, the MMS shall temporarily suspend the normal process of that multimedia message and shall provide the Operator Specific Services with at least the following information:
+
+- messaging event (submission, delivery)
+- multimedia message data:
+  - sender identification
+  - recipient addresses
+
+As a response to the above request from the MMS, the Operator Specific Services may request the MMS to perform one of the following actions:
+
+- leave the multimedia message unmodified and proceed with its processing;
+- reject the message.
+- modify one or more of the following multimedia message data:
+  - sender identification
+  - recipient addresses
+
+Operator Specific Services shall be allowed to influence charging of the message by providing additional information to the MMS. The MMS shall transparently forward this information to the billing systems together with the MMS charging relevant data.
+
+## 12.1 Service Interaction
+
+This subclause specifies interactions between Operator Specific Services and other services in the MMS.
+
+### 12.1.1 VASP Services
+
+Operator Specific Services take precedence over VASP services. If short code addressing to Value Added Services is supported by the MMS, the result from an Operator Specific Service shall be subject to short code address translation.
+
+Multimedia Messages submitted from a VASP may be subject to operator specific services.
+
+# --- Annex A (informative): Change history
+
+| TSG SA# | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                                                                                                   | Old   | New   | Work Item        |
+|---------|-----------|-----------|--------|-----|-----|-------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|------------------|
+| SP_06   | PP-99529  |           | 22.140 | -   |     | R99   | -   | Approved at SA#08 as version 3.0.0                                                                                                                                | 2.0.0 | 3.0.0 |                  |
+| SP_08   | SP-000214 | S1-000347 | 22.140 | 001 |     | R00   | B   | Introduction of streaming for MMS                                                                                                                                 | 3.0.0 | 4.0.0 |                  |
+| -       | -         | -         | 22.140 | -   |     | R00   | -   | Corrected implementation of CR001 by MCC, re-introducing the R00 text deleted by implementation of CR002 to R99 version (see SP-000208). Some editorial clean-up. | 4.0.0 | 4.0.1 |                  |
+| SP-11   | SP-010062 | S1-010265 | 22.140 | 004 |     | Rel-4 | C   | Alignment of Stage 1 MMS to Stage 2 MMS                                                                                                                           | 4.0.1 | 4.1.0 | MMS              |
+| SP-11   | SP-010062 | S1-010016 | 22.140 | 005 |     | Rel-4 | C   | Support for Streaming in MMS                                                                                                                                      | 4.0.1 | 4.1.0 | MMS              |
+| SP-11   | SP-010062 | S1-010014 | 22.140 | 006 |     | Rel-4 | F   | MM Forwarding                                                                                                                                                     | 4.0.1 | 4.1.0 | MMS              |
+| SP-11   | SP-010062 | S1-010015 | 22.140 | 007 |     | Rel-4 | B   | New features in MMS R'4                                                                                                                                           | 4.0.1 | 4.1.0 | MMS              |
+| SP-14   | SP-010676 | S1-011345 | 22.140 | 008 |     | Rel-5 | B   | Stage 1 Requirements for VASP connectivity                                                                                                                        | 4.1.0 | 5.0.0 | MESS5-MMS        |
+| SP-14   | SP-010748 |           | 22.140 | 009 | -   | Rel-5 | B   | Minimum set of functionality for the support of a Network Based repository                                                                                        | 4.1.0 | 5.0.0 | MMS enhancements |
+| SP-15   | SP-020193 |           | 22.140 | 010 | 1   | Rel-5 | B   | Support of charging models in MMS                                                                                                                                 | 5.0.0 | 5.1.0 | MMS              |
+| SP-15   | SP-020055 | S1-020209 | 22.140 | 011 |     | Rel-5 | B   | CR to 22.140 on addressing                                                                                                                                        | 5.0.0 | 5.1.0 | MMS              |
+| SP-15   | SP-020045 | S1-020457 | 22.140 | 012 | -   | Rel-5 | A   | Editorial CR to correct terms and references                                                                                                                      | 5.0.0 | 5.1.0 | CORRECT          |
+| SP-15   | SP-020055 | S1-020622 | 22.140 | 013 |     | Rel-5 | B   | CR 22.140 Rel. 5 MMS Configuration                                                                                                                                | 5.0.0 | 5.1.0 | MMS enhancements |
+| SP-15   | SP-020045 | S1-020468 | 22.140 | 014 |     | Rel-5 | D   | Editorial CR 22.140 Rel.5 D - Update of references and general requirements                                                                                       | 5.0.0 | 5.1.0 | CORRECT          |
+| SP-15   | SP-020195 |           | 22.140 | 015 |     | Rel-5 | B   | Automatic bearer selection for MMS delivery and submission                                                                                                        | 5.0.0 | 5.1.0 | MMS Enhancement  |
+| SP-16   | SP-020251 | S1-021073 | 22.140 | 016 |     | Rel-5 | F   | CR to 22.140 - Introduction of short codes for VASP addressing                                                                                                    | 5.1.0 | 5.2.0 | MMS Enhancement  |
+| SP-17   | SP-020553 | S1-021786 | 22.140 | 017 |     | Rel-5 | F   | Removal of SMS and USSD as possible bearers from 22.140 v5.2.0                                                                                                    | 5.2.0 | 5.3.0 | MMS              |
+| SP-18   | SP-020814 | S1-022387 | 22.140 | 019 | 1   | Rel-5 | A   | Storage of configuration information on the (U)SIM - for Rel 5                                                                                                    | 5.3.0 | 5.4.0 | MESS5-MMS        |
+| SP-18   | SP-020660 | S1-022312 | 22.140 | 020 |     | Rel-6 | B   | Requirements for the MMS charging models and charging mechanisms                                                                                                  | 5.4.0 | 6.0.0 | MMS              |
+| SP-18   | SP-020660 | S1-022313 | 22.140 | 021 |     | Rel-6 | B   | Additional feature for the MMS charging model                                                                                                                     | 5.4.0 | 6.0.0 | MMS              |
+| SP-18   | SP-020660 | S1-022314 | 22.140 | 022 |     | Rel-6 | B   | Requirement for preventing the loop of MM                                                                                                                         | 5.4.0 | 6.0.0 | MMS              |
+| SP-19   | SP-030024 | S1-030267 | 22.140 | 024 | -   | Rel-6 | C   | Update to 22.140 to clarify prioritisation                                                                                                                        | 6.0.0 | 6.1.0 | MMS6-SR          |
+| SP-20   | SP-030256 | S1-030493 | 22.140 | 026 | -   | Rel-6 | B   | Add DRM Requirement to 22.140                                                                                                                                     | 6.1.0 | 6.2.0 | MMS              |
+| SP-20   | SP-030256 | S1-030494 | 22.140 | 027 |     | Rel-6 | B   | Add a Standardized Charging Record Interface Requirement to 22.140                                                                                                | 6.1.0 | 6.2.0 | MMS              |
+| SP-20   | SP-030256 | S1-030551 | 22.140 | 028 |     | Rel-6 | B   | Add a Standardized User Profile to 22.140                                                                                                                         | 6.1.0 | 6.2.0 | MMS              |
+| SP-20   | SP-030256 | S1-030536 | 22.140 | 029 |     | Rel-6 | B   | Addition of blacklisting capability in the the multimedia messaging profiles                                                                                      | 6.1.0 | 6.2.0 | R6: MMS          |
+| SP-20   | SP-030257 | S1-030638 | 22.140 | 034 | -   | Rel-6 | F   | Error Messages in MMS                                                                                                                                             | 6.1.0 | 6.2.0 | MMS-R6           |
+| SP-21   | SP-030460 | S1-030883 | 22.140 | 035 | -   | Rel-6 | B   | Management of Hyperlinks with MMS                                                                                                                                 | 6.2.0 | 6.3.0 | MMS              |
+| SP-21   | SP-030552 | S1-031056 | 22.140 | 036 | 2   | Rel-6 | B   | MM storage in the USIM                                                                                                                                            | 6.2.0 | 6.3.0 | MMS-R6           |
+| SP-21   | SP-030542 | S1-031055 | 22.140 | 037 | 1   | Rel-6 | B   | Conditional delivery behaviour                                                                                                                                    | 6.2.0 | 6.3.0 | MMS6             |
+| SP-22   | SP-030689 | S1-031240 | 22.140 | 039 | -   | Rel-6 | B   | MMS targeting UE elements                                                                                                                                         | 6.3.0 | 6.4.0 | MMS              |
+
+|         |           |           |        |     |   |       |   |                                                       |        |        |         |
+|---------|-----------|-----------|--------|-----|---|-------|---|-------------------------------------------------------|--------|--------|---------|
+| SP-22   | SP-030783 | SP-030783 | 22.140 | 040 | 2 | Rel-6 | B | UICC interaction with MMS clients                     | 6.3.0  | 6.4.0  | MMS-R6  |
+| SP-23   | SP-040203 |           | 22.140 | 041 | 1 | Rel-6 | B | MMS targetting UE elements                            | 6.4.0  | 6.5.0  | MMS     |
+| SP-23   | SP-040093 | S1-040234 | 22.140 | 042 | - | Rel-6 | C | Prepaid – lack of credit error in MMS                 | 6.4.0  | 6.5.0  | MESS6   |
+| SP-24   | SP-040450 | S1-040540 | 22.140 | 044 | 1 | Rel-6 | B | Support of MMS operator specific services             | 6.5.0  | 6.6.0  | MMS-6   |
+| SP-24   | SP-040290 | S1-040541 | 22.140 | 045 | - | Rel-6 | F | Clarification on MMS client interaction with UICC     | 6.5.0  | 6.6.0  | MMS-R6  |
+| SP-24   | SP-040290 | S1-040542 | 22.140 | 046 |   | Rel-6 | F | Update to scope and removal of VHE based requirement. | 6.5.0  | 6.6.0  | MMS6-SR |
+| SP-27   | SP-050059 | S1-050218 | 22.140 | 047 | - | Rel-6 | F | Removal of Reference to TS 22.121                     | 6.6.0  | 6.7.0  | TEI6    |
+| SP-36   |           |           | 22.140 |     |   | Rel-7 |   | Updated from Rel-6 to Rel-7                           | 6.7.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 |         |
+| 2014-10 | -         | -         | -      | -   | - | -     | - | Update to Rel-12 version (MCC)                        | 11.0.0 | 12.0.0 |         |
+| 2015-12 | -         | -         | -      | -   | - | -     | - | Updated to Rel-13 by MCC                              | 12.0.0 | 13.0.0 |         |

marked/Rel-13/22_series/22141/raw.md

@@ -0,0 +1,867 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 22.141 V13.0.0 (2015-12) Presence Service** ---
+
+*Technical Specification*  
+**Stage 1  
+(Release 13)**
+
+![LTE Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The logo for LTE Advanced. It features the word "lte" in a bold, lowercase sans-serif font. Above the "t" is the word "ADVANCED" in a smaller, uppercase sans-serif font. Above "ADVANCED" are three red curved lines representing signal waves. A small "TM" trademark symbol is located to the bottom right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. The "3" is slightly larger and positioned to the left. The "G" and "P" are connected at the bottom by a single horizontal line. Below the "P" is a small red signal wave icon. A small "TM" trademark symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+LTE, UMTS, presence, stage 1
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                       |           |
+|-----------------------------------------------------------------------|-----------|
+| Foreword .....                                                        | 4         |
+| Introduction .....                                                    | 4         |
+| 1 Scope.....                                                          | 6         |
+| 2 References.....                                                     | 6         |
+| 2.1 Acknowledgement.....                                              | 6         |
+| 3 Definitions, symbols and abbreviations .....                        | 7         |
+| 3.1 Definitions.....                                                  | 7         |
+| 3.2 Abbreviations .....                                               | 7         |
+| 4 Presence models .....                                               | 8         |
+| 4a A brief introduction to the Presence Service.....                  | 8         |
+| 4.1 Informative models .....                                          | 10        |
+| 4.2 Roles in the presence service .....                               | 10        |
+| 4.3 Presence information.....                                         | 12        |
+| 5 High level requirements .....                                       | 13        |
+| 5.1 Home Environment requirements .....                               | 13        |
+| 5.3 General requirements .....                                        | 13        |
+| 5.4 Management requirements .....                                     | 15        |
+| 5.5 Notification and acknowledgement requirements.....                | 17        |
+| 6 Privacy .....                                                       | 17        |
+| 6.1 General privacy requirements .....                                | 17        |
+| 6.2 Access rules.....                                                 | 17        |
+| 7 Security .....                                                      | 18        |
+| 8 Charging.....                                                       | 18        |
+| 9 Administration .....                                                | 18        |
+| 9.1 Provision.....                                                    | 18        |
+| 9.2 Withdrawal.....                                                   | 19        |
+| 9.3 Registration .....                                                | 19        |
+| 9.4 Erasure.....                                                      | 19        |
+| 9.5 Activation.....                                                   | 19        |
+| 9.6 Deactivation .....                                                | 19        |
+| 9.7 Invocation.....                                                   | 20        |
+| <b>Annex A (informative): Example presence service use cases.....</b> | <b>21</b> |
+| Annex B (informative): Change history.....                            | 24        |
+
+# --- 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
+
+This specification defines the requirements for the support of the presence service. The presence service results in presence information of a user and information on a user's devices, services and services components being managed by the network. Together, user, these devices, services and services components are termed presentity (presence entity). This TS makes extensive use of internet terminology to ensure alignment with the presence service description and behaviour in internet recommendations.
+
+The presence service provides access to presence information to be made available to other users or services. Exploitation of this service, see figure 1, will enable the creation of enhanced rich multimedia services along the lines of those currently present in the internet world.
+
+Presence is an attribute related to, but quite different from mobility information, and is a service that can be exploited to create additional services. The types of services that could be supported by the presence service may include:
+
+- New communications services
+
+The presence service will enable new multimedia services to exploit this key enabler to support other advanced multimedia services and communications. These new services may infer the context, availability and willingness of a user to accept or participate in particular types of communications by accessing the presence information for the user's devices and services. Examples of such new multimedia services that could potentially exploit the presence service include "chat", instant messaging, multimedia messaging, e-mail, , handling of individual media in a multimedia session etc.
+
+- Information services
+
+The presence service may also be exploited to enable the creation of services in which abstract entities are providing the services to the mobile community. The presence service may be used to support such abstract services as cinema ticket information, the score at a football match, motorway traffic status, advanced push services etc.
+
+- Enhanced existing services
+
+Existing services may also be significantly enhanced by exploiting the presence information. For example a user may dynamically arrange for his wireless services to be supported through his corporate PABX whilst he is on-site, require media to be converted and directed to specific devices (e.g. user cannot accept a voice call whilst in a meeting, but is prepared to receive the voice call converted to text in the form of an SMS/MMS/e-mail message). The presence service may also be used to enable the creation of advanced versions of CS/PS services, enable terminal capabilities support etc.
+
+The following figure 1 represents a logical overview of how services could exploit the presence service to create advanced services.
+
+![Figure 1: Logical presence service support of services. The diagram illustrates the logical overview of how services could exploit the presence service to create advanced services. It shows a central 'Home Environment' cloud containing 'PS domain', 'CS domain', and 'IMS' components, with a 'Presence' server at the center. To the left, 'Presence-enhanced' services (Voice, Data, Supplementary, Multimedia) are shown interacting with the 'Presence' server. To the right, 'Visited networks', 'Internet', and 'Other networks' are shown, with 'Abstract entities' (represented by icons of a person, a computer, and a map) interacting with the 'Presence' server and the networks. Arrows indicate the flow of information and services between these components.](ca5566458a134032dd860e88fdaa0d2b_img.jpg)
+
+Figure 1: Logical presence service support of services. The diagram illustrates the logical overview of how services could exploit the presence service to create advanced services. It shows a central 'Home Environment' cloud containing 'PS domain', 'CS domain', and 'IMS' components, with a 'Presence' server at the center. To the left, 'Presence-enhanced' services (Voice, Data, Supplementary, Multimedia) are shown interacting with the 'Presence' server. To the right, 'Visited networks', 'Internet', and 'Other networks' are shown, with 'Abstract entities' (represented by icons of a person, a computer, and a map) interacting with the 'Presence' server and the networks. Arrows indicate the flow of information and services between these components.
+
+**Figure 1: Logical presence service support of services**
+
+A presence-enabled service as observed by the user is a service in which the user can control the dissemination of his presence information to other users and services, and also be able to explicitly identify specifically which other users and services to which he provides presence status. Combined with the capability of other users' control of their own presence status, virtually infinite combinations of users and services interacting at different levels can be created.
+
+The exploitation of the presence service is already available in the internet world, although unfortunately with different non interoperable mechanisms. This specification identifies the requirements for support of an enhanced version of the presence service through the support of attributes (e.g. services, media components of a multimedia service, location information) in an interoperable manner within both wireless and fixed networks, and with external networks.
+
+# --- 1 Scope
+
+This TS defines the stage one description for the presence service. Stage one is the set of requirements which shall be supported to enable the exploitation of the presence service, seen primarily from the users' and home environments' points of view.
+
+This TS includes information applicable to the home environment, device and network manufacturers which are sufficient to provide complete support of the presence service.
+
+Additional functionalities not documented in this TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the presence service defined in this specification.
+
+# --- 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: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications".
+- [2] Void
+- [3] RFC 2778: "A Model for Presence and Instant Messaging"; <http://www.ietf.org/rfc.html>.
+- [4] RFC 2779 "Instant Messaging / Presence Protocol Requirement"; <http://www.ietf.org/rfc.html>.
+- [5] RFC 3863 " Presence Information Data Format (PIDF)"; <http://www.ietf.org/rfc.html>.
+
+## 2.1 Acknowledgement
+
+This document contains extracts of documents, the copyright of which is vested in the Internet Society. The terms of the Internet Society copyright are fulfilled by the reproduction of the copyright and paragraph below. This copyright only applies to text in this document that has been directly reproduced from the appropriate RFC.
+
+Copyright (C) The Internet Society (2000). All Rights Reserved.
+
+This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+**Access rules:** constraints on how the presence service makes presence information available to watchers. For each presentity's presence information, the applicable access rules are managed by the principal that controls the presentity.
+
+**availability:** a property of a presentity denoting its ability and willingness to communicate based on factors such as the identity or properties of the watcher and the preferences and/or policies that are associated with the presentity
+
+**fetcher:** a form of watcher that has asked the presence service for the presence information of one or more presentities, but is not requesting a notification from the presence service of (future) changes in a presentity's presence information.
+
+**identifier:** a means of indicating a point of contact, intended for public use such as on a business card. Telephone numbers, email addresses, and typical home page URLs are all examples of identifier in other systems.
+
+**poller:** a fetcher that requests presence information on a regular basis.
+
+**presence information:** is a set of attributes characterising current properties of presentities such as status, an optional communication address and other optional attributes etc
+
+**presence service:** the capability to support management of presence information between watchers and presentities, in order to enable applications and services to make use of presence information
+
+**presentity (presence entity):** any uniquely identifiable entity that is capable of providing presence information to presence service. Examples of presentities are devices, services etc. Any presentity shall have one, and only one, principal associated with it.
+
+**principal:** human, organisation, program, or collection of humans, organisations and/or programs that chooses to appear to the presence services as a single actor, distinct from all other principals. A principal is associated with one or more presentities and/or watchers. A principal is said to "own" a certain presentity or watcher if such an association exists. Within the context of this specification a subscriber may be a principal to one or more presentities and/or watchers. Examples: A subscriber may be a principal to the terminals (the presentities) he owns. A program, providing a stock exchange information service to customers, may be the principal to the market quotations (the presentities) it monitors.
+
+Note: The case where a presentity is not a subscriber requires to be further considered
+
+**subscribed-watcher:** a subscribed-watcher is a type of watcher, which requests notification from the presence service of changes in a presentity's presence information, resulting in a watcher-subscription, as they occur in the future.
+
+**watcher-subscription:** the information kept by the presence service about a subscribed-watcher's request to be notified of changes in the presence information of one or more presentities
+
+Note: This definition represents an entity's request to obtain presence information, and is not related to the term "subscription" in [1]. Within this specification the term watcher-subscription (and its derivatives) purely refers to this relationship.
+
+**watcher:** any uniquely identifiable entity that requests presence information about a presentity, or watcher information about a watcher, from the presence service. Special types of watcher are fetcher, poller, and subscribed-watcher. Any watcher shall have one, and only one, principal associated with it.
+
+**watcher information:** information about watchers that have received or may receive presence information about a particular presentity within a particular recent span of time.
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+|      |                                 |
+|------|---------------------------------|
+| IETF | Internet Engineering Task Force |
+| LAN  | Local Area Network              |
+| VHE  | Virtual Home Environment        |
+
+# 4 Presence models
+
+# 4a A brief introduction to the Presence Service
+
+This clause attempts to give a simplistic high level informative overview of what presence is from a user's perspective, and how it is used to published to, and accessed by, other users.
+
+Mark's ability and willingness to be reached for communication is defined by a set of information known as presence information. Mark's presence information may be related to his mobile network connection status, however it represents much more than just whether he has network coverage or not. Mark also defines a set of access rules to control access to his presence information. For the presence service, Mark is represented by a presentity (presence entity) associated with Mark's presence information and set of access rules.. In this example, Mark's presence information consists of user status and location information.
+
+![Diagram illustrating the presence service. Mark is the principal, represented by a presentity containing User Status and Location information. Other users (Paggy, Paul, Jude, and a Watcher group) are accessing this information. Paggy, Paul, and Jude are shown with speech bubbles indicating they are checking Mark's status. The Watcher group is shown with a speech bubble indicating they are checking Mark's status. The presentity is represented by an orange oval containing a table with User Status and Location information, and an Access Rules section.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+The diagram shows Mark as the principal, represented by a presentity (orange oval) containing a table with User Status and Location information, and an Access Rules section. Other users (Paggy, Paul, Jude, and a Watcher group) are shown with speech bubbles indicating they are checking Mark's status. The presentity is represented by an orange oval containing a table with User Status and Location information, and an Access Rules section.
+
+|               |             |              |
+|---------------|-------------|--------------|
+| Available     | User Status | Access Rules |
+| Discreet      |             |              |
+| Not available |             |              |
+| Invisible     |             |              |
+| City          | Location    |              |
+| Country       |             |              |
+
+Diagram illustrating the presence service. Mark is the principal, represented by a presentity containing User Status and Location information. Other users (Paggy, Paul, Jude, and a Watcher group) are accessing this information. Paggy, Paul, and Jude are shown with speech bubbles indicating they are checking Mark's status. The Watcher group is shown with a speech bubble indicating they are checking Mark's status. The presentity is represented by an orange oval containing a table with User Status and Location information, and an Access Rules section.
+
+**Figure 1: Principal and his representation in the presence information as a presentity**
+
+As well as representing a user such as Mark, a presentity may even be created to represent an abstract service or application (e.g. to provide road traffic information, sports results, news headlines etc.). The entity represented by the Presentity (in this case Mark) controls the supply of information for the presentity and is known as the principal; thus Mark is principal of his presentity (see Figure 1).
+
+Paggy, Paul and Jude (e.g. Mark's callers or instant messaging buddies) who want to determine Mark's ability (and willingness) to communicate may do so by checking the status information in Mark's presentity. By doing so, Paggy, Paul and Jude become watchers of Mark (see Figure 2).
+
+![Figure 2: Watchers of Mark. A diagram showing Mark's presence information being accessed by Paggy, Paul, and Jude. Mark is shown on the right with a speech bubble 'Hello, weather is great here!'. On the left, Paggy, Paul, and Jude are shown with speech bubbles. Paggy says '...I think the car alarm is playing up...', Paul says '...see you in the bar at 7:30', and Jude says '...shame, Mark can't tell me where Paul is'. Below them, a 'Watcher group' has a speech bubble '...looks like Mark is not around!'. In the center, an orange oval labeled 'Mark's Presentity' contains a table with 'User Status' (Available, Discreet, Not available, Invisible) and 'Location' (City, Country), and a box for 'Access Rules'. Arrows show Paggy (blue) and Paul (purple) accessing the 'User Status' and 'Location' respectively. Jude (red) is shown accessing the 'Location' but receiving no information. The 'Watcher group' (red) is shown accessing the 'Location' and receiving information about Mark's availability.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+...I think the car alarm is playing up...
+
+...see you in the bar at 7:30
+
+...shame, Mark can't tell me where Paul is
+
+...looks like Mark is not around!
+
+Paggy
+
+Paul
+
+Jude
+
+Mark
+
+Watcher group
+
+Mark's Presentity
+
+|               |             |              |
+|---------------|-------------|--------------|
+| Available     | User Status | Access Rules |
+| Discreet      |             |              |
+| Not available |             |              |
+| Invisible     |             |              |
+| City          | Location    |              |
+| Country       |             |              |
+
+Figure 2: Watchers of Mark. A diagram showing Mark's presence information being accessed by Paggy, Paul, and Jude. Mark is shown on the right with a speech bubble 'Hello, weather is great here!'. On the left, Paggy, Paul, and Jude are shown with speech bubbles. Paggy says '...I think the car alarm is playing up...', Paul says '...see you in the bar at 7:30', and Jude says '...shame, Mark can't tell me where Paul is'. Below them, a 'Watcher group' has a speech bubble '...looks like Mark is not around!'. In the center, an orange oval labeled 'Mark's Presentity' contains a table with 'User Status' (Available, Discreet, Not available, Invisible) and 'Location' (City, Country), and a box for 'Access Rules'. Arrows show Paggy (blue) and Paul (purple) accessing the 'User Status' and 'Location' respectively. Jude (red) is shown accessing the 'Location' but receiving no information. The 'Watcher group' (red) is shown accessing the 'Location' and receiving information about Mark's availability.
+
+Figure 2: Watchers of Mark
+
+To protect his privacy and confidentiality, Mark has full control over whether Paggy, Paul and Jude, or any other group of watchers, can access his presence information. Mark may give different watchers different levels of access so that, for example Paggy can see all of Mark's of presence information, Paul may only see part of it, and Jude can see none of it. Hence, Mark can control (per watcher) which parts of his presence information may be seen, and he may decide that specific watchers have restricted access, and that some do not have any access at all. Indeed, Mark may also define his presence information and set up his access rules so that some watchers are given different information (e.g. Jude is told that Mark is not available, when in fact he is available), see Figure 3.
+
+![Figure 3: Application of Mark's access rules on watchers. This diagram is identical to Figure 2, but it illustrates the application of Mark's access rules. Paggy (blue) and Paul (purple) have arrows pointing to the 'User Status' and 'Location' respectively. Jude (red) has an arrow pointing to the 'Location' but no information is returned. The 'Watcher group' (red) has an arrow pointing to the 'Location' and receives information about Mark's availability.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+...I think the car alarm is playing up...
+
+...see you in the bar at 7:30
+
+...shame, Mark can't tell me where Paul is
+
+...looks like Mark is not around!
+
+Paggy
+
+Paul
+
+Jude
+
+Mark
+
+Watcher group
+
+Mark's Presentity
+
+|               |             |              |
+|---------------|-------------|--------------|
+| Available     | User Status | Access Rules |
+| Discreet      |             |              |
+| Not available |             |              |
+| Invisible     |             |              |
+| City          | Location    |              |
+| Country       |             |              |
+
+Figure 3: Application of Mark's access rules on watchers. This diagram is identical to Figure 2, but it illustrates the application of Mark's access rules. Paggy (blue) and Paul (purple) have arrows pointing to the 'User Status' and 'Location' respectively. Jude (red) has an arrow pointing to the 'Location' but no information is returned. The 'Watcher group' (red) has an arrow pointing to the 'Location' and receives information about Mark's availability.
+
+Figure 3: Application of Mark's access rules on watchers
+
+Mark's presentity consists of dynamic and static information supplied directly by himself and/or by the network. Some of the dynamic information may be derived from a number of sources (e.g. equipment login/attachment, roaming status, keyboard activity monitoring, equipment type, location information etc.). An example of the static information could be a fixed telephone number. The network may also add further information to the presentity (e.g. the evening/night times when his mobile is usually switched off derived from his usage patterns) to provide customised presence information.
+
+By supporting a presence service in the network, the operator has the capability to offer an exciting range of advanced presence-based services and applications.
+
+## 4.1 Informative models
+
+The below models of the presence service and presence information are not definitive, and no implementation model or architecture is implied or required by them, and are solely provided to describe the functions and roles that shall be provided by the presence service.
+
+## 4.2 Roles in the presence service
+
+![Figure 2: Presence service model diagram showing nested presence information structures.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+The diagram illustrates the 'PRESENCE INFORMATION' model. It is contained within a large grey rectangular box. Inside this box, at the top, is a green 3D-style box labeled 'PRESENCE TUPLE'. This box contains three stacked sub-sections: 'STATUS', 'COMMUNICATION ADDRESS' (which further contains 'Communication means' and 'Contact address'), and 'OTHER PRESENCE MARKUP'. Below this first 'PRESENCE TUPLE' box, there are three vertical dots indicating a list of similar items. Below the dots is a second identical 'PRESENCE TUPLE' box, also containing 'STATUS', 'COMMUNICATION ADDRESS' (with 'Communication means' and 'Contact address'), and 'OTHER PRESENCE MARKUP'.
+
+Figure 2: Presence service model diagram showing nested presence information structures.
+
+Figure 2: Presence service model
+
+The presence service may be considered to support two main roles, as depicted in figure 2 "Presence service model".
+
+For the purposes of this TS, the following roles are identified to support the presence service:
+
+- Suppliers of presence information
+
+This role represents those entities that supply presence information.
+
+- Requesters of presence information
+
+This role represents those entities which request (and subsequently receive) presence information of a presentity. The presence information may also maintain data on requesters of presence information, which may also be potentially distributed (on request) to requesters of presence information. The term watchers is used to identify the requesters of presence information.
+
+The requesters of presence information may be associated with 2 modes of operation:
+
+- Information Mode
+
+This mode corresponds to a request-response mode and represents those entities (i.e. watchers) which simply request the current presence information of a presentity. The term "fetchers" is used to identify the receivers of this type of presence information of a presentity. The term "pollers" identifies the type of fetchers that request the presence information of a presentity on a regular or periodic basis.
+
+- Notification Mode
+
+This mode corresponds to a 'push-type' mode and represents those entities (i.e. watchers) which request notifications on (future) changes in presence information of a presentity. The term subscribed-watchers is used to identify the receivers of these notifications. Watcher-subscriptions for subscribed-watchers are soft-stated i.e. they are time-bound, notifications of presence information cease on expiry of the negotiated interval. The subscribed-watcher is allowed to 'refresh' a watcher-subscription at any time. Watcher-subscription refreshes overwrite an existing watcher-subscription for the same presentity, subject to the presentity's access rules.
+
+![Figure 3: Presence Service Entity Relationships. The diagram shows a stack of 'PRESENCE INFORMATION' blocks. Each block contains a 'PRESENCE TUPLE' which is further divided into 'STATUS', 'COMMUNICATION ADDRESS' (with sub-fields 'Communication means' and 'Contact address'), and 'OTHER PRESENCE MARKUP'. There are two such tuples shown, separated by three vertical dots, indicating a list of tuples.](18442e4e239480f0c3c95b547aa8fde2_img.jpg)
+
+Figure 3: Presence Service Entity Relationships. The diagram shows a stack of 'PRESENCE INFORMATION' blocks. Each block contains a 'PRESENCE TUPLE' which is further divided into 'STATUS', 'COMMUNICATION ADDRESS' (with sub-fields 'Communication means' and 'Contact address'), and 'OTHER PRESENCE MARKUP'. There are two such tuples shown, separated by three vertical dots, indicating a list of tuples.
+
+**Figure 3: Presence Service Entity Relationships**
+
+The key concepts captured in figure 3 are as follows:
+
+- a principal may be associated with one or more watchers
+- a watcher is associated with one principal
+- a presentity is associated with one principal
+- a principal may be associated with one or more presentities.
+- a presentity may be associated with one or more presence-tuples
+
+- a watcher can have a watcher-subscription to one or more presentities
+- a presentity may be watched by one or more watchers
+
+## 4.3 Presence information
+
+A logical model of a presentity's presence information consists of an arbitrary number of elements, known as presence tuples, as depicted in figure 4. Presence information for each presentity is identified by a unique identifier.
+
+![Figure 4: Presence information diagram showing nested boxes for Presence Information, Presence Tuple, Status, Communication Address, and Other Presence Markup.](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+The diagram illustrates the hierarchical structure of presence information. A large grey box labeled 'PRESENCE INFORMATION' contains two identical 'PRESENCE TUPLE' boxes, separated by three vertical dots. Each 'PRESENCE TUPLE' box is a nested structure containing the following elements in order from top to bottom: 'STATUS', 'COMMUNICATION ADDRESS' (which further contains 'Communication means' and 'Contact address'), and 'OTHER PRESENCE MARKUP'.
+
+Figure 4: Presence information diagram showing nested boxes for Presence Information, Presence Tuple, Status, Communication Address, and Other Presence Markup.
+
+Figure 4: Presence information
+
+Each such presence tuples contains the following information as described in RFC 2778 [3]:
+
+- status
+
+Table 1: Status
+
+| Item   | Explanation                                                                                | Example Values                                                 |
+|--------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| status | Indicates the current condition of the device or service represented by the presence tuple | open, closed, online, offline, busy, away, do not disturb etc. |
+
+- communication address
+
+consists of a communication means and a contact address
+
+**Table 2: Communication address**
+
+| Item                | Explanation                                                                     | Example Values                                                                                                                                 |
+|---------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| communication means | Information indicating a method whereby communication can take place            | service type (e.g. telephony, SMS), media type (e.g. audio, video, text message), multimedia messaging service, instant messaging service etc. |
+| contact address     | Information indicating a specific point of contact via some communication means | E.164, URI, instant inbox address etc                                                                                                          |
+
+- other presence markup
+
+any additional presence information
+
+# 5 High level requirements
+
+## 5.1 Home Environment requirements
+
+The presence service shall provide the ability for the home environment to manage the presence information of users' devices, services and service media, even when roaming. The home environment shall be able to be both the supplier of presence information (i.e. presentities), as well as the requesters of presence information (i.e. watchers). The presence service can be regarded as a Home Environment service or a Home Environment – Value Added Service Provider (HE-VASP) service.
+
+The home environment requirements for the support of the presence service are defined in 5.3 General requirements, and the applicable requirements in 5.4 Management requirements and 5.5 Notification and acknowledgement requirements.
+
+External networks (e.g. those in other PLMN's, the Internet, LANs etc.) currently support several different forms of presence service. The presence service shall enable the network to present a consistent and interoperable support of presence, such that the presence capability users can interwork with one or more other external presence services.
+
+## 5.3 General requirements
+
+The following general requirements for the presence service shall be supported:-
+
+- Presence information
+  - presence information for presentities shall be made available in a standardised presence information format to enable interoperability within networks.
+  - presence information for presentities shall be made available in a standardised presence information format to enable interoperability with IETF specified presence information formats (e.g. RFC 2778 [3], RFC 2779 [4] and RFC3863 [5])
+  - presence information for presentities shall be extensible to represent additional information, without undermining the standardised format (e.g. device capabilities)
+  - presence information for presentities shall include a means to uniquely identify the presentity
+  - presence information for presentities shall define a particular type of presentity, representing a subscriber, with a minimum set of attributes as described below for interoperability within networks. The values for these attributes are to be determined in the Stage 2/3 specifications.
+
+In addition to the generic requirements described above, the presence information representing a subscriber:
+
+- may include a subscriber's status attribute describing the subscriber's willingness to communicate (e.g. available, unavailable). It does not identify the status of the device (e.g. registration or attachment to the network) or of any application.
+
+This attribute is controlled by the subscriber. It shall be possible for this subscriber's status to be provided by the subscriber, or by the network on behalf of the subscriber (subject to the subscriber's agreement). For example the subscriber could define that he's unavailable each day between 10 p.m. and 7 a.m., and the network would then be responsible for the subscriber's status update.
+
+The format and values of this attribute shall be standardised.
+
+Note: It is to be determined in the Stage 2/3 specifications how the Status field (in RFC2778 [3]) in notifications is completed, and whether or not the values in the subscriber status attribute, network status attribute or other information are used.
+
+- b) may include a network status attribute describing the connectivity state of the device used by the subscriber. This attribute could for example be defined using information describing the subscriber's state of connectivity to the network (e.g. attached, call active, CS attached, CS Call active with bearer information, IMS registered, PDP context information etc...).
+
+This attribute is controlled by the network.
+
+The format and values of this attribute shall be standardised.
+
+Note: It is to be determined in the Stage 2/3 specifications how the Status field (in RFC2778 [3]) in notifications is completed, and whether or not the values in the subscriber status attribute, network status attribute or other information are used.
+
+- c) may include one or more communication means (e.g. SMS, telephone, e-mail, multimedia session...) and their contact addresses (e.g. MSISDN, e-mail address, NULL...) by which the subscriber may be contacted.
+
+This attribute is controlled by the subscriber. It shall be possible for this information to be provided by the subscriber, or by the network on behalf of the subscriber (subject to the subscriber's agreement).
+
+The format and values of the communication means shall be standardised, and the format of the contact address shall be standardised.
+
+- d) may include two types of location information, one provided by the network (e.g. geographical co-ordinates) and/or one provided by the subscriber (e.g. "at home").
+
+The network provided location is controlled by the network, and the subscriber provided location information is controlled by the subscriber. It shall be possible for the subscriber provided location information to be furnished by the subscriber, or by the network on behalf of the subscriber (subject to the subscriber's agreement).
+
+The format of the network provided location shall be standardised, and the format of the subscriber provided location shall be standardised.
+
+- e) may include a priority attribute giving a relative priority for each of the defined communication means and contact address pairs. It is via this priority attribute that the subscriber can indicate his preference for the order in which the communication means and contact address pairs should be used.
+
+This attribute is controlled by the subscriber. It shall be possible for the priority information to be provided by the subscriber, or by the network on behalf of the subscriber (subject to the subscriber's agreement).
+
+The format and values of this attribute shall be standardised.
+
+- f) may include a text attribute (e.g. "In a meeting until 4 p.m.")
+
+This attribute is controlled by the subscriber. It shall be possible for the text information to be provided by the subscriber, or by the network on behalf of the subscriber (subject to the subscriber's agreement).
+
+The format of this attribute shall be standardised.
+
+- b) A means to uniquely identify the watcher
+- c) Forward compatible presence service
+
+Presence service shall leverage current and evolving presence technology by re-using existing standards as far as possible and proposing extensions (as necessary) to existing standards.
+
+### d) Interoperability with external presence services
+
+External networks (e.g. those in other PLMN's, the Internet, LANs etc.) currently support several different forms of presence service. The presence service shall enable the network to present a consistent and interoperable support of presence, such that the presence capability users can interwork with one or more other external presence services.
+
+### e) Consistent and interoperable presence service
+
+Regardless of the service using presence information, the presence service shall be supported in a consistent and interoperable manner between the UE and the network
+
+### f) Transport independence
+
+It shall be possible to use the presence service independent of the bearer or transport mechanism. Restrictions may apply due to the nature of the underlying transport mechanism (e.g. a CS or PSTN terminal may not be capable to supply the same presence information as a terminal attached to the IM CN Subsystem)
+
+### g) Presence service quality of service
+
+- i) the Presence Service shall enable a watcher, if required, to request a time after which delivery of the requested information shall not take place.
+- ii) the Presence Service shall enable a presentity to indicate an expiry time for the presence information, if required.
+- iii) the Presence Service shall enable presence information delivered to a watcher to be marked with an expiry time, if required.
+
+### h) Presence and other user services
+
+The operation of Presence Service may be offered both in parallel and independent of other services, e.g. supplementary services, teleservices, bearer services or any other services.
+
+### i) Simultaneous access to presence information from multiple terminals
+
+It shall be possible to access presence information simultaneously from multiple terminals (e.g. presentity or watcher would be able to access the presence service via mobile phone and PC).
+
+### j) Access to the presence service from external applications
+
+It shall be possible for external applications to be presentities/watchers.
+
+## 5.4 Management requirements
+
+The following management requirements shall be supported for the presence service:
+
+### a) Access control to the presence information
+
+The presentity shall be able to manage the access to its presence information in compliance with the principal's privacy and access rules requirements detailed in 6.1 and 6.2.
+
+The presentity shall have the ability to accept or reject a request for presence information on a per watcher basis, with the option:-
+
+- i) once only per watcher (e.g. set up access rules for known watcher, groups of watchers, anonymous watcher-subscriptions, etc.),
+- ii) for each presence information request (e.g. for watchers that are unknown or not set up in the current access rules).
+
+It shall be possible for the presence service to make access control decisions on behalf of the presentity (e.g. when the presentity is out of contact) subject to the principal's privacy.
+
+It shall be possible to inform the presentity of watcher-subscription requests
+
+It shall be possible to report existing watcher-subscriptions to the presentity (on request or periodically).
+
+It shall be possible for the presentity to request the watcher information.
+
+- b) Not used
+- c) Supplying data to the presence information
+
+When supplying data it shall be possible to update only part of the presence information.
+
+- d) Requesting data from the presence information
+
+It shall be possible to request the current value of presence information data on demand at any time (i.e. a fetcher) or on a periodic basis (i.e. a poller) subject to principal's privacy, or to be notified of subsequent changes in presence information data (except when such notification is prevented by access rules)
+
+It shall be possible for a watcher to define which parts of a presentity's presence information it receives, subject to the principal's privacy requirements.
+
+It shall be possible for watcher to request presence information anonymously (i.e. the watcher's identifier will not be revealed to the presentity). This request can be accepted or rejected, depending on the principal's privacy.
+
+A Watcher's interest to a presentity's presence information shall not be revealed to other watchers.
+
+Watcher-subscription to a presentity's presence information
+
+- i) an entity shall be able to watcher-subscribe to a presentity's presence information at any time, i.e. to request notification from the presence service of (future) changes in any of the attributes or only in the attributes specified by the watcher (subject to the principal's privacy). Note, that by this watcher-subscription the entity becomes a subscribed-watcher.
+  - ii) subscriptions are soft-stated. The subscribed-watcher shall be able to refresh a watcher-subscription to the presentity's presence information at any time. A watcher-subscription refreshes overwrite an existing watcher-subscription for the same presentity, subject to the presentity's access rules – the duration of a watcher-subscription starts from the time it is accepted.
+  - iii) the subscribed-watcher shall be able to determine the status of his watcher-subscription to that presentity's presence information, at any time.
+  - iv) the subscribed-watcher shall be able to cancel his watcher-subscription to a presentity's presence information at any time. Whenever a subscribed-watcher withdraws its watcher-subscription from a presentity's presence information, the subscribed-watcher shall no longer be receiving notifications regarding the presentity's presence information.
+  - v) an unauthorised third party shall not be able to cancel a subscribed-watcher's watcher-subscription to a presentity's presence information
+- e) User availability and mobility
+
+The presence service shall continue to be supported if the environment into which the user has moved supports presence service. The presence service shall take into account changes in the availability of users (e.g. the user is out of contact or not reachable, despite having activated his presence) or his mobility (e.g. wherever he may be in his home environment or in a visited network).
+
+- f) Not used
+
+- g) Access to presence service
+
+- i) it shall be possible for the presence service to accept presence information from a presentity at any time
+  - ii) it shall be possible for the presence service to accept requests from, and provide presence information to, an authorised watcher at any time
+
+## 5.5 Notification and acknowledgement requirements
+
+The following notification and acknowledgement presence service requirements shall be supported:-
+
+- a) Presence data modification and monitoring requests
+
+The presence service shall be able to support the acknowledgement of any requests to monitor a presentity's presence information (i.e. from watchers)
+
+If a subscribed-watcher establishes a watcher-subscription to a presentity's presence information:-
+
+- i) the presence service, depending on the presentity's access rules, shall inform the subscribed-watcher if the presentity refused the subscribed-watcher's watcher-subscription
+- ii) if the subscribed-watcher's watcher-subscription to presentity's presence information is cancelled, the presence service shall inform the subscribed-watcher of the cancellation
+- iii) it shall be possible for the presentity to configure the presence service to deny a subscribed-watcher's subscription, whilst appearing to the subscribed-watcher as if the subscription has been granted (this is sometimes called "polite blocking")
+
+# --- 6 Privacy
+
+## 6.1 General privacy requirements
+
+The privacy aspect of presence information and the need for authorisation before providing presence information shall be configurable by the user (i.e. presentity).
+
+The following privacy requirements shall be supported:-
+
+- principal's privacy
+
+a principal of a presentity shall, at any time, be able to control to whom, for how long and what (all or part of) presence information of the presentity is provided, and a principal of a watcher shall, at any time, be able to control to whom, for how long and what (all or part of) watcher information of the watcher is provided
+
+Note: need to consider where subscriber's privacy (as distinct from principal's privacy) requires to be addressed.
+
+Any services using the presence information shall ensure privacy agreement before releasing presence information. The presence service does not address deployment specific issues (e.g. where agreements are stored or how they are negotiated). It only gives requirements for privacy management.
+
+Specific local, national, and regional privacy regulations shall be complied with. In particular, an operator shall, at any time, be able to override principal's privacy if required to do so.
+
+## 6.2 Access rules
+
+The principal that controls the presentity shall be able to define access rules, in order to control how the presentity's presence information is made available for watchers.
+
+These access rules shall define:
+
+- a watcher or groups of watchers allowed access to the presentity's presence information. For example: watchers x and y are allowed, or only watchers in group z are allowed, or all watchers and groups are allowed.
+- the validity of the access authorisation granted for a given watcher or groups of watchers. The access to the presentity's presence information can be restricted for a certain period (i.e. duration or number of requests), or during specific periods of the day.
+- the attributes of the presentity's presence information that can be made available to a given watcher or groups of watchers.
+
+- the ability to provide different presence information (i.e. both number of attributes and values of attributes) based on the watcher, and principal's preferences (e.g. its availability). For example: watcher x receives 'Online/Instant Messaging/im:a@there.com', while group y receives 'Offline/Instant Messaging/im:a@there.com'.
+
+A set of default access rules shall be defined by the principal.
+
+# --- 7 Security
+
+The use and access to the presence service shall be supported in a secure manner. It shall only be possible for the presence information to be supplied and/or updated by the presentity or the home environment as identified in clause 5 "High Level Requirements".
+
+It shall be possible to authenticate a principal before allowing registration to the presence service.
+
+It shall be possible to authenticate at any time a watcher and/or a presentity requesting access to the presence service. Existing security mechanisms as well as mechanisms specific to presence service may be used.
+
+It shall be possible to protect the following items from attacks (e.g., eavesdropping, tampering, and replay attacks):
+
+- Presence information and notifications
+- Requests for presence information, e.g., requests for subscription and requests for presence information retrieval.
+
+# --- 8 Charging
+
+The presence service shall be able to support various charging mechanisms both for On-line and Off-line charging. The following charging characteristics shall be considered:
+
+- charging for a user's registration as a presentity
+- charging for each subscription to presence information for a user
+- charging for presence information retrieval for users
+- charging for presence information notifications received for users
+- charging for presence information usage when in a visited network
+
+The above list is not exhaustive.
+
+# --- 9 Administration
+
+The following administration requirements shall be supported.
+
+- Note: The different logical steps (provision, registration, activation) might be combined. For example when a principal requests a watcher-subscription, a watcher associated with him is automatically registered in the Presence Service.
+
+## 9.1 Provision
+
+Provision is an action taken by the service provider to make the presence service available to a principal. Provision may be:
+
+- General: where the service may be made available to all principals without prior arrangements being made with the service provider.
+- Pre-arranged: where the service is made available to an individual principal only after the necessary arrangements such as login name, password have been made with the service provider.
+
+This provision action shall allow the principals to subsequently register within the Presence Service as a presentity, as a watcher or as both.
+
+## 9.2 Withdrawal
+
+Withdrawal is an action taken by the service provider to withdraw the presence service from the principal. Withdrawal may be:
+
+- General: where the presence service is removed from all principals
+- Specific: where the presence service is removed per principal.
+
+## 9.3 Registration
+
+Registration is an action taken by the service provider or the principal to provide information necessary for presentities and/or watchers to use the Presence Service. For example, a subscriber could request the creation of a presentity associated with him and provide the corresponding access rules.
+
+It shall be possible to take this registration action under the condition that the presence service is available for the principal. (i.e. the provision has been performed previously).
+
+This registration process may be performed at any time by the principal or service provider to create new presentities/watchers.
+
+The service provider may provide privacy control at registration time on behalf of a presentity.
+
+## 9.4 Erasure
+
+Erasure is an action taken at any time by the service provider or the principal in order to cancel a registration.
+
+## 9.5 Activation
+
+Activation is an action taken at any time by the service provider, the presentity or the watcher to bring the Presence Service into the active state.
+
+It shall be possible to activate the service once the presentity or watcher has been registered.
+
+Once the presentity or watcher is in an active state,
+
+- This presentity or watcher may invoke Presence Service features
+- Other presentities or watchers may invoke Presence Service features concerning this presentity or watcher (e.g. by subscribing to its presence information)
+- The Presence Service may invoke Presence Service features concerning this presentity or watcher (e.g. by notifying changes in the presence information)
+
+## 9.6 Deactivation
+
+Deactivation is an action taken at any time by the service provider, the presentity or the watcher to bring the Presence Service into the non-active state.
+
+## 9.7 Invocation
+
+Invocation is an action taken at any time by the presentity or watcher (e.g. by requesting presence information) or by the Presence Service as a result of a particular condition (e.g. by notifying presence information's changes) in order to invoke the Presence Service features.
+
+# --- Annex A (informative): Example presence service use cases
+
+## Immediate Messaging Use Case
+
+- Premise:
+  - User is in-and-out of coverage
+  - Others wish to send a message and get a response - now
+- Considerations
+  - User's Presence provides info regarding availability (Yields measure of Probability of message delivery)
+- Presence capability can be separated from IM
+  - Functional Separation
+- Sequence
+  - User is out and about (having meetings or just travelling)
+  - Availability status gets updated as needed (User control - change to 'unavailable - in meeting', Network control - out-of-coverage / busy-in-call)
+- Co-worker wants to send you a note
+  - Check of Presence Info lets others see if user is available (If available - provides addressing info (e.g. IM server / account ids))
+- IM Server handles message deliveries
+  - Status updates available at any time
+
+## Location Info in Presence Use Case
+
+- Premise:
+  - User is travelling per a schedule
+  - Others looking to find out when user will arrive
+  - Alternative model is to know where to go to meet user
+- Considerations
+  - User's Presence Info could have activity indicator (e.g. 'in a meeting' or 'driving')
+- System may have access to location information on user
+  - Issue would be the granularity/resolution
+- System may have access to user's 'calendar'
+  - Would make a plan available
+- Security/authentication aspects of disclosures
+- Sequence
+  - User is out and about (having meetings or just travelling (Assume that user activity indication available (For example: 'unavailable - driving')))
+  - System could correlate location information with activity (Answer questions like - is user at planned meeting?, If travelling, could correlate distance with minimum transit time)
+
+System could maintain progress on plan from calendar (System may be able to determine if user is running late or not, User could revise plan or provide annotated information)
+
+Co-worker wants to know if you are available (System provides current activity, possible links to schedule)
+
+- Family wants to know if user is on way home
+
+Activity indication of 'driving' may assist in determination
+
+Current location info could help determine how far from home
+
+- Meet-me example
+
+Service may correlate matching info (Example where Activity Indication - 'Shopping' & Location - 'Mall', Friend with matching codes could be flagged, Could IM to determine which store or to have lunch)
+
+Service could manage meeting maker (May have appointment scheduled with others, Could check status to see if everybody was in right location)
+
+## Message Modality Control Use Case
+
+- Premise:
+
+User has different means to communicate (voice, text...)
+
+User may indicate preferences
+
+Voice number is managed by entity monitoring status
+
+- Considerations
+
+Content format adaptation available (e.g. text-to-speech (synthetic voice) or speech-to-text)
+
+User preferences set desired message format (May change the official communication device address)
+
+Related services subscribe to user status (Cell net could be watcher to provide value-add/quick routing)
+
+- Sequence
+
+User is in a meeting (can't take a phone call)
+
+Status shows 'busy - in a meeting' (Presence status listed as 'unavailable for voice', Option for speech-to-text delivery provided if available)
+
+If friend can send text - does so (Works as expected)
+
+If friend has a voice device (Calls into user's number, Switch sees speech delivery disabled - conversion offered, Switch connects caller to speech-to-text converter, Text is sent to user, If caller stays on circuit, could engage in two-way dialog)
+
+- Premise:
+
+User is travelling and changes plane
+
+Others looking to communicate with the user
+
+Service available to 'take a message'
+
+- Considerations
+
+Service has access to User's state
+
+Service could be associated with User info (May be dependent on state or watcher identification)
+
+Service may deliver 'markup' contact for reply (Ideal is to enable programmable or responsive operations)
+
+## Traveler Changing Planes Use Case
+
+- Sequence
+
+User is on a plane
+
+User (more correctly - device) is not connected to any network (Presence status listed as 'unavailable', Service ('take a message') shown as available)
+
+Friend wants to pass some info and sees 'unavailable' status (Uses 'take a message' to save a friendly note)
+
+Co-worker needs some specific info (Uses 'take a message' to record a 'get back to me' note)
+
+- User arrives at airport
+
+User (more correctly - device) is not connected to any network (Presence status listed as 'unavailable', Service ('take a message') shown as available) 'Take a Message' Service gets update and sends a report (Provides an inbox type message)
+
+User may interact to read the messages (stored by service) (Messages could be selectively managed (read/forward/delete))
+
+Addresses in Notes are associated with status information (Effectively invokes a dynamically generated buddy list, May have been entities that were not part of regular buddy list, Very easy to 'return the call' with know availability information)
+
+- User gets on next plane
+
+Status changes again - reverts to unavailable handling
+
+# Annex B (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                       |       |       |           |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|---------------------------------------------------------------------------------------|-------|-------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                       | Old   | New   | Work Item |
+|                |           |           | 22.141 |     |     |       |     | Produced during Presence Adhoc 18th-19th April, Seattle, Washington, USA              | 0.0.0 | 0.1.0 | Presence  |
+|                |           |           | 22.141 |     |     |       |     | Produced during S1 plenary 7 <sup>th</sup> -11 <sup>th</sup> May, Helsinki, Finland   | 0.1.0 | 0.2.0 | Presence  |
+|                |           |           | 22.141 |     |     |       |     | Produced for TSG-SA#12                                                                | 0.2.0 | 1.0.0 | Presence  |
+|                |           |           | 22.141 |     |     |       |     | Produced during Presence adhoc 5th-6th June, Sophia Antipolis, France                 | 1.0.0 | 1.1.0 | Presence  |
+|                |           |           | 22.141 |     |     |       |     | Produced during Presence adhoc 26th-28th June, Dallas, Texas, USA                     | 1.1.0 | 1.2.0 | Presence  |
+|                |           |           | 22.141 |     |     |       |     | Produced during Presence adhoc 10th -11th July, Lake Tahoe, Nevada, USA               | 1.2.0 | 1.3.0 | Presence  |
+|                |           |           | 22.141 |     |     |       |     | Produced during Presence adhoc 10th -11th July, Lake Tahoe, Nevada, USA               | 1.3.0 | 2.0.0 | Presence  |
+| SP-13          | SP-010444 | S1-010841 | 22.141 |     |     | Rel-5 |     | Approved at SA #13                                                                    | 2.0.0 | 5.0.0 | Presence  |
+| SP-14          | SP-010677 | S1-011059 | 22.141 | 001 |     | Rel-5 | C   | Protection against replay attacks                                                     | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-14          | SP-010677 | S1-011210 | 22.141 | 002 |     | Rel-5 | C   | Reserved for Presence                                                                 | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-14          | SP-010677 | S1-011211 | 22.141 | 003 |     | Rel-5 | C   | Clarification to Presence access rules                                                | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-14          | SP-010677 | S1-011212 | 22.141 | 004 |     | Rel-5 | B   | Clarification on charging mechanisms                                                  | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-14          | SP-010677 | S1-011213 | 22.141 | 005 |     | Rel-5 | F   | Clarification of registration and administration procedures                           | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-14          | SP-010677 | S1-010960 | 22.141 | 006 |     | Rel-5 | F   | Use of 'Principal' within TS 22.141                                                   | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-14          | SP-010677 | S1-011218 | 22.141 | 008 |     | Rel-5 | F   | Clarification of presence information requirements                                    | 5.0.0 | 5.1.0 | PRESNC    |
+| SP-15          | SP-020056 | S1-020306 | 22.141 | 009 |     | Rel-5 | D   | A brief introduction to the Presence Service                                          | 5.1.0 | 5.2.0 | PRESNC    |
+| SP-15          | SP-020056 | S1-020307 | 22.141 | 010 |     | Rel-5 | D   | Correction to the number of roles in the Presence Service                             | 5.1.0 | 5.2.0 | PRESNC    |
+| SP-15          | SP-020056 | S1-020430 | 22.141 | 011 |     | Rel-5 | C   | CR 22.141 Rel.5 Selective Notifications                                               | 5.1.0 | 5.2.0 | PRESNC    |
+| SP-15          | SP-020056 | S1-020602 | 22.141 | 012 |     | Rel-5 | F   | CR to 22.141 - Clarifications on identifier's hiding                                  | 5.1.0 | 5.2.0 | PRESNC    |
+| SP-15          | SP-020056 | S1-020619 | 22.141 | 013 |     | Rel-5 | C   | CR to 22.141 on Multiple terminal support in presence service                         | 5.1.0 | 5.2.0 | PRESNC    |
+| SP-15          | SP-020056 | S1-020623 | 22.141 | 014 |     | Rel-5 | C   | Access from external applications                                                     | 5.1.0 | 5.2.0 | PRESNC    |
+| SP-16          | SP-020267 | S1-021043 | 22.141 |     |     | Rel-6 |     | Updated from Rel-5 to Rel6; Rel5 deleted                                              | 5.2.0 | 6.0.0 |           |
+| SP-17          | SP-020560 | S1-021592 | 22.141 | 015 |     | Rel-6 | F   | Presence TS - Cleaning of requirements                                                | 6.0.0 | 6.1.0 | PRESNC    |
+| SP-17          | SP-020560 | S1-021781 | 22.141 | 016 |     | Rel-6 | F   | Presence TS - Tidy up of security requirements                                        | 6.0.0 | 6.1.0 | PRESNC    |
+| SP-19          | SP-030025 | S1-030066 | 22.141 | 017 | -   | Rel-6 | C   | Clarification of network status attribute description within Presence Service Stage 1 | 6.1.0 | 6.2.0 | PRESNC    |
+|                |           |           |        |     |     |       |     | 2004-07-02: Repair corrupt file.                                                      | 6.2.0 | 6.2.1 |           |
+| SP-26          | SP-040728 | S1-040993 | 22.141 | 018 | -   | Rel-6 | F   | Delete Requirements for IP session function                                           | 6.2.1 | 6.3.0 | OSA3      |
+| SP-27          | SP-050059 | S1-050219 | 22.141 | 019 | -   | Rel-6 | F   | Removal of Reference to TS 22.121                                                     | 6.3.0 | 6.4.0 | TEI       |
+|                |           |           |        |     |     | Rel-6 |     | 2005-07: File failed to open correctly in Word 2003.                                  | 6.4.0 | 6.4.1 |           |
+
+| Change history |           |           |        |      |     |       |     |                                                                  |        |        |           |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                                  | Old    | New    | Work Item |
+| SP-30          | SP-050806 | -         | 22.141 | 0021 | 1   | Rel-6 | F   | Correction to Reference in Presence TS                           | 6.4.1  | 6.5.0  | PRESNC    |
+| SP-30          | SP-050747 | S1-051225 | 22.141 | 0022 | -   | Rel-7 | F   | Introduction of generic (non-wireless specific) Presence Service | 6.4.1  | 7.0.0  | FBI       |
+| 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 |           |
+| 2014-10        | -         | -         | -      | -    | -   | -     | -   | Update to Rel-12 version (MCC)                                   | 11.0.0 | 12.0.0 |           |
+| 2015-12        | -         | -         | -      | -    | -   | -     | -   | Updated to Rel-13 by MCC                                         | 12.0.0 | 13.0.0 |           |

marked/Rel-13/22_series/22142/raw.md

@@ -0,0 +1,426 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Value Added Services (VAS) for Short Message Service (SMS) requirements *Technical Specification* (Release 13)** ---
+
+![3GPP logo with TM symbol](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. A small red signal icon is positioned below the 'G'. A 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo with TM symbol
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+SMS, Services
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                 |    |
+|-----------------------------------------------------------------|----|
+| Foreword .....                                                  | 4  |
+| 1 Scope.....                                                    | 5  |
+| 2 References.....                                               | 5  |
+| 3 Definitions, symbols and abbreviations .....                  | 5  |
+| 3.1 Definitions.....                                            | 5  |
+| 3.2 Abbreviations .....                                         | 6  |
+| 4 Requirements .....                                            | 6  |
+| 4.1 High Level Requirements.....                                | 6  |
+| 4.2 Overall Service Requirements.....                           | 6  |
+| 4.2.1 Management of Service Information.....                    | 6  |
+| 4.2.1.1 Capabilities provided to the user .....                 | 6  |
+| 4.2.1.2 Capabilities provided to the network.....               | 7  |
+| 4.2.1.3 Capabilities provided to authorized third party .....   | 7  |
+| 4.2.2 Short Message processing .....                            | 7  |
+| 4.2.3 Short Message Forwarding.....                             | 7  |
+| 4.2.4 Short Message Forwarding multiple subscriptions .....     | 7  |
+| 4.2.5 Short Message filtering.....                              | 8  |
+| 4.2.6 Short Message receipt.....                                | 8  |
+| 4.2.7 Short Message Network Storage .....                       | 8  |
+| 4.2.8 Short Message to multiple destinations.....               | 8  |
+| 4.2.9 Short Message Virtual Private Network (VPN) .....         | 9  |
+| 4.2.10 Short Message Auto Reply.....                            | 9  |
+| 4.2.11 Short Message Personal Signature .....                   | 9  |
+| 4.2.12 Short Message Deferred Delivery .....                    | 9  |
+| 4.2.13 Management and control of network based repository ..... | 9  |
+| 4.2.14 Addressing.....                                          | 10 |
+| 5 Requirements for service priority and Interaction .....       | 10 |
+| 6 Quality of Service .....                                      | 10 |
+| 7 Charging aspects for VAS-SMS .....                            | 10 |
+| 8 Security .....                                                | 11 |
+| 9 Interworking.....                                             | 11 |
+| 10 Roaming.....                                                 | 11 |
+| Annex A: 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 service requirements associated with series of value-added features for short message service (SMS). Specifically, the objective of this document is to specify potential new value-added services for SMS in 3GPP that need to be standardized.
+
+# --- 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 23.040: "Technical realization of the Short Message Service (SMS)".
+- [3] ITU-T E.164 (1997): "The International Public Telecommunications Numbering Plan".
+- [4] IETF STD 0011 (RFC 2822): "Internet Message Format", URL:  
+<http://www.ietf.org/rfc/rfc2822.txt>.
+- [5] 3GPP TS 23.204: " Support of Short Message Service (SMS) over Generic 3GPP Internet Protocol (IP) Access. Stage 2".
+- [6] 3GPP TR 22.942: "Study on Value Added Services (VAS) for Short Message Service (SMS)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in [1] and the following apply:
+
+**Short Message Forwarding:** The service permits the network to send all incoming short messages addressed to the called mobile subscriber's directory number to another directory number.
+
+**Short Message Filtering:** The service permits the network to filter certain short messages on behalf of a called/calling party based on the called/calling party's preferences.
+
+**Short Message Receipt:** The service permits the network to send one or more receipts to inform a calling party the status of sent message.
+
+**Short Message Network Storage:** The service permits the network to help the subscriber store messages that the subscriber has sent or received.
+
+**SMS VPN service:** Enables the exchange of SMS messages between VPN (Virtual Private Network) members by using a short number, usually similar to the receiver fixed extension number, instead of using the full mobile number of the recipient.
+
+**SMS Auto Reply:** The SMS Auto Reply service enables the subscriber to activate an automatic SMS reply in response to incoming SMS messages, both from in network subscribers as well as from foreign networks subscribers (incoming MT messages from foreign networks).
+
+**SMS Personal Signature:** The service allows the end user to personalize its outgoing messages either with a personal remark or a business title. The service enables a user to pre-define a text that will automatically be added to all outgoing SMS messages.
+
+**SMS Deferred Delivery:** The SMS deferred delivery service provides a subscriber the capability to control the actual delivery time of messages created by him. User using this capability can send a message and configure it to be delivered at a later time.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply in addition to [1]:
+
+|         |                                        |
+|---------|----------------------------------------|
+| SMS-SC  | Short Message Service - Service Centre |
+| SM      | Short Message                          |
+| VAS-SMS | Value-added Services for SMS           |
+
+# --- 4 Requirements
+
+## 4.1 High Level Requirements
+
+The VAS-SMS shall be implemented without influencing the existing SMS service.
+
+The VAS-SMS shall be implemented without depending on the terminal's capability.
+
+Users shall be able to register, activate, deactivate, withdraw and reconfigure VAS-SMS via the UE, or web portals.
+
+The VAS-SMS shall be designed and implemented in a way to provide users who joined the services one coherent and identical user experience, regardless of the SM flow and SM scenario (e.g. messages to and from applications, MO-MT in an in network and MT from Foreign Network).
+
+Provisioning of VAS-SMS by one operator should not depend on the support of other operators i.e. originating or terminating VAS-SMS services should be independently.
+
+## 4.2 Overall Service Requirements
+
+### 4.2.1 Management of Service Information
+
+#### 4.2.1.1 Capabilities provided to the user
+
+The VAS-SMS shall be able to support a request from an application to query/change the choice of services for a subscriber.
+
+The VAS-SMS shall be able to support a request from an application to query/change the subscriber's preferences for a certain service, for example:
+
+- i) To add or delete or modify a subscriber's filtering conditions by which VAS-SMS can refuse some of the subscriber's incoming messages.
+- ii) To modify a subscriber's signature that will be appended to an SM sent from the subscriber.
+- iii) To modify a subscriber's forwarding address that substitutes for the subscriber's original receiving address.
+
+#### 4.2.1.2 Capabilities provided to the network
+
+The VAS-SMS shall be able to support a request to query/change the subscriber's information, for example:
+
+- i) To get the detail information about the subscriber's service.
+- ii) To add or delete a subscriber's service information.
+
+The VAS-SMS shall be able to support a request to query the handling results of the subscription service.
+
+#### 4.2.1.3 Capabilities provided to authorized third party
+
+The VAS-SMS shall be able to support a request from an application to modify the contents that will be appended to an SM, for example:
+
+- i) to load or unload a particular content provided by the third party
+- ii) to associate a content with a particular subscriber or a type of subscribers
+- iii) to define the trigger for inclusion or change of such content
+
+Note: The management of VAS4SMS service is out of scope of 3GPP standardisation.
+
+### 4.2.2 Short Message processing
+
+The VAS-SMS should be able to deal with the content of an SM, for example:
+
+- i) To insert content (as agreed with the subscriber, or as agreed with a third party and authorized by the subscriber) into the original SM and form a new SM (e.g. append the signature to the SM, append the content as provided by the third party, ...).
+- ii) To compile an SM by containing operator's information (e.g. construct a delivery report).
+- iii) To use certain words in an SM as the filtering criteria.
+
+The VAS-SMS should be able to convert the format of an SM into other formats (e.g. email, WAP message, etc).
+
+### 4.2.3 Short Message Forwarding
+
+It shall be supported that users can set certain conditions (e.g., different time periods) for message forwarding. There are no significant delays to any part of the service.
+
+With the advent of SM forwarding there is also the issue of how to handle the situation when a user by mistake sets forwarding to wrong number (a number that is in use). Ideally a recipient should be capable of stopping the delivery of such SM to its own address. As a minimum the recipient's operator should be capable of identifying forwarded SM and stop delivery. Infinite forwarding loops needs to be prevented and the maximum number of times the SM is forwarded should be limited.
+
+SM Forwarding service should support forwarding to numbers of both the operator as well as other operators.
+
+It shall be possible to Notify a recipient upon activation of the service and only upon his approval activate the service for the user.
+
+There may be no relation between SM Forwarding service and Voice Call Forwarding service.
+
+### 4.2.4 Short Message Forwarding multiple subscriptions
+
+It may be supported that an operator can set a group of subscriptions for which SM are forwarded to the active/last activated subscription of that group, under the condition that the delivery address of the SM is associated to a subscription of that group and that address is not registered on the network.
+
+### 4.2.5 Short Message filtering
+
+It shall be supported that users can set certain conditions for message filtering.
+
+### 4.2.6 Short Message receipt
+
+It shall be supported that the callee can configure the content of an additional receipt SM for different callers, so the standard Status Report may be accompanied by a newly generated SM with the content provided by the operator.
+
+### 4.2.7 Short Message Network Storage
+
+It should be possible for the operator to support Short Message Network Storage to allow users to store the messages in the network.
+
+It should be possible for users to store the messages in the network based on their personal settings (e.g. store all sent & received messages, store the messages from/to particular users, store the messages sent & received in a specified period of time etc).
+
+It should be possible for users to store and manage the messages for their preference (e.g. users can set different folders to store different sort of messages, therefore it is convenient to inquire the stored messages based on message sort or key words).
+
+It should be possible for the operator to ensure all relevant information of the messages stored in the network are consistent with that displayed to users, e.g. content of the messages, sender/recipient, sending/receiving time, etc.
+
+It shall be supported that user can pre-set certain conditions for storage. The storage condition includes all sent messages, all received messages, messages sent to or received from one or more special phone numbers and so on.
+
+It should be possible for the operator to prevent storage of configuration SM, notifications (e.g. voice mail, SM delivery notifications).
+
+It shall be supported that users can transfer the messages stored in the message depository to any other mobile phone.
+
+It shall be supported that users can inquire the messages stored in the message depository according to certain query conditions (e.g., short message receiver, short message sender, key words etc.).
+
+It shall be supported that users can manage the stored messages via a website, and it shall be possible for the user to set access right for other users ( e.g. read only , read and download etc), in this way, other users are able to inquire his stored messages through a link to the website after valid authentication.
+
+In case of multiple delivery attempts SM will be copied only once regardless of the number of delivery attempts.
+
+It shall be possible to combine concatenated SM to single Message in the Network store or alternatively indicate in the message that it is part of concatenated SM.
+
+The Short Message Network Storage service shall prevent duplicate storage message as a result of failure in transmission of the original SM.
+
+Messages should be stored in the Network Storage regardless of the user availability and as soon as the original SM is being processed in the SMSC.
+
+### 4.2.8 Short Message to multiple destinations
+
+It shall be able to support inclusion of multiple recipients in a message when a user sends a single message to multiple individuals.
+
+It should be possible for all recipients of the message to be aware of other recipients.
+
+It should be possible for a recipient to choose to whom the reply message is sent, i.e. to the original sender and to other recipients of the original message.
+
+It shall be supported that a user can include multiple destination addresses in a message. The recipient except those addresses displaying information is blocked shall receive information on all recipients of the message.
+
+It shall be supported that each recipient of the message can send a message back to all recipients of the original message.
+
+### 4.2.9 Short Message Virtual Private Network (VPN)
+
+Sending messages to local numbers based on the dialling plan should be supported. There shall be no significant delays to any part of the service.
+
+### 4.2.10 Short Message Auto Reply
+
+It shall be possible that users can activate the SM Auto Reply Service to be active for different time periods. In addition it shall be possible to configure the system to reply only once to each sender in a predefined period of time.
+
+It shall be possible for users to configure and manage their Automatic Reply messages, e.g. edit and delete the content of the message.
+
+It shall be possible for users to set different Automatic Reply messages to different senders.
+
+Auto reply to auto reply loops need to be prevented.
+
+### 4.2.11 Short Message Personal Signature
+
+The SM Personal Signature Service shall support certain conditions configured by users or control system wide (e.g., append personal signature depending on the original short message length, append personal signature to certain destinations). There shall be no significant delays to any part of the service.
+
+### 4.2.12 Short Message Deferred Delivery
+
+The SM Deferred delivery shall support the following delivery time options:
+
+- Relative timing – The text will include information as for the of how many more days, hours, minutes shall pass before the message shall be delivered.
+- Absolute timing - The text will include information indicating of the specific Date and Time for the message to be delivered
+
+The SM Deferred Delivery Service shall support all type of languages
+
+The SM Deferred Delivery Service shall support concatenated messages
+
+There shall be no significant delays to any part of the service.
+
+### 4.2.13 Management and control of network based repository
+
+VAS-SMS should be able to provide following capabilities to support network based repository:
+
+- The VAS-SMS should allow configuring in such a way that certain sent or received messages of a particular user can be stored persistently in a network based repository.
+- The VAS-SMS should be able to support a request from SMS-SC to persistently store a sent message in a network based repository at the time of sending.
+- The VAS-SMS should be able to support a request from an application to upload certain messages into a network based repository for persistent storage.
+- The VAS-SMS should be able to support a request from an application to retrieve/delete certain messages stored in a network based repository
+- The VAS-SMS should be able to support a request from an application to view the list of messages and related attributes (e.g. sender, recipient, date/time, etc) in a network based repository
+
+### 4.2.14 Addressing
+
+The VAS-SMS should support different addressing formats to identify the sender and recipient; it should support both MSISDN[3] and e-mail addressing schemes[4].
+
+A short number should be supported. This number should be unique within VPN where it is used.
+
+The VAS-SMS should support an alpha-numeric addressing format (similar to specified in [2]).
+
+The VAS-SMS should be able to submit one message to multiple recipients.
+
+The VAS-SMS should be able to support the request to hide the sender's or other recipients' addresses.
+
+# --- 5 Requirements for service priority and Interaction
+
+The different rules of VAS-SMS priority and interaction are provided by operator. For example, the priority order maybe as following:
+
+- SM Filtering
+
+- SM Network Storage
+- SM Forwarding
+- etc.
+
+The VAS-SMS should be classified by priority and triggered according to priority order.
+
+The VAS-SMS should provide the capability to configure certain priority.
+
+Caller SMS receipt has higher priority than Callee SMS Receipt service.
+
+# --- 6 Quality of Service
+
+The quality of basic SMS service should not be affected by introducing the VAS-SMS.
+
+The following key performance for quality of VAS-SMS shall be kept consistent with basic SMS. For example:
+
+- SMS delivery successful rate
+- authentication successful rate
+- end to end data loss rate
+- end to end data delay
+- charging successful rate
+- reliability of network and service
+
+# --- 7 Charging aspects for VAS-SMS
+
+The VAS-SMS shall provide accounting rules for accurate accounting. It shall be able to support following charging aspects.
+
+- Charging Model
+
+The VAS-SMS charging includes basic communication fee and special service fee.
+
+Basic communication fee is paid for usage of network resource. CDR is generated by SMSC. Special service fee is paid for usage of the VAS-SMS. CDR is generated by the VAS-SMS system. Charging models of special service fee shall include but not limit to the following items:
+
+- i) charging per VAS-SMS
+- ii) monthly basis
+
+Per each service category, different charging models and rates should be configurable for the special service fee.
+
+- Charging principle
+
+The following principles shall be supported according to different service categories:
+
+- i) VAS-SMS triggered by sending party – basic communication fee and special service fee are paid by the sending party.
+- ii) VAS-SMS services triggered by recipient – basic communication fee is paid by the sending party, whilst special service fee is paid by the recipient.
+- iii) Charging only happens after the status report has been received by the SMSC.
+
+- Charging Scheme
+
+The VAS-SMS shall support a standardized interface to transfer CDRs and other charging related information between the VAS-SMS and the billing system for prepaid and post-paid billing solutions.
+
+# --- 8 Security
+
+Security of the VAS-SMS services shall be consistent with basic SMS service. The user shall be able to use and access the VAS-SMS services in a secure manner.
+
+VAS-SMS should support Lawful Interception as required by Regional Regulations.
+
+# --- 9 Interworking
+
+Interworking with existing messaging technologies and messaging services should be supported.
+
+The VAS-SMS should be able to send the content of an SM to a reachable address, for example:
+
+- i) To send an email to email servers after converting the SM into an email.
+- ii) To send a WAP message to a WAP Push Gateway after converting the SM into a WAP message.
+- iii) To send an SM to a subscriber by sending an SM to SMSC.
+- iv) To send an SM via IMS. Refer to [5].
+- v) To send a delivery report .
+
+# --- 10 Roaming
+
+General roaming requirements should be compliant with roaming function of SMS.
+
+The user should be able to experience the consistent VAS-SMS services whether in home network or roaming.
+
+# Annex A: Change history
+
+| Change history |           |           |        |      |     |       |     |                                                          |        |        |         |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|----------------------------------------------------------|--------|--------|---------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR   | Rev | Rel   | Cat | Subject/Comment                                          | Old    | New    | WI      |
+| SP-44          | SP-090376 | S1-091375 | 22.142 | 0001 | 1   | Rel-9 | C   | Limiting the maximum number of times the SM is forwarded | 9.0.0  | 9.1.0  | VAS4SMS |
+| SP-44          | SP-090376 | S1-091376 | 22.142 | 0002 | 1   | Rel-9 | C   | To prevent auto reply to auto reply loop                 | 9.0.0  | 9.1.0  | VAS4SMS |
+| SP-44          | SP-090376 | S1-091362 | 22.142 | 0003 | 1   | Rel-9 | B   | Independent provisioning of VAS-SMS                      | 9.0.0  | 9.1.0  | VAS4SMS |
+| 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 |         |
+| 2014-10        |           |           |        |      |     |       |     | Updated to Rel-12 by MCC                                 | 11.0.0 | 12.0.0 |         |
+| 2015-12        |           |           |        |      |     |       |     | Updated to Rel-13 by MCC                                 | 12.0.0 | 13.0.0 |         |

marked/Rel-13/22_series/22146/raw.md

@@ -0,0 +1,547 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Broadcast/Multicast Service (MBMS); Stage 1 (Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase sans-serif font. Above the "e" is the text "Advanced Pro" in a smaller, red, sans-serif font. To the right of the "e" is a small "TM" symbol. Above the "lte" text are three green curved lines representing signal waves.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a bold, black, stylized sans-serif font. The "3" is slightly larger and positioned to the left of the "G". The "P" and "P" are connected at the top by a single horizontal line. Below the "G" is a small red signal wave icon. To the right of the "P" is a small "TM" symbol.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+UMTS, service, multicast, broadcast
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                               |           |
+|-------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                | 4         |
+| Introduction .....                                                            | 4         |
+| 1 Scope.....                                                                  | 5         |
+| 2 References.....                                                             | 5         |
+| 3 Definitions, symbols and abbreviations.....                                 | 5         |
+| 3.1 Definitions.....                                                          | 5         |
+| 3.2 Abbreviations .....                                                       | 6         |
+| 4 General description of a multimedia broadcast/multicast service (MBMS)..... | 7         |
+| 4.1 MBMS broadcast mode.....                                                  | 7         |
+| 4.2 MBMS multicast mode .....                                                 | 8         |
+| 4.2.1 Multicast subscription and reception.....                               | 9         |
+| 4.3 Discovery and announcement of MBMS services .....                         | 10        |
+| 5 High level requirements.....                                                | 10        |
+| 5.1 Broadcast mode.....                                                       | 10        |
+| 5.1.1 Home environment requirements .....                                     | 10        |
+| 5.1.2 User requirements for MBMS .....                                        | 11        |
+| 5.2 Multicast mode.....                                                       | 12        |
+| 5.2.1 Home environment requirements .....                                     | 12        |
+| 5.2.2 User requirements for MBMS .....                                        | 13        |
+| 5.3 Availability.....                                                         | 14        |
+| 6 Security .....                                                              | 14        |
+| 7 Charging.....                                                               | 14        |
+| 7.1 Broadcast mode.....                                                       | 14        |
+| 7.2 Multicast mode.....                                                       | 14        |
+| <b>Annex A (informative): MBMS Bit Rates.....</b>                             | <b>16</b> |
+| Annex B (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
+
+Broadcast and Multicast are methods for transmitting data-grams from a single source to several destinations (point-to-multipoint). To date, release-4 and release-99 define two services in this respect:
+
+A cell broadcast service (CBS) allowing for low bit-rate data to be transmitted to all subscribers in a set of given cells over a shared broadcast channel. This service offers a message-based service [5,6]
+
+An IP-Multicast service allowing for mobile subscribers to receive multicast traffic. This service does not allow for multiple subscribers to share radio or core network resources and as such does not offer any advantages as far as resource utilization within the PLMN and over the radio access network. [3,4]
+
+It is envisaged that for some applications, multiple users can receive the same data at the same time. The benefit of multicast and broadcast in the network is that the data is sent once on each link. For example, an SGSN will send data once to an RNC regardless of the number of Node Bs and UEs that wish to receive it. The benefit of multicast and broadcast on the air interface is that many users can receive the same data on a common channel, thus not clogging up the air interface with multiple transmissions of the same data.
+
+With increasing use of high bandwidth applications in third generation mobile systems, especially with a large number of users receiving the same high data rate services, efficient information distribution is essential. Thus, broadcast and multicast are techniques to decrease the amount of data within the network and use resources more efficiently
+
+# --- 1 Scope
+
+This Technical specification defines the stage one description of the Broadcast and Multicast Services for the 3GPP System. Stage one is the set of requirements which shall be supported for the provision of Broadcast and Multicast services, seen primarily from the subscriber's and service providers' points of view.
+
+Note: Non-3GPP access systems may provide MBMS transport service, but this is not in the scope of this specification.
+
+This TS includes information applicable to network operators, content providers, and terminal and network manufacturers.
+
+This TS contains the core requirements for Multicast and Broadcast Services, which are sufficient to provide a complete 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] RFC 1112: "Host extensions for IP multicasting", RFC 1920: " Internet official protocol standards", RFC 1458: "Requirements for multicast protocols", RFC 1301: "Multicast transport protocol"
+- [3] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1".
+- [4] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [5] 3GPP TS 25.324: "Broadcast/Multicast Control BMC"
+- [6] 3GPP TS 23.041: "Technical Realization of Cell Broadcast Service (CBS)"
+- [7] 3GPP TS 22.246: "MBMS User Services".
+
+# --- 3 Definitions, symbols 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:** The area in which a specific broadcast service is available. It is defined individually per broadcast service. The broadcast service area may represent the coverage area of the entire PLMN, or part(s) of the PLMN's coverage area. The broadcast service area is the sum of all local broadcast areas offering the same service.
+
+**Local Broadcast Area:** The area of a broadcast service, where the service content is the same. One broadcast service may have different content in different local broadcast areas.
+
+**Broadcast mode:** The part of MBMS that supports broadcast services.
+
+**Broadcast service:** A unidirectional point-to-multipoint service in which data is efficiently transmitted from a single source to multiple UEs in the associated broadcast service area. Broadcast services may be received by all users who have enabled the specific broadcast service locally on their UE and who are in the broadcast area defined for the service.
+
+**Broadcast session:** A continuous and time-bounded reception of a broadcast service by the UE. A single broadcast service can only have one broadcast session at any time. A broadcast service may consist of multiple successive broadcast sessions.
+
+**Mobile Station (MS):** Defined in 3GPP TS 24.002. (The abbreviation "UE" in this specification refers both to MS and User Equipment.)
+
+**Multicast transmission activation:** The process by which the network activates the transmission of Multicast data.
+
+**Multicast service area:** The area in which a specific multicast service is available. It is defined individually per multicast service. The multicast service area may represent the coverage area of an entire PLMN, or part(s) of the PLMN's coverage area. The multicast service area is the sum of all local multicast areas offering the same service.
+
+**Local multicast area:** The area of a multicast service, where the service content is the same. One multicast service may have different content in different local multicast areas.
+
+**Multicast mode:** The part of MBMS that supports multicast services.
+
+**Multicast joining:** The process by which a user joins a multicast group.
+
+**Multicast session:** A continuous and time-bounded reception of a multicast service by the UE. A single multicast service can only have one multicast session at any time. A multicast service may consist of multiple successive multicast sessions.
+
+**Multimedia Broadcast/Multicast Service (MBMS):** A unidirectional point-to-multipoint service in which data is transmitted from a single source entity to a group of users in a specific area. The MBMS has two modes: Broadcast mode and Multicast mode.
+
+**Multicast group:** A group of users that have an activated MBMS in multicast mode and therefore are ready to or are receiving data transmitted by this service. The multicast group is a subset of the **Multicast subscription group**. Multicast subscription group members may join the corresponding multicast group.
+
+**Multicast service:** A unidirectional point-to-multipoint service in which data is efficiently transmitted from a single source to a multicast group in the associated multicast service area. Multicast services can only be received by such users that are subscribed to the specific multicast service and have joined the multicast group associated with the specific service.
+
+**Multicast subscription:** The process by which a user subscribes or is subscribed to a multicast subscription group and thereby is authorised to join certain multicast services. Multicast subscription is performed either upon user selection or due to home environment initiation.
+
+**Multicast Subscription Group:** A group of users who are subscribed to a certain MBMS in multicast mode and therefore authorised to join and receive multicast services associated with this group.
+
+**User Equipment:** defined in TS 21.905. An occurrence of a User Equipment is an MS for GSM as defined in TS 24.002.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                        |
+|------|----------------------------------------|
+| MBMS | Multimedia Broadcast/Multicast Service |
+| MS   | Mobile Station                         |
+| UE   | User Equipment                         |
+
+# 4 General description of a multimedia broadcast/multicast service (MBMS)
+
+Point to multipoint services exist today which allow data from a single source entity to be transmitted to multiple endpoints. These services are expected to be used extensively over wireless networks, hence there is a need for a capability in the PLMN to efficiently support them. The Multimedia Broadcast/Multicast Service (MBMS) will provide this capability for such broadcast/multicast services provided by the home environment and other VASPs.
+
+The MBMS is a unidirectional point to multipoint bearer service in which data is transmitted from a single source entity to multiple recipients. It is anticipated that other services will use these bearer capabilities.
+
+MBMS also enables an IMS application located on an application server to send multimedia to a set of IMS users in the service area by means of MBMS bearer service.
+
+3GPP has defined two modes of operation:
+
+- the broadcast mode
+- the multicast mode.
+
+## 4.1 MBMS broadcast mode
+
+The broadcast mode is a unidirectional point-to-multipoint transmission of multimedia data (e.g. text, audio, picture, video) from a single source entity to all users in a broadcast service area. The broadcast mode is intended to efficiently use radio/network resources e.g. data is transmitted over a common radio channel. Data is transmitted in the broadcast service area as defined by the network (Home environment).
+
+MBMS data transmission should adapt to different RAN capabilities or different radio resource availability, e.g. by reducing the bitrate of the MBMS data. The selection and description of an appropriate mechanism is subject to MBMS stage 2.
+
+Figure 1 gives an example of how a network can be configured to broadcast a variety of high bit rate services to users within the associated broadcast service area.
+
+A broadcast service received by the UE, involves one or more successive broadcast sessions. A broadcast service might, for example, consist of a single on-going session (e.g. a media stream) or may involve several intermittent sessions over an extended period of time (e.g. messages).
+
+![Diagram of MBMS Broadcast Mode Network architecture showing data flow from various service providers through a core network to users in a broadcast service area.](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg)
+
+The diagram illustrates the network architecture for MBMS broadcast mode. On the right, three service clouds—'Multimedia Services' (yellow), 'Operator Specific Services' (orange), and 'Internet Hosted Services' (grey)—are connected to a central 'UMTS Packet Switching Core'. Below these is an 'IP Multimedia Subsystem' (green). The core network performs several functions: 'QoS handling', 'VASP Authentication', 'Broadcast Area Configuration', and 'Provisioning control'. A large red arrow labeled 'Broadcast Data' points from the core to a 'Multimedia Broadcast Capable UTRAN/GERAN' (light blue cloud). This network element then broadcasts the data to a 'Broadcast Service Area' (indicated by a starburst shape) containing several mobile phones (UEs).
+
+Diagram of MBMS Broadcast Mode Network architecture showing data flow from various service providers through a core network to users in a broadcast service area.
+
+**Figure 1: Example of Multicast Broadcast Mode Network**
+
+The broadcast mode should not be confused with the existing Cell Broadcast service (CBS) which is currently used for low bit rate services (messaging) whilst the broadcast mode enables the broadcast of multimedia services (Audio, Video etc).
+
+An example of a service using the broadcast mode could be advertising or a welcome message to the network. As not all users attached to the network may wish to receive these messages then the user shall be able to enable/disable the reception of these broadcast service on his UE.
+
+The broadcast mode differs from the multicast mode in that there is no specific requirement to activate or subscribe to the MBMS in broadcast mode.
+
+The broadcast mode should allow terminals to minimise their power consumption.
+
+It is expected that charging data for the end user will not be generated for this mode at MBMS Transport Service layer. Charging data related to security procedures for the end user at MBMS User Service layer may be generated, cf. clause 7. The reception of the traffic in the broadcast mode is not guaranteed. The receiver may be able to recognize data loss.
+
+## 4.2 MBMS multicast mode
+
+The multicast mode allows the unidirectional point-to-multipoint transmission of multimedia data (e.g. text, audio, picture, video) from a single source point to a multicast group in a multicast service area. The multicast mode is intended to efficiently use radio/network resources e.g. data is transmitted over a common radio channel. Data is transmitted in the multicast service area as defined by the network (Home environment). In the multicast mode there is the possibility for the network to selectively transmit to cells within the multicast service area which contain members of a multicast group.
+
+MBMS data transmission should adapt to different RAN capabilities or different radio resource availability, e.g. by reducing the bitrate of the MBMS data. The selection and description of an appropriate mechanism is subject to MBMS stage 2.
+
+A multicast service received by the UE, involves one or more successive multicast sessions. A multicast service might, for example, consist of a single on-going session (e.g. a multimedia stream) or may involve several intermittent multicast sessions over an extended period of time (e.g. messages).
+
+An example of a service using the multicast mode could be a football results service for which a subscription is required.
+
+Unlike the broadcast mode, the multicast mode generally requires a subscription to the multicast subscription group and then the user joining the corresponding multicast group. The subscription and group joining may be made by the PLMN operator, the user or a third party on their behalf (e.g. company). Unlike the broadcast mode, it is expected that charging data for the end user will be generated for this mode at MBMS Transport Service layer. Charging data related to security procedures for the end user at MBMS User Service layer may be generated, cf. clause 7.
+
+![Figure 2: Example of Multicast Mode Network. The diagram illustrates the network architecture for MBMS multicast mode. On the left, a 'Multicast Subscription Group' is shown with several mobile phones. Arrows point from this group to a 'Multicast Capable UTRAN GERAN' cloud. Inside this cloud, three horizontal arrows represent 'Service synchronisation', 'User-initiated activation', and 'Multicast Data Stream'. These arrows point to a central box labeled '3GPP Packet Core / IP Multimedia'. This box contains a list of functions: 'QoS handling', 'Service Provisioning', 'Subscription Handling', 'Efficient routing', 'Activation', and 'Multicast area Control'. From this central box, arrows point to three clouds on the right: 'Multimedia Services' (yellow), 'Operator Specific Services' (orange), and 'IP Network' (purple). The 'IP Network' cloud is connected to an 'IP Multimedia subsystem' (green) and also to various services: 'Movie/Music Streaming', 'Live web casting', and 'TV news/sports/Advertising'.](740442c999390734911677f01af0316d_img.jpg)
+
+Figure 2: Example of Multicast Mode Network. The diagram illustrates the network architecture for MBMS multicast mode. On the left, a 'Multicast Subscription Group' is shown with several mobile phones. Arrows point from this group to a 'Multicast Capable UTRAN GERAN' cloud. Inside this cloud, three horizontal arrows represent 'Service synchronisation', 'User-initiated activation', and 'Multicast Data Stream'. These arrows point to a central box labeled '3GPP Packet Core / IP Multimedia'. This box contains a list of functions: 'QoS handling', 'Service Provisioning', 'Subscription Handling', 'Efficient routing', 'Activation', and 'Multicast area Control'. From this central box, arrows point to three clouds on the right: 'Multimedia Services' (yellow), 'Operator Specific Services' (orange), and 'IP Network' (purple). The 'IP Network' cloud is connected to an 'IP Multimedia subsystem' (green) and also to various services: 'Movie/Music Streaming', 'Live web casting', and 'TV news/sports/Advertising'.
+
+Figure 2: Example of Multicast Mode Network
+
+Reception of multicast services cannot be guaranteed over the access network. For many applications and services guaranteed data reception may be carried out by higher layer services or applications which make use of MBMS.
+
+Multicast mode should allow terminals to minimise their power consumption.
+
+The multicast mode defined in this specification should not be confused with IP Multicast (RFC s 1112, 1301, 1458, 1920 [2]). There are similarities between these two services and such similarities may be exploited in 3GPP networks given that 3GPP multicast mode has been defined with consideration to maximizing efficiency on the radio interface and of network resources.
+
+Multicast mode shall be inter-operable with IETF IP Multicast. This could allow the best use of IP service platforms to help maximize the availability of applications and content so that current and future services can be delivered in a more resource efficient manner. Figure 2 above shows a general high level overview of multicast mode network.
+
+### 4.2.1 Multicast subscription and reception
+
+The following is the expected sequence for the user to be able to access the MBMS multicast mode:
+
+- 1 The user subscribes or is subscribed to a multicast subscription group which is uniquely identified and thereby becomes a member of that group. The subscription may be continuous (e.g. as defined by the subscriber's contract), time-limited, or generated by the subscriber on a one-time basis. The subscription to multicast services shall not be further standardized.
+  - 2 The user discovers, or becomes aware (e.g. via service announcements), that there are multicast services currently active, or multicast services that will become active at some time later, at the user's current location.
+  - 3a) The user selects a multicast service and hence the user joins the corresponding multicast group. The user should be able to join a multicast service as soon as possible after announcement of the service.
+  - 3b) As an alternative, the Home Environment can join the user to the selected multicast group on behalf of the user, that has previously subscribed to this multicast group.
+- Signalling exchange between the UE and the network might not be necessary in some cases, e.g. in the case of network congestion.
+- 4 If the transmission is not already in progress the network starts transmitting the corresponding multicast content. Alternatively, the transmission may start at a later time.
+  - 5 The network may optionally select to set up unicast (point to point) connections to some users e.g. if there are insufficient users to justify multicasting
+  - 6 The UE starts receiving the multicast data associated with the multicast group(s) it has joined
+  - 7 The user may choose to stop receiving a selected multicast service and thereby leaves the multicast group. The user may also select to continue (or not) to receive service announcements for this multicast subscription group.
+  - 8 The user may unsubscribe or be unsubscribed from the multicast subscription group and stop receiving both the multicast data and future service announcements for this multicast subscription group.
+
+The home environment shall be able to remove a user from a multicast group (deactivation) and if required remove the subscriber from the multicast subscription group (un-subscription). This is required to allow the operator to bar service.
+
+## 4.3 Discovery and announcement of MBMS services
+
+The user shall be able to find out or be informed about MBMS services available in the network. The network shall support service announcements both for the broadcast and multicast mode of MBMS in order to enable the user to be informed about the MBMS services available currently, or some time later.. Users should also be able to discover and monitor MBMS service availability e.g. using a URL.
+
+# --- 5 High level requirements
+
+## 5.1 Broadcast mode
+
+### 5.1.1 Home environment requirements
+
+- Broadcast services
+
+The PLMN operator shall be able to provision one or more broadcast services within his PLMN.
+
+The operators sharing a network shall be able to provide one or more broadcast services for their own subscribers and inbound roamers from roaming partners only. This shall be applicable for sharing of radio network and for sharing of radio network and the core network entities connected to the radio network.
+
+A broadcast area is configured individually for each broadcast service. Broadcast areas associated with different broadcast services are independent of each other and may overlap.
+
+A broadcast service shall be able to distribute different content data to different locations, i.e. local broadcast areas, within the broadcast service area as shown in figure 3. This allows the user to receive broadcast data depending on his location (e.g. a “nationwide traffic service” with localized traffic reports). Only one location specific version of content data is distributed to each of the individual local broadcast areas, i.e. in any location a user will never receive different content data from a single broadcast service.
+
+It shall be possible to define a broadcast service for only the subscribers and inbound roamers of one of the operators sharing network. The broadcast services transmitted in a broadcast service area of operator A shall only be available to the subscribers and inbound roamers of operator A. The broadcast areas of different sharing operators may cover the same geographical area. This shall be applicable for sharing of radio network and for sharing of radio network and the core network entities connected to the radio network.
+
+![Diagram of Broadcast Service with different content data for different locations. A yellow box at the top is labeled 'Broadcast Service Data Source'. Below it, a horizontal line is labeled 'QoS or Media component'. This line branches into three vertical paths, each labeled with numbers 1, 2, and 3. Each path leads to a rounded rectangle containing text: 'Content data 1 in Local broadcast area A', 'Content data 2 in Local broadcast area B', and 'Content data 3 in Local broadcast area C'. These three rectangles are grouped by a dashed line labeled 'Broadcast Service Area' at the bottom.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+Diagram of Broadcast Service with different content data for different locations. A yellow box at the top is labeled 'Broadcast Service Data Source'. Below it, a horizontal line is labeled 'QoS or Media component'. This line branches into three vertical paths, each labeled with numbers 1, 2, and 3. Each path leads to a rounded rectangle containing text: 'Content data 1 in Local broadcast area A', 'Content data 2 in Local broadcast area B', and 'Content data 3 in Local broadcast area C'. These three rectangles are grouped by a dashed line labeled 'Broadcast Service Area' at the bottom.
+
+**Figure 3 Broadcast Service with different content data for different locations**
+
+- Quality of service
+
+The PLMN operator shall be able to configure the quality of service for each individual broadcast service. It should be possible to adapt the MBMS data transmission to different RAN capabilities or different radio resource availability.
+
+The home environment shall be able to set priority to select which simultaneous broadcast services are supported when there is a limit on the resources available.-
+
+- Network and radio efficiency
+
+The PLMN operator shall be able to use network and radio resources in an efficient manner.
+
+NOTE: Allocation of resources based on actual need in the broadcast service area is not applicable for the broadcast mode.
+
+The operator shall be able to schedule a certain broadcast service at pre-determined times.
+
+- Types of data services
+
+MBMS in The broadcast mode shall be transparent for the transferred data packets independent of the type of service being transmitted, will support a number of services, and permit support of and therefore transfer all data types e.g. Audio, Data, Video or combinations thereof. A minimum number of data types may need to be identified to enable interoperability.
+
+- Sources of data services
+
+In addition to supporting their own broadcast services the PLMN shall as well support broadcast services from third parties (i.e. HE-VASPs or VASPs or IMS server)
+
+- Broadcast service announcements
+
+The PLMN operator shall be able to provide service announcements for a broadcast service within and outside of the broadcast area defined for the service.
+
+### 5.1.2 User requirements for MBMS
+
+- User mobility
+
+The user shall be able to continue receiving broadcast services throughout the broadcast service area. For example, in case of handover and presuming that a certain broadcast service is offered in the target cell, it should be possible for the user to continue receiving the service in the target cell.
+
+- User selectivity
+
+The user shall be able to discover what broadcast services are available at the user's current location and outside of the current location.
+
+The user shall be able to enable/disable the reception of specific broadcast services and can receive simultaneously more than one MBMS service.
+
+The user may be able to define service preference for reception. A priority procedure may be implemented to allow the user to select between simultaneous broadcast services e.g. while receiving commercial broadcast service a new broadcast service may interrupt this.
+
+While receiving one or more broadcast services, it shall be possible for the user to be informed about incoming voice calls or the availability of other MBMS services.
+
+Dependent on terminal capabilities, it shall be possible for the user to participate in other services, while simultaneously participating in MBMS services. For example the user can originate or receive a call or send and receive messages whilst receiving advertisements.
+
+## 5.2 Multicast mode
+
+### 5.2.1 Home environment requirements
+
+- Multicast services
+
+The PLMN operator shall be able to provision one or more multicast services. A multicast area is configured individually for each multicast service. Multicast areas associated with different multicast services are independent of each other and may overlap.
+
+Multicast service areas may cover part(s) of one or more PLMNs.
+
+A multicast service shall be able to distribute different content data to different locations, i.e. local multicast areas, within the multicast service area as shown in figure 4. This allows the user to receive multicast data depending on his location (e.g. a “nationwide traffic service” with localized traffic reports) Only one version of location specific content data is distributed to each of the individual local multicast areas, i.e. in any location a user will never receive different content data from a single multicast service.
+
+![Diagram of Multicast Service with different content data for different locations. A yellow box at the top is labeled 'Multicast Service Data Source'. Below it, three vertical lines represent 'QoS or Media component' levels 1, 2, and 3. These lines connect to three separate boxes inside a dashed 'Multicast Service Area' boundary. The boxes are labeled 'Content data 1 in Local multicast area A', 'Content data 2 in Local multicast area B', and 'Content data 3 in Local multicast area C'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Diagram of Multicast Service with different content data for different locations. A yellow box at the top is labeled 'Multicast Service Data Source'. Below it, three vertical lines represent 'QoS or Media component' levels 1, 2, and 3. These lines connect to three separate boxes inside a dashed 'Multicast Service Area' boundary. The boxes are labeled 'Content data 1 in Local multicast area A', 'Content data 2 in Local multicast area B', and 'Content data 3 in Local multicast area C'.
+
+**Figure 4 Multicast Service with different content data for different locations**
+
+- Multicast subscription groups and multicast groups
+
+The PLMN operator shall be able to provision one or more multicast subscription groups. The home environment shall be able to make a user a member of a multicast subscription group (subscription).
+
+On receipt of a request to join a multicast group, the PLMN shall check that the user is a member of the applicable multicast subscription group. The home environment shall be able to join users to the multicast group e.g. at the request of the subscriber.
+
+- Quality of service
+
+The PLMN operator shall be able to configure the quality of service for individual multicast services. It should be possible to adapt the MBMS data transmission to different RAN capabilities or different radio resource availability.
+
+As part of the same service, it should be possible for the operator to provide the UEs with multiple successive sessions with different quality-of-service for each session.
+
+The home environment shall be able to set priority to select which simultaneous multicast services are supported when there is a limit on the resources available.
+
+- Network and radio efficiency
+
+The PLMN operator shall be able to use network and radio resources in an efficient manner.
+
+Within the multicast service area, the network may distribute the data across the whole multicast service area or parts of the area. The decision to distribute to only parts of the multicast service area may be based on: a) multicast group members are present in a given part of the multicast area b) resources are not available in parts of the multicast service area.
+
+The operator shall be able to schedule a certain multicast service at pre-determined times.
+
+- Types of services
+
+The multicast mode shall be independent of the type of service being transmitted, will support a number of services, and permit support of all data types e.g. Audio, Data, Video or combinations thereof. A minimum number of data types may need to be identified to enable interoperability
+
+- Sources of services
+
+In addition to supporting their own multicast services the PLMN shall as well support multicast services by third parties (i.e. HE-VASPs or VASPs or IMS server).
+
+- Multicast service announcements
+
+The PLMN operator shall be able to provide service announcements for a multicast service within and outside of the multicast area defined for the service.
+
+### 5.2.2 User requirements for MBMS
+
+- User mobility
+
+The user shall be able to continue receiving multicast services throughout the multicast service area in which the service is provided. For example, in case of handover and presuming that a certain multicast service is offered in the target cell, it should be possible for the user to continue the session in the target cell. It is possible that data loss will occur due to user mobility.
+
+#### - User selectivity
+
+The user shall be able to discover what multicast services are available at the user's current location and outside of the current location. The user shall be able to select between different multicast services provided to the user and can receive simultaneously more than one MBMS service.
+
+The user may be able to define service preference for reception. A priority procedure may be implemented to allow the user to select between simultaneous broadcast/multicast services e.g. while receiving commercial broadcast service a new multicast service may interrupt this.
+
+While receiving PS or CS services, it shall be possible for the user to receive notification of MBMS multicast sessions.
+
+Note: This may depend on the capability of the UE in some access system.
+
+While receiving one or more multicast services it shall be possible for the user to be informed about incoming voice calls or the availability of other MBMS services.
+
+Dependent on terminal capabilities, it shall be possible for the user to participate in other services, while simultaneously participating in MBMS services. For example the user can originate or receive a call or send and receive messages whilst receiving MBMS video content.
+
+#### - Multicast subscription groups and multicast groups
+
+The subscriber shall be able to subscribe to or unsubscribe from a multicast subscription group. (The subscription mechanism is outside the scope of this TS.)
+
+The user shall be able to join a multicast group only if he is a member of the applicable multicast subscription group. The user shall be able to leave a multicast group if he is a member of that group.
+
+## 5.3 Availability
+
+If provided by the network MBMS in broadcast mode shall be available to all users in the broadcast service areas that are registered/attached to a PLMN.
+
+If provided by the network, MBMS in multicast mode shall be available to all users that are registered/attached to a PLMN.
+
+MBMS services (multicast or broadcast mode) shall be available via GERAN, UTRAN, E-UTRAN.
+
+It is possible to prevent access to the content of the MBMS multicast / broadcast data by UEs that do not register to the PLMNs that deliver the MBMS service (including case when these PLMNs and the RPLMN of the UE are part of the same network sharing infrastructure). Access prevention could be done by application layer means (e.g. application layer ciphering).
+
+Within the broadcast or multicast service area, it shall be possible to inform users of up-coming MBMS sessions which they may receive. This may be useful e.g. to initiate UE processes for the reception of MBMS data.
+
+In case of roaming a user should also be able to subscribe and join Multicast Services that are provided in the home network and visited network, as allowed by the user's home environment.
+
+# --- 6 Security
+
+It shall be possible to ensure that only those users who are entitled to receive a specific MBMS service may do so. It should be possible to choose whether a given MBMS service is to be delivered with or without ensured group security.
+
+If a terminal supports MBMS, then it shall support UICC based key management and all the function and interfaces required for it. In addition, ME key management shall be supported. If the UICC is capable of MBMS key management, ME key management shall not be activated.
+
+# --- 7 Charging
+
+## 7.1 Broadcast mode
+
+It shall be possible to collect charging information for the transmission of broadcast services to enable billing of broadcast services providers e.g. billing 3<sup>rd</sup> parties for advertising.
+
+Examples of the type of the charging information that could be collected include:
+
+- usage duration
+- volume of contents
+
+The above list of possible charging mechanisms is neither complete nor exhaustive.
+
+It shall be possible to collect subscriber charging information for the end user (including roaming situations) based on security procedures (e.g. key management) for the receipt of broadcast data on a per broadcast service basis.
+
+## 7.2 Multicast mode
+
+It shall be possible to collect charging information for the transmission of multicast services to enable billing of multicast services providers e.g. billing 3<sup>rd</sup> parties for advertising.
+
+It shall be possible to collect subscriber charging information (including roaming) for the use of the multicast mode (e.g. to enable billing to multicast services providers), as well as for the receipt of multicast data (e.g. users), on a per multicast service basis. On-line charging for multicast services should be possible as well.
+
+Examples of the type of the charging information that could be collected include:
+
+- multicast session duration
+- time when joining and leaving a multicast subscription group, duration of membership to a multicast subscription group
+- time when joining and leaving a multicast group, duration of membership to a multicast group
+- multicast session volume of contents
+
+The above list of possible charging mechanisms is neither complete nor exhaustive.
+
+Billing issues are out of scope of this TS.
+
+# --- Annex A (informative): MBMS Bit Rates
+
+Application bit rates for user services provided over MBMS are detailed within the stage 1 specification for 3GPP TS 22.246 "MBMS User Services" [7].
+
+# Annex B (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                   |       |       |         |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|-----------------------------------------------------------------------------------|-------|-------|---------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                   | Old   | New   | WI      |
+|                | SA1#13    |           | 22.146 |     |     |       |     | Creation of TS                                                                    |       | 0.1.0 | MBMS    |
+|                | SA1#13    |           | 22.146 |     |     |       |     | Output version from SA1 #13                                                       | 0.1.0 | 1.0.0 | MBMS    |
+|                | SA1 #13   |           | 22.146 |     |     |       |     | Raised to version 2.0.0 for approval at SA #13                                    | 1.0.0 | 2.0.0 | MBMS    |
+| SP-13          | SP-010443 | S1-010858 | 22.146 |     |     |       |     | Approved at SA #13                                                                | 2.0.0 | 5.0.0 | MBMS    |
+| SP-14          | SP-010678 | 1077      | 22.146 | 002 | 2   | Rel-5 | F   | Proposed CR on changes to definitions in 22.146                                   | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1305      | 22.146 | 003 | 3   | Rel-5 | B   | Proposed CR on clarification of reliable transmission                             | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1075      | 22.146 | 005 | 1   | Rel-5 | F   | Proposed CR on clarifications of the availability of MBMS                         | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1303      | 22.146 | 006 | 2   | Rel-5 | F   | Proposed CR on Clarification on MBMS applicability in Gb mode                     | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1306      | 22.146 | 009 | 2   | Rel-5 | F   | Proposed CR on data loss during handover                                          | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1076      | 22.146 | 011 | 1   | Rel-5 | C   | Proposed CR on optional privacy assurance for Multicast services                  | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1304      | 22.146 | 018 | 2   | Rel-5 | F   | Proposed CR to 22.146: High level Diagrams of MBMS                                | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1065      | 22.146 | 019 |     | Rel-5 | F   | CR Clarifying Service Requirements on Multicast and Broadcast Areas               | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1326      | 22.146 | 020 | 2   | Rel-5 | F   | Proposed CR to 22.146 MBMS                                                        | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1225      | 22.146 | 021 |     | Rel-5 | B   | Multiple Areas for Multicast and Broadcast Services                               | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1309      | 22.146 | 022 | 1   | Rel-5 | F   | MBMS service discovery                                                            | 5.0.0 | 5.1.0 | MBMS    |
+| SP-14          | SP-010678 | 1020      | 22.146 | 023 |     | Rel-5 | F   | CR to 22.146 (MBMS) UE and MS definition                                          | 5.0.0 | 5.1.0 | MBMS    |
+| SP-15          | SP-020057 | S1-020125 | 22.146 | 024 |     | Rel-5 | F   | CR 22.146 Rel. 5 F Area Specific QoS for Broadcast and Multicast Services         | 5.1.0 | 5.2.0 | MBMS    |
+| SP-15          | SP-020057 | S1-020128 | 22.146 | 025 |     | Rel-5 | F   | CR 22.146 Rel. 5 F Clause 4.2 Multicast mode                                      | 5.1.0 | 5.2.0 | MBMS    |
+| SP-15          | SP-020057 | S1-020133 | 22.146 | 026 |     | Rel-5 | F   | CR 22.146 Rel. 5 F Addition of MBMS multicast mode and broadcast mode definitions | 5.1.0 | 5.2.0 | MBMS    |
+| SP-15          | SP-020057 | S1-020563 | 22.146 | 027 |     | Rel-5 | B   | Proposed CR on MBMS Broadcast and Multicast Sessions                              | 5.1.0 | 5.2.0 | MBMS    |
+| SP-15          | SP-020057 | S1-020565 | 22.146 | 028 |     | Rel-5 | B   | Power consumption minimisation for MBMS                                           | 5.1.0 | 5.2.0 | MBMS    |
+| SP-15          | SP-020057 | S1-020646 | 22.146 | 029 |     | Rel-5 | F   | CR to 22.146 (MBMS stage 1) 'Editorial Change'                                    | 5.1.0 | 5.2.0 | MBMS    |
+| SP-15          | SP-020045 | S1-020457 | 22.146 | 030 | -   | Rel-5 | F   | Editorial CR to correct terms and references                                      | 5.1.0 | 5.2.0 | CORRECT |
+| SP-16          | SP-020257 | S1-020892 | 22.146 | 031 |     | Rel-6 | C   | Proposed CR on Multicast Joining Outside the Multicast Area                       | 5.2.0 | 6.0.0 | MBMS    |
+| SP-16          | SP-020257 | S1-021180 | 22.146 | 032 |     | Rel-6 | F   | CR to 22.146: Clarification of requirement related to paging messages             | 5.2.0 | 6.0.0 | MBMS    |
+| SP-17          | SP-020561 | S1-021473 | 22.146 | 033 |     | Rel-6 | B   | Support of simultaneous services in MBMS                                          | 6.0.0 | 6.1.0 | MBMS    |
+| SP-17          | SP-020561 | S1-021472 | 22.146 | 034 |     | Rel-6 | F   | Proposal for Amalgamation of 1279, 1334, 1291                                     | 6.0.0 | 6.1.0 | MBMS    |
+| SP-17          | SP-020561 | S1-021471 | 22.146 | 035 |     | Rel-6 | B   | Proposed CR to 22.146: addition of QoS information                                | 6.0.0 | 6.1.0 | MBMS    |
+| SP-17          | SP-020561 | S1-021469 | 22.146 | 036 |     | Rel-6 | F   | MBMS Editorial CR                                                                 | 6.0.0 | 6.1.0 | MBMS    |
+| SP-17          | SP-020561 | S1-021483 | 22.146 | 037 |     | Rel-6 | F   | Proposed CR 22.146 on MBMS Availability                                           | 6.0.0 | 6.1.0 | MBMS    |
+
+|         |           |           |        |      |   |        |   |                                                                                                                                       |        |        |          |
+|---------|-----------|-----------|--------|------|---|--------|---|---------------------------------------------------------------------------------------------------------------------------------------|--------|--------|----------|
+| SP-17   | SP-020561 | S1-021481 | 22.146 | 038  |   | Rel-6  | C | Proposed CR to 22.146: Multicast service discovery                                                                                    | 6.0.0  | 6.1.0  | MBMS     |
+| SP-17   | SP-020561 | S1-021475 | 22.146 | 039  |   | Rel-6  | B | CR to 22.146 on MBMS Charging                                                                                                         | 6.0.0  | 6.1.0  | MBMS     |
+| SP-19   | SP-030026 | S1-030154 | 22.146 | 040  | - | Rel-6  | C | CR to 22.146 - MBMS Cell broadcast in shared network                                                                                  | 6.1.0  | 6.2.0  | MBMS     |
+| SP-22   | SP-030705 | S1-031010 | 22.146 | 041  | - | Rel-6  | F | Alignment of MBMS use cases and bit rates                                                                                             | 6.2.0  | 6.3.0  | MBMS     |
+| SP-23   | SP-040094 | S1-040225 | 22.146 | 042  | - | Rel-6  | F | Clarification on user requirements for notification of multicast sessions                                                             | 6.3.0  | 6.4.0  | MBMS     |
+| SP-24   | SP-040291 | S1-040518 | 22.146 | 043  | - | Rel-6  | F | Addition of a concept regarding UE joining time                                                                                       | 6.4.0  | 6.5.0  | MBMS     |
+| SP-25   | SP-040504 | S1-040706 | 22.146 | 044  | - | Rel-6  | F | Rel-6 removal of notification requirement while receiving PS or CS services                                                           | 6.5.0  | 6.6.0  | MBMS     |
+| SP-25   | SP-040696 | -         | 22.146 | 045  | 1 | Rel-6  | F | Key management priority for MBMS services                                                                                             | 6.5.0  | 6.6.0  | MBMS     |
+| SP-30   | SP-050742 | S1-051233 | 22.146 | 0046 | - | Rel-7  | B | Enabling IMS to use the MBMS bearer service                                                                                           | 6.6.0  | 7.0.0  | MBMSE    |
+| SP-31   | SP-060019 | S1-060305 | 22.146 | 0048 | - | Rel-7  | A | Alignment of 22.146 with MBMS stage 3                                                                                                 | 7.0.0  | 7.1.0  | MBMS     |
+| SP-32   | SP-060309 | S1-060610 | 22.146 | 0049 | - | Rel-8  | B | Extends MBMS bearers to all 3GPP systems                                                                                              | 7.1.0  | 8.0.0  | MBMSE    |
+| SP-33   | SP-060465 | S1-060934 | 22.146 | 0051 | - | Rel-8  | A | Relaxing the current requirement that suggests a mandatory support for MBMS                                                           | 8.0.0  | 8.1.0  | MBMSE    |
+| SP-35   | SP-070116 | S1-070288 | 22.146 | 0052 | - | Rel-8  | B | Requirement of MBMS Service Subscription for Roaming Users                                                                            | 8.1.0  | 8.2.0  | MBMSE    |
+| SP-36   | SP-070360 | S1-070788 | 22.146 | 0055 | 3 | Rel-8  | F | Explicitly define the function                                                                                                        | 8.2.0  | 8.3.0  | MBMS     |
+| SP-36   | SP-070361 | S1-070644 | 22.146 | 0056 | - | Rel-8  | F | Broadcast service priority                                                                                                            | 8.2.0  | 8.3.0  | MBMS     |
+| SP-40   | SP-080306 | S1-080722 | 22.146 | 0058 | 1 | Rel-9  | F | Addition of the support of eMBMS in Rel-9                                                                                             | 8.3.0  | 9.0.0  | AIPN-SAE |
+| 2011-03 | -         | -         | -      | -    | - | -      | - | Update to Rel-10 version (MCC)                                                                                                        | 9.0.0  | 10.0.0 |          |
+| SP-54   | SP-110810 | S1-113183 | 22.146 | 0061 | 1 | Rel-10 | F | MBMS reception                                                                                                                        | 10.0.0 | 10.1.0 | TEI10    |
+| SP-59   | -         | -         | -      | -    | - | -      | - | Updated to Rel-11 version by MCC. Since an unofficial v.11.0.0 had circulated, the first Rel-11 official version is numbered v.11.1.0 | 10.1.0 | 11.1.0 |          |
+| 2014-10 | -         | -         | -      | -    | - | -      | - | Update to Rel-12 version (MCC)                                                                                                        | 11.1.0 | 12.0.0 |          |
+| 2015-12 | -         | -         | -      | -    | - | -      | - | Updated to Rel-13 by MCC                                                                                                              | 12.0.0 | 13.0.0 |          |

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

@@ -0,0 +1,290 @@
+
+
+# **3GPP TS 22.153 V13.0.0 (2015-06)** **Technical Specification Group Services and System Aspects;** **Multimedia priority service** **(Release 13)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a red signal icon above the "l". The word "ADVANCED" is written in a smaller, uppercase font above the "e". A trademark symbol (TM) is located at the bottom right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top, and the "P" has a red signal icon below it. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, uppercase font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+UMTS, GSM, LTE, multimedia
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- 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  |
+| 2014-10        | -         | -         | -      | -    | -   | -      | -   | Update to Rel-12 version (MCC)                                          | 11.1.0 | 12.0.0 |        |
+| 2015-06        | -         | -         | -      | -    | -   | -      | -   | Update to Rel-13 version (MCC)                                          | 12.0.0 | 13.0.0 |        |

marked/Rel-13/22_series/22174/raw.md

@@ -0,0 +1,476 @@
+
+
+# 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; **3GPP TS 22.174 V13.0.0 (2015-12)** ~~Service aspects; Stage 1~~ *Technical Specification* **(Release 13)** ---
+
+![LTE Advanced Pro logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the left of the "l" is a green signal icon consisting of three curved lines of increasing height.
+
+LTE Advanced Pro logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP. It features the letters "3GPP" in a stylized, black, bold font. The "3" is slightly larger and positioned to the left of the "G". The "P" and "P" are connected at the top by a single horizontal line. Below the second "P" is a small red signal icon consisting of three curved lines of increasing height. A small "TM" symbol is located to the top right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+Keywords  
+LTE, UMTS, push, stage 1
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- 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 Overview of the Push Service.....           | 6  |
+| 5 Requirements .....                          | 7  |
+| 5.1 General .....                             | 8  |
+| 5.2 Provisioning .....                        | 8  |
+| 5.3 Subscription.....                         | 8  |
+| 5.4 Addressing and Routing.....               | 9  |
+| 5.5 Delivery.....                             | 9  |
+| 5.6 Service Management.....                   | 10 |
+| 6 Security .....                              | 10 |
+| 7 Privacy .....                               | 10 |
+| 8 Access rules.....                           | 11 |
+| 9 Charging.....                               | 11 |
+| 10 Push Subscription Profile Information..... | 12 |
+| 11 Roaming .....                              | 12 |
+| 12 Barring of the Push Service .....          | 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.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The Push Service introduces a means to transmit push data from a push initiator to a push recipient (e.g. a UE) without a previous user action. The push concept, as provided by the SMS teleservice, has been very successful in the GSM second generation, both for text messaging (for user viewing) and for other unstandardized data to the SIM (as a building block used for OTA and other purposes). This TS introduces the Push Service as a generalization of existing network capabilities plus the development of new capabilities. The Push Service should therefore be understood as a building block (network capability), which can be used for new services, both public and private, in 3GPP.
+
+In the normal client/server model, a client requests a service or information from a server, which then responds in transmitting information to the client. This is known as the "pull" technology, the user pulls information from the content provider. The World Wide Web is a typical example of pull technology, where a user enters a URL (the request) that is sent to a server and the server answers by sending a Web page (the response) to the user.
+
+In contrast to this there is also the "push" technology where there is no explicit request from the user before the content provider (push initiator) initiates an information transfer to a user. Another way of saying this is that whereas "pull" transaction of information are always initiated from the user, "push" transactions are content provider initiated. The welcome message received after registration with a visited network whilst roaming is an example of information transfer that has been initiated without a request from the user. Typically, a user signs up with the push initiator and defines their interest, volume of information acceptable and other factors in the push subscription profile. As information becomes available that satisfies the user's push subscription profile, the push initiator delivers it to the user using the Push Service.
+
+The Push service may be used to implement high level services such as IP multimedia services, MMS, etc., and new services including public safety, government, corporate IT, transfer of push data to machines and devices, in addition to infotainment type services.
+
+Another common use for push services is the delivery of notification from e.g. MMS to the user while the user has the option of "pulling" the actual push data from the push initiator.
+
+The PLMN Push function provides the push data to the user agent in the UE. The user agent interprets and presents the push data to a person, device or machine using the UE.
+
+NOTE: The requirements of services such as streaming, conversational services and broadcast are independent from push. Therefore they are not considered appropriate for inclusion here. Push will be available for use in appropriate applications of all high level services.
+
+# --- 1 Scope
+
+This Technical Specification defines the Stage 1 description of the Push Service and is the set of requirements that shall be supported for the provision of push, seen primarily from the subscriber's, service providers' and delivery network points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers. It is of use to manufacturers and organisations which have devices or machines benefiting by availability of push service.
+
+This TS contains the core requirements for the Push Service, for operator and external Push Initiators, which are sufficient to provide a complete service capability and service capability feature.
+
+This TS defines the requirements for the Push Service to enable delivery of push data, including such functionality as:
+
+- Transfer of push data from a Push Initiator to a Push Recipient
+- Latency and Priority classes,
+- Definition of handling of undeliverable push data.
+
+# --- 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.133: "3G security; Security threats and requirements".
+
+[2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[3] 3GPP TS 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
+
+# --- 3 Definitions and abbreviations
+
+Definitions and abbreviations used in the present document are listed in TR 21.905 [2]. For the purposes of this document the following definitions and abbreviations apply:
+
+## 3.1 Definitions
+
+**Push Data:** data sent by the push initiator to the push recipient, of a format known to the receiver (push recipient), and not otherwise defined by the push service.
+
+**PLMN:** the 3GPP network that receives the push data from the push initiator and ensures the delivery of push data to the push recipient. The delivery of the push data may involve other networks.
+
+**Push function:** the function in the PLMN that receives the Push Data from the Push initiator. The push function is responsible for delivering the push data to the Push recipient.
+
+**Push initiator:** the entity that originates push data and submits it to the push function for delivery to a Push recipient. A Push initiator may be e.g. an application providing value added services.
+
+**Push recipient:** the entity that receives the push data from the Push function and processes or uses it. This may include the UE with which the PLMN communicates with, the user agent with the application level address, and the device, machine or person which uses the push data. A Push recipient is controlled by an individual user .
+
+**Push service:** a service capability offered by the PLMN. The Push Service is initiated by a Push Initiator in order to transfer push data (e.g. data, multimedia content) from the Push Initiator to the Push Recipient without a previous user action. The Push Service could be used as a basic capability or as component of a value added service.
+
+**Push User agent:** is any software or device associated with a Push recipient that interprets Push Data to the user. This may include textual browsers, voice browsers, search engines, machine or device interface software, etc.
+
+**Push Subscription Profile:** a set of parameters indicating the Push recipient's settings and preferences for the Push Service.
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+URL – Uniform Resource Locator.
+
+# 4 Overview of the Push Service
+
+The overview of push is followed by a summary of the relationships among the entities involved (operators, users, push recipients and push initiators).
+
+NOTE: these are functional descriptions: multiple functions may, depending on business arrangements, be performed by a single entity.
+
+![Diagram of Push Service Overview showing the flow from Push Initiator to Push function in the PLMN to the Push Recipient.](68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg)
+
+The diagram illustrates the flow of the Push Service. On the left, a box labeled 'User, Device, Or Machine' is identified as the 'Push Recipient'. In the center, a cloud labeled 'PLMN' contains a box labeled 'Push function'. On the right, a server icon is labeled 'Push Initiator'. Dashed arrows indicate the flow of data: from the Push Initiator to the Push function, and from the Push function to the Push Recipient. A large bracket at the bottom, spanning from the Push Recipient to the Push Initiator, is labeled 'Push Service'.
+
+Diagram of Push Service Overview showing the flow from Push Initiator to Push function in the PLMN to the Push Recipient.
+
+**Figure 1: Push Service Overview**
+
+The Push Service is a service whereby the Push Initiator sends push data through a Push Server to a Push Recipient, without interaction from the Push Recipient.
+
+The typical mode of operation is as follows:
+
+- A Push Recipient (e.g. user, receiving device like a meter) explicitly or implicitly subscribes to a set of value added services offered by various Push Initiators and allow these Push Initiators to send it push data that meet the Push Recipient's configured criteria. (This configured criteria is part of the Push user profile.)
+- A Push Initiator identifies information matching the criteria set by the Push Initiator and package it up into the push data
+- The Push Initiator delivers the push data to the Push function, identifying the Recipient's address, and optionally priority, delivery time parameters, etc.
+
+- The Push function takes the responsibility of delivering the push data, optionally following the priority and delivery time parameters, to the Push Recipient and for providing feedback to the Push Initiator regarding delivery of the push data if requested by the Push Initiator.
+
+Key characteristics of the Push Service include:
+
+- The Push Initiator may, but is not required to deal with the specifics of the wireless transport, selection of appropriate bearers, out-of-coverage or roaming issues, and other wireless network anomalies. These are all managed by the Push Service and hence can be optimised at the network level rather than being handled by all applications. Using an available bearer the push service offers as many capabilities that are available to delivery of the push data following the requested push services requested by the push initiator.
+- The push initiator shall be provided with a means to query the push server for a specific recipient's push user profile subject to privacy considerations.
+- The push server shall not change the push data (contents). Any transformations that the Push Server provides shall be compliant with user privacy requirements as defined in the push subscriber profile.
+- The push service shall be able to handle user groups (i.e. have the ability to target a certain group of push recipients).
+- The push service is capable of supporting asynchronous communication between a Push Initiator and the push recipient on a wireless device.
+- The privacy of the user is important and the introduction of the push services should in no way result in unwanted information "spam" being sent to mobile users.
+
+The Push data could contain:
+
+- Application specific data exchanged between a server and its client e.g. ERP, CRM, Field Service management, m-commerce transaction data or a meter reading
+- Provisioning or configuration control data
+
+The entities shown in Figure 1 are Push Initiator, Push Server (PLMN) and the Push Recipient. The Push Initiator may be outside the Operators network and hence will require well-defined relationships amongst them.
+
+For example, a Push Initiator can be within the Operator domain (e.g. an operator portal) or an external VASP. A Push Recipient (e.g. a User) will need to be part of the Operators network and will require allowing the network to pass through push data and also subscribing to the Push Initiator to generate the data it wants pushed. To support flexible billing models, it becomes necessary for the Operator to have a defined commercial relationship with the Push Initiator.
+
+# --- 5 Requirements
+
+The following list gives the high level requirements for the Push service.
+
+## 5.1 General
+
+The Push Service shall allow a Push Initiator (which may be external to the PLMN) to initiate delivery of push data to the Push recipient. It shall be possible to deliver push data to the push recipient without any user intervention, subject to settings in the push subscription profile. The Push Initiator may interrogate the push subscription profile, if available, in order to establish the user preference related to the Push Service.
+
+- The push mechanism shall be efficient in the use of network resources and terminal resources.
+- It shall be possible to support Push Service independently over CS (including CS data and SMS), PS domains or IMS.
+- NOTE: Operators should be able to choose which of these options they use to deliver Push services, and it should be possible to use these options independently from each other. E.g. delivery over the PS domain would allow operators who are not planning to introduce IMS and SMS to offer Push Services.
+
+- It shall be possible to deploy Push Services independently of other services defined by 3GPP.
+- The quality of service delivery shall be able to include time-sensitive as well as reliable delivery choices
+- It shall be possible to use all available access networks (e.g. GERAN, UTRAN,).
+- It shall be possible for the Push Initiator to specify a bearer for the Push Service, as a default the push service shall identify the bearer. The Push Initiator may, however, require certain grade of service for delivery, e.g. speed of delivery or delivery acknowledgement.
+
+## 5.2 Provisioning
+
+The operator shall be able to provision a user or organisation-user (e.g. a subscriber or a VASP) with the Push Service. The provision may include usage of the Push Service as a Push initiator, as a Push recipient or both.
+
+The provision may be:
+
+- general: where the service is made available to all user or organisation-users (subject to compatibility restrictions enforced) without prior arrangements being made with the operator;
+- pre-arranged: where the service is made available to an individual user or organisation-user only after the necessary arrangements have been made with the operator.
+
+If the user is provisioned with the Push Service as a Push initiator he may use the Push Service in order to transfer push data to the Push Recipient, subject to settings in the push subscription profile of the Push Recipient.
+
+If the user is provisioned with the Push Service as a Push recipient he may use the Push Service in order to receive push data from a Push initiator.
+
+The push subscription profile parameters (user's settings and preferences) are managed by the user or the operator on behalf of the user.
+
+The operator shall be able to withdraw the provision of the Push service. Withdrawal may be general or pre-arranged.
+
+NOTE: Provisioning with – or subscription to – value added services, that make use the Push service are out of scope of this specification.
+
+NOTE : the concept of organisation user may apply to GUP and if so will not be duplicated here.
+
+## 5.3 Subscription
+
+The usage of the Push Service to deliver push data from a Push Initiator to a Push Recipient requires as a precondition either an explicit or implicit subscription to the Push Service
+
+Explicit Push Subscription:
+
+A subscriber subscribes to the Push Service together with the Push service provider, i.e. the home PLMN operator. Home PLMN Push service providers may then use the Push service to deliver content to the subscriber.
+
+Implicit Push Subscription:
+
+A Value added service provider shall be able to subscribe to the Push Service on behalf of a subscriber to a value added service provided by this VASP. From a Push service point of view the subscriber becomes a push recipient. From now on the Value added service provider shall be able to use the Push Service capabilities to deliver content to this particular subscriber, i.e. the push recipient.
+
+The Push service subscription is valid for the subscriber to receive push data from the VASP that has subscribed to the Push service as long as the subscription is valid.
+
+## 5.4 Addressing and Routing
+
+It shall be possible to uniquely identify push recipients.
+
+It shall be possible for push recipients to uniquely identify push initiators.
+
+The addressing model shall include addresses of the device (e.g. IP address, SIP-URI, MSISDN) and application level addressing (i.e. user agents). The addressing model shall be compatible with Internet specifications when applicable.
+
+It shall be possible to deliver push data to a push recipient with a dynamically allocated IP address.
+
+The Push service shall be able to deliver a push data to a push recipient that does not have an IP address currently assigned.
+
+Both telecom and internet numbering and addressing schemes shall be supported.
+
+It shall be possible to address push recipients without allocating E.164 numbers.
+
+## 5.5 Delivery
+
+The PLMN may set restrictions including maximum size of Push data.
+
+The Push Service may offer classes of priority and service delivery. When offered this shall include support for the following:
+
+- Delivery time constraints (timing window, i.e. allow the push initiator to specify "deliver after" and "deliver before" parameters)
+- Requested delivery priority (different priorities dependent on for example push initiator, or allowing the push initiator to specify the desired priority)
+- If neither delivery time nor priority is set then a single attempt shall be made to deliver the push data without unnecessary delay.
+- The push service shall be able to send a delivery report to the push initiator, which includes information about a specific submission's final outcome (delivered, expired, etc.). The report is sent only if the push initiator requested it in the initial push submission or has requested it for all push submissions.
+- It shall be possible to deliver push data both in an acknowledged and an un-acknowledged manner between the push service and the push recipient
+- It shall be possible for the push initiator to request that only one delivery attempt is made.
+
+In case the push recipient declines a specific instance of push data, it shall be provided with means to indicate whether the push service is allowed to re-send it or not.
+
+In the case that classes of priority and service delivery are not offered an attempt to deliver push data to the push recipient shall be made without unnecessary delay.
+
+## 5.6 Service Management
+
+The basic principle of service management is "the user is in control".
+
+The user is provisioned with the Push Service by a Network Operator. If a user is provisioned with the push service, the provisioning data shall include a push subscription profile for push service settings and push service preferences. .
+
+The push subscription profile of a Push Recipient shall at least contain:
+
+- General settings, independent of individual Push initiators this may include:
+  - Permissible minimal QoS per data format for receiving push data
+  - Permissible maximum size of push data permitted to be pushed
+  - Permissible charging thresholds to receive push data
+- A mechanism for screening push initiators
+
+NOTE: Parameters may be bearer sensitive.
+
+# --- 6 Security
+
+The "Security Threats and Requirements" specified in 21.133 [1] shall not be compromised.
+
+It shall be possible for the Push Service Operator to be assured of the identity of the Push Initiator.
+
+It shall be possible for the Push Recipient to be assured of the identity of the Push Initiator.
+
+Mechanisms shall be provided to ensure that the push data is sent to and accessed only by the intended addressed entity.
+
+It shall be possible for the Push Service or the user to deny unauthorized push data.
+
+An authorization may be based on the following:
+
+- identity of the Push Initiator
+- the destination user, device or user agent
+- push related attributes such as priority and content type
+
+It shall be possible for the user to control acceptance of push data sent to the user based on the trust level of the Push Initiator.
+
+The Push Service shall provide data integrity and data confidentiality of the push data.
+
+Push Initiators must have authorization (e.g. service level agreement) with the Push Service Operator (e.g. PLMN Operators) in order to use the Push Service.
+
+# --- 7 Privacy
+
+The Push Service shall ensure compliance with the Push Recipient's privacy requirements as described below. Specific local, national, and regional privacy regulations shall be complied with. An operator shall, at any time, be able to override a Push Recipient's privacy preferences if required to do so by legal authorities.
+
+The privacy of the user is important and the introduction of the push services should in no way result in unwanted information "spam" being sent to mobile users.
+
+# --- 8 Access rules
+
+The Push Recipient shall be able to define access rules, in order to control how her privacy requirements shall be handled by the Push function.
+
+It shall be possible for the Push Recipient to define the following access rules:
+
+- The Push Recipient shall be able to allow push data from individual push initiators or groups of Push Initiators to transmit push data to the Push recipient
+- It shall be possible for the Push Recipient to uniquely identify a Push initiator and the addressed User Agent prior to accepting or declining a request to receive push data from that Push Initiator.
+- The Push Recipient shall be able to automatically decline push data from individual push initiators or groups of Push Initiators to transmit push data to the Push recipient
+- At any time it shall be possible for the Push Recipient to stop receipt of push data from a Push Initiator. This may include any push data from this Push Initiator or only push data addressed to a particular User Agent of the Push Recipient.
+- The Push Recipient shall be able to allow individual push initiators or groups of Push Initiators to transmit push data without user interaction at the Push Recipient's side.
+
+It shall be possible for the Push Recipient to define these access rules based on:
+
+- The identity of the Push Initiator
+- The addressed User Agent
+
+In addition it shall be possible for the Push Recipient to specify the validity of these access rules
+
+- Only for the next request of the Push Initiator or
+- For a pre-defined period e.g. next hour
+- Unlimited, i.e. till modification or removal of the access rule.
+
+NOTE: A set of default access rules may be defined by the operator.
+
+# --- 9 Charging
+
+This paragraph specifies charging requirements for the Push service.
+
+The Push service shall support various charging mechanisms (e.g. reverse, prepaid and reply charging etc.).
+
+The following charging scenarios shall be supported:
+
+1. Charging for the push service can be subscription based.  
+Different charging options shall be permissible whether the user is provisioned with the Push Service as a Push initiator or as a Push recipient.
+2. Charging for the push service can be based on the push data, the resources used and time needed to carry out the push service.
+3. Charging for the push service can be based on the size of the push data pushed to a receiver.
+4. It shall be possible to charge the Push recipient only, the Push Initiator only, or both.
+5. It shall also be possible to mix and match the various different charging scenarios outlined above.
+6. It shall be possible to charge for the initial push service activation.
+7. It shall be possible to charge a Push initiator for an attempt to send push data to a push recipient, even if the push recipient rejects the push data
+
+It shall be possible to include the following data in the CDRs as charging information if available:
+
+- message types, length, storage time in the network, etc
+- delivery time, upload / download method,
+- Push service sender / -recipient
+- the amount of the push data sent
+- the amount of the push data received.
+- roaming conditions (e.g. in a visited network)
+- location conditions
+
+# --- 10 Push Subscription Profile Information
+
+For each Push recipient the Push Service shall keep a Push subscription profile. This Push subscription profile shall contain the Push recipient's access rules.
+
+Optionally (as an operator's option) the Push subscription profile may contain additional Push personalization settings of the Push recipient, e.g.
+
+- Permissible minimal QoS per data format for receiving push data
+- Permissible maximum size of data packages permitted to be pushed
+- Permissible charging thresholds to receive push data
+- ...
+
+At any time the Push Service shall permit a Push recipient to modify her Push subscription profile information.
+
+A Push initiator shall be able to interrogate any Push Recipient's Push subscription profile information. However only information relevant to this Push Initiator shall be revealed by the Push Service
+
+NOTE: The Push subscription profile may be realized as part of the 3GPP Generic User Profile (TS 22.240) [3]
+
+# 11 Roaming
+
+Push services shall be available when roaming.
+
+The push recipients shall be able to select and receive pushed local services, subject to the user profile settings.
+
+# 12 Barring of the Push Service
+
+It shall be possible to provide the Push Service to a user regardless of barring status of other services, providing that a bearer to deliver the Push Content is available.
+
+It shall be possible for user to bar the Push Service regardless of barring status of other services.
+
+# Annex A (informative): Change history
+
+|          |               |                                                                                       |
+|----------|---------------|---------------------------------------------------------------------------------------|
+| V. 0.1.0 | February 2001 | First Draft (Presented at TSG-SA-WG1 6 <sup>th</sup> – 9 <sup>th</sup> February 2001) |
+| V. 0.2.0 | July 2001     | Second Draft (from SA1 ad-hoc, 9 July 2001)                                           |
+| V. 0.3.0 | November 2001 | Third Draft (presented at SA1 5 <sup>th</sup> – 9 <sup>th</sup> November 2001)        |
+| V. 0.3.1 | January 2002  | Highlighting removed as basis for Phoenix SWG (13-18 January 2002)                    |
+| V. 0.5.0 | January 2002  | Output of Phoenix Push SWG (15-16 January 2002).                                      |
+| v. 0.6.0 | February 2002 | Output from Saalfelden (11 <sup>th</sup> – 15 <sup>th</sup> February 2002)            |
+| v. 0.7.0 | April 2002    | Output from Sophia Antipolis (9 <sup>th</sup> April 2002)                             |
+| v. 0.7.1 | April 2002    | Clean copy of output from Sophia Antipolis                                            |
+| v. 0.8.0 | May 2002      | Output of Victoria (15 <sup>th</sup> May 2002)                                        |
+| v. 0.8.1 | May 2002      | Clean copy of output from Victoria                                                    |
+| v. 1.0.0 | May 2002      | Submission to SA for information                                                      |
+| v. 1.1.0 | July 2002     | Output of Rome (8 – 12 July 2002)                                                     |
+| v. 1.1.1 | July 2002     | Clean copy of output from Rome                                                        |
+| v. 1.2.0 | August 2002   | Output of Durango (12 – 16 August 2002)                                               |
+
+|          |             |                                   |
+|----------|-------------|-----------------------------------|
+| v. 1.2.1 | August 2002 | Clean copy of output from Durango |
+|----------|-------------|-----------------------------------|
+
+| Change history |           |           |        |     |     |       |     |                                                               |        |        |      |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|---------------------------------------------------------------|--------|--------|------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                               | Old    | New    | WI   |
+|                |           |           | 22.174 |     |     | Rel 6 |     | Updated for presentation to SA #17                            |        | 2.0.0  |      |
+| SP-17          | SP-20571  |           | 22.174 |     |     | Rel 6 |     | Presented to SA #17 for approval                              | 2.0.0  | 6.0.0  |      |
+| SP-18          | SP-020661 | S1-021947 | 22.174 | 001 |     | Rel-6 | F   | Removal of Note                                               | 6.0.0  | 6.1.0  | PUSH |
+| SP-18          | SP-020661 | S1-021949 | 22.174 | 002 |     | Rel-6 | C   | Removal of Media from Charging Parameters                     | 6.0.0  | 6.1.0  | PUSH |
+| SP-18          | SP-020661 | S1-021950 | 22.174 | 003 |     | Rel-6 | D   | Removal of void reference                                     | 6.0.0  | 6.1.0  | PUSH |
+| SP-18          | SP-020661 | S1-022188 | 22.174 | 004 |     | Rel-6 | C   | Push Delivery Class                                           | 6.0.0  | 6.1.0  | PUSH |
+| SP-18          | SP-020661 | S1-022334 | 22.174 | 005 |     | Rel-6 | D   | Revision of Requirements for One-Off Charging                 | 6.0.0  | 6.1.0  | PUSH |
+| SP-19          | SP-030027 | S1-030059 | 22.174 | 006 | -   | Rel-6 | C   | Removal of MMS content                                        | 6.1.0  | 6.2.0  | PUSH |
+| SP-19          | SP-030027 | S1-030250 | 22.174 | 007 | -   | Rel-6 | C   | Barring of Push Service                                       | 6.1.0  | 6.2.0  | PUSH |
+| SP-19          | SP-030027 | S1-030063 | 22.174 | 008 | -   | Rel-6 | C   | Removal of 'Null' Interworking Chapter                        | 6.1.0  | 6.2.0  | PUSH |
+| SP-19          | SP-030027 | S1-030117 | 22.174 | 009 | -   | Rel-6 | D   | CR to the PUSH Stage 1 TS on the Feature Interactions section | 6.1.0  | 6.2.0  | PUSH |
+| SP-36          |           |           | 22.174 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                   | 6.2.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 |      |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                | 11.0.0 | 12.0.0 |      |
+| 2015-12        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-13 by MCC                                      | 12.0.0 | 13.0.0 |      |