Add files using upload-large-folder tool

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

@@ -0,0 +1,857 @@
+
+
+# 3GPP TS 22.001 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+LTE, GSM, UMTS, service
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                       |           |
+|-------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                        | 5         |
+| 0 Scope.....                                                                                          | 6         |
+| 0.1 References .....                                                                                  | 6         |
+| 0.2 Abbreviations .....                                                                               | 6         |
+| 1 Framework for the description of telecommunication services .....                                   | 7         |
+| 1.1 The attribute method of characterization of circuit telecommunication services .....              | 7         |
+| 2 Description of circuit telecommunication services by the attribute method.....                      | 7         |
+| 2.1 General .....                                                                                     | 7         |
+| 2.2 Categorisation of telecommunication services.....                                                 | 7         |
+| 3 Characterization of circuit telecommunication services .....                                        | 7         |
+| 3.1 General .....                                                                                     | 7         |
+| 3.2 Bearer services .....                                                                             | 8         |
+| 3.3 Teleservices.....                                                                                 | 8         |
+| 4 Provision of telecommunication services .....                                                       | 8         |
+| 4.1 Subscription checking for Basic Services.....                                                     | 9         |
+| 4.2 Subscription checking for Supplementary Services.....                                             | 10        |
+| <b>Annex A (normative): List of definition of attributes and values used for bearer services.....</b> | <b>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.....</b>   | <b>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:<br><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 |         |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                        | 11.0.0 | 12.0.0 |         |
+| 2015-12        |           |           |        |     |     |       |     | Update to Rel-13 version (MCC)                                        | 12.0.0 | 13.0.0 |         |
+| 2017-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-14 by MCC                                              | 13.0.0 | 14.0.0 |         |
+| 2018-06        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-15 by MCC                                              | 14.0.0 | 15.0.0 |         |
+| 2020-07        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-16 by MCC                                              | 15.0.0 | 16.0.0 |         |
+| 2020-07        | -         | -         | -      | -   | -   | -     | -   | Previous version incorrectly named "22001-h00" instead of "22001-g00" | 16.0.0 | 16.0.1 |         |
+| SA#95e         | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-17 by MCC                                              | 16.0.1 | 17.0.0 |         |
+| 2024-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload)             | 17.0.0 | 18.0.1 |         |

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

@@ -0,0 +1,423 @@
+
+
+# 3GPP TS 22.002 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font. The 'G' has a red signal wave icon below it.
+
+3GPP logo
+
+## Keywords
+
+---
+
+LTE, GSM, UMTS, circuit mode, bearer
+
+### **3GPP**
+
+### Postal address
+
+### --- 3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet
+
+---
+
+<http://www.3gpp.org>
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+---
+
+# --- Contents
+
+|                                                                                |           |
+|--------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                 | 4         |
+| 0 Scope.....                                                                   | 5         |
+| 0.1 References .....                                                           | 5         |
+| 0.2 Abbreviations .....                                                        | 5         |
+| 1 Framework for defining Circuit Bearer Services .....                         | 6         |
+| 2 Bearer Service categories.....                                               | 7         |
+| 3 Bearer Services .....                                                        | 7         |
+| 3.1 General bearer service user data characteristics.....                      | 8         |
+| 3.1.1 BS 20 (asynchronous services).....                                       | 9         |
+| 3.1.1.1 BS 20 T (transparent asynchronous services).....                       | 9         |
+| 3.1.1.1.1 BS 20 transparent in regular mode for analogue interworking .....    | 9         |
+| 3.1.1.1.2 BS 20 transparent in regular mode for digital interworking .....     | 9         |
+| 3.1.1.2 BS 20 NT (non-transparent asynchronous services).....                  | 10        |
+| 3.1.1.2.1 BS 20 non-transparent in regular mode for analogue interworking..... | 10        |
+| 3.1.1.2.2 BS 20 non-transparent in regular mode for digital interworking ..... | 10        |
+| 3.1.1.2.3 BS 20 non-transparent for PIAFS .....                                | 11        |
+| 3.1.1.2.4 BS 20 non-transparent for Frame Tunnelling Mode .....                | 11        |
+| 3.1.2 BS 30 (synchronous services) .....                                       | 12        |
+| 3.1.2.1 BS 30 T (transparent synchronous services).....                        | 12        |
+| 3.1.2.1.1 BS 30 transparent in regular mode for analogue interworking .....    | 12        |
+| 3.1.2.1.2 BS 30 transparent in regular mode for digital interworking .....     | 12        |
+| 3.1.2.1.3 BS 30 transparent for Multimedia.....                                | 12        |
+| <b>Annex A (informative): Change history.....</b>                              | <b>13</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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 0 Scope
+
+The present document defines a set of Circuit Bearer Services to be provided to PLMN subscribers by a PLMN itself and in connection with other networks. This TS should also be used as a reference for defining the corresponding required mobile network capabilities.
+
+## 0.1 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] TS 41.004: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] TS 22.001: " Principles of circuit telecommunication services supported by a GSM Public Land Mobile Network (PLMN)".
+- [3] TS 22.004: " General on supplementary services".
+- [4] TS 27.001: " General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+- [5] TS 27.002: " Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities".
+- [6] TS 27.003: " Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
+- [7] TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
+- [8] TS 29.002: " Mobile Application Part (MAP) specification".
+- [9] TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
+- [10] TS 29.010: " Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)".
+- [11] TS 29.011: " Signalling interworking for supplementary services".
+- [12] ITU-T Recommendation V.120: "Support by an ISDN of data terminal equipments with V-series type interface with provision for statistical multiplexing".
+- [13] TR 21.905: "Vocabulary for 3GPP Specifications"
+
+## 0.2 Abbreviations
+
+Abbreviations used in this TS are listed in TS 41.004 [1] and TR 21.905 [13].
+
+# 1 Framework for defining Circuit Bearer Services
+
+Bearer Services are described by attributes, which are intended to be independent. These attributes are described and defined in TS 22.001 [2]. They are grouped into four categories:
+
+- i) Information transfer attributes, which characterize the network capabilities for transferring information from a user access point in a PLMN to a user access point in another network. (Refer to TS 22.001 [2] ).
+- ii) Access attributes, which describe the means for accessing network functions or facilities as seen at the access point in the PLMN (see TS 22.001 [2]).
+- iii) Interworking attributes, which describe properties of the terminating network and its access point. The terminating network may include another PLMN or the originating PLMN.
+- iv) General attributes, which deal with the service in general.
+
+Figure 1 shows the relation between the groups of attributes and their fields of applicability.
+
+![Diagram illustrating the relation between groups of attributes and their fields of applicability. The diagram shows three overlapping circles representing network components: PLMN, Transit Network (note 1), and Terminating Network. The PLMN and Transit Network overlap at an IWF (Interworking Function). The Transit Network and Terminating Network overlap at another IWF. Above the diagram, 'Information Transfer and Access Attributes (note 3)' are indicated by a double-headed arrow spanning the PLMN and IWF. Below the diagram, 'Interworking Attributes' are indicated by a double-headed arrow spanning the IWF and Transit Network. At the bottom, 'General Attributes (note 2)' are indicated by a long double-headed arrow spanning the entire sequence from PLMN to Terminating Network.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg)
+
+Diagram illustrating the relation between groups of attributes and their fields of applicability. The diagram shows three overlapping circles representing network components: PLMN, Transit Network (note 1), and Terminating Network. The PLMN and Transit Network overlap at an IWF (Interworking Function). The Transit Network and Terminating Network overlap at another IWF. Above the diagram, 'Information Transfer and Access Attributes (note 3)' are indicated by a double-headed arrow spanning the PLMN and IWF. Below the diagram, 'Interworking Attributes' are indicated by a double-headed arrow spanning the IWF and Transit Network. At the bottom, 'General Attributes (note 2)' are indicated by a long double-headed arrow spanning the entire sequence from PLMN to Terminating Network.
+
+NOTE 1: A transit network may not exist for a Bearer Service.
+
+NOTE 2: Communication may be established from either end.
+
+NOTE 3: The information transfer and access attributes of a Bearer Service relate to a direct peer-to-peer communication of:
+
+- TE to TE;
+- TE to a network gateway (supporting, for example, PSTN interworking); or
+- network gateway to a TE.
+
+**Figure 1: Relation between the groups of attributes and fields of applicability**
+
+The following table lists the individual attributes in each of the four groups. The Bearer Service definitions in this specification are based on the "Minimal Set" of attributes.
+
+**Table 1: List of Bearer Service attributes**
+
+|                                        | Minimal Set |
+|----------------------------------------|-------------|
+| <b>Information Transfer Attributes</b> |             |
+| Information Transfer Mode              | X           |
+| Information Transfer Rate              | X           |
+| Information Transfer Capability        | X           |
+| Establishment of Communication         | X           |
+| Symmetry                               | X           |
+| Communication Configuration            | X           |
+| Data Compression                       |             |
+| <b>Access Attributes</b>               |             |
+| Access Channel and Rate                |             |
+| Signalling Access Protocols            |             |
+| Information Access Protocols           |             |
+| Information Access Structure           | X           |
+| Information Access Rate                | X           |
+| <b>Interworking Attributes</b>         |             |
+| <b>General Attributes</b>              |             |
+| Supplementary Services Provided        |             |
+| Quality of Service                     | X           |
+| Operational and Commercial             |             |
+
+Attributes that are not part of the minimal set provide further technical detail and are required to fully define the use of each Bearer Service.
+
+See specifications [4], [5], [6], [7] for information about the Signalling Access Protocols, Information Access Protocols and related access attributes.
+
+Supplementary services are defined in TS 22.004 [3].
+
+Intercommunication is required with services in the PSTN, ISDN and other PLMNs. The capabilities that describe the Interworking Attributes are described in specifications [8] to [9] and [15].
+
+# --- 2 Bearer Service categories
+
+All Bearer Service categories provide information transfer between the reference points and allow the use of sub-rate information streams which are rate-adapted.
+
+The Bearer Services can be grouped into the following categories:
+
+- Unrestricted Digital Information (UDI);
+
+Provides the transfer of unrestricted digital information.
+
+- 3,1 kHz (External to the PLMN);
+
+Used to select a "3,1 kHz audio" interworking function at the MSC. This service category is used when interworking with the ISDN or PSTN "3,1 kHz audio" service and includes the capability to select a modem at the interworking function. "External to the PLMN" indicates that the "3,1 kHz audio" service is only used outside of the PLMN, in the ISDN/PSTN. The connection within the PLMN, user access point to the interworking function, is an unrestricted digital connection.
+
+# --- 3 Bearer Services
+
+This clause provides a list of the existing Bearer Services and indicates the values for each attribute in the minimal set.
+
+The following attributes have the same value for all Bearer Services. Their values are as follows:
+
+Information Transfer Mode: "Circuit";
+
+Information Transfer Rate: Not applicable (note 1);  
+ Establishment of Communication: "Demand";  
+ Symmetry: "Bi-directional Symmetric";  
+ Communication Configuration: "Point to point".
+
+NOTE 1: The Information Transfer Rate attribute is not applicable because it depends on the reference point assumed in the PLMN, transit or terminating network.
+
+All asynchronous NT Bearer Services may support data compression to enhance user data throughput.
+
+NT Bearer Services 20 may support V.120 interworking, enabling data terminals connected to an UE to interwork with V.120 [12] terminal adapters on the ISDN as shown in the figure 2 below.
+
+![Figure 2: Model of V.120 Interworking. The diagram shows a sequence of components: Async/Sync Terminal, UE, RAN, MSC, IWF, and V.120 TA. The R reference point is marked at the Async/Sync Terminal. The PLMN (Packet Switched Network) section includes the UE, RAN, MSC, and IWF. The ISDN (Integrated Services Digital Network) section includes the IWF and V.120 TA. The V.110 protocol is indicated between the UE and the IWF, while the V.120 protocol is indicated between the IWF and the V.120 TA.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+Figure 2: Model of V.120 Interworking. The diagram shows a sequence of components: Async/Sync Terminal, UE, RAN, MSC, IWF, and V.120 TA. The R reference point is marked at the Async/Sync Terminal. The PLMN (Packet Switched Network) section includes the UE, RAN, MSC, and IWF. The ISDN (Integrated Services Digital Network) section includes the IWF and V.120 TA. The V.110 protocol is indicated between the UE and the IWF, while the V.120 protocol is indicated between the IWF and the V.120 TA.
+
+Figure 2: Model of V.120 Interworking
+
+Table 2 contains the list of the Bearer Services and the values for the remaining attributes in the minimal set.
+
+Table 2
+
+| Bearer Service Number                                                                                            | Bearer Service Name                 | Access Structure | Access Rate | Information Transfer Capability | QOS Attribute | Notes |
+|------------------------------------------------------------------------------------------------------------------|-------------------------------------|------------------|-------------|---------------------------------|---------------|-------|
+| 20                                                                                                               | Asynchronous General Bearer Service | Asynch           | note 1      | 3.1 kHz , UDI, RDI              | NT / T        |       |
+| 30                                                                                                               | Synchronous General Bearer Service  | Synch            | note 1      | 3.1 kHz , UDI, RDI              | T             |       |
+| Note 1: This General Bearer is independent of any nominal rate. It is elaborated in more detail in subclause 3.1 |                                     |                  |             |                                 |               |       |
+
+## 3.1 General bearer service user data characteristics
+
+The tables below describe the characteristics of the General Bearer Services. The indicated fixed network user rates are possible, but support of General Bearer Service does not imply support of all rates.
+
+### 3.1.1 BS 20 (asynchronous services)
+
+#### 3.1.1.1 BS 20 T (transparent asynchronous services)
+
+##### 3.1.1.1.1 BS 20 transparent in regular mode for analogue interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS attributes | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|----------------|-----------|---------------|-----------------|-------|
+| 0.3 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 1.2 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 2.4 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 4.8 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 9.6 kbit/s              | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 14.4 kbit/s             | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 19.2 kbit/s             | Asynch           | 3,1 kHz                         | -               | T              | -         | -             | Supported       |       |
+| 28.8 kbit/s             | Asynch           | 3,1 kHz                         | -               | T              | Supported | Supported     | Supported       |       |
+
+##### 3.1.1.1.2 BS 20 transparent in regular mode for digital interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-------|---------------|-----------------|-------|
+| 0.3 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 1.2 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 2.4 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 4.8 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 9.6 kbit/s              | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 14.4 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 19.2 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 28.8 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+| 38.4 kbit/s             | Asynch           | UDI                             | V.110           | T             | -     | -             | Supported       |       |
+
+#### 3.1.1.2 BS 20 NT (non-transparent asynchronous services)
+
+##### 3.1.1.2.1 BS 20 non-transparent in regular mode for analogue interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS attributes | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Note   |
+|-------------------------|------------------|---------------------------------|-----------------|----------------|-----------|---------------|-----------------|--------|
+| 0.3 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 1.2 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 2.4 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 4.8 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 2 |
+| 9.6 kbit/s              | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+| 14.4 kbit/s             | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+| 19.2 kbit/s             | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+| 28.8 kbit/s             | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       |        |
+|                         |                  |                                 |                 |                |           |               |                 |        |
+|                         | Asynch           | 3,1 kHz                         | -               | NT             | Supported | Supported     | Supported       | Note 1 |
+
+NOTE 1: This is used with high speed modems such as V.90 (56kbit/s). Modem type = 'Autobauding Type 1' is selected. FNUR has no meaning in this case.
+
+NOTE 2: In case of UTRAN and in GERAN Iu mode the FNURs 300, 1200, 2400 and 4800 bit/s towards the fixed network can be provided only with modem type = 'Autobauding Type 1' is selected.
+
+##### 3.1.1.2.2 BS 20 non-transparent in regular mode for digital interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes  |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|--------|
+| 0.3 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 1.2 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 2.4 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 4.8 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 9.6 kbit/s              | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 14.4 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 19.2 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 28.8 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+| 38.4 kbit/s             | Asynch           | UDI                             | V.110           | NT            | Supported | Supported     | Supported       |        |
+
+NOTE 1: In case of UTRAN and in GERAN Iu mode the user rates 300, 1200, 2400 and 4800 bit/s towards the fixed network can be provided only for mobile terminated calls.
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes  |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|--------|
+| 1.2 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 2 |
+| 2.4 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 2 |
+| 4.8 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 2 |
+| 9.6 kbit/s              | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 14.4 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 19.2 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 28.8 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       | Note 1 |
+| 38.4 kbit/s             | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 48 kbit/s               | Asynch           | UDI / RDI                       | V.120           | NT            | Supported | Supported     | Supported       |        |
+| 56 kbit/s               | Asynch           | UDI                             | V.120           | NT            |           |               |                 |        |
+
+NOTE 1: Requires a new code point in V.120 specification to be defined.
+
+NOTE 2: In case of UTRAN and in GERAN Iu mode the user rates 1200, 2400 and 4800 bit/s toward the fixed network can be provided only for mobile terminated calls.
+
+##### 3.1.1.2.3 BS 20 non-transparent for PIAFS
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|-------|
+| 32 kbit/s               | Asynch           | UDI                             | PIAFS           | NT            | Supported | -             | -               |       |
+| 64 kbit/s               | Asynch           | UDI                             | PIAFS           | NT            | Supported | -             | -               |       |
+
+##### 3.1.1.2.4 BS 20 non-transparent for Frame Tunnelling Mode
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation    | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|--------------------|---------------|-----------|---------------|-----------------|-------|
+| 56kbit/s                | Asynch           | RDI                             | X.31 flag stuffing | NT            | Supported | Supported     | Supported       |       |
+| 64 kbit/s               | Asynch           | UDI                             | X.31 flag stuffing | NT            | Supported | Supported     | Supported       |       |
+
+### 3.1.2 BS 30 (synchronous services)
+
+#### 3.1.2.1 BS 30 T (transparent synchronous services)
+
+##### 3.1.2.1.1 BS 30 transparent in regular mode for analogue interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS attributes | UTRAN     | GERAN Iu mode | GERAN A/Gb | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|----------------|-----------|---------------|------------|-------|
+| 1.2 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 2.4 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 4.8 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 9.6 kbit/s              | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 14.4 kbit/s             | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 19.2 kbit/s             | Synch            | 3,1 kHz                         | -               | T              | -         | -             | Supported  |       |
+| 28.8 kbit/s             | Synch            | 3,1 kHz                         | -               | T              | Supported | Supported     | Supported  |       |
+
+##### 3.1.2.1.2 BS 30 transparent in regular mode for digital interworking
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|-------|
+| 1.2 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 2.4 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 4.8 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 9.6 kbit/s              | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 14.4 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 19.2 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 28.8 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 38.4 kbit/s             | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 48 kbit/s               | Synch            | UDI                             | V.110           | T             | -         | -             | Supported       |       |
+| 56 kbit/s               | Synch            | UDI                             | V.110           | T             | Supported | Supported     | Supported       |       |
+| 56 kbit/s               | Synch            | RDI                             | -               | T             | Supported | Supported     | Supported       |       |
+| 64 kbit/s               | Synch            | UDI                             | -               | T             | Supported | Supported     | Supported       |       |
+
+##### 3.1.2.1.3 BS 30 transparent for Multimedia
+
+| Fixed Network User Rate | Access Structure | Information Transfer Capability | Rate Adaptation | QoS Attribute | UTRAN     | GERAN Iu mode | GERAN A/Gb mode | Notes  |
+|-------------------------|------------------|---------------------------------|-----------------|---------------|-----------|---------------|-----------------|--------|
+| 28.8 kbit/s             | Synch            | 3.1kHz Audio                    | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+| 32.0 kbit/s             | Synch            | UDI                             | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+| 33.6 kbit/s             | Synch            | 3.1kHz Audio                    | H.223 & H.245   | T             | Supported | Supported     | Supported       | Note 1 |
+| 56 kbit/s               | Synch            | RDI                             | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+| 64 kbit/s               | Synch            | UDI                             | H.223 & H.245   | T             | Supported | Supported     | Supported       |        |
+
+NOTE 1: 33.6kbit/s FNURs is applicable only for UTRAN.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                                                                 |        |        |                    |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|-----------------------------------------------------------------------------------------------------------------|--------|--------|--------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                                                                 | Old    | New    | WI                 |
+| Jun 1999       |           |           | 02.02  |     |     |       |     | Transferred to 3GPP SA1                                                                                         | 8.0.0  | 3.0.0  |                    |
+| SP-05          | SP-99479  | S1-99608  | 22.002 | 001 |     | R99   | D   | Editorial changes for alignment                                                                                 | 3.0.0  | 3.1.0  |                    |
+| SP-05          | SP-99446  | S1-99659  | 22.002 | 002 |     | R99   | B   | Bearer Services                                                                                                 | 3.0.0  | 3.1.0  |                    |
+| SP-06          | SP-99520  | S1-991008 | 22.002 | 003 |     | R99   | B   | Addition of new general bearer service user data characteristics for 33.6kbit/s modem, FTM and multimedia calls | 3.1.0  | 3.2.0  |                    |
+| SP-06          | SP-99520  | S1-991075 | 22.002 | 004 |     | R99   | C   | 22.002 made only applicable to CS Domain.                                                                       | 3.1.0  | 3.2.0  |                    |
+| SP-07          | SP-000054 | S1-000132 | 22.002 | 005 |     | R99   | F   | Corrections on 3,1 kHz Audio support                                                                            | 3.2.0  | 3.3.0  |                    |
+| SP-08          | SP-000192 | S1-000274 | 22.002 | 006 |     | R99   | F   | Lower User Rates in UMTS for Circuit Switched Data Services                                                     | 3.3.0  | 3.4.0  |                    |
+| SP-09          | SP-000371 | S1-000561 | 22.002 | 007 |     | R99   | F   | 32 kbit/s UDI/RDI multimedia in GSM                                                                             | 3.4.0  | 3.5.0  |                    |
+| SP-09          | SP-000390 | S1-000595 | 22.002 | 008 |     | R4    | C   | Deletion of bearer service BS 30 NT                                                                             | 3.4.0  | 4.0.0  |                    |
+| SP-11          | SP-010039 | S1-010253 | 22.002 | 010 |     | Rel-4 | C   | CR to 22.002 clarification on Circuit Switched Bearer Services in UMTS                                          | 4.0.0  | 4.1.0  | CS Bearers in UMTs |
+| SP-11          | SP-010040 | S1-010254 | 22.002 | 011 |     | Rel-4 | D   | Restructuring of 22.002                                                                                         | 4.0.0  | 4.1.0  | CS Bearers in UMTs |
+| SP-11          | SP-010040 | S1-010266 | 22.002 | 012 |     | Rel-4 | D   | Restructuring of tables in section 3.1                                                                          | 4.0.0  | 4.1.0  | CS Bearers in UMTs |
+| SP-12          | SP-010257 | S1-010357 | 22.002 | 013 |     | Rel-4 | F   | Corrections to erroneous implementation of CRs SP-010039 and SP-010040 to 22.002.                               | 4.1.0  | 4.2.0  | TEI4               |
+| SP-16          | SP-020244 | S1-021076 | 22.002 | 014 |     | Rel-5 | F   | CR to 22.002 Correction of terminology and references                                                           | 4.2.0  | 5.0.0  | TEI5               |
+| SP-26          | SP-040744 | S1-040997 | 22.002 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                                                                     | 5.0.0  | 6.0.0  |                    |
+| SP-36          |           |           | 22.002 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                                                                     | 6.0.0  | 7.0.0  |                    |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                                                                     | 7.0.0  | 8.0.0  |                    |
+| 2009-12        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-9 version (MCC)                                                                                   | 8.0.0  | 9.0.0  |                    |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                                                                  | 9.0.0  | 10.0.0 |                    |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                                                                  | 10.0.0 | 11.0.0 |                    |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                                                                  | 11.0.0 | 12.0.0 |                    |
+| 2015-12        |           |           |        |     |     |       |     | Update to Rel-13 version (MCC)                                                                                  | 12.0.0 | 13.0.0 |                    |
+| 2017-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-14 by MCC                                                                                        | 13.0.0 | 14.0.0 |                    |
+| 2018-06        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-15 by MCC                                                                                        | 14.0.0 | 15.0.0 |                    |
+| 2020-07        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-16 by MCC                                                                                        | 15.0.0 | 16.0.0 |                    |
+| 2022-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-17 by MCC                                                                                        | 16.0.0 | 17.0.0 |                    |
+| 2024-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload)                                                       | 17.0.0 | 18.0.1 |                    |

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

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

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

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

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

@@ -0,0 +1,206 @@
+
+
+# 3GPP TS 22.016 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; International Mobile station Equipment Identities (IMEI) (Releas2418)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like graphic above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## --- **Keywords**
+
+GSM, UMTS, LTE, addressing
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2012 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                   |          |
+|---------------------------------------------------|----------|
+| Foreword .....                                    | 4        |
+| 1 Scope.....                                      | 5        |
+| 1.1 References .....                              | 5        |
+| 1.2 Definitions and abbreviations.....            | 5        |
+| 2 General.....                                    | 5        |
+| 3 Composition of IMEI .....                       | 6        |
+| 4 Use of the equipment identity register .....    | 6        |
+| 5 Procedure .....                                 | 6        |
+| 6 Use of IMEI in case of emergency calls .....    | 6        |
+| 7 MS Software Version Number (SVN).....           | 7        |
+| <b>Annex A (informative): Change history.....</b> | <b>8</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 defines the principal purpose and use of International Mobile station Equipment Identities (IMEI).
+
+3GPP TS 23.003 describes the technical manner of numbering, addressing and identification.
+
+## 1.1 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [3] ISO/IEC 7812 (1989): "Identification cards - Numbering system and registration procedure for issuer identifiers".
+
+## 1.2 Definitions and abbreviations
+
+In addition to the following, abbreviations used in the present document are listed in 3GPP TS 21.905.
+
+**International Mobile Station Equipment Identity (IMEI):** An "International Mobile Station Equipment Identity" is a unique number which shall be allocated to each individual mobile station equipment in the PLMN and shall be unconditionally implemented by the MS manufacturer.
+
+# --- 2 General
+
+An MS can only be operated if a valid "International Mobile Subscriber Identity" (IMSI) is present. An IMSI is primarily intended for obtaining information on the use of the PLMN by subscribers for individual charging purposes.
+
+Besides the IMSI, the implementation of IMEI is found necessary in order to obtain knowledge about the presence of specific mobile station equipment in the network, disregarding whatever subscribers are making use of these equipment.
+
+The main objective is to be able to take measures against the use of stolen equipment or against equipment of which the use in the PLMN can not or no longer be tolerated for technical reasons.
+
+The IMEI is incorporated in an UE module which is contained within the UE. The IMEI shall be unique and shall not be changed after the ME's final production process. It shall resist tampering, i.e. manipulation and change, by any means (e.g. physical, electrical and software).
+
+NOTE: This requirement is valid for new GSM MEs type approved after 1st June 2002. However, this requirement is applicable to all 3GPP system compatible UEs from start of production.
+
+The manufacturer implementing the IMEI module in the ME is responsible for ensuring that each IMEI within the allocated range is unique to the ME in which it resides, and is also responsible for keeping detailed records of produced and delivered MEs.
+
+# --- 3 Composition of IMEI
+
+The composition of the IMEI shall be such that each individual mobile station equipment can be separately identified.
+
+Information is contained in the IMEI by which the PLMN, after requesting it, can immediately decide whether or not to accept calls made by means of this equipment.
+
+Secondly, the IMEI shall directly or indirectly contain all information which is necessary for the network operator to make relations through its administrative system to trace the equipment to its origin of production. 3GPP TS 23.003 [2] describes the structure of the IMEI in detail.
+
+The IMEI is complemented by a check digit. The check digit is not part of the digits transmitted at IMEI check occasions, as described below. The Check Digit shall avoid manual transmission errors, e.g. when customers register stolen MEs at the operators' customer care desk.
+
+NOTE: The Check Digit is not applied to the Software Version Number.
+
+# --- 4 Use of the equipment identity register
+
+A network operator can make administrative use of the IMEI in the following manner:
+
+Three registers are defined, known as "allowed lists", "tracked lists" and "prohibited lists". The use of such lists is at the operators' discretion.
+
+The **allowed list** is composed of all **number series** of equipment identities that are permitted for use.
+
+The **prohibited list** contains all equipment identities that belong to equipment that need to be barred.
+
+Besides the prohibited and allowed list, administrations have the possibility to use a **tracked list**. Equipment on the tracked list are not barred (unless on the prohibited list or not on the allowed list), but are tracked by the network (for evaluation or other purposes).
+
+# --- 5 Procedure
+
+It shall be possible to perform the IMEI check at any access attempt, except IMSI detach, and during an established call at any time when a dedicated radio resource is available, in accordance with the security policy of the PLMN operator. It shall also be possible to perform the IMEI check when a UE is IMS registered.
+
+The network shall terminate any access attempt or ongoing call when receiving indication from the EIR that the UE is on the prohibited list or the UE is not on the allowed list). An indication of "illegal ME" shall in these cases be given to the user. Furthermore this is equivalent to an authentication failure hence any call or IMS session establishment or any location updating is forbidden for the MS, it cannot answer to paging, it is just allowed to perform Emergency Calls. Emergency calls must never be terminated as a result of the IMEI check procedure.
+
+## --- 6 Use of IMEI in case of emergency calls
+
+Emergency calls can in some PLMNs be made without having to send the subscriber identity (IMSI) to the network. In this case the misuse of MS equipments after placing invalid emergency calls can be restrained by using the equipment identity.
+
+The network request for the equipment identity is sent to the MS after the emergency call has been set-up. The procedure is the same as for normal call set-up.
+
+# --- 7 MS Software Version Number (SVN)
+
+A Software Version Number (SVN) field shall be provided. This allows the ME manufacturer to identify different software versions of a given mobile.
+
+The SVN is a separate field from the IMEI, although it is associated with the IMEI. When the network requests the IMEI from the MS, it may also request that the SVN is also sent towards the network.
+
+The allowed list shall use the IMEI, The prohibited and tracked lists may also use the SVN.
+
+## Annex A (informative): Change history
+
+| Change history |           |           |            |      |      |       |     |                                                                                               |        |        |                   |
+|----------------|-----------|-----------|------------|------|------|-------|-----|-----------------------------------------------------------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec       | CR   | R ev | Rel   | Cat | Subject/Comment                                                                               | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02 .16 |      |      |       |     | Transferred to 3GPP SA1                                                                       | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.016     |      |      |       |     | Transferred to 3GPP SA1                                                                       |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99611  | 22.016     | 001  |      | R99   | D   | Editorial changes for alignment                                                               | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-06          | SP-99601  | P-99-777  | 22.016     | 002  |      | R99   | F   | Modification of section 2 to enhance IMEI security                                            | 3.0.1  | 3.1.0  |                   |
+| SP-08          | SP-000195 | S1-000441 | 22.016     | 003  | 1    | R99   | F   | IMEI coding                                                                                   | 3.1.0  | 3.2.0  |                   |
+| SP-08          | SP-000194 | S1-000266 | 22.016     | 004  |      | R99   | F   | Modification of section 2 to delete unnecessary information about phases and releases removed | 3.1.0  | 3.2.0  |                   |
+| SP-11          | SP-010065 | S1-010258 | 22.016     |      |      | Rel-4 |     | Transferred to 3GPP Release 4                                                                 | 3.2.0  | 4.0.0  |                   |
+| SP-15          | SP-020045 | S1-020457 | 22.016     | 006  | -    | Rel-4 | F   | Editorial CR to correct terms and                                                             | 4.0.0  | 4.1.0  | CORREC            |
+| SP-16          | SP-020237 | S1-021149 | 22.016     | 008  |      | Rel-4 | A   | Type approval code                                                                            | 4.0.0  | 4.1.0  | TEI               |
+| SP-16          | SP-020267 | S1-021043 | 22.016     |      |      | Rel-5 |     | Updated from Rel-4 to Rel5                                                                    | 4.1.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.016     |      |      | Rel-6 |     | Updated from Rel-5 to Rel-6                                                                   | 5.0.0  | 6.0.0  |                   |
+| SP-34          | SP-060768 | S1-061444 | 22.016     | 0009 | -    | Rel-7 | F   | IMEI Check and IMS                                                                            | 6.0.0  | 7.0.0  | TEI7              |
+|                |           |           | 22.016     |      |      | Rel-7 |     | Editorial correction to version identity on front cover                                       | 7.0.0  | 7.0.1  |                   |
+| SP-42          | SP-080891 | S1-083445 | 22.016     | 0010 | 1    | Rel-7 | F   | Correction of SVN sending when network requests IMEI                                          | 7.0.1  | 7.1.0  | TEI7              |
+|                |           |           |            |      |      |       |     | Rel-8 version created                                                                         | 7.1.0  | 8.0.0  |                   |
+| SP-45          | SP-090470 | S1-093278 | 22.016     | 0013 | 2    | Rel-9 | A   | Clarify that each IMEI shall be unique                                                        | 8.0.0  | 9.0.0  | TEI9              |
+|                |           |           |            |      |      |       |     | 2010-04: correct history table                                                                | 9.0.0  | 9.0.1  |                   |
+| 2011-03        | -         | -         | -          | -    | -    | -     | -   | Update to Rel-10 version (MCC)                                                                | 9.0.1  | 10.0.0 |                   |
+| 2012-09        |           |           |            |      |      |       |     | Update to Rel-11 version (MCC)                                                                | 10.0.0 | 11.0.0 |                   |
+| 2014-10        | -         | -         | -          | -    | -    | -     | -   | Update to Rel-12 version (MCC)                                                                | 11.0.0 | 12.0.0 |                   |
+| 2015-12        |           |           |            |      |      |       |     | Update to Rel-13 version (MCC)                                                                | 12.0.0 | 13.0.0 |                   |
+| 2017-03        | -         | -         | -          | -    | -    | -     | -   | Updated to Rel-14 by MCC                                                                      | 13.0.0 | 14.0.0 |                   |
+| 2018-06        | -         | -         | -          | -    | -    | -     | -   | Updated to Rel-15 by MCC                                                                      | 14.0.0 | 15.0.0 |                   |
+| 2020-07        | -         | -         | -          | -    | -    | -     | -   | Updated to Rel-16 by MCC                                                                      | 15.0.0 | 16.0.0 |                   |
+
+| Change history |         |           |      |     |     |                                                                    |             |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                    | New version |
+| 2021-12        | SP-94   | SP-211500 | 0014 |     | D   | Use of inclusive language to align with SA2 and CT4                | 17.0.0      |
+| 2022-05        | -       | -         | -    | -   | -   | Correction of cover page: v.17.0.0 was showing "16.1.0" and Rel-16 | 17.0.1      |
+| 2024-03        | SA#103  | -         | -    | -   | -   | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload)          | 18.0.1      |

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

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

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

@@ -0,0 +1,446 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Description of Charge Advice Information (CAI) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like signal icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+LTE, GSM, UMTS, charging
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                         |           |
+|---------------------------------------------------------|-----------|
+| Foreword .....                                          | 4         |
+| 1 Scope.....                                            | 5         |
+| 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        |
+| <b>Annex A (informative): Change history.....</b>       | <b>13</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 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 LPLMN 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 \quad * \quad \{ \quad e4 \quad + \quad e1 * \text{INT}(\text{CDUR}/(e7,e2)) \quad + \quad e5 * \text{INT}(\text{SEG}/e6) \} \\ &= \text{scaling} \quad * \quad \{ \quad \text{constant} \quad + \quad \text{time related} \quad + \quad \text{data related} \quad \} \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 * 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.1.
+
+## 4.2 Handling of call meters
+
+Two meters are defined.
+
+### 4.2.1 The Current Call Meter (CCM)
+
+This is required to accumulate the charging units generated by the current call and is capable of advising:
+
+- a) The current charge due for the call(s) in progress.
+- b) At the end of the call(s), the charge equivalent to the current call record in an itemized bill.
+
+The CCM shall hold the value of the last call AOC, until the initiation of an outgoing call or acceptance of an incoming call, at which point it shall be reset to zero, regardless of the success of the initiation/acceptance attempt. This information is deleted when the MS is switched off or the SIM/USIM is removed.
+
+The CCM is essential for the correct functioning of AOC, see subclauses 4.1 and 4.3, and is a component of the Mobile Equipment. The charging computation shall cease immediately on termination of a call, as indicated by the user or the network, or on failure of the call.
+
+For multiple calls, CCM will advise the total charge of all the calls made and/or received during occupation of a traffic channel.
+
+### 4.2.2 The Accumulated Call Meter (ACM)
+
+The Accumulated Call Meter accumulates the total units for both the current call and all preceding calls. The ACM is a function contained within the SIM/USIM. It is optional, but is essential for certain applications.
+
+For security reasons, the SIM/USIM only allows the value of the ACM to be incremented, not decremented. Resetting of the ACM shall only be possible after presentation of PIN2.
+
+If the ACMmax (see subclause 4.2.3) is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user (i.e. those calls that have a non-zero AoC associated with them), shall
+
+be terminated by the ME once the chargeable interval determined by the CAI has elapsed. The ACM will be updated with the new value, which may be greater than the ACMmax value. The reason why the call has terminated shall be given to the user by means of an appropriate indication given to the user.
+
+If the ACMmax is valid and the ACM is equal to or greater than the value of ACMmax, then no outgoing calls can be placed, except Emergency calls.
+
+If the ACMmax is valid and the ACM is equal to or greater than the value of ACMmax, and an incoming call is received and subsequently a non-zero CAI is received for that call, then the call shall be terminated by the ME with an appropriate indication given to the user.
+
+### 4.2.3 The ACM Maximum Value (ACMmax)
+
+This is the value that the subscriber can set, to limit the units which may be consumed by a user. The MS may provide for the means to set or update the ACMmax, using PIN2. The ACMmax is not valid if set to zero.
+
+NOTE: The network operator should make clear to the subscriber that the ACMmax must not be set to a value close to the maximum value possible in the encoding of ACMmax. The network operators should provide guidance as to what the maximum value for the ACMmax may be.
+
+### 4.2.4 The Price per Unit and Currency Table (PUCT)
+
+This is intended to enable the MS to calculate the cost of a call in a currency chosen by the subscriber. The subscriber may set the value of the home unit in the PUCT differently to the value of the unit published by the HPLMN in order to cover extra cost. An indication of the currency in use is part of the PUCT.
+
+## 4.3 Special processing
+
+- a) If e7 is zero or not sent in the CAI message, e2 applies and e7 is not used.
+- b) If e2 or e6 are set to zero, the relevant INT function shall handle the singularity by returning zero, thus disabling the relevant unitization process (call or data part).
+- c) On receipt of a subsequent e4, the MS shall transfer the value of  $e4 * e3$  to the CCM, by addition of  $e4 * e3$  to the current contents of the CCM.
+- d) When CDUR reaches e2 (or e7 as appropriate),  $e1 * e3$  is added to the CCM and CDUR is reset to zero, except when conditions given in (a) and (b) above, apply.
+- e) On receipt of new e1, e2 or e7 during a call, these new values are held in abeyance, until the value of the associated MS timer CDUR has reached the current e2 or e7 value as appropriate, and the processing as described in special processing item d) above has been completed. The new e1, e2 and/or e7 are then brought into operation. e7 is applied followed by e2, conditions a) and b) above determining the detailed processing.
+
+Any update of e1, e2 and/or e7 during the time before CDUR is reset, shall supersede any values already held in abeyance.
+
+If CDUR is not actively timing (i.e. due to e2 being zero, e7 being zero or the processing of e7 has been completed), then a new value of e2 and/or e7 is applied immediately as per a normal new call.
+
+- f) When SEG reaches e6,  $e5 * e3$  is added to the CCM and SEG is reset to zero, except where e6 is zero, where condition (b) above applies.
+- g) On receipt of a new e5 or e6 during the call, these new elements are held in abeyance, until the value of the associated MS counter SEG has reached the old e6 value, and the processing as described in special processing item (f) above has been completed. The resulting zero SEG and new e5 and e6 are then brought into operation.
+
+Any update of e5 or e6 during the time before SEG is reset, shall supersede any values already held in abeyance.
+
+If the old value of e6 was zero, then the new value of e5 and e6 is applied immediately.
+
+- h) The ACM shall be incremented when the CCM is incremented or once every 5 seconds, which ever is the longer period. Although the CCM is maintained with an accuracy of three places of decimals, the ACM shall be incremented and stored as integer units (i.e. no decimal places). The ACM shall be incremented by the difference
+
+between the present value of the CCM (rounded up) and the value of the CCM (rounded up) at the previous ACM incrementation.
+
+- i) A zero value for any of the CAI elements is valid and dealt with as described above.
+- j) Free calls should be implemented by sending a CAI message with appropriate zero elements.
+- k) On receipt of any CAI message from the network, provided the MS supports AoC, the MS it shall confirm receipt of the CAI message. An MS not supporting AoC as defined in TS 22.24 and TS 22.086 [2] shall not confirm receipt of the message.
+- l) During multiple calls the network shall send, and the MS shall receive, CAI elements for each call separately. The CCM shall record the sum of all the charges for the services being used currently.
+- m) If the MS detects a radio link failure the MS shall suspend CDUR. If a subsequent call reestablishment is successful, CDUR shall be resumed when call reestablishment is complete.
+
+## 4.4 Interactions with SCUDIF supplementary service
+
+When the MS requires a bearer change, e.g. from Audio to Video or vice versa, the SCUDIF Mode modify procedure is performed as described in TS 23.172 [3]. Depending on the operator's policy the success of the procedure may trigger a Facility message to convey new values for the CAI parameters. On receipt of new CAI values triggered by a service change based on the SCUDIF supplementary service, the MS shall reset CDUR and continue incrementing the CCM using the new CAI parameters as stated in subclause 4.3 of this specification. The MS shall add initial units to the CCM and measure units on a time basis using the new values.
+
+# --- 5 Functional operation in PLMN
+
+For applicable calls, the PLMN shall send the CAI message to the MS immediately the called party answers. The PLMN derives the values of the elements to be sent in the CAI message in the following way:
+
+## 5.1 Outgoing calls
+
+The local PLMN, be it the HPLMN or the VPLMN, always sets values of e1, e2, e4, e5, e6 and e7 in terms of units of the LPLMN and according to its own tariff structure.
+
+Element e3 is set according to variables of the LPLMN and the relevant HPLMN. If the LPLMN is the HPLMN (i.e. the MS is in its Home PLMN) then e3 shall be simplified to unity.
+
+There shall be only one value of e3 for a given combination of HPLMN and VPLMN. This value may be simply loaded into the VMSC of the LPLMN using the Man Machine Interface commands, since it is not expected to vary frequently and is independent of the type of outgoing call.
+
+## 5.2 Incoming calls
+
+For incoming calls the HPLMN determines the tariff and this tariff is dependent on the LPLMN of the MS. Therefore all the CAI elements are set according to the HPLMN tariff as a function of LPLMN.
+
+In the case of the LPLMN being the HPLMN these elements may be set to zero assuming the HPLMN does not charge for incoming calls.
+
+For roaming (i.e. where the LPLMN is not the HPLMN), in order to charge for incoming calls, the VPLMN must be provided with specific CAI values as defined by each HPLMN (e1i through e7i inclusive). This may be achieved by loading the offered HPLMN derived values via the VPLMN MMI.
+
+Each VPLMN will require a set of 7 values per HPLMN with which the VPLMN has a roaming agreement i.e.:
+
+e1i(h), e2i(h), e3(h), e4i(h), e5i(h), e6i(h) and e7i(h).
+
+These are derived by:
+
+$$e1i(h)=e1H(h)/e3(h);$$
+
+$$e4i(h)=e4H(h)/e3(h);$$
+
+$$e5i(h)=e5H(h)/e3(h);$$
+
+where :
+
+- h represents the 'h'th HPLMN with a roaming relationship with the VPLMN;
+- i indicates the CAI element as determined by the 'h'th HPLMN, for the charging of incoming calls;  
+the same value of e3 is used for both incoming and outgoing calls;  
+exH(h) represents the value of the element x, given in terms of HPLMN units;  
+exi(h) represents the value of the element x as handled by the VPLMN.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |           |     |     |       |     |                                                              |        |        |                   |
+|----------------|-----------|-----------|-----------|-----|-----|-------|-----|--------------------------------------------------------------|--------|--------|-------------------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec      | CR  | Rev | Rel   | Cat | Subject/Comment                                              | Old    | New    | WI                |
+| Jun 1999       |           |           | GSM 02.24 |     |     |       |     | Transferred to 3GPP SA1                                      | 7.0.0  |        |                   |
+| SA#04          |           |           | 22.024    |     |     |       |     | Transferred to 3GPP SA1                                      |        | 3.0.0  |                   |
+| SP-05          | SP-99479  | S1-99613  | 22.024    | 001 |     | R99   | D   | Editorial changes for alignment                              | 3.0.0  | 3.0.1  | Editorial changes |
+| SP-11          | SP-010065 | S1-010258 | 22.024    |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                | 3.0.1  | 4.0.0  |                   |
+| SP-16          | SP-020267 | S1-021043 | 22.024    |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                   | 4.0.0  | 5.0.0  |                   |
+| SP-26          | SP-040744 | S1-040997 | 22.024    |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                  | 5.0.0  | 6.0.0  |                   |
+| SP-28          | SP-050211 | S1-050397 | 22.024    | 003 | -   | Rel-6 | A   | AoC for SCUDIF                                               | 6.0.0  | 6.1.0  | TEI               |
+| SP-36          |           |           | 22.024    |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                  | 6.1.0  | 7.0.0  |                   |
+| SP-42          | -         | -         |           |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                  | 7.0.0  | 8.0.0  |                   |
+| SP-46          | -         | -         | -         | -   | -   | -     |     | Updated to Rel-9 by MCC                                      | 7.0.0  | 9.0.0  |                   |
+| 2011-03        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-10 version (MCC)                               | 9.1.0  | 10.0.0 |                   |
+| 2012-09        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-11 version (MCC)                               | 10.0.0 | 11.0.0 |                   |
+| 2014-10        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-12 version (MCC)                               | 11.0.0 | 12.0.0 |                   |
+| 2015-12        | -         | -         | -         | -   | -   | -     | -   | Update to Rel-13 version (MCC)                               | 12.0.0 | 13.0.0 |                   |
+| 2017-03        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-14 by MCC                                     | 13.0.0 | 14.0.0 |                   |
+| 2018-06        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-15 by MCC                                     | 14.0.0 | 15.0.0 |                   |
+| 2020-07        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-16 by MCC                                     | 15.0.0 | 16.0.0 |                   |
+| 2022-03        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-17 by MCC                                     | 16.0.0 | 17.0.0 |                   |
+| 2024-03        | -         | -         | -         | -   | -   | -     | -   | Updated to Rel-18 by MCC<br>(and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 |                   |

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

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

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

@@ -0,0 +1,375 @@
+
+
+# 3GPP TS 22.031 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Fraud Information Gathering System (FIGS); Service description; Stage 1 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+UMTS, GSM, Security, Stage 1
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                                                     |           |
+|-------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                      | 4         |
+| 1 Scope.....                                                                        | 5         |
+| 2 Normative references .....                                                        | 5         |
+| 3 Definitions and abbreviations .....                                               | 5         |
+| 3.1 Definitions.....                                                                | 5         |
+| 3.2 Abbreviations .....                                                             | 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> |
+| <b>Annex C (informative): Change history.....</b>                                   | <b>12</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+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 fraudulency.
+
+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 fraudulency. If call end is sent instead, the duration can be calculated using the call start and end times.
+
+The **Call Reference** is used to reference a particular call.
+
+The **MO/MT indicator** is required because call charging is different for MO and MT calls.
+
+The **Visited MSC address** gives the PLMN on which the call was made.
+
+The **Type of SS event** record is sent if the "call" start is actually the invocation of a supplementary service, e.g. ECT. The Type of SS event is required as this can help to indicate if the mobile is being fraudulently used or not.
+
+The **Type of Basic Service** indicates whether a teleservice or bearer service is being used and which sort of teleservice or bearer service is being used and is sent if the event is a call and not a supplementary service. The Type of Basic Service is required as this can help to indicate if the mobile station is being fraudulently used or not.
+
+## --- Annex B (normative): Message flow in FIGS monitoring, normal procedure
+
+![Sequence diagram showing message flow between HPLMN and VPLMN for FIGS monitoring.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+```
+sequenceDiagram
+    participant HPLMN
+    participant VPLMN
+    Note right of VPLMN: Request for FIGS monitoring
+    VPLMN->>HPLMN: Positive Acknowledgement
+    Note left of HPLMN: FIGS Data
+    HPLMN->>VPLMN: FIGS Data
+    Note left of VPLMN: Request to stop FIGS monitoring
+    VPLMN->>HPLMN: 
+```
+
+The diagram illustrates the message flow between HPLMN and VPLMN for FIGS monitoring. It consists of five messages exchanged between the two entities. The sequence starts with a 'Request for FIGS monitoring' from VPLMN to HPLMN. This is followed by a 'Positive Acknowledgement' from HPLMN to VPLMN. Then, two 'FIGS Data' messages are sent from HPLMN to VPLMN. Finally, a 'Request to stop FIGS monitoring' is sent from VPLMN to HPLMN.
+
+Sequence diagram showing message flow between HPLMN and VPLMN for FIGS monitoring.
+
+Figure B.1: Message flow in FIGS monitoring, normal procedure
+
+# Annex C (informative): Change history
+
+| Change history GSM 02.31      |        |          |      |     |                                                                                                                                            |                  |                  |
+|-------------------------------|--------|----------|------|-----|--------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|
+| Date                          | TSG #  | TSG Doc. | CR   | Rev | Subject/Comment                                                                                                                            | Old              | New              |
+|                               |        |          |      |     | 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            |
+| Change history 3GPP TS 42.031 |        |          |      |     |                                                                                                                                            |                  |                  |
+| Date                          | TSG #  | TSG Doc. | CR   | Rev | Subject/Comment                                                                                                                            | Old              | New              |
+| 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            |
+| Change history 3GPP TS 22.031 |        |          |      |     |                                                                                                                                            |                  |                  |
+| Date                          | TSG #  | TSG Doc. | CR   | Rev | Subject/Comment                                                                                                                            | Old              | New              |
+| 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  | -        | -    | -   | Upgrade to Release 6                                                                                                                       | 5.0.0            | 6.0.0            |
+| 06-2007                       | SA#36  | -        | -    | -   | Upgrade to Release 7                                                                                                                       | 6.0.0            | 7.0.0            |
+| 12-2008                       | SA#42  | -        | -    | -   | Upgrade to Release 8                                                                                                                       | 7.0.0            | 8.0.0            |
+| 12-2009                       | SA#46  | -        | -    | -   | Upgrade to Release 9                                                                                                                       | 8.0.0            | 9.0.0            |
+| 2011-03                       | -      | -        | -    | -   | Update to Rel-10 version (MCC)                                                                                                             | 9.0.0            | 10.0.0           |
+| 2012-09                       | -      | -        | -    | -   | Update to Rel-11 version (MCC)                                                                                                             | 10.0.0           | 11.0.0           |
+| 2014-09                       | -      | -        | -    | -   | Update to Rel-12 version (MCC)                                                                                                             | 11.0.0           | 12.0.0           |
+| 2015-12                       | -      | -        | -    | -   | Update to Rel-13 version (MCC)                                                                                                             | 12.0.0           | 13.0.0           |
+| 2017-03                       | -      | -        | -    | -   | Update to Rel-14 version (MCC)                                                                                                             | 13.0.0           | 14.0.0           |
+| 2018-06                       | -      | -        | -    | -   | Update to Rel-15 version (MCC)                                                                                                             | 14.0.0           | 15.0.0           |
+| 2020-07                       | -      | -        | -    | -   | Update to Rel-16 version (MCC)                                                                                                             | 15.0.0           | 16.0.0           |
+| 2022-03                       | -      | -        | -    | -   | Update to Rel-17 version (MCC)                                                                                                             | 16.0.0           | 17.0.0           |
+| 2024-03                       | -      | -        | -    | -   | Update to Rel-18 version (MCC)                                                                                                             | 17.0.0           | 18.0.0           |

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

@@ -0,0 +1,224 @@
+
+
+# 3GPP TS 22.032 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Immediate Service Termination (IST); Service description; Stage 1 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+GSM, UMTS, IST, Security, stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                       |          |
+|-------------------------------------------------------|----------|
+| Foreword .....                                        | 4        |
+| 1 Scope.....                                          | 5        |
+| 2 Normative references .....                          | 5        |
+| 3 Definitions and abbreviations .....                 | 5        |
+| 3.1 Definitions.....                                  | 5        |
+| 3.2 Abbreviations .....                               | 5        |
+| 4 Immediate Service Termination (IST).....            | 6        |
+| 4.1 Description .....                                 | 6        |
+| 4.2 Applicability.....                                | 6        |
+| 4.3 Normal procedure.....                             | 6        |
+| 4.4 Exception procedures .....                        | 6        |
+| 5 Security requirements between HPLMN and VPLMN ..... | 6        |
+| <b>Annex A (Informative): Normal procedure .....</b>  | <b>7</b> |
+| <b>Annex B (Informative): Change History.....</b>     | <b>8</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
+
+This Technical Specification specifies the stage 1 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via Fraud Information Gathering System (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
+
+This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
+
+The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
+
+# --- 2 Normative references
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this specification the following definitions apply:
+
+**subscriber activities:** subscriber activities that must be terminated. These can be call related events (e.g. call set-up, call termination) or the invocation of call related and call independent supplementary services (e.g. Call Hold, Call Waiting, Call Transfer, Call Forwarding, Unstructured Supplementary Service Data (USSD)).
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following abbreviations apply:
+
+|      |                                    |
+|------|------------------------------------|
+| IST  | Immediate Service Termination      |
+| FIGS | Fraud Information Gathering System |
+
+# 4 Immediate Service Termination (IST)
+
+## 4.1 Description
+
+It shall be possible for the Home Public Land Mobile Network (HPLMN) to instruct any PLMN to terminate immediately all the activities of a specified HPLMN subscriber.
+
+Immediate Service Termination (IST) is controlled by the HPLMN and can be triggered by the HPLMN only.
+
+A subscriber shall be specified by the International Mobile Subscriber Identity (IMSI).
+
+For subscribers that are marked as subscribed to a CAMEL-based service, IST shall be possible using Customised Application for Mobile network Enhanced Logic (CAMEL).
+
+IST shall also be possible for subscribers who are not marked as subscribed to any CAMEL-based service (see Annex A).
+
+## 4.2 Applicability
+
+This network feature applies to all subscribed Bearer Services and Teleservices of the subscriber, except for emergency calls.
+
+## 4.3 Normal procedure
+
+The HPLMN will normally direct a request for IST for a particular subscriber to the current Visited PLMN (VPLMN) of that subscriber and the PLMN visited by the subscriber immediately prior to visiting the current VPLMN
+
+NOTE: In practice, the IST command will be sent to individual Mobile-services Switching Centres (MSCs), and not to "VPLMNs" as a whole (but such detail is for Stage 2 and not Stage 1). IST will therefore be sent to all MSCs in which the subscriber has (or may have) an active call, as logged by the HPLMN. These MSCs may be confined to the current VPLMN or may include MSC(s) in the PLMN visited by the subscriber immediately prior to visiting the current VPLMN (or PLMNs visited even earlier).
+
+The VPLMN shall confirm receipt of the IST command.
+
+The VPLMN shall then terminate all activities of that subscriber in the VPLMN including ongoing calls and forwarded, deflected and transferred calls. The call records of calls terminated by the operation of IST shall contain a field indicating that the call terminated because of the operation of IST.
+
+The VPLMN shall then confirm to the HPLMN that all subscriber activities in that VPLMN have been terminated.
+
+If the specified subscriber has no activities in the VPLMN then the VPLMN shall inform the HPLMN of this.
+
+## 4.4 Exception procedures
+
+If after sending an IST command to a VPLMN, the HPLMN does not receive a positive acknowledgement from the VPLMN indicating receipt and comprehension of the IST command, the HPLMN should assume that the VPLMN does not support IST.
+
+# 5 Security requirements between HPLMN and VPLMN
+
+It is expected that there will be a need for authentication and confidentiality of the communication made between PLMNs.
+
+These issues are for study under other work items within the SMG10 work programme.
+
+## --- Annex A (Informative): Normal procedure
+
+IST has been defined to work in co-ordination with existing GSM facilities.
+
+- 1) The HPLMN changes the subscriber's entry in the HLR to prevent the resumption of activity in the HPLMN and VPLMN after IST has terminated all subscriber activity.
+- 2) The HPLMN sends a MAP "Cancel Location" command to the VLR to prevent the resumption of activity by the subscriber within the VPLMN without reference to the HPLMN.
+- 3) The HPLMN sends an IST command to the VPLMN, (possibly a specific MAP message).
+- 4) The VPLMN confirms receipt and comprehension of the command.
+- 5) The VPLMN terminates all activities of the subscriber indicated by the command.
+- 6) The VPLMN confirms to the HPLMN that all subscriber activities have been terminated.
+
+## Annex B (Informative): Change History
+
+| Change history                                                  |        |          |      |     |     |                                                           |                                 |                                 |
+|-----------------------------------------------------------------|--------|----------|------|-----|-----|-----------------------------------------------------------|---------------------------------|---------------------------------|
+| Date                                                            | TSG #  | TSG Doc. | CR   | Rev | Cat | Subject/Comment                                           | Old                             | New                             |
+| <b>Status of GSM 02.32</b>                                      |        |          |      |     |     |                                                           |                                 |                                 |
+|                                                                 |        |          |      |     |     | No Phase 1 version                                        |                                 |                                 |
+| 06-1997                                                         | SMG#22 |          |      |     |     | to SMG#22 for information                                 |                                 | 1.0.0                           |
+| 03-1998                                                         | SMG#25 |          |      |     |     | to SMG#25 for approval                                    | 1.0.0                           | 2.0.0                           |
+| 03-1998                                                         | SMG#25 |          |      |     |     | TS approved by SMG#25. IST is part of Release 98          | 2.0.0                           | 7.0.0                           |
+| 06-1998                                                         | SMG#26 |          | A001 | -   | C   | CR 02.32-A001 (cat C) approved by SMG#26                  | 7.0.0                           | 7.1.0                           |
+| 08-1999                                                         |        |          |      |     |     | R98 publication version                                   | 7.1.0                           | 7.1.1                           |
+| 04-2000                                                         |        |          |      |     |     | R99 publication version                                   | 7.1.1                           | 8.0.0                           |
+| <b>Status of TS 42.032 (Created from TS 02.32 Release 1999)</b> |        |          |      |     |     |                                                           |                                 |                                 |
+| SP-11                                                           | 02.32  |          |      |     |     | Upgrade to 42.032 Release 4 (3GPP numbering)              | <a href="#">02.32</a><br>8.0.0  | <a href="#">42.032</a><br>4.0.0 |
+| <b>Status of TS 22.032 (Created from TS 42.032 Release 4)</b>   |        |          |      |     |     |                                                           |                                 |                                 |
+| 06-2002                                                         | SP-16  |          |      |     |     | Decision to transfer IST to 3GPP system specification set | <a href="#">42.032</a><br>4.0.0 | <a href="#">22.032</a><br>4.0.0 |
+| 06-2002                                                         | SP-16  |          |      |     |     | Upgrade to Rel-5                                          | 4.0.0                           | 5.0.0                           |
+| 12-2004                                                         | SP-26  |          |      |     |     | Upgrade to Rel-6                                          | 5.0.0                           | 6.0.0                           |
+| 06-2007                                                         | SP-36  |          |      |     |     | Upgrade to Rel-7                                          | 6.0.0                           | 7.0.0                           |
+| 12-2008                                                         | SP-42  | --       | --   | --  | --  | Upgrade to Rel-8                                          | 7.0.0                           | 8.0.0                           |
+| 12-2009                                                         | SP-46  | -        | -    | -   | -   | Upgrade to Rel-9                                          | 8.0.0                           | 9.0.0                           |
+| 2011-03                                                         | -      | -        | -    | -   | -   | Update to Rel-10 version (MCC)                            | 9.0.0                           | 10.0.0                          |
+| 2012-09                                                         | -      | -        | -    | -   | -   | Update to Rel-11 version (MCC)                            | 10.0.0                          | 11.0.0                          |
+| 2014-09                                                         | -      | -        | -    | -   | -   | Update to Rel-12 version (MCC)                            | 11.0.0                          | 12.0.0                          |
+| 2015-12                                                         | -      | -        | -    | -   | -   | Update to Rel-13 version (MCC)                            | 12.0.0                          | 13.0.0                          |
+| 2017-03                                                         | -      | -        | -    | -   | -   | Update to Rel-14 version (MCC)                            | 13.0.0                          | 14.0.0                          |
+| 2018-06                                                         | -      | -        | -    | -   | -   | -                                                         | 14.0.0                          | 15.0.0                          |
+| 2020-07                                                         | -      | -        | -    | -   | -   | Update to Rel-16 version (MCC)                            | 15.0.0                          | 16.0.0                          |
+| 2022-03                                                         | -      | -        | -    | -   | -   | Update to Rel-17 version (MCC)                            | 16.0.0                          | 17.0.0                          |
+| 2024-03                                                         | -      | -        | -    | -   | -   | Update to Rel-18 version (MCC)                            | 17.0.0                          | 18.0.0                          |

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

@@ -0,0 +1,482 @@
+
+
+# 3GPP TS 22.034 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; High Speed Circuit Switched Data (HSCSD); Stage 1 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and a 'TM' symbol to the right.
+
+3GPP logo
+
+## --- **Keywords**
+
+GSM, UMTS, data, circuit mode
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                      |    |
+|--------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                       | 5  |
+| 1 Scope.....                                                                         | 6  |
+| 2 References.....                                                                    | 6  |
+| 3 Abbreviations and definitions .....                                                | 6  |
+| 3.1 Abbreviations .....                                                              | 6  |
+| 3.2 Definitions.....                                                                 | 7  |
+| 4 Description.....                                                                   | 7  |
+| 4.1 General .....                                                                    | 7  |
+| 4.2 Applicability.....                                                               | 7  |
+| 4.3 General Bearer Services.....                                                     | 7  |
+| 4.4 Parameters to be indicated and negotiated.....                                   | 7  |
+| 4.4.1 Call set-up.....                                                               | 7  |
+| 4.4.1.1 T services.....                                                              | 8  |
+| 4.4.1.2 NT services .....                                                            | 8  |
+| 4.4.2 Network initiated modification.....                                            | 8  |
+| 4.4.2.1 T services .....                                                             | 8  |
+| 4.4.2.2 NT services .....                                                            | 9  |
+| 4.4.3 User initiated modification .....                                              | 9  |
+| 4.4.3.1 T services .....                                                             | 9  |
+| 4.4.3.2 NT services .....                                                            | 9  |
+| 4.5 Air Interface Resource Allocation.....                                           | 9  |
+| 4.5.1 Minimum GERAN Air Interface Resource Allocation and Allocation Increment ..... | 9  |
+| 4.5.2 Flexible Air Interface Resource Allocation.....                                | 9  |
+| 4.6 Symmetric and asymmetric connections.....                                        | 9  |
+| 4.6.1 Symmetric connections .....                                                    | 9  |
+| 4.6.2 Asymmetric connections .....                                                   | 9  |
+| 4.6.2.1 Asymmetric air interface connection.....                                     | 9  |
+| 4.6.2.2 Channel coding asymmetry .....                                               | 10 |
+| 4.6.3 Network choice of connection symmetry.....                                     | 10 |
+| 4.7 User Equipment/Mobile Equipment requirements.....                                | 10 |
+| 4.8 Mobility Management.....                                                         | 10 |
+| 4.9 Roaming.....                                                                     | 10 |
+| 4.10 Quality of Service.....                                                         | 11 |
+| 4.10.1 Bit error rate .....                                                          | 11 |
+| 4.10.1.1 GERAN TCH/F Bit Error Rate.....                                             | 11 |
+| 4.10.1.2 Overall GBS Bit Error Rate .....                                            | 11 |
+| 4.10.2 GERAN Radio resource management.....                                          | 11 |
+| 4.10.3 Call set-up delay.....                                                        | 11 |
+| 4.10.4 End-to-end delay .....                                                        | 11 |
+| 4.10.5 Throughput .....                                                              | 11 |
+| 4.10.6 Network planning and interference levels.....                                 | 11 |
+| 4.11 Mapping of FNUR to GERAN TCH/F for T services .....                             | 11 |
+| 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services .....                      | 11 |
+| 4.13 GBS MMI aspects.....                                                            | 12 |
+| 4.14 GBS Subscription aspects .....                                                  | 12 |
+| 4.15 GBS charging aspects.....                                                       | 12 |
+| 4.16 O and M aspects.....                                                            | 12 |
+| 4.17 Multislot security aspects.....                                                 | 12 |
+| 5 Exceptional procedures or unsuccessful outcome .....                               | 13 |
+| 6 Interworking requirements.....                                                     | 13 |
+| 6.1 Service interworking .....                                                       | 13 |
+| 6.1.1 Interworking with supplementary services.....                                  | 13 |
+| 6.1.2 Interworking with other services .....                                         | 13 |
+| 6.2 Network interworking .....                                                       | 13 |
+
+**Annex A (informative): Change history..... 14**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the Stage 1 description of High Speed Circuit Switched Data (HSCSD). HSCSD is a feature that introduce General Bearer Services and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. Multislot also defines a flexible use of air interface resources which makes efficient and flexible use of higher user rates feasible.
+
+The Multislot mechanism is only applicable to GERAN.
+
+At UTRAN radio access parameters used for GBS user data are specified at TS 23.107.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.002: "Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
+- [3] 3GPP TS 22.004: "General on supplementary services".
+- [4] 3GPP TS 405.002: " Multiplexing and multiple access on the radio path".
+
+# --- 3 Abbreviations and definitions
+
+## 3.1 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                   |
+|-------|---------------------------------------------------|
+| AIUR  | Air Interface User Rate                           |
+| EDGE  | Enhanced Data rates for GSM Evolution             |
+| FNUR  | Fixed Network User Rate                           |
+| GBS   | General Bearer Services                           |
+| GERAN | GSM/EDGE radio access network                     |
+| HSCSD | High Speed Circuit Switched Data                  |
+| MO    | Mobile Originated                                 |
+| MT    | Mobile Terminated                                 |
+| NT    | Non Transparent                                   |
+| T     | Transparent                                       |
+| UE    | User Equipment (same as MS in GSM specifications) |
+
+Additional abbreviations can be found in TS 22.905 [1].
+
+## 3.2 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Fixed Network User Rate:** user rate between IWF and the fixed network.
+
+**Air Interface User Rate:** user rate between Mobile Termination and IWF. For T services it is the maximum possible AIUR not including padding. For NT services it is the maximum possible AIUR.
+
+**maximum possible GERAN AIUR:** highest possible GERAN AIUR that the multiple TCH/F can provide, e.g. 2 TCH/F using TCH/F9.6 provides a maximum possible AIUR of 19,2 kbit/s.
+
+**padding:** fill bits needed to adapt the maximum possible AIUR supported by a given number of TCH/F with a given channel coding to a FNUR that is lower than the maximum possible AIUR.
+
+# --- 4 Description
+
+## 4.1 General
+
+HSCSD is a feature that introduce General Bearer Services (GBS) and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. HSCSD also defines mechanisms for the use of air interface resources which makes efficient and flexible use of higher user rates feasible. The Multislot mechanism is only applicable to GERAN.
+
+## 4.2 Applicability
+
+GBS shall provide flexible ways of supporting GSM Phase 2, T and NT data services and new data services at the higher rates. Data compression shall be applicable to NT GBS. Supplementary Services applicable to the General Bearer Services are specified at TS 22.004, [3].
+
+## 4.3 General Bearer Services
+
+The General Bearer Services are defined in TS 22.002 [2].
+
+The General Bearer Services (GBS) consist of two Bearer Services, and they are as follows:
+
+- asynchronous;
+- synchronous.
+
+## 4.4 Parameters to be indicated and negotiated
+
+### 4.4.1 Call set-up
+
+The parameters to be indicated, and negotiated, if applicable, during the call set-up shall include:
+
+- FNUR;
+- GERAN Channel coding(s) acceptable (for the call);
+- maximum number of GERAN TCH/F (that the mobile user can accept);
+- wanted AIUR (desired rate that the mobile user wants the network to allocate). The wanted AIUR is applicable to NT services only;
+- indication if the user initiated modification is required, and if so, the network resource needs;
+- channel coding asymmetry indication.
+
+Some of the parameters are only utilised by GERAN. When UTRAN radio access bearer is allocated the values are ignored.
+
+The GERAN channel coding(s) acceptable shall be indicated by the mobile at call set-up and is not negotiable. It indicates the GERAN channel coding(s) that may be chosen by the network for the call.
+
+The maximum number of GERAN TCH/F shall be indicated at call set-up. It enables the mobile user to limit the number of GERAN TCH/F used and thus to control an essential parameter for charging. It sets the upper limit of number of TCH/F that the network may allocate to the mobile.
+
+The wanted AIUR (applicable to NT services only) indicates the AIUR that the mobile user wants and which the network shall try to reach but which it is not allowed to exceed. The exception where the network is allowed to exceed the wanted AIUR is when the network can achieve the GERAN AIUR with a lower number of TCH/F, e.g. wanted GERAN AIUR indicated by the mobile is 14,4 kbit/s, GERAN channel codings acceptable are both TCH/F9.6 and TCH/F4.8 and maximum number of TCH/F are 3, then the network shall choose 2 x 9,6 over 3 x 4,8 if a channel coding of TCH/F9.6 is available on two TCH/F.
+
+If the user wishes to make use of the user initiated modification procedure, this shall be indicated at the call set-up.
+
+It shall be possible to reserve a different FNUR than the AIUR.
+
+Channel coding asymmetry indication is only applicable to NT calls where the user has indicated acceptance for channel coding(s) based on enhanced modulation. In this case the user may indicate preference for channel coding symmetry, downlink biased channel coding asymmetry, or uplink biased channel coding asymmetry. The channel coding asymmetry indication is only applicable in direction UE to network.
+
+#### 4.4.1.1 T services
+
+The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is not allowed.
+
+The AIUR is always equal to the FNUR.
+
+Fax Group 3 can make use of HSCSD.
+
+The GERAN channel coding selected must be one of the channel coding(s) indicated in the channel coding(s) acceptable parameter, the number of TCH/F selected shall not exceed the maximum number of TCH/F parameter, and the combination of the two shall result in an AIUR that is equal to the FNUR.
+
+#### 4.4.1.2 NT services
+
+The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is allowed.
+
+The wanted AIUR is indicated by the mobile at call set-up.
+
+### 4.4.2 Network initiated modification
+
+#### 4.4.2.1 T services
+
+For transparent calls the radio resource parameters must remain within limits that allow the transparent call to maintain its characteristics of fixed end to end throughput and delay. This means that in GERAN the channel coding and the number of TCH/F used may change during the call as long as a channel coding indicated in the channel coding(s) acceptable parameter is used, the maximum number of TCH/F is not exceeded and the AIUR is kept constant.
+
+#### 4.4.2.2 NT services
+
+For NT calls the network may modify the number of TCH/F and the channel coding used at GERAN and thus also the AIUR during the call as long as the maximum number of TCH/F, and the channel coding(s) acceptable are all respected. The network shall try to reach the wanted GERAN AIUR indicated, as long as the resource situation allows it.
+
+### 4.4.3 User initiated modification
+
+The in-call modification feature shall be supported in case of alternate services.
+
+#### 4.4.3.1 T services
+
+The user initiated modification is not applicable to T services.
+
+#### 4.4.3.2 NT services
+
+The user may indicate a change of the parameters maximum number of GERAN TCH/F, wanted AIUR, and channel coding asymmetry. No other parameters may be modified.
+
+The user initiated modification is only applicable to the data phase of alternate services.
+
+## 4.5 Air Interface Resource Allocation
+
+### 4.5.1 Minimum GERAN Air Interface Resource Allocation and Allocation Increment
+
+Air interface resources shall be allocated to HSCSD calls at TCH/F increments. The minimum air interface resource allocation for HSCSD calls shall be one TCH/F.
+
+### 4.5.2 Flexible Air Interface Resource Allocation
+
+Flexible air interface resource allocation enables:
+
+- the network to allocate dynamically resources related to the air interface usage according to the network operator's strategy, within the limits negotiated at the call set-up or during a user initiated modification.
+
+## 4.6 Symmetric and asymmetric connections
+
+### 4.6.1 Symmetric connections
+
+For symmetric connections, air interface resources are allocated symmetrically.
+
+### 4.6.2 Asymmetric connections
+
+There are two types of asymmetry, asymmetric air interface connection and channel coding asymmetry. Asymmetric air interface connection implies that more time slots are used in the downlink than in the uplink at GERAN. Channel coding asymmetry implies that one channel coding is used in the uplink and another channel coding is used in the downlink at GERAN.
+
+#### 4.6.2.1 Asymmetric air interface connection
+
+The provision of the asymmetric air interface connections allows simple ME (of Type 1, Reference TS 405.002, [4]) to receive at higher AIUR than otherwise would be possible with a symmetric connection.
+
+Asymmetric air interface connections that are a subset of the symmetric HSCSD, and support different user rates at uplink and downlink, shall be provided.
+
+Asymmetric air interface connections are only applicable to the downlink-biased asymmetry, i.e., where the ME is receiving at a higher rate than it is transmitting.
+
+Asymmetric air interface connections shall only be applicable to NT GBS.
+
+#### 4.6.2.2 Channel coding asymmetry
+
+Channel coding asymmetry may be set up by the network in three cases:
+
+- if the UE only supports enhanced modulation in the downlink;
+- if the UE supports enhanced modulation in both links, but the user indicates preference for uplink or downlink biased channel coding asymmetry;
+- if the UE supports enhanced modulation in both links, and the user indicates preference for channel coding symmetry, but the link conditions justifies different channel codings in up- and downlink.
+
+In the case when preference of uplink or downlink biased channel coding asymmetry is indicated by the user, and a asymmetric channel coding connection is set up based on this indication, the network shall always assign a TCH/F14.4 channel at GERAN on the unbiased link.
+
+Channel coding asymmetry shall only be applicable to NT services applying the GERAN channel codings TCH/F14.4, TCH/F28.8 and TCH/F43.2.
+
+In case a symmetric channel coding connection is set up, the link adaptation mechanism may change a symmetric channel coding connection to an asymmetric channel coding connection.
+
+### 4.6.3 Network choice of connection symmetry
+
+When the network has a choice of allocating either a symmetric or an asymmetric air interface connection it shall proceed as follows:
+
+- in the case where the wanted AIUR is smaller than or equal to the AIUR supported symmetrically by the ME, or asymmetric air interface connection is not supported by the network, then a symmetric air interface connection is established;
+- in the case where the wanted AIUR exceeds the AIUR supported symmetrically by the ME, the network shall assign the maximum AIUR supported by the ME in the down-link at GERAN, upper-bounded by the maximum number of TCH/F indicated by the mobile user, and the number of TCH/F supported by the network, maintaining the minimum of one TCH/F.
+
+## 4.7 User Equipment/Mobile Equipment requirements
+
+The general UE capabilities is applicable to HSCSD.
+
+A ME that supports multislot mechanism shall support one or more of the GERAN channel types TCH/F at or above 4,8 kbit/s.
+
+Given that the ME supports a certain GERAN channel coding, the network shall be able to assume that the ME can support this channel coding in any multislot configuration allowed by its multislot class (Reference TS 45.002, [4]).
+
+## 4.8 Mobility Management
+
+HSCSD shall be provided for within the existing supported Mobility Management.
+
+## 4.9 Roaming
+
+Roaming shall be possible.
+
+## 4.10 Quality of Service
+
+### 4.10.1 Bit error rate
+
+#### 4.10.1.1 GERAN TCH/F Bit Error Rate
+
+The bit error rate performance of each TCH/F of a multiple TCH/F HSCSD call shall be the same as that of a single TCH/F data call for the same channel coding.
+
+#### 4.10.1.2 Overall GBS Bit Error Rate
+
+Any increase in the bit error rate caused by the splitting and combining of multiple GERAN TCH/F shall be kept to a minimum.
+
+### 4.10.2 GERAN Radio resource management
+
+The multislot mechanism shall be provided for within the existing Radio Resource management control functions, including the relevant handover types. The handover shall be simultaneous for all air interface timeslots making up the call.
+
+The multislot mechanism shall be provided with full mobility.
+
+### 4.10.3 Call set-up delay
+
+Any increase in call set-up delay of the GBS calls compared to GSM Phase 2 data services shall be kept to a minimum.
+
+### 4.10.4 End-to-end delay
+
+Any increase in end-to-end delay of the GBS calls compared to GSM Phase 2 data services shall be kept to a minimum.
+
+### 4.10.5 Throughput
+
+The throughput for GBS T calls shall remain constant for the duration of the call except for the interruption of transmission at handover.
+
+### 4.10.6 Network planning and interference levels
+
+The impact of multislot mechanism on network planning and interference levels shall be kept to a minimum.
+
+## 4.11 Mapping of FNUR to GERAN TCH/F for T services
+
+For some FNUR padding is required to adapt the maximum possible AIUR to the FNUR.
+
+## 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services
+
+The following table indicates the mapping of AIUR to the number of TCH/F for NT services.
+
+**Table 1: Mapping of AIUR to TCH/F for NT services**
+
+| <b>AIUR</b> | <b>TCH/F4.8</b> | <b>TCH/F9.6</b> | <b>TCH/F14.4</b> | <b>TCH/F28.8</b> | <b>TCH/F43.2</b> |
+|-------------|-----------------|-----------------|------------------|------------------|------------------|
+| 4,8 kbit/s  | 1               | N/A             | N/A              | N/A              | N/A              |
+| 9,6 kbit/s  | 2               | 1               | N/A              | N/A              | N/A              |
+| 14,4 kbit/s | 3               | N/A             | 1                | N/A              | N/A              |
+| 19,2 kbit/s | 4               | 2               | N/A              | N/A              | N/A              |
+| 28,8 kbit/s | N/A             | 3               | 2                | 1                | N/A              |
+| 38,4 kbit/s | N/A             | 4               | N/A              | N/A              | N/A              |
+| 43,2 kbit/s | N/A             | N/A             | 3                | N/A              | 1                |
+| 57,6 kbit/s | N/A             | N/A             | 4                | 2                | N/A              |
+| N/A         | Not applicable. |                 |                  |                  |                  |
+
+For Fixed Network User Rates (FRUR) see TS 22.002 [2].
+
+NOTE: GERAN TCH/F28.8 and GERAN TCH/F43.2 require EDGE capability.
+
+## 4.13 GBS MMI aspects
+
+It shall be possible to configure the parameters negotiated and indicated at GBS call set-up and during user initiated modification.
+
+## 4.14 GBS Subscription aspects
+
+HSCSD is not subscribed to. Users wanting to use multislot mechanism must subscribe to the General Bearer Services.
+
+## 4.15 GBS charging aspects
+
+To allow accurate charging of multislot calls, a record of start and stop timestamps versus the number of TCH/F, for each change in TCH/F allocation, shall be provided.
+
+NOTE: For MO multislot calls, the A party is liable for the use of all the TCH/F in her PLMN.
+
+For MT multislot calls, the B party may have to pay for one or more of the TCH/F in her PLMN.
+
+In case the originating or terminating subscriber is a fixed network subscriber, there should be no additional charge (in respect of the changing allocation of GERAN TCH/F) for the originating or terminating fixed network subscriber.
+
+## 4.16 O and M aspects
+
+For GBS call, there are several new and modified parameters compared to GSM Phase 2 data calls.
+
+For GBS, the air interface resource allocation may change several times during the call (network initiated and user initiated changes). It shall be possible to limit the frequency of changes per call, separately for network initiated and user initiated changes.
+
+Multislot calls can occupy multiple TCH/F. It shall dynamically be possible to limit the maximum number of GERAN TCH/F allowed for GBS calls per cell.
+
+## 4.17 Multislot security aspects
+
+Authentication and ciphering are applicable to multislot calls with no or minimal reduction in the security of the air interface.
+
+# --- 5 Exceptional procedures or unsuccessful outcome
+
+When a GBS call is offered to an entity (either ME or network) unable to support the offered GBS call, it shall be possible, within the limitations of the service, to revert the call:
+
+- to an GBS call the entity can support; or
+- at GERAN to a GSM Phase 2 data service.
+
+# --- 6 Interworking requirements
+
+## 6.1 Service interworking
+
+### 6.1.1 Interworking with supplementary services
+
+Supplementary Services that are applicable to the General Bearer Services can be used (Reference TS 22.004, [3]).
+
+### 6.1.2 Interworking with other services
+
+The simultaneous use of multislot mechanism and SMS MO/PP, and multislot mechanism and SMS MT/PP services shall be possible.
+
+## 6.2 Network interworking
+
+Interworking should be possible to all networks which are covered by GSM Phase 2 bearer services:
+
+- PSTN;
+- ISDN.
+
+# Annex A (informative): Change history
+
+| Change history |           |           |        |     |     |       |     |                                                                |        |        |           |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|----------------------------------------------------------------|--------|--------|-----------|
+| TSG SA#        | SA Doc.   | SA1 Doc   | Spec   | CR  | Rev | Rel   | Cat | Subject/Comment                                                | Old    | New    | Work Item |
+| SP-04          |           |           | 02.34  |     |     |       |     | Transferred to 3GPP SA1 at ETSI SMG#29                         | 8.1.0  | 3.0.0  |           |
+| SP-05          | SP-99479  | S1-99615  | 22.034 | 001 |     | R99   | D   | Editorial changes for alignment                                | 3.0.0  | 3.1.0  |           |
+| SP-05          | SP-99448  | S1-99706  | 22.034 | 002 |     | R99   | B   | Channel coding asymmetry for ECSD                              | 3.0.0  | 3.1.0  |           |
+| SP-07          | SP-000057 | S1-000052 | 22.034 | 003 |     | R99   | C   | CR on HSCSD changes for 3GPP                                   | 3.1.0  | 3.2.0  |           |
+| April 2000     |           |           |        |     |     |       |     | Editorial correction to title (Release 1999, not Release 2000) | 3.2.0  | 3.2.1  |           |
+| SP-11          | SP-010065 | S1-010258 | 22.004 |     |     | Rel-4 |     | Transferred to 3GPP Release 4                                  | 3.2.1  | 4.0.0  |           |
+| SP-16          | SP-020239 | S1-020890 | 22.034 | 004 |     | Rel-4 | F   | CR to 22.034 Correction of terminology and references          | 4.0.0  | 4.1.0  | Correct   |
+| SP-16          | SP-020267 | S1-021043 | 22.034 |     |     | Rel-5 |     | Updated from Rel-4 to Rel5                                     | 4.1.0  | 5.0.0  |           |
+| SP-26          | SP-040744 | S1-040997 | 22.034 |     |     | Rel-6 |     | Updated from Rel-5 to Rel-6                                    | 5.0.0  | 6.0.0  |           |
+| SP-36          |           |           | 22.034 |     |     | Rel-7 |     | Updated from Rel-6 to Rel-7                                    | 6.0.0  | 7.0.0  |           |
+| SP-42          | -         | -         |        |     |     | Rel-8 |     | Updated from Rel-7 to Rel-8                                    | 7.0.0  | 8.0.0  |           |
+| SP-46          | -         | -         | -      | -   | -   | -     |     | Updated to Rel-9 by MCC                                        | 7.0.0  | 9.0.0  |           |
+| 2011-03        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-10 version (MCC)                                 | 9.0.0  | 10.0.0 |           |
+| 2012-09        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-11 version (MCC)                                 | 10.0.0 | 11.0.0 |           |
+| 2014-10        | -         | -         | -      | -   | -   | -     | -   | Update to Rel-12 version (MCC)                                 | 11.0.0 | 12.0.0 |           |
+| 2015-12        |           |           |        |     |     |       |     | Update to Rel-13 version (MCC)                                 | 12.0.0 | 13.0.0 |           |
+| 2017-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-14 by MCC                                       | 13.0.0 | 14.0.0 |           |
+| 2018-06        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-15 by MCC                                       | 14.0.0 | 15.0.0 |           |
+| SP-88e         | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-16 by MCC                                       | 15.0.0 | 16.0.0 |           |
+| 2022-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-17 by MCC                                       | 16.0.0 | 17.0.0 |           |
+| 2024-03        | -         | -         | -      | -   | -   | -     | -   | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload)      | 17.0.0 | 18.0.1 |           |

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

@@ -0,0 +1,807 @@
+
+
+# 3GPP TS 22.038 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; (U)SIM Application Toolkit (USAT); Service description; Stage 1 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like signal icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+UMTS, GSM, Card, SIM, stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                    |    |
+|--------------------------------------------------------------------|----|
+| Foreword .....                                                     | 5  |
+| 1 Scope.....                                                       | 6  |
+| 2 References.....                                                  | 6  |
+| 2.1 Normative references .....                                     | 7  |
+| 3 Definitions and abbreviations .....                              | 7  |
+| 3.1 Definitions.....                                               | 7  |
+| 3.2 Abbreviations .....                                            | 8  |
+| 4 Description.....                                                 | 8  |
+| 5 High level USAT requirements.....                                | 9  |
+| 6 SAT/USAT/ME interface requirements.....                          | 10 |
+| 6.1 (U)SAT APIs.....                                               | 10 |
+| 6.2 USAT proactive capability.....                                 | 10 |
+| 6.3 ME Capability for support of bearer independent protocol ..... | 11 |
+| 6.4 ME equipped with positioning features .....                    | 12 |
+| 7 USAT User Interface requirements.....                            | 12 |
+| 7.1 Data presentation requirements (e.g. Display).....             | 12 |
+| 7.2 Data acquisition requirements (e.g. Keypad).....               | 12 |
+| 7.3 Access requirements (e.g. Menu).....                           | 12 |
+| 7.4 Menu capability.....                                           | 12 |
+| 7.4.1 Set up capability .....                                      | 12 |
+| 7.4.2 Selection capability .....                                   | 13 |
+| 7.5 Soft-key capability .....                                      | 13 |
+| 7.6 User control of the SAT/USAT execution environment.....        | 13 |
+| 7.7 MMS presentation requirements .....                            | 13 |
+| 8 Network interface requirements.....                              | 13 |
+| 8.1 USAT/Network interaction .....                                 | 13 |
+| 8.2 Communication control capability .....                         | 13 |
+| 8.3 Service Interworking requirements .....                        | 14 |
+| 9 USAT data exchange capabilities requirements .....               | 14 |
+| 9.1 Data exchange capabilities supported .....                     | 14 |
+| 10 Charging requirements.....                                      | 14 |
+| 11 Security requirements .....                                     | 15 |
+| 11.1 Secure Environment requirements .....                         | 15 |
+| 12 Emergency calls .....                                           | 15 |
+| 13 Roaming .....                                                   | 15 |
+| 14 Interaction with supplementary services.....                    | 16 |
+| 14.1 General .....                                                 | 16 |
+| 14.2 Line Identification .....                                     | 16 |
+| 14.2.1 Calling Line Identification Presentation (CLIP) .....       | 16 |
+| 14.2.2 Calling Line Identification Restriction (CLIR) .....        | 16 |
+| 14.2.3 Connected Line Identification Presentation (COLP).....      | 16 |
+| 14.2.4 Connected Line Identification Restriction (COLR) .....      | 16 |
+| 14.3 Call Forwarding.....                                          | 16 |
+| 14.3.1 Call Forwarding Unconditional (CFU) .....                   | 16 |
+| 14.3.2 Call Forwarding Busy (CFB) .....                            | 16 |
+| 14.3.3 Call Forwarding on No Reply (CFNRy) .....                   | 16 |
+| 14.3.4 Call Forwarding on Not Reachable (CFNRc) .....              | 16 |
+| 14.4 Call Completion .....                                         | 16 |
+
+|                               |                                                                                                  |           |
+|-------------------------------|--------------------------------------------------------------------------------------------------|-----------|
+| 14.4.1                        | Call Hold (CH) .....                                                                             | 16        |
+| 14.4.2                        | Call Waiting (CW) .....                                                                          | 17        |
+| 14.5                          | Multi Party (MPTY).....                                                                          | 17        |
+| 14.6                          | Closed User Group (CUG).....                                                                     | 17        |
+| 14.7                          | Advice of Charge (AoC) .....                                                                     | 17        |
+| 14.8                          | Call Barring.....                                                                                | 17        |
+| 14.8.1                        | Barring of all outgoing calls .....                                                              | 17        |
+| 14.8.2                        | Barring of outgoing international calls .....                                                    | 17        |
+| 14.8.2.1                      | Mobile originated calls .....                                                                    | 17        |
+| 14.8.2.2                      | Forwarded Calls.....                                                                             | 17        |
+| 14.8.3                        | Barring of outgoing international calls except those directed to the HPLMN country .....         | 17        |
+| 14.8.4                        | Barring of all incoming calls .....                                                              | 17        |
+| 14.8.5                        | Barring of incoming calls when roaming .....                                                     | 17        |
+| 14.9                          | Explicit Call Transfer (ECT).....                                                                | 17        |
+| 14.10                         | Completion of Call to Busy Subscriber (CCBS).....                                                | 18        |
+| 14.11                         | Multiple Subscriber Profile (MSP) .....                                                          | 18        |
+| 15                            | Interaction with network features .....                                                          | 18        |
+| 15.1                          | Interactions with Operator Determined Barring (ODB) .....                                        | 18        |
+| 15.1.1                        | Barring of all outgoing calls .....                                                              | 18        |
+| 15.1.2                        | Barring of all outgoing international calls .....                                                | 18        |
+| 15.1.3                        | Barring of all outgoing international calls except those directed to the home PLMN country ..... | 18        |
+| 15.1.4                        | Barring of outgoing calls when roaming outside the home PLMN country .....                       | 18        |
+| 15.1.5                        | Barring of outgoing premium rate calls.....                                                      | 18        |
+| 15.1.6                        | Barring of incoming calls .....                                                                  | 18        |
+| 15.1.7                        | Barring of incoming calls when roaming outside the home PLMN country .....                       | 18        |
+| 15.1.8                        | Operator Specific Barring.....                                                                   | 18        |
+| 15.1.9                        | Barring of Supplementary Services Management.....                                                | 19        |
+| 15.2                          | Interactions with Optimal Routing (OR).....                                                      | 19        |
+| 15.3                          | Interactions with MExE .....                                                                     | 19        |
+| 15.4                          | Interactions with CAMEL.....                                                                     | 19        |
+| 16                            | Compatibility of USAT ME's and applications.....                                                 | 19        |
+| 16.1                          | USAT Classification .....                                                                        | 19        |
+| 16.2                          | ME/USIM operation.....                                                                           | 20        |
+| 16.3                          | ME/UICC capability information exchange .....                                                    | 20        |
+| 16.4                          | ME and compatibility.....                                                                        | 20        |
+| 16.5                          | Void.....                                                                                        | 20        |
+| 17                            | Void.....                                                                                        | 20        |
+| <b>Annex A (informative):</b> | <b>Change history.....</b>                                                                       | <b>21</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
+
+This 3GPP Technical Specification defines the stage one description of the USIM application Toolkit (USAT). Stage one is an overall service description, primarily from the subscriber's and serving environment's points of view, and does not deal with the details of the human interface itself.
+
+This TS includes information applicable to network operators, serving environments and terminal, switch and database manufacturers.
+
+This TS contains the core requirements for a USIM application Toolkit (USAT) which are sufficient to provide a complete service.
+
+It is highly desirable however, that technical solutions for a USIM application Toolkit (USAT) are sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+![Diagram illustrating the scope of this TS. It shows a Mobile Equipment (ME) connected to a PLMN cloud, which is further connected to a SAT/USAT Server(s) cloud. The ME is shown interacting with a SIM/USIM card, which is divided into GSM/UMTS and SAT/USAT sections. Arrows indicate the scope of this TS, pointing to the ME, the SIM/USIM card, and the PLMN cloud.](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg)
+
+The diagram illustrates the scope of the specification. At the top left is a box labeled 'ME' (Mobile Equipment). Below it is a box representing a 'SIM/USIM' card, which is divided into two horizontal sections: 'GSM/UMTS' and 'SAT/USAT'. Double-headed arrows connect the 'ME' box to both the 'GSM/UMTS' and 'SAT/USAT' sections. To the right of the 'ME' box is a cloud labeled 'PLMN'. A single-headed arrow points from the 'ME' box to the 'PLMN' cloud. Another single-headed arrow points from the 'PLMN' cloud to a third cloud on the far right labeled 'SAT/USAT Server(s)'. A label 'Scope of this TS' has three arrows pointing to the 'ME' box, the 'SIM/USIM' card, and the 'PLMN' cloud. The 'SAT/USAT Server(s)' cloud is not pointed to by the 'Scope of this TS' label.
+
+Diagram illustrating the scope of this TS. It shows a Mobile Equipment (ME) connected to a PLMN cloud, which is further connected to a SAT/USAT Server(s) cloud. The ME is shown interacting with a SIM/USIM card, which is divided into GSM/UMTS and SAT/USAT sections. Arrows indicate the scope of this TS, pointing to the ME, the SIM/USIM card, and the PLMN cloud.
+
+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-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 | Extention of the USAT bearers                                                                                             | 7.1.0  | 7.2.0  | WLAN    |
+| SP-27   | SP-050057 | S1-050247     | 22.038 | 027  | - | Rel-7  | A | References corrections                                                                                                    | 7.2.0  | 7.3.0  | TEI-7   |
+| SP-28   | SP-050220 | S1-050479     | 22.038 | 028  | - | Rel-7  | F | Correction of WLAN into I-WLAN                                                                                            | 7.3.0  | 7.4.0  | WLAN    |
+| SP-29   | SP-050606 |               | 22.038 | 0030 | 1 | Rel-7  | A | Addition of UTRAN packet service as a data bearer for the UICC                                                            | 7.4.0  | 7.5.0  | TEI-7   |
+| SP-39   | SP-080043 | S1-080277     | 22.038 | 0032 | 3 | Rel-8  | C | Extension of Toolkit communication control to IMS                                                                         | 7.5.0  | 8.0.0  | TEI8    |
+| SP-39   | SP-080043 | S1-080311     | 22.038 | 0033 | 4 | Rel-8  | B | Availability of Location information in the UICC                                                                          | 7.5.0  | 8.0.0  | TEI8    |
+| SP-39   | SP-080043 | S1-080305     | 22.038 | 0035 | 4 | Rel-8  | B | Toolkit over HSP                                                                                                          | 7.5.0  | 8.0.0  | TEI8    |
+| -       | -         | -             | -      |      |   |        |   | Some revision marks appearing in v.8.0.0 have been accepted                                                               | 8.0.0  | 8.0.1  |         |
+| SP-43   | SP-090215 | S1-090288 rev | 22.038 | 0036 | 5 | Rel-9  | B | Discovery of surrounding home (e)NodeB by UICC                                                                            | 8.0.1  | 9.0.0  | EHNB    |
+| SP-50   | SP-100805 | S1-103325     | 22.038 | 0037 | 1 | Rel-10 | F | Correction of USAT requirements                                                                                           | 9.0.0  | 10.0.0 | TEI10   |
+| 2011-03 |           |               |        |      |   |        |   | Update to Rel-10 version (MCC)                                                                                            | 10.0.0 | 10.0.1 |         |
+| 2012-09 | -         | -             | -      | -    | - | -      | - | Update to Rel-11 version (MCC)                                                                                            | 10.0.1 | 11.0.0 |         |
+| 2014-10 | -         | -             | -      | -    | - | -      | - | Update to Rel-12 version (MCC)                                                                                            | 11.0.0 | 12.0.0 |         |
+| 2015-12 |           |               |        |      |   |        |   | Update to Rel-13 version (MCC)                                                                                            | 12.0.0 | 13.0.0 |         |
+| 2017-03 | -         | -             | -      | -    | - | -      | - | Updated to Rel-14 by MCC                                                                                                  | 13.0.0 | 14.0.0 |         |
+| 2018-06 | -         | -             | -      | -    | - | -      | - | Updated to Rel-15 by MCC                                                                                                  | 14.0.0 | 15.0.0 |         |
+| SA#88e  | -         | -             | -      | -    | - | -      | - | Updated to Rel-16 by MCC                                                                                                  | 15.0.0 | 16.0.0 |         |
+| 2022-03 | -         | -             | -      | -    | - | -      | - | Updated to Rel-17 by MCC                                                                                                  | 16.0.0 | 17.0.0 |         |
+| 2024-03 | -         | -             | -      | -    | - | -      | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload)                                                                 | 17.0.0 | 18.0.1 |         |

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

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