Add files using upload-large-folder tool

marked/Rel-11/43_series/43013/raw.md

@@ -0,0 +1,144 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                             |   |
+|---------------------------------------------|---|
+| Foreword .....                              | 4 |
+| 1 Scope.....                                | 5 |
+| 2 References.....                           | 5 |
+| 3 Abbreviations .....                       | 5 |
+| 4 Overview of discontinuous reception ..... | 6 |
+| 5 MSC functions .....                       | 6 |
+| 6 BSS functions.....                        | 6 |
+| 7 MS functions.....                         | 6 |
+| 8 Support via the air interface .....       | 7 |
+| 9 Operational aspects .....                 | 7 |
+| Annex A (informative): Change History.....  | 8 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document provides a system wide view of the operation of discontinuous reception on the GSM system.
+
+The support of DRX is mandatory in GSM PLMNs.
+
+The detailed coding and procedural details are defined in the relevant Technical Specifications dealing with the specific interfaces that are involved, for instance GSM 08.08 and GSM 04.08. Reference is also made to the framing on the air interface which is defined in Technical Specification GSM 05.02.
+
+The present document gives an overview of the implementation of discontinuous reception DRX within the GSM system, the actions required at MSC, BSS, and MS, the support of the facility via the air interface, and some operational aspects of the facility.
+
+# --- 2 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
+- [3] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path".
+- [4] GSM 08.02: "Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Interface principles".
+- [5] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification".
+- [6] GSM 03.68: "Digital cellular telecommunications system (Phase 2+); Voice Group Call Service (VGCS) Stage 2".
+- [7] GSM 03.69: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Service (VBS) Stage 2".
+
+# --- 3 Abbreviations
+
+Abbreviations used in the present document are listed in GSM 01.04.
+
+# --- 4 Overview of discontinuous reception
+
+DRX is a technique that allows the mobile station to power down significant amounts of its internal circuitry for a high percentage of the time when it is in the idle mode.
+
+It also ensures that the MS is aware of exactly when page requests for it may be transmitted and it can then therefore schedule other tasks such that it avoids the problem of not decoding valid page requests transmitted by the network in the idle mode periods.
+
+The technique works by dividing the MSs within a cell into a set of groups. The group in which an MS resides is then known locally at both the MS and the BSS. All paging requests to each group are then scheduled and sent at a particular time which is derived from the TDMA frame number in conjunction with the IMSI of the MS and some BCCH transmitted data.
+
+Thus both the BSS and the MS know when relevant page requests will be sent and the MS can power down for the period when it knows that page requests will not occur.
+
+The page request can contain the IMSI and may contain the TMSI in order to identify the MS concerned. The IMSI is however always used to identify the paging population. Paging by means of the IMEI is for further study.
+
+Mechanisms for the application of DRX for the voice group call and voice broadcast services are defined in stage 2 descriptions in GSM 03.68 [6] and GSM 03.69 [7], respectively.
+
+# --- 5 MSC functions
+
+The MSC is almost transparent to DRX, since it has no real time knowledge of the absolute frame numbers on the air interface (refer to Technical Specification GSM 08.02).
+
+It should be noted, however, that the MSC does define which cells are to be paged in order to locate a particular MS. Normally this will be a location area.
+
+The MSC therefore constructs page requests and sends them to a specific set of BSSs. Each page request always includes the IMSI. The timer to detect non receipt of a page response may require alteration depending upon the number of page groups that are involved. If this is the case, then the timer will be set by O and M command at the same time as the number of paging groups at the cell is altered.
+
+# --- 6 BSS functions
+
+At the BSS page requests are received. It is implicit (single cell BSSs) or explicit (multi cell BSSs) within the page requests from the MSC to which cell the page request is destined (Technical Specifications GSM 08.08 and GSM 08.02 refers).
+
+The BSS analyses the IMSI in order to derive the page group of the MS involved. The air interface page request is then constructed and transmitted in the appropriate TDMA burst. If the page request includes a TMSI and IMSI then the IMSI is used to derive the page population and the TMSI is inserted into the actual page request message. The scheduling of the page requests is therefore completely controlled by the BSS.
+
+The relationship between paging group and TDMA burst, and IMSI and paging group is given in Technical Specification GSM 05.02.
+
+The exact scheduling mechanism used at the BSS is not defined in the present document.
+
+However the BSS may set the "page mode" bits as described in Technical Specification GSM 04.08. This can be used to optimise paging load and reduce missed page requests during system reconfiguration.
+
+# --- 7 MS functions
+
+The MS shall derive its paging group as defined in Technical Specification GSM 05.02.
+
+The MS shall interpret all paging requests in its paging group according to the paging mode bits as described in Technical Specification GSM 04.08.
+
+# --- 8 Support via the air interface
+
+The BCCH and paging channel messages are defined in Technical Specification GSM 04.08. Technical Specification GSM 05.02 defines the algorithms which enable an MS to know the exact frame and burst when page requests relevant to it might be transmitted.
+
+# --- 9 Operational aspects
+
+There will be occasions when it is necessary to alter the parameters of cell such that the paging group of the MS may alter.
+
+If (referring to Technical Specification GSM 05.02) any of the parameters BS\_AG\_BLKS\_RES, BS\_CC\_CHANS\_COMB, BS\_CC\_CHANS or BS\_PA\_MFRMS have to be altered, then the period when page requests may be lost can be minimised for example by:
+
+Firstly setting the page mode to "page reorganisation" in all page requests on the affected cell for the exact duration of one paging period (i.e. BS\_PA\_MFRMS multiframe). At the completion of this announcement period, the BCCH parameters are set to the new values and the BSS starts scheduling the paging messages according to the new parameters. The page mode is reset to any of the values "normal mode" or "extended mode" as required.
+
+# Annex A (informative): Change History
+
+| Change history |           |         |                  |             |                      |
+|----------------|-----------|---------|------------------|-------------|----------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments     |
+| SMG#07         |           |         |                  | 4.0.4       | ETSI Publication     |
+| SMG#17         |           |         |                  | 5.0.0       | Release 1996 version |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version |
+
+| Change history |            |          |    |     |                    |        |        |
+|----------------|------------|----------|----|-----|--------------------|--------|--------|
+| Date           | TSG GERAN# | TSG Doc. | CR | Rev | Subject/Comment    | Old    | New    |
+| 2001-04        | 4          |          |    |     | Release 4 version  |        | 4.0.0  |
+| 2002-06        | 10         |          |    |     | Release 5 version  | 4.0.0  | 5.0.0  |
+| 2005-01        | 23         |          |    |     | Release 6 version  | 5.0.0  | 6.0.0  |
+| 2007-08        | 35         |          |    |     | Release 7 version  | 6.0.0  | 7.0.0  |
+| 2008-12        | 40         |          |    |     | Release 8 version  | 7.0.0  | 8.0.0  |
+| 2009-12        | 44         |          |    |     | Release 9 version  | 8.0.0  | 9.0.0  |
+| 2011-03        | 49         |          |    |     | Release 10 version | 9.0.0  | 10.0.0 |
+| 2012-09        | 55         |          |    |     | Release 11 version | 10.0.0 | 11.0.0 |

marked/Rel-11/43_series/43022/raw.md

@@ -0,0 +1,737 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                      |    |
+|----------------------------------------------------------------------|----|
+| Foreword .....                                                       | 5  |
+| 1 Scope.....                                                         | 6  |
+| 1.1 References.....                                                  | 6  |
+| 1.2 Definitions and abbreviations.....                               | 7  |
+| 2 General description of idle mode .....                             | 8  |
+| 3 Requirements and technical solutions.....                          | 9  |
+| 3.1 PLMN selection and roaming .....                                 | 9  |
+| 3.2 Camping on a cell.....                                           | 9  |
+| 3.2.1 Normal camping .....                                           | 9  |
+| 3.2.2 "Camp on any cell".....                                        | 10 |
+| 3.3 Regional provision of service.....                               | 10 |
+| 3.4 Borders between registration areas .....                         | 10 |
+| 3.5 Barred cells and access control .....                            | 10 |
+| 3.5.1 Barred cells.....                                              | 10 |
+| 3.5.2 Prioritizing cells.....                                        | 10 |
+| 3.5.2.1 For cell selection.....                                      | 10 |
+| 3.5.2.2 For cell reselection.....                                    | 11 |
+| 3.5.3 Access control .....                                           | 11 |
+| 3.5.4 Forbidden LA for regional provision of service .....           | 11 |
+| 3.5.5 Barred cell due to failed network authentication check .....   | 11 |
+| 3.6 Radio constraints.....                                           | 11 |
+| 3.7 No suitable cell (limited service state).....                    | 12 |
+| 3.8 CTS fixed part selection.....                                    | 12 |
+| 4 Overall process structure.....                                     | 12 |
+| 4.1 Process goal.....                                                | 12 |
+| 4.2 States description.....                                          | 13 |
+| 4.3 List of states .....                                             | 13 |
+| 4.3.1 List of states for the PLMN selection process.....             | 13 |
+| 4.3.2 List of States for the cell selection process (figure 3) ..... | 13 |
+| 4.3.3 List of states for location updating .....                     | 13 |
+| 4.3.4 List of states for location registration.....                  | 14 |
+| 4.4 PLMN selection process.....                                      | 14 |
+| 4.4.1 Introduction .....                                             | 14 |
+| 4.4.2 Registration on a PLMN.....                                    | 14 |
+| 4.4.3 PLMN selection.....                                            | 14 |
+| 4.4.4 Abnormal cases .....                                           | 14 |
+| 4.4.5 Roaming not allowed in this LA .....                           | 14 |
+| 4.5 Cell selection process.....                                      | 14 |
+| 4.6 Location registration process .....                              | 16 |
+| 4.7 Service indication.....                                          | 16 |
+| 4.8 BCCH allocation broadcasting and storage .....                   | 16 |
+| 4.9 Pageability of the mobile subscriber .....                       | 17 |
+| 4.10 MM Restart procedure .....                                      | 17 |
+| 5 Group receive mode .....                                           | 18 |
+| 5.1 General description .....                                        | 18 |
+| 5.2 Requirements and technical solutions.....                        | 18 |
+| 5.2.1 Network provisions .....                                       | 18 |
+| 5.2.2 Group receive mode cell monitoring.....                        | 19 |
+| 5.2.3 Group receive mode cell change .....                           | 20 |
+| 5.2.4 Uplink access in group calls .....                             | 20 |
+| 5a Broadcast/multicast receive mode .....                            | 20 |
+| 5a.1 General description .....                                       | 20 |
+| 5a.2 Requirements and technical solutions.....                       | 21 |
+| 5a.2.1 Network provisions .....                                      | 21 |
+| 5a.2.2 Broadcast/multicast receive mode cell monitoring .....        | 21 |
+
+5a.2.3 Broadcast/multicast receive mode cell change.....21  
+6 Tables and figures .....22  
+Annex A (informative): Change history.....23
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document gives an overview of the tasks undertaken by a GSM Mobile Station (MS) when in idle mode, that is, switched on but not having a dedicated channel allocated (e.g. not making or receiving a call), when in group receive mode, that is, receiving a voice group call or voice broadcast call but not having a dedicated connection or when in broadcast/multicast receive mode, that is, receiving an MBMS session but not having a dedicated channel allocated. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The idle mode functions are also performed by a CTS MS as long as the CTS MS is in manual mode GSM only or in automatic mode under PLMN coverage.
+
+NOTE: The term GSM MS is used for any type of MS supporting one, or combinations, of the frequency bands specified in 3GPP TS 45.005.
+
+The present document outlines how the requirements of the 3GPP TS 22 series Technical Specifications (especially 3GPP TS 22.011) on idle mode operation shall be implemented. Further details are given in 3GPP TS 44.018 and 3GPP TS 45.008.
+
+Clause 2 of the present document gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses. Clause 5 describes the cell change procedures for a MS in group receive mode. Clause 5a describes the cell change procedures for a MS in broadcast/multicast receive mode.
+
+## 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 TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] (void)
+- [3] (void)
+- [4] (void)
+- [5] (void)
+- [6] (void)
+- [7] (void)
+- [8] (void)
+- [9] 3GPP TS 22.011: " Service accessibility".
+- [10] (void)
+- [11] (void)
+- [12] (void)
+- [13] (void)
+- [14] (void)
+- [15] (void)
+
+- [16] (void)
+- [17] (void)
+- [18] (void)
+- [19] (void)
+- [20] (void)
+- [21] (void)
+- [22] (void)
+- [23] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol".
+- [24] (void)
+- [25] 3GPP TS 45.008: "Radio subsystem link control".
+- [26] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1".
+- [27] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [28] 3GPP TS 43.064: "General Packet Radio Service (GPRS); Overall description of the GPRS Radio Interface; Stage 2".
+- [29] (void)
+- [30] (void)
+- [31] 3GPP TS 23.122: " Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
+- [32] 3GPP TS 24.008: " Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3".
+- [33] 3GPP TS 31.102: "Characteristics of the USIM application".
+- [34] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2".
+- [35] 3GPP TS 43.069: "Voice Broadcast service (VBS); Stage 2".
+- [36] 3GPP TS 45.005: "Radio transmission and reception".
+- [37] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface" (Release 4).
+- [38] 3GPP TS 43.246: "Multimedia Broadcast Multicast Service (MBMS) in the GERAN; Stage 2".
+- [39] 3GPP TS 22.268: "Public Warning System (PWS) requirements; Stage 1".
+
+## 1.2 Definitions and abbreviations
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 21.905 and the following apply.
+
+|                                |                                                                                                          |
+|--------------------------------|----------------------------------------------------------------------------------------------------------|
+| <b>Selected PLMN</b>           | This is the PLMN that has been selected according to subclause 3.1, either manually or automatically.    |
+| <b>Available PLMN</b>          | This is a PLMN where the MS has found a cell that satisfies conditions (ii) and (iv) of subclause 3.2.1. |
+| <b>Home PLMN (HPLMN)</b>       | See 3GPP TS 23.122.                                                                                      |
+| <b>Registered PLMN (RPLMN)</b> | This is the PLMN on which certain LR outcomes have occurred (see 3GPP TS 23.122).                        |
+
+|                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Equivalent PLMN</b>              | A PLMN contained in the stored list of equivalent PLMNs. These PLMNs are considered equivalent to the selected PLMN regarding PLMN selection, cell selection, cell re-selection and handover (see 3GPP TS 23.122).                                                                                                                                                                                                                                                                                                            |
+| <b>Registration</b>                 | This is the process of camping on a cell of the PLMN and doing any necessary LRs.                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Camped on a cell</b>             | The MS (ME if there is no SIM) has completed the cell selection/reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN may not be aware of the existence of the MS (ME) within the chosen cell.                                                                                                                                                                                                                            |
+| <b>Current serving cell</b>         | This is the cell on which the MS is camped.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Suitable Cell</b>                | This is a cell on which an MS may camp. It must satisfy criteria defined in subclause 3.2.1. For an MS in group receive mode, the suitable cell is determined by the criteria defined in subclause 5.2.3.                                                                                                                                                                                                                                                                                                                     |
+| <b>Acceptable Cell</b>              | This is a cell that the MS may camp on to make emergency calls and to receive warning notifications. It must satisfy criteria defined in sub clause 3.2.2.                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Group call</b>                   | A communication in which several MSs can receive, but at most one may be allowed to transmit on a radio channel. Examples of group calls are those established for the voice group call service (VGCS, see 3GPP TS 43.068).                                                                                                                                                                                                                                                                                                   |
+| <b>Broadcast call</b>               | A communication in which several MSs can receive, but only the originator of the call is allowed to transmit on the radio channel. Examples of the broadcast call are those established for the voice broadcast service (VBS, see 3GPP TS 43.069).                                                                                                                                                                                                                                                                            |
+| <b>Group receive mode</b>           | State of the MS when it is engaged in a voice group or voice broadcast call as a listener.                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>GPRS MS</b>                      | An MS capable of GPRS services is a GPRS MS.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>CTS MS</b>                       | An MS capable of CTS services is a CTS MS.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Location Registration (LR)</b>   | An MS which is IMSI attached to non-GPRS services only performs location registration by the Location Updating procedure. A GPRS MS which is IMSI attached to GPRS services or to GPRS and non-GPRS services performs location registration by the Routing Area Update procedure only when in a network of network operation mode I. Both procedures are performed independently by the GPRS MS when it is IMSI attached to GPRS and non-GPRS services in a network of network operation mode II or III (see 3GPP TS 23.060). |
+| <b>Localised Service Area (LSA)</b> | A localised service area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide contiguous coverage.                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>SoLSA exclusive access</b>       | Cells on which normal camping is allowed only for MS with Localised Service Area (LSA) subscription.                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Registration Area</b>            | A registration area is an area in which mobile stations may roam without a need to perform location registration. The registration area corresponds to location area (LA) for performing location updating procedure and it corresponds to routing area for performing the routing area update procedure.                                                                                                                                                                                                                     |
+
+The PLMN to which a cell belongs (PLMN identity) is given in the system information transmitted on the BCCH (MCC + MNC part of LAI).
+
+# 2 General description of idle mode
+
+See 3GPP TS 23.122.
+
+# 3 Requirements and technical solutions
+
+The following subclauses list the main requirements of idle mode operation and give an outline of the technical solution.
+
+## 3.1 PLMN selection and roaming
+
+See 3GPP TS 23.122.
+
+## 3.2 Camping on a cell
+
+### 3.2.1 Normal camping
+
+For normal service, the MS has to camp on a suitable cell, tune to that cell's control channel(s), and possibly register within the PLMN so that the MS can:
+
+- a) Receive system information from the PLMN , e.g., the cell options ;
+- b) Receive paging messages from the PLMN, e.g., when there is an incoming call for the MS;
+- c) Initiate call setup for outgoing calls or other actions from the MS (where possible, see subclauses 3.5.3 and 3.5.4).
+
+The choice of such a suitable cell for the purpose of receiving normal service is referred to as "normal camping". There are various requirements that a cell must satisfy before an MS can perform normal camping on it:
+
+- i) It should be a cell of the selected PLMN or, if the selected PLMN is equal to the last registered PLMN, an equivalent PLMN;
+- ii) It should not be "barred" (see subclause 3.5.1);
+- iii) It should not be in an LA which is in the list of "forbidden LAs for roaming";
+- iv) The radio path loss between MS and BTS must be below a threshold set by the PLMN operator. This is estimated as shown in subclause 3.6;
+- v) It should not be a SoLSA exclusive cell to which MS does not subscribe. This requirement is only valid for MSs supporting SoLSA.
+
+Initially, the MS looks for a cell which satisfies these 5 constraints ("suitable cell") by checking cells in descending order of received signal strength. If a suitable cell is found, the MS camps on it and performs any registration necessary. Cells can have two levels of priority, suitable cells which are of low priority are only camped on if there are no other suitable cells of normal priority. (This is called "cell selection").
+
+When camped on a cell the MS regularly looks to see if there is a better cell in terms of a cell re-selection criterion, and if there is, the better cell is selected. Also if one of the other criteria changes, (e.g., the current serving cell becomes barred), or there is a downlink signalling failure (see subclause 3.6), a new cell is selected. (This is called "cell reselection").
+
+In order to speed up these processes, a list of the RF channels containing BCCH or CPBCCH carriers of the same PLMN is broadcast in the system information messages, see subclause 4.8. Also, the MS does not need to search all possible RF channels to find a suitable cell. If, after searching the number of RF channels, given for each frequency band below, with the strongest received signal level, a BCCH or CPBCCH carrier has been found but no suitable cell of the selected PLMN has been found, the MS can stop the attempt to find a suitable cell of the selected PLMN.
+
+The number of channels to be searched are 15 for T-GSM 380, 15 for T-GSM 410, 15 for GSM 450, 15 for GSM 480, 25 for GSM 710, 25 for GSM 750, 25 for T-GSM 810, 30 for GSM 850 Band, 30 for GSM 900, 15 for T-GSM 900 and 40 for DCS 1800 and PCS 1900.
+
+### 3.2.2 "Camp on any cell"
+
+If the MS cannot find a suitable cell, it attempts to camp on any acceptable cell and enter a "limited service state", as defined in subclause 3.7. An MS attempting to camp on any acceptable cell shall not scan for CPBCCH.
+
+There are various requirements that a cell must satisfy before being considered an acceptable cell to be camped on in "limited service state":
+
+- i) It should not be "barred" (see subclause 3.5.1);
+
+- ii) The radio path loss between MS and BTS must be below a threshold set by the PLMN operator. This is estimated as shown in subclause 3.6.
+
+## 3.3 Regional provision of service
+
+See 3GPP TS 23.122.
+
+## 3.4 Borders between registration areas
+
+If the MS is moving in a border area between registration areas, it might repeatedly change between cells of different registration areas. Each change of registration area would require an LR, which would cause a heavy signalling load and increase the risk of a paging message being lost. To prevent this, a "CELL\_RESELECT\_HYSTERESIS" (CRH) parameter is used. A cell in a different registration area is only selected if it is "better", in terms of the path loss criterion (see subclause 3.6), than all the cells in the current registration area by at least the value of CRH. The CRH parameter is broadcast as system information. As the value of CRH broadcast may be different on different cells, the CRH parameter to be used is that broadcast on the current serving cell. There is also a lower limit on the time interval between reselection of cells on different registration areas. Instead of CRH a GPRS MS uses a "GPRS\_CELL\_RESELECT\_HYSTERESIS" if provided.
+
+## 3.5 Barred cells and access control
+
+### 3.5.1 Barred cells
+
+The PLMN operator may decide not to allow MSs to camp on certain cells. (These cells may, for example, only be used for hand over traffic, i.e. calls which need to be handed over to other cells). Barred cell information is broadcast as system information to instruct MSs not to camp on these cells. The barred cell status may in fact change dynamically; hence the MS needs to regularly check the system information for this parameter.
+
+The barred status of a cell depends on the parameters CELL\_BAR\_ACCESS and CELL\_BAR\_QUALIFY, further described in 3GPP TS 45.008.
+
+If a cell is barred this applies both for cell selection and reselection.
+
+### 3.5.2 Prioritizing cells
+
+In general, cell prioritization is a means of encouraging MSs to select some suitable cells in preference to others. Since the priority comparison is only between suitable cells, prioritization does not affect coverage. Operators may prefer a certain type of cell not to be selected unless it is the only suitable type. For example, umbrella cells due to their large frequency reuse distance, or microcells because the MS could be travelling too fast for them.
+
+#### 3.5.2.1 For cell selection
+
+During cell selection (see subclause 3.2.1), a cell with low priority indication will only be selected if a suitable cell of normal priority cannot be found.
+
+#### 3.5.2.2 For cell reselection
+
+Cell prioritization can also be achieved during cell reselection by the use of the reselection parameters optionally broadcast. Cells are reselected on the basis of a parameter called C2 and the C2 value for each cell is given a positive or negative offset to encourage or discourage MSs to reselect that cell. A full range of positive and negative offsets is provided to allow the incorporation of this feature into already operational networks. Instead of C2 a GPRS MS uses the GPRS cell reselection parameter if provided.
+
+An MS supporting SoLSA with SoLSA subscription shall use the SoLSA cell re-selection parameters.
+
+### 3.5.3 Access control
+
+Due to problems in certain areas, Network Operators may decide to restrict access from some MSs (e.g., in case of congestion on the AGCH), and for this reason the access control mechanism is provided.
+
+At subscription one or more access control classes are allocated to the subscriber and stored in the SIM. The information providing all authorized classes is broadcast as system information (together with a bit indicating whether
+
+emergency calls may be made). This information is modified dynamically and therefore the MS has to check the system information before each attempt to access.
+
+The MS ignores the Access Control information when selecting a cell to camp on, i.e. it shall not reject a cell for camping on because access on that cell is not allowed.
+
+### 3.5.4 Forbidden LA for regional provision of service
+
+If the MS has received the cause "LA not allowed", it shall ignore this fact when selecting a cell to camp on, i.e. it shall not reject a cell for camping on because that cell is part of a LA where this cause has been received.
+
+### 3.5.5 Barred cell due to failed network authentication check
+
+If upper layers have determined that the network has failed an authentication check (3GPP TS 24.008), the MS shall treat this cell as if the barred status broadcasted in the system information is set and reselect another cell. The MS shall treat the cell as barred for a period equal to the MM timer T3212 minus 60 seconds if the MM authentication procedure was performed or equal to the GMM timer T3302 minus 60 seconds if the GMM authentication was performed (see 3GPP TS 24.008). If the timer T3212 or T3302 are disabled by the network a default value of 12 hours shall be used.
+
+## 3.6 Radio constraints
+
+The MS uses a "path loss criterion" parameter C1 to determine whether a cell is suitable to camp on. C1 depends on 4 parameters:
+
+- i) The received signal level (suitably averaged);
+- ii) The parameter RXLEV\_ACCESS\_MIN, which is broadcast as system information, and is related to the minimum signal that the operator wants the network to receive when being initially accessed by an MS;
+- iii) The parameter MS\_TXPWR\_MAX\_CCH, which is also broadcast as system information, and is the maximum power that an MS may use when initially accessing the network;
+- iv) The maximum power of the MS.
+
+The formula for determining C1 is given in 3GPP TS 45.008.
+
+Use of the parameter C1 enables the MS to determine whether communication is possible with the network in the absence of interference. However because of the possibility of interference degrading the communications, an additional safeguard is used. This is to monitor the success rate of the MS in decoding signalling blocks of the paging subchannel. If there is a downlink signalling failure, i.e. the success rate drops too low, this indicates probable interference on the downlink, and the MS attempts to find another suitable cell. Downlink signalling failure monitoring is specified in 3GPP TS 45.008.
+
+In order to optimize cell reselection, additional cell reselection parameters can be broadcast as system information of each cell. The cell reselection process employs a parameter C2 which depends on these parameters.
+
+The parameters used to calculate C2 are as follows:
+
+- i) CELL\_RESELECT\_OFFSET (see subclause 3.5.2.2);
+- ii) PENALTY\_TIME;
+
+When the MS places the cell on the list of the strongest carriers as specified in 3GPP TS 45.008, it starts a timer which expires after the PENALTY\_TIME. This timer will be reset when the cell is taken off the list. For the duration of this timer, C2 is given a negative offset. This will tend to prevent fast moving MSs from selecting the cell.
+
+- iii) TEMPORARY\_OFFSET;
+
+This is the amount of the negative offset described in (ii) above. An infinite value can be applied, but a number of finite values are also possible.
+
+The permitted values of these parameters and the way in which they are combined to calculate C2 are defined in 3GPP TS 45.008.
+
+Instead of the parameter C2, a GPRS MS applies the corresponding GPRS parameter if provided.
+
+An MS supporting SoLSA with SoLSA subscription shall use the SoLSA cell re-selection parameters.
+
+## 3.7 No suitable cell (limited service state)
+
+If the MS is unable to obtain normal service from a PLMN (see 3GPP TS 23.122), the MS attempts to camp on an acceptable cell, irrespective of its PLMN identity, so that emergency calls can be made or warning notifications can be received if necessary. To minimize the time taken to find new available PLMNs while maintaining battery life, discontinuous search schemes may be used, see 3GPP TS 22.011. Cell reselection takes place as normal, except that a zero dB value of CRH will be used.
+
+## 3.8 CTS fixed part selection
+
+See 3GPP TS 23.122
+
+# --- 4 Overall process structure
+
+## 4.1 Process goal
+
+The aim of the idle mode processes is to achieve the following conditions ("normal service state"):
+
+- a) The selected PLMN is one of the equivalent PLMNs;
+- b) The MS is camped on a suitable cell of the registration area on which the last successful LR was performed, and that cell has the highest value of C2 for any unbarred cell in that registration area;
+- c) The value of C2 for the MS is not lower than the value of C2 for any suitable cell in another registration area of an equivalent PLMN by more than the hysteresis value CRH.
+
+Instead of the parameter C2, a GPRS MS applies the corresponding GPRS parameter if provided.
+
+An MS supporting SoLSA with SoLSA subscription shall use the SoLSA cell re-selection parameters.
+
+Registration is not performed by MSs only capable of services which need no registration.
+
+There may be temporary conditions under which not all these are fully satisfied, e.g., during cell selection on a PLMN or while in the process of reselecting another cell. However, if the above cannot be satisfied for a certain period of time, the MS will normally enter a "limited service state" in which it will try to camp on an acceptable cell. In this state, only emergency calls and warning notifications are possible.
+
+## 4.2 States description
+
+Each of the processes of PLMN selection, cell selection and location registration can be described by a set of states. The overall state of the mobile is thus a composite of the states of the three processes. In some cases, an event which causes a change of state in one process may trigger a change of state in another process, e.g., camping on a cell in a new registration area triggers an LR request. The relationship between the processes is illustrated in figure 1 in 3GPP TS 23.122.
+
+In the event of any conflict between the diagrams and the text in this ETS, the text takes precedence.
+
+## 4.3 List of states
+
+### 4.3.1 List of states for the PLMN selection process
+
+See 3GPP TS 23.122.
+
+### 4.3.2 List of States for the cell selection process (figure 3)
+
+- C1 Normal Cell Selection - This is the process of initial cell selection, searching all RF channels.
+
+- C2 Stored List Cell Selection - This is the process of initial cell selection where BCCH carrier information (e.g. a BA list) for the selected PLMN is stored in the MS.
+- C3 Camped Normally - This is where the MS is camped on a cell of the registered PLMN and may be able to make and receive calls. (Whether or not the MS can make and receive calls depends on the state within the location registration process). The MS monitors received level and the system information and checks whether cell reselection is needed.
+- C4 Normal Cell Reselection - This is where the MS has determined that cell reselection is needed and an attempt is being made to reselect a new cell.
+- C5 Choose Cell - This is where the MS has returned to idle mode from "connected mode" and is choosing a suitable cell to camp on.
+- C6 Any Cell Selection - This is where the MS is unable to camp normally on any cell of the selected PLMN, or cannot obtain service because of certain responses to a location registration (LR) attempt. It is searching for a cell of any PLMN to camp on (so that emergency calls can be made and warning notifications can be received).
+- C7 Camped on any Cell - This is where the MS has camped on a cell irrespective of its PLMN identity, so that emergency calls can be made and warning notifications can be received.
+- C8 Any Cell Reselection - This is where the MS is attempting to reselect a cell, irrespective of PLMN identity.
+- C9 Choose Any Cell - This is where the MS is returning to idle mode, after having entered "connected mode" from the "camped on any cell" state to make an emergency call. It is attempting to find an acceptable cell to camp on.
+
+For detailed description of the behaviour in the above states see 3GPP TS 45.008.
+
+### 4.3.3 List of states for location updating
+
+See 3GPP TS 23.122.
+
+### 4.3.4 List of states for location registration
+
+See 3GPP TS 23.122.
+
+## 4.4 PLMN selection process
+
+### 4.4.1 Introduction
+
+See 3GPP TS 23.122.
+
+### 4.4.2 Registration on a PLMN
+
+An MS successfully registers on a PLMN if:
+
+- The MS has found a suitable cell of the PLMN to camp on; and
+- An LR request from the MS has been accepted in the registration area of the cell on which the MS is camped (see 3GPP TS 23.122).
+
+It should be noted that if registration is unsuccessful because no suitable cell could be found, the MS will have had to search at least the number, given in subclause 3.2.1, of the strongest RF channels (see subclause 3.2) and therefore all the available PLMNs will potentially have been detected. If registration is unsuccessful because of an LR failure or an LR rejection, the MS need not necessarily have already searched the number, given in subclause 3.2.1, of the strongest RF channels, and would need to do so before being in a position to display to the user all available PLMNs (see 3GPP TS 23.122).
+
+### 4.4.3 PLMN selection
+
+See 3GPP TS 23.122.
+
+A PLMN shall be understood to be received with high quality signal if the signal level is above -85 dBm.
+
+### 4.4.4 Abnormal cases
+
+See 3GPP TS 23.122.
+
+### 4.4.5 Roaming not allowed in this LA
+
+See 3GPP TS 23.122.
+
+## 4.5 Cell selection process
+
+Whenever a PLMN is selected, the MS attempts to find a suitable cell of that PLMN to camp on. Two methods of searching for a suitable cell are possible:
+
+- a) Normal cell selection ("Normal cell selection" state) - Here the MS has no prior knowledge of which RF channels are BCCH or CPBCCH carriers. It searches at least the number, given in subclause 3.2.1, of the strongest RF channels in descending order of received signal level to see which are BCCH or CPBCCH carriers. (If no BCCH or CPBCCH carriers have yet been found, searching will continue until at least one BCCH or CPBCCH carrier is found.). The first BCCH or CPBCCH carrier found which is from a suitable cell and on which there is a normal priority indication is taken and that cell is camped on. If at least the number, given in subclause 3.2.1, of the strongest RF channels have been tried and the only suitable cells found have low priority indication the MS shall camp on the strongest of these cells.
+- b) Stored list cell selection (optional) ("Stored list cell selection" state)- Here the MS has a list of the BCCH and CPBCCH carriers used by the PLMN. (This list may be derived by the MS from information gathered during previous selections of the PLMN). The BCCH and CPBCCH carriers in the list are searched in descending order of received signal level, and the first BCCH or CPBCCH carrier found which is from a suitable cell and on which there is a normal priority indication is taken, and that cell is camped on. If an MS decodes system information from a cell of the selected PLMN but is unable to camp on that cell, the BA of that cell shall be examined and any BCCH and CPBCCH carriers in the BA which are not in the list of BCCH or CPBCCH carriers to be searched shall be added to the list. If all these BCCH and CPBCCH carriers have been tried and the only suitable cells found have low priority indication, the MS shall camp on the strongest of these cells. When required to search for CPBCCH, the stored list cell selection is mandatory for CPBCCH carrier from the HPLMN.
+
+If no suitable cell is found using method b), method a) is then tried.
+
+An MS with GSM voice capability shall not search for CPBCCH carriers. An MS supporting GSM circuit-switched data without supporting GSM voice may search for CPBCCH carriers.
+
+NOTE: Since CPBCCH carriers are not transmitting continuously, another measurement algorithm than the one used for BCCH carriers must be followed when measuring signal strength of CPBCCH carriers (see 3GPP TS 45.008).
+
+While camped on a cell of the registered PLMN ("camped normally"), the MS may need to select a different cell ("normal cell reselection" state). The following events trigger a cell reselection:
+
+- i) The path loss criterion parameter C1 (see subclause 3.6) indicates that the path loss to the cell has become too high;
+- ii) There is a downlink signalling failure (subclause 3.6);
+- iii) The cell camped on (current serving cell) has become barred;
+- iv) There is a better cell (in terms of the path loss criterion C2) in the same registration area, or a much better cell in another registration area of an equivalent PLMN (using the CRH parameter, subclause 3.4);
+- v) A random access attempt is still unsuccessful either after "Max retrans" repetitions; "Max retrans" being a parameter broadcast on control channel, or in case the time given for the packet access procedure expires before the mobile station receives any response from the network;
+- vi) Upper layers have determined that the network has failed an authentication check (see subclause 3.5.5).
+
+A GPRS MS in Ready state applies the READY\_STATE CELL RESELECTION HYSTERESIS together with the path loss criterion when reselecting the cell within the registration area. The GPRS MS in Ready state shall inform the network about cell reselection within the registration area by the cell update procedure. The network may control cell reselection of a GPRS MS in Ready state (see 3GPP TS 43.064).
+
+Instead of the parameter C2, a GPRS MS applies the corresponding GPRS parameter if provided. If this GPRS parameter is provided the cell shall also broadcast a list BA(GPRS) indicating BCCH or CPBCCH carriers to be monitored by GPRS MSs for cell re-selection purpose.
+
+An MS supporting SoLSA with SoLSA subscription shall use the SoLSA cell re-selection parameters.
+
+The MS will then reselect a new cell in order to fulfil the process goal (see subclause 4.1).
+
+Before camping on the cell after re-selection, the MS shall attempt to decode the full set of system information. The MS shall check that the parameters affecting cell re-selection are unchanged. If a change is detected the MS shall check if the cell re-selection criterion is still valid using the changed parameters. If the cell selection criteria are still valid, the MS shall camp on the cell. If they are not still valid, the MS shall repeat this process for the cell with the next highest value of C2 or corresponding GPRS parameter or SoLSA parameters, respectively.
+
+Once the MS has re-tuned to the chosen cell, it shall monitor its paging subgroup (if known) for that cell. If the MS and the cell support group or broadcast calls, it shall also monitor the notification channel. A GPRS MS shall monitor the relevant GPRS control channel(s). If the MS receives a page before having decoded the relevant system information for the new cell, the MS shall store the page and respond, if permitted, once the relevant system information has been decoded. If not permitted, no page response shall be made.
+
+When the MS leaves "connected mode" (e.g., after a call), and returns to idle mode, a cell must be chosen ("choose cell" state) as soon as possible (e.g., to allow a new call to be made). The chosen cell will not necessarily be the same cell as the MS was camped on when the call started e.g., if the MS moved a significant distance while the call was in progress. Two cases are distinguished in 3GPP TS 45.008, for which the algorithm is slightly different:
+
+- a) Normal case - The call is terminated, either because the user (or network) has terminated the call, or because a radio link failure has occurred and call re-establishment is not being attempted.
+- b) Call re-establishment - A radio link failure has occurred and a call re-establishment is being attempted. (The MS returns to idle mode to start the call re-establishment attempt and needs to select a new cell on which to make the attempt as soon as possible in order to minimize the interruption to the call).
+
+If no suitable cell is found by either the stored list cell selection, normal cell reselection or choose cell tasks (all of which use a limited search), the normal cell selection task (which searches all RF channels for a suitable cell) is entered.
+
+If no suitable cell is found by the normal cell selection task, or if there is no valid SIM in the MS, the MS attempts to find an "acceptable cell" on which it may camp so that emergency calls may be made and warning notifications may be received ("any cell selection" state). The MS ignores the PLMN information when selecting an acceptable cell, and no attempt at location registration is made. This task is also entered if an LR reject is received with one of the following cause values:
+
+- "IMSI unknown in HLR" (only for non-GPRS MS as this impacts only the non-GPRS update state, MSs capable of GPRS and non-GPRS services take a cell selection state according to the outcome of the routing area update);
+- "Illegal MS";
+- "illegal ME";
+- "PLMN not allowed" (However, this will trigger a new PLMN selection if the MS is in automatic mode);
+- "GPRS not allowed" (only for MS capable of GPRS only, where this will trigger a new PLMN selection if the MS is in automatic mode; MSs capable of GPRS and non-GPRS services take a cell selection state according to the outcome of location updating as "GPRS not allowed" has only impact on the GPRS update status).
+
+NOTE: Some cause values will lead the mobile station to consider the SIM as invalid, see 3GPP TS 24.008.
+
+If an acceptable cell is found, the MS camps on it ("Camped on any cell" state). If one of the cell reselection trigger events (i) to (v) above occurs, the MS attempts to find a new acceptable cell to camp on ("any cell reselection" state) but using a zero dB value of CRH. If no acceptable cell can be found, the "any cell selection" task is re-entered.
+
+If while camped on an acceptable cell:
+
+- i) an emergency call origination is made, the MS enters a connected mode and at the end of the call, chooses an acceptable cell ("choose any cell" state) so that it is ready for the next emergency call origination;
+- ii) a warning notification is received, the MS continues to perform cell reselection to an acceptable cell.
+
+In all cases, if a new PLMN is selected and there is a valid SIM in the MS, the MS searches for a suitable cell of that PLMN. However, if the MS has recently searched the strongest RF channels while a previous PLMN was selected, it may already have information about other PLMNs.
+
+The user may request a search of RF channels to determine which PLMNs are available. This search shall be done in such a way as to minimize interruptions to the MS's monitoring of its paging subchannel.
+
+## 4.6 Location registration process
+
+See 3GPP TS 23.122.
+
+## 4.7 Service indication
+
+See 3GPP TS 23.122.
+
+## 4.8 BCCH allocation broadcasting and storage
+
+The BCCH allocation is the list of BCCH or CPBCCH carriers in use by a given PLMN (or co-operating PLMNs) in a given geographical area. (It indicates the RF channels that the MS is required to monitor while camped on a cell of that PLMN.) It is broadcast in the system information messages, and is referred to as the BA(BCCH).
+
+When the MS is first switched on in a PLMN, and has no knowledge of which RF channels are BCCH or CPBCCH carriers of that PLMN, it has to search the strongest RF channels in order to find which are BCCH or CPBCCH carriers. It then has to determine which BCCH or CPBCCH carriers belong to the selected PLMN. Once it has found a BCCH or CPBCCH carrier of the selected PLMN, it can read the BA(BCCH). It then knows which RF channels to monitor for cell selection and reselection purposes.
+
+Cells supporting GPRS may broadcast a list BA(GPRS) as system information. It indicates the BCCH or CPBCCH carriers to be monitored by a GPRS MS for cell re-selection.
+
+Whilst switched on in the PLMN, the MS can gain knowledge of the preferable carriers to use in subsequent cell selections in that PLMN. This knowledge may come from previously decoded BA(BCCH)s and from transmitted information from the network.
+
+When the MS switches off, it has the option of storing the last known BA(BCCH) in a non volatile store so that on a subsequent switch on in that PLMN, it does not need to search to find the BA(BCCH), and so can camp on a cell more quickly. If the BA(BCCH) is stored in the (U)SIM, it shall be stored in the format specified either in 3GPP TS 51.011 (if the mobile station supports the SIM) or 3GPP TS 31.102 (if the mobile station supports the USIM). Any other information used by the MS in cell selection shall be stored in a non volatile store on the ME.
+
+The BA(BCCH) may or may not be the total list of BCCH or CPBCCH carriers in use throughout the PLMN coverage area. For example there may be differences in different geographical areas, and there may be "umbrella cells" which are only used for hand over traffic and hence are not to be camped on.
+
+**NOTE:** The PLMN operator cannot expect the ME to store the BCCH or CPBCCH carrier frequency of the serving cell in the SIM unless the BA(BCCH) includes the BCCH or CPBCCH carrier frequency on which it is broadcast.
+
+A stored BA(BCCH) is not necessarily valid when the MS is switched on again e.g., if the system operator has made a change in BA(BCCH) or if the MS is switched on in a different geographical area. In these cases, the MS may not find a suitable cell for camping on using the stored BA(BCCH). However, the MS may use other stored information to find a suitable cell before searching all the strongest RF channels.
+
+It should also be noted that the BA(BCCH) only applies to the PLMN on which it was received. If a new PLMN is selected, only a BA(BCCH) previously obtained from that PLMN should be used.
+
+There is another BCCH or CPBCCH carrier list, called BA(SACCH), which is sent on the SACCH when in connected mode. This contains the list of BCCH or CPBCCH carriers to be monitored by the MS for hand over purposes. The
+
+BA(BCCH) and BA(SACCH) need not necessarily be the same. For example, the BA(SACCH) might contain umbrella cells, or the BCCH or CPBCCH carrier of the serving cell might be omitted.
+
+If the MS stores a BA list in the SIM, and there is a valid stored LAI, the BA list must be of the PLMN indicated by the stored LAI.
+
+## 4.9 Pageability of the mobile subscriber
+
+See 3GPP TS 23.122.
+
+## 4.10 MM Restart procedure
+
+See 3GPP TS 23.122 .
+
+# --- 5 Group receive mode
+
+## 5.1 General description
+
+The purpose of the group receive mode process is for a MS to determine the most suitable cell while listening to a group or broadcast call.
+
+There are various requirements that a cell must satisfy before an MS can perform group receive mode on it:
+
+- i) The radio path loss between MS and BTS must be below a threshold set by the PLMN operator. This is estimated as shown in subclause 3.6. That means that the cell is suitable for transmission and reception.
+- ii) It should not be "barred" (see subclause 3.5.1);
+- iii) The NCC of the PLMN should be permitted;
+
+The choice of a cell is based on the C2 criterion, as defined in 3GPP TS 45.008. . When in group receive mode on a cell the MS regularly looks to see if there is a better cell in terms of the cell reselection criterion C2, as defined in 3GPP TS 45.008. C2 is determined by the MS from reception measurements on the BCCH frequency on the cell and reselection parameters relative to the cell. The reselection parameters are the same as those used in idle mode.
+
+If there is a better cell which is suitable, the better cell is selected. (This is called "cell reselection in group receive mode").
+
+The switching from idle or dedicated or group transmit mode to group receive mode is controlled by the Radio Interface Layer 3 protocols, see 3GPP TS 44.018.
+
+If no suitable cell can be found the MS immediately returns to idle mode by choosing a cell like releasing a dedicated channel (see 3GPP TS 45.008).
+
+## 5.2 Requirements and technical solutions
+
+### 5.2.1 Network provisions
+
+For group and broadcast calls, the network provides a BA list in the SI TYPE 5, 5bis or 5ter message on the SACCH of the channel used for the group or broadcast call. The BA list indicates the BCCH carriers of the surrounding cells that MSs engaged in the call should monitor. The list shall include the cell on which it is sent. The cells in the list may belong to different PLMNs.
+
+The network also provides the SI TYPE 6 message including an NCC permitted information element on the SACCH of the channel used for the group or broadcast call.
+
+The network shall provide in SI TYPE 10 messages the necessary information for computation of the cell reselection criterion for all neighbour cells as given by SI TYPE 5, 5 bis and /or 5ter.
+
+### 5.2.2 Group receive mode cell monitoring
+
+A MS in group receive mode shall perform synchronization, identification and receive signal strength measurements of the BCCH carriers in the BA(SACCH) list of BCCH frequencies which was provided by the network in the serving cell. The regularity for performing synchronization and identification of the BCCH carriers shall be performed with a regularity as specified in 3GPP TS 45.008 for a MS in dedicated mode. The regularity of performing receive signal strength measurements of the BCCH carriers shall be as specified in 3GPP TS 45.008 for a MS in idle mode.
+
+As long as no BA(SACCH) list is available on the SACCH, the last received BA(BCCH) list of the current cell shall be used instead if available.
+
+The MS does not have to monitor cells for which NCC is not permitted. The NCC permitted information is provided on the SACCH of the current cell. As long as no NCC permitted information is available on the SACCH, the last received NCC permitted information on the BCCH of the current cell shall be used instead if available.
+
+The MS must also read the parameters affecting cell reselection of the surrounding cells. These parameters are:
+
+- MS txpwr max cch;
+- rxlev access min;
+- cell reselect offset;
+- temporary offset;
+- penalty time;
+- location identity.
+
+The MS receives this information in SI TYPE 10 messages on the SACCH, however if the necessary information for a neighbour cell is not available, the MS shall get the information from the BCCH of that neighbour cell.
+
+The MS shall attempt to decode this information within 15s after there are less than six stronger suitable cells and the MS is allowed to discard up to 6 speech frames during this period. The MS shall attempt to update the information at least every five minutes.
+
+If ciphering is not used in the call then, before selecting a cell in group receive mode the MS must have read the information which is presented in SI TYPE 1 and 3 messages transmitted in the target cell, or have received in the serving cell valid information relating to the target cell obtained from a SI TYPE 10bis, SI TYPE 10ter, or VGCS Neighbour Cell Information message. SI TYPE 3 information shall override information received in SI10.
+
+If ciphering is used in the call then, before selecting a cell in group receive mode the MS must have read the information which is presented in SI TYPE 3 messages transmitted in the target cell and either:
+
+- have received in the serving cell valid information relating to the target cell obtained from a SI TYPE 10bis, SI TYPE 10ter, or VGCS Neighbour Cell Information message, or
+- have read the information which is presented in SI TYPE 1 messages transmitted in the target cell.
+
+On this basis, the MS determines which of the cells in the list are suitable and computes their reselection criterion, and decides on its own whether one of the surrounding cells should be selected instead of the current one, as described in the next subclause.
+
+The procedures above do not consider whether the cell supports the call or not.
+
+To perform cell change, the MS shall at least have performed measurements on cells of the BA-list received and read the corresponding BSIC.
+
+### 5.2.3 Group receive mode cell change
+
+Either of the following events trigger a cell change by a MS in group receive mode:
+
+- (i) The path loss parameter C1 indicates that the path loss to the serving cell has become too high.
+- (ii) There is a radio link time-out.
+- (iii) There is a better cell (in terms of the criterion C2) in the same LA, or a much better cell in another LA (using CRH parameter, subclause 3.4) and with NCC permitted.
+
+After cell change, the MS either
+
+- leaves the group receive mode and goes to idle mode in order to establish a dedicated connection with the network to perform a location update if the cell belongs to a new LA
+- detects that the selected cell does not belong to an equivalent PLMN and therefore leaves the group receive mode and goes to idle mode;
+- detects that no NCH is present and therefore leaves the group receive mode and goes to idle mode;
+- reads the NCH but does not receive any notification message for the current group or broadcast call and therefore leaves the group receive mode and goes to idle mode;
+- reads the NCH and receives a notification message for the current group or broadcast call with the related channel position. If the channel is found, the MS changes to it and stays in group receive mode;
+- reads the NCH and receives a notification message for the current group or broadcast call without information on the related channel position. The MS leaves the group receive mode and goes to idle mode in order to establish a dedicated connection with the network to become informed on the related channel position.
+- moves directly to the group channel, if it had valid information describing the location of the group call which was received in the old cell.
+
+During these procedures, the MS may not be able to listen to the group or broadcast call, in which case it should mute the downlink.
+
+For all procedures, which require that the MS leaves group receive mode, the MS goes to idle mode by choosing a cell like releasing a dedicated channel (see 3GPP TS 45.008).
+
+### 5.2.4 Uplink access in group calls
+
+A MS assigned the uplink for the user to talk switches to group transmit mode.
+
+It thus performs synchronisation, identification and measurements of the BCCH carriers according to the BA(SACCH) list as well as radio link measurements and reporting and is subject to hand over control from the network as for dedicated mode.
+
+# --- 5a Broadcast/multicast receive mode
+
+## 5a.1 General description
+
+The purpose of the broadcast/multicast receive mode process is for a MS to determine the most suitable cell while listening to an MBMS session. The broadcast/multicast receive mode is a substate of packet idle mode, and can only be entered by mobile stations that are GPRS attached.
+
+If no suitable cell can be found the MS immediately returns to packet idle mode.
+
+## 5a.2 Requirements and technical solutions
+
+### 5a.2.1 Network provisions
+
+If the PBCCH is not allocated in the serving cell, the necessary information for the computation of the cell reselection criterion for all neighbour cells in the neighbour cell list shall not be read by the mobile station from the system information of the neighbour cells. Instead, this information shall be provided by the network (see 3GPP TS 44.018 and/or 3GPP TS 44.060).
+
+NOTE: If the PBCCH is allocated in the cell, this information is read by the MS from PSI TYPE 3 messages.
+
+### 5a.2.2 Broadcast/multicast receive mode cell monitoring
+
+The MS shall not read the parameters affecting cell reselection from the BCCH of the surrounding cells. Instead, this information shall be provided by the network. If the necessary information for a neighbour cell has not been received after entering broadcast/multicast receive mode, the MS shall use the the information read from the BCCH or PBCCH of that neighbour cell while in packet idle mode or, if not available, default parameters.
+
+If the information is not available for a suitable cell within 30 seconds after it has become one of the six stronger cells, the mobile station shall read this information from the BCCH of the neighbouring cell. The MS is allowed to interrupt the reception of the MBMS session during this period. The MS shall not attempt to perform periodic updates of this information while in broadcast/multicast receive mode.
+
+The MS determines which of the cells in the list are suitable and computes their reselection criterion, and decides on its own whether one of the surrounding cells should be selected instead of the current one. In computing the cell reselection criterion, the mobile station shall obey the intra-RAT and inter-RAT cell reselection algorithms defined for the GMM Ready state (see 3GPP TS 45.008).
+
+To perform cell change, the MS shall at least have performed measurements on cells of the BA(GPRS) list and read the corresponding BSIC.
+
+### 5a.2.3 Broadcast/multicast receive mode cell change
+
+Either of the following events trigger a cell change by a MS in broadcast/multicast receive mode:
+
+- (i) The pass loss parameter C1 indicates that the path loss to the serving cell has become too high.
+- (ii) There is a better cell (in terms of the criterion C2 or of the GPRS cell reselection criterion) in the same LA/RA, or a much better cell in another LA/RA and with NCC permitted.
+
+After cell change, the MS either
+
+- leaves the broadcast/multicast receive mode and goes to packet idle mode in order to establish a dedicated connection with the network to perform a location update or routing area update if the cell belongs to a new LA/RA;
+- detects that the selected cell does not belong to the MBMS Service Area and therefore leaves the broadcast/multicast receive mode and goes to packet idle mode;
+- detects that the selected cell does not belong to an equivalent PLMN and therefore leaves the broadcast/multicast receive mode and goes to packet idle mode;
+
+During these procedures, the MS may not be able to listen to the broadcast or multicast session.
+
+If the mobile station has received information about the location of the p-t-m bearer in the cell that it has reselected to, the mobile station can resume the reception of the MBMS session without the need to complete the acquisition of the system information.
+
+# 6 Tables and figures
+
+![Cell Selection State diagram showing the flow between Normal cell selection, Stored list cell selection, Camped normally, Normal cell re-selection, Any cell selection, Camped on any cell, and various modes like Connected mode and Choose cell.](a3472689858b068ef469213682965325_img.jpg)
+
+Go here whenever a new PLMN is selected
+
+```
+
+stateDiagram-v2
+    [*] --> 1 : Go here whenever a new PLMN is selected
+    1 --> 2 : No BA list stored for PLMN
+    1 --> 1 : BA list stored for PLMN
+    2 --> Normal cell selection
+    1 --> Stored list cell selection
+    Normal cell selection --> 2 : No suitable cell found
+    Normal cell selection --> Camped normally : Suitable cell found
+    Stored list cell selection --> Normal cell selection : No suitable cell found
+    Stored list cell selection --> Camped normally : Suitable cell found
+    Camped normally --> Connected mode (1) : Leave idle mode
+    Camped normally --> Normal cell re-selection : Trigger for cell reselection
+    Connected mode (1) --> Choose cell : Return to idle mode
+    Choose cell --> Normal cell selection : No suitable cell found
+    Choose cell --> Camped normally : Suitable cell found
+    Choose cell --> 1 : 'IMSI unknown', 'Illegal MS', 'PLMN not allowed'
+    Normal cell re-selection --> Camped normally : Suitable cell re-selected
+    Normal cell re-selection --> 2 : No suitable cell found
+    Any cell selection --> 1 : SIM inserted
+    Any cell selection --> 2 : No cell found
+    Any cell selection --> Camped on any cell (3) : Cell found
+    Camped on any cell (3) --> Connected mode (2) : Leave Idle mode
+    Camped on any cell (3) --> Any cell re-selection : Cell re-selection triggered
+    Connected mode (2) --> Choose any cell : Return to idle mode
+    Choose any cell --> Any cell selection : No cell found
+    Choose any cell --> Camped on any cell (3) : Cell found
+    Choose any cell --> 2 : Cell found on selected PLMN
+    Any cell re-selection --> Camped on any cell (3) : Cell re-selected
+    Any cell re-selection --> Any cell selection : No cell found
+  
+```
+
+Cell Selection State diagram showing the flow between Normal cell selection, Stored list cell selection, Camped normally, Normal cell re-selection, Any cell selection, Camped on any cell, and various modes like Connected mode and Choose cell.
+
+NOTE 1: To make or receive call
+
+NOTE 2: To make an emergency call
+
+NOTE 3: Reception of warning notifications are possible
+
+In any state, a new PLMN selection causes an exit to 1 if a valid SIM is present in the MS
+
+Go to 3 if no valid SIM in MS
+
+**Figure 3: Cell Selection State diagram**
+
+# Annex A (informative): Change history
+
+| SMG#          | SPEC   | CR   | R<br>E<br>V | PHASE | VERS  | SUBJECT                                                                                       | CAT | NEW_VERS | WORKITEM              |
+|---------------|--------|------|-------------|-------|-------|-----------------------------------------------------------------------------------------------|-----|----------|-----------------------|
+| S29           | 03.22  | A036 | 1           | R98   | 7.0.0 | GSM 400 spectrum update                                                                       | F   | 7.1.0    | GSM400                |
+| S30           | 03.22  | A041 |             | R99   | 8.0.0 | Clarification of SoLSA exclusive cells                                                        | A   | 8.1.0    | SoLSA                 |
+| S30           | 03.22  | A045 | 1           | R99   | 8.0.0 | Clarification of SoLSA exclusive cells                                                        | A   | 8.1.0    | SoLSA                 |
+| S30bis        | 03.22  | A046 |             | R99   | 8.1.0 | COMPACT Cell Selection part 2                                                                 | B   | 8.2.0    | EDGE                  |
+| S30bis        | 03.22  | A043 | 2           | R99   | 8.1.0 | COMPACT Cell Selection part 1                                                                 | B   | 8.2.0    | EDGE                  |
+|               | 03.22  |      |             |       | 8.2.0 | Editorial correction to headers                                                               |     | 8.2.1    |                       |
+| S31           | 03.22  | A048 |             | R99   | 8.2.1 | Removal of CN procedures from 03.22                                                           | F   | 8.3.0    | TEI                   |
+| <b>GERAN#</b> |        |      |             |       |       | September 2000 - 3G Release 4                                                                 |     |          |                       |
+| G01           | 03.22  | A049 | 1           | R00   | 8.3.0 | CR 03.22-A049 rev 1 Check selected cell deduced by SI10 information with SI3 ones (Release 4) | F   | 4.0.0    | ASCI                  |
+| G01           | 43.022 | A050 |             | R00   | 8.3.0 | CR 03.22-A050 GSM 700 spectrum update (Release 4)                                             | B   | 4.0.0    | GSM 700               |
+| October 2000  |        |      |             |       | 4.0.0 | GSM references revert to pre-Release-4 spec number format.                                    |     | 4.0.1    |                       |
+| G02           | 43.022 | 001  | 1           | Rel-4 | 4.0.1 | Mandatory usage of SYSTEM INFORMATION TYPE 10 messages for VGCS and VBS                       | C   | 4.1.0    | ASCI                  |
+|               |        |      |             |       | 4.1.0 | Front page layout correction                                                                  |     | 4.1.1    |                       |
+| January 2001  |        |      |             |       |       |                                                                                               |     |          |                       |
+| G03           | 43.022 | 002  |             | Rel-4 | 4.1.1 | Removal of Anonymous Access                                                                   | A   | 4.2.0    | GPRS                  |
+| June 2001     |        |      |             |       |       |                                                                                               |     |          |                       |
+| G05           | 43.022 | 003  | 1           | Rel-4 | 4.2.0 | Remaining errors from the split                                                               | A   | 4.3.0    | TEI                   |
+| G05           | 43.022 | 004  | 1           | Rel-4 | 4.2.0 | Clarifications due to equivalent PLMN                                                         | A   | 4.3.0    | GSM/UMTS interworking |
+| June 2002     |        |      |             |       |       |                                                                                               |     |          |                       |
+| G10           | 43.022 | 007  | 1           | Rel-4 | 4.3.0 | Removal of CBQ2                                                                               | A   | 4.4.0    | COMPACT               |
+| G10           | 43.022 | 008  | 1           | Rel-5 | 4.3.0 | Removal of CBQ2                                                                               | A   | 5.0.0    | COMPACT               |
+| August 2002   |        |      |             |       |       |                                                                                               |     |          |                       |
+| G11           | 43.022 | 011  |             | Rel-5 | 5.0.0 | MS behaviour in case of a failed authentication of the network                                | A   | 5.1.0    | TEI                   |
+
+| <b>Change history</b> |                   |                 |           |            |                                                                                |            |            |  |
+|-----------------------|-------------------|-----------------|-----------|------------|--------------------------------------------------------------------------------|------------|------------|--|
+| <b>Date</b>           | <b>TSG GERAN#</b> | <b>TSG Doc.</b> | <b>CR</b> | <b>Rev</b> | <b>Subject/Comment</b>                                                         | <b>Old</b> | <b>New</b> |  |
+| 2002-11               | 12                | GP-023318       | 009       | 2          | Implementation of new frequency ranges                                         | 5.1.9      | 6.0.0      |  |
+| 2004-11               | 22                | GP-042456       | 014       |            | Removal of PTM-M                                                               | 6.0.0      | 6.1.0      |  |
+| 2005-01               | 23                | GP-050592       | 015       | 3          | Introduction of MBMS                                                           | 6.1.0      | 6.2.0      |  |
+| 2005-01               | 23                | GP-050491       | 016       | 1          | Correction of references                                                       | 6.1.0      | 6.2.0      |  |
+| 2005-04               | 24                | GP-050773       | 018       |            | GSM 750 corrections                                                            | 6.2.0      | 6.3.0      |  |
+| 2005-04               | 24                | GP-050774       | 019       |            | Introduction of GSM 710                                                        | 6.3.0      | 7.0.0      |  |
+| 2005-06               | 25                | GP-051713       | 021       | 1          | Introduction of T-GSM 810                                                      | 7.0.0      | 7.1.0      |  |
+| 2006-09               | 31                | GP-061610       | 0022      | 1          | Clarification on mobile behaviour in "limited service" state                   | 7.1.0      | 7.2.0      |  |
+| 2006-09               | 31                | GP-061881       | 0023      | 1          | The failure of random access attempt                                           | 7.1.0      | 7.2.0      |  |
+| 2007-08               | 35                | GP-071519       | 0024      | 4          | TCRT: Enhanced Cell Reselection for VGCS                                       | 7.2.0      | 8.0.0      |  |
+| 2008-05               | 38                | GP-080584       | 0025      |            | TCRT: Correction to requirements for Cell Reselection for ciphered group calls | 8.0.0      | 8.1.0      |  |
+| 2009-12               | 44                |                 |           |            | Release 9 version                                                              | 8.1.0      | 9.0.0      |  |
+| 2010-03               | 45                | GP-100591       | 0027      | 1          | Reception of PWS warning notifications in an acceptable cell                   | 9.0.0      | 9.1.0      |  |
+| 2010-09               | 47                | GP-101319       | 0031      |            | Correction to "Camped on any cell" state                                       | 9.1.0      | 9.2.0      |  |
+| 2011-03               | 49                |                 |           |            | Release 10 version                                                             | 9.2.0      | 10.0.0     |  |
+| 2012-09               | 55                |                 |           |            | Release 11 version                                                             | 10.0.0     | 11.0.0     |  |

marked/Rel-11/43_series/43052/raw.md

@@ -0,0 +1,952 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                      |    |
+|--------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                       | 6  |
+| 1 Scope.....                                                                         | 7  |
+| 2 References.....                                                                    | 7  |
+| 3 Definitions and abbreviations .....                                                | 8  |
+| 3.1 Definitions.....                                                                 | 8  |
+| 3.2 Abbreviations .....                                                              | 8  |
+| 4 Main concepts of the CTS radio interface .....                                     | 8  |
+| 4.1 Beacon concept .....                                                             | 8  |
+| 4.2 Adaptive Frequency Allocation (AFA) concept .....                                | 8  |
+| 4.3 Total Frequency Hopping (TFH) concept.....                                       | 9  |
+| 5 Radio Transmission and Reception.....                                              | 9  |
+| 5.1 Frequency Band and Channel Arrangement .....                                     | 9  |
+| 5.2 Receiver Characteristics.....                                                    | 9  |
+| 5.2.1 CTS-MS characteristics.....                                                    | 9  |
+| 5.2.2 CTS-FP characteristics .....                                                   | 9  |
+| 5.3 Transmitter Characteristics .....                                                | 10 |
+| 5.3.1 CTS-MS characteristics.....                                                    | 10 |
+| 5.3.2 CTS-FP characteristics .....                                                   | 10 |
+| 5.4 CTS transmitter / receiver performance .....                                     | 10 |
+| 6 Modulation and Raw Data Rates .....                                                | 10 |
+| 7 Channel Coding and Interleaving .....                                              | 10 |
+| 8 Time Slots and TDMA-Frames.....                                                    | 10 |
+| 9 Bursts .....                                                                       | 11 |
+| 10 Logical Channels.....                                                             | 11 |
+| 10.1 CTS Beacon Channel (CTSBCH).....                                                | 11 |
+| 10.1.1 CTSBCH format.....                                                            | 11 |
+| 10.1.2 CTSBCH timing .....                                                           | 12 |
+| 10.1.3 CTSBCH radio frequency channel.....                                           | 12 |
+| 10.1.4 CTSBCH-SB information .....                                                   | 12 |
+| 10.2 CTS Access Request Channel (CTSARCH).....                                       | 12 |
+| 10.2.1 CTSARCH format.....                                                           | 12 |
+| 10.2.2 CTSARCH timing .....                                                          | 12 |
+| 10.2.3 CTSARCH radio frequency channel.....                                          | 13 |
+| 10.2.4 CTSARCH information.....                                                      | 13 |
+| 10.3 CTS Access Grant Channel (CTSAGCH) .....                                        | 13 |
+| 10.3.1 CTSAGCH format.....                                                           | 13 |
+| 10.3.2 CTSAGCH timing .....                                                          | 13 |
+| 10.3.3 CTSAGCH radio frequency channel.....                                          | 13 |
+| 10.3.4 CTSAGCH information.....                                                      | 14 |
+| 10.4 CTS Paging Channel (CTSPCH) .....                                               | 14 |
+| 10.4.1 CTSPCH format .....                                                           | 14 |
+| 10.4.2 CTSPCH timing.....                                                            | 14 |
+| 10.4.3 CTSPCH radio frequency channel .....                                          | 14 |
+| 10.4.4 CTSPCH information.....                                                       | 14 |
+| 10.5 SACCH.....                                                                      | 14 |
+| 10.6 FACCH.....                                                                      | 15 |
+| 10.7 TCH.....                                                                        | 15 |
+| 10.8 Mapping of the Logical Channels onto Physical Channels.....                     | 15 |
+| 10.8.1 Mapping in time of the logical channels onto the physical channels .....      | 15 |
+| 10.8.2 Mapping in frequency of the logical channels onto the physical channels ..... | 16 |
+| 10.8.3 Permitted Channel Combinations.....                                           | 16 |
+
+|                               |                                                                                    |           |
+|-------------------------------|------------------------------------------------------------------------------------|-----------|
+| 11                            | Lower Layer Procedures .....                                                       | 17        |
+| 11.1                          | CTSBCH transmission .....                                                          | 17        |
+| 11.2                          | CTSBCH timeslot management .....                                                   | 17        |
+| 11.3                          | CTSBCH-FB detection .....                                                          | 17        |
+| 11.4                          | CTSBCH-SB decoding .....                                                           | 17        |
+| 11.5                          | Discontinuous transmission (DTX).....                                              | 17        |
+| 11.6                          | Interference measurements.....                                                     | 17        |
+| 11.7                          | MS timing offset measurements.....                                                 | 18        |
+| 12                            | Radio Resource Management Procedures.....                                          | 18        |
+| 12.1                          | Radio Resources management states.....                                             | 18        |
+| 12.2                          | General procedures.....                                                            | 18        |
+| 12.2.1                        | Initial synchronization of a CTS-MS and CTS-FP.....                                | 18        |
+| 12.2.2                        | Frequency management.....                                                          | 18        |
+| 12.2.2.1                      | Interference measurements exchange .....                                           | 19        |
+| 12.2.2.2                      | Adaptive Frequency Allocation (AFA) algorithm.....                                 | 19        |
+| 12.2.2.3                      | AFA / TFH interworking .....                                                       | 19        |
+| 12.2.2.4                      | CTSBCH frequency selection.....                                                    | 19        |
+| 12.2.3                        | CTSBCH-SB information .....                                                        | 20        |
+| 12.2.4                        | Control of CTS-FP service range .....                                              | 20        |
+| 12.2.5                        | CTS-FP selection.....                                                              | 20        |
+| 12.3                          | RR Idle state procedures .....                                                     | 20        |
+| 12.3.1                        | CTSBCH monitoring.....                                                             | 20        |
+| 12.3.2                        | Alive check.....                                                                   | 20        |
+| 12.3.3                        | Establishment of a dedicated RR connection .....                                   | 20        |
+| 12.3.3.1                      | Timeslot assignment for dedicated connection.....                                  | 20        |
+| 12.3.3.2                      | CTS-MS initiated RR connection establishment .....                                 | 21        |
+| 12.3.3.2.1                    | Non-hopping access procedure .....                                                 | 21        |
+| 12.3.3.2.2                    | Hopping access procedure.....                                                      | 21        |
+| 12.3.3.3                      | CTS-FP initiated RR connection establishment .....                                 | 21        |
+| 12.3.4                        | CTSBCH failure detection .....                                                     | 22        |
+| 12.4                          | RR Active state procedures.....                                                    | 22        |
+| 12.4.1                        | Radio link failure detection .....                                                 | 22        |
+| 12.4.2                        | RF power control.....                                                              | 22        |
+| 12.4.3                        | Intracell handover .....                                                           | 22        |
+| 12.4.4                        | Channel release.....                                                               | 22        |
+| <b>Annex A (informative):</b> | <b>GSM backwards compatibility issues.....</b>                                     | <b>23</b> |
+| A.1                           | Reasons for possible impact of a CTS-FP on a GSM-MS in the PLMN.....               | 23        |
+| A.1.1                         | Power measurement of BCCH carrier.....                                             | 23        |
+| A.1.1.1                       | Power on CTS-FP beacon frequency seen by the GSM-MS in cell selection.....         | 23        |
+| A.1.1.2                       | Power on CTS-FP hopping frequencies seen by the GSM-MS in cell selection .....     | 24        |
+| A.1.2                         | Synchronisation of a GSM-MS .....                                                  | 24        |
+| A.2                           | Scenario 1: PLMN and CTS-GFL have no common frequency in whole coverage area ..... | 24        |
+| A.2.1                         | Cell Selection .....                                                               | 24        |
+| A.2.1.1                       | GSM-MS has no BA list stored on the SIM.....                                       | 24        |
+| A.2.1.2                       | GSM-MS has a stored BA list on the SIM (optional) .....                            | 24        |
+| A.2.2                         | Cell reselection.....                                                              | 25        |
+| A.2.3                         | Handover .....                                                                     | 25        |
+| A.3                           | Scenario 2: PLMN and CTS-GFL have locally no common frequency .....                | 25        |
+| A.3.1                         | Cell Selection .....                                                               | 25        |
+| A.3.1.1                       | GSM-MS has no BA list stored on the SIM.....                                       | 25        |
+| A.3.1.2                       | GSM-MS has a stored BA list on the SIM (optional) .....                            | 25        |
+| A.3.2                         | Cell reselection.....                                                              | 25        |
+| A.3.2.1                       | GSM-MS camping on its home PLMN .....                                              | 25        |
+| A.3.2.2                       | GSM-MS camping on a visited PLMN in home country.....                              | 26        |
+| A.3.3                         | Handover .....                                                                     | 26        |
+| A.4                           | Scenario 3: PLMN and CTS-GFL have locally some common frequencies .....            | 26        |
+| A.4.1                         | Cell selection.....                                                                | 26        |
+| A.4.2                         | Cell reselection.....                                                              | 26        |
+
+A.4.3 Handover ..... 27
+
+A.5 Conclusion ..... 27
+
+Annex B (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 gives an overall description of the lower layers of the radio interface for GSM based Cordless Telephony Systems (GSM-CTS).
+
+The GSM-CTS system is intended to provide a cordless connection between the fixed network and GSM-based CTS Mobile Stations (CTS-MS) via a private CTS Fixed Part (CTS-FP).
+
+Stage 1 is an overall description, from the service subscribers and user's standpoint, that view the network as a single entity which provides service to the user. GSM 02.56 contains the CTS Stage 1 service description.
+
+GSM 03.56 is a Stage 2 document that describes the system architecture of the GSM Cordless Telephone Systems (GSM-CTS), i.e. the system elements, the system interfaces and the functional capabilities.
+
+# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and Acronyms".
+- [2] GSM 02.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephone System (CTS); Service Description; Stage 1".
+- [3] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode".
+- [4] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephone System (CTS); Security related network functions; Stage 2".
+- [5] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); CTS Architecture Description; Stage 2".
+- [6] GSM 04.08: "European digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
+- [7] GSM 05.02 (V6.3): "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path".
+- [8] GSM 05.03 (V6.1): "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [9] GSM 05.04: "Digital cellular telecommunications system (Phase 2+); Modulation".
+- [10] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception".
+- [11] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
+- [12] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**CTS Mobile Station:** GSM-MS supporting CTS.
+
+**CTS Fixed Part:** CTS-FP is a device which acts as a link between the CTS-MS and the fixed network.
+
+**GSM-CTS:** Cordless Telephony System based on GSM.
+
+## 3.2 Abbreviations
+
+The following list describes the abbreviations and acronyms used in the present document. The GSM abbreviations explained in GSM 01.04 [1] are not included below.
+
+|         |                                  |
+|---------|----------------------------------|
+| AFA     | Adaptive Frequency Allocation    |
+| CTS     | Cordless Telephony System        |
+| CTSAGCH | CTS Access Grant CHannel         |
+| CTSARCH | CTS Access Request CHannel       |
+| CTSBCH  | CTS Beacon CHannel               |
+| CTS-FP  | CTS Fixed Part                   |
+| CTS-MS  | CTS Mobile Station               |
+| CTSMSI  | CTS Mobile Subscriber Identity   |
+| CTSPCH  | CTS Paging CHannel               |
+| DPLMN   | Donor Public Land Mobile Network |
+| FPBI    | Fixed Part Beacon Identity       |
+| GFL     | Generic Frequency List           |
+| RX      | Receive                          |
+| TFH     | Total Frequency Hopping          |
+| TX      | Transmit                         |
+
+# --- 4 Main concepts of the CTS radio interface
+
+The main assumption behind the CTS work item and in particular the CTS radio interface, is that a modified single timeslot state of the art GSM-MS chipset could be used for a home base station, i.e. as a CTS-FP.
+
+The CTS radio interface has been designed to meet a requirement of low generated interference, either from the CTS to existing overlaying PLMNS, either from a CTS to another CTS. This requirement is achieved by the combined usage of the three concepts: beacon concept, AFA concept and TFH concept.
+
+## 4.1 Beacon concept
+
+A limited number of CTS-MS shall be served by one CTS-FP (see GSM 02.56). Therefore, a broadcast channel continuously transmitted such as the BCCH in GSM is not needed for CTS.
+
+A channel called CTS beacon channel (CTSBCH) is proposed with the following main characteristics: it is transmitted by the CTS-FP every 26 frames in a 52-multiframe pattern, and allows the CTS-MS to synchronise with the CTS-FP. Minimum signalling is also supported by the CTSBCH, so that it is the only logical channel a CTS-FP shall periodically transmit on the CTS radio interface. Every other logical channel is only transmitted "on demand".
+
+## 4.2 Adaptive Frequency Allocation (AFA) concept
+
+A precise radio frequency planning can not be applied to the CTS-FP/MS pair, as the CTS is intended to be deployed by the end-user. Therefore, a list of frequencies (the GFL) on which it is allowed to operate is given to the CTS. With the AFA, interference measurements will be performed on the frequencies in the GFL to provide a ranking in the AFA table, in order to exclude unacceptably interfered frequencies from the usage in CTS.
+
+## 4.3 Total Frequency Hopping (TFH) concept
+
+The remaining frequencies are used by the Total Frequency Hopping algorithm in order to reduce the interference of the CTS with the overlaying PLMN and other CTS-FP/MS pairs. With TFH the interference caused by the CTS link is spread across multiple GSM links (interference averaging) and the co-channel interference is due to different users at different locations (interference diversity).
+
+A new hopping algorithm which is especially tailored for use in CTS with improved performance compared to the GSM hopping algorithms shall be used.
+
+# --- 5 Radio Transmission and Reception
+
+The CTS-FP and CTS-MS shall in Phase 1 GSM-CTS conform to the transmission and reception specifications of at least one or more of the following cellular standards:
+
+- P-GSM900;
+- E-GSM900;
+- DCS1800;
+- PCS1900.
+
+The final choice of characteristics and performance requirements depends on system scenario calculations.
+
+## 5.1 Frequency Band and Channel Arrangement
+
+The frequency band and channel arrangement for the GSM-CTS are as specified in GSM 05.05 clause 2.
+
+## 5.2 Receiver Characteristics
+
+### 5.2.1 CTS-MS characteristics
+
+It is the intention to keep the CTS-MS characteristics in line with the GSM-MS characteristics as specified in GSM 05.05 clause 5, but the final decision depends on system scenario calculations.
+
+### 5.2.2 CTS-FP characteristics
+
+It is the intention to keep the CTS-FP characteristics in line with the GSM-MS characteristics as specified in GSM 05.05 clause 5, but with reversed frequency bands. The final decision depends on system scenario calculations.
+
+## 5.3 Transmitter Characteristics
+
+### 5.3.1 CTS-MS characteristics
+
+It is the intention to keep the CTS-MS characteristics as far as possible in line with the GSM-MS characteristics as specified in GSM 05.05 clause 4, but the final decision depends on system scenario calculations.
+
+In addition, it is intended to lower the maximum nominal output power and the lowest nominal output power to values which shall be determined by system scenario calculations. Both values could be below the nominal output powers specified in GSM 05.05 subclause 4.1.1.
+
+### 5.3.2 CTS-FP characteristics
+
+It is the intention to keep the CTS-FP characteristics as far as possible in line with the GSM-MS characteristics as specified in GSM 05.05 subclause 4, but with reversed frequency bands. The final decision depends on system scenario calculations.
+
+In addition, it is intended to lower the maximum nominal output power and the lowest nominal output power to values which shall be determined by system scenario calculations. Both values could be below the nominal output powers specified in GSM 05.05 subclause 4.1.1.
+
+## 5.4 CTS transmitter / receiver performance
+
+It is the intention to keep the CTS transmitter / receiver performance in line with the GSM transmitter / receiver performance as specified in GSM 05.05 clause 6.
+
+The GSM requirement on receiver performance for frequency hopping where frequencies are interfered shall be fulfilled by both the CTS-MS and CTS-FP.
+
+# --- 6 Modulation and Raw Data Rates
+
+The modulation technique and raw data rates are as specified in GSM 05.04.
+
+# --- 7 Channel Coding and Interleaving
+
+The channel coding algorithm and interleaving schemes of existing GSM channels used in the GSM CTS radio interface are as specified in GSM 05.03.
+
+Channel coding algorithms and interleaving schemes for new logical channels are defined in clause 10.
+
+# --- 8 Time Slots and TDMA-Frames
+
+The time slot organisation is as specified in GSM 05.02 subclause 4.3.1.
+
+The TDMA frames are organised in multiframe, superframes, and hyperframes. The hyperframe is the longest recurrent time period and consists of  $26 \times 51 \times 2048$  TDMA frames. The TDMA frames are numbered modulo this hyperframe, which means that the frame number FN ranges from 0 to  $FN\_MAX = (26 \times 51 \times 2^{11}) - 1 = 2715647$ . The CTS-FP keeps track of the frame numbering once initialised.
+
+Two types of multiframe exist in the GSM-CTS system:
+
+- a 26-multiframe with a duration of 120 ms, comprising 26 TDMA frames. This multiframe is used to carry TCH, SACCH, and FACCH (see clause 10);
+- a 52-multiframe with a duration of 240 ms, comprising 52 TDMA frames. This multiframe is used to carry CTSBCH, CTSARCH, CTSAGCH and CTSPCH (see clause 10), and is indicated as CTSBCH multiframe.
+
+NOTE: GSM-CTS uses a scheme slightly different from the GSM-based frame structure in that instead of 51-multiframe, 52-multiframe are used. The reason for this choice is that the bursts of the CTSBCH have a frame distance that coincides with the idle frames of a TCH/F connection; it is therefore possible to support in the CTS-FP a speech connection and the CTSBCH transmission in parallel on the same timeslot, which allows the realisation of the CTS-FP hardware with a state of the art chipset for a GSM-MS supporting only a single timeslot.
+
+# --- 9 Bursts
+
+In the physical layer of the GSM-CTS system, three types of burst formats are used:
+
+- Normal Burst (NB);
+- Frequency Correction Burst (FB);
+- Synchronisation Burst (SB).
+
+They are as specified in GSM 05.02 subclause 5.2, with the difference that the synchronisation bursts used in GSM-CTS shall have a specific training sequence, in order to avoid misleading detection of a GSM-CTS synchronisation bursts by a GSM-MS.
+
+# 10 Logical Channels
+
+For the GSM-CTS system, eight logical channels have been specified. There is one traffic channel TCH/F, and there are six signalling channels CTSBCH, CTSARCH, CTSAGCH, CTSPCH, SACCH, and FACCH.
+
+## 10.1 CTS Beacon Channel (CTSBCH)
+
+The CTSBCH logical channel is used to provide frequency and synchronisation information in the downlink direction. From this information the CTS-MS is able to synchronise and to recognise the identity of the CTS-FP. It is made up of a pair of CTSBCH-SB and CTSBCH-FB transmitted in every 52-multiframe.
+
+Signalling mechanisms have been defined in order to reduce emissions from both CTS-FP and CTS-MS.
+
+In cases where the CTS-FP has no resources to handle accesses from a CTS-MS, the CTSBCH shall indicate that no CTS-MS shall attempt to access the CTS-FP.
+
+In order to avoid continuous broadcasting of the CTSPCH, signalling is provided on the CTSBCH that indicates the presence of the CTSPCH.
+
+### 10.1.1 CTSBCH format
+
+- **burst:**
+  - Frequency Correction Burst (FB) is used for the CTSBCH-FB;
+  - Synchronisation Burst (SB) is used for the CTSBCH-SB.
+- **channel coding scheme:** CTSBCH-SB uses the same channel coding scheme as the SCH, specified in GSM 05.03 subclause 4.7. No channel coding is required for CTSBCH-FB.
+
+### 10.1.2 CTSBCH timing
+
+The timing of the CTSBCH is as follows (see figure 1):
+
+- **frame position:**
+  - $FN \bmod 52 = 25$  the CTSBCH-FB is transmitted;
+  - $FN \bmod 52 = 51$  the CTSBCH-SB is transmitted.
+- **timeslot position:** a pair of CTSBCH-SB and CTSBCH-FB shall have the same timeslot position within one 52-multiframe but the position can change from one 52-multiframe to another according to the Beacon timeslot management procedure (see subclause 11.2).
+
+### 10.1.3 CTSBCH radio frequency channel
+
+The CTSBCH is transmitted on the CTSBCH frequency channel, according to the CTSBCH frequency selection, see subclause 12.2.2.
+
+### 10.1.4 CTSBCH-SB information
+
+The CTSBCH-SB carries 25 information bits. These 25 bits shall be divided into five fields as follows:
+
+- a status field indicating whether the CTS-FP has any radio resource available;
+- a flag indicating the presence of the CTSPCH in the next 52-multiframe;
+- a flag indicating whether the CTS-FP is currently performing timeslot shifting (see subclause 11.2) on the CTSBCH;
+- a field indicating the timeslot number of the CTSARCH, CTSAGCH and CTSPCH;
+- the FPBI field indicating the identity of the CTS-FP, in such a way that invalid attachment attempts by CTS-MS which are not enrolled (see GSM 03.56) with this CTS-FP are minimised.
+
+## 10.2 CTS Access Request Channel (CTSARCH)
+
+The CTSARCH is transmitted in the uplink by the CTS-MS to request dedicated radio resources from the CTS-FP; it is also used during the Alive check procedure (see clause 12).
+
+### 10.2.1 CTSARCH format
+
+- Burst: Synchronisation Bursts (SB) are used for the CTSARCH.
+
+NOTE: due to the short distance between the CTS-FP and the CTS-MS, there is no need to use a burst of reduced length like the Access Burst (as specified in GSM 05.02 subclause 5.2).
+
+- Channel coding scheme: same as for the SCH, specified in GSM 05.03 subclause 4.7.
+
+### 10.2.2 CTSARCH timing
+
+The timing of the CTSARCH is as follows (see figure 1):
+
+- frame position:
+  - $FN \bmod 52 = 2$  to 9 for CTSARCH used for the non-hopping access procedure, see subclause 12.3.3.2;
+  - $FN \bmod 52 = 10$  to 15 for CTSARCH used for the hopping access procedure (see subclause 12.3.3.2) and the alive check procedure (see subclause 12.3.2 and subclause 12.3.5).
+- timeslot position: the CTSARCH is transmitted on a timeslot number which shall be indicated in the CTSBCH-SB information bits (see subclause 10.1.4).
+
+### 10.2.3 CTSARCH radio frequency channel
+
+The CTSARCH radio frequency channel is:
+
+- the CTS beacon frequency for the CTSARCH used for the non-hopping access procedure, see subclause 12.3.3.2;
+- mapped on a predefined set of frequencies by the Total Frequency Hopping for the CTSARCH used for the hopping access procedure (see subclause 12.3.3.2) and the alive check procedure (see subclause 12.3.2).
+
+Refer to subclause 10.8.2 for background on the choice of the radio frequency channel.
+
+### 10.2.4 CTSARCH information
+
+The CTSARCH carries 25 information bits forming an access request message. These 25 bits shall be divided into two fields as follows:
+
+- a field indicating the cause of the type of the access request;
+- a field carrying the CTS Mobile Subscriber Identity (CTSMSI) allocated to the CTS-MS.
+
+## 10.3 CTS Access Grant Channel (CTSAGCH)
+
+The CTSAGCH is used in the downlink by the CTS-FP to grant a dedicated RR connection to a CTS-MS that has requested radio resources by the use of the CTSARCH.
+
+### 10.3.1 CTSAGCH format
+
+- Burst: Normal Bursts (NB) are used for the CTSAGCH.
+- Training sequence: it is determined by the three LSBs of the FPBI. These three bits form the 3-bit training sequence code (TSC) which selects one of the eight training sequences specified in GSM 05.02 subclause 5.2.3.
+- Channel coding and interleaving schemes: same as for the SACCH, as specified in GSM 05.03 subclause 4.1, over 4 consecutive bursts.
+
+### 10.3.2 CTSAGCH timing
+
+The timing of the CTSAGCH is as follows (see figure 1):
+
+- frame position:
+  - $FN \bmod 52 = 16$  to 19 for the CTSAGCH used for the non-hopping access procedure, see subclause 12.3.3.2;
+  - $FN \bmod 52 = 20$  to 23 for the CTSAGCH used for the hopping access procedure, see subclause 12.3.3.2.
+- timeslot position: the CTSAGCH is transmitted on a timeslot number which shall be indicated in the CTSBCH-SB information bits (see subclause 10.1.4).
+
+### 10.3.3 CTSAGCH radio frequency channel
+
+The CTSAGCH radio frequency channel is:
+
+- the CTS beacon frequency for the CTSAGCH used for the non-hopping access procedure, see subclause 12.3.3.2;
+- mapped on a predefined set of frequencies by the Total Frequency Hopping for the CTSAGCH used for the hopping access procedure, see subclause 12.3.3.2.
+
+Refer to subclause 10.8.2 for background on the choice of the radio frequency channel.
+
+### 10.3.4 CTSAGCH information
+
+The CTSAGCH carries 23 octets of information, forming a message which directs the CTS-MS to a channel on which the RR connection can be continued. This message provides the CTS-MS with channel and timing information.
+
+## 10.4 CTS Paging Channel (CTSPCH)
+
+The CTSPCH is used in the downlink by the CTS-FP to broadcast information for paging (see subclause 12.3.3.3) and alive check (see subclause 12.3.2) procedures. The presence of the CTSPCH on the physical channel is indicated by a signalling information in the CTSBCH (see subclause 10.1.4).
+
+### 10.4.1 CTSPCH format
+
+- Burst: Normal Bursts (NB) are used for the CTSPCH.
+- Training sequence: it is determined by the three LSBs of the FPBI. These three bits form the 3-bit training sequence code (TSC) which selects one of the eight training sequences specified in GSM 05.02 subclause 5.2.3.
+- Channel coding and interleaving schemes: same as for the SACCH, as specified in GSM 05.03 subclause 4.1, over 4 consecutive bursts.
+
+### 10.4.2 CTSPCH timing
+
+The timing of the CTSPCH is as follows (see figure 1):
+
+- frame position:  $FN \bmod 52 = 2$  to 5;
+- timeslot position: the CTSPCH is transmitted on a timeslot number which shall be indicated in the CTSBCH-SB information bits (see subclause 10.1.4).
+
+### 10.4.3 CTSPCH radio frequency channel
+
+The CTSPCH radio frequency channel is mapped on a predefined set of frequencies by the Total Frequency Hopping algorithm.
+
+Refer to subclause 10.8.2 for background on the choice of the radio frequency channel.
+
+### 10.4.4 CTSPCH information
+
+The CTSPCH contains 23 octets of information, forming the following possible messages:
+
+- a message used for the paging procedure, see subclause 12.3.3.3;
+- a message used for alive check procedure, see subclause 12.3.2.
+
+## 10.5 SACCH
+
+In GSM-CTS, the TDMA frames where the CTSBCH is transmitted ( $FN \bmod 26 = 25$ ) are not available for any SACCH transmission, in contrary to GSM. This results in the requirement that the SACCH multiframe shall span 104 TDMA frames (480 ms) as for GSM, however the interleaving scheme of the 4 SACCH bursts shall be so that no SACCH burst is sent in the TDMA frames:  $FN \bmod 104 = 25, 51, 77$  or  $103$ .
+
+Therefore, the mapping in time of the 4 SACCH/CTS frames onto the physical channel shall be as follows:
+
+- TN = 0 and 1       $FN \bmod 104 = 12, 38, 64, 90$ ;
+- TN = 2 and 3       $FN \bmod 104 = 38, 64, 90, 12$ ;
+- TN = 4 and 5       $FN \bmod 104 = 64, 90, 12, 38$ ;
+- TN = 6 and 7       $FN \bmod 104 = 90, 12, 38, 64$ .
+
+The timing of the SACCH on the 26-multiframe is shown on figure 2.
+
+The SACCH radio frequency channel is mapped on a predefined set of frequencies by the Total Frequency Hopping algorithm, as defined in subclause 10.8.2, except in the case of the non-hopping access procedure (for the attachment or enrolment of a CTS-MS), where the SACCH is mapped on the CTS beacon frequency.
+
+SACCH is a point-to-point dedicated control channel used to transmit signalling messages for the layered GSM-CTS protocol.
+
+## 10.6 FACCH
+
+The standard GSM FACCH as defined in GSM 05.02 is used in GSM-CTS. Full rate FACCH/F is supported.
+
+The timing of the FACCH on the 26-multiframe is shown on figure 2.
+
+The FACCH radio frequency channel is mapped on a predefined set of frequencies by the Total Frequency Hopping algorithm, as defined in subclause 10.8.2, except in the case of the non-hopping access procedure (for the attachment or enrolment of a CTS-MS), where the FACCH is mapped on the CTS beacon frequency.
+
+FACCH is a point-to-point dedicated control channel used to transmit signalling messages for the GSM-CTS layered protocol.
+
+## 10.7 TCH
+
+The traffic channel TCH used in GSM-CTS is the standard GSM traffic channel TCH as defined in GSM 05.02.
+
+The supported channel types shall be:
+
+- TCH/F.
+
+The supported channel modes shall be in the Phase 1 of the GSM-CTS:
+
+- speech v1: full rate speech coder;
+- speech v2: enhanced full rate speech coder;
+- signalling only.
+
+Discontinuous transmission (DTX) shall be supported on the speech TCH.
+
+The timing of the TCH on the 26-multiframe is shown on figure 2.
+
+The TCH radio frequency channel is mapped on a predefined set of frequencies by the Total Frequency Hopping algorithm, as defined in subclause 10.8.2, except in the case of the non-hopping access procedure (for the attachment or enrolment of a CTS-MS), where the TCH is mapped on the CTS beacon frequency.
+
+## 10.8 Mapping of the Logical Channels onto Physical Channels
+
+### 10.8.1 Mapping in time of the logical channels onto the physical channels
+
+The following figures give the mapping in time of the logical channels onto the physical channels.
+
+![Figure 1: 52-multiframe structure diagram showing Downlink and Uplink channel mapping over a 52-multiframe period. Downlink channels include CTSBCH-SB, CTSPCH, CTSAGCH, and CTSBCH-FB. Uplink channels include CTSARCH. Frame numbers (FN mod 52) are indicated from 0 to 25.](bffdddb47fced140f8d17fdc2a29f592_img.jpg)
+
+The diagram illustrates the 52-multiframe structure. The Downlink (DL) shows CTSBCH-SB at frame 0, CTSPCH at frames 1-4, CTSAGCH at frames 15-25, and CTSBCH-FB at frame 25. The Uplink (UL) shows CTSARCH at frames 1-25. The frame numbers are labeled as FN mod 52 = 51 0 1 2 5 6 9 10 15 16 19 20 23 25. A bracket at the bottom indicates the 52-multiframe period.
+
+Figure 1: 52-multiframe structure diagram showing Downlink and Uplink channel mapping over a 52-multiframe period. Downlink channels include CTSBCH-SB, CTSPCH, CTSAGCH, and CTSBCH-FB. Uplink channels include CTSARCH. Frame numbers (FN mod 52) are indicated from 0 to 25.
+
+Figure 1: 52-multiframe structure
+
+![Figure 2: 26-multiframe structure diagram showing Downlink and Uplink channel mapping over two 26-multiframe periods. Downlink channels include CTSBCH-SB, CTSBCH-FB, TCH/FACCH, SACCH, and IDLE. Uplink channels include TCH/FACCH. Frame numbers (FN mod 26) are indicated from 0 to 25.](a7c51c18111139f9aca2805114108565_img.jpg)
+
+The diagram illustrates the 26-multiframe structure. The Downlink (DL) shows CTSBCH-SB at frame 0, CTSBCH-FB at frame 12, and CTSBCH-SB at frame 25. The Uplink (UL) shows TCH/FACCH at frames 0-11 and 13-24. The Downlink (DL) also shows TCH/FACCH at frames 0-11 and 13-24, with IDLE at frame 12. The frame numbers are labeled as FN mod 26 = 25 0 12 25 0 25. A bracket at the bottom indicates two 26-multiframe periods.
+
+Figure 2: 26-multiframe structure diagram showing Downlink and Uplink channel mapping over two 26-multiframe periods. Downlink channels include CTSBCH-SB, CTSBCH-FB, TCH/FACCH, SACCH, and IDLE. Uplink channels include TCH/FACCH. Frame numbers (FN mod 26) are indicated from 0 to 25.
+
+Figure 2: 26-multiframe structure
+
+### 10.8.2 Mapping in frequency of the logical channels onto the physical channels
+
+Prior to its attachment with a CTS-FP, the CTS-MS can not perform hopping as it is not aware of:
+
+- the list of frequencies on which it shall hop: the TFH list (see subclause 12.2.2);
+- the hopping sequence to use with the CTS-FP: this is computed from a set of parameters of the TFH algorithm (see below).
+
+Therefore, the CTSBCH and the channels used in the attachment of a CTS-MS to access the CTS-FP (see non-hopping access procedure: subclause 12.3.3.2.1) are transmitted on the CTS beacon frequency.
+
+After attachment, the CTS-MS has obtained the required information i.e. the TFH list and the parameters for the TFH algorithm, therefore hopping can be performed. All logical channels (except the CTSBCH) are mapped by the TFH algorithm on the TFH list.
+
+The TFH algorithm shall be the Lempel-Greenberger algorithm concatenated with a non-repeating code (LG/NR). The hopping sequence is computed from a codeword which is continuously changing according to the LG/NR algorithm.
+
+### 10.8.3 Permitted Channel Combinations
+
+Due to the change of CTSBCH timeslot position from one 52-multiframe to another (see subclause 11.2), the following channel combinations are allowed on a physical channel:
+
+- (i) CTSBCH + CTSPCH + CTSARCH + CTSAGCH;
+- (ii) CTSPCH + CTSARCH + CTSAGCH;
+- (iii) CTSBCH;
+- (iv) CTSBCH + TCH/F + FACCH/F + SACCH/CTS;
+- (v) TCH/F + FACCH/F + SACCH/CTS.
+
+Channel combinations (i), (iii) and (iv) shall be mutually exclusive in one 52-multiframe, because the CTSBCH is transmitted only once per 52-multiframe.
+
+Channel combinations (i) and (ii) shall be also mutually exclusive.
+
+# --- 11 Lower Layer Procedures
+
+## 11.1 CTSBCH transmission
+
+The CTS-FP shall transmit the CTSBCH on the selected CTSBCH frequency (indicated by the Frequency Management procedure in the RR upper layer, see subclause 12.2.2) at the maximum permitted output power.
+
+## 11.2 CTSBCH timeslot management
+
+In order to further reduce the interference between two CTS-FP and to ease the detection of the CTSBCH of neighbour CTS-FP (for GSM-CTS Phase 2), the timeslot position of the CTSBCH within the TDMA frame where the CTSBCH is transmitted shall not be fixed from one 52-multiframe to another.
+
+A mechanism of CTSBCH timeslot shifting shall be performed on the CTSBCH while the CTS-FP is in RR Idle state (see subclause 12.1). This mechanism shall fulfil the following requirements:
+
+- the shifting sequences of CTSBCH timeslot positions shall be predictable;
+- a high number of shifting sequences shall be generated from a minimum number of parameters.
+
+The mechanism of CTSBCH timeslot shifting is optional while the CTS-FP is in RR Active state (see subclause 12.1), i.e. has established a dedicated RR connection to a CTS-MS. A flag shall indicate in the CTSBCH-SB information bits whether the CTSBCH timeslot shifting is currently performed or not (see subclause 10.1.4).
+
+## 11.3 CTSBCH-FB detection
+
+When triggered by the upper layers, the CTS-MS shall attempt to detect the CTSBCH-FB on the CTSBCH frequency given by the upper layers. When the CTSBCH-FB is detected, it is used by the CTS-MS to update its frequency synchronisation to the CTS-FP.
+
+## 11.4 CTSBCH-SB decoding
+
+When triggered by the upper layers, the CTS-MS shall attempt to decode the CTSBCH-SB on the CTSBCH frequency given by the upper layers. The decoding of the CTSBCH-SB allows the CTS-MS to update its time synchronisation to the CTS-FP.
+
+The CTSBCH-SB information bits shall be sent to the RR upper layer of the CTS-MS: see subclause 12.2.3.
+
+## 11.5 Discontinuous transmission (DTX)
+
+DTX shall be used by the CTS-FP and the CTS-MS. The DTX procedure specified in the relevant GSM 06 series specifications and in GSM 05.08 subclause 8.3 shall be employed.
+
+## 11.6 Interference measurements
+
+A procedure shall be implemented in the CTS-FP by which it estimates the interference level on the uplink frequencies of the Generic Frequency List (GFL).
+
+In the same manner, the CTS-MS shall estimate the interference level on the downlink frequencies of the GFL.
+
+Such interference measurements are periodically triggered by the RR upper layer, i.e. the AFA algorithm: the list of frequencies of the GFL which are to be measured, the required number of samples per frequency and the allowed measurement period, shall be specified.
+
+## 11.7 MS timing offset measurements
+
+When triggered by the upper RR layer, the CTS-FP shall measure the MS timing offset (as specified in GSM 05.10) of the bursts received on the CTS radio interface, i.e. Synchronisation Bursts (SB) and Normal Bursts (NB). The measurements shall be reported to the RR upper layer.
+
+The requirements on the measurement precision are intended to allow the control of the CTS-FP service range, as defined in subclause 12.2.4.
+
+# --- 12 Radio Resource Management Procedures
+
+## 12.1 Radio Resources management states
+
+RR Idle state: for the CTS-FP, the state where it has been initialised (see GSM 03.56); for the CTS-MS, the state where it is attached to a CTS-FP (see GSM 03.56).
+
+RR Active state: the state where the CTS-MS and the CTS-FP have successfully established a dedicated RR connection.
+
+## 12.2 General procedures
+
+### 12.2.1 Initial synchronization of a CTS-MS and CTS-FP
+
+Some procedures, e.g. the enrolment of a CTS-MS, shall require the synchronization of a CTS-FP and CTS-MS, whereas no parameters have yet been exchanged between the CTS-FP and CTS-MS, such as the used CTSBCH frequency. A special procedure shall be implemented in the CTS-FP by which the CTS-MS synchronization, i.e. decoding of the CTSBCH, is eased. This procedure shall include ways for the CTS-MS to detect the CTS beacon frequency more rapidly.
+
+At the end of this procedure, the CTS-FP and CTS-MS are synchronised and can establish a dedicated RR connection if requested by the upper layers.
+
+### 12.2.2 Frequency management
+
+The following figure 3 gives an overview of the frequency management in the CTS-FP and CTS-MS.
+
+The purpose of the frequency management is to avoid that a CTS-FP and a CTS-MS use the same frequencies as the surrounding PLMN and cause a too high interference level to it, to other CTS-FP and to the corresponding MS (GSM or CTS).
+
+![Figure 3: frequency management overview. This flowchart illustrates the frequency management process in a CTS system. It starts with the GFL (m freq.) and parameters being input to the AFA algorithm. The AFA algorithm interacts with the Interference measurements procedure (involving FP and MS) and outputs to the AFA table. The AFA table is then processed by the AFA / TFH interworking block, which also receives parameters and acceptance criteria. This block outputs to the TFH algorithm and the TFH list. The TFH list is then processed by the CTSBCH frequency selection block, which outputs the final frequency f_CTSBCH.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+```
+
+graph LR
+    GFL["GFL (m freq.)"] --> AFA["AFA algorithm"]
+    Params["parameters"] --> AFA
+    AFA <--> Interf["Interference measurements procedure (FP, MS)"]
+    AFA --> AFA_Table["AFA table (1, 2, ..., m)"]
+    AFA_Table --> AFA_TFH["AFA / TFH interworking"]
+    Params2["parameter : acceptance criteria..."] --> AFA_TFH
+    AFA_TFH --> TFH_Algo["TFH algorithm"]
+    AFA_TFH --> TFH_List["TFH list (1, 2, ..., n)"]
+    TFH_List --> CTSBCH["CTSBCH frequency selection"]
+    CTSBCH --> F_CTSBCH["f_CTSBCH"]
+  
+```
+
+Figure 3: frequency management overview. This flowchart illustrates the frequency management process in a CTS system. It starts with the GFL (m freq.) and parameters being input to the AFA algorithm. The AFA algorithm interacts with the Interference measurements procedure (involving FP and MS) and outputs to the AFA table. The AFA table is then processed by the AFA / TFH interworking block, which also receives parameters and acceptance criteria. This block outputs to the TFH algorithm and the TFH list. The TFH list is then processed by the CTSBCH frequency selection block, which outputs the final frequency f\_CTSBCH.
+
+**Figure 3: frequency management overview**
+
+- The GFL is allocated to a certain CTS-FP.
+- The AFA table contains the frequencies of the GFL ranked and ordered by the AFA algorithm (see subclause 12.2.2.2); it is managed by the CTS-FP only.
+- The TFH list is a reduced AFA table: the AFA / TFH interworking procedure (see subclause 12.2.2.3) has excluded some of the frequencies of the AFA table depending on an acceptance threshold and other parameters; the TFH list shall be known by both CTS-FP and CTS-MS, as it is the list of frequencies on which hopping is performed.
+
+The whole management of the frequencies in the CTS system can be sub-divided into the following procedures.
+
+#### 12.2.2.1 Interference measurements exchange
+
+The AFA algorithm shall periodically specify which interference measurements are to be performed on the Lower Layer in both CTS-FP and CTS-MS, then the interference measurements shall be reported from the Lower Layer of the CTS-FP and CTS-MS to the AFA algorithm.
+
+The protocol to request and report the interference measurements shall use a dedicated RR connection (see subclause 12.3.3).
+
+#### 12.2.2.2 Adaptive Frequency Allocation (AFA) algorithm
+
+The AFA algorithm shall perform a ranking with regard to interference measurements (see subclause 11.6), among the frequencies of the GFL, taking into account system parameters.
+
+The reaction time of the AFA algorithm shall decrease in case high interference is measured on the used frequencies, e.g. to adapt to strong changes in the interference environment caused by frequency replanning on the cellular network. It shall, however, be resistant against interference fluctuations caused by short time traffic variations, e.g. day and night traffic.
+
+#### 12.2.2.3 AFA / TFH interworking
+
+A set of frequencies from the AFA table shall be selected by the CTS-FP to be used by the Total Frequency Hopping (TFH) algorithm: this subset is the TFH list. The selection mechanisms shall use parameters, such as an acceptance criteria. All frequencies fulfilling the acceptance criteria shall be part of the TFH list.
+
+#### 12.2.2.4 CTSBCH frequency selection
+
+Any frequency from the TFH list shall be selected as the CTSBCH frequency, i.e. the frequency on which the CTSBCH is transmitted. The CTSBCH frequency can be either the frequency showing the lowest interference level with respect to reported interference measurements, either a random frequency chosen in the TFH list.
+
+### 12.2.3 CTSBCH-SB information
+
+The CTSBCH-SB shall be periodically transmitted by the CTS-FP on the CTS radio interface (see subclause 11.1). The information described in subclause 10.1.4, shall be sent by the CTS-FP at every CTSBCH-SB transmission.
+
+### 12.2.4 Control of CTS-FP service range
+
+The control of the CTS-FP service range can be performed using MS timing offset measurements (as defined in subclause 11.7). Considering the present MS requirements for synchronisation (see GSM 05.10 clause 6), the CTS-FP service range can be only controlled with an accuracy of  $\pm 750$  m.
+
+Methods for increasing this accuracy are needed in order to see if the CTS-FP service range can be restricted to 375 m. They are specified in GSM 05.10.
+
+### 12.2.5 CTS-FP selection
+
+When attempting to attach to a CTS-FP (see GSM 03.56), the CTS-MS shall periodically attempt to detect the CTSBCH-FB (see subclause 11.3) on the CTSBCH frequency. The CTSBCH frequency shall be stored in the CTS-MS for each CTS-FP it is enrolled with.
+
+## 12.3 RR Idle state procedures
+
+### 12.3.1 CTSBCH monitoring
+
+In the RR Idle state, the CTS-MS RR layer shall periodically request the CTS-MS Lower Layer to decode the CTSBCH-SB (see subclause 11.4).
+
+The periodicity of the CTSBCH monitoring shall ensure that synchronisation to the CTS-FP can be maintained and that the response time to information given in the CTSPCH is acceptable.
+
+### 12.3.2 Alive check
+
+The CTS-FP shall periodically verify the presence of its attached CTS-MS. This shall be performed in four steps:
+
+- the CTSPCH indicator flag of the CTSBCH shall indicate the need to decode the next following CTSPCH;
+- the CTS-FP shall transmit on the CTSPCH an alive check message: this message shall contain a CTSMSI, which is used by the CTS-FP to address one particular CTS-MS;
+- the addressed CTS-MS shall transmit an access request message on one of the six CTSARCH which are mapped onto the physical channel as specified in subclause 10.2.2. The choice of the CTSARCH to be used shall be randomly performed;
+- the alive check message shall be maintained on the CTSPCH until the access request message is received from the CTS-MS; however if after a timer has expired, no message is received from the CTS-MS, an alive check failure message shall be sent to the MM upper layer.
+
+### 12.3.3 Establishment of a dedicated RR connection
+
+#### 12.3.3.1 Timeslot assignment for dedicated connection
+
+The timeslot assignment for a dedicated channel shall be based on interference measurements performed by the CTS-FP in the uplink direction on any timeslot of the frequencies of the TFH list. The least interfered timeslot shall be used to establish a dedicated connection.
+
+#### 12.3.3.2 CTS-MS initiated RR connection establishment
+
+When the CTS-MS is willing to establish a dedicated RR connection with a CTS-FP, it shall access the CTS-FP using one of the two following procedures. The choice is dependent on the type of request for dedicated RR connection as triggered by the upper layers: e.g. attachment, CTS-MS initiated call set-up, etc.
+
+##### 12.3.3.2.1 Non-hopping access procedure
+
+An access request message shall be sent by the CTS-MS on the CTSARCH. The CTS-MS shall send two bursts on the CTSARCH: these two bursts shall be sent on two successive frames and shall contain the same access request message. The first sent burst can be used by the CTS-FP to assess the path loss between the CTS-MS and itself, in order to effectively decode the second burst. The choice of the two CTSARCH to be used among the eight CTSARCH which
+
+are mapped onto the physical channel as stated in subclause 10.2.2, shall be randomly performed, with the requirement of the first burst being sent in a TDMA frame with even FN.
+
+On receipt of the access request message, the CTS-FP shall transmit a message on the CTSAGCH which is mapped onto the physical channel as stated in subclause 10.3.2.
+
+This message shall contain the dedicated channel description.
+
+Upon receipt of this message, the CTS-MS shall switch to the assigned channel, set the channel mode to "Signalling only", activate the assigned channel in non-hopping mode and establish the main signalling link. The dedicated RR connection is then considered as established: the CTS-FP shall transmit to the CTS-MS the required information to perform hopping, i.e. the hopping parameters to be used by the Total Frequency Hopping algorithm (see subclause 10.8.2) and the TFH list. Upper layers shall then be informed, in order to perform the required procedure.
+
+##### 12.3.3.2.2 Hopping access procedure
+
+An access request message shall be sent by the CTS-MS on the CTSARCH. The CTS-MS shall send two bursts on the CTSARCH: these two bursts shall be sent on two successive frames and shall contain the same access request message. The first sent burst can be used by the CTS-FP to assess the path loss between the CTS-MS and itself, in order to effectively decode the second burst. The choice of the two CTSARCH to be used among the six CTSARCH which are mapped onto the physical channel as stated in subclause 10.2.2, shall be randomly performed, with the requirement of the first burst being sent in a TDMA frame with even FN.
+
+On receipt of the access request message, the CTS-FP shall transmit a message on the CTSAGCH which is mapped onto the physical channel as stated in subclause 10.3.2. This message shall contain the dedicated channel description.
+
+Upon receipt of this message, the CTS-MS shall switch to the assigned channel, set the channel mode to "Signalling only", activate the assigned channel in hopping mode and establish the main signalling link. The dedicated RR connection is then considered as established: upper layers shall be informed, in order to perform the required procedure.
+
+#### 12.3.3.3 CTS-FP initiated RR connection establishment
+
+When the CTS-FP is willing to establish a dedicated RR connection with a CTS-MS, it shall perform the paging procedure.
+
+The CTSPCH indicator flag of the CTSBCH shall indicate the need for the CTS-MS to decode the next following CTSPCH. Then the CTS-FP shall transmit on the CTSPCH a paging message: this message shall contain a CTMSMI, which is used by the CTS-FP to address one particular CTS-MS.
+
+On receipt of this paging message, the CTS-MS shall perform the hopping access procedure, similar to subclause 12.3.3.2.2.
+
+The paging message shall be maintained on the CTSPCH until the access request message is received from the CTS-MS; however if after a timer has expired, no message is received from the CTS-MS, an paging failure message shall be sent to the MM upper layer.
+
+The dedicated RR connection is then considered as established: upper layers shall be informed, in order to perform the required procedure.
+
+### 12.3.4 CTSBCH failure detection
+
+If the CTSBCH-SB can not be decoded by the CTS-MS performing CTSBCH monitoring, the CTS-MS shall attempts to monitor the CTSBCH again on the next 52-multiframe. If it cannot monitor the CTSBCH for a defined number of consecutive attempts, a CTSBCH failure message shall be sent to the upper layers.
+
+## 12.4 RR Active state procedures
+
+In the RR Active state, a dedicated RR connection has been successfully established between a CTS-MS and a CTS-FP.
+
+### 12.4.1 Radio link failure detection
+
+The radio link failure detection in the CTS-FP and the CTS-MS shall ensure that dedicated RR connection with unacceptable quality, which cannot be improved either by RF power control (see subclause 12.4.2) or intracell handover
+
+(see subclause 12.4.3) shall be released by the CTS-FP or the CTS-MS. A radio link failure message shall be sent to the upper layers.
+
+### 12.4.2 RF power control
+
+In the RR Active state, RF power control shall be employed to minimise the transmit power required by the CTS-MS or the CTS-FP whilst maintaining the quality of the radio link. Both the CTS-MS and CTS-FP shall apply power control in the uplink and downlink.
+
+The output power control level to be used by the CTS-MS shall be determined in the CTS-FP and shall be communicated to the CTS-MS on the SACCH.
+
+The requirements for the power control algorithm are specified in GSM 05.08.
+
+### 12.4.3 Intracell handover
+
+Intracell handover (change of active timeslot) shall be carried out in the case of unacceptable connection quality when in RR Active state. The handover shall be triggered by the CTS-FP.
+
+If an intracell handover is triggered, the CTS-FP shall re-assign another randomly chosen timeslot for the dedicated connection.
+
+### 12.4.4 Channel release
+
+When triggered by the upper layers or if a radio link failure is detected (see subclause 12.4.1), the dedicated RR connection shall be released by the CTS-MS and CTS-FP.
+
+# --- Annex A (informative): GSM backwards compatibility issues
+
+This annex is intended to study the impacts on a GSM-MS behaviour in a PLMN due to the deployment of CTS-FPs in the PLMN coverage area.
+
+This study is split in 3 scenarios:
+
+- Scenario 1: CTS is not operated by PLMN operator, or CTS and GSM are operated in separate bands. It means that PLMN and CTS-GFL have no common frequency in the whole overlapping coverage area;
+- Scenario 2: CTS and GSM are operated in shared band with optimal GFL definition in the considered area. It means that at every given location PLMN and CTS-GFL have no common frequency;
+- Scenario 3: CTS and GSM are operated in shared band with sub-optimal GFL definition for some considered area. It means that at some given locations PLMN and CTS-GFL (then possibly FPs) have common frequencies.
+
+NOTE: PLMN refers either to the home PLMN when the GSM-MS is under its coverage, or the roaming PLMN otherwise.
+
+## --- A.1 Reasons for possible impact of a CTS-FP on a GSM-MS in the PLMN
+
+### A.1.1 Power measurement of BCCH carrier
+
+CTS and GSM potentially share same frequency band. Thus signals emitted by a CTS-FP may impact the power measurement performed by the MS on GSM frequencies.
+
+Signals emitted by a CTS-FP are:
+
+- on the beacon frequency, maximum 6 bursts on 52 frames:
+  - the CTSBCH, permanently, 2 bursts every 52 frames;
+  - part of the CTSAGCH (non hopping), on demand, 4 bursts every 52 frames.
+- on a defined set of frequencies, using Total Frequency Hopping procedure :
+  - the CTSPCH, on demand, 4 bursts every 52 frames;
+  - part of the CTSAGCH (hopping), on demand, 4 bursts every 52 frames;
+  - SACCH, FACCH, TCH/F, for each dedicated connection, total of 50 bursts every 52 frames.
+
+The BCCH carrier power measured by the GSM-MS is according to GSM 05.08 and GSM 03.22 the average on 5 measurements, evenly spread in 5 s.
+
+#### A.1.1.1 Power on CTS-FP beacon frequency seen by the GSM-MS in cell selection
+
+Considering the logical channels mapping for a CTS-FP, the GSM-MS has a maximum probability of  $(6/416)^n$  to see  $(n/5)$  bursts of the CTS-FP beacon in the 5 measurements, i.e. probability 0.014 to see 1/5 of the beacon power, 0.00020 to see 2/5 of the beacon power, ...
+
+#### A.1.1.2 Power on CTS-FP hopping frequencies seen by the GSM-MS in cell selection
+
+On any other frequency, the CTS-FP has to perform Total Frequency Hopping. The power seen by the GSM-MS will depend on the number of frequencies used and the state of the FP (signalling, dedicated connection, ...).
+
+If there is one dedicated connection, one timeslot will be used, spread over the hopped frequencies. For example, when hopping on 8 frequencies, the impact on power is as low as for the beacon frequency.
+
+### A.1.2 Synchronisation of a GSM-MS
+
+CTS and GSM share same burst format for frequency burst (FCH and CTSBCH-FB). Therefore a GSM-MS could perform misleading FCH detection. But the Synchronisation Bursts (SCH and CTSBCH-SB) have different training sequences. A GSM-MS will not be able to decode a CTSBCH-SB. In addition, multiframe scheme is different between BCCH and CTS beacon.
+
+## --- A.2 Scenario 1: PLMN and CTS-GFL have no common frequency in whole coverage area
+
+In this section, we consider that any GFL in the considered PLMN coverage and any BA list in this PLMN never have any common frequency.
+
+This section corresponds mainly to the following cases:
+
+- donor PLMN and CTS are operated in separate bands;
+- the considered PLMN is not a CTS Donor PLMN.
+
+### A.2.1 Cell Selection
+
+#### A.2.1.1 GSM-MS has no BA list stored on the SIM
+
+In this case, the GSM-MS shall scan all frequencies allowed by its type (GSM 900Mhz, 1800Mhz, multi-band, ...), the number of such frequencies being possibly reduced by network parameter such as BA RANGE.
+
+The GSM-MS may see a CTS-FP frequency as the next most powerful frequency and try to find a FCH. If it is not a CTS beacon frequency, frequency burst detection will fail. If it is a CTS beacon frequency, the frequency burst may be detected, but the MS will fail to decode an SCH.
+
+The impact on GSM-MS is an **additional delay of maximum 0,5 s per CTS frequency on which synchronisation is attempted**, i.e. CTS frequency seen with higher power than the BCCH on which the MS is finally camping (see GSM 05.08 subclause 6.2 for maximum delay allowed for synchronisation to a BCCH carrier).
+
+#### A.2.1.2 GSM-MS has a stored BA list on the SIM (optional)
+
+The GSM-MS attempts first to camp on a cell with frequency in that BA list.
+
+If the GSM-MS achieves to camp on a cell with frequency from the BA list, no frequency used by any CTS-FP has been scanned. CTS deployment has **no impact on GSM-MS behaviour**.
+
+If the GSM-MS fails to camp on any cell with frequency from the stored list, the GSM-MS behaviour is like in subclause 2.1.1. The impact on GSM-MS is an **additional delay of maximum 0,5 s per CTS frequency on which synchronisation is attempted**.
+
+### A.2.2 Cell reselection
+
+When camped on a cell, the GSM-MS shall monitor frequencies from the BA list provided on the BCCH.
+
+Since the BA list and GFL have no common frequency, the GSM-MS never monitors CTS-FP frequency. CTS deployment has **no impact on GSM-MS behaviour**.
+
+### A.2.3 Handover
+
+When in connected mode, the GSM-MS shall monitor frequencies from the BA list provided on the SACCH.
+
+Since the BA list and GFL have no common frequency, the GSM-MS never monitors CTS-FP frequency. CTS deployment has **no impact on GSM-MS behaviour**.
+
+## --- A.3 Scenario 2: PLMN and CTS-GFL have locally no common frequency
+
+In this section we consider the locations where the BA list of any covering cell and the GFL of any covering CTS-FP have no common frequency.
+
+This section corresponds to the typical operation of GSM and CTS in shared band with appropriate GFL depending on CTS-FP location.
+
+### A.3.1 Cell Selection
+
+#### A.3.1.1 GSM-MS has no BA list stored on the SIM
+
+The GSM-MS behaviour is same as in scenario 1 (see subclause 2.1.1). The impact on GSM-MS is **an additional delay of maximum 0,5 sec per CTS frequency on which synchronisation is attempted.**
+
+#### A.3.1.2 GSM-MS has a stored BA list on the SIM (optional)
+
+The GSM-MS attempts first to camp on a cell with frequency in that BA list.
+
+Either no CTS-FP transmits on any frequency in the stored BA list, and impacts are similar to scenario 1 (see subclause 2.1.2). This is typically the case when the GSM-MS did not move since BA list was stored.
+
+Or one or more CTS-FPs transmit on frequency in the stored BA list at the MS current location. Then the GSM-MS will perform power measurements on CTS frequencies and possibly attempt to synchronise to them. The impact on GSM-MS is **an additional delay of maximum 0,5 sec per CTS frequency on which synchronisation is attempted.**
+
+### A.3.2 Cell reselection
+
+#### A.3.2.1 GSM-MS camping on its home PLMN
+
+When camped on a cell, the GSM-MS shall monitor frequencies from the BA list provided on the BCCH.
+
+Since the BA list and GFL have locally no common frequency, the GSM-MS never monitors CTS-FP frequency. CTS deployment has **no impact on GSM-MS behaviour.**
+
+#### A.3.2.2 GSM-MS camping on a visited PLMN in home country
+
+When on a VPLMN in home country, the GSM-MS has in addition to search its HPLMN with a period T, T from 6 minutes to 8 hours (this parameter is normally on the SIM, otherwise default value is 30 minutes). So every T minutes the GSM attempts to access its HPLMN. In this case, impact on GSM-MS is, as in subclause 2.1.1., **an additional delay of max 0,5 sec per CTS frequency on which synchronisation is attempted.**
+
+### A.3.3 Handover
+
+When in connected mode, the GSM-MS shall monitor frequencies from the BA list provided on the SACCH.
+
+Since the BA list and GFL have locally no common frequency, the GSM-MS never monitors any CTS-FP frequency. CTS deployment has **no impact on GSM-MS behaviour.**
+
+## --- A.4 Scenario 3: PLMN and CTS-GFL have locally some common frequencies
+
+In this section we consider the locations where the BA list of a covering cell and the GFL of a covering CTS-FP have at least one common frequency.
+
+This clause typically corresponds to GSM and CTS operated in shared band where GFL is sub-optimal for that location. It could happen for example where almost all frequencies are used for BCCH, or at the border between GFL areas.
+
+**One AFA requirement is to avoid that BCCH frequencies are used by a CTS-FP. Then scenario 3 is equivalent to scenario 2.**
+
+However, if this is not achieved (just after a new frequency planning for example), impacts are described hereafter. Note that impacts are similar to those on a GSM-MS in a PLMN where two cells with same BCCH frequency overlap.
+
+### A.4.1 Cell selection
+
+Due to the presence of the CTS-FP, the power measured by the GSM-MS on a BCCH may be higher than its actual value. The ranking of the BCCH power may be modified.
+
+In addition, if the GSM-MS tries to synchronise to such a "double" frequency it may find the CTSBCH-FB before the FCH (probability is 1/5 due to frequency burst repetition schemes). In this case, it will fail to find the SCH at the expected frame, then discard that BCCH.
+
+**The impact is that the GSM-MS could camp on a cell which is not the most powerful.** This is as for a GSM-MS in a PLMN at a location where 2 different BCCH are transmitted on same frequency.
+
+### A.4.2 Cell reselection
+
+Due to the presence of the CTS-FP, the power measured by the GSM-MS on a BCCH from the BA list may be higher than its actual value. The ranking of the 6 strongest BCCH carriers may be modified.
+
+In addition, the first time the GSM-MS tries to decode the BSIC of such a "double" frequency it may find the CTSBCH-FB before the FCH (probability is 1/5 due to FCH and CTSBCH-FB repetition schemes). It will fail to find the SCH at the expected frame, then discard that BCCH candidate. The MS shall attempt a new BSIC decoding every 30 s if the BCCH is still in the 6 strongest surrounding cells, with same probability of failure. Note that if the BSIC is decoded once, the GSM-MS keeps track of the synchronisation and BSIC decoding will not fail anymore.
+
+**The impact is that the GSM-MS ranking of the 6 strongest surrounding cells may be modified, the GSM-MS may camp on a valid but not best cell, and a valid BCCH may be temporarily discarded from the 6 strongest surrounding cells.** This could also happen for a GSM-MS in a PLMN at a location where 2 different BCCH are transmitted on same frequency.
+
+### A.4.3 Handover
+
+Due to the presence of the CTS-FP, the power measured by the GSM-MS on a BCCH from the BA list may be higher than its actual value. The ranking of the 6 strongest BCCH carriers may be modified. It has an impact only if it affects the ranking of a candidate cell for handover.
+
+In addition, the first time the GSM-MS tries to decode the BSIC of such a "double" frequency it may find the CTSBCH-FB before the FCH (probability is 1/5 due to FCH and CTSBCH-FB repetition schemes). It will fail to find the SCH at the expected frame, then discard that BCCH candidate. The MS shall attempt a new BSIC decoding every 10 s if the BCCH stays in the 6 strongest surrounding cells, with same probability of failure. Note that if the BSIC is decoded once, the GSM-MS keep track of the synchronisation and BSIC decoding will not fail anymore.
+
+**The impact is that the GSM-MS ranking of the 6 strongest surrounding cells may be modified, the GSM-MS may handover on a valid but not best cell, and a valid BCCH may be temporarily discarded from the 6 strongest surrounding cells.** This could also happen for a GSM-MS in a PLMN at a location where 2 different BCCH are transmitted on same frequency.
+
+## --- A.5 Conclusion
+
+If GSM and CTS are operated in separated bands (scenario 1), there is no impact on a GSM-MS except a small possible delay for cell selection in some specific cases.
+
+Where GSM and CTS are operated in shared band with proper GFL definition (scenario 2), impacts are same as for scenario 1.
+
+Where GSM and CTS are operated in shared band with sub-optimal GFL definition (scenario 3), AFA aims at having a configuration similar to scenario 2. If this is not achieved, possibly after new frequency planning, the impacts on the GSM-MS are similar to those of a PLMN where two cells overlap with same BCCH frequency.
+
+# Annex B (informative): Change history
+
+| SPEC  | SMG# | CR   | PHASE | VERS  | NEW_VE<br>RS | SUBJECT                                  |
+|-------|------|------|-------|-------|--------------|------------------------------------------|
+| 03.52 | s29  | A005 | R97   | 7.0.1 | 7.1.0        | Modification of access request operation |
+| 03.52 | s31  |      |       | 7.1.0 | 8.0.0        | Version for Release 1999                 |
+| 03.52 |      |      |       | 8.0.0 | 8.0.1        | Version update to 8.0.1 for Publication  |
+
+| Change history |            |          |    |     |                        |        |        |
+|----------------|------------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG GERAN# | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 2001-04        | 4          |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 2002-06        | 10         |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 2005-01        | 23         |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 2007-08        | 35         |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 2008-12        | 40         |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 2009-12        | 44         |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 2011-03        | 49         |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 2012-09        | 55         |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |