Add files using upload-large-folder tool

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

@@ -0,0 +1,788 @@
+
+
+
+
+
+
+# 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        |
+| <b>Annex C (normative):</b>   | <b>Definition of "busy" in a PLMN .....</b>                                       | <b>17</b> |
+| 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        |
+| <b>Annex D (normative):</b>   | <b>Call set-up procedures .....</b>                                               | <b>18</b> |
+| 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        |
+| <b>Annex E (normative):</b>   | <b>Automatic calling repeat call attempt restrictions .....</b>                   | <b>21</b> |
+| <b>Annex F (informative):</b> | <b>Procedures for call progress indications .....</b>                             | <b>23</b> |
+| 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        |
+| <b>Annex G (informative):</b> | <b>Change history.....</b>                                                        | <b>27</b> |
+
+# --- 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}<br>Number Unobtainable }<br>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 |         |

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

@@ -0,0 +1,669 @@
+
+
+
+
+
+
+# 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 |      |

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

@@ -0,0 +1,384 @@
+
+
+
+
+
+
+# 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 |                   |

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

@@ -0,0 +1,967 @@
+
+
+
+
+
+
+# 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.....                                                                                                                               | 7  |
+| 5.1 General .....                                                                                                                                                 | 7  |
+| 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.....                                                                                                                                             | 9  |
+| 6.4.1 General .....                                                                                                                                               | 9  |
+| 6.4.2 Voice calls .....                                                                                                                                           | 9  |
+| 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.....                                                                                                                                   | 10 |
+| 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 |
+
+**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:
+  - 5 presented to TSG for information;
+  - 5 presented to TSG for approval;
+  - 5 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.
+
+The present document included requirements 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?}
+    Action2 --> Action1
+    D9 -- Yes --> Action3[MS shall interpret this as USSD and send transparently towards the network]
+    D9 -- No --> Action4[Other meaning or error]
+    
+```
+
+The flowchart describes the logic for handling an input string in a mobile station (MS). It begins with the MS in an 'Idle or "in call"' state. Upon receiving an 'Input string', the system checks if it matches several criteria in sequence. If the string is a standard GSM SS procedure supported by the MS, a SIM control procedure, an MS manufacturer defined procedure, or a #-string, the MS performs the requested procedure. If it is a 'short string', the system checks if the MS is in a call; if yes, it performs the procedure; if no, it checks if the string is 2 digits starting with "1". If it is, or if the string is a 'call set-up string', it is sent as a call set-up request. If none of these apply, the system checks if USSD is supported. If USSD is supported, the string is interpreted as USSD and sent to 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 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, an indication is given to the user that the PIN must 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 must be entered.
+
+The PIN or PIN2 being entered is not revealed in any way. The PIN or PIN2 check is performed by entering the # function.
+
+### 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.**
+
+# 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 are labeled with input/output pairs like 'REQ/ICC' or 'REQ/Ok'.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> 1 : MS - OFF
+    1 --> 2 : ON
+    2 --> 3 : REQ
+    3 --> 2 : ICC
+    2 --> 4 : REQ
+    4 --> 2 : Ok
+    2 --> 5 : Failure
+    5 --> 2 : "LOCK"
+    2 --> 6 : REQ
+    6 --> 2 : Entered
+    2 --> 7 : Ok
+    7 --> 2 : Conditional
+  
+```
+
+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 are labeled with input/output pairs like 'REQ/ICC' or 'REQ/Ok'.
+
+Figure A.1: Mealy-graph for the UE access procedure
+
+![Mealy-graph for the In Case of Emergency access procedure. State 2 (Wait) transitions to state 8 (ICE) on 'ICE unlock (***)'. State 8 transitions back to state 2 on '"End" key'.](2eb23c2210154279f8013a1594fbcc5a_img.jpg)
+
+```
+
+stateDiagram-v2
+    2 --> 8 : ICE unlock (***)
+    8 --> 2 : "End" key
+  
+```
+
+Mealy-graph for the In Case of Emergency access procedure. State 2 (Wait) transitions to state 8 (ICE) on 'ICE unlock (\*\*\*)'. State 8 transitions back to state 2 on '"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 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|-----|-------------|-----|
+| <b>22.067</b>                                                                                                                                   | eMLPP                 | 75 and 75n        |     | where n=0-4 |     |
+| <b>22.072</b>                                                                                                                                   | CD                    | 66                |     |             |     |
+| <b>22.081</b>                                                                                                                                   | 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 “                                                   |                       |                   |     |             |     |
+| <b>22.082</b>                                                                                                                                   | 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   |
+| <b>22.083</b>                                                                                                                                   | WAIT                  | 43                | BS  | -           | -   |
+|                                                                                                                                                 | HOLD                  | see section 4.5.5 |     |             |     |
+| <b>22.084</b>                                                                                                                                   | MPTY                  | see section 4.5.5 |     |             |     |
+| <b>22.087</b>                                                                                                                                   | 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 |           |
+| 2012-09        | -         | -         | -      | -    | -    | -     | -   | Update to Rel-11 version (MCC)                              | 10.0.0 | 11.0.0 |           |

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

@@ -0,0 +1,307 @@
+
+
+
+
+
+
+# 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.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram is a sequence diagram illustrating the message flow between two entities: HPLMN (Home PLMN) on the left and VPLMN (Visited PLMN) on the right. The interaction consists of the following steps:
+
+- The HPLMN sends a **Request for FIGS monitoring** message to the VPLMN.
+- The VPLMN responds with a **Positive Acknowledgement** message back to the HPLMN.
+- The VPLMN then sends a **FIGS Data** message to the HPLMN.
+- Subsequently, another **FIGS Data** message is sent from the VPLMN to the HPLMN.
+- Finally, the HPLMN sends a **Request to stop FIGS monitoring** message to the VPLMN.
+
+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           | <b>11.0.0</b>    |

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

@@ -0,0 +1,736 @@
+
+
+
+
+
+
+# --- 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 contains a SIM/USIM card. The scope of this TS is indicated by arrows pointing to the ME and the SIM/USIM card, and a label 'Scope of this TS' pointing to the ME and SIM/USIM components.](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg)
+
+The diagram shows a Mobile Equipment (ME) represented by a rectangle with a small antenna. Inside the ME, at the bottom, is a box labeled 'SIM/USIM'. Above the SIM/USIM box are two side-by-side boxes labeled 'GSM/UMTS' and 'SAT/USAT'. The ME is connected to a cloud labeled 'PLMN' by a double-headed arrow. The PLMN cloud is connected to another cloud labeled 'SAT/USAT Server(s)' by a single-headed arrow. A label 'Scope of this TS' has arrows pointing to the ME and the SIM/USIM box, indicating that the scope of the specification covers these components and their interaction with the PLMN.
+
+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 contains a SIM/USIM card. The scope of this TS is indicated by arrows pointing to the ME and the SIM/USIM card, and a label 'Scope of this TS' pointing to the ME and SIM/USIM components.
+
+**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 |         |

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

@@ -0,0 +1,346 @@
+
+
+
+
+
+
+# --- 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         |

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

@@ -0,0 +1,253 @@
+
+
+
+
+
+
+# --- 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 # | 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 |

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

@@ -0,0 +1,260 @@
+
+
+
+
+
+
+# --- 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> |              |                 |           |            |                                 |      |          |                           |
+| <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>     |
+| 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             |

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

@@ -0,0 +1,454 @@
+
+
+
+
+
+
+# --- 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.
+
+![Solid black arrow with large arrowhead Dotted black arrow Solid black arrow with a cross (X) and a cyan arrowhead Dashed black arrow Thin solid black arrow with small arrowhead Single oval Double oval (one inside another)](d793cf7c174b89eb024d132f00679787_img.jpg)
+
+|  |                                                             |  |                                                                    |
+|--|-------------------------------------------------------------|--|--------------------------------------------------------------------|
+|  | <b>Traffic route</b>                                        |  | <b>Output of call record information</b>                           |
+|  | <b>Traffic route of basic GSM routeing, not used for OR</b> |  | <b>Interrogation</b>                                               |
+|  | <b>Call Attempt</b>                                         |  |                                                                    |
+|  | <b>Functional PLMN (e.g. IPLMN, VPLMN-B)</b>                |  | <b>Administrative PLMN, which may include two functional PLMNs</b> |
+
+Solid black arrow with large arrowhead Dotted black arrow Solid black arrow with a cross (X) and a cyan arrowhead Dashed black arrow Thin solid black arrow with small arrowhead Single oval Double oval (one inside another)
+
+**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 diagram showing call flow between Country X, Country Y, and Country Z. Subscriber A in Country X initiates a call attempt to Country Y. In Country Y, the call reaches an IPLMN which interrogates HPLMN-B (both within an administrative PLMN oval). A call record box is shown with 'Call record: Call forwarding record OR flag'. The call is then routed to subscriber C within Country Y. A separate VPLMN-B is shown in Country Z, but the traffic route to it is crossed out, indicating it is not used for OR.](06da11ab76cacc38bbcd714e437797ea_img.jpg)
+
+Scenario 1 diagram showing call flow between Country X, Country Y, and Country Z. Subscriber A in Country X initiates a call attempt to Country Y. In Country Y, the call reaches an IPLMN which interrogates HPLMN-B (both within an administrative PLMN oval). A call record box is shown with 'Call record: Call forwarding record OR flag'. The call is then routed to subscriber C within Country Y. A separate VPLMN-B is shown in Country Z, but the traffic route to it is crossed out, indicating it is not used for OR.
+
+**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 call routing for Scenario 2: OR for Late Call Forwarding. The diagram shows 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 'Call forwarding record' and 'OR flag'. The call is then routed to Country Z, where it is forwarded to subscriber C. The call record is also forwarded to the VPLMN-B.](35a7554182eb055209552843f341a1ae_img.jpg)
+
+The diagram shows the call routing process for Scenario 2. 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 'Call forwarding record' and 'OR flag'. The call is then routed to Country Z, where it is forwarded to subscriber C. The call record is also forwarded to the VPLMN-B.
+
+Diagram illustrating call routing for Scenario 2: OR for Late Call Forwarding. The diagram shows 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 'Call forwarding record' and 'OR flag'. The call is then routed to Country Z, where it is forwarded to subscriber C. The call record is also forwarded to the VPLMN-B.
+
+#### 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 from subscriber A goes to VPLMN-A (step 1). VPLMN-A sends an MO record (step 2) and routes the call to IPLMN (step 3). IPLMN routes the call to HPLMN-B in Country Y (step 4). HPLMN-B routes the call to VPLMN-B (step 5). VPLMN-B sends an MT record (step 6) and delivers the call to subscriber B. Call records are generated at steps 1 and 5.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates the call flow for Scenario 3. A call from subscriber A in Country X is routed through VPLMN-A to IPLMN. IPLMN then routes it to HPLMN-B in Country Y, which in turn routes it to VPLMN-B. Call records are generated at the originating (MO record) and terminating (MT record) VPLMNs.
+
+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 from subscriber A goes to VPLMN-A (step 1). VPLMN-A sends an MO record (step 2) and routes the call to IPLMN (step 3). IPLMN routes the call to HPLMN-B in Country Y (step 4). HPLMN-B routes the call to VPLMN-B (step 5). VPLMN-B sends an MT record (step 6) and delivers the call to subscriber B. Call records are generated at steps 1 and 5.
+
+**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 from subscriber A goes to VPLMN-A (step 1). VPLMN-A sends an MO record (step 2) and routes the call to IPLMN (step 3). IPLMN routes the call to HPLMN-B in Country Y (step 4). HPLMN-B routes the call to VPLMN-B (step 5). VPLMN-B delivers the call to subscriber B (step 6) and generates an MT record. Call records are generated at steps 1 and 5.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+The diagram illustrates the call flow for Scenario 4. A call from subscriber A in Country X is routed through VPLMN-A to IPLMN. IPLMN routes it to HPLMN-B in Country Y, which then routes it to VPLMN-B. Call records are generated at the originating (MO record) and terminating (MT record) VPLMNs.
+
+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 from subscriber A goes to VPLMN-A (step 1). VPLMN-A sends an MO record (step 2) and routes the call to IPLMN (step 3). IPLMN routes the call to HPLMN-B in Country Y (step 4). HPLMN-B routes the call to VPLMN-B (step 5). VPLMN-B delivers the call to subscriber B (step 6) and generates an MT record. Call records are generated at steps 1 and 5.
+
+**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) to subscriber C in Country X via HPLMN-B in Country Y. The call is forwarded by IPLMN. Call records are generated at the VPLMN-A and IPLMN nodes.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates a call flow for Scenario 5. Subscriber A is in Country X, connected to VPLMN-A. VPLMN-A is connected to IPLMN. IPLMN is connected to HPLMN-B in Country Y. HPLMN-B is connected to VPLMN-B in 'Any country'. Subscriber C is in Country X, connected to VPLMN-A. The call flow is: 1. A to VPLMN-A; 2. VPLMN-A to IPLMN; 3. IPLMN to HPLMN-B; 4. HPLMN-B to IPLMN; 5. IPLMN to C. There are call records generated at VPLMN-A (MO record) and IPLMN (Call forwarding record). Arrows 3 and 4 are crossed out with an 'X'.
+
+**Country X** **Country Y**
+
+**HPLMN-B**
+
+**IPLMN**
+
+**VPLMN-A**
+
+**C**
+
+**Any country**
+
+**VPLMN-B**
+
+**A**
+
+**1** **2** **3** **4** **5**
+
+**Call record:**  
+MO record  
+(Dialled nmb,  
+real destination,  
+OR flag)
+
+**Call record:**  
+Call forwarding  
+record  
+(OR flag)
+
+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) to subscriber C in Country X via HPLMN-B in Country Y. The call is forwarded by IPLMN. Call records are generated at the VPLMN-A and IPLMN nodes.
+
+**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) to subscriber C in Country Y (HPLMN-B) via IPLMN. The call is forwarded by HPLMN-B. Call records are generated at the VPLMN-A and IPLMN nodes.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+The diagram illustrates a call flow for Scenario 6. Subscriber A is in Country X, connected to VPLMN-A. VPLMN-A is connected to IPLMN. IPLMN is connected to HPLMN-B in Country Y. HPLMN-B is connected to VPLMN-B in 'Any country'. Subscriber C is in Country Y, connected to HPLMN-B. The call flow is: 1. A to VPLMN-A; 2. VPLMN-A to IPLMN; 3. IPLMN to HPLMN-B; 4. HPLMN-B to IPLMN; 5. IPLMN to C. There are call records generated at VPLMN-A (MO record) and IPLMN (Call forwarding record). Arrows 3 and 4 are crossed out with an 'X'.
+
+**Country X** **Country Y**
+
+**HPLMN-B**
+
+**IPLMN**
+
+**VPLMN-A**
+
+**C**
+
+**Any country**
+
+**VPLMN-B**
+
+**A**
+
+**1** **2** **3** **4** **5**
+
+**Call record:**  
+MO record  
+(Dialled nmb,  
+real destination,  
+OR flag)
+
+**Call record:**  
+Call forwarding  
+record  
+(OR flag)
+
+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) to subscriber C in Country Y (HPLMN-B) via IPLMN. The call is forwarded by HPLMN-B. Call records are generated at the VPLMN-A and IPLMN nodes.
+
+**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: BASIC OR + OR for Late Call Forwarding. It shows a call flow between Country X and Country Y. In Country X, the call starts at point A, goes to VPLMN-A (step 1), then to IPLMN (step 2). From IPLMN, a 'Call record: Call forwarding record (OR flag)' is generated. The call then proceeds to Country Y (step 3) to HPLMN-B. From HPLMN-B, the call is forwarded to VPLMN-B (step 4). A 'Call record: MO record (Dialled nmb, real destination, OR flag)' is generated at VPLMN-B (step 5). The call is then forwarded to point C (step 6). Arrows 3, 4, and 5 are crossed out with an 'X'.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+Diagram for Scenario 7: BASIC OR + OR for Late Call Forwarding. It shows a call flow between Country X and Country Y. In Country X, the call starts at point A, goes to VPLMN-A (step 1), then to IPLMN (step 2). From IPLMN, a 'Call record: Call forwarding record (OR flag)' is generated. The call then proceeds to Country Y (step 3) to HPLMN-B. From HPLMN-B, the call is forwarded to VPLMN-B (step 4). A 'Call record: MO record (Dialled nmb, real destination, OR flag)' is generated at VPLMN-B (step 5). The call is then forwarded to point C (step 6). Arrows 3, 4, and 5 are crossed out 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: BASIC OR + OR for Late Call Forwarding. It shows a call flow between Country X and Country Y. In Country X, the call starts at point A, goes to VPLMN-A (step 1), then to IPLMN (step 2). From IPLMN, a 'Call record: Call forwarding record (OR flag)' is generated. The call then proceeds to Country Y (step 3) to HPLMN-B. From HPLMN-B, the call is forwarded to VPLMN-B (step 4). A 'Call record: MO record (Dialled nmb, real destination, OR flag)' is generated at VPLMN-B (step 5). The call is then forwarded to point C (step 6). Arrows 3, 4, and 5 are crossed out with an 'X'.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+Diagram for Scenario 8: BASIC OR + OR for Late Call Forwarding. It shows a call flow between Country X and Country Y. In Country X, the call starts at point A, goes to VPLMN-A (step 1), then to IPLMN (step 2). From IPLMN, a 'Call record: Call forwarding record (OR flag)' is generated. The call then proceeds to Country Y (step 3) to HPLMN-B. From HPLMN-B, the call is forwarded to VPLMN-B (step 4). A 'Call record: MO record (Dialled nmb, real destination, OR flag)' is generated at VPLMN-B (step 5). The call is then forwarded to point C (step 6). Arrows 3, 4, and 5 are crossed out 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 forwarding paths 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 flow from A to C, with call records generated at various points.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+The diagram illustrates a call forwarding scenario between Country X and Country Y. In Country X, there is an IPLMN and a VPLMN-A. In Country Y, there is an HPLMN-B and a VPLMN-B. A call originates at point A (VPLMN-A) and is forwarded to point C (VPLMN-B). The call flow 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; 5. From VPLMN-B to IPLMN; 6. From IPLMN to C. Call records are generated at point A (MO record) and at the IPLMN (Call forwarding record).
+
+Diagram for Scenario 9 showing call forwarding paths 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 flow from A to C, with call records generated at various points.
+
+**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 forwarding paths 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 flow from A to C, with call records generated at various points.](853f59c89931a666c07903b31d098277_img.jpg)
+
+The diagram illustrates a call forwarding scenario between Country X and Country Y. In Country X, there is an IPLMN and a VPLMN-A. In Country Y, there is an HPLMN-B and a VPLMN-B. A call originates at point A (VPLMN-A) and is forwarded to point C (VPLMN-B). The call flow 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; 5. From VPLMN-B to IPLMN; 6. From IPLMN to C. Call records are generated at point A (MO record) and at the IPLMN (Call forwarding record).
+
+Diagram for Scenario 10 showing call forwarding paths 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 flow from A to C, with call records generated at various points.
+
+**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 |                   |

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

@@ -0,0 +1,1358 @@
+
+
+
+
+
+
+# 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              | No    |
+| notification the call has been forwarded | Yes   |
+| MSISDN of the served subscriber can be   | No    |
+| presented to the forwarded-to subscriber | 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 so 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 | 0005 | -   | Rel-11 | B   | Addition of Anonymous Call Rejection as a SS | 10.0.0 | 11.0.0 | ACR_CS            |

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

@@ -0,0 +1,468 @@
+
+
+
+
+
+
+# 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 |                   |

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

@@ -0,0 +1,396 @@
+
+
+
+
+
+
+# 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 |                   |

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

@@ -0,0 +1,480 @@
+
+
+
+
+
+
+# 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            |

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

@@ -0,0 +1,265 @@
+
+
+
+
+
+
+# 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 |           |

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

@@ -0,0 +1,439 @@
+
+
+
+
+
+
+# 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 |           |

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

@@ -0,0 +1,301 @@
+
+
+
+
+
+
+# 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 |                   |

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

@@ -0,0 +1,390 @@
+
+
+
+
+
+
+# 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 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 |           |

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

@@ -0,0 +1,655 @@
+
+
+
+
+
+
+# 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 (excepted 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. It shows the Home Location Register (HLR) in France, anchor and serving MSCs in Germany, and target MSCs in the Netherlands and Belgium. Connections are shown as dotted (signalling) and solid (circuit switched) lines.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg)
+
+The diagram shows a map of Western Europe with several network elements overlaid. 
+ 
+
+- France:** Contains a yellow cylinder labeled **HLR** and a yellow box labeled **Gateway MSC**.
+- Germany:** Contains a yellow box labeled **MSC** (the anchor MSC) and a yellow box labeled **VLR**. A second yellow box labeled **Gateway MSC** is also shown in Germany.
+- Netherlands:** Contains a pink box labeled **MSC**.
+- Belgium:** Contains a pink box labeled **MSC**.
+- Cell Towers:** Represented by icons with numbers (1) Germany, (2) Netherlands, and (3) Belgium next to them.
+- Connections:**
+  - Dotted lines represent signalling connections between the **HLR** in France and the **VLR** in Germany, and between the **HLR** and the **Gateway MSC** in Germany.
+  - Solid lines represent circuit-switched connections between the **anchor MSC** in Germany and the **serving MSC** in the Netherlands, and between the **anchor MSC** and the **Gateway MSC** in Germany.
+
+Diagram illustrating inter-PLMN handover elements across France, Germany, Netherlands, Belgium, and Luxembourg. It shows the Home Location Register (HLR) in France, anchor and serving MSCs in Germany, and target MSCs in the Netherlands and Belgium. Connections are shown as dotted (signalling) and solid (circuit switched) lines.
+
+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 |           |

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

@@ -0,0 +1,572 @@
+
+
+
+
+
+
+# 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 be used for speech at any one time.
+
+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 |         |